CockroachDB × AWS Hackathon 2026

Continuity begins when memory can explain what changed.

Messages are easy to store. Persistent identity requires attributable claims, semantic retrieval, conflict detection, human resolution and an immutable chain of canonical versions.

Claim→Source→Conflict→Resolution→Canon

Memory types5Episodic · Semantic · Canonical · Procedural · Provenance

Mutation modelAppend-onlyEach committed claim or governed conflict resolution creates a canonical version

Memory layerCockroachDBTransactional records and distributed vector retrieval

Agent runtimeAWSLambda · Bedrock · API Gateway · S3 · CloudFront

01 · Identity

Establish a persistent self

Display name Description

or restore an existing identity

Active identity

02 · Memory intake

Submit one atomic claim

Memory type Statement

Current canonical projection

No identity established

Version —

Create an identity, then submit a claim. The first accepted claim becomes Version 2.

Human-governed conflict resolution

Compare memory before changing identity

No unresolved conflicts. A contradictory claim will appear here instead of replacing canonical memory.

Immutable provenance ledger

How the present became authoritative

Lifecycle events will appear here with actor, time, linked claim and canonical version.

Live architecture

Browser→CloudFront + S3→API Gateway→Lambda agents→Bedrock↔CockroachDB

Managed MCP Memory Auditor completed a strictly read-only production audit: 16 passed, 2 warnings, 0 failed.