Inspect the team before use
Active database publicationFrontend Replica
Source URL and reference-screenshot replica with a desktop surface ledger, rendered proof, durable catalog facts, and visible narrative Turn summaries.
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.
3be052214 nodes- 01frontend-replica-plannerPublishes source closure, region ownership, modeling contract, and acceptance allocation.
root - 02frontend-replica-intent-analystChecks target intent and requested fidelity against the planned source closure.
← frontend-replica-planner - 03frontend-replica-source-researcherCaptures source structure, behavior, states, and assets for its partition.
← frontend-replica-planner - 04frontend-replica-interface-modelerProduces the planned interface model and mapping evidence.
← frontend-replica-planner
7 nodes- 01frontend-replica-plannerPublishes source closure, target region ownership, implementation contract, and acceptance allocation.
root - 02frontend-replica-explorerInvestigates target repository primitives and owned implementation paths.
← frontend-replica-planner - 03frontend-replica-intent-analystChecks task intent and fidelity boundaries.
← frontend-replica-planner - 04frontend-replica-source-researcherCaptures exact source evidence for its assigned regions.
← frontend-replica-planner - 05frontend-replica-interface-modelerProduces the planned interface mapping and component contract.
← frontend-replica-planner - 06frontend-replica-workload-analystChallenges region partition, ownership, and verification workload.
← frontend-replica-planner - 07frontend-replica-implementerImplements assigned regions and captures its own real rendered comparison evidence.
← frontend-replica-planner
Intended scope
Use for source URL or reference-screenshot desktop replica work with evidence-backed parity.
- Product pillarscode
- Agent roster7 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.
- Frontend Replica Explorer
exploreLocates target implementation surfaces, assets, primitives, and integration constraints. - Frontend Replica Intent Analyst
intent-analysisClassifies source, target, desktop scope, evidence gaps, and parity obligations. - Frontend Replica Interface Modeler
frontend-designGenerates the sole task-scoped source-bound interface model and implementation contract. - Frontend Replica Source Researcher
frontend-researchCaptures source-page structure, state, content, interaction, and screenshot evidence. - Frontend Replica Workload Analyst
goal-workload-analystSizes source evidence, surface implementation, interaction, and visual verification work. - Frontend Replica Implementer
buildImplements the same source-bound surface in the target project. - Frontend Replica Planner
delegated-workerPublishes one source-bound replica plan, region ownership map, and acceptance allocation for parallel specialist execution.
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.
interface-modeling
Planned Parallel Interface Modeling
One source-bound Planner partitions modeling work before intent, source, and interface-model workers execute in parallel.
- 01frontend-replica-plannerPublishes source closure, region ownership, modeling contract, and acceptance allocation.depends_on: []
- 02frontend-replica-intent-analystChecks target intent and requested fidelity against the planned source closure.depends_on: frontend-replica-planner
- 03frontend-replica-source-researcherCaptures source structure, behavior, states, and assets for its partition.depends_on: frontend-replica-planner
- 04frontend-replica-interface-modelerProduces the planned interface model and mapping evidence.depends_on: frontend-replica-planner
source-replica
Planned Parallel Source Replica
One source-bound Planner partitions the complete replica before repository, source, modeling, workload, implementation, and intent workers execute in parallel.
- 01frontend-replica-plannerPublishes source closure, target region ownership, implementation contract, and acceptance allocation.depends_on: []
- 02frontend-replica-explorerInvestigates target repository primitives and owned implementation paths.depends_on: frontend-replica-planner
- 03frontend-replica-intent-analystChecks task intent and fidelity boundaries.depends_on: frontend-replica-planner
- 04frontend-replica-source-researcherCaptures exact source evidence for its assigned regions.depends_on: frontend-replica-planner
- 05frontend-replica-interface-modelerProduces the planned interface mapping and component contract.depends_on: frontend-replica-planner
- 06frontend-replica-workload-analystChallenges region partition, ownership, and verification workload.depends_on: frontend-replica-planner
- 07frontend-replica-implementerImplements assigned regions and captures its own real rendered comparison evidence.depends_on: frontend-replica-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 projection1 unique references; 1 are the package-owned subset
- Full tool projection11 unique references; 2 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/frontend-replica
- Version2026.08.13.1
- Package SHA-2563be05221a063acf5d7f9882a1a06abf94444b49dda1f43eb2b18d846e57036a6
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