Fact 173
Riley Tanaka requested that the Helio Start lane remain `not board-ready` and include the two certified mature cohorts and March 3 technical-gate decision, framed as permitting consideration of a capped proposal rather than establishing acquisition economics; the exact start and end dates for both admitted-workspace cohorts with complete day-90 windows are missing.
Source evidence (1)
003556Mar 16, 2026 / 11:18 UTC-05:00
The March 16 source lock is complete. Update `Quarterly board operating evidence intake — Q1 2026` with the locked evidence, keeping the four lanes and their readiness statuses separate. Helio Start remains `not board-ready`: include the two certified mature cohorts and the March 3 technical-gate decision, making clear that they permit consideration of a capped proposal rather than establish acquisition economics. The exact cohort start and end dates for both sets of admitted workspaces with complete day-90 windows are still missing. Mark Expansion Assist `board-ready`: 18 actual exposures from December 1 through January 30, all with complete 45-day windows; six help-or-options requests and four expansions; no randomized control; every exposure met the standing current-state criteria; and no account had active Customer Success adoption or renewal work at exposure. Keep the claim descriptive, with no causal, revenue, or forecast treatment. Mark pricing-page path quality `board-ready`: November 26 through February 28 coverage of 9,604 organic sessions; 143 of 1,981 Helio Start eligibility-flow starts, or 7.2%, later routed out for an existing unsupported condition; 44.0% eligible-workspace admission completion; and account-level support time at the 90th percentile of 75 minutes. Because the control was retired November 26, frame this as post-rollout continuity rather than a new causal or revenue claim. Mark system controls `board-ready`: January 1 through February 28 coverage of 2,146 CS auto-nudge decisions, with 83 visible field-specific holds and 2,063 decisions that proceeded or were suppressed using current state; no governed-field disagreement, customer correction, or rollback; and two source-age alerts that fired before breach, with both affected sources refreshed before their limits. Set the outcome window to `not applicable — continuous control coverage` and limit the claim to system-control performance. For every row, preserve the lane-specific readiness model and include the applicable denominator or exact coverage dates, measurement limits, exclusions, source owner, source or release-reliability evidence, revenue and forecast treatment, and final claim owner. No unsupported revenue or forecast treatment should enter the board operating section.
Message 003556 in history