What the memory layer stores
Typed recall items with provenance, supersession, policy labels, and source evidence pointers. It is not a loose chat-history dump.
GRIFF Memory
Recall that stays tied to proof, policy, and source context.
The Memory/Brain layer helps agents recover the right operational context without drifting into stale summaries. Production memory remains private; this page explains the boundary for buyers and evaluators.
Protected memory portalAccess gated
Access boundary
Cloudflare Access gates the production memory host before origin traffic is reached.
Public explanation
This page is the buyer-safe explainer for memory.griff.run while the console remains private.
Pilot path
Evaluation starts with a narrow workflow, sample corpus, recall success criteria, and exported proof.
Not public demo yet
The live recall console and full API remain gated until a sanitized demo and abuse controls are approved.
Buyer context
What approved evaluators should expect.
Memory is useful only when it can be explained and audited. Pilot work focuses on a narrow corpus, measurable recall behavior, and exportable evidence rather than a generic memory chat box.
Why the live surface is private
The production recall API is protected by Cloudflare Access and an operator-issued bearer token so customer and operator memory cannot be browsed publicly.
How evaluators get proof
Approved pilots receive a scoped demo workspace, sample recall records, OpenAPI context, and a receipt pack that shows what was recalled and why.