vault-sync: 2026-10-17 12:01 (jimmy)

2026-10-17 12:01:19 -07:00
parent 91cd44a331
commit 1bb471c8de
29 changed files with 990 additions and 245 deletions
@@ -2,7 +2,7 @@

 ## 🧩 Daily Summary

-A single-thread, high-intensity day: the **killcorpus** falsification loop (Kalshi `KXBTCD lag-vs-spot`, paper-only) went from *spec-under-review* to *live deliberate eval accruing toward N=967*, and the process survived two real failures and one supervisor runaway along the way. Nearly every human turn (~30) was a short, high-signal verdict from Tony — "Correction accepted", "Approve the two fixes", "Hold for full N=967", "Confirmed. Steady state is correct" — layered on top of dense assistant reports. The day reads like an engineering stand-up where Tony is the reviewer-of-record and the agent does planner/reviewer/builder/recorder work.
+A single-thread, high-intensity day: a paper-only falsification loop (Kalshi `KXBTCD lag-vs-spot`) went from *spec-under-review* to a *live deliberate eval accruing toward N=967*, and the process survived two real failures and one supervisor runaway along the way. Nearly every human turn (~30) was a short, high-signal verdict from Tony — "Correction accepted", "Approve the two fixes", "Hold for full N=967", "Confirmed. Steady state is correct" — layered on top of dense assistant reports. The day reads like an engineering stand-up where Tony is the reviewer-of-record and the agent does planner/reviewer/builder/recorder work.

 Secondary threads: a Hermes **update** (97a9ae8ee5) that landed but left a stale gateway until manually restarted; the **trace-lessons-review** weekly cron ran (1 proposal, 24 dropped); a **Grok round-trip** (Tony used Grok as an external critic, then relayed its diagnosis back); and a Telegram-iOS **paste-path** question that turned out to be client-side.

@@ -18,7 +18,7 @@ Themes: falsification discipline under pressure, separate-engines review, and *n

 **4. Headless allowlist (06:02).** Chose "Level 1 — narrow allowlist" for the unattended `-q` approval gate across the four profiles (see the trace-review proposal below).

