Logseq

Structure

• journals/ — daily journal entries (YYYY_MM_DD.md), auto-created by Logseq
• pages/ — knowledge pages, backlog, weekly reports (Logseq page names = filenames)
• assets/ — images and attachments referenced by pages
• logseq/ — Logseq config and backups (do not edit manually)
• automation/ — weekly report and 1-on-1 report automation (shell scripts, amp prompts, launchd plist)
• docs/plans/ — design docs and implementation plans

Commands

• Test: ./automation/test-weekly-report.sh
• Dry-run: ./automation/weekly-report.sh --mode tuesday --dry-run
• Manual run: ./automation/weekly-report.sh --mode tuesday|friday --force
• 1-on-1 report: ./automation/1on1-report.sh [--force] [--dry-run]
• Validate plist: plutil -lint automation/com.lelouvincx.logseq-weekly-report.plist

Any day of the week can be used as --mode. Days map to an underlying report type:

When --mode is explicitly provided, the day-of-week and time-of-day schedule guards are skipped (the duplicate-run stamp file still applies unless --force is used).

RFCs

Design docs and implementation plans live in docs/plans/. Priority order reflects current focus.