rich-governance-spans-all-backends
IN derived (depth 9)
The system's exception-safe rich lifecycle governance — deterministic, lifecycle-complete, and spanning revision through source integrity — operates identically across all storage backends, achieving full behavioral parity between SQLite and PostgreSQL for metadata-enabled lifecycle management.
Summary
No matter which database you use — SQLite or PostgreSQL — the system's lifecycle management behaves exactly the same way, including all the safety guarantees around crash recovery, contradiction handling, and metadata tracking. This means you can swap storage backends without worrying that beliefs will be managed differently or that edge cases around retractions and state transitions will behave inconsistently.
Justifications
SL — Rich governance properties are established on the SQLite path; PgApi's partial API coverage is the sole barrier to backend universality — this GATE flips IN when PgApi achieves full API parity
Antecedents (all must be IN):
- rich-governance-is-exception-safe — The system's rich lifecycle governance — deterministic, lifecycle-complete, extending beyond binary truth to metadata-enabled state with full monitoring — operates within an exception-safe framework spanning both TMS core and source lifecycle: contradictions are resolved through deterministic backtracking, challenges reach correct truth states through crash-safe propagation, and source failures degrade gracefully through fail-safe path resolution — ensuring that rich state transitions never produce corrupted or inconsistent lifecycle metadata.
- rich-governance-is-deterministic-and-lifecycle-complete — The deterministic lifecycle-complete architecture governs state richer than binary truth values — deterministic reasoning ensures predictable state trajectories and gapless lifecycle monitoring ensures no belief escapes management, while metadata-enabled governance extends these guarantees to retraction reasons, staleness tracking, and access control beyond IN/OUT.
Unless (any of these IN defeats this justification):
- pgapi-partial-api-coverage — PgApi implements core operations (add/retract/assert/search/nogood/explain) but defers simulation, dialectics, namespace support, import/export, and maintenance operations to future work