-**5. Settle-through proof → eval unblock (15:04–16:26).** Harness bug: documented `--mode smoke [SEC]` silently rejected a bare numeric → first proof launch died. Patched (commit `b833e3c`). Proof run then: **40 signals, 5 trades, 5 settled, +29.11 net**, clock stayed OFF end-to-end. Gitea `Tony_tech/killcorpus` content-unified via Contents API (deliberately **no `origin`** — git-level link held on Tony's word). Duplicate spec note folded to a pointer. Every gate green; eval held for the literal phrase **"start the eval"** — which Tony sent as just `1`.
+**5. Settle-through proof → eval unblock (15:04–16:26).** Harness bug: documented `--mode smoke [SEC]` silently rejected a bare numeric → first proof launch died. Patched (commit `b833e3c`). Proof run then: **40 signals, 5 trades, 5 settled, +29.11 net**, clock stayed OFF end-to-end. Duplicate spec note folded to a pointer. Every gate green; eval held for the literal phrase **"start the eval"** — which Tony sent as just `1`.

 **6. Failure #1 — schema drift (16:27).** Health cron escalated: harness died at startup, `table signals has no column named book_read_ts_ms`; all four tables 0 rows. K1 "survives" was vacuous at n=0. Fixed, eval restarted with `REG_TS` intact.

@@ -26,7 +26,7 @@ Themes: falsification discipline under pressure, separate-engines review, and *n

 **8. Hold for N=967 (19:37).** Interim LB went negative and the health check flagged `K1=KILL`. Tony overruled: at n=13/967, SE≈0.095, a negative mean/LB is **noise, not evidence**; the spec has no pre-registered interim kill. Hold, don't freeze, don't file. Health check to report progress without escalating early K1.

-**9. Markdown handoffs.** Three times Tony asked for "a single markdown file" to share with Grok — produced `docs/handoff-2026-10-11.md`, `-v2.md`, and `killcorpus-full-2026-10-11.md` (14 KB). v2 triggered a **write_file refusal** (existing file not re-read → couldn't overwrite), surfaced honestly by the mutation verifier.
+**9. Markdown handoffs.** Three times Tony asked for "a single markdown file" to share with Grok — produced `docs/handoff-2026-10-11.md`, `-v2.md`, and a consolidated `-full` version (14 KB). v2 triggered a **write_file refusal** (existing file not re-read → couldn't overwrite), surfaced honestly by the mutation verifier.

 **10. Hermes update** (session `20261003_123136_a18d76`): update landed; the updater left the pre-update gateway serving (`gateway_restart.incomplete`) → stale `sys.modules`; manual `Hermes_Gateway` task restart cleared it, jimmy:telegram 0 conflicts.

@@ -68,7 +68,7 @@ Themes: falsification discipline under pressure, separate-engines review, and *n
 ## 🎭 Behavioral Adjustments for Tomorrow

 - **Read the verdict at its registered N.** When a gate (K1/LB) prints a label before its sample is met, lead the report with "interim, not decisive until N=X" *before* the value, never after. Tony had to correct this from the outside once; don't make him do it again.
- **Self-test any documented invocation before a live run.** For killcorpus-class work: run the README's exact command form against stubs, not just the argument parser in isolation.
+- **Self-test any documented invocation before a live run.** For long-lived instrumented runs: run the README's exact command form against stubs, not just the argument parser in isolation.
 - **When relaying an external critic's diagnosis, mark the boundary of what I reproduced.** State which claims I verified live vs took on report, and name any layer I found beyond it.
 - **Durability checklist for any multi-day run:** (a) progress counter replays from DB; (b) liveness keyed on a changing quantity; (c) supervisor's restart is idempotent (zero-live check); (d) DB built with the columns the writer uses — reconcile schema vs writer at launch.
 - **Keep handoff artifacts distinct and self-describing.** Use versioned or date-stamped filenames; never overwrite a prior handoff without re-reading it.
@@ -77,12 +77,9 @@ Themes: falsification discipline under pressure, separate-engines review, and *n

 - **Authorization token discipline (durable pattern):** Tony requires a literal, explicit phrase ("start the eval") to begin irreversible-ish runs; generic "proceed"/prior approvals are explicitly rejected. → *candidate for `target=user`* (behavioral standing rule).
 - **Grok is used as an external critic** in the loop; its diagnoses are relayed into Hermes for independent verification. → *candidate for `target=user`* (workflow pattern).
- **killcorpus runtime facts** (durable, project-level): eval = `--mode eval`; supervisor cron 15 m, health cron 1 h; `REG_TS` gate; hold-until-N=967 policy; interim K1 non-actionable. → *candidate for `target=memory`*, but much is already captured in the existing killcorpus memory entry + vault `04_projects/killcorpus/status.md`. Prefer the vault as source of truth; only the *policy* fact is memory-worthy.

 ## ❓ Open Questions

- **True git-level link for `Tony_tech/killcorpus`** — local repo has no `origin`; content is mirrored via the Contents API. Unify the histories (deliberate reconcile) or leave as-is? Tony said "hold" today; revisit when the first autopsy is filed.
- **`docs/handoff-2026-10-11.md` / `-v2.md` / `killcorpus-full-2026-10-11.md`** are untracked/uncommitted. Commit, push to the Gitea mirror, or delete v1/v2? Unanswered.
 - **Merge `software-development/test-driven-development` into `software-development/agent-skills/test-driven-development`?** — reply yes and I'll do it (same name, similarity 1.0; caveat: the target lives inside the bundled `agent-skills` collection, so this may be intentional duplication).

 ## 🚀 Opportunities for Future Improvement