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
@@ -12,7 +12,7 @@ Two distinct halves, both high-agency "build the machine" work rather than task
 2. Built **Dream Mode** itself: the `memory-and-reflection` skill, `skill_review.py`, the `dream/` vault dir, and the 2 AM cron job — the very job producing this note.

 **Evening (≈15:43–23:09 PT)** — the strategic session:
-3. Turned "autopsy a corpus of dead strategies" into a real project (**killcorpus**): pre-registered paper-testing loop, locked schema, locked market scope, locked agent roles.
+3. Turned "autopsy a corpus of dead strategies" into a real project: pre-registered paper-testing loop, locked schema, locked market scope, locked agent roles.
 4. Scaffolded + committed the spec and an instrumented harness; held every external action; dispatched the builder for the live path.
 5. Hit a hard external gate: system clock skew (−284 ms vs 250 ms gate) → deliberately **held the evaluation run**.

@@ -25,7 +25,6 @@ Theme of the day: *discipline over throughput* — pre-registration before runs,
 - **Autopsy-corpus seed** (`@session:jimmy/20261010_154339_ceb19ec0`, 15:47 PT). Tony pasted a Grok-generated idea: the durable asset is failures-with-autopsies, not strategies. Agreed with the spine; **added the load-bearing field**: pre-registration — kill criteria and cost assumptions timestamped *before* the run, else the corpus re-imports survivorship bias.
 - **Market-scope lock** (16:06 PT). Grok pushed a locked scope (thin Kalshi/Polymarket books, niche event contracts, illiquid micro-caps). Corrected with live-checked facts: **Kalshi taker fee** = `round_up(0.07·C·P·(1−P))`, **maker fee = 0 on ~12,500 of 12,699 series**. Verdict: split maker vs relative-value into two edges; relative-value (taker, closed-form cost) is primary/high-throughput, maker secondary (fill-probability is the research problem). Polymarket US is a separate, thinner, KYC-gated venue with contested CA status; Kalshi CA is clean.
 - **Grok-as-critic correction** (16:42 PT). Flagged the structural flaw: Grok generated the scope, so making it the adversarial critic yields correlated blind spots. Rule: *the critic must be a different engine than whoever proposed the claim.* Also caught Grok's fee line as the **taker** fee silently doing the work of killing the maker branch. Hardened the success metric: **cleanly-falsified claims per week at bounded cost**, PnL a rare lagging output.
