Dojo Use Guide

Projects

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.

All Tasks

Use this when you need to inspect canonical work directly. Tasks remain the truth layer for execution, ownership, due dates, and completion.

Daily Status

Internal operational reporting. This view only shows approved items by default. If something appears to be missing, check Sync Review first.

Sprint Reports

Windowed reporting by project. Use Ops Mgr mode for temperature, problems, and upcoming milestones without too much task detail.

Inbox

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.

Default rule: keep meaningful items as different thing, use same thing only for clearly identical work, and ignore noise.

Likely same should stay small and conservative. If a signal lacks a strong anchor in tasks, carry-forward items, or prior structured updates, treat it as new by default.

Save draft only cleans the signal. Save + Different Thing cleans it and resolves it as distinct work in one step.

Sync Review

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.

Use Triage as the default lane. Go deeper into reconciliation only when the overlap is genuinely strong.

Follow-ups

The communication obligations queue, especially for Slack threads. Track reply drafts, waiting states, overdue obligations, and Jira handoffs.

Diagnostics

The observability layer. Use it for webhook health, sync events, Slack setup, Jira bridge contracts, sample payloads, and test flows.

Approval Matters

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.

Reconciliation

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.

In inbox-first lanes, the practical moves are review, different thing, same thing, and ignore. The heavier compare/merge/link actions belong to stronger overlap cases.

Carry-forward

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.

Inbox Behavior

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.

Slack Intake

• Slack message or thread triggers Make.
• Claude analyzes the context against current Dojo state.
• Dojo receives normalized Inbox items and optional thread follow-ups.

Follow-up Actions

• Copy a reply draft.
• Mark waiting on team.
• Mark replied.
• Resolve when the loop is closed.

Jira Bridge

• Slack-derived issues can carry a Jira proposal.
• Make creates or updates the issue in Jira.
• Jira calls back into Dojo so the follow-up stores key, status, and assignee.

Where To Debug

Start in Diagnostics. It shows source events, payload examples, callback contracts, and a test checklist for Slack and Jira round trips.

Something Is Missing From Reporting

Check whether it is still in Sync Review, still unapproved, or filtered out by the current output mode.

Inbox Feels Stuck

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.

Slack Thread Needs Attention

Use Follow-ups. That view exists precisely so thread obligations do not get buried inside Inbox or project notes.

Automation Looks Broken

Open Diagnostics and inspect the latest sync events, Slack setup panel, Jira callback contract, or sample curl requests.

1. Import A Fresh File

• Run one real meeting import.
• Confirm Sync Status shows the new import and hash.
• If Dojo is still persisting changes, it should visibly say saving.
• Check the latest inbox routing summary so you can see how much landed as reviewable, likely distinct, triage, or task-anchored.

2. Check Intake Quality

• Inbox should not show obvious duplicate raw signals.
• Structured updates already represented in project data should not bounce back as fresh active Inbox work.
• Signals already anchored by task work from the same import should feel explained, not ambiguous.
• Noise should still be easy to spot and discard.

3. Check Review Lanes

• Triage should stay fast and focused.
• Likely distinct should hold valid new work with no strong anchor.
• Likely same should stay small and believable.
• Resolved should show outcomes without mixing them back into active review.

4. Resolve A Small Sample

• Use different thing for valid new work.
• Use same thing only when the overlap is genuinely strong.
• Use ignore aggressively for noise.
• Use Save draft only when you want to clean the signal without resolving it yet.
• Use Save + Different Thing when the item is clearly valid and new.

5. Watch Save Behavior

• The card should show saving... then saved ✓.
• Buttons should stay blocked while the write is still in flight.
• Handled items should not reappear after polling or refresh.

6. Verify Output

• Approved items should appear in Daily Status or Sprint Reports when expected.
• Ignored or discarded items should stop cluttering active review.
• If the loop still feels muddy, do not merge yet.

Dojo V2

Once the current triage and reconciliation flow is trustworthy again, the next step is to move Dojo toward a real product application architecture instead of growing the monolithic dashboard forever.

The current recommended direction is Next.js + TypeScript + shadcn/ui, with the current Netlify-backed operational model preserved while the product surfaces migrate gradually.

Migration Principle

Do not rewrite reactively. Stabilize the current tool first, then migrate by domain: Projects, Tasks, Inbox, Sync Review, Follow-ups, and Reporting.