# 4.2 KSoR knows (/ai-worker-paradigm/the-architecture-in-one-picture/ksor-knows) --- type: Document title: "4.2 KSoR knows" description: "The layer that holds what a company officially knows, kept as one approved record that people and workers both read." status: stable order: 104.2 ksor: owner: team:panaversity audience: [ public ] approval: by: process:panaversity at: 2026-10-15T12:46:14Z chapter: "04" part: I expert_status: required concepts: [ "4.2" ] last_verified: 2026-10-04 sources: - id: ksor title: "KSoR, the Knowledge System of Record (Panaversity, GitHub, verified 2026-10-04)" resource: https://github.com/panaversity/ksor generated: at: 2026-10-15T12:46:14Z by: esl-rewrite/1.2.0+ksor.1 trust_tier: unverified build_id: sha256:46fd53c5d7ab1c14f6347908d45c9fdaecda4d914439923ee878bdcecd57803e dirty: true ksor_version: 0.0.60 --- **In everyday life.** A school puts one official term calendar on its website, instead of a different date in each teacher's handout. A **KSoR**, or Knowledge System of Record, is the governed, authoritative knowledge layer. It holds what the organization officially knows and how it operates: policies, procedures, thresholds and definitions. Its design fits in one line: **one authoritative record**, **one governance boundary**, **many open projections**.[^ksor] In plain words: one official copy, one way to change it, and many ways to read it. ![KSoR knows: the school calendar. A school puts one official term calendar on its website, instead of a different date in each teacher's handout. A laptop shows the school website's term calendar, marked as the official copy, version 3, approved. Beside it, three teacher handouts each give a different date for term 1, and each is crossed out. On the desk, books labeled official calendar, policies, procedures and definitions. A side panel lists what a KSoR holds. Policies are the official rules with versions and an owner, procedures are step-by-step instructions, thresholds are limits such as approval amounts, and definitions are common terms in one place. Below it, one record and three rules. One authoritative record, where a new version replaces the old one. One governance boundary, where changes go through review and approval. Many open projections, where people and workers read the same record. The banner reads: one official copy, one way to change it, and many ways to read it. A worker reading a KSoR names the exact version it used, and says so when the record has no answer.](img/school-calendar.png) *The school calendar. One official copy on the website, and the handouts lose.* - **One authoritative record.** There is one AP policy, not one in a project and another in an email. A new version replaces the old one in the record, and the old one is marked as retired. - **One governance boundary.** Knowledge changes through review and approval by a named person, and every version is kept. A draft is not policy until someone with authority approves it. Each version has the date it takes effect, and the version in force on the day of a decision governs that decision. An August invoice paid in October is judged by version 3. - **Many open projections.** People read the record as pages. Workers read the same record through a governed interface: the worker sends a question and gets back the passage that answers it, with its version and owner, or nothing. The record's header, its owner, version and approval date, travels with every projection. Nobody keeps a separate copy for the machines. A worker reading a KSoR can do two things that a worker reading a loose file cannot. It **cites**: every answer points to the approved concept and version it came from. And it **abstains**: when the record does not contain the answer, it says so instead of filling the gap with whatever the model knows.[^ksor] In a run at night, the KSoR gives the worker an answer it can cite, or a flag when the record is silent. At nine, it gives the person a citation to check in ten seconds. A KSoR starts small, with the sources the role names, and each abstention is a request for the next entry, which the record's owner decides. A fact about a vendor is current state, read from the record. What to do about it is knowledge, and when the record is silent the worker abstains. Wednesday's failure was a knowledge failure. The approved policy existed, but it was badly published, and the worker answered from the retired copy it could see. With a KSoR, version 3 of the approval-limits entry would be the only approved version, owned by Dave and dated September 1. The answer would read "Yes. Invoices over $5,000 need the controller's approval (AP policy v3, approved September 1)." Maria could check that citation in ten seconds. This book is kept in a KSoR of that kind: a repository of pages with versions, owners and approvals, read by people as a site and by workers through a connector. [^ksor]: KSoR, the Knowledge System of Record, Panaversity.