Who you are
Five reading paths, one per job: what you own, what to read first, and the first task you can perform.
This section is for choosing a path rather than for reading straight through. Saphan Studio is answered for by several different people, and the same documentation serves them in a different order. Pick the row that matches what you are accountable for.
Each page below states the same four things: what that reader owns, the first three pages to read in order, the first task they can perform, and the limits that matter to their job.
| You are | Start here | Your first task |
|---|---|---|
| Accountable for the decision to run this product | For the owner | Decide whether the data posture is one your organisation can accept |
| The person who installs and runs it | For devops | Get one machine installed and reach the setup screen |
| Accountable for what it spends | For the finance controller | Understand how a run's ceiling is derived from its quote |
| Establishing what happened, and whether the record holds | For the auditor | Establish which properties of the record hold by construction |
| Signing off on the boundary | For the security officer | Read what the product declines to claim |
No prerequisites. These pages assume nothing installed and no terminal.
What this section does not cover
⚠ A role page routes; it does not teach. None of them explains a mechanism — each one sends you to the section that does, in the order that works for that job. If you would rather learn the vocabulary first, Concepts is written to be read straight through.
⚠ There is no page for the person extending the product. This documentation is written for operating Saphan Studio, not for building against it.