Inspect the team before use
Active database publicationOffice Delivery
Develops new source-backed PPTX presentations through parallel content and format planning plus the qualified Work Artifact lifecycle.
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.
dbe8a33e3 nodes- 01office-delivery-plannerPublishes the source boundary, document structure, formatting system, and acceptance allocation.
root - 02office-source-analystValidates source facts, citations, data, and content completeness.
← office-delivery-planner - 03office-delivery-builderBuilds, renders, and visually inspects the planned Office deliverable.
← office-delivery-planner
Intended scope
Use for a new editable PPTX presentation that requires traceable content, a real chart, fresh renders, and canonical validation.
- Product pillarswork
- Agent roster3 declared roles
- Declared workflows1 complete responsibility and dependency graphs
- Full capability projection2 Skills · 7 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.
- Office Source Analyst
deep-researchBuilds the dated source, claim, calculation, citation, terminology, and missing-input model. - Office Delivery Builder
buildBuilds editable deliverables and canonical exports directly from the Planner contract and original sources, then renders and inspects them. - Office Delivery Planner
delegated-workerPublishes the source boundary, document structure, formatting system, worker partition, and acceptance allocation.
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.
planned-office-delivery
Planned Parallel Office Delivery
One Planner fixes the source and formatting contract before source and build workers execute in parallel; no separate visual-review Agent exists.
- 01office-delivery-plannerPublishes the source boundary, document structure, formatting system, and acceptance allocation.depends_on: []
- 02office-source-analystValidates source facts, citations, data, and content completeness.depends_on: office-delivery-planner
- 03office-delivery-builderBuilds, renders, and visually inspects the planned Office deliverable.depends_on: office-delivery-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 projection2 unique references; 1 are the package-owned subset
- Full tool projection7 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/office-delivery
- Version2026.08.13.4
- Package SHA-256dbe8a33e68348011e9cd427f17f7ebdc4a12b8cce1b578607a92a10613b36373
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