/ memos / 2026-09-16
Describe your agent — the page that gets used in the room
2026-09-16. 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 memo, word for word
Voice memo, transcribed. Nothing trimmed, reordered or paraphrased. The reading of it below is ours and is kept separate on purpose.
Okay, so one of the I think pages that I think is missing is kind of a UI similar to some of the games we created, which is almost like describe your agent as. I think it's kind of like describe your agent, and then this is almost the 50 quid one that I can walk them through, which is the the page. In fact, this is the page that you should get once you. No, this is the 500 quid one. Sorry. So this is in addition to a prompt that we can give with the 500 quid one. There should also be a page which again you can access without paying, which is fundamentally one where I think we need to explore multiple UIs here. But fundamentally, where you choose either by clicking, by drag and dropping, by you know, basically selecting, or even maybe having multiple options of building up your agent, and and this is sort of like where somebody can say, okay, so my agent can access the database. Can connect to the internet. Connect partially to the internet. Can connect to a file system. Can generate emails. You know. Can access again Gmail, Dropbox, etc. So it's almost like imagine UI where you have in the centre the agent, and then around it you have all these assets that you can just click or drag and drop into it, and basically we can create a whole series of of questions, which again you can choose to answer them in sequence, or you can just drag and drop them all in one go. So let's experiment the UI, and basically what we're doing is we are creating that definition of what the agent could do, which, which I can then give to, for example, a cloud session or a ChatGPT session that has access to the template vault, and then just creates a vault for the user. So in a way, I could even have a workflow where I can walk people through it, you know, and then they go for a walk, and then you know later on I'll email them the vault. So that's a really cool workflow to have, and fundamentally I'll sell them and create that 500 quid vault, and then it's whether that is worth that money. So I just need that page and that experience, and so let's experiment with multiple UIs, and the best way to do this.
What we read in it
<b>This is the demonstration, and it is being given away on purpose</b>
“A page which again you can access without paying.” It produces the grant — everything the agent can actually do — which is one of the four objects inside the document this store sells. Giving the elicitation away and charging for the correction is a different business from charging for the whole thing, and it is the one the project lead just described.
It is for £500, and the memo corrects itself mid-sentence
“This is almost the fifty quid one… no, this is the five hundred quid one, sorry.” Worth keeping, because the correction is the substance: at £50 you get a vault of a template, and at £500 somebody corrects the mandate against your situation. This page is how a situation gets described in the first place.
The shape is a canvas, not a form
“The agent in the centre, and around it all these assets that you can just click or drag and drop into it.” And crucially, two ways through the same model: a sequence of questions for somebody working alone, or drag everything at once for somebody being walked through it by a person. That second mode is the one that matters here.
<b>The real deliverable is a prompt input, not a picture</b>
“We are creating that definition of what the agent could do, which I can then give to a Claude session or a ChatGPT session that has access to the template vault, and then just creates a vault for the user.” So the output is a structured document a model can act on. The canvas is the interface; the document is the product.
And the workflow it enables is the actual ask
“I could walk people through it, they go for a walk, and later on I email them the vault.” That is a £500 sale conducted as a conversation, with the work done after they leave — which is exactly what the delivery estimate of one to three days from your reply was written for.
It answers a proposal this store already recorded and did not act on
The partner review found that MAP-A-GRANT already exists, is already free, ships in every public template zip, and was only ever surfaced after a £500 purchase — and that moving it to the front door is a re-ordering rather than a build. This is that re-ordering, with an interface on it.
“Let’s experiment with multiple UIs”
Asked for twice in one memo, which is the same instruction the lab already runs on: five prototypes of one configurator, each with a column saying what is wrong with it, because five options presented with only their strengths is a menu rather than an experiment.
What this does not decide
Written down rather than guessed at. A memo is a direction; these are the places it stops, and every one of them is somebody’s call rather than a gap in the transcript.
<b>The capability vocabulary is not this store’s to invent</b>
The memo lists examples — a database, the internet, the internet partially, a file system, sending email, Gmail, Dropbox. The real vocabulary is the pinned one inside the template packs, and this store holds only the counts from riskmandate.ai, not the terms. Inventing a palette would put words in a buyer’s mouth that the document they receive does not use, which is the worst possible outcome for a page whose entire job is producing an input to that document.
“Connect partially to the internet” is the interesting one and it is not binary
Most of the listed capabilities are on or off; that one is a band. Whether the palette carries degrees, and how many, changes the whole interaction — and the barrier taxonomy this store already publishes says only one of four kinds of restraint is actually a control.
Where the output goes
It is handed to a model session with the template vault. That session is not this site and never will be: nothing here opens a connection to sell anything, there is no account, and the document has to leave as a file the reader holds. The clipboard and a download are the only two routes that do not require this site to become something it is not.
Which UI wins, and who decides
Multiple prototypes is the ask; picking one is not the builder’s call and the lab already has the convention for it — each prototype carries what is wrong with it, and which becomes real is written down as undecided until somebody decides.
The work it produced
Live off the board. If a unit below moves, this moves with it.
A free page where somebody builds their agent by clicking or dragging capabilities onto it, and what comes out is a definition of what that agent could do — a document a model session can turn into a vault. It is the elicitation half of the £500 level, given away, and the project lead expects it to be the page they use most in conversation.