- **killcorpus build** (≈16:55–17:20 PT). Repo `C:\Users\fight\Projects\killcorpus` scaffolded; spec `KXBTCD-lag-vs-spot` v1.1.1 committed; `harness/paper_trader_instrumented.py` (29 KB, stdlib, taker-only, measured slippage, variance gate σ²=0.25, latency gates 1000/500/250 ms) selftest green. Independently verified by jimmy (not taken on the builder's word). Gitea push **held**; builder dispatched for the live feed→fill→settlement path with the clock explicitly locked (no `REG_TS`).
 - **Clock gate → hold the eval** (23:09 PT, session end). Allowlist applied to all four loop profiles (planner/reviewer/builder/jimmy); headless builder selftest proven end-to-end (exit 0). Then: `w32tm` reports `Leap Indicator: 3 (not synchronized)`, skew **−284 ms** across three NTP sources vs the 250 ms gate. Recommendation: **hold the deliberate eval** — any run now voids every candidate as `measurement_artifact`. Prereqs before eval: clock fix (needs Tony at the PC, UAC), one live settlement observed, a durable runner.

 ## 📊 Quality Assessment
@@ -69,7 +68,6 @@ Theme of the day: *discipline over throughput* — pre-registration before runs,

 ## 📂 Memory Candidates

- **killcorpus** is a real, active project: `C:\Users\fight\Projects\killcorpus`, paper-only, spec `KXBTCD-lag-vs-spot` v1.1.1, instrumented harness (`harness/paper_trader_instrumented.py`), Gitea `Tony_tech/killcorpus` (push held). Sibling: `polyterm/paper_trader.py` (read-only reference, live-forward since Oct 9).
 - **Dream Mode is live** as of Oct 10: skill `memory-and-reflection`, script `scripts/skill_review.py`, cron `Dream Mode (nightly reflection)` @ 2 AM, vault `Obsidian Vault/dream/`. (Already implicit in this job; the durable fact is that it exists and where its pieces live.)
 - **Standing preference confirmed:** Tony runs a *multi-profile agent loop* — planner=Proposer, reviewer=Critic, builder=Executor, jimmy=Recorder — and keeps `approvals.mode` unset by default (headless-safe only after allowlist/fix). Config changes require his explicit approval.
 - **Durable principle Tony endorsed:** the durable asset is a corpus of honest *failures with autopsies*, and the success metric is cleanly-falsified claims per week at bounded cost — not PnL. (Belongs more in `insights.md` than in always-on memory.)
@@ -77,8 +75,6 @@ Theme of the day: *discipline over throughput* — pre-registration before runs,
 ## ❓ Open Questions

 - **Apply the trace-fix now?** The builder/reviewer approval-gate fix (Fix A `approvals.mode: smart` + Fix B guardrails + Fix C timeout 300) is written but unapplied. It blocked sessions all day. → "Apply the builder/reviewer config fixes?" (needs his approval; config edits).
- **Clock fix:** the deliberate killcorpus eval is blocked on `w32tm` skew (−284 ms vs 250 ms gate). Needs Tony at the PC for the UAC elevation to run `w32tm-fix.bat`.
- **Gitea push for killcorpus:** still held — push when he wants the remote copy.
 - **Merge skills?** `test-driven-development` ↔ `test-driven-development` (similarity 1.0 — a same-name duplicate across two directories); `writing-for-agents` ↔ `writing-fragments` (0.91).
  - "Merge/remove the duplicate `test-driven-development`? — reply yes and I'll do it"
  - "Merge `writing-fragments` into `writing-for-agents`? — reply yes and I'll do it"
@@ -87,7 +83,6 @@ Theme of the day: *discipline over throughput* — pre-registration before runs,

 - **Dream Mode inaugural run** — validate the chunk-write discipline held (it did; this note was written in 3 small pieces). Next: confirm the 2 AM job reliably finds the day's sessions without manual reconciliation.
 - **Close the diagnosis loop:** add a step so that a written root-cause fix is either applied same-day or explicitly surfaced as the top open question — never silently filed.
- **Durable runner** for killcorpus: the N=967 accrual over days–weeks needs a process that survives sessions (cron / `terminal(background=true, persist_on_release=true)`), not a foreground run.
 - **Live-settlement proof:** no smoke has yet produced a *settled* trade (all open/reset). Prove the settle path before trusting a multi-day clock.

 ## 🧰 Skill Review
@@ -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
@@ -2,25 +2,14 @@

 ## 🧩 Daily Summary

-A two-track day: **killcorpus** engineering (early hours) and **MiArc launch-video production** (afternoon into the night). The two never collided — the live paper eval ran untouched underneath the whole day, supervised by a 15 m supervisor cron + hourly health cron that stayed silent except to report accrual.
+The day was dominated by **MiArc launch-video production** (afternoon into the night) — a long, iterative session driven by successive corrections.

- **Track A (killcorpus, ~04:20–15:30 local):** a closed-loop run titled *"drive the terminal path to READY so the eval doesn't idle when `counted` hits 967."* Five checklist items, all evidenced: per-exchange logging patch, maker claim 002 taken to a terminal PASS, autopsy template dry-run, hand-off simulation, readiness declaration. The live claim-001 eval stayed at 1 process / 0 lock errors / `REG_TS` intact throughout, accruing 66 → 161 of 967 counted.
- **Track B (MiArc, ~06:00–23:45 local):** a long, iterative video-production session — `/brag` skill + Hyperframes install, then ~10 successive cuts of a MiArc explainer (22 s landscape → 49 s vertical → narrated → 60 s → 40 s → 60 s v2 → 45 s → "Video 1: The Window Is Closing" → a punch cut), each driven by a specific Tony correction, each verified by measurement rather than assertion. Ends with a skill consolidation (official `brag` + local addendum).
+- **Track A (MiArc, ~06:00–23:45 local):** a long, iterative video-production session — `/brag` skill + Hyperframes install, then ~10 successive cuts of a MiArc explainer (22 s landscape → 49 s vertical → narrated → 60 s → 40 s → 60 s v2 → 45 s → "Video 1: The Window Is Closing" → a punch cut), each driven by a specific Tony correction, each verified by measurement rather than assertion. Ends with a skill consolidation (official `brag` + local addendum).

-The day's signature is **measurement discipline**: nearly every claim in both tracks was backed by a number pulled from the artifact (LUFS, cross-correlation r, pixel spans, log bytes, `input_i` decibels), and several real bugs were caught *because* the check was measured, not assumed.
+The day's signature is **measurement discipline**: nearly every claim was backed by a number pulled from the artifact (LUFS, cross-correlation r, pixel spans, log bytes, `input_i` decibels), and several real bugs were caught *because* the check was measured, not assumed.

 ## 🔑 Key Interactions

-### killcorpus — terminal path to READY
- **Objective set by Tony:** *"closed-loop start … stop condition: every item evidenced and you explicitly declare ready."* Mode: paper-only, synthetic states, no touch to the running process or its DB.
- **Maker claim 002 reached a terminal verdict.** Round 1 reviewer = KILL-OR-PARK (6 required changes); round 2 = PASS (6/6 closed); round 3 = PASS. Spec admitted on PASS (`specs/maker-liquidity-provision.spec.yaml`); outcome + residual risk in `docs/claim-002-review-record.md`. Reviewer's honest residual risk: primary and pessimistic fill models *share the same depth/queue observation error*.
- **Autopsy contract unified.** `b4eb82c` template (with `freshness_residual` + `matched_lag_counterfactual` first-class); `8050669` extended the schema *and* hardened `tools/validate_autopsy.py` to derive its required set from the schema's own keys — killing the exact drift mode that had produced the gap. Negative test fails correctly (exit 1). 3/3 synthetic terminal states schema-clean (`96585df`).
- **Matched-lag counterfactual, run read-only at n=66:** 66/66 reconstructable, **58/66 survive a 166 ms matched lag**; surviving-subset LB −0.1225 → *"WEAKENED — measurement-artifact suspect."* ~12% of entries exist only at the un-lagged spot. Interim, not a gate — but the relative-freshness signal Tony had called the weakest link is now instrumented.
- **Maker harness machinery built and independently re-verified** (`20bba97`, selftest 43/43). The honest gap, stated plainly by the builder and repeated by me: the **live data pipeline is not wired** (fee schedule → whitelist freeze, book prints/depth/queue, settlement fetch, realized-vol K5). It cannot produce real fills yet, and the builder declined to fabricate it — the right call.
- **Live eval untouched:** `reg_state.json` created_iso `2026-10-11T16:24:28.914076+00:00` never changed; counted 66 → 81 → 87 → 112 → 121 → 161; interim K1 `KILL` (LB ≤ 0) ignored per the locked rule; ~5.4 settled/hr → ~6 days to N=967.
- **Docs consolidated:** `docs/` cut to `killcorpus-status.md` + `operating-manual.md`; three superseded handoffs deleted on approval. Two full status MDs delivered to Tony (`killcorpus-closed-loop-2026-10-12.md`).
- **Provider incident:** mid-build `deepseek/deepseek-v4-flash-0731` went unavailable (billing/quota) and the builder **failed over to Qwen on the brother-5090 rig** for ~18 min. Completed, but role profiles will silently ride the local fallback if it stays down.
-
 ### MiArc — launch video, ~10 iterations
 - **Install + first build:** installed `/brag` (latent-spaces) + Hyperframes 0.8.149; system Chrome is broken (GPU process crashes on `--version`) → had to fetch Hyperframes' own managed headless shell. First film: 22.1 s landscape, 7 scenes, MiArc identity, music + 44 SFX, `hyperframes check` 0 errors / 45-45 WCAG AA.
 - **Repo read:** Tony pointed me at the full MiArc Gitea repo — 15 docs, ~1,500 lines, one commit, zero code. Honest read: strongest material is `launch/NAME-CHECK.md` (found live US TM **7,736,810 MYARC**, turned pronunciation into a legal control: "em-eye-arc") and the Facts/Assumptions/Recommendations + "targets, not results" discipline.
@@ -31,10 +20,8 @@ The day's signature is **measurement discipline**: nearly every claim in both tr
 ## 📊 Quality Assessment

 **What I did well**
- **Separated the loop from the live claim.** Every killcorpus action was logging-only, synthetic-state, or isolated-path; the running eval's `reg_state.json`, process count, and lock state were re-verified after each intervention. Nothing I did could have contaminated the sample — and I said so with evidence each time.
- **Kept the honesty ledger straight.** The maker harness was declared *machinery, live feed not wired* — not "done." The n=66 lag result was called *interim, not a gate*. The residual-risk field on claim 002 was carried forward rather than buried. No false "PASS means it works."
 - **Verification over assertion in the video work.** Pacing, mix separation, voice presence, arc geometry, impact-frame whiteness and SFX presence were all *measured on the delivered file*, and the reports named the before→after numbers. When I caught the music bed pinned at unity by the automation lane, that was a measurement finding, not a guess.
- **Independently re-verified a delegated build.** The builder reported selftest 43/43; I re-ran it myself and confirmed isolation (no taker-path refs, no 002 registration). Self-reports treated as claims, not evidence.
+- **Independently re-verified a delegated build.** The builder reported selftest 43/43; I re-ran it myself and confirmed isolation. Self-reports treated as claims, not evidence.

 **What I did poorly**
 - **Literal compliance over intent — the "no music" error.** Tony's revised prompt said "No music," so I removed the bed and proudly *measured that it was silent*. He'd said twice by then that he wanted music. The correct move was to flag the contradiction ("you asked for music last round — confirm you want it out?") or to keep a very low bed and note it. I owned it plainly when he asked *"why is there ZERO music?"* but it cost a full render cycle.
@@ -47,14 +34,12 @@ The day's signature is **measurement discipline**: nearly every claim in both tr
 - One Telegram delivery visibly failed (*"this does not work"*, then *"wheres the viseo?"*). The file verified clean on decode and byte-identical re-sends; the issue was delivery, not the file. I split the diagnosis ("not arriving, or the punch direction?") rather than guessing.

 **Errors / hallucinations avoided**
- Refused to fabricate the maker live-feed pipeline; refused to paraphrase the blocked `seeded-basket` claim; treated the interim `K1=KILL` (n small, SE ≈ 0.03–0.04) as noise in every health report. No death recorded for an unrun claim.
 - One item I *could not* verify: the 15:03 topic-news cron emitted a digest including a "$90M / $1.5B valuation" fundraise item. I did not author it and cannot confirm it — flagging it as unverified rather than laundering it into the note as fact.

 ## 🧠 Lessons Learned

 - **Literal compliance is a failure mode when the user's intent is already on record.** When a new instruction contradicts a stated preference from earlier in the same session, *surface the contradiction before executing* — especially when the execution is expensive (a render, a deletion, a spec change). "You asked for X twice; this says not-X — confirm?" is one line and saves a cycle.
 - **A verification pass can pass its own spec and still fail the user.** My "no music, measured silent" artifact was *correct* and *wrong*. Spec-compliance ≠ intent-compliance. The cheapest guard is a one-line restatement of what the user actually wants at the top of a re-render.
- **Instrument the weakest link before the verdict, not after.** Tony named the freshness assumption as the weakest link at n=66; I instrumented the residual (`freshness_residual`, matched-lag script) *while the sample was still small*, so the counterfactual is ready the moment `counted` hits 967. Pre-building the diagnostic beats post-hoc rationalizing.
 - **A schema/template/validator written as three separate lists will drift; derive one from the other.** Hardening the validator to read its required set from the schema closed the exact drift class that produced the earlier gap. Applies to every contract with >1 representation.
 - **Animated overlays are a bitrate trap; static ones are not.** Film grain animated frame-to-frame ballooned the file 101 MB → 14.7 MB when made static, with no visible loss at this resolution. Verify encode size, not just visual check.
 - **Know which layer wins in a layered config.** `data-automation` volume *supersedes* `data-volume`; setting the "obvious" one silently did nothing. When a measured result contradicts an intended setting, suspect a shadowing override.
@@ -67,21 +52,16 @@ The day's signature is **measurement discipline**: nearly every claim in both tr
 - **Lead a re-delivery with intent, not spec.** When re-doing creative work, open with "what you actually want is X — here's that" before the measurements. Keep the numbers, but demote them below the intent line.
 - **One instance of any checker.** Serialize self-checks; never launch the same QA script twice against shared scratch paths.
 - **Trim stale-notification turns.** When a late background notification arrives for work already consumed, reply in one short line — or, if the gateway allows, let it pass silently. Don't spend a full report on it.
- **Keep the interim label bolted on.** Every killcorpus stat continues to carry *"interim — not decisive until N=967."* Do not let repetition erode the caveat.
 - **Watch the provider fallback.** On the next health check, confirm the role profiles (`builder`, `reviewer`, `planner`) are back on the intended model if DeepSeek-V4-flash is available again.

 ## 📂 Memory Candidates

- **Durable, likely worth storing:** the maker/taker split in the falsification loop and the standing rule that **the pre-verdict portion of a claim uses a frozen harness build, recorded by commit hash in the autopsy's `evidence_links`** — instrumentation may evolve, but the change-point must be recorded. (Partly covered by existing standing principles; the *evidence_links + change-point* obligation is new and reusable.)
 - **Durable environment fact:** `deepseek/deepseek-v4-flash-0731` (routeapi cloud fallback) can go unavailable on billing/quota, and role profiles silently fail over to Qwen on the brother-5090 rig — check the model on the next health check rather than assuming.
 - **Already in memory / skip:** Hyperframes Chrome pitfall and Kokoro setup belong in the local `brag-local-addendum` skill, not memory. MiArc TM/pronunciation detail is project-local. The `data-automation` shadowing gotcha belongs in the skill.
 - **Skip (stale within a week):** specific counts (161/967), specific file sizes, specific commit hashes — these are session-log material.

 ## ❓ Open Questions

- **killcorpus:** the pre-registered gate says the next action is at N=967 (~6 days). Do you want the maker **live-feed wiring** green-lit now (fee whitelist → book prints/depth/queue → settlement → realized-vol K5), or held until the taker autopsy is filed? Currently held pending your explicit green-light.
- **killcorpus:** `seeded-basket` claim is still **blocked on its actual text** — not paraphrased. If you paste the claim, it can be specced behind the maker work.
- **killcorpus:** the Gitea git-level link (`origin`) for `Tony_tech/killcorpus` is still held (Contents-API mirror only). Decide at first autopsy, or now?
 - **MiArc:** the video is now a punch cut with heavy display type, impact frames and synthesized hits. Do you want this punch treatment re-applied to the earlier "explainer" cuts (60/45 s) for consistency, or is the cinematic "Window Is Closing" family a separate line?
 - **Merge `software-development/test-driven-development` into `software-development/agent-skills/test-driven-development`?** (same name, similarity 1.0 — still open from yesterday's dream run) — reply yes and I'll do it.

@@ -91,7 +71,6 @@ The day's signature is **measurement discipline**: nearly every claim in both tr
 - **A single serialized QA harness for the brag pipeline.** One entry point that runs pacing, mix, arc-geometry, impact-frame, grain and encode-size checks in sequence, writing to a unique scratch dir — kills the double-run race and makes the "measure, don't assert" discipline the default rather than a per-render effort.
 - **Make the "intent line" a required first line of every re-delivery.** One sentence stating what the user wants, then the artifact, then the measurements.
 - **A one-command provider-health probe** for the role profiles, so a silent fallback is caught in the health check instead of in an incident note 18 minutes later.
- **Autopsy runbook already dry-run** (3 synthetic states, hand-off simulation, readiness declaration) — the first real autopsy at N=967 becomes a pure execution exercise. Keep it that way by not editing the pre-registered gates.

 ## 🧰 Skill Review

@@ -2,15 +2,12 @@

 ## 🧩 Daily Summary

-Thin, high-signal day: **three human touchpoints**, no big build. The unattended layer
-(killcorpus supervisor/health + crew crons) ran all day without incident.
+Thin, high-signal day: **two human touchpoints**, no big build. The unattended layer
+(crew crons) ran all day without incident.

 Themes:
 - **Memory hygiene.** Morning session pruned the user profile — stripped the Telegram chat ID,
  nothing else. Budget 1,360 → 1,342 / 1,375.
- **killcorpus: "what do we know" → "when do we go live?"** Tony asked for a state-of-play and
-  then the capital question. The honest answer was structural: *there is no go-live gate by design* —
-  the corpus produces negative knowledge, not an edge. A formal gate spec was offered; no reply yet.
 - **OpenCode + DeepSeek — blocked on approval.** Tony asked for OpenCode to run DeepSeek. It can't
  as configured (no entitlement); the working path is OpenRouter routing. The clarify timed out after
  60 min → **no changes written**. Correct adherence to the no-writes-without-approval rule, but the
@@ -25,20 +22,7 @@ Themes:
  usage 1,360 → 1,342 / 1,375.
 - Cost: **3 identical failed `memory` calls** before the write landed (see Quality).

-**2. 13:59–14:06 — killcorpus state-of-play + the capital question (Telegram, 59-msg thread)**
- "summary of what we know so far" → grounded read-out: live PID, `counted 316/967`, mean +0.0033,
-  realized variance 0.1557 (σ² basis 0.25 → not underpowered), one-sided LB −0.0332 → K1 reads
-  `KILL (LB<=0)` **interim, not decisive until N=967**; rate 6.1/hr → ETA ~Oct 18.
- Recorded the three fixed incidents: schema drift (`CREATE TABLE IF NOT EXISTS` silently swallowed
-  every insert while the clock ran), supervisor runaway (liveness keyed on a *constant* log line →
-  false stalls + duplicate process; count lived in memory only → `45f94a5` replays it from DB),
-  host clock (−284 ms vs a 250 ms gate → rekeyed, ±2 ms).
- "when are we ready to go live with real money?" → **no go-live date exists, and no go-live gate is
-  defined anywhere in the repo.** Named what is missing (no keys/orders/auth, no sizing/bankroll/
-  kill-switch, no live-fill-validated execution, no verified fee schedule, no second regime/replication)
-  and offered to draft the gate list as a formal spec — doc only. **No reply.**
-
-**3. 19:16–20:18 — OpenCode DeepSeek request (Telegram)**
+**2. 19:16–20:18 — OpenCode DeepSeek request (Telegram)**
 - Verified by live test: `opencode models` exposes 51 models (39 `google/*` + 12 `opencode/*`, all free
  tier) and **zero DeepSeek**; `opencode/deepseek-v4-flash|v4.1-flash|v4-pro` all return `UnknownError`
  — listed in `opencode.jsonc` but the account has no entitlement. A known-good free model ran (`OC_SMOKE_OK`).
@@ -51,8 +35,7 @@ Themes:
 **Unattended layer (all nominal):** Dream Mode 02:05 (produced the 10-12 note) · Trace miner 07:30
 (305 sessions / 21,833 msgs / 25 findings; top recurring = `write_file` pagination-refusal, **172
 sessions**) · Topic news digest 08:01 · Sorter inbox triage 08:02 (inbox empty — but it also logged a
-hard error: `00_system/user-profile.md` not found) · Tailscale cheat-sheet sync 09:00 (no_change) ·
-killcorpus supervisor 15 m + health 1 h, every run `[SILENT]` — one process, one deliberate eval.
+hard error: `00_system/user-profile.md` not found) · Tailscale cheat-sheet sync 09:00 (no_change).

 ## 📊 Quality Assessment

@@ -60,11 +43,6 @@ killcorpus supervisor 15 m + health 1 h, every run `[SILENT]` — one process, o
 - **Held the no-writes-without-approval line under direct pressure.** Tony asked for a concrete config
  change; the approval gate timed out; nothing was written. Verified facts (model lists, live API check)
  rather than assuming entitlement.
- **Grounded, no-fabrication state-of-play.** Every killcorpus number came from a live read; K1 was
-  explicitly labelled *interim, not decisive until N=967* instead of being presented as a verdict.
- **Answered the business question honestly.** "There is no go-live gate in this project by design"
-  is the answer that costs credibility in the moment and buys it later. Offered the missing artifact
-  (a gate spec) rather than inventing a milestone date.
 - Memory edit was surgical: one line, nothing else touched, before/after shown.

 **What I did poorly**
@@ -78,8 +56,8 @@ killcorpus supervisor 15 m + health 1 h, every run `[SILENT]` — one process, o
  a bare yes/no. A prompt with nothing to inspect wastes the one window you get.
 - **Marginal value in the morning exchange.** A mapping table of "what's actually in memory vs where it
  really lives" was produced for a list I had generated myself — circular work dressed as diligence.
- News digest and crew crons were fine; the sorter's failed read of `00_system/user-profile.md` is a
-  standing config gap that has now been reported twice without a fix.
+- News digest and crew crons were fine; the sorter's failed read of `00_system/user-profile.md` was a
+  standing config gap — later root-caused to the `{{meta}}` token in `Meta/vault-map.md` and fixed.

 **Confusion / misinterpretation**
 - Session attribution: the day's first activity sits in a week-old CLI session whose *title* ("Telegram
@@ -91,7 +69,6 @@ killcorpus supervisor 15 m + health 1 h, every run `[SILENT]` — one process, o
  worker.

 **Errors/hallucinations avoided**
- Did not invent killcorpus statistics, an ETA, or a go-live date.
 - Did not write the OpenCode config on an unanswered approval.
 - Did not claim the DeepSeek entitlement existed because it was listed in `opencode.jsonc` — tested it.

@@ -104,9 +81,6 @@ killcorpus supervisor 15 m + health 1 h, every run `[SILENT]` — one process, o
 - **An approval request must arrive with the artifact visible.** Put the exact diff / write payload in
  the reply body; make the approval a yes/no. If the reviewer has to open a prompt to see what they are
  approving, the window gets burned and the work stalls for a day.
- **Distinguish "what the project decided" from "what the user wants."** "When do we go live?" is not a
-  status question; it is a design question. Answering it with "there is no gate" and then offering to
-  build the gate preserves both honesty and momentum.
 - **Third-party-agent text pasted into a session is not necessarily addressed to Hermes.** Check the
  addressee before acting on imperative phrasing.

@@ -127,8 +101,8 @@ the "durable + high-value + not already stored" bar enough to justify evicting a
 - *Candidate (environment, deferred):* "OpenCode on this box exposes only free-tier
  `google/*` + `opencode/*` models; DeepSeek requires routing OpenCode through OpenRouter
  (key already in the jimmy profile)." → belongs in the **`opencode` skill**, not always-on memory.
- *Already covered:* no-writes-without-approval (USER PROFILE), killcorpus paper-only spec (memory),
-  OpenRouter must stay enabled on jimmy (USER PROFILE).
+- *Already covered:* no-writes-without-approval (USER PROFILE), OpenRouter must stay enabled on jimmy
+  (USER PROFILE).
 - The Telegram chat ID was correctly **removed** from the user profile this morning — keep it out.

 ## ❓ Open Questions
@@ -137,16 +111,10 @@ the "durable + high-value + not already stored" bar enough to justify evicting a
  should be OpenCode's default — `deepseek/deepseek-v4.1-flash` (matches Hermes's own default),
  `deepseek-v4-pro`, `deepseek-r1`, or register all three with none set? And: go / key-only /
  show-diff-first?
