admin
3ea8f02d55
- Update ACTION_SYSTEM_ARCHITECTURE.md to describe the active-position contract and visual lifecycle proof - Mark BUILD_IN_PUBLIC_PLAN.md systems-gate section complete - Mark LEARNING_ROADMAP.md architecture-gate section complete and renumber post-gate implementation sequence - Update PROJECT_CONTEXT.md immediate-milestone section to reflect completed gate and next food-loop milestone - Update SIMULATION_STATE_SCHEMA.md with NPCStateRecord v2 details - Update ADR 0001 checklist to mark active-position sync done
Documentation map
The project uses a small hierarchy so overlapping plans do not become competing sources of truth.
PROJECT_CONTEXT.mdis the canonical description of the vision, current implementation, target architecture, and active constraints.LEARNING_ROADMAP.mdowns milestone order, architecture gates, reusable-system exit tests, and intentionally deferred work.BUILD_IN_PUBLIC_PLAN.mdowns the scoped Jajce visual slice. It must respect the architecture gates in the learning roadmap.RESOURCE_NODE_MIGRATION.mdis a focused migration plan. Phases 1–4 are complete; its Phase 5 hands world placement to the visual-slice plan.ACTION_SYSTEM_ARCHITECTURE.md,SIMULATION_DEFINITIONS.md, andSIMULATION_STATE_SCHEMA.mddocument the current data contracts.decisions/contains durable architectural decisions, including consequences and revisit conditions.
When documents disagree:
- code and tests describe current behavior;
- the newest accepted decision record governs architecture;
PROJECT_CONTEXT.mdgoverns product intent;LEARNING_ROADMAP.mdgoverns 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.