Trying an assisted review

Use the existing context tools and bridge the remaining intake and evidence steps with a founder during early access.

Pilot Updated 2026-09-28

Bring one real task and a change to review. We agree which material may be shared and any model-provider use before accessing it. Keep your existing tracker; using the Orneos workspace is optional for this assisted workflow. You do not need to migrate your board or connect a repository to request a pilot. We prepare authorized external material with you; automated task and GitHub connections are planned and tracker connectors are not released yet.

1. Choose one change

Pick an existing task and a pull request with a specific commit to inspect. Write down the goal, acceptance criteria and exclusions, or use an approved Orneos Intent. Avoid sending repository secrets or private material before we agree how it will be handled.

Request early access. Tell us what is difficult about reviewing this change and which tools you already use. A pilot request does not require an app account or a migrated board.

2. Agree the material and prepare the review

We agree access, permitted tools and model use, output format and retention with you. Supply the authorised task, agreement and exact change, plus relevant checks or test results you have. We identify missing material explicitly. A link alone is not evidence that we have permission to open it or that we inspected it.

3. Read the result criterion by criterion

The review connects the agreement to the material actually examined. Here is a fictional teaching example using the CSV change from the quickstart, not a customer result or an automated app screen:

Agreed criterionExample material inspectedAssessment and next action
Only matching issues are exportedA test at the supplied commit checks a filtered set against the exported rows.Evidence supports the tested case; inspect whether other filter combinations need coverage.
Visible columns keep their displayed orderExport code was inspected, but no reordered-column test was supplied.Insufficient evidence for the full criterion; request a test with reordered columns.
Empty results produce headers and no issue rowsNo empty-result output or test was available.Unverified; ask the author to demonstrate the empty case before accepting that criterion.

The actual review names the concrete sources and revision inspected, what preparation was manual, and what remains unknown. If the pull request changes afterwards, reassess the affected criteria against the new revision.

4. Make and record your decision

The human reviewer decides what to accept, send back or leave unresolved. Record that decision in your existing review workflow, naming the agreement and exact change it covers. Ask the author for missing evidence where needed. Assistance does not approve or merge your work.

Check that the review was useful: you can identify the agreement, inspected revision, evidence for each assessed criterion, unanswered questions and next action. If any of those is missing, ask us to make it explicit before using the result.

Use the product where it already helps

For work in Orneos, use Intent to confirm the agreement and Copy context bundle to assemble available task context. These are existing features, not notes a founder has to collect for you.

For external work, we can help bring authorized material together, identify the exact revision, locate relevant checks and map criteria to evidence. The delivered review says which steps were manual, which sources were inspected and which were unavailable. We agree its format and retention with you.

You make the decision

Your reviewer inspects the evidence and decides what to accept, send back or leave unresolved. Assistance does not approve or merge your work. A decision covers the agreement and artifact actually examined.

What we learn

We measure preparation and review effort, consequential omissions, review quality, voluntary reuse and willingness to continue. This helps improve the active context-delivery, capture and review work without making customers wait for the broader platform.

Request early access, or read Getting the right context for the exact automation gaps.

Something here wrong, missing or out of date? Tell us at support@orneos.com — corrections to these pages are welcome and we would rather hear it than have you work around it.