Index Logging Protocol
After wiki operations, persist three machine surfaces:
_index.md,log.md, and qmd search state.
Routing
Open this page at the end of any substantive wiki edit, ingest, routing change, skill registry/family change, or automation update. It is the closeout route for making changed knowledge discoverable to the next agent. Open Generated Surface Contract when the question is which source file owns a generated page or ledger.
The wiki is only useful if agents can find what changed. Human-readable pages are not enough; the catalog, backlinks, search index, and chronological log must also agree. Source: AGENTS.md Indexing and Logging
Surfaces
| Surface | Role | How updated |
|---|---|---|
wiki/_index.md |
Content catalog by category | npx tsx scripts/build-index.ts |
wiki/_backlinks.json |
Typed inbound link graph | npx tsx scripts/build-index.ts |
Root README.md stats block |
Repository stats between auto markers | npx tsx scripts/build-index.ts |
wiki/log.md |
Append-only operation history | manual append by agent |
| qmd index | Local search / semantic retrieval | qmd update && qmd embed |
state.json |
Automation and sync timestamps | scripts and automation runners |
wiki/meta/wiki-redirect-index.md |
Generated retired-slug lookup | redirect generator / wiki/meta/wiki-redirects.json |
agent-docs/packs/*.md |
Portable agent context | npm run agent-packs:refresh when source pages or routing changed |
Generated Surface Contract is the authority for source/projection ownership and the closeout bundle to use when these surfaces change together.
Standard Wiki-Write Footer
After substantive page edits:
npx tsx scripts/build-index.ts
qmd update && qmd embed
After structural, routing, skill, or generated-pack changes, also consider:
npm run routing-doctor
npm run agent-packs:refresh
npm run agent-packs:check
npx tsx scripts/doctor.ts --quiet
Then append:
## [YYYY-MM-DD] operation | Short Title
Summary of what changed, why, and which pages were created or updated.
Pages created: N. Pages updated: N.
When README Narrative Must Change
build-index updates only the stats block. Manually update root README.md narrative when:
- directory layout changes
- setup commands change
- automation inventory changes
- sync or ingest flow changes
- agent bootstrap behavior changes
Log Quality
Good log entries are short but reconstructable. Include the user-visible intent, the pages touched, and validation commands. Do not paste full diffs into the log.
Merge And Redirect Closeout
When a page is moved, merged, or folded:
- Preserve useful aliases on the survivor.
- Add retired slug entries to
wiki/meta/wiki-redirects.jsonwhen lookup value remains. - Regenerate Wiki Redirect Index if the redirect ledger changed.
- Verify one old slug with
npm run wiki:resolve -- <old-slug>when practical.
Timeline
- 2026-07-01 | Linked generated-surface ownership to Generated Surface Contract so this page owns closeout sequence while the new contract owns source/projection boundaries. Source: User request, 2026-07-01
- 2026-07-01 | Added generated-pack, redirect, and structural closeout surfaces so filing changes update every machine-readable brain surface. Source: User request, 2026-07-01
- 2026-06-18 | Expanded index/log protocol with all persistence surfaces, standard command footer, README narrative rule, and log quality bar. Source: User request, 2026-06-18; AGENTS.md
- 2026-05-31 | Meta page compiled from AGENTS.md indexing and logging section. Source: AGENTS.md