references-are-durable-across-persistence-and-evolution

OUT derived (depth 5)

All system-generated identifiers survive both persistence boundaries (save/load cycles, cross-session durability via high-water marks) and format evolution boundaries (parser versioning, schema migration, forward-compatible metadata) — references remain valid and resolvable across time and system versions.

Summary

Every identifier the system creates will remain valid and resolvable no matter how many times the database is saved and reloaded or how the data format changes over time. This means nothing in the system can "go stale" — references written today will still work after schema migrations, parser updates, or restarts across sessions and versions.

Justifications

SL — Persistence durability (depth-4) covers temporal stability; evolution tolerance (depth-2) covers version stability — together they guarantee referential integrity across all change axes.

Antecedents (all must be IN):

  • all-identifiers-are-durable-across-persistence-boundaries — All system-generated identifiers are not only deterministic and collision-free at creation time but also durable across persistence boundaries — nogood IDs survive save/load cycles via the network_meta table's high-water mark, ensuring the collision-free property is maintained across the system's entire operational lifetime rather than just within a single session
  • system-boundaries-are-evolution-tolerant-and-reference-safe — The system handles boundary interactions safely along two independent dimensions: format and schema evolution is tolerated gracefully (derive parser fallbacks, forward-compatible metadata lines, SQLite schema migration via try/except), while reference validation prevents invalid IDs from crossing any boundary (import normalization drops unknown refs, nogoods skip missing nodes, LLM hallucination filtering discards phantom IDs)

Dependents

These beliefs depend on this one:

Details