store.sgit.ai / admin · the shop · the ledger · this page as markdown noindex · not in the sitemap
Produced with model assistance. Every page on this site, and every document in the dev packs area, was drafted with a large language model and reviewed by a person before publication.

/ work / take-the-moves

Take the moves from the concepts

0 of 10 units done. Three homepage directions arrived from outside on 16 September, drawn by a ChatGPT session from the live page. Two of them carry structure worth taking. This is that structure, broken into units, with what each one costs us written on it — because a borrowed idea whose price is not written down gets adopted and then quietly reverted. The critique is at /admin/concepts/ and the panel that tested the same four folds on five readers is at /admin/reviews/2026-09-16-four-homepages/. NOTHING HERE OUTRANKS THE BUY BUTTON. Both the critique and the panel reached the same conclusion by different routes: neither the live store nor any concept has one, and a better shop window on a shop that cannot take money is worth less than the till. take-money stays first.

Queued5

TK-3Rebuild the card anatomy: level and delivery on one line, one action

Identical order in every card so the eye can run down a column: level and delivery on one 12px line, the name, one line of what it is, the price, one sentence, one action.

The claim chips have to go somewhere. They are load-bearing — they are how a reader checks that “delivered by a person” is a thing somebody stood behind, and they are one of the two elements that won the two readers who would spend the most. This is a move, not a deletion.

TK-4Applications as chips, with a sixth that converts the miss

From 02 Guided, which lost the panel four-one and won this outright. One pill per application, each a link, with a sixth reading “something else — from £500”.

A visitor whose agent is not in the list currently reaches the end of a directory. The sixth chip sends them to the level that exists precisely because their deployment is not the template.

TK-5Forty-eight header links down to four

The review's first recommendation and the right one. Three destinations and the order stay in the header; eleven evidence and buying-mechanics destinations move to the footer; eight already have a home in the console.

Two things do not move. The version badge is how a reader knows which build they are quoting, and the model-assistance strip is required above the main element by this repository's own rules with a check that refuses a page without it. They can get quieter. They cannot go to the footer.

Blocked on TK-6, which changes the same fold
TK-6Cut the disclosure strip to one line without moving it

It is two lines on a phone before the headline starts, and the headline starts 358px down. One line with the rest behind the link is the same disclosure at a third of the height.

It stays above main. It is one of the two elements that won the two readers who would sign off £1,500, and a build check holds the floor, so the failure mode is loud rather than silent.

TK-10Show one real reader the same four folds

The one thing that would outweigh the whole panel. Five invented readers cannot tell you what a stranger does, and the weakness is not the sample size — it is that the sample and the thing being sampled have the same author. A bigger panel scales the problem rather than the evidence, and is recorded as won't-do on the review so nobody reads the silence as a plan.

One person who has never seen the store, shown the same four folds at the same two sizes and asked the same six questions.

The project lead, in conversation

Up Next5

TK-1Ship the four-fact strip, every fact linked to its claim

From 01 Marketplace, corrected by the one reader who checks things. Four short statements between the hero and the first product section: fifteen application templates, four levels, six vaults open to read now, the top two signed by a person. Every one of the four is already true here and already in the ledger.

Each item links to its claim. The concept's version has four ticks and not one of them is a link, which is the difference between a trust strip and a claim — and the reason this store can ship the idea and the concept could not.

TK-2Set the price at 42px on every card

The live card sets the price at 28px inline with the delivery estimate, at body weight. Every concept sets it at 42px as the second-largest thing in the card, and every reader shown that version used the prices to compare.

A type-scale change, not a redesign. It is the measurable difference between a card somebody compares and a card somebody reads.

TK-7A short name and a precise subtitle, in the same card

Needs a ruling. The concepts' names are boardroom-legible and this store's are not: “professional review” against “two sessions and a custom vault”. And the live names are the more honest ones — the first says exactly what arrives and the second could describe a phone call.

The proposal is both, in one card: a short name at heading size, the precise description as the line under it. The ruling is whether the short names are the project lead's to write, because they are the words a buyer repeats to their board.

The project lead, in conversation
TK-8Decide what replaces “a licence to operate”, or that nothing does

Raised twice, independently. The outside review flagged that “licence to operate” can be read as regulatory permission unless something beside it says otherwise; the panel found “powerful agents, clear boundaries” was the only headline every reader understood on sight.

Neither settles it, and nobody misread the live headline. It is also the name of a document inside the vault, so changing it on the homepage alone splits the vocabulary. A ruling, not a change.

The project lead, in conversation
TK-9Correct the £5 on riskmandate.ai

A live defect, found from outside. This store prices the pack at £10 and riskmandate.ai's homepage still carries “1 · £5 The pack, downloaded”. The price moved on a memo from the project lead and the product site was not moved with it.

A buyer who reads both properties — which is the whole point of them being one flow — sees two prices for one thing. It is the other team's file to change, so it goes to them as a correction rather than a suggestion.

The project lead, in conversation

In Progress0

Done0

← every workstream

An operations surface for the people building this store, public because every page here is. It is not a selling page and nothing on it is an offer. The shop is here · every claim, with its state · the reviews