# 4.4 SSoR tracks where the work stands (/ai-worker-paradigm/the-architecture-in-one-picture/ssor-tracks)

---
type: Document
title: "4.4 SSoR tracks where the work stands"
description: "The layer that keeps one governed case file for each piece of work, so a worker reads where the work stands instead of guessing, and how it differs from memory and DSoR."
status: stable
order: 104.4
ksor:
  owner: team:panaversity
  audience: [ public ]
  approval:
    by: process:panaversity
    at: 2026-10-12T23:51:55Z
chapter: "04"
part: I
expert_status: required
concepts: [ "4.4" ]
last_verified: 2026-10-13
sources:
  - id: ssor
    title: "SSoR, the State System of Record (Panaversity, GitHub, verified 2026-10-13)"
    resource: https://github.com/panaversity/ssor
generated:
  at: 2026-10-12T23:51:55Z
  by: process:panaversity
trust_tier: unverified
build_id: sha256:2f1e14f2a0f11dbc37eb5856ca9b7d35b4ce4894da74c3328cf61a3c17c03861
dirty: true
ksor_version: 0.0.60
---

**In everyday life.** A garage keeps one job card for each car. It shows what the customer reported, what was checked, which repair the customer approved, and what is still waiting. A mechanic who starts the next shift reads the card, not their memory.

An **SSoR**, or State System of Record, is the governed memory of the work. It keeps one case file for each **matter**. A matter is a piece of work carried to an end, such as an invoice from the day it arrives to the day it is paid. The case file says where the matter stands and how it got there. It keeps the evidence for each step: what was tried, what failed, who approved what, and why.[^ssor]

Three rules make it a system of record, not a notebook.

- **Each entry is checked when it is added.** People, systems and workers add steps, under rules about who may add what. Nobody records a step for someone else.
- **Nothing is overwritten.** A correction is a new entry, and the old one stays, so anyone can see how the matter got here.
- **It records. It does not act.** The SSoR does not pay an invoice or start a run. DSoR acts, and triggers start the work (Chapter 9).

The SSoR sits between two layers that it is easy to confuse it with.

- Memory is the worker's own continuity. It has no owner and no history. A case file belongs to the company, and every step in it can be traced.
- DSoR checks each action and acts. It reads the company's systems for business facts, such as whether an invoice is paid. The SSoR keeps the story of each matter: what happened, what it waits for, and why.

Thursday's failure shows how they work together. The worker marked invoice 5120 "approved by Dave" because an email said so. The approval itself is made in the accounting system, from Dave's own login, and DSoR checks for it before any payment (4.5). The case file is where the worker records what it saw and did, and where anyone reads where the invoice stands. One entry reads "October 15, 7:42 a.m. Email from a lookalike address claims Dave's approval. Flagged to Dave. Not an approval." The next reads "Waiting for Dave's approval of the run." A person or a worker who picks up the invoice tomorrow starts from those lines, not from a guess.

In the governance rule (4.7), SSoR governs what a worker may take as true right now. For invoice 5120, that is the last line of its case file, not an email and not the worker's own note.

**SSoR in this book.** SSoR is at the idea stage. Panaversity has published its design as a proposal, with no specification or code yet.[^ssor] In Part II you keep each matter's case file by hand. Part IV teaches SSoR in depth, in Chapter 29.

[^ssor]: SSoR, the State System of Record, Panaversity.