Ship

Turn an accepted code outcome into repository-native completion.

ship is a standalone Codex Orchestrator that owns one bounded request to ship code. Its root Session coordinates every Target Project mutation through native Target Tasks, while each Target Project retains its product authority, instructions, work state, approvals, and completion evidence.

Shipping means reaching the completion boundary defined by the target—not merely producing a patch or a reviewed branch. ship reconciles the live evidence, continues work that can safely progress, and remains accountable for the integrated outcome.

Use ship

Start a Codex task from an exact revision of this repository and describe the code outcome and Target Scope you want shipped. The Orchestrator resolves the request against current Target Project instructions and available authority before causing effects.

Read the contract

• Architecture — purpose, outcomes, planning, and terminal conditions.
• Authority — accepted requests, Target Scope, effects, approvals, and evidence.
• Recovery — reconciliation, interruption, duplicate prevention, and resumption.
• Scenarios — reviewable traces that pressure-test the contract.

ship runs independently. The lightfastai/orchestrator Workbench designs and evaluates exact revisions but is never consulted at runtime.

Verify

Run the local scenario suite:

python3 -m unittest discover -s tests -v

Structural conformance is checked externally from a Workbench checkout:

python3 -m conformance.v0_1_0 /path/to/ship

Status

ship implements Orchestrator Standard 0.1.0. Its initial revision and evaluation establish structural conformance and synthetic scenario coverage; real Target Project traces will drive future revisions.

License

MIT © Lightfast