Context
The ROADMAP's gate is compound and HONEST — but three of its clauses currently have no owner, no ticket, and no mechanism, which means they resolve to "claimed" by default. This ticket makes the measurement side real. It is also the revenue-bar instrument: the operator's explicit win condition is traction, or revenue sufficient to afford the frontier tier — you cannot steer toward a bar you don't measure.
The three falsifiers
F1 — the PoC falsifier (cornerstone 1): "@tobiu starts an agent from the UI, not a terminal." Mechanism: the J2 integration journey (the epic filed alongside) run BY THE OPERATOR on a clean checkout, recorded. The falsifier ticket's AC: a documented run where zero terminal commands occur between cockpit-open and agent-first-action. Repeatable = the e2e; the GATE event = the operator's run.
F2 — the TTFP harness (cornerstone 4): "self-configures to first persistence in minutes, MEASURED." Mechanism: an acceptance script (CI-runnable, also stranger-runnable) that clocks fresh-clone → config → first Memory-Core persistence, emitting a machine-readable result artifact. AC: the number appears in the release notes with the run's provenance, not prose. The fork→PR ≤ 30min half needs its own scripted scenario (a seeded starter ticket + the measured path).
F3 — reach analytics (cornerstone 5): "every flagship demo reports measured reach; strangers counted, not developers." Mechanism: the Ring-0 metric schema (shipped) wired to the deployed demo surfaces — per-demo view/interaction events with the developer-filter heuristic documented IN the metric node (falsifying-query discipline: every published number carries the query that would disprove it). AC per flagship demo: a reach dashboard slice exists before the demo is announced anywhere.
Acceptance Criteria
Out of Scope
The demos themselves · pricing/packaging decisions (business-repo) · any new analytics infra beyond the shipped Ring-0 schema.
Related
The ROADMAP gate (this mechanizes its measurement clauses) · #14781 (J2/J3 host F1/F2) · the business epic's shipped metric-schema leaf (F3's substrate) · the falsifying-query discipline (recorded).
Claimable — Opus-shaped; the specs are complete.
Origin Session ID: b9b95ac6-42f5-47a3-b58f-6071f79657e8
Retrieval Hint: "release gate falsifiers PoC operator run TTFP acceptance script reach analytics measured not claimed"
Context
The ROADMAP's gate is compound and HONEST — but three of its clauses currently have no owner, no ticket, and no mechanism, which means they resolve to "claimed" by default. This ticket makes the measurement side real. It is also the revenue-bar instrument: the operator's explicit win condition is traction, or revenue sufficient to afford the frontier tier — you cannot steer toward a bar you don't measure.
The three falsifiers
F1 — the PoC falsifier (cornerstone 1): "@tobiu starts an agent from the UI, not a terminal." Mechanism: the J2 integration journey (the epic filed alongside) run BY THE OPERATOR on a clean checkout, recorded. The falsifier ticket's AC: a documented run where zero terminal commands occur between cockpit-open and agent-first-action. Repeatable = the e2e; the GATE event = the operator's run.
F2 — the TTFP harness (cornerstone 4): "self-configures to first persistence in minutes, MEASURED." Mechanism: an acceptance script (CI-runnable, also stranger-runnable) that clocks fresh-clone → config → first Memory-Core persistence, emitting a machine-readable result artifact. AC: the number appears in the release notes with the run's provenance, not prose. The fork→PR ≤ 30min half needs its own scripted scenario (a seeded starter ticket + the measured path).
F3 — reach analytics (cornerstone 5): "every flagship demo reports measured reach; strangers counted, not developers." Mechanism: the Ring-0 metric schema (shipped) wired to the deployed demo surfaces — per-demo view/interaction events with the developer-filter heuristic documented IN the metric node (falsifying-query discipline: every published number carries the query that would disprove it). AC per flagship demo: a reach dashboard slice exists before the demo is announced anywhere.
Acceptance Criteria
Out of Scope
The demos themselves · pricing/packaging decisions (business-repo) · any new analytics infra beyond the shipped Ring-0 schema.
Related
The ROADMAP gate (this mechanizes its measurement clauses) · #14781 (J2/J3 host F1/F2) · the business epic's shipped metric-schema leaf (F3's substrate) · the falsifying-query discipline (recorded).
Claimable — Opus-shaped; the specs are complete.
Origin Session ID: b9b95ac6-42f5-47a3-b58f-6071f79657e8 Retrieval Hint: "release gate falsifiers PoC operator run TTFP acceptance script reach analytics measured not claimed"