1 · The nine sections, fixed
Not added to, not reordered, not merged. A provider page that skips §9 is the thing this family exists not to be.
| # | Section | What it is for |
|---|---|---|
| 1 | Disclosure | One line: commercial relationship, or none, with the date it was checked |
| 2 | What it grants | The capability block — verb × object class × reach, reversibility marked — in two layers: what the platform can grant per product, and what your scoped key grants |
| 3 | Which pattern | Which of the four↗ this provider supports and which it forbids, per product |
| 4 | Where the key goes | The exact mechanism, quoted with the product it belongs to, the URL and the date read |
| 5 | The bounding primitive | What caps the blast radius — and what it does not cap |
| 6 | The minimal working example | The smallest thing that runs, as a file rather than a snippet |
| 7 | What we use it for | Named workloads, so the page is a report rather than a tutorial |
| 8 | What it cost | Date, workload size, model, request count, price. These go stale fastest |
| 9 | What went wrong | The failures, the limits hit, the surprises. The section nobody else writes |
Sections 8 and 9 get the visual weight. If a reader takes one screenshot from a provider site, it should be §9.