One place. Every canonical document. Its current state. Exactly what belongs to you. When your name is on a document — it's in your queue. When you confirm — it's done. No Slack thread, no guesswork, no "did you see it?"
Click "Who are you?" in the top-right header. Select your name. The app remembers you across sessions — you won't need to do this again.
Once set, your badge count appears immediately. Every pending item assigned to you surfaces in the Change Feed, the Queue, and the Tasks tab.
Hit My Queue at any time to jump straight to your pending list — filtered, sorted, nothing else.
The bar below the tabs gives you the current state of the entire document registry at a glance.
These are document-level counts — not person counts. One document can be pending for three people and still shows as 1 pending.
Not every document goes to everyone. Recipients are determined by document type and source — automatically.
If a GitHub document returns a 404 for you — it wasn't designated for you, or there's an access gap to resolve with DJ.
Every document change that has been logged appears here. Cards are colour-coded by status and sortable by multiple filters simultaneously.
The Slack button on every card sends an immediate re-notification for that specific document to #dsa-document-notifications. Use it when someone hasn't confirmed and needs a nudge — without writing a message.
Click any card to open the full detail view — who confirmed, who's still pending, progress bar, source, and escalation options.
The Queue is for one thing: confirming you've read a document. It is intentionally fast and lightweight — no effort, no context required beyond reading.
The Queue groups pending items by person. Use the person tabs across the top to scope it.
You can also use the ✓ Confirm button in the top header — it opens a full modal, lets you select yourself, and walks through your entire queue in one sitting.
Confirmations are not agreement — they are acknowledgement. You've read it. You know the current state.
Every registered document, grouped by type. The health dot tells you the current state at a glance.
Groups are collapsible — click the header to expand or collapse a type. ⭐ Important documents are pinned to a dedicated section at the top.
Use the Search bar to filter by title across all groups. Use ↻ All to manually trigger a snapshot refresh on every document.
If you are a Feeder (DJ, Smoke, Michelle), the 📍 pin button appears on each card — use it to flag a document as Important and trigger an immediate team alert.
Hit + Log Change in the top header whenever a canonical document has been updated and the team needs to know.
On submit: DSA snapshots the document, creates a pending confirmation for each recipient, posts to #dsa-document-notifications, and DMs every recipient directly.
Rule: Only log real document changes. DSA is a state record — not a chat tool.
Who can pin: DJ, Smoke, and Michelle — the Feeder roles.
Pinning a document flags it as requiring immediate attention. It does three things at once:
#dsa-document-notificationsTo pin: use the 📍 button in the Registry, the Browse Docs card, or the detail modal. The same button unpins. Pinning overrides the recipient routing — all active team members are notified regardless of document type.
When a document goes overdue — deadline passed with outstanding confirmations — an → FCL-001 button appears on the card.
Escalation logs the event in the audit trail and flags the document for the Feedback Cascade Loop. It does not automatically notify anyone — it is a record of the failure to confirm, surfaced in the next FCL review cycle.
Overdue items are also visible in the stats bar. The FCL team (Smoke, DJ, Michelle) reviews escalated items as part of the weekly operating rhythm.
Confirmations are acknowledgement — seconds to complete. Tasks are work — they take time, effort, and coordination. They live in separate tabs for a reason.
The Tasks tab has three columns:
Hit + New Task (Tasks tab) or + Task (header) to create. Set the title, assign it, pick an area, optionally link it to a document and set a due date.
When creating a task, you can set it as Blocked by another open task. This wires a dependency chain.
On your task card, you will see:
The All Active Tasks column shows compact dependency chips so SA/DL can see bottlenecks across the whole team at a glance.
Tasks require two confirmations — not one. Both parties must close the loop.
If the creator disagrees, they don't accept — the task stays open for discussion. DSA records the state but does not resolve the disagreement.
Completed and cancelled tasks drop off all active views automatically. The audit log retains the full history.
A clean grid view of every registered document, organized by category. Use this when you want to explore rather than act on a queue.
Visible to Smoke and DJ only (Admin role). Manage who has access to DSA-001 without a code deploy.
Team membership is now DB-driven. When someone joins or leaves, this is the only place you need to change.