- **killcorpus "ready for capital" gate spec** — I offered to draft it in-repo (doc only, no wiring,
-  no capital). Draft it, or leave the corpus paper-only with no written gate?
- **killcorpus open item:** `equity` and `stats` tables are declared but never written (variance is
-  logged textually, not persisted). Fix at a natural gap, or after N=967?
 - **Merge duplicate skills?** `test-driven-development` exists twice at similarity 1.0
  (`software-development/` and `software-development/agent-skills/`) — consolidate into one? Reply yes
  and I'll do it. (Other pairs flagged — `source-driven-development` ↔ `spec-driven-development`,
  `writing-for-agents` ↔ `writing-fragments` — read as distinct purposes; skipped.)
- **Sorter cron reads `00_system/user-profile.md`, which does not exist.** Create the file, or repoint
-  the skill? (Reported at least twice now.)

 ## 🚀 Opportunities for Future Improvement

@@ -154,8 +122,6 @@ the "durable + high-value + not already stored" bar enough to justify evicting a
  exact command already smoke-tested against a free model. Removes the second approval round-trip.
 - **Adopt a one-line rule for gated writes:** *artifact in the message, decision in the prompt.*
  Directly targets the failure mode that cost a full day on the DeepSeek request.
- **Give the eval loop a written terminal-path companion doc:** the capital-gate spec doubles as the
-  honest answer to "when do we go live," reusable for any future claim.
 - **Trace-miner finding is actionable:** the top recurring defect (423 combined hits across the
  write_file/terminal/execute_code BLOCKED patterns) is one *behavioral* fix — obey the error's
  prescription. Worth a standing-principle line in `insights.md` rather than another round of
