TMCRAConsoleRequest access

THE MEMORY LAYER BETWEEN PAST WORK AND THE NEXT ACTION

Continue workacross conversations.

TMCRA lets earlier work enter the present with its actor, time, scope, and Source intact — so an Agent can continue from evidence instead of starting over.

Request pilot access Desktop release status Explore integrations
TMCRA / PRINCIPLE 01

Memory may shape the next action only when its origin remains visible.

THE CONTINUITY CUT / 01

Work stops at a conversation boundary. Evidence carries it forward.

CURRENT QUESTION

Continue the integration tests. Fix any failures you find.

USER · Session 18
ALLOW / 01USER GLOBALOwner-level facts only
ALLOW / 02PROJECT / memory-sdkSession 16—18
USERrequirements
AGENTprogress
SOURCE / USERSession 16
“Keep the public API backward-compatible.”
verbatim constraint
FAST / AGENTSession 17

Boundary audit complete.

retry-contract tests remain
working state
SLOW / USERGLOBAL

Engineering handoffs stay concise and executable.

settled preference
PROMPT EVIDENCE03 / 03
  1. 01Resume pending retry-contract tests
  2. 02Preserve public API compatibility
  3. 03Return a concise handoff
actor · scope · time · source retained
NEXT ACTIONRun the retry-contract suite

Continue from the last verified state.

01 / 07Question arrives
LONGMEMEVAL
82.2%
411 / 500
CORE RECALL TRACE
1.322 s
recorded run
ACTOR BOUNDARY
USER / AGENT
separate records
RECALL SCOPES
GLOBAL + PROJECT
parallel
02

THE CONDITIONS OF CONTINUITY

A memory can enter the next action after four questions are answered.

Who said it. When it happened. Where it belongs. What proves it.

01WHO

Keep the speaker

USER requirements and AGENT progress can meet inside one answer while remaining separate records.

02WHEN

Keep the sequence

Corrections and revisions add a new state without erasing what was previously said.

03WHERE

Keep the boundary

Global and Project memory can continue across sessions without crossing into unrelated work.

04SOURCE

Keep the proof

Every derived state remains linked to the exact Source that permits it to influence the next step.

Current instruction leads. Historical user requirements follow. Agent progress contributes without becoming the user's voice.

03

SOURCE / STATE / EVIDENCE

The past stays intact. Its usable meaning can evolve.

TMCRA separates the immutable record from revisable memory views, then binds selected evidence to the current task.

01SOURCE LEDGER

What happened remains intact.

Exact text, actor, time, session position, and content identity form the immutable record.

Keep the public API backward-compatible.

USER · Session 16 · 10:08
02FAST VIEW

The current state can change.

Fresh requirements, decisions, and work progress become compact searchable state with Source provenance.

Integration audit complete; retry-contract remains.

AGENT · Session 17 · 16:42
03SLOW VIEW

Long-lived meaning keeps its revisions.

Durable capsules organize support, counterevidence, challenges, resolutions, and prior versions.

Compatibility is a durable project constraint.

PROJECT · revision 04 · SOURCE BOUND
04READER EVIDENCE

Evidence is prepared before action.

The current task, bounded Source support, verified operations, and provenance become a Reader-ready view.

Resume the pending retry-contract tests.

PROMPT EVIDENCE · TOP-K BOUNDED
04

BOUNDARIES KEEP CONTINUITY TRUSTWORTHY

Shared context, distinct identities.

A project can span sessions and specialized Agents while every contribution keeps its own actor and Source.

CURRENT PROMPTContinue the integration tests.opens two allowed recall scopes
USER GLOBALALLOWED
USER

Use concise engineering handoffs.

SLOW · stable preference
PROJECT / memory-sdkALLOWED
Session 16Session 17Session 18
USER

Keep the public API backward-compatible.

SOURCE · Session 16
AGENT

Retry-contract tests remain.

FAST · Session 17
PROMPT EVIDENCEResume at retry-contract. Preserve compatibility. Return a concise handoff.
05

A COMPLETED RECALL, REPLAYED

Watch the exact cut that lets work continue.

