store.sgit.ai / What each level actually gets you
What each level actually gets you
Start with the free column. The templates are published with read keys and anybody can take one — so what each paid step adds is only legible next to a column that does not have it. The licence row on its own explains the first step.
| Free£0Published, with read keys | The pack£10 | A working vault£50 | Corrected for you£500 | Two sessions£1,500 | |
|---|---|---|---|---|---|
| What you get | |||||
| The behaviour policy, the grant, the mandate and the deltaThe document itself is the same at every level. What changes is the form it arrives in and who does the correcting. | ✓ | ✓ | ✓ | ✓ | ✓ |
| Packaged as a downloadAt the free level you take the files off the published vault yourself. From the first paid level a zip arrives on the page you land on, with its size and its sha256 beside it. | Take it yourself | ✓ | ✓ | ✓ | ✓ |
| A vault you hold the keys toA vault is versioned, has its own app, and can be handed to somebody with a read key. None of that survives an email, which is the difference between the first paid level and the second. | — | — | ✓ | ✓ | ✓ |
| Your own history, and a read key you can hand onThe property that makes a vault worth more than its contents: a reader you hand the key to sees what you see, and every change is dated. | — | — | ✓ | ✓ | ✓ |
| The public key taken off itA published template carries a read key anybody has. Yours does not. | — | — | ✓ | ✓ | ✓ |
| Whose work it is | |||||
| The mandate corrected against your situationBelow this line the mandate is the starting one, written to be corrected, and correcting it is yours to do. At and above it, that correction is done for you against the industry, the use case and the details you send. | — | — | — | ✓ | ✓ |
| A named security professional does the workThe two upper levels are somebody's time rather than a pipeline, which is why their delivery estimate depends on a calendar. | — | — | — | ✓ | ✓ |
| Reviewed and signed off by that professionalSigned off is not the company issuing a signed opinion as a formal instrument. That wording does not exist on this site and the delivery page keeps the two apart. | — | — | — | — | ✓ |
| Time with them, on a callTwo half-hour sessions: one to find out what is actually running, one to deliver it. | — | — | — | — | Two half hours |
| What you may do with it | |||||
| LicenceThe published files are Creative Commons Attribution, which obliges anybody using them to credit the source wherever it ends up. Every paid level replaces that with a commercial licence to the buyer over the same material. | CC BY — you must attribute | Commercial, to you | Commercial, to you | Commercial, to you | Commercial, to you |
| Use it in client work without crediting usThe practical difference the licence makes, said in the words somebody would actually use it in. | — | ✓ | ✓ | ✓ | ✓ |
| Your name on the licenceFrom the vault level the licence names you, because there is an artefact for it to sit in. | — | — | ✓ | ✓ | ✓ |
| When it arrives | |||||
| DeliveryAt the two upper levels the clock starts when you send the details rather than when you pay, because until then there is nothing to work on. The constraint is one person's calendar. | Now | Immediately | 1 to 2 days | 1 to 3 days from your reply | 1 to 5 days from your reply |
| Paid in full up frontThe two produced levels take the whole price. The two that are somebody's time take a fifth on the order and the rest when the work is in your hands. | Nothing to pay | ✓ | ✓ | A fifth now | A fifth now |
Every cell here is read off data/offers.yml or off a ruling, and a row whose cells would be a promise rather than a description is not on this table yet. What is still being specified is on the board rather than in a column.
How to read it
Every cell is read off something. A price comes from data/offers.yml, a capability from what that level's page says it gets, a licence from a ruling. A row whose five cells would be a promise rather than a description is not on this table — what is still being specified is on the board rather than in a column, because a table is the place where an unproven claim is hardest to notice and easiest to believe.
The free column is not a teaser. Fifteen template shapes are published with read keys, at riskmandate.ai. Go and open one before you buy anything here. That is not generosity and it is not a funnel: a policy nobody can check is a policy asking to be trusted, and the whole point of this document type is that it can be checked. exists and runs 15 Sep 2026
The licence is the first step, and it is the one worth understanding. What is published is Creative Commons Attribution, which obliges anybody using it to credit the source wherever it ends up — in a client report, inside a product, in a document that goes to a regulator. The paid levels replace that with a commercial licence to you over the same material. That is grantable because the copyright in the pack is ours: everything in it was written here. The wording is not drafted yet, and the ledger says so rather than this page implying otherwise. read, not run 16 Sep 2026
The line that matters most is between the second and third rows of the middle group. Below it, the mandate is the starting one — written to be corrected, and correcting it is yours to do. At and above it, a named security professional does that correction against the industry, the use case and the details you send. delivered by a person 15 Sep 2026 delivered by a person 15 Sep 2026
Which agent do you run? → How buying works → Every claim, with its state →