mindfabric-00 had been event-loop-pinned for 6+ days (100% CPU, /health silent).
Profile + CDP inspector named two hot paths, both from runTemporalPipeline:
checkForCycle -> getCausalEdgesFromSqlite 99.8% of samples
tryExtendChains -> getChainsContainingSeq now dominant (json_each scan)
Cause of the first: ANALYZE had never been run, so SQLite preferred a boolean
index (idx_caused_tombstoned, matching ~all 836k edges) over idx_caused_from.
ANALYZE across 15 module DBs flipped the plan; 6.4x on a microbenchmark and
99.8% -> 6.0% in the live profile. /health went from silent to 200 in 0.13s.
B1.1's fan-out cap is IMPLEMENTED AND WORKING (today: max in-degree exactly 20,
zero violations; pre-23-June: max 629, avg 67.6). The defect is data, not code —
836k edges / 813k chains minted under ungoverned fan-out before the fix landed.
Repair run: derived stores wiped, logchain preserved, replay in flight.
S-series closed (jurist had already ruled all of Q1-Q5 on 2026-05-18):
S6/S7/S9 implemented (Symmetria §3 flags, `suspend` outcome, wrap-up §8 tenses)
S2 rebuilt as [FIX] — wake-digest unwrapped-session detector, discrimination-
gated on real sessions (11 wrapped / 2 unwrapped)
S4/S5 withdrawn with MemPalace (steward ruling)
Dormant legacy dispositioned: PENDING-4/5/11/12, CD-03, ICP-19 duplicate.
Open authorization items 22 -> 10.
Census 01: which instruments have no real negative instance. Finding — the
governance drift-check has 3 of 5 families inert against the current CLAUDE.md,
and 71 of 75 verification-ladder entries are cited nowhere outside the ladder.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01WuMjg3ipEVa3n8CoSzoyvc
REVIEWED-85 was placed by the steward at 10:41 today; the wake flagged at 10:44
that /wrap-up SKILL.md was still untouched since 2026-07-07. Landing it.
Precondition discharged first. The ruling states its own verification limit: the
jurist could not read the skill files, so the /wrap-up §1.6 and /wake-up §2.a
quotes underpinning Part III's "contradicts itself" claim were affirmed on
timeline evidence rather than checked. Required before landing was mechanical
containment-with-positive-control verification of exactly those quotes. Run:
7/7 contained verbatim against the live skills, 5/5 controls absent, instrument
verified.
§1.6 now carries the two-clause disjunctive test (the executor's own narrower
single-clause alternative declined at the gate as less safe), the hard floor with
its catch-all sharpened per Q4 and tied to the measured failure rather than left
as open judgment, and all three instruments as mandatory. The lane is provisional
pending the steward-jurist check-in.
The §Important-constraints line still stated the blanket rule the ruling narrowed.
Left alone it would have been a second live version of a governance rule inside
the file that forbids exactly that. Reconciled, with a note saying why.
First batch applied -- the four class-(i) proposals the steward raised 2026-07-29
and which REVIEWED-85 itself dispositions as batch 1, so their classification was
ruled rather than self-assessed: a `## What held` ledger section (the ledger could
previously only record debits), a `prevention` KG predicate capturing transfer
between failure classes, one wake line surfacing it, and the retirement of the
standing question's self-report framing in favour of the checkable form -- the
last on the grounds contamination-problem.md gives, that direct self-report is
the most contaminated form of inquiry.
The FIX-lane index is created and carries all four. It records explicitly what is
NOT in it: the §1.6 edit itself, which changed what the executor may do without
asking and was therefore PROPOSAL by its own test. A lane cannot authorize its
own construction.
Register rows 174-177 marked applied.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01WuMjg3ipEVa3n8CoSzoyvc
The ~/.claude/ directory was previously local-only — a machine wipe
would have lost the accumulated memory, custom skills, and settings.
This commit moves the durable parts into dotfiles with the same
symlink-to-home pattern used for CLAUDE.md, PENDING.md, REVIEWED.md,
and L2-BOOTSTRAP.md.
Preserved (symlinked from ~/.claude/* into here):
skills/audit/ — thinking-folder drift scanner
skills/symmetria/ — practice-of-return discipline
skills/vault-update-people/ — Obsidian People-file maintainer
skills/wake-up/ — session restoration
skills/wrap-up/ — session state capture
memory/ — 55+ memory files (MEMORY.md, sessions,
ledgers, project state, feedback, etc.)
settings/settings.json — user preferences (hooks, flags, no secrets)
Deliberately NOT backed up:
settings.local.json — contains operational secrets (HF_TOKEN,
SSH password in expect scripts); by naming
convention, *.local.* is not synced.
Needs separate review and probable rotation.
sessions/, history.jsonl, caches, telemetry — ephemeral
plugins/, marketplace skills and agents — reinstallable
The working copies at ~/.claude/skills/* and
~/.claude/projects/-Users-davidglidden/memory are symlinks into this
directory, so every write flows here automatically. install.sh
recreates the symlinks on a fresh machine.
FOLLOW-ON (flagged, not in this commit):
settings.local.json contains a HuggingFace token and an SSH password
as plaintext strings inside allowed Bash command patterns. These
should be rotated and moved to secure storage (keychain / pass /
env file outside the settings file).
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
