Agentic memory that understands people

A memory layer built around people.

Within the verified closed-beta boundary, supported, authorized inputs can become canonical memory of people, organizations, commitments, relationships, and change—then qualified, cited context for the agent doing the work.

Evidence stays inspectable. Uncertainty stays visible. Memory never grants authority to act.

Illustrative mechanismAuthorized references connect to qualified fields with an inspectable evidence route. This diagram explains the product model; it is not a literal interface or a completeness claim.

Why memory

Retrieval finds a passage. Memory maintains identity, state, and support.

The same person appears across sources and time. Useful context needs identity, state, and evidence—not just a similar fragment.

Fragment retrieval

A passage comes back.

  • Identity is reconstructed again.
  • Old and current context compete.
  • Evidence and status can drift apart.
People-aware memory

Meaning stays qualified through change.

  • Entities remain canonical.
  • Time and conflict stay visible.
  • Citations and boundaries travel with context.

The memory model

Five facets make context usable.

01

Identity

Resolve recurring mentions without merging ambiguity by default.

02

Time

Keep current, historical, and superseded state distinct.

03

Evidence

Attach sources; label inference, conflict, and uncertainty.

04

Relationships

Place roles, commitments, and connections with their entities.

05

Authority

Keep useful context separate from permission to act.

Bounded retrieval

Return only the context the task permits.

Illustrative retrieval model

Define the retrieval frame.

Supported deployments may use the subject, integrating agent, permitted scope, and task to narrow already-published memory.

Claim boundary

What exists, what is being tested, and what remains product direction.

Current foundation

Canonical entity memory

Promoted people and other durable entities can retain qualified state through change.

Verified deployment

Searchable, cited retrieval

Supported sources can produce published memory and bounded retrieval inside the verified beta boundary.

Closed-beta evaluation

Whether cited memory improves customer judgment

This is the GTM beta’s evaluation question, not a measured result.

Product direction

Broader scope controls

Personal and organizational isolation and explicit sharing are being shaped—not offered as current behavior.

Closed beta

Bring one workflow where customer context gets lost.

We are inviting GTM teams that can bring authorized source context to the closed beta.