Status: Active
Owner: OSHUN Studio Architecture + Bellona Domain Engineering + OSHUN Web +
Program Operations
Last Updated: 2026-02-24
Related:
docs/domains/bellona/features.mddocs/domains/bellona/README.mdapps/oshun/web/src/app/studio/bellona/interchange-asset-cache/page.tsx
Purpose#
Define dedicated navigation entry points and canonical route structure for the Bellona Interchange Asset Cache capability in OSHUN Studio.
This document is the execution artifact for OST-00465.
1. Navigation Entry#
- Studio index entry label:
Open Bellona Interchange Asset Cache workspace - Studio index entry route:
/studio/bellona/interchange-asset-cache - Primary ownership: Bellona Domain Engineering + Studio Web
2. Canonical Route Map#
| Route | Scope | Purpose |
|---|---|---|
/studio/bellona/interchange-asset-cache |
GA entry route | Primary workspace shell for cache inventory and governance controls. |
/studio/bellona/interchange-asset-cache/new |
planned | Create/edit route for cache definitions, retention policies, and templates. |
/studio/bellona/interchange-asset-cache/[cacheId] |
planned | Cache detail route with diagnostics, lineage, and owner context. |
/studio/bellona/interchange-asset-cache/[cacheId]/entries/[entryId] |
planned | Entry detail route for key metadata, payload lineage, and remediation. |
/studio/bellona/interchange-asset-cache/[cacheId]/audit |
planned | Audit route for policy evidence, approvals, and release traceability. |
3. Route Governance Rules#
- All Interchange Asset Cache routes must remain under
/studio/bellona. - Cache detail routes must use stable
cacheIdidentifiers from Bellona cache orchestration records. - Entry detail routes must use stable
entryIdidentifiers linked to cache lineage metadata. - Future route expansion must preserve navigation continuity to the primary workspace route.
4. Acceptance Criteria (OST-00465)#
OST-00465 is complete only when:
- A dedicated studio navigation entry exists for Bellona Interchange Asset Cache.
- The primary route
/studio/bellona/interchange-asset-cacheis implemented. - A canonical route map document exists with planned subroutes and purposes.
- Navigation and routing align with Bellona feature documentation.