monthlylisted

# Tracework Monthly Write a phase-level judgment: what state changed this month, which outcomes or decisions matter, which risks repeated, and what next month should close. Raw entries are the semantic source. Daily and Weekly are editorial context and coverage, not stronger evidence. ## Required References Read: - `references/reporting-narrative-contract.md` - `references/daily-note-format.md` - `references/worklog-summary-template.md` - `references/project-tagging-guide.md` when Daily project labels are ambiguous - `references/tracework-storage-convention.md` for storage details ## Inputs and Outputs Resolve `{vault}` from project then global `.tracework/config.yaml`. Inputs: - `{vault}/raw/weeks/` entries matching the target month: semantic source. - `{vault}/Daily Note.md`: daily judgments, date index, and legacy coverage. - Matching `{vault}/Work Diary/Weekly/*.md`: optional prior prioritization hints. Outputs: - Monthly archive: `{vault}/Work Diary/Monthly/{YYYY-MM}.md` - Signals: `{vault}/raw/months/{YYYY-MM}/signals.json` - Skeleton: `{vault}/raw/months/{YYYY-MM}/skeleton.json` - Review: `{vault}/Work Diary/Monthly/{YYYY-MM}.summary.md` ## Workflow ### 1. Resolve Month and Scope - Parse explicit `all` or an exact registered reporting-group name such as `work` or `personal`. - Otherwise use `profile.default_reporting_group`; when absent, default a workplace-facing review to `work`. - Partition projects before ranking. Apply the audience-safety rules in