the machine

The pipeline is a state machine.

Blueprint's stages aren't prose you hope an agent follows — they're a model a program evaluates. Every gate is decided one of two ways: mechanically, from artifacts on disk (the deterministic core), or by a human/reviewer assertion for the fuzzy edges a disk check can't decide (the agentic shell). Move the non-determinism to the edges; keep the determinism at the core.

variant

A new product, no production surfaces. The prototype is the deliverable.

Deterministic core — 9 gates a program decides from diskAgentic shell — 3 gates a human/reviewer must assert
8 stages · 12 gatesscroll the pipeline →
  1. 0

    Application Legibility

  2. 1

    Research

  3. 2

    Design Principles

  4. 3

    Prototype

  5. 4

    Fact-Check / Validate

  6. 5

    Documents

  7. 6

    Deploy

  8. 7

    Iterate

Select a gate to see what the machine checks — and whether it's decided by disk or by assertion.

honest about the line

Real initiatives don't advance in a straight line.

Drawn as a tidy left-to-right flow, this chart would lie. When we ran the machine against the real consumer fleet, initiatives completed stages non-contiguously — research done, design-principles skipped, decisions and deploy done. So the tool reports two things, not one: a confirmed cursor (how far the contiguous spine reaches) and coverage (which stages are complete at all, gaps included).

That calibration also caught the gates themselves: the first run derived a sensible position for zero of seven real consumers, because the synthetic tests had been circular — shaped to match the gates. The gates are now layout-tolerant, and the finding is on the record. Determinism isn't a green test suite; it's the model surviving contact with reality.