session 2026-06-23: N6 deployed live + merged #175 + PENDING-41 corrected (43L/43M already designed) + OCR-workhorse plan + skill harvest

2026-06-23 22:35:16 +02:00
parent 3ca8e75c1b
commit d3b22cabe2
5 changed files with 135 additions and 1 deletions
@@ -231,3 +231,12 @@ The single place proposed skills live so they don't evaporate between sessions.
 | **verification-ladder: quantify-the-removed-cost as the A/B control** | verification-ladder entry | When a fix *removes* a hot operation, the cleanest control isn't a flaky end-to-end before/after race — it's to **time the exact removed operation on real data**. Today: timing the wedging `json_each` scan on the real 676k graph = **2.56 s each** (vs 0.003 s indexed) × ≤20/event = the wedge, quantified decisively in seconds, no full-replay race needed. Bounded, reproducible, and the number goes straight into the PR. | `reference-verification-ladder` | **PROPOSED** |

 *(Four, all earned in use today on the N6 work. The clone-test harness and running-binary-provenance are the load-bearing two — the first is a reusable safe-test pattern for the steward's live substrate; the second flipped a wrong root-cause to the right one. The probe-confirms-hypothesis flag is a clean new §3 shape [self-authored probe ≠ code behaviour]. Minor/reinforcing: "assert-process-dead-from-a-pgrep-pattern-miss" recurred today [declared PID gone; it was alive, my pattern just didn't match the cmdline] — reinforces the existing `census-through-a-pattern` flag, no new entry needed. None created autonomously — surfaced for steward authorization.)*
+
+### Harvest 2026-06-23 (N6 deployed live + consumer-hardware reframe — the thrash day)
+
+| Element | Kind | One-line | Where it lands | Status |
+|---|---|---|---|---|
+| **Symmetria §3 flag: diagnose-inference/latency-without-isolating-the-exact-endpoint-uncontended-first** | Symmetria §3 flag | **The load-bearing harvest.** When a network/inference call is slow, the FIRST test must be the *isolated* one: stop the competing load AND hit the *exact endpoint the code uses*. Today I thrashed **4 confident-then-overturned leads** (missing-model → structured-output-bug → "model dead on host") because I tested `/api/generate` (wrong endpoint — it has its own Ollama-0.30.8 quirk) *under contention* from the live instance. TEST G — BMF stopped + slot cleared + the real `/api/chat` — gave the answer (4.6s, saturation not breakage) in **one shot**. The thrash was the cost of not doing the clean isolation test first. Kin to `probe-confirms-hypothesis`, specialised to latency/throughput diagnosis. | Symmetria §3 | **PROPOSED** |
+| **Symmetria §3 flag: reinvent-governed-DESIGN-without-reading-the-spec** | Symmetria §3 flag (may be redundant) | Proposed PENDING-41 (consumer-hardware graceful degradation) as a *novel* architectural direction when `local-inference-spec` 43L/43M **already designed exactly it**. Steward's clasp/circles pointer caught it. Antidote: before proposing an architectural direction, grep/read the spec for the existing design. **Possibly redundant** with the KG drift `reinvented-governed-tooling-without-checking-it-exists` (this is the *design/architecture* sibling of that *tooling* flag) — steward to judge whether it needs its own entry or just widens the existing one. | Symmetria §3 | **PROPOSED (poss. redundant)** |
+
+*(Two. The first is genuinely load-bearing — it would have saved an embarrassing afternoon of flip-flopping and is a clean, reusable diagnostic discipline. The second may just widen an existing flag; surfaced for the steward to merge-or-keep. Reinforced-not-new: the clone-test discipline [proposed 2026-06-22] — I restarted the LIVE substrate 4× today doing diagnosis that belonged on a clone; reinforces that proposal, no new entry. None created autonomously.)*