symfonic.capabilities.memory.graph_native_admission¶
graph_native_admission ¶
Fail-closed admission for direct kind-aware graph memory operations.
admit_raw_pg_mutation ¶
Exact graph-only PostgreSQL v1 with an attested CORE-199 eraser (CORE-194).
verb None is composition, which needs the whole lifecycle. False hands
the decision to require_native_backends, which refuses PostgreSQL: a
writable v1 scope whose only forget is the bounded inline delete could
hold rows that no forget can erase.
Source code in src/symfonic/capabilities/memory/graph_native_admission.py
exact_pg_graph ¶
Exactly the owner backend or the nonowner runtime; never a subclass.
The runtime only replaces startup with read-only checks, so both serve the same lifecycle SQL (CORE-194). The module test keeps the optional PostgreSQL stack off ordinary in-memory paths.
Source code in src/symfonic/capabilities/memory/graph_native_admission.py
native_quick_writer_scope ¶
Validate the writing graph before reading the native QUICK window.
Source code in src/symfonic/capabilities/memory/graph_native_admission.py
require_composition ¶
Refuse an unadmitted v1 mutation shape before any Agent can exist.
Source code in src/symfonic/capabilities/memory/graph_native_admission.py
require_native_backends ¶
Only concrete backends that explicitly prove v1 storage may serve it.
Source code in src/symfonic/capabilities/memory/graph_native_admission.py
require_native_quick_graph ¶
Admit only the in-memory cycle's fenced, journalled reference graph.
Source code in src/symfonic/capabilities/memory/graph_native_admission.py
require_native_read ¶
Raw graph-only PostgreSQL proves v1 reads; mutation is admitted apart.
Reads need no eraser. Mutation goes through admit_raw_pg_mutation,
which also requires an attested CORE-199 eraser (CORE-194).
Exact HMS/backend types exclude custom implementations and cycle overlays.
Keep the optional PostgreSQL import off ordinary in-memory read paths.