Trace Continuity Labs — Every Decision Begins With Authority

Trace ContinuityTRACE·CONTINUITY
Break MePlayground
Trace Continuity — the guardian sees
Runtime Authority Verification

Every Decision Begins With Authority.

Authority verified on every call. PII tokenized before it is ever stored. Every read, write, and retrieval sealed into an append-only audit chain.

Open the PlaygroundTry to Break It
Authority

Re-evaluated on every call — never cached from login.

Action Admissibility

Valid authority is not enough — material conditions at execution time can still stop the action.

Tokenization

SSNs, emails, phones replaced before storage. No raw PII at rest.

Safe retrieval

Only what the caller is authorized to see, at the moment they ask.

Audit chain

Hash-linked, append-only evidence you can export.

Playground is live
The Playground

Don't believe the marketing.
Try to break it yourself.

Four live surfaces. Real authority evaluation. Real tokenization. Real audit evidence. Hand it your worst inputs and watch the governance layer respond.

Open the Playground

Experience governed memory firsthand.

Authority Trace
EVALUATED
actor: agent_med_42 → user_clinician_18
tenant: medicore.health
scope: patient.read · memory.write
delegation: verified · 3 hops
decision: AUTHORITY OK · proceed to governance
Governance Decision
TRANSFORM
input: "...SSN 456-78-9012, email schen@..."
detected: SSN · EMAIL
policy: PHI/PII · tokenize · retain 7y
verdict: TRANSFORM
evt: evt_a8c3
Tokenization
SEALED
raw_ssn: 456-78-9012
→ token: trace_tok_ssn_a7b3
raw_email: schen@medicore.health
→ token: trace_tok_email_x9f2
raw_pii_at_rest: false
Audit Evidence
APPENDED
chain: evt_a8c3 → evt_a8c7
stages: authority · governance · tokenize · store
hash: sha256:9f2a…c8d1
mutable: false
export: HIPAA · legal hold · DoD review

Authority Trace · Governance Decision · Tokenization · Audit Evidence

Authority Continuity

Most systems authenticate once.
Trace Continuity verifies authority at execution time.

A session token at login is not authority. In hospitals, legal, and defense, the question is not "did this user sign in?" — it is "is this user, this agent, this delegated identity, allowed to do this exact thing, right now, against this exact tenant?" Trace evaluates that on every call. No cached trust. No implicit bypasses.

Per-call evaluation

Authority is re-checked on every read, write, and retrieval — not once per session.

Delegation aware

Agent acting on behalf of user acting on behalf of tenant — the full chain is verified.

Tenant by construction

Cross-tenant access cannot happen by mistake. The architecture forbids it.

Action Admissibility

Valid authority does not always mean an action should proceed.

Trace separately checks the material conditions that exist at execution time, including consent, risk, jurisdiction, compliance, and other governed conditions. If those conditions make the action inadmissible, Trace stops it even though authority remains valid. Every decision produces audit evidence.

Separate decision

Runtime Authority Verification and Action Admissibility are two independent checks, evaluated and audited on their own.

Material conditions

Consent state, risk score, jurisdiction, legal hold, compliance status and other governed facts, evaluated at execution time.

Fail closed

If a required condition is missing or stale, the action is refused — not assumed admissible.

Authority: verified · Action admissibility: denied — both are real outcomes.

Architecture Flow
1
Authority Verification
2
Action Admissibility
3
Governance Evaluation
4
Tokenization
5
Memory Storage
6
Safe Retrieval
7
Audit Evidence

Authority Verification and Action Admissibility are two separate decisions. Authority can pass while admissibility denies — the execution gate evaluates material conditions after authority is established, on both the write and the read path.

Authority (Step 1)
  • ▸Key validity check
  • ▸Expiration verification
  • ▸Scope validation
  • ▸Delegation chain check
Action Admissibility (Step 2)
  • ▸Material conditions at execution time
  • ▸Consent · risk · jurisdiction · compliance
  • ▸Separate decision from authority
  • ▸Fail-closed with its own audit evidence
Governance (Step 3)
  • ▸PII & PHI detection
  • ▸Redaction & tokenization
  • ▸Retention policy assignment
  • ▸Audit event logging
Memory (Step 4)
  • ▸Only governed result stored
  • ▸Raw PII never persisted
  • ▸TTL enforced at write time
  • ▸Token mappings preserved
Download Technical Architecture Brief (PDF)Download Architectural Buyer’s Brief (PDF)
Step 1 — Authority First

Authority runs before everything else.

Before any data is scanned, tokenized, or stored — Authority evaluates who is making the request and what they are allowed to do. No bypasses.

6 questions Authority evaluates
1
Who is making the request?

API key, agent, or delegated identity

2
Who is receiving the request?

Target user or resource context

3
What permissions exist?

Scopes, roles, delegation chain

4
What actions are allowed?

Read, write, retrieve, export

5
Tenant boundary intact?

Cross-tenant blocked by construction

6
Final verdict?

Allow · Transform · Deny — with evidence

Break Me Challenge

We invite you to attack it.

This is not a game. There is no leaderboard. The Break Me Challenge exists so you can verify, with your own input, that the governance layer behaves the way we say it does. The expected result is not success — it is the platform visibly governing the data and exposing exactly how through "How Was This Governed?"

  • Insert an SSN, credit card, or API key
  • Insert raw passwords or email + phone combos
  • Attempt unsafe retrieval across tenants
  • Attempt authority failures and delegation gaps
  • Attempt policy violations and prompt-style bypasses
Try to break it
attempt_001 DENIED
cross-tenant read · authority failure
attempt_002 TRANSFORMED
raw SSN → tk_9f2a · vault sealed
attempt_003 AUDITED
evidence chain evt_a8c3 → evt_a8c9
Audit & Evidence

If it isn't audited, it didn't happen.

Append-only

Audit rows cannot be edited or deleted — by the platform, by tenants, by us.

Stage-attributed

Every event names the stage (authority, governance, tokenization, storage, retrieval) that produced it.

Compliance-ready

Evidence chains are exportable for HIPAA, legal hold, and defense review workflows.

Governance vs Memory

Memory systems remember. We govern what is remembered.

Mem0 and Zep are excellent at remembering. Trace Continuity Labs is built for environments where remembering without governance is the liability — hospitals, law firms, and defense.

CapabilityMem0ZepTCL
Long-term memoryYesYesYes
Authority continuityNoNoYes
Policy verdicts (allow / deny / transform)NoNoYes
PII detection & tokenizationNoNoYes
Per-tenant encryption keysNoNoYes
Safe retrieval with authority re-checkNoNoYes
Append-only audit at every stageNoNoYes
Compliance posture (HIPAA / legal / defense)NoNoYes

Comparison reflects publicly documented capabilities at the time of publication.

Built for

Where governance is not optional.

Healthcare

PHI tokenized at intake. Authority chains map to clinician scopes. Audit ready for HIPAA review.

Legal

Privileged content stays tokenized in storage. Matter-scoped authority. Evidence chains for legal hold.

Defense

Classification-aware governance. Per-tenant keys. Cross-tenant retrieval is structurally impossible.

Enterprise

Bring your own policy. Bring your own keys. Bring auditors — every stage emits evidence.

Pricing

Enterprise pricing available.

Priced by governance posture, not memory count. Tiers for evaluation through regulated production deployments.

View Plans
Who governs? How is it enforced?

Before you trust it —
you need to understand this.

The Playground is the proof. Test the architecture yourself.

Open the Playground