3 Commits

Author	SHA1	Message	Date
bigmerge	daad2fa2a0	log the fifth measurement defect: a count that was not counting ... git diff errored to stderr on a malformed revision while wc -l counted empty stdout, producing three confident IDENTICAL results that meant nothing. Had the promoted trees actually differed, I would have reported the promotion clean. The correct check is not 'how many files differ' but 'is the tree object the same object' -- all three share hash 2acd9374. All five defects are now visibly one shape: reading a PROXY instead of the thing. One file instead of the operation, a variable name instead of the shape, a scope instead of the whole, a pipe's exit instead of the program's, a line count instead of object identity.	2026-08-17 11:10:22 -05:00
bigmerge	511db25230	rerun cycle 18 rather than reconstruct it ... The async/future measurements were produced by a C stub in /tmp, and that artifact was destroyed when the session worktrees were removed. The log then asserted results with nothing behind them -- a claim inside an evidence record, which is exactly what turns a chain of custody into a pile. Rerun, not reconstructed. Rebuilding the missing file would have been a fabrication with a fresh timestamp; rerunning produces new evidence with its own. lang/tests/integration/fixtures/future.c the future, as a tagged heap object lang/tests/integration/async_future.sh the harness, 6/6 ok unbound: synchronous, correct result ok unbound: el_await on a non-future passes through, no crash ok bound: does not crash ok bound: the awaited result is correct ok bound: the caller continues BEFORE the body finishes ok bound: wrap returns in <10ms while the body takes 50ms LABELLED AS A REPLICATION. The outcomes were already known when this harness was written, so its expectations are NOT predictions committed in advance. Its evidentiary value is that a third party can reproduce it, not that it was called ahead of time. Recording it as anything stronger would corrupt the record it is meant to repair. The fixture also carries the P5 defect and its fix in a comment: the first el_await dereferenced ->magic off an unvalidated slot and SIGSEGV'd on the unbound path, sixty seconds after the same defect was diagnosed elsewhere in the runtime.	2026-08-17 11:03:59 -05:00
bigmerge	c6ba0677f0	log v1 experiments: nineteen cycles, organised by the method that produced them ... cycles/ one file per Ishikawa -> scientific method -> Six Sigma loop, named for the DEFECT not the fix, carrying the commit record as written at the time findings/ what the cycles produced, cross-cut: live bugs, architecture answers, and defects in my own measurement The organising finding is that predictions which came back FALSE produced every significant result. Eleven of sixty-one failed, and those eleven found: that the arity table was not drifted but 40% incomplete; that the AST traversal is irreducible and only rules and judgments move; that guards could refuse through the seam after all; and that routing el_bin_lookup through the gate did NOT fix the SIGSEGV, because the fallback strlen was the hazard -- a wrong fix I would otherwise have shipped as verified. One cycle was run without committing predictions first and had to be discarded as rigged. It is kept, in full, as 18-async-half-expressible.md.	2026-08-17 10:52:17 -05:00