---
type: schema
schema: daily-note
version: 1
applies_to: Daily/YYYY-MM-DD.md
tags: [meta, schema, daily]
author: alexandria
---

# Schema — daily note

The format for a note in `Daily/`. Daily notes are the **capture layer**: "on my mind" + a plan for the day, staged for the owner's own thinking and then routed into the PEAK pillars by the end-of-day **debrief** (see [[AGENTS#Daily capture & the debrief]]). They are not a permanent home — nothing lives here once the debrief has swept it.

The sections below mirror the debrief prompts so a filled-in day is the raw material the debrief reads.

## Contract

**Filename** — `YYYY-MM-DD.md`, one per day, in `Daily/`.

**Frontmatter** (required unless noted):
| key | value |
|---|---|
| `type` | `daily` |
| `date` | `YYYY-MM-DD` (matches the filename) |
| `tags` | includes `daily` |
| `author` | who wrote it (owner or agent) — optional |

**Required sections** (keep the headings even when empty — they cue the debrief):
- `## On my mind` — freeform capture; whatever the owner is carrying.
- `## Priorities` — the day's few priorities. Each points at a canonical item: `- [ ] <thing> → [[<Area> TODO]]`. Priorities are *pointers*, not the source of truth — the task lives in the area TODO.
- `## Log` — what actually happened as the day runs: who was talked to, what got done, decisions, anything travel/events/personal. This is what the debrief sweeps into People / area TODOs / [[Events]] / [[Knowledge]].
- `## Unresolved` — what's open going into tomorrow.

**Invariants**
- The daily note never *owns* a task, fact, or event — it stages them. After the debrief routes a piece to its pillar home, it need not be duplicated here.
- `date` in frontmatter equals the filename date.

## Reference rendering

```markdown
---
type: daily
date: 2026-07-04
tags: [daily]
---

## On my mind

## Priorities
- [ ]  → [[ TODO]]

## Log

## Unresolved
```
