Inspect the team before use
Active database publicationLocalization & Adaptation
Parallel terminology, locale adaptation, and linguistic quality work joined into a source-controlled locale release pack.
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.
97a59cd64 nodes- 01localization-terminology-stewardPublishes the contextual terminology and protected-token register.
root - 02localization-locale-adapterPublishes the locale-adapted content and adaptation log.
root - 03localization-linguistic-qaPublishes the independent linguistic quality review or preflight matrix.
root - 04localization-release-integratorJoins terminology, adaptation, and quality evidence into the final locale release pack.
← localization-linguistic-qa + localization-locale-adapter + localization-terminology-steward
Intended scope
Use for terminology-controlled adaptation to a named language-locale pair with explicit linguistic quality 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.
- Localization Terminology Steward
delegated-workerBuilds the contextual term register, protected-token inventory, and source ambiguity record. - Locale Adaptation Specialist
delegated-workerAdapts stable source content for the named locale, audience, channel, and format constraints. - Linguistic Quality Reviewer
fact-checkIndependently checks accuracy, fluency, terminology, locale conventions, tokens, and review coverage. - Localization Release Integrator
buildJoins terminology, adaptation, and linguistic quality evidence into the locale release pack.
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.
locale-release-pack
Locale Release Pack
Run terminology, locale adaptation, and linguistic quality work independently, then join them into one release pack.
- 01localization-terminology-stewardPublishes the contextual terminology and protected-token register.depends_on: []
- 02localization-locale-adapterPublishes the locale-adapted content and adaptation log.depends_on: []
- 03localization-linguistic-qaPublishes the independent linguistic quality review or preflight matrix.depends_on: []
- 04localization-release-integratorJoins terminology, adaptation, and quality evidence into the final locale release pack.depends_on: localization-linguistic-qa, localization-locale-adapter, localization-terminology-steward
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/localization-adaptation
- Version2026.08.13.1
- Package SHA-25697a59cd65a9bfe681be411324d0d117dd537dd9076feb468edf868c442b9f490
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