Memory Boundaries
Use this page when you need to understand how Helpifyr treats memory as an authorized, tenant-scoped, fail-closed surface rather than as free-form local state.
What this concept means
- memory decisions are governed by canonical runtime claims, not by local adapter shortcuts
- tenant isolation, scope posture, and correlation context stay explicit for memory read and write actions
- missing claims or mismatched tenant context fail closed
- downstream memory consumers may enrich local behavior, but they must not invent a second authorization truth
Why it exists in the Helpifyr stack
Helpifyr uses memory-capable components across agent, human, and service lanes. That makes memory useful, but also risky if different consumers start inferring local rules from deployment defaults, cached state, or UI convenience.
The stack therefore publishes one canonical runtime claims envelope and reason-code taxonomy so memory authorization stays aligned across consumers such as Bobbin.
What it is not
- not an unbounded cache
- not permission to infer tenant fallback from local deployment defaults
- not a place where roles may replace missing required scopes
Core objects and boundaries
Canonical claims envelope
Actor type, actor identity, tenant, scopes, and correlation context form the minimum truth needed for memory decisions.
Fail-closed reason codes
The decision model stays explainable through canonical reason codes such as missing claims, missing read or write scope, admin-required, or tenant mismatch.
Downstream parity
Consumers may expose local adapter types or user-facing language, but the final authorization decision still needs to map back to the canonical Fabric-published envelope.
Relationship to other concepts
- Identity, Session, and Projected Authority explains where access and admin posture come from before memory is touched.
- Runtime Projection and Readback explains how published memory claims still need clear readback and ownership.
- Event Modeling explains how memory and provenance lanes fit into the wider event model.
Source truth and evidence
helpifyr-fabric/docs/contracts/HELPIFYR_RUNTIME_MEMORY_CLAIMS_CONTRACT.mdhelpifyr-fabric/contracts/policies/runtime_memory_claims_contract.jsonhelpifyr-fabric/contracts/registry/index.jsonhelpifyr-fabric/contracts/matrix/producer_consumer_matrix.json