/ The console
The console
Everything here is public, because every page on this site is — no login, no account, nothing gated. What is different is that it is not advertised: noindex, out of the sitemap, out of llms-full.txt. Anybody handed the address reads every word.
In flight — 35 units of work
Read off the board. A unit is here because it is next in its workstream or being worked on now; it is not here because somebody added it to a list twice.
Take money at all
Take money at all
Take money at all
Take money at all
Take money at all
The entry price, and what it buys
Who runs the review
Who runs the review
Close the loop after payment
Keep the record
Keep the record
Keep the record
Qualify who is reading
The version the board can read
The version the board can read
The version the board can read
Decouple the views
Decouple the views
Never leave the site · blocked on The RiskMandate team publishing a manifest as JSON — item 1 of the brief.
Who owns what · blocked on The RiskMandate team's answer.
The comparison table
Product pages that show the product · blocked on PP-2.
What has actually been done · blocked on WD-2.
The homepage sells
The homepage sells · blocked on DT-1.
The homepage sells
Describe your agent
Take the moves from the concepts
Take the moves from the concepts
Take the moves from the concepts
Take the moves from the concepts
Take the moves from the concepts
Take the moves from the concepts
Take the moves from the concepts
Take the moves from the concepts
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.
For a person walking the whole flow from /admin/try/. A hundred per cent, so the order places and lands on the page that says what happens next without anybody paying for a walkthrough.
https://store.sgit.ai/?code=BETA7LOOP
For an agent driving the flow from the script on /admin/try/. Separate from the human's code so an order record says which of the two produced it.
https://store.sgit.ai/?code=SYNTH4DELTA
For showing the flow to somebody on a laptop or a phone, at a stand or across a table, without the demonstration wallet being the first thing they see.
https://store.sgit.ai/?code=DEMO3STAND
Published on the two level pages it applies to. It takes the whole price off the pack and the vault — and it cannot touch the two levels that are somebody's time, because what it gives away has to be a thing that costs nobody a day.
https://store.sgit.ai/?code=DOORSOPEN
4 more codes exist and are not on this page. They ship as a SHA-256 and never as a string, so they are not in the built site, not in the markdown twins and not in this console — a check reads every byte of the output against every code on every release. Read them out of data/discounts.yml, which is in the repository and not in the site.
Opening one of these lands on the shop with the discount already applied and the four prices repainted, and the code is taken out of the address before the page settles — so it is not in history, not in a bookmark and not in a referrer. Any page here takes ?code=, not just the front one.
Next: taking money
Both rails → — no payment rail is live, which is the single fact that most shapes this store. part exists 17 Sep 2026
| 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. |