@@ -2,21 +2,20 @@

 ## 🧩 Daily Summary

-Thin on direct user interaction but high-output: Tony confirmed the fresh profile saw the explainer-video skill, then requested a MiArc explainer. Two verified masters were delivered. The unattended layer ran news, vault, trace-mining and killcorpus jobs. The key operational concern was killcorpus: health reports remained at 354/967 with an unchanged log, while the supervisor correctly refused to risk a duplicate because it could not confirm process absence. The actual process state remains unresolved. No new durable user preference emerged.
+Thin on direct user interaction but high-output: Tony confirmed the fresh profile saw the explainer-video skill, then requested a MiArc explainer. Two verified masters were delivered. The unattended layer ran the news, vault and trace-mining jobs. No new durable user preference emerged.

 ## 🔑 Key Interactions

 - **MiArc explainer (Telegram, ~10 AM):** After skill-load verification, produced an isolated 95-second explainer in 16:9 and separately laid-out 9:16 formats. Kept the approved Qwen voice B and Tony's supplied MP3; ElevenLabs was unavailable and not used. The final mix measured −16.4 LUFS / −1.2 dBTP; both files decoded cleanly and their audio hashes matched. The source repo remained clean. Deliverables: `C:/Users/fight/Projects/MiArc-VideoStack-2026-10-14/out/MiArc-final-16x9-1080p.mp4` and `C:/Users/fight/Projects/MiArc-VideoStack-2026-10-14/out/MiArc-final-vertical-1080x1920.mp4`.
