pgapi-achieves-implementation-parity

OUT derived (depth 1)

PgApi achieves full behavioral parity with the in-memory Network implementation: it reimplements the core algorithms (entrenchment scoring, nogood resolution, BFS propagation, dialectics) in SQL with BFS propagation executed in application-level Python.

Summary

The PostgreSQL-backed API was considered to have reached full feature parity with the original in-memory implementation, covering all core algorithms like entrenchment scoring, contradiction resolution, and belief propagation. This is currently marked as not holding, meaning there may be gaps or regressions where the two implementations diverge in behavior.

Justifications

SL — PgApi reimplements core Network algorithms but has not yet achieved full API coverage — when pgapi-partial-api-coverage is retracted (all operations implemented), this GATE flips IN to confirm parity

Antecedents (all must be IN):

  • pgapi-bfs-propagation-in-python — PgApi implements BFS propagation in application-level Python (not stored procedures), using JSONB containment queries (`@>`) against GIN indexes to find dependents
  • 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

Details