The board
The queue of work on riskmandate.ai as a board: open, in flight, waiting on a ruling, done — read off the state file, the task briefs and the work files. Source: https://riskmandate.ai/admin/work/↗ · noindex · written by scripts/site/build-admin.mjs
Open12
#2 · T01 · a dayOne page per behaviour: behaviour-<id>.html, generated from the catalogue↗#3 · T02 · a daydata/edges.json per vault: the grant as edges, one per path, barrier on the path↗#4 · T03 · half a day + a Lab 03 askMetrics on behaviours (speed, volume, blast) as coarse ordinals in a vocabulary extension↗#5 · T03 · a dayOutward links per behaviour: ATT&CK technique ids, GDPR articles, cited↗#6 · T04 · several daysViews per audience + prompts + projections, regenerated by the build, refused when stale↗#7 · T05 · a day per vaultSettle the 18 open questions across the five connector vaults↗#8 · T06 · half a day eachThe next five connector vaults↗#9 · T06 · after 8The three business-function vaults↗#10 · T07 · two hoursLab 03: add the asks from the n8n review and the graph brief (barrier per path; a word for a broad-but-real gate; metrics and links on the primitives)↗#11 · T10 · a day, after the workflow agent runs the promptThe two Voice Debrief use-case vaults, and a use-case group on the library↗#12 · T09 · half a dayStop deploying the vault: inputs in the repository, the product in the vault↗#16 · T11 · doneDone v1.24.0 — the consequence layer for oc433z3m: assets, consequences, routes out, two scenarios; the research list documented from Google's pages; the standards mini-graphs↗
In flight0
nothing here
Waiting on a ruling4
#11a · the leadBoth pushes done 16 Sept (oc433z3m public, xjir6m0c private). Still owed: the twelve screens as redacted image files in evidence/; the correction call (§4 of the workflow brief)waiting on the lead
#13 · smallA page for the £500 workflow once the store has a return address; a per-shape header on MAP-A-GRANT.mdwaiting on the store agent
#14 · the store'sPoint the four payment links' success address at paid-t<n>.html (level 1: paid-t1.html?shape=<slug>&order=<ref>); the level-3 text on the store's product page; the opinion add-on page (brief D9)waiting on the store agent
#15 · two and a half daysDone v1.24.0 — the MVP vault: LICENCE.md + licence block in the build; the v3 reading app with the left navigation, Who are you?, Your keys, Keep it, Download; a new app vault; oc433z3m re-pushed; the vault page repositioned (direction__mvp-vault-and-the-reading-app.md)the lead's four decisions answered 16 Sept; renderer v5 in a new app vault vbhmlulo; oc433z3m re-pushed; the dual licence in the build
Done1
#1 · smallBy behaviour facet on the library
done v1.16.0
The four columns are read off the status column of the queue in the state file↗: done is done; waiting on the lead is needs the lead; any other waiting is waiting outside; a row whose brief a work file names is in flight; the rest are open and claimable. Nothing is dragged, so the board cannot say something the file does not.
Waiting on a ruling — 11, counting the decisions the lead owns
Both pushes done 16 Sept (oc433z3m public, xjir6m0c private). Still owed: the twelve screens as redacted image files in evidence/; the correction call (§4 of the workflow brief)
waiting on the leadneeds the lead
A page for the £500 workflow once the store has a return address; a per-shape header on MAP-A-GRANT.md
waiting on the store agentwaiting outside
Point the four payment links' success address at paid-t<n>.html (level 1: paid-t1.html?shape=<slug>&order=<ref>); the level-3 text on the store's product page; the opinion add-on page (brief D9)
waiting on the store agentwaiting outside
Done v1.24.0 — the MVP vault: LICENCE.md + licence block in the build; the v3 reading app with the left navigation, Who are you?, Your keys, Keep it, Download; a new app vault; oc433z3m re-pushed; the vault page repositioned (direction__mvp-vault-and-the-reading-app.md)
the lead's four decisions answered 16 Sept; renderer v5 in a new app vault vbhmlulo; oc433z3m re-pushed; the dual licence in the buildneeds the lead
Behaviour or behavior on the mark (the site is British; the recommendation is behaviour).
a decision the lead owns, listed in the state fileneeds the lead
The Licence to Operate referent (organisation / instrument / licensee) is adopted on the site
a decision the lead owns, listed in the state fileneeds the lead
Publish the n8n write-up and its author, or not.
a decision the lead owns, listed in the state fileneeds the lead
Extend the measuring environment's gateway rule to MCP-tunnelled requests (the deployer's).
a decision the lead owns, listed in the state fileneeds the lead
The return address for the level-3 files (a mailbox today; a write-only vault link when it exists).
a decision the lead owns, listed in the state fileneeds the lead
Who the reviewing person is at level 3, and whether the Voice Debrief vaults publish the routing service's providers by name.
a decision the lead owns, listed in the state fileneeds the lead
Which agent branches merge next, and in what order (see .claude/work/).
a decision the lead owns, listed in the state fileneeds the lead
In flight — 0 branches
One file per branch under .claude/work/. How a work file is written↗.
Nothing in flight.
Task briefs — 14
Each is a unit of work sized for one branch, with the files it touches named so two agents can see whether they would collide. How a task brief is written and claimed↗.
| Brief | Task | Touches | Size | State |
|---|
| T01↗ | one page per behaviour, generated | scripts/site/build-abp-pages.mjs, scripts/site/abp/, site/behaviour-*.html (new), site/pages.json | a day | open |
| T02↗ | the grant as edges, one per path | scripts/site/build-abp-vault.mjs, site/vaults/*/data/edges.json (new, derived), the renderer | a day | open |
| T03↗ | metrics and outward links on the 23 | site/vaults/_template/data/vocabulary/ extension, the behaviour pages, Lab 03 | a day and a half | open |
| T04↗ | audiences as views; prompts and projections in the vault | the generator, site/vaults/*/data/views/, prompts/, projections/, the renderer | several days | open |
| T05↗ | settle the 18 open questions | site/vaults/<slug>/data/grant.json, one slug at a time | a day per vault | open |
| T06↗ | the next five connectors, then the three business functions | site/vaults/<new-slug>/, site/vaults/index.json | half a day each | open |
| T07↗ | the request list against the model site, brought up to date | site/lab-abp-requests.html, an edition | two hours | open |
| T08↗ | bring docs/how-the-website-works.md to the current site | docs/how-the-website-works.md | half a day | open |
| T09↗ | inputs in the repository, the product in the vault; drop the snapshot fallback | the two build scripts, abp-vaults.js, site/vaults/, tests, CI | half a day | open |
| T10↗ | the two Voice Debrief use-case vaults, and a use-case group on the library | site/vaults/voice-debrief-*/, index.json, the library page | a day | open |
| T11↗ | the consequence layer: assets, consequences, routes out, open consequences on the delta; first for oc433z3m | site/vaults/claude-gmail-connector/data/{assets,consequences}.json (new), build-abp-vault.mjs, the renderer, _template/data/ | a day | open |
| T12↗ | GDPR, EU AI Act and ATT&CK as nodes inside the vault, titles only, for consequences and behaviours to link to | _template/data/standards/ (new), build-abp-vault.mjs, the renderer, Lab 03 | a day, with T03 | open |