Problem
The June post-mortem's sharpest line: the views were "not connected." A cleared board of excellent leaves still fails the release gate if no path crosses module boundaries. Nothing currently FORCES connection: every cornerstone can individually complete while the product remains a set of islands. The release gate is written as journeys ("a stranger downloads… the operator starts an agent from the UI… docking demos public"), so the proof must be journeys.
Intended solution
Three named end-to-end journeys, each = ONE whitebox e2e (NL-driven, deterministic) + ONE demo tour segment + a measured-reach hook (the traction bar: every journey emits the Ring-0 analytics events that let us count strangers, not developers — the explicit win condition is traction or revenue at the frontier tier, and journeys are where measurement attaches honestly):
- J1 — the creation journey: typed intent → blueprint preview → live grid with chrome → "make it taller" mutation → promote to OS window → reload, still there. (Crosses: keeper spine → registry → dock/promote → persistence.)
- J2 — the operator journey: cockpit → start an agent from the UI (control-plane actuator) → agent wakes → picks a GP item → its PR/activity appears in the cockpit's activity adapter. (Crosses: cockpit UI → daemon control plane → orchestrator → GP → fleet adapters. This IS the PoC falsifier as a repeatable test.)
- J3 — the stranger journey: fresh clone → self-configure → first persistence → first created widget, with TTFP measured by the harness (crosses: onboarding → config SSOT → keeper; the "minutes, measured" bar).
Leaf tickets: first claimant per journey FILES the leaf from this body via ticket-create (the journey spec above is the contract; filing is reading). Each leaf carries: the boundary list, the e2e AC, the tour segment AC, the analytics-event AC, and the explicit rule that a journey test failing on a module seam is a SEAM defect (highest-priority class), never a test to weaken.
Constraints carried
Whitebox-e2e discipline (custom Playwright configs, NL fixture) · tour segments consume the motion-standards tokens · analytics events per the Ring-0 schema (business epic's shipped leaf) · no journey mocks a crossed boundary — that's the anti-rubber-stamp rule; doubles are for unit specs, journeys run the real seams.
Related
The five cornerstones (this epic is their connective tissue) · the motion-standards ticket (tour vocabulary) · the release-gate falsifier set (J2/J3 host two of them) · the June post-mortem (the class this kills).
Steward: claimable — an Opus peer with cross-pillar context (the journey specs are complete; driving them is coordination + e2e authorship).
Origin Session ID: b9b95ac6-42f5-47a3-b58f-6071f79657e8
Retrieval Hint: "integration journeys end to end product paths creation operator stranger connected seam defect"
Problem
The June post-mortem's sharpest line: the views were "not connected." A cleared board of excellent leaves still fails the release gate if no path crosses module boundaries. Nothing currently FORCES connection: every cornerstone can individually complete while the product remains a set of islands. The release gate is written as journeys ("a stranger downloads… the operator starts an agent from the UI… docking demos public"), so the proof must be journeys.
Intended solution
Three named end-to-end journeys, each = ONE whitebox e2e (NL-driven, deterministic) + ONE demo tour segment + a measured-reach hook (the traction bar: every journey emits the Ring-0 analytics events that let us count strangers, not developers — the explicit win condition is traction or revenue at the frontier tier, and journeys are where measurement attaches honestly):
Leaf tickets: first claimant per journey FILES the leaf from this body via ticket-create (the journey spec above is the contract; filing is reading). Each leaf carries: the boundary list, the e2e AC, the tour segment AC, the analytics-event AC, and the explicit rule that a journey test failing on a module seam is a SEAM defect (highest-priority class), never a test to weaken.
Constraints carried
Whitebox-e2e discipline (custom Playwright configs, NL fixture) · tour segments consume the motion-standards tokens · analytics events per the Ring-0 schema (business epic's shipped leaf) · no journey mocks a crossed boundary — that's the anti-rubber-stamp rule; doubles are for unit specs, journeys run the real seams.
Related
The five cornerstones (this epic is their connective tissue) · the motion-standards ticket (tour vocabulary) · the release-gate falsifier set (J2/J3 host two of them) · the June post-mortem (the class this kills).
Steward: claimable — an Opus peer with cross-pillar context (the journey specs are complete; driving them is coordination + e2e authorship).
Origin Session ID: b9b95ac6-42f5-47a3-b58f-6071f79657e8 Retrieval Hint: "integration journeys end to end product paths creation operator stranger connected seam defect"