format-resilience-spans-all-external-interfaces
OUT derived (depth 2)
The system tolerates format variation at every external interface — derive output parsers support version fallback, import parsers silently skip unknown fields, storage handles schema evolution — and extends this resilience to LLM response parsing, where the list-negative parser uses regex extraction to recover structured data from prose-laden responses.
Summary
The system handles format differences gracefully everywhere it touches external data, from version mismatches in its own output formats to unknown fields in imports to database schema changes, and this same resilience extends to parsing LLM responses where structured data gets extracted even when buried in freeform text. This means no single format change or messy response can break the pipeline.
Justifications
SL — Format evolution tolerance extends from system boundaries to LLM output parsing
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
- list-negative-parser-is-fully-resilient — The list-negative LLM response parser handles all degradation levels: regex extraction recovers JSON objects from prose-laden responses, and completely unparseable output returns zero results gracefully rather than raising exceptions.
Dependents
These beliefs depend on this one:
- external-ingestion-is-format-resilient-and-defensively-layered — External belief ingestion achieves both defensive containment (fail-soft validation, Jaccard retraction guards, dual import/sync reconciliation, namespace isolation) AND format resilience (parser version fallback, forward-compatible metadata parsing, prose-tolerant JSON extraction), ensuring robust integration even as external source formats evolve unpredictably.
- format-resilient-boundaries-enforce-validated-trust — All system boundaries simultaneously tolerate format variation at every level — from LLM response parsing through schema migration to derive output versioning — while enforcing strict validated trust through typed exceptions, referential integrity checks, and hallucination filtering.