This site is built from briefs written elsewhere. Two things go wrong with that arrangement: the same document gets worked twice, and a document arrives and is never worked at all. Both failures are invisible unless somebody keeps a list — so here is the list, with the digest of every file as it was received and an honest status against each one.
Neither of these is hypothetical. One of the documents below arrived twice, byte-identical, six hours apart — and three Lab entries had already been written from it. Without a digest to compare, the only thing standing between that and a wasted afternoon is somebody's memory of a filename.
| Status | What it means | |
|---|---|---|
| Processed | processed | Read in full, and something on this site exists because of it |
| Partly | partly | Read in full; some of it is built and a named part is not |
| Received | received | Archived and read, and nothing has been built from it yet |
| Superseded | superseded | Later material replaced it. Kept, because the reasoning is still the record |
Each one is linked in full, as received, with nothing edited. Where a brief and this site disagree, the brief is what we were given and the site is what we concluded — and where we corrected a brief, the correction is on the page rather than in the file.
sha256 1b2dfa45d228be6b0f6eb6a420090da160e979fe0b347048588565441a9f6e38
This is the one that arrived twice. Byte-identical both times, and the second arrival came in the same message as D3 and D4. It was not reprocessed — the three Lab entries below were already written from the first copy. This entry is the reason the register exists.
material propertysha256 11ff8f5f9eebb9200d30694381ff27c7e53a59417dd92f1a0461bbfe1b65ad89
One correction to this brief is stated on the page it produced, and marked as ours. The brief treats banding as the fix. Worked through, banding is the necessary first move and not the whole answer, because a banded submission still carries roughly the entropy of the fingerprint study the brief benchmarks against. The page shows the assumptions so somebody can check the arithmetic.
sha256 b54eddae92bc88d8133c1e544c339433972ef6cf8cf8656ac4771b7ffbce7ccd
The finding and the prompt are built; the experiment is not. All six load-bearing quotations were fetched and checked against their sources rather than relayed — which produced two corrections to this brief, both stated on the page it became: the partially verified state additionally requires the author to have enabled vigilant mode, and the claim that the attribution renders a profile picture and a profile link could not be found on the page cited.
sha256 af73131b6a72bb5f6d8aad1563f124a016040833310df0fb8be717ec44bb0e56
Both of its rulings are now on the site. The entry product says it reduces accidents and does not stop an attacker, in those words, on the page carrying a price — and the behaviour policy is not sold as a skill, because the portable part of that format cannot carry a constraint. The word for the narrowing cover does not appear on the pricing page at all; the authorise question stands in its place.
sha256 d13e3f08729fa8ffaab7f4e1d247535fb0782c5182df67e365ef61d52ca0cf3d
Third-party material, and it corrected three of our own planning assumptions — the banner is not permitted, submissions go through the exhibitor portal rather than by email, and power has to be requested rather than assumed. Kept on a working page rather than a public one; whether it stays fetchable here at all is an open decision.
These have no digest to check, which makes them the ones most easily lost — a voice memo that changed the direction of the whole site leaves no artefact at all unless somebody writes it down. So they are recorded here in the same list, with the same two columns.
Put the Agent Behaviour Policy at the centre of the site. The ABP is the fundamental primitive; the grant is calculated from reality via digital twins; RiskMandate drives the sale of ABPs, and those are the first batch of customers; the audiences are corporate users, investors and founders; and a security vendor whose controls reduce the delta has a business case we can make for them.
docs/briefs/The Startup Summit exhibitor pack and the event site, for a strategy document and the materials we need to submit.
docs/briefs/Hire a freelancer who also works through agents. Give them a page and a first prompt focused on making sales online and at Lisbon, and make their first task being a power user and tester of behaviour policies.
Preserve the Lab's thinking as it changes, and publish it as files that can be sent through a chat app — because by the time a reader follows a link, the page has moved on.
The whole point of a digest is that somebody else can compute it. If you produce these documents, you do not have to take this page's word for what arrived — hash what you sent and compare.
Every document is recorded by the SHA-256 of the file exactly as we received it. Hash your copy, look for the digest in the register, and anything that is not there did not reach us — or reached us and was not archived, which is our bug and worth telling us about.
# what did we actually receive? curl -s https://riskmandate.ai/briefs-register.json \ | jq -r '.documents[] | "\(.sha256) \(.status) \(.title)"' # is the brief I just sent in there? sha256sum my-brief.md
A register that only lists what was done is a press release.
Every entry above carries what it asked for and did not get, and on most of the nine that column is the longer one. It is kept that way deliberately: the value of this page is that it can embarrass us, and a version that could not would not be worth fetching.
Register maintained by hand alongside the work, and checked in CI: every document listed must exist at the path given and match its recorded digest, and every file in assets/briefs/ must appear in the register. Last reconciled 12 September 2026.
Every item now names something it produced and something it did not. Four of the nine are marked partly, which is the honest state of almost all real work and the status this register expects to use most. The column that matters is the right-hand one.