Documentation map

The project uses a small hierarchy so overlapping plans do not become competing sources of truth.

1. PROJECT_CONTEXT.md is the canonical description of the vision, current implementation, target architecture, and active constraints.
2. ARCHITECTURE_OVERVIEW.md is the concise map of runtime ownership, folder responsibilities, and dependency rules.
3. LEARNING_ROADMAP.md owns milestone order, architecture gates, reusable-system exit tests, and intentionally deferred work.
4. BUILD_IN_PUBLIC_PLAN.md owns the scoped Jajce visual slice. It must respect the architecture gates in the learning roadmap.
5. RESOURCE_NODE_MIGRATION.md is a focused migration plan. Phases 1–6 are complete; follow-up work should expand resource discovery without reintroducing abstract resource zones.
6. ACTION_SYSTEM_ARCHITECTURE.md, ECONOMIC_EVENTS.md, FOOD_STORAGE_ARCHITECTURE.md, SIMULATION_DEFINITIONS.md, and SIMULATION_STATE_SCHEMA.md document the current data contracts.
7. decisions/ contains durable architectural decisions, including consequences and revisit conditions.
8. benchmarks/ contains reviewed, workload-specific performance ledgers and their machine-readable samples. Measurements are local evidence, not portable CI limits.

When documents disagree:

• code and tests describe current behavior;
• the newest accepted decision record governs architecture;
• PROJECT_CONTEXT.md governs product intent;
• LEARNING_ROADMAP.md governs what should be built next;
• focused plans govern only their stated scope.

Update the smallest relevant set of documents after a decision or milestone. Do not copy full status tables into every plan.