Skip to main content

Valenar Roadmap

Status board for the current Valenar implementation surface.

This page is intentionally narrower than the full design tree. It records what the prototype already proves, what remains explicitly prototype-only, and which surfaces are the next likely implementation consumers.

Current Runtime Surface​

The live Valenar prototype already exercises these broad slices:

  • backend-owned read models for map, queue, inventory, camp, character sheet, and objective-facing UI
  • queueable MC activities backed by the server snapshot
  • Location dossier, feature drill-in, and map selection flows
  • combat chronicle surfaces and a growing combat-screen design
  • a settlement/runtime bridge strong enough to test ownership, buildings, inventory, and camp state

Prototype Boundaries​

The prototype is still a stepping-in fixture in several important ways:

  • the map is not the final world-scale contract
  • many screens prove ownership and interaction shape before full content depth
  • Generated/ is still hand-written instead of compiler-emitted
  • compiler work is deferred even though the lowering contract already matters

Near-Term Implementation Consumers​

These docs are the main current consumers for future implementation waves:

Working Rule​

When a wave lands, update the doc that owns the behavior first, then update this page if the implementation boundary changed in a way other waves must respect. For the pending follow-up wave plan, see pr-wave-roadmap.md.