bigmerge
c6ba0677f0
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.
48 lines
2.0 KiB
Markdown
48 lines
2.0 KiB
Markdown
# judgment lives with knowledge
|
|
|
|
One `Ishikawa → scientific method → Six Sigma` loop. The record below is the
|
|
commit message as written at the time, before the outcome was known to anyone
|
|
reading this file.
|
|
|
|
## Record — `e8e25a0`
|
|
|
|
```
|
|
EXPERIMENT: temporal adjudication moves out; the placeholder stays
|
|
|
|
The previous pass moved the type DATA and left the judgment inline, which I
|
|
stated rather than hid. This finishes it.
|
|
|
|
PREDICTIONS AND RESULTS
|
|
P1 codegen can emit operand-type relations TRUE
|
|
"main calls temporal:instant_plus_instant"
|
|
P2 the affine rules are a small closed set as data TRUE 6 rules
|
|
P3 violations still caught at build time TRUE exit=1
|
|
P4 the reporter leaves codegen TRUE 4538 -> 4507
|
|
P5 the TIME_TYPE_ERROR placeholder must STAY TRUE
|
|
|
|
P5 is the boundary of this whole approach. The emitter has to emit SOMETHING
|
|
for an illegal expression -- it cannot emit nothing and it cannot decide what
|
|
the program meant. So the placeholder is irreducible in the same way the AST
|
|
traversal was: what moved is the judgment and the wording, not the fact that
|
|
something must be written.
|
|
|
|
The rules are affine algebra and the set is closed because there are only two
|
|
kinds of thing. An Instant is a POINT, a Duration is a DISPLACEMENT: add a
|
|
displacement to a point, subtract two points for a displacement, combine
|
|
displacements. Nothing else is meaningful, which is why the enumeration in
|
|
temporal.rel cannot grow the way an allowlist does.
|
|
|
|
A defect in my own checker, found by running it: the .rel file uses aligned
|
|
columns and my awk assumed a single space, so the message came out with the
|
|
rule key still prefixed. Same class as the multi-line header parse in the arity
|
|
pass -- formatting assumptions that only fail when you look at the output.
|
|
|
|
98/98 native, 6/6 temporal_query.sh, fixpoint ok.
|
|
```
|
|
|
|
## Record — `50425f3`
|
|
|
|
```
|
|
land temporal adjudication as a query: the emitter records, the rules are data
|
|
```
|