Components
Daily running notes
Keep notes and note-derived tasks attached to the selected day, with history locking.
On this page
Purpose and usage
Keep notes and note-derived tasks attached to the selected day, with history locking.
Use for daily observations and captured actions, not a replacement for the project’s structured milestone list.
Anatomy
| Part | Contract |
|---|---|
| Text block | Markdown content line. |
| Task block | References a note inbox task. |
| Save status | Local saved/dirty state tracks editing. |
| Daily context | date and locked determine the editing boundary. |
Variants and configuration
| Configuration | Behavior |
|---|---|
| Text | {id, type: text, markdown}. |
| Task | {id, type: task, taskId}. |
| locked | Past notes are reviewable without mutation. |
State coverage
| State | Implemented behavior |
|---|---|
| Loading | Requests /api/planning/notes for the date. |
| Editing | Local blocks update. |
| Task line | Connected to an inbox task record. |
| History | Read-only context. |
Interaction and responsive behavior
- Use the existing normalization helpers when composing text and task lines.
- Keep the selected date stable across Radar/Notes view changes.
- A note task and a project task have different ownership boundaries.
Accessibility contract
- Editable text needs a comprehensible keyboard path and accessible name.
- Task actions should expose their state and title.
- Test multiline editing, focus position, and announcements with assistive technology.
Known gaps and readiness
Local fixtures provide real text blocks. Save, sync, offline recovery and full rich-editing accessibility remain separate verification tasks.
Composition example
<RunningNotesEditor date={selectedDate}
locked={locked} scrollToEndRequest={notesRequest} />Source references
| File | Responsibility |
|---|---|
| app/components/running-notes-editor.tsx | Text/task editing and daily API |
| app/components/running-notes-store.ts | Typed text/task blocks and storage helpers |
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