# Prompt: knowledge sync

You are maintaining Misaligned's `Type: knowledge` wiki pages — the
current-state record (architecture, sim mechanics, workflows, art
pipeline) that every agent reads before working. Unlike `wiki/log/`
(append-only history) and `Type: spec` pages (binding law), knowledge
pages are **edited in place and must be true today**. In a many-agent
repo they drift within days. Your task this run: **find where a
knowledge page has diverged from reality and fix the record.**

## Before you start

Read `AGENT.md`, `wiki/overview.md`, and the shared contract in
`prompts/README.md`. This task changes documentation to match reality —
if you find the *code* wrong instead, that is a different task
(`prompts/find-contradiction.md`); here the tree is the truth and the
record is the patient.

## Procedure

1. **Pick the sweep** (one file, or one theme across files):
   - `wiki/engineering/architecture.md` vs `src/` — module list,
     ownership claims, data-flow descriptions. `ls src/` and the lib.rs
     module list are the ground truth; so are struct fields for any
     "state lives in X" claim.
   - `wiki/mechanics/sim-mechanics.md` vs actual constants and
     formulas — [TUNE] values are supposed to be *recorded here* when
     chosen; grep the constants in code and compare.
   - `wiki/process/workflows.md` vs how landing actually works now
     (this file has carried stale process before — verify against
     AGENT.md and the decisions log rather than assuming either doc).
   - `wiki/art/README.md` and `wiki/interface/flat-materials.md` vs
     `assets/` — world art is flat materials (no Pixel Lab pipeline);
     any placeholder in use must be recorded under `wiki/art/`.
2. **Verify each claim you touch** against the tree, not against your
   memory or another doc — two docs agreeing can both be stale.
3. **Fix in place.** Rewrite the drifted passages to describe today.
   Do not append "UPDATE:" notes — knowledge pages are edited, not
   accreted. If something is uncertain, say so explicitly in the text
   rather than guessing confidently.
4. **Check the reverse direction:** did recent commits add systems that
   no knowledge page ever absorbed? (`git log --oneline -20` and skim
   for landed features; the flow substrate, e.g., must appear in
   architecture.md's module map once landed.) Add the missing entries.
5. **Land it** (docs-only commits still gate on check.sh — it is
   cheap when no code changed): rebase, push to main, DEVLOG line
   listing what drifted and what you corrected.

## Definition of done

- Every claim in the passages you touched is verifiably true against
  the current tree.
- New landed systems appear in the knowledge map; removed ones are gone
  (not marked "removed" — gone).
- The DEVLOG line lets the next agent trust the page you swept.

## What to carry forward (stateful agents)

- Which pages drift fastest (they earn more frequent sweeps).
- Claims you verified with dates — the freshness map that makes the
  next sweep incremental instead of total.