Who you are
For the owner
You decide whether Saphan Studio is deployed and what it is allowed to do.
| Who this is for | You are the person who owns the decision to run this product, and answers for it afterwards. |
| What you need | An hour, and no terminal. |
Your first task: decide whether the product's data posture is one your organisation can accept. That is a reading task, it needs no terminal, and it is the decision every other one below depends on.
Read these three, in this order
| Go here | Because |
|---|---|
| 1 · What the product does for you | The only section written to be read straight through. Everything else assumes it. |
| 2 · What it will ask of your organisation | Your machines, your record: what runs where, what you are asked to own, and what the product deliberately does not do for you. |
| 3 · What you are accountable for | The record kept on your behalf, and what it lets you answer when someone asks. |
Then, when the answer is yes
| Go here | Because |
|---|---|
| The delivery routes | How little each machine actually receives. |
| Human gates | The decision only you make, and why the product shows you a command instead of running it. |
| What it costs and what stops it | The ceiling a run is stopped at, and who sets it. |
The limits that are yours to weigh
- The product does not decide. Every merge waits for a human act, and that human is you or someone you delegate to. A fleet nobody gates does not run.
- What it proves has an edge, and that edge is written down rather than implied — what this does not prove.
- Some capabilities are built and not exercised on every platform. Where that is true, the page says which platform was measured; a reading from one platform is not a guarantee on another.