Skip to content
OpenCorvus

Inspect the team before use

Active database publication

Advanced

Built-in advanced software delivery team with capability-matched Requirements-to-Architect traceability, execution, testing, interface, and independent-review frontiers.

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 · 6 workflows · 53 nodes · 14 Agents
Bound revisionbdc6db2a
01Planned Delivery8 nodes
  1. 01request-interpreterConfirms intent, inputs, and scope, explicitly recording when no clarification gap remains.root
  2. 02requirement-engineerInventories every Task element and registers complete falsifiable requirements and foundational decisions from current evidence.root
  3. 03source-investigatorInvestigates repository structure and, when projected, current external authority through read-only Skills or clients in parallel with intent and Requirements work.root
  4. 04solution-architectJoins exact intent, RequirementSet, and repository evidence into traceable contracts, individually observable acceptance specs, immutable Delivery Slice revisions, and assembly ownership.← request-interpreter + requirement-engineer + source-investigator
  5. 05workload-reviewerAssesses Slice size, coupling, omitted work, acceptance coverage, and verification cost without architecture authority.← solution-architect
  6. 06implementation-engineerImplements the exact Architect contract in parallel with workload review and records concrete repository and verification evidence.← solution-architect
  7. 07test-engineerExecutes applicable non-UI tests and runtime checks independently after implementation evidence exists.← implementation-engineer
  8. 08system-integrity-reviewerPerforms independent adversarial review after implementation, workload, and executable test evidence exist.← implementation-engineer + test-engineer + workload-reviewer
02Externally Researched Planned Delivery9 nodes
  1. 01request-interpreterConfirms intent, inputs, and scope, explicitly recording when no clarification gap remains.root
  2. 02source-investigatorInvestigates repository structure and projected current-authority sources with read-only repository, Skill, and client operations.root
  3. 03research-investigatorResolves the selected coherent multi-source external fact gap with its projected web research capabilities.root
  4. 04requirement-engineerRegisters complete falsifiable requirements after exact intent, repository, and external evidence settle.← request-interpreter + research-investigator + source-investigator
  5. 05solution-architectBinds the settled RequirementSet and selected evidence into traceable contracts, observable acceptance specs, Delivery Slice revisions, and assembly ownership.← requirement-engineer
  6. 06workload-reviewerAssesses Slice size, coupling, omitted work, acceptance coverage, and verification cost without architecture authority.← solution-architect
  7. 07implementation-engineerUses executable projected capabilities to settle remaining dynamic values and implement the exact Architect contract.← solution-architect
  8. 08test-engineerIndependently rereads authoritative sources and executes applicable non-UI and runtime checks after implementation settles.← implementation-engineer
  9. 09system-integrity-reviewerAudits requirement coverage, source mapping, implementation, workload, and executable Test evidence after all settle.← implementation-engineer + test-engineer + workload-reviewer
03Evidence Investigation3 nodes
  1. 01source-investigatorPerforms read-oriented repository investigation and records source-grounded evidence.root
  2. 02research-investigatorCollects durable multi-source external evidence and separates fact from inference.root
  3. 03claim-verifierVerifies material factual claims against the collected evidence and reports uncertainty.← research-investigator + source-investigator
04Greenfield Interface Delivery10 nodes
  1. 01request-interpreterConfirms the greenfield interface intent, inputs, and scope without inventing a source-interface dependency.root
  2. 02requirement-engineerRegisters falsifiable product, data, interaction, and visual requirements for the original interface.root
  3. 03source-investigatorInvestigates the target repository, design-system implementation surface, and ownership boundaries in parallel with intent and Requirements work.root
  4. 04solution-architectJoins exact intent, RequirementSet, and repository evidence into traceable interface contracts, immutable Delivery Slice revisions, and assembly ownership.← request-interpreter + requirement-engineer + source-investigator
  5. 05interface-designerProduces an original, traceable interface design and implementation contract from the approved requirements and architecture evidence.← solution-architect
  6. 06workload-reviewerChallenges Slice size, ownership, and verification workload in parallel with interface design after the Architect contract exists.← solution-architect
  7. 07implementation-engineerImplements the approved interface contract after design evidence exists while preserving the Architect ownership boundaries.← interface-designer
  8. 08test-engineerExecutes applicable non-UI tests and runtime checks independently after implementation evidence exists.← implementation-engineer
  9. 09interface-integrity-reviewerIndependently reviews implemented interface behavior and rendered evidence.← implementation-engineer
  10. 10system-integrity-reviewerReviews requirement, contract, implementation, workload, and executable test evidence independently of interface review.← implementation-engineer + test-engineer + workload-reviewer
