One queue: the life of an obligation, from inbound to evidence.

An allocator’s DDQ in the inbox. A compliance attestation overdue in a thread. An administrator query. A meeting in ninety minutes with an LP whose file nobody has reread. A factsheet deadline. A commitment made in last week’s meeting that exists only in a notebook.

The firm’s real operating system is the set of surfaces work arrives on, and the task board is downstream of all of them. The expensive failure is rarely that a single item is hard. It is that finding, sorting and holding the items consumes the attention the items themselves deserve. A task list only helps once something has become a task, and at most firms that conversion is manual, partial and permanently in arrears.

A thumbs-up approves. A disposition grammar handles the rest: approve, edit, reject, or hold until Friday. The Principal stops checking five places, because everything that needs them shows up in one list, already researched, and closes with a tap.

Two details keep the queue from becoming another notification stream. The first is Tōryō’s interrupt budget: a closed, static list of what may interrupt a human, and a daily limit on how much attention the system may spend, so urgency is never a per-item judgement call made in the moment. The second is silence. When a sweep finds nothing genuinely actionable, the turn produces no output at all. A system that reports “nothing to report” trains its reader to stop reading, and the quiet is exactly what makes the queue worth opening.

The conversion is aggressive about its inputs. Review comments on a document become items. Administrator queries become items. Attestations become items. Commitments made out loud in an LP meeting become items. Handwritten pages from a notebook are read, transcribed, and the commitments in them land on the board with owners and dates attached.

This is the hinge of the whole system. Every downstream guarantee, the chasing and the evidence and the clean month-end, depends on work existing as items rather than as scattered intentions.

Anything that must be actioned escalates on Tōryō’s ladder: a re-ping in thread, then the alert surface, then a final call, then a hard stop at end of day. Anything still unacknowledged rolls into the next morning’s briefing, marked missed and still open. Delegated work is chased on the same mechanism, and attestation cycles, the classic quarterly chase, run the ladder without a human ever being the nag.

The effect is asymmetric. For the person being chased, ignoring something means it comes back louder tomorrow. For the person who used to do the chasing, an entire category of low-grade interpersonal friction leaves the building. Nothing regulatory slips, because ignoring it is not one of the available outcomes. Silence about the clean days and relentlessness about the ignored ones are halves of the same attention contract, and between them they decide whether a system is still switched on in month six.

The system writes the reply, stages the document, checks the distribution list and tracks the approval, then holds the finished artifact at distribution for a named human, who presses send. Always.

This is the rule that makes agentic work deployable at a regulated firm. The fear that keeps such systems away from investor-facing work is a correct reading of the stakes, so the answer to it has to be structural rather than cultural. The system does every part of the job up to the send button, and it is incapable of pressing it.

“Why did that not get done?” and “who approved this?” are expensive questions to answer retrospectively, and for a regulated firm they are not optional ones. Here they are a query rather than an archaeology project, answerable months later with the context intact, for a regulator, an auditor, or an allocator’s operational due diligence team. Every action that touched a live system carries its own receipt from Daimon, the governed execution boundary, and the whole lifecycle runs inside one operating context held by Tōryō.

The record also closes the loop on the boundary. The firm does not merely assert that nothing goes out unapproved. It can show the approvals.

The table below sizes ten tasks a fund runs end to end against the manual version. The hours are indicative, sized from the shape of the work rather than from a stopwatch. Where a claim has to be evidenced, Shuin produces a measured count over a stated window.

Recurring tasks alone, before any per-event work, return six or more days a month. The strongest single line is the first: a full institutional DDQ, two and a half days across two or three people, becomes two hours spent reviewing a draft and its flagged gaps.

A position’s thesis is written once, in a memo, and the memo is never opened again, so positions end up held for reasons that quietly stopped being true. That cost does not show up in hours.

Treat thesis invalidation as a monitored condition and it joins the same lifecycle as everything else. Every memo states what would make it wrong; those conditions become monitored items, silent while they hold and raised when they trip, with the original memo language quoted next to what actually changed, on an escalation path that makes not-looking unavailable.

That is the honest summary of the system. It runs the firm’s existing obligations faster, and it also runs the ones the firm never had the capacity to staff, keeping the evidence that they ran.