Zero is not the same as unmeasured. 0 commitments is a fact. Repeat unprompted use has no source at all. A dashboard that paints both as 0 tells the board a gate is failing when nobody has even defined how it would pass.
Undefined is not the same as zero. Net revenue retention with no paid cohort is a division by zero, not 0%. Rendering it as 0% would say "we retain nothing", when the truth is "there is nothing yet to retain".
Tranche gates are a planning instrument. The SAFE is a rolling close with no contractual tranche conditions — nothing on this screen creates an investor obligation or a drawdown right.
Legal is deliberately front-loaded into T1: protection cannot wait on the team build. Founder runway is the second call on capital, never the first. No engineering salary is committed before T3.
| Item | Target date | Gate — what it unlocks | Status |
|---|
The standing rule for investor-visible surfaces is no roadmap promises or dates. Investors diligence missed dates in the next round; a slipped quarter that was never promised costs nothing, and one that was costs the raise.
The estate already speaks the alternative fluently — Bands, gates, T1–T4. What unlocks what, never when.
These are two renders of one source, not two roadmaps. Maintaining a second, investor-safe roadmap by hand is how the two drift — and the one that drifts is always the one nobody edits daily.
A row removed by the disclosure filter is counted, never silently dropped. An operator handing out a pack has to know the render is filtered and by how much.
| Pack | Track | Onboarding enrollment | NDA | EAPA | Last access |
|---|---|---|---|---|---|
| TM2SS1 | investor | not enrolled correct — track suppresses the sequence |
v2 signed 2026-07-30 |
— | 2026-08-05 |
| K4R9QD | investor | enrolled · step 2 sequence is teaching them to send a Relay |
v2 signed 2026-08-01 |
— | 2026-08-06 |
| 7XM2LP | investor | not enrolled | v1 superseded by v2 on 2026-07-22 |
— | 2026-08-04 |
| QB8N4Z | investor product | enrolled · step 4 correct — dual-role, they are a real user too |
v2 signed 2026-07-25 |
v3 signed 2026-07-25 |
2026-08-07 |
| RD5W1C | investor | not enrolled | v2 signed 2026-08-03 |
— | never |
A suppressed principal leaves the activation and retention denominators — but by the same law as a withheld roadmap row, an excluded principal is counted, never silently dropped.
The onboarding overview reports suppressed_by_track as its own number alongside enrolled and completed. A denominator that quietly shrank is indistinguishable from a funnel that quietly improved, and this whole surface exists because a number you can't source is a number nobody can trust.
Revocation, residency and retention are owned by the Investor track screen and SPEC.investor-track.md §7–§9 — not restated here.
Tracks are not exclusive. QB8N4Z is an investor and a working user — suppressing their onboarding because one attribute is set would break a real product experience to satisfy a tidy model.
The rule that holds: enrollment follows what a principal is here to do, not the strongest label attached to them. Investor-only suppresses; investor-plus-product does not.
Minimize what this screen renders. Signature status and version, never the executed document inline — the copy is fetched only on explicit request, and that fetch is itself an audited event.
| Figure | Source | Mechanism | Cadence | As of | State |
|---|---|---|---|---|---|
| Round target · floor | commitments — round terms | generated | on change | 2026-08-07 | fresh |
| Tranche amounts T1–T4 | commitments — tranche model | generated | on change | 2026-08-07 | unmerged |
| First milestone | derived — 0.10 × target | computed | — | live | fresh |
| Commitments signed · $ | commitments — ledger | manual | weekly | 2026-07-12 | stale · 26d |
| Provisional filed | legal — filing status | manual | weekly | 2026-08-07 | fresh |
| Insurance bound | ops — policy register | manual | monthly | never | no input |
| EAP → paid conversions | platform — billing | live | on read | 2 min ago | fresh |
| Net revenue retention | platform — billing | live | on read | 2 min ago | not computable |
| Repeat unprompted use | — none — | — | — | — | not instrumented |
| Activation rate | platform — onboarding funnel | live | on read | 2 min ago | fresh |
| Roadmap items | roadmap — item list | generated | on change | 2026-08-06 | fresh |
1 · One canonical source. One machine-readable record per figure. Not a number typed into a page.
2 · Rendered, not transcribed. Every surface derives from that record at build or request time, so two surfaces are physically incapable of disagreeing.
3 · Provenance on every figure. Source and as-of, visible. A number with no timestamp is a number nobody can trust.
4 · Stale is visible. A manual input past its cadence says so, rather than showing an old value as current.
This estate has the scar tissue: one round figure wrong in six places at once, an allocation table summing to 107.2%, a documented feature flag that was never built, and a preview config that quietly diverged from production.
Every one of those was a hand-maintained number that drifted. A board dashboard is the worst possible surface to learn the lesson on again — a wrong number in front of the board is worse than no dashboard.