/ admin / memos
The memo queue
8 memos. Captured word for word, read into a brief, broken into units of work. The state below is read off the board, not typed.
The queue. A memo from the project lead arrives spoken, is kept here verbatim, is read into a brief, and the brief is broken into units of work that appear on the board. This file is the first of those four and the only one written by hand — the brief page and the board cards are generated from it, so a memo cannot be captured and then quietly not acted on.
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.
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.
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.
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.
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.
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.
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.
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.
The four steps
- 1 · Capture
The memo goes in this file verbatim, dated, the moment it arrives. Nothing is trimmed.
- 2 · Read
A brief: what was asked, what it changes, what it contradicts, and what is not yet decidable.
- 3 · Break
Units of work, each one small enough to be finished, each naming the memo it came from.
- 4 · Track
The units go on the board at /admin/work/ and move there. The memo page shows their live state.
Why the memo is kept word for word
A memo is dictated, so it arrives with the repetitions and the self-corrections of speech in it. It is kept exactly as it arrived. The reading of it is written underneath and kept separate, which is the same rule the reviews follow: what somebody said and what we made of it are two different objects, and only one of them is allowed to be wrong.