pgapi-find-dependents-queries-outlist
IN premise
PgApi's `_find_dependents` queries both `antecedents @>` and `outlist @>` JSONB containment, correctly enqueuing outlist-dependent nodes for re-evaluation — a capability the in-memory Network historically lacked until PR #31.
Summary
When the system needs to figure out which beliefs are affected by a change, the PostgreSQL implementation searches two separate dependency lists — both the logical antecedents and the "outlist" entries. This means nodes that depend on something being OUT (not just IN) get properly re-evaluated during cascades, fixing a gap that the original in-memory engine had missed.
Dependents
These beliefs depend on this one:
- pgapi-enforces-referential-integrity-bidirectionally — PgApi enforces referential integrity in both directions: write-time validation checks all antecedent and outlist IDs exist before inserting justifications, while read-time dependent discovery queries both antecedent and outlist JSONB containment to find all affected nodes.
Details
| Source | entries/2026/04/29/gated-and-negative-analysis.md |