Pipeline

Orchestrate triage → align → execute phases with machine-validated gates and artifact-based resume. Each phase narrows scope until a constraint contract is tight enough for autonomous execution.

Principles

• Forward-only phase progression: triage → align → execute. No phase type can repeat in the same position without superseding the prior one.
• state.json is a thin cached projection (<2KB). events.ndjson is the authoritative ledger.
• All paths are repo-root-relative. Never store absolute paths.
• The pipeline orchestrator owns .pipeline/ state. manage-codex owns relay child state.
• Execute output artifacts are owned by the pipeline orchestrator, not the child workflow.

Filesystem Contract