Maintaining This Wiki

Maintaining this wiki

Back to Home. Related: Operations-Memory, Development-Workflow.

This wiki is the primary knowledge base for the project — the first thing to read at session start and where durable learnings are recorded. It is a GitHub project wiki (repo.wiki.git) checked out at .wiki/, separate from the main repository.

How to use it

1. Start at Home; follow [[WikiLinks]] to the topic you need.
2. For exact, current facts, follow each page's "Canonical source" links to CLAUDE.md, docs/*, and GitHub issues — the wiki is a map, not the source of truth.
3. Treat anything with a date, version, or cluster ID as possibly stale; re-verify live infrastructure and GitHub state before mutating anything.

Where new knowledge goes

• Durable project or operational learning → append to the most relevant existing page (usually Operations-Memory, Deployment-and-Security, or Development-Workflow). Keep entries short and actionable; link the detail.
• Large runbooks / verbatim grammar probes → keep in the Claude native memory archive (~/.claude/projects/-Users-Workspaces-acm-altinity-sql-browser/memory/) and add a one-line index entry under Operations-Memory. That archive is the deep-detail layer; the wiki distills it.
• Settled architecture or decision → Decisions-and-Roadmap and the relevant ADR under docs/.

Keeping it honest

• Every page ends with a "Canonical source" pointer; keep those accurate.
• When the native archive gains or loses a file, update the index list in Operations-Memory so the two stay in sync.
• .wiki/ is not committed to the main repo (it is gitignored there). Push wiki changes to the wiki remote, not the code repo.