/ memos / 2026-09-16
The homepage sells — and the work has been done before
2026-09-16. 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.
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.
Yeah, and the final thing is once we've done all this, we need to sort of take a hard look at the homepage because the homepage of store, the S-Git, it's all about selling. So a lot of the stuff that is there, you know, part of the S-Git, a lot of the any things, etc. Like, you know, we can move that all to admin sections to kind of other parts. It needs to be really, really focused on selling, right? Big banners, big stuff, big sort of like welcomes buy now, sort of the sort of promotion sort of element to it, end-to-end flows, user testimonies. But for now, put the products like up front, right? Like, you know, have like, you know, articles about it, you know, have like, um, you know, sort of feature sets about, hey, this is happening, that is happening, right? So... It's very important that we, we really clean up that homepage and it should look as professional because also I'm going to have it open on my laptop, right? So my workflow should literally be. And so I actually think the homepage should really be very focused on the persona, right? So if you think about it, yes, I can still access maybe from the top menu, you have a link to the entire catalog and you have a link to the, the, the individual personas or you have a link to the specific bits. But if you imagine like, I want to be laptop open, somebody comes along or, or iPad, Somebody come along and say, hey, who are you? Oh, I'm a founder. Boom. And you want to buy this. Boom. Navigate, you know, uh, click, click, navigate, select the thing, touch, go. That is really what we want to do, right? And um, and basically, um, we, you know, we really need to clean up this workflow, right? And... Again, if there are discount codes to be applied, click a link, apply the discount code, or I give the discount code to them. You know, let's just make it smooth. But the, the homepage needs to really feel like a professional e-commerce. And now we got our four things that we sell. And, and, yeah, just, and the other thing is that as, uh, we've done this all, right? Like every workflow I'm describing, I've done it, right? So I know there's a bit there you says... We haven't done it. I've done it, right? Like, you know, that's why I'm defining it. I've done, you know, if you think about when I create the vaults, For the examples, I've done those policies and I actually work and I've done consulting with other projects. So this is all stuff that I've done before. So let's just remove all the stuff that we have not never done this before. Let's just make it super professional and say, look, I, Dennis, am the ones who are delivering this. You know, I have 20 years of cybersecurity, right? Uh, I've done this sitting in my head, right? So uh, I can deliver all this stuff. And also, actually, one more point we forgot to mention all the other ones. Give some, you know, estimate delivery times and make it make it like a, a delivery, right? So we we expect, for example, the, um, the, the, the, the dual license. In fact, the dual license deliver every day. Expect the, the customized version to be... Um, delivered within, you know, a day, right, or one to two days. Expect the the the the you know the consulting to be done within five you know five days. Question mark depending on their availability, right? So, um, you know, let's let's map that out, right, so that we we can. Um, fundamentally, you know, you know, make these look very, very professional. Yeah, so sorry, just to clarify. So the the 10 quid one is delivered immediately. The new vault is delivered between one and two days. The um, customized vault, uh, customized review is delivered again, let's say two to three days, also one to three days after we received the, the customization. And then the other one is one to five days, right? And you can say depending on inventory, right? Depending on loads, depending on how busy the team is, right? But it would be a lovely problem to have if we have to add stock to this thing. Also, you know, I've been giving lots of voice memos, but um, please catalog them really carefully, map them exactly what I'm saying on them, create the action plan, then execute them all, but do them almost like bit by bit, right? And keep pushing to prod, right? Keep pushing, again, minor versions, right? So don't, you know, this is where you should go V, um, you know, if the next version, right? Um, of the website, just give me a second. but we're really pushing my new version, so this is is on the 0.117. So actually, I think you can you can do a couple of major ones, you know, V2.x and then V3.x. I think some of these changes are a little bit significant, so you can do that, right? But yeah, but keep pushing often and regularly, and just keep going um, until you kind of. I think all these briefings, hopefully you can execute them in sequence.
What we read in it
<b>The correction that changes the most: “I’ve done it.”</b>
“Every workflow I’m describing, I’ve done it… when I create the vaults for the examples, I’ve done those policies, and I’ve done consulting with other projects.” The store has been saying something technically true and practically false. Its claims say the £500 and £1,500 levels have never run for a paying buyer — accurate, and what a reader takes from it is that nobody has ever done this work at all. Those are different sentences and only one of them is true.
What replaces it is stronger than what it removes
The evidence was never missing; it was on a different domain. sgit.ai publishes vault after vault of exactly this work — risk graphs, the regulation graph as a citable object, a conformance layer, a penetration test delivered as a vault, the licence-to-operate model — each with a read key anybody can open right now. “Here are twenty of these, open one” beats both “nobody has done this” and a testimonial.
The distinction to keep, stated once and plainly
The work has been done. This store has not sold it. That second sentence stays, because a first buyer really is the first through this checkout and that is worth them knowing — but it stops being the headline and stops standing in for the first.
A name on the delivery
“Look, I, Dinis, am the one delivering this. I have 20 years of cybersecurity.” Same ask as the reviewer memo, arriving from the selling side rather than the trust side: the two upper levels are somebody’s work and the store has never said whose.
The homepage is a shop front, not an essay
“Big banners, buy now, the products up front.” And everything about sgit, the mechanism and the meta moves to the admin side. The home page today opens by explaining what an Agent Behaviour Policy is; a shop opens with what is for sale.
<b>The real design brief is a physical one</b>
“Laptop open, somebody comes along — who are you? A founder. Boom. And you want to buy this. Boom. Click, click, navigate, select, touch, go.” That is not a web page, it is a counter at an event, operated by a person standing next to the buyer. It sets the whole shape: big targets, few of them, works on a tablet, no dead ends, and a discount code applied by following a link rather than by typing.
Delivery times, given as numbers rather than as a principle
£10 immediately. The vault in one to two days. The customised review in one to three days from receiving the customisation, which is the clock that actually matters. The top level in one to five days, depending on load. And an honest hedge that is also good copy: “it would be a lovely problem to have if we had to add stock.”
And the process is set: catalogue, plan, execute in sequence, push often
“Catalogue them really carefully, map exactly what I’m saying, create the action plan, then execute them all — bit by bit, and keep pushing to prod.” Some changes warrant a major version rather than a minor one.
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>“Remove all the stuff that we have never done this before” — read as a fix, not a delete</b>
Taken literally this deletes the disclosure apparatus, which is the single thing two independent reviewers praised without being asked and the reason a founder persona trusted the site at all. Read as the complaint it is, the problem is not that the site discloses — it is that the disclosure is doing the job of the evidence, because the evidence lives on another domain and was never linked. So: the evidence leads, the disclosure narrows to what is actually undone (a sale through this checkout), and nothing that is true gets removed. If the intent was the literal one, say so and it is one edit.
Which claims are simply wrong now, and which were always right
Every claim has to be re-read one at a time against “the work has been done.” Some are wrong as written. Some are precisely right and were misread. Doing this by search-and-replace would break the ledger, which is the one artefact on this site that must not be edited carelessly.
Twenty years, and what is citable
The claim is the project lead’s to make and the site should carry it in their voice with a source, not assert it in the shop’s voice. Same rule as the reviewer page: nothing goes up that is not traceable to something published.
Testimonials
Named in the memo as something the homepage should have. There are none. The review pages are the closest thing and they are critiques, which is a different object. A placeholder that says it is empty is the house style; an invented one would undo everything else in this memo.
What “depending on inventory” means for a thing with no stock
Good copy and it needs a true referent. The real constraint is one person’s calendar, which is worth saying in those words rather than borrowing a warehouse metaphor that would be the only false sentence on the page.
The work it produced
Live off the board. If a unit below moves, this moves with it.
A counter at an event, not an essay with a buy button. Laptop or tablet turned round: who are you, here is your thing, buy it. Products up front, big targets, few of them, and everything about the mechanism moved to the admin side.
Every level gets an estimated delivery, because a shop that will not say when something arrives is a shop people leave. The numbers were given: immediate, one to two days, one to three days from receiving the customisation, one to five days.
The store says the upper levels have never run for a paying buyer. True, and it reads as “nobody has ever done this”, which is false. The work has been done many times and published; what has not happened is a sale through this checkout. Lead with the first, keep the second, stop letting one stand for the other.
The reviews, the ledger, the console and this board. The part of the store that exists so a decision taken today can be argued with in a month.