Wiki Brain Operating Model

The wiki should behave like a compiled brain: coherent articles, stable retrieval, generated inventories, explicit provenance, and routing that makes the next edit obvious.

This is the shape spec for broad wiki changes. Read it before consolidation, recategorization, page creation, or any rewrite that could change the graph. Then use Filing Decision Tree for directory placement.

For corpus-wide merge, fold, archive, redirect, regeneration, split, or deletion work, use Wiki Corpus Refactor Program. This page defines the desired brain shape; the refactor program defines how the existing corpus migrates without losing evidence or retrieval. Source: User request, 2026-07-15

The durable unit is not a captured thought, source, skill, or folder path. The durable unit is a coherent mental object: a page, section, ledger row, generated view, or redirect that future agents can retrieve and update without reconstructing the original chat.

Current Brain State

The current wiki is no longer just flat article pages. It has canonical synthesis pages, operational protocols, a typed brain graph, workflow manifests, generated skill/source views, identity/cadence extractions, and redirect ledgers. The filing model has to account for all of them. Source: User request, 2026-08-10

Thesis

Flatten meaning. Use folders to clarify ownership, not to manufacture ontology.

A good wiki page should be useful to a human reader and to an agent. It should explain what is true now, preserve why we believe it, and make the next action obvious. If a page only exists because a source was captured once, it is probably the wrong shape.

Design Targets

Brain Architecture

The raw source archive, compiled wiki, user/interaction memory, and session/run state are separate owners. The wiki precomputes durable synthesis so agents do not rediscover structure on every query. It does not replace exact source retrieval, and it does not automatically remember Kevin's later correction, a rejected approach, or a workflow outcome unless those interaction facts are explicitly written to the scoped operating graph. Source: X/@hwchase17, “Wiki Memory,” 2026-06-30; X/@mem0ai, “The State of Agent Wikis,” 2026-07-21

Page Layers

Category Shape

Use Filing Decision Tree for final placement. This model describes why the placement exists.

Everything else should justify itself. If a category mostly contains stubs, fold those stubs into a stronger article, ledger, timeline, or generated view.

Flattening Rule

Prefer a strong article with sections and decision tables over a deep tree of thin pages. Use subfolders only when they improve browsing, enforce generation boundaries, or preserve a mature domain.

Good reasons for subfolders:

• Generated namespaces such as wiki/skills/<category>/ and wiki/agent-docs/.
• Resolver companion pages that provide retrieval handles but point back to canonical authority.
• Identity/cadence expansions that keep boot files readable.
• Asset provenance and media groupings.
• Mature domains with multiple real standalone articles.

Folders are navigation. Identity lives in canonical slugs, titles, aliases, redirects, and qmd retrieval.

Article Standard

Every canonical article should include the subset of these sections that helps the topic:

Small pages do not need every section. Long pages need enough structure to be scanned.

Combining Rule

When merging pages, preserve ideas by changing their form:

No idea gets deleted because it is small. It gets promoted, folded, generated, or redirected.

Rewrite Procedure

1. Pick a cluster, not a pair of pages.
2. List pages, aliases, source files, skills, tools, workflow bindings, graph objects, and redirects in the cluster.
3. Choose the canonical article owner.
4. Move useful claims into the owner as sections, rows, matrices, or timeline entries.
5. Preserve source trails, citations, dates, and embeds.
6. Add aliases for old titles.
7. Add redirects for retired slugs.
8. Update wikilinks when the old link should no longer resolve through redirects.
9. Regenerate indexes, qmd, registries, graph projections, and audits.
10. Log the rewrite.

Promotion And Demotion

Validation Loop

After any structural rewrite:

npm run build-index
npm run wiki-quality
npm run routing-doctor
npm run brain
npx tsx scripts/doctor.ts --quiet
qmd update && qmd embed

Use npm run wiki:resolve -- <old-slug> to verify retired names still land on the intended article.

---

Timeline

• 2026-07-15 | Linked the shape model to Wiki Corpus Refactor Program so compaction, merge, fold, deletion, redirects, and retrieval/privacy proof have one migration owner. Source: User request, 2026-07-15
• 2026-08-10 | Aligned the compiled-brain model with typed goals, loops, durable objects, workflows, sources, proof, and callable graph APIs. Source: User request, 2026-08-10
• 2026-08-10 | Clarified that compiled wiki knowledge, user/interaction memory, raw sources, and session state are separate planes, and added goal/output effect as a page-shape criterion. Source: X/@hwchase17; X/@mem0ai; X/@thedankoe
• 2026-07-01 | Added Generated Surface Contract as the explicit source/projection layer for generated pages, registries, qmd, redirects, and stateful ledgers. Source: User request, 2026-07-01
• 2026-06-27 | Established the wiki brain operating model after the skill-source folder work revealed the larger need: flatten meaning, combine weak articles, keep generated inventories generated, and make the brain readable to humans and agents. Source: User request, 2026-06-27