epoch_forge/docs/roadmap.md

2.7 KiB

Roadmap

The detailed backlog is AGENTS-TASKS.md.

Implemented foundation

  • Local CLI repository with full-world epoch snapshots.
  • Five entity collections with add/edit/show/diff/delete operations.
  • Statistics, positions, duration/effects, selected relationships, and random generation.
  • Timeline advance, switch, log, tags, summaries, and explicit future deletion.

Current release target

The trustworthy-foundation milestone is complete: documentation now reflects the executable, user-triggerable panic paths found in the audit are guarded, initialisation is safe, show, read-only fsck, and world diff are real, individual files are persisted atomically, and CLI workflows are covered.

The dependable-daily-CLI milestone is complete: naming and aliases are consistent, organisations are managed directly, help includes examples, Nerd Font output has a portable build option, relationships are type-validated, and every mutation has documented and tested recovery guidance.

The Phase 4 format contract is implemented. Native format 1.0 initialization, locking, recovery, staging, immutable commits, revert, and recoverable pruning are implemented. The unreleased prototype reader and its temporary migration were removed before the first release. Future compatible changes use 1.x versions and regain explicit migration tooling when needed. Organisation-agnostic custom fields and types follow, with unknown-field retention designed before that format change.

The TUI browser now includes search, layer browsing, responsive layouts, and guarded terminal handling. The read-only efo-tui uses the same library API. Interactive mutations remain a later, separately reviewed checkpoint.

The next implementation track is the simulation and world-generation design. Its first checkpoint is deterministic, configuration-driven generation; road topology, event diffusion, and PNG rendering build on that validated foundation.

Proposed stretch goals

  1. Shell completions and generated man pages.
  2. Stable JSON/JSONL output and query/filter expressions.
  3. Extend the first read-only TUI with previewed, recoverable write workflows.
  4. Named timeline branches with merge/conflict handling.
  5. Setting templates for empires, companies, guilds, and nations.
  6. Validation/simulation hooks before committing an epoch.
  7. Optional signed snapshots and append-only audit records.
  8. Deterministic seeded generation/simulation.
  9. A scripting/plugin boundary after persistence is stable.

Completions and structured output are the best first stretch investments. A TUI and branching should wait until staging, revert, and locking are reliable.