lin-0235
20.2 The Odyssey–Prometheus division of labor
Odyssey and Prometheus occupy different positions in the architecture. Prometheus acquires heterogeneous sources, extracts structured events and claims, builds local predictive or causal representations, checks overlaps, and emits an artifact bundle. Odyssey declares what is being built, governs the workflow, validates representation laws, exposes arguments, and decides what becomes maintained foundry state.
|
Role |
Primary responsibility |
Trust question |
|---|---|---|
|
Scylla |
Human-facing model brief and answer contract |
What is being claimed, for whom, and under what scope? |
|
Homer |
Workflow orchestration, checkpoints, and replay |
Can the construction be reproduced and refreshed? |
|
Athena |
Cover, local types, restrictions, and gluing laws |
Do the representations compose as declared? |
|
Prometheus |
Source acquisition and candidate world-model artifacts |
What local evidence, models, and tensions can be constructed? |
|
Toulmin |
Claim, grounds, warrant, backing, qualifier, and rebuttal |
Does the evidence license the stated conclusion? |
|
TICKET |
Promotion, qualification, quarantine, or rejection |
May this artifact enter maintained state for the requested use? |
The names are less important than the separation of powers. A Prometheus bundle can contain a source manifest, artifact manifest, world-model description, restriction and gluing audit, obstruction ledger, dashboards, and refresh plan. These artifacts remain inspectable even if Odyssey declines to promote them. Conversely, Odyssey can export an admitted foundry slice to Prometheus for exploration without surrendering the admission boundary.
The artifact producer should expose enough structure for another component to reject, qualify, or replay its work. Trustworthy generation requires a first-class refusal path.