Skip to main content

Outcome Compiler

The Outcome Compiler turns intent into a versioned capability graph, a contract set, and an evidence ledger, then compiles deployable releases with deterministic gates. Completion is "PASS gates" and proof — not narrative.

Flow

Intent (from you or intent.yaml) → capability graph → contract set (frozen) → scope lock → implementation → gates run → evidence recorded. See Gates reference and gates.yaml for how gates are defined and executed.

The three outputs

  • Capability graph — Versioned nodes (features/capabilities) with contract edges and dependencies. Stored and updated as you compile intent.
  • Contract set — OpenAPI, event schemas, invariants. Frozen before implementation so the build breaks when contracts are violated.
  • Evidence ledger — Append-only record of every gate run, test result, and verification. The proof that the release satisfies the gates.

Contracts first

Scope and contracts are frozen before implementation. No coding until the compiler has locked API shapes, event payloads, and invariants. This keeps documentation and behavior in sync and prevents scope creep.

Pilot tier

The current delivery tier is pilot: 16 gates, most hardening required. Production tier requires 25+ gates and full hardening with no waivers.

Capability passports

Every capability-changing task can produce a Capability Passport that proves contracts exist, tests exist and pass, and evidence was recorded. Proof-carrying capabilities (PCC) are a core invariant: no capability ships without proof unless explicitly escrowed with a time-bound waiver.

Delivery tiers

Prototype (8 baseline gates), Pilot (16 gates), Production (25+ gates). Your .maestro/intent.yaml and tier configuration determine which gates run and what evidence is required.

Key takeaways

  • Intent drives the capability graph, contract set, and evidence; contracts are frozen before implementation.
  • Scope lock and contracts first prevent scope creep and keep docs and behavior in sync.
  • Capability passports prove that contracts, tests, and evidence exist for each capability.
  • Delivery tier (prototype / pilot / production) determines how many gates and how much hardening are required.

Related documentation

Gates & evidence · intent.yaml · Gates reference · How Midcore works