Skip to content

Catch-up: migration 10, the end-of-run compile, the truth sweep - #130

Merged
leeovery merged 2 commits into
instance-map-lintfrom
instance-map-catchup
Sep 1, 2026
Merged

Catch-up: migration 10, the end-of-run compile, the truth sweep#130
leeovery merged 2 commits into
instance-map-lintfrom
instance-map-catchup

Conversation

@leeovery

@leeovery leeovery commented Sep 1, 2026

Copy link
Copy Markdown
Owner

PR5, closing the instance-map stack (design: #125, on #129). Migration 10 compiles both derived artifacts at sync time — serve tools answer the moment an instance lands on the release, and the rendered catalog replaces the model-written index; a malformed judgment file records an anomaly instead of bricking sync at step 0. The dex-run flow gains the end-of-run bin/dex map step (closing the gap direct page edits open, before the health check diffs). README, CLAUDE.md, the contract, and the run-skill prose brought true — including two statements earlier slices left false (taxonomy "still written directly"; hand-merge rules for files the verb now owns).

11 migration tests; mutation audit clean (4 equivalent survivors).

🤖 Generated with Claude Code

leeovery and others added 2 commits September 1, 2026 14:28
…he wiki gap

How existing instances catch up: a numbered migration runs the map
compile the moment an instance syncs to this release, so state/map.json
and the rendered wiki/index.md exist before the instance's next run —
the serve map tools answer at once, and the rendered catalog takes over
the model-written index. The compile is the engine's own (compile_map,
byte-deterministic), written only where an artifact differs from it, so
a second apply writes nothing and a log-race re-application recompiles
current inputs and destroys nothing. A pre-taxonomy instance gets the
honestly-empty artifacts, recorded like any migration. A malformed
taxonomy or entity-members file lands as an anomaly on the sync report,
never a raise: the repair is session judgment on the named file, and a
raising migration would stop every future sync at step 0, ahead of the
machinery refresh that ships the repair procedure — bin/dex map catches
the artifacts up once the file is healed, and lint flags them until then.

The run flow gains its required compile step: bin/dex map after the
cognitive work and before the health check, because wiki pages are
session-edited directly and page-derived map content (has-page, wikilink
edges) is only as fresh as the last compile — the verbs already
recompile on placement and exclusion; this closes the gap the page
edits open. Steps renumber, and the contract's run summary says the
same flow.

The truth sweep: README's serve surface states seven tools (six reads
including topics/entities/graph off the compiled map, plus capture) and
the dex-serve row and instance layout name the map; CLAUDE.md's
library.py line gains the map reads; the contract's state/ inventory
lists map.json; dex-run's State writes hands taxonomy and entity
members to enrich place (the stack moved that fence), and preparation's
merge rules route a conflicted taxonomy through the verb and a
conflicted index through bin/dex map.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
… the field

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@leeovery
leeovery force-pushed the instance-map-catchup branch from 21d2525 to 89b5c0a Compare September 1, 2026 13:29
@leeovery
leeovery merged commit 9bf5f91 into main Sep 1, 2026
@leeovery
leeovery deleted the instance-map-catchup branch September 1, 2026 14:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant