store.sgit.ai

site v0.3.24

Every agent needs a licence to operate. This is where you buy one. Six offers: four tiers with a price and a code, and two add-ons priced by depth band. The paid thing is not access and it is not customisation. It is independence.

What is sold here is an instance. The free public library lives on the platform site and is not sold. Prices are in pounds. Two of the six offers do not exist yet and say so on their own row: the signed-opinion wording has not been written, and the check that proves every rendered variant carries the same facts has not been built, so the guarantee that would make the multi-format add-on worth buying is not printed anywhere on this site.

Nothing here is a compliance assessment and no page claims conformity to any standard. Outputs are model generated and marked as such. Every finding that reaches a buyer has been reproduced rather than reviewed: recall-optimised agents run at 0.388 precision, so what is sold is triage and never raw findings.

Every factual claim on this site carries one of ten states — exists, measured, read-not-run, projected, specified-not-built, specified-never-run, built-not-located, a-booking, part-exists, does-not-exist-yet. The full list is at /ledger/. Every page is also served as markdown at <page>/index.md. No page on this site that sells anything opens a network connection at all; two kinds of page do and each says so on itself — a review under /admin/reviews/ embeds the vault it reviews, and a page under /paid/ embeds one published example vault. Both from one host. Nothing here sends anything about a reader, on any page.

Offer identifiers are stable and the host is not: a payment code redirects to /d/<id>/, so this site can move host without reprinting a card or reissuing a link. Licence: This document is released under the Creative Commons Attribution 4.0 International licence (CC BY 4.0).

Pages

• The console↗: The operations surface for this store: what is blocking a first paid order, the units of work in flight, the memo queue behind them, the payment rails, the reviews and the walkthrough. Public, like every page here, and kept out of the sitemap because it is not a selling surface.
• Run the whole flow yourself↗: A walkthrough of store.sgit.ai from the catalogue to the page after payment, for a person and for an agent. It takes about four minutes, it costs nothing, and the discount codes that make it free are printed on this page.
• Booking a person↗: Two of the four tiers are a booking rather than a download: a person reviewing your situation, and an assessment by a team. What a booking commits, what it does not, and why a signature is a separate thing you cannot buy yet.
• Who owns what, between this store and riskmandate.ai↗: The boundary between store.sgit.ai and riskmandate.ai, written down where both sides' agents can read it: the store owns e-commerce, riskmandate.ai owns the products and the policies, and neither sends the other's visitors away. Includes the brief asking their team to do the reverse.
• What is not for sale yet↗: Eight further offers are specified and none of them is for this week. They are listed so that nobody proposes them as new, and so that the four that are for sale are not quietly widened to include them.
• The dev packs↗: The area is built and the documents are held. Nineteen documents, every one of them hashed and listed, none of them published — because five checks run before anything opens, none has been run by a person, and two of them a script can already show would fail.
• What we do not say, and why↗: The words this site does not use, the sentence it does not print, the claims it does not make, and the reason for each one. Every entry has a source, and most of them have an enforcement precedent behind them.
• How buying works↗: Pick shapes, pick levels, and pay on the provider's own page. Your order lives in your browser, the payment provider takes your name and card, and what reaches it is an amount and an order reference carrying the codes for what you bought.
• Five prototypes of one purchase↗: Five interfaces over the same configurator for the grant-and-mandate mapping work: an interview, a ladder, an estate board, a delta matrix and a scenario start. Each produces the same JSON brief. Nothing on any of them can be bought.
• All six, side by side↗: The four tiers and the two add-ons in one table: the question each answers, its price, what is true of the thing behind it today, how it is paid, and the stable offer identifier a printed code redirects to.
• The two rails, and why they never meet↗: Payment links with printed codes for everything at the event and everything below about a thousand pounds; the cloud marketplace for business buyers above it, after a conversation. They are strictly separated, the separation is a rule rather than a preference, and no link has been issued yet.
• The review moved↗: The partner review that was published here in v0.1.15 now lives in the review register at /admin/reviews/, with every other review, dated and sorted.
• Every agent needs a licence to operate↗: Agent Behaviour Policies for the agents you already run: everything one can do, what you authorised it to do, and the gap between them. Fifteen applications, four levels — the pack at £10, a vault you hold the keys to at £50, corrected for your situation at £500, and two sessions with a security professional signing it at £1,500.
• The three buyers, and what each one buys↗: Three buyers, ordered by opportunity rather than presented as three equal doors: a team running agents they already granted credentials to, an investor backing a company, and a startup about to meet diligence. Which of the six offers each one is shown, which were actually built for them, and — for one of the three — that none were.
• What each level actually gets you↗: Every level side by side, including the free one: what you get, whose work it is, what you may do with it, and when it arrives. Fourteen rows, five columns, and every cell read off the offer data rather than written as copy.
• Every claim on this site, with its state↗: One row per factual claim: what it says, the state it earned, how we know, and every page that says it. A claim cannot appear on a page here without appearing in this table first.
• Which agent do you run?↗: Fifteen Agent Behaviour Policies, one per application, at four levels: the pack downloaded at £5, a working vault you hold the keys to at £50, corrected against your situation at £500, and two sessions with a security professional signing it at £1,500.
• Release history↗: Every release of this site, what changed in it, and the commit it was built from. The version is owned by one file, the release commit's subject repeats it, and the pipeline refuses to tag if the two disagree.
• What is actually in one↗: The four objects inside an Agent Behaviour Policy and the order they come in: the mandate, the grant, the delta and the barrier. Why there is no score on anything here and never will be. And the difference between the free template and the thing that is priced.

