store.sgit.ai / Five prototypes of one purchase
Five prototypes of one purchase
Nothing in this area can be bought. These are five prototypes of a purchase flow for work that is fulfilled by people — mapping what the agents a company already runs were granted, what they are expected to do, and writing the policies that would close the gap. Five interfaces, one model, and one JSON brief that every one of them produces identically. The interface is the variable. The document is not.
What is actually being sold here
Two things, and neither of them is a scan.
A map. Every agent surface a company runs, the credential behind it, and what that credential permits. Then the other half: what each one is actually authorised and expected to do. The gap between the two lists is the product — permitted, and nothing anybody wrote down would need it.
A policy set that would close it. Written against the estate that was just described, one policy per gap, each naming the grant it constrains. Not a template with a company name substituted in.
A team does this work. Nothing in it runs by itself today, the team specified for it has never run, and which parts of it could later be done without people is a decision nobody has taken. specified, never run 11 Sep 2026 So what these pages produce is the brief that team starts from — the thing a first call would otherwise be spent assembling.
The same question, from three sides
The three buyers on this site arrive at the same map from different directions, and the configurator changes its frame accordingly. Who each one is for.
| Arrives asking | What the map is drawn for | |
|---|---|---|
| You are a startup | What does our estate look like to somebody who is about to ask? | Map it upwards. Diligence is coming, the questions are the same every time, and the difference is whether the answers already exist in writing |
| You are an investor | What is the agent in this company actually doing, and what was it allowed to do? | Map both sides of a company you do not operate: the permitted half from its credentials, the expected half from its own account |
| You run agents today | What did we actually grant the things we are already running? | Map your own estate. The credentials were issued over months by different people, and no document says what their union permits |
The five
| The prototype | What it is testing | What is wrong with it |
|---|---|---|
| The interview One question per screen, in the order somebody would ask them out loud. | Whether the story carries. The estate is described in the order a person would actually describe it, and the price moves while they talk. | Five screens is five chances to leave. It hides how much is left, and a buyer who cannot see the whole shape cannot tell whether it is worth starting. |
| The ladder Everything on one page, in order, with the ticket pinned beside it. | Whether seeing the whole thing at once beats being walked through it. Closest to an ordinary cart, and the cheapest to be wrong about. | It looks like a form, and a long page of choices is a page people skim to the bottom of and price without reading. |
| The estate board One card per surface, each carrying what it permits and what it is expected to do. | Whether the map is the sale. This is the only view where the deliverable and the configurator are the same object, so the buyer is already holding a rough version of what they would be buying. | It is the most work to fill in, and an empty board is a worse first screen than an empty list. |
| The delta Permitted on the left, expected on the right, and the gap filling itself in between. | Whether the product explains itself. The middle column is the thing being sold, computed live from two lists the buyer ticks, so nobody has to be told what excess authority means. | It asks for both halves before it shows anything, and the honest answer to the right-hand column is often that nothing is written down. |
| The scenario Start from the shape that looks most like you, then correct it. | Whether starting from a guess beats starting from nothing. The corrections are the signal: what somebody removes from a prefilled estate says more than what they add to an empty one. | A scenario that is nearly right gets accepted whole. The brief records which one it started from for exactly that reason, and it is still a risk. |
Each one is a hypothesis about how somebody would rather describe their estate, and each has a column saying what is wrong with it — five options presented with only their strengths is a menu, not an experiment. Which of them becomes the real one, if any, is not decided. specified, not built 11 Sep 2026
The model all five render
Every prototype reads one file. The sections below are the questions, the weight column is what moves the price, and both are published here because a page that asks somebody twenty questions owes them the list before they start, and a weighting a reader cannot see is a price a reader cannot check.
| Section | Options | Weight | Why it is asked |
|---|---|---|---|
| 1. What is running Which of these is already in your environment? | 10 | ×1 | Every one you name becomes a node in the map. Anything you do not name cannot be mapped, and the brief says which ones you were unsure about rather than leaving them out. |
| 2. What it was granted What does the credential behind each of those actually permit? | 12 | ×1 | This is the permitted half of the delta. Tick what the credential CAN do, not what anybody intends to use it for — that is the next question, and keeping them apart is the entire method. |
| 3. What it is supposed to do What is each of them actually authorised and expected to do? | 9 | ×1 | This is the expected half. The delta is the gap between this list and the one above, so a brief with an empty list here has nothing to compute and says so on its own face. |
| 4. What you want out of it Which of these should the team produce? | 9 | ×1 | Each line is a deliverable with a state. Two of them do not exist yet, they are on the list anyway, and the brief carries the reason rather than dropping the row. |
| 5. How the answers are evidenced How much of this should be taken on your word? | 3 | pick one | The cheapest version of this work is your own account, written down properly. The expensive version is somebody checking it. Both are real products and the difference is stated rather than assumed. |
Where a total lands
| Weighted total | The tier it names | What that band is |
|---|---|---|
| up to 8 | t1 — £10 | A small estate, your own account of it, and the delta between the two halves. |
| up to 18 | t2 — £50 to £100 | Enough surfaces that the map is worth drawing, and the regulation slice attached to it. |
| up to 34 | t3 — £150 to £1,000 | Wide enough that somebody should read it with you rather than hand it over. |
| above that | t4 — £5,000 to £10,000 | An estate, not a project. This one starts with a conversation and a written scope. |
The five prebaked starts
| Scenario | Track | Surfaces / grants / mandates |
|---|---|---|
| Shipping fast, two people, everything wired to everything A coding assistant with a shell, a hosted app builder, and one automation nobody has looked at since it was wired. | You are a startup | 3 / 6 / 2 |
| An agent answering customers, and a support desk behind it The one where the grant nobody questions is the customer record, because answering questions obviously needs it. | You run agents | 2 / 3 / 2 |
| Something on the payment path The smallest estate on this list and the one with the shortest distance between a mistake and a refund. | You run agents | 2 / 4 / 2 |
| One portfolio company, both sides of it The permitted side from their credentials, the expected side from their own account, and the distance between them. | You are an investor | 4 / 6 / 3 |
| A whole estate, issued by different people over a year Nobody wrote the union of these down, which is the reason it is worth writing down. | You run agents | 7 / 10 / 6 |
The configurator does not compute a price. Weighted selections add up, the total lands in a band, and the band names one of the four tiers that already exist and its price. Nothing here invents a number — a price is the first thing the pack says may not be invented, and a checkout that emitted "£347" would be inventing one with extra steps. A build check fails the release if a band names an offer that is not on the offer list. exists and runs 11 Sep 2026
The prebaked starts are hypotheses. Nobody has counted how common any of those five shapes is. Each brief records which one it started from, so the team reading it can tell what was assumed from what was answered — which is the only thing that makes starting from a guess safe rather than fast. specified, not built 11 Sep 2026
What a brief carries, including what it does not know
The output is one JSON document. Beside the estate, the grants, the mandates and the deliverables, every brief carries two fields that most configurators would not emit:
excess_authority— the grants you ticked that no mandate on the brief would need. Computed from edges published in the model, so a reader can disagree with a specific edge rather than with a verdict.unknowns— what this brief could not establish. An empty expected column. A deliverable whose thing does not exist yet. A grant that a named surface normally carries and you removed. A brief that names its own gaps is worth more to the team reading it than one that reads as complete and is not, and this is the same discipline the ledger applies to the rest of the site.
What happens to it
Nothing, unless you send it. A brief is written to your browser's own local storage and reaches nothing else. There is no form, input, textarea or select anywhere in this site's output, and no page here opens a network connection — both are build checks rather than intentions — so exporting a brief hands the file to you. exists and runs 11 Sep 2026
What the deliverables look like is a separate question, and it is not answered here. This area is the purchasing half. Examples of what comes out the other end belong on their own pages and do not exist yet.
The six offers → Every claim on this site, with its state → What we do not say →