execution-plan/GATES.md · UPDATED 2026-10-01
Gates and evidence
Superseded from week 5 on by the gates in ROADMAP-v7 (2026-09-29). The week 4 gate below still applies; later rows are kept for reference.
All gates begin NOT_STARTED. Preserve target weeks; when delayed, retain target and record forecast/actual separately in PROGRESS and the relevant weekly review.
| Week | Gate | Required evidence | Reputation interpretation |
|---|---|---|---|
| 04 | Public and reproducible | batchlens v0.1 public, measured headline, reproducible report, actual DOI. | L1; L2 when citable |
| 08 | Technical report | Technical report DOI; public per-field F1 table; five founder messages actually sent. Track five conversations as a separate relationship target. | L2 |
| 13 | Dataset release | FermLit v0.5 public with dataset card and DOI; Paper 1 skeleton with all figures; at least one dated live endorsement conversation. | L2 |
| 16 | Paper 1 | Public bioRxiv preprint DOI. Submission receipt alone leaves the public gate pending. | L3 when public |
| 20 | Paper 2 | Public arXiv ID with endorsement, or scope-eligible bioRxiv public ID and a dated endorsement conversation per v5 fallback. | L4-endorsed only if endorsement exists |
| 24 | Scientific partner | Actual written agreement with a contributing scientist and a timestamped validation protocol. | L4 path; not yet co-authored publication |
| 28 | First invoice | Actual invoice issued for real agreed work. Track signed scope, amount invoiced, upfront payment and cash received separately. | Money milestone; no reputation promotion |
| 32 | Paper 3 | Public preprint DOI with a contributing scientist as co-author and all authors' approval. | L4-co-authored when public |
| 36 | Journal and software submissions | Two journal submission receipts (one each for Papers 1 and 2) and one eligible JOSS submission receipt. | L5 path; submission is not acceptance |
| 40 | Evidence and decision | Three public preprints, one co-authored; two journal submissions; one JOSS submission; batchlens/trialkit/labdocs release DOIs; one delivered talk; at least one paid engagement delivered; written career decision. | L5 only with actual reviewed/accepted and invited evidence |
0101
Weekly operating indicators
01
Weekly operating indicators
Record blocks completed (target 5/7), days with actual commits when using Git (target 3/7), Sunday log (1), optional Wednesday note (1), actual founder conversations, earned evidence level and consecutive lost weeks. Hours allocated are a capacity constraint, not a learning-success metric. Do not use likes, followers, stars or videos watched as evidence of competence.
Relationship targets from v5: five founder conversations by 8; ten by 16; two substantive endorsement/co-author routes by 24; three qualified offer conversations by 28; twenty cumulative founder conversations by 28. Record messages, booked calls and held calls independently.
0202
Status semantics
02
Status semantics
- Prepared artifact: local draft/package exists and has been checked.
- Sent/submitted: actual external action has a dated receipt or record.
- Public: a working public artifact link exists.
- Reviewed/accepted: actual reviewer feedback or venue acceptance exists; distinguish the two.
- Paid work: separate signed scope, invoice issued, cash received, delivery and client acceptance.
- Blocked gate: essential evidence missing, with named dependency, next action and forecast date.
A minimum viable week prevents abandonment; it does not automatically pass a gate. The week 40 decision can be useful and complete as a document even while the programme's evidence gate remains incomplete.