How to Update the Wiki

Updating the wiki means updating durable knowledge, graph structure, machine indexes, and operation history.

This is the practical update guide. AGENTS.md remains the root contract. The meta pages linked here hold the specialized details. Source: AGENTS.md; Agent Operations Hub

When To Update

Update the wiki when a session creates durable knowledge:

Kevin says "remember this", "add it", or similar.
A new project, person, tool, concept, decision, or philosophy appears.
A debugging session reveals a reusable lesson.
A convention or protocol changes.
A skill, automation, rule, hook, or config changes.
A query answer becomes reusable enough that future agents should not re-derive it.
A source in raw/ is compiled.

Do not update the wiki for purely ephemeral context unless Kevin asks.

Direct Write Flow in `kevin-wiki`

Choose the durable shape. Use Wiki Brain Operating Model.
Route the content. Use Filing Decision Tree.
Search for duplicates. Use Entity Identity Protocol.
Read the nearby graph. Read existing related pages before writing.
Write or update pages. Follow Wiki Page Format.
Apply quality gates. Citations, links, timeline, routing, and backlinks.
Update action surfaces. Capability Routing Map, SKILL-RESOLVER, Active Stack (What to Actually Use), harness projections, or config when behavior changes.
Refresh generated surfaces. Use Generated Surface Contract for indexes, qmd, packs, registries, redirects, and stateful ledgers.
Log. Append wiki/log.md.
Absorb. If source came from raw/, update _absorb_log.json.

If You Are Outside This Repo

If the current workspace is not kevin-wiki, do not silently edit some other copy. Propose the update:

Wiki update: I would add this to [[page-name]].

Target file: wiki/<category>/<slug>.md
Change type: new page | update section | timeline entry | routing update

Draft:
...

If Kevin asks you to apply it and the wiki repo is accessible, switch to the canonical checkout path ~/Documents/GitHub/kevin-wiki.

Page Creation Minimum

A new page needs:

required frontmatter
a one-line summary
compiled truth with a point
citations
related links
timeline when required
index/qmd/log updates

An orphan stub is not a completed page.

Skill and Automation Updates

When updating executable agent behavior:

skill body: skills/{engineering,productivity,personal,misc,in-progress,deprecated}/<slug>/SKILL.md
skill registry: Skill Registry (npm run skill-registry)
family synthesis: wiki/concepts/*-skills.md when durable routing or concepts change
routes: wiki/meta/capability-routing-map.md + wiki/SKILL-RESOLVER.md
active recommendation: Active Stack (What to Actually Use)
compact routing: harness projection files such as config/cursor/rules/tool-hierarchy.mdc
validation: bash scripts/sync-skills.sh --check, npm run routing-doctor, npm run trigger-eval

When creating automations, follow Automation Schema and update AGENTS.md if the inventory changed.

Writing Standard

Write like a reference work:

flat, factual, direct
no hype or peacock prose
lead with the key insight
organize by theme
use [[wikilinks]]
cite facts inline
split only on topic boundaries

Done Checklist

Correct page location
Duplicate/entity search done
Citations added
Related pages linked
Backlinks added when meaningful
Routing updated if behavior changed
Generated surfaces refreshed through Generated Surface Contract
wiki/log.md appended
Raw source marked absorbed if applicable

Timeline

2026-07-01 | Updated the wiki write flow to choose durable shape before filing and to refresh generated surfaces through Generated Surface Contract. Source: User request, 2026-07-01
2026-06-18 | Rewrote as a practical update guide with direct-write flow, outside-repo proposal format, page minimum, skill/automation update rules, and done checklist. Source: User request, 2026-06-18; AGENTS.md
2026-04-06 | Initial update guide created. Source: AGENTS.md

Source: User request, 2026-07-01

Source: AGENTS.md