Who each offer was built for

Three buyers, ordered by opportunity rather than presented as three equal doors. The grouping is a second index over the same six offers: it adds no offer and no price.

• agents — You run agents today — asks "What did I actually grant it?" — built for them: t1, t2 — also shown: add-formats — https://store.sgit.ai/for/agents/↗
• investors — You are backing a company, and want somebody to look — asks "What would somebody who knows what they are doing find?" — built for them: t3, t4 — also shown: add-opinion, add-formats — https://store.sgit.ai/for/investors/↗
• startups — You are a startup, and diligence is coming — asks "What is diligence going to find before it finds it?" — built for them: NOTHING — every offer shown there was built for another buyer — also shown: t3, t4, t2, add-formats — https://store.sgit.ai/for/startups/↗

Offers, and where each code lands

• t1 — £10 — Can I just have the pack? — for: agents — https://store.sgit.ai/d/t1/↗ — checkout: https://buy.stripe.com/dRmbITfDa7E31Z8fY15os03 ↗
• t2 — £50 — Can I have a vault I hold the keys to? — for: agents — https://store.sgit.ai/d/t2/↗ — checkout: no payment link (fixed) — One price means one standing payment link, printable on a card.
• t3 — £500 — Can you correct it for my situation? — for: startups — https://store.sgit.ai/d/t3/↗ — checkout: no payment link (fixed) — One price means one standing payment link, printable on a card.
• t4 — £1,500 — Can somebody go through it with my team? — for: investors — https://store.sgit.ai/d/t4/↗ — checkout: no payment link (fixed) — One price means one standing payment link, printable on a card.
• add-formats — By depth band — Can I have the same result in a form the board will read? — for: any — https://store.sgit.ai/d/add-formats/↗ — checkout: no payment link (attached) — This attaches to another offer and is priced against its depth band, so it has no checkout of its own.
• add-opinion — By depth band — Will somebody put their name to it? — for: investors — no code behind it yet — checkout: no payment link (none) — There is no code behind this one.

No payment link has been created for any offer on this site: every checkout_url in data/offers.yml is empty, so each offer shows its code and its delivery page rather than a button. A standing payment link carries one price, so only the single-priced tier can ever have one; the two banded tiers take a link issued once the band is fixed, and the top tier goes by invoice after a conversation. Any URL that does land there is held by the build to the payment provider's own checkout hosts over HTTPS.