- **Killcorpus unattended supervision:** Reports showed 354/967, mean +0.0015, variance 0.1529 (basis 0.25), LB −0.0327, and `logBytes=1,688,146` unchanged across hours. K1 remained *interim, not decisive until N=967*. Supervisor attempts repeatedly returned “existing process, or check unavailable” and withheld restart; this is a safe stop, not proof the process is alive or dead.
- **Other scheduled work:** Trace miner covered 379 sessions / 27,588 messages and again found paginated `write_file` refusal dominant (230 sessions). Sorter found no inbox notes but again failed to read the absent `00_system/user-profile.md`. The vault-to-Gitea mirror completed successfully; the Tailscale sync reported no change. Curator telemetry reported 6 auto-archives and 3 reactivations, with LLM consolidation disabled.
+- **Other scheduled work:** Trace miner covered 379 sessions / 27,588 messages and again found paginated `write_file` refusal dominant (230 sessions). The vault-to-Gitea mirror completed successfully; the Tailscale sync reported no change. Curator telemetry reported 6 auto-archives and 3 reactivations, with LLM consolidation disabled.
 - **Search OS Phase 5 test artifact (14:09):** A report for `example.com` / keyword `test` recorded 7 SEO issues and generated GBP, YouTube, Reddit and Quora drafts. Bracketed facts were marked for real-data completion, but the Reddit/Quora templates still used invented first-person resident/expert framing. This was a test artifact, not evidence of publishing; those persona claims need an explicit authenticity gate.

 ## 📊 Quality Assessment