05Greenfield Interface Delivery With Independent Visual Review11 nodes
  1. 01request-interpreterConfirms the greenfield interface intent, inputs, and scope without inventing a source-interface dependency.root
  2. 02requirement-engineerRegisters falsifiable product, data, interaction, and visual requirements for the original interface.root
  3. 03source-investigatorInvestigates the target repository, design-system implementation surface, and ownership boundaries in parallel with intent and Requirements work.root
  4. 04solution-architectJoins exact intent, RequirementSet, and repository evidence into traceable interface contracts, immutable Delivery Slice revisions, and assembly ownership.← request-interpreter + requirement-engineer + source-investigator
  5. 05interface-designerProduces an original, traceable interface design and implementation contract from the approved requirements and architecture evidence.← solution-architect
  6. 06workload-reviewerChallenges Slice size, ownership, and verification workload in parallel with interface design after the Architect contract exists.← solution-architect
  7. 07implementation-engineerImplements the approved interface contract after design evidence exists while preserving the Architect ownership boundaries.← interface-designer
  8. 08test-engineerExecutes applicable non-UI tests and runtime checks independently after implementation evidence exists.← implementation-engineer
  9. 09visual-reviewerReviews the real rendered implementation and interaction states in parallel with testing and independent integrity review.← implementation-engineer
  10. 10interface-integrity-reviewerIndependently reviews implemented interface behavior and rendered evidence without consuming the Visual Reviewer's verdict.← implementation-engineer
  11. 11system-integrity-reviewerReviews requirement, contract, implementation, workload, and executable test evidence independently of visual and interface review.← implementation-engineer + test-engineer + workload-reviewer
06Supplied-Reference Interface Delivery12 nodes
  1. 01interface-investigatorCaptures structure, behavior, states, assets, and reference evidence from exactly one operator-supplied source interface URL.root
  2. 02request-interpreterConfirms intent, inputs, and scope in parallel with Requirements and direct interface observation.root
  3. 03requirement-engineerRegisters falsifiable product, interaction, fidelity, and acceptance requirements from the complete request.root
  4. 04source-investigatorInvestigates the target repository and ownership boundaries in parallel with source-interface observation and Requirements work.root
  5. 05solution-architectJoins direct interface, intent, RequirementSet, and repository evidence into traceable contracts and immutable Delivery Slice revisions.← interface-investigator + request-interpreter + requirement-engineer + source-investigator
  6. 06interface-designerProduces a traceable interface design and implementation contract from the supplied-reference and Architect evidence.← solution-architect
  7. 07workload-reviewerChallenges Slice size, ownership, and visual verification workload in parallel with interface design.← solution-architect
  8. 08implementation-engineerImplements the supplied-reference interface contract after design evidence exists.← interface-designer
  9. 09test-engineerExecutes applicable non-UI tests and runtime checks independently after implementation evidence exists.← implementation-engineer
  10. 10visual-reviewerReviews the real rendered result, interactions, and reference fidelity in parallel with testing and independent review.← implementation-engineer
  11. 11interface-integrity-reviewerIndependently reviews implemented interface behavior and rendered evidence without consuming the Visual Reviewer's verdict.← implementation-engineer
  12. 12system-integrity-reviewerReviews requirement, contract, implementation, workload, and executable test evidence independently of visual and interface review.← implementation-engineer + test-engineer + workload-reviewer
Evidence output6

Intended scope

