The operating rule

Three lanes.
One release.

Engineering completion is not rollout completion. Every build card must have observable evidence in the QA lane and a truthful provider-facing consequence in the GTM lane. A slip moves all dependent cards together.

No QA evidence, no GTM promise.

QA and GTM share one Notion deliverables database. Engineering remains anchored to the memory bank and delivering repositories.

Three-lane roadmap

Dependency map

Cards are linked by ID. Click one to inspect what it proves, what it unlocks, and the exact Notion or engineering source.

Dragon 1 → Dragon 2

Tool transfer gate

“Used on Dragon 1” is not proof of Dragon 2 readiness. Every tool below needs portable configuration, a D2 execution test and retained evidence. Click for the three checks.

Production stays closed until Q12 says GO.

  1. W1 codifies the reusable stack and proves Dragon 1 parity.
  2. W2 launches Dragon 2 from automation and proves data, DAC, payment and visibility.
  3. W3 onboards a representative provider host and rehearses the entire path.
  4. W4 admits the 2–3 committed providers only after the signed go/no-go.

Roadmap card

Depends on
Unlocks / aligns with

Validation · maximum 3 checks

    Linked cards

    Open source record ↗