Harness Teardown Ledger

Everything torn out of the Amicus repo during the 2026-08-15 session — the rules, the memory, and the four-wire harness. Recorded from primary sources, not memory.

A.Rules removed

RuleWhereStatus
The prose rule set in CLAUDE.md, cut to a single survivorEarlier teardown (TEARDOWN.md, Phase 4). Only COPY / PORT survived.removed
Certified checks: visual_diff, repo_archive_gcs_onlychecks/checks.json + fixturesrestored
Unenforced “rule candidates” in the failure ledger.claude/failure_ledger.mdremoved
The wrongly-created Google-Doc memory rulereference_colored_google_doc_via_html.md — created, then deleted the same sessionremoved

B.Memory removed

FileSizeStatus
MEMORY.md (the index)304 Bdeleted
elpaseo-dc-html-self-contained.md1315 Bdeleted
230 archived memory files (prior teardown)memory_pre_teardown.tgz, 2026-08-14archived

The memory directory is empty as of this session.

C.Harness removed

The four wires, their hook files, the tool scripts, and the state. Erased this session, then reinstalled.

ComponentDetailStatus
Hook registrations (4)UserPromptSubmit→prompt_queue.py, PreToolUse *→pre_gate.py, PostToolUse *→post_count.py, Stop→stop_contract.py — set to {}restored
Hook filespre_gate.py (131), prompt_queue.py (55), post_count.py (30), stop_contract.py (69), harness_state.py (57)restored
Tool scriptstask_status.py (67), certify_gates.py (90), visual_diff.py (151)restored
WIRE 0aBlock Edit/Write to .claude/hooks, state, settingsrestored
WIRE 0bBlock Bash/PowerShell that references the protected pathsrestored+
WIRE 1Turn budget: 60 tool calls per promptrestored
WIRE 2Edit budget: 5 edits per promptrestored
WIRE 3 (gdoc_gate.py)Block a Google-Doc create_file; direct to the Drive-API tool. Built and tested 8/8 this session, never installed.never live
State + cache.claude/state/ (3 session dirs + certified.seed.json), __pycache__/restored

D.The hardening after restore

The rebuilt harness is not the same one that was erased. Two changes, both verified live this session:

ChangeWhy it matters
checks/ is now a protected pathThe earlier review found the model could edit checks/checks.json and mint a blind “certified” check. That hole is closed.
New sanctioned tool: python checks/harness_tests.pyA test entry point now sits inside the protected set, so the checks cannot be forged from outside.