epoch_forge/docs/roadmap.md

62 lines
3.1 KiB
Markdown

# Roadmap
The detailed backlog is [AGENTS-TASKS.md](../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](staging-design.md) 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](tui-design.md) now includes search, layer browsing, responsive
layouts, and guarded terminal handling. Its entity editor supports previewed
worktree creation/edits and conflict-checked one-step undo through the library.
Interactive staging, commits, relationships, and general deletion remain later
workflows.
The simulation track has deterministic world generation, road topology,
character travel, and spatial event frontiers. The next approved work is the
[shared adjudication and conflict design](resolution-conflict-design.md):
player-roll adjudication first, then protected-town/character diffusion
outcomes, then fight/war. The
[presentation design](presentation-design.md) is implemented alongside those
slices so every new preview is buffered and exportable rather than adding more
direct terminal printing. PNG map rendering follows those tracker issues.
## Proposed stretch goals
1. Shell completions and generated man pages.
2. Stable JSON/JSONL output and query/filter expressions.
3. Extend the TUI entity editor with previewed staging and commit 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.