Normative language, evidence labels and tiers
672 words1 tablePlan version 1.1
MUST, MUST NOT, SHOULD and MAY carry their RFC 2119 meanings. Five labels say what kind of statement a sentence is. A number in this plan without one of these labels, or without an obvious label from its table header, is a defect in the plan.
| Label | Meaning | Who may change it |
|---|---|---|
| FACT | Observed on 2026-11-21 in a sibling repo, on this machine, or in a cited public source. Code facts cite repo/path; web facts cite a URL in Appendix H. |
New evidence only |
| DESIGN | A decision of this plan. It carries its reason. | An architecture decision record (ADR) |
| HYPOTHESIS | Believed, not established. It names the test that would confirm or kill it. | The named test |
| TARGET | A number we intend to hit. It is not a measurement until a gate records the measured value. | The gate that measures it |
| OPEN | Undecided. It has an owner, a deadline expressed as the gate it blocks, and a fail-closed default (§42). | The owner |
Three rules govern numbers that come from outside this repository.
- An external number is a FACT about its source, not about this system. Every external figure is registered in Appendix H with its URL or path, the version or tag it was read at, how it was read (raw text, a rendered figure read by eye, or a derivation from published inputs), and the phrase "to be re-read from the primary source before a gate cites it". The phrase is not repeated in each sentence that uses the figure.
- A reported defect in a foundation is a FACT to recheck. Where a review reported a defect in a sibling crate and this program has not reproduced it at a pinned commit, the statement is written "FACT (to recheck)", and it becomes an admission test and an upstream work item (§33, Appendix F) before anything depends on it.
- No number is written as a result. Nothing in this plan was measured on FrankenRobotics. A ratio, a rate or a coverage figure that describes this system is a TARGET, or a HYPOTHESIS with the range the evidence supports. Headline multipliers do not appear.
Ambition is calibrated with the three tiers the suite already uses (FACT:
frankensim/COMPREHENSIVE_PLAN_FOR_FRANKENSIM.md §0). Every mechanism in this plan carries one.
- S Solid: established mathematics and engineering. The risk is implementation quality.
- F Frontier: published research that mainstream robot simulators have not productized, or a narrowed form of a mechanism whose strong form failed review (§0.8). Real engineering risk.
- M Moonshot: a synthesis proposed here. It lives behind a feature flag and never sits on the critical path.
The spine of this plan is S. The features that make it worth building are F. The M items are what would make it unlike anything else, and the plan works without every one of them. Two obligations attach to the upper tiers (DESIGN; the reason is in §0.7):
- Every F and M item names a paper-scale pilot with a falsifier that must run before its work package is funded, and states the ceiling of its benefit before any speed test is run.
- Every F and M item has a kill gate with a fallback named in advance. The fallback is a mechanism of a lower tier that the plan already contains, so that losing the item costs a capability and never the critical path.
Every mechanism, at any tier, states: what it is (types, data layout, algorithm); which crate owns it (§34); the verb that exposes it (Appendix J); a known-answer or negative-control test (§38, Appendix M); and a gate with a numeric threshold (§40). The word "verified" is not used for results anywhere in this plan or in the product's output. A result is proved, certified, tested or estimated (§12), and it says which.