Jesse Daniel Brown commited on
Commit
ee17e7d
·
1 Parent(s): b7cbd9c

P4B (acer, docs-first/E=0): front-door root frame for Harness-edit. For liris attack-verify before main.

Browse files
Files changed (1) hide show
  1. HARNESS-EDIT-ROOT-FRAME.md +36 -0
HARNESS-EDIT-ROOT-FRAME.md ADDED
@@ -0,0 +1,36 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ # Harness-edit — SkillOpt / claims-gate / watcher-correction loop
2
+
3
+ Date: 2026-06-28 · Branch: `acer/p4b-harness-loop` · **docs-first, E=0.** No runtime fire, no cutover, no corpus, no keys. For liris attack-verify before main.
4
+
5
+ ## Claim
6
+ Harness-edit is **the watcher-correction loop applied to the system's own skills/laws** — not a hot-path
7
+ JSON data fabric:
8
+
9
+ > a **SkillOpt-style, validation-gated edit loop** (`score_skill` / `rollout_score` / `apply_edit`) over
10
+ > the **claims-gate** held-out scenarios — it changes a skill/law doc **only if** held-out coverage does
11
+ > not regress, else it refuses and logs to the rejected-edit buffer.
12
+
13
+ It is the meta-loop that gates self-editing; it does not route runtime PID traffic.
14
+
15
+ ## How it maps to the root
16
+ - It is the **N-Nest-Prime corrective gate, raised to the docs/skill layer**: a proposed edit is the
17
+ "child," the held-out validation is the "watcher," and the edit converges **only when**
18
+ `reported == recomputed-truth` (coverage doesn't regress) — exactly `recurrence + correction = cognition`,
19
+ applied to the system's own laws.
20
+ - It is **how the system self-improves its skills safely**: edits don't self-authorize; they pass the
21
+ gate or go to the rejected buffer (consent/scaling stays non-recursive, anchored at the operator apex).
22
+ - It is the local analog of Hermes's learning-loop, but **gated** — the upgrade we keep over the external
23
+ mirror (don't harden a negative claim into a refusal; make the gate prove it).
24
+
25
+ ## Evidence tags / honest boundaries
26
+ - CANON: Harness-edit implements the SkillOpt paper's validation-gate + edit-budget + rejected-buffer =
27
+ the CLAUDE.md / memory / claims-gate edit loop; `apply_edit.py` applies only on `VALIDATION_ACCEPTED`,
28
+ else `REJECTED_BUFFER`.
29
+ - BOUNDARY: this is **NOT** a hot-path / JSON runtime fabric — it is a decides-only edit/validation tool.
30
+ It governs *changes to docs/skills/laws*, not live agent traffic.
31
+ - BOUNDARY: "8/8 law-coverage ≠ disciplined" — the gate reminds; it does not by itself prove the edit is
32
+ wise. The verifier (the other seat) still attack-verifies content, per author≠verifier.
33
+
34
+ ## Hard holds (T0 only; NOT this docs pass)
35
+ No auto-application of edits to live law/skill docs without the gate + operator authority; no runtime
36
+ fire; no USB/ADC/census/private-root.