Built by itself, with receipts

Saphan Studio is developed with Saphan Studio: its own changes enter as orders, pass the same gates, reviews and merges, and leave the same kind of record — costs, refusals and observed git facts included — that your fleet will leave in yours.

What that is worth to you is narrower than it sounds, and it is stated here so it is not overstated elsewhere: it is not evidence you can check. That record belongs to its own workspace, and this site publishes no measurements of it. The evidence you can verify is the record your own installation keeps — see Audit and compliance for what it guarantees and how to check it without trusting the machine that produced it.

What the practice does produce, and what you will see on every page here, is the habit of naming a failure as a class with a cure rather than as an incident: a refusal carries its reason and the next performable act, and a capability that is built but not exercised says so on the page that owns it.