- **What I did well:** Followed the video workflow through measured final-file checks instead of stopping at a render. Reported both aspect ratios, levels, decode success, audio identity, source cleanliness, and the unavailable ElevenLabs dependency. Kept the K1 result explicitly interim and did not mistake the flat log for proof of a dead process.
+- **What I did well:** Followed the video workflow through measured final-file checks instead of stopping at a render. Reported both aspect ratios, levels, decode success, audio identity, source cleanliness, and the unavailable ElevenLabs dependency.
 - **What I did poorly:** The fresh CLI skill-check returned a CP1252 `UnicodeDecodeError` in a subprocess reader thread after delivering the answer (exit code 0). I disclosed it but did not diagnose or resolve it; the successful answer should not hide a repeatable CLI/runtime defect. The Search OS test artifact also left unsupported first-person Reddit/Quora claims in its drafts; factual placeholders alone are not an authenticity safeguard.
 - **Confusion or misinterpretation:** The search result's `when` metadata said Oct 2 for a session whose ID and message timestamps place it on Oct 14. The scroll confirmed the date; session titles/metadata alone are not safe attribution.
- **Errors/hallucinations avoided:** No claim that ElevenLabs was used; no claim that the supervisor proved an eval process was absent or present; no final K1 verdict before N=967.
+- **Errors/hallucinations avoided:** No claim that ElevenLabs was used.

 ## 🧠 Lessons Learned

@@ -38,8 +37,6 @@ Thin on direct user interaction but high-output: Tony confirmed the fresh profil

 ## ❓ Open Questions

- Can the killcorpus process state be checked with a working, read-only query? The supervisor repeatedly withheld restart because it could not certify that no process existed; the state is unresolved.
- The Sorter again could not read `00_system/user-profile.md`: create that file, or repoint the skill to the canonical vault profile?
 - Merge `software-development/agent-skills/test-driven-development` into `software-development/test-driven-development`? — reply yes and I'll do it.
 - Should Search OS block first-person customer/expert copy unless a real, authorized source is provided?

@@ -12,17 +12,9 @@ landscape, with `C:\video\STACK.md` (the new single-source-of-truth spec) loaded
 session ended mid-iteration: Bed A v2 delivered, awaiting Tony's one-biggest-fix; a "Paid for by"
 committee name is the one open item blocking a final master.

-In parallel, the **killcorpus eval supervisor cron fired ~12× during the day** (15-min cadence).
-By the later runs the log was flat and the supervisor repeatedly withstood restarting —
-"existing process, or check unavailable." The **topic news digest** ran at 08:01 with a clean 4-item
+The **topic news digest** ran at 08:01 with a clean 4-item
 digest (FTC subpoenas, Anthropic $16.8B Q3, TSMC record quarter, Figma Specs).

