Eve library

OSHUN Studio Bellona Interchange Batch Conversion Route Map

Spec

Revision 1

On this page

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/interchange-batch-conversion/page.tsx

Purpose#

Define dedicated navigation entry points and canonical route structure for the Bellona Interchange Batch Conversion capability in OSHUN Studio.

This document is the execution artifact for OST-00447.

1. Navigation Entry#

  • Studio index entry label: Open Bellona Interchange Batch Conversion workspace
  • Studio index entry route: /studio/bellona/interchange-batch-conversion
  • Primary ownership: Bellona Domain Engineering + Studio Web

2. Canonical Route Map#

Route Scope Purpose
/studio/bellona/interchange-batch-conversion GA entry route Primary workspace shell for batch conversion orchestration.
/studio/bellona/interchange-batch-conversion/new planned Create/edit route for batch jobs, presets, and pipeline targets.
/studio/bellona/interchange-batch-conversion/[batchId] planned Batch detail route with diagnostics and lifecycle evidence.
/studio/bellona/interchange-batch-conversion/[batchId]/runs/[runId] planned Run detail route for retries, progress, and failure remediation.
/studio/bellona/interchange-batch-conversion/[batchId]/audit planned Audit route for approvals, owner signoff, and traceability controls.

3. Route Governance Rules#

  • All Interchange Batch Conversion routes must remain under /studio/bellona.
  • Batch-specific routes must use stable batchId identifiers from Bellona batch orchestration records.
  • Run-specific routes must use stable runId identifiers linked to batch execution lineage.
  • Future route expansion must preserve navigation continuity to the primary workspace route.

4. Acceptance Criteria (OST-00447)#

OST-00447 is complete only when:

  1. A dedicated studio navigation entry exists for Bellona Interchange Batch Conversion.
  2. The primary route /studio/bellona/interchange-batch-conversion is implemented.
  3. A canonical route map document exists with planned subroutes and purposes.
  4. Navigation and routing align with Bellona feature documentation.