26 lines
1.4 KiB
Markdown
26 lines
1.4 KiB
Markdown
# Epoch Forge documentation
|
|
|
|
This documentation describes current executable behavior and labels planned
|
|
behavior clearly.
|
|
|
|
- [Commands](commands.md): verified CLI surface and examples.
|
|
- [Repository format](repository.md): files, epochs, compatibility, backup, and recovery.
|
|
- [Reversing changes](recovery.md): checkpoints and recovery for every mutation.
|
|
- [Architecture](architecture.md): crate responsibilities, data flow, and quality gates.
|
|
- [Staging design](staging-design.md): approved Phase 4 state, command, transaction,
|
|
and migration contract.
|
|
- [TUI design](tui-design.md): approved first-pass scope, interaction, safety,
|
|
and accessibility contract.
|
|
- [Simulation and world generation](simulation-worldgen-design.md): seeded
|
|
fuzzing, roads, movement, diffusion, map rendering, and config packaging.
|
|
- [Adjudication/influx, diffusion resolution, and conflict](resolution-conflict-design.md):
|
|
implementation contract for tracker issues #9, #8, and #12.
|
|
- [Presentation and export](presentation-design.md): remaining buffered,
|
|
coherent, saveable output contract for tracker issue #10.
|
|
- [Roadmap](roadmap.md): current work and stretch proposals.
|
|
- [Gitea issue audit](issue-audit.md): disposition and dependencies of the
|
|
upstream tracker backlog.
|
|
|
|
Start with the project [README](../README.md). Contributors should also read
|
|
[AGENTS.md](../AGENTS.md) and maintain [AGENTS-TASKS.md](../AGENTS-TASKS.md).
|