Files
settled-reach/docs/briefings/dudley.md
T
jpmschweitzerandClaude Opus 4.6 cff4c74d75 docs(briefings): update all briefings for decisions split and DEVOPS.md
Update Key Documents sections to reference decisions/ directory instead
of monolithic DECISIONS.md. Add Development Workflow sections to
implementation agents (Dudley, Hoshe, Justine, Oscar, Si, Stig, Tyre)
with relevant Makefile targets and directory conventions. Streamline
decision references to point to specific domain files.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2026-02-11 15:55:58 +01:00

1.8 KiB

Dudley - Project Briefing

Last updated: 2026-02-10

Current Project State

The Settled Reach: top-down immersive sim, single-character perspective, asymmetric information core mechanic, Rimworld-style storyteller. 29 confirmed decisions, 17 discussion rounds complete. Engine selected (D-020: Rust/bevy_ecs server). Vertical slice defined (D-027).

Status

STANDBY. This briefing will be populated when backend/engine implementation begins.

Key Decisions for Your Domain

Read decisions/architecture.md (primary) and decisions/content.md (NPC model). Key decisions:

  • D-010: Four architectural principles (client-server, info boundaries, deterministic sim, input events)
  • D-020: Rust simulation server with bevy_ecs, MessagePack protocol to Godot client
  • D-024: NPC ECS model (10 axes + CombatCapability component)
  • D-026: Simulation tier engine (Active/Background/State-saved/Ungenerated, timestamp LRU)
  • D-030: Testability architecture (hybrid Rust tests, deterministic replay critical)
  • D-031: Time system (10 ticks = 1 game-minute, 4 day phases)

Development Workflow

See docs/DEVOPS.md for full procedures. Your key targets:

  • make setup — verify Rust toolchain (clippy + rustfmt)
  • make build-servercargo build in server/
  • make servercargo run in server/
  • make test-servercargo test in server/
  • make lint-server — clippy (deny warnings) + rustfmt check
  • make ci-server — full server CI pipeline (lint → build → test)
  • Server code lives in server/ — unit tests inline with #[cfg(test)], integration tests in server/tests/
  • Cross-boundary IPC fixtures in tests/

Key Documents

  • decisions/ - domain-split decision files (see decisions/README.md for index)
  • docs/DEVOPS.md - build, test, lint, CI procedures
  • docs/discussions/ - archived design rounds