MEMORY / PROJECT HISTORYWhat the project learned
What the project learned
should survive the session.
HARIKOS stores structured decisions, attempts, failures, fixes, constraints, discoveries, incidents, and outcomes without pretending that history is current Truth.
ILLUSTRATIVE PRODUCT EXAMPLEATTEMPTCreate the subscription from the browser FAILED ATTEMPTPrivileged Stripe credentials required DECISIONKeep billing mutations server-side
01STRUCTUREDEleven useful memory types
02PERSISTENTAcross browsers and agents
03SCOPEDAttached to the project
04SEPARATEMemory never self-authorizes Truth
A TECHNICAL TIMELINEKeep the useful sequence,
Keep the useful sequence,
not another chat transcript.
HARIKOS preserves the project-relevant event chain: what was tried, why it failed, what was decided, and what finally worked.
ILLUSTRATIVE PRODUCT EXAMPLE
ATTEMPT
01Create the subscription from the browser
Codex / session 2F7AFAILED ATTEMPT
02Privileged Stripe credentials required
root cause / client boundaryDECISION
03Keep billing mutations server-side
applies to checkout and portalOUTCOME
04Signed webhook boundary completed
commit c2137fbAGENT CONTINUITYThe next agent inherits
The next agent inherits
the hard-won parts.
A related task receives current Truth plus the prior constraint, failed attempt, decision, outcome, and relevant files.
ILLUSTRATIVE PRODUCT EXAMPLE
01C
CODEXSESSION COMPLETE
FAILED ATTEMPTDECISIONOUTCOME
CURRENT TRUTHCONSTRAINTFAILED ATTEMPTDECISIONOUTCOMERELEVANT FILES
02CL
CLAUDECONTEXT RECEIVED
MEMORY CONTROLUseful history stays
Useful history stays
inspectable and reversible.
Records remain visible to the user and can move through simple active, superseded, and archived states.
Still useful for current work
Replaced but retained as history
Hidden from normal retrieval
Let the next session start where the last one ended.
Connect a repository and give every coding agent one current, evidence-backed understanding.