admin c690937afa docs: update architecture gate progress
BUILD_IN_PUBLIC_PLAN.md:
- Mark systems gate items deterministic clock and headless checksum
  as complete; remaining gate work stays flagged as in-progress
- Rename TaskZone references to ActivityMarkers for consistency

LEARNING_ROADMAP.md:
- Add architecture gate progress note: first deterministic slice
  (SimulationClock, seeded streams, headless checksum) is implemented
- Update recommended implementation order to reflect shifted priorities

PROJECT_CONTEXT.md:
- Note that farm and forest markers have been deleted from main.tscn
- Update activity marker description (4 remaining: guard/study/rest/food)
- Add SimulationClock.gd and deterministic_simulation_test.gd to repo map
- Update technical debt: randomness is now seeded but RNG state is not
  yet serialized; clock is explicit but orchestration still lives on scene tree
- Gate status updated with completed first-slice summary

RESOURCE_NODE_MIGRATION.md:
- Mark Phase 4b (player parity) complete
- Phase 6 renamed from 'remove zone model' to 'replace activity markers'
  with progress note: TaskZone container and FarmZone/ForestZone deleted
- Update divergences to note farm/forest scene nodes have been removed
2026-07-05 11:23:19 +02:00
2026-07-04 21:06:57 +02:00

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. LEARNING_ROADMAP.md owns milestone order, architecture gates, reusable-system exit tests, and intentionally deferred work.
  3. BUILD_IN_PUBLIC_PLAN.md owns the scoped Jajce visual slice. It must respect the architecture gates in the learning roadmap.
  4. RESOURCE_NODE_MIGRATION.md is a focused migration plan. Phases 14 are complete; its Phase 5 hands world placement to the visual-slice plan.
  5. 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.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.

S
Description
No description provided
Readme 48 MiB
Languages
GDScript 86.6%
GDShader 9%
PowerShell 2.4%
Shell 2%