context-anchoring

# Context Anchoring ## Scope > Feature-level only — anchors decisions as a feature flows from design → implementation → bugfix → refactor. ## Config Resolution Skill manage dir of per-feature context docs. Resolution order: 1. Look `.lattice/config.yaml` in repo root 2. If found, check `paths.context_base` for custom dir path 3. If custom path exist, use that dir for context docs 4. If no config/path/path not found, use default `.lattice/context/` Each feature get one doc at `<context_base>/<feature-name>.md`. No default principles, no overlay modes, no override files -- just thin template and per-feature docs that grow through enrichment. ## Problem AI no persistent memory. Context decay real: by message 30+, early decisions contradicted, naming inconsistent, "why" evaporate. Damage compound -- forgotten decision become potential contradiction, lost constraint become violation, unresolved question become silent assumption. Context anchor docs solve: - **Feature-bound** -- one doc per feature, scoped decisions only - **Decision-focused** -- capture what, why, what-else-considered for every choice - **Append-only** -- decisions never removed/rewritten, only added chronologically - **Session-spanning** -- doc outlive conversation, carry context forward - **Git-native** -- live in repo, versioned alongside code Two docs per feature: **requirement doc** (static, written upfront, not managed by this skill) and **context anchor doc** (living, evolving, managed by this sk...