Every engagement this login holds, as a docket. Open a client and their whole file becomes the console — queue, workbench, evidence, engagement, register — scoped to them. Counts and coverage are computed from item state, never typed. Unassigned clients render locked: assignment is the engagement object, and unassigned means invisible.
The one queue — every item in a signable state across every engagement this login holds, grouped by urgency and computed from item state × engagement scope, never hand-listed. A CPA serving a lender who also owns STRs wants one queue; clients are the spine, this is today's lens over the same items. Opening an item lands on that client's docket.
Append-only: who acted on what, when, in which lane, on which evidence, with which memo. This register is the professional's own defense file — it records diligence; it is not marketed or offered as a liability shield. It spans clients; filter by docket below.
| When | By · lane | Client | Item | Action | Basis memo |
|---|
Interpretive-lane regulatory deltas land here with the source document linked; the professional's ratification is what lets a guidance change touch client-facing law files. Indexed and regime items never appear — those route to the operator's lanes (D19 §5).
Latest watch run: DELTA_REPORT 2026-07-03 — its open items are regime-lane (rescheduling docket clocks) and assumption-lane (NPV defaults), which route to the operator, not to this desk. When Treasury or IRS guidance changes an interpretation an engine relies on, it lands here as a proposed-delta for lane ratification before any law file moves.
The aide drafts basis memos and summarizes evidence for the professional — and, exactly as on the client side, it never signs, never books, never files.