Patterns
Capture daily notes and actions
Keep observations and newly identified actions with the day that produced them.
On this page
User goal
Keep observations and newly identified actions with the day that produced them.
Workflow
| Step | Expected behavior |
|---|---|
| 1 | Choose the day, then switch from Radar to Notes without changing the selected date. |
| 2 | Write observations as text blocks using the existing editor and normalization helpers. |
| 3 | Use supported task-line behavior when a note becomes an action. |
| 4 | Keep note-derived tasks linked to their Inbox representation. |
| 5 | Review past notes in locked mode rather than rewriting history. |
Decision rules
- Text blocks store markdown; task blocks reference a taskId.
- A notes task is not automatically a project task.
- Date keys and task ownership must remain stable during view switching.
- Maintain an explicit distinction between dirty local content and confirmed save state.
Edge cases and recovery
- Check empty-day notes and long multiline content.
- Loading and offline errors need a visible recovery contract.
- Do not invent task synchronization success from a local capture.
- Rich editable content needs manual keyboard and screen-reader verification.
Source references
| File | Responsibility |
|---|---|
| app/components/running-notes-editor.tsx | Daily editor and API |
| app/components/running-notes-store.ts | Block/task models |
| app/components/radar-workspace.tsx | Shared date context |
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