sots-re/findings
alex d12459d1e1 nav: lane DN, the instrument -- what the classifier hook declares and where each input comes from
Names the six regions (four result, two guard) that are the classifier's whole
output surface, and then names every predicate the decision consumes next to
which side computed it -- because the module takes those predicates as given, so
reading them off the live objects is its interface rather than a shortcut. Also
records that the node-graph indirect edge path-solver.md could not resolve
statically is resolved DYNAMICALLY here, by making the same call from the hook.
2026-09-09 10:32:02 -04:00
..
control-flow lane CZ: predictions for the z word, committed before the run 2026-09-09 09:19:51 -04:00
objects lane WS: pay the ratchet debt -- prep/TacReports/Lay/trdmgr/fwarn typed, 97.6% -> 99.9959% 2026-09-08 20:15:38 -04:00
resolutions resolver: the residue is fleet VISIT ORDER not id allocation, and the block records it; rule 26 gains (d), my 26(c) over-read corrected 2026-09-09 02:19:33 -04:00
subsystems nav: lane DN, the instrument -- what the classifier hook declares and where each input comes from 2026-09-09 10:32:02 -04:00
.keep.md init commit 2026-09-07 12:31:56 -04:00
00-strategy.md strategy: phase 2 decisions (two repos, c++ shim, accrual order) 2026-09-07 17:10:21 -04:00
01-fingerprint.md map: RTTI class inventory (1924 types, engine=Mars); reseed board with real targets 2026-09-07 14:48:43 -04:00
_template.md scaffold RE campaign: board, backlog, findings template, verify tree 2026-09-07 14:40:44 -04:00