epoch_forge/docs/roadmap.md

37 lines
1.6 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 immediate release prioritises trust: truthful help/docs, no user-triggerable
panics, safe initialisation, real `show`, useful read-only `fsck`, world diff,
atomic persistence, CLI workflow tests, accessible output, and clear recovery.
Next comes a reviewed Git-like model for working changes, pseudo-staging,
committed epochs, restore, and revert. Organisation-agnostic custom fields and
types follow, with migrations and unknown-field retention designed first.
## Proposed stretch goals
1. Shell completions and generated man pages.
2. Stable JSON/JSONL output and query/filter expressions.
3. A keyboard-driven TUI over the same domain API (no GUI).
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.