Documentation
Every System runs behind a declared wall — fixed egress, scoped credentials, your approval for consequential actions — and anything outside the wall is refused by construction. These pages describe how that is put together, and say where a part of it is written but not yet in service.
About this copy
Written 2026-09-05 against the two documents below. It is PROVISIONAL pending FG-8 ratification, and the pages are corrected as the product changes rather than kept as a promise of what it will become.
- Brand voice M0 v1 — sha256
- 4d0a739fabc71284d008d9776925a3cbb8589bcf9eee576beb2975dc1c31755b
- Product delivery plan v1 — sha256
- 8b30d1a90cd3433c73d920f64c54e9045cdfbea8873ebf5ffd723c8d279f213c
For customers
Getting started
The path from subscribing to a box that runs a System, as the product works today.
Bring your own keys
You supply the model API key. What that means for your bill, your rate limits and your outages.
Approvals
How an approval request is made, bound and answered — and which part of it has never run.
Billing
Price, the founding rate, and what happens to your box when a plan is cancelled.
For System authors
Elsewhere on this site
- How confinement works — the wall, and the System we refused, rendered from the vetted artifact.
- Systems — the catalog, with each System's manifest and content digest.
- Pricing, Terms, Privacy, Refund policy.