AgentMemorySDKby KYE Protocol™ · the memory-authority record
Record class · personal data · authority-bearing

What your agent remembers about a person is evidence about them.

Agents accumulate memory — preferences, histories, identities — and then act on it. The question that decides liability is never what the memory says. It is whether it may be used for this action, right now, on this legal basis. AgentMemorySDK makes that a filed, answerable question.

Exhibit A — one memory, filed
Record
"prefers morning deliveries; flat 4B"
Principal
one identified customer, one tenant
Basis
consent · purpose: delivery-scheduling
Use verdict
ALLOW for inference · DENY for training
Withdrawal
routed, provable, evidenced
Admissible
The docket

Five entries every memory carries, from birth to erasure

Regulators already treat agent memory as personal data — Singapore's PDPC guidance validated exactly this lifecycle. Each stage below is a decision with an evidence trail, so a deletion request or an audit is a query, not an archaeology dig.

I
Entry I — Collection

Filed at birth, never inferred later

The memory is written with its class, principal, tenant, and AI-specific notice declared in the record itself — not in a policy PDF nobody can query.

II
Entry II — Basis

Consent and purpose bind to the record

Legal basis and purpose scope attach where the data lives. When the basis changes, the record knows before the agent does.

III
Entry III — Use

The moment-of-use verdict

Training, fine-tuning, inference, and action are four different questions with four different answers: ALLOW, DENY, REQUIRE_CONSENT, REQUIRE_MINIMISATION — decided when it matters, not audited after.

IV
Entry IV — Evidence

Every use and every refusal leaves a reference

Sealed, tenant-scoped, replayable. The answer to "which memories did the agent act on, and was it allowed?" is one lookup.

V
Entry V — Erasure

Deletion is provable, not promised

Withdrawal routes through the same governed path as use — the erasure itself seals evidence, closing the file the way it was opened.

Honest scope: the SDK governs whether a memory may be used for an action. It does not verify the truth of what the memory contains, and it claims no regulation it has not mapped.

Early access

For agents that remember customers

KYC, support, healthcare, finance — teams whose agents hold people's data get access first. Replies come from a person at [email protected].

Explore KYE Protocol™

Join the waitlist

Tell us what your agents remember — a person replies from [email protected].

Routed via the governed comms rail.

Filed.

Your request is on record — routed to [email protected].