Skip to content
Sattari

Systems fail in the gaps between the people responsible for their parts.

Sattari reads a system whole: what it is for, what composes it, how the parts relate, and where it is and is not tested against the world. The work is for the person who owns the whole, and it begins by deciding where the system ends.

How people arrive

  • Something is wrong and no one can find it.

    A fault that has outlasted its fixes, a recurring incident, a backlog that returns.

    Fault Investigation
  • You have inherited a system and need to know what you have.

    Before you act on it, and before someone else forces the question.

    The Reading
  • You have grown past how you are organized.

    Years of growth, turnover, or incremental workarounds have left a structure that no longer follows from what the system is meant to do.

    Design Derivation
  • A report has named your organization.

    A grand jury, an auditor, a regulator, or an accreditor has found a problem and left the answer to you.

    The Reading

What a Reading is

Every system is described twice: once in the documents that say how it should work, and once in the way it actually behaves. A Reading is an independent account of the second—why the system behaves as it does, and what no one inside it can see from where they sit. The system may be an organization, a program within one, a technical system, or one that runs across organizations. It is delivered as a written report and a working session. The question a Reading answers is, what do we have?

Where every part must be examined and scored, the work is the Grade. Where one specific fault must be traced to its source and its remedy defined, it is a Fault Investigation.

The Reading

On what terms

The work is commissioned by whoever answers for the whole system, such as an agency head, a chief executive, a program director, or a board. A Reading commissioned from inside one part stops at that part’s edge. Every engagement begins with a written fee ceiling and a first milestone that settles what the system is for and where it ends.

Our independence is built into the terms. Findings are delivered unedited, and we decline any engagement where a conclusion or remedy has already been chosen. We neither pay nor accept referral fees, and we never carry out the remedy—leaving us with no stake in what we find.

Engagement Conditions

The discipline

Every specialist holds a part of a system. Systems ontology takes the whole as its object: what a system actually is, apart from how it is described, divided, or measured. It is an old competence with a new name, and this firm exists to practice it, publish it, and in time teach it.

Our readings of public systems are published in full, so the method can be judged on cases anyone can check.

The Discipline

Published readings

The Horizon Scandal — Branch Accounting and Enforcement at the UK Post Office

International · Post Office Limited, United Kingdom · November 15, 2026 · 3 findings

The United Kingdom’s Post Office does not staff most of its branches. It contracts other people to run them, and it built a system to account for the money each branch holds and to settle any difference. Horizon, the software at the center of the scandal, was one part of that system: the part that produced the figure a branch was measured against. This reading sets the software aside at the start and asks the prior question the method asks of anything built: what was the whole system meant to do, and what must any system built to do that contain? Worked forward from the system’s own purpose, the failure is not the software errors the courts later found. It is a function the design never included, absent on the day the system was drawn, years before the first error made it visible.

All publications

Begin with the situation

Tell us what you own and what has happened, and we will tell you which engagement fits. We reply within two business days, and the first conversation is free.

Begin