TheRON/mechanical-compiler
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: record the F-034 decision in HANDOFF.md

Browse Source 
CIVICVS approved option 1 on 20 AUG: scale-aware bounds in test_oracle.py for SECTION_AREA_MM2, VOLUME_MM3 and MASS_G, derived from the 0.01 mm criterion and the section perimeter. Not implemented yet. Implementation, mutation testing and a green suite are one piece of work, not a partial landing.

Section 4 item 2 is removed. The F-034 measurement rewrite in FAILURES.md landed in b255ebb, so listing it as a next step sends the next reader to redo work already done. FAILURES.md keeps status Open, which is correct until the change lands.

Header commit line moved to b255ebb. Section 7 and the section 11 open-questions table now say decided rather than ready to decide.
This commit is contained in:
TheRON
2026-08-20 08:06:16 -05:00
parent b255ebbab9
commit 52d00b588b
1 changed files with 17 additions and 11 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/HANDOFF.md
+17 -11
View File
@@ -6,7 +6,7 @@ It is the only handoff you need to read. Dated handoffs in `docs/archive/` are
historical and are not required reading — do not diff them against this to work
out what is true. If something here is wrong, correct it here.
Last updated 2026-08-20 at commit `114189c`.
Last updated 2026-08-20 at commit `b255ebb`.
---
@@ -155,15 +155,20 @@ red `make test` as a broken port — read §7 before doing anything about it.
## 4. What to do next
**Nothing is blocked. Pick up §7 first if the operator wants it closed; otherwise
the port is done and the next work is new capability.**
**Nothing is blocked. §7 is decided and awaiting implementation;
everything else is new capability.**
Immediate, small, and already scoped:
**Immediate: the F-034 tolerance change — decided, not yet
implemented.** CIVICVS approved **option 1** (§7) on 20 AUG:
scale-aware bounds in `test_oracle.py` for `SECTION_AREA_MM2`,
`VOLUME_MM3` and `MASS_G`, derived from the 0.01 mm criterion and the
section perimeter. It was deferred deliberately — implementation,
mutation testing and a green suite are one piece of work, not a partial
landing. **Do not touch the oracle JSON** (§7).
1. **F-034 tolerance decision** (§7). Evidence is gathered; the decision is
CIVICVS's. Do not implement before he chooses.
2. **Rewrite F-034 in `FAILURES.md`** around the measurements below. The entry
still describes it as an unquantified hazard; it is now measured.
`FAILURES.md` still records F-034 as Open, which is correct until the
change lands. Its measurement rewrite is already done (commit
`b255ebb`) — do not redo it.
After that, the roadmap items — read `ROADMAP.md` before starting any:
@@ -342,8 +347,9 @@ The change belongs in `test_oracle.py`, which is not hashed:
3. **Accept 30 known failures.** Honest but `make test` is never green and a real
regression hides among them.
**CIVICVS decides.** The evidence is above; bring him the recommendation and
stop.
**Decided 20 AUG: option 1**, scale-aware bounds for the three
discretisation-limited keys. The change goes in `test_oracle.py`, never
the oracle JSON. Not yet implemented — see §4.
---
@@ -434,7 +440,7 @@ held to it. When in doubt, narrow.
| 2 | Backup strategy — USB, IPFS, optical? | CIVICVS |
| 3 | Where is the 3+ TB USB disk attached? | CIVICVS |
| 4 | Kane Fabric participant mail, send and receive | Cross-project |
| 5 | Tolerance model for the three discretisation-limited keys — see §7 | CIVICVS, **ready to decide** |
| 5 | Tolerance model for the three discretisation-limited keys — see §7 | **Decided 20 AUG: option 1.** Implementation pending |
Question 4 is real and unaddressed. Containers do not send mail by standard and
nothing can reach `vmbr1` from outside, so receiving has no path at all. It needs