Inspect the team before use
Active database publicationKnowledge Base Operations
Parallel source mapping, change editing, and lifecycle governance joined into a traceable knowledge publication record.
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.
b7cd93114 nodes- 01knowledge-source-curatorPublishes the source, claim, and destination map.
root - 02knowledge-change-editorPublishes the canonical knowledge update proposal and material diff.
root - 03knowledge-lifecycle-governorPublishes ownership, review, deprecation, replacement, and publication controls.
root - 04knowledge-publication-integratorJoins source, change, and lifecycle evidence into the final publication record.
← knowledge-change-editor + knowledge-lifecycle-governor + knowledge-source-curator
Intended scope
Use to add, update, deprecate, or replace governed knowledge with exact source, destination, lifecycle, and publication evidence.
- Product pillarswork
- Agent roster4 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.
- Knowledge Source Curator
deep-researchMaps authoritative source claims to exact knowledge destinations with conflicts and freshness evidence. - Knowledge Change Editor
delegated-workerPrepares canonical additions or revisions with stable keys, material diffs, and dependency impacts. - Knowledge Lifecycle Governor
fact-checkDefines ownership, review, approval, deprecation, replacement, retention, and correction controls. - Knowledge Publication Integrator
buildJoins source, change, and lifecycle evidence into the canonical prepared publication record.
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.
grounded-knowledge-release
Source-grounded Knowledge Release
Run source mapping, change editing, and lifecycle governance independently, then join them into a traceable publication record.
- 01knowledge-source-curatorPublishes the source, claim, and destination map.depends_on: []
- 02knowledge-change-editorPublishes the canonical knowledge update proposal and material diff.depends_on: []
- 03knowledge-lifecycle-governorPublishes ownership, review, deprecation, replacement, and publication controls.depends_on: []
- 04knowledge-publication-integratorJoins source, change, and lifecycle evidence into the final publication record.depends_on: knowledge-change-editor, knowledge-lifecycle-governor, knowledge-source-curator
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/knowledge-base-operations
- Version2026.08.13.1
- Package SHA-256b7cd9311084fcc29a5e2ac774163bc881c25ec7fc7a7f416bb9e77bbaf1e3cc8
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