pgapi-is-complete-sql-reimplementation
OUT derived (depth 2)
PgApi is a complete SQL-native reimplementation of the in-memory Network: it re-implements core algorithms (BFS propagation, entrenchment scoring, nogood resolution) directly in SQL with multi-tenant composite keys and per-method transaction semantics, achieving full behavioral parity.
Summary
The PostgreSQL API was thought to fully replicate the in-memory reasoning engine's behavior using pure SQL, covering propagation, scoring, and conflict resolution with multi-tenant support. This has been retracted, meaning the two implementations likely diverge in important ways and cannot be treated as interchangeable.
Justifications
SL — SQL-native multi-tenancy composed with algorithm reimplementation yields full parity — but only when API coverage is complete
Antecedents (all must be IN):
- pgapi-is-sql-native-multi-tenant — PgApi operates as a SQL-native multi-tenant implementation: all operations execute directly against PostgreSQL with no in-memory Network object constructed, composite primary keys on all tables provide project-level isolation, and each public method is a single committed transaction.
- pg-reimplements-network-in-sql — `PgApi` reimplements the in-memory `Network`'s algorithms (BFS propagation, entrenchment scoring, nogood resolution, dialectical operations) directly in SQL rather than delegating to the `Network` class.
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