maintain-codex-wiki

Maintain Codex Wiki

Overview

Maintain a repository-local Markdown wiki as compiled engineering knowledge, not as an automatic source of truth. Preserve provenance, separate evidence classes, and require review before wiki conclusions become repository rules, skills, or learning material.

When to Use

• Query what a repository already knows about a technical decision or practice.
• Capture a durable lesson from a merged change, incident, review, or experiment.
• Ingest external research without silently treating it as authoritative.
• Reconcile conflicting or superseded guidance.
• Check wiki structure, citations, freshness, and index coverage.
• Promote verified knowledge into a rule, skill, module, or automated check.

Do not invoke this workflow merely because a task produced code or chat output. No material wiki change is a valid result.

Knowledge Contract

Use a knowledge/ directory with these minimum surfaces:

knowledge/
├── index.md
├── log.md
├── sources.json
├── decisions/
├── experiments/
└── topics/

Each wiki page starts with one allowed status: verified, community, experimental, or decision.

# Article title

> Status: <verified|community|experimental|decision>
> Last verified: YYYY-MM-DD
> Sources: `source-id`, `another-source-id`

Choose the status from the evidence and operation. Capture and Archive pages def