This is a replay of a completed result: scope opening, candidate return, matching, evidence splice, prompt delivery, and role-safe writeback.

CONTINUITY CUTPROJECT / MEMORY-SDKRECORDED / 09:14:22
01 / 09Current prompt
CURRENT PROMPTUSER · Session 18

Continue the integration tests and fix anything that fails.

01 / ALLOWED SCOPE

The question opens only the permitted continuity fields.

USER GLOBALOwner preference
PROJECT / memory-sdk
Session 16Session 17Session 18
Session remains a grouping inside Project.
02 / CANDIDATE TRACKSSEARCHING THREE MEMORY LAYERS
SOURCEUSERSRC-016
Project / memory-sdkSession 16

Keep the public API backward-compatible.

MATCH / 01

The constraint still governs every integration fix.

FASTAGENTFST-017
Project / memory-sdkSession 17

Boundary audit complete; retry-contract tests remain.

MATCH / 02

Unfinished progress directly answers where work should resume.

SLOWUSERSLW-G01
User GlobalCross-project

Use concise handoff notes for engineering work.

MATCH / 03

An allowed owner preference defines the response form.

03 / EVIDENCE STRIPevidence_windows[3]
BOUND / START
01 · USER · SOURCE

Preserve public API compatibility while fixing failures.

SRC-016 · Session 16
02 · AGENT · FAST

Resume from the pending retry-contract tests.

FST-017 · Session 17
03 · USER · SLOW

Return a concise engineering handoff after completion.

SLW-G01 · Cross-project
BOUND / END
PROMPT EVIDENCE / 03 WINDOWSEvidence delivered with actor, source, scope and time intact.
USER requirements AGENT progress
AGENT NEXT / RESOLVEDRun the pending integration suite.

Preserve API compatibility · return a concise handoff

ANSWER COMPLETEDThe continuation now has a new cut point.
04 / AFTER THE ANSWERTwo speakers remain two records.
USER PROMPTUSER RECORD
AGENT ANSWERAGENT RECORD
Recorded sequence · no live server progress is implied
06

VERIFICATION SLATE

Recorded results, with every protocol kept visible.

LongMemEval reports all 500 questions task by task. LoCoMo keeps the Mem0-style Judge subset separate from full-set Token F1 and Evidence Recall.

LONGMEMEVAL / RECORDED82.2%
411 / 500
TMCRA · RESULT LOCK 2026
01Knowledge Update71 / 7891.03%
02Multi Session90 / 13367.67%
03Single Session Assistant55 / 5698.21%
04Single Session Preference27 / 3090.00%
05Single Session User67 / 7095.71%
06Temporal Reasoning101 / 13375.94%
LOCOMO / MEM0-STYLE LLM JUDGE80.92%auxiliary measure · five-run mean · Categories 1–4 · N = 1,540
OFFICIAL TOKEN F155.20all 1,986 questions
EVIDENCE RECALL82.00%all 1,986 questions
CORE RECALL TRACE1.322 seconds

Recorded retrieval, reranking, and evidence packing trace. Planner and answer generation are excluded.

Read protocols and complete benchmark notes
07

ONE CONTRACT, MULTIPLE HOSTS

Connect the cut to the tools your Agents already use.

Each host reaches the same recall and writeback contract through its own lifecycle events.

01 / VERSIONED CONTRACT

REST / OpenAPI

STABLEEXPLICIT

A production HTTP contract for services that control their own model lifecycle.

  1. 01 / RecallPOST …/recall

    Send the current query and allowed scopes.

  2. 02 / Answercaller model

    The caller injects returned prompt evidence.

  3. 03 / WritebackPOST …/ingest

    Persist USER and AGENT as separate messages.

BOUNDARY

The caller explicitly starts recall and ingest; TMCRA does not observe the model call by itself.

Open API reference
RESEARCH / OPEN SOURCE

Inspect the architecture. Reproduce the benchmark.

The repository contains the research architecture, evaluation protocol, and benchmark adapters used by the project.

GitHub
NEXT ACTION / READY

Continue from where the work actually stopped.

Choose the integration path that matches your current Agent workflow.

Request pilot access Desktop release status Read integration guides