/ admin / reviews
Reviews
Every review of this store, newest first. A review is a moment locked — dated, kept, never rewritten, and carrying the screenshots and the version it was taken against. A month from now this is the only record of what the store looked like today.
Five readers walked the new store from the front page to the till. Four of them stopped at the same place.
store.sgit.ai at v0.3.16, the release that made the new design the store: the front page, the picker, the product page, the comparison, the order, the checkout and the page a payment returns to.
Five walks, ten screens each, six findings. The strongest thing the store has is 7.9 screens down a phone. The picker puts 521 pixels of filters in front of fifteen things. And four readers built an order, read a total, and found nothing on the page to do next — which is the true state of the till and not a flaw in the drawing of it, but the page could say so in a way a person can act on.
Four homepages, five readers — and the two who would pay the most chose the one that lost
The live home page and the three concepts drawn for it by a ChatGPT session on 16 September
Twenty reads, five forced rankings, eight findings and four reasons to discount every one of them. The panel agrees with the store's own critique of the same concepts, which is not corroboration, because the same author wrote both.
Five synthetic users walked the store. What that was worth, and what it was not
The synthetic-users vault, and the method inside it
The runs found real defects and two of them were independently corroborated by a human reviewer the same week. They also had a hole in the middle: the agent never chose anything. Seven proposals, one of which cannot be fixed and is marked so.
A partner walked the whole store and wrote it up
store.sgit.ai v0.1.14, the whole buying flow
Sixteen points sorted into keep, friction and recommendation. The reading: six frictions collapse into four levers, and one lever carries half the note — the free diagnostic already exists and sits on the wrong side of the paywall.
How this works
Each review keeps its own stance on every proposal in it — do now, do next, won’t do, or needs a ruling — and carries a verdict control so the reviewer can disagree with the stance and say why. The reasons matter more than the verdicts; the whole point of writing down a won’t do is that somebody gets to argue with it.
Adding one is adding a file. A review is a JSON record in data/reviews/ and a line in the register; the page, its markdown twin, its card here and its place in the sort are generated. The build refuses a register entry with no file and a file with no register entry, because a review nobody can reach is a review that did not happen.
These pages are public and not advertised. They carry reason boxes, pricing deliberation and roadmap, which is not selling copy — so they are noindex, out of sitemap.xml and out of llms-full.txt, and anybody handed the address can read every word. read, not run 15 Sep 2026