Dojo is a layered operating system for delivery. Use it as a flow, not as one big dashboard: intake enters through Inbox, gets cleaned in Sync Review, turns into reporting in Daily Status and Sprint Reports, and communication obligations live in Follow-ups.
Use project cards for a top-level read on health, next actions, risks, reporting hygiene, thread pressure, and Jira pressure. If the hygiene panel looks noisy, the project likely needs review work before the reporting output is trustworthy.
Open Projects ↗Use this when you need to inspect canonical work directly. Tasks remain the truth layer for execution, ownership, due dates, and completion.
Open All Tasks ↗Internal operational reporting. This view only shows approved items by default. If something appears to be missing, check Sync Review first.
Windowed reporting by project. Use Ops Mgr mode for temperature, problems, and upcoming milestones without too much task detail.
Raw intake from imports, Slack, and future connectors. Items disappear from the default Inbox view once they are handled through review, approval, merge, link, or discard.
Open Inbox ↗The editorial control layer. Review items, compare likely matches, reconcile with current work, approve what should publish, and discard what should not survive. Pending Inbox signals can surface here too when they still need editorial handling.
Open Sync Review ↗The communication obligations queue, especially for Slack threads. Track reply drafts, waiting states, overdue obligations, and Jira handoffs.
Open Follow-ups ↗The observability layer. Use it for webhook health, sync events, Slack setup, Jira bridge contracts, sample payloads, and test flows.
Open Diagnostics ↗Daily Status and Sprint Reports use approved content by default. Imported items can exist in Dojo without appearing in reporting yet, and that is expected while they are still in draft or need review.
When imported work overlaps with existing tasks or reporting items, use compare, merge, link, or keep separate. The main review states are now Needs decision, Distinct, and Reconciled. Exact duplicates can auto-merge when the copy and project pattern clearly match.
Status items exist so unfinished work can roll from one internal call to the next. Resolve, hide, or link them instead of letting old wording accumulate forever.
If an Inbox card remains visible, it usually still needs action. Handled items should fall out of the default view after review, approval, merge, link, or discard.
Start in Diagnostics. It shows source events, payload examples, callback contracts, and a test checklist for Slack and Jira round trips.
Use Diagnostics for Slack intake payloads, Jira callback contracts, curl examples, sync events, and setup validation.
Open Diagnostics ↗Use Daily Status, Sprint Reports, Inbox, and Sync Review together when you need to trace how raw intake becomes approved reporting.
Open Reporting Views ↗Use Insights, Pulse, Scan, and Biz Dev as the live operating pages instead of looking for separate repo documentation.
Use Settings for theme selection, data review, import/export, integrations, and Dojo build tracking.
Open Settings ↗Dojo’s main working layers are projects, tasks, status items, team updates, inbox items, sync events, and thread follow-ups. This page now summarizes the operational model directly in-app.
The repo remains the implementation source of truth, but the live app docs now point you to the actual pages you can use inside Dojo instead of private markdown files.
Check whether it is still in Sync Review, still unapproved, or filtered out by the current output mode.
Make sure the related review item was actually handled. Approval, merge, link, and discard should all clear the corresponding Inbox signal from the default view.
Use Follow-ups. That view exists precisely so thread obligations do not get buried inside Inbox or project notes.
Open Diagnostics and inspect the latest sync events, Slack setup panel, Jira callback contract, or sample curl requests.