Files
tolaria/demo-vault-v2/task-24q1-01.md
Test b3126044e8 refactor: flatten vault structure — simplify migration API and flatten demo vault
- Simplify flatten_vault API to return usize instead of MigrationResult struct
- Add KEEP_FOLDERS: attachments/ and _themes/ alongside type/, config/, theme/
- Use HashSet for collision tracking in unique_filename
- Update wikilinks from path-based [[folder/slug]] to title-based [[slug]]
- Clean up empty directories after flattening
- Flatten demo-vault-v2: move all notes from type-based subfolders to root
- Update smoke tests for flat vault structure
- Remove migrate_to_flat_vault from repair_vault (one-time migration only)

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
2026-03-15 23:40:47 +01:00

1.7 KiB

aliases, Is A, Belongs to, Status, Owner
aliases Is A Belongs to Status Owner
Write Q24Q1 retrospective
Task 24q1 Done person-luca-rossi

Write Q24Q1 retrospective

The Q1 2024 retrospective is the first formalized quarterly review for the newsletter business. This document captures what went well, what missed, and key learnings from the quarter across all tracked dimensions: measure-subscribers, measure-sponsorship-mrr, measure-books-per-month, and measure-resting-hr. The retro is published internally (in this vault) and a condensed version is shared with person-paco-furiani and person-sara-ricci for alignment.

Writing the retro also involves pulling data from analytics dashboards, reviewing the quarter's content performance, and identifying patterns that should inform 24q2 planning. This is the first time the process is being done formally, so part of the task is establishing a repeatable template that can be used in future quarters.

Acceptance criteria

  • Pull final metrics for all four tracked measures and record actual values
  • Write narrative summary for each goal area (subscribers, revenue, books, health)
  • Identify top 3 learnings and top 3 action items for Q2
  • Share condensed summary with person-paco-furiani and person-sara-ricci
  • Commit the retro document to the vault and link it to 24q1

Notes

  • Established the retro template that has been used every quarter since. The format of "metrics / narrative / learnings / actions" works well.
  • The biggest learning from Q1 was that subscriber targets need to account for content style changes (the technical pivot caused unexpected churn).
  • Linked to procedure-quarterly-retro as the canonical process for future quarters.