franalgaba__grimoire/docs/explanation

Explanation

Use this section for conceptual and architectural context.

An explanation page should:

• Clarify why the system works the way it does.
• Cover tradeoffs, alternatives, and constraints.
• Help readers build accurate mental models.
• Connect design choices to user and runtime outcomes.

Typical examples:

• Execution model and preview/commit rationale
• Core/compiler separation and protocol-agnostic design
• State persistence architecture decisions

Start Here

Read in this order for the fastest mental model:

1. docs/explanation/mental-model.md
2. docs/explanation/architecture.md
3. docs/explanation/preview-commit-model.md
4. docs/explanation/advisory-decision-flow.md
5. docs/explanation/type-system.md
6. docs/explanation/data-provenance-and-replay.md

Pages

• docs/explanation/mental-model.md
• docs/explanation/architecture.md
• docs/explanation/preview-commit-model.md
• docs/explanation/advisory-decision-flow.md
• docs/explanation/type-system.md
• docs/explanation/data-provenance-and-replay.md