Making the decision was the easy part
Governance rarely fails at the decision. It fails afterwards, in the six action items that went into six different systems, each visible only to whoever remembers to open it. This is one list of everything you owe.
One list, five systems of record
Committee action items, board actions, safety corrective actions, bias remediation and lineage work items all land in one inbox, sorted by what is actually late.
It never becomes the second copy
Only work created here can be closed here. Everything else links back to the module that owns it, because marking a copy done tells somebody they are finished while the real record still says open.
It finds work filed under your other names
One subsystem owns an item by user id, another by email, another by a bare string. Your identity is resolved once against the user record and matched every way that record implies.
It reads five systems and owns none of them
Copying work into a task tool creates two records that drift, and the one the auditor reads is never the one you updated. These rows stay owned by the module that raised them, and the inbox links you there.
Committees
Action items raised in a committee meeting, with their assignee and due date.
Board portal
Board action items, owned by email and dated to a deadline.
Health & Safety
Corrective actions raised from a hazard, triage or an incident follow-up.
Bias audits
Remediation actions from a bias audit, which carry no deadline and are shown as undated.
Governance lineage
Work items from the lineage workbench, where evidence is still missing.
What is actually in it
Four things, each of which exists because the obvious version of it was wrong in a way that hides work.
The inbox itself
The first question is never what exists. It is what is late, what is mine, and what I can ignore this week.
- Overdue, undated and open counts across every source, not per module
- Filter to one source, or read the whole obligation set at once
- Every mirrored row carries a link straight to the screen that owns it
- Undated work is shown as undated rather than given an invented deadline
- A source whose table is not present is named as unavailable, so a short list is never mistaken for a clear one
Turn a line in a document into an obligation
A sentence in a note cannot be owned, dated or completed. It is prose, and prose cannot be late.
- Promote a line in a note, a shape on a canvas, or a cell in a sheet into a real task
- The document is left exactly as it was, and the task links back to the element it came from
- Re-promoting the same element updates the task instead of creating a duplicate
- Assign to a colleague by email and the platform resolves them to the right person
- Refuses to promote anything a subsystem already owns, so no obligation exists twice
Compliance programs, instantiated whole
A regulatory cycle is a set of obligations with an order, owners and a closing condition. Creating them one at a time is how a step goes missing.
- NYC Local Law 144 annual bias audit, dated backwards from the audit's expiry
- GDPR data protection impact assessment, from processing record to automated-decision review
- EU AI Act high-risk readiness, covering risk management, data governance, transparency, human oversight and accuracy
- Every item cites a requirement in the framework registry, and the regulation's own wording is quoted from there rather than paraphrased
- Each item states what closes it, taken from the requirement's own evidence types
- Instantiating a program a second time updates the same set rather than duplicating it
Identity, resolved carefully
Five subsystems collected the same person's address from five different humans. Matching naively means half your work is invisible.
- Resolves the caller once against the user record, then matches on user id, directory id and email together
- Email comparison is case-insensitive everywhere, so one subsystem's capitalisation cannot hide an item
- Never matches on display name or username, because neither is unique and a false match shows one person another person's obligations
- When an identity cannot be fully resolved, the inbox says so rather than presenting a partial list as complete
Three programs, each checked against the regulation it cites
Not a catalogue of a thousand shallow templates. Three, because each item points at a requirement in the framework registry and that checking does not scale by wishing. The title describes the work, which is ours to word. The obligation is quoted from the registry, which is not.
NYC Local Law 144
Annual bias audit for an automated employment decision tool: run the audit, compute selection and impact ratios, publish, notify candidates.
GDPR DPIA
From the record of processing through the principles assessment to the automated-decision review.
EU AI Act high risk
Risk management, data governance, transparency, human oversight and accuracy, as a dated readiness set.
A citation that does not resolve against the registry fails the build, so a stale or invented reference cannot reach you. An item with no genuine deadline is created unscheduled rather than given one.
Work starts where the thinking happened
The commitment is usually made in a document, not in a task tool. Promote it there and it keeps its context.
Canvas
Promote a sticky or a shape into an owned, dated task.
Notes
A line in a meeting note becomes an obligation with a deadline.
Sheets
A cell becomes a task, linked back to the workbook it came from.
Agents
Reachable over MCP, under the same permissions as everything else.
An honest list is worth more than a tidy one
A task inbox that quietly drops what it could not read is worse than no inbox, because it looks finished. Every gap here is declared: a source that cannot be reached is named, work with no deadline is marked undated, and an identity that could not be fully resolved is flagged on the list rather than hidden behind it.