Patterns
Capture and triage the Inbox
Capture a thought quickly, then complete it or assign it to the right project without losing its meaning.
On this page
User goal
Capture a thought quickly, then complete it or assign it to the right project without losing its meaning.
Workflow
| Step | Expected behavior |
|---|---|
| 1 | Capture a short actionable title in the Inbox. |
| 2 | Review active items separately from completed ones. |
| 3 | For a project-related item, open its Move action and choose the appropriate active project. |
| 4 | Complete a standalone action through its named completion control. |
| 5 | Expand completed work when restoring or reviewing an item. |
| 6 | Keep the user in the current context while the action’s result is announced. |
Decision rules
- Inbox is an ownership state, not a project color or urgency.
- Moving should preserve the task title and meaningful supporting detail.
- A completed item remains reviewable; it is not silently deleted.
- Expose the target project by name instead of relying on its icon or fill.
Edge cases and recovery
- No valid move targets should not leave an unusable empty menu.
- Long task titles must wrap while keeping completion/move controls available.
- The current UI calls planning actions and refreshes the router; error recovery is not uniformly specified.
- Local fixture rows do not prove an item moved or persisted.
Source references
| File | Responsibility |
|---|---|
| app/components/inbox-workspace.tsx | Capture, completed group and actions |
| app/components/inbox-task-move-menu.tsx | Project move target |
| app/components/task-checkbox.tsx | Completion control |
Examples from the app
Actual Radarist components with fictional data. Captured at 2× resolution or higher. Select an image to inspect it full size.
Related topics
Source audit: 2026-10-07 · Revision 0103e2549959 · Documentation v0.1