1.5 KiB
1.5 KiB
— title: Ephemeral First, Persistent Later type: reference tags: :passepartout:architecture: —
Ephemeral First, Persistent Later
The architecture note's Option 5 (ephemeral facts, no disk persistence) is the correct first implementation. Three reasons:
- The fact language is unproven. Triples with provenance and grounding is a hypothesis. It may be too simple for some domains, too complex for others. Committing to a serialization format before knowing what's useful is premature.
- The ontology is emergent. Categories are created on first use. What proves useful stays; what doesn't fades. A persistent format would need a migration story every time the category structure changes. Ephemeral avoids this entirely — the facts are re-derived on each session start using the current (evolved) ontology.
- Rebuildability is the safety net. Because all facts have a
:groundingto an Org heading, and gate-outcome facts are regenerated from the gate stack on every load, the entire symbolic index can be thrown away and rebuilt from scratch. The cost is compute, not data. This is the practical realization of "the prose is always the ground truth."
The transition to persistence (Phase 5: VivaceGraph) happens when two conditions are met: the fact language has stabilized through use, and the accumulated deductions across sessions provide value that justifies the serialization cost.