# OSHUN Studio Bellona Format Registry Route Map

Status: Active  
Owner: OSHUN Studio Architecture + Bellona Domain Engineering + OSHUN Web +
Program Operations  
Last Updated: 2026-02-24  
Related:

- `docs/domains/bellona/features.md`
- `docs/domains/bellona/README.md`
- `apps/oshun/web/src/app/studio/bellona/format-registry/page.tsx`

## Purpose

Define dedicated navigation entry points and canonical route structure for the
Bellona Format Registry capability in OSHUN Studio.

This document is the execution artifact for `OST-00483`.

## 1. Navigation Entry

- Studio index entry label: `Open Bellona Format Registry workspace`
- Studio index entry route: `/studio/bellona/format-registry`
- Primary ownership: Bellona Domain Engineering + Studio Web

## 2. Canonical Route Map

| Route                                                             | Scope          | Purpose                                                                      |
| ----------------------------------------------------------------- | -------------- | ---------------------------------------------------------------------------- |
| `/studio/bellona/format-registry`                                 | GA entry route | Primary workspace shell for format registry catalog and governance controls. |
| `/studio/bellona/format-registry/new`                             | planned        | Create/edit route for format definitions and handler metadata.               |
| `/studio/bellona/format-registry/[formatId]`                      | planned        | Format detail route with compatibility diagnostics and lifecycle context.    |
| `/studio/bellona/format-registry/[formatId]/versions/[versionId]` | planned        | Version route for schema diff, migration evidence, and rollback support.     |
| `/studio/bellona/format-registry/[formatId]/audit`                | planned        | Audit route for approvals, policy evidence, and release traceability.        |

## 3. Route Governance Rules

- All Format Registry routes must remain under `/studio/bellona`.
- Format detail routes must use stable `formatId` identifiers from registry
  records.
- Version routes must use stable `versionId` identifiers for immutable registry
  snapshots.
- Future route expansion must preserve navigation continuity to the primary
  workspace route.

## 4. Acceptance Criteria (OST-00483)

`OST-00483` is complete only when:

1. A dedicated studio navigation entry exists for Bellona Format Registry.
2. The primary route `/studio/bellona/format-registry` is implemented.
3. A canonical route map document exists with planned subroutes and purposes.
4. Navigation and routing align with Bellona feature documentation.
