Inspect the team before use
Active database publicationBrowser Research & Acceptance
Plans bounded browser research, then runs independent real-page observation and criterion-level acceptance workers in parallel.
Opens the installed OpenCorvus desktop app. The client re-downloads and re-verifies this exact revision, then asks you for an install scope. No desktop app yet? Install OpenCorvus first
Bound execution graph
Workflow and handoffs
The graph shows who owns each step and which earlier result it depends on. It explains the team's collaboration contract; it is not live task progress and does not schedule Agents from the page.
5499805b3 nodes- 01browser-research-plannerPublishes the exact page journey, viewport, interaction, and evidence acceptance allocation.
root - 02browser-evidence-observerCaptures the planned real-page states, interactions, diagnostics, and screenshots.
← browser-research-planner - 03browser-acceptance-reviewerIndependently checks the requested browser claims against the planned evidence contract.
← browser-research-planner
Intended scope
Use when a result depends on current rendered pages, observable browser interaction, and evidence-backed acceptance.
- Product pillarscode + work
- Agent roster3 declared roles
- Declared workflows1 complete responsibility and dependency graphs
- Full capability projection1 Skills · 3 tools · 0 MCP refs
Roles and ownership
This roster comes from the exact package. Agent identity and base role participate in the real runtime; avatars, ratings, and personas do not influence selection.
- Browser Research Planner
delegated-workerDefines the observable goal, page boundary, evidence matrix, interaction scenarios, and stopping conditions. - Browser Evidence Observer
frontend-researchInspects real pages and records dated claims, visible state, source locators, and screenshots against the research matrix. - Browser Acceptance Reviewer
fact-checkIndependently executes the planned acceptance partition and publishes criterion-level pass, fail, blocked, or unverified decisions.
Workflow and handoffs
The graph shows who owns each step and which earlier result it depends on. It explains the team's collaboration contract; it is not live task progress and does not schedule Agents from the page.
browser-evidence-acceptance
Planned Parallel Browser Evidence Acceptance
One Planner fixes the page journey and evidence boundary before observation and acceptance workers execute in parallel.
- 01browser-research-plannerPublishes the exact page journey, viewport, interaction, and evidence acceptance allocation.depends_on: []
- 02browser-evidence-observerCaptures the planned real-page states, interactions, diagnostics, and screenshots.depends_on: browser-research-planner
- 03browser-acceptance-reviewerIndependently checks the requested browser claims against the planned evidence contract.depends_on: browser-research-planner
Capability scope
The full projection includes built-in, default, and package-owned references. The package-owned subset is disclosed separately and never presented as the complete permission surface.
- Full Skill projection1 unique references; 1 are the package-owned subset
- Full tool projection3 unique references; 0 are the package-owned subset
- Full MCP projection0 server/tool/prompt/resource references; 0 are the package-owned subset
- Configuration0 fields · 0 required
Version and provenance
During publication import, the website reconstructs the canonical file tree and complete display facts from the exact ZIP referenced by the signed catalog. The local Manager validates shape, identity, topology, and digest again during install.
- Identitybuiltin/browser-research-acceptance
- Version2026.08.13.1
- Package SHA-2565499805bb716c01d074036e469847d720feb5e463359bb5fc08df3e3df88ac07
This record belongs to the active database publication. The importer checked it field by field against the OpenCorvus-signed catalog, exact ZIP, and content digest. The signing private key never reaches the production server; third-party publisher identity and independent review services are not open yet.
Install boundary
The page can hand this exact revision to an installed OpenCorvus client, or stream its content-addressed ZIP. Neither path installs or activates a team from the web: the client re-downloads the archive, re-verifies its bytes, digest, and shape, and requires an explicit scope.
- 01Resolve the exact revision in the website database, verify ZIP bytes and SHA-256, then hand it to the client or start the download response
- 02Recompute the digest and strictly validate the selected package during client import
- 03Require the operator to choose project or user-global scope
- 04Import atomically through the Manager and return a mutation receipt
- 05Select the installed Squad separately before the active profile changes