ARCHITECTURE / MEMORY EVIDENCE

Every recalled fact keeps its boundary and source.

TMCRA resolves two recall scopes in parallel, composes Source, Fast, and Slow memory paths, preserves actor provenance, and returns bounded Prompt Evidence to the Agent.

01 / SCOPE MODEL

Cross-session memory without cross-project leakage.

Session is a stable grouping and provenance identifier inside a Project Scope. It is not a third recall scope beside Global and Project.

USER GLOBALStable facts and preferences
PROJECT SCOPEProject state and shared Agent work
SESSION 17SESSION 18SESSION 19

02 / LAYERED RETRIEVAL

Three memory paths, one evidence contract.

01SOURCE

Original evidence

Verbatim or source-bound records retain the strongest trace back to the completed turn.

02FAST

Recent working state

Fresh events and progress become available quickly for the next relevant question.

03SLOW

Longer-term structure

Background organization resolves subjects, changes, contradictions, and relationships over time.

04EVIDENCE

Prompt Evidence

Role composition and bounded packing preserve the selected memory IDs, actors, scopes, sessions, time, and source links.

03 / ACTOR PROVENANCE

User requirements and Agent progress remain different records.

Both can be recalled because both matter to continuity. Their role labels, colors, source fields, and display lanes remain distinct.

USER · SOURCE

Requirements and facts

“Keep every small section fully designed.”

COMPOSE, DO NOT MERGE
AGENT · FAST

Progress and results

“The design architecture is complete; homepage implementation is in progress.”

04 / TURN COMPLETION

Recall before the answer. Write after the answer.

When the completed answer is available, TMCRA persists the user and assistant messages as two separate records for future turns.

View lifecycle integration