119 tickets this week

contradiction · Accountability gap · 3 edges

contradiction · Agent health · 2 edges

contradiction · Agent health monitoring · 2 edges

contradiction · AI fluency

contradiction · Automation pipeline

contradiction · Automation reliability · 2 edges

contradiction · Automation routines · 2 edges

contradiction · Benchmarking artifact · 4 edges

contradiction · Boundary object theory

contradiction · Comprehension audit

contradiction · Context compounding · 2 edges

contradiction · Context management as a bottleneck · 3 edges

contradiction · Control architecture as evangelism

contradiction · Cost capped agentic workflows · 3 edges

contradiction · Craft in product design

contradiction · Creative studio workflows

contradiction · Credential rotency vs infrastructure stability

contradiction · Cross domain bridging · 2 edges

contradiction · Decentralized ecosystem invariant

contradiction · Deep work

eval failed: vs-017

discovery review-sites collector under-yields (Phase-4 follow-up, LOW): the live 2026-06-21 standard+deep runs both returned only 3 review records. Root cause is Brave collapsing the OR'd multi-`site:` query in `_review_query` ([tools/llm-council/council/discovery/gather/reviews.py](tools/llm-council/council/discovery/gather/reviews.py)) — Brave treats `site:` as a single filter hint, not a Boolean. Records that DO return are real + gate-valid (correctness fine); this is yield tuning only. Fix when convenient: fan out to N single-`site:` queries (one per REVIEW_DOMAIN) instead of one OR'd query, or feed query-expansion. Surfaced by the Phase-4 final whole-branch review (M2).

✅ CORRECTED 2026-06-21 (close-out) — STALE TICKET, NOT a HIGH blocker: the bug is already fixed (Phase 3 shipped `_decode_payload` SSE-strip + `FusionError.cost` + failure-path `record_spend`) AND validated documented-correct by OpenRouter research (`: OPENROUTER PROCESSING` is a documented SSE keep-alive comment; ignoring `:`-prefixed lines is the spec-correct handling `_strip_sse_padding` already does). The "two runs failed" were Phase-2, pre-fix. Residual is confidence only (a few live runs incl. deep). See council/docs/2026-06-21-fusion-discovery-council-phase5-field-report.md §7a. ORIGINAL (stale) — discovery Fusion response robustness (Phase-3, HIGH — live discovery intermittently fails today): two live `quick`-tier e2e runs on 2026-06-20 both failed at the Fusion parse step — run 1 `FusionError` "did not return parseable", run 2 bare `JSONDecodeError: Expecting value: line 181 column 1 (char 990)`. Root cause: OpenRouter streams `: OPENROUTER PROCESSING` SSE keep-alive comment lines as padding on slow Fusion calls (panel + web tool calls), so `fuse()`'s unguarded `payload = resp.json()` in [tools/llm-council/council/discovery/fusion.py](tools/llm-council/council/discovery/fusion.py) chokes on the non-JSON prefix. Intermittent (Phase 1 run #2 succeeded when fast). Fix: strip leading `: ` comment lines / extract the first balanced `{…}` before json.loads, harden `_parse`. ALSO: failed Fusion calls bill OpenRouter but record $0 locally (`record_spend` is post-success only in [__main__.py](tools/llm-council/council/discovery/__main__.py)) — record usage.cost on failure too. Full write-up: council/docs/2026-06-20-fusion-discovery-council-phase2-field-report.md §5/§6.

✅ RESOLVED 2026-06-21 (close-out, commit 85b1a63) — fixed durably in our repo: `gather/last30.py`'s `_last30_env()` forces `INCLUDE_SOURCES=reddit,hackernews` (keyless) in the subprocess env, which wins in the plugin's `os.environ`-first loader. Live-verified: crash gone, reddit yields records. (HN errored under `--no-native-web` — degrades safely; LOW follow-up below.) ORIGINAL — discovery last30 live-blocked by upstream plugin bug: `~/.claude/plugins/marketplaces/last30days-skill/scripts/last30days.py` crashes before emitting JSON — `config.get('INCLUDE_SOURCES', '').split(',')` raises `AttributeError: 'NoneType' object has no attribute 'split'` because `INCLUDE_SOURCES` is set to an explicit null. Our fusion-discovery-council collector ([tools/llm-council/council/discovery/gather/last30.py](tools/llm-council/council/discovery/gather/last30.py)) degrades safely to `[]`, so the pipeline never crashes, but last30 contributes zero live evidence until fixed. Fix is config/upstream: set a non-null `INCLUDE_SOURCES` in `~/.config/last30days/.env` (e.g. `reddit,hackernews`) or patch/report the plugin. Surfaced during fusion-discovery-council Phase 2 (see council/docs/2026-06-20-fusion-discovery-council-phase2-field-report.md §4).

llm-council transcript render crashes when any council model returns null content: `_render_markdown` appends `r["content"]` (None) to `lines`, so `"\n".join(lines)` raises `TypeError: sequence item N: expected str instance, NoneType found` and the whole transcript fails to write even though the run + spend succeeded (hit 2026-06-16 on the 16BitFit 4Q run, gemini-pro returned null; recovered by reconstructing the .md from the session JSON archive). One-line fix at [tools/llm-council/council/cli.py](tools/llm-council/council/cli.py) line 40: change `lines.append(r["content"])` to `lines.append(r["content"] or "_(no response: model returned null)_")`. Optional follow-on: guard chairman content (line 52) + ranking reasoning (line 47) the same way.

voice-pass program COMPLETE 2026-06-11 (Cowork): the LinkedIn drafts, Loom scripts, pinned-repo READMEs, and the 5 highest-traffic 4Q EXPLANATIONs referenced by the publishing tickets below (vault-knowledge Loom+LinkedIn, judge Steps 8-9, MCP security, Discovery PRD, Control Architecture, AP Agent Spec) are all drafted and run through writing-voice-modes → writing-critique → writing-humanity-pass at recruiter dials. Paste-ready before→after docs in job-hunt-2026-roadmap/2026-06-11-{linkedin-posts,loom-scripts,readmes,explanations}-voice-final.md + the sequenced publish-sprint playbook 2026-06-11-publish-sprint-playbook.md. REMAINING is execution-only (commit / record / post — Sean checks off as he goes) plus 6 more EXPLANATIONs queued (System Card, Data Readiness, Vault Scorecard, Phase D, Phase 6, vault-synth eval) and reconciling the duplicate Phase-D / knowledge-loop 4Q files. Next-priority menu in 2026-06-11-continuation-prompt.md

substack-post-6: build the Agent-or-Automation Advisor MCP (sibling to intent-engineering; `advise_task` + `audit_fleet`; deterministic rubric + pass^k reliability engine; local/no-key; npm + registry under `com.seanwinslow/*`). Spec ready: `[redacted]`. Build in a fresh Claude Code session (a weekend) before drafting Post 6 (due Thu 6/25)

