P0 was the only milestone gating the product track and all three of its features
sat in `draft` with no spec, while M9/M10/P1/PG1 are released. Engine work was
running ahead of the validation that decides whether any of it is wanted.
- p0-target-segment-recruitment: screening criteria per beachhead persona, a
funnel sized to yield the 20-50 pilot cohort, outreach limits (no accuracy or
onboarding promise the prototype cannot meet), consent and data handling,
opaque participant ids only, segment balance, and a pre-pilot baseline-feed
question so the readout has a control.
- p0-concierge-pilot-loop: the 14-day daily loop with the manual source-QA gate
the ROADMAP permits, the briefing card contract, the normative session
boundary, instrumentation bound to existing pg1 surfaces (signal-type
counters, feedback-loop histogram, /diagnostics snapshots) rather than a new
counting path, weekly interviews on the fixed beachhead question set, an
intervention ledger so concierge help cannot silently inflate quality, abort
conditions, and the frozen handoff dataset.
- p0-validation-readout: pre-registered GO/NO-GO/EXTEND rule over five gates
with an explicit dropout/missed-day/partial-observation policy, double-coded
interviews against the beachhead required answers, a sensitivity re-run that
downgrades GO to EXTEND if the verdict flips, a falsification section, and a
named reviewer who must argue the NO-GO case before publication.
Every threshold traces to a ROADMAP P0 acceptance criterion or the beachhead
doc; the three that neither document fixes (D2 retention floor, value-confirmed
fraction, noise kill-frame ceiling) are marked TBD (owner: product) instead of
being invented.
Next directive for all three is create_design.
