Inspect the team before use
Active database publicationBase
Built-in Planner-first Expert Squad for compact capability-matched delivery and independent verification of the settled result.
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.
cd34635d3 nodes- 01base-plannerPublishes the complete Task-element inventory, discovery obligations, capability allocation, and acceptance contract.
root - 02base-developerUses projected Skills and executable tools to discover dynamic sources and complete the requested delivery.
← base-planner - 03base-testerIndependently rereads dynamic sources and verifies the settled result criterion by criterion.
← base-developer
4 nodes- 01base-plannerPublishes the complete Task-element inventory, stable acceptance criteria, shared inputs, owned paths, and acceptance allocation.
root - 02base-researcherExecutes the plan's evidence and repository research partition.
← base-planner - 03base-developerExecutes the plan's implementation partition and its implementation-owned checks.
← base-planner - 04base-testerExecutes every planned acceptance criterion against the settled result and records criterion-by-criterion evidence.
← base-developer
Intended scope
Use Base for one compact Task planned once, executed by capability-matched owners, then independently verified against the settled result.
- Product pillarscode + work
- Agent roster4 declared roles
- Declared workflows2 complete responsibility and dependency graphs
- Full capability projection1 Skills · 11 tools · 17 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.
- Base Researcher
explorePerforms read-oriented repository and relevant external research and publishes the canonical Base research report. - Base Planner
delegated-workerPublishes one capability-matched Task implementation plan after read-only current-authority discovery, without mutating external state, editing product files, or creating Goal-derived planning facts. - Base Developer
buildConsumes the selected Base implementation plan, changes the repository, performs implementation-owned checks, and publishes the development report. - Base Tester
delegated-workerIndependently verifies the settled implementation against the original request and the plan's acceptance criteria through the final diff, executable checks, and rendered evidence, and publishes the canonical test report.
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.
planner-execution-verification
Planner, Execution, and Verification
Plan once, execute source discovery and delivery with a command-capable owner, then independently verify the settled result.
- 01base-plannerPublishes the complete Task-element inventory, discovery obligations, capability allocation, and acceptance contract.depends_on: []
- 02base-developerUses projected Skills and executable tools to discover dynamic sources and complete the requested delivery.depends_on: base-planner
- 03base-testerIndependently rereads dynamic sources and verifies the settled result criterion by criterion.depends_on: base-developer
planner-parallel-delivery
Planner, Parallel Workers, and Verification
Publish one bounded Task plan, run the research and implementation partitions in the same dependency-ready frontier, then verify the settled result.
- 01base-plannerPublishes the complete Task-element inventory, stable acceptance criteria, shared inputs, owned paths, and acceptance allocation.depends_on: []
- 02base-researcherExecutes the plan's evidence and repository research partition.depends_on: base-planner
- 03base-developerExecutes the plan's implementation partition and its implementation-owned checks.depends_on: base-planner
- 04base-testerExecutes every planned acceptance criterion against the settled result and records criterion-by-criterion evidence.depends_on: base-developer
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 projection11 unique references; 0 are the package-owned subset
- Full MCP projection17 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/base
- Version2026.08.22.4
- Package SHA-256cd34635d41bc1d6652a23ec4e5bb78c9361a7e8fafa6834446b1f62d4cbaf29b
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