substack-post-6 proof: run `audit_fleet` on the real 14-agent fleet, capture the results table (= the post's self-dogfood proof + the relead opening)

recruiter-cleanup: delete the pre-rewrite mirror backup `~/code-brain-backup-2026-06-10.git` (holds ALL scrubbed private history) + `/tmp/code-brain-restore` + `~/code-brain-scrub-paths*.txt` once confident in the rewrite (suggest after 1-2 weeks of clean operation)

recruiter-cleanup: file GitHub Support ticket to purge unreachable objects (old commits remain SHA-fetchable server-side until GC); flip repo public only after Support confirms or after accepting the residual-while-private risk

fleet privacy filter: nightly synthesizer/flush still write job-hunt-derived concepts into the PUBLIC [redacted] + tickets.md over time — add a privacy-aware exclusion (route career/personal-derived concepts to [redacted]) or schedule a periodic prune pass

fleet venv durable fix: the 2026-06-10 13:31 Homebrew python@3.13 reinstall (3.13.11→3.13.13_1) changed the interpreter cdhash, which invalidated launchd's cached LWCR for 5 jobs (daily-morning, meta-agent, vault-indexer, vault-synthesizer, deep-researcher) — every fire on 2026-06-11 was kernel-killed with OS_REASON_CODESIGNING (no daily note, no overnight knowledge loop). Recovered manually 2026-06-11 09:15 via `launchctl bootout`+`bootstrap` of the 5 jobs (binary itself was valid on disk; only launchd's cache was stale). RECURS on every `brew upgrade python@3.13`. Durable fix still open: either (a) uv-managed pinned interpreter under the repo so brew can't move the binary, or (b) a post-`brew upgrade` hook that re-bootstraps the com.sean.agent.* jobs

recruiter-cleanup deferred polish: docs/ top level still has loose dirs (NotebookLM Synthesis Cleanup, Design-Enhancement-Docs, Additional Skills…); consider folding into docs/ subtaxonomy in a later pass

enterprise-ap-agent-spec: repo public + `/transactions/enterprise-ap-agent-spec/` route LIVE (branch merged 2026-06-08). Last open item from the Task 26 gate: ≥1 substantive LinkedIn comment from an enterprise AI PM (post ~5–7 days pre-ship)

