Concept
Memory and system
Memory forms, ecosystem, whole-system view, and operating discipline.
Cover for Memory and system7 concepts in this section.
All sections
Illustration for Six forms of memoryTell memory kinds apart
10 minSix forms of memory
Context, working state, knowledge, experience, expertise, and transcript each carry different lifetime, governance, and UX implications, learn to tell them apart.
Illustration for Four kinds of sourceWhere a fact came from
10 minFour kinds of source
When a cognitive unit needs a fact, classify where it came from. Approved, system, observed, and unaccountable sources carry different trust and different obligations.
Illustration for The Thoughtware Map and GrammarShared workshop notation
10 minThe Thoughtware Map and Grammar
Shared map and specification language for outcomes, behaviour, memory, authority, and evaluation, so construction does not restart from features every sprint.
Illustration for When AI stops being visibleOutcomes without scaffolding
9 minWhen AI stops being visible
When architecture is sound, intelligence disappears into ordinary UX, users interact with outcomes and trustworthy conduct, not scaffolding or model theatre.
Illustration for Thoughtware in practiceOperating model, not demos
9 minThoughtware in practice
Practicing Thoughtware means decision maps, cognitive unit specs, library publishing, eval gates, and maturity migration, not hackathons on prompts.
Illustration for Working state versus transcriptState versus chat log
9 minWorking state versus transcript
Agents need structured working state, goal, constraints, progress, gaps, not chat logs, to loop, repair, and evaluate reliably.
Illustration for Preference store versus chat memoryCommitment is not the same as episode
9 minPreference store versus chat memory
Standing household choices belong in a structured, editable preference store, ephemeral run context stays in chat and working state, not the database of record.