store.sgit.ai / Every claim on this site, with its state
Every claim on this site, with its state
Every factual claim this site makes lives here once, with the state it earned and the date it earned it. Pages cite a claim rather than restating it, so the same fact cannot be strong on one page and hedged on another. The rightmost column is joined at build time: it shows where each claim is actually said, and it is not editable by hand.
The ledger
1exists and runs
1measured
10read, not run
2projected
2specified, not built
1specified, never run
1built, not located
1a booking, not a download
4does not exist yet
The state of each thing on the offer list
| Claim | State | How we know | Where it is said |
|---|---|---|---|
| The application that would compute tier 1's delta was built in August and has not been located. Until it is, tier 1 is a questions page, and this site says so on the offer, on the delivery page and here. | built, not located 10 Sep 2026 | 01__WHAT-TO-BUILD.md, the tier table | home |
| Tier 2 was specified on 28 July. The graph it selects from exists at 1,523 nodes with amendments applied. The pipeline that turns a situation into a vault does not exist. | specified, not built 28 Jul 2026 | 01__WHAT-TO-BUILD.md, the tier table | home |
| Tier 3 is a booking, and it overlaps the signed-opinion add-on. The overlap is recorded and unresolved, so the two are sold separately and neither page implies the other. | a booking, not a download 10 Sep 2026 | 01__WHAT-TO-BUILD.md, the tier table | booking |
| Tier 4 is a booking with a deposit. The seven-role team is specified and has never run. A first buyer would be the first run, and the page says so before the conversation, not after it. | specified, never run 10 Sep 2026 | 01__WHAT-TO-BUILD.md, the tier table | home, booking |
| The multi-format add-on's generator exists. The check that every variant renders the same fact set — the diff that must be empty — does not exist, and hard rule 6 forbids printing the guarantee before the check is built. So the guarantee is not printed. | does not exist yet 10 Sep 2026 | 02__THE-HARD-RULES.md, rule 6 | home, catalogue |
| The signed-opinion add-on's wording does not exist, and it must before a first signature. The offer is listed and cannot be bought: there is no code behind it. | does not exist yet 10 Sep 2026 | 01__WHAT-TO-BUILD.md, the add-on rows | home, audiences, booking |
How paying works, and why it works that way
| Claim | State | How we know | Where it is said |
|---|---|---|---|
| A United Kingdom card account cannot tap in Portugal: the provider declines the transaction on detecting a different country, and says so in those words. A payment link is an online payment, so no cross-border rule applies to it. The conclusion the pack draws: no card reader should be bought. | read, not run 10 Sep 2026 | The payment-rail brief, in the pack at /dev-packs/store/ | home, paying |
| At £5 the fixed card fee alone is about four per cent of the transaction, which is why £10 is the floor rather than £5. At £10,000 a card costs up to about £250, which is why the top tier goes by invoice and bank transfer. Arithmetic, not an invoice. | projected 10 Sep 2026 | 01__WHAT-TO-BUILD.md, the price paragraph | booking, offers |
| Prices are in pounds. Pricing in euros while settling in pounds adds about two per cent. | projected 10 Sep 2026 | 01__WHAT-TO-BUILD.md, the price paragraph | offers |
| The cloud marketplace's seller terms state that a seller is not permitted to collect customer payment information at any time. The two rails are therefore strictly separated: the marketplace is not a second button beside the card button, it is a different conversation with a different threshold. | read, not run 10 Sep 2026 | The marketplace brief, in the pack at /dev-packs/store/ | home, paying |
| The marketplace listing fee is 0.5 per cent, and falls to zero inside a qualifying multi-product solution. The pitch is procurement, not discount: the buyer already holds the marketplace's legal terms, so there is no master agreement, no vendor onboarding and no new purchase order. | read, not run 10 Sep 2026 | The marketplace brief, in the pack at /dev-packs/store/ | paying |
| Professional services listings do not draw down committed spend on the cloud provider. Three independent sources state the exclusion. An earlier version of this claim said the opposite; the correction is recorded here rather than quietly dropped, and the old version appears on no page of this site. | read, not run 10 Sep 2026 | The marketplace brief, correction carried in brief 2 of the pack | paying, versions |
| Marketplace registration is the long pole: four to eight weeks. The listing is therefore a November surface, not an event surface, and nothing on this site depends on it. | specified, not built 10 Sep 2026 | 01__WHAT-TO-BUILD.md, the surface table | catalogue, paying |
What a finding is worth, and what may be promised
| Claim | State | How we know | Where it is said |
|---|---|---|---|
| Recall-optimised agents run at 0.388 precision — about three findings in five are wrong. This is the reason the product is triage and never raw findings, and the reason every finding that reaches a buyer has been reproduced rather than reviewed. | measured 10 Sep 2026 | The disclaimer brief, in the pack at /dev-packs/store/ | home, audiences, booking, disclosures |
| The transparency article has applied since 2 August 2026 and reaches a third-country party whose output is used in the Union. Outputs here are model generated and are marked as such on the face of the artefact, not only in a footer. | read, not run 2 Aug 2026 | The disclaimer brief, in the pack at /dev-packs/store/ | home, booking, disclosures, versions |
| The regulation graph exists at 1,523 nodes, with amendments applied. It is the launch catalogue because the European regulation is expressly reusable commercially, including adaptation. | exists and runs 10 Sep 2026 | 01__WHAT-TO-BUILD.md and hard rule 10 | home, disclosures |
| The international management standards are not adapted, translated, resold as a derivative, or fed to a model here — prohibited twice over, once as a derivative and once as a model input. The same prohibition covers the payment card standard and the centre's controls. Nothing on this site is derived from any of them. | read, not run 10 Sep 2026 | 02__THE-HARD-RULES.md, rule 10 | disclosures |
The words this site uses, and the words it does not
| Claim | State | How we know | Where it is said |
|---|---|---|---|
| Tamper evident, given a witness — never the absolute form of that claim, which is false. A rewritten hash chain verifies against itself; tampering is detectable only when another party already holds an older hash. The witness is a second clone, which makes handing somebody a read key the act that makes the claim true. Append-only is stated as a policy, not a property. | read, not run 10 Sep 2026 | 02__THE-HARD-RULES.md, rule 14 | disclosures, versions |
| The sentence a reader expects from an encryption product — the one about what its operator can and cannot see — is not printed on this site in any form, because six questions about what leaks (filenames, directory structure, object sizes, commit timing, recovery or escrow, support access) have not been answered. In November 2020 a regulator acted against a company for claiming end-to-end encryption while its servers held the keys; the settlement imposed twenty years of third-party assessments. | does not exist yet 10 Sep 2026 | 02__THE-HARD-RULES.md, rule 13 | home, catalogue, disclosures, versions |
| Licence to operate — a permission granted by an authority, ruled 3 September — collides with a second phrase in the same vocabulary, written 17 July, which describes exposure already carried. They mean opposite things and both are in use. The collision was recorded on 8 September and is still open, so the second phrase appears on no page of this site and a build check keeps it off. | does not exist yet 10 Sep 2026 | 03__THE-NAMES.md, the open collision | disclosures, versions |
| Three contested terms — one for encryption, one for recall, one for autonomy — do not appear anywhere on this site. What is used instead: end-to-end encrypted as the primary term, client-side encryption as the mechanical one, and durable for the property that resumes losslessly. The build fails if any of the three reaches a page. Each is described on the disclosures page. | read, not run 10 Sep 2026 | 02__THE-HARD-RULES.md, rule 12 | disclosures, versions |
The deadline, and what actually depends on it
| Claim | State | How we know | Where it is said |
|---|---|---|---|
| The event is 17 and 18 September 2026, in Lisbon. The offer page and the payment codes are the only parts of this with a hard date. The merchandise surface, the catalogue of eight further offers and the marketplace listing do not depend on it. | read, not run 10 Sep 2026 | 00__START-HERE.md, the deadline | paying |
| 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, in the pack — and the build treats the host as moveable: every internal link is relative, the host appears in no copy, and the offer identifiers are stable. | read, not run 10 Sep 2026 | 00__START-HERE.md and 03__THE-NAMES.md | dev-packs, offers |
What the states mean
Four of the ten states are ways of saying "not yet", and that proportion is the point rather than an embarrassment.
| State | What it means |
|---|---|
| exists and runs | Built, and it runs today |
| measured | Measured by our own pipeline, on a named workload and date |
| read, not run | Read from a published source on this date. Never executed by us |
| projected | Arithmetic, not an invoice. The workings are shown |
| specified, not built | A specification. The thing it specifies does not exist |
| specified, never run | Specified in full, and never executed once |
| built, not located | It was built. It has not been found since, and nothing here promises it until it is |
| a booking, not a download | What is bought is a person's time, not a file |
| part exists | One half runs. The half carrying the guarantee does not |
| does not exist yet | It does not exist. It is listed so nobody proposes it as new |
Why a store publishes one of these
Because checkability is the thing being sold. An offer page that cannot be checked is arguing against the product sitting beside it.
And because the alternative is worse in a specific, predictable way: without a ledger, the sentence "the pipeline does not exist" survives one draft, gets softened to "the pipeline is in development" in the next, and is gone by the third. Here it is a row with a state, cited from the page that makes the claim, and the build fails if a page cites a claim that is not in this table.
The six offers → Every claim on this site, with its state → What we do not say →