Substack series "Make It Sound Like Me" (working name): rewrite the post-1 draft (the-confident-stranger) against the 2026-06-05 upgraded skill — new Pi-anchored thesis ("there are many Claudes; this one writes like me" / the humbling that you can't one-shot your own brain into an LLM), grittier title, dial Sedaris way down, references rationed

Substack value engine: build the reader-facing tool — ship a Cheese-Gauntlet + reference-universe-interview prompt kit (copy-paste, Nate-style) with post 1 [DONE — kit shipped]; design the full "interview-the-reader → emit their personal voice-mode SKILL.md" Cowork plugin as a later flagship post [SPEC DELIVERED 2026-06-07: job-hunt-2026-roadmap/2026-06-07-voiceprint-plugin-build-spec.md, working name VoicePrint, MVP ~4-6 sessions; 4 open decisions: name / MVP boundary / bundle-the-chain / public-vs-dogfood-first; BUILD not started pending Sean's go]

Substack: lock series name (candidates: "Make It Sound Like Me", "This One's Mine", "Writing With Taste", "Raising Claude") + per-post title convention (blunt/bodily over clever)

writing-voice-modes: send MORE raw stories to deepen the Raw Stories grit anchor in voice-samples.md (the more full pre-AI narratives, the better the register holds)

writing-voice-modes: evaluate Bukowski as a sixth author influence (beauty-in-squalor register, distinct from Thompson's mania) — stated influence in his own NBAGT script ("The Laughing Heart" recited as thesis); evidence in script-mining report §10.1

writing-humanity-pass: add an over-polish guard — Sean's looser constructions are voice data (typos/run-ons consistent across 7 years of scripts + raw interviews); the pass should fix rhythm and word choice, never sand the looseness (script-mining report §10.8)

writing-voice-modes: re-run the eval baseline (evals.yaml) after the 2026-06-04 WHAT-layer + script-corpus integration — current scores pre-date reference-universe.md, cheese-bank.md, and the 9 new/promoted moves

writing-voice-modes: close remaining elicitation gaps — games beyond Smash (R2-3), NY sports beyond Giants (R4-3), D-series text-register samples; plus watch-list promotions needing instances: Rhetorical Catechism (1 more prose instance), Post-Chaos Inventory Shot (1 more)

vault-critic AG hang — network theory REFUTED by 6/04 probe; hang is INSIDE gemini's request path, not the network. The 6/04 03:30 run fired the IP-family probe AT the 120s-timeout moment: BOTH Google hosts (cloudcode-pa + play.googleapis) connected in ~15-26ms on IPv4 AND IPv6, and the api.openai.com control connected too — i.e. the network was fully up while gemini's authenticated model request hung to 120s and returned 0 tokens. The 6/03 play.googleapis.com connect-timeouts were a red herring (telemetry endpoint, intermittent; the actual model host cloudcode-pa was reachable). So eliminated now: MCP, OAuth-refresh, machine-asleep, AND raw network reachability. What remains is the authenticated Code Assist streaming call silently hanging (server-side throttle-as-hang on the preview model, or a CLI stream bug) — but note: curl-reachable ≠ authed-call-works, and the CLI swallows the real error, so further --debug captures won't reveal more. RECOMMENDATION: stop chasing the gemini hang — the circuit breaker now contains it ($0 impact) and the June-18 oauth EOL obsoletes the whole path. Collapse this into the migration decision below

vault-critic AG — DECISION (6/04, Sean): Codex-only for now (`antigravity_enabled = false` shipped); no Gemini API spend. POST-JUNE-18 TASK: re-enable AG via the Antigravity CLI (uses the paid Google-One subscription, NOT the metered API) and A/B test whether the second opinion is worth keeping — flip `antigravity_enabled = true` (or run once with `--antigravity`), watch a few nightlies, compare expansion quality vs Codex-only + duration. If the Antigravity CLI hits the same silent hang, add a hard <120s stream timeout or drop AG for good. gemini-cli oauth-personal EOL is 6/18 (flag 45740200) — don't test the old gemini-cli path after that, go straight to Antigravity CLI

vault-critic budget waste — RESOLVED + VERIFIED on the 6/04 nightly. AG circuit-breaker tripped after 1 failure exactly as designed: manifest shows antigravity_calls=1, antigravity_skipped=7, codex_calls=8, articles=3 fresh + 5 backfill = 8 (was 5 on 6/03), codex_tokens=260K (was 145K), duration=323s (was 610s). Throughput +60%, budget headroom restored. With ~277s spare now, could raise backfill_max_per_run (currently 5) to drain the orphan backlog faster. Raise threshold to 2 (or 0=off) once AG is healthy/migrated

Remove `VAULT_CRITIC_AG_DEBUG=1` from com.sean.agent.vault-critic.plist (and the run-once connectivity probe is gated behind it) once the 6/04 probe evidence pins the sub-cause — it appends gemini --debug noise + a ~10s probe to every nightly AG timeout

Obsidian-Git stale `.git/index.lock` recurs (fixed 5/31 and 6/03) — root cause is git commit crashing mid-write when Modern Standby cuts power during the 60-min auto-commit cycle. Permanent fix instead of repeated manual `rm .git/index.lock`: either widen the commit interval, gate commits on machine-awake, or add a pre-commit stale-lock sweep that only deletes a >5-min-old EMPTY index.lock with no live git process

Re-add fleet-memory to daily_driver via cheap read-only inject (drop MCP bridge + context-management beta that doubled cost to $0.97 and tripped the cap 5/29); reuse inject_memories_into_prompt() like vault_synthesizer

Build a $0/run local summarizer (gemma4:e4b / qwen3 on Mac Mini) that curates daily_driver's fleet-memory namespace, so the Opus agent only reads, never writes

Wire SDK fleet agents to surface/read open tickets from tickets.md (mirror the interactive session-start-inject-tickets.sh hook) — GATE: only do this once agents have real tasks beyond vault upkeep (e.g. substack-drafter); the current vault-upkeep loop agents don't need it

Build a $0/run local critic-synthesizer (gemma4:e4b / qwen3 on Mac Mini) that reads the nightly critic-manifest-{date}.json after the 03:30 run, ranks+dedupes vault_critic suggestions, and writes a top-N shortlist to a SEPARATE suggestions lane (NOT the hand-curated Manual Todo) for Sean to review and promote — propose-don't-auto-promote, human-in-the-loop — GATE: only build after ~2 weeks of clean vault_critic nightly runs (recent runs show status=partial / ag_fail=5; don't triage noise)

vault-knowledge-mcp launch comms: record the 90-sec Loom from docs/LOOM-SCRIPT.md (all 3 tools, lead on find_contradictions), drop npm + GitHub links into the LinkedIn first-comment, then post docs/LINKEDIN-DRAFT.md tagging Anthropic

Task 12 judge layer Steps 8-9 (Sean-host): run the full pytest suite + validate.py per 2026-05-31-task-12-day-6-handoff.md; record the 90-sec --demo-injection Loom; post the LinkedIn draft tagging Anthropic + FDE-Boston JD; commit + tag judge-layer-v0.1.0 (paste-ready CHANGELOG block in the handoff doc)

Task 12 judge layer: add the /transactions/judge-layer ledger row in sw-ai-pm-portfolio (surface: control-plane) — GATE: Gap-Fill 3 personal-site deploy must land first so the page resolves

Task 25 LDR Grounding-Collapse: create the standalone repo from the 5 staged scratchpad files (mkdir ~/Code-Brain/ldr-grounding-collapse, copy README.md + the-failure.md + the-diagnosis.md + the-fix.md + eval-case.yaml, git init, gh repo create --public, push) — the standalone path isn't a mounted folder so it must be created host-side

Task 25 LDR Grounding-Collapse: run writing-voice-modes on substack-drafts/2026-05-29-ldr-grounding-collapse.md, then publish Substack Post 1 (gates Posts 2-3 + the Task 13 manifesto + the Looms); confirm npm run build in sw-ai-pm-portfolio resolves /transactions/ldr-grounding-collapse/; swap the repo URL placeholder → live in both the Substack draft and the ledger row once pushed

meta-agent monitoring blind spot: it reported "all healthy" through the vault_critic Anti-Gravity 5/5 nightly failures (5/26→6/1) because critic status=partial is treated as tolerable. Add an alert when a CLI's failures == calls (100% failure) OR tokens_total==0 with calls>0, even if overall status is partial — so a fully-dead sub-CLI surfaces. Now that the manifest carries antigravity_last_error/codex_last_error, surface that text in the alert

job-feed: add the web3.career API token to Keychain so the web3career feed adapter stops returning [] (`python3 agents-sdk/lib/keychain.py set web3career_token <token>`; free token from web3.career/api). Keychain secret — Sean-only. (Split out 2026-06-18 from the now-resolved ATS-watchlist-decay ticket; see Done.)

Task 23 MCP Security Audit (v0.1.1 already published to npm + registry): run npm run build in sw-ai-pm-portfolio to confirm /transactions/mcp-security-audit/ resolves, then commit the new mcp-security-audit.mdx ledger row; post sw-mcp-intent-engineering/docs/LINKEDIN-DRAFT.md (links in first comment, tag Anthropic) and optionally commit that draft file

vault-critic AG hang — read tomorrow's 03:30 capture: check [redacted]*.log + critic-manifest-2026-06-03.json for 429/RESOURCE_EXHAUSTED/Quota/"Request cancelled." If confirmed (high-confidence hypothesis: gemini-cli #22648 swallows a preview-model 429 at the 00:30-Pacific quota-reset boundary), migrate the nightly off oauth-personal to GEMINI_API_KEY (also forced by oauth-personal-via-gemini-cli EOL 2026-06-18), then REMOVE the temporary VAULT_CRITIC_AG_DEBUG=1 from schedules/com.sean.agent.vault-critic.plist + reload. Context: agents-sdk/CONTINUATION-2026-06-02-vault-critic-antigravity.md Session 3

daily-driver morning cost cap breach: 2026-06-02 run cost $0.6848 vs $0.60 cap (second breach after 5/29 hit $0.97) yet meta-agent reported "healthy". Either raise the cap deliberately or investigate the overrun; also fold cost>cap into the meta-agent alert blind-spot ticket

Task 24 Discovery PRD (content-complete + council-revised; ledger row validated clean via scripts/validate_content.mjs): run `npm run build` in sw-ai-pm-portfolio to confirm /transactions/discovery-prd-content-workflow/ resolves, then commit the new discovery-prd-content-workflow.mdx (surface: product) by hand; optional LinkedIn teaser on the cross-functional-translation angle

Add the writing-humanity-pass skill to an export-group manifest (export-groups/*/playground.json) + a preset if it should ship via the installer; until then it is correctly listed in README as not-in-any-group

Re-verify sean-anchor + claude-mascot Bibles' Pass-3 on a PINNED model — the 2026-06-02 provenance forensics found both were verified by the Antigravity backend-default gemini-3.5-flash (agy `-p` with no `-m`), NOT the "Gemini 3.1 Pro" their docs claimed. Cy's Pass-3 now routes through the Gemini API transport (gemini-3.5-flash, pinned by ID, served model read back from resp.model_version) per the A2 hardening PR; this ticket is the COSTED re-run of the two locked Bibles on that pinned path, scheduled AFTER the hardening PR merges. Decide Flash-as-shipped vs a deliberate gemini-3.1-pro upgrade (re-baseline whichever is chosen). See docs/2026-06-02-em-provenance-and-hardening-kickoff.md §A4

ESCALATION (2026-06-03, B1b DINOv2 spike): this is BIGGER than "Flash-verified." sean-anchor's BODY turnarounds are proportion-OFF — head reads ~1:5.3 (profile-right), ~1:4.6 (back), ~1:4-4.5 (walk-cycle) instead of the 1:7 target — and were baked into the LOCKED Bible anyway because the Pass-2.5 similarity gate is record-only (it never measured proportion). So a re-verify on a pinned model isn't enough; the body plates need a proportion re-bake to clean 1:7, then re-lock. Evidence: anima PR #20 + evals/vision_critic/traces/dinov2-separation-2026-06-03.md.

SUB-ITEM (gates on the re-bake): the Em vision_critic eval fixtures are contaminated — the proportion-defect fixtures (evals/vision_critic/fixtures/frames/defect_body_*.png) are SHA-identical to the drifted Bible plates (verified byte-for-byte, 2026-06-03). Once the Bible body plates are re-baked clean, those fixtures must be RE-DERIVED (or the eval is testing against drifted ground truth), and the cases.yaml labels RE-RATIFIED against the clean fixtures (Sean's call — locked-label rule).

Publish "Raising Claude" post 1 (You Can't Prompt Taste Into a Machine): (1) create a public GitHub gist from substack-drafts/raising-claude-cheese-gauntlet-kit-PUBLIC.md; (2) swap the gist URL into the canonical post (substack-drafts/2026-06-05-raising-claude-post1.md — placeholder `https://gist.github.com/REPLACE-WITH-YOUR-GIST-URL`); (3) paste post into Substack — Title field = "You Can't Prompt Taste Into a Machine", Subtitle = "Raising Claude · Post 1"; (4) after publish, swap the live Substack post URL back into the gist's backlink (placeholder `https://REPLACE-WITH-YOUR-SUBSTACK-POST-URL`)

writing-voice-modes eval re-baseline — RUN ON YOUR MAC (prep DONE 2026-06-06; harness can't run in Cowork). Generation now routes through your Claude SUBSCRIPTION via the Agent SDK (OAuth), NOT the Anthropic API key — _SubscriptionClient passes env={} (never the key) and warns if one is set. Prereqs: `claude login` valid, NO ANTHROPIC_API_KEY in env (unset it to be safe), Mac Mini Ollama up at localhost:5050 with qwen3-14b-research. Steps already done by Claude: stylometry baseline rebuilt (em-dash 1.41→0.08, de-contaminated) + threshold recomputed offline (=9.64, reuse-existing, zero API). FIRST RUN FAILED 2026-06-07 (SDK exit-1, swallowed) — root-caused to the invalid model string `claude-opus-4-7`; FIXED 2026-06-07 (switched to the `opus`/`sonnet` Agent SDK aliases, dropped empty-valued `--setting-sources=`/`--tools` flags, wired the stderr callback so any next failure prints `[claude-cli] ...`). RE-RUN now on the Mac: `cd agents-sdk && PYTHONPATH=. .venv/bin/python -m agents.skill_optimizer --score-only` (5 train + 2 holdout × 15 = 105 Opus gens via subscription + local Qwen judge; writes a score-only-<date> row). SECOND RUN ALSO FAILED 2026-06-07 (same generic exit-1; stderr callback produced NO output, so the CLI started, accepted the query, and failed mid-run reporting a generic error over the control channel — not the model alias). Can't diagnose remotely (SDK hides it). DIAGNOSTIC LADDER on the Mac: (1) `claude --version` then `claude --print "say hello in five words"` then `claude --print --model opus "say hello in five words"` — isolates CLI/auth/model from our SDK usage; (2) a `--debug` flag was added 2026-06-07: `PYTHONPATH=. .venv/bin/python -m agents.skill_optimizer --score-only --debug 2>&1 | grep '\[claude-cli\]' | head -40` surfaces the CLI's real error. Interpret: `--print` fails -> auth (`claude login`) or CLI broken; `--print` works but `--model opus` fails -> model access on plan (try `--model sonnet` or a full ID in config.toml generator_model); both bare work but SDK fails -> our option set, paste the [claude-cli] debug lines. Paste whichever output back. DELEGATED 2026-06-07 to Claude Code (it has the SDK/CLI/OAuth/Ollama locally): handoff prompt at job-hunt-2026-roadmap/2026-06-07-claude-code-eval-fix-prompt.md — instructs it to diagnose from real output, fix forward (incl. a `claude --print` CLI-subprocess transport as an allowed subscription-billed fallback), run --score-only to completion, and report vs 0.7267. Hard constraint repeated: subscription/OAuth only, never an API key. Compare train_score to the 2026-05-10 baseline 0.7267 — but read it knowing the eval is blunt (see next ticket). If you ever re-run the FULL calibration with fresh AI samples, that path still needs an API key (`calibrate_stylometry_threshold.py` without --reuse-existing) — prefer `--reuse-existing` to stay key-free

writing-voice-modes eval is TOO BLUNT to detect the grit/90-10 overhaul: `sounds_like_sean` was pinned at 1.00 in the only prior run, so the criterion that should register a voice improvement has no headroom; the criteria with headroom are format-mechanics + the (now-fixed) stylometry signal. Redesign the eval to discriminate: make sounds_like_sean harder (graded/sub-checks), add a cheese-bank NEGATIVE criterion (reject MEANING_OVER_ACCESS-register output), add a grit-register check. Until then a re-baseline number won't tell you if the overhaul worked

writing-voice-modes stylometry: the em-dash density feature is now a DEAD feature post-ban (≈0 in both corpus and compliant output); harmless (zero-stdev → guard sets std=1.0 → contributes 0) but consider dropping it from FEATURE_KEYS and re-tuning, so the 4 live features carry the signal

writing-voice-modes skill_optimizer: cost_usd is logged as 0.0000 even on real Opus runs (results.tsv iteration 1 had real scores + duration 6303s but $0) — wire actual token-based cost from msg.usage so the $50 soft / $200 hard caps in config.toml actually engage

Task 14 Control Architecture (BUILD COMPLETE 2026-06-07; in-session verification green): host close-outs — (1) run the LIVE demo `cd tools/governance-demo && PUSHOVER_USER_KEY=… PUSHOVER_API_TOKEN=… python3 replay_budget_breach.py --fixture over_budget` to fire a real Pushover ping + confirm exit 7 (sandbox can't page); (2) record the 90-sec Loom (split-pane: the over_budget run + `tail -f` the demo ledger + phone showing the push); (3) post the LinkedIn draft tagging the Anthropic FDE Boston JD; (4) commit code-brain by hand (`agents-sdk/docs/CONTROL_ARCHITECTURE.md` + `agents-sdk/docs/EXPLANATION.md` + `agents-sdk/config/authority.example.yaml` + `tools/governance-demo/` + CHANGELOG/CLAUDE/README; suggested: `feat(docs): ship control-architecture trinity reframe — authority + recovery + audit (Council Gap-Fill 4)`) and the portfolio `control-architecture.mdx` (`content(transactions): add control-architecture ledger row, surface infra`)

Task 14 Council: DONE 2026-06-07 (premium, $0.4856; transcript `agents-sdk/docs/critiques/control-architecture-council-2026-06-07.md`). Convergent fixes folded into CONTROL_ARCHITECTURE.md. ONE open decision for Sean: the council (Gemini + chairman) advised dropping the internal "Task 7 STOP-DOING" label from the routing paragraph as fourth-wall-breaking; I rephrased it to a generic "deliberate, standing decision" to honor BOTH the council and your locked "explicit deferral" decision — if you want the verbatim "Task 7 STOP-DOING" link restored, say so. (Mermaid was KEPT per your locked decision despite the council's cut suggestion.)

Task 13 voice-pass-2 (applied 2026-06-07): commit the de-cheesed access-over-meaning across both repos — code-brain `docs/MEANING_OVER_ACCESS.md` (`docs(essay): voice-pass-2 on access-over-meaning — de-cheese + cut layoff + recruiter-dialed grit`) and portfolio `meaning-over-access.mdx` (live/PUBLISHED, so the commit is a deploy: `content(essay): sync access-over-meaning voice-pass-2; lastRevised 2026-06-07`). ALSO propagate the same voice-pass-2 into the Substack cross-post `substack-drafts/2026-06-19-meaning-over-access-substack-cross.md` (still carries the old cheese prose) before the ~6/19 publish

Task 26 AP-agent eval-suite hardening (when the suite grows past ~30 cases): add confusion-matrix output to run_evals.py — emit precision / recall / false-pass on the should-escalate class (not just per-case pass/fail), so the suite reports detection quality the way a real eval does. Files at job-hunt-2026-roadmap/task-26-ap-agent-build/ (move to the enterprise-ap-agent-spec repo when created)

Task 26 AP-agent eval-suite hardening: expand from 1 to 3-4 cases per class (happy / edge / adversarial / controller / precision) so a single stub change can't pass by coincidence; balance the classes and keep the bite + xfail markers. Pairs with the confusion-matrix ticket above

Task 26 Enterprise AP Agent Spec — Step 10 critique (sole remaining verification-gate item; repo + ledger live at github.com/seanwinslow28/enterprise-ap-agent-spec + /transactions/enterprise-ap-agent-spec). PREREQ DONE 2026-06-11 (Sean, via Claude Code): the ⏱ time-sensitive numbers (g5.12xlarge hourly rate + APQC $5.83 labor median in cost-model.md) re-pulled + the OpenAI vendor certs (HIPAA BAA + SAML/SCIM in build-vs-buy-memo.md) re-confirmed. REMAINING: run the hardened writing-voice-modes pass on the LinkedIn draft, then post tagging ~3 enterprise AI PMs ~5–7 days before any push to land ≥1 substantive comment

writing-voice-modes skill_optimizer score-only (2026-06-08): the new score-only row used a LOCAL `qwen3.5:27b` judge substitute because the canonical `qwen3-14b-research` judge (Mac Mini :5050) was asleep/unreachable — the 3 structural criteria are baseline-comparable but the 3 LLM-judge criteria are NOT. Re-run with `--judge-model qwen3-14b-research:latest --ollama-base-url http://localhost:5050` once the Mac Mini is back for a comparable LLM-judge number; AND capture that model's `/no_think` Modelfile into the repo (it lived only on the Mac Mini) so the judge is reproducible without that host

anima SF03 sean-anchor body-turnaround re-bake + re-lock — DECIDED 2026-06-08 (Sean): bundle with the next heads-tall character authoring, no standalone costed run. SF03 proportion gate now enforces 1:7 at Bible-lock going forward (merged #33); sean-anchor's locked body plates predate constrained generation so they read `indeterminate` (honest non-measurement, not off-proportion). Trigger: the next authoring session that already spins up the Approach-A feeder re-bakes the five body turnarounds born-1:7 + re-locks → converts `indeterminate` to a certified pass. Resolves the re-bake half of the line-48 escalation ticket; the Em fixture-contamination sub-item there is already closed by the 2026-06-03 eval-foundation reset (50→52 clean Flow-authored fixtures). Recorded in anima CLAUDE.md SF03 "Open:" note + docs/2026-06-08-em-eval-suite-completion-plan.md item #9

last30days X/Twitter broken by incomplete vendored dep — `.claude/skills/last30days/scripts/lib/vendor/bird-search/node_modules/@steipete/sweet-cookie/` shipped with only package.json+README+LICENSE; its `dist/` (the actual code) was never vendored, so every X search crashed with `ERR_MODULE_NOT_FOUND` regardless of auth. FROM_BROWSER=auto silently failed for the same reason. 2026-06-08 hotfix: pulled `dist/` from `npm pack @steipete/sweet-cookie@0.1.0` and dropped it into the vendored folder (verified — X returned 19 posts). FOLLOW-UPS: (1) [DONE 2026-06-08] ran `sync.sh` — dist/ propagated to ~/.claude / ~/.agents / ~/.codex, all 3 import-check OK + module resolves; (2) [MOOT] can't commit — `node_modules/` is gitignored in code-brain (.gitignore:40), so the fix is local-only and won't survive a fresh clone or `npm` clean; sync.sh re-propagates from the source copy, but the dist/ in the SOURCE copy is itself gitignored — so a fresh code-brain clone reintroduces the bug. PERMANENT FIX is upstream only; (3) [OPEN] report upstream to mvanhorn/last30days-skill — published skill vendors @steipete/sweet-cookie without its dist/ (external action, needs Sean). Also: AUTH_TOKEN/CT0 now persisted in ~/.config/last30days/.env (X session cookies, will expire)

VoicePrint: real-human dogfood before public launch — run 2-3 non-Sean people through the full pipeline per [`creative-studio/voiceprint/docs/dogfood-runbook.md`](creative-studio/voiceprint/docs/dogfood-runbook.md); confirm each bundle sounds like them (not a template), `/voiceprint-proof` lands `closer_to: reader`, and no bundle leaks another person's content. The in-session dogfood was a simulated persona (Priya). DECISION 2026-06-11: Sean shipped the public install with Post 2 AHEAD of this, so it is now a high-priority FAST-FOLLOW (run ASAP post-launch), not a pre-launch gate. RUN-LOCATION CAVEAT (2026-06-11): run the dogfood in a folder OUTSIDE ~/Code-Brain (no CLAUDE.md, no .claude/skills in the directory tree) — launching Claude Code inside Code-Brain loads Sean's canonical writing-voice-modes/cheese-bank/reference-universe skills into scope, which can contaminate the leakage test (a stranger's bundle looks right while quietly borrowing Sean's calibration). Only the plugin's de-Sean'd bundled skills should be in play

VoicePrint: ship as a `claude-plugins-community` GitHub marketplace repo (add `.claude-plugin/marketplace.json`) in addition to the `.plugin` file — the marketplace path (`/plugin marketplace add <repo>`) is how Claude Code users discover/install; the `.plugin` is only the Cowork rich-preview install. Per `market-read.md` §7 distribution

[SHIPPED 2026-06-15 · https://seanpwins.substack.com/p/i-built-a-machine-to-sound-like-you] VoicePrint: Post 2 launch (the "Raising Claude" flagship) — write the Substack post leading with the differentiation the research validated (reject-based gauntlet + works-with-no-corpus + honest hours-not-one-shot loop + local/free), NOT "interview" or "build a skill" (Grill Me + Skill Creator own those). Include a one-screen before/after demo (the format that wins per the research) + the copy-paste install command. Use the verbatim demand vocabulary ("AI slop", "taste", "sound like you") from `market-read.md` §5

VoicePrint: deferred add-ons from the build (plan-time decision, may revisit) — a `/voiceprint-status` quick text readout (lighter sibling of the dashboard) and any further "voice report card" surface beyond `/voiceprint-proof`. Not built; `/voiceprint-proof` + the dashboard cover the core proof need

anima Em (Tier 2) — view-correctness fix-rate 0.00: in the 2026-06-08 G6.9 Gate-3 baseline Em's declared-view-correction clauses cleared 0/6 on the no-regen label-side path (golden 3/6; all six classes discriminative, overall lift 0.667). The next constructive-axis improvement target. Investigate WHY her view diffs don't move the label-side re-critique (re-critique the same fixture under a corrected declared view); decide if fixable (tighten the view-diff content / view-rule grounding) or inherent to the no-regen path. Improvement work, not eval-completeness. Source: docs/anima-test-runs/2026-06-08-em-g6.9-gate3-fixrate.md §5

anima Em (Tier 3) — Gate-3 fuller 30×5 run: tighten the small-N bands from the 12×3 baseline (6 outcomes/class/arm, per-class stderr≈0.33; the per-class +2.0 lifts ride on tiny golden−null denominators, directional not precise). Same `patch_efficacy --arm both+null` machinery, `--sample 30 --rerolls 5`, ~$31.50 costed under fleet-ops. DEFER — the 12×3 already clears "axis measured + discriminative on all 6 classes"; only run when a specific per-class number needs defending

anima Em (Tier 3) — mascot eval corpus: Em is corpus-validated only on sean-anchor. Build a claude-mascot defect/clean corpus (the box-creature register) + Sean-ratify it so Em's verdict/citation/constructive axes are measured on the second character too. Fold in the cosmetic `_criteria_block` nit (the hardcoded `IR.sean.*` example shows for non-sean frames) during mascot validation. DEFER until mascot work

anima Em (Tier 3) — identity-mode corpus (hair/jaw/eye): coverage extension consciously deferred at G6 — add identity-drift sub-modes to the verdict corpus so SF02-style drift is measured at sub-mode granularity. DEFER

anima evals (horizon) — next-agent eval suite: Em is now the reference template for fully evaluating a fleet agent (verdict + citation + constructive, all measured/ratified). Next highest-leverage target per the eval handbook per-agent matrix (docs/research/2026-05-31-ai-evals-best-practices-and-anima-eval-strategy.md): Maya planner / Cy character-designer / Mo museum-writer / the T3 council. Horizon marker — scope only once Em's Tier 1 close-out lands

Substack folder reorg (2026-06-09): the substack-drafts/ folder was restructured into per-post folders (01–07) + _ideas/_archive/_experiments/_assets + a README index that is now the single source of truth (series, dated queue, status legend, image+tool maps, conventions). Queue runs 2–3×/week Mon/Thu: Post 2 (Thu 6/11) → Post 6 (Mon 6/15) → evals bonus (Thu 6/18) → Post 3 (Mon 6/22) → Post 4 (Thu 6/25) → Post 5 (Mon 6/29) → Post 7 capstone (Thu 7/2). See substack-drafts/README.md

Substack hero images — GENERATE the 5 missing heroes (Posts 1, 2, 4, 5, 6; Posts 3/7/bonus already have one). Priority: Post 2 by Thu 6/11. Use gemini-image-gen / gemini-pencil-animation-image-gen with the refs in substack-drafts/_assets/references/; house style = cheesy-caption + grotesquely-detailed-image satire (cheese-bank format). Drop each into its post's images/hero.png

Substack tools — build the 3 missing ships-with tools in report build-order: (1) Agent-or-Automation Advisor for Post 6 (cheapest, a weekend, loudest hook); (2) Intent Card brief-mode tools on intent-engineering MCP for Post 3 (audit_brief/scaffold_brief/assess_brief_readiness); (3) On-Brand Gate for Posts 4+5 (generalize writing-critique → pass/fail + violated clauses + slop-risk). Each unblocks its post's publish date

Substack Post 6 hook pivot: the 06-stop-building-agents/post.md body is still the LDR "Day My Research Agent Invented Microsoft" draft (labeled Post 1 in stale frontmatter — now Post 6). Reframe the open around the agent-vs-automation hook ("automations with LLM nodes," 1,556 upvotes) so it ships with the Advisor, then run the voice chain. Note: the existing line-38 ticket calling this "Post 1" is superseded by this reorg

Substack drafts to write: Posts 3, 4, 5 (scaffolds with pain-point + ships_with + raw-material pointers are in each folder's post.md). Post 3 is draftable now (MCP already shipped); Posts 4/5 are tool-gated on the On-Brand Gate. All three need the voice chain before publish

Substack cleanup: delete 4 empty legacy dirs left in substack-drafts/ (images/, archive/, experiments/, substack-image-generation-references/) — the Cowork session couldn't remove them (sandbox EPERM); they're empty so git won't commit them, but tidy them in Finder

Substack image house style v2 (2026-06-10): replaced the deprecated Steadman/voice-mode image design with the pencil-test portfolio look (cream paper, graphite, ONE accent color, blob-baby characters + amber thread, minimal watercolor bloom behind the linework). Spec: docs/substack-image-generation-design-2026-05-23.md (v2). Drop the 3 ChatGPT portfolio illustrations (desk-kid, spear-warrior, trader) into substack-drafts/_assets/style-anchors/ on the Mac so they're reusable reference anchors — they didn't transfer as files in the Cowork session

Substack heroes — regenerate all in the v2 pencil-test style (Post 1 first, then 2/4/5/6) via the openai-image-gen skill (GPT Image 2, OPENAI_API_KEY in code-brain/.env; pass a style anchor with --reference, --quality high, --aspect-ratio 16:9) or ChatGPT, per the v2 doc's master recipe. Accent per post: amber for human posts (1/2/5/bonus), teal for technical (3/4/6/7). Post 1's pencil-test prompt is ready at 01-cant-prompt-taste/images/hero-prompt.txt (the "confident stranger rising from the laptop" concept). The grotesque NB2 path is retired

anima Flo (Phase 5) — self-hosted FLUX + Shakker sketch-LoRA for pencil in-betweens (the $0-ongoing future). Flo-B (2026-06-10) disqualified both fal.ai in-between candidates: Seedream morphs faces through the tween (the Reve failure DINOv2 misses), Qwen-plus reframes/degrades. In-betweens pivoted to NB2 (winner) / NB Pro (backup). API edit models hope-and-pray on grain+identity; self-hosted FLUX + sketch-LoRA controls the aesthetic at generation time. Re-evaluate by dropping FLUX in as a variant in the retained re-runnable bake-off (evals/bakeoffs/2026-06-10-flo-inbetween-pencil-pilot/, run the full 4×14). NOTE: this ticket was claimed-filed in the Flo-B field report + CLAUDE.md but never actually landed here until the 2026-06-10 Cowork verification caught the gap. Until then NB2/NB Pro own in-betweens

anima Flo (Phase 5) — NB Pro routes render SQUARE, fail HF01 (pre-flight before any end-to-end run). The nb2/standard path (pipeline/generate.py generate_frame) passes --aspect-ratio 16:9, but the nb_pro path (invoke_image_edit / nb_pro_runner) passes NO aspect ratio → renders 1024²/2048² square, which fails the HF01 16:9 gate (audit.py, 2% tolerance). So Flo's hero_keyframe + in_between_mid routes (both nb_pro) currently produce HF01-failing frames. Never surfaced in the pencil-test (Act 1 used the 16:9 skill path); will bite the first end-to-end run that routes a hero frame to NB Pro. Fix: plumb aspect_ratio through invoke_image_edit (or have frame_router's nb_pro branch request 16:9). Surfaced 2026-06-10 (Flo-B field report flagged it as a "framing confound"; it's a production gap) — assigned: Sean- anima Em CC01 (seam #10, EVAL-GATED): Em's absolute left/right stylus-hand verdict is noisy in a screen-right profile — in the first integrated run it PASSED F01 then FAILED F02/F04/F05 on the identical near-hand-draws config. CC01 is better judged frame-to-frame than per-frame-absolute (continuity_audit.py already has CC01-CC08). Fix = a frame-to-frame continuity check, NOT a per-frame-absolute verdict. EVAL-GATED: any change to Em's verdicts requires re-running the vision_critic baseline + re-ratifying — must NOT touch evals/vision_critic/ (md5 2af75906502f1caf8857e18828ceb2e4) without a deliberate re-baseline. Field report: anima docs/anima-test-runs/2026-06-11-first-integrated-run.md seam #10

anima museum #14 / Slice 3: the seam-#12 JPEG-as-PNG fix is forward-looking — it normalizes future candidates at FloNode generation time, but the already-shipped "Spark, Shared" frames in runs/2026-06-11-spark-shared-first-integrated/approved/ are still JPEG-data-as-.png (they assembled fine via the hand path). When museum capture (#14) copies those existing frames as thumbnails, run pipeline/agents/image_utils.normalize_to_png on them first or the museum inherits the mislabel. Fold into the Slice 3 museum-capture build

anima FLEET HARDENING CAMPAIGN — before the costed run / production use, each agent needs more tests/evals/hardening passes to be ROCK-SOLID. Current eval coverage (uneven): Em has a full scored suite (the ratified 0.97/1.00/0.00 verdict baseline + Gate-2/Gate-3 axes); Maya + Cy have evals/{agent}/cases.yaml + pytest runners; Flo, Mo, T3 council, and the orchestrator have NO scored eval suite yet; Sam + Bea aren't built. Per the eval handbook (anima docs/research/2026-05-31-ai-evals-best-practices-and-anima-eval-strategy.md) per-agent matrix, build error-analysis-first / binary / ships-red eval suites + targeted hardening per agent. Rough priority once the fleet is complete: (a) orchestrator drift + restart/retry-rate eval over N real runs (deterministic state/JSON discipline, promote to Opus if restart >10%); (b) Flo route-correctness + the self-hosted-FLUX in-between future; (c) T3 panel-value-add (PoLL κ-delta) + chairman-synthesis fidelity (Sage-tier bake-off #2); (d) Mo never-invent fidelity. SEQUENCE: after Sam + Bea land (complete the fleet first), then a hardening sweep.

anima orchestrator COSTED VALIDATION RUN (HELD by Sean 2026-06-11) — the first real end-to-end CLI run. Pre-flight: `python -m pipeline.run --brief briefs/2026-06-10-spark-shared --stub` (now $0, ANIMA_FORCE_STUB-gated, walks to DONE — Cowork-verified 2026-06-12) to confirm the chain; THEN drop --stub for the real ~$0.66 run from a PLAIN TERMINAL (not inside a Claude Code session — nested-SDK throttle, seam #4), under fleet-ops §0. The 5-frame shots.yaml reproduces the 5-key cut; the shipped 6-key SS_F03b grin-peak insert stays a hand edit to sequence.txt. The Slice 2.1 brief snapshot means the run won't dirty the committed brief.

animation-pipeline upgrade — feed the Miyazaki/visual findings from the screenplay-modes calibration into the `animation-pipeline` skill (the calibration flagged these for both skills). Carry over: object-economy / Room-as-Biography / the Loaded Object, Haptic Visuality, and Metaphor-Compression-in-an-empty-frame as Sean's door into wordless *ache* (the feeling lands on a symbolic object in an empty frame AFTER the character leaves — never a held close-up on a grieving face). Load-bearing coaching note: Sean CANNOT sit in a contemplative hold — he converts stillness into a goal/errand (installs a ticking clock + a deadline that weren't asked for), so the Miyazaki Micro-Ma / contemplative stillness must be a deliberately-coached muscle, not assumed; his wordless muscle is visual-narrative (objects/rooms), not contemplative. Sources: `.claude/skills/screenwriting-modes/references/screenplay-calibration-notes.md` §2 (Miyazaki SPLIT), §3 (wordless = visual-narrative muscle), and the script-mining report §2 (room-as-biography exemplars). This is also the Sam↔Bea handoff surface in anima (Sam writes the loaded object; Bea boards it).

intent-engineering MCP Workstream B / Intent Card — brainstorm DONE 2026-06-18; decided build-brief at sw-mcp-intent-engineering/docs/2026-06-18-intent-card-build-brief.md (grounded by docs/2026-06-18-brief-quality-research.md, a 5-agent deep-research synthesis of creative-brief craft). LOCKED: one product (brief mode = optional `mode` field on the existing 3 tools, NOT 6 tools / separate server), self-contained v1 (brand assets deferred to the On-Brand Gate), a research-validated 10-section brief rubric + focus / anti-bloat / completeness≠correctness cross-cutting checks + a documented-failure-cited anti-pattern catalog (the rational proposition + insight stay OPTIONAL = a deliberate contested stance to own in the README). OPEN: (1) `mode` default explicit-vs-auto-detect; (2) Q2 canonical dogfood brief + stand-in brand (candidate: Sean's own Substack brand); (3) Q5 naming — Intent Card vs `audit_intent_spec` in the post/README. BUILD = #2 after the Advisor, NOT started; §9 CHANGELOG approval gates the `mode` schema change before code

discovery GATHER-stage spend invariant (Phase-3 review follow-up, LOW): the new `except DiscoveryFailed` cost-recording path in [tools/llm-council/council/discovery/__main__.py](tools/llm-council/council/discovery/__main__.py) only covers FUSE-stage spend; the generic `except Exception` after it assumes "no spend incurred pre-fuse." That holds today because FUSE (OpenRouter) is the only billable stage, but GATHER calls Perplexity Sonar + web search — if a Sonar/web call is ever instrumented to bill (or already incurs cost not surfaced as an exception attribute), a gather-stage failure would silently record $0, re-opening the exact cost-integrity bug Phase 3 closed one stage upstream. Flagged by the Task-3 code-quality review. Fix when GATHER billing is confirmed: thread gather-stage incurred cost into a typed failure the same way `FusionError.cost` → `DiscoveryFailed.cost_usd` does. Until then it's a documented invariant, not a live bug.

discovery `--segment` free-text into operator-bearing queries (Phase-5 follow-up, LOW): the Phase-5 `--segment` qualifier composes raw free text into the github (`f"{subject} in:title,body is:issue"`, [tools/llm-council/council/discovery/gather/github.py](tools/llm-council/council/discovery/gather/github.py)) and reviews (`({weak}) ({sites})` grouping, [tools/llm-council/council/discovery/gather/reviews.py](tools/llm-council/council/discovery/gather/reviews.py)) queries unescaped. A `--segment` carrying operator tokens (`is:pr`, an unbalanced `)`, `site:foo`) alters query semantics rather than just narrowing the audience — a self-inflicted yield bug, NOT a security/fabrication issue (read-only public search APIs; the VERIFY gate still governs every record downstream). Surfaced by the Phase-5 final whole-branch review. Fix if `--segment` ever becomes non-interactive/automated input: strip query-operator chars (`:`, parens) + collapse whitespace via a single `segment = segment.strip()` normalization at the CLI/pipeline boundary (also closes the whitespace-only-segment edge in the sonar prompt), and/or tighten the `--segment` help to "plain keywords only." Until then it's Sean's own arg against read-only APIs.

discovery Fusion request-shape compatibility watch (Phase-5 close-out research, LOW): `_build_body` in [tools/llm-council/council/discovery/fusion.py](tools/llm-council/council/discovery/fusion.py) sends the Fusion config as a TOP-LEVEL `"fusion"` block + top-level `model`, but current OpenRouter docs (https://openrouter.ai/docs/guides/features/server-tools/fusion) show it nested under `tools[0].parameters` with the judge as `model` inside. Ours is live-verified working (FUSION_SCHEMA.md), and no test would catch a regression if OpenRouter ever drops the top-level form. Fix-if-it-breaks: move config into `tools[0].parameters`. Add a periodic live re-verify (e.g., a quick run after any OpenRouter Fusion changelog). Surfaced by the 2026-06-21 close-out research dig.

discovery surface Fusion typed failure_reason (Phase-5 close-out research, LOW diagnosability): the Fusion server tool hard-fails with `status:"error"` + a typed `failure_reason` (all_panels_failed / insufficient_credits / rate_limited / fusion_invocation_capped / unexpected_error). Because `fuse()` reads the outer judge's `message.content` rather than the raw tool result, those reach us as a vague "did not return parseable" + one retry → `FusionError`. Safe (degrades correctly) but loses the real reason. Enhancement: detect `status`/`failure_reason` in the response (if exposed at our layer) and surface it in the FusionError message for diagnosability. Surfaced by the 2026-06-21 close-out research.

discovery last30 HackerNews errors under --no-native-web (Phase-5 close-out, LOW): the 2026-06-21 last30 verification run yielded reddit (3 records) but HN emitted a `hackernews_error` field (0 HN records). Likely the `--no-native-web` flag our collector passes ([tools/llm-council/council/discovery/gather/last30.py](tools/llm-council/council/discovery/gather/last30.py) `_subprocess_runner`) disables a path HN needs. Degrades safely (parser handles the empty hackernews list). Investigate when convenient: try dropping `--no-native-web` for HN, or confirm HN needs native web; weigh against latency/cost. reddit alone already restores meaningful social evidence.

discovery per-run cost cap can be exceeded by actual spend (Phase-5 close-out live finding, MEDIUM): the per-run cap is enforced ONLY on the pre-flight ESTIMATE (`estimated = max_cost_per_run * 0.6`) in [tools/llm-council/council/discovery/__main__.py](tools/llm-council/council/discovery/__main__.py), never against the actual `usage.cost`. A 2026-06-21 standard run on "Claude plugins and skills for 2D animation pipelines" cost $2.74 vs the $1.50 standard cap (1.8x over); cost is web-tool-call-dominated and high-variance by topic (a deep run the same day was only $0.99). The daily cap ($10) IS checked against actual accumulated spend and remains the real guardrail (close-out testing hit $7.31/$10). Not a correctness/fabrication issue — a budget-predictability one. Options if tighter per-run control is wanted: (a) raise the estimate factor (0.6 → ~1.0) so the pre-flight gate is less optimistic; (b) print a post-run warning when actual > per_run_cap; (c) bound evidence-bundle size / `max_tool_calls` more aggressively per tier; (d) accept it and lean on the daily cap (current design). Surfaced by the close-out confidence runs.

substack-studio (migrated 2026-06-22): decide whether it becomes the LIVING drafting home or stays a curated public snapshot. Today `substack_drafter.py:529` + `agents-sdk/config.toml:556` still write to the gitignored source under `prj-job-hunt-2026/onwards-and-upwards-5-4-26/substack-drafts/`, so new drafts do NOT land in substack-studio. Do NOT repoint `output_dir` to the public folder until a scrub-gate exists — raw drafter output can carry un-suppressed Do-Not-Promote framing that would leak into the public path. See [redacted] §Path-coupling.

⚠️ pre-existing public leak (NOT from the substack-studio migration): the already-tracked `[redacted]:106` still contains an un-scrubbed Do-Not-Promote illustrative example (the "ask lands sideways" sample sentence) in the PUBLIC repo today (the substack-studio copy was scrubbed). Recommend a source-side scrub. Also LOW: the two `[redacted]*-last30days.md` reports carry mild hiring-signal framing that's already public — decide whether to neutralize at source.

agent-fleet-observability test suite (LOW, surfaced 2026-06-23 during the dashboard-freeze fix): 2 time-bomb fixture tests in `tests/test_aggregations.py` (`test_compute_kpis_eval_pass_and_spend`, `test_compute_fleet_status_health_per_agent`) fail on origin/main because their fixtures hard-code 2026-05-12/13/16 dates and assume "now" is inside the 7d/30d rolling windows; past mid-June they age out (e.g. `fleet_spend_30d_usd` computes 0 vs expected 0.3812). Pre-existing, harmless to production (the live dashboard reads real telemetry, not fixtures), but leaves the suite red (2 failed / 165 passed). Fix: parametrize the fixtures against a relative `today`/`end` anchor instead of absolute May dates.

[closed 2026-06-18] intent-engineering MCP Workstream A — SHIPPED v0.2.0 (A1 heading-vocab mapper + A2 schema-drift snapshot + A3 pagination test), merged to main, npm publish + MCP registry both DONE (Sean confirmed published + registered 6/18). This is the MCP Post 3 ships on. Only Workstream B (Intent Card) remains — parked/spec'd, build #2 after the Advisor, no deadline.

[closed 2026-06-18] Publish "Raising Claude" Post 3 (Correct Was Never Defined) — PUBLISHED 6/18: https://seanpwins.substack.com/p/correct-was-never-defined. Live render QA'd clean (title / subtitle / hero / repo link / social card all correct); npm package name hyperlinked to npmjs by Sean. post.md frontmatter → status: published + publish_date 2026-06-18 + live_url; substack README queue row marked published. Ships with the shipped intent-engineering MCP @swins/intent-engineering-mcp (v0.2.0).

DONE 2026-06-18 (Claude Code): job-feed ATS watchlist decay — failed pollers cut from 20 → 0 (verified via a live `fetch_all` run; postings 3876 → 4798). Probed every flagged slug against Greenhouse/Lever/Ashby: (1) recovered 3 via corrected slugs in `watchlist.yaml` — `scale`→`scaleai` (177 jobs), `glean`→`gleanwork` (171), `together-ai`→`togetherai`; (2) the 7 "ReadTimeouts" (elevenlabs, lovable, hubspot, klaviyo, webflow, cursor, together-ai) were valid-but-slow boards dying at the 10s budget, NOT dead — fixed by bumping `http_timeout_sec` 10→20 in [agents-sdk/config.toml](agents-sdk/config.toml) (committed); (3) 11 companies on unsupported ATSes (Workday/SmartRecruiters/custom — huggingface, replicate, tome, canva, framer, spline, beehiiv, fourthwall, draftkings, datarobot, circle) moved to a documented commented block in the watchlist (track manually in target-companies.md). NOTE: `watchlist.yaml` is under the gitignored job-hunt private layer, so that edit is local-only / uncommitted (the config.toml timeout bump is committed). The web3career_token sub-item was split into its own Todo (Keychain secret — Sean-only).

DONE 2026-06-18 (Claude Code): llm-council transcript render no longer crashes on null model content. Guarded all three model-supplied appends in `_render_markdown` at [tools/llm-council/council/cli.py](tools/llm-council/council/cli.py) — response content (line 40), ranking reasoning (line 47), and chairman synthesis (line 52) — each now falls back to a `_(no response…)_` placeholder instead of appending `None` into `lines`. Added regression test `test_render_markdown_handles_null_content` in [tools/llm-council/tests/test_cli.py](tools/llm-council/tests/test_cli.py) that reproduces the exact `TypeError` (red before fix) and asserts the placeholder + real content survive. Verified: `pytest tests/` → 34 passed, 1 skipped. NOTE: code lives outside the vault and is uncommitted in the working tree — commit when ready.

DONE 2026-06-18 (Claude Code, verify-and-close — already shipped): Tier C batch route wiring. All three asks are satisfied in-tree: the route `tier_c_batch_summarize = { model = "gemma4_26b-32k", machine = "alienware", fallback = "none" }` exists at [agents-sdk/config.toml](agents-sdk/config.toml) line 403 (fail-fast Pattern-E shape, no API fallback — the recommended choice), and the Tier C "production" note is in [CLAUDE.md](CLAUDE.md) line 170. No further work needed; closing the stale ticket.

DONE 2026-06-18 (Claude Code): "test suite hang" on the Gemini DR call resolved — `pytest tests/` now completes (895 passed in ~13s, was hanging). Root cause was subtler than reported: `test_run_warn_called_with_mtd_plus_pred` in [agents-sdk/tests/test_gemini_dr.py](agents-sdk/tests/test_gemini_dr.py) pre-seeded the ledger with a hard-coded 2026-05-03 entry, but `run()` computes mtd/today against the live `date.today()`. Once real time passed into June the May entry stopped counting, the daily-cap refusal no longer fired, and execution fell through to the real `client.interactions.create()` (genai + get_credential were unpatched) — a live DR call that polls up to 3900s. Fix: dated the ledger entry to `date.today()` so the cap math engages (also restores the intended $12.80 warn assertion), and added hermetic `patch("scripts.gemini_dr.genai")` + `get_credential` guards plus `mock_genai.Client.assert_not_called()` so no test can ever reach the network again. NOTE: code lives outside the vault and is uncommitted in the working tree — commit when ready.