dailylisted

# Tracework Daily Write a concise daily management-closure view. Answer what changed today, why it matters, what is now closed or bounded, and the next gate. Do not produce a module inventory or agent handoff. ## Required References Read both before writing: - `references/reporting-narrative-contract.md`: scope partition, closure types, headline selection, evidence rules, and audience safety. - `references/daily-note-writing.md`: source handling, merge rules, vault file shape, and conversation / first-run shapes. ## Configuration Resolve configuration in this order: 1. Project `.tracework/config.yaml` 2. `~/.tracework/config.yaml` The primary output defaults to `{vault}/Daily Note.md`, overridable through `daily_note.path`. The shared reader selects projects; `daily_note.repos` restricts Daily only. If no vault can be resolved, return the report in the conversation. Do not create an unrequested vault. Do not block on cold-start. Optionally add one soft upgrade line at the end (see First-Run and Local Fallback). ## First-Run and Local Fallback Daily must produce value without prior setup. Cold-start is an upgrade for durable multi-day storage and strict audience partition, not a ticket to try. ### Scope resolution Use the shared contract's `read-report --report daily` command with the target dates; add `--scope` only for explicit user choice. Use the returned scope and projects. An assigned current-project group is a normal exact-group scope; `scope_source=imp