PR-129-Empty-Fingerprints: prose relabelling, what stays empty, operator order Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
PR-129-Empty-Fingerprints (pending merge) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Record #119 search provenance; describe the search tables in Design, Data safety and Migration
Records for #58 references and citations, #59 text refresh, #60 Crossref reference lists Design gains the reflist and references stages and refresh-text; Data safety gains the rule refresh-text follows when it writes corpus text. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
PR-54: the sync, prose-only articles synced from passages' text
PR-54: meta-analyses stored as level meta, and the Neurostore fix
PR-54: prose split into passages and prose, metadata between; the corpus run and upload
PR-54: third fine-tune round
PR-54: end-to-end on the test split only; second fine-tune round
PR-54: a model call does not beat the resolve rule
Record #54: coordinates in prose
PR-51: coordinate space from the text; stage order in Design
Record #29: keep every table, and what it did to the corpus
Describe one-extraction-per-article Living-page edit for the change that stops extract fanning out over every source an article was downloaded from.
Describe merge hand-over and the ready column Living-page edit for the follow-up that fixed artifact hand-over on merge and added a ready count to status.
Point at AGENTS.md for whether a change earns a record The threshold now lives in the repo where agents read it; this page keeps the layout rules so the two cannot drift.
Separate living pages from per-change records The first cut named every page generically -- Design, Benchmarks, Profiling. Since the wiki namespace is flat, the second change wanting a Benchmarks page would have had nowhere to put it. Two kinds of page now: Living, describing the system as it stands, edited by each change: Design, Data-Safety, Migration Frozen records of one change, prefixed so the next one can sit beside them: PR-11-Catalog-Refactor, PR-11-Before, PR-11-Benchmarks, PR-11-Profiling Changes indexes the records and says how to add one.
Document the catalog refactor Moves the prose from the PR's docs/ directory into the wiki, with a parent page for the change and one page per document. GitHub wikis are flat -- a file in a subdirectory is served at its bare page name -- so the hierarchy is expressed by _Sidebar.md and by links from the parent page. Relative links between documents become wiki links; links into the source tree become blob URLs on refactor/catalog-and-stages.
Remove nesting probe
Probe: does a subdirectory render as a nested wiki page?
Initial Home page