sgit newsroom v0.1.29 · snapshot 2026-09-24

Reading room · store.sgit.ai

On this page

Reading room / store.sgit.ai · raw text · live ↗

From store.sgit.ai, the page as fetched on 2026-09-25 · open the live page ↗Everything on this sheet is the source site's own text; the newsroom's chrome is outside it.

title: The console description: "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." lead: "" order: 90 robots: "noindex,follow" console: true blurb: "<b>Everything here is public</b>, because every page on this site is — no login, no account, nothing gated. What is different is that it is not <em>advertised</em>: noindex, out of the sitemap, out of <code>llms-full.txt</code>. Anybody handed the address reads every word."


{{console-dash}}

The queue, and how work gets here

The memo queue →↗ — a memo from the project lead arrives spoken, is kept here word for word, is read into a brief, and the brief is broken into units of work. The reading is kept separate from the memo on purpose: what somebody said and what we made of it are two different objects, and only one of them is allowed to be wrong.

The board →↗ — those units, in four columns, grouped into workstreams. A workstream never moves by hand; it moves because a task inside it moved, so the summary cannot contradict the detail.

Hand somebody a code

A code is a link, not something to type. Open one on the laptop you are holding, or send it, and the shop comes up with the discount already on it and the four prices repainted.

{{code-links}}

Next: taking money

Both rails →↗ — no payment rail is live, which is the single fact that most shapes this store. {{claim:checkout-links-not-issued}}

Stripe↗The rail that turns a buyer into a customer, including a buyer who pays nothing. Six products, eight prices, three coupons — and a webhook that has to listen to the session rather than the payment, because a hundred-per-cent order creates no charge at all.
SumUp — parked↗Taken off the store on 16 September for the first end-to-end MVP. The plan is kept rather than deleted, so turning it back on is restoring a record instead of rediscovering an argument.

Run it yourself

The walkthrough →↗ — a beta tester or an agent goes from the catalogue to the page after payment in about four minutes, for nothing, with a discount code printed on the page. Screenshots of every step, and a script an agent can follow without a person in the loop.

The same thing as PDFs, for sharing or for reading away from a screen — by hand ↗ (11 pages, every screenshot) and as an agent ↗ (7 pages, the assertions). Both are snapshots; the page is the source of truth.

The record

Reviews, dated and kept↗Every review of this store, newest first. A review is a moment locked: the version it was taken against, the screenshots, and a stance on every proposal in it.
What happened to each memo↗The join: every memo from the project lead, the units of work it became, the page each one built and the release it shipped in.
The homepage concepts, reviewed↗Three homepage directions drawn for this store from outside, screenshotted and measured against the live page — what is taken, what is refused, and the live pricing contradiction the review found.
The design brief↗What a design session needs to mock up the rest of this store without access to the repository: the constraints with the hard rules named, the real tokens read from the stylesheet, eighteen components and nine screens. The markdown twin is the pasteable form.
The claim ledger↗Every factual claim this site makes, with the state it earned and the date. Pages cite a claim and the chip links back here.
What we do not say, and why↗The words this site will not use, the sentence it will not print, and the naming collision that is still open.
The dev packs↗The working documents behind the store, and the manifest of which of them are held back and why.
Release history↗Every release, what changed, and the commit it is.
The purchase lab↗The tool that turns a described deployment into a depth band. Nothing on it can be bought.
What is not for sale yet↗The offers that exist as specifications and have not been built.

This document is released under the Creative Commons Attribution 4.0 International licence (CC BY 4.0).