Four views of one project. Every claim is tagged [SHIPPED] / [PROVEN] / [CONCEPT] — read the tag, not just the sentence.
| doc | audience | what it is |
|---|---|---|
TECH-SPEC-AGENTS.md |
engineering agents | mechanics, the falsifier ledger, invariants, what to build next |
TECH-SPEC-PRODUCT.md |
product lead | what it is, the eight-product surface with per-product maturity, roadmap, risk |
PROPOSAL-EN.md |
stakeholders (English) | the case for direction + investment |
PROPOSAL-DE.md |
stakeholders (Deutsch) | derselbe Vorschlag auf Deutsch |
One line: lower any code to R2IL, address it by ordinal in ogar-loco,
execute it zero-copy through r2conc; every product is a policy/render glove
on that one engine. Canon: r2il-machine-semantic-contract-v1.md §7.7–7.8;
E-ONE-SUBSTRATE-FIVE-GLOVES (lance-graph-java).
Honesty note. The proposals lead with what is proven (LIVE-REGFILE, R7 zero-alloc, R12 flatten, zipper-hop-parity) and explicitly name what is not (a banked throughput number; the learned decoder). Keep it that way — a proposal that overclaims is worth less than one that a technical reviewer can trust line by line.