Patterns
Complete work and recover from changes
Differentiate task completion, project completion, and agenda removal so the consequences remain understandable.
On this page
User goal
Differentiate task completion, project completion, and agenda removal so the consequences remain understandable.
Workflow
| Step | Expected behavior |
|---|---|
| 1 | Complete an individual task using its labeled completion button. |
| 2 | When completing a project with unfinished tasks, show the project completion decision. |
| 3 | Let the user complete remaining tasks, leave them incomplete, or cancel the project completion. |
| 4 | When removing a daily agenda block, announce the removal and offer Undo. |
| 5 | Restore the removed entry to its original day when Undo is selected. |
Decision rules
- Task completion is binary work state; project completion is an outcome/lifecycle decision.
- Removing a scheduled block does not delete the project or its task history.
- Undo belongs to the last removed agenda entry and selected date.
- Use an explicit confirmation for consequential lifecycle choices, not a generic success toast.
Edge cases and recovery
- The seven-second Undo period needs accessibility review and should not be assumed sufficient as the only recovery route.
- A past day’s task completion is locked.
- Check the zero-incomplete-task path separately from the decision dialog.
- Parent callbacks own persistence. The isolated dialog specimen never completes real tasks.
Source references
| File | Responsibility |
|---|---|
| app/components/project-detail-content.tsx | Lifecycle orchestration |
| app/components/project-completion-dialog.tsx | Unfinished-task decision |
| app/components/radar-calendar.tsx | Remove/restore entry |
| app/components/agenda-removal-toast.tsx | Recovery feedback |
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