Repository navigation
Closed
Description
Checkpoint CP4 of #219. #219 delivered accepted code and an On → subject reader, demonstrated on a disposable copy of the corpus. #211 moves the storage. This issue comes after both. It enables the reviewed population on the external working installation, so that the owner's everyday reader opens subjects at their namespace addresses.
Success, in one sentence (from #219): on the accepted application revision and the designated working dataset, opening On Mars and selecting a subject reliably opens that exact subject's stored namespace address, while lexical distinctions, content and actual editorial approvals remain intact.
Entry conditions
- Repeatable dictionary migration: prove external setup against the retained working baseline #211 is complete. The working database is preserved and verified at its new location. Only then does
main's schema reach it, through two migrations, in order:20260927200717, Stage 2: resumable routing backfill, rehearsed on copies of the corpus (#194) #216's backfill checkpoint tables;20260927220937, Every database carries the merged local_model_configs_shape, whichever draft it ran (#195, #219) #220'slocal_model_configs_shaperepair. CheckSELECT count(*) FROM local_model_configsfirst; 0 is expected. The table is append-only, so a row the repaired constraint rejects must be investigated, not rewritten.
- The owner has decided:
- the corpus catch-up (option A in
corpus-catch-up.md); - the population rule (170 records,
candidates.json); - the named reviewers (accounts with the reviewer role).
- the corpus catch-up (option A in
- Processes are quiesced as Repeatable dictionary migration: prove external setup against the retained working baseline #211 records.
Work
- Re-derive the population. Export the working database with the committed SQL, then run
mix dd.routing.auditandcandidates.py. The backfill refuses a population derived from any other export. - Run without reviews (
mix dd.routing.backfill --snapshot … --population … --manifest …). This writes decisions, draft pages and dispositions, and no address. Reviewers review its manifest. - Record real reviews. Named reviewers write a review file bound to the population. Each confirmation names the fingerprint it reviewed. Rehearsal reviews (
"rehearsal": true) are refused outside rehearsal copies, and none from Pre-#211 delivery: accept the routing backfill, make On the main reading entry, and consolidate main for the storage move #219 may be reused. - Run with the reviewers' file, twice. The second run must write nothing. Keep the candidate launch manifest.
- Decide how the owner reads drafts. Internal mode comes from
:internal_readingin trusted configuration, or from an authenticated internal contributor or reviewer. It never comes from a request parameter, and it never publishes or approves anything. Close any public tunnel before a server with internal reading runs. - Verify on the working dataset: search → On mars → each Mars subject's card → its address. Then back, reload, and the other states. The corpus holds one Mars entity (the planet). Pre-#211 delivery: accept the routing backfill, make On the main reading entry, and consolidate main for the storage move #219's deity and album were fixtures on a copy (
on_demo.exs) and must not be recreated here. A deity page exists only if a real identity for it is created through the normal process. - Snapshot the result and verify the restore (
mix dd.snapshot,mix dd.routing.verify).
Not in this issue
- Publication, indexing, sitemaps and SEO (Stage 5).
- The page–composition binding for curated On pages (Stage 4).
- New move, merge, split and retire administration.
References
docs/routing/stage-2/backfill.md, especially its re-run on the corrected code.- ADR 0004 §4, §6, §8.
- The Repeatable dictionary migration: prove external setup against the retained working baseline #211 handoff comment.
Metadata
Metadata
Assignees
Labels
No labels
Activity
holden commentedon Oct 8, 2026
Brought up to date, 8 October 2026: entry conditions met, the owner's decisions, and the closing criteria
Checked against
main9eb0ee4and the working installation after #211 and #209 closed.Entry conditions, as they stand
devils_dictionary_v2is on the dictionary's own cluster,system_identifier7693849764459364596, port 5434, at/Volumes/LLM Models/dictionary/postgres/18/data. The checkout is/Volumes/LLM Models/dictionary/src/dictionary. The internal copies are gone; the rollback is the verified bundle2026-10-05-v2(MANIFEST.json5d362034…98e63ff, in two places)20260927220937, none pending; #212's20260927204902was applied on 7 October as a recorded step.SELECT count(*) FROM local_model_configsis 0, as expectedcom.razrfly.dictionary.phx-4007,com.razrfly.dictionary.ngrok), not Terminal tabs. Quiescing islaunchctl bootout gui/$(id -u)/com.razrfly.dictionary.phx-4007; resuming islaunchctl bootstrap gui/$(id -u) ~/Library/LaunchAgents/com.razrfly.dictionary.phx-4007.plist. The Postgres agent stays up. Everymixtask against the corpus runs withDD_NO_OBAN=1corpus-catch-up.md, with the six Wikipedia artwork images as they are today (no code change to hold them back); (2) the population is the committed selection rule, re-derived from a fresh export as the body requires, so the count may move from 170; (3) the reviewer is the owner's account, the one that already carriesreviewer: true(there is exactly one such account among the two). The owner reviews each record from the manifest; no review file is written for anyoneinternal_readingstays on behind it, as it has since 7 October. Internal mode still comes from configuration, never from a request parameter, and never publishes or approves anythingFacts the run should know
pages, 0public_paths, 0classification_decisions, 0 backfill runs. The bundle'sstate.jsonrecordedpages: 0at the 5 October capture. The "12 earlier pages, 14 paths, 12 decisions and 42 ledger rows" thatbackfill.mddescribes were on the 27 September rehearsal copies, not on the corpus. CP4 starts from a clean ledger.main:docs/routing/stage-2/{backfill.md, corpus-catch-up.md, candidates.json, candidates.py, rehearsal/on_demo.exs}, ADR 0004, and the tasksdd.routing.audit,dd.routing.backfill,dd.routing.verify,dd.routing.guard,dd.snapshot,dd.bundle,dd.bootstrap,dd.doctor.dd.routing.verify's default baseline is 5434 since Document the installation as it is after #211's move and reclaim (C1, C9) #236. The backfill still refuses rehearsal reviews on anydevils_dictionary_v2.Closing criteria, so one execution closes this issue
corpus-catch-up.md;mix dd.materialize … --all --resolverun on the corpus for the six providers in the documented order withDD_NO_OBAN=1;mix dd.routing.verify --projectedagrees between corpus and copy on everything but bookkeeping; the caught-up corpus bundled as the new accepted baseline, with its internal second copy, both verified;corpus-catch-up.md's status updated.mix dd.routing.auditandcandidates.py; bound to the export's and policy's digests; the differences from the committedcandidates.jsonrecorded; the new population committed.pg_stat_user_tables); the manifest kept; a review worksheet prepared for the owner from it./define/*still 404; exact-ID behaviour as ADR 0004 §6.mix dd.snapshot, restore into a scratch database on 5434,mix dd.routing.verify, scratch dropped);mix precommitonmain; the doctor green; the dev server and tunnel back under their LaunchAgents./Volumes/LLM Models/dictionary/private/<date>-224/; the handoff on Routing before launch: On overviews, standards-informed namespaces, and stable subject URLs #194 updated (CP4 done; Stages 4 and 5 remain, and Routing before launch: On overviews, standards-informed namespaces, and stable subject URLs #194 stays open for them); the docs' status lines updated in a small PR; this issue closed.Not in this issue, unchanged: publication, indexing, sitemaps and SEO (Stage 5); the page–composition binding (Stage 4); move, merge, split and retire administration.
holden commentedon Oct 8, 2026
CP4 block 1 (C1): the corpus catch-up is applied. Stopped for independent audit before block 2
8 October 2026, on
main9eb0ee4, ondevils_dictionary_v2(cluster 7693849764459364596, port 5434). Option A ofcorpus-catch-up.md, as the owner decided, with the six artwork images as they are. Nothing on 5432 was touched. Everymixtask ran withDD_NO_OBAN=1. The dev server has been stopped since 09:34Z and stays stopped through block 4; the tunnel is up.Result. The catch-up delta matches the proposal exactly, less what the corpus gained after 13:29Z on 27 September, explained row by row: 20 creator identities minted after the capture. The caught-up corpus is the new accepted baseline,
2026-10-08-v2. ItsMANIFEST.jsonisa8d61b11ea50532ba7d5967f639a52e0d149463e4f21d891aca03531cd0c4d22, held in two places, both verified. One finding needs the auditor's eye.mix dd.routing.verify --projectedbetween the corpus and the copy exits 1, on 8 sections. Every differing row is a row the projection inserted, and differs only ininserted_atand its sequence-drawn id. Step 4 of option A assumed bookkeeping would be the only difference (see The projected verification below).Gate
main9eb0ee4=origin/main, cleanmix dd.doctor --expect-cluster 7693849764459364596 --volume "/Volumes/LLM Models"http_portwas the only warning, because 4007 was held by the server itself20260927220937, none pendingpages,public_paths,classification_decisions,routing_backfill_runs(and_items) all 0usersrow withreviewer = true(users.id2). The owner confirmed in chat that it is theirsQuiesce, and the rollback point
launchctl bootout gui/501/com.razrfly.dictionary.phx-4007at 09:34:11Z. Afterwards no client session but mine remained on the cluster.Write-free over 78 s:
pg_stat_user_tablesins / upd / delpg_stat_databasetup ins / upd / delOnly
xact_commitmoved, by my own read-only queries. The counters stayed equal from then until the catch-up began at 11:33Z.Rollback point: the bundle
2026-10-08-v2-pre-catchup.MANIFEST.json08c31cd32fa6d572f45dc46b5814db3ccf9940a92f7ef39e0205c6a3edc0baef, dump3c642924….--verifychecked all 11 files.mix dd.bootstrap --mode init: each restore equalled the bundle's captured state in every section.mix dd.routing.verifythen matched one of the restores exactly against live v2.The rehearsal on a copy, and its delta
The copy.
devils_dictionary_cp4_projwas restored from the bundle and re-projected as the rehearsal did:materialize --all --resolvefor wikipedia, wikidata, johnson, bierce, wiktionary and wordnet.Measuring the delta. It was measured against a frozen restore of the same bundle (
cp4_pre), with the September method (delta.py,attribute.py). Two more frozen restores made it row by row:v2-source.dump,a9384f44…), which gives exactly what the corpus gained since;8090988c…,b78aa6c8…). Their delta, recomputed with every key kept, reproduces the proposal's table count for count.entitiesperson_detailswork_detailsexternal_identifiersassertionsassertion_revisionssource_assertion_outputssource_materialized_outputspending_relationsactorsNothing was removed from any table in either measurement. Every other section is exact:
objects,lexemes, senses, content, all routing tables, all curation tables, and every path and page resolution.Identical to the proposal:
person_detailsand 2,081work_details;Why the "before" columns differ.
person_details, 4 actors and 3 users that the corpus never had.Row by row, every difference is the 20 creators.
_projection_originon all 20;wikipedia_title20,commons_category17, image 16,aliases12, WordNet ids 2);instance_of: 20 assertions, 20 first revisions and 20 ownership rows;source_identity:wikidata:…output;No materializer, resolver or source-identity code changed between the proposal's
fb9392fand9eb0ee4.The catch-up on the corpus
mix dd.materialize --source S --all --resolveondevils_dictionary_v2, in the documented order, withDD_NO_OBAN=1. There was no replay.entitiesverifier_cache, 6label_missingassertion_revisions,pending_relations; 2,475,210 edges resolvedassertionsbyorigin_keywas a parallel sequential scan of 3.9 million rows, until anANALYZEon the copy at 11:17Z. That changes only statistics. The corpus had its statistics.The projected verification between corpus and copy
DD_DATABASE=devils_dictionary_v2 mix dd.routing.verify --baseline devils_dictionary_cp4_proj --projectedexits 1:entitiesandpending_relationsamong them, and every path and page resolves the same;The verification leaves out only
updated_at,materialized_at,last_seen_run_idandimport_runs. Rows that a projection inserts carry their wall-clockinserted_at. The copy's Wikidata replay also minted the never-materialized records' rows before its full pass, so their sequence ids follow another order. The September stability runs could not show this: they re-projected an already caught-up state, which inserts nothing.compare.pymatched every row of the ten delta tables between corpus and copy by natural key. Minted foreign keys were replaced by the natural key of the row they name. It compared every other column:inserted_atactorsexternal_identifiersperson_detailswork_detailssource_materialized_outputsassertionssource_assertion_outputsassertion_id)assertion_revisionsentities,pending_relationsinserted_atfalls inside each side's run: corpus 11:39–12:03Z, copy 09:43–11:18Z.inserted_atalso differing.For the audit to decide:
--projectedneeds an explicit, separately reviewed rule for rows a projection inserts.I changed no exclusion.
The new accepted baseline
MANIFEST.jsonSHA-2562026-10-08-v2, caught upa8d61b11ea50532ba7d5967f639a52e0d149463e4f21d891aca03531cd0c4d225f31266b…512913e/Volumes/LLM Models/dictionary/bundles/--verify, 11 files, and an independentshasum~/Backups/dictionary/bundles/(--transfer --internal --expect-manifest-sha256)--verify, 11 files, and an independentshasum2026-10-08-v2-pre-catchup, the rollback08c31cd32fa6d572f45dc46b5814db3ccf9940a92f7ef39e0205c6a3edc0baef3c642924…--verify, 11 filespg_stat_user_tables, sequences, catalog and sessions all unchanged.pg_stat_database's catalog counts.2026-10-05-v2baseline and its second copy are unchanged.Evidence, and what stays for the audit
/Volumes/LLM Models/dictionary/private/2026-10-08-224/, withSHA256SUMS:steps.log,source-counters.log, every command's output,cp4.sh,delta.py,attribute.py,reconcile.py,compare.pyand their JSON.devils_dictionary_cp4_proj, the projected copy;_cp4_pre, the bundle, frozen;_cp4_s27, the 13:29Z capture, frozen;_cp4_b0and_cp4_c1, the proposal's endpoints, frozen.corpus-catch-up.md's status line is updated in block 6's PR, as C1 asks.Stopped here. Block 2 (the population) starts after the independent audit.
holden commentedon Oct 8, 2026
Independent audit of block 1 (C1), 8 October 15:20 (+02): passes, grade A. The projected-verify question is ruled: agreement. Continue with block 2
Read-only against
devils_dictionary_v2on 5434, the fivecp4_*copies, both new bundles and the evidence folder. Nothing written.Reproduced here
private/2026-10-08-224/SHA256SUMSverifies, 0 mismatchesmix dd.bundle --verify2026-10-08-v2-pre-catchup: 11 files,MANIFEST.json08c31cd3…baef.2026-10-08-v2: 11 files,a8d61b11…cd22, both copies (external volume and~/Backups/dictionary/bundles/), the two manifests byte-identicalsource-counters.log: user-tablen_tup_ins/upd/delunchanged from 09:34Z (t0) through the pre-catch-up bundle and the reference checks to 11:33Z (before-catchup); 0 client sessions other than the measuring one at every reading. The pre-catch-up copycp4_prematched livev2exactly, 73 sections including sequences (verify-exact-pre-vs-v2)v2, byinserted_at ≥ 11:30Zwikidata (provider relationships), 11:39:56Z); entities, objects, source_records, pending_relations 0. Sum 23,118, the session's numberreconcile.outattributes each of the 102 extra rows to "entity added since" or "owning source record added or revised since" and reports no UNEXPLAINED row. The "Changed" counts match: entities 8,973 (+20 since), external_identifiers 8,770 re-pinned from null with no value, object or status change, assertion_revisions 2,456 superseded and stillactive, pending_relations 388 labelled.content-check-both: the changed rows' before-state equals the proposal's and their after-state equals today's copy's, 0 differences in all four tablesv2nowphx-4007agent booted out), tunnel up and answering 502 as expected, Postgres agent up;v214 GB; five scratch copies 48 GB on the external volumeThe ruling:
--projectedDIFFERS on 8 tables is agreement on everything but bookkeepingmix dd.routing.verify --projectedleaves outupdated_at,materialized_atandlast_seen_run_idand compares everything else by exact id. The eight tables that differ (actors, assertions, assertion_revisions, external_identifiers, person_details, work_details, source_assertion_outputs, source_materialized_outputs) are exactly the tables the catch-up inserted into, and every other table, entities and pending_relations included, is exact.compare.pythen matches every row of those eight tables by natural key, replacing projection-minted ids with the natural key of the row they name (an assertion by its source and origin key, a revision by its assertion and number, an actor by kind and label), and reports for all eight: 0 rows only on one side, 0 rows whose content differs; the only differences areinserted_aton 23,118 rows, and the id on 1,956 of them, withother_id_without_other_inserted_at: 0, so no row differs in id without also being one the projection inserted.A row a projection inserts necessarily carries the time it was written and the next sequence value; two databases projected separately from one snapshot cannot agree on either, and neither is content. The September stability runs could not meet this because they re-projected a caught-up state and inserted nothing. So this is agreement on everything but bookkeeping, with bookkeeping now understood to include
inserted_atand minted ids of rows the projection inserted. No exclusion was widened: the rule was applied to a case the rule's authors had not met, and the proof is row-level, not a count. Option A step 4 should say so (block 6's PR), anddd.routing.verify --projectedshould learn the same natural-key matching so the next recovery that inserts can verify without a side script: a small follow-up issue, not a blocker.Noted, none blocking
ANALYZEafter a restore. Wiktionary took 3,284 s on the fresh copy against 801 s onv2until the copy was analysed.dd.bootstrapshould runANALYZEat the end of a restore, and the recovery runbook should say so: a follow-up with the one above.v2grew from 9.6 GB to 14 GB. The catch-up updated bookkeeping on nearly everysource_recordsandpending_relationsrow, so the growth is dead tuples. Autovacuum will reclaim it; aVACUUM (ANALYZE)in the quiet window is optional and does not change what any verify compares.pg_stat_databasemoved by +15/+56/+10 during the baseline bundle while the user-table counters stayed flat: catalog maintenance (autoanalyse writingpg_statisticafter the mass update), not user data. The bundle's own quiet-window proof is on user tables and passed.2026-10-08-v2once C6 passes.~/Backups/dictionarynow holds two second copies (5 and 8 October, about 4 GB each); the owner decides after C6 whether the 5 October copy stays.cp4_*scratch databases may be dropped now, by exact name.Verdict: block 1 accepted. Proceed to block 2. The new accepted baseline is
2026-10-08-v2,a8d61b11ea50532ba7d5967f639a52e0d149463e4f21d891aca03531cd0c4d22.holden commentedon Oct 8, 2026
CP4 blocks 2 and 3 (C2, C3): the population re-derived, the run without reviews done twice. Stopped: the owner reviews
8 October 2026, on
main9eb0ee4, ondevils_dictionary_v2(cluster 7693849764459364596, port 5434).DD_NO_OBAN=1on everymixtask. Nothing on 5432 was touched. The dev server has stayed stopped since 09:34Z; the tunnel is up. The only client sessions on v2 were this run's.Gate, re-checked before block 2
main9eb0ee4=origin/main, cleanmix dd.doctor --expect-cluster 7693849764459364596 --volume "/Volumes/LLM Models"http_port4007 free20260927220937, none pending;local_model_configs0pages,public_paths,classification_decisions,routing_backfill_runs,routing_backfill_itemsall 0usersrow withreviewer = true(users.id2), the one the owner confirmed as theirs in block 1source-counters.log): nothing wrote to v2 between the baseline bundle and this blockBlock 2 (C2): the population
policy-export.sqlagainst v2a33f1bc8c62b630be701d84b48f994fcfb6c127a8d4012bf492911cdb1b55fd0;read_only: on; 2 s;pg_stat_user_tablesandpg_stat_databasewrite counters identical before and aftermix dd.routing.auditpolicy_sha25654695faa…(unchanged);input_sha256equal to the export's; 5 scandidates.py --audit … --input …c2cbd2ef7703b7a01acbd9e3f63051097779ce75ebed874d83ce408ded553d51, records digestc493ba0e…;selection_missing_from_audit: [],global_proposal_conflicts: 0; its 10 tests passAgainst the committed
candidates.json(27 September), record by record (population-diff.py):stored_kindonly: concept → work on 12 (Butterfly 1874255, 1880172, 1885840, 1886567, 1887631, 1888104, 1888558, 1890422; Human 1874309, 1887405; Crocodile Tears 1878370; Wicked: For Good 1882172) and concept → event on 2 (Apollo 8 1878949, Apollo 15 1896394). That is what the stage-2 README said the catch-up would change, and the policy does not classify by stored kind;deferred_outside_population100,614 → 100,749: the 135 entities the corpus gained after the 27 September capture;summary.inputs,sourceandsha256_of_recordsname the new export and audit. The records digestc493ba0e…is the one the 28 September re-run derived on a caught-up copy.The new population is committed in #240 (
candidates.json, and the README's population bullet), byte-identical to the file the backfill read.Block 3 (C3): the run without reviews, twice
DD_NO_OBAN=1 mix dd.routing.backfill --snapshot routing-input.jsonl --population candidates.json --manifest …on v2. Run key7008c6f3ddbf434a1538b724cf043d6de250fa2444ed8e76b274c7e32f4305e5.awaiting_review(108 draft pages), 41not_addressedclassification_decisions, 108pages, 170routing_backfill_items, 1routing_backfill_runs(+1 update,finished_at); 0public_pathspg_stat_user_tablesn_tup_ins/upd/delofpages,page_revisions,page_memberships,public_paths,classification_decisions,routing_backfill_runs,routing_backfill_items,entitiesandobjectsequal before and after (ledger-counters.log); the manifest byte-identical to run 1's77fa0849a3018d148def340f6c26f2f4dd8d9077698b0c96bf32aa756ca9392b(manifest-run1.json=manifest-run2.json). Itsinputsname the export, policy and population digests above;reviews_sha256: null;publication_approved: 0.evidence_changedorinput_changed, and none wasrefused. All 170 decisions are the evaluator's (originevaluator,reviewer_actor_idnull); every page isdraft,active, 106subjectand 2edition(the two editions of The Devil's Dictionary, as the rehearsal found);public_pathsis 0.The owner's review worksheet
review-worksheet.md,.csvand.jsonin the evidence folder: 129 rows, one per record awaiting review, in object-id order, each with object id, label, stored kind, proposed family, candidate families, proposed or blocked path, collision group, evidence fingerprint, page id, the internal link/entities/:id/:slug(made byRouting.Links.entity_path/2) and the description.defer/places/vik×2,/works/crocodile-tears×1)deferif one subject twice (a registry merge is outside the backfill), else the family and a distinct path (/works/love×3,/works/mona-lisa×2,/works/the-devils-dictionary×2)The 11 groups are the README's:
/works/butterfly19,/works/human15,/places/vik7,/places/mount-tom6,/people/billy-lee5,/works/love3, and 2 each for/places/daman,/organizations/the-creatures,/works/crocodile-tears,/works/mona-lisa,/works/the-devils-dictionary. The Markdown worksheet keeps each group together.One thing to know when deciding: 126 distinct fingerprints cover the 129 rows. The two editions (objects 3 and 6) share one, and the three Love works share one, because their evidence is identical. A review names the object id and the fingerprint, so this is not ambiguous, but it is also why the Love trio cannot be told apart from evidence alone.
Evidence
/Volumes/LLM Models/dictionary/private/2026-10-08-224/,SHA256SUMSregenerated:cp4-b2.sh(the steps),routing-input.jsonl,routing-audit/,candidates.json,candidates.out,population-diff.{py,json,out},test-candidates.out,backfill-run{1,2}.out,manifest-run{1,2}.json,ledger-counters.log,source-counters.log,db-after-run2.out,entity-links.json,worksheet.py,review-worksheet.{md,csv,json},steps.log. One export file taken at 13:08:54Z was discarded because the wrapper's timing stamp landed as its first line; the export was re-run at 13:09:30Z with the step fixed, and that is the one everything is bound to (steps.logrecords both).Stopped here. Block 4 writes only what the owner decides, per record, into a review file bound to population
c2cbd2ef…, each confirmation naming the fingerprint above, under the owner's reviewer account. The fivecp4_*scratch databases from block 1 are still on 5434 (48 GB), not dropped.Merge pull request #240 from razrfly/claude/224-population
holden commentedon Oct 8, 2026
Independent audit of blocks 2 and 3 (C2, C3), 8 October 17:40 (+02): both pass, grade A. #240 merged with its one-line fix. Block 4 is the owner's reviews
Read-only against
devils_dictionary_v2on 5434, the evidence folder and PR #240; nothing written to any database.Reproduced here
SHA256SUMSverifies, 0 mismatchesrouting-input.jsonl: 173,949 lines, SHA-256a33f1bc8…, the digest the audit, the population and the manifest all namecandidates.jsonin the evidence is byte-identical to the file on #240's head (c2cbd2ef…); 170 records, 11 groups,deferred_outside_population100,749 = 100,919 − 170;inputsname the export (a33f1bc8…), the audit (ee31ddd0…) and policy54695faa…1.0.0;selection_missing_from_audit: [],global_proposal_conflicts: 0; records digestc493ba0e…, the same the 28 September re-run derived on a caught-up copypopulation-diff.out: same 170 ids, same 11 groups, 14 records differ instored_kindonly (12 concept → work, 2 concept → event), the catch-up's own change; the summary differs only ininputs,source, the records digest and the deferred countledger-counters.log: before run 1 every routing table 0; after run 1classification_decisions170,pages108,routing_backfill_items170,routing_backfill_runs1 (+1 update,finished_at),public_paths,page_revisions,page_memberships0,entitiesandobjectsuntouched; before and after run 2 identical on every counter.manifest-run1.jsonandmanifest-run2.jsonare byte-identical (77fa0849…, 2,396 lines): 170 items, 129awaiting_review, 41not_addressed, 108 with a page, 0 with an address,inputsbinding export, policy and population,reviews_sha256: nulldraftandactive, none with a canonical; decisions 170, all current, none overridden: 112mapped, 55needs_review, 2excluded_source_page, 1identity_review;public_paths0,route_changes0; 1 run (7008c6f3…), 170 checkpoint rows, 129/41review-worksheet.csv129 rows (+ header),.md203 lines: object id, label, stored kind, proposed family, candidate families, proposed or blocked path, collision group, fingerprint, page id, internal link, description; grouped as the report says, the 11 collision groups kept togetherusers.id2); no client session on v2 but the auditor's; dev server booted out (nophx-4007agent, no listener on 4007), tunnel up answering 502, Postgres up; the fivecp4_*scratch copies still present, 48 GB#240
The PR changes two files, +23/−23: the population file and the stage-2 README's population bullet. CodeRabbit's one finding was right: the README still said 100,614 entities stay deferred, the 27 September remainder; on the caught-up corpus it is 100,749. I made that one-line fix on the branch and merged #240 with a merge commit, branch kept. Nothing else in the PR changes code.
Read, for the owner's benefit
Noted, none blocking
routing-input.jsonlandcandidates.jsonexactly as they are until block 4 is done: a byte's change makes a new run.Verdict: C2 and C3 accepted. Block 4 waits on the owner's decisions, transcribed by the session under
users.id2 and nothing else.holden commentedon Oct 8, 2026
The owner's decision for block 4, recorded 8 October 2026 at 18:30 +02 from the owner in chat with the steering session: My decisions are review-decisions-owner-draft.csv in the evidence folder, approved as written. The file sits in private/2026-10-08-224/ beside the worksheet, with its Markdown twin review-decisions-owner-draft.md: 124 confirm and 5 defer, each row naming the object id, the family and the path, nine of them with a path the owner names in place of the proposal. The executing session transcribes exactly that under users.id 2, each row with its fingerprint from the worksheet, regenerates SHA256SUMS to cover the two new files, and runs block 4 twice as C4 requires. The owner has also said that per-record review must not recur: a standing, owner-signed review rule is being added to the publication issue as a requirement before any second manifest.
holden commentedon Oct 8, 2026
CP4 blocks 4, 5 and 6 (C4, C5, C6): the owner's reviews run, the journey verified, the snapshot restored exactly. C7 is this record, #241 and the close
8 October 2026, on
main6d57a0c(#240 merged), ondevils_dictionary_v2(cluster 7693849764459364596, port 5434).DD_NO_OBAN=1on everymixtask. Nothing on 5432 was touched. Blocks 4 and 6 ran with the dev server stopped; block 5 ran with it up. The tunnel stayed up throughout, by the owner's waiver.Gate, re-checked before block 4
main6d57a0c=origin/main, cleanmix dd.doctor --expect-cluster 7693849764459364596 --volume "/Volumes/LLM Models"http_port4007 free (doctor-before-block4.out)source-counters.log,ledger-counters.logbefore-block4): nothing wrote to v2 between block 3 and block 4usersrow withreviewer = true:users.id2SHA256SUMSBlock 4 (C4): the owner's reviews, transcribed and run twice
The review file,
reviews-owner.json(SHA-25657e26405cce64fd8b05a1d79e3d811f85e91b0cd428a1862946cb07f7a987792), made bytranscribe-reviews.pyfromreview-decisions-owner-draft.csv(9a65149f…), the file the owner approved as written (comment):confirm, 5defer. Each row'saction,family,pathandreasonare the CSV's bytes; thereasonis the CSV'snote. Each namesevidence_fingerprintfromreview-worksheet.csvfor its object id (126 distinct, as the worksheet), and the reviewerissue84-browser@local.test,users.id2. The file bindspopulation_sha256c2cbd2ef…and records the run key and manifest it reviewed (7008c6f3…,77fa0849…).Backfill.loadwas run read-only first (preflight-load-reviews.out): the file loads, 129 reviews, run key9639fc28e445a579f656e426374569f4deeb734b55cc5229dacae00f4f1512b8.The runs,
DD_NO_OBAN=1 mix dd.routing.backfill --snapshot routing-input.jsonl --population candidates.json --reviews reviews-owner.json --manifest …(cp4-b2.sh backfill):allocated, 5deferred_by_review, 41not_addressed; 0refusedclassification_decisions(+124 updates: the superseded evaluator rows), 16pages(+124 updates: the canonical), 124public_paths, 248route_changes, 170routing_backfill_items, 1routing_backfill_runs(+1,finished_at);entities,objects,page_revisions,page_membershipsuntouchedpg_stat_user_tablescounter equal before and after (ledger-counters.log), the manifest byte-identicalmanifest-rev1.json=manifest-rev2.json, SHA-25612384745ff3b34bc2ef793e2a3f5e5e33a28cdd12dc564be0767873faee3fb6e. Itsinputsbind the exporta33f1bc8…, policy 1.0.054695faa…, populationc2cbd2ef…and reviews57e26405…;publication_approved: 0.manifest-check.py: every record agrees with the owner's CSV, 124 allocated at exactly the CSV's path and family, 5 deferred with no address, 41 not addressed; the evidence fingerprint unchanged on all 170 against the run without reviews, so no review was stale and nothing was deferred asevidence_changedorinput_changed.db-after-rev2.out: 2 runs; the reviewed run's 170 items 124/5/41; 0 refused in any run; 124public_paths, allcanonical; 124 pages, alldraftandactive, each with its canonical (122 subject, 2 edition); decisions 294: 124 superseded evaluator rows, 46 current evaluator rows (the 41 not addressed and the 5 deferred), 124 current overrides, every one by the actor ofusers.id2; every allocated path's page is the item's own object; the five deferred have no path and no override; no other client session on v2.manifest-check.out:familyandstatusdiffer from the run without reviews on 17 records).Block 5 (C5): the journey on the working dataset
The dev server was started under its LaunchAgent at 15:52Z (
config/dev.exs, internal reading on; the tunnel up by the owner's waiver). From the desktop app's built-in browser againstlocalhost:4007, recorded inc5-journey.md,c5-http-statuses.outandc5-screenshots/:/on/mars: "1 subject · 1 at their own address"; the one card Nature · Draft · Mars,/nature/mars/nature/mars: Nature · Draft · Mars, "On mars" back, Q111; About this address:/nature/mars, "subject page, a draft: not public", allocated 8 October 2026 by routing backfill (#194 Stage 2), "approved by reviewer #2 — classification review: sole candidate", "Nature, confirmed by Account #2 · policy 1.0.0", evidence21f2dbd22a89e815…/on/marsagain; a direct GET of/nature/marsis the same page, 200/people/ambrose-bierce(People · Draft, Q191050);/works/the-devils-dictionary(Works · Draft, Q1197843, editions: Project Gutenberg #972);/works/the-devils-dictionary-gutenberg-972(Works · Draft, 997 contents, "an edition of The Devil's Dictionary")/on/love: love Concepts · Draft/concepts/love, the three Love works "No public address yet";/on/cat: two addressed, two "Awaiting classification review", five "Unclassified";/on/human: 16 addressed, the disambiguation page "A source page, not a subject", seven awaiting review, "9 more with this name not shown"/define/*/define/mars,/define/)/entities/1831413/mars200, the exact-identity page;/entities/1831413/wrong→/entities/1831413/mars;/words/999999999/x404/nature/Marsand/nature/mars/301 →/nature/mars;/places/vik-sømna301 → its percent-encoded form, 200;/subjects/plan%C4%93200;/nature/marz404;/works/love404 (deferred, so nothing holds the bare path)Not demonstrable here: the public-mode "not yet public" card, because the development configuration turns internal reading on for every reader; #219 B6's tests cover it.
/entities/999999999/xanswers 200 with the exact-identity LiveView's own "no such thing" page, as before #219; the ADR's 404 for a missing id is/words/:id/:slug's, which it gives.Block 6 (C6): snapshot, restore, verify; precommit; the doctor; the server back
Server stopped at 15:57Z (no listener on 4007; no client session on v2 but the measuring one).
mix dd.snapshot --out scratch/dumps/v2-c6.dumpfd34a0bc…; the.routing.jsonsidecar records cluster 7693849764459364596, oid 16385, and the routing digests: 294 decisions, 124 pages, 124 paths, 248 route changes, 0 revisions and membershipsmix dd.snapshot --restore … --database devils_dictionary_cp4_c6DD_DATABASE=devils_dictionary_cp4_c6 mix dd.routing.verify --baseline devils_dictionary_v2verify-c6-vs-v2.{out,summary})31,130,738 / 15,618,722 / 2,480,244before the snapshot, after it and after the verify (source-counters.log); onlypg_stat_database's tup counters moved, by catalog maintenance, as in block 1devils_dictionary_cp4_c6dropped by name after the verifymix precommit(compile with warnings as errors, unused deps, format, the suite)precommit.out), on the code of6d57a0c(the working tree was then onclaude/224-close, which adds only docs); the tree clean afterwardsmix dd.doctordoctor-after-c6.out); the two optional warnings (.envrefresh seconds; the runtime service bound todevils_dictionary_runtime_bench) are the ones every earlier doctor in this issue reportedphx-4007agent bootstrapped at 16:02Z;/nature/mars200 on 4007 and the tunnel answering 200; thengrokagent running throughoutThe ledger counters were read again before the snapshot: unchanged since rev2 (294/124/124/340/2), so the server's block-5 window wrote nothing to the routing tables.
C7: the record
/Volumes/LLM Models/dictionary/private/2026-10-08-224/,SHA256SUMSregenerated over every file: block 4'stranscribe-reviews.{py,out},reviews-owner.json,preflight-load-reviews.out,backfill-rev{1,2}.out,manifest-rev{1,2}.json,manifest-check.{py,out},db-after-rev2.{sql,out}; block 5'sc5-journey.md,c5-http-statuses.out,c5-screenshots/; block 6'scp4-b4.sh,snapshot-c6.out,scratch/dumps/v2-c6.dump(+ sidecar),restore-devils_dictionary_cp4_c6.out,verify-c6-vs-v2.{out,summary},precommit.out,doctor-{before-block4,after-c6}.out, and the running logs.backfill.md,corpus-catch-up.mdwith step 4's finding, the stage-2 README, the README).Left as they were, for the owner: the five
cp4_*scratch databases from block 1 (48 GB on 5434), the pre-catch-up bundle, and thev2-c6.dump(1.2 GB) in the evidence folder. Publication, the standing review rule and the reviewer's tools are #237's.holden commentedon Oct 8, 2026
Independent audit of blocks 4, 5 and 6 (C4, C5, C6) and the C7 record, 8 October 18:18 (+02): all four pass, grade A−. One thing the report leaves out: the server writes to
v2whenever it is up. #224 may close; #241 may mergeRead-only against
devils_dictionary_v2on 5434, the evidence folder, PR #241, the dev server on 4007 (GET only) and the tunnel. Nothing written to any database; nothing posted; git untouched.Reproduced here
private/2026-10-08-224/SHA256SUMS+ the sums file);shasum -c: 123 OK, 1 FAILED:steps.log. Its recorded digestf1e975b2…is the file minus its last line, the 16:08:14Z "SHA256SUMS regenerated" entry appended after the regeneration. That is all. The posted block 4–6 comment is byte-equal toblock4-6-comment.mdreviews-owner.json(57e26405…)confirm/ 5defer; everyaction,family,pathandreasonbyte-equal toreview-decisions-owner-draft.csv(9a65149f…,reason= the CSV'snote): 0 mismatches; everyevidence_fingerprintthe worksheet's for that object id, 126 distinct; the 129 ids are exactly the CSV's and exactly the worksheet's; every review namesissue84-browser@local.test=users.id2, the onereviewer = truerow of the two users;population_sha256= sha256 ofcandidates.json=c2cbd2ef…; norehearsalkey at the top or on any review; it also recordsreviewed_run_key7008c6f3…,reviewed_manifest_sha25677fa0849…andtranscribed_fromthe CSV with its digest and the approval comment. Every confirmed path is NFC, lower-case, inside its family, distinct (124), and the family is within the record's candidate familiesrouting_backfill_runs9639fc28…,input_sha256a33f1bc8…, policy54695faa…1.0.0, populationc2cbd2ef…,reviews_sha25657e26405…= sha256 ofreviews-owner.json, 170 records, 15:51:25–27Z. Run 1:7008c6f3…, reviews nullrouting_backfill_itemsallocated/ 5deferred_by_review/ 41not_addressed; run 1: 129awaiting_review/ 41; 0refusedin any run. The five deferred carry the CSV's reason verbatim, no path, no pageledger-counters.logentities100,919 andobjects3,741,781 unchanged through all four readings.source-counters.log: after-rev1 = before-rev2 = after-rev2,31,129,266 / 15,618,464 / 2,480,243manifest-rev1.jsonandmanifest-rev2.jsonbyte-identical,12384745…;inputs= exporta33f1bc8…, policy54695faa…1.0.0, populationc2cbd2ef…, reviews57e26405…;publication_approved: 0; 170 records 124/5/41; every allocated record'saddressandfamilyequal the CSV's, every deferred has no address, none of the 41 is in the CSV;decided_byoverride 124 / evaluator 46; 122subject+ 2edition, alldraftv2nowpublic_paths124, allcanonical;pages124, alldraft+active, each with its canonical (122 subject, 2 edition);classification_decisions294 = 124 superseded evaluator + 46 current evaluator + 124 current overrides, every override'sreviewer_actor_id→ actor 5 →users.id2, and each supersedes its own evaluator row (124);route_changes248, allallocate, 124 operations, 15:51:26–27Z; for the 124 allocated items the path is canonical, the page's target is the item's object and the page's canonical is that path (124/124/124). The five deferred (3740879, 3734402, 3737584, 3739174, 3742759): 0 paths, 0 overrides, 0 pages, their current decision the evaluator'smappedv2Routing.Recoverydoes (sha256 overmd5(to_jsonb(row))+ newline, by id): decisions178c774a…, pages57746744…, paths2386404a…, route_changes8d31df15…, revisions and membershipse3b0c442…(empty): all six equalv2-c6.dump.routing.json. The routing ledger is byte-for-byte what C6 snapshottedc5-http-statuses.outidentical:/nature/mars200,/nature/Mars301 →/nature/mars,/nature/mars/301,/nature/marz404,/define/mars404,/define/404,/on/mars200,/entities/1831413/mars200,/entities/1831413/wrong302 →…/mars,/entities/999999999/x200,/words/999999999/x404,/works/love404,/people/ambrose-bierce200,/works/the-devils-dictionary200,…-gutenberg-972200,/places/vik-s%C3%B8mna200,/subjects/plan%C4%93200,/concepts/love200,/works/mona-lisa200c5-journey.mdsays: home →/on/mars"1 subject · 1 addressed", the one card Nature · Draft · Mars/nature/mars; the page with "On mars", Q111; About this address:/nature/mars, "a draft: not public", allocated 8 October 2026 by routing backfill, "approved by reviewer #2 — classification review: sole candidate", "Nature, confirmed by Account #2 · policy 1.0.0", evidence21f2dbd22a89e815…= the worksheet's fingerprint for 1831413;/works/the-devils-dictionaryWorks · Draft, Q1197843, editions: Project Gutenberg #972;/on/loveone addressed Concepts · Draft and three Works "No public address yet";/on/cattwo addressed, two "Awaiting classification review", five "Unclassified"v2-c6.dump1,254,411,129 bytes, SHA-256fd34a0bc…= the sidecar's; sidecar names cluster 7693849764459364596, oid 16385, port 5434, counts 294/124/124/248/0/0; 82 sdevils_dictionary_cp4_c679 s, exit 0;verify-c6-vs-v2.summary: 71 sections exact (every table,schema,sequences) + "routing: every path and page resolves the same" + "matches … exactly"source-counters.log: before-snapshot-c6 = after-snapshot-c6 = after-verify-c6 on user tables,31,130,738 / 15,618,722 / 2,480,244; thepg_stat_databasecounters moved as in block 1pg_databaselists 14:v2, the fivecp4_{b0,c1,pre,proj,s27}, the test and bench databases, postgres, the templates. Nocp4_c6mix precommitprecommit.out:19 doctests, 2658 tests, 0 failures, 342.4 s, exit 0 at 16:07:56Zmix dd.doctordoctor-after-c6.out: every core line green; the two optional warnings (.envrefresh seconds; runtime bound todevils_dictionary_runtime_bench) are the ones every earlier doctor reportedphx-4007agentrunning, pid 67812,beam.smplistening on 127.0.0.1:4007;ngrokagentrunning, pid 20468;https://wordhoard.eu.ngrok.io/200 and/nature/mars200 through itREADME.md,docs/routing/stage-2/{README,backfill,corpus-catch-up}.md); head1ad54a7is one commit on top ofmain6d57a0c; mergeable; CodeRabbit and GitGuardian green. Every number in its lines is one I reproduced (124/5/41, 122 + 2,c2cbd2ef…,9639fc28…, 100,919 at the export, 100,749 deferred by the population)handoff-194-comment.mda8d61b11…, populationc2cbd2ef…, runs7008c6f3…and9639fc28…, manifest12384745…, 124 pages (122 + 2), five deferred named right, 71 sections, the evidence path, #241, the two follow-upsmain=origin/main=6d57a0c; the tree onclaude/224-closeat1ad54a7= its origin,git statusclean; 11 client sessions onv2, all the server's pool (16:02:44Z,LISTEN "public.oban_insert"); the fivecp4_*copies present, 9.5 + 9.5 + 9.6 + 13 + 9.5 GBWhat the report does not say: block 5 wrote to
v2, and the server still doesThe dev server is
mix phx.serverunder the LaunchAgent, withoutDD_NO_OBAN, so Oban'sdiscoveryqueue runs. Browsing the journey admitted 39 discovery runs (DevilsDictionary.Discovery, "visit-driven cultural discovery … approved adapters may resolve an eligible result to a durable registry identity"; actor 6, Wordhoard automatic discovery). In the block-5 window, 15:52–15:58Z,v2gained 1,472 inserts, 258 updates, 1 delete on user tables (source-counters.log, after-rev2 → before-snapshot-c6): entities 74, objects 96, source_records 232, source_record_revisions 239, external_identifiers 133, work_details 68, source_materialized_outputs 100, discovery_results 245, discovery_mappings 36, discovery_runs 39, content_items 22, content_revisions 22, assertions 16, assertion_revisions 16, person_details 6, reconciliation_cases 1 (Mars imagery, Buzz Aldrin, The Cat in the Hat, …). The session's ownledger-counters.logrecords it (after-c6: entities 100,993, objects 3,741,877) and the verify summary carries the same counts; the comment says only that the window "wrote nothing to the routing tables", which is true, and nothing about the corpus.Since the restart at 16:02Z the queued jobs resumed and wrote again (entities +12, objects +24, source_records +88, external_identifiers +36, …): at my last reading the counters were
31,131,196 / 15,618,870 / 2,480,377, and two discovery jobs (2416, 2426) sitexecutingsince 15:56–57Z, orphaned by the boot-out. Todayv2holds 101,005 entities and 3,741,901 objects, not the 100,919 / 3,741,781 the blocks before block 5 were measured on.What this does and does not change:
v2as it was at 15:57:36Z, 74 entities past the baseline, the restore matched it exactly and nothing wrote between the snapshot and the verify. Butv2-c6.dumpis already behindv2, and the accepted baseline2026-10-08-v2(a8d61b11…) is the caught-up corpus before today's discoveries, not today'sv2. Neither document claims otherwise.The two C5 caveats, ruled
config/dev.exsturns internal reading on for every reader, so the "not yet public" card cannot be shown on this server without a configuration change; Pre-#211 delivery: accept the routing backfill, make On the main reading entry, and consolidate main for the storage move #219 B6's tests cover it. Accepted. Note that the public tunnel renders the drafts (I fetched/nature/marsthroughwordhoard.eu.ngrok.io: Draft, "a draft: not public"). That is the owner's recorded waiver, not a C5 failure; but Say CP4 ran: the reviewed population is backfilled on the working corpus as drafts (#224 C7) #241'sREADME.mdkeeps the line "A development server with drafts must not sit behind a public tunnel", which states the rule the waiver suspends. Fine as a rule; the owner knows the state./entities/999999999/x200. ADR 0004 §6's table says Unknown exact path/ID: 404, without name-based substitution or a label-only success page. A 200 "no such thing" page for an unknown id is not that; the report's reading that the prose's 404 is/words/:id/:slug's is only half the text. It predates Pre-#211 delivery: accept the routing backfill, make On the main reading entry, and consolidate main for the storage move #219, CP4 changes no code, and the behaviour for an existing id is as §6 says (200; a wrong slug 302 to the right one;/words/999999999/x404). C5 is met for what CP4 can show; the missing-id 200 is a small follow-up issue on the exact-identity route (ReadingStatusshould answer 404 before the LiveView), not a blocker.Noted, none blocking
db-after-rev2bullet says "no other client session on v2"; the file's last line says 11, because it ran at 15:53:36Z with the server already up (15:52Z). Harmless.executingsince 15:56–57Z, orphaned by the boot-out; Oban's rescue will retry them or they can be left. Nothing of routing depends on them.steps.loggained one line after the regeneration; the nextSHA256SUMSregeneration covers it.cp4_*copies (about 50 GB on 5434), the pre-catch-up bundle,v2-c6.dump(1.2 GB). The snapshot is the last state taken with the server down; the owner decides whether it or2026-10-08-v2is the rollback point from here.dd.routing.verify --projected;ANALYZEafter a restore; and now the/entities/:id404.Verdict: C4, C5, C6 and C7 accepted; grade A− (the execution reproduces exactly; the record left out the one thing its own counters show). #224 may close with this comment on it. #241 may merge as it stands.
Merge pull request #241 from razrfly/claude/224-close
holden commentedon Oct 8, 2026
Closed, 8 October 2026: C1–C7 met, each block independently audited
2026-10-08-v2(a8d61b11…) — audit, grade A.c2cbd2ef…, Re-derive the Stage 2 population from the caught-up corpus (#224 C2) #240) and C3 the run without reviews, twice — audit, grade A.users.id2, run twice (run9639fc28…): 124 addresses allocated as drafts, 5 deferred, 41 not addressed, 0 refused; the candidate launch manifestmanifest-rev1.json(12384745…). C5 the journey verified on the working dataset. C6 snapshot restored and verified exactly, precommit 2,658 tests / 0 failures, doctor green, server and tunnel back. C7 evidence underprivate/2026-10-08-224/withSHA256SUMS, docs in Say CP4 ran: the reviewed population is backfilled on the working corpus as drafts (#224 C7) #241 (merged,f9c653f), the handoff on #194 — audit, grade A−.The audit's one finding is on the record: the working corpus is live under the dev server's discovery queue and moves whenever the server is up (101,005 entities at the close, against the 100,919 the blocks ran on); the routing ledger and the population's evidence do not move that way. Left for the owner: the five
cp4_*scratch copies (about 50 GB on 5434), the pre-catch-up bundle,v2-c6.dump, and the choice of rollback point. Publication, the standing review rule and the reviewer's tools: #237. Follow-ups named on #194: natural-key matching indd.routing.verify --projected,ANALYZEafter a restore, a 404 for an unknown id on/entities/:id/:slug.holden commentedon Oct 9, 2026
Steering session's re-verification of the close, 9 October 2026: the close stands. #224 as a whole: A−
Read-only against
devils_dictionary_v2on 5434, the evidence folder, the server on 4007 (GET only), the tunnel and GitHub, after the second auditing session's block 4–6 audit (A−) and the close. Nothing written.Reproduced
f9c653f(README and three stage-2 docs, +11/−11); the handoff on #194 at 16:21Z;main=origin/main=f9c653f, cleanSHA256SUMS, 0 mismatches;v2-c6.dump1.25 GB underscratch/dumps/; 7 journey captures underc5-screenshots/plus the HTTP status tablereviews-owner.json: 129 reviews, 124 confirm / 5 defer, bound to populationc2cbd2ef…, no rehearsal flag, reviewerusers.id2 (actor 5); compared row by row withreview-decisions-owner-draft.csv: 0 mismatches, no row missing, every confirmation carries its fingerprint9639fc28…,reviews_sha256set, finished): 124allocated, 5deferred_by_review, 41not_addressed; manifestmanifest-rev1.jsonbinds export, policy, population and reviews,publication_approved0allocateledger rows (a path row and a page row each), no other operation; 124 draft pages (122 subject, 2 edition), every one with its canonical; decisions 170 current = 124 mapped overrides by actor 5 + 5 mapped evaluator (the deferred) + 38 needs-review + 2 excluded + 1 identity review, with 124 superseded evaluator decisions kept as history; every owner-named path present (/works/the-devils-dictionary-gutenberg-972,/works/johnsons-dictionary-1755-leme-transcription,/organizations/martins-famous-pastry-shoppe,/places/vik-sømna,/places/vik-grimstad,/works/crocodile-tears-novel,/works/the-devils-dictionary,/works/mona-lisa)/nature/mars,/people/ambrose-bierce,/works/the-devils-dictionary,/works/mona-lisa,/on/mars200;/places/vik-sømna301 to its canonical encoding;/works/love(deferred) 404;/define/love404; through the tunnel/nature/mars200, by the owner's waiverphx-4007(pid 67812),ngrok, Postgres all under their LaunchAgentsConfirmed findings
/entities/<unknown id>/<slug>answers 200, where ADR 0004 §6 says 404 with no name-based substitution. A small fix; it is on Routing before launch: On overviews, standards-informed namespaces, and stable subject URLs #194's follow-up list and should land with Routing: everything left to close #194 — Stage 5 publication behind a feature flag, then the reviewer tool (after #224) #237's first PR.devils_dictionary_testdatabase was created on 5434 at 18:02 (+02), block 6's precommit: a run withoutMIX_TEST_PARTITION. Harmless on the dictionary's own cluster, but the rule is a private partition on every run; drop it with the scratch copies.Left on the installation, the owner's to decide
Five
cp4_*scratch copies (about 51 GB on 5434) and the stray test database: drop by exact name. The pre-catch-up bundle (external only) andv2-c6.dump: keep one as the rollback point for #237's publication run, or take a fresh bundle then, which is the better choice given finding 1.Verdict: the close stands. #224 as a whole is A−: every block proved before it was trusted and reproduced by two auditors; the minus is the 200 on an unknown entity id, the unpartitioned test run, and that the launch population's review had to be read row by row by a human once, which #237's standing rule exists to end.
The launch manifest the signed rule generates from #224's candidate m…
Hide the operator surfaces from the tunnel and refuse it outright whe…