# 8.1 Five places an answer comes from (/managing-ai-workers/context-memory-knowledge-and-state/five-places) --- type: Document title: "8.1 Five places an answer comes from" description: "Where an AI Worker's answer can come from, the question each source answers, and which sources may decide a question about a rule or about a payment." status: stable order: 208.1 ksor: owner: team:panaversity audience: [ public ] approval: by: process:panaversity at: 2026-10-07T18:30:04Z chapter: "08" part: II expert_status: required concepts: [ "8.1" ] last_verified: 2026-10-07 sources: - id: ksor title: "KSoR, the Knowledge System of Record (Panaversity, GitHub, verified 2026-10-07)" resource: https://github.com/panaversity/ksor - id: ssor title: "SSoR, the State System of Record (Panaversity, GitHub, verified 2026-10-07)" resource: https://github.com/panaversity/ssor - id: dsor title: "DSoR, the Data System of Record (Panaversity, GitHub, verified 2026-10-07)" resource: https://github.com/panaversity/dsor - id: v1-system-of-context title: "The System of Context (Panaversity, first edition, verified 2026-10-07)" resource: https://agentfactory.panaversity.org/docs/ecosystem/system-of-context generated: at: 2026-10-07T18:30:04Z by: esl-rewrite/1.2.0+ksor.1 trust_tier: unverified build_id: sha256:c93b28093c2f70c60faae2645a693d881b657ff94d00f7dd9f8c06427ff61c87 dirty: true ksor_version: 0.0.60 --- **In everyday life.** You ask a friend when the pharmacy closes. They might read the sign in front of them (**context**), or remember what you told them last week (**memory**). They might know that your prescription was ordered Monday and promised for Thursday (the case file, the job **SSoR** does). They might quote the pharmacy's official hours (the official record, the job **KSoR** does). Or they might call to check whether it closed early today (current state, the job **DSoR** does). **What you will learn.** How to tell which of five places an AI Worker's answer came from, and which of them can give the final answer about a rule or a payment. You practice it in step 1 of the build step. **Why it matters.** A wrong answer can sound just as sure as a right one. Where an answer came from tells you whether to trust it. An AI Worker's answer can come from five places, and they are not the same kind of thing. The last three, SSoR, KSoR and DSoR, are systems of record: each is the official source for one kind of fact. The table's examples come from Brightline Wholesale Supply, the book's example company, and its AP Worker, the AI Worker that handles the bills Brightline owes. AP means accounts payable. Maria is the office manager, and Dave, the controller, runs Brightline's accounting. | | **Context** | **Memory** | **SSoR** | **KSoR** | **DSoR** | | --- | --- | --- | --- | --- | --- | | **The question it answers** | What can the worker see right now? | What does it remember about you? | Where does this **matter** (one piece of work, such as an invoice) stand, and how did it get here? | What is officially true here? | What is true right now? | | **Who writes it** | You, your files and the conversation | The AI product, from your chats | Systems, AI Workers and people, each entry checked when it is added | A person who drafts it, then one who approves it, under a named owner who is responsible for it | The company's systems | | **How long it lasts** | This conversation | Until edited or deleted | Kept. A correction is a new entry, and the old one stays | Until someone with authority changes it | As recorded, until it changes | | **AP example** | The invoice you just attached | "Maria wants replies in plain English" | "Invoice 5149: callback October 22, held October 23, paid October 30" | "Invoices over $5,000 need the controller's approval" | "Invoice 5149 is paid" | - **Context** is what the worker sees now. - **Memory** is non-authoritative continuity: preferences, experience and where to look. It helps the worker carry on from past chats, but it never has the final word. - **SSoR**, the State System of Record, is the governed record of each **matter**. Governed means kept under rules about who may add, approve or change it. A matter is a piece of work carried to an end, such as an invoice from receipt to payment.[^ssor] Think of it as the matter's case file: where it stands, how it got there, and the evidence for each step. - **KSoR**, the Knowledge System of Record, is the governed knowledge layer: what the company has approved as true.[^ksor] - **DSoR**, the Data System of Record, governs state and action: it reads what is currently so in the real systems, and checks every action against authority. State is where things stand now, such as whether an invoice is paid. The ERP, the ledger and the vendor records stay authoritative underneath it.[^dsor] These are the company's own systems: the ERP is its main business software, and the ledger is its record of accounts. DSoR is an open specification, and Part IV of this book teaches it in depth. SSoR is a published design. In Part II, this part of the book, you read current state from the company's systems yourself, and keep the SSoR record by hand. These are five places to manage, not five separate parts inside the AI. The worker works only from its context. The other four reach it only by being put into that context. What settles a question, or gives its final answer, is where the content came from, not how it reached the worker.[^v1-system-of-context] For example, "Invoice 5149 is paid" settles the question when it was read from the accounting system, not when memory supplies it. **One fact, one authority.** This is the rule in SSoR's design that keeps SSoR, KSoR and DSoR apart. Every fact has exactly one named authority, and every copy carries a record of where it came from.[^ssor] The authority is the source whose word is final for that fact: - KSoR settles policy. - The company's systems settle current state, and DSoR reads them. - SSoR settles the record of the matter: what was received, what was believed and why, and what was decided. SSoR does not settle whether 5149 is paid right now. When SSoR shows 5149 paid, it records what the authority said and when. Its latest-known status is only that: the latest known, as of its date. Two rules follow. 1. Memory never overrides the other four. If memory disagrees with any of them, memory loses. 2. A rule and a fact are different things. "Invoices over $5,000 need approval" is knowledge. It stays true until someone with authority changes it. "Invoice 5149 is unpaid" is state. It was true on October 23, and it changed when 5149 was paid on October 30. A file can hold knowledge safely if someone owns it. A file that holds state is a snapshot: evidence of its date. It is out of date as soon as the state changes. In the chapter's opening story, the AP Worker gave four wrong answers. Each came from the wrong place: - Whether invoice 5149 was paid came from an out-of-date file. SSoR would have shown its history, and the accounting system would have shown its current state. - The approval threshold, the amount above which an invoice needs Dave's approval, came from memory. - The rule for a vendor's new bank details came from notes that nobody owned. - A standing instruction, a rule meant for every conversation, came from context alone. When the long conversation was condensed, the worker stopped following it. ![The title reads "Five places an answer comes from." The line below it reads "Working context, personal continuity, case history, approved policy and current business state." Five columns each give a question, a source, how long it lasts and an AP example. Context, the working space: what can the worker see this turn? Instructions, messages, files and tool results, limited to what is loaded for this turn. Example: the invoice you just attached. Its badge reads "Carries source material." Memory, personal continuity: what does it remember about you? Preferences and details from past chats. It may persist across chats, and it can be incomplete. Example: "Maria prefers plain English." Badge: "Continuity, not authority." SSoR, the State System of Record: where does this matter stand, and how did it get here? Governed entries from systems, workers and people. History is kept, and corrections add new entries. Example: a timeline for invoice 5149, a callback on October 22, held on October 23, paid on October 30. Badge: "Authority for the case record." KSoR, the Knowledge System of Record: what is the approved rule? A named owner and a recorded approval. It lasts while in force and within its review period. Example: "Invoices over $5,000 need controller approval." Badge: "Authority for policy." DSoR, the Data System of Record: what do business systems record now? Governed reads and actions in authoritative systems. State changes, so recheck before acting. Example: the accounting system shows "Invoice 5149 is paid." Badge: "Current state and action." A bar below reads "Memory and retrieved records enter context. Their authority comes from their source." Then, in red, "One fact, one authority." The last line reads "SSoR records what happened and the evidence. Payment status remains authoritative in the accounting system."](img/five-places.png) *Figure 8.1. Five places an answer comes from.* Figure 8.2 asks one question about current state, whether invoice 5149 is paid, and shows five answers that might come back. ![The title asks "Is invoice 5149 paid right now?" The line below it reads "Verify current recorded status in the accounting system." On the left, under "Useful evidence," four cards. Memory, a remembered status, "5149 was paid," which supports continuity but does not verify current status. Snapshot, the saved status list of 23 October, "5149: on hold," evidence of the status recorded on that date. SSoR, the latest known case state of 30 October, "Paid in the 30 October run," which preserves the case record but still needs a fresh check. Reported, a vendor email of 2 November, "Still unpaid," a discrepancy to investigate, not a status override. Below the cards: "Evidence can be valid without being current." An arrow labeled "Verify" points to a box on the right, "Read the accounting system now," the authority for recorded payment status. It reads "Check before answering or acting" and lists status, payment reference, read time, source and unresolved discrepancies. Part II, a human check: a person reads the system and records what it shows. Part IV, governed execution: DSoR reads for the worker and checks actions against delegated authority. A banner at the foot reads "SSoR preserves the case. The accounting system verifies its current payment status."](img/current-state.png) *Figure 8.2. Memory, an old snapshot, SSoR's latest-known line and a vendor's email may each be true, but none settles whether 5149 is paid now. Only the accounting system, read now, settles it. In Part IV, DSoR does that reading for the worker.* [^ssor]: SSoR, the State System of Record, Panaversity. [^ksor]: KSoR, the Knowledge System of Record, Panaversity. [^dsor]: DSoR, the Data System of Record, Panaversity. [^v1-system-of-context]: The System of Context, Panaversity, first edition.