Shared Pipeline — General View

One protected host admits Tomo, Codex, or OMP sequencing for each run

BACKEND AUTHORITY SHARED PIPELINE PROTOCOL Member authenticated turn API Backend authority + policy Shared Host effects + lifecycle fixed contract Selected Controller Tomo, Codex, or OMP run-scoped Model Gateway routing + budgets Tool Callback current permissions Journal events + terminal Checkpoint recovery state Streamed Result durable projection immutable admission typed control next protected effect model step tool request Legend External Security Backend Message bus Cloud Database Frontend

Controller Choice

  • • Tomo owns reducer transitions
  • • Codex owns session, task, turn, and step
  • • OMP owns outer queue and inner loop

Protected Effects

  • • Python rechecks authority for every callback
  • • Model and tool clients stay outside controllers
  • • Journal and terminal settlement remain shared

Stable Contract

  • • One immutable admission per run
  • • Runtime-neutral events and checkpoints
  • • Controller changes never change member authority