Use for advanced software delivery that requires capability-matched Requirements-to-Architect traceability, execution evidence, and independent review without a narrower installed expert contract.

  • Product pillarscode + work
  • Agent roster14 declared roles
  • Declared workflows6 complete responsibility and dependency graphs
  • Full capability projection2 Skills · 7 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/advanced@2026.08.22.6package sha256:bdc6db2afdab074f962343d66efeb834b59199abef93b227bdf8fd17f83b0427

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

planned-delivery

Planned Delivery

  1. 01request-interpreterdepends_on: []
  2. 02requirement-engineerdepends_on: []
  3. 03source-investigatordepends_on: []
  4. 04solution-architectdepends_on: request-interpreter, requirement-engineer, source-investigator
  5. 05workload-reviewerdepends_on: solution-architect
  6. 06implementation-engineerdepends_on: solution-architect
  7. 07test-engineerdepends_on: implementation-engineer
  8. 08system-integrity-reviewerdepends_on: implementation-engineer, test-engineer, workload-reviewer

researched-planned-delivery

Externally Researched Planned Delivery

  1. 01request-interpreterdepends_on: []
  2. 02source-investigatordepends_on: []
  3. 03research-investigatordepends_on: []
  4. 04requirement-engineerdepends_on: request-interpreter, research-investigator, source-investigator
  5. 05solution-architectdepends_on: requirement-engineer
  6. 06workload-reviewerdepends_on: solution-architect
  7. 07implementation-engineerdepends_on: solution-architect
  8. 08test-engineerdepends_on: implementation-engineer
  9. 09system-integrity-reviewerdepends_on: implementation-engineer, test-engineer, workload-reviewer

evidence-investigation

Evidence Investigation

  1. 01source-investigatordepends_on: []
  2. 02research-investigatordepends_on: []
  3. 03claim-verifierdepends_on: research-investigator, source-investigator

greenfield-interface-delivery

Greenfield Interface Delivery

  1. 01request-interpreterdepends_on: []
  2. 02requirement-engineerdepends_on: []
  3. 03source-investigatordepends_on: []
  4. 04solution-architectdepends_on: request-interpreter, requirement-engineer, source-investigator
  5. 05interface-designerdepends_on: solution-architect
  6. 06workload-reviewerdepends_on: solution-architect
  7. 07implementation-engineerdepends_on: interface-designer
  8. 08test-engineerdepends_on: implementation-engineer
  9. 09interface-integrity-reviewerdepends_on: implementation-engineer
  10. 10system-integrity-reviewerdepends_on: implementation-engineer, test-engineer, workload-reviewer

greenfield-interface-visual-delivery

Greenfield Interface Delivery With Independent Visual Review

  1. 01request-interpreterdepends_on: []
  2. 02requirement-engineerdepends_on: []
  3. 03source-investigatordepends_on: []
  4. 04solution-architectdepends_on: request-interpreter, requirement-engineer, source-investigator
  5. 05interface-designerdepends_on: solution-architect
  6. 06workload-reviewerdepends_on: solution-architect
  7. 07implementation-engineerdepends_on: interface-designer
  8. 08test-engineerdepends_on: implementation-engineer
  9. 09visual-reviewerdepends_on: implementation-engineer
  10. 10interface-integrity-reviewerdepends_on: implementation-engineer
  11. 11system-integrity-reviewerdepends_on: implementation-engineer, test-engineer, workload-reviewer

reference-interface-delivery

Supplied-Reference Interface Delivery

  1. 01interface-investigatordepends_on: []
  2. 02request-interpreterdepends_on: []
  3. 03requirement-engineerdepends_on: []
  4. 04source-investigatordepends_on: []
  5. 05solution-architectdepends_on: interface-investigator, request-interpreter, requirement-engineer, source-investigator
  6. 06interface-designerdepends_on: solution-architect
  7. 07workload-reviewerdepends_on: solution-architect
  8. 08implementation-engineerdepends_on: interface-designer
  9. 09test-engineerdepends_on: implementation-engineer
  10. 10visual-reviewerdepends_on: implementation-engineer
  11. 11interface-integrity-reviewerdepends_on: implementation-engineer
  12. 12system-integrity-reviewerdepends_on: implementation-engineer, test-engineer, workload-reviewer

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.