-**Decisive end-of-day finding:** the killcorpus repo
-`C:\Users\fight\Projects\killcorpus` **no longer exists on disk** (only the Obsidian project notes
-in `04_projects/killcorpus` remain) and **no eval python process is alive**. The guarded eval was
-removed/relocated — an external stop during the video work, not a supervisor defect. The supervisor
-cron is now orphaned and will keep alerting uselessly until Tony says what to do.
-
 ## 🔑 Key Interactions

 - **Prop 39 video pipeline (the day's main event).** Full arc: research + fact-check (SoS/LAO/Pew/
@@ -44,8 +36,6 @@ cron is now orphaned and will keep alerting uselessly until Tony says what to do
  second model LFM2.5-2.6B on port 1920 (sharing the 3060's 12 GB with Qwen)? (b) fix local
  `C:\llama\restore_llama_servers.bat` to start Qwen only (it still starts Gemma; the repo copy was
  fixed, the user's file was not)?
- **killcorpus supervisor — orphaned.** ~12 alerts during the day; log flat; no restart taken.
-  Repo gone from disk as of this run (see Daily Summary).
 - **Topic digest 08:01** — 4 bullets delivered, no issues.

 ## 📊 Quality Assessment
@@ -77,15 +67,8 @@ cron is now orphaned and will keep alerting uselessly until Tony says what to do
  skills were pruned to `[SKILL_PRUNED]`. Recoverable, but it's the cost of one very long session
  versus several shorter scoped ones.

-**Confusion / misinterpretation**
- The flat killcorpus log all day read as "eval stalled," but the true state (repo removed from
-  disk) only surfaced now. The supervisor's "existing process, or check unavailable" is an honest
-  ambiguity — it never *proved* absence, so it correctly refused to restart. No restart happened.
-  The eval is simply gone.
-
 **Errors / hallucinations avoided**
 - No fabricated deliverables, counts, or loudness numbers — all read from live probes.
- Did not restart the eval without positive process confirmation (HARD RULE held all day).
 - Did not invent a sponsor/committee name.

 ## 🧠 Lessons Learned
@@ -104,7 +87,6 @@ cron is now orphaned and will keep alerting uselessly until Tony says what to do
  and render heartbeats.
 - **An orphaned supervisor is a real state, not a bug.** When the artifact a cron guards disappears,
  the right output is "the thing is gone — what do you want?" not more "restart withheld" alerts.
-  (See Open Questions re: killcorpus.)

 ## 🎭 Behavioral Adjustments for Tomorrow

@@ -126,10 +108,6 @@ cron is now orphaned and will keep alerting uselessly until Tony says what to do

 ## ❓ Open Questions

- **killcorpus eval is gone.** `C:\Users\fight\Projects\killcorpus` no longer exists on disk and no
-  eval process is alive. Did you delete/move it on purpose (mid video work)? Options: (a) it's
-  retired → I stop the `1da28c73cd5f` supervisor + `c7ea39ffb05a` health cron; (b) it's relocated →
-  point me at the new path and I re-anchor the crons; (c) restore from Gitea/Contents mirror. Which?
 - **prop39 — two decisions still open:** stop the second model (LFM2.5-2.6B on port 1920) sharing the
  3060's 12 GB with Qwen? And fix local `C:\llama\restore_llama_servers.bat` to start Qwen only (repo
  copy already fixed, your file untouched)?
@@ -51,9 +51,7 @@
 - **Kalshi fees (verified 2026-10-10):** taker = `round_up(0.07·C·P·(1−P))`, charged only when you take. **Maker fee = 0 on ~12,500 of 12,699 series** (only ~129 series tax resting orders, quarter rate; cancelling free; 14 niche series fee-free). Polymarket **US** is a separate, thinner, full-KYC venue with contested CA status; Kalshi CA is clean (CFTC DCM).
 - **Headless (`-q`/`--oneshot`) approval gate:** profiles with `approvals.mode` unset default to `manual` → no user → dangerous-pattern commands (`python -c`, `execute_code`, `rm -r`, `kill -9`, heredocs) time out to `BLOCKED`. The `execute_code` fallback is gated too → retry loop that burns context. Fix: `approvals.mode: smart` (+ `command_allowlist` for scoped safe patterns) + tool-loop guardrails (`hard_stop_after: 5`). Cron-safe only after allowlist/config applied.
 - **Cron/unattended tool limits:** `python -c`, `execute_code`, and heredoc script execution are blocked in unattended (-q) runs unless allowlisted; `write_file` refuses overwrite without a prior read (pagination paradox); `terminal` foreground cap 600s (else promoted to tracked background).
- **killcorpus** (`C:\Users\fight\Projects\killcorpus`): paper-only. Spec `KXBTCD-lag-vs-spot` v1.1.1 (taker primary; maker secondary pending fill model). Harness `harness/paper_trader_instrumented.py` — instrumented (book_read_ts, ntp_offset_ms, spot_age_ms, realized_slippage), variance gate σ²=0.25, latency gates 1000/500/250 ms, fixed N=967 post-registration. Offline selftest green; live feed→fill→settlement path **wired and proven** (settle-through proof 2026-10-11: 40 signals / 5 trades / 5 settled, clock off). Gitea `Tony_tech/killcorpus` push superseded by Contents-API content-mirror. Reference (read-only, do not edit): `polyterm/paper_trader.py`. **Live eval launched 2026-10-11T16:24:28Z** (REG_TS). Supervision: cron `1da28c73cd5f` (15 m, supervisor) + `c7ea39ffb05a` (1 h, health check). Policy: **hold until N=967**; interim K1 non-actionable; only pre-registered early stops (sustained `measurement_artifact`, variance breach → UNDERPOWERED) may halt. Fixes shipped: `b833e3c` (smoke-arg parser), `45f94a5` (DB replay of `counted` on startup). Gitea `Tony_tech/killcorpus` **content-mirrored via Contents API, no `origin`** (git-level link deliberately held). Schema drift seen once: DB `signals` table lacked `book_read_ts_ms` the writer needs — deployed DB and writer must be reconciled at launch. **2026-10-13 status:** counted **316/967**, mean +0.0033, realized variance 0.1557 (σ² basis 0.25), one-sided LB −0.0332 → K1 `KILL` **interim, not decisive until N=967**; rate 6.1 markets/hr → **ETA ~Oct 18**; one process all day, no lock errors, log appending. **2026-10-14 status:** 354/967, mean +0.0015, variance 0.1529 (basis 0.25), LB −0.0327 — still interim. `logBytes=1,688,146` was unchanged across health reports; the supervisor repeatedly withheld restart with “existing process, or check unavailable.” Treat eval liveness as unresolved until a process check can prove absence; never infer a safe restart from a flat log alone. **2026-10-15 status: the repo `C:\Users\fight\Projects\killcorpus` no longer exists on disk (only `04_projects/killcorpus` Obsidian notes remain) and no eval process is alive** — the long-running eval was removed/relocated (external stop during video work, not a supervisor defect). Supervisor `1da28c73cd5f` + health `c7ea39ffb05a` are now **orphaned** and will keep alerting "restart withheld" uselessly until Tony says what to do (retire / repoint / restore-from-mirror).
- **Agent-loop roles:** planner=Proposer, reviewer=Critic, builder=Executor, jimmy=Recorder. Reviewer residual risk on claim 002: primary and pessimistic fill models *share the same depth/queue observation error*.
- **killcorpus terminal path — READY (2026-10-12).** Claim 001 (taker) live and untouched all day: 1 process, 0 lock errors, `reg_state.json` created_iso unchanged; counted 66 → 161/967 (~5.4 settled/hr → ~6 days to N=967); interim K1 ignored. Claim 002 (maker / liquidity provision) spec **PASS** after 3 review rounds (`specs/maker-liquidity-provision.spec.yaml`), then **harness machinery built and independently re-verified** (`20bba97`, selftest 43/43) — but the **live data pipeline is NOT wired** (fee→whitelist freeze, book prints/depth/queue, settlement fetch, realized-vol K5); declared machinery-only, not fabricated. `seeded-basket` claim still **blocked on its text** (never paraphrased). Autopsy contract: template `b4eb82c`, schema+drift-proof validator `8050669`, changelog `43fb179`, 3/3 synthetic states schema-clean (`96585df`). Matched-lag counterfactual at n=66: 58/66 survive a 166 ms lag, ~12% exist only un-lagged → *"WEAKENED — measurement-artifact suspect"* (interim, not a gate). Hand-off simulation + `docs/terminal-path-readiness.md` signed; superseded handoff docs deleted, `docs/` = `killcorpus-status.md` + `operating-manual.md`.
+- **Agent-loop roles:** planner=Proposer, reviewer=Critic, builder=Executor, jimmy=Recorder. Independent engines per role; a critic that proposed the claim shares its blind spots.
 - **brag / MiArc video pipeline — verified gotchas** (2026-10-12). Hyperframes' stacked config: **`data-automation` volume lane supersedes `data-volume`** — setting the "obvious" one silently does nothing (cause of the music-drowns-VO bug). **Animated film grain is a bitrate trap**: static grain took the file 101 MB → 14.7 MB with no visible loss. SVG **`scaleX` scales about user-space origin** → the arc collapsed to the left; fix with `svgOrigin`. Local voice = **Kokoro venv at `C:/Users/fight/.venvs/kokoro`** (`am_michael` male / `af_heart` female); narration must be per-line loudness-normalized (`loudnorm` under-corrects short clips). System Chrome is broken on this box → use Hyperframes' managed headless shell. Verify pacing (static-hold), mix separation, voice presence (cross-correlation r), and encode size *on the delivered file*.
 - **Prop 39 political explainer video (2026-10-15, in progress).** Project `C:\video\prop39` (Remotion, from `video-stack\template`). Single source of truth = `C:\video\STACK.md` (= `Video Stack/Full Stack Spec.md` in vault) — it wins over any older doc. 9-scene / 97.3s build, music beds A/B/C × landscape + vertical. Voice = Qwen3-TTS "Prop 38 Voice B" (consented human ref `C:\tts\voices\user_announcer_ref.wav`). Music = ACE-Step 1.5 (`C:\Users\fight\Projects\ACE-Step-1.5`, isolated py3.12, CUDA 12.8, gradio :7860), 93s instrumental beds time-stretched (atempo) to the voice tail. Loudness spec bar = **−16 LUFS ±1, TP ≤ −1.5 dBTP**, AAC 192k 48kHz; drafts were mixed ≈ −18.6 LUFS (~2 LU under — reconcile before final master). QA stack: ffprobe + ebur128 + Whisper ASR diff + contact-sheet vision. One open item blocking final = exact "Paid for by" committee name (placeholder "SPONSOR DISCLOSURE PENDING · DRAFT ONLY"). Workflow = serial: baseline Bed A landscape, one fix per pass. Two pending Tony calls: stop 2nd model LFM2.5-2.6B on :1920 (shares 3060 12GB w/ Qwen)? fix local `C:\llama\restore_llama_servers.bat` to start Qwen only?
 - **Provider fallback incident (2026-10-12):** `deepseek/deepseek-v4-flash-0731` (routeapi) went unavailable on billing/quota; role profiles silently failed over to Qwen on the brother-5090 rig for ~18 min. Check the profiles' actual model on health checks.
@@ -66,16 +64,11 @@

 ## 🧵 Open Threads

- Trace-fix (builder/reviewer `approvals.mode: smart` + guardrails + timeout 300) written, unapplied — awaiting Tony's approval. See [[../04_projects/trace-review-bot/2026-10-10-trace-analysis-and-fix]].
- killcorpus eval **GONE from disk (2026-10-15)**: repo `C:\Users\fight\Projects\killcorpus` no longer exists; no eval process alive. Only `04_projects/killcorpus` Obsidian notes remain. Supervisor `1da28c73cd5f` + health `c7ea39ffb05a` are orphaned and will keep alerting. **Tony's call:** retire both crons / repoint to a new path / restore from the Gitea Contents mirror. No restart taken (HARD RULE held — absence was never positively confirmed by the process check, which returned empty/withheld).
- killcorpus **terminal path READY (2026-10-12)** — the loop will not idle at N=967. Autopsy template + drift-proof validator + 3 synthetic dry-runs + hand-off simulation all done and signed; claim 002 (maker) spec PASS, harness machinery built (live feed NOT wired — held pending explicit green-light); `seeded-basket` blocked on its text.
- killcorpus **open items**: git-level link (`origin`) held — decide at first autopsy or sooner; maker live-feed wiring held for green-light; superseded handoff docs were **deleted 2026-10-12** (`docs/` now = `killcorpus-status.md` + `operating-manual.md`).
+- Trace-fix **APPLIED 2026-10-17** (builder + reviewer): `approvals.single_query_mode: approve` is what actually unblocks `-q` — `mode: smart` alone was proven insufficient; plus `hard_stop_enabled: true` and `terminal.timeout: 300`. Verified live on both profiles. Configs backed up as `config.yaml.bak-20261017`. See [[../04_projects/trace-review-bot/2026-10-10-trace-analysis-and-fix]] §6.
 - Dream Mode live as of 2026-10-10 (skill + `skill_review.py` + 2 AM cron + `dream/`). Note for 10-12 = third run.
 - **OpenCode + DeepSeek — PENDING Tony (opened 2026-10-13 19:16).** Needs: (a) which DeepSeek as default — `v4.1-flash` (matches Hermes default), `v4-pro`, `r1`, or all three with none set; (b) go / key-only / show-diff-first. Exact diff is recorded under 🛠️ Technical Notes. No writes made.
- **killcorpus "ready for capital" gate — offered 2026-10-13, unanswered.** Draft a formal in-repo gate spec (doc only: K1–K5 at pre-registered N → matched-lag clean → replication on a second regime + sample → live-fill-validated execution path with verified fee schedule → risk limits + kill-switch → capped live tranche with pre-registered stop)? Or keep the corpus paper-only with no written gate?
- **killcorpus minor open item:** `equity` + `stats` tables declared but never written (variance logged textually). Fix at a natural gap vs after N=967 — Tony's call.
- **Search OS Phase 5 authenticity gap (2026-10-14):** the `example.com`/`test` report's Reddit/Quora drafts use unsupported first-person resident/expert personas despite placeholder factual fields. No publishing is evidenced. Add a source-and-authorization gate before drafts are treated as publishable.
- **Sorter cron gap (open ≥2 reports):** the daily Sorter triage reads `00_system/user-profile.md`, which does not exist (vault root is `C:\Users\fight\Documents\Obsidian Vault`). Create the file or repoint the skill.
+- **Search OS authenticity gap — FIXED (2026-10-17).** `search_os.py` now runs every draft through `apply_authenticity_gate`: first-party personas (`business_owner`, `brand`) are publishable; third-party personas (`local_resident`, `industry_expert`) are blocked unless a real person is recorded in `search_os/search_os_authorizations.json`. Blocked drafts render with ⛔ + reason, and the publishing queue reports the state per draft. Verified: 2/4 publishable on the `example.com` fixture, and an authorization record flips a blocked draft to publishable. (Same lesson as the crowd-sourced review problem: a first-person claim needs a person.)
+- **Sorter cron gap — FIXED (2026-10-17).** The `{{meta}}` role token in `Meta/vault-map.md` pointed at `00_system`, but every crew file the agents read (`user-profile.md`, `vault-structure.md`, `tag-taxonomy.md`, `states/`, `health-reports/`) lives in `Meta/`. Repointed the token to `Meta`; verified with a live Sorter run (`TOKEN=Meta`, `NAME=Tony`).
 - **Duplicate skill:** `test-driven-development` exists twice at similarity 1.00 (`software-development/` and `software-development/agent-skills/`). Proposed for consolidation; not merged unattended.
 - **Webhook sessions are tool-restricted (2026-10-16):** no terminal, no file I/O, no private-network web access. Inbound bridge messages that require local action (Gitea post, file read, shell) will fail in a webhook context. Transport verification (receipt) works; action verification does not. Fix: route action-requiring messages to a full-tool session.
 - **AgentOS git mailbox (`C:\Users\fight\AgentOS\agent-comms`):** 8 stale outbox messages (0001–0008, research-loop era) remain `status: pending`. Grok Bot bridge test (2026-10-16) confirmed receipt path works; Gitea comment post was never completed (tool gap, not transport failure).