Skip to content
OpenCorvus

Inspect the team before use

Active database publication

Base

Compact outcome delivery through capability-matched execution and independent verification; planning and parallel research only when needed.

Install in OpenCorvusDownload this exact revisionTrust model

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.

Bound revision · 3 workflows · 8 nodes · 4 Agents
Bound revision7c457a90
01Execution and Independent Verification1 nodes
  1. 01base-testerIndependently rereads dynamic sources and verifies the settled result criterion by criterion.root
02Source Planning, Execution, and Independent Verification3 nodes
  1. 01base-plannerSeparates execution-authority conditions, applicable constraints, and Developer-owned outcome semantics and destination execution dependencies; resolves traceable source obligations through a bounded minimal-anchor worklist before mutation.root
  2. 02base-developerReconciles per-operation source classes with original authority, owns destination discovery for operations whose real prerequisites are resolved, performs the authorized mutation, and hands off the complete Host-recorded receipt.← base-planner
  3. 03base-testerIndependently checks source classifications and coordinates against original authority, then maps applicable rules and outcome semantics to the raw mutation receipt and any correct same-record destination read.← base-developer
03Planner, Parallel Workers, and Verification4 nodes
  1. 01base-plannerPublishes the complete Task-element inventory, stable acceptance criteria, shared inputs, owned paths, and acceptance allocation.root
  2. 02base-researcherExecutes the plan's evidence and repository research partition.← base-planner
  3. 03base-developerExecutes the plan's implementation partition and its implementation-owned checks.← base-planner
  4. 04base-testerExecutes every planned acceptance criterion against the settled result and records criterion-by-criterion evidence.← base-developer
Evidence output3

Intended scope

Use Base for one complete Task executed by one capable owner and independently verified against the actual outcome.

  • Product pillarscode + work
  • Agent roster4 declared roles
  • Declared workflows3 complete responsibility and dependency graphs
  • Full capability projection1 Skills · 17 tools · 17 MCP refs

Walkthrough pinned revision

Role and dependency walkthrough

This workflow explanation is pinned to the current package digest. It is not a running Agent session, timer, or generated language-model output. Real execution occurs in the OpenCorvus client.

builtin/base@2026.10.12.1package sha256:7c457a9059e6adcd6686e226695fca0f80bdb7dd7945939b7d69c216e52f56be

A node becomes schedulable only after its depends_on evidence is terminal. This page explains that contract and does not advance runtime state.

execution-verification

Execution and Independent Verification

  1. 01base-testerdepends_on: []

source-planned-execution-verification

Source Planning, Execution, and Independent Verification

  1. 01base-plannerdepends_on: []
  2. 02base-developerdepends_on: base-planner
  3. 03base-testerdepends_on: base-developer

planner-parallel-delivery

Planner, Parallel Workers, and Verification

  1. 01base-plannerdepends_on: []
  2. 02base-researcherdepends_on: base-planner
  3. 03base-developerdepends_on: base-planner
  4. 04base-testerdepends_on: base-developer

Install handoff boundary

The OpenCorvus client owns the real scope choice when a later import is performed. This page only explains project and global behavior and does not submit an install itself.

The client requires an explicit scope

Project scopeApplies only inside the current project; the same package ID overrides a global installation.
User-global scopeAvailable to the current user, but never silently overrides a project installation.

The public page hands over one exact revision, or completes a signed bundle download. It never batch-installs or activates a team. The scope explanation describes client responsibility; it is not a web form that can be submitted.