store.sgit.ai / All six, side by side
All six, side by side
Four tiers and two add-ons. Four prices are set, one range is deliberately wide, and the add-ons are banded rather than priced. Every number on this page comes from one file, and a build check holds each of them against the pack that set it — because these prices go onto printed cards, and a printed price cannot be corrected from a conference floor.
The table
| The question it answers | Price | What is true of it today | How it is paid | Offer id | |
|---|---|---|---|---|---|
| Tier 1 | What did I actually grant it? | £10 | built, not located | Payment link | t1 |
| Tier 2 | Which parts of the regulation actually reach me? | £50 to £100 | specified, not built | Payment link | t2 |
| Tier 3 | Will somebody look at my situation with me? | £150 to £1,000 | a booking, not a download | Payment link | t3 |
| Tier 4 | What would a team of security professionals find? | £5,000 to £10,000 | specified, never run | Invoice and bank transfer | t4 |
| Add-on | Can I have the same result in a form the board will read? | By depth band | part exists | Payment link | add-formats |
| Add-on | Will somebody put their name to it? | By depth band | does not exist yet | Not for sale yet | add-opinion |
The offer id is the stable part. A payment link redirects to /d/<id>/, so this site can move host without reprinting a card or reissuing a link.
The six, in full
What did I actually grant it?
Your own answers, your measured grant, and the delta between them, as a file you keep.
built, not located An application built in August may exist and has not been located. Until it is found, this is a questions page, and this page does not promise more than that.
Payment link. A link, and a printed code beside it. An online payment, so no cross-border rule applies to it.
What arrives, and what does not →Which parts of the regulation actually reach me?
Only the provisions of the regulation that reach your situation, with the fact that caused each provision to arrive visible beside it, as a vault you own.
specified, not built Specified 28 July. The graph exists at 1,523 nodes with amendments applied. The pipeline that turns a situation into a vault does not exist.
Payment link. A link, and a printed code beside it. An online payment, so no cross-border rule applies to it.
What arrives, and what does not →Will somebody look at my situation with me?
A person reviewing your situation, and running a vault for you.
a booking, not a download A booking, not a download. This tier overlaps the signed-opinion add-on, and the overlap is recorded and unresolved — so the two are sold separately and the page says which one you are buying.
Payment link. A link, and a printed code beside it. An online payment, so no cross-border rule applies to it.
What arrives, and what does not →What would a team of security professionals find?
An assessment by security professionals.
specified, never run A booking with a deposit. The seven-role team is specified and has never run. You would be the first, and the price reflects it.
Invoice and bank transfer. Above about £1,000 a card stops making sense. This one starts with a conversation.
What arrives, and what does not →The two add-ons
Both attach to an offer above and are priced against its depth band. Neither is a tier, and neither can be bought on its own.
Can I have the same result in a form the board will read?
The same result as a document, a deck, an infographic, and in a second language.
part exists The generator exists. The check that proves every variant carries the same facts does not, so the guarantee that would make this worth buying is not printed here yet.
Payment link. A link, and a printed code beside it. An online payment, so no cross-border rule applies to it.
What arrives, and what does not →Will somebody put their name to it?
A reviewed opinion, issued by the company, signed by a named professional.
does not exist yet The wording does not exist. It has to, before a first signature — so this add-on is listed and cannot yet be bought.
Not for sale yet. There is no code behind this one.
No code behind this one yetWhy each number is that number
No price on this site was invented, and none of them is positioning. Three of the six are arithmetic and the workings are here.
| The number | Why it is that number |
|---|---|
| £10 — What did I actually grant it? | The floor is arithmetic, not positioning. At £5 the fixed card fee alone is about four per cent of the transaction |
| £50 to £100 — Which parts of the regulation actually reach me? | A band, not a number. Where a case lands inside it depends on how much of the graph the situation touches |
| £150 to £1,000 — Will somebody look at my situation with me? | The width is deliberate. It is a person's time, and the range covers an hour at one end and a working week at the other |
| £5,000 to £10,000 — What would a team of security professionals find? | Above about £1,000 a card stops making sense — at £10,000 the card fee alone reaches roughly £250 — so this tier goes by invoice and bank transfer, or through the cloud marketplace after a conversation |
| By depth band — Can I have the same result in a form the board will read? | Priced against the depth band of the offer it attaches to, because the work is the rendering and the rendering scales with what there is to render |
| By depth band — Will somebody put their name to it? | Priced against the depth band of the offer it attaches to |
The floor is the clearest of them: at £5 the fixed card fee alone is about four per cent of the transaction, so £10 is the floor and £5 is not a cheaper version of it — it is a worse one. At the other end, at £10,000 a card costs up to about £250, which is why tier 4 does not take one. projected 10 Sep 2026
Prices are in pounds. Pricing in euros while settling in pounds adds about two per cent, and that two per cent buys nothing. projected 10 Sep 2026
The offer identifier is the stable part
A printed code redirects to /d/<id>/ and nothing else about it is load-bearing. Not the host, not the path above it, not a word of the copy.
That is deliberate, and it is the one piece of engineering this site does purely because of a disagreement. A ruling of 10 September placed a storefront under the risk product rather than on the platform domain. The instruction in hand overrode it and named this host. The ruling stands on the record, unedited, and the build treats the host as moveable: every internal link here is relative, the host appears in no sentence of copy, and the identifiers above do not change. If the site moves, it costs a DNS record and no reprinting. read, not run 10 Sep 2026
What is not on this page
Eight further offers are specified and none of them is for this week. The amendment subscription, the divergence report, the rendering diff as a verification service, crosswalk resolution, the write-only vault link, the vault as a data room, the threat-model estate, and the infographic generator with a purchase page. They are listed here so that nobody proposes them as new.
The six offers → Every claim on this site, with its state → What we do not say →