system-boundaries-are-evolution-tolerant-and-reference-safe
OUT derived (depth 2)
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)
Summary
This claim combines two safety properties into one: the system can handle older or newer data formats without crashing, and it also catches invalid references before they cause downstream errors. It is currently retracted, meaning at least one of those two properties — graceful format evolution or consistent reference validation — is no longer considered established, so the combined guarantee does not hold.
Justifications
SL — Evolution tolerance ensures old formats/schemas don't break new code, while reference validation ensures new data doesn't corrupt existing networks — together they make all system boundaries both forward-compatible and integrity-preserving
Antecedents (all must be IN):
- system-tolerates-evolution-at-all-boundaries — The system handles format and schema evolution gracefully at every external boundary: derive output parsers support two format versions with automatic fallback, belief import silently skips unknown metadata fields, and storage tolerates missing tables from older database schemas via exception handling
- reference-validation-is-defense-in-depth — Every system boundary that accepts node ID references validates them against the actual network: import normalization drops unknown antecedent/outlist refs, nogood recording skips invalid node IDs, and LLM-returned negative-list IDs are filtered against existing nodes.
Dependents
These beliefs depend on this one:
- references-are-durable-across-persistence-and-evolution — 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.