Sessions and Memory
Understand Klykable database memory as structured product state.
Klykable memory lives in structured database state.
That means sessions, context, events, tool results, transcripts, outcomes, and reusable facts can be owned, reviewed, and scoped like product data.
Session state
Session state explains what happened in one run of a surface. It should preserve enough detail for review and handoff.
Reusable memory
Reusable facts should have provenance and scope. A fact may belong to a workspace, account, workflow, customer, or individual session.
Why database memory
Product teams need memory they can inspect and govern. Hidden memory may feel magical, but structured memory is easier to trust.