Journal Template

Objective

Create a reusable template (or templates) for Chronicles journal entries to standardize structure across daily reflections and topic-spanning logs.

Context

Chronicles/Journal currently has 12+ entries with no consistent structure:

  • Daily date-only: 2025-05-05.md, 2025-07-14.md, 2025-07-15.md (some use a “5 minute journal” format)
  • Daily date + topic: 2025-11-22 NYC Boys TODO.md, 2026-04-25 Vault Restructure Day.md (rich reflective format: “What I set out to do / What I actually did / Decisions worth remembering / What was striking / What I got wrong / Top 3 tomorrow / Related”)
  • Topic + date: Physio 2025-01-20.md
  • Topic-only multi-date: Thailand Trip Journal.md (created 2026-05-02)
  • Random: note 2026-04-04 17-30-00.md

templates has templates for ADR, devices, notes, people, projects, and quick-capture, but none for journals. Adding one (or two) closes the gap and makes future entries consistent.

Approach

  1. Survey the existing entries to identify the 2-3 distinct journal modes in use (likely: daily reflection, topic-spanning log, single-event log).
  2. Decide whether one flexible template covers all modes or whether multiple are needed.
  3. Draft the template(s) under x/templates/, mirroring the conventions of the existing templates (frontmatter style, section headers, comment placeholders).
  4. Update README / vault rulebook if needed to reference the new template(s).
  5. Optionally backfill an ADR documenting the decision.

Next Actions

  • Pick journal modes to support (daily vs topic vs single-event)
  • Draft x/templates/journal-template.md (or split into multiple)
  • Add Templater dynamic frontmatter (date, tags) following the people-template.md pattern
  • Update README if it documents available templates
  • Optionally write an ADR for the decision

Resources

Notes