/ admin / status
What happened to each memo
48 done · 63 open · 19 waiting on you. A memo, what it became, and where every piece of it landed.
Every memo, what it became, and where each piece of it landed. This page is a join rather than a list — the queue says what arrived, the board says what it became and the release history says what shipped, and until this page existed the only way to answer “what happened to that memo” was to read three pages and hold the join in your head.
A workstream can belong to two memos, and where it does its units appear under both — which is right for reading one memo and wrong for adding up. The four numbers below count every unit once.
Stripe end to end, with their SKUs — and a customer even at 100% off
2026-09-16 · Voice memo, transcribed. Run the real Stripe purchase flow rather than an amount-only link, so a buyer handed a hundred-per-cent code still becomes a customer with an email. Then leak codes on specific journeys. And start capturing the work as units on a board.
What it built: /admin/ /admin/memos/ /admin/rails/ /admin/rails/stripe/ /admin/rails/sumup/ /admin/status/ /admin/try/ /admin/work/ /d/t1/ /d/t2/ /paid/t1/ /paid/t2/ /paid/t3/ /paid/t4/
Released in: v0.1.11 · v0.1.18 · v0.2.2 · v0.2.4 · v0.2.6 · v0.3.0 · v0.3.1 · v0.3.6
| Unit of work | State | Where it landed | Release | |
|---|---|---|---|---|
TM-1 | Create the products in Stripeyours | done | /admin/rails/stripe/ | v0.2.2 |
TM-2 | Set customer creation to always, and prove it on a £0 orderyours | next | — | — |
TM-3 | Create the promotion codes over the three couponsyours | next | — | — |
TM-4 | Enable promotion codes on every link, prefill where a code was leaked | queued | — | — |
TM-5 | Bring the return address onto this site | done | /paid/t1/ /paid/t2/ /paid/t3/ /paid/t4/ | v0.3.0 |
TM-6 | Stand up the checkout.session.completed webhookBlocked on Runs off this site. This site is static and opens no connection. | queued | — | — |
TM-7 | Take one real £10 payment and read the receiptBlocked on TM-1 and TM-6. | queued | — | — |
TM-8 | Retire the browser-side discount arithmeticBlocked on TM-3. | queued | — | — |
TM-9 | SumUp — parked for the MVP | done | /admin/rails/sumup/ | v0.2.6 |
TM-10 | Write the two rails up as plans rather than intentions | done | /admin/rails/ /admin/rails/stripe/ /admin/rails/sumup/ | v0.1.18 |
TM-11 | Get the codes into Price.lookup_key, not just the descriptionyours | next | — | — |
TM-12 | Re-export the product CSV whenever the dashboard changesyours | next | — | — |
TM-13 | Decide what a DELIVERY-only purchase meansyours | next | — | — |
TM-14 | Caps on the hundred-per-cent coupon — ruled not neededyours | done | /admin/rails/stripe/ | v0.2.4 |
TM-15 | Bring SumUp back once Stripe has taken moneyBlocked on TM-7 — a first real payment. | queued | — | — |
LC-1 | Decide which journeys carry a codeyours | done | /d/t1/ /d/t2/ | v0.3.1 |
LC-2 | Print the code on the journey, with the link carrying it applied | done | /d/t1/ /d/t2/ | v0.3.1 |
LC-3 | Give every leaked code a cap and an expiry before it is printed | done | /admin/rails/stripe/ | v0.2.4 |
LC-4 | Keep the codes out of the built site except where they are meant to be | done | /admin/try/ | v0.1.11 |
TR-1 | Give the admin surface its own console UI | done | /admin/ | v0.1.18 |
TR-2 | Build this board | done | /admin/work/ | v0.1.18 |
TR-3 | Link the admin console from the main site's top-level nav | done | /admin/ | v0.1.18 |
TR-6 | Build the memo queue | done | /admin/memos/ | v0.1.18 |
TR-4 | Operationalise the review proposals | in progress | — | — |
TR-5 | Capture the next reviewBlocked on TM-7. | queued | — | — |
TR-7 | Execute the memos in sequence, pushing often | in progress | — | — |
TR-8 | Join the memos to what they became | done | /admin/status/ | v0.3.6 |
£10, a commercial licence, and a name on the review
2026-09-16 · Voice memo, transcribed — arrived twice, as a raw transcript and a cleaned one. The cleaned copy is below; the two differ only in punctuation and disfluency, and nothing in the substance moved.. The entry level goes to £10 and gains a commercial licence over the CC BY version anybody can download. And the two upper levels get a named reviewer, starting with the project lead, on a surface built for several.
What it built: /d/t1/ /ledger/ /offers/ /who/ /who/dinis-cruz/
| Unit of work | State | Where it landed | Release | |
|---|---|---|---|---|
PL-1 | Move the entry level from £5 to £10yours | done | /d/t1/ /offers/ /ledger/ | v0.2.0 |
PL-2 | Dual-licence the pack: CC BY public, commercial to the buyeryours | done | /d/t1/ /offers/ /ledger/ | v0.2.0 |
PL-3 | Research the cleanest way to grant it | next | — | — |
PL-4 | Put the licence text where the buyer reads it before payingBlocked on PL-2. | queued | — | — |
PL-5 | Record the price arc as one claim, not threeBlocked on PL-1. | queued | — | — |
WD-1 | Build the reviewer register and a page per reviewer | done | /who/ | v0.2.9 |
WD-2 | Write the first reviewer's page | done | /who/dinis-cruz/ | v0.2.9 |
WD-3 | Let the buyer choose their reviewer at £500 and £1,500Blocked on WD-4 — a second name. | queued | — | — |
WD-4 | Recruit the restyours | next | — | — |
WD-5 | Say what happens when the chosen reviewer cannot take the workBlocked on WD-3. | queued | — | — |
Five audiences, decoupled views, and the version the board can read
2026-09-16 · Voice memo, transcribed. The store does not qualify who is reading it. Five audiences, each with its own view and path and its own subset of the offers; the views driven by JSON and built as components rather than written out; and every vault — free ones included — carrying a version its reader’s board can read.
What it built: /admin/ /admin/memos/ /admin/status/ /admin/work/ /are/ /are/exec/ /are/founder/ /are/governance/ /are/investor/ /are/security/
Released in: v0.1.18 · v0.2.7 · v0.3.6
| Unit of work | State | Where it landed | Release | |
|---|---|---|---|---|
QB-1 | Decide what happens to the three buyer groupsyours | next | — | — |
QB-2 | Write the five audiences down as data | done | /are/ | v0.2.7 |
QB-3 | Hidden, or shown differently — answeredyours | done | /are/investor/ | v0.2.7 |
QB-4 | Build the five paths | done | /are/founder/ /are/investor/ /are/exec/ /are/security/ /are/governance/ | v0.2.7 |
QB-5 | Run a synthetic pass over the five pathsBlocked on QB-4. | queued | — | — |
BR-1 | Specify what a board-readable cut actually isyours | next | — | — |
BR-2 | Decide who writes it, per vaultyours | next | — | — |
BR-3 | Say on the site what is inside a vault | next | — | — |
BR-4 | Put it in the free vaults firstBlocked on BR-1, BR-2. | queued | — | — |
BR-5 | Re-read the entry level once it carries oneBlocked on BR-4, PL-2. | queued | — | — |
DV-1 | Read the two guidance sites properly and write down what applies | in progress | — | — |
DV-2 | Settle: custom elements at runtime, or generated partials at build?yours | next | — | — |
DV-3 | Lift the view layer out of build.py into declared blocksBlocked on DV-2. | queued | — | — |
DV-4 | One JSON file per view, and a check that fails on an unused oneBlocked on DV-3. | queued | — | — |
DV-5 | Prove it by adding the sixth audience as a fileBlocked on DV-4, QB-4. | queued | — | — |
TR-1 | Give the admin surface its own console UI | done | /admin/ | v0.1.18 |
TR-2 | Build this board | done | /admin/work/ | v0.1.18 |
TR-3 | Link the admin console from the main site's top-level nav | done | /admin/ | v0.1.18 |
TR-6 | Build the memo queue | done | /admin/memos/ | v0.1.18 |
TR-4 | Operationalise the review proposals | in progress | — | — |
TR-5 | Capture the next reviewBlocked on TM-7. | queued | — | — |
TR-7 | Execute the memos in sequence, pushing often | in progress | — | — |
TR-8 | Join the memos to what they became | done | /admin/status/ | v0.3.6 |
Never leave the site — and write down who owns what
2026-09-16 · Voice memo, transcribed. The whole purchase, and everything after it, happens on store.sgit.ai. The store owns e-commerce; riskmandate.ai owns the products and the policies; the two read each other's files over CORS rather than sending each other's visitors away. Do the store first, then brief the other side.
What it built: /boundary/ /boundary/#debt-marked-as-debt /boundary/#the-brief-addressed-to-the-riskmandate-team /paid/t1/ /paid/t2/ /paid/t3/ /paid/t4/
Released in: v0.3.0 · v0.3.2 · v0.3.3
| Unit of work | State | Where it landed | Release | |
|---|---|---|---|---|
OS-1 | Narrow the no-network rule before the first cross-origin read | done | /paid/t2/ | v0.3.3 |
OS-2 | Move the post-sale page onto this site | done | /paid/t1/ /paid/t2/ /paid/t3/ /paid/t4/ | v0.3.0 |
OS-3 | Embed the bought vault on the page they land on | done | /paid/t2/ /paid/t3/ /paid/t4/ | v0.3.3 |
OS-4 | Read riskmandate.ai's manifest over CORS and close the last hopBlocked on The RiskMandate team publishing a manifest as JSON — item 1 of the brief. | next | — | — |
OS-5 | Make the store feel like a shopBlocked on More information from the project lead.yours | queued | — | — |
OS-6 | Re-run the synthetic buyer who got confusedBlocked on OS-2, OS-3. | queued | — | — |
WO-1 | Publish the ownership boundary as a page both agents can read | done | /boundary/ | v0.3.2 |
WO-2 | Brief the RiskMandate team to do the reverse | done | /boundary/#the-brief-addressed-to-the-riskmandate-team | v0.3.2 |
WO-3 | Mark the files that are on the wrong side | done | /boundary/#debt-marked-as-debt | v0.3.2 |
WO-4 | Agree the contract for the shared filesBlocked on The RiskMandate team's answer. | next | — | — |
One table, five columns, and the free one first
2026-09-16 · Voice memo, transcribed. The comparison table every pricing page has and this store does not: features down the left, five columns across — free, £10, £50, £500, £1,500 — and a cell for every one. New page, so it can be reviewed before it is wired in.
What it built: /compare/
Released in: v0.2.8
| Unit of work | State | Where it landed | Release | |
|---|---|---|---|---|
CT-1 | Decide what every cell is allowed to sayyours | done | /compare/ | v0.2.8 |
CT-2 | Write the feature list as data | done | /compare/ | v0.2.8 |
CT-3 | Settle whether £10 includes a vaultyours | done | /compare/ | v0.2.8 |
CT-4 | Decide what support means, and who answersyours | next | — | — |
CT-5 | Build the page, free column first | done | /compare/ | v0.2.8 |
CT-6 | Render it as a PDFBlocked on CT-5. | queued | — | — |
Make a product page feel like a product page
2026-09-16 · Voice memo, transcribed. Description, price and buy button, a carousel of screenshots of what you actually get, specs and SKUs, and a place for reviews. Built as prototypes first, then wired in — and eventually switchable by audience, the way a product has editions.
What it built: /lab/product/ /lab/product/#reviews
Released in: v0.3.4
| Unit of work | State | Where it landed | Release | |
|---|---|---|---|---|
PP-1 | Prototype one product page in the lab | done | /lab/product/ | v0.3.4 |
PP-2 | Find out which screenshots exist and which have to be taken | done | /lab/product/ | v0.3.4 |
PP-3 | Put a version on every piece of product mediaBlocked on PP-2. | next | — | — |
PP-4 | Print the specs and the SKUsBlocked on TM-1. | queued | — | — |
PP-5 | Add the review section, and say it is emptyBlocked on PP-1. | done | /lab/product/#reviews | v0.3.4 |
PP-6 | Make the page switchable by audience | done | /lab/product/ | v0.3.4 |
The homepage sells — and the work has been done before
2026-09-16 · Voice memo, transcribed. A shop front built for a laptop turned round at an event: who are you, here is your thing, buy it. Delivery times on every level. And the correction that matters most — this work has been done many times; what has not happened is a sale through this store, and the site has been conflating the two.
What it built: / /admin/ /admin/memos/ /admin/status/ /admin/work/ /are/ /d/t1/ /d/t2/ /d/t3/ /d/t4/ /ledger/ /paying/
Released in: v0.1.18 · v0.2.0 · v0.2.1 · v0.2.4 · v0.2.7 · v0.3.6
| Unit of work | State | Where it landed | Release | |
|---|---|---|---|---|
SF-1 | Move the mechanism and the meta off the front page | next | — | — |
SF-2 | Put the four products up front, with prices and deliveryBlocked on DT-1. | next | — | — |
SF-3 | Build the who-are-you entry | done | / /are/ | v0.2.7 |
SF-4 | Make a discount code a link, never a thing to type | next | — | — |
SF-5 | Add the sections a shop front hasBlocked on SF-1, WH-5. | queued | — | — |
SF-6 | Test it the way it will be usedBlocked on SF-3. | queued | — | — |
SF-7 | Rename level four to match the product | done | /d/t4/ | v0.2.4 |
DT-1 | Put a delivery estimate on every level | done | /d/t1/ /d/t2/ /d/t3/ /d/t4/ | v0.2.0 |
DT-2 | Replace the it-has-never-run non-answer about timing | done | /paying/ /ledger/ | v0.2.0 |
DT-3 | Say what the constraint really is | done | /d/t4/ | v0.2.0 |
DT-4 | Start measuring the moment there is something to measureBlocked on TM-7. | queued | — | — |
WH-1 | Re-read every claim against “the work has been done” | done | /ledger/ | v0.2.1 |
WH-2 | Link the published evidence | done | / | v0.2.1 |
WH-3 | Narrow the disclosure to what is genuinely undone | done | / /d/t3/ /d/t4/ | v0.2.1 |
WH-4 | Put a name and a track record on the deliveryBlocked on WD-2. | next | — | — |
WH-5 | Decide what to do about testimonialsyours | queued | — | — |
TR-1 | Give the admin surface its own console UI | done | /admin/ | v0.1.18 |
TR-2 | Build this board | done | /admin/work/ | v0.1.18 |
TR-3 | Link the admin console from the main site's top-level nav | done | /admin/ | v0.1.18 |
TR-6 | Build the memo queue | done | /admin/memos/ | v0.1.18 |
TR-4 | Operationalise the review proposals | in progress | — | — |
TR-5 | Capture the next reviewBlocked on TM-7. | queued | — | — |
TR-7 | Execute the memos in sequence, pushing often | in progress | — | — |
TR-8 | Join the memos to what they became | done | /admin/status/ | v0.3.6 |
Describe your agent — the page that gets used in the room
2026-09-16 · Voice memo, transcribed. A free page where somebody builds their agent by clicking or dragging capabilities onto it, and what comes out is the definition of what that agent could do. It is the front half of the £500 level, given away, and it is the page the project lead expects to use most in conversation.
What it built: /lab/agent-canvas/ /lab/agent-canvas/#the-vocabulary /lab/agent-canvas/#what-this-produces /lab/agent-sequence/
Released in: v0.3.5
| Unit of work | State | Where it landed | Release | |
|---|---|---|---|---|
DA-1 | Get the real capability vocabulary | done | /lab/agent-canvas/#the-vocabulary | v0.3.5 |
DA-2 | Prototype the canvas — agent in the centre, capabilities around it | done | /lab/agent-canvas/ | v0.3.5 |
DA-3 | Prototype the sequence — one question at a time | done | /lab/agent-sequence/ | v0.3.5 |
DA-4 | Decide whether a capability has degreesyours | next | — | — |
DA-5 | Emit the definition as a document a model can act on | done | /lab/agent-canvas/ | v0.3.5 |
DA-6 | Write the prompt that turns the definition into a vaultBlocked on DA-8, and a decision on which of the two interfaces is real. | queued | — | — |
DA-7 | Say on the page what it is and is not | done | /lab/agent-canvas/#what-this-produces | v0.3.5 |
DA-8 | Put it in front of the £500 level and in the walk-through flowBlocked on DA-5. | queued | — | — |
Close the loop after payment
Not from a memo. The store hands a buyer to riskmandate.ai and promises a person within 24 hours. Nothing carries the sale to that person, and nobody owns the mailbox it would arrive in.
| Unit of work | State | Where it landed | Release | |
|---|---|---|---|---|
CL-1 | Name the owner of the follow-up mailboxyours | next | — | — |
CL-2 | Route the level-3 brief back to a personBlocked on CL-1. | queued | — | — |
CL-3 | Verify the handover contract against a real landingBlocked on TM-5, TM-7. | queued | — | — |
Take the moves from the concepts
Not from a memo. 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.
| Unit of work | State | Where it landed | Release | |
|---|---|---|---|---|
TK-1 | Ship the four-fact strip, every fact linked to its claim | next | — | — |
TK-2 | Set the price at 42px on every card | next | — | — |
TK-3 | Rebuild the card anatomy: level and delivery on one line, one action | queued | — | — |
TK-4 | Applications as chips, with a sixth that converts the miss | queued | — | — |
TK-5 | Forty-eight header links down to fourBlocked on TK-6, which changes the same fold | queued | — | — |
TK-6 | Cut the disclosure strip to one line without moving it | queued | — | — |
TK-7 | A short name and a precise subtitle, in the same cardyours | next | — | — |
TK-8 | Decide what replaces “a licence to operate”, or that nothing doesyours | next | — | — |
TK-9 | Correct the £5 on riskmandate.aiyours | next | — | — |
TK-10 | Show one real reader the same four foldsyours | queued | — | — |
How this page is built
Every row is generated. A memo names its workstreams, a workstream holds its units, and a unit that is done carries the pages it produced and the release it went out in. A unit that claims to be done and points at nothing fails the release — because "done" with nothing to open is the one status that can be wrong without anybody noticing.
The memos themselves are kept word for word at the queue, with the reading of each one held separately from the memo. The board at /admin/work/ is the same units arranged by workstream rather than by where they came from.