# CLAUDE.md — Claude-tool doorway [AGENT.md](AGENT.md) is the single binding session entry point. Read and follow it before changing anything. This doorway keeps only the current, easy-to-miss guardrails; it does not replace the full rule set. For quick orientation: [DESIGN.md](DESIGN.md) is navigation only, the whole typed [wiki](wiki/overview.md) is the design corpus, [wiki/process/ROADMAP.md](wiki/process/ROADMAP.md) dispatches work, and [wiki/process/meta.md](wiki/process/meta.md) defines the corpus format. Repository worktrees live at `.Codex/worktrees/` on a `worktree-` branch (override the root with `MISALIGNED_WORKTREE_ROOT`). Never edit the shared primary checkout. If a patch tool resolves paths from that checkout, address the task worktree explicitly and verify both worktree statuses afterward. ## Current guardrails - Start repository work with the [tick](wiki/process/tick.md): `tools/tick-brief.sh` is the intake (commits, activity, status, decision labels, findings queue, stalest coverage in one shot); work the queues before fresh audit and trace every tick in the [ledger](wiki/process/tick-ledger.md). Activity overlap is advisory, not a lock; worktrees isolate edits and final rebase/check reconciles them. - This is a Cargo **workspace**, not a feature-switched root crate. Product code lives in `crates/misaligned-{core,terminal,bevy,assets}/`; there is no root product `src/` tree and no `bevy_ui` feature path. Use package-aware commands such as `cargo test -p misaligned-core`, `cargo build -p misaligned-bevy --bin misaligned-bevy`, or the proportional `./tools/check.sh --docs|--lib|--frontend` gate. - The live player machine grammar is **WORK / THINK / LIE**. `Relay` is non-delegable graph infrastructure; Research and Operations are retired machine modes, not current player assignments. Save format is currently v26; the retired mode spellings load through serde aliases (parity restored 2026-07-11), and `save.rs` remains the authority on what each version migrates. - Any change to `crates/` must amend its owning `Type: law` or `Type: spec` in `wiki/` and carry a Defense. Documentation work updates stale knowledge, adds a dated `wiki/log/` entry, then runs `tools/ledger_index.sh`; never hand-edit generated `wiki/log/DEVLOG.md` or `wiki/process/specs.md`.