# OSHUN Studio Bellona Live Engine Bridges Route Map

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

- `docs/domains/bellona/features.md`
- `docs/domains/bellona/README.md`
- `apps/oshun/web/src/app/studio/bellona/live-engine-bridges/page.tsx`

## Purpose

Define dedicated navigation entry points and canonical route structure for the
Bellona Live Engine Bridges capability in OSHUN Studio.

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

## 1. Navigation Entry

- Studio index entry label: `Open Bellona Live Engine Bridges workspace`
- Studio index entry route: `/studio/bellona/live-engine-bridges`
- Primary ownership: Bellona Domain Engineering + Studio Web

## 2. Canonical Route Map

| Route                                                     | Scope          | Purpose                                                               |
| --------------------------------------------------------- | -------------- | --------------------------------------------------------------------- |
| `/studio/bellona/live-engine-bridges`                     | GA entry route | Primary workspace shell for bridge inventory and expert operations.   |
| `/studio/bellona/live-engine-bridges/new`                 | planned        | Create/edit wizard route for bridge templates and advanced settings.  |
| `/studio/bellona/live-engine-bridges/[bridgeId]`          | planned        | Bridge detail route with timeline, diagnostics, and related entities. |
| `/studio/bellona/live-engine-bridges/[bridgeId]/sessions` | planned        | Session stream state, reconnect, throughput, and transport health.    |
| `/studio/bellona/live-engine-bridges/[bridgeId]/audit`    | planned        | Audit/change history with reversible operation evidence.              |

## 3. Route Governance Rules

- All Live Engine Bridges routes must remain under `/studio/bellona`.
- Detail routes must use stable `bridgeId` parameters from Bellona bridge
  inventory records.
- Future feature routes must preserve forward/back navigation to the primary
  route.
- Route expansion must remain consistent with Bellona bridge types (Unity,
  Unreal, Godot, Blender).

## 4. Acceptance Criteria (OST-00321)

`OST-00321` is complete only when:

1. A dedicated studio navigation entry exists for Bellona Live Engine Bridges.
2. The primary route `/studio/bellona/live-engine-bridges` is implemented.
3. A canonical route map document exists with planned subroutes and purposes.
4. Navigation and routing align with Bellona feature documentation.
