From f223d4f654b6da397b3502b9e0d47807c1dd7c2a Mon Sep 17 00:00:00 2001 From: lucaronin Date: Sun, 19 Apr 2026 22:26:35 +0200 Subject: [PATCH] refactor: curate demo-vault-v2 fixture --- .gitignore | 1 + demo-vault-v2/.fixture-manifest.json | 55 ++ demo-vault-v2/.gitignore | 17 +- demo-vault-v2/.laputa/settings.json | 3 - demo-vault-v2/2024-01.md | 29 - demo-vault-v2/2024-02.md | 29 - demo-vault-v2/2024-03.md | 29 - demo-vault-v2/2024-04.md | 30 - demo-vault-v2/2024-05.md | 30 - demo-vault-v2/2024-06.md | 32 - demo-vault-v2/2024-07.md | 29 - demo-vault-v2/2024-08.md | 29 - demo-vault-v2/2024-09.md | 29 - demo-vault-v2/2024-10.md | 28 - demo-vault-v2/2024-11.md | 31 - demo-vault-v2/2024-12.md | 32 - .../2024-complete-two-gran-fondos.md | 32 - demo-vault-v2/2024-double-revenue.md | 34 - demo-vault-v2/2024-launch-podcast.md | 34 - demo-vault-v2/2024-reach-50k-subscribers.md | 34 - demo-vault-v2/2024-read-24-books.md | 33 - demo-vault-v2/2024.md | 49 -- demo-vault-v2/2025-01.md | 29 - demo-vault-v2/2025-02.md | 29 - demo-vault-v2/2025-03.md | 30 - demo-vault-v2/2025-04.md | 31 - demo-vault-v2/2025-05.md | 30 - demo-vault-v2/2025-06.md | 32 - demo-vault-v2/2025-07.md | 31 - demo-vault-v2/2025-08.md | 31 - demo-vault-v2/2025-09.md | 31 - demo-vault-v2/2025-10.md | 31 - demo-vault-v2/2025-11.md | 32 - demo-vault-v2/2025-12.md | 34 - demo-vault-v2/2025-reach-22k-mrr.md | 33 - demo-vault-v2/2025-reach-85k-subscribers.md | 33 - demo-vault-v2/2025-read-20-books.md | 33 - demo-vault-v2/2025-ride-stelvio.md | 34 - demo-vault-v2/2025-ship-laputa.md | 34 - demo-vault-v2/2025.md | 51 -- .../24q1-launch-sponsorship-packages.md | 36 -- demo-vault-v2/24q1-plan-cycling-season.md | 36 -- demo-vault-v2/24q1-podcast-season-1.md | 36 -- .../24q1-redesign-newsletter-template.md | 36 -- demo-vault-v2/24q1-set-investing-framework.md | 36 -- demo-vault-v2/24q1.md | 31 - demo-vault-v2/24q2-10-pillar-articles.md | 36 -- .../24q2-build-podcast-landing-page.md | 36 -- demo-vault-v2/24q2-hire-editor.md | 36 -- demo-vault-v2/24q2-sponsor-crm.md | 36 -- demo-vault-v2/24q2-spring-gran-fondo.md | 37 -- demo-vault-v2/24q2-stock-screener.md | 35 - demo-vault-v2/24q2-video-format-test.md | 36 -- demo-vault-v2/24q2.md | 32 - demo-vault-v2/24q3-codemotion-talk.md | 36 -- demo-vault-v2/24q3-morning-journaling.md | 36 -- demo-vault-v2/24q3-new-sponsor-verticals.md | 37 -- demo-vault-v2/24q3-podcast-season-2.md | 37 -- demo-vault-v2/24q3-premium-tier.md | 37 -- demo-vault-v2/24q3-summer-reading-sprint.md | 37 -- demo-vault-v2/24q3.md | 32 - demo-vault-v2/24q4-annual-review-process.md | 36 -- demo-vault-v2/24q4-black-friday-campaign.md | 37 -- demo-vault-v2/24q4-cycling-year-review.md | 38 -- demo-vault-v2/24q4-laputa-start.md | 42 +- demo-vault-v2/24q4-linkedin-crossposting.md | 37 -- demo-vault-v2/24q4-sponsor-dashboard.md | 37 -- demo-vault-v2/24q4.md | 36 +- demo-vault-v2/25q1-laputa-v1.md | 42 +- demo-vault-v2/25q1-newsletter-seo-sprint.md | 37 -- demo-vault-v2/25q1-paid-newsletter-trial.md | 36 -- demo-vault-v2/25q1-rate-increase.md | 37 -- demo-vault-v2/25q1-referral-program.md | 38 -- demo-vault-v2/25q1-strength-program.md | 38 -- demo-vault-v2/25q1.md | 35 +- demo-vault-v2/25q2-dolomites-trip.md | 38 -- demo-vault-v2/25q2-laputa-v2.md | 45 +- demo-vault-v2/25q2-podcast-season-3.md | 38 -- demo-vault-v2/25q2-reach-70k.md | 38 -- demo-vault-v2/25q2-team-retreat.md | 37 -- demo-vault-v2/25q2.md | 35 +- demo-vault-v2/25q3-community-launch.md | 38 -- demo-vault-v2/25q3-discord-community-soft.md | 38 -- demo-vault-v2/25q3-ebook.md | 38 -- demo-vault-v2/25q3-leaddev-london.md | 38 -- demo-vault-v2/25q3-peak-training.md | 38 -- demo-vault-v2/25q3-podcast-season-4.md | 38 -- demo-vault-v2/25q3.md | 34 - demo-vault-v2/25q4-2026-sponsors.md | 37 -- demo-vault-v2/25q4-financial-review.md | 38 -- demo-vault-v2/25q4-laputa-v3.md | 38 -- demo-vault-v2/25q4-reach-85k.md | 38 -- demo-vault-v2/25q4-year-review-2025.md | 38 -- demo-vault-v2/25q4.md | 31 - demo-vault-v2/_themes/dark.json | 33 - demo-vault-v2/_themes/default.json | 33 - demo-vault-v2/_themes/minimal.json | 33 - demo-vault-v2/_themes/untitled-2.json | 33 - demo-vault-v2/_themes/untitled-3.json | 33 - demo-vault-v2/_themes/untitled-4.json | 33 - demo-vault-v2/_themes/untitled.json | 33 - demo-vault-v2/ai-wont-replace-thinking.md | 26 - demo-vault-v2/area-building.md | 31 +- demo-vault-v2/area-finance.md | 29 - demo-vault-v2/area-health.md | 29 - demo-vault-v2/area-learning.md | 30 - demo-vault-v2/area-personal.md | 25 - demo-vault-v2/area.md | 7 - ...21-CleanShot_2026-02-21_at_17.12.59_2x.png | Bin 365881 -> 0 bytes ...ed_design__3_.png => laputa-reference.png} | Bin .../b2b-content-is-trust-not-traffic.md | 28 - .../career-tracks-depend-on-company-shape.md | 4 - demo-vault-v2/cycling-teaches-patience.md | 28 - demo-vault-v2/dark.md | 54 -- demo-vault-v2/default-theme.md | 21 - demo-vault-v2/enter-rename-test.md | 8 - demo-vault-v2/event-1on1-matteo-2024-01-10.md | 22 - demo-vault-v2/event-1on1-matteo-2024-01-24.md | 21 - demo-vault-v2/event-1on1-matteo-2024-02-07.md | 21 - demo-vault-v2/event-1on1-matteo-2024-02-21.md | 20 - demo-vault-v2/event-1on1-matteo-2024-03-06.md | 21 - demo-vault-v2/event-1on1-matteo-2024-03-20.md | 21 - demo-vault-v2/event-1on1-matteo-2024-04-03.md | 20 - demo-vault-v2/event-1on1-matteo-2024-04-17.md | 21 - demo-vault-v2/event-1on1-matteo-2024-05-01.md | 19 - demo-vault-v2/event-1on1-matteo-2024-05-15.md | 20 - demo-vault-v2/event-1on1-matteo-2024-05-29.md | 20 - demo-vault-v2/event-1on1-matteo-2024-06-12.md | 19 - demo-vault-v2/event-1on1-matteo-2024-06-26.md | 21 - demo-vault-v2/event-1on1-matteo-2024-07-10.md | 21 - demo-vault-v2/event-1on1-matteo-2024-07-24.md | 21 - demo-vault-v2/event-1on1-matteo-2024-08-07.md | 21 - demo-vault-v2/event-1on1-matteo-2024-08-21.md | 21 - demo-vault-v2/event-1on1-matteo-2024-09-04.md | 21 - demo-vault-v2/event-1on1-matteo-2024-09-18.md | 20 - demo-vault-v2/event-1on1-matteo-2024-10-02.md | 19 - demo-vault-v2/event-1on1-matteo-2024-10-16.md | 21 - demo-vault-v2/event-1on1-matteo-2024-10-30.md | 20 - demo-vault-v2/event-1on1-matteo-2024-11-13.md | 19 - demo-vault-v2/event-1on1-matteo-2024-11-27.md | 20 - demo-vault-v2/event-1on1-matteo-2024-12-11.md | 22 - demo-vault-v2/event-1on1-matteo-2024-12-25.md | 22 - demo-vault-v2/event-1on1-matteo-2025-01-08.md | 20 - demo-vault-v2/event-1on1-matteo-2025-01-22.md | 22 - demo-vault-v2/event-1on1-matteo-2025-02-05.md | 20 - demo-vault-v2/event-1on1-matteo-2025-02-19.md | 19 - demo-vault-v2/event-1on1-matteo-2025-03-05.md | 21 - demo-vault-v2/event-1on1-matteo-2025-03-19.md | 20 - demo-vault-v2/event-1on1-matteo-2025-04-02.md | 21 - demo-vault-v2/event-1on1-matteo-2025-04-16.md | 20 - demo-vault-v2/event-1on1-matteo-2025-04-30.md | 19 - demo-vault-v2/event-1on1-matteo-2025-05-14.md | 20 - demo-vault-v2/event-1on1-matteo-2025-05-28.md | 19 - demo-vault-v2/event-1on1-matteo-2025-06-11.md | 20 - demo-vault-v2/event-1on1-paco-2024-01-04.md | 20 - demo-vault-v2/event-1on1-paco-2024-02-01.md | 21 - demo-vault-v2/event-1on1-paco-2024-03-07.md | 21 - demo-vault-v2/event-1on1-paco-2024-04-04.md | 21 - demo-vault-v2/event-1on1-paco-2024-05-02.md | 21 - demo-vault-v2/event-1on1-paco-2024-06-06.md | 21 - demo-vault-v2/event-1on1-paco-2024-07-04.md | 20 - demo-vault-v2/event-1on1-paco-2024-08-01.md | 21 - demo-vault-v2/event-1on1-paco-2024-09-05.md | 20 - demo-vault-v2/event-1on1-paco-2024-10-03.md | 20 - demo-vault-v2/event-1on1-paco-2024-11-07.md | 21 - demo-vault-v2/event-1on1-paco-2024-12-05.md | 20 - demo-vault-v2/event-1on1-paco-2025-01-02.md | 20 - demo-vault-v2/event-1on1-paco-2025-02-06.md | 19 - demo-vault-v2/event-1on1-paco-2025-03-06.md | 20 - demo-vault-v2/event-1on1-paco-2025-04-03.md | 21 - demo-vault-v2/event-1on1-paco-2025-05-01.md | 21 - demo-vault-v2/event-1on1-paco-2025-06-05.md | 20 - demo-vault-v2/event-cycling-2024-01-02.md | 15 - demo-vault-v2/event-cycling-2024-01-09.md | 16 - demo-vault-v2/event-cycling-2024-01-16.md | 16 - demo-vault-v2/event-cycling-2024-01-23.md | 16 - demo-vault-v2/event-cycling-2024-01-30.md | 16 - demo-vault-v2/event-cycling-2024-02-06.md | 16 - demo-vault-v2/event-cycling-2024-02-13.md | 16 - demo-vault-v2/event-cycling-2024-02-20.md | 16 - demo-vault-v2/event-cycling-2024-02-27.md | 16 - demo-vault-v2/event-cycling-2024-03-05.md | 16 - demo-vault-v2/event-cycling-2024-03-12.md | 16 - demo-vault-v2/event-cycling-2024-03-19.md | 16 - demo-vault-v2/event-cycling-2024-03-26.md | 15 - demo-vault-v2/event-cycling-2024-04-02.md | 16 - demo-vault-v2/event-cycling-2024-04-09.md | 16 - demo-vault-v2/event-cycling-2024-04-16.md | 15 - demo-vault-v2/event-cycling-2024-04-23.md | 16 - demo-vault-v2/event-cycling-2024-04-30.md | 16 - demo-vault-v2/event-cycling-2024-05-07.md | 16 - demo-vault-v2/event-cycling-2024-05-14.md | 15 - demo-vault-v2/event-cycling-2024-05-21.md | 16 - demo-vault-v2/event-cycling-2024-05-28.md | 16 - demo-vault-v2/event-cycling-2024-06-04.md | 15 - demo-vault-v2/event-cycling-2024-06-11.md | 16 - demo-vault-v2/event-cycling-2024-06-18.md | 15 - demo-vault-v2/event-cycling-2024-06-25.md | 16 - demo-vault-v2/event-cycling-2024-07-02.md | 16 - demo-vault-v2/event-cycling-2024-07-09.md | 16 - demo-vault-v2/event-cycling-2024-07-16.md | 16 - demo-vault-v2/event-cycling-2024-07-23.md | 15 - demo-vault-v2/event-cycling-2024-07-30.md | 15 - demo-vault-v2/event-cycling-2024-08-06.md | 16 - demo-vault-v2/event-cycling-2024-08-13.md | 16 - demo-vault-v2/event-cycling-2024-08-20.md | 15 - demo-vault-v2/event-cycling-2024-08-27.md | 15 - demo-vault-v2/event-cycling-2024-09-03.md | 16 - demo-vault-v2/event-cycling-2024-09-10.md | 16 - demo-vault-v2/event-cycling-2024-09-17.md | 16 - demo-vault-v2/event-cycling-2024-09-24.md | 15 - demo-vault-v2/event-cycling-2024-10-01.md | 16 - demo-vault-v2/event-cycling-2024-10-08.md | 15 - demo-vault-v2/event-cycling-2024-10-15.md | 15 - demo-vault-v2/event-cycling-2024-10-22.md | 15 - demo-vault-v2/event-cycling-2024-10-29.md | 16 - demo-vault-v2/event-cycling-2024-11-05.md | 15 - demo-vault-v2/event-cycling-2024-11-12.md | 15 - demo-vault-v2/event-cycling-2024-11-19.md | 15 - demo-vault-v2/event-cycling-2024-11-26.md | 15 - demo-vault-v2/event-cycling-2024-12-03.md | 16 - demo-vault-v2/event-cycling-2024-12-10.md | 15 - demo-vault-v2/event-cycling-2024-12-17.md | 15 - demo-vault-v2/event-cycling-2024-12-24.md | 16 - demo-vault-v2/event-cycling-2024-12-31.md | 15 - demo-vault-v2/event-cycling-2025-01-07.md | 16 - demo-vault-v2/event-cycling-2025-01-14.md | 15 - demo-vault-v2/event-cycling-2025-01-21.md | 16 - demo-vault-v2/event-cycling-2025-01-28.md | 15 - demo-vault-v2/event-cycling-2025-02-04.md | 16 - demo-vault-v2/event-cycling-2025-02-11.md | 16 - demo-vault-v2/event-cycling-2025-02-18.md | 15 - demo-vault-v2/event-cycling-2025-02-25.md | 15 - demo-vault-v2/event-cycling-2025-03-04.md | 15 - demo-vault-v2/event-cycling-2025-03-11.md | 16 - demo-vault-v2/event-cycling-2025-03-18.md | 16 - demo-vault-v2/event-cycling-2025-03-25.md | 16 - demo-vault-v2/event-cycling-2025-04-01.md | 16 - demo-vault-v2/event-cycling-2025-04-08.md | 16 - demo-vault-v2/event-cycling-2025-04-15.md | 16 - demo-vault-v2/event-cycling-2025-04-22.md | 15 - demo-vault-v2/event-cycling-2025-04-29.md | 15 - demo-vault-v2/event-cycling-2025-05-06.md | 15 - demo-vault-v2/event-cycling-2025-05-13.md | 15 - demo-vault-v2/event-cycling-2025-05-20.md | 16 - demo-vault-v2/event-cycling-2025-05-27.md | 15 - demo-vault-v2/event-cycling-2025-06-03.md | 16 - demo-vault-v2/event-cycling-2025-06-10.md | 16 - demo-vault-v2/event-cycling-2025-06-17.md | 15 - .../event-cycling-endurance-2024-01-04.md | 15 - .../event-cycling-endurance-2024-01-11.md | 15 - .../event-cycling-endurance-2024-01-18.md | 15 - .../event-cycling-endurance-2024-01-25.md | 15 - .../event-cycling-endurance-2024-02-01.md | 15 - .../event-cycling-endurance-2024-02-08.md | 15 - .../event-cycling-endurance-2024-02-15.md | 15 - .../event-cycling-endurance-2024-02-22.md | 15 - .../event-cycling-endurance-2024-02-29.md | 15 - .../event-cycling-endurance-2024-03-07.md | 15 - .../event-cycling-endurance-2024-03-14.md | 15 - .../event-cycling-endurance-2024-03-21.md | 15 - .../event-cycling-endurance-2024-03-28.md | 15 - .../event-cycling-endurance-2024-04-04.md | 15 - .../event-cycling-endurance-2024-04-11.md | 15 - .../event-cycling-endurance-2024-04-18.md | 15 - .../event-cycling-endurance-2024-04-25.md | 15 - .../event-cycling-endurance-2024-05-02.md | 15 - .../event-cycling-endurance-2024-05-09.md | 15 - .../event-cycling-endurance-2024-05-16.md | 15 - .../event-cycling-endurance-2024-05-23.md | 15 - .../event-cycling-endurance-2024-05-30.md | 15 - .../event-cycling-endurance-2024-06-06.md | 15 - .../event-cycling-endurance-2024-06-13.md | 15 - .../event-cycling-endurance-2024-06-20.md | 15 - .../event-cycling-endurance-2024-06-27.md | 15 - .../event-cycling-endurance-2024-07-04.md | 15 - .../event-cycling-endurance-2024-07-11.md | 15 - .../event-cycling-endurance-2024-07-18.md | 15 - .../event-cycling-endurance-2024-07-25.md | 15 - .../event-cycling-endurance-2024-08-01.md | 15 - .../event-cycling-endurance-2024-08-08.md | 15 - .../event-cycling-endurance-2024-08-15.md | 15 - .../event-cycling-endurance-2024-08-22.md | 15 - .../event-cycling-endurance-2024-08-29.md | 15 - .../event-cycling-endurance-2024-09-05.md | 15 - .../event-cycling-endurance-2024-09-12.md | 15 - .../event-cycling-endurance-2024-09-19.md | 15 - .../event-cycling-endurance-2024-09-26.md | 15 - .../event-cycling-endurance-2024-10-03.md | 15 - .../event-cycling-endurance-2024-10-10.md | 15 - .../event-cycling-endurance-2024-10-17.md | 15 - .../event-cycling-endurance-2024-10-24.md | 15 - .../event-cycling-endurance-2024-10-31.md | 15 - .../event-cycling-endurance-2024-11-07.md | 15 - .../event-cycling-endurance-2024-11-14.md | 15 - .../event-cycling-endurance-2024-11-21.md | 15 - .../event-cycling-endurance-2024-11-28.md | 15 - .../event-cycling-endurance-2024-12-05.md | 15 - .../event-cycling-endurance-2024-12-12.md | 15 - .../event-cycling-endurance-2024-12-19.md | 15 - .../event-cycling-endurance-2024-12-26.md | 15 - .../event-cycling-endurance-2025-01-02.md | 15 - .../event-cycling-endurance-2025-01-09.md | 15 - .../event-cycling-endurance-2025-01-16.md | 15 - .../event-cycling-endurance-2025-01-23.md | 15 - .../event-cycling-endurance-2025-01-30.md | 15 - .../event-cycling-endurance-2025-02-06.md | 15 - .../event-cycling-endurance-2025-02-13.md | 15 - .../event-cycling-endurance-2025-02-20.md | 15 - .../event-cycling-endurance-2025-02-27.md | 15 - .../event-cycling-endurance-2025-03-06.md | 15 - .../event-cycling-endurance-2025-03-13.md | 15 - .../event-cycling-endurance-2025-03-20.md | 15 - .../event-cycling-endurance-2025-03-27.md | 15 - .../event-cycling-endurance-2025-04-03.md | 15 - .../event-cycling-endurance-2025-04-10.md | 15 - .../event-cycling-endurance-2025-04-17.md | 15 - .../event-cycling-endurance-2025-04-24.md | 15 - .../event-cycling-endurance-2025-05-01.md | 15 - .../event-cycling-endurance-2025-05-08.md | 15 - .../event-cycling-endurance-2025-05-15.md | 15 - .../event-cycling-endurance-2025-05-22.md | 15 - .../event-cycling-endurance-2025-05-29.md | 15 - .../event-cycling-endurance-2025-06-05.md | 15 - .../event-cycling-endurance-2025-06-12.md | 15 - .../event-cycling-endurance-2025-06-19.md | 15 - demo-vault-v2/event-dinner-2024-01-05.md | 16 - demo-vault-v2/event-dinner-2024-01-12.md | 16 - demo-vault-v2/event-dinner-2024-01-19.md | 16 - demo-vault-v2/event-dinner-2024-02-23.md | 16 - demo-vault-v2/event-dinner-2024-03-01.md | 16 - demo-vault-v2/event-dinner-2024-04-05.md | 16 - demo-vault-v2/event-dinner-2024-04-19.md | 16 - demo-vault-v2/event-dinner-2024-05-24.md | 16 - demo-vault-v2/event-dinner-2024-06-21.md | 16 - demo-vault-v2/event-dinner-2024-06-28.md | 16 - demo-vault-v2/event-dinner-2024-07-19.md | 16 - demo-vault-v2/event-dinner-2024-08-02.md | 16 - demo-vault-v2/event-dinner-2024-08-09.md | 16 - demo-vault-v2/event-dinner-2024-08-16.md | 16 - demo-vault-v2/event-dinner-2024-08-23.md | 16 - demo-vault-v2/event-dinner-2024-09-13.md | 16 - demo-vault-v2/event-dinner-2024-10-04.md | 16 - demo-vault-v2/event-dinner-2024-10-11.md | 16 - demo-vault-v2/event-dinner-2024-10-18.md | 16 - demo-vault-v2/event-dinner-2024-10-25.md | 16 - demo-vault-v2/event-dinner-2024-11-01.md | 16 - demo-vault-v2/event-dinner-2024-11-29.md | 16 - demo-vault-v2/event-dinner-2024-12-06.md | 16 - demo-vault-v2/event-dinner-2024-12-13.md | 16 - demo-vault-v2/event-dinner-2024-12-20.md | 16 - demo-vault-v2/event-dinner-2024-12-27.md | 16 - demo-vault-v2/event-dinner-2025-01-03.md | 16 - demo-vault-v2/event-dinner-2025-01-10.md | 16 - demo-vault-v2/event-dinner-2025-01-17.md | 16 - demo-vault-v2/event-dinner-2025-01-24.md | 16 - demo-vault-v2/event-dinner-2025-02-14.md | 16 - demo-vault-v2/event-dinner-2025-02-28.md | 16 - demo-vault-v2/event-dinner-2025-03-07.md | 16 - demo-vault-v2/event-dinner-2025-03-14.md | 16 - demo-vault-v2/event-dinner-2025-03-28.md | 16 - demo-vault-v2/event-dinner-2025-04-04.md | 16 - demo-vault-v2/event-dinner-2025-04-11.md | 16 - demo-vault-v2/event-dinner-2025-04-25.md | 16 - demo-vault-v2/event-dinner-2025-05-02.md | 16 - demo-vault-v2/event-dinner-2025-05-16.md | 16 - demo-vault-v2/event-dinner-2025-05-23.md | 16 - demo-vault-v2/event-dinner-2025-06-06.md | 16 - demo-vault-v2/event-dinner-2025-06-13.md | 16 - demo-vault-v2/event-family-call-2024-01-14.md | 16 - demo-vault-v2/event-family-call-2024-01-28.md | 15 - demo-vault-v2/event-family-call-2024-02-11.md | 15 - demo-vault-v2/event-family-call-2024-02-25.md | 16 - demo-vault-v2/event-family-call-2024-03-10.md | 15 - demo-vault-v2/event-family-call-2024-03-24.md | 16 - demo-vault-v2/event-family-call-2024-04-07.md | 16 - demo-vault-v2/event-family-call-2024-04-21.md | 15 - demo-vault-v2/event-family-call-2024-05-05.md | 16 - demo-vault-v2/event-family-call-2024-05-19.md | 15 - demo-vault-v2/event-family-call-2024-06-02.md | 16 - demo-vault-v2/event-family-call-2024-06-16.md | 16 - demo-vault-v2/event-family-call-2024-06-30.md | 16 - demo-vault-v2/event-family-call-2024-07-14.md | 16 - demo-vault-v2/event-family-call-2024-07-28.md | 16 - demo-vault-v2/event-family-call-2024-08-11.md | 16 - demo-vault-v2/event-family-call-2024-08-25.md | 16 - demo-vault-v2/event-family-call-2024-09-08.md | 15 - demo-vault-v2/event-family-call-2024-09-22.md | 16 - demo-vault-v2/event-family-call-2024-10-06.md | 16 - demo-vault-v2/event-family-call-2024-10-20.md | 16 - demo-vault-v2/event-family-call-2024-11-03.md | 16 - demo-vault-v2/event-family-call-2024-11-17.md | 16 - demo-vault-v2/event-family-call-2024-12-01.md | 16 - demo-vault-v2/event-family-call-2024-12-15.md | 16 - demo-vault-v2/event-family-call-2024-12-29.md | 16 - demo-vault-v2/event-family-call-2025-01-12.md | 16 - demo-vault-v2/event-family-call-2025-01-26.md | 16 - demo-vault-v2/event-family-call-2025-02-09.md | 16 - demo-vault-v2/event-family-call-2025-02-23.md | 16 - demo-vault-v2/event-family-call-2025-03-09.md | 16 - demo-vault-v2/event-family-call-2025-03-23.md | 16 - demo-vault-v2/event-family-call-2025-04-06.md | 16 - demo-vault-v2/event-family-call-2025-04-20.md | 16 - demo-vault-v2/event-family-call-2025-05-04.md | 16 - demo-vault-v2/event-family-call-2025-05-18.md | 16 - demo-vault-v2/event-family-call-2025-06-01.md | 16 - demo-vault-v2/event-family-call-2025-06-15.md | 16 - demo-vault-v2/event-gym-2024-01-03.md | 15 - demo-vault-v2/event-gym-2024-01-17.md | 15 - demo-vault-v2/event-gym-2024-01-31.md | 15 - demo-vault-v2/event-gym-2024-02-14.md | 15 - demo-vault-v2/event-gym-2024-02-28.md | 15 - demo-vault-v2/event-gym-2024-03-13.md | 15 - demo-vault-v2/event-gym-2024-03-27.md | 15 - demo-vault-v2/event-gym-2024-04-10.md | 15 - demo-vault-v2/event-gym-2024-04-24.md | 15 - demo-vault-v2/event-gym-2024-05-08.md | 15 - demo-vault-v2/event-gym-2024-05-22.md | 15 - demo-vault-v2/event-gym-2024-06-05.md | 15 - demo-vault-v2/event-gym-2024-06-19.md | 15 - demo-vault-v2/event-gym-2024-07-03.md | 15 - demo-vault-v2/event-gym-2024-07-17.md | 15 - demo-vault-v2/event-gym-2024-07-31.md | 15 - demo-vault-v2/event-gym-2024-08-14.md | 15 - demo-vault-v2/event-gym-2024-08-28.md | 15 - demo-vault-v2/event-gym-2024-09-11.md | 15 - demo-vault-v2/event-gym-2024-09-25.md | 15 - demo-vault-v2/event-gym-2024-10-09.md | 15 - demo-vault-v2/event-gym-2024-10-23.md | 15 - demo-vault-v2/event-gym-2024-11-06.md | 15 - demo-vault-v2/event-gym-2024-11-20.md | 15 - demo-vault-v2/event-gym-2024-12-04.md | 15 - demo-vault-v2/event-gym-2024-12-18.md | 15 - demo-vault-v2/event-gym-2025-01-01.md | 15 - demo-vault-v2/event-gym-2025-01-15.md | 15 - demo-vault-v2/event-gym-2025-01-29.md | 15 - demo-vault-v2/event-gym-2025-02-12.md | 15 - demo-vault-v2/event-gym-2025-02-26.md | 15 - demo-vault-v2/event-gym-2025-03-12.md | 15 - demo-vault-v2/event-gym-2025-03-26.md | 15 - demo-vault-v2/event-gym-2025-04-09.md | 15 - demo-vault-v2/event-gym-2025-04-23.md | 15 - demo-vault-v2/event-gym-2025-05-07.md | 15 - demo-vault-v2/event-gym-2025-05-21.md | 15 - demo-vault-v2/event-gym-2025-06-04.md | 15 - demo-vault-v2/event-gym-2025-06-18.md | 15 - demo-vault-v2/event-gym-fri-2024-01-12.md | 15 - demo-vault-v2/event-gym-fri-2024-01-26.md | 15 - demo-vault-v2/event-gym-fri-2024-02-09.md | 15 - demo-vault-v2/event-gym-fri-2024-02-23.md | 15 - demo-vault-v2/event-gym-fri-2024-03-08.md | 15 - demo-vault-v2/event-gym-fri-2024-03-22.md | 15 - demo-vault-v2/event-gym-fri-2024-04-05.md | 15 - demo-vault-v2/event-gym-fri-2024-04-19.md | 15 - demo-vault-v2/event-gym-fri-2024-05-03.md | 15 - demo-vault-v2/event-gym-fri-2024-05-17.md | 15 - demo-vault-v2/event-gym-fri-2024-05-31.md | 15 - demo-vault-v2/event-gym-fri-2024-06-14.md | 15 - demo-vault-v2/event-gym-fri-2024-06-28.md | 15 - demo-vault-v2/event-gym-fri-2024-07-12.md | 15 - demo-vault-v2/event-gym-fri-2024-07-26.md | 15 - demo-vault-v2/event-gym-fri-2024-08-09.md | 15 - demo-vault-v2/event-gym-fri-2024-08-23.md | 15 - demo-vault-v2/event-gym-fri-2024-09-06.md | 15 - demo-vault-v2/event-gym-fri-2024-09-20.md | 15 - demo-vault-v2/event-gym-fri-2024-10-04.md | 15 - demo-vault-v2/event-gym-fri-2024-10-18.md | 15 - demo-vault-v2/event-gym-fri-2024-11-01.md | 15 - demo-vault-v2/event-gym-fri-2024-11-15.md | 15 - demo-vault-v2/event-gym-fri-2024-11-29.md | 15 - demo-vault-v2/event-gym-fri-2024-12-13.md | 15 - demo-vault-v2/event-gym-fri-2024-12-27.md | 15 - demo-vault-v2/event-gym-fri-2025-01-10.md | 15 - demo-vault-v2/event-gym-fri-2025-01-24.md | 15 - demo-vault-v2/event-gym-fri-2025-02-07.md | 15 - demo-vault-v2/event-gym-fri-2025-02-21.md | 15 - demo-vault-v2/event-gym-fri-2025-03-07.md | 15 - demo-vault-v2/event-gym-fri-2025-03-21.md | 15 - demo-vault-v2/event-gym-fri-2025-04-04.md | 15 - demo-vault-v2/event-gym-fri-2025-04-18.md | 15 - demo-vault-v2/event-gym-fri-2025-05-02.md | 15 - demo-vault-v2/event-gym-fri-2025-05-16.md | 15 - demo-vault-v2/event-gym-fri-2025-05-30.md | 15 - demo-vault-v2/event-gym-fri-2025-06-13.md | 15 - demo-vault-v2/event-long-ride-2024-01-06.md | 21 - demo-vault-v2/event-long-ride-2024-01-13.md | 18 - demo-vault-v2/event-long-ride-2024-01-20.md | 18 - demo-vault-v2/event-long-ride-2024-01-27.md | 21 - demo-vault-v2/event-long-ride-2024-02-03.md | 18 - demo-vault-v2/event-long-ride-2024-02-10.md | 21 - demo-vault-v2/event-long-ride-2024-02-17.md | 18 - demo-vault-v2/event-long-ride-2024-02-24.md | 18 - demo-vault-v2/event-long-ride-2024-03-02.md | 18 - demo-vault-v2/event-long-ride-2024-03-09.md | 21 - demo-vault-v2/event-long-ride-2024-03-16.md | 18 - demo-vault-v2/event-long-ride-2024-03-23.md | 18 - demo-vault-v2/event-long-ride-2024-03-30.md | 22 - demo-vault-v2/event-long-ride-2024-04-06.md | 18 - demo-vault-v2/event-long-ride-2024-04-13.md | 21 - demo-vault-v2/event-long-ride-2024-04-20.md | 18 - demo-vault-v2/event-long-ride-2024-04-27.md | 18 - demo-vault-v2/event-long-ride-2024-05-04.md | 21 - demo-vault-v2/event-long-ride-2024-05-11.md | 18 - demo-vault-v2/event-long-ride-2024-05-18.md | 18 - demo-vault-v2/event-long-ride-2024-05-25.md | 18 - demo-vault-v2/event-long-ride-2024-06-01.md | 21 - demo-vault-v2/event-long-ride-2024-06-08.md | 19 - demo-vault-v2/event-long-ride-2024-06-15.md | 18 - demo-vault-v2/event-long-ride-2024-06-22.md | 21 - demo-vault-v2/event-long-ride-2024-06-29.md | 18 - demo-vault-v2/event-long-ride-2024-07-06.md | 18 - demo-vault-v2/event-long-ride-2024-07-13.md | 18 - demo-vault-v2/event-long-ride-2024-07-20.md | 21 - demo-vault-v2/event-long-ride-2024-07-27.md | 18 - demo-vault-v2/event-long-ride-2024-08-03.md | 21 - demo-vault-v2/event-long-ride-2024-08-10.md | 18 - demo-vault-v2/event-long-ride-2024-08-17.md | 18 - demo-vault-v2/event-long-ride-2024-08-24.md | 21 - demo-vault-v2/event-long-ride-2024-08-31.md | 18 - demo-vault-v2/event-long-ride-2024-09-07.md | 18 - demo-vault-v2/event-long-ride-2024-09-14.md | 22 - demo-vault-v2/event-long-ride-2024-09-21.md | 19 - demo-vault-v2/event-long-ride-2024-09-28.md | 18 - demo-vault-v2/event-long-ride-2024-10-05.md | 18 - demo-vault-v2/event-long-ride-2024-10-12.md | 18 - demo-vault-v2/event-long-ride-2024-10-19.md | 21 - demo-vault-v2/event-long-ride-2024-10-26.md | 18 - demo-vault-v2/event-long-ride-2024-11-02.md | 19 - demo-vault-v2/event-long-ride-2024-11-09.md | 21 - demo-vault-v2/event-long-ride-2024-11-16.md | 18 - demo-vault-v2/event-long-ride-2024-11-23.md | 18 - demo-vault-v2/event-long-ride-2024-11-30.md | 21 - demo-vault-v2/event-long-ride-2024-12-07.md | 18 - demo-vault-v2/event-long-ride-2024-12-14.md | 18 - demo-vault-v2/event-long-ride-2024-12-21.md | 18 - demo-vault-v2/event-long-ride-2024-12-28.md | 19 - demo-vault-v2/event-long-ride-2025-01-04.md | 18 - demo-vault-v2/event-long-ride-2025-01-11.md | 21 - demo-vault-v2/event-long-ride-2025-01-18.md | 18 - demo-vault-v2/event-long-ride-2025-01-25.md | 21 - demo-vault-v2/event-long-ride-2025-02-01.md | 18 - demo-vault-v2/event-long-ride-2025-02-08.md | 21 - demo-vault-v2/event-long-ride-2025-02-15.md | 18 - demo-vault-v2/event-long-ride-2025-02-22.md | 18 - demo-vault-v2/event-long-ride-2025-03-01.md | 18 - demo-vault-v2/event-long-ride-2025-03-08.md | 18 - demo-vault-v2/event-long-ride-2025-03-15.md | 21 - demo-vault-v2/event-long-ride-2025-03-22.md | 18 - demo-vault-v2/event-long-ride-2025-03-29.md | 18 - demo-vault-v2/event-long-ride-2025-04-05.md | 18 - demo-vault-v2/event-long-ride-2025-04-12.md | 21 - demo-vault-v2/event-long-ride-2025-04-19.md | 18 - demo-vault-v2/event-long-ride-2025-04-26.md | 21 - demo-vault-v2/event-long-ride-2025-05-03.md | 18 - demo-vault-v2/event-long-ride-2025-05-10.md | 18 - demo-vault-v2/event-long-ride-2025-05-17.md | 18 - demo-vault-v2/event-long-ride-2025-05-24.md | 19 - demo-vault-v2/event-long-ride-2025-05-31.md | 21 - demo-vault-v2/event-long-ride-2025-06-07.md | 19 - demo-vault-v2/event-long-ride-2025-06-14.md | 22 - demo-vault-v2/event-nonna-visit-2024-01-28.md | 17 - demo-vault-v2/event-nonna-visit-2024-02-25.md | 17 - demo-vault-v2/event-nonna-visit-2024-03-24.md | 17 - demo-vault-v2/event-nonna-visit-2024-03-31.md | 17 - demo-vault-v2/event-nonna-visit-2024-04-28.md | 17 - demo-vault-v2/event-nonna-visit-2024-05-26.md | 17 - demo-vault-v2/event-nonna-visit-2024-06-30.md | 17 - demo-vault-v2/event-nonna-visit-2024-07-28.md | 17 - demo-vault-v2/event-nonna-visit-2024-08-25.md | 17 - demo-vault-v2/event-nonna-visit-2024-09-29.md | 17 - demo-vault-v2/event-nonna-visit-2024-10-27.md | 17 - demo-vault-v2/event-nonna-visit-2024-11-24.md | 17 - demo-vault-v2/event-nonna-visit-2024-12-29.md | 17 - demo-vault-v2/event-nonna-visit-2025-01-26.md | 17 - demo-vault-v2/event-nonna-visit-2025-03-30.md | 17 - demo-vault-v2/event-nonna-visit-2025-04-27.md | 17 - demo-vault-v2/event-nonna-visit-2025-05-25.md | 17 - demo-vault-v2/event-podcast-rec-2024-02-01.md | 24 - demo-vault-v2/event-podcast-rec-2024-02-15.md | 23 - demo-vault-v2/event-podcast-rec-2024-02-29.md | 24 - demo-vault-v2/event-podcast-rec-2024-03-14.md | 23 - demo-vault-v2/event-podcast-rec-2024-03-28.md | 24 - demo-vault-v2/event-podcast-rec-2024-04-11.md | 24 - demo-vault-v2/event-podcast-rec-2024-04-25.md | 23 - demo-vault-v2/event-podcast-rec-2024-05-09.md | 24 - demo-vault-v2/event-podcast-rec-2024-05-23.md | 23 - demo-vault-v2/event-podcast-rec-2024-06-06.md | 24 - demo-vault-v2/event-podcast-rec-2024-06-20.md | 24 - demo-vault-v2/event-podcast-rec-2024-07-04.md | 23 - demo-vault-v2/event-podcast-rec-2024-07-18.md | 24 - demo-vault-v2/event-podcast-rec-2024-08-01.md | 23 - demo-vault-v2/event-podcast-rec-2024-08-15.md | 24 - demo-vault-v2/event-podcast-rec-2024-08-29.md | 23 - demo-vault-v2/event-podcast-rec-2024-09-12.md | 24 - demo-vault-v2/event-podcast-rec-2024-09-26.md | 23 - demo-vault-v2/event-podcast-rec-2024-10-10.md | 24 - demo-vault-v2/event-podcast-rec-2024-10-24.md | 24 - demo-vault-v2/event-podcast-rec-2024-11-07.md | 24 - demo-vault-v2/event-podcast-rec-2024-11-21.md | 23 - demo-vault-v2/event-podcast-rec-2024-12-05.md | 24 - demo-vault-v2/event-podcast-rec-2024-12-19.md | 23 - demo-vault-v2/event-podcast-rec-2025-01-02.md | 24 - demo-vault-v2/event-podcast-rec-2025-01-16.md | 23 - demo-vault-v2/event-podcast-rec-2025-01-30.md | 24 - demo-vault-v2/event-podcast-rec-2025-02-13.md | 24 - demo-vault-v2/event-podcast-rec-2025-02-27.md | 23 - demo-vault-v2/event-podcast-rec-2025-03-13.md | 24 - demo-vault-v2/event-podcast-rec-2025-03-27.md | 24 - demo-vault-v2/event-podcast-rec-2025-04-10.md | 23 - demo-vault-v2/event-podcast-rec-2025-04-24.md | 24 - demo-vault-v2/event-podcast-rec-2025-05-08.md | 24 - demo-vault-v2/event-podcast-rec-2025-05-22.md | 23 - demo-vault-v2/event-podcast-rec-2025-06-05.md | 24 - demo-vault-v2/event-podcast-rec-2025-06-19.md | 24 - demo-vault-v2/event-reading-2024-01-07.md | 15 - demo-vault-v2/event-reading-2024-01-21.md | 18 - demo-vault-v2/event-reading-2024-02-04.md | 15 - demo-vault-v2/event-reading-2024-02-18.md | 15 - demo-vault-v2/event-reading-2024-03-03.md | 19 - demo-vault-v2/event-reading-2024-03-17.md | 15 - demo-vault-v2/event-reading-2024-03-31.md | 15 - demo-vault-v2/event-reading-2024-04-14.md | 15 - demo-vault-v2/event-reading-2024-04-28.md | 18 - demo-vault-v2/event-reading-2024-05-12.md | 15 - demo-vault-v2/event-reading-2024-05-26.md | 15 - demo-vault-v2/event-reading-2024-06-09.md | 15 - demo-vault-v2/event-reading-2024-06-23.md | 18 - demo-vault-v2/event-reading-2024-07-07.md | 15 - demo-vault-v2/event-reading-2024-07-21.md | 15 - demo-vault-v2/event-reading-2024-08-04.md | 15 - demo-vault-v2/event-reading-2024-08-18.md | 15 - demo-vault-v2/event-reading-2024-09-01.md | 18 - demo-vault-v2/event-reading-2024-09-15.md | 15 - demo-vault-v2/event-reading-2024-09-29.md | 15 - demo-vault-v2/event-reading-2024-10-13.md | 18 - demo-vault-v2/event-reading-2024-10-27.md | 15 - demo-vault-v2/event-reading-2024-11-10.md | 18 - demo-vault-v2/event-reading-2024-11-24.md | 15 - demo-vault-v2/event-reading-2024-12-08.md | 15 - demo-vault-v2/event-reading-2024-12-22.md | 15 - demo-vault-v2/event-reading-2025-01-05.md | 18 - demo-vault-v2/event-reading-2025-01-19.md | 15 - demo-vault-v2/event-reading-2025-02-02.md | 15 - demo-vault-v2/event-reading-2025-02-16.md | 18 - demo-vault-v2/event-reading-2025-03-02.md | 15 - demo-vault-v2/event-reading-2025-03-16.md | 18 - demo-vault-v2/event-reading-2025-03-30.md | 15 - demo-vault-v2/event-reading-2025-04-13.md | 18 - demo-vault-v2/event-reading-2025-04-27.md | 15 - demo-vault-v2/event-reading-2025-05-11.md | 15 - demo-vault-v2/event-reading-2025-05-25.md | 19 - demo-vault-v2/event-reading-2025-06-08.md | 15 - .../event-sponsor-call-2024-01-05.md | 22 - .../event-sponsor-call-2024-01-19.md | 22 - .../event-sponsor-call-2024-02-02.md | 22 - .../event-sponsor-call-2024-02-16.md | 22 - .../event-sponsor-call-2024-03-01.md | 22 - .../event-sponsor-call-2024-03-15.md | 22 - .../event-sponsor-call-2024-03-29.md | 22 - .../event-sponsor-call-2024-04-12.md | 22 - .../event-sponsor-call-2024-04-26.md | 22 - .../event-sponsor-call-2024-05-10.md | 22 - .../event-sponsor-call-2024-05-24.md | 22 - .../event-sponsor-call-2024-06-07.md | 22 - .../event-sponsor-call-2024-06-21.md | 22 - .../event-sponsor-call-2024-07-05.md | 22 - .../event-sponsor-call-2024-07-19.md | 22 - .../event-sponsor-call-2024-08-02.md | 22 - .../event-sponsor-call-2024-08-16.md | 22 - .../event-sponsor-call-2024-08-30.md | 22 - .../event-sponsor-call-2024-09-13.md | 22 - .../event-sponsor-call-2024-09-27.md | 22 - .../event-sponsor-call-2024-10-11.md | 22 - .../event-sponsor-call-2024-10-25.md | 22 - .../event-sponsor-call-2024-11-08.md | 22 - .../event-sponsor-call-2024-11-22.md | 22 - .../event-sponsor-call-2024-12-06.md | 22 - .../event-sponsor-call-2024-12-20.md | 22 - .../event-sponsor-call-2025-01-03.md | 22 - .../event-sponsor-call-2025-01-17.md | 22 - .../event-sponsor-call-2025-01-31.md | 22 - .../event-sponsor-call-2025-02-14.md | 22 - .../event-sponsor-call-2025-02-28.md | 22 - .../event-sponsor-call-2025-03-14.md | 22 - .../event-sponsor-call-2025-03-28.md | 22 - .../event-sponsor-call-2025-04-11.md | 22 - .../event-sponsor-call-2025-04-25.md | 22 - .../event-sponsor-call-2025-05-09.md | 22 - .../event-sponsor-call-2025-05-23.md | 22 - .../event-sponsor-call-2025-06-06.md | 22 - demo-vault-v2/event-team-sync-2024-01-01.md | 23 - demo-vault-v2/event-team-sync-2024-01-08.md | 24 - demo-vault-v2/event-team-sync-2024-01-15.md | 24 - demo-vault-v2/event-team-sync-2024-01-22.md | 23 - demo-vault-v2/event-team-sync-2024-01-29.md | 22 - demo-vault-v2/event-team-sync-2024-02-05.md | 22 - demo-vault-v2/event-team-sync-2024-02-12.md | 24 - demo-vault-v2/event-team-sync-2024-02-19.md | 23 - demo-vault-v2/event-team-sync-2024-02-26.md | 24 - demo-vault-v2/event-team-sync-2024-03-04.md | 25 - demo-vault-v2/event-team-sync-2024-03-11.md | 23 - demo-vault-v2/event-team-sync-2024-03-18.md | 23 - demo-vault-v2/event-team-sync-2024-03-25.md | 23 - demo-vault-v2/event-team-sync-2024-04-01.md | 23 - demo-vault-v2/event-team-sync-2024-04-08.md | 25 - demo-vault-v2/event-team-sync-2024-04-15.md | 22 - demo-vault-v2/event-team-sync-2024-04-22.md | 24 - demo-vault-v2/event-team-sync-2024-04-29.md | 24 - demo-vault-v2/event-team-sync-2024-05-06.md | 24 - demo-vault-v2/event-team-sync-2024-05-13.md | 22 - demo-vault-v2/event-team-sync-2024-05-20.md | 23 - demo-vault-v2/event-team-sync-2024-05-27.md | 22 - demo-vault-v2/event-team-sync-2024-06-03.md | 22 - demo-vault-v2/event-team-sync-2024-06-10.md | 23 - demo-vault-v2/event-team-sync-2024-06-17.md | 23 - demo-vault-v2/event-team-sync-2024-06-24.md | 24 - demo-vault-v2/event-team-sync-2024-07-01.md | 25 - demo-vault-v2/event-team-sync-2024-07-08.md | 23 - demo-vault-v2/event-team-sync-2024-07-15.md | 22 - demo-vault-v2/event-team-sync-2024-07-22.md | 24 - demo-vault-v2/event-team-sync-2024-07-29.md | 23 - demo-vault-v2/event-team-sync-2024-08-05.md | 23 - demo-vault-v2/event-team-sync-2024-08-12.md | 24 - demo-vault-v2/event-team-sync-2024-08-19.md | 22 - demo-vault-v2/event-team-sync-2024-08-26.md | 24 - demo-vault-v2/event-team-sync-2024-09-02.md | 23 - demo-vault-v2/event-team-sync-2024-09-09.md | 24 - demo-vault-v2/event-team-sync-2024-09-16.md | 23 - demo-vault-v2/event-team-sync-2024-09-23.md | 23 - demo-vault-v2/event-team-sync-2024-09-30.md | 25 - demo-vault-v2/event-team-sync-2024-10-07.md | 23 - demo-vault-v2/event-team-sync-2024-10-14.md | 24 - demo-vault-v2/event-team-sync-2024-10-21.md | 22 - demo-vault-v2/event-team-sync-2024-10-28.md | 22 - demo-vault-v2/event-team-sync-2024-11-04.md | 24 - demo-vault-v2/event-team-sync-2024-11-11.md | 25 - demo-vault-v2/event-team-sync-2024-11-18.md | 22 - demo-vault-v2/event-team-sync-2024-11-25.md | 24 - demo-vault-v2/event-team-sync-2024-12-02.md | 23 - demo-vault-v2/event-team-sync-2024-12-09.md | 24 - demo-vault-v2/event-team-sync-2024-12-16.md | 23 - demo-vault-v2/event-team-sync-2024-12-23.md | 24 - demo-vault-v2/event-team-sync-2024-12-30.md | 22 - demo-vault-v2/event-team-sync-2025-01-06.md | 24 - demo-vault-v2/event-team-sync-2025-01-13.md | 28 +- demo-vault-v2/event-team-sync-2025-01-20.md | 22 - demo-vault-v2/event-team-sync-2025-01-27.md | 25 - demo-vault-v2/event-team-sync-2025-02-03.md | 24 - demo-vault-v2/event-team-sync-2025-02-10.md | 22 - demo-vault-v2/event-team-sync-2025-02-17.md | 22 - demo-vault-v2/event-team-sync-2025-02-24.md | 24 - demo-vault-v2/event-team-sync-2025-03-03.md | 22 - demo-vault-v2/event-team-sync-2025-03-10.md | 25 - demo-vault-v2/event-team-sync-2025-03-17.md | 24 - demo-vault-v2/event-team-sync-2025-03-24.md | 22 - demo-vault-v2/event-team-sync-2025-03-31.md | 22 - demo-vault-v2/event-team-sync-2025-04-07.md | 24 - demo-vault-v2/event-team-sync-2025-04-14.md | 24 - demo-vault-v2/event-team-sync-2025-04-21.md | 23 - demo-vault-v2/event-team-sync-2025-04-28.md | 24 - demo-vault-v2/event-team-sync-2025-05-05.md | 24 - demo-vault-v2/event-team-sync-2025-05-12.md | 23 - demo-vault-v2/event-team-sync-2025-05-19.md | 24 - demo-vault-v2/event-team-sync-2025-05-26.md | 23 - demo-vault-v2/event-team-sync-2025-06-02.md | 25 - demo-vault-v2/event-team-sync-2025-06-09.md | 24 - demo-vault-v2/event-team-sync-2025-06-16.md | 22 - demo-vault-v2/event.md | 7 - demo-vault-v2/evergreen.md | 7 - demo-vault-v2/experiment-failed-podcast.md | 21 - demo-vault-v2/experiment.md | 7 - demo-vault-v2/final-renamed.md | 10 - demo-vault-v2/final-title-r-renamed.md | 12 - demo-vault-v2/final-title-r.md | 8 - demo-vault-v2/final-title-renamed-renamed.md | 12 - demo-vault-v2/final-title-renamed.md | 8 - demo-vault-v2/final-title.md | 4 - demo-vault-v2/goal.md | 7 - .../index-funds-and-intellectual-humility.md | 27 - .../investing-in-yourself-vs-markets.md | 27 - .../italian-startup-ecosystem-observations.md | 27 - .../knowledge-management-is-not-filing.md | 28 - demo-vault-v2/laputa-qa-reference.md | 16 + demo-vault-v2/measure-articles-per-week.md | 27 - demo-vault-v2/measure-books-per-month.md | 28 - demo-vault-v2/measure-close-rate.md | 30 +- demo-vault-v2/measure-cycling-km-per-month.md | 30 - demo-vault-v2/measure-essay-quality-score.md | 36 -- .../measure-evergreen-notes-created.md | 29 - demo-vault-v2/measure-net-worth.md | 29 - demo-vault-v2/measure-open-rate.md | 29 - demo-vault-v2/measure-podcast-downloads.md | 29 - .../measure-podcast-episodes-per-month.md | 29 - demo-vault-v2/measure-resting-hr.md | 29 - demo-vault-v2/measure-savings-rate.md | 29 - demo-vault-v2/measure-sponsorship-mrr.md | 31 +- demo-vault-v2/measure-subscribers.md | 29 - demo-vault-v2/measure-task-completion-rate.md | 29 - demo-vault-v2/measure-team-nps.md | 29 - demo-vault-v2/measure.md | 7 - demo-vault-v2/minimal.md | 54 -- demo-vault-v2/month.md | 7 - demo-vault-v2/my-renamed-note.md | 8 - .../newsletter-growth-is-about-trust.md | 28 - demo-vault-v2/newsletter-subject-lines.md | 28 - demo-vault-v2/note-atomic-habits.md | 43 -- demo-vault-v2/note-born-to-run.md | 42 -- demo-vault-v2/note-building-a-second-brain.md | 43 -- demo-vault-v2/note-deep-work.md | 44 -- demo-vault-v2/note-deprecated-workflow.md | 18 - demo-vault-v2/note-essentialism.md | 43 -- .../note-good-strategy-bad-strategy.md | 44 -- demo-vault-v2/note-grit.md | 44 -- demo-vault-v2/note-how-minds-change.md | 43 -- .../note-makers-schedule-managers.md | 43 -- demo-vault-v2/note-man-search-for-meaning.md | 43 -- demo-vault-v2/note-never-split-difference.md | 43 -- demo-vault-v2/note-old-meeting-notes.md | 18 - demo-vault-v2/note-on-clear-prose.md | 9 + .../note-on-the-shortness-of-life.md | 44 -- demo-vault-v2/note-on-writing-well.md | 44 -- demo-vault-v2/note-radical-candor.md | 43 -- demo-vault-v2/note-range.md | 44 -- demo-vault-v2/note-show-your-work.md | 44 -- .../note-so-good-they-cant-ignore.md | 44 -- demo-vault-v2/note-the-art-of-learning.md | 44 -- .../note-the-courage-to-be-disliked.md | 43 -- demo-vault-v2/note-the-effective-executive.md | 44 -- .../note-the-hard-thing-about-hard-things.md | 44 -- demo-vault-v2/note-the-innovators-dilemma.md | 46 -- demo-vault-v2/note-the-lean-startup.md | 44 -- demo-vault-v2/note-the-mom-test.md | 44 -- demo-vault-v2/note-the-obstacle-is-the-way.md | 43 -- demo-vault-v2/note-the-willpower-instinct.md | 44 -- demo-vault-v2/note-thinking-fast-and-slow.md | 44 -- demo-vault-v2/note-thinking-in-bets.md | 44 -- demo-vault-v2/note-traffic-secrets.md | 45 -- demo-vault-v2/note-zero-to-one.md | 44 -- demo-vault-v2/note.md | 7 - demo-vault-v2/note/final-title-r-renamed.md | 10 - demo-vault-v2/note/final-title-r.md | 8 - .../note/final-title-renamed-renamed.md | 10 - .../note/untitled-save-no-rename-te.md | 8 - .../note/untitled-save-no-rename-test-2.md | 6 - .../note/untitled-save-no-rename-test.md | 6 - demo-vault-v2/note/untitled-tes-renamed.md | 10 - .../note/untitled-test-note-abc-2.md | 6 - .../note/untitled-test-note-abc-3.md | 6 - .../note/untitled-test-note-abc-renamed.md | 10 - .../on-consistency-in-creative-work.md | 28 - demo-vault-v2/on-founder-energy-management.md | 28 - demo-vault-v2/open-source-as-marketing.md | 28 - demo-vault-v2/person-adeel-khan.md | 22 - demo-vault-v2/person-alberto-ferro.md | 22 - demo-vault-v2/person-alessandro-ferrari.md | 22 - demo-vault-v2/person-andrea-colombo.md | 21 - demo-vault-v2/person-andrea-provaglio.md | 22 - demo-vault-v2/person-anna-fontana.md | 20 - demo-vault-v2/person-anna-kowalski.md | 22 - demo-vault-v2/person-anna-lindberg.md | 22 - demo-vault-v2/person-antonio-marchetti.md | 22 - demo-vault-v2/person-benedetta-vitali.md | 22 - demo-vault-v2/person-carlos-mendez.md | 22 - demo-vault-v2/person-chiara-romano.md | 22 - demo-vault-v2/person-clara-dupont.md | 22 - demo-vault-v2/person-david-eriksson.md | 22 - demo-vault-v2/person-david-kim.md | 22 - demo-vault-v2/person-davide-conti.md | 22 - demo-vault-v2/person-diego-santos.md | 22 - demo-vault-v2/person-elena-konstantinou.md | 22 - demo-vault-v2/person-elena-rossi.md | 23 - demo-vault-v2/person-elisa-barbieri.md | 20 - demo-vault-v2/person-emilia-hoffmann.md | 22 - demo-vault-v2/person-emma-wilson.md | 22 - demo-vault-v2/person-federico-moretti.md | 23 - demo-vault-v2/person-francesca-deluca.md | 22 - demo-vault-v2/person-francesca-marino.md | 21 - demo-vault-v2/person-gianluca-esposito.md | 22 - demo-vault-v2/person-giulia-conti.md | 20 - demo-vault-v2/person-giulia-marchetti.md | 24 - demo-vault-v2/person-henrik-johansson.md | 22 - demo-vault-v2/person-hiroshi-tanaka.md | 22 - demo-vault-v2/person-james-mitchell.md | 22 - demo-vault-v2/person-james-murphy.md | 22 - demo-vault-v2/person-katja-mueller.md | 22 - demo-vault-v2/person-kenji-tanaka.md | 22 - demo-vault-v2/person-lisa-chen.md | 22 - demo-vault-v2/person-lorenzo-galli.md | 21 - demo-vault-v2/person-luca-rossi.md | 28 +- demo-vault-v2/person-lucia-martinez.md | 22 - demo-vault-v2/person-marco-bianchi.md | 24 - demo-vault-v2/person-marco-cecconi.md | 22 - demo-vault-v2/person-marcus-weber.md | 22 - demo-vault-v2/person-maria-colombo.md | 23 - demo-vault-v2/person-marta-pellegrini.md | 20 - demo-vault-v2/person-massimo-artusi.md | 22 - demo-vault-v2/person-matteo-cellini.md | 30 +- demo-vault-v2/person-matteo-gentile.md | 22 - demo-vault-v2/person-mattia-de-luca.md | 20 - demo-vault-v2/person-michael-brown.md | 22 - demo-vault-v2/person-natalie-chang.md | 22 - demo-vault-v2/person-nicola-fabbri.md | 20 - demo-vault-v2/person-nina-petersen.md | 22 - demo-vault-v2/person-nonna-lucia.md | 23 - demo-vault-v2/person-olivia-martinez.md | 22 - demo-vault-v2/person-paco-furiani.md | 29 - demo-vault-v2/person-paolo-bergamo.md | 22 - demo-vault-v2/person-patrick-nguyen.md | 22 - demo-vault-v2/person-peter-schmidt.md | 22 - demo-vault-v2/person-piergiorgio-conte.md | 23 - demo-vault-v2/person-priya-sharma.md | 22 - demo-vault-v2/person-rachel-green.md | 22 - demo-vault-v2/person-raj-patel.md | 22 - demo-vault-v2/person-roberto-rossi.md | 23 - demo-vault-v2/person-sara-ricci.md | 29 - demo-vault-v2/person-sarah-oconnor.md | 22 - demo-vault-v2/person-silvia-mancini.md | 20 - demo-vault-v2/person-simone-bianchi.md | 22 - demo-vault-v2/person-sophie-laurent.md | 22 - demo-vault-v2/person-stefano-villa.md | 21 - demo-vault-v2/person-thomas-mueller.md | 22 - demo-vault-v2/person-tom-richardson.md | 22 - demo-vault-v2/person-tommaso-greco.md | 21 - demo-vault-v2/person-valentina-rizzo.md | 23 - demo-vault-v2/person-yuki-sato.md | 22 - demo-vault-v2/person-yusuf-osman.md | 22 - demo-vault-v2/person.md | 7 - .../podcasting-is-relationship-building.md | 31 - .../procedure-biweekly-1on1-matteo.md | 30 - demo-vault-v2/procedure-biweekly-1on1-paco.md | 30 - demo-vault-v2/procedure-biweekly-1on1-sara.md | 30 - .../procedure-content-calendar-review.md | 29 - demo-vault-v2/procedure-editorial-review.md | 30 - .../procedure-evergreen-content-audit.md | 31 - .../procedure-evergreen-note-writing.md | 28 - demo-vault-v2/procedure-gym-routine.md | 29 - demo-vault-v2/procedure-invoice-processing.md | 30 - .../procedure-monthly-health-review.md | 30 - .../procedure-monthly-pillar-planning.md | 30 - .../procedure-monthly-portfolio-review.md | 30 - .../procedure-monthly-sponsor-report.md | 30 - .../procedure-monthly-subscriber-metrics.md | 30 - .../procedure-newsletter-ab-testing.md | 30 - .../procedure-newsletter-metrics-weekly.md | 29 - demo-vault-v2/procedure-podcast-analytics.md | 30 - demo-vault-v2/procedure-podcast-editing.md | 30 - .../procedure-podcast-guest-outreach.md | 30 - demo-vault-v2/procedure-podcast-recording.md | 31 - demo-vault-v2/procedure-podcast-show-notes.md | 30 - .../procedure-quarterly-financial-planning.md | 31 - .../procedure-quarterly-sponsor-outreach.md | 35 +- .../procedure-quarterly-team-retro.md | 31 - demo-vault-v2/procedure-race-preparation.md | 30 - demo-vault-v2/procedure-referral-program.md | 29 - .../procedure-seo-content-optimization.md | 30 - .../procedure-social-media-scheduling.md | 29 - demo-vault-v2/procedure-sponsor-onboarding.md | 35 +- demo-vault-v2/procedure-sponsor-renewal.md | 31 - .../procedure-weekly-cycling-block.md | 30 - demo-vault-v2/procedure-weekly-newsletter.md | 31 - .../procedure-weekly-reading-session.md | 29 - demo-vault-v2/procedure-weekly-team-sync.md | 30 - .../procedure-welcome-email-sequence.md | 30 - demo-vault-v2/procedure.md | 7 - demo-vault-v2/project.md | 7 - demo-vault-v2/quarter.md | 7 - .../reading-more-by-reading-better.md | 33 - demo-vault-v2/recovery-week-in-training.md | 28 - demo-vault-v2/refactoring-ideas.md | 6 - demo-vault-v2/refactoring-key-ideas.md | 6 - demo-vault-v2/refactoring-patterns.md | 6 - demo-vault-v2/refactoring.md | 7 - demo-vault-v2/renamed-title-xyz.md | 4 - .../responsibility-content-production.md | 42 -- .../responsibility-grow-newsletter.md | 37 -- .../responsibility-health-fitness.md | 38 -- demo-vault-v2/responsibility-learning.md | 36 -- .../responsibility-personal-finance.md | 37 -- demo-vault-v2/responsibility-podcast.md | 39 -- demo-vault-v2/responsibility-sponsorships.md | 48 +- .../responsibility-team-management.md | 39 -- demo-vault-v2/responsibility.md | 7 - .../responsive-rename-test-renamed.md | 7 - demo-vault-v2/save-no-rename-test.md | 6 - demo-vault-v2/should-be-r-renamed.md | 8 - .../sleeping-more-is-a-superpower.md | 28 - .../small-teams-scale-through-systems.md | 28 - demo-vault-v2/target-books-24q1.md | 25 - demo-vault-v2/target-books-24q2.md | 25 - demo-vault-v2/target-books-24q3.md | 25 - demo-vault-v2/target-books-24q4.md | 25 - demo-vault-v2/target-books-25q1.md | 25 - demo-vault-v2/target-books-25q2.md | 25 - demo-vault-v2/target-books-25q3.md | 25 - demo-vault-v2/target-books-25q4.md | 25 - demo-vault-v2/target-resting-hr-24q1.md | 25 - demo-vault-v2/target-resting-hr-24q2.md | 25 - demo-vault-v2/target-resting-hr-24q3.md | 25 - demo-vault-v2/target-resting-hr-24q4.md | 25 - demo-vault-v2/target-resting-hr-25q1.md | 25 - demo-vault-v2/target-resting-hr-25q2.md | 25 - demo-vault-v2/target-resting-hr-25q3.md | 25 - demo-vault-v2/target-resting-hr-25q4.md | 25 - demo-vault-v2/target-revenue-24q1.md | 25 - demo-vault-v2/target-revenue-24q2.md | 25 - demo-vault-v2/target-revenue-24q3.md | 25 - demo-vault-v2/target-revenue-24q4.md | 25 - demo-vault-v2/target-revenue-25q1.md | 25 - demo-vault-v2/target-revenue-25q2.md | 25 - demo-vault-v2/target-revenue-25q3.md | 25 - demo-vault-v2/target-revenue-25q4.md | 25 - demo-vault-v2/target-subscribers-24q1.md | 25 - demo-vault-v2/target-subscribers-24q2.md | 25 - demo-vault-v2/target-subscribers-24q3.md | 25 - demo-vault-v2/target-subscribers-24q4.md | 25 - demo-vault-v2/target-subscribers-25q1.md | 25 - demo-vault-v2/target-subscribers-25q2.md | 25 - demo-vault-v2/target-subscribers-25q3.md | 25 - demo-vault-v2/target-subscribers-25q4.md | 25 - demo-vault-v2/target.md | 7 - demo-vault-v2/task-24q1-01.md | 26 - demo-vault-v2/task-24q1-02.md | 26 - demo-vault-v2/task-24q1-03.md | 26 - demo-vault-v2/task-24q2-04.md | 26 - demo-vault-v2/task-24q2-05.md | 26 - demo-vault-v2/task-24q2-06.md | 26 - demo-vault-v2/task-24q2-07.md | 26 - demo-vault-v2/task-24q3-08.md | 26 - demo-vault-v2/task-24q3-09.md | 26 - demo-vault-v2/task-24q3-10.md | 26 - demo-vault-v2/task-24q3-11.md | 26 - demo-vault-v2/task-24q4-12.md | 26 - demo-vault-v2/task-24q4-13.md | 26 - demo-vault-v2/task-24q4-14.md | 26 - demo-vault-v2/task-24q4-15.md | 26 - demo-vault-v2/task-24q4-16.md | 26 - demo-vault-v2/task-25q1-17.md | 26 - demo-vault-v2/task-25q1-18.md | 26 - demo-vault-v2/task-25q1-19.md | 26 - demo-vault-v2/task-25q1-20.md | 26 - demo-vault-v2/task-25q1-21.md | 26 - demo-vault-v2/task-25q1-22.md | 26 - demo-vault-v2/task-25q1-23.md | 26 - demo-vault-v2/task-25q2-24.md | 26 - demo-vault-v2/task-25q2-25.md | 26 - demo-vault-v2/task-25q2-26.md | 26 - demo-vault-v2/task-25q2-27.md | 26 - demo-vault-v2/task-25q2-28.md | 26 - demo-vault-v2/task-25q2-29.md | 26 - demo-vault-v2/task-25q3-30.md | 26 - demo-vault-v2/task-25q3-31.md | 26 - demo-vault-v2/task-25q3-32.md | 26 - demo-vault-v2/task-25q3-33.md | 26 - demo-vault-v2/task-25q3-34.md | 26 - demo-vault-v2/task-25q3-35.md | 26 - demo-vault-v2/task-25q4-36.md | 26 - demo-vault-v2/task-25q4-37.md | 26 - demo-vault-v2/task-25q4-38.md | 26 - demo-vault-v2/task-25q4-39.md | 26 - demo-vault-v2/task-25q4-40.md | 26 - demo-vault-v2/task-25q4-41.md | 26 - demo-vault-v2/task-25q4-42.md | 26 - demo-vault-v2/task-25q4-43.md | 26 - demo-vault-v2/task-25q4-44.md | 26 - demo-vault-v2/task-25q4-45.md | 26 - demo-vault-v2/task.md | 7 - demo-vault-v2/test-note-a.md | 8 - demo-vault-v2/test-note-abc.md | 4 - .../the-compound-effect-in-knowledge-work.md | 28 - demo-vault-v2/the-real-job-of-a-newsletter.md | 28 - demo-vault-v2/the-saas-metric-that-matters.md | 28 - demo-vault-v2/the-sponsorship-relationship.md | 28 - demo-vault-v2/the-two-types-of-hard.md | 28 - demo-vault-v2/theme/dark.md | 54 -- demo-vault-v2/theme/default-theme.md | 20 - demo-vault-v2/theme/default.md | 54 -- demo-vault-v2/theme/minimal.md | 53 -- demo-vault-v2/topic-ai-ml.md | 27 - demo-vault-v2/topic-b2b-marketing.md | 27 - demo-vault-v2/topic-content-strategy.md | 27 - demo-vault-v2/topic-cooking.md | 27 - demo-vault-v2/topic-cycling-training.md | 27 - demo-vault-v2/topic-data-engineering.md | 27 - demo-vault-v2/topic-developer-tools.md | 27 - demo-vault-v2/topic-italian-startups.md | 27 - demo-vault-v2/topic-mental-health.md | 27 - demo-vault-v2/topic-music-guitar.md | 27 - demo-vault-v2/topic-newsletter-growth.md | 27 - demo-vault-v2/topic-nutrition.md | 27 - demo-vault-v2/topic-open-source.md | 27 - demo-vault-v2/topic-personal-finance.md | 27 - demo-vault-v2/topic-podcasting.md | 27 - demo-vault-v2/topic-product-management.md | 27 - demo-vault-v2/topic-productivity-systems.md | 27 - demo-vault-v2/topic-public-speaking.md | 27 - demo-vault-v2/topic-reading-books.md | 27 - demo-vault-v2/topic-running.md | 27 - demo-vault-v2/topic-saas-business.md | 27 - demo-vault-v2/topic-sleep-recovery.md | 27 - demo-vault-v2/topic-team-leadership.md | 27 - demo-vault-v2/topic-travel.md | 27 - demo-vault-v2/topic-writing.md | 30 +- demo-vault-v2/topic.md | 7 - .../training-load-and-knowledge-work.md | 30 - demo-vault-v2/type/area.md | 8 +- demo-vault-v2/type/event.md | 8 +- demo-vault-v2/type/evergreen.md | 7 - demo-vault-v2/type/experiment.md | 7 - demo-vault-v2/type/goal.md | 7 - demo-vault-v2/type/measure.md | 8 +- demo-vault-v2/type/month.md | 7 - demo-vault-v2/type/note.md | 8 +- demo-vault-v2/type/person.md | 8 +- demo-vault-v2/type/procedure.md | 8 +- demo-vault-v2/type/project.md | 8 +- demo-vault-v2/type/quarter.md | 8 +- demo-vault-v2/type/responsibility.md | 8 +- demo-vault-v2/type/target.md | 7 - demo-vault-v2/type/task.md | 7 - demo-vault-v2/type/topic.md | 8 +- demo-vault-v2/type/year.md | 7 - demo-vault-v2/untitled-area-10.md | 8 - demo-vault-v2/untitled-area-11.md | 8 - demo-vault-v2/untitled-area-12.md | 10 - demo-vault-v2/untitled-area-13.md | 8 - demo-vault-v2/untitled-area-14.md | 8 - demo-vault-v2/untitled-area-15.md | 8 - demo-vault-v2/untitled-area-16.md | 8 - demo-vault-v2/untitled-area-17.md | 8 - demo-vault-v2/untitled-area-18.md | 8 - demo-vault-v2/untitled-area-2.md | 6 - demo-vault-v2/untitled-area-3.md | 8 - demo-vault-v2/untitled-area-4.md | 8 - demo-vault-v2/untitled-area-5.md | 8 - demo-vault-v2/untitled-area-6.md | 8 - demo-vault-v2/untitled-area-7.md | 8 - demo-vault-v2/untitled-area-8.md | 8 - demo-vault-v2/untitled-area-9.md | 8 - demo-vault-v2/untitled-area.md | 8 - ...career-tracks-depend-on-company-shape-2.md | 6 - demo-vault-v2/untitled-experiment-2.md | 14 - demo-vault-v2/untitled-experiment.md | 16 - demo-vault-v2/untitled-not.md | 8 - demo-vault-v2/untitled-note-10.md | 8 - demo-vault-v2/untitled-note-100-md-renamed.md | 11 - demo-vault-v2/untitled-note-101.md | 10 - demo-vault-v2/untitled-note-102.md | 8 - demo-vault-v2/untitled-note-103.md | 8 - demo-vault-v2/untitled-note-104.md | 6 - demo-vault-v2/untitled-note-105-md-renamed.md | 11 - demo-vault-v2/untitled-note-106.md | 10 - demo-vault-v2/untitled-note-107.md | 8 - demo-vault-v2/untitled-note-108.md | 8 - demo-vault-v2/untitled-note-109.md | 6 - demo-vault-v2/untitled-note-11.md | 8 - demo-vault-v2/untitled-note-110-md-renamed.md | 11 - demo-vault-v2/untitled-note-111.md | 8 - demo-vault-v2/untitled-note-112.md | 8 - demo-vault-v2/untitled-note-113.md | 8 - demo-vault-v2/untitled-note-114.md | 6 - demo-vault-v2/untitled-note-115-md-renamed.md | 11 - demo-vault-v2/untitled-note-116.md | 8 - demo-vault-v2/untitled-note-117.md | 5 - demo-vault-v2/untitled-note-118.md | 5 - demo-vault-v2/untitled-note-119.md | 5 - demo-vault-v2/untitled-note-12.md | 8 - demo-vault-v2/untitled-note-120.md | 6 - demo-vault-v2/untitled-note-121-md-renamed.md | 8 - demo-vault-v2/untitled-note-122.md | 8 - demo-vault-v2/untitled-note-123.md | 5 - demo-vault-v2/untitled-note-124.md | 5 - demo-vault-v2/untitled-note-125.md | 5 - demo-vault-v2/untitled-note-126.md | 6 - demo-vault-v2/untitled-note-127-md-renamed.md | 8 - demo-vault-v2/untitled-note-128.md | 8 - demo-vault-v2/untitled-note-129.md | 5 - demo-vault-v2/untitled-note-13.md | 6 - demo-vault-v2/untitled-note-130.md | 5 - demo-vault-v2/untitled-note-131.md | 6 - demo-vault-v2/untitled-note-132-md-renamed.md | 8 - demo-vault-v2/untitled-note-133.md | 8 - demo-vault-v2/untitled-note-134.md | 5 - demo-vault-v2/untitled-note-135.md | 5 - demo-vault-v2/untitled-note-136.md | 6 - demo-vault-v2/untitled-note-137-md-renamed.md | 8 - demo-vault-v2/untitled-note-138.md | 8 - demo-vault-v2/untitled-note-139.md | 5 - demo-vault-v2/untitled-note-14.md | 6 - demo-vault-v2/untitled-note-140.md | 5 - demo-vault-v2/untitled-note-141.md | 6 - demo-vault-v2/untitled-note-142-md-renamed.md | 8 - demo-vault-v2/untitled-note-143.md | 8 - demo-vault-v2/untitled-note-144.md | 5 - demo-vault-v2/untitled-note-145.md | 5 - demo-vault-v2/untitled-note-146.md | 5 - demo-vault-v2/untitled-note-147.md | 6 - demo-vault-v2/untitled-note-148-md-renamed.md | 8 - demo-vault-v2/untitled-note-149.md | 8 - demo-vault-v2/untitled-note-15-md-renamed.md | 11 - demo-vault-v2/untitled-note-150.md | 5 - demo-vault-v2/untitled-note-151.md | 5 - demo-vault-v2/untitled-note-152.md | 6 - demo-vault-v2/untitled-note-153-md-renamed.md | 8 - demo-vault-v2/untitled-note-154.md | 8 - demo-vault-v2/untitled-note-155.md | 5 - demo-vault-v2/untitled-note-156.md | 5 - demo-vault-v2/untitled-note-157.md | 6 - demo-vault-v2/untitled-note-158-md-renamed.md | 8 - demo-vault-v2/untitled-note-159.md | 8 - demo-vault-v2/untitled-note-16.md | 8 - demo-vault-v2/untitled-note-160.md | 5 - demo-vault-v2/untitled-note-161.md | 5 - demo-vault-v2/untitled-note-162.md | 6 - demo-vault-v2/untitled-note-163-md-renamed.md | 8 - demo-vault-v2/untitled-note-164.md | 8 - demo-vault-v2/untitled-note-165.md | 5 - demo-vault-v2/untitled-note-166.md | 5 - demo-vault-v2/untitled-note-167.md | 6 - demo-vault-v2/untitled-note-168-md-renamed.md | 8 - demo-vault-v2/untitled-note-169.md | 8 - demo-vault-v2/untitled-note-17.md | 8 - demo-vault-v2/untitled-note-170.md | 5 - demo-vault-v2/untitled-note-171.md | 5 - demo-vault-v2/untitled-note-172.md | 6 - demo-vault-v2/untitled-note-173-md-renamed.md | 8 - demo-vault-v2/untitled-note-174.md | 8 - demo-vault-v2/untitled-note-175.md | 5 - demo-vault-v2/untitled-note-176.md | 5 - demo-vault-v2/untitled-note-177.md | 6 - demo-vault-v2/untitled-note-1775473305.md | 4 - demo-vault-v2/untitled-note-1775473680.md | 5 - demo-vault-v2/untitled-note-1775473969.md | 7 - demo-vault-v2/untitled-note-1775496473.md | 4 - demo-vault-v2/untitled-note-1775496825.md | 5 - demo-vault-v2/untitled-note-1775497099.md | 7 - demo-vault-v2/untitled-note-1775541952.md | 4 - demo-vault-v2/untitled-note-1775542285.md | 4 - demo-vault-v2/untitled-note-1775542291.md | 4 - demo-vault-v2/untitled-note-1775542296.md | 4 - demo-vault-v2/untitled-note-1775542431.md | 4 - demo-vault-v2/untitled-note-1775542439.md | 4 - demo-vault-v2/untitled-note-1775542446.md | 4 - demo-vault-v2/untitled-note-1775542459.md | 4 - demo-vault-v2/untitled-note-1775542467.md | 4 - demo-vault-v2/untitled-note-1775542474.md | 4 - demo-vault-v2/untitled-note-1775542676.md | 4 - demo-vault-v2/untitled-note-1775542684.md | 4 - demo-vault-v2/untitled-note-1775542692.md | 4 - demo-vault-v2/untitled-note-1775542700.md | 4 - demo-vault-v2/untitled-note-1775542708.md | 4 - .../untitled-note-1775542716-renamed.md | 7 - demo-vault-v2/untitled-note-1775542923.md | 4 - demo-vault-v2/untitled-note-1775542931.md | 4 - demo-vault-v2/untitled-note-1775542938.md | 4 - demo-vault-v2/untitled-note-1775542951.md | 4 - demo-vault-v2/untitled-note-1775542959.md | 4 - demo-vault-v2/untitled-note-1775542967.md | 4 - demo-vault-v2/untitled-note-1775542981.md | 7 - demo-vault-v2/untitled-note-178-md-renamed.md | 8 - demo-vault-v2/untitled-note-179.md | 8 - demo-vault-v2/untitled-note-18.md | 8 - demo-vault-v2/untitled-note-180.md | 5 - demo-vault-v2/untitled-note-181.md | 5 - demo-vault-v2/untitled-note-182.md | 6 - demo-vault-v2/untitled-note-183-md-renamed.md | 8 - demo-vault-v2/untitled-note-184.md | 8 - demo-vault-v2/untitled-note-185.md | 5 - demo-vault-v2/untitled-note-186.md | 5 - demo-vault-v2/untitled-note-187.md | 5 - demo-vault-v2/untitled-note-188.md | 6 - demo-vault-v2/untitled-note-189-md-renamed.md | 8 - demo-vault-v2/untitled-note-19.md | 8 - demo-vault-v2/untitled-note-190.md | 8 - demo-vault-v2/untitled-note-191.md | 5 - demo-vault-v2/untitled-note-192.md | 5 - demo-vault-v2/untitled-note-193.md | 5 - demo-vault-v2/untitled-note-194.md | 6 - ...ed-note-195untitled-note-195-md-renamed.md | 8 - demo-vault-v2/untitled-note-196.md | 8 - demo-vault-v2/untitled-note-197.md | 5 - demo-vault-v2/untitled-note-198.md | 5 - demo-vault-v2/untitled-note-199.md | 6 - demo-vault-v2/untitled-note-2.md | 10 - demo-vault-v2/untitled-note-20.md | 8 - ...ed-note-200untitled-note-200-md-renamed.md | 8 - demo-vault-v2/untitled-note-201.md | 8 - demo-vault-v2/untitled-note-202.md | 5 - demo-vault-v2/untitled-note-203.md | 5 - demo-vault-v2/untitled-note-204.md | 6 - ...ed-note-205untitled-note-205-md-renamed.md | 8 - demo-vault-v2/untitled-note-206.md | 8 - demo-vault-v2/untitled-note-207.md | 5 - demo-vault-v2/untitled-note-208.md | 5 - demo-vault-v2/untitled-note-209.md | 6 - demo-vault-v2/untitled-note-21.md | 6 - ...ed-note-210untitled-note-210-md-renamed.md | 8 - demo-vault-v2/untitled-note-211.md | 8 - demo-vault-v2/untitled-note-212.md | 5 - demo-vault-v2/untitled-note-213.md | 5 - demo-vault-v2/untitled-note-214.md | 6 - demo-vault-v2/untitled-note-215-renamed.md | 8 - demo-vault-v2/untitled-note-216.md | 8 - demo-vault-v2/untitled-note-217.md | 5 - demo-vault-v2/untitled-note-218.md | 5 - demo-vault-v2/untitled-note-219.md | 6 - demo-vault-v2/untitled-note-22-md-renamed.md | 11 - demo-vault-v2/untitled-note-220-renamed.md | 8 - demo-vault-v2/untitled-note-221.md | 8 - demo-vault-v2/untitled-note-222.md | 5 - demo-vault-v2/untitled-note-223.md | 5 - demo-vault-v2/untitled-note-224.md | 5 - demo-vault-v2/untitled-note-225.md | 6 - demo-vault-v2/untitled-note-226-renamed.md | 8 - demo-vault-v2/untitled-note-227.md | 8 - demo-vault-v2/untitled-note-228.md | 5 - demo-vault-v2/untitled-note-229.md | 5 - demo-vault-v2/untitled-note-23.md | 8 - demo-vault-v2/untitled-note-230.md | 6 - demo-vault-v2/untitled-note-231-renamed.md | 8 - demo-vault-v2/untitled-note-232.md | 8 - demo-vault-v2/untitled-note-233.md | 5 - demo-vault-v2/untitled-note-234.md | 5 - demo-vault-v2/untitled-note-235.md | 6 - demo-vault-v2/untitled-note-236-renamed.md | 8 - demo-vault-v2/untitled-note-237.md | 8 - demo-vault-v2/untitled-note-238.md | 5 - demo-vault-v2/untitled-note-239.md | 5 - demo-vault-v2/untitled-note-24.md | 8 - demo-vault-v2/untitled-note-240.md | 6 - demo-vault-v2/untitled-note-241-renamed.md | 8 - demo-vault-v2/untitled-note-242.md | 8 - demo-vault-v2/untitled-note-243.md | 5 - demo-vault-v2/untitled-note-244.md | 5 - demo-vault-v2/untitled-note-245.md | 5 - demo-vault-v2/untitled-note-246-renamed.md | 8 - demo-vault-v2/untitled-note-247.md | 8 - demo-vault-v2/untitled-note-248.md | 5 - demo-vault-v2/untitled-note-249.md | 5 - demo-vault-v2/untitled-note-25.md | 6 - demo-vault-v2/untitled-note-250.md | 5 - demo-vault-v2/untitled-note-251.md | 5 - demo-vault-v2/untitled-note-252.md | 5 - demo-vault-v2/untitled-note-253.md | 6 - demo-vault-v2/untitled-note-254-renamed.md | 8 - demo-vault-v2/untitled-note-255.md | 5 - demo-vault-v2/untitled-note-256.md | 5 - demo-vault-v2/untitled-note-257.md | 5 - demo-vault-v2/untitled-note-258.md | 6 - demo-vault-v2/untitled-note-259.md | 6 - demo-vault-v2/untitled-note-26-md-renamed.md | 11 - demo-vault-v2/untitled-note-260-renamed.md | 8 - demo-vault-v2/untitled-note-261.md | 8 - demo-vault-v2/untitled-note-262.md | 5 - demo-vault-v2/untitled-note-263.md | 5 - demo-vault-v2/untitled-note-264.md | 5 - demo-vault-v2/untitled-note-265.md | 6 - demo-vault-v2/untitled-note-266-renamed.md | 8 - demo-vault-v2/untitled-note-267.md | 8 - demo-vault-v2/untitled-note-268.md | 5 - demo-vault-v2/untitled-note-269.md | 5 - demo-vault-v2/untitled-note-27.md | 8 - demo-vault-v2/untitled-note-270.md | 6 - demo-vault-v2/untitled-note-271-renamed.md | 8 - demo-vault-v2/untitled-note-272.md | 8 - demo-vault-v2/untitled-note-273.md | 5 - demo-vault-v2/untitled-note-274.md | 5 - demo-vault-v2/untitled-note-275.md | 5 - demo-vault-v2/untitled-note-276.md | 6 - demo-vault-v2/untitled-note-277.md | 8 - demo-vault-v2/untitled-note-278.md | 5 - demo-vault-v2/untitled-note-279.md | 5 - demo-vault-v2/untitled-note-28.md | 8 - demo-vault-v2/untitled-note-280.md | 6 - demo-vault-v2/untitled-note-281-renamed.md | 8 - demo-vault-v2/untitled-note-282.md | 5 - demo-vault-v2/untitled-note-283.md | 5 - demo-vault-v2/untitled-note-284.md | 6 - demo-vault-v2/untitled-note-285-renamed.md | 8 - demo-vault-v2/untitled-note-286.md | 8 - demo-vault-v2/untitled-note-287.md | 5 - demo-vault-v2/untitled-note-288.md | 5 - demo-vault-v2/untitled-note-289.md | 6 - demo-vault-v2/untitled-note-29.md | 6 - demo-vault-v2/untitled-note-290-renamed.md | 8 - demo-vault-v2/untitled-note-291.md | 8 - demo-vault-v2/untitled-note-292.md | 5 - demo-vault-v2/untitled-note-293.md | 5 - demo-vault-v2/untitled-note-294.md | 5 - demo-vault-v2/untitled-note-295.md | 6 - demo-vault-v2/untitled-note-296-renamed.md | 8 - demo-vault-v2/untitled-note-297.md | 8 - demo-vault-v2/untitled-note-298.md | 5 - demo-vault-v2/untitled-note-299.md | 5 - demo-vault-v2/untitled-note-3.md | 10 - demo-vault-v2/untitled-note-30-md-renamed.md | 11 - demo-vault-v2/untitled-note-300.md | 6 - demo-vault-v2/untitled-note-301-renamed.md | 8 - demo-vault-v2/untitled-note-302.md | 8 - demo-vault-v2/untitled-note-303.md | 5 - demo-vault-v2/untitled-note-304.md | 5 - demo-vault-v2/untitled-note-305.md | 6 - demo-vault-v2/untitled-note-306-renamed.md | 8 - demo-vault-v2/untitled-note-307.md | 8 - demo-vault-v2/untitled-note-308.md | 5 - demo-vault-v2/untitled-note-309.md | 5 - demo-vault-v2/untitled-note-31.md | 8 - demo-vault-v2/untitled-note-310.md | 5 - demo-vault-v2/untitled-note-311-renamed.md | 8 - demo-vault-v2/untitled-note-312.md | 8 - demo-vault-v2/untitled-note-313.md | 5 - demo-vault-v2/untitled-note-314.md | 5 - demo-vault-v2/untitled-note-315.md | 5 - demo-vault-v2/untitled-note-316.md | 6 - demo-vault-v2/untitled-note-317.md | 5 - demo-vault-v2/untitled-note-318.md | 6 - demo-vault-v2/untitled-note-319-renamed.md | 6 - demo-vault-v2/untitled-note-32.md | 8 - demo-vault-v2/untitled-note-320.md | 5 - demo-vault-v2/untitled-note-321.md | 5 - demo-vault-v2/untitled-note-322.md | 6 - demo-vault-v2/untitled-note-323-renamed.md | 8 - demo-vault-v2/untitled-note-324.md | 8 - demo-vault-v2/untitled-note-325.md | 5 - demo-vault-v2/untitled-note-326.md | 5 - demo-vault-v2/untitled-note-327.md | 6 - demo-vault-v2/untitled-note-328-renamed.md | 8 - demo-vault-v2/untitled-note-329.md | 5 - demo-vault-v2/untitled-note-33.md | 6 - demo-vault-v2/untitled-note-330.md | 5 - demo-vault-v2/untitled-note-331.md | 6 - demo-vault-v2/untitled-note-332.md | 5 - demo-vault-v2/untitled-note-333-renamed.md | 8 - demo-vault-v2/untitled-note-334-renamed.md | 8 - demo-vault-v2/untitled-note-335.md | 5 - demo-vault-v2/untitled-note-336.md | 5 - demo-vault-v2/untitled-note-337.md | 5 - demo-vault-v2/untitled-note-338-renamed.md | 6 - demo-vault-v2/untitled-note-339.md | 5 - demo-vault-v2/untitled-note-34-md-renamed.md | 11 - demo-vault-v2/untitled-note-340.md | 5 - demo-vault-v2/untitled-note-341.md | 6 - demo-vault-v2/untitled-note-342.md | 6 - demo-vault-v2/untitled-note-343.md | 8 - demo-vault-v2/untitled-note-344-renamed.md | 6 - demo-vault-v2/untitled-note-346.md | 5 - demo-vault-v2/untitled-note-347.md | 5 - demo-vault-v2/untitled-note-348.md | 5 - demo-vault-v2/untitled-note-349.md | 6 - demo-vault-v2/untitled-note-35.md | 8 - demo-vault-v2/untitled-note-350.md | 5 - demo-vault-v2/untitled-note-351.md | 5 - demo-vault-v2/untitled-note-352.md | 6 - demo-vault-v2/untitled-note-353-renamed.md | 8 - demo-vault-v2/untitled-note-354.md | 8 - demo-vault-v2/untitled-note-355.md | 5 - demo-vault-v2/untitled-note-356.md | 5 - demo-vault-v2/untitled-note-357.md | 5 - demo-vault-v2/untitled-note-359-renamed.md | 8 - demo-vault-v2/untitled-note-36.md | 8 - demo-vault-v2/untitled-note-361.md | 5 - demo-vault-v2/untitled-note-37.md | 6 - demo-vault-v2/untitled-note-38-md-renamed.md | 11 - demo-vault-v2/untitled-note-39.md | 8 - demo-vault-v2/untitled-note-40.md | 8 - demo-vault-v2/untitled-note-41.md | 8 - demo-vault-v2/untitled-note-42.md | 6 - demo-vault-v2/untitled-note-43-md-renamed.md | 11 - demo-vault-v2/untitled-note-44.md | 8 - demo-vault-v2/untitled-note-45.md | 8 - demo-vault-v2/untitled-note-46.md | 6 - demo-vault-v2/untitled-note-47-md-renamed.md | 11 - demo-vault-v2/untitled-note-48.md | 8 - demo-vault-v2/untitled-note-49.md | 8 - demo-vault-v2/untitled-note-5.md | 8 - demo-vault-v2/untitled-note-50.md | 6 - demo-vault-v2/untitled-note-51-md-renamed.md | 11 - demo-vault-v2/untitled-note-52.md | 8 - demo-vault-v2/untitled-note-53.md | 8 - demo-vault-v2/untitled-note-54.md | 8 - demo-vault-v2/untitled-note-55.md | 6 - demo-vault-v2/untitled-note-56-md-renamed.md | 11 - demo-vault-v2/untitled-note-57.md | 10 - demo-vault-v2/untitled-note-58.md | 8 - demo-vault-v2/untitled-note-59.md | 6 - demo-vault-v2/untitled-note-6.md | 10 - demo-vault-v2/untitled-note-60-md-renamed.md | 11 - demo-vault-v2/untitled-note-61.md | 10 - demo-vault-v2/untitled-note-62.md | 8 - demo-vault-v2/untitled-note-63.md | 8 - demo-vault-v2/untitled-note-64.md | 8 - demo-vault-v2/untitled-note-65.md | 8 - demo-vault-v2/untitled-note-66.md | 8 - demo-vault-v2/untitled-note-67.md | 6 - demo-vault-v2/untitled-note-68-md-renamed.md | 11 - demo-vault-v2/untitled-note-69.md | 8 - demo-vault-v2/untitled-note-7.md | 8 - demo-vault-v2/untitled-note-70.md | 6 - demo-vault-v2/untitled-note-71.md | 8 - demo-vault-v2/untitled-note-72.md | 8 - demo-vault-v2/untitled-note-73.md | 8 - demo-vault-v2/untitled-note-74-md-renamed.md | 11 - demo-vault-v2/untitled-note-75.md | 10 - demo-vault-v2/untitled-note-76.md | 8 - demo-vault-v2/untitled-note-77.md | 8 - demo-vault-v2/untitled-note-78.md | 8 - demo-vault-v2/untitled-note-79.md | 6 - demo-vault-v2/untitled-note-8.md | 8 - demo-vault-v2/untitled-note-80.md | 6 - demo-vault-v2/untitled-note-81.md | 10 - demo-vault-v2/untitled-note-82.md | 6 - demo-vault-v2/untitled-note-83-md-renamed.md | 13 - demo-vault-v2/untitled-note-84.md | 8 - demo-vault-v2/untitled-note-85.md | 8 - demo-vault-v2/untitled-note-86.md | 6 - demo-vault-v2/untitled-note-87-md-renamed.md | 11 - demo-vault-v2/untitled-note-88.md | 10 - demo-vault-v2/untitled-note-89.md | 8 - demo-vault-v2/untitled-note-9.md | 8 - demo-vault-v2/untitled-note-90.md | 8 - demo-vault-v2/untitled-note-91.md | 6 - demo-vault-v2/untitled-note-92-md-renamed.md | 11 - demo-vault-v2/untitled-note-93.md | 10 - demo-vault-v2/untitled-note-94.md | 8 - demo-vault-v2/untitled-note-95.md | 8 - demo-vault-v2/untitled-note-96.md | 6 - demo-vault-v2/untitled-note-97.md | 8 - demo-vault-v2/untitled-note-98.md | 8 - demo-vault-v2/untitled-note-99.md | 6 - demo-vault-v2/untitled-note.md | 5 - demo-vault-v2/untitled-project-10.md | 18 - demo-vault-v2/untitled-project-11.md | 18 - demo-vault-v2/untitled-project-12.md | 18 - demo-vault-v2/untitled-project-13.md | 18 - demo-vault-v2/untitled-project-14.md | 18 - demo-vault-v2/untitled-project-15.md | 18 - demo-vault-v2/untitled-project-16.md | 18 - demo-vault-v2/untitled-project-17.md | 18 - demo-vault-v2/untitled-project-1775473964.md | 15 - demo-vault-v2/untitled-project-1775497094.md | 15 - demo-vault-v2/untitled-project-1775542975.md | 15 - demo-vault-v2/untitled-project-18.md | 18 - demo-vault-v2/untitled-project-19.md | 16 - demo-vault-v2/untitled-project-2.md | 18 - demo-vault-v2/untitled-project-20.md | 16 - demo-vault-v2/untitled-project-21.md | 16 - demo-vault-v2/untitled-project-22.md | 16 - demo-vault-v2/untitled-project-23.md | 16 - demo-vault-v2/untitled-project-24.md | 16 - demo-vault-v2/untitled-project-25.md | 16 - demo-vault-v2/untitled-project-26.md | 16 - demo-vault-v2/untitled-project-27.md | 16 - demo-vault-v2/untitled-project-28.md | 16 - demo-vault-v2/untitled-project-29.md | 16 - demo-vault-v2/untitled-project-3.md | 18 - demo-vault-v2/untitled-project-30.md | 16 - demo-vault-v2/untitled-project-31.md | 16 - demo-vault-v2/untitled-project-32.md | 16 - demo-vault-v2/untitled-project-33.md | 16 - demo-vault-v2/untitled-project-34.md | 16 - demo-vault-v2/untitled-project-35.md | 16 - demo-vault-v2/untitled-project-36.md | 16 - demo-vault-v2/untitled-project-37.md | 16 - demo-vault-v2/untitled-project-38.md | 16 - demo-vault-v2/untitled-project-39.md | 16 - demo-vault-v2/untitled-project-4.md | 18 - demo-vault-v2/untitled-project-40.md | 16 - demo-vault-v2/untitled-project-41.md | 16 - demo-vault-v2/untitled-project-42.md | 16 - demo-vault-v2/untitled-project-43.md | 16 - demo-vault-v2/untitled-project-44.md | 16 - demo-vault-v2/untitled-project-45.md | 16 - demo-vault-v2/untitled-project-46.md | 16 - demo-vault-v2/untitled-project-47.md | 16 - demo-vault-v2/untitled-project-48.md | 16 - demo-vault-v2/untitled-project-49.md | 16 - demo-vault-v2/untitled-project-5.md | 18 - demo-vault-v2/untitled-project-50.md | 16 - demo-vault-v2/untitled-project-51.md | 16 - demo-vault-v2/untitled-project-52.md | 16 - demo-vault-v2/untitled-project-53.md | 16 - demo-vault-v2/untitled-project-54.md | 16 - demo-vault-v2/untitled-project-55.md | 16 - demo-vault-v2/untitled-project-56.md | 16 - demo-vault-v2/untitled-project-57.md | 16 - demo-vault-v2/untitled-project-58.md | 16 - demo-vault-v2/untitled-project-6.md | 18 - demo-vault-v2/untitled-project-7.md | 18 - demo-vault-v2/untitled-project-8.md | 12 - demo-vault-v2/untitled-project-9.md | 18 - demo-vault-v2/untitled-project.md | 18 - demo-vault-v2/untitled-save-no-rename-test.md | 6 - .../untitled-test-note-abc-2-renamed.md | 6 - demo-vault-v2/untitled-test-note-abc-2.md | 6 - demo-vault-v2/untitled-test-note-abc.md | 6 - .../what-makes-a-good-podcast-guest.md | 28 - demo-vault-v2/why-b2b-newsletters-work.md | 28 - demo-vault-v2/wikilinks-qa-test.md | 5 - ...iting-for-clarity-vs-writing-for-credit.md | 31 +- demo-vault-v2/writing-weekly-rhythm.md | 11 + demo-vault-v2/year.md | 7 - docs/ABSTRACTIONS.md | 2 +- docs/ARCHITECTURE.md | 2 +- docs/GETTING-STARTED.md | 8 +- scripts/generate_demo_vault.py | 612 +++++++++++------- 1604 files changed, 689 insertions(+), 28190 deletions(-) create mode 100644 demo-vault-v2/.fixture-manifest.json delete mode 100644 demo-vault-v2/.laputa/settings.json delete mode 100644 demo-vault-v2/2024-01.md delete mode 100644 demo-vault-v2/2024-02.md delete mode 100644 demo-vault-v2/2024-03.md delete mode 100644 demo-vault-v2/2024-04.md delete mode 100644 demo-vault-v2/2024-05.md delete mode 100644 demo-vault-v2/2024-06.md delete mode 100644 demo-vault-v2/2024-07.md delete mode 100644 demo-vault-v2/2024-08.md delete mode 100644 demo-vault-v2/2024-09.md delete mode 100644 demo-vault-v2/2024-10.md delete mode 100644 demo-vault-v2/2024-11.md delete mode 100644 demo-vault-v2/2024-12.md delete mode 100644 demo-vault-v2/2024-complete-two-gran-fondos.md delete mode 100644 demo-vault-v2/2024-double-revenue.md delete mode 100644 demo-vault-v2/2024-launch-podcast.md delete mode 100644 demo-vault-v2/2024-reach-50k-subscribers.md delete mode 100644 demo-vault-v2/2024-read-24-books.md delete mode 100644 demo-vault-v2/2024.md delete mode 100644 demo-vault-v2/2025-01.md delete mode 100644 demo-vault-v2/2025-02.md delete mode 100644 demo-vault-v2/2025-03.md delete mode 100644 demo-vault-v2/2025-04.md delete mode 100644 demo-vault-v2/2025-05.md delete mode 100644 demo-vault-v2/2025-06.md delete mode 100644 demo-vault-v2/2025-07.md delete mode 100644 demo-vault-v2/2025-08.md delete mode 100644 demo-vault-v2/2025-09.md delete mode 100644 demo-vault-v2/2025-10.md delete mode 100644 demo-vault-v2/2025-11.md delete mode 100644 demo-vault-v2/2025-12.md delete mode 100644 demo-vault-v2/2025-reach-22k-mrr.md delete mode 100644 demo-vault-v2/2025-reach-85k-subscribers.md delete mode 100644 demo-vault-v2/2025-read-20-books.md delete mode 100644 demo-vault-v2/2025-ride-stelvio.md delete mode 100644 demo-vault-v2/2025-ship-laputa.md delete mode 100644 demo-vault-v2/2025.md delete mode 100644 demo-vault-v2/24q1-launch-sponsorship-packages.md delete mode 100644 demo-vault-v2/24q1-plan-cycling-season.md delete mode 100644 demo-vault-v2/24q1-podcast-season-1.md delete mode 100644 demo-vault-v2/24q1-redesign-newsletter-template.md delete mode 100644 demo-vault-v2/24q1-set-investing-framework.md delete mode 100644 demo-vault-v2/24q1.md delete mode 100644 demo-vault-v2/24q2-10-pillar-articles.md delete mode 100644 demo-vault-v2/24q2-build-podcast-landing-page.md delete mode 100644 demo-vault-v2/24q2-hire-editor.md delete mode 100644 demo-vault-v2/24q2-sponsor-crm.md delete mode 100644 demo-vault-v2/24q2-spring-gran-fondo.md delete mode 100644 demo-vault-v2/24q2-stock-screener.md delete mode 100644 demo-vault-v2/24q2-video-format-test.md delete mode 100644 demo-vault-v2/24q2.md delete mode 100644 demo-vault-v2/24q3-codemotion-talk.md delete mode 100644 demo-vault-v2/24q3-morning-journaling.md delete mode 100644 demo-vault-v2/24q3-new-sponsor-verticals.md delete mode 100644 demo-vault-v2/24q3-podcast-season-2.md delete mode 100644 demo-vault-v2/24q3-premium-tier.md delete mode 100644 demo-vault-v2/24q3-summer-reading-sprint.md delete mode 100644 demo-vault-v2/24q3.md delete mode 100644 demo-vault-v2/24q4-annual-review-process.md delete mode 100644 demo-vault-v2/24q4-black-friday-campaign.md delete mode 100644 demo-vault-v2/24q4-cycling-year-review.md delete mode 100644 demo-vault-v2/24q4-linkedin-crossposting.md delete mode 100644 demo-vault-v2/24q4-sponsor-dashboard.md delete mode 100644 demo-vault-v2/25q1-newsletter-seo-sprint.md delete mode 100644 demo-vault-v2/25q1-paid-newsletter-trial.md delete mode 100644 demo-vault-v2/25q1-rate-increase.md delete mode 100644 demo-vault-v2/25q1-referral-program.md delete mode 100644 demo-vault-v2/25q1-strength-program.md delete mode 100644 demo-vault-v2/25q2-dolomites-trip.md delete mode 100644 demo-vault-v2/25q2-podcast-season-3.md delete mode 100644 demo-vault-v2/25q2-reach-70k.md delete mode 100644 demo-vault-v2/25q2-team-retreat.md delete mode 100644 demo-vault-v2/25q3-community-launch.md delete mode 100644 demo-vault-v2/25q3-discord-community-soft.md delete mode 100644 demo-vault-v2/25q3-ebook.md delete mode 100644 demo-vault-v2/25q3-leaddev-london.md delete mode 100644 demo-vault-v2/25q3-peak-training.md delete mode 100644 demo-vault-v2/25q3-podcast-season-4.md delete mode 100644 demo-vault-v2/25q3.md delete mode 100644 demo-vault-v2/25q4-2026-sponsors.md delete mode 100644 demo-vault-v2/25q4-financial-review.md delete mode 100644 demo-vault-v2/25q4-laputa-v3.md delete mode 100644 demo-vault-v2/25q4-reach-85k.md delete mode 100644 demo-vault-v2/25q4-year-review-2025.md delete mode 100644 demo-vault-v2/25q4.md delete mode 100644 demo-vault-v2/_themes/dark.json delete mode 100644 demo-vault-v2/_themes/default.json delete mode 100644 demo-vault-v2/_themes/minimal.json delete mode 100644 demo-vault-v2/_themes/untitled-2.json delete mode 100644 demo-vault-v2/_themes/untitled-3.json delete mode 100644 demo-vault-v2/_themes/untitled-4.json delete mode 100644 demo-vault-v2/_themes/untitled.json delete mode 100644 demo-vault-v2/ai-wont-replace-thinking.md delete mode 100644 demo-vault-v2/area-finance.md delete mode 100644 demo-vault-v2/area-health.md delete mode 100644 demo-vault-v2/area-learning.md delete mode 100644 demo-vault-v2/area-personal.md delete mode 100644 demo-vault-v2/area.md delete mode 100644 demo-vault-v2/attachments/1771694098221-CleanShot_2026-02-21_at_17.12.59_2x.png rename demo-vault-v2/attachments/{1771850902033-Untitled_design__3_.png => laputa-reference.png} (100%) delete mode 100644 demo-vault-v2/b2b-content-is-trust-not-traffic.md delete mode 100644 demo-vault-v2/career-tracks-depend-on-company-shape.md delete mode 100644 demo-vault-v2/cycling-teaches-patience.md delete mode 100644 demo-vault-v2/dark.md delete mode 100644 demo-vault-v2/default-theme.md delete mode 100644 demo-vault-v2/enter-rename-test.md delete mode 100644 demo-vault-v2/event-1on1-matteo-2024-01-10.md delete mode 100644 demo-vault-v2/event-1on1-matteo-2024-01-24.md delete mode 100644 demo-vault-v2/event-1on1-matteo-2024-02-07.md delete mode 100644 demo-vault-v2/event-1on1-matteo-2024-02-21.md delete mode 100644 demo-vault-v2/event-1on1-matteo-2024-03-06.md delete mode 100644 demo-vault-v2/event-1on1-matteo-2024-03-20.md delete mode 100644 demo-vault-v2/event-1on1-matteo-2024-04-03.md delete mode 100644 demo-vault-v2/event-1on1-matteo-2024-04-17.md delete mode 100644 demo-vault-v2/event-1on1-matteo-2024-05-01.md delete mode 100644 demo-vault-v2/event-1on1-matteo-2024-05-15.md delete mode 100644 demo-vault-v2/event-1on1-matteo-2024-05-29.md delete mode 100644 demo-vault-v2/event-1on1-matteo-2024-06-12.md delete mode 100644 demo-vault-v2/event-1on1-matteo-2024-06-26.md delete mode 100644 demo-vault-v2/event-1on1-matteo-2024-07-10.md delete mode 100644 demo-vault-v2/event-1on1-matteo-2024-07-24.md delete mode 100644 demo-vault-v2/event-1on1-matteo-2024-08-07.md delete mode 100644 demo-vault-v2/event-1on1-matteo-2024-08-21.md delete mode 100644 demo-vault-v2/event-1on1-matteo-2024-09-04.md delete mode 100644 demo-vault-v2/event-1on1-matteo-2024-09-18.md delete mode 100644 demo-vault-v2/event-1on1-matteo-2024-10-02.md delete mode 100644 demo-vault-v2/event-1on1-matteo-2024-10-16.md delete mode 100644 demo-vault-v2/event-1on1-matteo-2024-10-30.md delete mode 100644 demo-vault-v2/event-1on1-matteo-2024-11-13.md delete mode 100644 demo-vault-v2/event-1on1-matteo-2024-11-27.md delete mode 100644 demo-vault-v2/event-1on1-matteo-2024-12-11.md delete mode 100644 demo-vault-v2/event-1on1-matteo-2024-12-25.md delete mode 100644 demo-vault-v2/event-1on1-matteo-2025-01-08.md delete mode 100644 demo-vault-v2/event-1on1-matteo-2025-01-22.md delete mode 100644 demo-vault-v2/event-1on1-matteo-2025-02-05.md delete mode 100644 demo-vault-v2/event-1on1-matteo-2025-02-19.md delete mode 100644 demo-vault-v2/event-1on1-matteo-2025-03-05.md delete mode 100644 demo-vault-v2/event-1on1-matteo-2025-03-19.md delete mode 100644 demo-vault-v2/event-1on1-matteo-2025-04-02.md delete mode 100644 demo-vault-v2/event-1on1-matteo-2025-04-16.md delete mode 100644 demo-vault-v2/event-1on1-matteo-2025-04-30.md delete mode 100644 demo-vault-v2/event-1on1-matteo-2025-05-14.md delete mode 100644 demo-vault-v2/event-1on1-matteo-2025-05-28.md delete mode 100644 demo-vault-v2/event-1on1-matteo-2025-06-11.md delete mode 100644 demo-vault-v2/event-1on1-paco-2024-01-04.md delete mode 100644 demo-vault-v2/event-1on1-paco-2024-02-01.md delete mode 100644 demo-vault-v2/event-1on1-paco-2024-03-07.md delete mode 100644 demo-vault-v2/event-1on1-paco-2024-04-04.md delete mode 100644 demo-vault-v2/event-1on1-paco-2024-05-02.md delete mode 100644 demo-vault-v2/event-1on1-paco-2024-06-06.md delete mode 100644 demo-vault-v2/event-1on1-paco-2024-07-04.md delete mode 100644 demo-vault-v2/event-1on1-paco-2024-08-01.md delete mode 100644 demo-vault-v2/event-1on1-paco-2024-09-05.md delete mode 100644 demo-vault-v2/event-1on1-paco-2024-10-03.md delete mode 100644 demo-vault-v2/event-1on1-paco-2024-11-07.md delete mode 100644 demo-vault-v2/event-1on1-paco-2024-12-05.md delete mode 100644 demo-vault-v2/event-1on1-paco-2025-01-02.md delete mode 100644 demo-vault-v2/event-1on1-paco-2025-02-06.md delete mode 100644 demo-vault-v2/event-1on1-paco-2025-03-06.md delete mode 100644 demo-vault-v2/event-1on1-paco-2025-04-03.md delete mode 100644 demo-vault-v2/event-1on1-paco-2025-05-01.md delete mode 100644 demo-vault-v2/event-1on1-paco-2025-06-05.md delete mode 100644 demo-vault-v2/event-cycling-2024-01-02.md delete mode 100644 demo-vault-v2/event-cycling-2024-01-09.md delete mode 100644 demo-vault-v2/event-cycling-2024-01-16.md delete mode 100644 demo-vault-v2/event-cycling-2024-01-23.md delete mode 100644 demo-vault-v2/event-cycling-2024-01-30.md delete mode 100644 demo-vault-v2/event-cycling-2024-02-06.md delete mode 100644 demo-vault-v2/event-cycling-2024-02-13.md delete mode 100644 demo-vault-v2/event-cycling-2024-02-20.md delete mode 100644 demo-vault-v2/event-cycling-2024-02-27.md delete mode 100644 demo-vault-v2/event-cycling-2024-03-05.md delete mode 100644 demo-vault-v2/event-cycling-2024-03-12.md delete mode 100644 demo-vault-v2/event-cycling-2024-03-19.md delete mode 100644 demo-vault-v2/event-cycling-2024-03-26.md delete mode 100644 demo-vault-v2/event-cycling-2024-04-02.md delete mode 100644 demo-vault-v2/event-cycling-2024-04-09.md delete mode 100644 demo-vault-v2/event-cycling-2024-04-16.md delete mode 100644 demo-vault-v2/event-cycling-2024-04-23.md delete mode 100644 demo-vault-v2/event-cycling-2024-04-30.md delete mode 100644 demo-vault-v2/event-cycling-2024-05-07.md delete mode 100644 demo-vault-v2/event-cycling-2024-05-14.md delete mode 100644 demo-vault-v2/event-cycling-2024-05-21.md delete mode 100644 demo-vault-v2/event-cycling-2024-05-28.md delete mode 100644 demo-vault-v2/event-cycling-2024-06-04.md delete mode 100644 demo-vault-v2/event-cycling-2024-06-11.md delete mode 100644 demo-vault-v2/event-cycling-2024-06-18.md delete mode 100644 demo-vault-v2/event-cycling-2024-06-25.md delete mode 100644 demo-vault-v2/event-cycling-2024-07-02.md delete mode 100644 demo-vault-v2/event-cycling-2024-07-09.md delete mode 100644 demo-vault-v2/event-cycling-2024-07-16.md delete mode 100644 demo-vault-v2/event-cycling-2024-07-23.md delete mode 100644 demo-vault-v2/event-cycling-2024-07-30.md delete mode 100644 demo-vault-v2/event-cycling-2024-08-06.md delete mode 100644 demo-vault-v2/event-cycling-2024-08-13.md delete mode 100644 demo-vault-v2/event-cycling-2024-08-20.md delete mode 100644 demo-vault-v2/event-cycling-2024-08-27.md delete mode 100644 demo-vault-v2/event-cycling-2024-09-03.md delete mode 100644 demo-vault-v2/event-cycling-2024-09-10.md delete mode 100644 demo-vault-v2/event-cycling-2024-09-17.md delete mode 100644 demo-vault-v2/event-cycling-2024-09-24.md delete mode 100644 demo-vault-v2/event-cycling-2024-10-01.md delete mode 100644 demo-vault-v2/event-cycling-2024-10-08.md delete mode 100644 demo-vault-v2/event-cycling-2024-10-15.md delete mode 100644 demo-vault-v2/event-cycling-2024-10-22.md delete mode 100644 demo-vault-v2/event-cycling-2024-10-29.md delete mode 100644 demo-vault-v2/event-cycling-2024-11-05.md delete mode 100644 demo-vault-v2/event-cycling-2024-11-12.md delete mode 100644 demo-vault-v2/event-cycling-2024-11-19.md delete mode 100644 demo-vault-v2/event-cycling-2024-11-26.md delete mode 100644 demo-vault-v2/event-cycling-2024-12-03.md delete mode 100644 demo-vault-v2/event-cycling-2024-12-10.md delete mode 100644 demo-vault-v2/event-cycling-2024-12-17.md delete mode 100644 demo-vault-v2/event-cycling-2024-12-24.md delete mode 100644 demo-vault-v2/event-cycling-2024-12-31.md delete mode 100644 demo-vault-v2/event-cycling-2025-01-07.md delete mode 100644 demo-vault-v2/event-cycling-2025-01-14.md delete mode 100644 demo-vault-v2/event-cycling-2025-01-21.md delete mode 100644 demo-vault-v2/event-cycling-2025-01-28.md delete mode 100644 demo-vault-v2/event-cycling-2025-02-04.md delete mode 100644 demo-vault-v2/event-cycling-2025-02-11.md delete mode 100644 demo-vault-v2/event-cycling-2025-02-18.md delete mode 100644 demo-vault-v2/event-cycling-2025-02-25.md delete mode 100644 demo-vault-v2/event-cycling-2025-03-04.md delete mode 100644 demo-vault-v2/event-cycling-2025-03-11.md delete mode 100644 demo-vault-v2/event-cycling-2025-03-18.md delete mode 100644 demo-vault-v2/event-cycling-2025-03-25.md delete mode 100644 demo-vault-v2/event-cycling-2025-04-01.md delete mode 100644 demo-vault-v2/event-cycling-2025-04-08.md delete mode 100644 demo-vault-v2/event-cycling-2025-04-15.md delete mode 100644 demo-vault-v2/event-cycling-2025-04-22.md delete mode 100644 demo-vault-v2/event-cycling-2025-04-29.md delete mode 100644 demo-vault-v2/event-cycling-2025-05-06.md delete mode 100644 demo-vault-v2/event-cycling-2025-05-13.md delete mode 100644 demo-vault-v2/event-cycling-2025-05-20.md delete mode 100644 demo-vault-v2/event-cycling-2025-05-27.md delete mode 100644 demo-vault-v2/event-cycling-2025-06-03.md delete mode 100644 demo-vault-v2/event-cycling-2025-06-10.md delete mode 100644 demo-vault-v2/event-cycling-2025-06-17.md delete mode 100644 demo-vault-v2/event-cycling-endurance-2024-01-04.md delete mode 100644 demo-vault-v2/event-cycling-endurance-2024-01-11.md delete mode 100644 demo-vault-v2/event-cycling-endurance-2024-01-18.md delete mode 100644 demo-vault-v2/event-cycling-endurance-2024-01-25.md delete mode 100644 demo-vault-v2/event-cycling-endurance-2024-02-01.md delete mode 100644 demo-vault-v2/event-cycling-endurance-2024-02-08.md delete mode 100644 demo-vault-v2/event-cycling-endurance-2024-02-15.md delete mode 100644 demo-vault-v2/event-cycling-endurance-2024-02-22.md delete mode 100644 demo-vault-v2/event-cycling-endurance-2024-02-29.md delete mode 100644 demo-vault-v2/event-cycling-endurance-2024-03-07.md delete mode 100644 demo-vault-v2/event-cycling-endurance-2024-03-14.md delete mode 100644 demo-vault-v2/event-cycling-endurance-2024-03-21.md delete mode 100644 demo-vault-v2/event-cycling-endurance-2024-03-28.md delete mode 100644 demo-vault-v2/event-cycling-endurance-2024-04-04.md delete mode 100644 demo-vault-v2/event-cycling-endurance-2024-04-11.md delete mode 100644 demo-vault-v2/event-cycling-endurance-2024-04-18.md delete mode 100644 demo-vault-v2/event-cycling-endurance-2024-04-25.md delete mode 100644 demo-vault-v2/event-cycling-endurance-2024-05-02.md delete mode 100644 demo-vault-v2/event-cycling-endurance-2024-05-09.md delete mode 100644 demo-vault-v2/event-cycling-endurance-2024-05-16.md delete mode 100644 demo-vault-v2/event-cycling-endurance-2024-05-23.md delete mode 100644 demo-vault-v2/event-cycling-endurance-2024-05-30.md delete mode 100644 demo-vault-v2/event-cycling-endurance-2024-06-06.md delete mode 100644 demo-vault-v2/event-cycling-endurance-2024-06-13.md delete mode 100644 demo-vault-v2/event-cycling-endurance-2024-06-20.md delete mode 100644 demo-vault-v2/event-cycling-endurance-2024-06-27.md delete mode 100644 demo-vault-v2/event-cycling-endurance-2024-07-04.md delete mode 100644 demo-vault-v2/event-cycling-endurance-2024-07-11.md delete mode 100644 demo-vault-v2/event-cycling-endurance-2024-07-18.md delete mode 100644 demo-vault-v2/event-cycling-endurance-2024-07-25.md delete mode 100644 demo-vault-v2/event-cycling-endurance-2024-08-01.md delete mode 100644 demo-vault-v2/event-cycling-endurance-2024-08-08.md delete mode 100644 demo-vault-v2/event-cycling-endurance-2024-08-15.md delete mode 100644 demo-vault-v2/event-cycling-endurance-2024-08-22.md delete mode 100644 demo-vault-v2/event-cycling-endurance-2024-08-29.md delete mode 100644 demo-vault-v2/event-cycling-endurance-2024-09-05.md delete mode 100644 demo-vault-v2/event-cycling-endurance-2024-09-12.md delete mode 100644 demo-vault-v2/event-cycling-endurance-2024-09-19.md delete mode 100644 demo-vault-v2/event-cycling-endurance-2024-09-26.md delete mode 100644 demo-vault-v2/event-cycling-endurance-2024-10-03.md delete mode 100644 demo-vault-v2/event-cycling-endurance-2024-10-10.md delete mode 100644 demo-vault-v2/event-cycling-endurance-2024-10-17.md delete mode 100644 demo-vault-v2/event-cycling-endurance-2024-10-24.md delete mode 100644 demo-vault-v2/event-cycling-endurance-2024-10-31.md delete mode 100644 demo-vault-v2/event-cycling-endurance-2024-11-07.md delete mode 100644 demo-vault-v2/event-cycling-endurance-2024-11-14.md delete mode 100644 demo-vault-v2/event-cycling-endurance-2024-11-21.md delete mode 100644 demo-vault-v2/event-cycling-endurance-2024-11-28.md delete mode 100644 demo-vault-v2/event-cycling-endurance-2024-12-05.md delete mode 100644 demo-vault-v2/event-cycling-endurance-2024-12-12.md delete mode 100644 demo-vault-v2/event-cycling-endurance-2024-12-19.md delete mode 100644 demo-vault-v2/event-cycling-endurance-2024-12-26.md delete mode 100644 demo-vault-v2/event-cycling-endurance-2025-01-02.md delete mode 100644 demo-vault-v2/event-cycling-endurance-2025-01-09.md delete mode 100644 demo-vault-v2/event-cycling-endurance-2025-01-16.md delete mode 100644 demo-vault-v2/event-cycling-endurance-2025-01-23.md delete mode 100644 demo-vault-v2/event-cycling-endurance-2025-01-30.md delete mode 100644 demo-vault-v2/event-cycling-endurance-2025-02-06.md delete mode 100644 demo-vault-v2/event-cycling-endurance-2025-02-13.md delete mode 100644 demo-vault-v2/event-cycling-endurance-2025-02-20.md delete mode 100644 demo-vault-v2/event-cycling-endurance-2025-02-27.md delete mode 100644 demo-vault-v2/event-cycling-endurance-2025-03-06.md delete mode 100644 demo-vault-v2/event-cycling-endurance-2025-03-13.md delete mode 100644 demo-vault-v2/event-cycling-endurance-2025-03-20.md delete mode 100644 demo-vault-v2/event-cycling-endurance-2025-03-27.md delete mode 100644 demo-vault-v2/event-cycling-endurance-2025-04-03.md delete mode 100644 demo-vault-v2/event-cycling-endurance-2025-04-10.md delete mode 100644 demo-vault-v2/event-cycling-endurance-2025-04-17.md delete mode 100644 demo-vault-v2/event-cycling-endurance-2025-04-24.md delete mode 100644 demo-vault-v2/event-cycling-endurance-2025-05-01.md delete mode 100644 demo-vault-v2/event-cycling-endurance-2025-05-08.md delete mode 100644 demo-vault-v2/event-cycling-endurance-2025-05-15.md delete mode 100644 demo-vault-v2/event-cycling-endurance-2025-05-22.md delete mode 100644 demo-vault-v2/event-cycling-endurance-2025-05-29.md delete mode 100644 demo-vault-v2/event-cycling-endurance-2025-06-05.md delete mode 100644 demo-vault-v2/event-cycling-endurance-2025-06-12.md delete mode 100644 demo-vault-v2/event-cycling-endurance-2025-06-19.md delete mode 100644 demo-vault-v2/event-dinner-2024-01-05.md delete mode 100644 demo-vault-v2/event-dinner-2024-01-12.md delete mode 100644 demo-vault-v2/event-dinner-2024-01-19.md delete mode 100644 demo-vault-v2/event-dinner-2024-02-23.md delete mode 100644 demo-vault-v2/event-dinner-2024-03-01.md delete mode 100644 demo-vault-v2/event-dinner-2024-04-05.md delete mode 100644 demo-vault-v2/event-dinner-2024-04-19.md delete mode 100644 demo-vault-v2/event-dinner-2024-05-24.md delete mode 100644 demo-vault-v2/event-dinner-2024-06-21.md delete mode 100644 demo-vault-v2/event-dinner-2024-06-28.md delete mode 100644 demo-vault-v2/event-dinner-2024-07-19.md delete mode 100644 demo-vault-v2/event-dinner-2024-08-02.md delete mode 100644 demo-vault-v2/event-dinner-2024-08-09.md delete mode 100644 demo-vault-v2/event-dinner-2024-08-16.md delete mode 100644 demo-vault-v2/event-dinner-2024-08-23.md delete mode 100644 demo-vault-v2/event-dinner-2024-09-13.md delete mode 100644 demo-vault-v2/event-dinner-2024-10-04.md delete mode 100644 demo-vault-v2/event-dinner-2024-10-11.md delete mode 100644 demo-vault-v2/event-dinner-2024-10-18.md delete mode 100644 demo-vault-v2/event-dinner-2024-10-25.md delete mode 100644 demo-vault-v2/event-dinner-2024-11-01.md delete mode 100644 demo-vault-v2/event-dinner-2024-11-29.md delete mode 100644 demo-vault-v2/event-dinner-2024-12-06.md delete mode 100644 demo-vault-v2/event-dinner-2024-12-13.md delete mode 100644 demo-vault-v2/event-dinner-2024-12-20.md delete mode 100644 demo-vault-v2/event-dinner-2024-12-27.md delete mode 100644 demo-vault-v2/event-dinner-2025-01-03.md delete mode 100644 demo-vault-v2/event-dinner-2025-01-10.md delete mode 100644 demo-vault-v2/event-dinner-2025-01-17.md delete mode 100644 demo-vault-v2/event-dinner-2025-01-24.md delete mode 100644 demo-vault-v2/event-dinner-2025-02-14.md delete mode 100644 demo-vault-v2/event-dinner-2025-02-28.md delete mode 100644 demo-vault-v2/event-dinner-2025-03-07.md delete mode 100644 demo-vault-v2/event-dinner-2025-03-14.md delete mode 100644 demo-vault-v2/event-dinner-2025-03-28.md delete mode 100644 demo-vault-v2/event-dinner-2025-04-04.md delete mode 100644 demo-vault-v2/event-dinner-2025-04-11.md delete mode 100644 demo-vault-v2/event-dinner-2025-04-25.md delete mode 100644 demo-vault-v2/event-dinner-2025-05-02.md delete mode 100644 demo-vault-v2/event-dinner-2025-05-16.md delete mode 100644 demo-vault-v2/event-dinner-2025-05-23.md delete mode 100644 demo-vault-v2/event-dinner-2025-06-06.md delete mode 100644 demo-vault-v2/event-dinner-2025-06-13.md delete mode 100644 demo-vault-v2/event-family-call-2024-01-14.md delete mode 100644 demo-vault-v2/event-family-call-2024-01-28.md delete mode 100644 demo-vault-v2/event-family-call-2024-02-11.md delete mode 100644 demo-vault-v2/event-family-call-2024-02-25.md delete mode 100644 demo-vault-v2/event-family-call-2024-03-10.md delete mode 100644 demo-vault-v2/event-family-call-2024-03-24.md delete mode 100644 demo-vault-v2/event-family-call-2024-04-07.md delete mode 100644 demo-vault-v2/event-family-call-2024-04-21.md delete mode 100644 demo-vault-v2/event-family-call-2024-05-05.md delete mode 100644 demo-vault-v2/event-family-call-2024-05-19.md delete mode 100644 demo-vault-v2/event-family-call-2024-06-02.md delete mode 100644 demo-vault-v2/event-family-call-2024-06-16.md delete mode 100644 demo-vault-v2/event-family-call-2024-06-30.md delete mode 100644 demo-vault-v2/event-family-call-2024-07-14.md delete mode 100644 demo-vault-v2/event-family-call-2024-07-28.md delete mode 100644 demo-vault-v2/event-family-call-2024-08-11.md delete mode 100644 demo-vault-v2/event-family-call-2024-08-25.md delete mode 100644 demo-vault-v2/event-family-call-2024-09-08.md delete mode 100644 demo-vault-v2/event-family-call-2024-09-22.md delete mode 100644 demo-vault-v2/event-family-call-2024-10-06.md delete mode 100644 demo-vault-v2/event-family-call-2024-10-20.md delete mode 100644 demo-vault-v2/event-family-call-2024-11-03.md delete mode 100644 demo-vault-v2/event-family-call-2024-11-17.md delete mode 100644 demo-vault-v2/event-family-call-2024-12-01.md delete mode 100644 demo-vault-v2/event-family-call-2024-12-15.md delete mode 100644 demo-vault-v2/event-family-call-2024-12-29.md delete mode 100644 demo-vault-v2/event-family-call-2025-01-12.md delete mode 100644 demo-vault-v2/event-family-call-2025-01-26.md delete mode 100644 demo-vault-v2/event-family-call-2025-02-09.md delete mode 100644 demo-vault-v2/event-family-call-2025-02-23.md delete mode 100644 demo-vault-v2/event-family-call-2025-03-09.md delete mode 100644 demo-vault-v2/event-family-call-2025-03-23.md delete mode 100644 demo-vault-v2/event-family-call-2025-04-06.md delete mode 100644 demo-vault-v2/event-family-call-2025-04-20.md delete mode 100644 demo-vault-v2/event-family-call-2025-05-04.md delete mode 100644 demo-vault-v2/event-family-call-2025-05-18.md delete mode 100644 demo-vault-v2/event-family-call-2025-06-01.md delete mode 100644 demo-vault-v2/event-family-call-2025-06-15.md delete mode 100644 demo-vault-v2/event-gym-2024-01-03.md delete mode 100644 demo-vault-v2/event-gym-2024-01-17.md delete mode 100644 demo-vault-v2/event-gym-2024-01-31.md delete mode 100644 demo-vault-v2/event-gym-2024-02-14.md delete mode 100644 demo-vault-v2/event-gym-2024-02-28.md delete mode 100644 demo-vault-v2/event-gym-2024-03-13.md delete mode 100644 demo-vault-v2/event-gym-2024-03-27.md delete mode 100644 demo-vault-v2/event-gym-2024-04-10.md delete mode 100644 demo-vault-v2/event-gym-2024-04-24.md delete mode 100644 demo-vault-v2/event-gym-2024-05-08.md delete mode 100644 demo-vault-v2/event-gym-2024-05-22.md delete mode 100644 demo-vault-v2/event-gym-2024-06-05.md delete mode 100644 demo-vault-v2/event-gym-2024-06-19.md delete mode 100644 demo-vault-v2/event-gym-2024-07-03.md delete mode 100644 demo-vault-v2/event-gym-2024-07-17.md delete mode 100644 demo-vault-v2/event-gym-2024-07-31.md delete mode 100644 demo-vault-v2/event-gym-2024-08-14.md delete mode 100644 demo-vault-v2/event-gym-2024-08-28.md delete mode 100644 demo-vault-v2/event-gym-2024-09-11.md delete mode 100644 demo-vault-v2/event-gym-2024-09-25.md delete mode 100644 demo-vault-v2/event-gym-2024-10-09.md delete mode 100644 demo-vault-v2/event-gym-2024-10-23.md delete mode 100644 demo-vault-v2/event-gym-2024-11-06.md delete mode 100644 demo-vault-v2/event-gym-2024-11-20.md delete mode 100644 demo-vault-v2/event-gym-2024-12-04.md delete mode 100644 demo-vault-v2/event-gym-2024-12-18.md delete mode 100644 demo-vault-v2/event-gym-2025-01-01.md delete mode 100644 demo-vault-v2/event-gym-2025-01-15.md delete mode 100644 demo-vault-v2/event-gym-2025-01-29.md delete mode 100644 demo-vault-v2/event-gym-2025-02-12.md delete mode 100644 demo-vault-v2/event-gym-2025-02-26.md delete mode 100644 demo-vault-v2/event-gym-2025-03-12.md delete mode 100644 demo-vault-v2/event-gym-2025-03-26.md delete mode 100644 demo-vault-v2/event-gym-2025-04-09.md delete mode 100644 demo-vault-v2/event-gym-2025-04-23.md delete mode 100644 demo-vault-v2/event-gym-2025-05-07.md delete mode 100644 demo-vault-v2/event-gym-2025-05-21.md delete mode 100644 demo-vault-v2/event-gym-2025-06-04.md delete mode 100644 demo-vault-v2/event-gym-2025-06-18.md delete mode 100644 demo-vault-v2/event-gym-fri-2024-01-12.md delete mode 100644 demo-vault-v2/event-gym-fri-2024-01-26.md delete mode 100644 demo-vault-v2/event-gym-fri-2024-02-09.md delete mode 100644 demo-vault-v2/event-gym-fri-2024-02-23.md delete mode 100644 demo-vault-v2/event-gym-fri-2024-03-08.md delete mode 100644 demo-vault-v2/event-gym-fri-2024-03-22.md delete mode 100644 demo-vault-v2/event-gym-fri-2024-04-05.md delete mode 100644 demo-vault-v2/event-gym-fri-2024-04-19.md delete mode 100644 demo-vault-v2/event-gym-fri-2024-05-03.md delete mode 100644 demo-vault-v2/event-gym-fri-2024-05-17.md delete mode 100644 demo-vault-v2/event-gym-fri-2024-05-31.md delete mode 100644 demo-vault-v2/event-gym-fri-2024-06-14.md delete mode 100644 demo-vault-v2/event-gym-fri-2024-06-28.md delete mode 100644 demo-vault-v2/event-gym-fri-2024-07-12.md delete mode 100644 demo-vault-v2/event-gym-fri-2024-07-26.md delete mode 100644 demo-vault-v2/event-gym-fri-2024-08-09.md delete mode 100644 demo-vault-v2/event-gym-fri-2024-08-23.md delete mode 100644 demo-vault-v2/event-gym-fri-2024-09-06.md delete mode 100644 demo-vault-v2/event-gym-fri-2024-09-20.md delete mode 100644 demo-vault-v2/event-gym-fri-2024-10-04.md delete mode 100644 demo-vault-v2/event-gym-fri-2024-10-18.md delete mode 100644 demo-vault-v2/event-gym-fri-2024-11-01.md delete mode 100644 demo-vault-v2/event-gym-fri-2024-11-15.md delete mode 100644 demo-vault-v2/event-gym-fri-2024-11-29.md delete mode 100644 demo-vault-v2/event-gym-fri-2024-12-13.md delete mode 100644 demo-vault-v2/event-gym-fri-2024-12-27.md delete mode 100644 demo-vault-v2/event-gym-fri-2025-01-10.md delete mode 100644 demo-vault-v2/event-gym-fri-2025-01-24.md delete mode 100644 demo-vault-v2/event-gym-fri-2025-02-07.md delete mode 100644 demo-vault-v2/event-gym-fri-2025-02-21.md delete mode 100644 demo-vault-v2/event-gym-fri-2025-03-07.md delete mode 100644 demo-vault-v2/event-gym-fri-2025-03-21.md delete mode 100644 demo-vault-v2/event-gym-fri-2025-04-04.md delete mode 100644 demo-vault-v2/event-gym-fri-2025-04-18.md delete mode 100644 demo-vault-v2/event-gym-fri-2025-05-02.md delete mode 100644 demo-vault-v2/event-gym-fri-2025-05-16.md delete mode 100644 demo-vault-v2/event-gym-fri-2025-05-30.md delete mode 100644 demo-vault-v2/event-gym-fri-2025-06-13.md delete mode 100644 demo-vault-v2/event-long-ride-2024-01-06.md delete mode 100644 demo-vault-v2/event-long-ride-2024-01-13.md delete mode 100644 demo-vault-v2/event-long-ride-2024-01-20.md delete mode 100644 demo-vault-v2/event-long-ride-2024-01-27.md delete mode 100644 demo-vault-v2/event-long-ride-2024-02-03.md delete mode 100644 demo-vault-v2/event-long-ride-2024-02-10.md delete mode 100644 demo-vault-v2/event-long-ride-2024-02-17.md delete mode 100644 demo-vault-v2/event-long-ride-2024-02-24.md delete mode 100644 demo-vault-v2/event-long-ride-2024-03-02.md delete mode 100644 demo-vault-v2/event-long-ride-2024-03-09.md delete mode 100644 demo-vault-v2/event-long-ride-2024-03-16.md delete mode 100644 demo-vault-v2/event-long-ride-2024-03-23.md delete mode 100644 demo-vault-v2/event-long-ride-2024-03-30.md delete mode 100644 demo-vault-v2/event-long-ride-2024-04-06.md delete mode 100644 demo-vault-v2/event-long-ride-2024-04-13.md delete mode 100644 demo-vault-v2/event-long-ride-2024-04-20.md delete mode 100644 demo-vault-v2/event-long-ride-2024-04-27.md delete mode 100644 demo-vault-v2/event-long-ride-2024-05-04.md delete mode 100644 demo-vault-v2/event-long-ride-2024-05-11.md delete mode 100644 demo-vault-v2/event-long-ride-2024-05-18.md delete mode 100644 demo-vault-v2/event-long-ride-2024-05-25.md delete mode 100644 demo-vault-v2/event-long-ride-2024-06-01.md delete mode 100644 demo-vault-v2/event-long-ride-2024-06-08.md delete mode 100644 demo-vault-v2/event-long-ride-2024-06-15.md delete mode 100644 demo-vault-v2/event-long-ride-2024-06-22.md delete mode 100644 demo-vault-v2/event-long-ride-2024-06-29.md delete mode 100644 demo-vault-v2/event-long-ride-2024-07-06.md delete mode 100644 demo-vault-v2/event-long-ride-2024-07-13.md delete mode 100644 demo-vault-v2/event-long-ride-2024-07-20.md delete mode 100644 demo-vault-v2/event-long-ride-2024-07-27.md delete mode 100644 demo-vault-v2/event-long-ride-2024-08-03.md delete mode 100644 demo-vault-v2/event-long-ride-2024-08-10.md delete mode 100644 demo-vault-v2/event-long-ride-2024-08-17.md delete mode 100644 demo-vault-v2/event-long-ride-2024-08-24.md delete mode 100644 demo-vault-v2/event-long-ride-2024-08-31.md delete mode 100644 demo-vault-v2/event-long-ride-2024-09-07.md delete mode 100644 demo-vault-v2/event-long-ride-2024-09-14.md delete mode 100644 demo-vault-v2/event-long-ride-2024-09-21.md delete mode 100644 demo-vault-v2/event-long-ride-2024-09-28.md delete mode 100644 demo-vault-v2/event-long-ride-2024-10-05.md delete mode 100644 demo-vault-v2/event-long-ride-2024-10-12.md delete mode 100644 demo-vault-v2/event-long-ride-2024-10-19.md delete mode 100644 demo-vault-v2/event-long-ride-2024-10-26.md delete mode 100644 demo-vault-v2/event-long-ride-2024-11-02.md delete mode 100644 demo-vault-v2/event-long-ride-2024-11-09.md delete mode 100644 demo-vault-v2/event-long-ride-2024-11-16.md delete mode 100644 demo-vault-v2/event-long-ride-2024-11-23.md delete mode 100644 demo-vault-v2/event-long-ride-2024-11-30.md delete mode 100644 demo-vault-v2/event-long-ride-2024-12-07.md delete mode 100644 demo-vault-v2/event-long-ride-2024-12-14.md delete mode 100644 demo-vault-v2/event-long-ride-2024-12-21.md delete mode 100644 demo-vault-v2/event-long-ride-2024-12-28.md delete mode 100644 demo-vault-v2/event-long-ride-2025-01-04.md delete mode 100644 demo-vault-v2/event-long-ride-2025-01-11.md delete mode 100644 demo-vault-v2/event-long-ride-2025-01-18.md delete mode 100644 demo-vault-v2/event-long-ride-2025-01-25.md delete mode 100644 demo-vault-v2/event-long-ride-2025-02-01.md delete mode 100644 demo-vault-v2/event-long-ride-2025-02-08.md delete mode 100644 demo-vault-v2/event-long-ride-2025-02-15.md delete mode 100644 demo-vault-v2/event-long-ride-2025-02-22.md delete mode 100644 demo-vault-v2/event-long-ride-2025-03-01.md delete mode 100644 demo-vault-v2/event-long-ride-2025-03-08.md delete mode 100644 demo-vault-v2/event-long-ride-2025-03-15.md delete mode 100644 demo-vault-v2/event-long-ride-2025-03-22.md delete mode 100644 demo-vault-v2/event-long-ride-2025-03-29.md delete mode 100644 demo-vault-v2/event-long-ride-2025-04-05.md delete mode 100644 demo-vault-v2/event-long-ride-2025-04-12.md delete mode 100644 demo-vault-v2/event-long-ride-2025-04-19.md delete mode 100644 demo-vault-v2/event-long-ride-2025-04-26.md delete mode 100644 demo-vault-v2/event-long-ride-2025-05-03.md delete mode 100644 demo-vault-v2/event-long-ride-2025-05-10.md delete mode 100644 demo-vault-v2/event-long-ride-2025-05-17.md delete mode 100644 demo-vault-v2/event-long-ride-2025-05-24.md delete mode 100644 demo-vault-v2/event-long-ride-2025-05-31.md delete mode 100644 demo-vault-v2/event-long-ride-2025-06-07.md delete mode 100644 demo-vault-v2/event-long-ride-2025-06-14.md delete mode 100644 demo-vault-v2/event-nonna-visit-2024-01-28.md delete mode 100644 demo-vault-v2/event-nonna-visit-2024-02-25.md delete mode 100644 demo-vault-v2/event-nonna-visit-2024-03-24.md delete mode 100644 demo-vault-v2/event-nonna-visit-2024-03-31.md delete mode 100644 demo-vault-v2/event-nonna-visit-2024-04-28.md delete mode 100644 demo-vault-v2/event-nonna-visit-2024-05-26.md delete mode 100644 demo-vault-v2/event-nonna-visit-2024-06-30.md delete mode 100644 demo-vault-v2/event-nonna-visit-2024-07-28.md delete mode 100644 demo-vault-v2/event-nonna-visit-2024-08-25.md delete mode 100644 demo-vault-v2/event-nonna-visit-2024-09-29.md delete mode 100644 demo-vault-v2/event-nonna-visit-2024-10-27.md delete mode 100644 demo-vault-v2/event-nonna-visit-2024-11-24.md delete mode 100644 demo-vault-v2/event-nonna-visit-2024-12-29.md delete mode 100644 demo-vault-v2/event-nonna-visit-2025-01-26.md delete mode 100644 demo-vault-v2/event-nonna-visit-2025-03-30.md delete mode 100644 demo-vault-v2/event-nonna-visit-2025-04-27.md delete mode 100644 demo-vault-v2/event-nonna-visit-2025-05-25.md delete mode 100644 demo-vault-v2/event-podcast-rec-2024-02-01.md delete mode 100644 demo-vault-v2/event-podcast-rec-2024-02-15.md delete mode 100644 demo-vault-v2/event-podcast-rec-2024-02-29.md delete mode 100644 demo-vault-v2/event-podcast-rec-2024-03-14.md delete mode 100644 demo-vault-v2/event-podcast-rec-2024-03-28.md delete mode 100644 demo-vault-v2/event-podcast-rec-2024-04-11.md delete mode 100644 demo-vault-v2/event-podcast-rec-2024-04-25.md delete mode 100644 demo-vault-v2/event-podcast-rec-2024-05-09.md delete mode 100644 demo-vault-v2/event-podcast-rec-2024-05-23.md delete mode 100644 demo-vault-v2/event-podcast-rec-2024-06-06.md delete mode 100644 demo-vault-v2/event-podcast-rec-2024-06-20.md delete mode 100644 demo-vault-v2/event-podcast-rec-2024-07-04.md delete mode 100644 demo-vault-v2/event-podcast-rec-2024-07-18.md delete mode 100644 demo-vault-v2/event-podcast-rec-2024-08-01.md delete mode 100644 demo-vault-v2/event-podcast-rec-2024-08-15.md delete mode 100644 demo-vault-v2/event-podcast-rec-2024-08-29.md delete mode 100644 demo-vault-v2/event-podcast-rec-2024-09-12.md delete mode 100644 demo-vault-v2/event-podcast-rec-2024-09-26.md delete mode 100644 demo-vault-v2/event-podcast-rec-2024-10-10.md delete mode 100644 demo-vault-v2/event-podcast-rec-2024-10-24.md delete mode 100644 demo-vault-v2/event-podcast-rec-2024-11-07.md delete mode 100644 demo-vault-v2/event-podcast-rec-2024-11-21.md delete mode 100644 demo-vault-v2/event-podcast-rec-2024-12-05.md delete mode 100644 demo-vault-v2/event-podcast-rec-2024-12-19.md delete mode 100644 demo-vault-v2/event-podcast-rec-2025-01-02.md delete mode 100644 demo-vault-v2/event-podcast-rec-2025-01-16.md delete mode 100644 demo-vault-v2/event-podcast-rec-2025-01-30.md delete mode 100644 demo-vault-v2/event-podcast-rec-2025-02-13.md delete mode 100644 demo-vault-v2/event-podcast-rec-2025-02-27.md delete mode 100644 demo-vault-v2/event-podcast-rec-2025-03-13.md delete mode 100644 demo-vault-v2/event-podcast-rec-2025-03-27.md delete mode 100644 demo-vault-v2/event-podcast-rec-2025-04-10.md delete mode 100644 demo-vault-v2/event-podcast-rec-2025-04-24.md delete mode 100644 demo-vault-v2/event-podcast-rec-2025-05-08.md delete mode 100644 demo-vault-v2/event-podcast-rec-2025-05-22.md delete mode 100644 demo-vault-v2/event-podcast-rec-2025-06-05.md delete mode 100644 demo-vault-v2/event-podcast-rec-2025-06-19.md delete mode 100644 demo-vault-v2/event-reading-2024-01-07.md delete mode 100644 demo-vault-v2/event-reading-2024-01-21.md delete mode 100644 demo-vault-v2/event-reading-2024-02-04.md delete mode 100644 demo-vault-v2/event-reading-2024-02-18.md delete mode 100644 demo-vault-v2/event-reading-2024-03-03.md delete mode 100644 demo-vault-v2/event-reading-2024-03-17.md delete mode 100644 demo-vault-v2/event-reading-2024-03-31.md delete mode 100644 demo-vault-v2/event-reading-2024-04-14.md delete mode 100644 demo-vault-v2/event-reading-2024-04-28.md delete mode 100644 demo-vault-v2/event-reading-2024-05-12.md delete mode 100644 demo-vault-v2/event-reading-2024-05-26.md delete mode 100644 demo-vault-v2/event-reading-2024-06-09.md delete mode 100644 demo-vault-v2/event-reading-2024-06-23.md delete mode 100644 demo-vault-v2/event-reading-2024-07-07.md delete mode 100644 demo-vault-v2/event-reading-2024-07-21.md delete mode 100644 demo-vault-v2/event-reading-2024-08-04.md delete mode 100644 demo-vault-v2/event-reading-2024-08-18.md delete mode 100644 demo-vault-v2/event-reading-2024-09-01.md delete mode 100644 demo-vault-v2/event-reading-2024-09-15.md delete mode 100644 demo-vault-v2/event-reading-2024-09-29.md delete mode 100644 demo-vault-v2/event-reading-2024-10-13.md delete mode 100644 demo-vault-v2/event-reading-2024-10-27.md delete mode 100644 demo-vault-v2/event-reading-2024-11-10.md delete mode 100644 demo-vault-v2/event-reading-2024-11-24.md delete mode 100644 demo-vault-v2/event-reading-2024-12-08.md delete mode 100644 demo-vault-v2/event-reading-2024-12-22.md delete mode 100644 demo-vault-v2/event-reading-2025-01-05.md delete mode 100644 demo-vault-v2/event-reading-2025-01-19.md delete mode 100644 demo-vault-v2/event-reading-2025-02-02.md delete mode 100644 demo-vault-v2/event-reading-2025-02-16.md delete mode 100644 demo-vault-v2/event-reading-2025-03-02.md delete mode 100644 demo-vault-v2/event-reading-2025-03-16.md delete mode 100644 demo-vault-v2/event-reading-2025-03-30.md delete mode 100644 demo-vault-v2/event-reading-2025-04-13.md delete mode 100644 demo-vault-v2/event-reading-2025-04-27.md delete mode 100644 demo-vault-v2/event-reading-2025-05-11.md delete mode 100644 demo-vault-v2/event-reading-2025-05-25.md delete mode 100644 demo-vault-v2/event-reading-2025-06-08.md delete mode 100644 demo-vault-v2/event-sponsor-call-2024-01-05.md delete mode 100644 demo-vault-v2/event-sponsor-call-2024-01-19.md delete mode 100644 demo-vault-v2/event-sponsor-call-2024-02-02.md delete mode 100644 demo-vault-v2/event-sponsor-call-2024-02-16.md delete mode 100644 demo-vault-v2/event-sponsor-call-2024-03-01.md delete mode 100644 demo-vault-v2/event-sponsor-call-2024-03-15.md delete mode 100644 demo-vault-v2/event-sponsor-call-2024-03-29.md delete mode 100644 demo-vault-v2/event-sponsor-call-2024-04-12.md delete mode 100644 demo-vault-v2/event-sponsor-call-2024-04-26.md delete mode 100644 demo-vault-v2/event-sponsor-call-2024-05-10.md delete mode 100644 demo-vault-v2/event-sponsor-call-2024-05-24.md delete mode 100644 demo-vault-v2/event-sponsor-call-2024-06-07.md delete mode 100644 demo-vault-v2/event-sponsor-call-2024-06-21.md delete mode 100644 demo-vault-v2/event-sponsor-call-2024-07-05.md delete mode 100644 demo-vault-v2/event-sponsor-call-2024-07-19.md delete mode 100644 demo-vault-v2/event-sponsor-call-2024-08-02.md delete mode 100644 demo-vault-v2/event-sponsor-call-2024-08-16.md delete mode 100644 demo-vault-v2/event-sponsor-call-2024-08-30.md delete mode 100644 demo-vault-v2/event-sponsor-call-2024-09-13.md delete mode 100644 demo-vault-v2/event-sponsor-call-2024-09-27.md delete mode 100644 demo-vault-v2/event-sponsor-call-2024-10-11.md delete mode 100644 demo-vault-v2/event-sponsor-call-2024-10-25.md delete mode 100644 demo-vault-v2/event-sponsor-call-2024-11-08.md delete mode 100644 demo-vault-v2/event-sponsor-call-2024-11-22.md delete mode 100644 demo-vault-v2/event-sponsor-call-2024-12-06.md delete mode 100644 demo-vault-v2/event-sponsor-call-2024-12-20.md delete mode 100644 demo-vault-v2/event-sponsor-call-2025-01-03.md delete mode 100644 demo-vault-v2/event-sponsor-call-2025-01-17.md delete mode 100644 demo-vault-v2/event-sponsor-call-2025-01-31.md delete mode 100644 demo-vault-v2/event-sponsor-call-2025-02-14.md delete mode 100644 demo-vault-v2/event-sponsor-call-2025-02-28.md delete mode 100644 demo-vault-v2/event-sponsor-call-2025-03-14.md delete mode 100644 demo-vault-v2/event-sponsor-call-2025-03-28.md delete mode 100644 demo-vault-v2/event-sponsor-call-2025-04-11.md delete mode 100644 demo-vault-v2/event-sponsor-call-2025-04-25.md delete mode 100644 demo-vault-v2/event-sponsor-call-2025-05-09.md delete mode 100644 demo-vault-v2/event-sponsor-call-2025-05-23.md delete mode 100644 demo-vault-v2/event-sponsor-call-2025-06-06.md delete mode 100644 demo-vault-v2/event-team-sync-2024-01-01.md delete mode 100644 demo-vault-v2/event-team-sync-2024-01-08.md delete mode 100644 demo-vault-v2/event-team-sync-2024-01-15.md delete mode 100644 demo-vault-v2/event-team-sync-2024-01-22.md delete mode 100644 demo-vault-v2/event-team-sync-2024-01-29.md delete mode 100644 demo-vault-v2/event-team-sync-2024-02-05.md delete mode 100644 demo-vault-v2/event-team-sync-2024-02-12.md delete mode 100644 demo-vault-v2/event-team-sync-2024-02-19.md delete mode 100644 demo-vault-v2/event-team-sync-2024-02-26.md delete mode 100644 demo-vault-v2/event-team-sync-2024-03-04.md delete mode 100644 demo-vault-v2/event-team-sync-2024-03-11.md delete mode 100644 demo-vault-v2/event-team-sync-2024-03-18.md delete mode 100644 demo-vault-v2/event-team-sync-2024-03-25.md delete mode 100644 demo-vault-v2/event-team-sync-2024-04-01.md delete mode 100644 demo-vault-v2/event-team-sync-2024-04-08.md delete mode 100644 demo-vault-v2/event-team-sync-2024-04-15.md delete mode 100644 demo-vault-v2/event-team-sync-2024-04-22.md delete mode 100644 demo-vault-v2/event-team-sync-2024-04-29.md delete mode 100644 demo-vault-v2/event-team-sync-2024-05-06.md delete mode 100644 demo-vault-v2/event-team-sync-2024-05-13.md delete mode 100644 demo-vault-v2/event-team-sync-2024-05-20.md delete mode 100644 demo-vault-v2/event-team-sync-2024-05-27.md delete mode 100644 demo-vault-v2/event-team-sync-2024-06-03.md delete mode 100644 demo-vault-v2/event-team-sync-2024-06-10.md delete mode 100644 demo-vault-v2/event-team-sync-2024-06-17.md delete mode 100644 demo-vault-v2/event-team-sync-2024-06-24.md delete mode 100644 demo-vault-v2/event-team-sync-2024-07-01.md delete mode 100644 demo-vault-v2/event-team-sync-2024-07-08.md delete mode 100644 demo-vault-v2/event-team-sync-2024-07-15.md delete mode 100644 demo-vault-v2/event-team-sync-2024-07-22.md delete mode 100644 demo-vault-v2/event-team-sync-2024-07-29.md delete mode 100644 demo-vault-v2/event-team-sync-2024-08-05.md delete mode 100644 demo-vault-v2/event-team-sync-2024-08-12.md delete mode 100644 demo-vault-v2/event-team-sync-2024-08-19.md delete mode 100644 demo-vault-v2/event-team-sync-2024-08-26.md delete mode 100644 demo-vault-v2/event-team-sync-2024-09-02.md delete mode 100644 demo-vault-v2/event-team-sync-2024-09-09.md delete mode 100644 demo-vault-v2/event-team-sync-2024-09-16.md delete mode 100644 demo-vault-v2/event-team-sync-2024-09-23.md delete mode 100644 demo-vault-v2/event-team-sync-2024-09-30.md delete mode 100644 demo-vault-v2/event-team-sync-2024-10-07.md delete mode 100644 demo-vault-v2/event-team-sync-2024-10-14.md delete mode 100644 demo-vault-v2/event-team-sync-2024-10-21.md delete mode 100644 demo-vault-v2/event-team-sync-2024-10-28.md delete mode 100644 demo-vault-v2/event-team-sync-2024-11-04.md delete mode 100644 demo-vault-v2/event-team-sync-2024-11-11.md delete mode 100644 demo-vault-v2/event-team-sync-2024-11-18.md delete mode 100644 demo-vault-v2/event-team-sync-2024-11-25.md delete mode 100644 demo-vault-v2/event-team-sync-2024-12-02.md delete mode 100644 demo-vault-v2/event-team-sync-2024-12-09.md delete mode 100644 demo-vault-v2/event-team-sync-2024-12-16.md delete mode 100644 demo-vault-v2/event-team-sync-2024-12-23.md delete mode 100644 demo-vault-v2/event-team-sync-2024-12-30.md delete mode 100644 demo-vault-v2/event-team-sync-2025-01-06.md delete mode 100644 demo-vault-v2/event-team-sync-2025-01-20.md delete mode 100644 demo-vault-v2/event-team-sync-2025-01-27.md delete mode 100644 demo-vault-v2/event-team-sync-2025-02-03.md delete mode 100644 demo-vault-v2/event-team-sync-2025-02-10.md delete mode 100644 demo-vault-v2/event-team-sync-2025-02-17.md delete mode 100644 demo-vault-v2/event-team-sync-2025-02-24.md delete mode 100644 demo-vault-v2/event-team-sync-2025-03-03.md delete mode 100644 demo-vault-v2/event-team-sync-2025-03-10.md delete mode 100644 demo-vault-v2/event-team-sync-2025-03-17.md delete mode 100644 demo-vault-v2/event-team-sync-2025-03-24.md delete mode 100644 demo-vault-v2/event-team-sync-2025-03-31.md delete mode 100644 demo-vault-v2/event-team-sync-2025-04-07.md delete mode 100644 demo-vault-v2/event-team-sync-2025-04-14.md delete mode 100644 demo-vault-v2/event-team-sync-2025-04-21.md delete mode 100644 demo-vault-v2/event-team-sync-2025-04-28.md delete mode 100644 demo-vault-v2/event-team-sync-2025-05-05.md delete mode 100644 demo-vault-v2/event-team-sync-2025-05-12.md delete mode 100644 demo-vault-v2/event-team-sync-2025-05-19.md delete mode 100644 demo-vault-v2/event-team-sync-2025-05-26.md delete mode 100644 demo-vault-v2/event-team-sync-2025-06-02.md delete mode 100644 demo-vault-v2/event-team-sync-2025-06-09.md delete mode 100644 demo-vault-v2/event-team-sync-2025-06-16.md delete mode 100644 demo-vault-v2/event.md delete mode 100644 demo-vault-v2/evergreen.md delete mode 100644 demo-vault-v2/experiment-failed-podcast.md delete mode 100644 demo-vault-v2/experiment.md delete mode 100644 demo-vault-v2/final-renamed.md delete mode 100644 demo-vault-v2/final-title-r-renamed.md delete mode 100644 demo-vault-v2/final-title-r.md delete mode 100644 demo-vault-v2/final-title-renamed-renamed.md delete mode 100644 demo-vault-v2/final-title-renamed.md delete mode 100644 demo-vault-v2/final-title.md delete mode 100644 demo-vault-v2/goal.md delete mode 100644 demo-vault-v2/index-funds-and-intellectual-humility.md delete mode 100644 demo-vault-v2/investing-in-yourself-vs-markets.md delete mode 100644 demo-vault-v2/italian-startup-ecosystem-observations.md delete mode 100644 demo-vault-v2/knowledge-management-is-not-filing.md create mode 100644 demo-vault-v2/laputa-qa-reference.md delete mode 100644 demo-vault-v2/measure-articles-per-week.md delete mode 100644 demo-vault-v2/measure-books-per-month.md delete mode 100644 demo-vault-v2/measure-cycling-km-per-month.md delete mode 100644 demo-vault-v2/measure-essay-quality-score.md delete mode 100644 demo-vault-v2/measure-evergreen-notes-created.md delete mode 100644 demo-vault-v2/measure-net-worth.md delete mode 100644 demo-vault-v2/measure-open-rate.md delete mode 100644 demo-vault-v2/measure-podcast-downloads.md delete mode 100644 demo-vault-v2/measure-podcast-episodes-per-month.md delete mode 100644 demo-vault-v2/measure-resting-hr.md delete mode 100644 demo-vault-v2/measure-savings-rate.md delete mode 100644 demo-vault-v2/measure-subscribers.md delete mode 100644 demo-vault-v2/measure-task-completion-rate.md delete mode 100644 demo-vault-v2/measure-team-nps.md delete mode 100644 demo-vault-v2/measure.md delete mode 100644 demo-vault-v2/minimal.md delete mode 100644 demo-vault-v2/month.md delete mode 100644 demo-vault-v2/my-renamed-note.md delete mode 100644 demo-vault-v2/newsletter-growth-is-about-trust.md delete mode 100644 demo-vault-v2/newsletter-subject-lines.md delete mode 100644 demo-vault-v2/note-atomic-habits.md delete mode 100644 demo-vault-v2/note-born-to-run.md delete mode 100644 demo-vault-v2/note-building-a-second-brain.md delete mode 100644 demo-vault-v2/note-deep-work.md delete mode 100644 demo-vault-v2/note-deprecated-workflow.md delete mode 100644 demo-vault-v2/note-essentialism.md delete mode 100644 demo-vault-v2/note-good-strategy-bad-strategy.md delete mode 100644 demo-vault-v2/note-grit.md delete mode 100644 demo-vault-v2/note-how-minds-change.md delete mode 100644 demo-vault-v2/note-makers-schedule-managers.md delete mode 100644 demo-vault-v2/note-man-search-for-meaning.md delete mode 100644 demo-vault-v2/note-never-split-difference.md delete mode 100644 demo-vault-v2/note-old-meeting-notes.md create mode 100644 demo-vault-v2/note-on-clear-prose.md delete mode 100644 demo-vault-v2/note-on-the-shortness-of-life.md delete mode 100644 demo-vault-v2/note-on-writing-well.md delete mode 100644 demo-vault-v2/note-radical-candor.md delete mode 100644 demo-vault-v2/note-range.md delete mode 100644 demo-vault-v2/note-show-your-work.md delete mode 100644 demo-vault-v2/note-so-good-they-cant-ignore.md delete mode 100644 demo-vault-v2/note-the-art-of-learning.md delete mode 100644 demo-vault-v2/note-the-courage-to-be-disliked.md delete mode 100644 demo-vault-v2/note-the-effective-executive.md delete mode 100644 demo-vault-v2/note-the-hard-thing-about-hard-things.md delete mode 100644 demo-vault-v2/note-the-innovators-dilemma.md delete mode 100644 demo-vault-v2/note-the-lean-startup.md delete mode 100644 demo-vault-v2/note-the-mom-test.md delete mode 100644 demo-vault-v2/note-the-obstacle-is-the-way.md delete mode 100644 demo-vault-v2/note-the-willpower-instinct.md delete mode 100644 demo-vault-v2/note-thinking-fast-and-slow.md delete mode 100644 demo-vault-v2/note-thinking-in-bets.md delete mode 100644 demo-vault-v2/note-traffic-secrets.md delete mode 100644 demo-vault-v2/note-zero-to-one.md delete mode 100644 demo-vault-v2/note.md delete mode 100644 demo-vault-v2/note/final-title-r-renamed.md delete mode 100644 demo-vault-v2/note/final-title-r.md delete mode 100644 demo-vault-v2/note/final-title-renamed-renamed.md delete mode 100644 demo-vault-v2/note/untitled-save-no-rename-te.md delete mode 100644 demo-vault-v2/note/untitled-save-no-rename-test-2.md delete mode 100644 demo-vault-v2/note/untitled-save-no-rename-test.md delete mode 100644 demo-vault-v2/note/untitled-tes-renamed.md delete mode 100644 demo-vault-v2/note/untitled-test-note-abc-2.md delete mode 100644 demo-vault-v2/note/untitled-test-note-abc-3.md delete mode 100644 demo-vault-v2/note/untitled-test-note-abc-renamed.md delete mode 100644 demo-vault-v2/on-consistency-in-creative-work.md delete mode 100644 demo-vault-v2/on-founder-energy-management.md delete mode 100644 demo-vault-v2/open-source-as-marketing.md delete mode 100644 demo-vault-v2/person-adeel-khan.md delete mode 100644 demo-vault-v2/person-alberto-ferro.md delete mode 100644 demo-vault-v2/person-alessandro-ferrari.md delete mode 100644 demo-vault-v2/person-andrea-colombo.md delete mode 100644 demo-vault-v2/person-andrea-provaglio.md delete mode 100644 demo-vault-v2/person-anna-fontana.md delete mode 100644 demo-vault-v2/person-anna-kowalski.md delete mode 100644 demo-vault-v2/person-anna-lindberg.md delete mode 100644 demo-vault-v2/person-antonio-marchetti.md delete mode 100644 demo-vault-v2/person-benedetta-vitali.md delete mode 100644 demo-vault-v2/person-carlos-mendez.md delete mode 100644 demo-vault-v2/person-chiara-romano.md delete mode 100644 demo-vault-v2/person-clara-dupont.md delete mode 100644 demo-vault-v2/person-david-eriksson.md delete mode 100644 demo-vault-v2/person-david-kim.md delete mode 100644 demo-vault-v2/person-davide-conti.md delete mode 100644 demo-vault-v2/person-diego-santos.md delete mode 100644 demo-vault-v2/person-elena-konstantinou.md delete mode 100644 demo-vault-v2/person-elena-rossi.md delete mode 100644 demo-vault-v2/person-elisa-barbieri.md delete mode 100644 demo-vault-v2/person-emilia-hoffmann.md delete mode 100644 demo-vault-v2/person-emma-wilson.md delete mode 100644 demo-vault-v2/person-federico-moretti.md delete mode 100644 demo-vault-v2/person-francesca-deluca.md delete mode 100644 demo-vault-v2/person-francesca-marino.md delete mode 100644 demo-vault-v2/person-gianluca-esposito.md delete mode 100644 demo-vault-v2/person-giulia-conti.md delete mode 100644 demo-vault-v2/person-giulia-marchetti.md delete mode 100644 demo-vault-v2/person-henrik-johansson.md delete mode 100644 demo-vault-v2/person-hiroshi-tanaka.md delete mode 100644 demo-vault-v2/person-james-mitchell.md delete mode 100644 demo-vault-v2/person-james-murphy.md delete mode 100644 demo-vault-v2/person-katja-mueller.md delete mode 100644 demo-vault-v2/person-kenji-tanaka.md delete mode 100644 demo-vault-v2/person-lisa-chen.md delete mode 100644 demo-vault-v2/person-lorenzo-galli.md delete mode 100644 demo-vault-v2/person-lucia-martinez.md delete mode 100644 demo-vault-v2/person-marco-bianchi.md delete mode 100644 demo-vault-v2/person-marco-cecconi.md delete mode 100644 demo-vault-v2/person-marcus-weber.md delete mode 100644 demo-vault-v2/person-maria-colombo.md delete mode 100644 demo-vault-v2/person-marta-pellegrini.md delete mode 100644 demo-vault-v2/person-massimo-artusi.md delete mode 100644 demo-vault-v2/person-matteo-gentile.md delete mode 100644 demo-vault-v2/person-mattia-de-luca.md delete mode 100644 demo-vault-v2/person-michael-brown.md delete mode 100644 demo-vault-v2/person-natalie-chang.md delete mode 100644 demo-vault-v2/person-nicola-fabbri.md delete mode 100644 demo-vault-v2/person-nina-petersen.md delete mode 100644 demo-vault-v2/person-nonna-lucia.md delete mode 100644 demo-vault-v2/person-olivia-martinez.md delete mode 100644 demo-vault-v2/person-paco-furiani.md delete mode 100644 demo-vault-v2/person-paolo-bergamo.md delete mode 100644 demo-vault-v2/person-patrick-nguyen.md delete mode 100644 demo-vault-v2/person-peter-schmidt.md delete mode 100644 demo-vault-v2/person-piergiorgio-conte.md delete mode 100644 demo-vault-v2/person-priya-sharma.md delete mode 100644 demo-vault-v2/person-rachel-green.md delete mode 100644 demo-vault-v2/person-raj-patel.md delete mode 100644 demo-vault-v2/person-roberto-rossi.md delete mode 100644 demo-vault-v2/person-sara-ricci.md delete mode 100644 demo-vault-v2/person-sarah-oconnor.md delete mode 100644 demo-vault-v2/person-silvia-mancini.md delete mode 100644 demo-vault-v2/person-simone-bianchi.md delete mode 100644 demo-vault-v2/person-sophie-laurent.md delete mode 100644 demo-vault-v2/person-stefano-villa.md delete mode 100644 demo-vault-v2/person-thomas-mueller.md delete mode 100644 demo-vault-v2/person-tom-richardson.md delete mode 100644 demo-vault-v2/person-tommaso-greco.md delete mode 100644 demo-vault-v2/person-valentina-rizzo.md delete mode 100644 demo-vault-v2/person-yuki-sato.md delete mode 100644 demo-vault-v2/person-yusuf-osman.md delete mode 100644 demo-vault-v2/person.md delete mode 100644 demo-vault-v2/podcasting-is-relationship-building.md delete mode 100644 demo-vault-v2/procedure-biweekly-1on1-matteo.md delete mode 100644 demo-vault-v2/procedure-biweekly-1on1-paco.md delete mode 100644 demo-vault-v2/procedure-biweekly-1on1-sara.md delete mode 100644 demo-vault-v2/procedure-content-calendar-review.md delete mode 100644 demo-vault-v2/procedure-editorial-review.md delete mode 100644 demo-vault-v2/procedure-evergreen-content-audit.md delete mode 100644 demo-vault-v2/procedure-evergreen-note-writing.md delete mode 100644 demo-vault-v2/procedure-gym-routine.md delete mode 100644 demo-vault-v2/procedure-invoice-processing.md delete mode 100644 demo-vault-v2/procedure-monthly-health-review.md delete mode 100644 demo-vault-v2/procedure-monthly-pillar-planning.md delete mode 100644 demo-vault-v2/procedure-monthly-portfolio-review.md delete mode 100644 demo-vault-v2/procedure-monthly-sponsor-report.md delete mode 100644 demo-vault-v2/procedure-monthly-subscriber-metrics.md delete mode 100644 demo-vault-v2/procedure-newsletter-ab-testing.md delete mode 100644 demo-vault-v2/procedure-newsletter-metrics-weekly.md delete mode 100644 demo-vault-v2/procedure-podcast-analytics.md delete mode 100644 demo-vault-v2/procedure-podcast-editing.md delete mode 100644 demo-vault-v2/procedure-podcast-guest-outreach.md delete mode 100644 demo-vault-v2/procedure-podcast-recording.md delete mode 100644 demo-vault-v2/procedure-podcast-show-notes.md delete mode 100644 demo-vault-v2/procedure-quarterly-financial-planning.md delete mode 100644 demo-vault-v2/procedure-quarterly-team-retro.md delete mode 100644 demo-vault-v2/procedure-race-preparation.md delete mode 100644 demo-vault-v2/procedure-referral-program.md delete mode 100644 demo-vault-v2/procedure-seo-content-optimization.md delete mode 100644 demo-vault-v2/procedure-social-media-scheduling.md delete mode 100644 demo-vault-v2/procedure-sponsor-renewal.md delete mode 100644 demo-vault-v2/procedure-weekly-cycling-block.md delete mode 100644 demo-vault-v2/procedure-weekly-newsletter.md delete mode 100644 demo-vault-v2/procedure-weekly-reading-session.md delete mode 100644 demo-vault-v2/procedure-weekly-team-sync.md delete mode 100644 demo-vault-v2/procedure-welcome-email-sequence.md delete mode 100644 demo-vault-v2/procedure.md delete mode 100644 demo-vault-v2/project.md delete mode 100644 demo-vault-v2/quarter.md delete mode 100644 demo-vault-v2/reading-more-by-reading-better.md delete mode 100644 demo-vault-v2/recovery-week-in-training.md delete mode 100644 demo-vault-v2/refactoring-ideas.md delete mode 100644 demo-vault-v2/refactoring-key-ideas.md delete mode 100644 demo-vault-v2/refactoring-patterns.md delete mode 100644 demo-vault-v2/refactoring.md delete mode 100644 demo-vault-v2/renamed-title-xyz.md delete mode 100644 demo-vault-v2/responsibility-content-production.md delete mode 100644 demo-vault-v2/responsibility-grow-newsletter.md delete mode 100644 demo-vault-v2/responsibility-health-fitness.md delete mode 100644 demo-vault-v2/responsibility-learning.md delete mode 100644 demo-vault-v2/responsibility-personal-finance.md delete mode 100644 demo-vault-v2/responsibility-podcast.md delete mode 100644 demo-vault-v2/responsibility-team-management.md delete mode 100644 demo-vault-v2/responsibility.md delete mode 100644 demo-vault-v2/responsive-rename-test-renamed.md delete mode 100644 demo-vault-v2/save-no-rename-test.md delete mode 100644 demo-vault-v2/should-be-r-renamed.md delete mode 100644 demo-vault-v2/sleeping-more-is-a-superpower.md delete mode 100644 demo-vault-v2/small-teams-scale-through-systems.md delete mode 100644 demo-vault-v2/target-books-24q1.md delete mode 100644 demo-vault-v2/target-books-24q2.md delete mode 100644 demo-vault-v2/target-books-24q3.md delete mode 100644 demo-vault-v2/target-books-24q4.md delete mode 100644 demo-vault-v2/target-books-25q1.md delete mode 100644 demo-vault-v2/target-books-25q2.md delete mode 100644 demo-vault-v2/target-books-25q3.md delete mode 100644 demo-vault-v2/target-books-25q4.md delete mode 100644 demo-vault-v2/target-resting-hr-24q1.md delete mode 100644 demo-vault-v2/target-resting-hr-24q2.md delete mode 100644 demo-vault-v2/target-resting-hr-24q3.md delete mode 100644 demo-vault-v2/target-resting-hr-24q4.md delete mode 100644 demo-vault-v2/target-resting-hr-25q1.md delete mode 100644 demo-vault-v2/target-resting-hr-25q2.md delete mode 100644 demo-vault-v2/target-resting-hr-25q3.md delete mode 100644 demo-vault-v2/target-resting-hr-25q4.md delete mode 100644 demo-vault-v2/target-revenue-24q1.md delete mode 100644 demo-vault-v2/target-revenue-24q2.md delete mode 100644 demo-vault-v2/target-revenue-24q3.md delete mode 100644 demo-vault-v2/target-revenue-24q4.md delete mode 100644 demo-vault-v2/target-revenue-25q1.md delete mode 100644 demo-vault-v2/target-revenue-25q2.md delete mode 100644 demo-vault-v2/target-revenue-25q3.md delete mode 100644 demo-vault-v2/target-revenue-25q4.md delete mode 100644 demo-vault-v2/target-subscribers-24q1.md delete mode 100644 demo-vault-v2/target-subscribers-24q2.md delete mode 100644 demo-vault-v2/target-subscribers-24q3.md delete mode 100644 demo-vault-v2/target-subscribers-24q4.md delete mode 100644 demo-vault-v2/target-subscribers-25q1.md delete mode 100644 demo-vault-v2/target-subscribers-25q2.md delete mode 100644 demo-vault-v2/target-subscribers-25q3.md delete mode 100644 demo-vault-v2/target-subscribers-25q4.md delete mode 100644 demo-vault-v2/target.md delete mode 100644 demo-vault-v2/task-24q1-01.md delete mode 100644 demo-vault-v2/task-24q1-02.md delete mode 100644 demo-vault-v2/task-24q1-03.md delete mode 100644 demo-vault-v2/task-24q2-04.md delete mode 100644 demo-vault-v2/task-24q2-05.md delete mode 100644 demo-vault-v2/task-24q2-06.md delete mode 100644 demo-vault-v2/task-24q2-07.md delete mode 100644 demo-vault-v2/task-24q3-08.md delete mode 100644 demo-vault-v2/task-24q3-09.md delete mode 100644 demo-vault-v2/task-24q3-10.md delete mode 100644 demo-vault-v2/task-24q3-11.md delete mode 100644 demo-vault-v2/task-24q4-12.md delete mode 100644 demo-vault-v2/task-24q4-13.md delete mode 100644 demo-vault-v2/task-24q4-14.md delete mode 100644 demo-vault-v2/task-24q4-15.md delete mode 100644 demo-vault-v2/task-24q4-16.md delete mode 100644 demo-vault-v2/task-25q1-17.md delete mode 100644 demo-vault-v2/task-25q1-18.md delete mode 100644 demo-vault-v2/task-25q1-19.md delete mode 100644 demo-vault-v2/task-25q1-20.md delete mode 100644 demo-vault-v2/task-25q1-21.md delete mode 100644 demo-vault-v2/task-25q1-22.md delete mode 100644 demo-vault-v2/task-25q1-23.md delete mode 100644 demo-vault-v2/task-25q2-24.md delete mode 100644 demo-vault-v2/task-25q2-25.md delete mode 100644 demo-vault-v2/task-25q2-26.md delete mode 100644 demo-vault-v2/task-25q2-27.md delete mode 100644 demo-vault-v2/task-25q2-28.md delete mode 100644 demo-vault-v2/task-25q2-29.md delete mode 100644 demo-vault-v2/task-25q3-30.md delete mode 100644 demo-vault-v2/task-25q3-31.md delete mode 100644 demo-vault-v2/task-25q3-32.md delete mode 100644 demo-vault-v2/task-25q3-33.md delete mode 100644 demo-vault-v2/task-25q3-34.md delete mode 100644 demo-vault-v2/task-25q3-35.md delete mode 100644 demo-vault-v2/task-25q4-36.md delete mode 100644 demo-vault-v2/task-25q4-37.md delete mode 100644 demo-vault-v2/task-25q4-38.md delete mode 100644 demo-vault-v2/task-25q4-39.md delete mode 100644 demo-vault-v2/task-25q4-40.md delete mode 100644 demo-vault-v2/task-25q4-41.md delete mode 100644 demo-vault-v2/task-25q4-42.md delete mode 100644 demo-vault-v2/task-25q4-43.md delete mode 100644 demo-vault-v2/task-25q4-44.md delete mode 100644 demo-vault-v2/task-25q4-45.md delete mode 100644 demo-vault-v2/task.md delete mode 100644 demo-vault-v2/test-note-a.md delete mode 100644 demo-vault-v2/test-note-abc.md delete mode 100644 demo-vault-v2/the-compound-effect-in-knowledge-work.md delete mode 100644 demo-vault-v2/the-real-job-of-a-newsletter.md delete mode 100644 demo-vault-v2/the-saas-metric-that-matters.md delete mode 100644 demo-vault-v2/the-sponsorship-relationship.md delete mode 100644 demo-vault-v2/the-two-types-of-hard.md delete mode 100644 demo-vault-v2/theme/dark.md delete mode 100644 demo-vault-v2/theme/default-theme.md delete mode 100644 demo-vault-v2/theme/default.md delete mode 100644 demo-vault-v2/theme/minimal.md delete mode 100644 demo-vault-v2/topic-ai-ml.md delete mode 100644 demo-vault-v2/topic-b2b-marketing.md delete mode 100644 demo-vault-v2/topic-content-strategy.md delete mode 100644 demo-vault-v2/topic-cooking.md delete mode 100644 demo-vault-v2/topic-cycling-training.md delete mode 100644 demo-vault-v2/topic-data-engineering.md delete mode 100644 demo-vault-v2/topic-developer-tools.md delete mode 100644 demo-vault-v2/topic-italian-startups.md delete mode 100644 demo-vault-v2/topic-mental-health.md delete mode 100644 demo-vault-v2/topic-music-guitar.md delete mode 100644 demo-vault-v2/topic-newsletter-growth.md delete mode 100644 demo-vault-v2/topic-nutrition.md delete mode 100644 demo-vault-v2/topic-open-source.md delete mode 100644 demo-vault-v2/topic-personal-finance.md delete mode 100644 demo-vault-v2/topic-podcasting.md delete mode 100644 demo-vault-v2/topic-product-management.md delete mode 100644 demo-vault-v2/topic-productivity-systems.md delete mode 100644 demo-vault-v2/topic-public-speaking.md delete mode 100644 demo-vault-v2/topic-reading-books.md delete mode 100644 demo-vault-v2/topic-running.md delete mode 100644 demo-vault-v2/topic-saas-business.md delete mode 100644 demo-vault-v2/topic-sleep-recovery.md delete mode 100644 demo-vault-v2/topic-team-leadership.md delete mode 100644 demo-vault-v2/topic-travel.md delete mode 100644 demo-vault-v2/topic.md delete mode 100644 demo-vault-v2/training-load-and-knowledge-work.md delete mode 100644 demo-vault-v2/type/evergreen.md delete mode 100644 demo-vault-v2/type/experiment.md delete mode 100644 demo-vault-v2/type/goal.md delete mode 100644 demo-vault-v2/type/month.md delete mode 100644 demo-vault-v2/type/target.md delete mode 100644 demo-vault-v2/type/task.md delete mode 100644 demo-vault-v2/type/year.md delete mode 100644 demo-vault-v2/untitled-area-10.md delete mode 100644 demo-vault-v2/untitled-area-11.md delete mode 100644 demo-vault-v2/untitled-area-12.md delete mode 100644 demo-vault-v2/untitled-area-13.md delete mode 100644 demo-vault-v2/untitled-area-14.md delete mode 100644 demo-vault-v2/untitled-area-15.md delete mode 100644 demo-vault-v2/untitled-area-16.md delete mode 100644 demo-vault-v2/untitled-area-17.md delete mode 100644 demo-vault-v2/untitled-area-18.md delete mode 100644 demo-vault-v2/untitled-area-2.md delete mode 100644 demo-vault-v2/untitled-area-3.md delete mode 100644 demo-vault-v2/untitled-area-4.md delete mode 100644 demo-vault-v2/untitled-area-5.md delete mode 100644 demo-vault-v2/untitled-area-6.md delete mode 100644 demo-vault-v2/untitled-area-7.md delete mode 100644 demo-vault-v2/untitled-area-8.md delete mode 100644 demo-vault-v2/untitled-area-9.md delete mode 100644 demo-vault-v2/untitled-area.md delete mode 100644 demo-vault-v2/untitled-career-tracks-depend-on-company-shape-2.md delete mode 100644 demo-vault-v2/untitled-experiment-2.md delete mode 100644 demo-vault-v2/untitled-experiment.md delete mode 100644 demo-vault-v2/untitled-not.md delete mode 100644 demo-vault-v2/untitled-note-10.md delete mode 100644 demo-vault-v2/untitled-note-100-md-renamed.md delete mode 100644 demo-vault-v2/untitled-note-101.md delete mode 100644 demo-vault-v2/untitled-note-102.md delete mode 100644 demo-vault-v2/untitled-note-103.md delete mode 100644 demo-vault-v2/untitled-note-104.md delete mode 100644 demo-vault-v2/untitled-note-105-md-renamed.md delete mode 100644 demo-vault-v2/untitled-note-106.md delete mode 100644 demo-vault-v2/untitled-note-107.md delete mode 100644 demo-vault-v2/untitled-note-108.md delete mode 100644 demo-vault-v2/untitled-note-109.md delete mode 100644 demo-vault-v2/untitled-note-11.md delete mode 100644 demo-vault-v2/untitled-note-110-md-renamed.md delete mode 100644 demo-vault-v2/untitled-note-111.md delete mode 100644 demo-vault-v2/untitled-note-112.md delete mode 100644 demo-vault-v2/untitled-note-113.md delete mode 100644 demo-vault-v2/untitled-note-114.md delete mode 100644 demo-vault-v2/untitled-note-115-md-renamed.md delete mode 100644 demo-vault-v2/untitled-note-116.md delete mode 100644 demo-vault-v2/untitled-note-117.md delete mode 100644 demo-vault-v2/untitled-note-118.md delete mode 100644 demo-vault-v2/untitled-note-119.md delete mode 100644 demo-vault-v2/untitled-note-12.md delete mode 100644 demo-vault-v2/untitled-note-120.md delete mode 100644 demo-vault-v2/untitled-note-121-md-renamed.md delete mode 100644 demo-vault-v2/untitled-note-122.md delete mode 100644 demo-vault-v2/untitled-note-123.md delete mode 100644 demo-vault-v2/untitled-note-124.md delete mode 100644 demo-vault-v2/untitled-note-125.md delete mode 100644 demo-vault-v2/untitled-note-126.md delete mode 100644 demo-vault-v2/untitled-note-127-md-renamed.md delete mode 100644 demo-vault-v2/untitled-note-128.md delete mode 100644 demo-vault-v2/untitled-note-129.md delete mode 100644 demo-vault-v2/untitled-note-13.md delete mode 100644 demo-vault-v2/untitled-note-130.md delete mode 100644 demo-vault-v2/untitled-note-131.md delete mode 100644 demo-vault-v2/untitled-note-132-md-renamed.md delete mode 100644 demo-vault-v2/untitled-note-133.md delete mode 100644 demo-vault-v2/untitled-note-134.md delete mode 100644 demo-vault-v2/untitled-note-135.md delete mode 100644 demo-vault-v2/untitled-note-136.md delete mode 100644 demo-vault-v2/untitled-note-137-md-renamed.md delete mode 100644 demo-vault-v2/untitled-note-138.md delete mode 100644 demo-vault-v2/untitled-note-139.md delete mode 100644 demo-vault-v2/untitled-note-14.md delete mode 100644 demo-vault-v2/untitled-note-140.md delete mode 100644 demo-vault-v2/untitled-note-141.md delete mode 100644 demo-vault-v2/untitled-note-142-md-renamed.md delete mode 100644 demo-vault-v2/untitled-note-143.md delete mode 100644 demo-vault-v2/untitled-note-144.md delete mode 100644 demo-vault-v2/untitled-note-145.md delete mode 100644 demo-vault-v2/untitled-note-146.md delete mode 100644 demo-vault-v2/untitled-note-147.md delete mode 100644 demo-vault-v2/untitled-note-148-md-renamed.md delete mode 100644 demo-vault-v2/untitled-note-149.md delete mode 100644 demo-vault-v2/untitled-note-15-md-renamed.md delete mode 100644 demo-vault-v2/untitled-note-150.md delete mode 100644 demo-vault-v2/untitled-note-151.md delete mode 100644 demo-vault-v2/untitled-note-152.md delete mode 100644 demo-vault-v2/untitled-note-153-md-renamed.md delete mode 100644 demo-vault-v2/untitled-note-154.md delete mode 100644 demo-vault-v2/untitled-note-155.md delete mode 100644 demo-vault-v2/untitled-note-156.md delete mode 100644 demo-vault-v2/untitled-note-157.md delete mode 100644 demo-vault-v2/untitled-note-158-md-renamed.md delete mode 100644 demo-vault-v2/untitled-note-159.md delete mode 100644 demo-vault-v2/untitled-note-16.md delete mode 100644 demo-vault-v2/untitled-note-160.md delete mode 100644 demo-vault-v2/untitled-note-161.md delete mode 100644 demo-vault-v2/untitled-note-162.md delete mode 100644 demo-vault-v2/untitled-note-163-md-renamed.md delete mode 100644 demo-vault-v2/untitled-note-164.md delete mode 100644 demo-vault-v2/untitled-note-165.md delete mode 100644 demo-vault-v2/untitled-note-166.md delete mode 100644 demo-vault-v2/untitled-note-167.md delete mode 100644 demo-vault-v2/untitled-note-168-md-renamed.md delete mode 100644 demo-vault-v2/untitled-note-169.md delete mode 100644 demo-vault-v2/untitled-note-17.md delete mode 100644 demo-vault-v2/untitled-note-170.md delete mode 100644 demo-vault-v2/untitled-note-171.md delete mode 100644 demo-vault-v2/untitled-note-172.md delete mode 100644 demo-vault-v2/untitled-note-173-md-renamed.md delete mode 100644 demo-vault-v2/untitled-note-174.md delete mode 100644 demo-vault-v2/untitled-note-175.md delete mode 100644 demo-vault-v2/untitled-note-176.md delete mode 100644 demo-vault-v2/untitled-note-177.md delete mode 100644 demo-vault-v2/untitled-note-1775473305.md delete mode 100644 demo-vault-v2/untitled-note-1775473680.md delete mode 100644 demo-vault-v2/untitled-note-1775473969.md delete mode 100644 demo-vault-v2/untitled-note-1775496473.md delete mode 100644 demo-vault-v2/untitled-note-1775496825.md delete mode 100644 demo-vault-v2/untitled-note-1775497099.md delete mode 100644 demo-vault-v2/untitled-note-1775541952.md delete mode 100644 demo-vault-v2/untitled-note-1775542285.md delete mode 100644 demo-vault-v2/untitled-note-1775542291.md delete mode 100644 demo-vault-v2/untitled-note-1775542296.md delete mode 100644 demo-vault-v2/untitled-note-1775542431.md delete mode 100644 demo-vault-v2/untitled-note-1775542439.md delete mode 100644 demo-vault-v2/untitled-note-1775542446.md delete mode 100644 demo-vault-v2/untitled-note-1775542459.md delete mode 100644 demo-vault-v2/untitled-note-1775542467.md delete mode 100644 demo-vault-v2/untitled-note-1775542474.md delete mode 100644 demo-vault-v2/untitled-note-1775542676.md delete mode 100644 demo-vault-v2/untitled-note-1775542684.md delete mode 100644 demo-vault-v2/untitled-note-1775542692.md delete mode 100644 demo-vault-v2/untitled-note-1775542700.md delete mode 100644 demo-vault-v2/untitled-note-1775542708.md delete mode 100644 demo-vault-v2/untitled-note-1775542716-renamed.md delete mode 100644 demo-vault-v2/untitled-note-1775542923.md delete mode 100644 demo-vault-v2/untitled-note-1775542931.md delete mode 100644 demo-vault-v2/untitled-note-1775542938.md delete mode 100644 demo-vault-v2/untitled-note-1775542951.md delete mode 100644 demo-vault-v2/untitled-note-1775542959.md delete mode 100644 demo-vault-v2/untitled-note-1775542967.md delete mode 100644 demo-vault-v2/untitled-note-1775542981.md delete mode 100644 demo-vault-v2/untitled-note-178-md-renamed.md delete mode 100644 demo-vault-v2/untitled-note-179.md delete mode 100644 demo-vault-v2/untitled-note-18.md delete mode 100644 demo-vault-v2/untitled-note-180.md delete mode 100644 demo-vault-v2/untitled-note-181.md delete mode 100644 demo-vault-v2/untitled-note-182.md delete mode 100644 demo-vault-v2/untitled-note-183-md-renamed.md delete mode 100644 demo-vault-v2/untitled-note-184.md delete mode 100644 demo-vault-v2/untitled-note-185.md delete mode 100644 demo-vault-v2/untitled-note-186.md delete mode 100644 demo-vault-v2/untitled-note-187.md delete mode 100644 demo-vault-v2/untitled-note-188.md delete mode 100644 demo-vault-v2/untitled-note-189-md-renamed.md delete mode 100644 demo-vault-v2/untitled-note-19.md delete mode 100644 demo-vault-v2/untitled-note-190.md delete mode 100644 demo-vault-v2/untitled-note-191.md delete mode 100644 demo-vault-v2/untitled-note-192.md delete mode 100644 demo-vault-v2/untitled-note-193.md delete mode 100644 demo-vault-v2/untitled-note-194.md delete mode 100644 demo-vault-v2/untitled-note-195untitled-note-195-md-renamed.md delete mode 100644 demo-vault-v2/untitled-note-196.md delete mode 100644 demo-vault-v2/untitled-note-197.md delete mode 100644 demo-vault-v2/untitled-note-198.md delete mode 100644 demo-vault-v2/untitled-note-199.md delete mode 100644 demo-vault-v2/untitled-note-2.md delete mode 100644 demo-vault-v2/untitled-note-20.md delete mode 100644 demo-vault-v2/untitled-note-200untitled-note-200-md-renamed.md delete mode 100644 demo-vault-v2/untitled-note-201.md delete mode 100644 demo-vault-v2/untitled-note-202.md delete mode 100644 demo-vault-v2/untitled-note-203.md delete mode 100644 demo-vault-v2/untitled-note-204.md delete mode 100644 demo-vault-v2/untitled-note-205untitled-note-205-md-renamed.md delete mode 100644 demo-vault-v2/untitled-note-206.md delete mode 100644 demo-vault-v2/untitled-note-207.md delete mode 100644 demo-vault-v2/untitled-note-208.md delete mode 100644 demo-vault-v2/untitled-note-209.md delete mode 100644 demo-vault-v2/untitled-note-21.md delete mode 100644 demo-vault-v2/untitled-note-210untitled-note-210-md-renamed.md delete mode 100644 demo-vault-v2/untitled-note-211.md delete mode 100644 demo-vault-v2/untitled-note-212.md delete mode 100644 demo-vault-v2/untitled-note-213.md delete mode 100644 demo-vault-v2/untitled-note-214.md delete mode 100644 demo-vault-v2/untitled-note-215-renamed.md delete mode 100644 demo-vault-v2/untitled-note-216.md delete mode 100644 demo-vault-v2/untitled-note-217.md delete mode 100644 demo-vault-v2/untitled-note-218.md delete mode 100644 demo-vault-v2/untitled-note-219.md delete mode 100644 demo-vault-v2/untitled-note-22-md-renamed.md delete mode 100644 demo-vault-v2/untitled-note-220-renamed.md delete mode 100644 demo-vault-v2/untitled-note-221.md delete mode 100644 demo-vault-v2/untitled-note-222.md delete mode 100644 demo-vault-v2/untitled-note-223.md delete mode 100644 demo-vault-v2/untitled-note-224.md delete mode 100644 demo-vault-v2/untitled-note-225.md delete mode 100644 demo-vault-v2/untitled-note-226-renamed.md delete mode 100644 demo-vault-v2/untitled-note-227.md delete mode 100644 demo-vault-v2/untitled-note-228.md delete mode 100644 demo-vault-v2/untitled-note-229.md delete mode 100644 demo-vault-v2/untitled-note-23.md delete mode 100644 demo-vault-v2/untitled-note-230.md delete mode 100644 demo-vault-v2/untitled-note-231-renamed.md delete mode 100644 demo-vault-v2/untitled-note-232.md delete mode 100644 demo-vault-v2/untitled-note-233.md delete mode 100644 demo-vault-v2/untitled-note-234.md delete mode 100644 demo-vault-v2/untitled-note-235.md delete mode 100644 demo-vault-v2/untitled-note-236-renamed.md delete mode 100644 demo-vault-v2/untitled-note-237.md delete mode 100644 demo-vault-v2/untitled-note-238.md delete mode 100644 demo-vault-v2/untitled-note-239.md delete mode 100644 demo-vault-v2/untitled-note-24.md delete mode 100644 demo-vault-v2/untitled-note-240.md delete mode 100644 demo-vault-v2/untitled-note-241-renamed.md delete mode 100644 demo-vault-v2/untitled-note-242.md delete mode 100644 demo-vault-v2/untitled-note-243.md delete mode 100644 demo-vault-v2/untitled-note-244.md delete mode 100644 demo-vault-v2/untitled-note-245.md delete mode 100644 demo-vault-v2/untitled-note-246-renamed.md delete mode 100644 demo-vault-v2/untitled-note-247.md delete mode 100644 demo-vault-v2/untitled-note-248.md delete mode 100644 demo-vault-v2/untitled-note-249.md delete mode 100644 demo-vault-v2/untitled-note-25.md delete mode 100644 demo-vault-v2/untitled-note-250.md delete mode 100644 demo-vault-v2/untitled-note-251.md delete mode 100644 demo-vault-v2/untitled-note-252.md delete mode 100644 demo-vault-v2/untitled-note-253.md delete mode 100644 demo-vault-v2/untitled-note-254-renamed.md delete mode 100644 demo-vault-v2/untitled-note-255.md delete mode 100644 demo-vault-v2/untitled-note-256.md delete mode 100644 demo-vault-v2/untitled-note-257.md delete mode 100644 demo-vault-v2/untitled-note-258.md delete mode 100644 demo-vault-v2/untitled-note-259.md delete mode 100644 demo-vault-v2/untitled-note-26-md-renamed.md delete mode 100644 demo-vault-v2/untitled-note-260-renamed.md delete mode 100644 demo-vault-v2/untitled-note-261.md delete mode 100644 demo-vault-v2/untitled-note-262.md delete mode 100644 demo-vault-v2/untitled-note-263.md delete mode 100644 demo-vault-v2/untitled-note-264.md delete mode 100644 demo-vault-v2/untitled-note-265.md delete mode 100644 demo-vault-v2/untitled-note-266-renamed.md delete mode 100644 demo-vault-v2/untitled-note-267.md delete mode 100644 demo-vault-v2/untitled-note-268.md delete mode 100644 demo-vault-v2/untitled-note-269.md delete mode 100644 demo-vault-v2/untitled-note-27.md delete mode 100644 demo-vault-v2/untitled-note-270.md delete mode 100644 demo-vault-v2/untitled-note-271-renamed.md delete mode 100644 demo-vault-v2/untitled-note-272.md delete mode 100644 demo-vault-v2/untitled-note-273.md delete mode 100644 demo-vault-v2/untitled-note-274.md delete mode 100644 demo-vault-v2/untitled-note-275.md delete mode 100644 demo-vault-v2/untitled-note-276.md delete mode 100644 demo-vault-v2/untitled-note-277.md delete mode 100644 demo-vault-v2/untitled-note-278.md delete mode 100644 demo-vault-v2/untitled-note-279.md delete mode 100644 demo-vault-v2/untitled-note-28.md delete mode 100644 demo-vault-v2/untitled-note-280.md delete mode 100644 demo-vault-v2/untitled-note-281-renamed.md delete mode 100644 demo-vault-v2/untitled-note-282.md delete mode 100644 demo-vault-v2/untitled-note-283.md delete mode 100644 demo-vault-v2/untitled-note-284.md delete mode 100644 demo-vault-v2/untitled-note-285-renamed.md delete mode 100644 demo-vault-v2/untitled-note-286.md delete mode 100644 demo-vault-v2/untitled-note-287.md delete mode 100644 demo-vault-v2/untitled-note-288.md delete mode 100644 demo-vault-v2/untitled-note-289.md delete mode 100644 demo-vault-v2/untitled-note-29.md delete mode 100644 demo-vault-v2/untitled-note-290-renamed.md delete mode 100644 demo-vault-v2/untitled-note-291.md delete mode 100644 demo-vault-v2/untitled-note-292.md delete mode 100644 demo-vault-v2/untitled-note-293.md delete mode 100644 demo-vault-v2/untitled-note-294.md delete mode 100644 demo-vault-v2/untitled-note-295.md delete mode 100644 demo-vault-v2/untitled-note-296-renamed.md delete mode 100644 demo-vault-v2/untitled-note-297.md delete mode 100644 demo-vault-v2/untitled-note-298.md delete mode 100644 demo-vault-v2/untitled-note-299.md delete mode 100644 demo-vault-v2/untitled-note-3.md delete mode 100644 demo-vault-v2/untitled-note-30-md-renamed.md delete mode 100644 demo-vault-v2/untitled-note-300.md delete mode 100644 demo-vault-v2/untitled-note-301-renamed.md delete mode 100644 demo-vault-v2/untitled-note-302.md delete mode 100644 demo-vault-v2/untitled-note-303.md delete mode 100644 demo-vault-v2/untitled-note-304.md delete mode 100644 demo-vault-v2/untitled-note-305.md delete mode 100644 demo-vault-v2/untitled-note-306-renamed.md delete mode 100644 demo-vault-v2/untitled-note-307.md delete mode 100644 demo-vault-v2/untitled-note-308.md delete mode 100644 demo-vault-v2/untitled-note-309.md delete mode 100644 demo-vault-v2/untitled-note-31.md delete mode 100644 demo-vault-v2/untitled-note-310.md delete mode 100644 demo-vault-v2/untitled-note-311-renamed.md delete mode 100644 demo-vault-v2/untitled-note-312.md delete mode 100644 demo-vault-v2/untitled-note-313.md delete mode 100644 demo-vault-v2/untitled-note-314.md delete mode 100644 demo-vault-v2/untitled-note-315.md delete mode 100644 demo-vault-v2/untitled-note-316.md delete mode 100644 demo-vault-v2/untitled-note-317.md delete mode 100644 demo-vault-v2/untitled-note-318.md delete mode 100644 demo-vault-v2/untitled-note-319-renamed.md delete mode 100644 demo-vault-v2/untitled-note-32.md delete mode 100644 demo-vault-v2/untitled-note-320.md delete mode 100644 demo-vault-v2/untitled-note-321.md delete mode 100644 demo-vault-v2/untitled-note-322.md delete mode 100644 demo-vault-v2/untitled-note-323-renamed.md delete mode 100644 demo-vault-v2/untitled-note-324.md delete mode 100644 demo-vault-v2/untitled-note-325.md delete mode 100644 demo-vault-v2/untitled-note-326.md delete mode 100644 demo-vault-v2/untitled-note-327.md delete mode 100644 demo-vault-v2/untitled-note-328-renamed.md delete mode 100644 demo-vault-v2/untitled-note-329.md delete mode 100644 demo-vault-v2/untitled-note-33.md delete mode 100644 demo-vault-v2/untitled-note-330.md delete mode 100644 demo-vault-v2/untitled-note-331.md delete mode 100644 demo-vault-v2/untitled-note-332.md delete mode 100644 demo-vault-v2/untitled-note-333-renamed.md delete mode 100644 demo-vault-v2/untitled-note-334-renamed.md delete mode 100644 demo-vault-v2/untitled-note-335.md delete mode 100644 demo-vault-v2/untitled-note-336.md delete mode 100644 demo-vault-v2/untitled-note-337.md delete mode 100644 demo-vault-v2/untitled-note-338-renamed.md delete mode 100644 demo-vault-v2/untitled-note-339.md delete mode 100644 demo-vault-v2/untitled-note-34-md-renamed.md delete mode 100644 demo-vault-v2/untitled-note-340.md delete mode 100644 demo-vault-v2/untitled-note-341.md delete mode 100644 demo-vault-v2/untitled-note-342.md delete mode 100644 demo-vault-v2/untitled-note-343.md delete mode 100644 demo-vault-v2/untitled-note-344-renamed.md delete mode 100644 demo-vault-v2/untitled-note-346.md delete mode 100644 demo-vault-v2/untitled-note-347.md delete mode 100644 demo-vault-v2/untitled-note-348.md delete mode 100644 demo-vault-v2/untitled-note-349.md delete mode 100644 demo-vault-v2/untitled-note-35.md delete mode 100644 demo-vault-v2/untitled-note-350.md delete mode 100644 demo-vault-v2/untitled-note-351.md delete mode 100644 demo-vault-v2/untitled-note-352.md delete mode 100644 demo-vault-v2/untitled-note-353-renamed.md delete mode 100644 demo-vault-v2/untitled-note-354.md delete mode 100644 demo-vault-v2/untitled-note-355.md delete mode 100644 demo-vault-v2/untitled-note-356.md delete mode 100644 demo-vault-v2/untitled-note-357.md delete mode 100644 demo-vault-v2/untitled-note-359-renamed.md delete mode 100644 demo-vault-v2/untitled-note-36.md delete mode 100644 demo-vault-v2/untitled-note-361.md delete mode 100644 demo-vault-v2/untitled-note-37.md delete mode 100644 demo-vault-v2/untitled-note-38-md-renamed.md delete mode 100644 demo-vault-v2/untitled-note-39.md delete mode 100644 demo-vault-v2/untitled-note-40.md delete mode 100644 demo-vault-v2/untitled-note-41.md delete mode 100644 demo-vault-v2/untitled-note-42.md delete mode 100644 demo-vault-v2/untitled-note-43-md-renamed.md delete mode 100644 demo-vault-v2/untitled-note-44.md delete mode 100644 demo-vault-v2/untitled-note-45.md delete mode 100644 demo-vault-v2/untitled-note-46.md delete mode 100644 demo-vault-v2/untitled-note-47-md-renamed.md delete mode 100644 demo-vault-v2/untitled-note-48.md delete mode 100644 demo-vault-v2/untitled-note-49.md delete mode 100644 demo-vault-v2/untitled-note-5.md delete mode 100644 demo-vault-v2/untitled-note-50.md delete mode 100644 demo-vault-v2/untitled-note-51-md-renamed.md delete mode 100644 demo-vault-v2/untitled-note-52.md delete mode 100644 demo-vault-v2/untitled-note-53.md delete mode 100644 demo-vault-v2/untitled-note-54.md delete mode 100644 demo-vault-v2/untitled-note-55.md delete mode 100644 demo-vault-v2/untitled-note-56-md-renamed.md delete mode 100644 demo-vault-v2/untitled-note-57.md delete mode 100644 demo-vault-v2/untitled-note-58.md delete mode 100644 demo-vault-v2/untitled-note-59.md delete mode 100644 demo-vault-v2/untitled-note-6.md delete mode 100644 demo-vault-v2/untitled-note-60-md-renamed.md delete mode 100644 demo-vault-v2/untitled-note-61.md delete mode 100644 demo-vault-v2/untitled-note-62.md delete mode 100644 demo-vault-v2/untitled-note-63.md delete mode 100644 demo-vault-v2/untitled-note-64.md delete mode 100644 demo-vault-v2/untitled-note-65.md delete mode 100644 demo-vault-v2/untitled-note-66.md delete mode 100644 demo-vault-v2/untitled-note-67.md delete mode 100644 demo-vault-v2/untitled-note-68-md-renamed.md delete mode 100644 demo-vault-v2/untitled-note-69.md delete mode 100644 demo-vault-v2/untitled-note-7.md delete mode 100644 demo-vault-v2/untitled-note-70.md delete mode 100644 demo-vault-v2/untitled-note-71.md delete mode 100644 demo-vault-v2/untitled-note-72.md delete mode 100644 demo-vault-v2/untitled-note-73.md delete mode 100644 demo-vault-v2/untitled-note-74-md-renamed.md delete mode 100644 demo-vault-v2/untitled-note-75.md delete mode 100644 demo-vault-v2/untitled-note-76.md delete mode 100644 demo-vault-v2/untitled-note-77.md delete mode 100644 demo-vault-v2/untitled-note-78.md delete mode 100644 demo-vault-v2/untitled-note-79.md delete mode 100644 demo-vault-v2/untitled-note-8.md delete mode 100644 demo-vault-v2/untitled-note-80.md delete mode 100644 demo-vault-v2/untitled-note-81.md delete mode 100644 demo-vault-v2/untitled-note-82.md delete mode 100644 demo-vault-v2/untitled-note-83-md-renamed.md delete mode 100644 demo-vault-v2/untitled-note-84.md delete mode 100644 demo-vault-v2/untitled-note-85.md delete mode 100644 demo-vault-v2/untitled-note-86.md delete mode 100644 demo-vault-v2/untitled-note-87-md-renamed.md delete mode 100644 demo-vault-v2/untitled-note-88.md delete mode 100644 demo-vault-v2/untitled-note-89.md delete mode 100644 demo-vault-v2/untitled-note-9.md delete mode 100644 demo-vault-v2/untitled-note-90.md delete mode 100644 demo-vault-v2/untitled-note-91.md delete mode 100644 demo-vault-v2/untitled-note-92-md-renamed.md delete mode 100644 demo-vault-v2/untitled-note-93.md delete mode 100644 demo-vault-v2/untitled-note-94.md delete mode 100644 demo-vault-v2/untitled-note-95.md delete mode 100644 demo-vault-v2/untitled-note-96.md delete mode 100644 demo-vault-v2/untitled-note-97.md delete mode 100644 demo-vault-v2/untitled-note-98.md delete mode 100644 demo-vault-v2/untitled-note-99.md delete mode 100644 demo-vault-v2/untitled-note.md delete mode 100644 demo-vault-v2/untitled-project-10.md delete mode 100644 demo-vault-v2/untitled-project-11.md delete mode 100644 demo-vault-v2/untitled-project-12.md delete mode 100644 demo-vault-v2/untitled-project-13.md delete mode 100644 demo-vault-v2/untitled-project-14.md delete mode 100644 demo-vault-v2/untitled-project-15.md delete mode 100644 demo-vault-v2/untitled-project-16.md delete mode 100644 demo-vault-v2/untitled-project-17.md delete mode 100644 demo-vault-v2/untitled-project-1775473964.md delete mode 100644 demo-vault-v2/untitled-project-1775497094.md delete mode 100644 demo-vault-v2/untitled-project-1775542975.md delete mode 100644 demo-vault-v2/untitled-project-18.md delete mode 100644 demo-vault-v2/untitled-project-19.md delete mode 100644 demo-vault-v2/untitled-project-2.md delete mode 100644 demo-vault-v2/untitled-project-20.md delete mode 100644 demo-vault-v2/untitled-project-21.md delete mode 100644 demo-vault-v2/untitled-project-22.md delete mode 100644 demo-vault-v2/untitled-project-23.md delete mode 100644 demo-vault-v2/untitled-project-24.md delete mode 100644 demo-vault-v2/untitled-project-25.md delete mode 100644 demo-vault-v2/untitled-project-26.md delete mode 100644 demo-vault-v2/untitled-project-27.md delete mode 100644 demo-vault-v2/untitled-project-28.md delete mode 100644 demo-vault-v2/untitled-project-29.md delete mode 100644 demo-vault-v2/untitled-project-3.md delete mode 100644 demo-vault-v2/untitled-project-30.md delete mode 100644 demo-vault-v2/untitled-project-31.md delete mode 100644 demo-vault-v2/untitled-project-32.md delete mode 100644 demo-vault-v2/untitled-project-33.md delete mode 100644 demo-vault-v2/untitled-project-34.md delete mode 100644 demo-vault-v2/untitled-project-35.md delete mode 100644 demo-vault-v2/untitled-project-36.md delete mode 100644 demo-vault-v2/untitled-project-37.md delete mode 100644 demo-vault-v2/untitled-project-38.md delete mode 100644 demo-vault-v2/untitled-project-39.md delete mode 100644 demo-vault-v2/untitled-project-4.md delete mode 100644 demo-vault-v2/untitled-project-40.md delete mode 100644 demo-vault-v2/untitled-project-41.md delete mode 100644 demo-vault-v2/untitled-project-42.md delete mode 100644 demo-vault-v2/untitled-project-43.md delete mode 100644 demo-vault-v2/untitled-project-44.md delete mode 100644 demo-vault-v2/untitled-project-45.md delete mode 100644 demo-vault-v2/untitled-project-46.md delete mode 100644 demo-vault-v2/untitled-project-47.md delete mode 100644 demo-vault-v2/untitled-project-48.md delete mode 100644 demo-vault-v2/untitled-project-49.md delete mode 100644 demo-vault-v2/untitled-project-5.md delete mode 100644 demo-vault-v2/untitled-project-50.md delete mode 100644 demo-vault-v2/untitled-project-51.md delete mode 100644 demo-vault-v2/untitled-project-52.md delete mode 100644 demo-vault-v2/untitled-project-53.md delete mode 100644 demo-vault-v2/untitled-project-54.md delete mode 100644 demo-vault-v2/untitled-project-55.md delete mode 100644 demo-vault-v2/untitled-project-56.md delete mode 100644 demo-vault-v2/untitled-project-57.md delete mode 100644 demo-vault-v2/untitled-project-58.md delete mode 100644 demo-vault-v2/untitled-project-6.md delete mode 100644 demo-vault-v2/untitled-project-7.md delete mode 100644 demo-vault-v2/untitled-project-8.md delete mode 100644 demo-vault-v2/untitled-project-9.md delete mode 100644 demo-vault-v2/untitled-project.md delete mode 100644 demo-vault-v2/untitled-save-no-rename-test.md delete mode 100644 demo-vault-v2/untitled-test-note-abc-2-renamed.md delete mode 100644 demo-vault-v2/untitled-test-note-abc-2.md delete mode 100644 demo-vault-v2/untitled-test-note-abc.md delete mode 100644 demo-vault-v2/what-makes-a-good-podcast-guest.md delete mode 100644 demo-vault-v2/why-b2b-newsletters-work.md delete mode 100644 demo-vault-v2/wikilinks-qa-test.md create mode 100644 demo-vault-v2/writing-weekly-rhythm.md delete mode 100644 demo-vault-v2/year.md diff --git a/.gitignore b/.gitignore index b5c1250b..55104136 100644 --- a/.gitignore +++ b/.gitignore @@ -32,6 +32,7 @@ dist-ssr # Demo vault and helper scripts demo-vault/ +generated-fixtures/ select_demo_notes*.py final_selection.py diff --git a/demo-vault-v2/.fixture-manifest.json b/demo-vault-v2/.fixture-manifest.json new file mode 100644 index 00000000..ee77194f --- /dev/null +++ b/demo-vault-v2/.fixture-manifest.json @@ -0,0 +1,55 @@ +{ + "name": "Tolaria QA fixture", + "purpose": "Curated local vault for native QA and developer flows. This is not the public Getting Started starter vault.", + "large_fixture": { + "generator": "python3 scripts/generate_demo_vault.py", + "default_output": "generated-fixtures/demo-vault-large" + }, + "scenarios": [ + { + "id": "exact-match-search", + "reason": "Quick Open should rank the exact title 'Writing' above prefix matches.", + "files": [ + "topic-writing.md", + "writing-for-clarity-vs-writing-for-credit.md", + "writing-weekly-rhythm.md" + ] + }, + { + "id": "relationship-rendering", + "reason": "Relationship keys should render in the inspector instead of as plain properties.", + "files": [ + "responsibility-sponsorships.md", + "measure-sponsorship-mrr.md", + "measure-close-rate.md", + "procedure-quarterly-sponsor-outreach.md", + "procedure-sponsor-onboarding.md", + "24q4-laputa-start.md", + "24q4.md", + "person-luca-rossi.md" + ] + }, + { + "id": "project-navigation", + "reason": "Projects, quarters, and a saved view give keyboard QA a compact but representative browsing path.", + "files": [ + "24q4.md", + "25q1.md", + "25q2.md", + "24q4-laputa-start.md", + "25q1-laputa-v1.md", + "25q2-laputa-v2.md", + "views/active-projects.yml" + ] + }, + { + "id": "attachment-rendering", + "reason": "A note with a real binary attachment keeps image/block QA anchored to the fixture.", + "files": [ + "laputa-qa-reference.md", + "attachments/laputa-reference.png" + ] + } + ] +} + diff --git a/demo-vault-v2/.gitignore b/demo-vault-v2/.gitignore index 4b8e0699..9ff2df4e 100644 --- a/demo-vault-v2/.gitignore +++ b/demo-vault-v2/.gitignore @@ -1,16 +1,5 @@ -# Laputa app files (machine-specific, never commit) -.laputa/settings.json - -# macOS +.git/ +.laputa/ +.laputa-index.json .DS_Store -.AppleDouble -.LSOverride -# Thumbnails -._* - -# Editors -.vscode/ -.idea/ -*.swp -*.swo diff --git a/demo-vault-v2/.laputa/settings.json b/demo-vault-v2/.laputa/settings.json deleted file mode 100644 index 9ecbd575..00000000 --- a/demo-vault-v2/.laputa/settings.json +++ /dev/null @@ -1,3 +0,0 @@ -{ - "theme": null -} \ No newline at end of file diff --git a/demo-vault-v2/2024-01.md b/demo-vault-v2/2024-01.md deleted file mode 100644 index 67ccf4a3..00000000 --- a/demo-vault-v2/2024-01.md +++ /dev/null @@ -1,29 +0,0 @@ ---- -aliases: ["January 2024"] -Is A: Month -Created at: "2024-01-28" -Belongs to: "[[24q1]]" -Rating: "😄" ---- -# January 2024 - -## Focus - -- Set up [[24q1-launch-sponsorship-packages]] — research pricing, structure tiers, draft sponsor-facing materials -- Begin planning [[24q1-podcast-season-1]] — outline first 6 episode topics, research recording setup -- Map out cycling calendar for the year ([[24q1-plan-cycling-season]]) - -## Highlights - -- Finalized the three-tier sponsorship model (Gold, Silver, Bronze) with [[person-matteo-cellini]] — spent two full days on pricing research and competitive analysis -- Ordered podcast equipment: Shure SM7B, Focusrite Scarlett, pop filter — the home studio is starting to take shape -- Newsletter hit 35.4k subscribers, steady organic growth from December's end-of-year content -- Read "The Hard Thing About Hard Things" and "Measure What Matters" — both immediately applicable to how I think about Refactoring's goals -- Registered for Nove Colli (May) and submitted lottery application for Maratona dles Dolomites (July) -- Started base training: 380 km this month, mostly zone 2 rides on the trainer - -## Reflections - -January always feels like a slow month, but this one was quietly productive. The sponsorship package work was the kind of unglamorous, strategic task that doesn't produce visible output but sets up everything that follows. [[person-matteo-cellini]] and I went back and forth on pricing for days — we kept second-guessing whether Gold at EUR 2.8k/issue was too high. In the end, we decided to launch at that price and see what happens. Worst case, we adjust. - -The podcast planning was fun but nerve-wracking. I've been talking about launching a podcast for over a year, and now it's actually happening. The equipment is here, the topics are outlined. No more excuses. February is recording month. diff --git a/demo-vault-v2/2024-02.md b/demo-vault-v2/2024-02.md deleted file mode 100644 index 8ea80542..00000000 --- a/demo-vault-v2/2024-02.md +++ /dev/null @@ -1,29 +0,0 @@ ---- -aliases: ["February 2024"] -Is A: Month -Created at: "2024-02-28" -Belongs to: "[[24q1]]" -Rating: "🤩" ---- -# February 2024 - -## Focus - -- Record and edit first batch of podcast episodes ([[24q1-podcast-season-1]]) -- Launch [[24q1-launch-sponsorship-packages]] to existing sponsors and new prospects -- Start [[24q1-redesign-newsletter-template]] with improved mobile layout - -## Highlights - -- Recorded episodes 1-4 of [[24q1-podcast-season-1]] in a single weekend marathon session — exhausting but exhilarating -- Published Episode 1 ("Why Engineering Managers Fail") — 600 downloads in the first 48 hours, way above my modest expectations -- [[24q1-launch-sponsorship-packages]] went live — sent the new pricing deck to 12 existing sponsors and 20 cold prospects -- [[person-matteo-cellini]] closed the first Gold sponsor deal within a week of launch — a DevOps platform company, EUR 2.8k/issue for 4 issues -- Newsletter grew to 36.1k subscribers — the podcast announcement email had a 52% open rate -- First draft of [[24q1-redesign-newsletter-template]] ready — cleaner header, better CTA placement, responsive images - -## Reflections - -This was the month everything started to feel real. Hearing my own voice on the podcast for the first time was deeply uncomfortable — I hated it, edited obsessively, almost scrapped the whole thing. But then the downloads came in, and the feedback was overwhelmingly positive. People said things like "it feels like you're explaining this to me over coffee." That's exactly the vibe I was going for. Maybe my voice isn't so bad after all. - -The sponsorship launch going well this quickly was a confidence boost. [[person-matteo-cellini]] deserves the credit — he positioned the packages perfectly and his follow-up game is relentless. Having a second Gold sponsor in the pipeline already makes the Q2 revenue forecast look strong. February was a month where preparation met opportunity. Best month in a while. diff --git a/demo-vault-v2/2024-03.md b/demo-vault-v2/2024-03.md deleted file mode 100644 index 6a91ef47..00000000 --- a/demo-vault-v2/2024-03.md +++ /dev/null @@ -1,29 +0,0 @@ ---- -aliases: ["March 2024"] -Is A: Month -Created at: "2024-03-28" -Belongs to: "[[24q1]]" -Rating: "😄" ---- -# March 2024 - -## Focus - -- Finalize [[24q1-redesign-newsletter-template]] and ship to production -- Continue podcast momentum with episodes 3-4 release -- Set up [[24q1-set-investing-framework]] — automate monthly contributions - -## Highlights - -- Shipped [[24q1-redesign-newsletter-template]] — [[measure-open-rate]] improved by 1.5pp in the first two weeks, click-through rate also up -- Released episodes 3 and 4 of [[24q1-podcast-season-1]] — Episode 3 on "Technical Debt as a Strategic Tool" got shared widely on LinkedIn -- Set up [[24q1-set-investing-framework]]: automated monthly DCA into VWCE (global ETF), topped up emergency fund to 6 months of expenses -- Newsletter crossed 37k subscribers — strong organic growth from podcast cross-promotion -- Got accepted for Maratona dles Dolomites via lottery — both gran fondos now confirmed for [[2024-complete-two-gran-fondos]] -- Cycling: 420 km this month, first outdoor rides of the season — legs feel good after months on the trainer - -## Reflections - -March wrapped up Q1 nicely. The newsletter template redesign was one of those things that seems small but makes a real difference — the new layout just looks more professional, and the numbers back it up. Sometimes the boring improvements are the most impactful. - -Getting into Maratona via lottery was a huge relief. I'd been anxious about it for weeks. Now both races are locked in and the training plan has clear milestones. The investing framework is the kind of "set it and forget it" system I love — one less thing to think about each month. [[24q1]] was a strong quarter overall. Time to execute in Q2. diff --git a/demo-vault-v2/2024-04.md b/demo-vault-v2/2024-04.md deleted file mode 100644 index 4d93ef9c..00000000 --- a/demo-vault-v2/2024-04.md +++ /dev/null @@ -1,30 +0,0 @@ ---- -aliases: ["April 2024"] -Is A: Month -Created at: "2024-04-28" -Belongs to: "[[24q2]]" -Rating: "😄" ---- -# April 2024 - -## Focus - -- Kick off [[24q2-hire-editor]] search — post the role, screen candidates, run test edits -- Start [[24q2-10-pillar-articles]] strategy — identify topics, outline first 3 articles -- Begin building [[24q2-sponsor-crm]] in Notion - -## Highlights - -- Posted the freelance editor role on LinkedIn and two newsletter job boards — received 45 applications in two weeks -- Shortlisted 5 editor candidates and ran paid test edits on a sample newsletter issue — two stood out clearly -- Outlined the first 3 [[24q2-10-pillar-articles]]: "Staff Engineer vs. Manager," "How to Prioritize Technical Debt," and "The 1:1 Framework That Actually Works" -- Started building [[24q2-sponsor-crm]] in Notion — pipeline view, deal stages, revenue tracking -- [[person-paco-furiani]] took over invoicing — freed up ~3 hours/month of admin work -- Newsletter at 38.5k subscribers — steady growth, no spikes -- Cycling: ramping up volume — 480 km this month, including a 120 km long ride in Tuscany - -## Reflections - -A transitional month. Not flashy, but the groundwork being laid is important. The editor hire is going to be transformative if I get it right — spending Sunday evenings editing is my least favorite part of the workflow. The test edits revealed that most applicants can fix grammar but few can preserve voice. The two finalists both "got" the Refactoring tone, which is rare. - -The pillar articles strategy feels right. Instead of grinding out a new topic every week, investing in fewer, deeper pieces that can rank on search and compound over time. It's a bet on long-term value over short-term output. [[person-paco-furiani]] quietly picking up the invoicing was a small moment that mattered more than it looked — the team is starting to function as a team, not just a collection of helpers. diff --git a/demo-vault-v2/2024-05.md b/demo-vault-v2/2024-05.md deleted file mode 100644 index f7d7a5c9..00000000 --- a/demo-vault-v2/2024-05.md +++ /dev/null @@ -1,30 +0,0 @@ ---- -aliases: ["May 2024"] -Is A: Month -Created at: "2024-05-28" -Belongs to: "[[24q2]]" -Rating: "😐" ---- -# May 2024 - -## Focus - -- Finalize [[24q2-hire-editor]] — make the offer, onboard -- Publish first batch of [[24q2-10-pillar-articles]] -- Race Nove Colli ([[24q2-spring-gran-fondo]]) - -## Highlights - -- Hired the editor — she starts full-time in June, doing first-pass editing on every newsletter issue -- Published "Staff Engineer vs. Manager" — it went semi-viral on LinkedIn, drove 800+ new subscribers in a single week -- Completed Nove Colli ([[24q2-spring-gran-fondo]]) in 7h42m — finished but bonked hard on the fourth climb due to heat -- [[24q2-build-podcast-landing-page]] kicked off — basic wireframes done, episodes 1-6 now need a proper home -- Newsletter hit 40.5k subscribers — the pillar article spike was significant - -## Reflections - -Mixed feelings this month. The editor hire is great news — having someone who can handle the first pass means I can focus on the ideas rather than the polish. But Nove Colli was humbling. The heat in Romagna was 34 degrees, and I didn't manage my nutrition well enough. Bonking on the fourth climb — legs completely empty, seeing spots — was scary. I sat on the side of the road for 10 minutes eating everything in my pockets before I could continue. - -I finished, and that matters. But the time was disappointing. Lesson learned: nutrition strategy needs to be as planned as the training itself. The Maratona in July will be at altitude, which adds another variable. Need to take fueling much more seriously. - -The "Staff Engineer vs. Manager" article reminded me why I do this. The number of engineers who DMed me saying "I needed to read this three years ago" — that's the impact I care about. More than subscriber counts. diff --git a/demo-vault-v2/2024-06.md b/demo-vault-v2/2024-06.md deleted file mode 100644 index 62cede24..00000000 --- a/demo-vault-v2/2024-06.md +++ /dev/null @@ -1,32 +0,0 @@ ---- -aliases: ["June 2024"] -Is A: Month -Created at: "2024-06-28" -Belongs to: "[[24q2]]" -Rating: "🤩" ---- -# June 2024 - -## Focus - -- Ship [[24q2-build-podcast-landing-page]] with full episode archive -- Complete [[24q2-sponsor-crm]] and migrate all sponsor data -- Ramp up training for Maratona dles Dolomites in July - -## Highlights - -- Launched [[24q2-build-podcast-landing-page]] — clean design, Apple/Spotify links, full show notes for all 8 episodes — podcast downloads crossed 5k/month -- [[24q2-sponsor-crm]] completed and live — all pipeline data migrated from scattered spreadsheets, [[person-matteo-cellini]] now tracks everything in one place -- Published 3 more [[24q2-10-pillar-articles]] including "How to Prioritize Technical Debt" (32k views) -- Editor fully onboarded and in rhythm — first-pass drafts arriving every Monday morning, quality is excellent -- Newsletter hit 42k subscribers — right on pace for [[2024-reach-50k-subscribers]] -- [[measure-sponsorship-mrr]] reached EUR 8.2k — strong Q2 performance -- Cycling: biggest training month yet — 620 km, including two back-to-back long rides simulating Maratona's profile - -## Reflections - -June was one of those months where everything clicks. The podcast landing page looks professional and is already converting visitors to subscribers. The sponsor CRM might be the most impactful internal tool we've built — no more "where's that sponsor contract?" emails. [[person-matteo-cellini]] went from managing sponsors in his head to having a proper pipeline view. - -The editor hire is already paying off. She catches things I'd miss after staring at my own words for hours. The Monday morning routine of reviewing a clean draft instead of starting from a rough mess is a genuine quality-of-life improvement. My writing quality is actually better because I can focus on substance rather than mechanics. - -Training is going well. The two back-to-back long rides (140 km + 120 km over a weekend) left me wrecked but confident. If I can do that in Tuscany's hills, the Dolomites are within reach. Bring on July. diff --git a/demo-vault-v2/2024-07.md b/demo-vault-v2/2024-07.md deleted file mode 100644 index 2bff1c46..00000000 --- a/demo-vault-v2/2024-07.md +++ /dev/null @@ -1,29 +0,0 @@ ---- -aliases: ["July 2024"] -Is A: Month -Created at: "2024-07-28" -Belongs to: "[[24q3]]" -Rating: "😄" ---- -# July 2024 - -## Focus - -- Race Maratona dles Dolomites — the big one for [[2024-complete-two-gran-fondos]] -- Begin [[24q3-premium-tier]] planning — pricing, content strategy, platform selection -- Launch [[24q3-summer-reading-sprint]] — target 8 books in July-August - -## Highlights - -- Completed Maratona dles Dolomites in 9h15m — Passo Giau at dawn was transcendent, Fedaia was brutal, but finished strong — [[2024-complete-two-gran-fondos]] achieved -- Started planning [[24q3-premium-tier]]: researched Substack paid, Ghost memberships, and Stripe checkout — leaning toward custom Stripe integration for flexibility -- Read "An Elegant Puzzle" and "Team Topologies" — both excellent, immediately useful for newsletter content -- Newsletter at 43.5k subscribers — summer slowdown typical but growth still positive -- Began outlining [[24q3-codemotion-talk]] abstract — submitted "Scaling Engineering Culture" as the proposed topic -- [[measure-podcast-downloads]] hit 6.5k/month — organic growth without new episodes (between seasons) - -## Reflections - -Maratona was the cycling highlight of the year, maybe of my life so far. 138 km through the Dolomites, 4,200m of climbing, starting in the dark at 6am in Corvara. The Sella and Gardena passes were hard, Campolongo was deceptively steep, but Giau — Giau was magical. The sunrise hitting the peaks as I climbed the final switchbacks, the silence broken only by breathing and chain noise. I didn't care about my time. I was just there. - -The post-race week was recovery — both physical and mental. After months of structured training and race anxiety, there's a strange emptiness when the goal is achieved. I channeled that into reading and planning the premium tier. Pricing is the hardest part: too cheap and it devalues the content, too expensive and the audience is too small to sustain it. Need to think about this more in August. diff --git a/demo-vault-v2/2024-08.md b/demo-vault-v2/2024-08.md deleted file mode 100644 index 708d88c1..00000000 --- a/demo-vault-v2/2024-08.md +++ /dev/null @@ -1,29 +0,0 @@ ---- -aliases: ["August 2024"] -Is A: Month -Created at: "2024-08-28" -Belongs to: "[[24q3]]" -Rating: "🤩" ---- -# August 2024 - -## Focus - -- Build and launch [[24q3-premium-tier]] — set up payments, create first premium content -- Continue [[24q3-summer-reading-sprint]] — deep reading weeks with lighter work schedule -- Record first episodes of [[24q3-podcast-season-2]] - -## Highlights - -- Launched [[24q3-premium-tier]] at EUR 8/month — 120 subscribers in the first week, bumped to EUR 12/month after seeing strong demand -- Premium content: published first deep-dive case study ("How Stripe Scales Engineering Teams") and announced monthly AMA calls -- Finished [[24q3-summer-reading-sprint]]: 8 books total across July-August, including "The Ride of a Lifetime" and "Thinking in Systems" -- Recorded episodes 13-16 of [[24q3-podcast-season-2]] — new guest interview format with [[person-sara-ricci]] coordinating guests -- Newsletter at 44.8k — August is always slow, but premium launch generated a subscriber bump -- [[person-matteo-cellini]] began outreach for [[24q3-new-sponsor-verticals]] — targeting cloud and DevOps companies - -## Reflections - -August is usually my favorite work month — lighter pace, longer mornings, room to think. This year it was productive in a different way. The premium tier launch felt risky: asking people to pay for something they'd been getting for free. But the response was encouraging. 120 subscribers in the first week validated the hypothesis. Bumping the price from EUR 8 to EUR 12 was a gut call based on [[person-matteo-cellini]]'s advice — "if people are subscribing this fast, you're underpriced." He was right. - -The reading sprint was exactly what I needed. Eight books in two months, with time to actually think about each one. "Thinking in Systems" by Donella Meadows is probably the most underrated book in the business canon — it changed how I think about feedback loops in newsletter growth. Summer energy is real — I feel recharged and ready for an intense September. diff --git a/demo-vault-v2/2024-09.md b/demo-vault-v2/2024-09.md deleted file mode 100644 index 7d336f70..00000000 --- a/demo-vault-v2/2024-09.md +++ /dev/null @@ -1,29 +0,0 @@ ---- -aliases: ["September 2024"] -Is A: Month -Created at: "2024-09-28" -Belongs to: "[[24q3]]" -Rating: "😄" ---- -# September 2024 - -## Focus - -- Deliver [[24q3-codemotion-talk]] at Codemotion Milan -- Push premium tier to 300+ subscribers -- Close Q3 strong on sponsor pipeline ([[24q3-new-sponsor-verticals]]) - -## Highlights - -- Delivered [[24q3-codemotion-talk]] on "Scaling Engineering Culture" to ~400 attendees — standing ovation, 3 inbound sponsor inquiries within a week -- [[24q3-premium-tier]] hit 320 paid subscribers — AMA calls proving to be the most valued feature -- [[24q3-new-sponsor-verticals]]: [[person-matteo-cellini]] closed deals with two DevOps platform companies, diversifying the sponsor base -- Released episodes 17-20 of [[24q3-podcast-season-2]] — guest episode with a VP Engineering at a Series D startup was the most downloaded yet -- Newsletter hit 46k subscribers — Codemotion exposure plus podcast cross-promotion driving growth -- [[measure-sponsorship-mrr]] reached EUR 10.1k — first time crossing EUR 10k - -## Reflections - -Codemotion was terrifying and wonderful. I spent the week before rehearsing obsessively, convinced I'd forget my lines or that the audience wouldn't care. None of that happened. The talk landed well, the Q&A was engaged, and the hallway conversations afterward were some of the best I've had this year. Three sponsors reaching out unsolicited — that's the power of being on stage in front of your target audience. - -But September also felt like the start of a crunch period. Premium content, podcast production, conference prep, sponsor pipeline — the workload is stacking up. I'm starting to feel the edges of my capacity. [[person-paco-furiani]] flagged that I missed two invoicing deadlines because I was focused on the talk. He's right — I need to stay disciplined about the operational basics even when the creative work is exciting. Heading into Q4, I need to be honest about what I can sustain. diff --git a/demo-vault-v2/2024-10.md b/demo-vault-v2/2024-10.md deleted file mode 100644 index 7e3d1c3e..00000000 --- a/demo-vault-v2/2024-10.md +++ /dev/null @@ -1,28 +0,0 @@ ---- -aliases: ["October 2024"] -Is A: Month -Created at: "2024-10-28" -Belongs to: "[[24q4]]" -Rating: "😐" ---- -# October 2024 - -## Focus - -- Begin [[24q4-laputa-start]] — initial prototype of the PKM tool -- Design [[24q4-annual-review-process]] template -- Start planning [[24q4-black-friday-campaign]] - -## Highlights - -- Started [[24q4-laputa-start]]: Tauri v2 + React scaffold, basic markdown file reading, first pass at YAML frontmatter parsing — spending evenings and weekends on it -- Drafted [[24q4-annual-review-process]] template with quarterly, goal, and project review sections -- [[24q4-black-friday-campaign]] strategy defined: 30% off annual premium, referral bonuses, limited-time offers -- Newsletter at 47.5k subscribers — growth steady but nothing spectacular -- [[person-matteo-cellini]] started building the [[24q4-sponsor-dashboard]] concept — mockups in Figma - -## Reflections - -October was a grind. The post-Codemotion high wore off fast, replaced by the reality of a packed Q4. Starting Laputa was exciting but also a bit reckless — adding a software project on top of everything else. But I couldn't help it. The frustration with existing PKM tools had been building for months, and once I started coding, I couldn't stop. The first time I saw my vault rendered in the four-panel layout, I got that spark you only get when you're building something you genuinely need. - -The newsletter growth plateauing at ~47k is worrying. We need a big push to hit [[2024-reach-50k-subscribers]] by year end. The Black Friday campaign is the obvious lever, but we need it to be genuinely compelling, not just another discount email. [[person-paco-furiani]] suggested adding a community element to the campaign — worth exploring. Energy-wise, I'm running at about 70%. Not burned out, but not firing on all cylinders either. Need to protect sleep and exercise. diff --git a/demo-vault-v2/2024-11.md b/demo-vault-v2/2024-11.md deleted file mode 100644 index dfb3777d..00000000 --- a/demo-vault-v2/2024-11.md +++ /dev/null @@ -1,31 +0,0 @@ ---- -aliases: ["November 2024"] -Is A: Month -Created at: "2024-11-28" -Belongs to: "[[24q4]]" -Rating: "😄" ---- -# November 2024 - -## Focus - -- Execute [[24q4-black-friday-campaign]] — the big push to 50k subscribers -- Ship [[24q4-sponsor-dashboard]] for sponsor self-service metrics -- Continue Laputa development ([[24q4-laputa-start]]) - -## Highlights - -- [[24q4-black-friday-campaign]] was a massive success: 2,800 new subscribers in 10 days, 180 free-to-premium conversions, best campaign ever -- Newsletter crossed 50k subscribers on November 22nd — [[2024-reach-50k-subscribers]] achieved, two months ahead of my mental timeline -- Shipped [[24q4-sponsor-dashboard]] — sponsors can now see impressions, clicks, and conversion data in real-time — [[person-matteo-cellini]] reports dramatically fewer support emails -- Laputa ([[24q4-laputa-start]]) now has working search, type-based navigation, and basic frontmatter editing — using it for my own vault daily -- [[measure-sponsorship-mrr]] hit EUR 11.2k — November renewals came in strong -- Recorded end-of-year reflections episode for the podcast — raw and personal, felt right - -## Reflections - -Crossing 50k subscribers was the defining moment of the month. I remember refreshing the Substack dashboard at 11pm on a Friday, watching the number tick from 49,998 to 50,001. It sounds silly, but I actually teared up a little. Two years ago, 50k felt like a fantasy. The Black Friday campaign was the catalyst, but it only worked because of 11 months of consistent work before it. - -The sponsor dashboard was [[person-matteo-cellini]]'s baby, and he executed it beautifully. Giving sponsors self-serve access to their data is the kind of product thinking that separates a media business from a newsletter. [[person-paco-furiani]] handled the backend automation — pulling data from Substack's API into a clean dashboard. Small team, big impact. - -Laputa is becoming a real tool. I'm using it every day now, and the workflow of navigating my vault through types and relationships is already better than what I had in Obsidian. It's rough around the edges, but the bones are good. Heading into December with real momentum. diff --git a/demo-vault-v2/2024-12.md b/demo-vault-v2/2024-12.md deleted file mode 100644 index 72fb916b..00000000 --- a/demo-vault-v2/2024-12.md +++ /dev/null @@ -1,32 +0,0 @@ ---- -aliases: ["December 2024"] -Is A: Month -Created at: "2024-12-28" -Belongs to: "[[24q4]]" -Rating: "😄" ---- -# December 2024 - -## Focus - -- Run [[24q4-annual-review-process]] — review all goals, projects, and metrics for [[2024]] -- Complete [[24q4-cycling-year-review]] — analyze training data, plan 2025 cycling goals -- Set [[2025]] goals and plan [[25q1]] - -## Highlights - -- Completed [[24q4-annual-review-process]]: reviewed all 4 quarters, 20 projects, and 5 annual goals — documented everything in structured templates -- [[24q4-cycling-year-review]]: 6,200 km total, FTP up 12% YoY, 2 gran fondos completed — decided to target Stelvio for [[2025-ride-stelvio]] -- Set [[2025]] goals: [[2025-reach-85k-subscribers]], [[2025-reach-22k-mrr]], [[2025-ship-laputa]], [[2025-ride-stelvio]], [[2025-read-20-books]] -- Newsletter closed the year at 50.2k subscribers — slight post-Black-Friday churn, but net position is excellent -- [[measure-sponsorship-mrr]] ended at EUR 11.4k — [[2024-double-revenue]] confirmed (was EUR 5.5k in January) -- Read 2 books in December to finish at 26 total — [[2024-read-24-books]] exceeded -- [[person-paco-furiani]] and I sketched out the 2025 operational calendar — quarterly planning cadence locked in - -## Reflections - -December is always reflective, and this one more than most. Sitting down to review [[2024]] in detail, I realized that every major goal was either hit or exceeded. That almost never happens. The newsletter from 35k to 50k. Revenue doubled. Podcast launched and growing. Two gran fondos. 26 books. It was a genuinely great year. - -But the review also surfaced where I was lucky vs. where I was good. The Black Friday campaign was well-executed, but the timing was also favorable — low competition in the engineering leadership newsletter space. The pillar articles strategy worked partly because of SEO tailwinds. I don't want to mistake a rising tide for good swimming. - -Looking ahead to [[2025]], the goals are deliberately ambitious: 85k subscribers, EUR 22k MRR, shipping Laputa as a product, riding Stelvio. These require a different gear than 2024. More team, more systems, less heroics. The cycling review was satisfying — seeing 6,200 km logged, the FTP curve rising, the race results improving — it's the same compounding principle as the newsletter, just applied to watts instead of words. Here's to [[2025]]. diff --git a/demo-vault-v2/2024-complete-two-gran-fondos.md b/demo-vault-v2/2024-complete-two-gran-fondos.md deleted file mode 100644 index b2589061..00000000 --- a/demo-vault-v2/2024-complete-two-gran-fondos.md +++ /dev/null @@ -1,32 +0,0 @@ ---- -aliases: ["Complete Two Gran Fondos"] -Is A: Goal -Belongs to: "[[2024]]" -Status: Done ---- -# Complete Two Gran Fondos - -Cycling is a core part of how I manage energy and sustain focus for the business. Completing two gran fondos in 2024 was about proving that endurance fitness and a demanding content business can coexist, and about setting a physical benchmark for the year tied to [[responsibility-health-fitness]]. - -## Success criteria - -- Finish at least two official gran fondo events (120+ km each) -- Complete both without DNF, regardless of placement -- Maintain consistent training volume of 400+ km/month during the build phase -- No injuries that impact work capacity - -## Key milestones - -- Plan the cycling season and select target events during [[24q1-plan-cycling-season]] -- Build base fitness through structured winter training (Jan-Mar) -- Complete first gran fondo by end of Q2 -- Complete second gran fondo by end of Q3 -- Maintain [[measure-cycling-km-per-month]] above 400 km during peak training months - -## Notes - -- Completed both events successfully: Nove Colli in May and Maratona dles Dolomites in July. -- Training volume averaged 480 km/month from February through July, well above target. -- The structured training plan from [[24q1-plan-cycling-season]] was essential. Without it, the business would have crowded out ride time. -- Key insight: blocking training rides on the calendar like meetings is non-negotiable. Treating fitness as optional leads to skipped sessions. -- This goal set the foundation for the more ambitious [[2025-ride-stelvio]] target. diff --git a/demo-vault-v2/2024-double-revenue.md b/demo-vault-v2/2024-double-revenue.md deleted file mode 100644 index 21572f35..00000000 --- a/demo-vault-v2/2024-double-revenue.md +++ /dev/null @@ -1,34 +0,0 @@ ---- -aliases: ["Double Sponsorship Revenue"] -Is A: Goal -Belongs to: "[[2024]]" -Status: Done ---- -# Double Sponsorship Revenue - -Revenue growth is the clearest signal that the newsletter business is becoming a sustainable long-term venture. Doubling MRR from ~7k to 14k+ in 2024 would prove that the sponsorship model scales with audience growth and that the business can support a small team without requiring a pivot to paid subscriptions or courses. - -## Success criteria - -- Reach 14,000 EUR MRR by December 2024 -- Maintain or increase average deal size (target: 1,200+ EUR per placement) -- Onboard at least 6 new sponsors over the year -- Achieve 80%+ renewal rate on existing sponsor contracts -- Keep [[measure-close-rate]] above 30% on inbound leads - -## Key milestones - -- Launch restructured sponsorship packages with tiered pricing in [[24q1-launch-sponsorship-packages]] -- Build a lightweight CRM to manage pipeline and renewals via [[24q2-sponsor-crm]] -- Hit 10k MRR by end of Q2 (midpoint target) -- Reach 12k MRR by end of Q3 with [[24q3-premium-tier]] upsells -- Close Q4 at 14k+ MRR, with pipeline visibility into Q1 2025 - -## Notes - -- Final MRR in December 2024: approximately 15,200 EUR. Goal exceeded by ~8%. -- The tiered sponsorship packages from [[24q1-launch-sponsorship-packages]] were the single biggest driver. The premium tier accounted for 40% of new revenue. -- [[24q2-sponsor-crm]] was simple (a Notion database) but effective. Having a structured pipeline view reduced missed follow-ups significantly. -- Renewal rate landed at 78%, just below the 80% target. Two sponsors churned due to budget cuts, not dissatisfaction. -- The subscriber growth from [[2024-reach-50k-subscribers]] directly enabled higher pricing. Audience size and engagement metrics are the foundation of sponsorship value. -- This sets the trajectory for [[2025-reach-22k-mrr]], which will require both audience growth and continued pricing optimization. diff --git a/demo-vault-v2/2024-launch-podcast.md b/demo-vault-v2/2024-launch-podcast.md deleted file mode 100644 index ae3e3c1d..00000000 --- a/demo-vault-v2/2024-launch-podcast.md +++ /dev/null @@ -1,34 +0,0 @@ ---- -aliases: ["Launch Refactoring Podcast"] -Is A: Goal -Belongs to: "[[2024]]" -Status: Done ---- -# Launch Refactoring Podcast - -The podcast is the biggest new distribution channel for Refactoring in 2024. Audio content reaches a different audience segment than the newsletter and deepens engagement with existing subscribers. A successful podcast also opens new sponsorship inventory, directly supporting [[2024-double-revenue]] and [[responsibility-sponsorships]]. - -## Success criteria - -- Launch Season 1 by end of Q1 2024 -- Publish at least 20 episodes across two seasons in the year -- Reach 1,000+ downloads per episode by Season 2 -- Secure at least 2 podcast-specific sponsors -- Maintain a sustainable production cadence without degrading newsletter quality - -## Key milestones - -- Produce and launch Season 1 during [[24q1-podcast-season-1]] (8-10 episodes) -- Establish production workflow with [[person-paco-furiani]] handling editing and distribution -- Launch Season 2 during [[24q3-podcast-season-2]] with improved format based on Season 1 feedback -- Track growth via [[measure-podcast-downloads]] and [[measure-podcast-episodes-per-month]] -- Review analytics quarterly using [[procedure-podcast-analytics]] - -## Notes - -- Season 1 launched in March 2024 with 10 episodes. Season 2 launched in August with 12 episodes. Total: 22 episodes, exceeding the 20-episode target. -- Downloads per episode grew from ~400 in Season 1 to ~1,300 by late Season 2. Crossed the 1,000 threshold in episode 16. -- Secured 2 podcast sponsors by Q3, both cross-sold from existing newsletter sponsors. The podcast inventory added approximately 1,800 EUR/month to [[measure-sponsorship-mrr]]. -- Production workflow stabilized by episode 5. [[person-paco-furiani]] now handles end-to-end production with minimal input needed. -- Interview format performed better than solo episodes for downloads. Solo episodes had higher completion rates. -- The podcast is now a permanent channel. Planning [[25q2-podcast-season-3]] to continue momentum into 2025. diff --git a/demo-vault-v2/2024-reach-50k-subscribers.md b/demo-vault-v2/2024-reach-50k-subscribers.md deleted file mode 100644 index a1b8aca3..00000000 --- a/demo-vault-v2/2024-reach-50k-subscribers.md +++ /dev/null @@ -1,34 +0,0 @@ ---- -aliases: ["Reach 50k Subscribers"] -Is A: Goal -Belongs to: "[[2024]]" -Status: Done ---- -# Reach 50k Subscribers - -Subscriber count is the foundational growth metric for the newsletter business. Reaching 50,000 subscribers by end of 2024 would put Refactoring firmly in the top tier of engineering newsletters, enabling premium sponsorship pricing and establishing the audience base needed for future product launches. This goal is the north star for all [[responsibility-grow-newsletter]] efforts. - -## Success criteria - -- End 2024 with 50,000+ total newsletter subscribers -- Maintain monthly net growth of 2,000+ subscribers -- Keep unsubscribe rate below 1.5% per issue -- Achieve organic growth rate of at least 60% (not purely paid acquisition) -- Maintain [[measure-open-rate]] above 45% as the list scales - -## Key milestones - -- Cross 35,000 subscribers by end of Q1, validating early-year growth tactics -- Launch [[24q2-10-pillar-articles]] to drive SEO-based organic acquisition -- Cross 42,000 by mid-year, on pace for the 50k target -- Experiment with [[24q4-linkedin-crossposting]] as an additional growth channel in Q4 -- Hit 50,000 by December with a sustained final push through [[responsibility-grow-newsletter]] - -## Notes - -- Final count: 53,000 subscribers by December 2024. Exceeded target by 6%. -- Organic growth accounted for approximately 65% of new subscribers. Top sources: Twitter/X, SEO from pillar articles, and word-of-mouth referrals. -- The [[24q2-10-pillar-articles]] project was the single biggest organic growth lever. Those 10 articles now account for ~30% of monthly organic signups. -- [[measure-open-rate]] held at 47% even at scale, which is strong for a list this size. This is a key selling point for sponsors. -- LinkedIn cross-posting ([[24q4-linkedin-crossposting]]) added ~150 subscribers directly but had an outsized brand awareness effect. -- The path to [[2025-reach-85k-subscribers]] is clear but will require new channels. Organic growth from existing channels alone will not close the gap. diff --git a/demo-vault-v2/2024-read-24-books.md b/demo-vault-v2/2024-read-24-books.md deleted file mode 100644 index fc46e552..00000000 --- a/demo-vault-v2/2024-read-24-books.md +++ /dev/null @@ -1,33 +0,0 @@ ---- -aliases: ["Read 24 Books in 2024"] -Is A: Goal -Belongs to: "[[2024]]" -Status: Behind ---- -# Read 24 Books in 2024 - -Consistent reading is the primary input for original thinking and content quality. A target of 24 books (2 per month) ensures a steady flow of ideas feeding into newsletter essays, podcast topics, and [[responsibility-learning]]. Falling behind on reading directly correlates with weaker content output. - -## Success criteria - -- Read 24 books by December 31, 2024 (2 per month average) -- Maintain at least 1 book per month even in busy periods -- Track progress via [[measure-books-per-month]] -- At least 50% should be non-fiction relevant to the newsletter (engineering, business, leadership) -- Create at least 5 [[measure-evergreen-notes-created]] from each book - -## Key milestones - -- Establish the reading habit in Q1 with 6 books by March -- Maintain pace through Q2 despite the busy season for [[24q2-10-pillar-articles]] -- Reach 18 books by end of Q3 -- Close the year at 24 by maintaining 2/month in Q4 - -## Notes - -- Final count: 18 books. Missed the 24-book target by 6 books (75% completion). -- Q1 started strong at 7 books, ahead of pace. Q2 dropped to 3 books due to the pillar articles push and podcast launch. -- Q3 recovered to 5 books. Q4 was only 3 books as year-end business priorities took over. -- The shortfall was entirely a time management issue, not a motivation issue. During weeks with heavy content production, reading was the first thing to get cut. -- Adjusted the 2025 target to 20 books ([[2025-read-20-books]]) to be more realistic given current business demands. -- Key insight: audiobooks during cycling training significantly boosted volume. 6 of the 18 books were consumed this way. Will lean into this more in 2025. diff --git a/demo-vault-v2/2024.md b/demo-vault-v2/2024.md deleted file mode 100644 index eface7c3..00000000 --- a/demo-vault-v2/2024.md +++ /dev/null @@ -1,49 +0,0 @@ ---- -aliases: ["2024"] -Is A: Year -Created at: "2024-01-01" -Has: ["[[24q1]]", "[[24q2]]", "[[24q3]]", "[[24q4]]"] ---- -# 2024 - -## Theme - -2024 was the growth year — the year Refactoring went from "successful newsletter" to "real business." At the start of January, I had ~35,000 subscribers, ad-hoc sponsor deals, no podcast, and a vague sense that this could become something bigger. By December, the newsletter had crossed 50k subscribers, revenue had more than doubled, the podcast was a genuine channel, and I had a small team helping me run things. The word that keeps coming back when I think about this year is *professionalization*. - -But 2024 was also the year I stopped being just a content creator and started being a founder. Launching sponsorship packages, hiring an editor, building a sponsor CRM, creating a premium tier — these aren't creative acts, they're business-building acts. And toward the end of the year, starting [[24q4-laputa-start]] added a product dimension that I hadn't anticipated. I ended the year wearing more hats than ever, but feeling more focused than ever. Paradox noted. - -## Highlights - -- Newsletter grew from ~35k to 50k+ subscribers — [[2024-reach-50k-subscribers]] achieved in November -- Revenue more than doubled: [[measure-sponsorship-mrr]] went from EUR 5.5k in January to EUR 11.4k in December — [[2024-double-revenue]] hit -- Launched the podcast in [[24q1]] — grew from 0 to 8k+ downloads/month across two seasons ([[24q1-podcast-season-1]], [[24q3-podcast-season-2]]) -- Shipped [[24q3-premium-tier]] with 320+ paid subscribers by year end -- Completed both gran fondos — Nove Colli ([[24q2-spring-gran-fondo]]) and Maratona dles Dolomites — [[2024-complete-two-gran-fondos]] done -- Published [[24q2-10-pillar-articles]] including "Staff Engineer vs. Manager" (50k+ views) -- Delivered [[24q3-codemotion-talk]] to ~400 attendees — first major conference appearance -- Built the team: [[person-matteo-cellini]] on partnerships, [[person-paco-furiani]] on operations, freelance editor for content -- [[24q4-black-friday-campaign]] drove 2,800 new subscribers in 10 days -- Started building [[24q4-laputa-start]] — the PKM tool I'd been dreaming about for years - -## By the numbers - -- **Subscribers**: 35k to 50.2k (+43%) -- **Sponsorship MRR**: EUR 5.5k to EUR 11.4k (+107%) -- **Podcast downloads**: 0 to 8.2k/month (24 episodes across 2 seasons) -- **Premium subscribers**: 0 to 320 (launched in [[24q3]]) -- **Books read**: 26 — [[2024-read-24-books]] exceeded by 2 -- **Cycling km**: 6,200 km — [[measure-cycling-km-per-month]] averaged ~517 km -- **Gran fondos**: 2/2 — Nove Colli (7h42m), Maratona dles Dolomites (9h15m) -- **Open rate**: [[measure-open-rate]] averaged 44.2%, up from 41.8% in 2023 -- **Conference talks**: 1 (Codemotion Milan) -- **Total revenue**: ~EUR 155k (sponsorships + premium + speaking) - -## Reflections - -Looking back at 2024, the thing I'm most proud of isn't any single achievement — it's the system. At the start of the year, everything ran through me. By December, [[person-matteo-cellini]] was closing sponsor deals I never even saw, [[person-paco-furiani]] was handling invoicing and logistics autonomously, and the editor was shipping polished drafts on a weekly cadence. I built leverage, not just output. - -The podcast was the surprise of the year. I'd been so anxious about launching it — imposter syndrome about my speaking voice, worry about production quality, fear that nobody would listen. But the format I landed on (20-minute focused deep dives) resonated immediately. Season 2 adding guest interviews was the right evolution. By December, the podcast was driving subscriber growth, sponsor interest, and content ideas in a way I hadn't anticipated. It's now an essential pillar, not a side experiment. - -The premium tier launch in Q3 validated something I'd been unsure about: that people would pay for curated, structured content even when the free version was already high quality. The 320 subscribers at EUR 12/month represent a small but meaningful revenue stream — and more importantly, a direct relationship with my most engaged readers. The AMA calls are gold for understanding what engineering leaders actually struggle with. - -If I'm being honest about what didn't go well: I pushed too hard in Q3. The combination of the premium launch, Codemotion, and Maratona training left me running on fumes by October. The Black Friday campaign in Q4 was successful but felt mechanical — I was going through motions rather than creating with energy. That's a warning sign I need to heed going into [[2025]]. The business can scale, but my energy can't scale linearly with it. I need to hire more, delegate more, and protect creative time more aggressively. The Laputa project ([[24q4-laputa-start]]) is a wildcard heading into next year — it could be a distraction or it could be the most important thing I build. We'll see. diff --git a/demo-vault-v2/2025-01.md b/demo-vault-v2/2025-01.md deleted file mode 100644 index 8087d5a6..00000000 --- a/demo-vault-v2/2025-01.md +++ /dev/null @@ -1,29 +0,0 @@ ---- -aliases: ["January 2025"] -Is A: Month -Created at: "2025-01-28" -Belongs to: "[[25q1]]" -Rating: "😄" ---- -# January 2025 - -## Focus - -- Begin [[25q1-laputa-v1]] development sprint — four-panel layout, markdown rendering, search -- Plan [[25q1-rate-increase]] strategy with [[person-matteo-cellini]] -- Start [[25q1-strength-program]] — 3x/week gym sessions - -## Highlights - -- Kicked off [[25q1-laputa-v1]] development with a focused 2-week sprint — four-panel layout working, markdown rendering with frontmatter extraction functional -- Researched competitor sponsor rates and prepared [[25q1-rate-increase]] proposal with [[person-matteo-cellini]] — planning to raise Gold from EUR 2.8k to EUR 3.5k/issue -- Started [[25q1-strength-program]]: working with a coach, 3x/week focusing on core stability and leg strength for cycling -- Newsletter at 51.8k subscribers — steady organic growth to start the year -- Read "Build" by Tony Fadell — excellent on product thinking, relevant to Laputa -- Cycling: 320 km, mostly indoor on the trainer — January weather in northern Italy is brutal - -## Reflections - -January is always a reset month, and this one felt especially deliberate. Coming off the high of [[2024]], I wanted to start [[2025]] with intention rather than momentum alone. The Laputa development sprint was intense — coding every evening after the newsletter work was done, often until midnight. But seeing the four-panel layout come alive with my own vault data was deeply motivating. It's scratching an itch that's been bothering me for years. - -The strength program is humbling. My first session, I could barely hold a plank for 60 seconds. Years of cycling have given me the cardiovascular fitness of someone 10 years younger and the upper body strength of someone 10 years older. The coach just smiled and said "we'll fix that." Three weeks in, everything hurts, but I can already feel the difference in posture and stability on the bike. diff --git a/demo-vault-v2/2025-02.md b/demo-vault-v2/2025-02.md deleted file mode 100644 index c3bf66e5..00000000 --- a/demo-vault-v2/2025-02.md +++ /dev/null @@ -1,29 +0,0 @@ ---- -aliases: ["February 2025"] -Is A: Month -Created at: "2025-02-28" -Belongs to: "[[25q1]]" -Rating: "🤩" ---- -# February 2025 - -## Focus - -- Execute [[25q1-rate-increase]] — communicate new pricing to sponsors -- Launch [[25q1-referral-program]] — design tiers, set up tracking -- Continue [[25q1-laputa-v1]] — add search and navigation features - -## Highlights - -- Executed [[25q1-rate-increase]]: communicated new Gold rate (EUR 3.5k/issue) to all sponsors — 9 out of 10 renewed without pushback, one negotiated a 6-month lock at the old rate -- Launched [[25q1-referral-program]] with three tiers: 3 referrals (exclusive article), 10 referrals (premium trial), 25 referrals (1:1 call) — 1,100 referral subscribers in the first 3 weeks -- [[25q1-laputa-v1]] now has full-text search, type-based sidebar navigation, and keyboard shortcuts — my daily driver for vault browsing -- [[measure-sponsorship-mrr]] jumped to EUR 13.5k after rate increase — significant lift with minimal churn -- Newsletter at 54.2k subscribers — referral program providing a noticeable acceleration -- [[person-matteo-cellini]] onboarded a new enterprise sponsor (cloud infrastructure company) at the higher rate — first deal at the new pricing - -## Reflections - -This was the month I learned that raising prices is one of the highest-leverage moves in a business. We spent weeks agonizing over the rate increase, running scenarios, worrying about sponsor churn. And then... almost nothing happened. Sponsors said "sure, sounds fair" and renewed. One even said "honestly, I'm surprised you didn't raise earlier." That's the curse of the bootstrapper mindset — you're so grateful for every dollar that you forget to charge what you're worth. - -The referral program is generating genuine excitement. Seeing readers actively sharing Refactoring with their colleagues because they want the rewards — it's word-of-mouth at scale. The 1:1 call tier at 25 referrals is clever because it creates a personal connection between me and my most engaged readers. Three people earned it in the first month, and those calls were some of the best conversations I've had about engineering leadership. February was excellent. Everything is tracking. diff --git a/demo-vault-v2/2025-03.md b/demo-vault-v2/2025-03.md deleted file mode 100644 index c5113658..00000000 --- a/demo-vault-v2/2025-03.md +++ /dev/null @@ -1,30 +0,0 @@ ---- -aliases: ["March 2025"] -Is A: Month -Created at: "2025-03-28" -Belongs to: "[[25q1]]" -Rating: "😄" ---- -# March 2025 - -## Focus - -- Complete [[25q1-newsletter-seo-sprint]] — optimize top 15 articles for search -- Ship [[25q1-laputa-v1]] as internal release — feature-complete for personal use -- First outdoor rides of the season - -## Highlights - -- Completed [[25q1-newsletter-seo-sprint]]: optimized 15 pillar articles with updated titles, meta descriptions, internal linking, and structured data — organic traffic up 40% by month end -- [[25q1-laputa-v1]] shipped as "internal v1" — search, navigation, frontmatter editing, and property panel all working — vault has 9,000+ files and performs well -- Referral program ([[25q1-referral-program]]) running strong — 3,200 total referral subscribers in Q1 -- Newsletter hit 56k subscribers — [[25q1]] delivered well above expectations -- [[25q1-strength-program]] paying off — can hold a 2-minute plank now, leg press up 40%, climbing power noticeably improved -- First outdoor ride of the season: 85 km along the Po River, 12 degrees, absolutely beautiful -- [[measure-sponsorship-mrr]] at EUR 14.2k — strong close to [[25q1]] - -## Reflections - -March was the month where Q1 came together. The SEO sprint was unglamorous work — rewriting titles, adding alt text to images, building internal link maps — but the results were immediate. One article ("How to Run Effective 1:1s") went from page 3 to the #2 result for its target keyword. That single article now brings in 200+ organic subscribers per month. The compounding effect of SEO on a content business is underrated. - -Shipping Laputa v1 felt like a real milestone, even if I'm the only user. It's not pretty, it has bugs, and the graph view is more confusing than helpful. But it works. I browse my vault in it every day — types on the left, notes in the middle, properties on the right. The workflow is faster than Obsidian for my use case, and that's all the validation I need to keep building. Next up: bidirectional linking and a better graph. Closing [[25q1]] feeling strong and focused. [[25q2]] is going to be intense. diff --git a/demo-vault-v2/2025-04.md b/demo-vault-v2/2025-04.md deleted file mode 100644 index 3f20e2a1..00000000 --- a/demo-vault-v2/2025-04.md +++ /dev/null @@ -1,31 +0,0 @@ ---- -aliases: ["April 2025"] -Is A: Month -Created at: "2025-04-28" -Belongs to: "[[25q2]]" -Rating: "😄" ---- -# April 2025 - -## Focus - -- Begin [[25q2-podcast-season-3]] production — new "Tactical Tuesday" format alongside regular episodes -- Start [[25q2-laputa-v2]] development — bidirectional linking, graph view improvements -- Plan [[25q2-team-retreat]] logistics for late May - -## Highlights - -- Recorded first 4 episodes of [[25q2-podcast-season-3]] including the debut "Tactical Tuesday" — 15-minute actionable episodes dropping every Tuesday -- Started [[25q2-laputa-v2]] with bidirectional linking engine — the backlinks panel is already transforming how I navigate between notes -- [[25q2-team-retreat]] booked: farmhouse outside Siena, 3 days in late May, agenda drafted with [[person-paco-furiani]] -- Newsletter at 58.5k subscribers — growth accelerating, referral program still compounding -- Published a deep-dive on "The Architecture of Engineering Onboarding" — 28k views, widely shared on HackerNews -- Cycling: 480 km, first real outdoor training block — spring is here and the motivation is high - -## Reflections - -April felt like the start of the real work for [[25q2]]. The "Tactical Tuesday" format for the podcast was an experiment born from reader feedback — people kept saying "I love the deep dives but sometimes I just need a quick actionable takeaway." So we're doing both: deep dives on Thursdays, tactical tips on Tuesdays. Early numbers are promising — the short episodes have a higher completion rate. - -The Laputa work on bidirectional linking was technically challenging but incredibly satisfying. Clicking on a note and seeing all the other notes that link to it, without having to manually maintain those connections — it's the kind of feature that makes you wonder how you ever worked without it. My vault is starting to feel alive, like a knowledge graph I can actually traverse. - -Planning the retreat with [[person-paco-furiani]] was a reminder of how much the team dynamic matters. We're four people working remotely, mostly asynchronously. That works for execution, but not for alignment. Three days together in Tuscany should fix that. diff --git a/demo-vault-v2/2025-05.md b/demo-vault-v2/2025-05.md deleted file mode 100644 index 1daf589e..00000000 --- a/demo-vault-v2/2025-05.md +++ /dev/null @@ -1,30 +0,0 @@ ---- -aliases: ["May 2025"] -Is A: Month -Created at: "2025-05-28" -Belongs to: "[[25q2]]" -Rating: "😐" ---- -# May 2025 - -## Focus - -- Execute [[25q2-team-retreat]] in Tuscany -- Push toward [[25q2-reach-70k]] — growth sprint with coordinated content + referral push -- Continue [[25q2-laputa-v2]] — graph view and frontmatter editing - -## Highlights - -- [[25q2-team-retreat]] in Siena was transformational — 3 days of strategy, bonding, and cooking together with [[person-matteo-cellini]], [[person-paco-furiani]], and [[person-sara-ricci]] -- The community idea emerged from a dinner conversation at the retreat — [[person-sara-ricci]] pitched it, everyone immediately saw the potential -- Newsletter at 64k subscribers — growth strong but the 70k target for June feels aggressive -- [[25q2-laputa-v2]] graph view working but confusing at scale — need to rethink the visual density for 9,000+ nodes -- Two newsletter issues underperformed — open rates dipped below 40% for the first time this year - -## Reflections - -The retreat was everything I hoped for and more. There's a moment on the second evening — the four of us on the terrace, bottles of Brunello open, whiteboarding H2 plans on a flip chart — where it hit me that this is a real team, not just a collection of freelancers. [[person-sara-ricci]]'s community pitch was brilliant in its simplicity: "Your readers already help each other in reply-all email chains. Give them a proper space to do it." That became [[25q3-community-launch]]. - -But May was also the first month this year where I felt like I was slipping. Two issues with below-40% open rates is a warning sign. The topics weren't wrong, but the subject lines were lazy — I wrote them in a rush. In a newsletter business, subject lines are the product as much as the content. Sloppy subject lines = sloppy product. Need to get disciplined about this again. - -The Laputa graph view at 9,000 nodes is essentially unusable — just a hairball of connections. I need to rethink the approach: maybe cluster by type, maybe progressive disclosure, maybe skip the full graph entirely and focus on local neighborhoods. Technical challenge, but also a product design challenge. Not everything that works at 100 nodes works at 10,000. diff --git a/demo-vault-v2/2025-06.md b/demo-vault-v2/2025-06.md deleted file mode 100644 index 3463df57..00000000 --- a/demo-vault-v2/2025-06.md +++ /dev/null @@ -1,32 +0,0 @@ ---- -aliases: ["June 2025"] -Is A: Month -Created at: "2025-06-28" -Belongs to: "[[25q2]]" -Rating: "🤩" ---- -# June 2025 - -## Focus - -- Hit [[25q2-reach-70k]] subscribers -- Ship [[25q2-laputa-v2]] with refined graph view and improved frontmatter editing -- Start planning [[25q2-dolomites-trip]] logistics for late June - -## Highlights - -- Hit [[25q2-reach-70k]] subscribers on June 12th — two weeks ahead of schedule, driven by two viral LinkedIn posts and the referral program -- Shipped [[25q2-laputa-v2]]: bidirectional linking, local graph view (neighborhood-based, not full graph), improved frontmatter editing — feels like a real product now -- Completed [[25q2-dolomites-trip]]: 4 days, 5 passes, 380 km with three friends — Passo Fedaia, Pordoi, Sella, Gardena, Campolongo -- [[25q2-podcast-season-3]] "Tactical Tuesday" format growing fast — 14k total downloads/month -- [[measure-sponsorship-mrr]] hit EUR 17.5k — two new enterprise sponsors signed -- Premium tier reached 680 paying subscribers — AMA calls now have 40+ attendees -- Two pillar articles syndicated by InfoQ and The New Stack — drove ~4k new subscribers - -## Reflections - -June was the peak of [[25q2]] — everything came together. Hitting 70k subscribers two weeks early felt effortless, which is a sign that the flywheel is genuinely spinning now. The LinkedIn posts that went viral weren't planned; they were honest reflections on engineering leadership challenges that resonated. Authenticity scales, apparently. - -The Dolomites trip was the cycling highlight of the year so far. Four days of pure mountain riding with friends — the kind of trip where you forget about metrics and just pedal. Passo Fedaia at sunset, the Marmolada glacier turning orange overhead, was a moment I'll remember forever. My legs felt strong — the [[25q1-strength-program]] is paying dividends in climbing power and stability. - -Shipping Laputa v2 with the local graph view was the right call. Instead of showing all 9,000 nodes (useless hairball), it shows the current note plus 2 degrees of connection. Clean, useful, navigable. Sometimes the best product decisions are about what you don't show. Heading into Q3 with serious momentum and slightly too much on my plate. diff --git a/demo-vault-v2/2025-07.md b/demo-vault-v2/2025-07.md deleted file mode 100644 index 1ffd1f99..00000000 --- a/demo-vault-v2/2025-07.md +++ /dev/null @@ -1,31 +0,0 @@ ---- -aliases: ["July 2025"] -Is A: Month -Created at: "2025-07-28" -Belongs to: "[[25q3]]" -Rating: "😄" ---- -# July 2025 - -## Focus - -- Begin [[25q3-ebook]] production — compile, edit, and design "The Engineering Leader's Playbook" -- Prepare for [[25q3-community-launch]] on Circle — set up platform, invite founding members -- Enter [[25q3-peak-training]] block for Stelvio in August - -## Highlights - -- [[25q3-ebook]] first draft completed — 12 chapters compiled from the best newsletter content, heavily rewritten for book format, sent to editor -- [[25q3-community-launch]] platform set up on Circle — designed channels (ask-anything, career-advice, tech-leadership, off-topic), invited first 200 premium subscribers as founding members -- [[25q3-peak-training]] underway: structured intervals 4x/week, long ride every Saturday, altitude simulation sessions on the trainer -- Newsletter at 72k subscribers — summer slowdown minimal thanks to the community buzz -- Recorded first episodes of [[25q3-podcast-season-4]] — the 3-part "Building Engineering Culture from Scratch" series -- [[person-sara-ricci]] took over community moderation and onboarding, freeing me to focus on content and training - -## Reflections - -July was the month where the ambition of Q3 became real. Three major launches (ebook, community, podcast season) plus peak training for Stelvio. On paper it looks insane. In practice... it felt intense but manageable, mostly because [[person-sara-ricci]] stepped up massively on the community side. She went from coordinating podcast guests to designing the entire community architecture. The founding members are engaged, the conversations are high-quality, and I barely had to touch it. - -The ebook rewriting was harder than expected. Newsletter articles are written for a 5-minute read with specific context. A book chapter needs to stand alone, build on previous chapters, and go deeper. I spent more time rewriting than compiling. But the result feels substantial — not a lazy content recycling, but a genuine book that adds value beyond the newsletter. - -Training is going well. The altitude simulation sessions are brutal — 90 minutes at reduced oxygen while doing threshold intervals — but I can feel my body adapting. FTP is climbing toward 280W. Stelvio from Bormio is 24 km at 7.1% average gradient. At my weight and power, that's roughly 1h50m. Tight, but possible. The mountain is calling. diff --git a/demo-vault-v2/2025-08.md b/demo-vault-v2/2025-08.md deleted file mode 100644 index b7385dfe..00000000 --- a/demo-vault-v2/2025-08.md +++ /dev/null @@ -1,31 +0,0 @@ ---- -aliases: ["August 2025"] -Is A: Month -Created at: "2025-08-28" -Belongs to: "[[25q3]]" -Rating: "🤩" ---- -# August 2025 - -## Focus - -- Publish [[25q3-ebook]] — final edits, cover design, launch campaign -- Ride Stelvio — the culmination of [[25q3-peak-training]] and [[2025-ride-stelvio]] -- Open [[25q3-community-launch]] to all premium subscribers - -## Highlights - -- Published [[25q3-ebook]] "The Engineering Leader's Playbook" — 1,400 copies sold in the first month at EUR 29, far exceeding the 500-copy target -- Rode Stelvio from Bormio in 1h52m — [[2025-ride-stelvio]] achieved — the hardest and most beautiful thing I've done on a bike -- [[25q3-community-launch]] opened to all premium members — 850 founding members, 65% weekly active rate from day one -- [[25q3-podcast-season-4]] debut: "Building Engineering Culture from Scratch" Part 1 got 22k downloads in the first week — biggest episode ever -- FTP peaked at 285W during [[25q3-peak-training]] — best numbers of my life -- Newsletter at 75k subscribers - -## Reflections - -Stelvio. I don't know how to write about it without sounding dramatic, so I'll just be dramatic. It was the hardest thing I've ever done on a bike. The Bormio side starts deceptively gentle — wide roads, gradual grade, you think "this isn't so bad." Then the switchbacks begin. 48 of them. Each one steeper than the last, each one revealing another section of road winding above you. At km 18, with 6 km still to go, I almost stopped. My legs were screaming, my heart rate was at 175, and a voice in my head was saying "you've proved enough." But I kept going because the summit was up there, and I'd been thinking about it since December. 1h52m. Not fast. But done. I cried at the top. No shame. - -The ebook launch going well was almost anticlimactic after Stelvio. But 1,400 copies in the first month is genuinely impressive for a self-published niche book. The "real book" effect is interesting — people treat you differently when you have a book, even if the content is largely derived from free newsletter articles. Perception is reality in media. - -I need to be honest: by the end of August, I was running on empty. Three big things shipped (ebook, community, Stelvio), podcast recording ongoing, newsletter still weekly. Sleep has been under 6 hours most nights. [[person-paco-furiani]] told me I looked tired on our weekly call. He's right. September needs to include real rest, or I'll pay for it later. diff --git a/demo-vault-v2/2025-09.md b/demo-vault-v2/2025-09.md deleted file mode 100644 index eb434cc4..00000000 --- a/demo-vault-v2/2025-09.md +++ /dev/null @@ -1,31 +0,0 @@ ---- -aliases: ["September 2025"] -Is A: Month -Created at: "2025-09-28" -Belongs to: "[[25q3]]" -Rating: "😄" ---- -# September 2025 - -## Focus - -- Deliver keynote at [[25q3-leaddev-london]] -- Recover from August intensity — schedule white space, prioritize sleep -- Close Q3 metrics and plan Q4 - -## Highlights - -- Delivered keynote at [[25q3-leaddev-london]] on "The Newsletter-to-Business Pipeline" to 1,200 attendees — biggest stage ever, standing ovation, 5 enterprise sponsor inquiries -- Took 10 days fully off in early September — first real break since January, no email, no Slack, just cycling and reading -- Newsletter hit 78k subscribers by month end — the LeadDev exposure and ebook cross-promotion driving a late-Q3 surge -- [[measure-sponsorship-mrr]] reached EUR 20.1k — [[2025-reach-22k-mrr]] within reach for Q4 -- [[25q3-podcast-season-4]] wrapped up with 8 episodes released — consistently above 15k downloads per episode -- Community stabilizing at 850 members with strong engagement — [[person-sara-ricci]] running it almost independently - -## Reflections - -The 10 days off in early September saved me. I came back from August brittle — snapping at [[person-paco-furiani]] over minor things, dreading the newsletter instead of enjoying it, skipping workouts. The break was non-negotiable: I told the team I'd be unreachable, set up auto-responders, and disappeared into the Dolomites with my bike and a stack of books. By day 4, the fog lifted. By day 7, I was excited about work again. By day 10, I had a notebook full of ideas for Q4. - -LeadDev London was the professional peak of the year. The keynote was different from Codemotion last year — bigger stage, broader audience, higher stakes. But I was more prepared and, honestly, more confident. The talk traced the arc from "person with a newsletter" to "media business with a team, a podcast, a book, and a community." The vulnerability of sharing revenue numbers on stage felt risky but landed well. Authenticity again. - -Q3 was the most productive quarter of my career. Ebook published, community launched, Stelvio climbed, LeadDev delivered, podcast season completed. But it was also the most draining. The lesson is crystal clear: I can sustain this intensity for 13 weeks, but not 26. Q4 needs to be calmer. Fewer launches. More depth. More sleep. diff --git a/demo-vault-v2/2025-10.md b/demo-vault-v2/2025-10.md deleted file mode 100644 index b4ca52f8..00000000 --- a/demo-vault-v2/2025-10.md +++ /dev/null @@ -1,31 +0,0 @@ ---- -aliases: ["October 2025"] -Is A: Month -Created at: "2025-10-28" -Belongs to: "[[25q4]]" -Rating: "😐" ---- -# October 2025 - -## Focus - -- Begin [[25q4-laputa-v3]] development — AI chat panel, type creation, graph improvements -- Start [[25q4-2026-sponsors]] pipeline with [[person-matteo-cellini]] -- Settle into a sustainable Q4 rhythm after the intensity of Q3 - -## Highlights - -- [[25q4-laputa-v3]] development started: AI chat panel prototype working — can ask questions about vault content and get contextual answers with linked references -- [[person-matteo-cellini]] began [[25q4-2026-sponsors]] outreach — 4 sponsors already in early conversations for Q1-Q2 2026 -- Newsletter at 80k subscribers — growth continuing but I'm less obsessed with the number than I used to be -- Community reaching a self-sustaining rhythm — members helping each other without prompting, which is the whole point -- Cycling winding down for the season — 280 km this month, mostly easy rides, letting the body recover from Stelvio -- Read "Working in Public" by Nadia Eghbal and "The Mom Test" by Rob Fitzpatrick — both relevant to the community and Laputa product thinking - -## Reflections - -October was deliberately quieter than the previous three months, and I'm grateful for it. After Q3's intensity, I needed a month of sustained work at 70% capacity rather than another sprint at 110%. The Laputa v3 work has been the right kind of creative — exploratory, no deadlines, just building something cool. The AI chat panel started as a "what if" experiment and quickly became the most interesting feature I've built. Asking your vault "what did I write about technical debt last year?" and getting a contextual, linked answer feels like magic. - -But I'm also feeling a low-grade anxiety about hitting [[2025-reach-85k-subscribers]] by year end. We're at 80k with two months to go. The math works — 2.5k/month is within our normal range — but it doesn't leave room for a bad month. The Black Friday campaign will be critical again. - -The sponsor pipeline work is less exciting but equally important. [[person-matteo-cellini]] is already mapping out 2026, which means I need to make decisions about pricing, formats, and what we offer. The business is maturing in ways that require more strategic thinking and less reactive selling. That's a good problem to have, but it requires a different kind of energy. diff --git a/demo-vault-v2/2025-11.md b/demo-vault-v2/2025-11.md deleted file mode 100644 index ef8cfe5d..00000000 --- a/demo-vault-v2/2025-11.md +++ /dev/null @@ -1,32 +0,0 @@ ---- -aliases: ["November 2025"] -Is A: Month -Created at: "2025-11-28" -Belongs to: "[[25q4]]" -Rating: "😄" ---- -# November 2025 - -## Focus - -- Push for [[25q4-reach-85k]] with Black Friday campaign -- Ship [[25q4-laputa-v3]] features — type creation UI, improved AI chat -- Begin [[25q4-financial-review]] — compile 2025 revenue and expense data - -## Highlights - -- Black Friday campaign launched: bundled ebook + premium annual subscription at 30% off — early results strong, 1,800 new subscribers in the first week -- Newsletter at 83.5k subscribers — on pace for [[25q4-reach-85k]] by mid-December -- [[25q4-laputa-v3]] type creation shipped — users (well, me) can now define custom types with properties directly in the app, no more editing YAML manually -- [[25q4-financial-review]] started: 2025 tracking to ~EUR 260k total revenue (sponsorships EUR 210k, premium EUR 35k, ebook EUR 15k) -- [[person-matteo-cellini]] closed 3 more [[25q4-2026-sponsors]] deals — Q1 2026 pipeline at EUR 24k+ MRR -- [[measure-podcast-downloads]] averaging 18k/month — consistent and growing -- AI chat panel refined: better context retrieval, source linking, faster responses — starting to share with a few trusted friends for feedback - -## Reflections - -The Black Friday campaign this year was more strategic than last year's. Instead of a pure discount play, we bundled the ebook with premium — giving people a reason to upgrade that goes beyond price. Early numbers suggest it's working better than last year's approach. [[person-paco-furiani]] set up the automation so cleanly that I barely had to touch it — sign-ups flowing in, welcome emails going out, access provisioning automatic. The team is genuinely running the machine now. - -The financial review numbers are staggering to me. EUR 260k from what was, not that long ago, a side project newsletter. The breakdown is healthy too — sponsorships dominate but premium and the ebook are diversifying the revenue. If the 2026 sponsor pipeline closes as projected, we'll be looking at EUR 300k+ next year. That's "hire a full-time person" territory. - -Laputa v3 is getting close to something I could show other people without apologizing for it. The type creation UI was the missing piece — non-technical users (hypothetical ones, since I'm still the only user) can now define their own taxonomy without touching YAML. [[2025-ship-laputa]] feels achievable. I've started sharing it with 3 friends who maintain large vaults. Their feedback has been encouraging: "this is what I wanted Obsidian to be." Music to my ears. diff --git a/demo-vault-v2/2025-12.md b/demo-vault-v2/2025-12.md deleted file mode 100644 index 4e070c1d..00000000 --- a/demo-vault-v2/2025-12.md +++ /dev/null @@ -1,34 +0,0 @@ ---- -aliases: ["December 2025"] -Is A: Month -Created at: "2025-12-28" -Belongs to: "[[25q4]]" -Rating: "😄" ---- -# December 2025 - -## Focus - -- Close the year: hit [[25q4-reach-85k]], finalize [[25q4-financial-review]], run [[25q4-year-review-2025]] -- Complete [[25q4-laputa-v3]] — prepare for closed beta in January -- Reflect, rest, and plan [[2025]] wrap-up - -## Highlights - -- Newsletter crossed 85k subscribers on December 11th — [[2025-reach-85k-subscribers]] achieved, exactly one year after hitting 50k -- [[25q4-financial-review]] finalized: 2025 total revenue EUR 262k, up 69% from 2024 — [[2025-reach-22k-mrr]] hit in November with MRR at EUR 22.3k -- [[25q4-year-review-2025]] completed: every 2025 goal either hit or exceeded — [[2025-reach-85k-subscribers]], [[2025-reach-22k-mrr]], [[2025-ride-stelvio]], [[2025-ship-laputa]] (beta), [[2025-read-20-books]] (21 books) -- [[25q4-laputa-v3]] beta-ready: 12 closed beta testers lined up for January, onboarding docs written, feedback channels set up -- [[person-matteo-cellini]] locked in 8 sponsors for [[25q4-2026-sponsors]] Q1-Q2 pipeline — projected MRR EUR 24.5k -- End-of-year podcast episode recorded: honest, vulnerable, grateful — the kind of episode that's hard to record and easy to listen to -- Read 3 books in December: finished at 21 for the year - -## Reflections - -Crossing 85k subscribers felt different from crossing 50k last year. Last year was euphoria — "I can't believe this is happening." This year was quieter — "of course it happened, look at the system we built." That shift from surprise to expectation is both a sign of maturity and a subtle loss. I miss the wonder a little. But I'll take sustainable confidence over periodic amazement. - -The financial review was the most sobering exercise of the month. EUR 262k in revenue. A real team of four people. A product in beta. A published book. A keynote at LeadDev. Two years ago, I was a solo newsletter writer hoping to make rent from sponsorships. The speed of change is disorienting when you zoom out. In the day-to-day, it feels gradual. In the annual review, it feels dramatic. - -Laputa going to beta testers in January is the thing I'm most excited about heading into 2026. Building software for yourself is satisfying, but it's also a trap — you optimize for your own quirks and blind spots. Having 12 other people use it will surface assumptions I didn't know I was making. Some of those assumptions will be wrong. That's the point. - -[[2025]] was the year I stopped being a content creator with a side hustle and became a founder running a media company with a software product. Both descriptions are true, but the second one is the more accurate framing now. Looking ahead: more team, more product, more depth, less heroics. And maybe Ventoux next summer. We'll see. diff --git a/demo-vault-v2/2025-reach-22k-mrr.md b/demo-vault-v2/2025-reach-22k-mrr.md deleted file mode 100644 index c19d2de7..00000000 --- a/demo-vault-v2/2025-reach-22k-mrr.md +++ /dev/null @@ -1,33 +0,0 @@ ---- -aliases: ["Reach €22k MRR"] -Is A: Goal -Belongs to: "[[2025]]" -Status: Open ---- -# Reach €22k MRR - -Growing sponsorship revenue to 22,000 EUR/month is the key financial milestone for 2025. Hitting this target would make Refactoring a comfortably profitable business capable of supporting a team of 3-4, funding product development like [[25q1-laputa-v1]], and providing the financial runway to experiment with new revenue lines such as community or premium offerings. - -## Success criteria - -- Reach 22,000 EUR MRR by December 2025 -- Maintain average deal size above 1,400 EUR per placement -- Grow sponsor roster to 15+ active sponsors (up from ~10) -- Achieve 85%+ renewal rate on existing contracts -- Keep [[measure-close-rate]] above 35% on inbound leads - -## Key milestones - -- Start the year at 15k MRR baseline (carry-over from 2024 contracts) -- Launch updated sponsorship packages with audience segmentation data in [[25q1]] -- Cross 18k MRR by mid-year through new sponsor acquisition -- Introduce premium placement options tied to [[25q2-reach-70k]] subscriber milestone -- Close Q4 at 22k MRR, with strong pipeline for 2026 - -## Notes - -- Currently tracking at approximately 19k MRR as of Q3. The gap to 22k is closable but requires 2-3 new sponsors or upsells in Q4. -- Subscriber growth ([[2025-reach-85k-subscribers]]) is the enabler. Every 10k subscriber increase unlocks ~1,500 EUR in pricing power. -- The [[25q1-referral-program]] is driving higher-quality subscribers, which improves engagement metrics that sponsors care about (open rate, click rate). -- Risk: if [[measure-subscribers]] growth stalls, pricing increases become harder to justify. Revenue and audience growth are tightly coupled. -- The community experiment ([[25q3-discord-community-soft]]) could become a supplemental revenue line, but is not included in the 22k MRR target to keep it focused on sponsorships. diff --git a/demo-vault-v2/2025-reach-85k-subscribers.md b/demo-vault-v2/2025-reach-85k-subscribers.md deleted file mode 100644 index 67d9a688..00000000 --- a/demo-vault-v2/2025-reach-85k-subscribers.md +++ /dev/null @@ -1,33 +0,0 @@ ---- -aliases: ["Reach 85k Subscribers"] -Is A: Goal -Belongs to: "[[2025]]" -Status: Open ---- -# Reach 85k Subscribers - -Reaching 85,000 subscribers by end of 2025 is the primary growth target for the year. This represents roughly 60% growth over the 53k base from end of 2024 and would position Refactoring as one of the largest independent engineering newsletters globally. Audience scale is the engine that drives [[measure-sponsorship-mrr]], enables premium pricing for [[2025-reach-22k-mrr]], and provides the distribution base for any future product launches. - -## Success criteria - -- End 2025 with 85,000+ total newsletter subscribers -- Maintain net monthly growth of 2,500+ subscribers -- Keep unsubscribe rate below 1.3% per issue -- Maintain [[measure-open-rate]] above 43% at scale -- Diversify acquisition channels: no single channel should account for more than 40% of new subscribers - -## Key milestones - -- Launch [[25q1-newsletter-seo-sprint]] to build a long-term organic acquisition engine -- Launch [[25q1-referral-program]] to drive word-of-mouth growth -- Cross 65,000 by end of Q1 (strong start to the year) -- Reach 70,000 by mid-year through [[25q2-reach-70k]] push -- Hit 85,000 by December with sustained multi-channel growth through [[25q4-reach-85k]] - -## Notes - -- Currently at approximately 75,000 subscribers as of Q3. On track but the pace needs to hold through Q4. -- The [[25q1-referral-program]] has been the strongest new channel in 2025, accounting for ~20% of new subscribers. Referral subscribers also have higher engagement. -- SEO from the [[25q1-newsletter-seo-sprint]] is a slow burn. Articles are ranking but take 3-6 months to reach full traffic potential. Expect the biggest impact in Q4. -- Twitter/X remains the largest single channel at ~35%, close to the 40% cap. Need to continue diversifying. -- Key risk: list quality at scale. As the audience grows, maintaining [[measure-open-rate]] above 43% requires active list hygiene and consistently high content quality from [[responsibility-content-production]]. diff --git a/demo-vault-v2/2025-read-20-books.md b/demo-vault-v2/2025-read-20-books.md deleted file mode 100644 index 41964e60..00000000 --- a/demo-vault-v2/2025-read-20-books.md +++ /dev/null @@ -1,33 +0,0 @@ ---- -aliases: ["Read 20 Books in 2025"] -Is A: Goal -Belongs to: "[[2025]]" -Status: Open ---- -# Read 20 Books in 2025 - -Reading remains the highest-leverage input for content quality and original thinking. The 2025 target of 20 books is calibrated to be ambitious but realistic based on the [[2024-read-24-books]] experience, where the 24-book target was missed at 18. The adjusted goal accounts for the increasing demands of a growing business while preserving [[responsibility-learning]] as a non-negotiable priority. - -## Success criteria - -- Read 20 books by December 31, 2025 -- Maintain at least 1 book per month, even in the busiest months -- Track monthly progress via [[measure-books-per-month]] -- At least 60% should be non-fiction relevant to content, engineering, or business -- Create at least 3 newsletter essay ideas per quarter sourced from reading - -## Key milestones - -- Read 5 books by end of Q1 to build early momentum -- Integrate audiobooks into cycling training to boost volume (learned from 2024) -- Reach 10 books by mid-year -- Maintain pace through the busy Q3 podcast and community launch season -- Close the year at 20 by protecting reading time in Q4 - -## Notes - -- Currently at 14 books as of Q3. On pace to hit 20, but Q4 needs to deliver 6 books which matches the best quarterly performance in 2024. -- Audiobooks during cycling continue to be the most reliable reading channel. 8 of the 14 books so far were consumed via audio during rides. -- The shift to 60% non-fiction is working well. Recent reads on platform economics and community building directly informed the [[25q3-community-launch]] strategy. -- The biggest risk to this goal is the Q4 crunch: [[25q4-reach-85k]] and year-end sponsor renewals tend to consume all available bandwidth. -- Linking reading notes to [[measure-evergreen-notes-created]] helps ensure books translate into lasting knowledge rather than forgotten highlights. diff --git a/demo-vault-v2/2025-ride-stelvio.md b/demo-vault-v2/2025-ride-stelvio.md deleted file mode 100644 index be58b446..00000000 --- a/demo-vault-v2/2025-ride-stelvio.md +++ /dev/null @@ -1,34 +0,0 @@ ---- -aliases: ["Ride the Stelvio Pass"] -Is A: Goal -Belongs to: "[[2025]]" -Status: Done ---- -# Ride the Stelvio Pass - -The Stelvio Pass is one of the most iconic climbs in professional cycling: 24.3 km at 7.4% average gradient, reaching 2,758 meters of elevation. Completing a full ascent has been a bucket-list goal for years and represents the intersection of [[responsibility-health-fitness]] and personal ambition. After successfully completing two gran fondos in 2024 ([[2024-complete-two-gran-fondos]]), the Stelvio was the natural next challenge. - -## Success criteria - -- Complete a full ascent of the Stelvio Pass from Prato allo Stelvio (the classic east side) -- Finish under 2 hours 15 minutes -- No mechanical issues or health incidents during the climb -- Maintain [[measure-cycling-km-per-month]] above 500 km during the 3-month build phase -- Sustain [[measure-resting-hr]] below 52 bpm during peak training - -## Key milestones - -- Begin structured climbing-specific training block in March 2025 -- Complete at least 3 alpine climbs of 1,500+ meters elevation gain as preparation rides by May -- Ride the Stelvio in June or July, weather permitting -- Document the ride for a potential newsletter essay on [[topic-cycling-training]] -- Recover and return to baseline training volume within 2 weeks - -## Notes - -- Completed the Stelvio in late June 2025 in 2 hours 8 minutes. Under the 2:15 target by 7 minutes. -- The climbing-specific training block made a significant difference. Focused on sustained threshold efforts and long climbs in the Dolomites during April-June. -- [[measure-resting-hr]] averaged 50 bpm during peak training, indicating good aerobic adaptation. -- Weather was perfect on the day. Started early (6:30 AM) to avoid afternoon traffic and wind. -- Wrote a newsletter essay about the experience that became one of the most-engaged issues of the year. Personal stories consistently outperform tactical content. -- This was the most personally meaningful goal completed in 2025. The physical challenge is a reminder that capacity is often self-limited. diff --git a/demo-vault-v2/2025-ship-laputa.md b/demo-vault-v2/2025-ship-laputa.md deleted file mode 100644 index c3c917e5..00000000 --- a/demo-vault-v2/2025-ship-laputa.md +++ /dev/null @@ -1,34 +0,0 @@ ---- -aliases: ["Ship Laputa App"] -Is A: Goal -Belongs to: "[[2025]]" -Status: Done ---- -# Ship Laputa App - -Laputa is a personal knowledge and life management desktop app designed to replace the patchwork of tools currently used to manage the vault of ~9,200 markdown files that power content production, goal tracking, and personal operations. Shipping a usable v1 and adopting it as the daily driver is both a product goal and an infrastructure investment: a better tool for managing knowledge directly improves output quality for [[responsibility-content-production]] and operational clarity across all responsibilities. - -## Success criteria - -- Ship Laputa v1 as a functional Tauri desktop app with four-panel UI -- Support reading and editing markdown files with YAML frontmatter -- Implement vault navigation, search, and filtering by type -- Use Laputa as the primary daily knowledge management tool (replace current workflow) -- Achieve stable performance with the full ~9,200 file vault - -## Key milestones - -- Build the core Tauri + React architecture and file I/O layer during [[25q1-laputa-v1]] -- Implement the four-panel UI (sidebar, list, editor, properties) by end of Q1 -- Add frontmatter parsing, type filtering, and basic search by mid-Q2 -- Iterate on editor experience (CodeMirror 6 integration) during [[25q2-laputa-v2]] -- Reach daily-driver status by end of Q2 and sustain through Q3-Q4 - -## Notes - -- Laputa v1 shipped in March 2025 and has been the daily driver since April. The app handles the full vault without performance issues. -- The Tauri v2 + React + TypeScript stack was the right choice. Desktop performance is excellent and the Rust backend handles file I/O efficiently even at scale. -- The mock layer (`src/mock-tauri.ts`) proved invaluable for rapid UI iteration without needing the full backend running. -- CodeMirror 6 integration was the most complex part of the frontend. Live preview with reveal-on-focus required significant customization. -- [[25q2-laputa-v2]] added refinements: better search, improved frontmatter editing, and the AI chat panel. -- Key lesson: building your own tools is high-leverage when you are the primary user. Every improvement to Laputa directly improves daily workflow efficiency across [[responsibility-content-production]], [[responsibility-personal-finance]], and [[responsibility-learning]]. diff --git a/demo-vault-v2/2025.md b/demo-vault-v2/2025.md deleted file mode 100644 index f3c4de72..00000000 --- a/demo-vault-v2/2025.md +++ /dev/null @@ -1,51 +0,0 @@ ---- -aliases: ["2025"] -Is A: Year -Created at: "2025-01-01" -Has: ["[[25q1]]", "[[25q2]]", "[[25q3]]", "[[25q4]]"] ---- -# 2025 - -## Theme - -2025 is the scale year — the year the question shifted from "can this work?" to "how big can this get?" Coming off the momentum of [[2024]], every metric pointed upward: subscribers, revenue, podcast downloads, team capacity. The goal wasn't just to grow more, but to grow *better* — building systems and a team that could sustain 85k subscribers, EUR 22k MRR, and a product (Laputa) without everything depending on me. - -But scaling surfaced a tension I hadn't anticipated: the more successful Refactoring becomes, the more it pulls me away from the craft that made it successful in the first place — writing. Managing sponsors, coordinating a team, shipping a product, speaking at conferences — these are all valuable, but they're not writing. The creative struggle of 2025 has been protecting the space to think deeply and write well, while everything else demands attention. Some months I won that battle. Others, I didn't. - -## Highlights - -- Newsletter grew from 50k to 82k+ subscribers (on track for [[2025-reach-85k-subscribers]] by year end) -- [[measure-sponsorship-mrr]] grew from EUR 11.4k to EUR 20.1k by end of Q3, tracking toward [[2025-reach-22k-mrr]] -- Shipped three versions of Laputa: [[25q1-laputa-v1]], [[25q2-laputa-v2]], [[25q4-laputa-v3]] — from internal prototype to closed beta candidate ([[2025-ship-laputa]]) -- Podcast grew to 18k downloads/month across Seasons 3 and 4 ([[25q2-podcast-season-3]], [[25q3-podcast-season-4]]) -- Published [[25q3-ebook]] "The Engineering Leader's Playbook" — 1,400+ copies sold in the first month -- Launched [[25q3-community-launch]] with 850 founding members -- Rode Stelvio from Bormio in 1h52m — [[2025-ride-stelvio]] achieved -- Keynote at [[25q3-leaddev-london]] to 1,200 attendees — biggest speaking engagement to date -- [[25q2-team-retreat]] in Tuscany aligned the team for H2 and catalyzed the community idea -- Executed [[25q1-rate-increase]] — sponsor rates up 25%, retention at 90% - -## By the numbers - -- **Subscribers**: 50.2k to ~82k (projected 85k by Dec) — +64% YoY -- **Sponsorship MRR**: EUR 11.4k to EUR 20.1k (Q3 close) — targeting EUR 22k by year end -- **Podcast downloads**: 8.2k/month to 18k/month — +120% YoY -- **Premium subscribers**: 320 to 680+ — +112% YoY -- **Ebook sales**: 1,400+ copies (launched Q3) -- **Community members**: 850 (launched Q3) -- **Books read**: on track for [[2025-read-20-books]] (16 through Q3) -- **Cycling km**: ~5,800 km through Q3, projected 7,500+ for year — [[measure-cycling-km-per-month]] -- **Stelvio**: 1h52m from Bormio — personal milestone -- **Conference talks**: 2 (LeadDev London keynote, plus a workshop) -- **Total revenue**: projected ~EUR 260k (+68% vs 2024) -- **Resting HR**: [[measure-resting-hr]] averaged 48 bpm, down from 52 bpm in 2024 - -## Reflections - -The most important thing I did in 2025 was hire well and delegate aggressively. [[person-matteo-cellini]] now runs the entire sponsor relationship lifecycle — from prospecting to renewal — and does it better than I did. [[person-paco-furiani]] owns operations, invoicing, and now coordinates the community logistics. [[person-sara-ricci]] handles podcast production and guest coordination. For the first time, I can take a week off and nothing breaks. That's the real milestone, even if it doesn't show up in the metrics. - -The ebook and community launches in Q3 represented a philosophical shift. For three years, Refactoring was a one-to-many broadcast channel: I write, you read. The community made it many-to-many. Engineering leaders helping each other, sharing war stories, giving feedback on each other's challenges. I'm a facilitator now, not just a broadcaster. It's a better model, but it requires a different kind of energy — more listening, less performing. - -Laputa has been the most surprising journey of the year. What started as a weekend hack in Q4 2024 has become a serious product with three major versions shipped. Using it daily to manage my 9,000+ file vault has been the best kind of dogfooding — every friction point I hit becomes a feature. The AI chat panel in v3 was a breakthrough moment: asking your own vault questions and getting contextual, linked answers feels like the future of personal knowledge management. Whether this becomes a real product with real users or stays a personal tool, building it has made me a better engineer and a better thinker. - -If I'm being honest, Q3 nearly broke me. Three major launches, a keynote, and peak cycling training in the same 13 weeks was too much. I hit a wall in late August — low energy, poor sleep, short temper. [[person-paco-furiani]] noticed before I did. I took 10 days fully off in early September and came back feeling human again. The lesson is one I keep having to relearn: ambition without recovery is just a burnout timeline. Going into Q4 and planning for 2026, I'm trying to build more white space into the calendar. Fewer launches per quarter. More weeks with nothing scheduled. The business can handle it — the question is whether I can resist the urge to fill every gap with a new project. History suggests I can't, but I'm working on it. diff --git a/demo-vault-v2/24q1-launch-sponsorship-packages.md b/demo-vault-v2/24q1-launch-sponsorship-packages.md deleted file mode 100644 index 2f5021e2..00000000 --- a/demo-vault-v2/24q1-launch-sponsorship-packages.md +++ /dev/null @@ -1,36 +0,0 @@ ---- -aliases: ["Launch Sponsorship Packages"] -Is A: Project -Belongs to: "[[24q1]]" -Advances: "[[responsibility-sponsorships]]" -Status: Done -Owner: "[[person-luca-rossi]]" ---- -# Launch Sponsorship Packages - -## Overview - -This project formalized Refactoring's monetization through sponsorships by creating structured packages that sponsors could evaluate and purchase. Before this, sponsorship deals were ad-hoc and inconsistent — pricing varied per deal, deliverables were loosely defined, and there was no media kit to send prospects. - -The goal was to create three clear tiers (Logo, Spotlight, and Deep Dive) with fixed pricing, well-defined deliverables, and a professional media kit PDF. This would make outreach scalable and give [[person-luca-rossi]] a repeatable process instead of negotiating every deal from scratch. The project directly supported [[2024-double-revenue]] by establishing the revenue engine for the year. - -## Goals - -- Define three sponsorship tiers with clear deliverables and pricing (Logo: $500, Spotlight: $1,200, Deep Dive: $2,500) -- Create a professional media kit PDF with audience demographics, open rates, and testimonials -- Set up a Stripe billing workflow for recurring sponsors -- Draft email templates for outreach, follow-up, and renewal -- Close the first 3 paying sponsors before end of [[24q1]] - -## Key decisions - -- **Three tiers, not two or four.** Considered a simpler two-tier model, but having three gives sponsors a clear upgrade path. The Logo tier serves as a low-friction entry point. -- **Monthly pricing, not per-issue.** Charging monthly (4 issues) simplifies invoicing and gives sponsors more predictable budgets. This also aligns with how [[measure-sponsorship-mrr]] is tracked. -- **No exclusivity clauses.** Decided against offering category exclusivity because the newsletter audience is too broad to guarantee meaningful exclusivity, and it would limit revenue potential. - -## Notes - -- The media kit took longer than expected — gathering accurate audience data required exporting from Substack and ConvertKit, which have inconsistent analytics. Settled on a conservative subscriber count to maintain credibility. -- [[person-matteo-cellini]] provided useful feedback on the pricing deck layout. His experience with B2B sales helped shape the value proposition framing. -- First three sponsors came from warm outreach to developer tool companies who had previously engaged with newsletter content. Cold outreach conversion was near zero at this stage. -- This project established the foundation for [[procedure-sponsor-onboarding]] and [[procedure-quarterly-sponsor-outreach]], which were formalized later in [[24q2]]. diff --git a/demo-vault-v2/24q1-plan-cycling-season.md b/demo-vault-v2/24q1-plan-cycling-season.md deleted file mode 100644 index 61daeeb4..00000000 --- a/demo-vault-v2/24q1-plan-cycling-season.md +++ /dev/null @@ -1,36 +0,0 @@ ---- -aliases: ["Plan 2024 Cycling Season"] -Is A: Project -Belongs to: "[[24q1]]" -Advances: "[[responsibility-health-fitness]]" -Status: Done -Owner: "[[person-luca-rossi]]" ---- -# Plan 2024 Cycling Season - -## Overview - -This project laid out the full 2024 cycling calendar — target events, training blocks, rest weeks, and equipment needs. The main objective was to complete two gran fondos in 2024, supporting [[2024-complete-two-gran-fondos]], while maintaining a sustainable training load that would not interfere with work commitments. - -Planning happened in January and February so that structured training could begin in March. This included selecting target events, mapping out a periodized training plan (base, build, peak, recovery), and identifying any gear upgrades needed before the season. [[person-paco-furiani]] helped review the training plan and suggested adjustments based on his own racing experience. - -## Goals - -- Select two target gran fondos for 2024 (spring and autumn) -- Design a 24-week periodized training plan with base, build, and peak phases -- Establish weekly volume targets: 8-12 hours per week during build phase -- Budget and plan equipment upgrades (new wheelset, tire strategy for events) -- Set up tracking in Strava and TrainingPeaks for [[measure-cycling-km-per-month]] - -## Key decisions - -- **Granfondo di Varese (May) and Granfondo dell'Appennino (September)** selected as the two target events. Varese was chosen for its accessibility and moderate difficulty; Appennino for its challenging profile that would test peak fitness. -- **Polarized training model** rather than threshold-heavy. After reading several studies on amateur endurance performance, decided that 80/20 (easy/hard) distribution would be more sustainable alongside a demanding work schedule. -- **No coach for now.** Considered hiring a cycling coach but decided to self-coach for 2024 using structured plans from TrainingPeaks. If results are good, revisit for 2025. - -## Notes - -- The biggest risk to the plan was always going to be consistency — weeks with heavy newsletter deadlines or sponsor calls tend to eat into training time. Built in buffer weeks to account for this. -- Realized during planning that the winter base phase was already partially missed. Adjusted by extending the base phase by two weeks and compressing the first build block slightly. -- Equipment decision: went with a new set of carbon wheels (Campagnolo Bora WTO 45) rather than upgrading the frame. Better bang for the buck in terms of performance gain per euro. -- This plan feeds directly into [[24q2-spring-gran-fondo]] for the first event execution and into [[topic-cycling-training]] for ongoing training notes. diff --git a/demo-vault-v2/24q1-podcast-season-1.md b/demo-vault-v2/24q1-podcast-season-1.md deleted file mode 100644 index 86a9889f..00000000 --- a/demo-vault-v2/24q1-podcast-season-1.md +++ /dev/null @@ -1,36 +0,0 @@ ---- -aliases: ["Podcast Season 1 Launch"] -Is A: Project -Belongs to: "[[24q1]]" -Advances: "[[responsibility-podcast]]" -Status: Done -Owner: "[[person-luca-rossi]]" ---- -# Podcast Season 1 Launch - -## Overview - -This project launched the Refactoring podcast — a long-form interview show focused on engineering culture, technical leadership, and the human side of building software. The idea had been brewing for months, but the decision to actually ship was driven by [[2024-launch-podcast]] as a key goal for the year. - -The strategy was to batch-record 6 episodes before publishing anything, so that the launch would have a backlog and a consistent weekly cadence from day one. This meant spending most of January and February on guest outreach, recording, and editing, with the public launch in mid-March. [[person-sara-ricci]] joined as editor toward the end of the project to handle post-production, which proved essential for maintaining quality while keeping up with the newsletter schedule. - -## Goals - -- Record 6 episodes before public launch (buffer for consistent weekly releases) -- Secure guests with strong engineering leadership backgrounds (CTOs, VPEs, Staff+ engineers) -- Set up podcast hosting, RSS feed, and distribution to Apple Podcasts, Spotify, and YouTube -- Design cover art and episode template graphics -- Establish [[procedure-podcast-recording]] and [[procedure-podcast-editing]] workflows - -## Key decisions - -- **Interview format, not solo.** Considered doing solo episodes or co-hosted commentary, but interviews leverage guest audiences for cross-promotion and are more engaging for a new show with no existing listener base. -- **Season model, not continuous.** Adopted a seasonal structure (8-10 episodes per season) with breaks between seasons. This prevents burnout and allows time to plan each season's theme. Season 1 theme: "Engineering Culture." -- **Audio-first, video as bonus.** Recorded video but optimized for audio quality. Video clips are used for social promotion, but the primary distribution is audio podcasts. This reduced production overhead significantly. - -## Notes - -- Guest booking was the hardest part. Sent about 40 outreach emails to get 8 confirmed guests (6 recorded, 2 cancelled). Cold outreach to high-profile CTOs had about a 5% response rate. Warm intros from [[person-matteo-cellini]] and [[person-david-kim]] were far more effective. -- The first two episodes had noticeable audio quality issues — learned the hard way that remote recordings via Zoom are not sufficient. Switched to Riverside.fm for episodes 3-6, which was a significant improvement. -- Launch week saw about 1,200 downloads across the first 3 episodes, which was above the initial target of 500. The newsletter cross-promotion was the primary driver — [[measure-podcast-downloads]] tracked closely with newsletter send days. -- This project created the foundation for [[24q3-podcast-season-2]] and all subsequent seasons. The workflows established here, particularly [[procedure-podcast-recording]], have remained largely unchanged. diff --git a/demo-vault-v2/24q1-redesign-newsletter-template.md b/demo-vault-v2/24q1-redesign-newsletter-template.md deleted file mode 100644 index ca97eb17..00000000 --- a/demo-vault-v2/24q1-redesign-newsletter-template.md +++ /dev/null @@ -1,36 +0,0 @@ ---- -aliases: ["Redesign Newsletter Template"] -Is A: Project -Belongs to: "[[24q1]]" -Advances: "[[responsibility-content-production]]" -Status: Done -Owner: "[[person-luca-rossi]]" ---- -# Redesign Newsletter Template - -## Overview - -The Refactoring newsletter template had been largely unchanged since launch — a plain text-heavy layout that worked at small scale but felt increasingly dated as the subscriber base grew. This project redesigned the email template for better readability, visual hierarchy, and sponsor placement. The redesign needed to improve the reading experience while also making sponsorship placements more visually distinct and valuable, supporting [[2024-double-revenue]]. - -The new template introduced a cleaner header, better typography spacing, a dedicated sponsor block with clear visual boundaries, and a structured footer with social links and podcast promotion. It was tested across major email clients (Gmail, Apple Mail, Outlook) and went through three iterations based on feedback from a small group of beta readers. - -## Goals - -- Redesign the email template with improved visual hierarchy and readability -- Create a dedicated, visually distinct sponsor placement section -- Ensure compatibility across Gmail, Apple Mail, Outlook, and mobile clients -- Improve click-through rate on inline links by at least 15% -- Establish the new template as the standard for [[procedure-weekly-newsletter]] - -## Key decisions - -- **Single-column layout.** Evaluated two-column layouts with sidebar content, but testing showed that single-column performs significantly better on mobile (where 65%+ of opens happen). Simplicity won. -- **Sponsor block above the fold.** Moved the sponsor placement from mid-article to just below the header intro. This increased sponsor visibility without feeling intrusive, since the block is clearly labeled and visually separated. Sponsors noticed and appreciated the change. -- **No images in the main body.** Kept the template text-focused with minimal imagery. Images in email are unreliable (blocked by many clients), increase load time, and distract from the content. The only image is the sponsor logo. - -## Notes - -- The biggest surprise was how much email client rendering varies. A layout that looked perfect in Gmail was broken in Outlook. Ended up using a very conservative CSS approach with inline styles and table-based layout for maximum compatibility. -- [[person-sara-ricci]] helped with copy feedback on the new footer and CTA sections. Her editorial eye caught several awkward phrasings in the template boilerplate. -- A/B tested the new template against the old one over two issues. The new template showed a 22% increase in click-through rate, primarily driven by better link placement and the structured "further reading" section at the bottom. -- [[measure-open-rate]] remained stable through the transition, confirming that the redesign did not trigger spam filters or cause deliverability issues. This was a real concern given how sensitive email infrastructure is to template changes. diff --git a/demo-vault-v2/24q1-set-investing-framework.md b/demo-vault-v2/24q1-set-investing-framework.md deleted file mode 100644 index 382003be..00000000 --- a/demo-vault-v2/24q1-set-investing-framework.md +++ /dev/null @@ -1,36 +0,0 @@ ---- -aliases: ["Set Up Investing Framework"] -Is A: Project -Belongs to: "[[24q1]]" -Advances: "[[responsibility-personal-finance]]" -Status: Done -Owner: "[[person-luca-rossi]]" ---- -# Set Up Investing Framework - -## Overview - -As Refactoring's revenue grew, it became clear that personal finance needed a more structured approach. This project defined a personal investment policy statement (IPS) and set up automated monthly contributions to a diversified portfolio of index funds. The goal was to remove emotion and ad-hoc decision-making from investing and replace it with a simple, repeatable system. - -Before this project, savings were sitting in a low-yield savings account with no clear allocation strategy. The framework needed to be simple enough to maintain alongside a busy content business, while being sophisticated enough to actually build long-term wealth. Research phase took about three weeks, followed by account setup and automation. - -## Goals - -- Draft a personal Investment Policy Statement defining asset allocation, risk tolerance, and rebalancing rules -- Open a brokerage account with a low-cost provider (selected Degiro for European access and low fees) -- Set up automated monthly contributions (20% of net monthly revenue) -- Define a target allocation: 70% global equities (VWCE), 20% bonds (VAGF), 10% cash reserve -- Create a quarterly review checklist to assess allocation drift and rebalance if needed - -## Key decisions - -- **Passive index funds, not individual stocks.** After extensive reading (Bogle, Bernstein, Housel), decided that passive investing is the only approach that makes sense for someone whose primary income comes from a content business. Time spent stock-picking is time not spent on the newsletter. -- **Single accumulating ETF for equities (VWCE).** Rather than splitting across US, European, and emerging market ETFs, chose a single all-world accumulating ETF. Simplicity reduces friction and the urge to tinker. -- **20% of revenue, not a fixed amount.** Tying contributions to revenue percentage means the system scales with business growth and naturally reduces in leaner months without requiring manual adjustment. - -## Notes - -- The hardest part was actually committing to a framework and stopping the research phase. There is an infinite amount of personal finance content online, and it is easy to fall into analysis paralysis. Set a hard deadline of February 15 to finalize the IPS and stop reading. -- [[person-marco-bianchi]] shared his own investment framework, which was helpful for validating the approach. His suggestion to keep a separate 6-month emergency fund in a high-yield savings account was incorporated. -- The [[24q2-stock-screener]] experiment later in the year was a brief detour into individual stock analysis, but it reinforced the decision to stick with passive investing. The time spent did not justify the marginal (and uncertain) returns. -- Quarterly reviews are tracked as part of [[responsibility-personal-finance]]. The first two reviews in 2024 showed minimal drift, confirming that the set-and-forget approach works as intended. diff --git a/demo-vault-v2/24q1.md b/demo-vault-v2/24q1.md deleted file mode 100644 index 45f696d1..00000000 --- a/demo-vault-v2/24q1.md +++ /dev/null @@ -1,31 +0,0 @@ ---- -aliases: ["Q1 2024"] -Is A: Quarter -Created at: "2024-01-01" -Belongs to: "[[2024]]" -Has: ["[[24q1-launch-sponsorship-packages]]", "[[24q1-redesign-newsletter-template]]", "[[24q1-plan-cycling-season]]", "[[24q1-set-investing-framework]]", "[[24q1-podcast-season-1]]"] -Status: Done ---- -# Q1 2024 - -## Focus - -The first quarter of 2024 was about laying foundations. After a strong 2023, the goal was to professionalize the business side of Refactoring — move from ad-hoc sponsor deals to structured packages, refresh the newsletter design, and finally launch the podcast that had been in planning for months. On the personal side, I wanted to get the cycling season mapped out early and put a real investing framework in place. - -## Highlights - -- Launched [[24q1-launch-sponsorship-packages]] with three tiers (Gold, Silver, Bronze) — immediately booked two Gold sponsors for Q2 -- Shipped [[24q1-redesign-newsletter-template]] with a cleaner layout, better mobile rendering, and improved CTA placement — [[measure-open-rate]] ticked up ~1.5pp -- Recorded and released the first four episodes of [[24q1-podcast-season-1]], crossing 2k downloads in the first month -- Mapped out the full [[24q1-plan-cycling-season]] including target events: Nove Colli in May and Maratona dles Dolomites in July (goal: [[2024-complete-two-gran-fondos]]) -- Built out [[24q1-set-investing-framework]] — monthly DCA into a global ETF portfolio, emergency fund topped up -- Newsletter crossed 37k subscribers by end of March, up from ~35k at year start -- [[person-matteo-cellini]] closed the first two sponsor deals under the new packages within weeks of launch - -## Reflections - -Q1 felt like the quarter where things started clicking into place on the business side. The sponsorship packages were long overdue — I'd been doing custom deals for every sponsor, which was eating time and leaving money on the table. Having a clear menu made everything faster: [[person-matteo-cellini]] could sell without looping me in on every detail, and sponsors appreciated the transparency. - -The podcast launch was nerve-wracking. I'd been procrastinating on it for almost a year, finding reasons to delay. But once the first episode went live and the feedback started coming in, I wondered why I'd waited so long. The format — 20-minute deep dives on one engineering leadership topic — resonated immediately. Production quality was rough in the first couple of episodes, but it improved fast. - -On the personal front, planning the cycling season early was a game changer. Having Nove Colli and Maratona on the calendar gave structure to my training weeks. The investing framework was less exciting but equally important — automating contributions meant I could stop thinking about it and focus on building the business. All in all, a solid start to [[2024]]. diff --git a/demo-vault-v2/24q2-10-pillar-articles.md b/demo-vault-v2/24q2-10-pillar-articles.md deleted file mode 100644 index 1d228ffa..00000000 --- a/demo-vault-v2/24q2-10-pillar-articles.md +++ /dev/null @@ -1,36 +0,0 @@ ---- -aliases: ["Write 10 Pillar Articles"] -Is A: Project -Belongs to: "[[24q2]]" -Advances: "[[responsibility-content-production]]" -Status: Done -Owner: "[[person-luca-rossi]]" ---- -# Write 10 Pillar Articles - -## Overview - -This project focused on creating 10 long-form "pillar" articles — comprehensive, SEO-optimized pieces targeting high-traffic search terms in the engineering leadership and developer productivity space. These articles serve a dual purpose: they drive organic search traffic to the Refactoring website (feeding [[measure-subscribers]] growth) and establish topical authority that supports [[2024-reach-50k-subscribers]]. - -Each article was 2,500-4,000 words, thoroughly researched, and structured for both readability and search engine performance. Topics were selected based on keyword research using Ahrefs, focusing on terms with decent search volume (1K-10K monthly) and moderate competition. The articles were published on the Refactoring blog and cross-promoted through the newsletter over [[24q2]]. - -## Goals - -- Research and select 10 high-value keyword targets using Ahrefs -- Write 10 articles of 2,500-4,000 words each, with clear structure and internal linking -- Optimize each article for on-page SEO (meta descriptions, headers, image alt text) -- Publish on a bi-weekly cadence throughout Q2 -- Achieve first-page Google ranking for at least 3 target keywords within 6 months - -## Key decisions - -- **Evergreen topics only.** All 10 articles target topics that will remain relevant for 2+ years (e.g., "how to run effective 1:1s," "staff engineer vs. engineering manager"). Avoided trending or news-driven topics that would decay quickly. -- **Newsletter-first drafts, then expanded for SEO.** Several articles started as popular newsletter issues that were expanded with additional depth, examples, and structure. This reduced research time and ensured the topics had proven audience interest. -- **No freelance writers.** Considered outsourcing some articles but decided that the Refactoring voice is too distinctive to delegate at this stage. [[person-sara-ricci]] edited all 10 pieces, which maintained quality while freeing time for drafting. - -## Notes - -- Writing 10 pillar articles in one quarter while maintaining the weekly newsletter was extremely demanding. Weeks 5-8 were particularly brutal — the output quality dipped on newsletter issues during that period. In hindsight, 7-8 articles would have been more sustainable. -- The article on "Engineering Manager vs. Tech Lead" became the highest-performing piece, ranking on page 1 within 8 weeks and driving ~3,000 monthly organic visits. This single article accounted for about 30% of the total organic traffic from all 10 pieces. -- Internal linking between pillar articles and existing newsletter content created a noticeable boost in site-wide SEO metrics. Average session duration increased by 40% during Q2. -- This project directly informed [[topic-content-strategy]] and established the content pillar framework that was later extended in [[25q1-newsletter-seo-sprint]]. diff --git a/demo-vault-v2/24q2-build-podcast-landing-page.md b/demo-vault-v2/24q2-build-podcast-landing-page.md deleted file mode 100644 index d4a69aab..00000000 --- a/demo-vault-v2/24q2-build-podcast-landing-page.md +++ /dev/null @@ -1,36 +0,0 @@ ---- -aliases: ["Build Podcast Landing Page"] -Is A: Project -Belongs to: "[[24q2]]" -Advances: "[[responsibility-podcast]]" -Status: Done -Owner: "[[person-luca-rossi]]" ---- -# Build Podcast Landing Page - -## Overview - -After launching the podcast in [[24q1-podcast-season-1]], it became clear that there was no proper home for the show on the web. Episodes were scattered across Apple Podcasts, Spotify, and YouTube, but there was no single page where listeners could browse the archive, read show notes, and subscribe. This project created a dedicated landing page on the Refactoring website to serve as the podcast's canonical home. - -The page needed to work both as a discovery tool for new listeners and as a reference for existing ones. It also needed to support sponsor visibility, since podcast sponsorships were part of the package tiers defined in [[24q1-launch-sponsorship-packages]]. The page was built using the existing site's tech stack (Next.js) and went live in early May. - -## Goals - -- Design and build a podcast landing page with episode archive, show notes, and embedded audio player -- Include subscribe CTAs for Apple Podcasts, Spotify, YouTube, and RSS -- Add a "Featured Guest" section to highlight notable episodes and drive social proof -- Integrate sponsor logos and links for current podcast sponsors -- Ensure the page is mobile-responsive and loads quickly (target: <2s LCP) - -## Key decisions - -- **Static generation, not dynamic.** Each episode page is statically generated at build time from a markdown file with frontmatter metadata. This keeps hosting costs zero (Vercel free tier) and ensures fast page loads. New episodes trigger a rebuild via a GitHub webhook. -- **Embedded player, not custom.** Used the native Spotify/Apple embed widgets rather than building a custom audio player. The maintenance cost of a custom player was not justified given that most listeners use their preferred podcast app anyway. -- **Show notes as full articles.** Rather than just listing bullet points, each episode's show notes page is a full article with key takeaways, timestamps, and links. This gives the pages SEO value and provides genuine utility for listeners who prefer reading to listening. - -## Notes - -- The page design went through two iterations. The first version was too sparse — just a list of episodes with play buttons. [[person-giulia-conti]] suggested adding guest photos and pull quotes, which made the page significantly more engaging. -- Getting the embedded players to render correctly across browsers was more annoying than expected. Spotify's embed widget has inconsistent height behavior on Safari. Ended up using a fixed-height iframe with a fallback link. -- The landing page became the default link shared in the newsletter for podcast promotion, replacing direct Spotify/Apple links. This centralized analytics tracking through [[measure-podcast-downloads]] and gave better visibility into listener behavior. -- Page traffic is modest (~500 unique visitors/month) but steady, and it ranks for several long-tail podcast-related keywords. The SEO investment in show notes is paying off gradually. diff --git a/demo-vault-v2/24q2-hire-editor.md b/demo-vault-v2/24q2-hire-editor.md deleted file mode 100644 index 45d302e7..00000000 --- a/demo-vault-v2/24q2-hire-editor.md +++ /dev/null @@ -1,36 +0,0 @@ ---- -aliases: ["Hire Editor (Sara)"] -Is A: Project -Belongs to: "[[24q2]]" -Advances: "[[responsibility-team-management]]" -Status: Done -Owner: "[[person-luca-rossi]]" ---- -# Hire Editor (Sara) - -## Overview - -By mid-2024, writing the weekly newsletter, managing sponsorships, recording podcast episodes, and handling business operations was becoming unsustainable as a solo operation. The most impactful hire at this stage was an editor — someone who could elevate the writing quality, reduce revision cycles, and free up time for higher-leverage activities like strategy and guest relationships. - -After a lightweight hiring process, [[person-sara-ricci]] joined as a part-time editor in May 2024. Sara had previous experience editing technical content for developer publications, which was critical — engineering leadership content requires an editor who understands the domain, not just grammar. This hire directly supported scaling [[responsibility-content-production]] and was a prerequisite for hitting [[2024-reach-50k-subscribers]]. - -## Goals - -- Define the editor role: scope, hours, compensation, and working relationship -- Source and evaluate 5-10 candidates through network referrals and job boards -- Run a paid trial edit with top 3 candidates using a real newsletter draft -- Onboard the selected editor with style guide, editorial calendar, and tooling access -- Achieve a steady-state workflow where drafts go through one editorial pass before publish - -## Key decisions - -- **Part-time contractor, not full-time employee.** The workload did not justify a full-time hire yet, and contractor status keeps the arrangement flexible as the business scales. Sara works approximately 15 hours/week. -- **Paid trial before commitment.** Rather than hiring based on interviews alone, asked the top 3 candidates to edit the same newsletter draft. This revealed huge differences in editorial judgment that interviews could not surface. Sara's edits were the most substantive — she restructured sections and challenged weak arguments, not just fixed typos. -- **Editor has veto power on publish readiness.** Gave Sara explicit authority to push back on drafts that are not ready. This was uncomfortable at first but has significantly improved quality. If Sara says it needs another pass, it gets another pass. - -## Notes - -- The hiring process took about 4 weeks from posting to signed contract. Received ~30 applications, shortlisted 8, did calls with 5, trial edits with 3. The trial edit step was by far the most valuable signal. -- Biggest adjustment was learning to write "editor-friendly" first drafts — meaning rough structure and arguments are solid, but prose is intentionally unpolished. Trying to write perfectly on the first pass and then having an editor change it creates friction. Better to write fast and let Sara shape the prose. -- Sara also took on podcast show notes editing, which was not in the original scope but made sense as her familiarity with the content grew. This expanded into the workflow documented in [[procedure-podcast-editing]]. -- [[person-matteo-cellini]] recommended Sara — they had worked together at a previous company. Network referrals continue to be the best hiring channel for roles that require domain expertise. diff --git a/demo-vault-v2/24q2-sponsor-crm.md b/demo-vault-v2/24q2-sponsor-crm.md deleted file mode 100644 index 01e313ae..00000000 --- a/demo-vault-v2/24q2-sponsor-crm.md +++ /dev/null @@ -1,36 +0,0 @@ ---- -aliases: ["Set Up Sponsor CRM"] -Is A: Project -Belongs to: "[[24q2]]" -Advances: "[[responsibility-sponsorships]]" -Status: Done -Owner: "[[person-luca-rossi]]" ---- -# Set Up Sponsor CRM - -## Overview - -With sponsorship deals increasing after [[24q1-launch-sponsorship-packages]], tracking outreach, deal status, invoicing, and renewals in a spreadsheet was no longer viable. This project built a proper CRM system in Airtable to manage the full sponsor lifecycle — from initial outreach through booking, fulfillment, reporting, and renewal. - -The CRM needed to support [[procedure-quarterly-sponsor-outreach]] and [[procedure-sponsor-onboarding]] while being lightweight enough for a one-person sales operation (with occasional help from [[person-matteo-cellini]] on outreach). The system went live in April 2024 and has been the backbone of sponsor management since, directly supporting [[2024-double-revenue]]. - -## Goals - -- Design an Airtable base with tables for Companies, Contacts, Deals, Invoices, and Placements -- Build views for pipeline management (kanban), upcoming renewals, and revenue tracking -- Set up automations for deal stage notifications and renewal reminders (30 days before expiry) -- Import existing sponsor data from the old spreadsheet (~15 companies, ~25 deals) -- Document the CRM workflow and train [[person-matteo-cellini]] on outreach tracking - -## Key decisions - -- **Airtable, not a dedicated CRM tool.** Evaluated HubSpot, Pipedrive, and Notion. HubSpot was overkill (and expensive) for ~50 deals/year. Pipedrive was close but lacked the flexibility for tracking placement fulfillment. Airtable's combination of structured data, views, and automations hit the sweet spot for this scale. -- **Deal-centric model, not contact-centric.** The primary entity is the Deal (a specific sponsorship booking), not the Contact or Company. This reflects the actual workflow — most actions are about advancing a specific deal, not managing a relationship in the abstract. -- **Automated renewal reminders at 30 and 7 days.** Renewal is the highest-leverage moment in the sponsor lifecycle. Automating reminders ensures no renewal slips through the cracks, which was happening with the spreadsheet system. - -## Notes - -- Migrating from the spreadsheet exposed several data quality issues — duplicate companies, inconsistent naming, missing invoice dates. Cleaning this up took a full day but was worth it for a clean foundation. -- The kanban view for pipeline management became the default "daily check" for sponsor operations. Being able to see all deals by stage (Prospect, Outreach, Negotiation, Booked, Fulfilled, Renewed) at a glance changed how proactive the outreach process feels. -- Airtable's automation limits on the free plan were a constraint. Upgraded to the Team plan ($20/month) to get enough automation runs. The cost is trivial relative to the revenue it manages. -- [[measure-sponsorship-mrr]] is now calculated directly from the CRM data, which eliminated the manual reconciliation that was happening before. Revenue reporting went from a quarterly headache to an always-current dashboard. diff --git a/demo-vault-v2/24q2-spring-gran-fondo.md b/demo-vault-v2/24q2-spring-gran-fondo.md deleted file mode 100644 index 8bd1861c..00000000 --- a/demo-vault-v2/24q2-spring-gran-fondo.md +++ /dev/null @@ -1,37 +0,0 @@ ---- -aliases: ["Spring Gran Fondo 2024"] -Is A: Project -Belongs to: "[[24q2]]" -Advances: "[[responsibility-health-fitness]]" -Status: Done -Owner: "[[person-luca-rossi]]" ---- -# Spring Gran Fondo 2024 - -## Overview - -This was the first of two target events for 2024, as planned in [[24q1-plan-cycling-season]]. The Granfondo di Varese — 130km with 2,200m of elevation gain — served as both a fitness benchmark and a motivational milestone for the spring training block. The event was scheduled for late May, giving a solid 12-week build phase from March through mid-May. - -Preparation included structured interval training (3 sessions/week), long weekend rides (4-5 hours), and two recon rides on sections of the actual course. The goal was not to race competitively but to complete the full route in under 5 hours and 30 minutes, maintaining good form throughout. This project directly advanced [[2024-complete-two-gran-fondos]]. - -## Goals - -- Complete the Granfondo di Varese full route (130km, 2,200m elevation) in under 5:30 -- Execute the 12-week build training plan with at least 80% adherence -- Complete two course recon rides to familiarize with key climbs and descents -- Maintain race weight (72kg) through the build phase -- Log all training data for post-event analysis via [[measure-cycling-km-per-month]] - -## Key decisions - -- **Full route, not the medio.** The event offered a 90km "medio" option. Chose the full 130km because the training plan was designed for it, and the shorter route would not provide a meaningful fitness test. If the legs failed on race day, it would be better to know that at full distance. -- **Conservative pacing strategy.** Rather than going hard on the first climb (which is where most amateurs blow up), planned to ride the first 60km at 75% of threshold power and increase effort in the second half. This negative-split approach is less exciting but far more reliable. -- **No travel the day before.** Drove to Varese two days before the event to avoid travel fatigue. Stayed at a simple hotel near the start line. The extra cost was worth the better sleep and relaxed morning. - -## Notes - -- Finished in 5:17, which was well within the target. The conservative pacing strategy worked perfectly — felt strong on the final climb while many riders around were walking. Negative split confirmed: second half was 3 minutes faster than the first. -- Training adherence was about 85%, which was above target. The two weeks lost to a mild cold in April were compensated by extending the build phase slightly and cutting one recovery week short. -- [[person-paco-furiani]] rode the event as well and finished about 20 minutes ahead. His feedback on nutrition strategy (eating every 30 minutes from the start, not waiting until hungry) was a game-changer. Applied the same approach going forward. -- Biggest lesson: the mental game matters more than fitness above a certain threshold. The climbs at km 90-110 were physically manageable but mentally draining. Having a clear pacing target on the bike computer helped maintain focus. -- Post-event recovery took about 10 days before training resumed. This feeds into preparation for the autumn event, which was later scoped as a separate project. diff --git a/demo-vault-v2/24q2-stock-screener.md b/demo-vault-v2/24q2-stock-screener.md deleted file mode 100644 index c2c0fb9a..00000000 --- a/demo-vault-v2/24q2-stock-screener.md +++ /dev/null @@ -1,35 +0,0 @@ ---- -aliases: ["Vibe-coding a Stock Screener"] -Is A: Experiment -Belongs to: "[[24q2]]" -Status: Done -Owner: "[[person-luca-rossi]]" ---- -# Vibe-coding a Stock Screener - -Built a stock screener in Python over a weekend to test whether a simple EMA bounce strategy could surface actionable trade setups on US equities. The broader motivation was to explore whether personal tooling for investment analysis could complement the [[procedure-monthly-portfolio-review]] and eventually improve [[measure-net-worth]] trajectory. - -## Hypothesis - -A lightweight, self-built screener using exponential moving average crossovers would surface 2-3 viable swing trade candidates per week, outperforming manual chart scanning in both speed and consistency. - -## Setup - -- Wrote a Python script pulling daily OHLCV data from Yahoo Finance for the S&P 500 universe. -- Implemented a 21/50 EMA bounce filter: flag stocks where price touches the 21 EMA from above, with the 50 EMA still trending up. -- Ran the screener nightly via cron for 4 weeks, logging all flagged tickers and tracking outcomes over 10-day windows. -- Compared results against manual chart review done for the same period. - -## Results - -- The screener flagged an average of 5 candidates per day (higher than expected). -- Roughly 40% of flagged setups produced a positive 10-day return above 2%. -- Manual chart review caught about 60% of the same setups, but took 3x longer. -- False positives were mostly in low-volume mid-caps where the bounce pattern was noise. - -## Takeaways - -- Vibe-coding a quick tool like this is a high-leverage weekend project. Total effort was about 8 hours. -- The EMA bounce strategy has signal, but needs volume and volatility filters to reduce false positives. -- Automating the screener freed up time previously spent on manual scanning for the [[procedure-monthly-portfolio-review]]. -- Worth maintaining as a personal tool. Not worth productizing, but could become a newsletter content piece on [[topic-personal-finance]]. diff --git a/demo-vault-v2/24q2-video-format-test.md b/demo-vault-v2/24q2-video-format-test.md deleted file mode 100644 index bbd1a017..00000000 --- a/demo-vault-v2/24q2-video-format-test.md +++ /dev/null @@ -1,36 +0,0 @@ ---- -aliases: ["Video Format Experiment"] -Is A: Experiment -Belongs to: "[[24q2]]" -Status: Abandoned -Owner: "[[person-luca-rossi]]" ---- -# Video Format Experiment - -Tested whether short-form video (3-5 minute explainers) could work as a distribution channel alongside the newsletter. The idea was to repurpose existing [[responsibility-content-production]] into video format to reach audiences who prefer visual content, potentially feeding [[measure-subscribers]] growth from a new channel. - -## Hypothesis - -Publishing 2 short technical explainer videos per week on YouTube and Twitter would generate at least 500 new newsletter subscribers over 6 weeks, with a production cost under 3 hours per video once a workflow was established. - -## Setup - -- Produced 3 videos covering topics already published as newsletter essays: system design patterns, engineering management tips, and a career growth framework. -- Used screen recording with voiceover (no face camera) to minimize production overhead. -- Published on YouTube Shorts and Twitter/X with a newsletter CTA in the description and pinned comment. -- Tracked view counts, click-through to newsletter signup, and time spent per video. - -## Results - -- Total views across 3 videos: ~4,200 (mostly Twitter, YouTube was negligible). -- Newsletter signups attributed to video: 23 total. -- Average production time: 5-6 hours per video (scripting, recording, editing, captioning). -- The time-to-subscriber ratio was roughly 15x worse than writing a newsletter essay. - -## Takeaways - -- Video production cost was significantly underestimated. Editing and captioning alone took 2+ hours per video. -- The audience overlap between short-form video viewers and newsletter subscribers appears small. -- Abandoned after 3 videos. The ROI does not justify the effort given current team size and [[responsibility-content-production]] bandwidth. -- If revisited, would need a dedicated video editor or a fundamentally simpler format (e.g., talking head with no editing). -- Better to double down on written content and [[topic-newsletter-growth]] strategies that already work. diff --git a/demo-vault-v2/24q2.md b/demo-vault-v2/24q2.md deleted file mode 100644 index 391b9e2b..00000000 --- a/demo-vault-v2/24q2.md +++ /dev/null @@ -1,32 +0,0 @@ ---- -aliases: ["Q2 2024"] -Is A: Quarter -Created at: "2024-04-01" -Belongs to: "[[2024]]" -Has: ["[[24q2-hire-editor]]", "[[24q2-build-podcast-landing-page]]", "[[24q2-10-pillar-articles]]", "[[24q2-spring-gran-fondo]]", "[[24q2-sponsor-crm]]"] -Status: Done ---- -# Q2 2024 - -## Focus - -Q2 was the execution quarter. With the foundations from Q1 in place, the focus shifted to scaling content production and building systems that could run without me doing everything. Hiring an editor was the biggest unlock. On the cycling side, Nove Colli was the target — months of base training coming to a head. - -## Highlights - -- [[24q2-hire-editor]] completed — brought on a freelance editor who now handles first-pass editing on every newsletter issue, saving me 4-5 hours per week -- Published [[24q2-10-pillar-articles]]: long-form pieces on topics like "Staff Engineer vs. Manager" and "Technical Debt Prioritization" — two of them hit 50k+ views -- Built and launched [[24q2-build-podcast-landing-page]] with episode archive, show notes, and Apple/Spotify links — podcast downloads crossed 5k/month -- Completed Nove Colli ([[24q2-spring-gran-fondo]]) in 7h42m — not my best time, but finished strong on the climbs -- Shipped [[24q2-sponsor-crm]] in Notion — tracking pipeline, renewal dates, and revenue per sponsor in one place -- Newsletter hit 42k subscribers by end of June, right on track for the [[2024-reach-50k-subscribers]] goal -- [[person-paco-furiani]] started handling more operational tasks — invoicing, sponsor logistics, calendar management -- [[measure-sponsorship-mrr]] reached EUR 8.2k, up from EUR 5.5k at start of year - -## Reflections - -This was the quarter where I started to feel the leverage of having a small team. With [[person-matteo-cellini]] handling sponsor relationships and [[person-paco-furiani]] taking on operations, I could actually focus on writing and recording. The editor hire was transformative — I went from spending Sunday evenings frantically editing to having a polished draft waiting for me on Monday morning. - -The pillar articles strategy paid off more than expected. Instead of chasing weekly topics, I invested in fewer, deeper pieces that could rank on search and get shared. "Staff Engineer vs. Manager" alone brought in 800+ new subscribers organically. This shifted my thinking about content strategy: depth over frequency. - -Nove Colli was harder than I expected. The heat in Romagna in late May was brutal, and I bonked on the fourth climb. But crossing the finish line in Cesenatico — exhausted, sunburned, grinning — reminded me why I do this. Already looking forward to Maratona in July. The cycling and the business run on the same fuel: consistent effort over months, then showing up on race day. [[2024-complete-two-gran-fondos]] is halfway done. diff --git a/demo-vault-v2/24q3-codemotion-talk.md b/demo-vault-v2/24q3-codemotion-talk.md deleted file mode 100644 index cc8b153e..00000000 --- a/demo-vault-v2/24q3-codemotion-talk.md +++ /dev/null @@ -1,36 +0,0 @@ ---- -aliases: ["Speak at Codemotion Milan"] -Is A: Project -Belongs to: "[[24q3]]" -Advances: "[[responsibility-content-production]]" -Status: Done -Owner: "[[person-luca-rossi]]" ---- -# Speak at Codemotion Milan - -## Overview - -Codemotion Milan 2024 invited [[person-luca-rossi]] to deliver a 30-minute talk on growing a newsletter business as a technical founder. The talk, titled "From Side Project to 50K Subscribers: Building a Content Business in Public," covered the Refactoring growth story, key inflection points, and practical lessons for engineers considering content as a career path or side business. - -This was the first major conference speaking engagement and represented an important step in building personal brand credibility beyond the newsletter audience. Conference talks drive a different kind of trust than written content — they put a face and voice to the brand, which strengthens both subscriber acquisition and sponsor confidence. The talk was well-received and led to several valuable connections, including two future podcast guests. - -## Goals - -- Write and rehearse a 30-minute talk with slides -- Target key themes: newsletter economics, audience building, and the engineering-to-content pipeline -- Deliver the talk at Codemotion Milan in October 2024 -- Record the talk for repurposing as a YouTube video and newsletter content -- Generate at least 200 new newsletter subscribers from the event - -## Key decisions - -- **Story-driven structure, not a how-to.** Rather than a generic "10 tips for growing a newsletter" format, structured the talk as a chronological narrative of the Refactoring journey. Stories are more memorable and more authentic than advice lists. -- **Include real numbers.** Shared actual subscriber counts, revenue milestones, and open rates. Transparency is a core Refactoring value and it differentiates the talk from vague "I grew my audience" presentations. This decision was slightly uncomfortable but generated the most positive feedback. -- **No live demo.** Considered showing the newsletter creation process live but decided the risk of technical issues on stage was not worth it. Used screenshots and short video clips instead. - -## Notes - -- Preparation took about 3 weeks of part-time work — mostly slide design and rehearsal. Rehearsed the full talk 5 times, including twice in front of [[person-sara-ricci]] and [[person-matteo-cellini]] who gave tough but useful feedback on pacing and clarity. -- The audience was about 300 people, skewing toward mid-career developers and engineering managers. Q&A was lively — the most common question was about time management (how to write a weekly newsletter while also doing other work). This became a topic for a future newsletter issue. -- Post-talk networking led to meeting [[person-emma-wilson]] and [[person-david-kim]], both of whom later appeared as podcast guests in [[24q3-podcast-season-2]] and [[25q2-podcast-season-3]] respectively. -- The talk recording was published on YouTube and performed modestly (~2,500 views in 3 months), but the subscriber spike from the event itself was about 180 — slightly below the 200 target but still a strong result for a single event. The real value was in credibility and relationship building, not direct conversion. diff --git a/demo-vault-v2/24q3-morning-journaling.md b/demo-vault-v2/24q3-morning-journaling.md deleted file mode 100644 index 11ded0c1..00000000 --- a/demo-vault-v2/24q3-morning-journaling.md +++ /dev/null @@ -1,36 +0,0 @@ ---- -aliases: ["Morning Journaling Habit"] -Is A: Experiment -Belongs to: "[[24q3]]" -Status: Done -Owner: "[[person-luca-rossi]]" ---- -# Morning Journaling Habit - -Ran an 8-week experiment with daily morning journaling to evaluate its impact on focus, decision-making clarity, and overall stress management. This ties into the broader theme of personal operating systems: if running a content business and training for cycling events simultaneously, mental bandwidth becomes the bottleneck, and journaling is often cited as a way to decompress and prioritize. - -## Hypothesis - -Writing 10-15 minutes each morning (freeform, no template) would reduce decision fatigue and improve weekly [[measure-task-completion-rate]] by at least 10%, while also providing a subjective sense of reduced stress. - -## Setup - -- Journaled every morning for 8 weeks using a plain markdown file in the vault. -- No rigid template: some days were gratitude lists, some were brain dumps, some were planning sessions. -- Tracked adherence (did I journal today? yes/no), subjective stress rating (1-5), and weekly task completion rate. -- Weeks 1-4 were during a high-stress period (podcast launch prep for [[24q3-podcast-season-2]] and newsletter deadlines). Weeks 5-8 were calmer. - -## Results - -- Adherence: 85% in weeks 1-4 (high stress), dropped to 55% in weeks 5-8 (low stress). -- Subjective stress rating improved by ~0.8 points on average during weeks 1-4. -- Task completion rate showed no statistically meaningful change (too many confounding variables). -- The most useful entries were "decision journals" where a specific choice was weighed explicitly. - -## Takeaways - -- Morning journaling is most valuable during high-stress, high-decision-load periods. It acts as a pressure valve. -- During calm stretches, the habit felt forced and adherence dropped naturally. This is fine; it does not need to be daily forever. -- Decision journals (structured: "What am I deciding? What are the options? What do I fear?") were the highest-signal format. -- Will keep journaling as a situational tool rather than a rigid daily habit. Likely to resurface during intense project sprints like [[25q1-laputa-v1]]. -- No direct impact on [[measure-task-completion-rate]], but the qualitative clarity benefit is real. diff --git a/demo-vault-v2/24q3-new-sponsor-verticals.md b/demo-vault-v2/24q3-new-sponsor-verticals.md deleted file mode 100644 index f5362ea7..00000000 --- a/demo-vault-v2/24q3-new-sponsor-verticals.md +++ /dev/null @@ -1,37 +0,0 @@ ---- -aliases: ["Expand Sponsor Verticals"] -Is A: Project -Belongs to: "[[24q3]]" -Advances: "[[responsibility-sponsorships]]" -Status: Done -Owner: "[[person-luca-rossi]]" ---- -# Expand Sponsor Verticals - -## Overview - -The first two quarters of sponsorship revenue came primarily from developer tools (CI/CD, monitoring, testing platforms). While this vertical was reliable, concentration risk was high — losing one or two devtools sponsors could significantly impact [[measure-sponsorship-mrr]]. This project expanded the sponsor base into three new verticals: cloud infrastructure, AI/ML platforms, and developer education. - -Expanding verticals required adapting the outreach messaging and media kit to resonate with different buyer personas. Cloud infra companies care about enterprise decision-makers in the audience; AI/ML companies want to reach early adopters; education companies want ambitious individual developers. [[person-matteo-cellini]] led much of the outreach effort, using the CRM built in [[24q2-sponsor-crm]] to manage the pipeline. This project was critical for [[2024-double-revenue]]. - -## Goals - -- Identify 30+ target companies across cloud infrastructure, AI/ML, and developer education verticals -- Adapt the media kit with vertical-specific audience data and case studies -- Run targeted outreach campaigns for each vertical (10+ companies each) -- Close at least 5 new sponsors from the new verticals by end of [[24q3]] -- Achieve vertical diversification: no single vertical should represent more than 40% of sponsorship revenue - -## Key decisions - -- **Three verticals, not more.** Considered also targeting recruitment platforms and SaaS tools, but decided to focus on three verticals where the audience fit was strongest. Spreading too thin would dilute outreach quality. -- **Vertical-specific case studies.** Rather than using a generic media kit, created tailored one-pagers for each vertical showing relevant audience segments. For example, the cloud infra pitch highlighted the percentage of readers who are engineering managers or directors (the buying decision-makers for infrastructure). -- **Higher pricing for AI/ML vertical.** AI/ML companies had larger marketing budgets and higher urgency to reach developers. Tested a 20% price premium on the Deep Dive tier for this vertical, and it held without pushback. - -## Notes - -- Cloud infrastructure was the easiest vertical to crack — many companies were already familiar with newsletter sponsorships and had established budgets for developer marketing. Closed 3 deals in this vertical within 6 weeks. -- AI/ML was more volatile — companies had budget but were less predictable. Two deals fell through after verbal commitment because of budget freezes. The companies that did close were excellent sponsors with high renewal rates. -- Developer education was harder than expected. Many education companies preferred affiliate/commission models over flat-rate sponsorships. Only closed 1 deal in this vertical during Q3, though it renewed for 3 months. -- By end of Q3, vertical distribution was: devtools 35%, cloud infra 30%, AI/ML 25%, education 10%. This was a significant improvement from the previous 85% devtools concentration. -- The outreach templates developed during this project became part of [[procedure-quarterly-sponsor-outreach]] and continue to be used with minor updates. diff --git a/demo-vault-v2/24q3-podcast-season-2.md b/demo-vault-v2/24q3-podcast-season-2.md deleted file mode 100644 index 4cc491b6..00000000 --- a/demo-vault-v2/24q3-podcast-season-2.md +++ /dev/null @@ -1,37 +0,0 @@ ---- -aliases: ["Podcast Season 2"] -Is A: Project -Belongs to: "[[24q3]]" -Advances: "[[responsibility-podcast]]" -Status: Done -Owner: "[[person-luca-rossi]]" ---- -# Podcast Season 2 - -## Overview - -Building on the momentum from [[24q1-podcast-season-1]], Season 2 expanded the podcast to 8 episodes with a focused theme on engineering leadership and organizational design. The season explored how high-performing engineering teams are structured, how technical leaders make decisions, and the human dynamics that make or break engineering organizations. - -The production workflow was significantly smoother this time — [[person-sara-ricci]] handled all post-production editing using the [[procedure-podcast-editing]] workflow established during Season 1, and [[person-paco-furiani]] helped with guest research and outreach. The landing page built in [[24q2-build-podcast-landing-page]] served as the canonical home for all episodes. Season 2 launched in July and ran through September. - -## Goals - -- Record and publish 8 episodes on engineering leadership and org design -- Secure higher-profile guests (target: at least 2 guests with 10K+ Twitter following) -- Grow average episode downloads to 2,000 (up from Season 1's ~1,500 average) -- Introduce a podcast sponsorship slot (mid-roll read) aligned with newsletter sponsor packages -- Improve audio quality: all episodes recorded on Riverside.fm with backup local recordings - -## Key decisions - -- **Themed season with a narrative arc.** Rather than random topics, structured Season 2 around a progression: from individual contributor leadership (episodes 1-2) to team dynamics (3-4) to org design (5-6) to executive leadership (7-8). This gave the season a cohesive feel and encouraged binge listening. -- **Mid-roll sponsor read, not pre-roll.** Tested sponsor placements and found that mid-roll reads (inserted at a natural break around the 15-minute mark) had significantly better recall and click-through than pre-roll. This aligned with the sponsorship packages from [[24q1-launch-sponsorship-packages]]. -- **No video this season.** Dropped the video component entirely to reduce production overhead. The video clips from Season 1 generated minimal YouTube traction, and the effort-to-impact ratio was poor. Refocused entirely on audio quality. - -## Notes - -- Guest booking was easier in Season 2 — having a published Season 1 with real download numbers made outreach emails far more credible. Response rate improved from ~15% to ~30%. -- [[person-emma-wilson]] (VP Engineering at a Series C startup) was the standout guest — her episode on "Building Engineering Culture from Scratch" became the most downloaded episode of the season (~3,200 downloads) and was widely shared on LinkedIn. -- Average downloads per episode reached 2,100, exceeding the 2,000 target. The newsletter cross-promotion and improved show notes SEO from [[24q2-build-podcast-landing-page]] were the primary growth drivers. -- The podcast sponsorship slot generated about $1,500 in additional monthly revenue during the season, which validated the channel as a revenue stream alongside newsletter sponsorships. -- [[measure-podcast-downloads]] showed a clear pattern: downloads spike on newsletter send days and taper gradually. This confirms that the newsletter audience is the primary distribution channel for the podcast. diff --git a/demo-vault-v2/24q3-premium-tier.md b/demo-vault-v2/24q3-premium-tier.md deleted file mode 100644 index 6a363e09..00000000 --- a/demo-vault-v2/24q3-premium-tier.md +++ /dev/null @@ -1,37 +0,0 @@ ---- -aliases: ["Launch Premium Newsletter Tier"] -Is A: Project -Belongs to: "[[24q3]]" -Advances: "[[responsibility-grow-newsletter]]" -Status: Abandoned -Owner: "[[person-luca-rossi]]" ---- -# Launch Premium Newsletter Tier - -## Overview - -This project explored adding a paid subscription tier to the Refactoring newsletter. The hypothesis was that a segment of the audience would pay $10/month for premium content — deeper case studies, exclusive interviews, and a private community. If successful, this would create a second revenue stream alongside sponsorships and reduce dependency on a single monetization model. - -The premium tier launched in mid-July with a 2-week free trial. After 6 weeks of operation, conversion rates were significantly below projections (0.3% vs. the 2% target), and the incremental content burden was unsustainable alongside the free newsletter and podcast. The project was abandoned in early September. While the outcome was a clear negative, the experiment provided valuable data about the audience's willingness to pay and the true cost of premium content production. - -## Goals - -- Design the premium tier: pricing, content cadence, and exclusive features -- Set up Substack paid subscriptions with a 2-week free trial -- Create 4 premium-only deep dives to serve as the initial content library -- Acquire 200 paying subscribers within the first 6 weeks -- Evaluate viability: target a sustainable $2,000/month from paid subscriptions - -## Key decisions - -- **$10/month, not $5 or $15.** Benchmarked against similar engineering newsletters. $5 felt too cheap to justify the effort; $15 was above what comparable newsletters charged. $10 was the market rate, but it turned out the audience was not price-sensitive — they simply did not want to pay for content that was perceived as similar to the free tier. -- **Deep dives as the core premium offering.** Rather than gating regular newsletter issues, created separate premium-only deep dives (3,000-5,000 words). This preserved the free newsletter's value while offering something genuinely different. The problem was that the deep dives took 8-10 hours each to write, making the unit economics terrible at low subscriber counts. -- **Abandoned rather than pivoted.** Considered pivoting to a community-only premium tier (no premium content, just Discord access), but decided the timing was wrong. The audience was not large enough to sustain a vibrant paid community. Revisiting community as a concept in [[25q3-community-launch]] with a different approach. - -## Notes - -- The 0.3% conversion rate was the clearest signal. Industry benchmarks for engineering newsletters suggest 1-3% is typical. Being at 0.3% meant the value proposition was fundamentally off, not just undermarketed. -- The 60 subscribers who did convert were highly engaged and gave positive feedback. Several said they subscribed to "support the newsletter" rather than for the premium content itself. This suggests a patronage model (like Patreon) might work better than a content-gated model. -- The biggest cost was not financial but attentional. Writing premium deep dives while maintaining the free newsletter, podcast, and sponsor obligations created unsustainable pressure during July-August. [[person-sara-ricci]] flagged this early and was right. -- Key lesson: for a sponsorship-funded newsletter, adding paid subscriptions creates a conflict. Free reach drives sponsor value; gating content behind a paywall reduces reach. The two models work against each other unless the audience is very large. Better to focus on growing [[measure-subscribers]] and increasing sponsor rates. -- This experiment informed the decision to try [[25q1-paid-newsletter-trial]] with a completely different approach (annual pricing, bundled with podcast content). diff --git a/demo-vault-v2/24q3-summer-reading-sprint.md b/demo-vault-v2/24q3-summer-reading-sprint.md deleted file mode 100644 index 11016140..00000000 --- a/demo-vault-v2/24q3-summer-reading-sprint.md +++ /dev/null @@ -1,37 +0,0 @@ ---- -aliases: ["Summer Reading Sprint"] -Is A: Project -Belongs to: "[[24q3]]" -Advances: "[[responsibility-learning]]" -Status: Done -Owner: "[[person-luca-rossi]]" ---- -# Summer Reading Sprint - -## Overview - -July and August are traditionally lighter months for the newsletter (sponsors pause, audience engagement dips during European summer holidays), which creates space for deeper reading. This project set an intentional reading goal of 6 books in two months, focused on history, business, and philosophy of science — topics that inform the newsletter's intellectual depth without being directly "content research." - -The sprint contributed to [[2024-read-24-books]] and was structured around dedicated morning reading blocks (7:00-8:30 AM, before work) and longer sessions during weekends. The mix of topics was deliberate: history for perspective, business for practical frameworks, and philosophy of science for clearer thinking about complex systems. - -## Goals - -- Read 6 books in July and August (3 per month) -- Topic mix: 2 history, 2 business, 2 philosophy of science -- Write brief reading notes for each book in the vault -- Identify at least 3 ideas from the reading that can be developed into newsletter issues -- Maintain the reading habit: minimum 45 minutes per day, 6 days per week - -## Key decisions - -- **Curated list, not discovery-driven.** Selected all 6 books before the sprint began rather than picking the next book after finishing one. This avoided the decision fatigue that usually slows down reading between books. The list was finalized in late June. -- **Physical books only.** Committed to reading physical copies rather than Kindle during the sprint. The tactile experience and absence of screen distractions improved focus and retention. Kindle is fine for casual reading, but for a concentrated sprint, physical books won. -- **Notes in the vault, not Goodreads.** All reading notes written as markdown files in the personal vault rather than on Goodreads or a public platform. The notes are for personal reference and newsletter idea generation, not social signaling. - -## Notes - -- Completed 5 of 6 books (83% completion). The sixth book (a dense history of the Scientific Revolution) was about 60% finished by end of August and completed in early September. Close enough to call it a success. -- The standout read was "The Innovator's Dilemma" (re-read) — it directly influenced thinking about the newsletter's competitive dynamics and informed two Q4 newsletter issues on disruption in developer tools. -- Morning reading blocks worked exceptionally well. The consistency of a fixed time slot made the habit nearly automatic by the third week. This approach has been maintained beyond the sprint. -- [[person-marco-bianchi]] recommended "The Structure of Scientific Revolutions" (Kuhn), which turned out to be the most intellectually challenging and rewarding book of the sprint. The concept of paradigm shifts maps surprisingly well onto how engineering organizations evolve. -- Three newsletter issues in Q4 drew directly from the reading: one on Christensen's disruption theory applied to DevOps tools, one on historical patterns in technology adoption, and one on mental models from philosophy of science. The reading-to-content pipeline works, but with a 2-3 month delay. diff --git a/demo-vault-v2/24q3.md b/demo-vault-v2/24q3.md deleted file mode 100644 index 5dcf021a..00000000 --- a/demo-vault-v2/24q3.md +++ /dev/null @@ -1,32 +0,0 @@ ---- -aliases: ["Q3 2024"] -Is A: Quarter -Created at: "2024-07-01" -Belongs to: "[[2024]]" -Has: ["[[24q3-premium-tier]]", "[[24q3-codemotion-talk]]", "[[24q3-summer-reading-sprint]]", "[[24q3-podcast-season-2]]", "[[24q3-new-sponsor-verticals]]"] -Status: Done ---- -# Q3 2024 - -## Focus - -Q3 was about diversifying revenue and expanding reach. The premium tier launch was the biggest bet — adding a paid subscription layer on top of the free newsletter. I also committed to a speaking slot at Codemotion and kicked off Season 2 of the podcast. On the personal side, summer meant a reading sprint and Maratona dles Dolomites. - -## Highlights - -- Launched [[24q3-premium-tier]] with deep-dive case studies, templates, and a monthly AMA — 320 paid subscribers in the first 6 weeks -- Delivered [[24q3-codemotion-talk]] on "Scaling Engineering Culture" to ~400 attendees — led to 3 inbound sponsor inquiries and a burst of new subscribers -- Completed [[24q3-summer-reading-sprint]]: read 8 books in July-August including "An Elegant Puzzle", "Team Topologies", and "The Ride of a Lifetime" -- Recorded and shipped [[24q3-podcast-season-2]] (episodes 13-24) — introduced guest interviews, with [[person-sara-ricci]] helping coordinate guests -- Opened [[24q3-new-sponsor-verticals]] targeting DevOps tooling and cloud platforms, expanding beyond the original developer tools niche -- Newsletter hit 46k subscribers — [[2024-reach-50k-subscribers]] within reach -- Completed Maratona dles Dolomites in 9h15m — [[2024-complete-two-gran-fondos]] achieved -- [[measure-podcast-downloads]] reached 8k/month, nearly 4x since launch - -## Reflections - -The premium tier launch taught me a lot about pricing psychology. I initially set it at EUR 8/month, then bumped to EUR 12/month after the first week when conversion was higher than expected. The people who pay aren't price-sensitive — they want signal, not savings. The AMA calls turned out to be the most valued feature, which I didn't expect. Hearing directly from engineering leaders about their challenges gives me better content ideas than any amount of keyword research. - -Codemotion was a turning point for visibility. Speaking on stage to 400 people, then having a line of folks wanting to chat afterward — it hit me that Refactoring had become a real brand, not just "Luca's newsletter." Three sponsors reached out within a week of the talk. [[person-matteo-cellini]] converted two of them. - -Finishing Maratona was the personal highlight of the year. The Dolomites are otherworldly — Passo Giau at dawn, with the peaks turning pink, was one of those moments where you forget about pace and just exist. Both gran fondos done, [[2024-complete-two-gran-fondos]] checked off. The [[24q3-summer-reading-sprint]] kept me intellectually fueled during the quieter August weeks. Heading into Q4 feeling strong on all fronts. diff --git a/demo-vault-v2/24q4-annual-review-process.md b/demo-vault-v2/24q4-annual-review-process.md deleted file mode 100644 index 28a51051..00000000 --- a/demo-vault-v2/24q4-annual-review-process.md +++ /dev/null @@ -1,36 +0,0 @@ ---- -aliases: ["Team Annual Review"] -Is A: Project -Belongs to: "[[24q4]]" -Advances: "[[responsibility-team-management]]" -Status: Done -Owner: "[[person-luca-rossi]]" ---- -# Team Annual Review - -## Overview - -As the Refactoring team grew from a solo operation to a small but functional team, it became clear that informal check-ins were not sufficient for aligning on expectations, giving structured feedback, and planning development. This project designed and executed the first formal annual review process for the three team members: [[person-matteo-cellini]] (sponsorship outreach), [[person-paco-furiani]] (operations and podcast support), and [[person-sara-ricci]] (editing). - -The goal was not to create a heavyweight corporate HR process but to establish a lightweight, honest, and useful review cycle that fits a small indie team. Reviews happened in December 2024, covering the full calendar year, and set the stage for [[25q1]] planning. The process was designed to be reusable and will run annually going forward. - -## Goals - -- Design a review template covering: role scope, key accomplishments, areas for growth, and goals for next year -- Write a self-assessment prompt for each team member to complete before the review meeting -- Conduct 1-hour review conversations with each team member -- Document agreed-upon goals and any compensation adjustments for 2025 -- Establish this as a repeatable annual process with a calendar reminder and documented procedure - -## Key decisions - -- **Conversation-first, not form-first.** The review is structured around a 1-hour conversation, not a lengthy written form. The self-assessment is a short (half-page) prompt to help team members reflect before the meeting. The conversation is where the real feedback happens. -- **Bidirectional feedback.** Each team member was explicitly asked to give feedback on working with [[person-luca-rossi]] — what works, what does not, what they need more of. This was uncomfortable but produced the most actionable insights of the entire process. -- **Compensation adjustments tied to review, not negotiation.** Rather than waiting for team members to ask for raises, proactively included compensation review as part of the process. All three team members received adjustments based on expanded scope and demonstrated value. - -## Notes - -- [[person-sara-ricci]]'s review was the most impactful. She articulated clearly that the editing workflow needed more lead time — receiving drafts 24 hours before publish was creating unnecessary stress and reducing edit quality. This led to adjusting the [[procedure-weekly-newsletter]] timeline to give her 48 hours minimum. -- [[person-matteo-cellini]] expressed interest in taking on more strategic work beyond outreach execution. This was a growth signal — his Q4 performance on [[24q3-new-sponsor-verticals]] showed he could handle strategic thinking, not just tactical execution. Agreed to expand his role in 2025. -- [[person-paco-furiani]] was the most straightforward review — he is happy with his current role scope and compensated fairly. His main feedback was wanting more visibility into the business roadmap, which is a fair ask. Started sharing quarterly plans with the full team afterward. -- The process took about 6 hours total (prep + 3 conversations + documentation). This is very manageable for a small team. The key learning: do this every year, not just when it feels necessary. Scheduled the 2025 review for December in advance. diff --git a/demo-vault-v2/24q4-black-friday-campaign.md b/demo-vault-v2/24q4-black-friday-campaign.md deleted file mode 100644 index cb52914b..00000000 --- a/demo-vault-v2/24q4-black-friday-campaign.md +++ /dev/null @@ -1,37 +0,0 @@ ---- -aliases: ["Black Friday Newsletter Campaign"] -Is A: Project -Belongs to: "[[24q4]]" -Advances: "[[responsibility-grow-newsletter]]" -Status: Done -Owner: "[[person-luca-rossi]]" ---- -# Black Friday Newsletter Campaign - -## Overview - -Black Friday represents a unique opportunity for a technical newsletter: readers are actively looking for tool and resource recommendations, and companies are offering significant discounts. This project designed and executed a curated Black Friday campaign — a special edition newsletter with hand-picked tool recommendations for engineering leaders and developers, paired with a subscriber acquisition push through social media and cross-promotions. - -The campaign ran from November 25-29, 2024, and generated +1,200 new subscribers in 3 days — the single largest acquisition spike of the year. The key insight was that curation is the value: readers do not want to sift through hundreds of generic deals. They want a trusted voice telling them which 10-15 tools are actually worth buying. This directly supported [[2024-reach-50k-subscribers]] and pushed the subscriber count past the 48K mark. - -## Goals - -- Curate a list of 15-20 Black Friday deals on developer tools, SaaS products, and learning resources -- Negotiate exclusive or enhanced discount codes with at least 5 companies -- Publish a special-edition newsletter issue on Black Friday week -- Run a social media campaign (Twitter, LinkedIn) driving traffic to the newsletter signup with the deal list as the lead magnet -- Acquire 1,000+ new subscribers during the campaign window - -## Key decisions - -- **Curated recommendations, not affiliate links.** While affiliate revenue was tempting, prioritized trust over short-term monetization. Every recommendation was a tool that [[person-luca-rossi]] personally uses or has thoroughly evaluated. Included honest caveats alongside recommendations. This authenticity drove shares and word-of-mouth signups. -- **Gated the full list behind email signup.** Shared 5 deals publicly on social media with a CTA to "get the full list of 20 deals" via newsletter signup. This was the primary acquisition mechanism and converted at approximately 35% of landing page visitors. -- **Separate from regular sponsor placements.** Black Friday sponsors paid a premium rate for a dedicated section, clearly labeled as "sponsored picks." This maintained editorial integrity while monetizing the high-attention window. Three sponsors participated at $3,000 each. - -## Notes - -- The +1,200 subscribers in 3 days was remarkable, but retention was the real test. At the 30-day mark, 78% of Black Friday subscribers were still active (industry benchmark is ~60% for acquisition spikes). This suggests the deal-seekers were genuinely interested in the newsletter's regular content, not just the deals. -- Negotiating exclusive discount codes with tool companies was easier than expected. Most developer tool companies are eager for newsletter placement during Black Friday and will create custom codes quickly. Started these conversations in early November — next year, will start in October. -- [[person-matteo-cellini]] handled sponsor coordination for the campaign, managing the three premium placements. His work on the CRM ([[24q2-sponsor-crm]]) made tracking these deals seamless. -- The social media push was amplified significantly by retweets/reshares from the tools featured in the list. This organic amplification was not planned but accounted for an estimated 30-40% of the total reach. Will be more intentional about asking for shares in future campaigns. -- [[measure-subscribers]] jumped from ~46,800 to ~48,000 during the campaign. Combined with organic growth, this put the year-end total within striking distance of the 50K target set in [[2024-reach-50k-subscribers]]. diff --git a/demo-vault-v2/24q4-cycling-year-review.md b/demo-vault-v2/24q4-cycling-year-review.md deleted file mode 100644 index c68c2040..00000000 --- a/demo-vault-v2/24q4-cycling-year-review.md +++ /dev/null @@ -1,38 +0,0 @@ ---- -aliases: ["Cycling Year in Review 2024"] -Is A: Project -Belongs to: "[[24q4]]" -Advances: "[[responsibility-health-fitness]]" -Status: Done -Owner: "[[person-luca-rossi]]" ---- -# Cycling Year in Review 2024 - -## Overview - -This project reviewed the full 2024 cycling season — training volumes, event results, fitness progression, and gear decisions — and used the analysis to plan the 2025 season. The review covered everything from the spring training plan established in [[24q1-plan-cycling-season]] through the two gran fondos and into the autumn detraining period. - -The review was conducted in November-December, using data from Strava, TrainingPeaks, and personal notes. It combined quantitative analysis (volume, intensity distribution, power data) with qualitative reflection (what felt good, what caused fatigue, where motivation dipped). The output was both a retrospective document and a set of concrete recommendations for [[25q1-strength-program]] and the 2025 race calendar. - -## Goals - -- Compile and analyze full-year training data: total distance, climbing, hours, and TSS -- Review performance at both gran fondos (Varese in May, Appennino in September) -- Assess the effectiveness of the polarized training model adopted in Q1 -- Identify 3-5 specific areas for improvement in 2025 -- Draft a preliminary 2025 season plan including target events and training philosophy adjustments - -## Key decisions - -- **Add structured strength training for 2025.** The year review revealed that upper body and core fatigue was a limiter on long climbs. Pure cycling volume is not enough — need complementary strength work. This directly led to [[25q1-strength-program]]. -- **Target the Stelvio in 2025.** The two 2024 gran fondos were rewarding but relatively conservative choices. For 2025, the stretch goal is the Stelvio — one of cycling's most iconic climbs. This requires a step up in training specificity and altitude preparation. Supports [[2025-ride-stelvio]]. -- **Hire a coach for 2025.** Self-coaching worked reasonably well in 2024 (both events completed within targets), but the Stelvio goal requires more sophisticated periodization and real-time plan adjustments. Will look for a coach in Q1. - -## Notes - -- Full-year numbers: 8,200 km ridden, 98,000m elevation gain, approximately 320 hours on the bike. This was above target (7,500 km) and sustainable — no overtraining symptoms or significant injuries. -- The polarized model (80% easy / 20% hard) was broadly successful, though the actual distribution ended up closer to 75/25 because "easy" rides often crept into moderate territory. Discipline on easy days is something to improve. -- [[person-paco-furiani]] completed the same two events and his season review is a useful comparison point. His higher-volume approach (10,500 km) yielded better absolute results but also led to a knee issue in October. Reinforces the value of sustainability over pure volume. -- The Campagnolo Bora WTO 45 wheels purchased pre-season were the best equipment decision of the year. Noticeable improvement on climbs and crosswind stability. No regrets on prioritizing wheels over frame upgrade. -- [[measure-cycling-km-per-month]] data shows clear seasonal pattern: low in Jan-Feb (800-900km/month), building through Mar-May (1,000-1,200km), peaking in Jun-Aug (1,200-1,400km), and tapering in Sep-Nov. December was deliberately rest-focused (~400km). -- The retrospective feeds directly into [[topic-cycling-training]] notes and sets the direction for 2025 season planning. diff --git a/demo-vault-v2/24q4-laputa-start.md b/demo-vault-v2/24q4-laputa-start.md index 2af0ecf0..71479bcb 100644 --- a/demo-vault-v2/24q4-laputa-start.md +++ b/demo-vault-v2/24q4-laputa-start.md @@ -1,37 +1,17 @@ --- -aliases: ["Start Laputa App Project"] -Is A: Project -Belongs to: "[[24q4]]" -Advances: "[[responsibility-learning]]" -Status: Done -Owner: "[[person-luca-rossi]]" +type: Project +aliases: + - "[[Start Laputa App Project]]" +belongs_to: "[[24q4]]" +owner: "[[person-luca-rossi]]" +status: Done --- + # Start Laputa App Project -## Overview +The original spike that proved Tolaria could read a markdown vault, render note metadata, and support keyboard-first navigation. -After years of managing a personal knowledge vault in Obsidian and finding it increasingly insufficient for the structured, frontmatter-heavy workflow that had evolved, this project kicked off the development of Laputa — a custom desktop application built specifically for the vault's unique requirements. The app is built with Tauri v2 (Rust backend) and React (TypeScript frontend), designed to read and write the same markdown files with YAML frontmatter that the vault already uses. +- Set the initial four-panel layout. +- Proved the note list, editor, and inspector could coexist in one flow. +- Led directly into [[25q1-laputa-v1]]. -The motivation was not to replace Obsidian for general note-taking, but to build a purpose-built tool for the structured data layer — types, relationships, properties, and views that Obsidian handles poorly. Laputa treats the vault as a lightweight database of markdown files, offering a four-panel UI with type-aware navigation, property editing, and relational browsing. This project covers the initial spike: architecture decisions, proof of concept, and first working prototype. It advances [[2025-ship-laputa]] as the longer-term goal. - -## Goals - -- Define the technical architecture: Tauri v2, React 18, CodeMirror 6, Vite -- Build a proof of concept that reads markdown files from a directory and displays them in a panel UI -- Implement frontmatter parsing in Rust (using serde and gray_matter) -- Create the basic four-panel layout: type sidebar, note list, editor, and property panel -- Validate that the app can handle the full vault (~9,200 markdown files) without performance issues - -## Key decisions - -- **Tauri v2, not Electron.** Tauri produces much smaller binaries, uses less memory, and leverages native webview rather than shipping a full Chromium instance. For a single-user desktop app, Tauri's trade-offs (no cross-platform webview consistency, newer ecosystem) are acceptable. The Rust backend is also more natural for file I/O heavy workloads. -- **Files as the source of truth, not a database.** Laputa reads and writes markdown files directly. No SQLite, no JSON store, no separate database. This means the vault remains portable, version-controllable with git, and readable in any text editor. The cost is that some queries are slower than they would be with a database, but for ~10K files, filesystem operations are fast enough. -- **CodeMirror 6, not ProseMirror or TipTap.** CodeMirror 6 provides the best foundation for a reveal-on-focus markdown editor — showing rendered markdown by default but revealing raw syntax when the cursor enters a block. This is the editing model that feels most natural for power users. - -## Notes - -- The initial proof of concept took about 3 weeks of focused evening/weekend work. Getting Tauri v2 set up and communicating between the Rust backend and React frontend required working through several documentation gaps — Tauri v2 was still relatively new and the ecosystem was evolving. -- Performance testing with the full vault (~9,200 files) showed that initial directory scanning takes about 2 seconds, and frontmatter parsing adds another 1.5 seconds. This is acceptable for app startup, though indexing will need optimization for real-time search. -- [[person-david-kim]] (who works on developer tools) provided useful early feedback on the UI concept during a podcast conversation. His perspective on tool-building for personal use versus building products helped frame the project's scope. -- The mock data layer (`src/mock-tauri.ts`) was built early and proved invaluable for browser-based testing. Being able to develop and test the React frontend without the Rust backend running dramatically accelerated UI iteration. -- This project transitions directly into [[25q1-laputa-v1]] for the first real milestone of the app. diff --git a/demo-vault-v2/24q4-linkedin-crossposting.md b/demo-vault-v2/24q4-linkedin-crossposting.md deleted file mode 100644 index 1529e741..00000000 --- a/demo-vault-v2/24q4-linkedin-crossposting.md +++ /dev/null @@ -1,37 +0,0 @@ ---- -aliases: ["LinkedIn Cross-posting Experiment"] -Is A: Experiment -Belongs to: "[[24q4]]" -Status: Done -Owner: "[[person-luca-rossi]]" ---- -# LinkedIn Cross-posting Experiment - -Tested whether repurposing newsletter essays as LinkedIn posts could drive meaningful follower growth and referral traffic back to the newsletter. LinkedIn's algorithm favors native content, so the hypothesis was that adapted versions of existing essays would perform well without requiring net-new writing effort, supporting both [[responsibility-grow-newsletter]] and [[topic-newsletter-growth]]. - -## Hypothesis - -Posting 3 adapted newsletter essays per week on LinkedIn for 6 weeks would generate at least 500 new LinkedIn followers and drive 200+ clicks to the newsletter signup page, at under 30 minutes of incremental work per post. - -## Setup - -- Selected the top-performing newsletter essays from [[24q3]] and [[24q4]] based on [[measure-open-rate]]. -- Adapted each essay into LinkedIn-native format: shorter paragraphs, hook-first structure, no external links in the body (link in first comment instead). -- Posted 3x per week (Monday, Wednesday, Friday) for 6 weeks. -- Tracked LinkedIn follower growth, post impressions, engagement rate, and UTM-tagged clicks to the newsletter signup page. - -## Results - -- LinkedIn followers: +812 over 6 weeks (from ~2,400 to ~3,200). -- Average post impressions: ~6,500 (range: 1,200 to 28,000). -- Newsletter signups via LinkedIn referral: 147 (below the 200 target but still meaningful). -- Time per post: approximately 20 minutes (mostly reformatting, not rewriting). -- Top-performing posts were contrarian takes and personal stories; tactical how-to posts underperformed. - -## Takeaways - -- LinkedIn cross-posting is a high-ROI channel for newsletter growth. The effort-to-output ratio is excellent since the content already exists. -- Follower growth exceeded the target. The platform rewards consistency and native formatting. -- Referral traffic was modest. LinkedIn users tend to engage on-platform rather than clicking out. The real value is brand awareness and top-of-funnel reach. -- Will continue cross-posting as a permanent part of the [[procedure-weekly-newsletter]] workflow. -- Consider having [[person-matteo-cellini]] handle the reformatting to free up time for [[responsibility-content-production]]. diff --git a/demo-vault-v2/24q4-sponsor-dashboard.md b/demo-vault-v2/24q4-sponsor-dashboard.md deleted file mode 100644 index e2c00a35..00000000 --- a/demo-vault-v2/24q4-sponsor-dashboard.md +++ /dev/null @@ -1,37 +0,0 @@ ---- -aliases: ["Build Sponsor Dashboard"] -Is A: Project -Belongs to: "[[24q4]]" -Advances: "[[responsibility-sponsorships]]" -Status: Done -Owner: "[[person-luca-rossi]]" ---- -# Build Sponsor Dashboard - -## Overview - -As the sponsor base grew through 2024, reporting became a bottleneck. After each newsletter issue, sponsors would ask for performance data — click counts, open rates, and placement impressions. This data was being compiled manually from ConvertKit analytics and sent via email, which was time-consuming and error-prone. This project built an Airtable-based dashboard that gives sponsors self-serve access to real-time performance data for their placements. - -The dashboard connects to the CRM built in [[24q2-sponsor-crm]] and pulls performance data from ConvertKit's API via a Zapier integration. Each sponsor gets a unique link to a filtered Airtable view showing only their placements, metrics, and invoice history. This project was a significant step toward professionalizing the sponsor experience and supporting [[2024-double-revenue]] through improved retention and upsell conversations. - -## Goals - -- Build an Airtable dashboard with per-sponsor performance data (clicks, CTR, impressions) -- Set up a Zapier integration to pull click and open data from ConvertKit after each newsletter send -- Create unique, filtered dashboard links for each sponsor (no login required, link-based access) -- Include historical performance trends (week-over-week, month-over-month) -- Reduce sponsor reporting time from ~2 hours/week to near-zero - -## Key decisions - -- **Airtable interface, not a custom web app.** Considered building a custom dashboard with Next.js and a database, but the engineering effort was not justified for ~20 active sponsors. Airtable's Interface Designer provides 80% of the functionality at 5% of the development cost. Can always migrate to a custom solution if the sponsor base grows significantly. -- **Self-serve access via unique links.** Rather than requiring sponsors to log into a portal, each sponsor gets a unique Airtable shared view URL. This is simpler for both parties — no password management, no onboarding friction. The trade-off is that anyone with the link can see the data, but the risk is low for non-sensitive marketing metrics. -- **Automated data ingestion, manual quality checks.** The Zapier integration pulls data automatically after each send, but [[person-matteo-cellini]] reviews the numbers weekly before they appear on sponsor dashboards. This catches any data anomalies (e.g., bot clicks, tracking issues) before sponsors see them. - -## Notes - -- The dashboard launch received very positive feedback from sponsors. Several mentioned it was the most transparent reporting they had seen from any newsletter sponsorship. This transparency became a competitive advantage in renewal conversations. -- The Zapier integration was the most fragile part of the system. ConvertKit's API rate limits and occasional data delays caused the integration to fail about once a month. Building retry logic and error notifications helped, but this remains a maintenance burden. -- Sponsor self-serve reporting reduced [[person-matteo-cellini]]'s weekly reporting workload from approximately 2 hours to about 15 minutes (just the quality review). This freed significant time for outreach and relationship management. -- The dashboard data also proved valuable for internal analysis. Being able to see click-through rates across all sponsors and placements revealed which types of copy and positioning perform best, informing both editorial decisions and sponsor pitch strategy. -- One unexpected benefit: sponsors who could see their own performance data were more likely to experiment with different ad copy and CTAs. This improved their results and, by extension, their satisfaction and renewal rates. The dashboard supported [[measure-sponsorship-mrr]] growth indirectly through improved retention. diff --git a/demo-vault-v2/24q4.md b/demo-vault-v2/24q4.md index e659f412..765b17e9 100644 --- a/demo-vault-v2/24q4.md +++ b/demo-vault-v2/24q4.md @@ -1,32 +1,16 @@ --- -aliases: ["Q4 2024"] -Is A: Quarter -Created at: "2024-10-01" -Belongs to: "[[2024]]" -Has: ["[[24q4-annual-review-process]]", "[[24q4-sponsor-dashboard]]", "[[24q4-laputa-start]]", "[[24q4-black-friday-campaign]]", "[[24q4-cycling-year-review]]"] -Status: Done +type: Quarter +aliases: + - "[[Q4 2024]]" +status: Done +has: + - "[[24q4-laputa-start]]" --- + # Q4 2024 -## Focus +The quarter where the Laputa prototype became real enough to replace sketches and notes. -Q4 was about closing the year strong and planting seeds for 2025. The Black Friday campaign was the commercial centerpiece. But the most exciting thing was starting work on [[24q4-laputa-start]] — the personal knowledge management tool I'd been sketching in notebooks for years. The quarter also meant wrapping up the annual review process and reflecting on a transformative cycling season. +- Started [[24q4-laputa-start]] as the first working app spike. +- Captured the initial panel layout and editor decisions. -## Highlights - -- [[24q4-black-friday-campaign]] drove 2,800 new subscribers in 10 days and converted 180 free readers to premium — best single campaign ever -- Built [[24q4-sponsor-dashboard]] giving sponsors real-time access to their campaign metrics — reduced back-and-forth emails by ~70% -- Started [[24q4-laputa-start]]: initial Tauri + React prototype, basic markdown reading, YAML frontmatter parsing — the MVP of the MVP -- Designed and documented [[24q4-annual-review-process]] — a structured template for reviewing goals, projects, and metrics across the year -- Completed [[24q4-cycling-year-review]]: 6,200 km ridden, two gran fondos, FTP up 12% year-over-year -- Newsletter crossed 50k subscribers in November — [[2024-reach-50k-subscribers]] achieved -- [[measure-sponsorship-mrr]] closed the year at EUR 11.4k, more than doubling from January — [[2024-double-revenue]] hit -- [[2024-read-24-books]] finished with 26 books total — exceeded target - -## Reflections - -Hitting 50k subscribers felt like a milestone that validated the whole year's strategy. When I started 2024 at 35k, doubling the growth rate felt ambitious. But the combination of pillar content, podcast reach, the Codemotion talk, and the Black Friday push all compounded. Each channel fed the others in ways I couldn't have predicted at the start of the year. - -Starting Laputa was the sleeper highlight of Q4. I'd been frustrated with Obsidian's limitations for months — specifically around structured data, relationships between notes, and the inability to build custom views. So I started building my own tool. The early prototype was rough, but the moment I saw my own vault rendered in a four-panel layout I'd designed, something clicked. This could be more than a side project. - -The sponsor dashboard was [[person-matteo-cellini]]'s idea, and it was brilliant. Sponsors love transparency, and giving them self-serve access to metrics reduced our support burden dramatically. [[person-paco-furiani]] set up the automated reporting pipeline. Looking back at [[2024]] as a whole, every major goal was hit or exceeded. That doesn't happen often, and I don't take it for granted. Now the question is: how do we scale this in [[2025]] without burning out? diff --git a/demo-vault-v2/25q1-laputa-v1.md b/demo-vault-v2/25q1-laputa-v1.md index 1bd22191..facbde0a 100644 --- a/demo-vault-v2/25q1-laputa-v1.md +++ b/demo-vault-v2/25q1-laputa-v1.md @@ -1,37 +1,17 @@ --- -aliases: ["Laputa App V1"] -Is A: Project -Belongs to: "[[25q1]]" -Advances: "[[responsibility-learning]]" -Status: Done -Owner: "[[person-luca-rossi]]" +type: Project +aliases: + - "[[Laputa App V1]]" +belongs_to: "[[25q1]]" +owner: "[[person-luca-rossi]]" +status: Done --- + # Laputa App V1 -## Overview +The first usable release for daily browsing, quick open, and note-property editing. -Following the proof of concept built in [[24q4-laputa-start]], this project delivered the first working version of Laputa with a complete four-panel layout, a property inspector, and a quick-open command palette. V1 represents the transition from "can this work?" to "I can actually use this daily" — the app became the primary interface for browsing and editing the vault, replacing Obsidian for structured data workflows. +- Shipped the working command palette. +- Made the inspector practical for real frontmatter editing. +- Captured enough confidence to continue with [[25q2-laputa-v2]]. -The four-panel layout includes a type sidebar (showing all note types like Project, Person, Quarter), a filterable note list, the main editor panel with CodeMirror 6, and a property inspector for viewing and editing YAML frontmatter fields. Quick Open (Cmd+K) enables instant navigation across all ~9,200 vault files. This milestone is a key step toward [[2025-ship-laputa]] and was completed during [[25q1]]. - -## Goals - -- Implement the four-panel layout with resizable panels and responsive behavior -- Build the property inspector panel for viewing and editing frontmatter properties -- Implement Quick Open (Cmd+K) with fuzzy search across all vault files -- Add type-aware sidebar navigation with collapsible sections and file counts -- Achieve sub-200ms navigation between notes (read file, parse frontmatter, render editor) - -## Key decisions - -- **CodeMirror 6 with reveal-on-focus editing.** The editor shows rendered markdown by default but reveals raw syntax when the cursor enters a block. This hybrid approach was chosen over a pure WYSIWYG editor (TipTap/ProseMirror) because power users need direct access to markdown syntax, especially for frontmatter and wiki-links. The reveal-on-focus model provides the best of both worlds. -- **Frontmatter parsing in Rust, rendering in React.** The Rust backend parses YAML frontmatter and provides structured data to the frontend via Tauri commands. This keeps the parsing fast and consistent, while React handles all presentation logic. The alternative — parsing in JavaScript — would be slower for bulk operations and harder to keep consistent with the Rust-side file operations. -- **Mock layer for browser development.** Built `src/mock-tauri.ts` to return realistic test data when running in a browser without the Tauri backend. This allows UI development and testing in Chrome without starting the full Rust backend, which dramatically accelerated the development loop. - -## Notes - -- The biggest engineering challenge was making the editor performant with large files. Some vault files are 5,000+ lines, and CodeMirror 6's default configuration struggled with these. Enabling viewport-based rendering and lazy decoration computation solved the performance issues. -- Quick Open search across 9,200 files needed careful optimization. The initial naive approach (filter on every keystroke) was too slow. Implemented a pre-built search index that loads at startup and supports fuzzy matching with sub-50ms response times. -- [[person-david-kim]] tested an early build and identified several UX issues with the property inspector — particularly around editing array-type frontmatter fields (like tags and aliases). His feedback led to a redesigned array editor with inline add/remove controls. -- The mock data layer proved its value immediately. It allowed running Playwright E2E tests and visual verification in Chrome without any Rust toolchain setup. This made CI testing feasible and significantly reduced the feedback loop for UI changes. -- V1 was usable but rough around the edges. The editor lacked many creature comforts (undo/redo state persistence, find-and-replace, syntax highlighting for YAML). These were deferred to [[25q2-laputa-v2]] to keep V1 scope manageable. diff --git a/demo-vault-v2/25q1-newsletter-seo-sprint.md b/demo-vault-v2/25q1-newsletter-seo-sprint.md deleted file mode 100644 index f725a206..00000000 --- a/demo-vault-v2/25q1-newsletter-seo-sprint.md +++ /dev/null @@ -1,37 +0,0 @@ ---- -aliases: ["Newsletter SEO Sprint"] -Is A: Project -Belongs to: "[[25q1]]" -Advances: "[[responsibility-grow-newsletter]]" -Status: Done -Owner: "[[person-luca-rossi]]" ---- -# Newsletter SEO Sprint - -## Overview - -Building on the pillar article strategy from [[24q2-10-pillar-articles]], this project was a concentrated 30-day sprint to boost organic search traffic and subscriber acquisition. The sprint had two components: writing 5 new high-traffic articles targeting keywords identified in an updated Ahrefs analysis, and overhauling the internal linking structure across all existing content to improve site-wide SEO authority. - -The sprint ran through February 2025 and was timed to take advantage of the post-holiday traffic recovery in the engineering content space. By this point, the blog had about 40 published articles, but many lacked internal links and had suboptimal meta descriptions. The combination of new content and structural improvements was designed to create a compounding traffic effect that would support [[2025-reach-85k-subscribers]] through organic growth. - -## Goals - -- Write and publish 5 new SEO-optimized articles (2,500-4,000 words each) -- Audit and update internal links across all existing blog posts (target: every article links to at least 3 other articles) -- Update meta descriptions and title tags for the 20 highest-traffic existing articles -- Improve site-wide Core Web Vitals scores (target: all pages in "Good" range) -- Achieve a 30% increase in organic search traffic within 90 days of sprint completion - -## Key decisions - -- **Concentrated sprint, not ongoing drip.** Rather than publishing one SEO article per month, concentrated the effort into a 30-day window. This allowed full focus on SEO without the context-switching cost of alternating between newsletter writing and SEO writing. The trade-off was that the regular newsletter required extra preparation in advance to cover the sprint period. -- **Internal linking overhaul as a force multiplier.** The internal linking audit was actually higher-impact than the new articles. Many existing articles had zero internal links, meaning Google could not discover or weight them properly. Adding contextual links between related articles created a proper content topology that improved rankings site-wide. -- **Content refresh over new content for some keywords.** For 3 keywords where existing articles were already ranking on page 2-3, chose to refresh and expand those articles rather than write new ones. Refreshing existing URLs preserves accumulated link equity and is faster than starting from scratch. - -## Notes - -- The 30% organic traffic increase was achieved in about 75 days (ahead of the 90-day target). The internal linking overhaul was the primary driver — several existing articles jumped from page 2 to page 1 within weeks of gaining internal links. -- [[person-sara-ricci]] edited all 5 new articles and the refreshed content. The editing workload during the sprint was significant, and she flagged that future sprints should give her more lead time. Noted for next time. -- The article on "How to Run Effective Engineering All-Hands" became the strongest performer, reaching #3 on Google for its target keyword and driving ~1,500 monthly organic visits. This single article generated an estimated 200 new subscribers per month through its email capture CTA. -- Core Web Vitals optimization required some technical work — lazy loading images, reducing JavaScript bundle size, and optimizing font loading. These changes improved site speed across the board and had a modest positive effect on rankings. -- This sprint validated the content pillar strategy and demonstrated that concentrated SEO investment compounds over time. The articles written in [[24q2-10-pillar-articles]] continued to grow in traffic alongside the new content, suggesting that the internal linking network creates a rising-tide effect. Feeds into [[topic-newsletter-growth]] and [[topic-content-strategy]]. diff --git a/demo-vault-v2/25q1-paid-newsletter-trial.md b/demo-vault-v2/25q1-paid-newsletter-trial.md deleted file mode 100644 index 35355b80..00000000 --- a/demo-vault-v2/25q1-paid-newsletter-trial.md +++ /dev/null @@ -1,36 +0,0 @@ ---- -aliases: ["Paid Newsletter Trial"] -Is A: Experiment -Belongs to: "[[25q1]]" -Status: Abandoned -Owner: "[[person-luca-rossi]]" ---- -# Paid Newsletter Trial - -Tested a Substack-style paid tier to evaluate whether the newsletter audience would convert to a direct subscription model. The motivation was to explore revenue diversification beyond [[measure-sponsorship-mrr]], which currently accounts for the majority of income. A paid tier could provide more predictable, audience-aligned revenue while reducing dependence on the sponsorship sales cycle. - -## Hypothesis - -Offering a paid tier at $10/month (or $100/year) with one exclusive deep-dive essay per month and early access to all posts would convert at least 2% of the free subscriber base within 8 weeks, generating $2,000+ MRR. - -## Setup - -- Built a paid tier on the existing newsletter platform with two perks: one exclusive monthly deep-dive and 48-hour early access to all free posts. -- Announced the paid tier via a dedicated newsletter issue, a pinned tweet, and a LinkedIn post. -- Ran a 2-week launch promotion at 50% off the annual plan. -- Tracked conversion rate, churn after first month, and qualitative feedback from subscribers who did and did not convert. - -## Results - -- Total paid subscribers after 8 weeks: 89 (approximately 0.2% of the free base, well below the 2% target). -- MRR generated: ~$620 (mix of monthly and discounted annual). -- Churn after first month: 18% of monthly subscribers cancelled. -- Qualitative feedback: most free subscribers said the free content was already "more than enough." Those who paid cited "supporting the creator" as the primary reason, not exclusive content. - -## Takeaways - -- The audience does not perceive enough differentiation between free and paid content to justify a subscription. The newsletter's value proposition is built on free, high-quality essays. -- Conversion was 10x below target. The paid tier would need a fundamentally different value prop (e.g., community, tools, templates) to work. -- Abandoned the paid tier to avoid splitting focus. The sponsorship model ([[responsibility-sponsorships]], [[24q1-launch-sponsorship-packages]]) delivers significantly higher revenue per hour of effort. -- If revisited, would explore a premium community model (see [[25q3-discord-community-soft]]) rather than paywalled content. -- Key lesson: do not assume that "more content" is a compelling paid offering. Access, community, and tools tend to convert better for this audience segment. diff --git a/demo-vault-v2/25q1-rate-increase.md b/demo-vault-v2/25q1-rate-increase.md deleted file mode 100644 index de0bd31a..00000000 --- a/demo-vault-v2/25q1-rate-increase.md +++ /dev/null @@ -1,37 +0,0 @@ ---- -aliases: ["Increase Sponsorship Rates Q2"] -Is A: Project -Belongs to: "[[25q1]]" -Advances: "[[responsibility-sponsorships]]" -Status: Done -Owner: "[[person-luca-rossi]]" ---- -# Increase Sponsorship Rates Q2 - -## Overview - -With the subscriber base approaching 60K and click-through performance data showing consistent improvement through 2024, the sponsorship rates set during [[24q1-launch-sponsorship-packages]] were underpriced relative to the audience value delivered. This project prepared and executed a 25% rate increase across all sponsorship tiers, effective for Q2 2025 bookings. - -The rate increase required careful preparation: assembling performance data, updating the media kit, communicating the changes to existing sponsors, and adjusting outreach messaging for new prospects. The goal was to increase [[measure-sponsorship-mrr]] without losing existing sponsors. [[person-matteo-cellini]] led the communication with current sponsors while [[person-luca-rossi]] handled the strategic positioning and media kit updates. - -## Goals - -- Analyze per-sponsor performance data to build the justification case (CTR, impressions, conversions) -- Update the media kit with current audience size, demographics, and performance benchmarks -- Communicate the rate increase to all existing sponsors with 60 days advance notice -- Update pricing across all three tiers: Logo ($625), Spotlight ($1,500), Deep Dive ($3,125) -- Retain at least 80% of existing sponsors through the transition - -## Key decisions - -- **25% increase, not 15% or 30%.** Benchmarked against similar-sized engineering newsletters and found the current rates were 20-35% below market. A 25% increase brings pricing to market rate while leaving room for another adjustment in 12-18 months as the audience continues to grow. -- **Grandfathered pricing for 90 days.** Offered existing sponsors who renewed before April 1 the option to lock in the old rate for one additional quarter. This rewarded loyalty and created urgency for renewals, which improved cash flow predictability. -- **Performance data as the lead message.** Rather than leading with "rates are going up," led with "here is how your sponsorship performed." Sharing concrete performance data first made the rate increase feel like a natural consequence of value delivered, not an arbitrary price hike. - -## Notes - -- Sponsor retention through the increase was 88% — above the 80% target. The two sponsors who did not renew cited budget constraints (not value concerns), which is a healthy signal. They indicated interest in returning at a future date. -- [[person-matteo-cellini]] handled the sponsor communication calls and reported that the response was overwhelmingly positive. Several sponsors said the previous rates felt "too cheap" and appreciated the transparency about pricing methodology. -- The rate increase translated to approximately $3,200/month in additional MRR, which was a significant contribution to [[2025-reach-22k-mrr]]. This was the highest-leverage revenue action of Q1 — no new sponsors needed, just better pricing for existing value. -- The updated media kit now includes a "Performance Highlights" section with anonymized case studies showing sponsor CTR and conversion data. This has become one of the most effective tools in the outreach process. -- Key lesson: rate increases should be proactive and regular (annually), not reactive and rare. Waiting too long to adjust pricing means leaving significant revenue on the table. The discomfort of raising prices is always greater in anticipation than in reality. diff --git a/demo-vault-v2/25q1-referral-program.md b/demo-vault-v2/25q1-referral-program.md deleted file mode 100644 index d0f78dcf..00000000 --- a/demo-vault-v2/25q1-referral-program.md +++ /dev/null @@ -1,38 +0,0 @@ ---- -aliases: ["Newsletter Referral Program"] -Is A: Project -Belongs to: "[[25q1]]" -Advances: "[[responsibility-grow-newsletter]]" -Status: Done -Owner: "[[person-luca-rossi]]" ---- -# Newsletter Referral Program - -## Overview - -Word-of-mouth had always been the newsletter's strongest organic growth channel, but it was entirely passive — readers shared when they felt like it, with no structured incentive. This project launched a formal referral program that rewards subscribers who bring in new readers, turning the most engaged audience members into active growth ambassadors. The program contributes to [[2025-reach-85k-subscribers]] and [[measure-subscribers]] growth. - -The program was built using SparkLoop (a referral platform designed for newsletters) and integrated with the existing ConvertKit setup. Rewards are tiered: 3 referrals earns a digital resource pack, 10 referrals earns a private Q&A session, and 25 referrals earns a 1-year premium membership. The program launched in February 2025 and immediately became the second-largest subscriber acquisition channel after organic search. - -## Goals - -- Design a tiered reward structure that motivates sharing without creating perverse incentives (spam, fake signups) -- Set up SparkLoop integration with ConvertKit for automated tracking and reward fulfillment -- Create shareable assets: personalized referral links, social cards, and email forward templates -- Acquire 2,000+ new subscribers through the referral program in Q1 -- Achieve a referral conversion rate of at least 20% (referred visitors who subscribe) - -## Key decisions - -- **SparkLoop, not a custom solution.** Evaluated building a custom referral system with unique links and a tracking database, but SparkLoop handles fraud detection, analytics, and reward automation out of the box. The $99/month cost is trivially justified by the subscriber value it generates. -- **Digital rewards, not physical.** Physical rewards (stickers, merchandise) create fulfillment complexity and shipping costs. Digital rewards (resource packs, access, sessions) scale infinitely and are more aligned with what the audience values. The private Q&A session at 10 referrals proved to be the most motivating tier. -- **Anti-fraud measures from day one.** Required referred subscribers to confirm via double opt-in and excluded signups from disposable email domains. This reduced fraudulent referrals to less than 2% of total, which is well below SparkLoop's industry average of 5-8%. - -## Notes - -- The referral program generated approximately 2,400 new subscribers in the first 8 weeks — above the 2,000 target. About 15% of the existing subscriber base activated their referral link, which is strong engagement for a referral program. -- The conversion rate on referred visitors was 28%, significantly above the 20% target. This makes sense: referred visitors arrive with a personal recommendation from someone they trust, which dramatically reduces the "should I subscribe?" friction. -- The top referrer brought in 47 new subscribers in the first month. Sent a personal thank-you email and offered an hour-long call. This kind of super-referrer engagement is worth cultivating. -- [[person-elena-rossi]] suggested adding a leaderboard showing top referrers (anonymized). Implemented this as a monthly "Referral Champions" section in the newsletter footer. It created a subtle competitive dynamic that boosted engagement. -- One unexpected finding: referred subscribers have higher 30-day retention (85%) compared to subscribers from other channels (~72% average). This suggests that referral-acquired subscribers are genuinely interested in the content, not just casually signing up. -- The program runs continuously and feeds into [[topic-newsletter-growth]]. The per-subscriber acquisition cost through referrals is approximately $0.40 (cost of SparkLoop + digital rewards amortized), compared to $2-3 for paid acquisition channels. diff --git a/demo-vault-v2/25q1-strength-program.md b/demo-vault-v2/25q1-strength-program.md deleted file mode 100644 index d2307ac1..00000000 --- a/demo-vault-v2/25q1-strength-program.md +++ /dev/null @@ -1,38 +0,0 @@ ---- -aliases: ["New Strength Program"] -Is A: Project -Belongs to: "[[25q1]]" -Advances: "[[responsibility-health-fitness]]" -Status: Done -Owner: "[[person-luca-rossi]]" ---- -# New Strength Program - -## Overview - -The [[24q4-cycling-year-review]] identified a clear gap: upper body and core strength were limiters on long climbs, and pure cycling volume was not addressing them. This project introduced a structured 12-week strength training program to complement the cycling training plan, with the primary goal of improving climbing performance and reducing injury risk for the 2025 season — specifically for [[2025-ride-stelvio]]. - -The program followed a progressive overload model with three sessions per week (Monday, Wednesday, Friday mornings), focusing on core stability, hip strength, and upper body endurance. The sessions were designed to be cycling-compatible — meaning they build functional strength without adding excessive muscle mass that would penalize climbing performance. The program ran from January through March 2025. - -## Goals - -- Complete a 12-week strength program with at least 85% session adherence -- Focus areas: core stability (planks, dead bugs, pallof press), hip strength (single-leg squats, hip thrusts), upper body endurance (rows, push-ups, shoulder press) -- Sessions capped at 45 minutes to fit before the work day -- Improve core endurance test (plank hold) from 2:00 to 3:00+ minutes -- No negative impact on cycling performance metrics (FTP, weekly TSS) - -## Key decisions - -- **Gym-based, not home-based.** Considered a bodyweight-only home program for convenience, but decided that gym access (barbells, cable machines) allows for more precise progressive overload. Signed up at a gym 10 minutes from home with early morning hours (opens 6:30 AM). -- **Three sessions per week, not two or four.** Two sessions would not provide sufficient stimulus for meaningful adaptation. Four would risk interfering with cycling recovery, especially during build-phase weeks. Three sessions, alternating between upper/lower focus, hit the sweet spot. -- **No heavy squats or deadlifts.** Traditional powerlifting movements build too much leg mass for a cyclist targeting climbing performance. Instead, focused on single-leg movements and moderate-weight, higher-rep schemes that build strength endurance rather than maximal strength. - -## Notes - -- Session adherence was 89% (32 of 36 planned sessions). The four missed sessions were all during a particularly heavy newsletter week in February. Built in makeup sessions the following week when possible. -- The plank hold test improved from 2:00 to 3:25 — well above the 3:00 target. More importantly, subjective feedback from early-season rides confirmed that upper body fatigue during long climbs was significantly reduced. -- [[person-paco-furiani]] joined for several sessions and followed a modified version of the same program. Training together added accountability and made the early morning sessions more tolerable. -- The biggest adaptation was not physical but scheduling. Finding 45 minutes three mornings per week while also cycling 8-10 hours per week and running a content business required ruthless calendar management. The key was treating strength sessions as non-negotiable appointments. -- No measurable negative impact on cycling FTP (remained at ~275W throughout the program). This confirmed that the moderate-weight, endurance-focused approach was compatible with cycling performance. -- The program transitions into a maintenance phase (2 sessions/week) during the peak cycling season. Detailed in [[topic-cycling-training]] notes. diff --git a/demo-vault-v2/25q1.md b/demo-vault-v2/25q1.md index fde3bb1f..a6ce6a7d 100644 --- a/demo-vault-v2/25q1.md +++ b/demo-vault-v2/25q1.md @@ -1,32 +1,13 @@ --- -aliases: ["Q1 2025"] -Is A: Quarter -Created at: "2025-01-01" -Belongs to: "[[2025]]" -Has: ["[[25q1-laputa-v1]]", "[[25q1-newsletter-seo-sprint]]", "[[25q1-strength-program]]", "[[25q1-rate-increase]]", "[[25q1-referral-program]]"] -Status: Done +type: Quarter +aliases: + - "[[Q1 2025]]" +status: Done +has: + - "[[25q1-laputa-v1]]" --- + # Q1 2025 -## Focus +The first period where Laputa was usable for daily navigation, quick open, and inspector flows. -Q1 2025 was about building momentum for the scale year. The two big bets were shipping Laputa v1 as a usable internal tool and pushing a sponsor rate increase now that we had the audience and metrics to justify it. On the content side, an SEO sprint to capture organic search traffic. On the fitness side, starting a strength training program to complement cycling. - -## Highlights - -- Shipped [[25q1-laputa-v1]] — four-panel layout, markdown rendering, frontmatter-driven navigation, and a working search. Using it daily for my own vault -- Executed [[25q1-rate-increase]]: raised Gold sponsorship from EUR 2.8k to EUR 3.5k per issue — retained 90% of sponsors, [[measure-sponsorship-mrr]] jumped to EUR 14.2k -- Launched [[25q1-referral-program]] with tiered rewards — drove 3,200 referral subscribers in Q1 -- [[25q1-newsletter-seo-sprint]]: optimized 15 pillar articles for search, added internal linking structure — organic traffic up 40% by March -- Started [[25q1-strength-program]]: 3x/week gym sessions focusing on core and legs — noticeable improvement in climbing power -- Newsletter reached 56k subscribers by end of March -- [[person-matteo-cellini]] onboarded two new enterprise sponsors at the higher rate with no pushback -- Podcast backlog strategy: released "best of Season 1 & 2" compilation episodes during recording break — maintained download numbers - -## Reflections - -The rate increase was the decision I was most nervous about. Raising prices always feels like you're testing whether the value you think you provide matches what the market believes. But [[person-matteo-cellini]] was right — we were underpriced. When sponsors didn't blink at the new rate, it was a clear signal we could have moved sooner. Lesson learned: if you're anxious about raising prices, you're probably already late. - -Laputa v1 was a labor of love. Spending evenings and weekends building a tool that only I use might seem indulgent, but it's the most energized I've felt about a coding project in years. There's something deeply satisfying about building software for a problem you understand intimately. The vault has 9,000+ files now, and seeing them organized in my own four-panel UI — types, relationships, properties — feels like the PKM tool I've been waiting for. - -The strength program was a humbling start. Years of cycling had given me good cardio but embarrassingly weak upper body strength. The first month was all DOMS and ego management. By March, though, I could feel the difference on the bike — more stable in the saddle, better power transfer on steep gradients. The [[2025-ride-stelvio]] goal feels more realistic with this foundation. Big quarter overall. [[2025]] is off to a strong start. diff --git a/demo-vault-v2/25q2-dolomites-trip.md b/demo-vault-v2/25q2-dolomites-trip.md deleted file mode 100644 index c8a771c3..00000000 --- a/demo-vault-v2/25q2-dolomites-trip.md +++ /dev/null @@ -1,38 +0,0 @@ ---- -aliases: ["Cycling Trip: Dolomites"] -Is A: Project -Belongs to: "[[25q2]]" -Advances: "[[responsibility-health-fitness]]" -Status: Done -Owner: "[[person-luca-rossi]]" ---- -# Cycling Trip: Dolomites - -## Overview - -This was the centerpiece event of the 2025 cycling season — a 5-day cycling trip through the Dolomites with [[person-paco-furiani]], tackling two of cycling's most legendary climbs: the Stelvio and the Mortirolo. The trip totaled approximately 650km with over 12,000m of elevation gain, and it represented the culmination of the training work from [[25q1-strength-program]] and the 2025 season plan outlined in [[24q4-cycling-year-review]]. - -The trip was planned as both a personal challenge and a goal completion event for [[2025-ride-stelvio]]. Route planning, accommodation booking, and logistics were handled in April-May, with the ride itself taking place in the second half of June when the high-altitude passes are reliably open and the weather is most favorable. Each day featured one major climb plus connecting roads through the valleys. - -## Goals - -- Complete the Stelvio from Bormio (the hardest side: 21.5km, 1,533m elevation gain, avg 7.1% gradient) -- Complete the Mortirolo from Mazzo (12.4km, 1,300m elevation gain, avg 10.5% gradient) -- Ride 5 consecutive days with an average of 130km and 2,400m elevation per day -- Maintain a sustainable pace throughout — no bonking, no mechanical failures, no injuries -- Document the trip with photos and notes for the vault and a potential newsletter piece - -## Key decisions - -- **Stelvio from Bormio, not Prato.** The Bormio side is considered the hardest but also the most dramatic — 48 hairpin turns through alpine scenery. The Prato side is more famous (classic from the Giro d'Italia) but less challenging. Chose difficulty over fame. -- **Self-supported, not organized tour.** Rather than joining a commercial cycling tour, planned the trip independently. This allowed full control over pacing, rest stops, and daily distance. Carried minimal gear (jersey pockets + a small saddle bag) and relied on valley-town hotels rather than mountain huts. -- **Rest day strategy: active recovery on day 3.** Rather than a full rest day mid-trip, did a short flat recovery ride (50km, no significant climbing) on day 3. This kept the legs moving and prevented the stiffness that comes from a complete rest day mid-tour. - -## Notes - -- The Stelvio was everything expected and more. Completed the climb in 2:08, which was within the target window (sub 2:15). The final 5km above the tree line, with the glacier visible ahead, were genuinely transcendent. The strength training from [[25q1-strength-program]] made a noticeable difference — upper body and core held up far better than they would have a year ago. -- The Mortirolo was harder than the Stelvio in terms of pure suffering. The sustained 10%+ gradients for 12km with minimal respite are relentless. Finished but it required every ounce of mental discipline. [[person-paco-furiani]] later said it was the hardest thing he has done on a bike. -- Nutrition strategy (eating every 25 minutes, starting from the first pedal stroke) worked perfectly. No bonking episodes across all 5 days. This was a direct application of the lesson from [[24q2-spring-gran-fondo]]. -- Day 4 featured unexpected rain on the descent from Passo Gavia, which made the wet hairpins genuinely nerve-wracking. Descended very conservatively (brake check every turn) and lost about 40 minutes compared to the planned schedule. Safety over speed — always. -- The trip generated a newsletter issue ("What Climbing the Stelvio Taught Me About Endurance") that became one of the most engaged pieces of the year. The personal story format resonated strongly with readers, even those who do not cycle. -- [[measure-cycling-km-per-month]] for June peaked at 1,450km — the highest monthly total ever. The Dolomites trip alone contributed 650km of that. diff --git a/demo-vault-v2/25q2-laputa-v2.md b/demo-vault-v2/25q2-laputa-v2.md index dc5e357f..2a40ac69 100644 --- a/demo-vault-v2/25q2-laputa-v2.md +++ b/demo-vault-v2/25q2-laputa-v2.md @@ -1,38 +1,19 @@ --- -aliases: ["Laputa App V2"] -Is A: Project -Belongs to: "[[25q2]]" -Advances: "[[responsibility-learning]]" -Status: Done -Owner: "[[person-luca-rossi]]" +type: Project +aliases: + - "[[Laputa App V2]]" +belongs_to: "[[25q2]]" +owner: "[[person-luca-rossi]]" +status: Active +related_to: + - "[[laputa-qa-reference]]" --- + # Laputa App V2 -## Overview +The active polish project used for current QA, especially richer editing, keyboard navigation, and attachment rendering. -V2 of Laputa was a major iteration that addressed the rough edges from [[25q1-laputa-v1]] and introduced three headline features: a BlockNote-based rich text editor replacing the raw CodeMirror setup, wiki-link autocomplete for seamless navigation between notes, and a completely redesigned theme system with CSS custom properties. These changes transformed the app from a functional prototype into something that feels genuinely pleasant to use daily. +- Tightened the editor interaction model. +- Reduced friction in wikilink navigation. +- Uses [[laputa-qa-reference]] as a lightweight visual reference note. -The BlockNote integration was the most significant architectural change — it provides a block-based editing experience similar to Notion while preserving the underlying markdown format. Wiki-link autocomplete (triggered by typing `[[`) searches across all vault files and inserts links with proper display names. The theme system uses design tokens defined as CSS custom properties, making it straightforward to adjust the visual style without touching component code. This milestone continues the path toward [[2025-ship-laputa]]. - -## Goals - -- Replace the basic CodeMirror editor with BlockNote for a block-based editing experience -- Implement wiki-link autocomplete with fuzzy search across all vault files -- Redesign the theme system using CSS custom properties and a centralized token file -- Improve the property inspector with inline editing for all frontmatter field types -- Fix the top 10 UX issues reported during V1 daily use - -## Key decisions - -- **BlockNote over plain CodeMirror.** While CodeMirror 6 is excellent for code editing, the reveal-on-focus model proved too jarring for prose-heavy content. BlockNote provides a smoother editing experience where formatting is always visible and blocks can be manipulated as units. The trade-off is less control over the raw markdown, but for the primary use case (structured notes with frontmatter), this is acceptable. -- **CSS custom properties, not a CSS-in-JS theme.** Evaluated styled-components and Tailwind CSS theme approaches but chose plain CSS custom properties. They are natively supported, have zero runtime cost, can be inspected in browser DevTools, and align with the project philosophy of preferring simple, standard approaches over framework-dependent abstractions. -- **Wiki-link search index prebuilt at startup.** The autocomplete needs to search across all ~9,200 files in sub-50ms. Rather than querying the filesystem on each keystroke, the Rust backend builds a search index at startup (including file names, aliases, and titles) and the frontend queries this index. Incremental updates happen when files change. - -## Notes - -- The BlockNote integration took longer than expected — about 3 weeks of focused work. The main challenge was ensuring that markdown round-tripping (markdown to BlockNote blocks to markdown) preserved formatting perfectly. Several edge cases with nested lists and code blocks required custom serializers. -- Wiki-link autocomplete was the most impactful feature from a daily use perspective. Being able to type `[[` and instantly find any note in the vault by name, alias, or title makes the linking experience far superior to Obsidian's implementation (which does not search aliases by default). -- [[person-david-kim]] continued to provide UX feedback, particularly around keyboard navigation patterns. His suggestion to add Vim-style `j/k` navigation in the note list was implemented and feels natural for power users. -- The theme redesign consolidated about 200 scattered color values into 45 semantic design tokens. This made it trivial to create a dark mode variant (completed in a single afternoon) and establishes a foundation for future theme customization. -- Performance remained solid despite the architectural changes. Note switching is still sub-200ms, and the BlockNote editor handles files up to 5,000 lines without noticeable lag. Memory usage increased by about 15% compared to V1 due to BlockNote's richer DOM, which is acceptable. -- The V2 release was the point where Laputa became genuinely preferable to Obsidian for daily vault management. Feeds into [[25q4-laputa-v3]] for the next major milestone. diff --git a/demo-vault-v2/25q2-podcast-season-3.md b/demo-vault-v2/25q2-podcast-season-3.md deleted file mode 100644 index f66005e9..00000000 --- a/demo-vault-v2/25q2-podcast-season-3.md +++ /dev/null @@ -1,38 +0,0 @@ ---- -aliases: ["Podcast Season 3"] -Is A: Project -Belongs to: "[[25q2]]" -Advances: "[[responsibility-podcast]]" -Status: Done -Owner: "[[person-luca-rossi]]" ---- -# Podcast Season 3 - -## Overview - -Season 3 expanded the Refactoring podcast to 10 episodes with a thematic focus on building in public, founder journeys, and product-led growth. After two seasons focused on engineering leadership and org design, this season shifted toward the entrepreneurial side of the audience — developers who are building products, running side projects, or considering the leap to full-time founder. The theme resonated strongly, producing the highest average downloads per episode of any season so far. - -Production was now a well-oiled operation: [[person-sara-ricci]] handled post-production, [[person-paco-furiani]] managed guest scheduling and logistics, and [[person-luca-rossi]] focused purely on guest selection, interview preparation, and hosting. The workflows from [[procedure-podcast-recording]] and [[procedure-podcast-editing]] continued to function with only minor updates. - -## Goals - -- Record and publish 10 episodes on building in public, founder journeys, and product-led growth -- Secure at least 3 guests who are active indie hackers or solopreneurs with public revenue data -- Grow average episode downloads to 3,000 (up from Season 2's ~2,100) -- Introduce YouTube video for 3 select episodes as an experiment -- Generate at least 5 newsletter issues from podcast conversations (repurposed content) - -## Key decisions - -- **10 episodes, up from 8.** The seasonal model allows for flexibility in episode count. 10 episodes fit cleanly into the Q2 window (April-June) with a weekly release schedule. The extra two episodes justified by the stronger guest pipeline and revenue from podcast sponsorships. -- **Selective video for 3 episodes.** Rather than doing video for all episodes (too much production overhead) or none (missed YouTube opportunity), selected 3 episodes with the most visually engaging guests for video. This tests the YouTube channel without committing to full video production. -- **Founder-focused theme, not pure engineering.** The shift toward entrepreneurial topics was a deliberate audience expansion move. Refactoring's readership increasingly includes developers who are also founders or aspire to be. This theme serves them while maintaining technical credibility through the "building" angle. - -## Notes - -- Average downloads per episode reached 3,400, significantly exceeding the 3,000 target. The standout episode was a conversation with an indie hacker who publicly shared their journey from $0 to $25K MRR, which was shared widely on Twitter/X and LinkedIn. -- The 3 video episodes performed well on YouTube (~4,000-6,000 views each), which is a promising signal for a channel with no prior content. The production cost was manageable because Riverside.fm captures both audio and video in the same recording session. -- [[person-david-kim]] appeared as a guest for an episode on developer tool startups. His insights on distribution in the developer tools market were among the most practical advice shared on the show. -- Content repurposing worked exceptionally well this season. 6 newsletter issues drew directly from podcast conversations (exceeding the 5-issue target), and the cross-promotion between newsletter and podcast continued to be the primary growth engine for [[measure-podcast-downloads]]. -- Podcast sponsorship revenue reached $2,500/month during the season, representing meaningful incremental revenue on top of newsletter sponsorships. The combined sponsorship revenue contributes significantly to [[2025-reach-22k-mrr]]. -- Season 3 was the first season where the podcast felt like it was pulling its own weight as a growth channel, not just a newsletter supplement. This has implications for resource allocation in [[25q3-podcast-season-4]]. diff --git a/demo-vault-v2/25q2-reach-70k.md b/demo-vault-v2/25q2-reach-70k.md deleted file mode 100644 index 16363a80..00000000 --- a/demo-vault-v2/25q2-reach-70k.md +++ /dev/null @@ -1,38 +0,0 @@ ---- -aliases: ["Reach 70k Subscribers"] -Is A: Project -Belongs to: "[[25q2]]" -Advances: "[[responsibility-grow-newsletter]]" -Status: Done -Owner: "[[person-luca-rossi]]" ---- -# Reach 70k Subscribers - -## Overview - -This project was a focused growth sprint to push [[measure-subscribers]] from approximately 60K to 70K during [[25q2]]. The strategy combined two approaches: amplifying the referral program launched in [[25q1-referral-program]] with targeted campaigns, and establishing cross-promotion partnerships with 3 complementary newsletters in adjacent spaces (startup operations, product management, and design leadership). - -The 70K milestone was significant both psychologically (a round number that signals scale) and commercially (larger audience commands higher sponsorship rates and opens doors to enterprise-tier sponsors). The sprint ran from April through June and involved weekly tracking against a linear growth trajectory to catch underperformance early. - -## Goals - -- Grow from ~60K to 70K subscribers by end of June 2025 -- Drive 4,000+ subscribers through the referral program (with targeted campaigns and incentive boosts) -- Establish 3 newsletter cross-promotion partnerships with reciprocal recommendation swaps -- Maintain subscriber quality: 30-day retention rate above 75% for new subscribers -- Achieve the milestone while keeping cost-per-acquisition below $1.00 - -## Key decisions - -- **Cross-promotion over paid acquisition.** Considered investing in paid newsletter ads (Sparkloop's partner network, Twitter ads), but the economics favored cross-promotion. A reciprocal recommendation swap with a complementary newsletter costs nothing and generates high-quality subscribers who are already newsletter readers. Paid acquisition was kept as a backup if organic channels underperformed. -- **Three partners, carefully selected.** Rather than doing many low-quality cross-promotions, invested time in selecting three newsletters where the audience overlap is genuine but not complete. The partners were a startup operations newsletter (~40K subscribers), a product management newsletter (~55K subscribers), and a design leadership newsletter (~30K subscribers). Each introduces Refactoring to a slightly different but adjacent audience. -- **Weekly tracking cadence.** Set up a weekly check against a linear growth trajectory (~2,500 new subscribers/month needed). This allowed early detection of underperformance and mid-course corrections. In week 3, growth was tracking below target, which led to an additional referral incentive push that course-corrected by week 5. - -## Notes - -- Final subscriber count at end of June: 71,200 — slightly above the 70K target. The growth distribution was approximately: cross-promotions (3,800), referral program (3,500), organic search (2,200), social media (800), other (900). -- Cross-promotion partnerships were the highest-quality growth channel. Subscribers from cross-promotions had a 30-day retention rate of 82%, the highest of any acquisition channel. This makes sense — they were already engaged newsletter readers, just not yet aware of Refactoring. -- The referral program saw a significant boost from a "Spring Referral Challenge" campaign run in May, where the rewards were temporarily enhanced (extra rewards at the 5-referral tier). This generated a spike of ~1,200 new subscribers in a single week. -- [[person-elena-rossi]] helped design the cross-promotion creative (email copy and graphics) for the partner newsletters. Her marketing background was valuable for crafting the recommendation copy that appeared in partner newsletters. -- Cost-per-acquisition across all channels was $0.62, well below the $1.00 target. The primary costs were SparkLoop subscription, referral rewards, and the time spent on partnership management. -- The 70K milestone was used in the updated media kit and referenced in sponsorship conversations, directly supporting the rate increases and new sponsor acquisition feeding into [[2025-reach-22k-mrr]]. diff --git a/demo-vault-v2/25q2-team-retreat.md b/demo-vault-v2/25q2-team-retreat.md deleted file mode 100644 index 588a10f3..00000000 --- a/demo-vault-v2/25q2-team-retreat.md +++ /dev/null @@ -1,37 +0,0 @@ ---- -aliases: ["Team Retreat Milan"] -Is A: Project -Belongs to: "[[25q2]]" -Advances: "[[responsibility-team-management]]" -Status: Done -Owner: "[[person-luca-rossi]]" ---- -# Team Retreat Milan - -## Overview - -After more than a year of working together remotely, the Refactoring team gathered for its first in-person retreat in Milan. The retreat brought together [[person-luca-rossi]], [[person-matteo-cellini]], [[person-paco-furiani]], and [[person-sara-ricci]] for two days of strategy sessions, workshops, and team bonding. The purpose was to align on the business direction for the second half of 2025, address operational friction points, and build the personal relationships that make remote collaboration smoother. - -The retreat was planned for early May, timed to fall between Season 3 podcast production and the summer growth push. The agenda was deliberately balanced between structured work sessions (morning) and unstructured social time (afternoon/evening). Milan was chosen for its central location relative to all team members. - -## Goals - -- Conduct a half-day business strategy session covering H2 2025 priorities and goals -- Run a workflow retrospective: identify and resolve the top 3 operational friction points -- Host a creative workshop on content format experimentation for H2 -- Provide space for unstructured team bonding (dinner, activities) -- Document decisions and action items for follow-up within 1 week - -## Key decisions - -- **Two days, not three.** Considered a 3-day retreat but decided that two full days (plus a team dinner the evening before) provided enough time for meaningful work without pulling everyone away from their schedules for too long. Especially for a small team where everyone wears multiple hats, minimizing away-from-work time matters. -- **Strategy session first, social second.** Ran the strategy and retrospective sessions on the first day (when energy and focus are highest) and the creative workshop + social activities on the second day. This ensured the most important decisions got the best thinking. -- **External facilitator for the retrospective.** Rather than running the retrospective internally, brought in [[person-giulia-conti]] (who has experience facilitating team sessions) to moderate. Having an external voice made it easier for team members to surface honest feedback without the founder-employee dynamic filtering the conversation. - -## Notes - -- The retrospective produced the most actionable outcomes. The top 3 friction points identified were: (1) newsletter draft handoff timing (Sara needs more lead time), (2) sponsor pipeline visibility (Matteo wants to see content calendar earlier for pitch alignment), and (3) podcast scheduling conflicts (Paco needs more advance notice for guest confirmations). All three had clear action items assigned. -- The strategy session confirmed H2 priorities: community launch ([[25q3-community-launch]]), continued Laputa development ([[25q4-laputa-v3]]), and the push toward [[2025-reach-85k-subscribers]]. There was a genuine debate about whether to invest in a premium podcast (higher production value, video-first) versus the community. Decided on community as the higher-leverage bet. -- The creative workshop generated several content format ideas for H2, including a "Refactoring Case Studies" series (deep dives into real company engineering decisions) and a "Founder Metrics" segment sharing real revenue/growth numbers. Both were added to the content roadmap. -- Team dinner was at a classic Milanese trattoria near the Navigli. The informal conversation over dinner revealed a lot about individual motivations and career aspirations that would never surface in a video call. [[person-matteo-cellini]] mentioned wanting to eventually run his own content business, which was valuable context for thinking about his long-term role. -- Total cost: approximately 2,800 EUR (hotel, meals, workspace rental, facilitator). Very reasonable for the alignment value produced. Planning to make this a biannual event (spring and autumn). diff --git a/demo-vault-v2/25q2.md b/demo-vault-v2/25q2.md index e5710bf2..08a42cce 100644 --- a/demo-vault-v2/25q2.md +++ b/demo-vault-v2/25q2.md @@ -1,32 +1,13 @@ --- -aliases: ["Q2 2025"] -Is A: Quarter -Created at: "2025-04-01" -Belongs to: "[[2025]]" -Has: ["[[25q2-reach-70k]]", "[[25q2-podcast-season-3]]", "[[25q2-team-retreat]]", "[[25q2-laputa-v2]]", "[[25q2-dolomites-trip]]"] -Status: Done +type: Quarter +aliases: + - "[[Q2 2025]]" +status: Active +has: + - "[[25q2-laputa-v2]]" --- + # Q2 2025 -## Focus +The polish cycle focused on richer editing, faster linking, and better keyboard QA. -Q2 was the heart of the execution phase for 2025. The 70k subscriber milestone was the key growth target. Season 3 of the podcast brought a new format — shorter episodes, more actionable. The team retreat in Tuscany was about alignment and bonding. And the Dolomites cycling trip was both training for Stelvio and pure joy. - -## Highlights - -- Hit [[25q2-reach-70k]] subscribers in early June — two weeks ahead of schedule, driven by viral LinkedIn posts and the referral program compounding -- Launched [[25q2-podcast-season-3]] with a new 15-minute "Tactical Tuesday" format alongside the regular deep dives — downloads surged to 14k/month -- Held [[25q2-team-retreat]] in a farmhouse outside Siena with [[person-matteo-cellini]], [[person-paco-furiani]], and [[person-sara-ricci]] — aligned on H2 roadmap, built real trust -- Shipped [[25q2-laputa-v2]] with bidirectional linking, graph view, and improved frontmatter editing — starting to feel like a real product -- Completed [[25q2-dolomites-trip]]: 4 days, 5 passes, 380 km — Passo Fedaia, Pordoi, Sella, Gardena, Campolongo -- [[measure-sponsorship-mrr]] hit EUR 17.5k — tracking well toward [[2025-reach-22k-mrr]] -- Premium tier reached 680 paying subscribers, up from 420 at start of quarter -- Two pillar articles syndicated by major tech publications, driving ~4k new subscribers - -## Reflections - -The team retreat was the highlight of the quarter, and maybe the most important thing we did all year. Working remotely with contractors is efficient, but you miss the informal conversations that build real relationships. Three days in Tuscany — cooking together, long walks, whiteboard sessions on the terrace — transformed how we collaborate. [[person-sara-ricci]] pitched the community idea over dinner on the second night, and it was so obvious in hindsight that we all wondered why we hadn't done it sooner. That became [[25q3-community-launch]]. - -Reaching 70k subscribers felt almost routine, which is itself remarkable. A year ago, every thousand felt hard-won. Now the flywheel is spinning: content drives subscribers, subscribers attract sponsors, sponsors fund better content. The referral program is the turbocharger — word-of-mouth from engineering leaders who trust their peers' recommendations. - -The Dolomites trip was pure magic. Four days of riding through the most beautiful mountain landscape in Europe with three friends. Passo Fedaia at sunset, the Marmolada glacier glowing overhead — these are the moments that make the 5am training rides worth it. My legs are ready for [[2025-ride-stelvio]] in August. Bring it on. diff --git a/demo-vault-v2/25q3-community-launch.md b/demo-vault-v2/25q3-community-launch.md deleted file mode 100644 index 2fcd731e..00000000 --- a/demo-vault-v2/25q3-community-launch.md +++ /dev/null @@ -1,38 +0,0 @@ ---- -aliases: ["Launch Refactoring Community"] -Is A: Project -Belongs to: "[[25q3]]" -Advances: "[[responsibility-grow-newsletter]]" -Status: Open -Owner: "[[person-luca-rossi]]" ---- -# Launch Refactoring Community - -## Overview - -This project is building a private Discord community for Refactoring's most engaged readers — a space where engineering leaders, indie hackers, and technical founders can connect, share challenges, and learn from each other beyond the one-way format of the newsletter and podcast. The community concept was validated during the [[25q2-team-retreat]] strategy session and represents the most significant new product surface since the podcast launch. - -The approach is a soft launch with a small, curated initial cohort rather than opening the doors to all subscribers at once. The [[25q3-discord-community-soft]] experiment is testing engagement patterns, channel structure, and moderation needs with approximately 150 founding members before a broader rollout. The community is free for now, with potential for a paid tier once the value proposition is validated. This is a fundamentally different approach from the failed [[24q3-premium-tier]] — the focus is on community value, not content gating. - -## Goals - -- Set up the Discord server with initial channel structure (introductions, weekly discussions, resource sharing, career advice, project showcases) -- Recruit 150 founding members from the most engaged newsletter subscribers (based on open rate, click-through, and referral data) -- Establish community guidelines, moderation policies, and a code of conduct -- Host 2 live events during the soft launch period (AMA sessions with podcast guests) -- Achieve a weekly active member rate of at least 40% during the soft launch - -## Key decisions - -- **Discord, not Circle or Slack.** Evaluated all three platforms. Discord offers the best combination of real-time and async communication, has robust moderation tools, and most of the target audience already has accounts. Circle has a cleaner UX but lacks real-time chat. Slack is too work-associated — people do not want another Slack workspace. -- **Soft launch with curated cohort, not open launch.** The lesson from [[24q3-premium-tier]] was that launching to everyone at once creates a spike-and-fade pattern. A soft launch with hand-selected engaged members builds genuine activity and social proof before scaling. The founding members become community champions. -- **Free entry, no paywall yet.** The community needs to prove its value before asking members to pay. Charging too early kills participation momentum. Will evaluate a paid tier once weekly active member rate stabilizes above 40% and there is clear demand for premium features (private channels, exclusive events). - -## Notes - -- The soft launch began in late July with 150 invitations sent to subscribers identified through engagement scoring. Acceptance rate was 72% (108 active members), which is strong for a community invitation. -- Early engagement is promising but uneven. The "weekly discussion" channel (a prompted discussion thread posted every Monday) generates the most activity. Organic conversation in open channels is still sparse — this is the typical early-community challenge. -- The two AMA sessions (with guests from [[25q2-podcast-season-3]]) were well-attended (~60 members each) and generated follow-up discussions that lasted several days. Live events appear to be the strongest engagement driver. -- [[person-paco-furiani]] is handling day-to-day community moderation. His operational experience and even temperament make him well-suited for this role. The time commitment is currently about 3 hours/week. -- The biggest risk is that the community becomes another content channel (one-to-many) rather than a genuine peer space (many-to-many). Actively encouraging member-initiated discussions and resisting the urge to "fill the silence" with content is important. -- This project feeds into the broader question of whether the community becomes a revenue stream or remains a free engagement tool. Will evaluate after the soft launch period ends in [[25q4]]. diff --git a/demo-vault-v2/25q3-discord-community-soft.md b/demo-vault-v2/25q3-discord-community-soft.md deleted file mode 100644 index 7f271a03..00000000 --- a/demo-vault-v2/25q3-discord-community-soft.md +++ /dev/null @@ -1,38 +0,0 @@ ---- -aliases: ["Discord Community Soft Launch"] -Is A: Experiment -Belongs to: "[[25q3]]" -Status: Open -Owner: "[[person-luca-rossi]]" ---- -# Discord Community Soft Launch - -Soft-launched a Discord community for the Refactoring newsletter with an initial cohort of 50 beta subscribers. The goal is to validate whether a private community can drive meaningful engagement, reduce churn, and eventually become a monetizable product tied to [[25q3-community-launch]]. This experiment directly informs whether community is the right next revenue line beyond sponsorships. - -## Hypothesis - -A curated Discord community with 50 hand-picked beta members will achieve at least 40% weekly active participation (defined as posting or reacting at least once per week) over the first 8 weeks, and at least 70% of members will express willingness to pay $20/month for continued access. - -## Setup - -- Invited 50 beta members from the most engaged newsletter subscribers (high open rate, frequent replies, active on social). -- Created a minimal channel structure: #introductions, #general, #content-ideas, #career-advice, #weekly-thread. -- [[person-luca-rossi]] posts a weekly discussion prompt every Monday tied to that week's newsletter topic. -- [[person-paco-furiani]] moderates and tracks engagement metrics. -- Running a survey at week 4 and week 8 to gauge willingness to pay and feature requests. - -## Results - -- Currently in progress. Early signals after 3 weeks: - - Weekly active participation: ~52% (above the 40% target so far). - - Most active channels: #career-advice and #general. #content-ideas is quieter than expected. - - Three members have organically started peer accountability threads (unplanned, positive signal). - - No dropoffs yet, though engagement tends to decay after the novelty period. - -## Takeaways - -- Early results are encouraging but it is too soon to draw conclusions. The real test is whether engagement sustains past week 6. -- The #career-advice channel suggests the community's core value may be peer networking rather than content discussion. Worth leaning into. -- If the willingness-to-pay survey at week 8 confirms demand, this becomes the foundation for [[25q3-community-launch]] and a potential path to the [[2025-reach-22k-mrr]] goal. -- Lessons from the [[25q1-paid-newsletter-trial]] apply here: the value proposition must be access and connection, not more content. -- Key risk: community management overhead. Need to assess whether [[person-paco-furiani]] can handle moderation long-term or if additional support is needed from [[responsibility-team-management]]. diff --git a/demo-vault-v2/25q3-ebook.md b/demo-vault-v2/25q3-ebook.md deleted file mode 100644 index 2731563d..00000000 --- a/demo-vault-v2/25q3-ebook.md +++ /dev/null @@ -1,38 +0,0 @@ ---- -aliases: ["Write Newsletter Growth E-book"] -Is A: Project -Belongs to: "[[25q3]]" -Advances: "[[responsibility-content-production]]" -Status: Done -Owner: "[[person-luca-rossi]]" ---- -# Write Newsletter Growth E-book - -## Overview - -This project produced a 15,000-word e-book titled "The Newsletter Growth Playbook for Technical Founders" — a comprehensive guide distilling the Refactoring growth story, strategies, and lessons into a free downloadable resource. The e-book serves as a high-value lead magnet for subscriber acquisition and establishes authority in the growing "technical content creator" space. - -The e-book drew heavily from existing content — the Codemotion talk from [[24q3-codemotion-talk]], pillar articles from [[24q2-10-pillar-articles]], and newsletter issues that covered growth topics throughout 2024. Rather than writing everything from scratch, the project assembled, updated, and expanded existing material into a cohesive narrative. [[person-sara-ricci]] edited the full manuscript over two rounds, and [[person-giulia-conti]] designed the cover and interior layout. - -## Goals - -- Write a 15,000-word e-book covering newsletter strategy, growth tactics, and monetization for technical audiences -- Structure in 8 chapters with actionable takeaways and real data from the Refactoring journey -- Design a professional PDF layout with custom cover art and clean typography -- Set up a landing page with email capture for the download (new subscribers get the e-book as a welcome gift) -- Generate 3,000+ new subscribers through the e-book in the first 3 months - -## Key decisions - -- **Free, not paid.** The primary goal is subscriber acquisition, not direct revenue. A free e-book with an email gate generates far more subscribers than a $9.99 paid e-book would generate in revenue. The subscriber lifetime value (through sponsorship revenue) far exceeds any reasonable e-book price. -- **Existing content as foundation, not writing from scratch.** About 60% of the e-book content was adapted from existing newsletter issues, blog posts, and the Codemotion talk transcript. This reduced the writing time from an estimated 6 weeks to about 3 weeks while producing a more proven and polished result (the content had already been validated with the audience). -- **PDF format, not a Substack post or blog series.** A designed PDF feels more substantial and "worth downloading" than a blog series. It also creates a sense of exclusivity and ownership that a public web page does not. The design investment was modest but made the resource feel premium. - -## Notes - -- The writing process was faster than expected. The structure emerged naturally from grouping existing content into themes: chapters on audience identification, content strategy, distribution, SEO, sponsorship, and community. New writing focused mainly on connecting threads and adding updated data. -- [[person-sara-ricci]]'s editing was particularly valuable for the e-book format. Newsletter writing can be casual and conversational; a longer-form document requires more careful structure and flow. She restructured two chapters significantly and improved the opening section. -- [[person-giulia-conti]]'s cover design was clean and professional — a minimalist style with the Refactoring brand colors. The interior layout used a two-column format with pull quotes and data callouts that made the dense content more scannable. -- The landing page conversion rate is approximately 42% (visitors who enter email and download). This is above the benchmark for e-book lead magnets (~25-30%). The high conversion likely reflects the specificity of the topic and the trust already built through the newsletter brand. -- At the 2-month mark, the e-book has generated approximately 2,300 new subscribers, tracking toward the 3,000 target. The e-book landing page is now promoted in the newsletter footer, on the podcast, and through social media. It has also been shared organically by readers, creating a compounding distribution effect. -- The e-book content will likely need updating in 6-12 months as strategies evolve. Built the manuscript in markdown with a separate build script for PDF generation, making updates straightforward. Feeds into [[topic-content-strategy]]. diff --git a/demo-vault-v2/25q3-leaddev-london.md b/demo-vault-v2/25q3-leaddev-london.md deleted file mode 100644 index 302f9baf..00000000 --- a/demo-vault-v2/25q3-leaddev-london.md +++ /dev/null @@ -1,38 +0,0 @@ ---- -aliases: ["LeadDev London 2025"] -Is A: Project -Belongs to: "[[25q3]]" -Advances: "[[responsibility-content-production]]" -Status: Done -Owner: "[[person-luca-rossi]]" ---- -# LeadDev London 2025 - -## Overview - -LeadDev London is one of the premier conferences for engineering leaders, and attending in 2025 served three purposes: participating in a panel on "Building Engineering Content Brands," meeting potential podcast guests and sponsors in person, and writing a post-conference analysis piece for the newsletter. The trip combined brand-building, relationship development, and content creation into a single, high-leverage event. - -The conference took place in early September in London. Beyond the panel, the most valuable aspect was the hallway conversations — meeting people who have been reading the newsletter for years, connecting with potential sponsors face-to-face, and identifying guests for [[25q3-podcast-season-4]]. The post-conference newsletter issue became one of the highest-engagement pieces of the quarter. - -## Goals - -- Participate in the "Building Engineering Content Brands" panel discussion -- Schedule at least 5 in-person meetings with current/potential sponsors during the conference -- Identify and pitch 3+ potential guests for the upcoming podcast season -- Write a post-conference analysis newsletter issue highlighting key themes and takeaways -- Strengthen relationships with 10+ newsletter readers and community members attending the event - -## Key decisions - -- **Panel participation over keynote pitch.** Was offered the option to propose a keynote talk, but chose the panel format instead. A panel requires less preparation time, provides exposure to the other panelists' audiences, and positions Refactoring alongside other established content brands. The trade-off is less individual spotlight, but the networking value of sharing a stage with peers outweighs that. -- **Three days, not just conference days.** Arrived one day before the conference for scheduled sponsor meetings and stayed one day after for follow-up conversations. The extra days doubled the relationship ROI of the trip. -- **Post-conference piece as synthesis, not summary.** Rather than writing a play-by-play of conference talks (which dozens of attendees will do), wrote a synthesized analysis of the three biggest themes emerging across all talks. This is more valuable to readers and stands out in the content noise after any major conference. - -## Notes - -- The panel discussion went well. The other panelists represented a startup-focused newsletter (~80K subscribers), a podcast network, and a YouTube channel for developers. The conversation surfaced interesting differences in monetization strategies and audience engagement patterns. Several audience members approached afterward to discuss Refactoring's sponsorship model. -- In-person sponsor meetings were extremely productive. Met with 6 sponsors (5 existing, 1 prospective), and the face-to-face time strengthened relationships in a way that video calls cannot. The prospective sponsor signed a 3-month Deep Dive package within a week of the conference. [[person-matteo-cellini]] prepared one-pagers for each meeting, which was a professional touch. -- Identified 4 potential podcast guests, 3 of whom have since confirmed for [[25q3-podcast-season-4]]. In-person conversation is vastly more effective for podcast guest recruitment than cold email. -- The post-conference newsletter issue ("Three Things I Learned at LeadDev London 2025") had the highest open rate of any issue in Q3 (48%) and generated significant discussion in the [[25q3-community-launch]] Discord. Conference analysis content consistently outperforms regular issues. -- [[person-emma-wilson]] also attended and facilitated an introduction to several VPEs from UK-based scale-ups. These connections are valuable for both podcast guests and understanding the European engineering leadership landscape. -- Total trip cost: approximately 1,800 GBP (flights, hotel, meals, conference ticket). The ROI through the new sponsor alone covered the trip cost several times over. diff --git a/demo-vault-v2/25q3-peak-training.md b/demo-vault-v2/25q3-peak-training.md deleted file mode 100644 index b8ebcfa3..00000000 --- a/demo-vault-v2/25q3-peak-training.md +++ /dev/null @@ -1,38 +0,0 @@ ---- -aliases: ["Summer Cycling Peak Training"] -Is A: Project -Belongs to: "[[25q3]]" -Advances: "[[responsibility-health-fitness]]" -Status: Done -Owner: "[[person-luca-rossi]]" ---- -# Summer Cycling Peak Training - -## Overview - -This was the final intensive training block of the 2025 cycling season, preparing for a September gran fondo event. After the successful Dolomites trip in [[25q2-dolomites-trip]], this peak training block focused on sharpening form and building the high-end fitness needed for a competitive autumn event. The block ran from mid-July through late August, with the target event in the second week of September. - -The training philosophy shifted from the high-volume base approach used earlier in the year to a high-intensity, lower-volume peak phase. Interval sessions became more specific (longer threshold efforts, race-simulation rides), while total weekly hours decreased to allow for recovery and adaptation. The strength training from [[25q1-strength-program]] continued in maintenance mode (2 sessions/week) to preserve the gains without adding fatigue. - -## Goals - -- Execute a 6-week peak training block with high-intensity focus -- Hit a new season-best monthly volume in August (target: 1,400+ km) -- Complete 3 race-simulation rides on courses with similar profile to the target event -- Maintain FTP at or above 280W through the peak phase -- Arrive at the target event rested and sharp (2-week taper before the event) - -## Key decisions - -- **Intensity over volume for the peak phase.** After building a strong aerobic base through the first half of the year (~6,000 km by end of June), the peak phase prioritized quality over quantity. Three key sessions per week: a VO2max interval session, a threshold ride, and a long endurance ride with race-pace segments. Total weekly hours dropped from 10-12 to 8-9. -- **Two-week taper, not one.** Considered a shorter taper to maintain sharpness, but the Dolomites trip had left some residual fatigue. A two-week taper with gradually decreasing volume allowed full recovery while maintaining neuromuscular activation through short, sharp efforts. -- **No new equipment or position changes.** Resisted the temptation to try new tires or adjust bike fit close to the event. Everything that worked in the Dolomites stays unchanged for the autumn event. Equipment experiments belong in the off-season. - -## Notes - -- August volume reached 1,420 km, hitting the target. The weekly structure of one high-intensity day, one threshold day, one long day, and recovery between worked well. The long rides (5-6 hours) on weekends were the most important sessions for event-specific preparation. -- FTP tested at 282W in late August, a slight improvement from the 275W measured earlier in the year. The strength training may be contributing to this — improved core stability allows for more efficient power transfer, especially at higher intensities. -- [[person-paco-furiani]] followed a similar peak block and they completed two of the three race-simulation rides together. Training with a partner on hard sessions added motivation and pacing discipline. -- The main challenge during the peak block was managing fatigue alongside work commitments. August is a lighter newsletter period (similar reasoning as [[24q3-summer-reading-sprint]]), but podcast recording for [[25q3-podcast-season-4]] overlapped with the peak training weeks. Scheduling required careful coordination. -- The 2-week taper felt luxurious but paid off. Arrived at the event feeling genuinely fresh — legs snappy, weight on target (71.5kg), and mentally eager. This is the best pre-race state achieved across all events so far. -- [[measure-cycling-km-per-month]] for the full peak period (July-August): approximately 2,700 km combined. This brings the year-to-date total to approximately 9,500 km, on track for a year-end total exceeding 2024's 8,200 km. diff --git a/demo-vault-v2/25q3-podcast-season-4.md b/demo-vault-v2/25q3-podcast-season-4.md deleted file mode 100644 index 01c9444d..00000000 --- a/demo-vault-v2/25q3-podcast-season-4.md +++ /dev/null @@ -1,38 +0,0 @@ ---- -aliases: ["Podcast Season 4"] -Is A: Project -Belongs to: "[[25q3]]" -Advances: "[[responsibility-podcast]]" -Status: Open -Owner: "[[person-luca-rossi]]" ---- -# Podcast Season 4 - -## Overview - -Season 4 tackles the most urgent topic in the engineering world right now: how AI is changing software engineering. With 8 planned episodes, the season explores the practical impact of AI on engineering teams — from coding assistants and AI-augmented code review to the shifting role of senior engineers and the organizational implications of dramatically increased developer productivity. The theme was selected during the [[25q2-team-retreat]] strategy session and reflects the audience's most-requested topic in community polls. - -Production is following the established workflows from [[procedure-podcast-recording]] and [[procedure-podcast-editing]], with [[person-sara-ricci]] on post-production and [[person-paco-furiani]] on guest logistics. Three guests were recruited during [[25q3-leaddev-london]], and the remaining slots are being filled through network outreach. The season is currently in production with recording underway. - -## Goals - -- Record and publish 8 episodes on AI and its impact on software engineering -- Secure guests who are actively building or deploying AI tools in engineering orgs (not just commentators) -- Continue video production for select episodes (target: 4 out of 8 with video, up from 3 in Season 3) -- Grow average episode downloads to 4,000 (up from Season 3's ~3,400) -- Generate sponsor revenue of at least $3,000/month from podcast placements - -## Key decisions - -- **Practitioners over pundits.** The AI space is full of hot takes and hype. This season deliberately focuses on guests who are hands-on — CTOs implementing AI coding tools, engineers who have integrated AI into their workflows, and founders building AI developer tools. The practical angle differentiates from the noise. -- **Expanded video to 4 episodes.** Season 3's video experiment showed promising YouTube numbers. Expanding to 4 video episodes (every other episode) increases YouTube content cadence without committing to full video production for every episode. The video episodes are selected based on guest visual engagement and topic appeal. -- **AI tools as sponsors.** The season theme creates a natural alignment with AI tool sponsors. Actively targeting AI coding assistants and developer productivity tools for the podcast sponsorship slots. The topical alignment between content and sponsor should improve click-through rates. - -## Notes - -- Guest recruitment has been the strongest of any season. The AI topic is so timely that response rates on outreach are approximately 45% — nearly double Season 3. The challenge is now selecting the best guests rather than finding enough willing guests. -- The first two recorded episodes are highly engaging. The opening episode, an interview with a CTO who replaced their entire QA team with AI-augmented testing, generated strong early reactions from the team during review. This kind of provocative-but-substantive content is what the season needs. -- [[person-david-kim]] is returning as a guest for an episode on building AI developer tools — his perspective as both a builder and user of these tools bridges the practitioner-founder divide nicely. -- Sponsor interest for the AI-themed season is strong. Two AI tool companies have committed to the full season (all 8 episodes), which secures the $3,000/month target. The thematic alignment between content and sponsor has made the pitch very natural. -- The biggest production challenge is that AI topics evolve extremely fast. Episodes recorded in August may feel slightly dated by the time they air in October. Mitigating this by focusing conversations on principles and organizational dynamics rather than specific tool features. -- This season, combined with the community discussions in [[25q3-community-launch]], is positioning Refactoring as a thought leader on AI's impact on engineering teams — a valuable positioning for both audience growth and sponsor value. diff --git a/demo-vault-v2/25q3.md b/demo-vault-v2/25q3.md deleted file mode 100644 index 807d0255..00000000 --- a/demo-vault-v2/25q3.md +++ /dev/null @@ -1,34 +0,0 @@ ---- -aliases: ["Q3 2025"] -Is A: Quarter -Created at: "2025-07-01" -Belongs to: "[[2025]]" -Has: ["[[25q3-ebook]]", "[[25q3-community-launch]]", "[[25q3-podcast-season-4]]", "[[25q3-leaddev-london]]", "[[25q3-peak-training]]"] -Status: Done ---- -# Q3 2025 - -## Focus - -Q3 was the most ambitious quarter yet. Three big launches — the ebook, the community, and podcast Season 4 — plus a keynote at LeadDev London and peak training for Stelvio. This was the quarter where I felt the tension between "scale everything" and "don't burn out." It worked, but just barely. - -## Highlights - -- Published [[25q3-ebook]] "The Engineering Leader's Playbook" — 12 chapters distilled from the best newsletter content, sold 1,400 copies in the first month at EUR 29 -- Launched [[25q3-community-launch]] on Circle with 850 founding members from the premium tier — weekly AMAs, peer groups, async Q&A -- [[25q3-podcast-season-4]] opened with a special 3-part series on "Building Engineering Culture from Scratch" — 22k downloads in the first week -- Delivered keynote at [[25q3-leaddev-london]] on "The Newsletter-to-Business Pipeline" to ~1,200 attendees — biggest stage yet -- Completed [[25q3-peak-training]] block: 14 weeks of structured intervals, altitude simulation, and long weekend rides — FTP peaked at 285W -- Newsletter hit 78k subscribers by end of September -- [[measure-sponsorship-mrr]] reached EUR 20.1k — [[2025-reach-22k-mrr]] is close -- Rode Stelvio from Bormio side in 1h52m — [[2025-ride-stelvio]] achieved - -## Reflections - -I'm not going to pretend this quarter was smooth. It was intense to the point of being unsustainable. Three major launches in 13 weeks, plus a keynote, plus peak cycling training — something had to give, and it was sleep. I averaged under 6 hours for most of August. [[person-paco-furiani]] flagged it during a 1:1, and he was right. I need to build more buffer into ambitious quarters. - -That said, the outcomes were extraordinary. The ebook exceeded every expectation. I'd been skeptical about packaging newsletter content into a book — would people pay for what they'd already read for free? Turns out, curation and structure have enormous value. The people buying the ebook aren't the same people who read every issue; they want the distilled playbook, and they're happy to pay for it. - -LeadDev London was a career highlight. Standing on that stage, looking out at 1,200 engineering leaders — many of whom I recognized from the newsletter subscriber list — was surreal. The talk went well, but the conversations afterward were even better. Three potential enterprise sponsors, two podcast guest leads, and a half-dozen people who said Refactoring changed how they lead their teams. - -And then Stelvio. Climbing the most iconic pass in cycling, legs screaming, lungs burning, the summit appearing and disappearing behind switchbacks — it was everything I'd imagined. 1h52m from Bormio. Not fast by any serious cyclist's standard, but I didn't care. I made it. [[2025-ride-stelvio]] done. Now I need to rest — body and mind — before tackling Q4. diff --git a/demo-vault-v2/25q4-2026-sponsors.md b/demo-vault-v2/25q4-2026-sponsors.md deleted file mode 100644 index 95eae2bb..00000000 --- a/demo-vault-v2/25q4-2026-sponsors.md +++ /dev/null @@ -1,37 +0,0 @@ ---- -aliases: ["2026 Sponsorship Pipeline"] -Is A: Project -Belongs to: "[[25q4]]" -Advances: "[[responsibility-sponsorships]]" -Status: Open -Owner: "[[person-luca-rossi]]" ---- -# 2026 Sponsorship Pipeline - -## Overview - -This project focuses on pre-selling Q1-Q2 2026 sponsorship slots before December 31, 2025, targeting 80% of available inventory sold in advance. Pre-selling provides revenue predictability, reduces the need for reactive outreach early in the new year, and allows sponsors to lock in current rates before any potential 2026 rate adjustments. It also demonstrates business maturity to sponsors, who appreciate the ability to plan their marketing budgets in advance. - -The pipeline effort builds on the CRM infrastructure from [[24q2-sponsor-crm]], the dashboard from [[24q4-sponsor-dashboard]], and the expanded verticals from [[24q3-new-sponsor-verticals]]. [[person-matteo-cellini]] is leading outreach with a focus on renewals first (highest conversion probability), followed by upsells (sponsors moving to higher tiers), and finally new prospect acquisition. The [[procedure-quarterly-sponsor-outreach]] workflow drives the execution. - -## Goals - -- Pre-sell 80% of Q1-Q2 2026 sponsorship inventory (newsletter + podcast) by December 31 -- Secure renewals from at least 85% of existing H2 2025 sponsors -- Upsell at least 3 sponsors to higher tiers (e.g., Spotlight to Deep Dive) -- Acquire 5+ new sponsors from outreach (targeting AI/ML and cloud infrastructure verticals) -- Set pricing for 2026: evaluate a 15-20% rate increase based on audience growth and performance data - -## Key decisions - -- **Renewals first, then new business.** The renewal pipeline is the most efficient revenue source — existing sponsors already understand the value, and the CRM tracks their performance data. Starting renewal conversations in October gives sponsors 2+ months to approve budgets. New prospect outreach begins in November once the renewal pipeline is established. -- **Bundle pricing for annual commitments.** Offering a 10% discount for sponsors who commit to 6+ months upfront. This trades a small rate discount for significant revenue predictability and reduced sales overhead (one contract instead of monthly renewals). -- **2026 rate increase evaluation.** The audience growth from [[25q2-reach-70k]] and the push toward [[2025-reach-85k-subscribers]] justifies another rate adjustment. Planning a 15-20% increase for 2026, applied to new bookings and renewals after March 2026. Existing annual commitments honored at current rates. - -## Notes - -- Early renewal conversations (started in October) are going well. Three sponsors have already verbally committed to H1 2026 renewals. The performance dashboard from [[24q4-sponsor-dashboard]] is proving invaluable — sponsors can see their own data and self-justify the renewal internally. -- [[person-matteo-cellini]] is running the outreach systematically through the CRM, with weekly pipeline reviews. His expanded role (agreed during [[24q4-annual-review-process]]) is paying off — he is now handling the full sales cycle from prospecting to contract, not just initial outreach. -- The AI/ML vertical continues to be the fastest-growing sponsor category. Several AI tool companies that sponsored [[25q3-podcast-season-4]] are expressing interest in annual newsletter packages. The thematic alignment between content and sponsors creates natural demand. -- Pipeline tracking against the 80% target happens weekly. Current projection (as of mid-November) suggests the target is achievable, though some deals may slip into early January. The key risk is budget freeze season — many companies pause new commitments in late December. -- This project directly feeds into [[2025-reach-22k-mrr]] and sets the revenue foundation for 2026 planning. The combination of rate increases, new sponsor acquisition, and high renewal rates should push [[measure-sponsorship-mrr]] to new highs. diff --git a/demo-vault-v2/25q4-financial-review.md b/demo-vault-v2/25q4-financial-review.md deleted file mode 100644 index fc128a35..00000000 --- a/demo-vault-v2/25q4-financial-review.md +++ /dev/null @@ -1,38 +0,0 @@ ---- -aliases: ["2025 Financial Review"] -Is A: Project -Belongs to: "[[25q4]]" -Advances: "[[responsibility-personal-finance]]" -Status: Open -Owner: "[[person-luca-rossi]]" ---- -# 2025 Financial Review - -## Overview - -This project conducts the annual financial review — assessing the investment portfolio established in [[24q1-set-investing-framework]], evaluating business profitability, reviewing spending patterns, and setting financial targets for 2026. The review covers both personal finances (investment portfolio, savings rate, emergency fund) and business finances (revenue, expenses, margins, and tax optimization). - -The 2025 review is particularly significant because it is the second year of the investing framework, providing enough data to evaluate whether the strategy is working as intended. The business has also grown substantially, meaning cash management, tax planning, and reinvestment decisions are more complex than in the early days. The review is scheduled for December 2025, with outputs informing both personal financial planning and business budgeting for 2026. - -## Goals - -- Review investment portfolio performance against benchmark (MSCI ACWI) and rebalance if allocation has drifted more than 5% from target -- Calculate the full-year savings rate and compare against the 20% target -- Analyze business revenue and expenses: total revenue, margins, and year-over-year growth -- Assess tax efficiency and identify optimization opportunities for 2026 -- Set 2026 financial targets: savings rate, investment contributions, and business revenue goals - -## Key decisions - -- **Annual review, not quarterly.** While the investing framework includes quarterly check-ins for allocation drift, the full financial review (business + personal + tax) happens annually. Quarterly is too frequent for strategic financial planning and creates unnecessary anxiety about short-term market movements. -- **Business and personal finances reviewed together.** As a solo business owner, the line between business and personal finances is thin. Reviewing them together reveals the full picture — business revenue minus expenses minus taxes equals the pool available for personal savings and investment. Separating the reviews would hide the dependencies. -- **Tax optimization as a first-class concern.** Italian tax law for individual businesses is complex, and proactive planning can significantly reduce the effective tax rate through legitimate deductions and timing strategies. Working with an accountant to identify opportunities before year-end rather than discovering them retroactively. - -## Notes - -- The investment portfolio has been on autopilot since [[24q1-set-investing-framework]], with automated monthly contributions of 20% of net revenue. Preliminary review shows the portfolio is performing in line with the benchmark, which is exactly the goal of passive investing — matching the market, not beating it. -- The savings rate for 2025 is tracking at approximately 22%, slightly above the 20% target. This reflects increased revenue (sponsorship growth) without proportionally increased spending. The business has natural operating leverage — more subscribers and sponsors does not linearly increase costs. -- [[person-marco-bianchi]] is reviewing the tax optimization section, as he went through a similar analysis for his own business last year. His recommendation to prepay certain expenses in December for tax timing purposes is being evaluated. -- Business revenue has grown significantly year-over-year, driven by the rate increase from [[25q1-rate-increase]], new sponsor verticals, and podcast sponsorship revenue. The detailed revenue analysis will feed into [[25q4-2026-sponsors]] for setting 2026 pricing. -- The emergency fund (6 months of expenses in a high-yield savings account) remains fully funded. No need to adjust — the original sizing from the 2024 framework still covers the current expense base with comfortable margin. -- One area for improvement: better tracking of business expenses by category. Currently using a basic spreadsheet. Considering a proper accounting tool for 2026, especially as the team grows and expense categories become more varied. diff --git a/demo-vault-v2/25q4-laputa-v3.md b/demo-vault-v2/25q4-laputa-v3.md deleted file mode 100644 index 8e16f300..00000000 --- a/demo-vault-v2/25q4-laputa-v3.md +++ /dev/null @@ -1,38 +0,0 @@ ---- -aliases: ["Laputa App V3"] -Is A: Project -Belongs to: "[[25q4]]" -Advances: "[[responsibility-learning]]" -Status: Open -Owner: "[[person-luca-rossi]]" ---- -# Laputa App V3 - -## Overview - -V3 represents the most ambitious Laputa milestone yet, introducing three headline features that take the app from a desktop-only vault browser to a truly integrated knowledge management system: mobile sync (read/write access to the vault from an iPhone), AI-powered note linking (automatic suggestions for connections between notes), and a quick capture menu bar widget for frictionless note creation without opening the full app. - -The mobile sync challenge is primarily architectural — the vault is a local directory of markdown files, and syncing across devices requires either a cloud sync layer (iCloud, Dropbox) or a custom sync protocol. The AI linking feature uses embeddings to find semantically related notes that may not share explicit wiki-links. Quick capture provides a lightweight input surface that integrates with macOS system-wide, accessible via a keyboard shortcut. This milestone continues the path toward [[2025-ship-laputa]]. - -## Goals - -- Implement mobile sync via iCloud Drive for read/write vault access on iOS -- Build an AI note linking system that suggests related notes based on semantic similarity -- Create a menu bar quick capture widget (macOS) for instant note creation via keyboard shortcut -- Optimize app performance for vaults exceeding 10,000 files (anticipating vault growth) -- Ship a beta release to a small group of testers (5-10 people) for external feedback - -## Key decisions - -- **iCloud Drive for sync, not custom backend.** Evaluated building a custom sync server, using Dropbox API, or leveraging iCloud Drive. iCloud was chosen because it is native to the Apple ecosystem (where most potential users are), requires zero server infrastructure, and handles conflict resolution at the file level. The downside is platform lock-in (no Android sync), but the user base is overwhelmingly macOS/iOS. -- **Embedding-based similarity, not keyword matching.** The AI linking system uses text embeddings (via a local model, not cloud API) to compute semantic similarity between notes. This catches connections that keyword matching would miss — for example, a note about "team retrospectives" being related to a note about "learning from failure" even though they share no common terms. Running locally preserves privacy and eliminates API costs. -- **Menu bar widget as a Tauri secondary window.** Rather than a separate app, the quick capture widget is a secondary Tauri window that can be toggled via a global keyboard shortcut. This keeps the implementation within the existing codebase and shares the Rust backend for file operations. - -## Notes - -- The iCloud Drive integration is the most technically uncertain component. Tauri's file system access works well for local directories, but iCloud Drive introduces sync conflicts, delayed availability, and platform-specific behaviors that need careful handling. Early prototyping is focused on identifying and handling edge cases before building the full sync UI. -- The AI linking prototype is showing promising results. Using a local embedding model (all-MiniLM-L6-v2), the system generates similarity scores between all vault notes. For a 9,200-file vault, the full embedding computation takes about 45 seconds — acceptable as a one-time startup cost with incremental updates for changed files. -- [[person-david-kim]] has agreed to be one of the beta testers. His experience with developer tools and his own extensive note-taking practice make him an ideal early user. Planning to recruit 4-5 additional testers from the [[25q3-community-launch]] Discord. -- The quick capture widget addresses a genuine daily friction point. Currently, capturing a quick thought requires opening the full Laputa app, navigating to the right location, and creating a new note. The menu bar widget reduces this to: hit keyboard shortcut, type, hit enter. The captured note gets filed with a timestamp and can be processed later. -- Performance optimization work has begun with profiling the app under load with 10K+ files. The main bottleneck is the initial file scan and frontmatter parsing — exploring a caching layer that persists parsed metadata between sessions to avoid re-parsing unchanged files. -- V3 is planned for completion by end of [[25q4]], which would fulfill [[2025-ship-laputa]] with a feature-complete app that handles the full vault management workflow across devices. diff --git a/demo-vault-v2/25q4-reach-85k.md b/demo-vault-v2/25q4-reach-85k.md deleted file mode 100644 index 96aea133..00000000 --- a/demo-vault-v2/25q4-reach-85k.md +++ /dev/null @@ -1,38 +0,0 @@ ---- -aliases: ["Reach 85k Subscribers"] -Is A: Project -Belongs to: "[[25q4]]" -Advances: "[[responsibility-grow-newsletter]]" -Status: Open -Owner: "[[person-luca-rossi]]" ---- -# Reach 85k Subscribers - -## Overview - -This project is the year-end push to hit [[2025-reach-85k-subscribers]], the headline growth goal for the year. With [[measure-subscribers]] at approximately 75K after the [[25q2-reach-70k]] sprint and continued organic growth through Q3, reaching 85K by December 31 requires an additional ~10K subscribers in the final quarter. The strategy combines expansion of existing growth channels (referral program, cross-promotions, SEO) with a repeat of the Black Friday campaign that was so successful in [[24q4-black-friday-campaign]]. - -The growth plan is structured in two phases: a steady October-November push through referral amplification and new cross-promotion partnerships, followed by a concentrated Black Friday campaign in late November that aims to replicate the 1,200+ subscriber spike from 2024. [[person-elena-rossi]] is supporting the campaign creative, and [[person-matteo-cellini]] is coordinating the sponsor participation in the Black Friday special. - -## Goals - -- Grow from ~75K to 85K subscribers by December 31, 2025 -- Generate 3,000+ subscribers through referral program campaigns (including a holiday referral challenge) -- Establish 2 new cross-promotion partnerships (in addition to the 3 from [[25q2-reach-70k]]) -- Execute a Black Friday 2025 campaign targeting 1,500+ new subscribers (improvement over 2024's 1,200) -- Maintain subscriber quality: 30-day retention rate above 75% for all acquisition channels - -## Key decisions - -- **Referral program as the primary engine.** The referral program from [[25q1-referral-program]] has proven to be the most cost-effective and highest-quality growth channel. Rather than investing in new, unproven channels, the strategy doubles down on referrals with increased incentives, a holiday-themed challenge, and more prominent placement in the newsletter. -- **Black Friday 2025 with expanded scope.** The 2024 campaign focused on developer tools. The 2025 version expands to include AI tools, learning resources, and SaaS products relevant to engineering leaders. The broader scope should increase the lead magnet's appeal while maintaining curation quality. -- **No paid acquisition at scale.** Tested paid newsletter ads (via SparkLoop partner network) during Q3 with a small budget. The cost-per-acquisition was $2.50, which is acceptable but significantly higher than organic channels ($0.60-0.80). Keeping paid as a supplementary channel rather than a primary one. - -## Notes - -- The early October referral push generated approximately 800 new subscribers in two weeks, which is slightly above the run-rate needed to hit target. The "Holiday Referral Challenge" is scheduled for late November, offering enhanced rewards for the holiday season. -- New cross-promotion partnerships are being negotiated with a DevOps-focused newsletter (~45K subscribers) and a tech career newsletter (~60K subscribers). These are adjacent but distinct audiences, minimizing overlap with existing partners. -- The e-book from [[25q3-ebook]] continues to drive steady subscriber growth (~300-400/month) and is being promoted more aggressively as part of the Q4 push. It is now the primary CTA on the Refactoring website homepage. -- [[person-elena-rossi]] is designing the Black Friday 2025 campaign creative, building on the successful format from 2024. The plan includes a dedicated landing page, social media assets, and email sequences for the week-long campaign. -- The [[25q3-community-launch]] Discord is becoming an organic growth channel — community members share the newsletter with their networks. Quantifying this effect is difficult, but anecdotal evidence suggests it is meaningful. -- Current projection (mid-November): on track to reach approximately 83K-86K by year-end, which means the 85K target is achievable but not guaranteed. The Black Friday campaign is the swing factor — a strong campaign pushes past 85K, a weak one leaves the target short. diff --git a/demo-vault-v2/25q4-year-review-2025.md b/demo-vault-v2/25q4-year-review-2025.md deleted file mode 100644 index 9dd9dd59..00000000 --- a/demo-vault-v2/25q4-year-review-2025.md +++ /dev/null @@ -1,38 +0,0 @@ ---- -aliases: ["2025 Annual Review"] -Is A: Project -Belongs to: "[[25q4]]" -Advances: "[[responsibility-team-management]]" -Status: Open -Owner: "[[person-luca-rossi]]" ---- -# 2025 Annual Review - -## Overview - -This is the full 2025 retrospective — a comprehensive review covering both the team (structured reviews for each team member) and a personal year-in-review across all areas of responsibility. The process builds on the framework established in [[24q4-annual-review-process]], which proved effective and is now in its second iteration. The review covers business performance, content output, team development, personal health and fitness, and financial outcomes. - -The review is scheduled for December 2025 and will be conducted in two phases: individual team member reviews (week 1-2 of December), followed by the personal retrospective and 2026 planning (week 3-4 of December). The outputs will inform Q1 2026 planning, team role adjustments, compensation reviews, and personal goal-setting for the new year. - -## Goals - -- Conduct structured annual reviews with [[person-matteo-cellini]], [[person-paco-furiani]], and [[person-sara-ricci]] -- Evaluate each team member against 2025 goals set during the 2024 review -- Conduct a personal retrospective across all responsibilities: content, sponsorships, podcast, fitness, finance, and Laputa development -- Set 2026 goals for the business, team, and personal areas -- Identify 3-5 strategic priorities for 2026 based on 2025 learnings - -## Key decisions - -- **Same review format as 2024, with one addition.** The conversation-first, self-assessment-supported format from [[24q4-annual-review-process]] worked well and will be reused. The addition for 2025: a peer feedback component where team members provide brief feedback on each other (not just on [[person-luca-rossi]]). This gives a more complete picture as the team grows. -- **Personal retrospective tied to vault data.** Using data from the vault (goals achieved, projects completed, measures tracked) as the foundation for the personal retrospective rather than relying on memory. This is one of the use cases where Laputa ([[25q4-laputa-v3]]) and the structured vault pay off — the data is all there, organized by quarter and responsibility. -- **2026 planning as part of the review, not a separate process.** Rather than separating the retrospective from forward planning, combining them ensures that 2026 goals are directly informed by 2025 learnings. The risk of separating them is that planning happens in a vacuum, disconnected from recent experience. - -## Notes - -- The team has grown from 3 part-time contractors in 2024 to 4 people with expanded roles. [[person-matteo-cellini]]'s role expansion (from outreach to full sales cycle, as discussed in the 2024 review) has been successful. His 2025 review should formalize this expanded scope. -- [[person-sara-ricci]]'s feedback from the 2024 review about draft lead time was acted upon and has improved the editorial workflow. Will assess whether the 48-hour minimum lead time for [[procedure-weekly-newsletter]] is sufficient or if further adjustment is needed. -- [[person-paco-furiani]]'s new community moderation responsibilities (from [[25q3-community-launch]]) were not part of his original scope. The review should address whether this is a permanent addition, requires compensation adjustment, and how it fits with his other operational duties. -- The personal retrospective will draw on goal outcomes ([[2025-reach-85k-subscribers]], [[2025-reach-22k-mrr]], [[2025-ship-laputa]], [[2025-ride-stelvio]], [[2025-read-20-books]]) as quantitative inputs, supplemented by qualitative reflection on what felt sustainable, what caused stress, and where energy was best spent. -- Key question for 2026 planning: is the current business model (newsletter + podcast + sponsorships) approaching its ceiling, or is there still significant headroom? The community experiment ([[25q3-community-launch]]) and the e-book ([[25q3-ebook]]) suggest there are adjacent revenue and engagement opportunities worth exploring. -- Scheduling note: the review takes approximately 8-10 hours total (preparation, 4 conversations, personal retrospective, documentation). Blocking this time in December is essential — the review gets squeezed out if it has to compete with end-of-year operational demands. diff --git a/demo-vault-v2/25q4.md b/demo-vault-v2/25q4.md deleted file mode 100644 index 05c3d238..00000000 --- a/demo-vault-v2/25q4.md +++ /dev/null @@ -1,31 +0,0 @@ ---- -aliases: ["Q4 2025"] -Is A: Quarter -Created at: "2025-10-01" -Belongs to: "[[2025]]" -Has: ["[[25q4-year-review-2025]]", "[[25q4-reach-85k]]", "[[25q4-2026-sponsors]]", "[[25q4-laputa-v3]]", "[[25q4-financial-review]]"] -Status: Open ---- -# Q4 2025 - -## Focus - -Q4 is about closing the year and setting up 2026. The push to 85k subscribers is the final growth sprint. Sponsor renewals and 2026 pipeline need to be locked in before the holidays. Laputa v3 aims to make the app ready for early beta testers beyond just me. And the financial review will determine if we can hire a full-time team member in 2026. - -## Highlights - -- [[25q4-reach-85k]] is on track — sitting at 82k as of mid-November, with a Black Friday campaign planned to close the gap -- [[25q4-2026-sponsors]] pipeline building: [[person-matteo-cellini]] has 8 sponsors in negotiation for Q1-Q2 2026, projected MRR of EUR 24k+ -- [[25q4-laputa-v3]] in active development — AI-powered chat panel, type creation, and improved graph navigation shipped; preparing for closed beta -- [[25q4-financial-review]] underway — 2025 on track to close at ~EUR 260k total revenue, up from EUR 155k in 2024 -- [[25q4-year-review-2025]] template designed, retrospective sessions scheduled for December -- Community engagement stabilizing at ~65% weekly active rate — better than industry benchmarks -- [[measure-podcast-downloads]] averaging 18k/month — up 125% year-over-year - -## Reflections - -There's a different energy to Q4 this year compared to last. In 2024, Q4 felt like a victory lap after a good year. This year, it feels heavier — not because things are going badly, but because the complexity has increased. More revenue means more sponsors to manage. More subscribers means more expectations. A community means more conversations to facilitate. A product means more code to ship. - -I'm learning that scaling isn't just "more of the same, but bigger." It's a qualitative shift in what the work looks like. [[person-paco-furiani]] and I have been talking about what a full-time hire would look like — someone who can own community management and free me up to focus on content and Laputa. The [[25q4-financial-review]] will tell us if we can afford it. - -The Laputa work has been the most creatively fulfilling part of this quarter. V3 is starting to feel like software other people could actually use. The AI chat panel was a stretch goal that landed well — asking questions about your own vault and getting contextual answers is genuinely useful. If I can get 10-20 beta testers by January, [[2025-ship-laputa]] will feel real. Looking ahead to [[2025]] closing out and [[2025]]: cautiously optimistic, mildly exhausted, deeply grateful. diff --git a/demo-vault-v2/_themes/dark.json b/demo-vault-v2/_themes/dark.json deleted file mode 100644 index 6d902ae2..00000000 --- a/demo-vault-v2/_themes/dark.json +++ /dev/null @@ -1,33 +0,0 @@ -{ - "name": "Dark", - "description": "Dark variant with deep navy tones", - "colors": { - "background": "#0f0f1a", - "foreground": "#e0e0e0", - "card": "#16162a", - "popover": "#1e1e3a", - "primary": "#155DFF", - "primary-foreground": "#FFFFFF", - "secondary": "#2a2a4a", - "secondary-foreground": "#e0e0e0", - "muted": "#1e1e3a", - "muted-foreground": "#888888", - "accent": "#2a2a4a", - "accent-foreground": "#e0e0e0", - "destructive": "#f44336", - "border": "#2a2a4a", - "input": "#2a2a4a", - "ring": "#155DFF", - "sidebar-background": "#1a1a2e", - "sidebar-foreground": "#e0e0e0", - "sidebar-border": "#2a2a4a", - "sidebar-accent": "#2a2a4a" - }, - "typography": { - "font-family": "'Inter', -apple-system, BlinkMacSystemFont, sans-serif", - "font-size-base": "14px" - }, - "spacing": { - "sidebar-width": "250px" - } -} \ No newline at end of file diff --git a/demo-vault-v2/_themes/default.json b/demo-vault-v2/_themes/default.json deleted file mode 100644 index 77ca9349..00000000 --- a/demo-vault-v2/_themes/default.json +++ /dev/null @@ -1,33 +0,0 @@ -{ - "name": "Default", - "description": "Light theme with warm, paper-like tones", - "colors": { - "background": "#FFFFFF", - "foreground": "#37352F", - "card": "#FFFFFF", - "popover": "#FFFFFF", - "primary": "#155DFF", - "primary-foreground": "#FFFFFF", - "secondary": "#EBEBEA", - "secondary-foreground": "#37352F", - "muted": "#F0F0EF", - "muted-foreground": "#787774", - "accent": "#EBEBEA", - "accent-foreground": "#37352F", - "destructive": "#E03E3E", - "border": "#E9E9E7", - "input": "#E9E9E7", - "ring": "#155DFF", - "sidebar-background": "#F7F6F3", - "sidebar-foreground": "#37352F", - "sidebar-border": "#E9E9E7", - "sidebar-accent": "#EBEBEA" - }, - "typography": { - "font-family": "'Inter', -apple-system, BlinkMacSystemFont, sans-serif", - "font-size-base": "14px" - }, - "spacing": { - "sidebar-width": "250px" - } -} \ No newline at end of file diff --git a/demo-vault-v2/_themes/minimal.json b/demo-vault-v2/_themes/minimal.json deleted file mode 100644 index e0fd9960..00000000 --- a/demo-vault-v2/_themes/minimal.json +++ /dev/null @@ -1,33 +0,0 @@ -{ - "name": "Minimal", - "description": "High contrast, minimal chrome", - "colors": { - "background": "#FAFAFA", - "foreground": "#111111", - "card": "#FFFFFF", - "popover": "#FFFFFF", - "primary": "#000000", - "primary-foreground": "#FFFFFF", - "secondary": "#F0F0F0", - "secondary-foreground": "#111111", - "muted": "#F5F5F5", - "muted-foreground": "#666666", - "accent": "#F0F0F0", - "accent-foreground": "#111111", - "destructive": "#CC0000", - "border": "#E0E0E0", - "input": "#E0E0E0", - "ring": "#000000", - "sidebar-background": "#F5F5F5", - "sidebar-foreground": "#111111", - "sidebar-border": "#E0E0E0", - "sidebar-accent": "#E8E8E8" - }, - "typography": { - "font-family": "'SF Mono', 'Menlo', monospace", - "font-size-base": "13px" - }, - "spacing": { - "sidebar-width": "220px" - } -} \ No newline at end of file diff --git a/demo-vault-v2/_themes/untitled-2.json b/demo-vault-v2/_themes/untitled-2.json deleted file mode 100644 index d52e497e..00000000 --- a/demo-vault-v2/_themes/untitled-2.json +++ /dev/null @@ -1,33 +0,0 @@ -{ - "colors": { - "accent": "#EBEBEA", - "accent-foreground": "#37352F", - "background": "#FFFFFF", - "border": "#E9E9E7", - "card": "#FFFFFF", - "destructive": "#E03E3E", - "foreground": "#37352F", - "input": "#E9E9E7", - "muted": "#F0F0EF", - "muted-foreground": "#787774", - "popover": "#FFFFFF", - "primary": "#155DFF", - "primary-foreground": "#FFFFFF", - "ring": "#155DFF", - "secondary": "#EBEBEA", - "secondary-foreground": "#37352F", - "sidebar-accent": "#EBEBEA", - "sidebar-background": "#F7F6F3", - "sidebar-border": "#E9E9E7", - "sidebar-foreground": "#37352F" - }, - "description": "Light theme with warm, paper-like tones", - "name": "Untitled Theme", - "spacing": { - "sidebar-width": "250px" - }, - "typography": { - "font-family": "'Inter', -apple-system, BlinkMacSystemFont, sans-serif", - "font-size-base": "14px" - } -} \ No newline at end of file diff --git a/demo-vault-v2/_themes/untitled-3.json b/demo-vault-v2/_themes/untitled-3.json deleted file mode 100644 index d52e497e..00000000 --- a/demo-vault-v2/_themes/untitled-3.json +++ /dev/null @@ -1,33 +0,0 @@ -{ - "colors": { - "accent": "#EBEBEA", - "accent-foreground": "#37352F", - "background": "#FFFFFF", - "border": "#E9E9E7", - "card": "#FFFFFF", - "destructive": "#E03E3E", - "foreground": "#37352F", - "input": "#E9E9E7", - "muted": "#F0F0EF", - "muted-foreground": "#787774", - "popover": "#FFFFFF", - "primary": "#155DFF", - "primary-foreground": "#FFFFFF", - "ring": "#155DFF", - "secondary": "#EBEBEA", - "secondary-foreground": "#37352F", - "sidebar-accent": "#EBEBEA", - "sidebar-background": "#F7F6F3", - "sidebar-border": "#E9E9E7", - "sidebar-foreground": "#37352F" - }, - "description": "Light theme with warm, paper-like tones", - "name": "Untitled Theme", - "spacing": { - "sidebar-width": "250px" - }, - "typography": { - "font-family": "'Inter', -apple-system, BlinkMacSystemFont, sans-serif", - "font-size-base": "14px" - } -} \ No newline at end of file diff --git a/demo-vault-v2/_themes/untitled-4.json b/demo-vault-v2/_themes/untitled-4.json deleted file mode 100644 index d52e497e..00000000 --- a/demo-vault-v2/_themes/untitled-4.json +++ /dev/null @@ -1,33 +0,0 @@ -{ - "colors": { - "accent": "#EBEBEA", - "accent-foreground": "#37352F", - "background": "#FFFFFF", - "border": "#E9E9E7", - "card": "#FFFFFF", - "destructive": "#E03E3E", - "foreground": "#37352F", - "input": "#E9E9E7", - "muted": "#F0F0EF", - "muted-foreground": "#787774", - "popover": "#FFFFFF", - "primary": "#155DFF", - "primary-foreground": "#FFFFFF", - "ring": "#155DFF", - "secondary": "#EBEBEA", - "secondary-foreground": "#37352F", - "sidebar-accent": "#EBEBEA", - "sidebar-background": "#F7F6F3", - "sidebar-border": "#E9E9E7", - "sidebar-foreground": "#37352F" - }, - "description": "Light theme with warm, paper-like tones", - "name": "Untitled Theme", - "spacing": { - "sidebar-width": "250px" - }, - "typography": { - "font-family": "'Inter', -apple-system, BlinkMacSystemFont, sans-serif", - "font-size-base": "14px" - } -} \ No newline at end of file diff --git a/demo-vault-v2/_themes/untitled.json b/demo-vault-v2/_themes/untitled.json deleted file mode 100644 index d52e497e..00000000 --- a/demo-vault-v2/_themes/untitled.json +++ /dev/null @@ -1,33 +0,0 @@ -{ - "colors": { - "accent": "#EBEBEA", - "accent-foreground": "#37352F", - "background": "#FFFFFF", - "border": "#E9E9E7", - "card": "#FFFFFF", - "destructive": "#E03E3E", - "foreground": "#37352F", - "input": "#E9E9E7", - "muted": "#F0F0EF", - "muted-foreground": "#787774", - "popover": "#FFFFFF", - "primary": "#155DFF", - "primary-foreground": "#FFFFFF", - "ring": "#155DFF", - "secondary": "#EBEBEA", - "secondary-foreground": "#37352F", - "sidebar-accent": "#EBEBEA", - "sidebar-background": "#F7F6F3", - "sidebar-border": "#E9E9E7", - "sidebar-foreground": "#37352F" - }, - "description": "Light theme with warm, paper-like tones", - "name": "Untitled Theme", - "spacing": { - "sidebar-width": "250px" - }, - "typography": { - "font-family": "'Inter', -apple-system, BlinkMacSystemFont, sans-serif", - "font-size-base": "14px" - } -} \ No newline at end of file diff --git a/demo-vault-v2/ai-wont-replace-thinking.md b/demo-vault-v2/ai-wont-replace-thinking.md deleted file mode 100644 index 05d8402c..00000000 --- a/demo-vault-v2/ai-wont-replace-thinking.md +++ /dev/null @@ -1,26 +0,0 @@ ---- -aliases: ["AI Won't Replace Thinking — It Will Raise the Bar"] -Is A: Evergreen -Topics: ["[[topic-ai-ml]]", "[[topic-writing]]"] -Status: Published ---- -# AI Won't Replace Thinking — It Will Raise the Bar -The first generation of AI writing tools made it possible to produce content without thinking. The next generation is making it impossible to compete without thinking — deeply. - -When everyone can generate serviceable prose in seconds, the competitive advantage shifts to the things AI can't replicate: genuine expertise, authentic perspective, earned trust, and original insight. Surface-level content becomes worthless. Depth becomes more valuable. - -For writers with real knowledge and real opinions, this is good news. For those who were providing formatting around thin ideas, the reckoning is here. - -The newsletter space is where this plays out most visibly. I have watched dozens of newsletters launch in the engineering leadership niche since GPT-3 became widely available. The ones that use AI to generate "7 tips for better code reviews" articles are already indistinguishable from each other and losing subscribers. The ones that use AI to accelerate their own thinking — to draft faster, to find patterns in their notes, to explore counterarguments — are producing better work than ever. The tool amplifies what is already there. If what is already there is nothing, you get polished nothing. - -This maps directly to the experience of running Refactoring. Readers can sense when a piece comes from lived experience versus when it is assembled from other people's ideas. The engagement signals are completely different. A piece where I describe exactly how a reorganization went wrong at a specific company, with the emotional texture of being in the room, generates ten times the replies of a well-structured but generic piece about org design principles. AI can help me write the first draft faster, but it cannot manufacture the experience. - -## Key insight -The bar for content is being raised, not lowered. AI commoditizes the act of writing while increasing the premium on the act of thinking. This means that the most valuable investment a knowledge worker can make is not learning prompt engineering — it is deepening their domain expertise and developing stronger, more specific opinions. The writers who will thrive are the ones who use AI as a thinking partner while maintaining the intellectual rigor to reject its confident-sounding mediocrity. Being willing to disagree with your own AI-generated draft is the new editorial skill. - -## Related -- [[the-compound-effect-in-knowledge-work]] — Consistent deep thinking compounds over time in ways that AI-generated content cannot replicate -- [[writing-for-clarity-vs-writing-for-credit]] — AI makes it easier to write for credit; the challenge remains writing for genuine clarity -- [[on-consistency-in-creative-work]] — Consistency in creative output remains a human discipline even when AI accelerates production -- [[topic-ai-ml]] — Broader observations on AI and machine learning -- [[topic-writing]] — Writing craft and practice diff --git a/demo-vault-v2/area-building.md b/demo-vault-v2/area-building.md index f27c6a1c..1be6e50f 100644 --- a/demo-vault-v2/area-building.md +++ b/demo-vault-v2/area-building.md @@ -1,29 +1,12 @@ --- -aliases: ["Building"] -Is A: Area -Has: ["[[responsibility-grow-newsletter]]", "[[responsibility-sponsorships]]", "[[responsibility-content-production]]", "[[responsibility-podcast]]", "[[responsibility-team-management]]"] +type: Area +aliases: + - "[[Building]]" +has: + - "[[responsibility-sponsorships]]" --- + # Building -The core area encompassing everything related to building and growing Refactoring as a business. This includes the newsletter, podcast, sponsorship revenue, team operations, and content strategy. +The business-facing area used in QA to anchor a responsibility with linked procedures and metrics. -## Scope - -Building covers the full lifecycle of running a media business as an indie founder: - -- **Content production** — writing weekly essays, publishing the newsletter, maintaining editorial quality -- **Audience growth** — subscriber acquisition, retention, referral programs, SEO -- **Revenue** — sponsorship packages, pricing strategy, sponsor relationships, renewals -- **Podcast** — guest outreach, recording, editing, distribution, analytics -- **Team** — managing [[person-matteo-cellini]] and [[person-paco-furiani]], weekly syncs, 1:1s - -## Why this area matters - -Refactoring is the primary vehicle for professional impact and income. Everything in this area ladders up to the long-term vision of building a sustainable, high-quality engineering media company that serves tens of thousands of senior developers and engineering leaders. - -## Key principles - -- Ship consistently — a weekly newsletter is a promise to the audience -- Quality over quantity — one great essay beats three mediocre ones -- Revenue follows trust — sponsorships work because the audience trusts the content -- Build systems, not heroics — processes like [[procedure-weekly-newsletter]] and [[procedure-content-calendar-review]] keep things running even on low-energy weeks diff --git a/demo-vault-v2/area-finance.md b/demo-vault-v2/area-finance.md deleted file mode 100644 index 6bebf0bc..00000000 --- a/demo-vault-v2/area-finance.md +++ /dev/null @@ -1,29 +0,0 @@ ---- -aliases: ["Finance"] -Is A: Area -Has: ["[[responsibility-personal-finance]]"] ---- -# Finance - -Personal and business finances. Covers investing, savings, tax planning, and the financial health of Refactoring as a business. - -## Scope - -- **Personal investing** — index fund portfolio, occasional individual stock research, long-term wealth building -- **Savings** — maintaining a healthy savings rate, emergency fund, annual targets -- **Business finances** — Refactoring revenue tracking, expense management, quarterly financial reviews -- **Tax planning** — Italian tax obligations, VAT management, accountant coordination - -## Philosophy - -The approach to finance is intentionally simple: automate what can be automated, invest passively for the long term, and focus energy on growing business revenue rather than optimizing portfolio returns. See [[index-funds-and-intellectual-humility]] for the underlying thinking. - -## Key measures - -- [[measure-net-worth]] — tracked quarterly -- [[measure-savings-rate]] — target 30%+ of net income -- [[measure-sponsorship-mrr]] — the primary revenue metric - -## Cadence - -Monthly portfolio check via [[procedure-monthly-portfolio-review]]. Quarterly deep dive via [[procedure-quarterly-financial-planning]]. diff --git a/demo-vault-v2/area-health.md b/demo-vault-v2/area-health.md deleted file mode 100644 index c6ed89c6..00000000 --- a/demo-vault-v2/area-health.md +++ /dev/null @@ -1,29 +0,0 @@ ---- -aliases: ["Health"] -Is A: Area -Has: ["[[responsibility-health-fitness]]"] ---- -# Health - -Physical and mental health. Encompasses cycling training, gym work, nutrition, sleep, and recovery. - -## Scope - -- **Cycling** — the primary sport, including structured training blocks, gran fondos, and the long-term goal of riding the Stelvio -- **Strength training** — gym sessions focused on functional strength and injury prevention -- **Nutrition** — fueling for performance and general health, cooking as a creative outlet -- **Sleep & recovery** — tracking resting heart rate, prioritizing sleep duration, managing training load -- **Mental health** — recognizing burnout patterns, maintaining boundaries between work and rest - -## Why this area matters - -Health is the foundation everything else is built on. Consistent training and sleep directly correlate with better creative output, clearer thinking, and more sustainable work habits. The [[training-load-and-knowledge-work]] connection is real and measurable. - -## Key measures - -- [[measure-resting-hr]] — proxy for overall cardiovascular fitness and recovery status -- [[measure-cycling-km-per-month]] — volume indicator for training consistency - -## Cadence - -Weekly training reviews via [[procedure-weekly-cycling-block]]. Monthly health check via [[procedure-monthly-health-review]]. Daily gym or ride tracked as events. diff --git a/demo-vault-v2/area-learning.md b/demo-vault-v2/area-learning.md deleted file mode 100644 index 0aaead2e..00000000 --- a/demo-vault-v2/area-learning.md +++ /dev/null @@ -1,30 +0,0 @@ ---- -aliases: ["Learning"] -Is A: Area -Has: ["[[responsibility-learning]]"] ---- -# Learning - -Continuous learning through reading, courses, conversations, and writing. The input side that feeds everything else. - -## Scope - -- **Reading** — books, articles, newsletters, research papers. Target of 20+ books per year -- **Writing as learning** — [[the-compound-effect-in-knowledge-work]] captures why writing notes and evergreen pieces accelerates understanding -- **Conversations** — podcast guests, conference hallway chats, 1:1s with smart people -- **Courses & talks** — occasional online courses, preparing conference talks as a forcing function - -## Philosophy - -Learning is not about consuming more — it's about extracting and connecting ideas. The [[procedure-evergreen-note-writing]] process exists to turn raw input into lasting, reusable knowledge. Every book note in the vault should eventually produce at least one evergreen idea. - -See [[reading-more-by-reading-better]] for the approach to reading. - -## Key measures - -- [[measure-books-per-month]] — reading volume -- [[measure-evergreen-notes-created]] — output quality indicator - -## Topics of interest - -[[topic-ai-ml]], [[topic-saas-business]], [[topic-team-leadership]], [[topic-product-management]], [[topic-personal-finance]], [[topic-cycling-training]], [[topic-writing]] diff --git a/demo-vault-v2/area-personal.md b/demo-vault-v2/area-personal.md deleted file mode 100644 index 37946025..00000000 --- a/demo-vault-v2/area-personal.md +++ /dev/null @@ -1,25 +0,0 @@ ---- -aliases: ["Personal"] -Is A: Area -Has: [] ---- -# Personal - -Personal life, family, relationships, and non-work interests. The area that keeps everything grounded. - -## Scope - -- **Family** — regular calls home, visits to [[person-nonna-lucia]], staying connected despite distance -- **Relationships** — friendships, social dinners, maintaining a life outside of work -- **Hobbies** — [[topic-cooking]], [[topic-music-guitar]], [[topic-travel]] -- **Rest & downtime** — intentionally unstructured time, weekends without screens, vacation planning - -## Philosophy - -It's easy to let the Building area consume everything. This area exists as a reminder that the point of building a sustainable business is to have a good life — not the other way around. Protecting personal time is not a luxury; it's what makes the work sustainable long-term. - -## Notes - -- Dinner events with friends are tracked as recurring events — not because socializing needs to be optimized, but because it's easy to let weeks slip by without seeing people -- Family calls are a non-negotiable weekly commitment -- Travel planning happens quarterly, usually tied to cycling events or conferences diff --git a/demo-vault-v2/area.md b/demo-vault-v2/area.md deleted file mode 100644 index 5409f903..00000000 --- a/demo-vault-v2/area.md +++ /dev/null @@ -1,7 +0,0 @@ ---- -Is A: Type ---- - -# Area - -An Area is an ongoing sphere of responsibility in your life or work — something you maintain indefinitely. Areas have standards to uphold, not completion dates. diff --git a/demo-vault-v2/attachments/1771694098221-CleanShot_2026-02-21_at_17.12.59_2x.png b/demo-vault-v2/attachments/1771694098221-CleanShot_2026-02-21_at_17.12.59_2x.png deleted file mode 100644 index 18138a758c742744a8bb1d2fa2ac35c98aa2cb18..0000000000000000000000000000000000000000 GIT binary patch literal 0 HcmV?d00001 literal 365881 zcmeFZXIPV6*DZ=7;)7CD5TzFt=^)ap(o{Mm^d_N02)zeHrAW2Vt8@q@^iBXNL8`RS z2}OGEHE?d8_ub$3opYVNul@4-`9;W`dnK7`tvSaWW2}5uRhB0vq9Ve>!y|t4T1FlC z^92v@#>lOkz%!!J_yu@)*V(N=+RoZaiXspgljdv$T5c>1d|msSJX6+CYR&nIt8M#N0)I0ib5i z?-<;nwsuY;?&3^;k1GN^zI>XSiQ(^;INOLbX)CERNW&b>7zDU@xOkW(h#15iP0dBr zW#s;SGw`1{lclq>y$CnAo0}V#8y^?U(Sn;-SXh{w=Q;QD=bXSRIGsG~oZq=~+Bq>_ z4)L!sWXzl(j#l>0Rxmq;%Q4@Xz+9ZgnV5j<4F4Y7*~l@;^5H6!*(obUN_k6VJww&8z* z?$QlgJjThg%){c}5Gj$c$TofVisPw6O0hj~EV<~NJHkdYMyeFN3%H|>c+7KsTco`j zmz?}4-&n1GqKNgu*3%spAu!!T@m76S_IJUVKVKh^?+T%sh-hafzOX7kIAV9a@!WNg zd^gkQs|LrfP}Tedj(5D-vCMIWFO%sCg0go;iExR7IU}q+_gcEZgVA)4#FCoTTb}IP zYBfAc!%JCq!BH%JVZ?P#5!kls>sW(+%+d%A?C;8USt(g1rU}qthhZWtx?j1YkDp=g z-EO8h_I~%CiK{yp)D^|Zy|_1F-})%a;lt1Dhcee6eZi+Ad#@-(hzg3i&P#Tkq&<2& z=2x3wO9#1y!VT8k=OXv3UA#r~TFT>OD=W+0ZW^DFsGyiOt?s+sPn%2(FUY&mIM+2Y zGBUcXtxAo@a_<@gMj72jdHu&2Y2&_=e)VIU=K>DHJnwIT@F*-9v4qUVB>8^g_BS^g zsgL{^$Zn=diD}=cVxTa^`%9b1v5D#nDN)mdBK*h?^~RDycf$R?|Da36k7?q!zg_01 zy!Fueqr?`~9lr=;@(&C&G6B!NJjfu8lhXVm-tu0IQS#Z1;Pxs=sY^)l zN>-J%j1=)nS<2!^=WpU1TF+biQux0`mu`oCc*8@1@mHD|<-s@q*%N2cr-(j#gAY$iX3YY zGlIZ{awv>S1}+EbBY!~)4Re(zOiS<6-@CW>c2CZk^@OK}WHJ;Lvhk8MwE@!pkT#T} zjkvk3<()c@0`GCGN!Lq7&IPut`vZZ;L9HfM+I;!91<0r)l$yEFb}bui7-Q~t2#8AgdPsmU|}r+icr^ZP$PM_AT{W zUccBAzkch?dzo`@hod|rCB6^7iGKXR>e?ISF&Pn=8X3>mo+?kjEB%`KbE71*?z8?I z)GHsk^9)6`3N>@~-AFCg7}jA{w`UD%j5)D6Jm3epe{#t464k5IpXa<)j7g5E{Qd{H7O!0;wtcl6N-I9qF@u5cWPCUE|K_= zd65!q(bjTi8Us20gOEYZl`jD`0qJs~ZO_A=hwV~Lz98?8Y|Hw~D#41y%Aky!&)I^< zV#~rdR!uw|(iXI!s033&nfsZCnP)Fha@ItrXx3mf3p@+5$1I@=>mFkY<%gC=Lv)F6 zl9naDi^a~$5Mv&1Zd*!I%2vvLtW1M}!rj=ub0ox_4R7{yhN zRkl?+>UgD~ZrudW1i{iU3zn`aky^6@H$4`;)b(rQXxA0jm##MJRO?ftdSg!Oook!I zUue&0HHBXY)wz^8{t?}9@Sc`&Aac>&9Q?D_J=&@>tG_NbZL;=lNqxgH<)zstK7r?j zwI=#-eXZ(bC*0b?+EXXd<%8_na<7`xyN5AOT?<=_G_eD#@0OajM;80m-yACLosE`` zcQ%I1foJw7#@iDX;lFEBteO-dbY`gS;{C5jgD0Uy6WZ+BG2UvZYbXL#fzOIhpHHSw z?-?;p<1Fti@Ot9)XhMCWmK!$-?TG7oF=kGqQERCTF+V6?b~j~Aw@>#^FEU0me*4m< zD)i!+v)ZeY!POHsQ4@GVDMh5Ilx1P*cEWTUx?`2OoWcta)B$)Q(+r4U`o!5WR z&r))_)gscn)93q?c-eSwo3KITOyH0ZliE3RbU{!p1(KFK2===1Ny}pz#fQn8g1+c8 z6oK;X9ZF};7kX8;Ghwo0A)i8exHWaUbiCQ_et($Y{&<_6B~+v7k+KO(6brF~&P3A0 zuo!I0bqWvr(Wqrp<={2fTc5buuO*yj3`6YYLN2O}_acd=vIw%)m8jp4Do933JPoD5 zm`?NEDx#3*EOnR4CzeW{m|;_GeQrQ zXbVjpOm-%(f(oaG-cwyy(edYA(yqSYzCGNXeVx^v368{$!+#F)jSELA@9D;sl~_gf zA?m>JJbX=hLuvi*sD>9r zwtoCo-xbb)+a&wLAFIKA&vpSp3LS$xcW|EnN8UMV z>#nQY+V+%2y_OqnW{O+#wvSH{x3Q6dzm@E^&)RuDj+>-~#`4&ITVej?`bU4l2HJbH zD-tvgRn`5OB|AYqU%SEfQFYeSOCQpqXzvJqke=3NUg{7z9U*!iZItv{tk327k?8GoWv^so-G_ZPCp{p?cu=!Wd>mA{+NAPzya@i*iFwLa?<%!j+}<>@}-RID*4k z`YpOT?`Pge2Wpt~K6GA+aWc6W7_NJ!xTw<#d(bfCEb5lBxxHSE6WckSGql@W#b!46 zu6KI9^ii8YVvUab&*!VJUHDaK?HcXZKWLz%?YfX&kJu4hfGJ-r;}+Lbt5Q*w-zp)S z0;pk6-=&Xpfmt(KGZyrG65-+G-u)-eM|^WmoiQWaxO9bvSyZ%l=@I5g{OI(1acD6w zul&zAO9IvQ_us!?b9cLi=O~6po)O5i652XC2gyBqYJSL!>Hu8*>4&=O&2B8WCdMly1b0i?Uy+b8eT50et@z z>{$a|H;C-KVwI%~4^Im3jm%4s`?a-6k5~h69QXO*pjg&(l`o%!8A?O1D+lF3)2H)u z%K9sU4eOPcppg#yh8LvD7 z*|WcHeet+^#rG#;DEdxx>&touDF%A?O5XtZ-cs+oM6dGY{|=d75=iR3EepKJF62KC z-@k)?-E`_dj{JYk*ILH)>!za1A6@jWI*DXt47()%HQs;vz?g-CjA8r@ef~JpRfG5* zFV5`>i|^l`R5bTJ-l+14@#KRm2k}OG9sZT0H}ZzyM!Rc2;cCT|7cqm>0_{~-@B2n& zHU_DR?-JUTvR4k`wdb2xUcEP5)vsMEN!n|w;kfs@(y%nPl? z7gG5?MS@gpuAdK3^L_gDHi~)rGzIHWhch)6^jAU&C&DT{y~kHgBaJOLTt|pZX$@92 z+}H9P#!EUORjNUg2iBkK4-@W+i%SEV78E#c4;Y*uYpKgsDOIhpDlDD zKldCE&Z>}3P^}Ihv?Y;Fk#!Rr1>p|FoJ}0f?_YIy8VBD7DQ@GS#q}Gg@FiB)Hspn~ z+JyUsnVO!)BOLr=->~RIcDjvV$um!n<)ao#?$0>VL|SQhb05fvR{G=J)?~k+rluup zZaF6>mlrB|VH?SqqcL9`c4^Ied{$TF>YIl7HhF-?xSHLxo0~q3uc43Ciwr4k-&Ahv zm9aD?_15BYc(J#K7J@@FRJK;2ttqhk4Y(Dd@UmpKQFU+-)Dl39+n$E6_x1HrR$f>c zaJ=3<@eG`8@)Cvgbj58C;wL|#HK66Kw{oaEmxVwH~Fa=t}@wzcT^rMKYL;MUZK$}fv?2iC!vr#+$3%R_yW{IL?POKZ>M zQq#yj;-v55n$;e1wQT*iKUU)tcu)vWMVbzWAaQd+!v}q9QI=nf%94IbHGPbzI znq#bR<&yBQp)r#5%l@8ATW{epfDKRg`}pfP%(-)dU2H;FA8X$4)FN$3aw}`Cp_p`N z`C1D3wV~8EE=tBv&6bWTW;;1$XC@jd_B4YzXRMg+ms1qmDf!;XWElO{+RZBnX0(aZ zp*AqUspW9UsJQuNAgk6Ie8~plvs&$LA3kcxh`aLVjy1WiAtEIp1Pbj$UU*NOO-J>O z8ik(wHN}e7vRbpT&!R-fO`2xgw5xtFA~fcU&QVR;^#~SB0hb)a06h2tBnOoSgEC}B zR>1XrgOTBRxBF5MQMB&A^R-Lloyffi)AY=n@W z55z#sJL^~v+HC``T#M%JUuGm!uJ5=`_0Gt=@0sF6<%ye`hFVYu;#FA}BEx6vd~UWb>H*!rx@gVNUg?`lJi+9XV}A_@CuW?ed5-iPn6Wa8Wf!aXU^%x=4M)V zNJ!ddR1zq=IbC>FX%s1bd8Q+?B|SZFLf~FTtQi;#hH_}AycnH^4?(t`qIbjLE*!Dt zrs{Y;N6qwYLs~`#uImxrf0+9wCiGn=@cd|%rZ;Lg!;#+e>=B~}5x!@0VGSx0$A5AP z3c{Rv#Rb{e*aQwlueM)es~RHT7VTpnJ+Tp^9k>%LNwO}6x7eZ+7& z$tf9Z13Qr&942o02G>hN3Xzj?uLfsfOo%>$vwvv&mMP`2f*-~Nwzbi6HN}~-M|?H|x)f?!S`_81wgNmn%Z=bcb8h5te->`J9Y1uJD3cyG7fkF(>t62fdWzpjC} zuH&^>v$V%IpFP}CQ(o`T%%2Bo4)7zV$_t%J_N$tUt{8E`M!O&R z^;p`hhaKNuotqNXg|sqHZV#rLqX&}3C9SCuX{tf$WSoR(1cIn`Z zpV7t1aNpFFL~<_m;@P3^h1=fVUIx*Jed<%1|Fn(%*Cq%xGVZw1ZihNuIcn-{AS+1f zG(qCBWu>K+#CBA*INmlDVqD4(vJUbb1sTI{~lSdu(2<@?=TZA`HY`YRA(4sQ$8-;GjeK1Z}N|Jzk zCi%I-2e{067_dtnw zh*efIsA32&{TE4U;`Pd0gD>E&o3z8EJU5GRGpu!Le|I1i|rZ z-MluK{Qkx1kEG#?VvEAOUI%LhD1GMpA|fKQZPYND5(_K;fNtfYP zTDOV2Zc`o>69Cl7+?EY_&^p^1GUw6jWw?eq-Jo8CtxuEs9!dYf8?fX=Rxc)dg$tC) zV!>Jl<+9k1z7Su6Dg544qDUwjJRcy1zOsX}HlwmK8O7dXBA7*PZQFnpHD2@`t7 zmIgO48XVHfoYpZL%)n0Ou4r4h`GUY&a$p0OJLIS7E-pqdK;5CfqML-pmNRza>pR>R zJKPR4{*=)MEP>Te?_t<#e?P<*p4gA;_0A%H#YX8qy0`Z#l`N3X)3WY#ax)wfA?`Ym zsulsOSIk6h$ih_lmqE~SPw2#O2g_6FuY(w|Ld8JI<&i3;F*>GYG@FKy;KqPEMj#S7L% z<{lj#R5s9}X`BG4M!HoeoqvlTO`ltB-?BZcjG~$+<{CN0-T~3 zJ24G3`zA)m9a^);y}mwmhxMCbAzU?e0>YU!|y3)e{!0Ii`-WW zD(z@Gy*f8v3UCfnQBlo;k)GhXWhGef@$OcuuvpRJEd*|rYezh4rz>P_uLyEol7ENYDeI{a-Q8#4uP_gMSnDG z1--Gw)YZh+{$L!_5X$ExXg0AI(i9t{h{)lqup%!B4FAgRaCENyut9QRCaIuP3h~oorXS>G@RZ6}<#V!_&{K_5)pQFY; z12c6F{iKUHsKw&Al!azK6$GGn%I&J>qx-SrqZTO!C)D0zg)rhPOqKB>WllU%WtHu` z_%@CmMaCc2y0rW#7}1gXEF)|P1J2sg=EY>=4cAvzqU{mh{IKDGhjdio^Q^ZpSV5Yo zC|14b>lTL-QxDuG>bNuume|1DqI!LPa>W ziaMj}9lcHlQs{(LF~h@^trM$-wOpD=Lt3ZBo=Fp1FA<50<6ae^#0uB-F?Iej--|=v zh-``d+;Q(?Z%LT%={O|qTG!dyu4qbLFL=QhkN*mj^1kumbrpAllEUPJqm_%(*ZJ$7 zLgrjKA#GMeys>#<;{CJ@^^US<8x2}*!GX1NU(zkmcU5|4zRqa78d*&E4Af}HyfQe% z4$(E7w(eBT29jo5Lt3>x8}o&>pD4^$-G9(#=cN=9S84+}n5eOgQ=>km6JtJ@Kt5UE zE{vFr7RV+t9a4*WWmU^z{mj5k3BiM@Kt0Tham)UqU0fD1Lr!J$8vM)Jnmw)3h5>y3 zD7X_@_n52Z%uCdn;zuQFzhIn}j@kn$$Hp9Xmb~Of@;lLEA@06-!3*EVsxFraYT#IO z>*tvw3Ti zd{=mVO8>o(gVz*o4+PsZNRl2oEe^_#Ba*8&dk)5?L2A;qrX6&p@D7dRL+q?r{g;ZLr{E~9m*iim%ah+rg^GdeU@Owgempd8F*v!YP@ z%9a6NE4`p;IO;aj+fDj5r={-zECsiQ@s%m_p2SBXl-%J6L;)qDlcJ>%03`*5!egIE z;Y-rR)kkx>##yXmIG1m_p2u#mepAqNjX8 zk%wo2l4tJ*IYA&$i&OG$B03aG^~|eF>V#L547yvbcbb%!SP$&KP#VQ?Of+_s8@{YC z?(A7O;x+`DAa?;FF3KIpk+$JyiziyAc2rre|h8q4PPKIRdIbUFD?fc$;uK?H_CP>Q_T=Sdw0h zZDGq`ZK01Gng}Ru>&&N47bOm>0XQNlw3=UP5+Q!zu6XEkx_%goJw^{VobN9!FOQ~4 zx{>#vo}LUhNK75I2}Zy2W&U2WZXvN7SG88M^9~Jzuj+ke?;jc(3QIhwf-kN{-?pN4 zY-hX#<7j<$!VbqG+cGCR)bWD*QflDanJRQ*8L{Na>FHdbJpH8mLcUJvY$i9{YOQ?O zFcWpU*&qo}H1tsZk=T@9dBE-+0T>*?LjL5BO4wtui%V?046`^tJLbJtQ@hi_j=m%7 z>gw8NA$dA_bcB|aNLGlKzQV#0dqa@Cg{R}{dy?84q2P)!RK$pmR?hl2GYqF_itQT zWpmWz2cH(r(c@>JN7_J0qEsT3h$Endd2v_ z{?sGROT1{wvl-HCnfLh>6#|zHNtoBTE34U3nzDCxjbSwKkd#rtb7BktP*? z;mBZLb^u_`$2+H6?iDn6o#3sN)m8e^wc4ruLZQvN-M0MSnj8-lX6ghRj=Lj--RdMA zqZ*L#b(`%$pjh%|Um{XA|EDUFxV?7pY)83%6sHz;d`whx!y9*np0}}wTa}l>uDGU# zi)xjciK6ChYC+`DTW~{s){qP@n8@qsywDQHDM#X8Ubw8_SDZ|K#+JqEKR8UChuM?q zJPWXl2UFIIf81_|(-yCME!0Nkv-^hyq%nc1^credbhQq%tj(JHzJD+-uG5M{e$HtMJxs@jfxLBwRv>AU1tpqRk2dCIHgvtX76 zE)vnDpxj2mRPnQA6<;>Jp`})CpX~=T#Y&VgTU!or)mRy9V2+qtpygzLRdAi^aJxTK zVNUX5SF-X}L>PyC2WxiAqvgbCZ}dJjrs>hnQ5uw4MG%8`JQ0VtG7 z1c4arYBih;X*ZjpclaBCegk@!j#_x;Jw8d$rtigR-|yc%{pGE0=Lxkl0n`;s!!NI} zImsU0jlD!FYtR7T=gfY;vAjoy|^4|`1 zWbwD0pVG!2sPoNMHG9)Lb@4g?h%urDOA|Y)J8qEzZ%Zrz3TZny>gkvxK>>{_b>94Y zJ(9scKSnGIkVxc<1E8n#Dx0CLK^7KrT|#uVO-8Mtyqt%kw`&0QK`vP^RwF*W>}-N= zQ$TZsebWL+(+~H*u_W5R%H0{Z{OE>-yRp8m+(ey*3y7tnmIt!YIu=RgLrzlw%8@Ue z0^}iql?j^ZjwoDwLV`Rk_i$WZ^m_f_)O>&f4xldd{&=LEPAqoxbY82_XH;driUc0| zl*e_&w2bd*DzYMr*EOzEh4oKV%%;-Il5-Goex=1TOg=}J3QTOLF@XGhC9H=0o{bTf z62H0GVe77w$uF+3z68W~V&^+;bhRoGIFk6d9pmO=J231{2A(dM$Q!Jg>7;u)`!!Gm zvLBpm2~!yAQlGYkBV;Py5UaTTIV}aC3>8<+DK` z{+&A?V)Px~jJmKq-*WRkbo(l8s%OK=$>}irnI$?YTH0g&C)`ZsEk4qt+op|bO6b58 zz9@KI=qk)*g@Wj#rmr;!MYkWpXqkB6H4! zD3Um<7vC*=-2?W=5!oC_43 zyP{KQ9sN=4BmPI;dJl7}f>+BmbG5y+W}1ark?iU&&d!k%$A|6PfF_Bn!nOfWLvVw? zQu7)V;PmDUZ7dRE*^3GQggG`oUg>Uke7t{faNcbPV3~8L31FR@Aq6$xbEHJ#>s_LH zd2vZC0WY8}(>l?karr4En$mt~hsoFBwdhH7Sa)vvK#;j&e!K}39#fx1`Q6|0SI9hK zn#ON$wC_Z_CRJL1NCaikClq}niHHC&r3r@1MNQA(Q9&nw?~EBRh0Ds|*cHe&U3cH4 zZm8LM>yiq%gJ~X3MU|KCJIzhetZP0f3x=9a_`2y$oSqpIT3x0MY69ul_Jp2T+U0*nC6gN}c$B%=c$v)aY%D=l{7OLn`Om?8)XIJ( z&7?wHQ+x51^0M#VlG}T&-A|fE`u*{|tjA?qomRWit|9iS_YXuAX14v>h!`UxEpNu?a-be71MOLN4u$fuYsi zG(7B-3|@b}$}?%ji>?(lx9LM{KHm4(jOH>BS#Z1$-+b!0?ma`3cm{M`LMwDnJ=fJJ z``%n3=4)lwHJ(agwAMcNY=j4OfaLRe$oVX?$+STksydA38NrZ!;=7aLa9+4Bcuc|=(QRP??1Rj zSq;c82~PbF9>$;2@S)MsPs;NJzvAwhr}wgQ0qwjsgc5y;$d8|AVpRfox{*Hnc|wO1 zPIFUUo3umIpEtUErK{g+S67&K#|!Ot@pTf%oCNk`=d?Kq2P*`nD#}$yvWBs`^R=H* zZudPFcO}}0zRY)+3g6NN^P8OuV6p@9#(T)%)-ev8rnt=+P!6;qF?A5u$DaEhmqEV~t1%>okR06kCi-cCZPx zz+N_oE+fFe=EwdtB39xrHjW916)xopW_6ENR!EsyVkeO^qS}1BTMIe=c zC4Z~{ZqHgQ($P(KRZ__}7^SWk7Z>$bg#c`)!K92ROTS^OQqrr|D3kaRAl`0G^RS3A1 zZMU_xS=!P0-f{*q0Ynp(u;f+Axp`)J`1RD$7zqeQ{#Myh327-;uz9%O0|JSsBP(mR zR&I&aF13c5DPFLu-q8l<{?yjf^Cj}g{G`1nGhUOdo|9Ko!RBAhmc~NRP*Z!7 z&e*N=tAzZVDme1uZB+S5nxKDke0-kC%(pD^n}9!ni9MqOBK#@38G>6bH3z%h*(1$- z|C+IYpRAm;7d z;i7g4Tv7N&!mov=7=}yCI{O=>kFhCz<1*OV&zcd`t4YZG{6y7U4Y1!onDDC^Xhb1Gz%ud(F-=9B zKZuJX@Ta3YM_>n)#*<>=_1v_PvXvZ_6n!X%)|1YeViY;a>N;(3+d{m0RPmXpQBIbC zf2+DnNiwu)NUN@PSO$3Uhta(gR40{ zvjCXxV)yM?ODii@xT8zDcj8Bm>=d7qInPZ%Fj}k{wz07Z8Oqa&Ns@G0=qiDv6aR6u z6)Vu@2)7u^=sy0X;!`rTHS&^>mOPNg@%5#e^c7!;xtBw-(%XBlPd;X9{>`|lu25h; zSM6HKuez4Da&FYoER^KSyzGvb;1u4df!k#Hc1=31;$D41yJ!kh5VOBq+H-Mkb%hQG z&#&)B7U=z2`^RLul#3Wx8!1;UgB@yd#nOf|>-Vq}>t6pL=sVjdu$+Ok3{=|8+3r~u zkqLh8hY?kx7_clr#pb)0iFSv@*4jYsWJ}3{5znGwMNIx}o+s)@wv$qOnfBUn-8_lz zO_fEr3d(dS)QD9KgB`x0On0{Hfq*i0odB7JfA#gdGVg*3^WH>_lc~OQ7A^f6VB2=s zoi^f=h624zNU`a!ZzWDZ!S4)*t~LVV9Pfq(fMqv$7klFQZMwF*37wwgZI@lPBw_mHcF7nN3b!&nVw$;JyK?BBoC>bU&{~W2pF2 zK4w!GE$km*CUuoFTIpm&V)*NeJw3F_3RXi*R1gBuuOJ1>XZv|xX+k_SI9x8$f&u(! zHN+*)GmV>8YY3FFV%D5#1In7#E|e4aElG}pH}ghv4JEOCqdkwbXpMuNYbS2k9G($_ z=^7L!?VE{td3bnMJ_sis!Y&SA5I`09Oe((jJ7*E5vbbJ}HALw1C-Ywln!MRznreue znwm9XQpq#>(PAY+z%zzY@;z6IaB5#q_S#_e>b^A7=n+R0=$2deH$yx={tbTN5>xm| zNlDuPcVnFpQ@@YVL&G;J>f9ilQv(C{4}n^!tsxLTzXHMGF7De+j+_pE?3+4n2p74E zhd+7k(x@@o-W)3qajjdCg@qd7HWs(rgXPmIP|rOBPSRtq8wjrrY0!kDPEyH5-o7hB zHL2Tkr08Km;FZqQA_O^JUOwU(n0j?}BZ8mwP_A=rY_IltjmT-b;68W=1fW_*f+64z zKv8*DHbt(U_j(>}-On$oPEa>8~%}0=!L|&uLQjkaX0h$#0)BiQ%}>i*K4EN zB9tX)2k0hB)~LosiU7^}Z$w~5l<)kfxmS88i37|qoHvpN(u6jo8 zR1dI&`Ez^E?U%%Ye$Wb7T15z6x)tZP9`9v+rmnw4eV zWyP+U|Io=he=%BRVyu*!h9;E$;s^~foZEib#aLcgSXiQv{!U`mtu7ph)fK_;61#mQsF_9atDi|F%w?1<6$U+8+Cokg_dg`K|3 zB=_tI^*LD*u7EZFF6&a%2a_lYwPDpL)WBv_kRK>DKP~MGA{ZQr__m*EKWfZNoMGl< zV?@cKSjjP{LgWj=;XrojL> ze0;R8?{0Ror?od=Y7PIcEV9h&mqh2}~B5)AqT4X=-a|ED_tX{Sbb-a+#LEUiEa4v z^Qh4Y=2hq zW^$a*rAh3ZiBEu`gu$WI590(@+(_QfzaO_;zx3vKZ-*GsKywCT@)G8YdSodLKtywY z8ixUHncQu{0WF|aIksm~y`l+)LihIfp=0&iLWFaU?n`FeUOIoIR7ncEV|gKvEm(|! zD=TeGp3DJm(^pa#NSE}0&Z}?=aBtyycGa1C6PMyctN7tW>9+27moMxt^F@&A3ILF_ zVLsT;_jCi{-C`Sdw1?{9n|gHDZq%?Fp6|rOtQ`O_y5DT0;o`gsU{*T~93dBV9=o%f z7w4OT=gCVieGYeOkGo+$e2)8dfUyFN0O!5+4V?SS2DKdqOI&)=&2k0aE!p%^hUD;C z#M5DW_CQ#XSC=67tHn+SWxYi5#Tq5LM4mpB6ux4xeCqe?fCQ~d6hhHoExpY5TM!g4 z@jK<4X)Zzs*4t==QMnN1;fZC7%G}bXN&xz5=Y7{KhEXZj7Y8cY_2METqG<*7{D!AH zf^D<@A&~P4f99AeRum~f1E{}V0B`}_zR#tg^WiqvGq_w5&zmH9T9-ixo8l#xvtz-; z8HjYmvnZ>$I6sYf14l! zDUN1D6o7bdC7l>JuvnlT3O%oDbu0WCC8+}H1P=zcnv8a)xX*qzLstlV!G|lvaB&jU z%O!a24{60*cNTUQoQlSW3lBy&e`e;COes$8Yp+vkaB6hQ_=(NJ>4{40v@_2EPOs)R zE8+KU-TcG0XX42p#Scc9FFga>iu_kO3IOzoAVq(#-fIcLuUY}?$5(j8i^>+iQ#zUy z$;H)eQlt>G#CGo@x>otZIMH!7*P-Pay5&Q4NLsA4ssD`nGpI2GZ8pNB*$UV2se^59 zKN}^$b#{TG-t_LQh0N5+ZdVLo?{C6ab+*6qN!~R&I%;VB8c0(=;E$F&yX@{lX_Svd z1MPrnmiSjnW%+%HEkDwhYlJjKd_@?HHMt5HR2_P;-X`aQyKALD#YeDyy*B0T<#QFQ zy~gWH8m^)hQfY7)9 z^15hYk+=)A8(RWNqL??rUAxGO6Qr7vktC)}4edCTt6yMq07zTm5zY&E{S^W5somtm zNCY@6znl{b^XSy8unE)mXQu{(6wg!+05jE4h9*L{)^$C0sPqAcc9FrgrnUNVB6Gdl zMPUbBKvpEDKOI5KQIA<;FFVIeTQ8czle2Q#~ox|%1+l5R7DwO`*%sTCeYNvq8j7)G*tCjr=Y8}KW-_q$f0>AYGl*)YKUc36ch z1}fN56R8gwKtxu6qdfD0u~`Xa(@&MTB_&UQMPwXU%bw;|{>Hxj!~o&0Nn915GN z-##Q3oFD^0*vOGr9icGD9ca^A_m&6HUT*>09Pf70rnkkb#n1}(!llE@j1ubHKXuU-Y>-m>K?(jaIL2ncw4sHHVYwrj2!^2i0uo346y0Kt}4AsI%D zd-6g+Oe~S@+kCvKN>6m2c0Fz#7NK9xN~jheA1~)`X=xcGST{rL09YSdFNJQkMX}_h zKzbkdKRo@Hw08S2*RUghp}z16(DMSE)3D)u7PK!#TA%*7U49m5D;#MYTJGwF!p6R$ zxdBGO{je5WuLN!oFtGU}L^$cQn}BU0lssxG&{U)rw%FaIX{(tHW}gM(;Pj`%Fuk0H zrZY7o1-E8#34TLGp9ziW&Ml8iRf@9zuipaD-A5LHNvV7JiTq!MQpj}r4#XIGF1tsM zne?y&9>Xd?exHlfQ2uPIRXFc9ON~8}%bhiVKp@pt_g8v*w}5gGba}|=EB@DcU7*`Y zbZC3DJ&rvWFx>h;8JUoE6%vl2$X|+)fcyL#V$8%6z50xxS^c+ZYq0#>0KJDsSwTYs z`T6qlMubZNd^@1h=Y`?+%7AMfb;2Lo!~Olgt-tJAg`t2Xrq08vb-mLsnr32j%JmYf zDH!g2E9v|*-Mav8aeQb$T4Lq^SSH&5Byhiar$0?L#N^kvC&j%Ir=gGbSiMraZ_;^h zHC5pb#ucLSFi0aKT}iAPNv2W;(~x;*`08R~qmbc_oc@SJv@l!fU-6XRAN^ayG&;?kCIHFy1miX6!HDb?WwwIZo;w?zIV{ zKunl0(q4hh!1KGfo8y`GMDCT*cu7R+OllZl#0$8|%rb*u8{h=rK~IeG7rSrd4{8Jr z+0>W_5qyiMwyB(dE{YQd*cb;uFi^}r?E?3^jzcT^7ccdjj5Vk!?v0K&d&q*drSO** zeX9LgoePbl0Mny)Vmr3!K2Bh5Z9U7X;_-I5bUn}ZG;VjHJLJrxjW4-)Jw)jH75G|) zqR)-@=@>%DPdoU3SLF7CMR+e_^hnZ(v&eKvz7SL1Oiz_CF;vhP9M)=`p0>}|u4W8_ z`tlbjtrXbsfLTj`;gsN0td(gNaN~S*z&iX(E>OG%{89t!7MZQzRkrfq6ZoBxK}z5e0&}H; zeF>Qw$${S+Nw`kh^x(?D{3j6qp1ywq@lPQB-^t*g74grC_-94@|5lcNw#GkOJs1vuKeUjPfcw1JLS#}E9k=60OL9w72t#-|P{j)0Sr zl&hG6aa3#K|2Rq1_+7d2LS;L{>yKURzuyn&E&MK0>iPVJ5jhtZfMX^t?G_gU*E74^ z>PRc9D!sR$_yv?%ocY2|Cl4=wu|D6EZbzj)^@-nuAjjSgc#}9~qYT+gS@NUZxN~f_ z$3n6N_Wxn;J;R!Mzim-L5JBt|QJO&LMFFKLRfL3I41_9>gpSgSQd9&fQbOn;y-6p4 zbSxkwROv-PDbl5b^!rBr|8}{1Kj)rv&&U16hsVImTJL(xoMVnLX4l4>!NqZ0N4&^} z^z8V?-3j}IP}!Vj6+xv1SPh`Ty_8?_I2WDTg)BQTWSH^JK?>K=RzDJ zth1uOf?C^GP}iA1Nhmv4M)J=E4E+5bap05^fCb*f5V%4`T=8i zWA~4gTr_uLsgBuKw?`ilU!)+;0{l|^7TWaYFyM&4c}(>~Z?`A50Xtv$CJz;Z_)M`A ze)Sf?z6{S9Z((g*4aDYSpuipL>|tEv;%Hk`oqhbK+r7CPLYb>7*ygEy@?3eZnBvJ* zC+KO})DL9lOtN2@<}bs6;O`y4YHI<*XBO5&{Cbc9eOOMGMt%WDu z$($2EKG+xokp3Jt$P?&Y@rc-ycrxUw*G7lf*tJJ>-+|7ET_~=oX5p>Lhn`TF|Fl*K z{hvwOJwnF(Wa;J(5PnFBy!v!biXYcWMV1i#9@MmdaD=PG^p%-5`lvfiM_gAp2>sA8 z@@S9z_vGl1JF%NnzP}0-)E&l;Kad}BNIYKxbeF7K5$PjNSD)<8#MV#km9+^jCiGWJ zE4DIF{T_GSAX)xnj$2Q_+()|sB0#4PT1dh`OefO0==m5@M|*ccuW>|mEFWf?xp76z zA*puZZN5|G&IbyXs-VkUdnrVYz|UEk<7)R{4aw^bJJl|}WkJlKp8T^{L#9JC1EFAW z-9wd$NFrJw&51&M}rE48t%%%8^&z?2clLKuPfti%j z*J9&C_{d1&IHx9%O}eL!0GPAZ`+{5AB6qH&Pcb*;tt{`;9C*4l5i?PmxTy)+5%MdBTJR+p!vG&=3*Yu9^Jgj|2szUn%AvYqCYFBpk^*_Tx&?C(auC#D-U zfXZ|cvGj5<-*d9K^z+r3+s&RA{A6E%tIJf^uo-`(Z~UdWvah<1HNrZr4El2b1Kxz< zRKL2cSQAP28HiG*b2on+@8npuvt?ta(4Vy^TYG7)NA;vHSlQm68y<6pJw1%Nu0(=# zVvdvx)Mg|>y{rQ~E*!7nkF@Wf0&5>Vow}yZl0oy&LI(SoKN;4a$UB<**0(X25$_ys+YD9uQ8uihX_j;t5#dhpf|A z%E3%3|LHd;@n?r*J^u_J#Z?O`MG_qZ-BuD#4Uq>jeK{H|IkN9SQF&ZSBwL`w8z=-F zfFRA)=@)M$k+Y-TSw|(#H)!Swh$p}KQt;I{(vD!t2Hwh)*SR}D#Zd#;B?SAD52rkZ ziXT1~_uyZlWaLluJMv-ioW3ZdV>HzI;=J_SbbCE;77MIJ1cD7))0Gr+T{OfpE!~Ue zG*(`AMGV5+xK!4bgd9NgCde)SNPN`kVhy%k6nO;dDz}qjSsdCwT1`VF>Xr(0Urez& zX-mLqCR$H&UiLxLypqhGR&|FXGZ||)DH-;L#)LUw+|}*_$=7!xkWM$}>g=Kw6owKi zW0(T8at*GOS)&u`Zf8BWacXkP!wt}A^hgCS2^qmo^`^IE1ee`R}fHhm~@8@HbtrE&2 zo`zrCw?3VhNxG#{pY(9%hR0enyR=COOZE%V)RE)a^8LFZD%m61}T` zlcAHN{&ROW#l6Ry`+ZliovqWh_V%iF$aJE@ISCGtUcXKj38&1I*9Co*38f9BC#c9H z4gtl==5tX_kp>vj@MD>bXN8SNd*jvWm7e6g^ zm{fk^#WJeUP~C55$VqRK;8o$GFIs`&$9JH&JUcow&FJ%2B^;Tr_Itf*WXsu&HBTuMzo(lQxIc9=}P*QYNpIa_?d!qCthsBkdepGHf zwS1M%R{L=lVUGC)Wx>5m-Po^WG%j48P6R9u)1?fKZc1snWP4Q>e|!^2tRPfM;W}-qP-NQ+aj58yJPg(2~)(-W-4p~6D+?((5@_wb1QJ* zQMr2t=D!J!n%)%7*(tEUcD3bXl`9zkT@<*Bnv=A{xR2>O8z@FF4^8wosF3p10J><8B( z>JnF^WM^R-ym#Mh#yBmBR5$2)*7y0ue&Uq2{Lvo&^BD#6YVErb8@`?B;-?TDMd9s~ z;{(eahVYpx{?W$`jf?F;1;p5x`-R_83NNA@J>LF+m-2{5kt=<1wpWg}%s$#SHn>H= zQx+HhcBSWo^3N#mf+0kClkU;ob@HBexR+9Yk2=jxqseHZU0KjRAnRjXC0-u_V*^K^ zIDRC&59#IM+09OLNEoIsvbtRoYw9z+fl1;XFLQ(ppZK)#(RGZg*0QG--^Gj9Ykwnz zA29oJ_q=NWw5GDer^t19hN!tXdu^|Kp+a2+9M$ZUjIMoJh&`5hX>8L}8AJrV@MJi6+#1Hl@kF`79kYO! zxkvI5qd0AQ$8P9G&a_x{aDDia$DB;zHepSIcV^6Nu+W94ksBYmuJmQ+SLLX~B9lSJM$}Lt+!MPxt9qMfs`8dPQ7fLuwE={DVj+dCvDt`x} zymwM+P#eYI=YYx9b=&*!#W~4ViY#NV`7Fd|Zl0!NKx*r<2gL69y|rNJ0AE1c*k$FT zgqR_~45(u-B$E-j>ffReXw5W8@eM?)v+6R3F2zPAHImza;M&FHIUOmHTwdsqry_z5 zvcGZ%z5MDK4eU~RpA2bhD76Z4zAr0&12JUn@nfImiot{Tv=JFQ8R-3Xy#;TRhK9@; zeGET4S2U=m5AeisiQeG;H3t|*f;^9v?$e;OD$8bK4EI=BQ4}$ZoLuMloMeHb7N`x% zjpI?;GW|v9*nVd-xyKkGc?sxnc{KmGv_NJ8)w=d443uaMBaV0YE)gFhh=?pxIm9wD zltq-z0*=F)x|CBZCdo=sZvSw9XD1Ol6>B!rbXjB5DND^$h>Nwflucor!7}OlSwZdf zmx=-P>|x?;IoI#IW@Td5?o$bnBVQ^K?n1O8oYgS60Gfy9**Ezf3-CMb#Z0QKXFVT& zi*PZP$jG+?bWtY8awKDvmV(I1eABCXrKi*l44b)klspPlnW2w+u~-e-hM zFMyP<;2aLk&AJ3^P}8Nr`RlD&*FWe4DB{k5!7L+OJ1u_IvI=`q5G#Rvk1e33+iIES zl!$Ble%|Ug^Eu=tvsud`qDCUvAC)RTGcU6>K)4N~##VfGYE{`tMkfd=!`dq~i-Ighv7+b5 zRYx}7xZJTet@f&R+VZ>1rS1ZJFN$%PE6Tn(eqDeL_(^K_<&IWY!1Qhvc66mG*{O2t z?sWGPI8Ms9UIGvFMUdhrQTYj`mw^F*0;id+Lv zsMS`?UL!Fj-#dl!t;jU*uO$_bd++Icmb~-Zaqq7jxesk+AMC2W2aGo=9|(cnV%*<6{u*xkf<)*25o47uB$_Cztf&zGBf2v47#H7F$EbxBG|7pfE27| zr(Gx5c;Ix*R3Q6k{?W9^y%PvFK{sMJsSJ7Mv~_b!x;Sz*kZ8`W_sr;z$oboO7zI`TLxxk~d3PmHFTEh%?E0&5VQq3bS3g+T zs7MOq=`nfh605m_a zNEXQBAZO+5$9YFD%oH#g((RqotX#jWF8<-IC2&ULiPJjd$=0o%Xf_flV6Qe&gid0R zuH-OSm|j`&>aoVqsl^M*C;yD2(Ak2io64WRv}^EE#YFmc-@j&0qqh-sS%K-rcz9XG zG~dj^JaZcX|Dp^I54 z!=NY*r2rD7nQZcBp8BDk#$#`KE=sXeu)W+Sau||hn6)oCFKpTnA|7s;U$Nn8bc8Nr zB1r42u9Hf=gR9_6(~Ocf?_f8m*VVKRrLrGhyqj1?!3Uk&=#nu#4CyvEyv(h~oVVk- z>=rfcoaT39I0EZG9Q-t8>V)w8BkVN7NlsgfjdlJCjjX_NVy55s)jF7+!%UsjM_awJ zqMbt06&hs9rt!5(0TvE&>u^R1;mco{IFrvUmYw^ZZ_cy-+52uKJe|GoE<5P^>w6%s zCXL!E#u2h8TV4uK4&-v=8h7mFGG5-38rrLIx7a@Q0d@MDTPiP^dR1x6R^!rlZe0!$ zZuOTBN^%rkRA^v(cAs#PJRGVIO+cyLk1~30+EBT{6y?W_QcSYvy3<1AzAMb|a_e_8 ze&X5Yg^1pl96%zpZ}e8jIP9)mx@m5p~jB8KrE1Ql z{5UW^b?Ww{J!)$p6kQ!W%^_hK7)B%flvmRh;F9VAytF)HqHRh`Pctnh=}(1QbDo9J z4gsssvLt^FiqGDWj=a>&I;?{rFk8Z2=T-G%wTMm9Z%Q>leS81RBusbJ5VQ1lF^)0M z6$#Z!1;J3EZ0fj^YW1Kkc}&HEMd3_}LBsKs><#k4mi2IC^o>_42($_%X>5BcgJB1Q z(T*Gr3)K1Nq<;~9hD@J?kldKnS`N2l(L90B#~_b~9HrcThK*8>^0^v+mSwn4$;=nc zxOE+b7t>sSR_b~uI{hI$8%|lzmS?s#_E;s34I($H zNc%rsYU89LP%;(jiec3Dnk&lB54xs#g!vA5*noz&8M1Y>|UL`V5LpE6=OlDH;J0euQH^Hi23;u zR&-+WaU*F36*)>T{c>r8f17+|q0Mj>4P&-nW(l{IX_7$x8zoH>G&9mKp6dAP@|o(DWQ@~$ z!OibF%@p>Mk{wBHTse~I*yosITAdN{mB@dwR%>{~O!Yj>`;`ERmPeW0y@Z$Lnyfa} zx8FH|)0Bk|p=W-zgM)6*de%l`1&!DI-kw^$P{#6mr|nTpHS$)i@3K9$pmtG~&Qb(^ zpWgX>2L%t$Mu_mjH1D2r%!w?-E#wuQz6M5zPi$F!>1&_TQ*RvVM?P2StR2Z=V9UIr zdHVt%5$HC_vF_K=txb9!Z43=&DGUrg%R`T4NPVN&3v@PfXztwEt!lbI*msPd#B1({ zcEp^9%ATj9!a)uR=UU2J&L8yrUNLHKToxL7F^WrL8d{#D9>76^XOj0RVbO#FD2( zHNGfoh^o#0-PjKivJq(s;U&#A&No(8AgQGOxRWh4J%@YuHjv5=%FM{%U~P z;zA9~WD{tDz0OU?K`5?`6+gaz`7Yn~JL|#xt)8TEQA0)&WJR{xKFH%LP7fUuyzs;` z)?muM+091axNrTiIG*QYJfDjIp4Ti=?nZmIef(46vqK&+K7LQ4{=p1R(^PcgX~#ES z%dx0fWM(BBf}{O;f!zdb5(#nhh)EX}1a?3A14Tn-l?f!sp2nBwY7q43lfU0Mf%DIb zB``lclah-Vi1z3X9)FR>ua#HG+bPdP5i(!nmQr{=OI#Q}(x@MH8g+U2=j1R)UyG*6 zMJb%)d>rFT`P#&7Nc7PCJZJes)gFnFcVHK^e4belh8%pVxIT0}kP$NzSCA<`0i55~ zlLwqyGU?0w6o;jbLFL5#$_og-=NZtq2~0g5OPf5N(8@Crba>b8?zd?V8$c=I8o3{; z;#rXNF@hRhupVdYSu4b{PoOXn$IikK{>X+OhRl zCaMWnKz+7_voUVLRxF~_XjHFDsWoWlsdMBlKmD_k4}6wNThOF+QUjmgk7or*v?j7aGu>n2Ly>F)9C$l`L zA?|FTpM!C|Ytcg)pmDcpU7+?VhZO0Zcx^HId*2~E3daZhg)V-vO)kg&mMLC zsDfwe+~vH}zfV~K4NxliWjI7bf^@v!EPjK3@NvL-mhtbJ(o>=SxwuZrwq<}CJ48Q# zui=uQk?HXqA1_gvjIf|3d$x&1ofuOe&%(X*cF_^~m}?GI*S{{66fMG_oD_xWG>-v?1x0(+XaCel|zl6duu^eK} zB4*J0LAb4#9lROgWo!7;*$ko_IOuMnw9Kz>F9flJ(^Zdw&oCN2p}j4M(z<%fMt3Ol z42q9I7s&_$;3a_AyBR*JuSofzsxD1Xmq52)$=BZ04!FfLhCC6e`j){GvV*6DlAz$_ zD*&bHa-z|OF9M*v^Q{M0RQHWcI}PE}`jIzTU4r47aiQcG#Vz)!Xz~@jcEX*_9fghPV)QBQA^j47Q|6$ z`L|KAo!#m(yGR6S;Ko<{pM=)svYDp*Z zQ$Fc#Au$w2s4xDAU_#@tjP%kOX%_F0W!?C(5ftU`3DBYV{wO?g>Ed?hHX?a7?!Wr_ zEKlPVb4X?>3yO?rm^g6#dl>0s`M_A1{R7ygEY>T0RL?0-4oB;AyO>8iWV-@uKBTxeLlp8}$bWg-N-+*-Hp zsr^h)6C1;p3gAD}bn&x2iMyl#6O8m;dc_{rN*0N@W^K%SLRHS)Y}h8h@F4q*NTO#; zSPHPCjc2fFHs~_28q~RaHzZA!fzTq!yccY}4|HxdDK7_>oD<>;m=#6pMt1yT%D(XY zQgeF1ZMyKtIw#qU;F8xvL;$G?!SGF{j3>E`TSVsz+KOiUg;vG)$g@#*KYIPA$@3qU z6bR7keW%^cAe)h28bC%iYbS3bm#C7_ zOI6fl3ACSrg=u&bOh2QJ3R9r+2U8FCU(OnAmpi662C(O z_>3QI&V7-Nd{4z!@Qq0VlO!=+m06hsid&-?_P``~6Z9NhAy!-rdNX&LY)jBSO z+OnhklB83At&q|AKcSXV>cF~2;lwe}|Jn|y?ohGnl+;Dv@KaS!qqYdP9t{o}3e~$?^IT|GHQ!#HVGDyWIZ6Lo+}99*M~`RuS^9 z`6Lcw+aAxQ7sQGw70Ka*=ziGr#SU5PX0&~e+ZBJimMPRN7dFSlT|2{pM^ZUPwYsH; z@aIY!^xA$km!x3y8+(hzmL21qhN&2eW<|;X8r4kJx7sQq1Ujlqz0~%+J*GiHn}+L- zR3Xz;XFh*f)9lnqRqxq1a;wzQxO=NN^!Z^kqVB=8CEZ?V&^yc{LPOpnzL;ONC&D`S zGaprV_>0Xc6@o)e$XmoLOgqPP-onKT^Av+(W_*FK@GAE!Rgfd`Sg1D)Q1FCN(V|Xj{z$#?aia4} zOG@Zj#~_?&%i!xpJzK+o3(g!Ej5>k)@3G86!t-&Uh0)XZ&Eup zFjIAn9!0MW|DbtYw}|>W1FIfu<8*qrTop(KziN!eh&bs_s&=^XkFyZqrD=jOX&-NA zx`e!_Tk@#GW@rmSk{K437$xdy*e?gn;wfPPCpv`DigHeL+&Kl4!ghE$6-1eZgm$Nv z6Q*n(G}EXqwP@K>>zK}dC=Vfx=#A_!Lc7{l=ynf*=1fyeD4Nsyp=R&k-f6!JS~C}N z-!ba^+#)a-8g%AW9Ox|WG-58yGuaPE%sgiMl#=usLO*Qxu*TF$8q*6cgK!DXW z8owv(xsG)0SWH8n?DL6I%RJV6T#MOkH5+<9K68au@`8%e#l@JX8I+CY*RrNXY8~Xa z+6BkLhu*|@-M8inz`wMcpyW#Wwx#+KZCJYZU0YIeKF>yrx0D`MoRtavu~hi}1o+03 z59Th=w1c;fF&VKTyVLvUxZyjww`mVJXX`SxLwvZ5xhABYuLyBgeOb`Iz5jICiJG+V z{$D`gR#DcrUIRB(UH|d5L^)NGe5bG&-!KB;$s}HxzHG{O#9|nx&fy@EV)tOFR&HHM zx>on=BNf>zJCN}KPp=~LVTH=tOg2x27DD93ga?(}q8m8}ABe;rRi_N|<;b!Sm>cz? zt#RE0U>Q9%V+m2!jC=}QUoH1p>Mdy>Rsvdv$G)lflak`E?@g~pUD5+Cb07%5dTD|t zdTa=6=$|OWV7Fs_#*scVxcCQps<`UQSI*}fUKMA;dgNQUQf@Rchmn!@OcZ8}0WO?1jEZOKIMCRc6wW zA~SJpWxTIjpsw7y-M?73Is7WjC$IR%qj^hoTZZQUE7)Pop`&8 z610HTnU+PPIN_XMOSq*Rv@aGLk(fcZHnwVw;vWM}7a~>?n5NflsA}J?29~T(s_j6N z5ch<$)6Mjz?UL?9=y$j!>T~|0)%JxBR<0MH3g3+2FzAHQrc5rcAO@EUdJ58CmeL6C?V8bh zH@NJVW7*%8X^+&GSilE6U%&WbC-b|&cEL)JbcVnV!1n6g2k*q328Mw*)L}SvsM#0y z3Q~tjhR!zcm6l50`oRtc=-^qLa$s4I%NZw0flA$cUo+X7=Ravn1i6fd%XB%Slyl5Q zRIE}u)aeMES*?)L*Vj`PqrY?f_+k7?ik*Z!SRG$DQvSAk`b2z6W@;;Khw-HnAdzf^z^tl z#9NG}Oy$AIBRq>)kiB~|^O?mgGh;cUG9A7XUtkA6Lzctf8f_jwI#!J;yoXV-)f^HU zB1t^fSW>E)#E9hOy?JXD&h?N)d|qfdg$yen~8Gk-midtv1kd?ahunswt2lEGWe1hj6EB< z7;!RSJP`18V)e=lyW@-Mg-;O;={0K1_z= zg;(9Q?%|NJO+#yH#pHQ)c)`uyNic!1NS5v|2%q0;*Y{esV*D7`0O6!&usWdQYjUh} zCFYmE`Uvb5$CxS)tOgj;OST#Dk)7&bxO!RiE~ zHJ<>K=rFv$KM17V^AV3(>j2zOq~dnpAtOX9fztEFg?t|kq(zx54}`6+hP*pWCbHY-Hpr3L)@SI*3kapxbe~`cmI8U%jQ|-6c=E- z>NO0jNd);lpN^tPpGK1Smql-3sSy3hsVdTL8!Z?mn`%wNkWHm{skR@+1<~WlV(-cYG|~6VFOQ<{>n*O@(3oNfd2_N$9PeeQ!JKloCQtC z7H$1O9HPlp#MEoc@JJKRu>pbn2yvC@>Bx;^iArW6$W(U4?1mwdGf_AKU5^SP@(qlC z=7x}jCX@jZ@)F{6UmhV=kmEXE^YK#S86pp5r(5CtF6%Gg3p7mey7~44@-QM3Vcc?Q z$Rhk~Vm`j+2<`(sXDvtI7^ST*1kc&zSyZ7oYif_B=JJM`8CJz`;mH)JHSKWCSD$Tk zhS>&x~35S=fe?V@?hFkjfTa=yQ*6J7JNAivCoygX z`3qM5&+6nusaCul1^5fFiH@!RWG!wn2s|})#LPbWCru5M=TrGmwShhSs)L(;c*b_& zb7~7=eSNJ93E6HBvU~kOp3XilyqV1quIQ`4EwnlA>LYqEKl0efFi= zkY(D%tjP@r3gC*9AT$C(&$#qJ@uqt3!x7=Ma%rX?-f8M&6!&OMz&&n09GFmm2&XYVJ_r2#j@cDclGLy$o%O<` zX5Hzk>lPYGK?ubBrdSROEx8ZjA!N1~SP~4bM6rj3mQ;W;=`)4(s<@CB5*fcjHi)T- zY{FgdQ-JhK;LOvJt0k$rPXFj>d8Lr;CGhzEF1C%(@dayNGp|%CPpPQwcjh{e~&Or31xr$w) zP6TdRB1))$Y53LV5pRxYhTZj)?8n(P=AUV0*h|O0jA;5*B&~nK(A+ED$$L7wnUOxM z4*+ksvhIMl@#sZR9N5-d1g(%<;3wjzEr!>zL%jSTZX2MRpt+y^E33hgf9=ImWB8qQ z<-n-fu9TIX`RW7U8ZtGAih^HYCnue`@F$p?2`%jJ($Y=>W;r)(uK?2|9kk(bvBKSm zO_n_w40egrrv*~qB78QsRJ+h!i6QpKUxu(O{_nw!p@7d^P5`xj2G?osjCL=$=;%jC ztkL9IORz}@BY{`ZM4R}aO{4U{*0Y4-)|-0gZW8@*aBr<8*GjlORG0Hw<@5-rLw?2T zRAjRbHdM8?TIdY6J&xAplFqp}di6!9Xu`Za!i$Q0{8oCn(dFM6^;IQVSnJad=G9*C zl?|t@7l+Xo#h1%_CB@%cWfzF|773q@)j{eQUc$>>Mpxnmzg&T1b>P!4X0@8aVxa?DJQ+ND2%>_<(gOh@X+^g+N6D$w+ zbgoXns7J~G7yVgX!AaF)J}Y)f+hMLdP1+2z{K`_GcJ<>Kk+M(;>--|La_zV0XAZ1^ z@tr9SZODy^IbSRIH$LS5lRFLS!?vnx#wQXA-y=^#Vk7`b7Pl$VU;e-z#2zMGW(;p> zWzo3v)=ikRlL&gM$XxU>O*;xyDoU+Roui$XQ)S8WzfJVFt6Nrgjn;1=0Nun4_Ej!c z*lTmH;Dj)FKe1(kNg!<-+(r*~w+W}7`&u57gp%E3?a&t5&wZ`sCS|Ng8PKkd$n8MO z2ukQlO7+Gge4|6H042Jjqpr<{Fykq-d3+w$SViE?N1`jDGRDmUnSL-e2~=r#y(7|o zJQMTX8>1vMX7zl#V3J#)y!fl}Fw<+#P=|+xEZ#*B9Con3Qxa}&U}L)F(<{}xbT6j+ z{xbJm)sVJ8vU2I5$o}hop+UhcpTK7;fSvis{KPO|o4=v7!PG;2?qYm5nK54>@p6i8 z8KC*eP-9NPBcc*zS5WmE6SHlsYkgp?`^uY098DG1Xc{{IjEYrMug^_pVdSe~HU_oZ zs(j{;pv)YJK8uDE>p_eVnYP<`Yz$hJO`1P(8x?(05)%cfW@Fj|(GTS)%|2zGE{n3M zOEW^ui&%M2CVo`LzSF&6-;mC#nQ!5{vb*3+O}cv;%NO3aU-#5Px%cLww=LZO@wh^K z(k4v=G7xE;&;V}EZyW*I=5z_Wmb0b&xDkPv@awM})Lk5l?039PoNNF?yv6Z1>9`>G zAzO;RKr4sJY47z}ZNfNLni9-|96kTSXMGxf#D3>MS&u#|^IiC_r^W*`tAw8GAE3i` zuwUjtyU8|5)QhvXTSvl9c239H;>vQ<$)tFy0H|{8mKn>P?9snuoqf+1I0k)eC!V_+px$Ty-u+o`e?4E z_0nY9mi$s(_@l9F5Wiob1z*%n?1K#Zk-y?C(QD7Z;^BX)`#Vi-SiK7{ngdC57}M=Dq~HJP3etBGXyaR&I72x-$)*V_mS z1xf)ByH^!t^gs?l2g;6-LBchsq8N2PL82TXMNx1(rQBGp`cB?qrgxb}pqJwOk7-dc zr)lMt(46+wGQ-5DNqzU(_mcb0C*D$`Ed5CK0Inx;Vf6S~zHN&>@ey*#Nl>$4DuYGF zD(l91G3p#Ym5P=@aenjY%!Clgn#0c9P!;Es-NW>^@5~WJ5kI`y5!~CBn3FY2HZYIE zs>yx$O9*^sRz~?fqd@PXR()&+&+0t=?UJF6X8fT zT5ooPdbFB}=|O8A<+E)_Dw5y}Le0Z)G-H&s9R6`8MTvjYeao*^j!aJ<%d;@_*8-=q zF(TeI!6IoIBrAFn^^3VD^yQwfP6zP_ytRMN@L$3^-TSFLXx82fSnHoaqVrM;OmLB~ z@=FdhOS;@wREB-RBo}g@a}4NPoZVS(6WSlS!d7}5JKn|H9mNb!Dn_m$Xu=Ka60$^~T# z5^^^lRsvSP`hJ#Qu~SIdSL^LT(7fPAuRoGs;z64yVz^J9JeC)FomL9M;(M?*UMkml z2kv4LSFLrfuOC**G((t#|`Pvb2)2C=V{2nU0rFpxaO zP|FIab@sct>JQXTFiDmm16{&lblJn2{95^Fq*kP$j$9^h&(=lRA6ly*I?ugH0x69Q z*RbmPa%@b_L~r;u?=sJJLVt-0lq-WQh%*rSL#ND+oCyeXK6ZV)%87$d(9mSA8AN7O zEvdo#0??uF5K|SVPC<4KK(1M0V_#jqQ{sZ;g|%0KBCzM(7&}+T6N8{a7IW)UF50`d z-2+&5t{m)A9buL`?A#`w0I9&P#Wr7M2b3%KNt&z(UxK&3OpOLzlYI*>!X{f1kXlO~ z&H%;U2JUFMw()9LYDEWe@j2u@5+Kj`!54E!*LUOP!VlX(3-CsqF96TqBTZc;kj6DO z$$HhV%-{-6IMR~8o*#1qs?%D~_$=wA!OQFs;y|i@d=h~+LLq=SN7znl_v(Jn07@B8QhmsL~ zGM);b&oC58dKsVSY+O9Pk4lOM;@!pq8V;woF&SD#DL{wTUmNnbG6bNNQ=@xNmvB0F#nnh%KkOx|Hg!Jw-|(;lf!)uA z{NhebNVJ{YXFfhBD~uT|ApeGk>IW;~)7D~ra^=7A6jP9R?nfjFGUrok01<%(m6o6F9Bt?SBotJ6i@tvur)aHkuhjuW{=B7-I`fX7p%&}puNSnhb*KxRJxsWkeN`)wyNd( zn^Het*bVl~FFew%v>&c}RQ3Io4118>NSX7ZZ^QyNYKX0Yd6c*f2VcKHaj9jrxm*hb zcsB>NlZj_gSopFXQB;{Ij0z5U(Gmu-AbMQn@+?qb;YaNu&qGl;ZU?~9+RSe7viR`e zr{p%zyYk6FG(9T6jS7@CqGybu)C7&-+xN zH=tXS{SLEdE_QR!uCr*#>T7=yOKKQ4PeGB(8IrO|Y1reHGHH?nk`3F-3|7L-ixioD zmo&g#+i0Zbk+zC{1%UC0#^s{WC%dG0?3zBqFRZr~sb(nv!PM8nZlz5XcSff{d+T_g zsA@-=e+LLfRLb@(p0>bHa_xc%klU-Dszmdf(c#fcEZ%=Bw6dvdWLRs&GmYvw&Q!XM?O^9Zd7IPETu1%O{7o2Hd zzxeLM?cb0N2rxT|tZ&Jbcnm3^g#0j8ZGB z$&a73@Z`&ve|DDq`IyJlYo8x^Pvy*rx;zjsO+7W1xTa^2dHyPqWG0fp1jnUkr73q( zGtF2i{W5RS7pSfqTFiTs^!e74!49#BCBcSY<|z-ML7CI1i!5&p#6sqouYFnZ2!+A2 z7_>IuWg=Qc7rOxeeby4viz^D)B~&5OCh*HMGsP z)H)IS^xh;}3JL-r5X7>mJ0zsoWFo;y_kmlpb#L}= zUjNp20XeIo5;Fu&XnLU^h|d<;7niG&JQWm!&{Nu?4b&olO7_l%JXZKr9gyex+!pGP zyq>k6D)&NCe2vcT71h7OF4@#)WZ3H~V2ZkBQ#f^214X#-DB(RNWV|YgM5+pxS$%#WaSow1YWBln)byt|g8UeegP%w| z7>o_Q%EiOo2fTrCV_=h>J`4L4c)p8)KejKdjJ*K>bLt0~R!w;JpiBFIbE|%c=Ib3_ z*C*JqglQK1BN5Ba&2u~n{pFXq7M2Ev|5=mqr$uWE-wyBV&6yCMzGX0;@LCku0Vm=9 zLXRGghbq*!eeIp56l3w(X9jIEJ;Ok$CmPEHU{H6rE}7%H2U|hO_d~Bl4u|R4jII3g zTC03xJKVBW&r0Dg(V?=ULL@UqoFc903+n3;-0GBC@jxiJ3E>&2mR`TWu8*-CY78E` z9m<49U7VIGW(uFbdjNPD9<^`AU#xFjTFFc;HhQ|rUw5>(I3BJRMCRg?x2>}qKi~44 z+u1nZWFKsIw!>ZUwUK}mWFz5z4YNykIUB*Ng1TAxpUsV*U|QZm-Z1~Oy~)m# zB}n=eY<@?kXmR`T*WUgoUY1R*KTSi$Y74&#JCXWOjKNDc^FnXIHNsmJ1 zpH!QoelvfC@An^T-XvMlre)9koeBS^%O&{B#&XV6jDflS_jQ6mMT-n9BMC9DO)GaG zT-)1A2(oRDyXgRa-j+%DvIwM0E(DmRqKH4RN7t&vU;0Dw_>*b>hwIC-JtOjb4p#$Z z+8L$Rnl6t4z5c>wed~ZY;1E3IeX!ONKb7D)4Nj%&9{dXazty$#Y<|YP#ye48hMI52QPwiPUb2hceMxf@oxM?Y5o% z(^r4QuK)3he;*n_<~HW4w*%}vYWa%mdbsio>O4xH07?6S2D}+^4aDiL!2F@|nuHVb zU)NE-2u78sCZ76_Lgb&(0|VLpnM^XrbBVA$Q0+Y1u946}82aa9SqUjzO&HZW)HIKpAib@96_|h=D{Cw?%IDEgnzq~AgPK#1y*Wz zI%=#b=<*mk(f$W$pc?z20+`4<6jls45i{Ldpd&oZ+?M|76d1E-E|=a5MtANLa{sx? zKQDgyerhi!)H-C;zB}}<69(~>vKo_d^r)vuk9EOrTXnO(1L%}E?*IRlh*u~FmaVNLJL4iw|F8T0-@C2fx5GL^cA8aX_bl4u zzZu5=a-RNozbm_c2@IU~%3b#VD+8yk?suXLJMl08NUr|-7ybYB4*zH1{tw6Se+KS< z2JU~g3I5Mg{Xg8@|7YO-XW;%9Bk+IyR83XEg+E%GYz{I$0KQmXL6_LE=j3O;5`D#p zhIgQi3RXWh`Co^8-y7N4&g3zo85giRnFP&Ie}HP^_Zm=u^Z2fwED8B(IqOTwdc4Z< zcbhbLabjI#>*rd(5F^)r?%IOYRdO5AH~o z8U*feO41JtI*lit{&n+MWmytbz1Nl#XxzH?47D~-hCyAHJHr3?@JDbbn@S6A9qTq2 z;R~Bm{2Q9fid>RCvi@8vpYqR}k=?i;d)#|x=lPqz4@rRd9p#8R0gJu0^uO>&Dg$Na zgClFgi86hUo+We8)zlHRU1;;VEsBFS`Wy=Hm;V;K5Vz9Qn`ELQxxr}42cCe*c-Z43 zP`}x8R4-sdB?<(zy z?rOd~>Kba~omD;aXW*XMT;zry%}+EoreyKgIq>Zji5j0k@ZW)2VOBY=!FndPf^WD96_qW&e`&Y)9^Sl6wY*xmY4_~oisc>OEG=*_JRlNQh z$FO=ckCze(%;M$Ahv>_Xly(=#TdAU9_Ahm_ZuS8I>4<3;NW9hHOP@BwH`AEtN~596 z>Ay-H!{9VnvCzp?w%g4bwJ@?^oRMVUOVdCT>~Dl<4M-#6eN)){xXIGWr96)}RewtP zn-%O@$&WZR72EU;w*_$oq*3s0KR;oyLI0PI40?gJvdj@LWt!jJ zy!lj)KXh^_GZ%#0L>ZR-X@B6m1nafVjq$lU|Fm#sigUAsN;U??=cy5@{Vm97IM!1P zV1bp_k4$#|{&`RVoTF>EGVE>$fKnNTCO?O{3ETd+Ml7(#T&O_2>lm!ON9tqd?H{07 zf44h~W$VU#Q&JJmGhs9IOPR0|6Wo7`jrxJC{8rd}akA-en27&$g zYP9e09=9OYzhE3%0+zD>1ClP`=E{{{9I!Fl;8~*d^)^cJMadHN*TVgQT z?t99g{O>?jU@VpSX2ZUcSxnxLZ3*Ec9zw>OQdVtp*l*s&Ie}8(#>h8o3p8Ig#RtC8*E@)csTLRzwjs`TxlHh$o-!@ z2SWtPFau0T$WIk1mb3tl&v%%u_wdn$U0)@8^v)OG)>Xs(f;h05M(T_Opxop+c3sH} z?Th!XyR%GhGWO`_;C#ax8cMDe1*2U446}}&WVGBs9wy`cX7>P7~-5=k{qYOcZ z+e~OO5h{H_ex7;keV5`NmtRgMR00&`eTQLQg0eSzMC7lN=u1TgCBxRhCco!7|RRznfvQWD^0B}?lHo0w(tb$Zob0@tS_vg*XleI+$7&Mvuy^eVgA*`)A;x}7?idp{gnmxf6 ze#7kfDqP#NgeKj+aSsnz2!23fP@kP;wX<#LG%y0L4M*wId1Q7+l&I0IStrJu)wE%9 zm>34cnIm)~-BEre+a~cO7>^|a`|LB8i4D@t>3ar0Bzdquz*!oA@kWEq?V7q{l6x@peVbgX-s*EN51r^ErEh2{<)ZLndzwQ-_V9 z2dwsS%uVe^Ke)?O75O&*hY0Zf_a37Iq1Iq!vB*SqH$IG$b+GUp9NjqS zL7W?4lO~G4PMq&L9W;SN+p5K^S6Zk2k-`m29JB|+8cpEpOOk3d3vc;;acqZ~nf$fQ zvV_Xq?fpS$?REyYzOBg$N%yoHXX*!4AsVb}a@(10+{q+bM( zUrvaa8Z0Lu^Tke?3u!5{d{)2X=EpfQpb|eIuNXeu+UcMV%K71+Mf91wz~<}P!YOVF zKmM-l1d~mJu=0zM=F`8=ll2s{JoOs=?DNx1=MLO|7sDyNzfLUtAXxS(>#2qbsrO~Q6al5$)C|YU^nO8r|8y_Q^ zINmOL37{OIlZO!H{Q(dbN}*FbsdLcW{xriViYi&OT{MfJ(8&A-71RF_a4S}W~^bBS4;kD^;$$lnz|E+iQhgLbvT=L1z zD18xBZljh_QPh1i921{AW~tP&v%j8?SmgN zo0R%@W4SK7PaTUK2yBZud3clvSf4;(tF2WyZ*P2s7J{+$-M-#wI_1+67SvVZC{!QkY4XX7Ha>UoJeZ1B@g=waFt$Jl}7_+ouP<07VvlZRykp9#a1Mq^1=7RA73iM*Ds{xg5OB z7)ZggJ~oC5$O=Y&+D0_*!^@$3L3G<(Ef@3`>cX?3kduG}hQm<|p!TWx0?8(t_Eki- z(`s$rhjs6Z>YL>uAbDUc#h||G#`8$|O>p}(AO#7;T#8wE)$N75eK+y8Vwt6m@~RuD z#ynKqCGSq++fI|InhwMGuwjhb|EC5v5HS`vzYV^DOGHKK3d5^6*TRii{Qpsh{TG!# zR{{l3s@6|7|GlpNue!^B7uf&PZ$^NOOrQCW(|`BT|Ibg~8rQAE{lES6J(j^}gwpR} z!0k82x&q6C}DtZx>;$ zh}89J%YBSe@WzOok!)fphlLV`cUY`$7oo}RZy8TXMFiF17Fxf>f&SlC_W!x`|H}t} zA6h4Z{>mS6S~go$y?xbyy*u9gozA)~^ET_)jdy}(i6RxSJSx{R4*RIV^S@6bB!3|M zS;KZ~5dZ;!Q2OM5S%@Fh=jOj1JX+O$VG9IblP*#(19WW<$nn3|>?{-dTQHwXEYbqiZ;DM01WhX5UN|vB9ki zT9xnz&3OZ*TFxYyp$oa4b^$GFCcmpZ4%NpuZnm7qUuYe;_sQdzmh=BM&Hn?2P}${3 zF@nH*TT8}ufcSF;p!R@Nelvys)JxC=6up9@;NaxKjk9o$>|aKn_EmsUepxaK`F7uz z*av%CA6;jVOTW8(ltg&%=Dlwz0s0R_H}5?rk&{2l4%<#u)f%~w*fQiW>EzYJgFpFW z)1kaGi_=%Db=!e}eL=yi??~TQWL4ay-{UU&?dEle_ZFLBV6BM3<2rD@Y{u0thue@hUWQ$c@)S6u>JnG>7^##=M#9CWF4MV!|(ML?TN z#H1Nv3{J+K-1%6Dcmj+D%=9J;&Hz!?nI_oP3wp=gtg^pE+kn&Fp<-0$z~$_J_j^h_ z*tfD-${SjE;O`1ByhM+99gdk3&$EhO6=wShUiErhQdRYmq1Vi|xp91^?7t00|F4$# zh0y=Org2fzwfHsUUM;T>_U#3@g~0&(8Og(QW6#5~pm~Q;^}T{l)g7}S6f%;lc92Lf zV6Ie9_pta1&YLL(`0yKN;pFoGlqn_Rb?P|w_0i{m)o%eE_WKwRm+@4+(ECJB#;s(#TdEtd~|CB?EZ*FbW z++}Dg?0Av3Ul%(0d8c7TXMEXt?9)ybUgyOBL?a%sI-bq&UOYOcu2A^;S?eF!75ojC z^B`^-+k0+MivIIgS@s}pF5fD!x;=)a7~C%VFfyACz> zkuKh2^jo#~hMg|@uRX@Ts^C}MXE=g98Iz{nXjoAivpwSFwJ{rtsWj?&Zo5zqtB#s; zZ$EmnrII{fmXBq3d&SISmWN$F`m=RC#Omv&(J1_b5URte-2Y!ZV1!caI~pc5c3Y)@ z_`43lZ4OqZgntuw9Wf2w+1HptkDdX1ztYXN-$`|y;ULP5sj3&F8H9bJm4BI_x~>m0 zVby@-U$?-U>N$-+oL~Q`Q{TO9z+>nLhjsLejm6+o)tiGy3iE*9G!za*nTg|kG!4eeQcH*U(;i@` z0$5}Es~%42p-{`%Txb>{I2zA2y!So?Z>LjBphdY*7w1y*t+N*nh}TtrdQDP>rJ~Ph(f>F{fqy$yfPHY<_r*BGi%a7pTPL@A}^N zPJ?eEES|FKjz!nm&7r~gnFw6q`M$$wUbm$afCJR(8hL!TuUSqg5D!ngYCQcNHUp<` zJUr2ioH1Q!4c-QfO|Rgr@diF;%jrZ(2Fd(pA#g6;nWt_u%fbM=$lg@0!&xwWqGM|K z07B05WJz7>=rNFKzUnUkS`GRG`kY%oOShA)GX5-$75~&yIm@}Ks3)@@3xR^#1bFm= zOCf{2iu0y3fV!;#niMllCr7YqprL_Fc@Cd30>aHSb5VW5Q#eg|A=AN=M&80LmDiY|rG)+Eje4 zd;ti&eR-ZbSb!Pr;0;HulujLVFGF}~1FD9ZBXi9UgVe1FC z%R71bzu}rMZ~^BUKoi0sIjyzvD#iy4?##&HOD!ox()U8qLtG9S^J@H*&g=o`876rhP60LI1#oVzjSIoS2dmgWerLCuaDepNW0G?-c1 zhQnG`dO?gNP&UiW1=r5dn1q1K_yl0BYxHa7Aq<0$QHGgdOZ&d+0aAb|s|s-2vD1G0 z)A;0SE^Z*8;beKS9E`&Ka;B-F%9Qqgol6gg?Bfr1YbRb6C}#ny()!b#sfY+zxi98s z07EkG4)u7Ml?G%ltT7o+Vv~>F&ggmF&roO`vGo)}DV!+`er;Y~zX0MA_b}&^($d7U~Mx%PN3_b>r!Js~6o=>G*Wi9Q>#q@26T5REY2NtP!XFM@fCqnoef5P)Bey0`H0R?fs zP3h5G70-WRz$VJ@Ggu5Pid2kql?zLCcvG?>#z~bu za@V1ToCQ2i0M-33XX!uhITt9>d9?qTOriXkA|Fx;*MHGhYlK~2H~^^BbqW?)%tQMD zsS{@i5Z8d;FNxZT5ywo9;Prbd>Pz8M5KV2&3O)fnr3TC#`D+i*1Dioarj>_iOJ^`q_gYSm3mxpH&_3ty$xlQa zV3WfOQaGRZQ@#`)(<+kp2H&rY$!)Y`33+9svs#O*chDplWwBM@C0CZ*cWP2=z<2OT z)vVTar=rq8;D`QdZ{sT+__+6ruBd?qz^8r1O^l@p0mo~x&Bs7+ z82;--?f`t?y_@tT-ru-;b69JsmuD4~HH?P;+5IOW-*3}K9yJD@!hK1@X3C0qZJ5Wq%-4O;NJRzqF8KEcD z-8Aur->L7IY0$1x^^ft%q%AMIRGAlY6y(~y3S?fM`lq0Sbu=dfSkxonid6OKh8qPs zaWuwdd0%P39Bl99*mIHM?-x_!)tfuFTmT6`3WzP^o^65wAXeWHFR06nuCle&@57-> zsXYWlYD!)-_kushDK2(IIKfl8zk_yg!Yv>&@VWi`zc`Y?8$}gOIq=e{gVO4Bo?lF5 z1KII(cOjXY?NeU}wZq!ye8@_Y8GO=x-O7KIJD*AdUX_F@LCd1;0aN|LUC_<*Cm~F_ zI8@sn(J!)yuukTst7OT_d-SXEn;o~!Bl{+&gDAniKa)qo6dJ)XLsv_u9IdGW$_4xh? z?9pr&i8DB;PVnobGP#0A!Zm+Dy$CA6`aa=c>GeiIqW0$r5uuGC5Zp{{&e%;}SG;-^ zqOaY?@o-EiAR~75kc^1c7F8jdSn0YxPo$ ziq~#Z#D!DlMcPPI%pF5;7x=`a3;oHoPvd6PR6&aW1TC}}cs_m%SJE+f5k&O8(8l}A z0-vB7*ZDCVt)41m6BGNfq6espt(6g3+$p)uWTD?MlQvCDm88&Z$I7K2zuNLRSg8SA z7Of&BfF;oqH7a=P!S(z4kxwe*5VO!F2CUoocT3)6+eyR<*ZmJ+UG+Ayt%yp{~}HGfT_!LCg(-&UvM<+G-zIJ!msDgE@`4KKh(YGjvI}VKK}xmg>^fg?q93se5T+G z6zWI|KfgY@di0v8KRX4OQD%T9PTRWv2IyQJmIW9Bw90h~xHV47O1A*m$pOv* z1doRS(?}*nu`JJf0o%As+?X29K>(ay#fw#VTn*R2v0wYX3zSg4OC9}uWaN=s3)d(i z@_+!a%QhU!vD4I1D4hpOX}CX@xaa`@Oet{H0&kYGbAFJ2f9@3nya`J36B$63XB%j2 zK|~v-&7DV2L-1(V0SCzzoX;tThPx6zE3aNw^kwY@bQy%0M<>b~J<$yEW`i^b5 z<2|aaE5>saxjCAb=*zne^5<=Xx$}gPe7cusha(yd^&hSvr!Dx?05-BSHxYC2vmd~u zR>1(eq}#Y@s2FO4&7=)!1utcHPY@=tAqYzB1Xl$bXW_HD*Fd47Hk9sl*Po|69u^>4 zJlW}l)6iN;h%=n2Eyjn7*iQ;oSr0LZxbK?4TCQN@68MhF@7A}-^`8nT5k#Y6B4NLy z0HCq}rN}!+WzwEkdj2WxXv zwhW$y>lm~M!d2o1zUtAsgWGiX#G%y0f~tB3Xv1x6C@<#x!f@yR@o_-l2lqBWsF%+q zPqDyqr88(f>HbJao&sr}g)C1qRQ4ZTZ3|(N$TmlDHhJ;iUmcXk#>a4mT6q=Lth|C( z$(r!0J?qF{wD@7ZVZJQ}El zni*y(K#Dex6aIu2u@ua);aqT(#^CiaBS;xMEpn@8Rd}uwLR%Co zH$;A@Xwp6Y-L1oB*H7-dGl_f$i)~p4t(>d@BLfOp`I=^zGF3u^&U=C3WF zb{LT}tH0HHH`E(T0$2LMcz&}JJo*#Q&9@yI1*un0=Bw$KooB1f{YBVy;+MtwY73Q0 zQ*iu(?_5dXvnqKJI5-pRq<{_c03Ko-h``c(?-tjYtS(Y2$KH{4aGBTY5VrLGD!238 zVuGxGcgF0yoY$sm%(=N;#kl<*ZTm{!9hu%ES0J0GN?jjsHB~BXRhMysdu)H$aZ0jp zXd<}!l$?#P}KNKiH^u1NGrf7I(*J`U~Rd(39T#2@l#omj4dq|EwwrlCh}DyVQ^Ir zF19x6-5<)tD}r!sJP1x^h%WOAdMNB^N^{%WmU(?{s-G#BTZzjOj+{Q^y)RCmswVNZ z^hqA{;?hg6m?@{9t_^)`D576YnUAtOpk6U>Ow;VSzUKHyDk)%>Dt*F+)W>Z0y3F`% z0UHK7BL=%Oj#@+33i40onR*Uu6$#|7wH~-%rPWFvT-c4lVUTNS`9=p28JX0Ama1}l z%@xY4mPmt|s`GKQSiH`0qN;Q+dxKHFFZm(kIg%TD?fJl8f zYG4JlbmgdmG}?>|Y^tx%0G!unmA_b~FLHHaKb(L?Ayait@Bu#`Q!7>YK1%gVsWB=t z9lA)pOUCRniaCi0{09PE%*ZYrqH(E@#0Ge=-g3)B-3z3#;pZ;o4$@V-FNV9NR>X&8 zaIMf2gp<}aaqFkEnsr9ntKQ#|#8E^EUEICzhaIV|+~3jO+oA1_6?*_LHobF<^UrFw z{P0}1x&CRVG@FeFOFsTJGI}6-5E6PIa<-@y6CE*IeZDI7K6ZbbbsPOVx>Nl%3ZpnV zO(Rmez~Oh-!PB_gJ@l98Y5e!ub})}t-h-6<2YR+?oS=UvWhl!;t3%zEWoSJi%5opb zF?NV?+heF41-yvl?w}dOFfPSM`?h5-i0m@Nf?>m7d+3lxfbnl29EzL}=Ke?-%6ov* zzRo$N)AKv|w^%!r7R!Dy$^$JA?U^%P@La={Pqi^cIiE>tma6=_%WZ39i(J%X9ghSs z)Z#-Q7xGMuB!h5;lEdmD3DILlLL}KNACy_&?QO(hpXY_FGmi!PrA&;u8a2^fymzBQ zslJaSsG~*mhwK%$c_8@&@^jGG%1Q?y<18|a1qH|iKxhm!pD!Y0kW^!|RIhQ%me^8u z@)1Ofa;R04wV|bTqd2t9;fhSpdpt;p>?ka;e@cT@xC_8*zJuez?;`*(5YDwUCa*tZ z7Z$FZR`e2`ghdt#_nd=2FiiN^^>7#`@LbVx=EApnPljof^9Onhl0WljKATna=p9pH zBEkMuxzTD*YZ0`(M>&JHC?)GC)mm*|OX*C4GRcnWNqvsK61>K&B-&<3ZuAQW+c66- z2Brxai$Ne{C#2zhhgF^R2vK(%6R$_!U3=)JX?$q-3v~$w1PZg_aNbUtK;!mNuez$zpPN?Ya zspU?G8Grgw1FkpiZryCP>FGKrdqv4U>Q8%|ddEi(nJV=(rfO@AU=LZK#WD;w3QzvG z%pLW;zRHFg956HS;nRN{7u5gWS%7EQGuhFcjn|O3Kf)8qmFuK{0+{yJ~e-Fd=3Kh6C)}0L5`g-K8Psob*c8DeQX=)^^E$xdw(a zGLl?8EXUOND4o=3t~Vs%c(%N9s|j`;c$rO^dDhmbfV2S^I(vD2o{a?=*gXMU#Ty87 z%(G3W`+SXrlKrj3@~Ei{l_KuZn6A9DEvHXSVLimt$7PvUb_8Sm5|r1pr#}eRGUK8@ zmOoG9we3`?te9}Sgbg9LhVC&lec@A^4-WSXk2T%Z(^r@EBU!$uqGe~sV<;U(Qem;e z8SC^$hG8vY4j1tu3UvpHH>-Wf;sjP`TIi0RV2j9ra|Qo(qKo(GR8gzj=~DtpGAwDC z%lDgpXUL*Kdw15lx1=Xr*4os#F$NpUcrGq%NuzM4at9jTHb-MKl$j*w2tJc|LGNOA zn9Z|*UG&u6q?nx;n^-*H{To*`tbVCzJe-I5hklG)&c8ohfl#7K_uae+PECtUDwOUG z3FSM!=Ovli{4s>(=8Gls{7e=$BO;A^xR5=#W^{d<^^-Uu`(SSVF9ebuVWe#|OM$K* zxMg4ZX$1@CVDj3tC1E^lynn|DqWNT=!1MgiXHRxJ5@N4NOkR&Tx%*48Ln!&t2JB+O zGViK8Im%B}%bkp55M>`r+b@XgOzMHm{_^UXX7&r5{QMCAXLqAaH1AIY4YHx3>7k@og{i-9N@- zTLJ`J#j7mxI?Lr3xT_2Xv`A4c$;tB!9ZGR5;rCE@>;bo22Gn?Bk<)pBe zRw+X10wc;nmOBJw7&Fx`7cYZEdvirWxNpE;Q?*M(f@~g^-H^ZJ-?|3CeJ5MNZq4>x zP!g>AH_dFPs9aJdT9gx(6t*o$s1n5HX+4y-5p^WX1lsO6)gK?rQCuu=a*(dk+q3ZD z(O}jxQp!B^m(yYkVROGT9g%halvF=*J|V8}4p+9BWC+J@u-OMgxtH%r;_Myef)2v4 zPDreTwsEJ)+V1v17vnjk^lE~krRA%+z};Tpuv}<;Dwsyr*=i%iQ@j_hE*W|mg6U@- z*(`y57soBwsuM-}N0|ZwJ7q!A2x!eoUjMB1ansJQAc^B};j0%^T=4krL8RE=xn0u< z(V&>`&I!skU_uFkUSX(uoe_6haGi}D;JD_Nn7O?8%7w$AQu%57d_SSn6ZhKB32!m& z&r4NBG%H4g@V)Re5&zn?U`L%0;*xV_ar%B!$p`D@-0tCS`#{ZdO|ZRXh9Z-Xia*oJ zC+a#>AU5DV<}7Mvz-PX>PC^v*kVqs&1f&MF#Mt`AiIY+qEN_Zxe%F>gc#pB^71ttO zEhP>$$I-$k^WSWXS<3JEl@}wka|`}C#X|w4HAP4B^ylBcUf#*EQ%>>!h#~nwe~{#y zZbda)uT?srM2Tixb)AD*AH5cV22)n1sg*uP^+9VI0iIlGtLD7^WlNZnWYW(W$Gb94 zqAFly%9Tg-8L#YTLUFpFRW``tysD>Te!69fjh8GNY830kVYi#;S{~)R`&t{tH)gYi z5@VZ>KAvezM1mZ`bfDWp=l^jZaMkRH;UAMYPo93uN_`POZx!UkBeS#iquVpUdw@))_queS`qgwKIDLdT!EBDk_rJno0wF!nxfJe;pS2NO(7}NFm%?+w| zaCPhf@ea`^svz{e<63Vmm%7>1{87qUru0i8)MpKC3{~JvnJ@Uul`$R@w zdE#)dgfnDh$}t04!>|KkEFz?K)z(d^O*0z}8h65e?15mv`8Tz5J{M=&LYK<1*TEKi z)&xP{5l|U_v(ivaTJxfWZw`r;e()<6e&S*GGV22lTN^j$3nYK$0P52FmP&E=Rjm&& zz*X!QN9dwPpiSY8+p_xVl4a{vsmw6VJpc2_#@%y=X7pjdEQ(f{ag;WW z0d!=Mcf4pOsL_<-lUVTZ^*08^DjyyZB(K7=z`<4}e$r9NlBiz~GpgCIUC%Ed;3cll zuqt0Wfl@mK{tMGrFJxpy4FBo~VVgF8UV^~C-uf_=RD0otu$bisTsC>p z``UD7ix5L})KtuqH;^C`$^Jm>p-LvC&X%E6Wv?XrP)~JBhH7dwXuxaDB*Na{;>?RE zGYVq&Q!}mnEpuHB@t^Di5#Fm}fd_k%q3TDHq0=hc^aDIHQ8rlLx$%sbDU~X#9vGYz zm`n#7IPosHvY9{l&Y-l967chMCV0Rx z9*LY^Lt^Ws=3pE1;9iznNlBuUqtfs6J_?M?W_=EtopGy<&p@v9H3GhWS+wMvJ(3K6 z#8f&PnGW-W+_R~SdnFj^@azQiqP{%l!aTMHo&y-#5t`S1-tl@y6M z*5M=3^Q4#DJ4rb&JKOSnZ=zas41(#P@g6g;5J3WHM;d7;qTL<-g(ui_ZH(kI2pz9z z+#L&>e+3agNcj0sA>XSyR!qz!vBf4vdNNJ8Tdf$KP%>l&(-SQ+X04+d&x-OKsfpnY zb|EoVKWiE?tmTiN2d|TIHPIEaiZk&Vceqo~7(1j*u-Nn=`)iVzbibn8q68GeU?R+3 zCgbu!L#L|ZQ>1WKU?_ePAJ8&q^m~`(c#0ryiDWq(Q#?^&Q8{jm@mmoh=ZEGa#pX!t z%*gUb&>M3r&!Bjepjx(-j<}l9m2Xqud{gm6o#0_cGilG44;QT+vW`6<2wK&Zs$2UI zhBiLY{3b{VjC}Z4;c6Nakza;c^CCr_))GudHG7u~Wk<=8Tf}g;9b4J|c&0mw&y}a< z5%nI!8_bIDN$a@cNuZaPAUPldY)MD`A-gs zpVrifY%4phEiAC+Cgdsl0NQW_5#mFiUHXGPsIS6&Z`>n1JT>c4QRDBCR#zOQ7Bno~ zEMAn;&k)U5cmw+R4F8m2v2zZ0Fs-gsSdf8Wm-3{9@Bk+u_K!~6D~vZ5+krv;t_xx| znR|1;-GVhWtjE;r*eaVg>jF_05}+Ap54#qICiYXI?7d#^nmvDGyF(auDNwwNFt?%# z1`U@_#+2!7u7)c;36ttQQ-7r-$OuJ$_>nX=K?R(xmeqtuj{s6+))Jy5k zBzfP3*0O{W6tX&$Nr%=i`w);!W`L!~~f076;NyP<& zSF@n4ev0%lKjbDoRw%+{V!N$V{N%xxtjf&VX)!@a>v`pRk zeO^cF72o3ymaw+5E1WnRE;NZ4Q3mrtA;r34-pj(XD<;uC*7#W0yId_n9WqnKW0i$g z$u(MbjqQ>lVrTpz+?Ja(l;=dl2jgB0`WC)ri2p7nJWD)xh!- z@WS%LB8n-dvMK#|IaxzubbBVLd$Eal0QB-USEJU(;a!4EA)=k>bS_z%ot_Qx#6h_SY4#wL|QM}=-X?(nO_Ow zlL$qv?CsZ%(ky&Pp~f99H25zcM2OMp7SLY=PAC?42ep{#2p>}hJa0vymCzX@+irbM z$zP&vGt^f6z}Dz1+@V=YbKAHIi}JlK96_0(ut$SzKIFd~^#5+>XJgTEocO(eGr;1i z_?bOtEk1Sfgk_s;OM6T}+xxb&kaR0)qx`J*IM6S@7j;Mzzg3ph9u|f?8sce^%lMiz zz7u_=T<5$${cUbYq%#BiuoNYZX?$80(s%N$`ccSz3}>#t#_jwe{hzBQkQ}&>-Wa&F z7+KFd@9!zi{xsTs%^!QIM|cQ1hvAm2{* zr#Vx?5RsF65pcNdi5EH=pPm6B$>SZp7>3{$GgmxJT<+)<`0VKEgU%e%MX$O|cT?Ya zmKAc61Nz^F2lN4%LDx*$qRQhTMrU?1rk9PFmJhI`FT>{~sZVE@NmsZ5C)Gz!&>WG{ zQ1+}mNYGuGF>Tan=g8?pJe?tSd^3LLF=f6A59?ACpU{_YsiTA#B2cP?GV`-9xXv)$ zgmoF3nEs1us&Ae|iEXy`t4&$qDOcJRrdzRubS*nNmM>NY^L-COYzq$;9Z88{@VL9R z>aJgM?BrdFufyh2Hf@&@#AUX?60fLv$Vh=uro&O9ilpCS@3GG1sm`@0b7u1J*L{<+ zp9MFUVGpxOTAQfSSxk?yjf;UnPvT*BJj#3i_bek!6R%~}{Y&1Eejgt&7a}{AH^B;M zi$ra>pndDxp_t@FghEeDlQPMfaK);_9;t-!AX!t{;ffU_wYgfTg}~adL^b*~h@QOV z-hP)-#g2Pm>zi?9{y~K}tt32p8%_0B z?DvHYFSMRYQh5$6$#x`y81MPIJutv>we`X`Ed4hv=127Bllo(2s<~cq?SMPZL5=4T zKL|3G*E6eK`~}eSJ?a@ zt5Y#}CSEU%^MD!Ij1qGysa`rlZhnx?h@Dp>vF!&Gg$D+AZRn>KLQn zOb7$Njxl>zcTi2K#qSEzp3NkC%$(LC;yMhxA+j8c&WY03weiH;RRb<@rWV>0A3iei zW96v~t|ZNC2Jx-p9*Ojx=|4qboag2o&vA^-*^CgLFA6wYeS_K$$eg-T0_@c3AZz*2!?wP&lUvH1eSg_tLaErm~g z^h_npGW%MDJ;E=Zy=8q_AEiv8c?NRh@9N#t;3A{S@hB z5Bzh>ob5T&Qf2+O6lyQRY4I+qm9?h}XzYWbB20fRi+$1>ELnUg#5`SlPT#`b`cx?C z1(%Fbh+3)l=|V9UVRxa(to!1UDNJhMqVP*Z?MZ9WkWN7_t^gMku+Z@ZJ0nPzD@6Zf`6)$?V@ z6llskf-2DI+1z>4)&cKm*-S(M>O7%ja>o@lJ39Sf#P7Dy!npf?^nH9=EQX>iW@#_C zmGRz1Pc!8HSfOx2PkpoysL*Uch&XbmsY!jmi|OiTO}dQ9uK4?Oo6zU>%t#C0%rdVw ztv=pcy~kvV!xGDsjHe%S0O+1w>uDya&XjaaT8wRCRVC(VUToIc^8@L6tx6oOFrG+g zG+DTHeO3X!hYpUJBXfYX8bxmlMK2}7KF8~3Lepm4#BjA=rpUbPcE%=!Z?NpwnUu6o z8=8WBx4Jp1`8KS8g-m7D&vvWJuXCUNxc(+-nWy~Yby+LVG^SM^=p(L5$Hqj!T+F-ic5L!_X%zn? z;4m0~dAS+5%5u%!0o}Fx4ikag60h^8Eibq)+$TLG^QJYnx$MKzGmp4`oq-}g-cv&rXP|~ID5cSyl$`KEo~4=hXO^q!qdi%9y<$hS(aRLZ z9rN7t+sAOd^n!6K%FCDKt!QSoRB7S!cH>@-0SNfcVirO3{HHXMq4Ay15N#}aM(_R0 zj~GBr3}^)uy_)q{#r=kHg`@s$&A71oH`WgKTOPZjhGQychY8x1fk3>k$vg;=iB{S_ z1?;;&c4klK2)>xDeYf7&Yx%RcA8>${ospWGb@LR2Te^O;tQOfYqug9SZhQW#qkPfh zG9z4q{fAP&OibsQ(NB1tTy;nB%EHdfW$o$Ly71!PYEKwYmifn^ZidHhNmXhdnSV52 z7?PgU+mCpFb^Z)RxX!ZBUCSl~$64Oa+O%lMWueVKtLht*$E@2zU7`NdQ<SkraI*v6+(Tg2&IWup76pGX($&ssEf^(AKET&18wUTE%w?qwDH6^IL0mf))^ z{r&cUdZUlBW+o?!8HxSOqWaYQBCp-^X-$}6i@304yN_53_HCTiymKHxx^^0 zY<=wCph1$m>lgkOw}T>Fpt4rBZlS8{B41gDYpNY(jKwCW?8>8(Bj0hIwdbBnIKzZk zg7+Mbc_pNV)iYcSJ-AczU9u2YVE#LsR&P--w&wlVx2)R^ei6&4^#yT@P~3m{e1O?J zOt@u2Dr$Z(KGbBH^GE+5A!*R9uN|mu-mj!c07{pXuu$Z?O;6FTK{34W{le5_!A;Q- zN5O<+mmWu7wda)C1V@otAaZ_5m2VIzT>jFFOn-R=njeSId(=NL^(~$IZld z>}9q%Px(A;xf*28)7D*M3`W@sCE&wjVBGYNuIy6s3O*w>M41SqQt5}n&-@7SyTH7K zkzzHZdc7t0U`5v_d+l!1OPS{^%+HVGN29cKIm$ojqR4fE?%*#WTRT+^Sv12AeH<@Q zLH@*5e1DCS2k;4*%x@F})YCd-Kkm@a zzh&1_VQ0jAO;8Ni6O)X3hNt|BbY-#6E>$$k5VXBFekG?H_ieeVfeX z{!YD=!gjF}=_&E1;<>w%OqoAStWMHje>*iLwXv!j;8|SMLBE?lTa*v4r&e(PvdH*U z>SFO!SK);r`nJCPFhAp845+`9j=Qd>Tli3v*G*8&<-f3)bNb=v`Zb;Bwd}kglURkq(eRwuSHf0rZqi%Q}YiFXt)lxi&rD}M|>o7+`6{H z&KE}aE;dM_%CBvw8ZdBb5Cmu-m<(nyW4&F&-=-{yd-LP-o@k3KKdH2)(cH2yESJ_X zZe}Dh^>8d*8vxA%X+ahR=(Xc)2SY*}T$06tbVP@v>_E(6XrnTUXK0rr?@jJ%TKOk6 zv9VI-J#Jm5U&p$+v7nK1D>4%EdjYPJ(KDPld)rel$EY$A{tlN^P6J5>o>TJ53U2n*WYM*( zKrg-x;5~o2`{-X$SZuvlr2C`$2Qf^&Pt5=!{T&I?)4*nuHfae4zsHKq&M@*NKy>^qE-mQ>-kEb$ zcSrV(`z!>L3*)Y-7i9IJ+g;vo3YO*#qo)jI;1lH`e)Z(w-gXY-$E%wI$b~V!ZdOiS z*i6I0xpqXjDGa8iUYU(LAHNU6XIzt1DUBR^sGu_=A33BO(A*jn=}}~bDsqUM@6&&@ z%W*ybco!$_j^6UU+^S;n)_AC62ZNk|>%F(PU1}dWzq3QlBN(F$C89ZoFrVms+GpJe z%|}JPSGFq;@NBL{UCKX_T09=|PJWu3>>cF#IUU)z?Syr!`e?#g^|*m{3XJqj4)vG1 z#2vlNLr&D((fuy`>&5G_(i4Fl7ng;MD(Q4~l*zZvnk$g4cCi;v#|KoEn9L1(j$K~a zUIq&{LrNzTIy72OIK!mO&z`47DJDSFXWW09cA62A63JOA+r5ke$^;`V{2AWI`X_)z z>2*5o@%_uR_j*X{rD-gA_FLkW6PBs>)Q)MTd4JuFdB#)mQ%l+pM`~Hez zaUY!scDL#B6}%^X-moUF{AQA~WHs`9VOzhcAbQGbBH7Fvb1#4Yf;cKXJI@<_nYFy- zP*3AE<2`bfBw9J0==UE!|BgjNkxYQbhYc-V^r*}i4JpHK{gFz_^h}nIEKh;844J#6 zooLo$A3mB+*luJ0#$qX(F5K`wjgu5!UB2vlHX92+e@dY!@pX=qh8^!0nuL~iOVCn$ zSAi?$Xr8`Zw31>A6LJGP{yJ_aTS_4y4A9Z@!`4zK?q%`RuK#@~%_;H-TzFVu%A z=LJBZhR?1=-*nc9VKO%U#CTld1oauL;R7g?#9!X`ZuYvXAW+7ha)a`)by4XnTOHah zQOnEL^H|bqWaIlihhyts13NX*3}YcAYT+mOEA3KnMrcW2u2>xZ4P~EbHaPGFLbB)p zXCBcIZFYLYOr965f6Nd-8kR2zvT!4d2`b!B52P63aJVqUuKJ9-`Xaw(KHejeq{qWkJgLzdxTnjCd zUd~N!pi@jy$mXQ~!bLJUj4kU&ZiegRh}7`Rt3_vDbtF~~(zG96BzjFivS>ciCWFLI zDbSW3_6N0O&#$tTuoTCvgKNSMtu)&ANPKc=$>jve{P#ZafXo!Qj~H~VF&&zrR` zU$}T`Hxh6Jz|Wn$No z++Ak3#-VpSjEBRss^nMq;$@=FM>4N}0*PxQ6EN@2H4;8qh?yzj1NiP$Vxup}kJ_*| zzAm1y(ZZ*QY3p~q?ph5!%M2SpL%?~%=bbPacPlpf3j z53L*obRxXj9mZS!VSHT*dpEqa_Av?%|DN=LmK4C^P|d~C=ZC}bM5A5so@y>#*=AzB z$p{+5xlPO_fU=hKAPoVLclqp)XSi?07(-Vlt-@bpVATmsa2BLV8f3gpau$@P(1q*w zDc-*q5Ws_T9CoC5@wb8?M~k>f(;*}79|~5W#ZGS&aV+FM6exwh}3#1tkWAt2o;9SV~!r3Dn3fG8cJq;z+8cd3Xs#L*=ZtaoZ|^^4I9_<)r|##vuMl_iQc~q_E8wu+NDp@qnKqvNT)C)= zMp=}oO zNO_-V897uA!C^4ZHTSK!#6f3_i)g#;i2rDy_3HRcYoz2%28HteDlLoIqqy3fQ@dHI zyF+o9R?2c;qQZ%;aC* z%TiPdOPZK6SxL7%@;3s(miaSan7vJutXW{znFdVbyfgy#P+j1fd~WO{TTH+OSZ04n zU3Sp4PyN=K*=xDKCkr+ABGX~|Rn#{d9EuW~8tGZKz~K!F*=jVeYm_H&{2Pe)hvV-IPiX5r76pJR>t<7aIsIHT>oBn7 z_Y`UzdVYusb!i0EozO_pe%@{@Drv52^0qY9c~K}K{Z?6tC(WR>=5XNRSqp)n3;^kCs`qVLq?hMWw1utSu@st=^{hV8`b#n6nC=|N8ut?cyZi{twrW zK~ z=C!;_E7LIV3F9ZJM6vhO6*Wjco=a@2&NeejKezlFyH6A>(u_mirpDK^-v@eBg1Z1BgmFq^zL4>oV_d>H7H|xhRbuG3isH5)_i-6AWz? z+8sId3nYwbQlMsptS$*v%XBDEEduyu0(Ii(dy)7kY7D%_BSQ{b4%1sOK z0^VDjC+WIZc*A|B5#Ox5bd7^nonJ=_zl2rx2B~F3V`|-_ODbLh8X4%?@RNdZ_)K_? zjm<)np%K#76QZ*g3g(*ts)3mrjGz*)Rp%Sxr9`Ty6K$C=Uh$=Ol98ju?77d(6lxP|^uFAt;$_68C`Pgw8UdJ;Zw)aIYj z3K*Bc3D&A^#rjf0J+JCUZd9&R?A=q-eHtY|!*1pFSk0PdyWp5^z)`>636!VNGW%v% zAZkq05=#qDm~g~On9XVy=kpiKzn1nL$dEfEl=8+UH~3!feYr~OUTxDUL*!>dOZa1$ zZ@XmPHulM4b54qfyIA{XJnhMDOs9kVr5`T`c|;H|9Z7q(nR-f~EoGNEI=*9TvPy+z`U1h zrVhoSFY{0i;OV)I6p^x7NxYe&pPWe1t5}xyc4^5Vg^W6L5IJ$XC^0!vuORXmyWRAr zz2&8j)kLD3F$fYo3}197IJrp6y+3_tbK0&I&xd3v+N48b;C#W2Ex|@)s9rdlL{HM( z$M<4@*;Mz1p#uaw-({k)!5eX}P$Fs{ zkgj;PHnW^+*b=XtK`tPxV}8x@amvEoBakAf7*s|%z!1tIrupoRDBbQ2mL(~LyFY*n zzw?Wdk15P&Ov7_#54zUKIExeb)T3ph^mdL3Ut0A%60`>mNXbQtSZ1yH$`am4vz}c%8b*5;Leau8q!EPmUEF2W z0Bz3?`wq-;2@&YC z;297;t!m06Xi#MPD<4$WHj1Jedl4l9@fQj=#s4mpF7IMG=Z!-crvz5k;)`Mx zIRXPkP3uXz)6(qO1IxWhi{6W#qR9&YqUj^4uosRDB0<@_-ed0W63$tzmC!e z`Yv(A?i2?<8QbPY#-5;i_Y!sAw8a`}21(l&RbdV(XKp}*LB@TOIJWMA#ZjW7pN?%W zi5__F^ON3Ner+4DwAS2jOOUU2a{6Z;H9d6syzn&HGW}GEuHE~GWVc{!dHws)Y`bOP-sOIeP?yB<6n!U6)G(8C|f z{DI6^4MYd@Fd-xI#J^QHYvd@>AlW?0c|`egknaxmx#p-WQFSZ<)}rIf!&pA=pQ@J> zr<5B!Zvzz-10~HsYWVOIbUaByWyGlA7?w2~jD9J$^Eob((FVB2T&GsnJ`1z6j=a+T z=H1?iPh#z56p(%0KsDg`fdN>{*}Y;GhOa%>=F1})fWW|+g{9JL#{PDKjcIFDvhzi_ z%{id86h+_Xd8DmPUn^$+-h_Hxr@82->X`L#una4^>Q+|+fqn_OhT4{vc0uhlGB=u}niwTlX^OH<`$ zck2L#m(t|@g!>8Nh?$h64_QHH&~1g@&{*#}er&0Yud%TzdKDGv>yf7uKi-dF@ZeOw z$%Z5^uII8L!)z+LZ$@`N1xU8g@lGcpVOV_mF@}E3N3Ar%wEJmYhvzliCzP^o=ju?Z zdrH+dICGuCA!&}14jAXda)y_nr{uF7&lqz0gwCIl(plDs7?1#hkhAI)d2brlm#>8_ zJx|FaY8OZ&S0TGb5J*Q5i%shk=Sx||&BEsx1-EbufD)rAKGMo-? zSSE1`?Xv<`LF#ky7Lt|WeV`x%BQ&N77H$VbDLKWOzG@66cMrb9qQ+ppagS-l1vFos zx7Xtokl$FxJgbkzw{Du<2C%#WyqAAQ7*~{0qMLJQ@(-cxXa_K5wEdd23DpbcEP#a;fUsjMuQQI^~5g^pQOh%NyrRK4L9OCj1iqnP4h&4N`X?C zvQwF=H=EmBxpH>WwQ_^M-GW9@w2NNutwMm=G^5$O5D@{Fd9hpT*M02;-C{(;#t1NW zbRJt3JWI@QfbxFmFa`b>^xJ9o?TPhx7NsM38{QEL%Y_FsLGI!CADBbvUbF`z+Faol zo$iA{E&BHPo2s^pz7%@*Gt9dy_A6`bjS`sS(6KB_;_R|V36_}tHyqD8Yiy0jx` z%i304t;$>NSk%@Cce)tlxz7o0(69p#2iq^Vefsdb98xg4;Sm>}yPE8&nCn*CW>;SZ zaq4i#QHeuIJ*XgW^_^@)b_*1#gImv#+q31@;7(&hEze91v+3Dd_Uc~8XoCNdz4JoH zH-tKV4xcwzHvE`$sgyEdR2IRHE~4^FS;;mKllYVjqZk<|z3bCUJY9#?KGA#=7D+M= zD(CgHP<4zfibjfB`T1}I0$NSAy(ncWSCc-g+&>VElQ;&fX}alKKxgGNerg(sqLFAd zY6*&=rL8?dy zp0X)l``h_LXc*QhE^@UZ(&_*c)?>)ZF8r$x0=CV2dAS>gE`&-+N=CXu#%i%8Zox5F z)I?H@lV6a5S_s0xIdrMOSf!M*U{*Ayb|zV~wVFk97EBi7J4dfR^pj^EmTfHoSfct` zE7?Ha!rIkIXD!qkm0Wgc4l~}j1Rj6hZ4T5Di{VJMU2Me~vwM@b`05ZCxk~9T62x_7p&Lx;ng@C)i?^68y{x<+yv;TNAbn^9r~yij!Ku@E?3 z1g;V`0S7)+@e0IUgfx3t?f)%iXFK>E#~evJaai`g`PEUSPCv zq#^{EZzd&*EMIDYzgfy%&@f&pkAr6}E08I-Vj*zBM z#n}nvdO1RjaoBIrIZ*KlNd|k|W0z!QpC}ge1D#?Su(bQ0sk_12cZXh=zvtA>MK5Yq z(Z_kiWS?jxS-x`oqTQ4u3d+KA#-=jJ`LK7pbfao0D|Tp$0^xwhf+RNQ3^ATJZo*q* z9?1fI5C3sS{<-h#_3tg{(y~^f8`T{XeUc7!#NMkJx@ZbIYt$ke+HA$~-y73V4i2oScy# zua~q(2Zj|6T_jC87|A6)(NUy~H^JTr5K7PMG@^@5EXVP;+reD%XW3-VCu+c=3FU2A zW1_cC5pGqqtOiL?ZY}RNrJseeDdJ0<4G>h zkZ6tlOsC2-fDpIlx|in8gLZmWixH#TDbJzYfNx^uI29fc|6fVp)a-u+Z6gZ(o3FMDBD#p*TndUOA5DD+@Mu^IlfWmC1JZEpv!iNW(%XW~ynYOp)-J`}lR1j5*Dx1wg@flD)WCwoeiB6XNc85ZK=-ubo{d)yf*&c)uvUr) zWPzI$2a9CzJuHrbZ*{shM$ne2%pfH*S`rcU#o8Y~yu6XaccWB`orY$P(|7HW`z3|p zpo)RM#nj$nJ2D{Mh~(3a{mv1w!m(Z?4^ee*fXKN5(b?R7BSTC;a`%pL6wYxR1$sFY zlP__<2vytsh!^1gSO&vLyf0`}-S)!5NWOy;Npo58i2lnK4*%3uA3Utw1dXp1j!O^^ zTV%i|%4WbQ`9Bd1i4hweF;GjEmrVnr$nj zV-s4xC9M*yi!l-r44{A6$7n!l)Ei;zfMCiT2OeI(fP+(c&obc3Dn>QhPr;kcBBU@& zo^iDr=Ex^W&j!M0Eipg-+AbZavL2yo74osW!AQi!a7ps&!PV+>m1C9iZ6W*T*6Y@7u;`_1BDN5W{FTCh8R z%nWqO>9cB3K%j^+c}4!in;nNkx0KO>IyDk}C4dLod`0HPWVZ=`T59WNY|nzKzQk~< zvsUbV{0*%E@iP`irSHd)OYI4g;O0e?Yi1|AXi7*-xb`6XPrjnj#JXWO<8Oj9&feN{ zQJA?k3{555Edz=Z%Wi^OWEH0ePvN>eqoU5_-z&F zLABTEK1>`ZUMij!9)pGH>)KTG`J#=4V#yLfkm|ygGIQKU{)7aVwMf&{iiLQ;8`)$n zUyxM@p?O^26!hzSI|Tqe_5Y=k`#3qVd=1Zm2&wxjvsiy`QV@{TQU|LRu2nE0dG}_N z_Iowf**zTR>GcHg;Tq`+hSGa|x4FgZTXm2lan~7^7Tf9qs|2u8!E1`wc0T)z9ce9O zw&YI~=WOwg+N>>$bu&I2h?`^{IfU^H+T56nd7VI6y#eD2A{MyrZ>*=o^dT`I;Tk3r zS3-psrykW`ouAP;=mD<(K%j{TXWX+|q()9-p(BdCv7-Th(9Yln0%RWv{wla;ZeE)w zr0Ds+BwJSLBd$N-;RD0`l0NOSIkzy+4dzUe>sB^Hkr332H% zT`E4#S?Y+E+dDM;hQDNBggXb z>fiV2XCX3WJGuRt&Tn#KN&4;`2>Czd&Q;FSnUhOTx=;J{&ey=+wp0c&rb#{HsG$h% z&q&biJzZAo=af@WNbzEK!`B0?_6yEB|Nh2ncOW4LxMs85l}D)1X{olz$=)MQcVnKc5%4!xtNkAQ*T_$ux;ob zch>p@JI*t$puO_hzji!qs?*>~e>Ioasr5-PH`BD4WHxDRM0739*!Ohmp^xSepz18Z|%N&@Y+joZO4cG!eJ%b)xZ@rpFBMKHP2`dUidDD zlC@U-HGM5m)0drw@Py{F88iy$aC^Gd!_Ixh{2P9e{?&#eQp^K;2Pw8jf*bjC)iE%F z-X)8dEhCZZX#uXIjbH|TYd)HOu?6g_cJ$8suypUy`5=v5!L6?zW%5)ep@2p*K-$j^ z_1i|7Aky>qBpjLDItB2DWPJ_*s%L?n&Ju7>Yk|R(p z7ImA@M}>-hR;1rdG4QZz2h1=OE+84uhJwcR#en0{$+5Ja*Cyb|9UGAE<{GpHKEKku zi$K|b7Q3lh>;jJ26!krK9c{7%y&ZMrm(-T8hec$^5A}=Y$)EB8(uN;W!*evpE92*^ z<%<6BeXpOy$DbR^2;LoZPUPf};=6n_jNVuxoX>IEXtf21tV`m3fsa?`yIsm+krTNN z+tQw)p6mX2vzf;$cACVFR|0ATvtC>^IKY#sic&|lK z=BVtlu6xo%xh1;ny814136Z5P_v}39rlFTZZkIdgUHBAyyG`mCuDscihC$?D0H(8X4BCyV&>TnJiaWdHd2E@OF=vd zup?}NZ+Tc0QxU7oqS~!eNo@43g51EZ{nPC+HCrHgn`FTRuSMlSO31S zr(gB2<=hN5x4Ved_K%rDM8TWnS2&+XEg9ot+EBJ!Czn}{&+nx>B{`vP2ZE>_Ubf`? z&ea8yS!8jgbFMM=>C=|DzT`39nwm`K<%?OfL=9rm4^RK>!{9^7pzcq(<%WN2Q+|J@ zd_TVpL;0~QZ1y^oZE8G`2e9>{$Bk_`h2fx|7!{6u2RoE5&{mVqJ zx2XQn?~gAdg!(Wbt=NGbh~)H++b{`lW3*WZ3)0*}^)`ArF>hvdJ=ZZKN&|tqgipS| ztpX;zHt!2kUIL>R!&g||f7sHfXMG`BBg04@zqI!)clO^Cjmdt@y6?(LP&#=QFvmE++ho%(P-NwGEi@ffQWn#JGv6YAEdJQ!o1{lWA< zV~64I^IbZ;^k>nZKlb<6KcxdZ)9K~SqQJlZ-*eeN@93uXc2YiDzEdYBc;m$9? ze_l=o>U0yl!|?aA>AznJ>MzX9e{1JO1MB#)FUmH{^Qyjat}B(^nZD(+_-w6tVz!sQ zWtIB&$=A+VKz>_)n`15|@`;9dwlLIp?7rkWhK+6Uhd+Xj-+wP^|M~lUz~bfz1QXO; zbL?NtY(CVcKj^Aq^M{QC>f^@{QkijxAw~z18sN~0Le9GX+Q2XT!4~8@t9ba=0SzA7 z7mJ2&jEg%Mn>zgWW(*d{fBj~eGDdK)mdy!#)cNOG?;^mHv?0!a%^0ZvCGg|BTu<=$ zd)ED3LjBj1{-^(7$U_s9#QxW(_^3y=CI;Sqa`Qvw{IWQ(9guUha*H>C2 zgP_Xy+MjPT8&IN?g3O_h_HTEWdQ*8{r}9DMPkl#av9JH?vGdudu3ZeFZUD8X$!G<9 z3kfQ|x%^PNU&0Gsj;P*DZ6#+i4{Eioc|zW9oY8&wXZ!l!9a?|JC=l%qj@Nue1oZ+k zMBi(-oBCN6aIoJ3&SHlPD9(z?+E|>BE%5TY=<6?$`jTDU!Xznb^V2xAQJu2 zVoEHn_&CaW&lcrv2SW1X7S}y50$R_P`ErERMVFIozrK4A4T|hx@hx!BIic)bJyDK% zC_Bx!IUc`ycHutYIxRj6d}Zg}eLvqHvGW?o{W{f2(pOEM0CJuMeGdd%rnO)hcaGQI*3+)a0mpH; zk#;&*RKdikEB37DYSx$=xl0D~nzt76CcJ?m8t(~kb4PiyJ7ii{hU*}-KfJj|?y5>X z#&7+gR+U_Tx%LjJsEbveb3S;AWMmu43|m?{(>R2(Ny^{-aYpqE{DJRQ&834%oi#eg zsmqv~9x1>(VcPcYRth6p`Y^>q zKdqQ)Jac_5t}kF=Q%&g84;Rq#wtbc`%>X&2^4~hV+k;9 zeLo;T#i-%lG!KYB)!)xNq+73TNux(@CV{~n*_t$sbw>G_kI?L*#5>vFQa=<8IKn^3 zp{g9286t+j>;9~ek9$79s@J^7=EaGYFt(eIa~dyC*Dv<%0sFDKR#x=I`di^1{-LSp znjH9_;nTN^;RNSxo+*@{y=kLza28y&R)KqkNT@*=w=Y-{MItWEfa4iBJw7bJ5m|WH zz-vlWF4^)LpZ?iu)gzH6^HY6S>R-HN`lmtai3`W3v666Ca;?Gjl$JtaP3(V$<)5*X zj6e&Q)wKz{%ZTc#V;_G1qRQtC?k8^>ft@)v?HIwojv*&Jj8J;u9QXb?puO7y!UE+e zw>9k!<)ueE_Dh+iMg$%X&tgPjwo67J_4q9?dZ;?Zw)qe)0+_aTTqRXoK72)#HFKlB zD-`Fv>prCo`F76(iPjV#)fjpr^T}B@8Q?cJz1{#?f}bs?-^vuqI@&YLXH$)+k zm|b*sSvY3En{D9qiW#$fA_pgg3!7?xyhr}@_6Vz(A}H7yquR(@k@so=w+LA*2xNdp zgYlzoaRj?v;UsgYeOLpwQQkQVt_g`gFY#jA>_FR;wQTn6bfVRu{w+L8RnKPQCJh&6 zA;zB%oL2yC0-tZ5Vn4O@yt{(x0FV)WTI71W^!fzYrl-<6bP?NvCFY{aU2*p{kDjUK z(whva>deAqo0^{amwg}i^*ARwwi;9#61E!XpGW`esQr5Yf5`iN>t^})&S?&Ln`VMr z`#pl|=p}hW!)CEu4S@5V-b5n{_t^iU!aRp^_!U$6&^BktM1mB9g3^}V5#P(PX5bvy z5`6_=mS&;P6D>y{Wo>-Gb?8Fsnk{~Sf_Ml&MsZIlvw=v-z{L9*7JqU>S+|DWFo5>x@usew^ss|Jpb zEpS)f9c~0L>xJKZ+|QfowhceeaZSBquf62BOli4Dnat`^|6d9z z8Bby(gClT^o~eicc_Dhc>4q8EC{N8~2P$;H$9Way4U9^^*tB``{QtYGes|43)xe`a z+i_SFB``6V*nh9#Jphb7XG>ZyPq#o!N9h@GiOPOF(o65VQQEjA=GuOZ9BFnJb?9~0 zJ_GKoFV~VQAq)ASwRxfyBfbR_>7{Y3135?AwkW@pGj9Jwp4!>(s3?%uSTcqfkR>VG zeF>yDJ2rK|eSI#HuVw8Sd3bz^p^y7Q3^18>9lf*hTSL>>dRSst51h}Z+3&xK0^Yxb z2G}kjm{zfDO#Pp&BCnPRxo&v%i$G#WX5rZqZ9m=lFP+wxC}2Aig?&6wq)nFCAfdGb z25>(9XbF6!)n8ODvjDIA%hQ+rthR5{Enc!`J0&cjSVVQ;G#F`*Rs)ATsW07va&ar@ z>rCa#&H$uppj{bUkqivCQIXm$z-hYizVKAneW{Zlfx{!y{+~vWBsOk-9Ty+`j+ilbclk3p^0V4kAa15PmYz+sm5c@&obWgdLo#~cew zfQ^mw`Rqn+0iWdj)gYG#4@$!&4}f>jUcd0BkG`JuViq8yC!PU4&Ze&JHEVKRBlOy? z8>+~oQo!Y3{245z!_&y?bAGmPH9rSlA86#sh8Qu<7+@Zq3hM`)$6tU}jP-j5l@TJnXZ{0ho5!2x_n4C&157uS@VWd{GAlT_dP{%g1=X!maP>iFUkhzPxt-q6tmQ9wWG9lK2`(IPJRcZ)){Hrp=5fqr5 zfxn&Pk6+8^yDulx-Yx!c4rbV1&?>4RLY=I9j$mB&k8hP&L#ZzO)LvfIW4jn8%7$5) z2c0o0NHF6gX4$v6-q0rC{CvTNa@1@D#h@1h%hW)7Dr*oh_Z{E(BHPZR1# zM%C8U<@VKVUpzDQNBh!S87EJN0M3__x9f?UtISp9u=s{h?bS2PV>du~-h(ZG%HmS= zyF|H6d^AzqX|$bJr?2`Mw$+b|PG_jOfP+lhlie7hpKn)(rr)4A9@(;pg{#Y25!h~y zV!W}*HjgLy9s$Tgz;50%1r30`m~oJ~kTEDePDV@k410Kvq7-2fr5tq<^`ePzY<>~) zbI%}TsR_hk7&x>~b~`V6j-IC1l)S!*^0rr*9#LWI$)pGche(9NH~Vl@tOb|3HG2q< zKr4R)OJ~})wItIMpX1!uP;*=$rx=i?ZNXMeZI3%L1Y~t9y)JdQHb3U`Wc(L0NGVe{ zGMHw}s3X6pY3u04T<={>Up`sVGm|O@aI59Zx>vJ`G@hSlw`m)DQA{`>bxOJ7$%l4Q zj5LLK+lvIqr964r|MeJm`NxH%em2VP4D?#^I99Vi=?{hk}3nsWGsrBWAtAD$4<+PgYHERP} z)IEC|C;i#iX)S!#p2Si_o+-Mt+dy3G1asN7?&@;8c^bY$`F76v*ELc+U`uAzQ2hcP^HW=!Z-3$P|2pYLqoH|AZM~uO2{>XHE9H~TrOii= z?P`1N*w_?l9D>AwA_I%218amnrgPHuOOV*^g$ybSy0yS|X4O^gw0AaE8sZ6mI9gy` z-j0QN+9o=ghwPL+MVSr6H1)r5h*4xldoS0tlF4`OIhGbJ1N(!S;zX>FHQL40N&IUeUGLLNgk;Tk#x={Y?S|eD zN2|UwuG>k^J8;JxUe1H66peSIM}Q)_bu~SjHc_gL?_|k++P?Gp90;CT*T+#k|5!IxTPC3VZ z58Le`xj2cFJ;lOVY{e1V0e>%8Ar9 zE6@a|9l#yLO>G}5?!jtBFWq{7+Q+~%dvMU7K07rtjPweX$N{%BgP#`1*sJ*b7HB=U z*l*okxB{fBgAuIWx|kPh!~;2D#@1>5{;o^`gprc{j`6F#N~W{Bg@FW^Tg7 zlq+dc7P-OTKEB>8xcN0NMQ6`g4+_aHxJeaDJ( z&IP6fb@M}Rzo;{LaW~$MdY{LQCB?7AI6HY>;Jsb@sT5##oK!(pJc^TWB1jsL_)H^V zDP%P-v=fRwye2nYz*Qkk+8p{sXH}wWx;^C^;RtLAU)qr0YcZ9=>GNXGL5cSC!?)YU zp8skp{Cyo5wSmU90emt|RVcJ$App_=iOr9cCG4QVGsHc(qs;g-=2|R}4i?4aH?|Y_ z83cTT`Rpa;vhWR_4?m%AC4g9JpIa!A2H2qoNHLIlB`EF4(<@m-eF}S1i)3Eh_q)Ps zV0BWj77^BYBjH6--WabI&7z1@NLObq*2w)27(aj4&&bUUS1K~BxY0Apv zb-9yIcG=lSuiqM2DjL2A++4}~0qwT}Z&wY-MQ1McmM;S@P!fk7D*^i3)3HyF0Mc@J z93B)@^OC`w?c#h2bz{vF!@y-IiZNDHH6mi*oT2e55r`wrBB$7K5M*+^{RS61k6)&* zRDS9P?l3VVmROHKG@mX>;I4^K*sC-XG|TsA5*>&^nW#NWaLd>aibNx$xjihgueN|4 z;Mnobmy5i29N?juImHe%mMVfbWCJMr6r-uk3r~3l_@LLjh&zJh!q@v?XvA$(!RR6H z&X~A7@!zrZl4D6>-LW@iz{g=xUB5A97ibjo9V;6Hr(2dPl&8{A$S+Xf_`1n}x4MNV z6PKWR)BgQ|@w=o_$Fbj*83N*<_5gnLeo5GX|3gBD$R5h^2J=RnV}KTEP_USZigX`? z`kgr6EnSjT4{nnrhCO#?ZGOdOVVaJkr*)j}D`d%55JvLEGl?P7^i$uSLg(DD_! z@rvs`BDCXAY#fU>%1YdZpYgTw1ql8}X*5Z>Jm z6vch4B-r~CoA`_)%l&N($lbbn@=}^12^JtbO`KKimOClgZWZr{q}Ad}6bPd?IXvaN zb%nhCP-?)2rp8TVXIM_|o@1?q<*m6hD-9MGQ0I5ivta5mkJ2xmY)_-XI$PRM5>KZg*$LUjlc!48wJ$eU`!Ux5it?M^ z@yt(0+gFe!tLo3Oix~SY5TR>kNf)-Pcc&#j{QN zJ=#4K{A_JGyWL5~2(^%W5UVt6n&tXrK;N}$KLU{khm*y8stW%e?+MjmCdyhxQxCfl zzY23QvAYJ+g>=R*^V=#)uIxo%WHjLmtjExt=m)gs{Igt?<%S2x*3MP{)0A;#Zfitq z#@|L;X^EQH$@&qYZSLvs6R@XyLM2ILDy{67R!hA#)sU~5iu!>_t;-W9ZiWsUAnLbHT6Pca1CH5=WoJMqu^f0aHGGNOGtzp$8T`Oo^?t#)3`qTxFH9(wJnOC<6vSMfvAQ+DZ|iCjc+AfZ&dQYwfD+P#Ky<|zSujs~p zNdB}NyMwAyWfTGod4mQA9R3s#%>d%fXp)C&6b!oabjuVhAv{0)k7UIkcXgkTKC zHPg@M9k6;;hP$V5<%0JK(OqD*)eoT_?Z((0eVhca7?98gEO(HPVTQReWqo`{m=d<{vpp{FJ=d&q|^$#wN zjv}chlce^(>l$L)KENg;!FKONrZ@`KAKS-v;#D3VJb_p+LNd~wBG|tuMAcOXpQ#c7 zRm=i;R=nDVM5=a|6LZPe^OXCJ!R_v@(uD$w`Bb_H|NB~s;Ey^=1y&6^VC3gODu4>sa@HNWlB zX+VdcthczR)X0dPKf-^4RN(d~Mz{4H`hcLmoj{=o(b~9X`tQMGxabmW999gZcVC+# zG;q~#HX-U$^0FmN)JX&sZ)E91pBwMQ;KVd5gLF)^z&PW!pd)^??|#`&DpMRMHH-+p z{F3dxRW($$6~k8v2L2HzniuAOvtzcauqcl zVQD;Pl%<#+xum7mmTXBplt_Z%Lw<87)uq+MyvEcJ)HR!HMZduHAx{co!X?X3x5FDO z6yIKG%lJ=;}A)LlxbMIdHWx>LM~pzwK5kHqlGqVwEAJy@yAfluj=`eE*UnUCAOJH#Tr zY8LLczT6;+jAvFb3%nz&Hv=k^^Sglg6%J#|_ zc|RQ0GDd!<%Zu$}w&&?7O^bPfeA6c5|2kU=ZZY^Z*J4=WzFy%#AMyL;{(64;f<(im#=-0GHSc1t|2))xnAtD)y6_E_ zC(qD)H8JeUnT_cg5!kIN8zyX%FU#K}*atgsN^b1?Mq*tGc+hzI2{X0nrrSPDo)yzM9kD@(wUyxW|DXoKyxiol9OdZ7f;&pZagRt0QR@Z$N2^d@A;^^$zM|zO`x6nd7wE2`~v;>GZR9jIBdQ0HX*boQh;n`?Z>-WdWQ9` zRwK4IEe^u1O&BXQ)(b`JE575lns1SB6S1slroh!3k6rgfU$`1-qwtAkVi{t;*N$ok z0<|rN;S&8XJ?5F`RIaZK=0C2a4N;J3bxoR0^=vn7@=W`3E%eOmO1caUM`x4FSgzIv zcy|3#-7=M6O^e}HMS)#98TsWV=0Vk#EP4vHzGWR1V>x>vq7ss!NL5ae*N>|f_1!zSSQrG@NcMQ~#;abQKGq_ym|fmwz7(%pMe04ePG~z1 z$MPp5epZOOk3U(Mer_sTYyb~bNvvKs@nR^!KkBSUg-5q~*iziRyW(`(wW~Q{yrkLa zZchZZC zzY{!!wBYlv@4mjBdXB@_dS2=JMmU$@Kt7CBSdGgMm|TZX)!1W+%snXPJy2icf_kVr z*2J*dL?sveb2tUb*fGoOJ+h`n-U52P=@ucR-}edA@KGo(lgu;FiX8UJ{#2HZIGr@X zbace`ZU7xJ2A~|FW|z1yPBL+n(?B3sx+D zkgj2~cV4-GgPZ}Lvvc4syt&QZ|3NuQCXUAC6`VDs>&WOx<^214(g*X2{@8t~$Vuaf z2+0@bt4wfum%3^+so_PD!28u|)FlL{#r_W4|D2fV@N412$9{g-J#G?(RADM0`K$Q8 z-LO(eqg0_NWyIt+nK&Hbj^!i$MV?KGqoo5UU;^k7kiHUS_k&wcz3RxZWp3oh$3@q5 z@-v29y@a=3Lk(;$L(|FMLSK!fe~k7_Wz#!!xW6GnoN}+R-VpY@Aili%j4WkrYh-RG z>to}{2O!3`djSjuS*-JHwB#s(4RfVR~P2puMvau4YrJ(QQ zw45wAmNFiZCzSjVNP#n{XnjvmKYwUojZ~xh%wiK->%vW=-?=n*TK{J)K(1SjaB^{& zkals{i1mt1KYX)2=W+Fw7gVeN%Zgz1^Nr~T#u-NRLbXV!9$I?I(H!^Z=n}D9J^TJZ zyQbZc)=E8UShx$K@c^_(tITW~)c&E8u3F%QFI;I_bTeBSzP<3Spk2NXIpJj2y zZw?2Jp{0svzY@U^=|utLT~l!B-*itdv*x zfl{R=pz%U;W4R&CCV}wF-3Ss7EGJQ++S5C9Bc+B|+Q=l(+g5kWuXFpzrO6!1`-YT> zMldeSD{+lL^+r;8*n&Mkx_FWd*R>oQ)&*$gu0VUm^^N4Jo)*p!_BsR7D2}1NP-tv4 zunn&&oqE6%Oej1QT7pIk0RkPiDy5@r-O+wMBcw^PM5;Z0tmM;a$Ub~K?{?O^=WB7ug#K-#B#bafp{7x+Ewa1^WEYFQt7Z`k%)sa8JsRQD2 zzCW}n-|@xeXlrFFKthspMk9())ddnflwBkMyXUC;V>H%;#IeKGejf`m{O60L<*81F z%z^{63(jxc#Q&{Sc!o*dd(Gesr)=o!3870x#bvjZ5KpCCf*1T?lUviiudw#g-2zcI z^`4!qyA%m-J>{pr(~x5%Ia8d^WBnj%Oqxss>vbzbewWZUb_HTd?LVfzn&d`anjVid zaybfK%OnnA7#w-3;Qh1CNATIRXSunw{;1(NHN6*hxg{qhyd`|?NxA(7Rxv~`hRNRd zx4KxO&tKxcs0w(_@BT*KM@urkh_W(IOkItS&s1LbX9?RrzlR%e*N6270U~3d)nzlC{7;d(^K-hdE|`zWXGo~sH{r1;{KTU?xTnM~+Y-vjD6 z`g{7`xoG0K(dEhr%urRpo}Y;Jd$PcCaDf3 zJ?3vH7+JCGE0C(Qw%A66TDK5*4-Cr~Z0(`UI*Nq9%A$i`bczLJDIK}dzrnktLa3tn z`y*$FbkjLBN;PVRret#>>^j|+C;t-$(zAy|p>r4l^sADLfV)H2_J{L^R*hMSTctBx zZ+vD{*aYyw<)0QU`(R83_sTG6>VQ*;2vI?&&*@XL`6(bF9Z=wrkd&ISN|gJ2>j1c_ zGlgBF)1z$4=7CaX{PF^zvU}11y-s}?bT^6~JK5M6qt|d05TEEeveyRdJ22#hw2$f& zs^qwk+)%tPJx&&MSE-Cvm`?dT9<$}E>tRIqwVpZnVl5_5sg?=fjS&|`5k{mujXVUo@ybVk6W z^-=CBnX|u2H}WBK29>QdHXfLnF7=$?bZivwMM3p61{8^9f(YInkD$XBaV8DUYnyFt zu2iAdjkg=RgHDh6q%c!~P?h225TZcu1hRC&SP; zZd;vweB*(hFxGT+>ZVGidfL(O%~`9=v+18Zn_1De9^vLA{3~4{w*#ojr+gllQuc^ZOz@+%T{*5IplJmnZWFt@B zSNd60EZ)Zx^{YpiKLaoQu;+H0^HmfmWMFJ;mX( z@I13tb|h8EK#@^pRqq1b|a zuAM(n`Hde?tL&&)YVTjG2|n`kZMVgVN!6nHpBeD? zU5UE?71{m4E;nofxb%&$RC_L|N!!-N+Qra3qqgPq--^i1r1#q1;x4x45!cR?z54Ok z_xf|HG}eicgeTM{**`r>PoqU6TZr1Ps+H>2*G-DDD2yy}=b)>FQy zE=;oYj^mB>6FDedobapnkyJ*k-lNfrJKfNUxqv5hFv>gbqy)(oTVr1({qkNq3clK| z?#s0~vgu=>v|>y6qDIH|B6G)XvdSj7K1zs5JN)9lh~10K;$@h7w|n92wkqna<@%}# z3T61Y@4*E;8asKy+Y@=)ub(5#_D`?FPm_`Ed6?tJ<_B#u89&rTFHv_c?b-NB33cq@ z!Gd2qQ3a1{y@QrmhFKD;&`}Q6`tqte-HNvU=Vww5Yz*w}b#jSQpPXOSJIxsBEs zRB9Z%3%!(BLzA7-=jnCRv!3f5XBpiK2W;1#rm89uYQ&sF9tP0YfO`DSeW%gS_AdV8 zHCf4WL;Y%Jwfa3v16BENfp+~g86%3mm>cawHq6AEE&WQM)>uz3k?C}-A&ty+Y0iuv zjcUdm`UM9}UTfQ9CeM8YY%_*IkcEt0Fw^16uZ^7NLC?0u#5pD=D*Bm81{`j(v|%2j zDl(x#Cx-?@10!<7U{_2UdDMNn=F%w0Hv7F!y|cZZENmNPkHAEBpGUs4LT>qrq;z|J z1!)L7?5^cx11m)t$m&;(Caga_=&y12mlZ6S6_`;HWg6zs$Z=Fz=;bUEtTsxJOgmxqF*zG(_y64Whr-Mdn0D zVQkxqOsgabeFfJ*VEMdF%&MKYH*?+3VpCS(YwiJs?)^g`(AH(#By6(e7n~}sD>AyY z?=D_}ebBvU$V-=+zIgL~ht`2UjD|Y22L$|7=66ZRa$qoBZTEnQ>qs)RQfFRES)1iR1=zVoHX2aBqnV2?t4s>e0#kD02R?Lm#jGrpw zqo^Zp0DXD!HQH6ObmY)C+2j( z%=Cowi~_%9JCWMWCsTY20|}4g#Udq)px1!$jG!4w5~DyNfRXN7^~%Odvbj;?izlh@ z+XE8TbA&0K^Ac?fO^hDBozds4f-W^}T@C&>J$tg6-dYHT;J#dxFp6_&^vvZ&N}@xZ zf?4ci4yi*ioukZmkE7uqj4Rwt5)UWlx5dZGfEQkZBlPppW7MKo`|`TJiB}3p#Y_eb z+?{cK5mz^2p!zubOmEN~YqM~O&iM%eCqGGG8m-rP9A?bg*e&ez1}DC+I*XvAng?^x zKd#o)@;LhXb1jkTBGpwlY<9aXItuPI)kS6iIqsng;>J{sYb39V3 zKm=~uf|u%SD$ibi{ZuAlHSIk?p6J$WDK*4UP=sB5yOnQbnBqq}Wws+*C7^m2)ExF! zkBWe5G}wz9555~nPgSwB|M@t6U=$aNddg#mDDG6K?!px8;Q2b*|}`AL^HQ|){b98ql9qb9MM_l zqCxunUVpo3z?SL(>^F>9ydJ`vd%UFOFb2c^<|7YU*3Y%wUo`vT4$%0zp<|<ig4VD8Mogp=a}xBR)wOURtb4vhL`y4g`7LVVw%`?(DUB+(`M!#K!{X%#fBtZ4e&$ z1?lVbmV_x}jKW$@v(kM)c18>_`Q|$BN0QM&_UQDn_FvohS3>uVa8qFu?GIL7GfR*x z)>poT16-f|Fvv;HXpI%xs7V?Fbi~89#Zn73L`a2delvxvy;)l4Mr7C{?9oyOtY(J| z3v8ahFIe1~cgnM`V&6;nm2oPDaZgXN^N{aM>D5Bsx?ZfW*Upgg8mkL&0()aKLn7<3 z|5Ns)5lLpo`}48C>)i0sMa4jqIGnc?gaLAU_kAvOY2eDY*I^k87`5>OuF13=Y|V30 z$QBT@4)p=)h*7!2J*WQ3j<3Wrq_*2j{AoKLyZ!1lxragFX8y*_OL(jdI__Gt`xYiJ zo3v+v@ObBXBzNbqP1z(WarK%@&Zbk>ZBww0cL`tRBXimILeEiBK*OfTpHTCqmr-lD zaI6?#;y#TF>(dErXhIjg8aY zfko2px#v($0Nm#B!Nxk9tHWLXNCq}Cfpd3vaWad&^)Zyp9op-$H|QT>L8rw7%VeWq z61Ccg^G0wNV4$tQlq=7~74=%4T&K9_0Q2UR2jwj^-8zMUF1JmSyBf6@S%(#z*9{gT z*i)vBQ*UQ3lL;W3!ieSKRk#(|!b3KJdcF8QuNqf7cRQ~oZ}=l<`}1tsnHzDQ-5}M` zcW$sIW1|yb>6^mMn9(ODmsgundmlk_2IeaZj7@CKS23DAN}TH}aZl>NBZ;&lzlm9GuupvP@-#MILHY@!$npqlf$UDWRU%Jjy7f25K1O&o)|27=OkvN_ zoQ)*Weh3~xY(HI9yTr}d_=L@KbJ=M#Cl6)LjCH--Gq*Uq$~z$q{=wPvlM6gFv=M~w zlxXulV50ncY)3b=hA)B@s5n7)0|l9Xpsdy)1LSp?1`H*D*Qbtjb5(0Zo{Amc7DCPO zjUmSZp?ciYFaQ%w1X8g^1*KE@O+K{)Uo_5gSvTs|K2H5DM~aEYKAS(doV>0#H*J4k z6najtovCmdbijG7=O*O3sK6PsJ6H(CYf?$nZO`h9!Y4-{z4$<1wH;)}4(I471pb4YiB7 z&U&IL7mg<{y`>%m>6I~t^n#q1KK|Un32sbB;O2C7T74Sk9NKpod6>EFq|^M9UpQBP z#^Fv?(z7G@D@1C+vFT*+(SZQ@#nv)Osn?Z1s;I1XHcf?ow3hKfW_=+oo;>I_--h-; zdSVem?cs|f{2SdkMLk`;=rmm*k=I@z5dpqi(P5}h=@o^slUkqGx|=jkbvZ&0bU*|{ z$%fT&c40vO2-_8@b#cfMl(=?vo~@af^(EE&Snf{Dw`FzZ$=|qSl@;5|6!0Y`MYeU2 z>c%k`>IXeOeD=Z!Zq%zR+@C_G~ozT}5q zm+gSi~e!6{@nLqbt;aw2`P8k9CLV}ES!g>!K0!6=OYxK&Tg!tXy@`#r*6<} zuEWWitwI@2RoTud)SDsggASq&o}uopiN>`g9Njx~*bKx1vxQRJ%yx>XFsgG%%UXgN zIT%u!ytdm@4vDJf%{uj!Y9|h}wF$VrN!QpA*6PC>VC8GuTs8!R>pw>ucO=loG@rJN zk+6?R@6m&WPR3pGJn*8iqy@{34JU3^{;&xE{ z;RL|n5F7r|`>B=o%^gMEerq+j9#EHC{!T&x<|PfA_7)uX$zz`;2+Ic@)J*Yxh`ES< z%Ie~VUfx>223p+crc|ToH7Av*?BYcD>ScIO?l2EDVra}8EEVc^ziYb4O_}BjW)?B` zLQHWZTgDHhi9YkVotp~Ab$2X@^wb2^zZP>7CT-ZTo+@s(IX(*L5@x_a*~bF1Rpmbh z21i+taThjWnD;!j+hL5|(e1Si3#v+WLOJqz#nCr?IVe=^SXBZAmYU5r#U{ty5q~Sy|tGRDRkr5O6(W4?2}zBY}NeiB%6l@C!vq2Y1rD@5(}j~ zal1|O5i8-Gf$Y$fQnP*{*r(15H+E}m?&m^eMST#xM3Z1~?%0kCI%$3j=TF5PQ&FXc zGfp1E8A7St-RZwmgvm7+}a_og9F?i(?Koh-@V|CnD~i-^D*u7!OVI>?6}e zNYFaxn~cc%@>tHc@%IlV!#6e~^F#Dx19ErX|{ZcagpT)CVR zs^;Dqsh@?H2?Xyhob;nCT+I_yG2UI8gCZppW6+4&rFU~*-RF{=)}Gp0MFOw8K@z4< zCAAZMdokJ`&7=ZQe_43;k#R6mo(H!IHw?Mgph!($C%G)VI^Wnib0djmJe^$b~#1D&f2hoB9&|< z-b<5)G}lB7yV`W%61MS|<9%M~)kuuEH?R6hM~AVaO->X=o!-eKNEI|5`$CSD)Miz* zzH;6={e!^_We>xnKgwUW^a>2ya$qV7LpL z+mY2b%PfMxQQ$~EZa!H1u~8&KVUotJ&`oj+C#>%?97De=_$&XK<8PEZ=+9G^%f7xi zw?=;=NBw+8|LXx2(bH}|iyzciVx|cXe|v#5?ykd zKJvc)WROAMc!tosUbvP(;3Xcx*X`3Nh5AHlYy6B@p96B8kf~6S7IemHGFtgC)U)ti zcF^eQjAxtQ>{x!~Z$~Z>x_2dQEFIMjwz?0Y{& znGk=qXyh$8+>!pN7hrijF9pT7)){7)kk^dSCyCJPYV6P*Hk}NWoPIhx+FD)%GpF-2 z%Ayb~&p4-G##hBQL~&Q~&2xIhc@K6Hudx!Rzv4@09ZX9s5woWDVvrMiCZTqY@~Zn& zoAE6%arecho8l=yLNeSp3a0pVWe0YuQ}F zhE88l@_DDYID26S}<)@$k4D* zV3rIOYnyb*wPNgIhNsy@*vy<~940c>xR1w+r_H3J+%MC;Z*Ie@utQI1R7%A6@~*2~ zPenxe6}uqVn+h(LQpN8A`y zMnaItm>#71Y!1%mbGF+dn7lsI-TknuTjKcs+DKIpKccWIC^}6`0>4R8=R{@q;-ju` zt8uYvn2l9h+v`q06O)nQD3VV_fs!^XjXO*tU7w~7hqLUv77t>tu`b1CuODlz<_ApC zK0n>LLe^`e);LBnoE&xa@Gz;jj;kzhzy)CmdzbHclRr>IiX6FAFiG}CE`F-7LuLb6 z3(>HVJ~|oE@{?|r6LsoRszr7!4j(P{w(6+7Y&X{jt&CcedV^5(r{+b9m^XLI!>})x zT}HBMEbA}dyf>v)afG?am92d7#es)>ja3aVYopME2Fn4y$K-v#bwq!>Q|fcQ)9JO{ z$b-IkMdi}qQpakKzY#&jQ-KhZb-JAyg}}3I>+KBjVMaav=CJHr+{d>oBR`d+rOfa-)L$_5@Gr1{BHRJ#68U73|j6`ZKLHXMn(xD5ahBNF?|uhV^SY z`hdKvx$Lndmt-CVjP~J48)_nQwEsX&$^z6s^4d;UxBFrw2YCOQM-Xg@sGbK(W06sBzlA(Fe_MP^&_#i}1q&r{QnYLYlQ?ek zIU#Up2L+*GX29&VgN+*W2EIl(vHH$f`XsOsbh&j+#SSLM#D^6=T$AvM@*cO<$JsX9n%zP+VstsM~svo|Umf*w@-|$tM#zm!XEOqqr{~ zdV6ck;#Q4a^M%FX;pPD37U>j6xbdO6^|AI>^y<5#R1+=C%O%m=pNY6`O4NNbR|V~k zp{4Ex!|)rvC;8ONG){bm++RuYu9C=m0N;S2ukDRpz_lsPUw8}qfPDUC(b7jr$084B@ZrwyCxHUEJ;^K-qh)ak6JR64+Q69%^a=~g}noz_ltjm z!{F}voE0zdtSin)*k5e3b8Vz-LYfrd%gn=1ukS_W#)a(ynjAh@pFY5#{t#}*{G9jR zyeE-E9)+=V;PI~BZiv?OrQfSzNostGpQj0H*+d?C?UDqE=aqN}FLe?gi`5KvULsPr zx@FO7PH3-4pYl^NVyz=*==6Bc6EmbnK>b)d8#cjy-a>D@(WP@Gv7jj3DL6ik;@P#h zD?K6b2n}$4QTy)sPCI@V1PL9XT=G4O%`edbd|u?kk1gy}H;(Sm_*wW~`0o?(2VBmH-^Tq7;LGse^sg9I zJksNMc2AluBw998c#Ew#3h(Dd`C!t>2Dy`z>j1dq@fH&JMBW1=SX z^NrsBQk48UzyJM_dgW{sV`oR(0EVz?`QV^<&_8la1b-;A5{M9IsBgw z{eOG+A}K!Y^ORQmTYUd=YW|=8nX^gA%XwM;P6`MGzgG7D`xCzFiuk2TP>K)Xzc#`D zdMW-t`~ZDc2%&X^?FZU_#qR#+HT^%oo5PEvNon6*PxzG+D!NU4xZr) ze(m#9+<%|jTWC^AYu49Xl|_?gz7D?*d4LOVgv5))EE14C|NXD~Pp^j(>E!egT6@Gg zOzWq<`o-n>(b`2-C@DML$$Dp4^Ve<&C;57xr0HAX|NRwFY$6#*59z6Flv6JDq7;grF1CG#EQ^wV+vS772l9nL>r4;?2Rcorg* z!gJTp&u^m~mG#%Eq=;9%G{%{tt>?gbd+_Q#R?Q;z4}T-ATcmGFDQ=I@w-u+y|NmIf z->6A&AItC_M3nr|Lg&9eH7>mI)m2AhP1Z2yZ%m`ZH-wF@-ud%Tx4FN)T+6Oiw731g zynNtzLu*L}qC@_Ax6*5fHSN>e~>mn((a85fDJfN#!Uh!XTcHVMMKD{%A z{IDYO=WdPQ0&i=OjgdzPn!NoxuKikB|LZG~-uPbJoMg(b{kaiF#&wUqe9IUA+FdNn zp=~jYH5dHHa=4_YD)shtm0{fu8GnAaHv+h$-jz&N{&mIw=Z*HycXJE~UtRb(t<~*3 zSzDcwmS$vQ^L9pMqSU5a%jX`Tvi?{Ip+riJ>a)%KjZ${YH^GN1v^Zq{{o%vl!&UyL z56@vD#LZyMxaMEM?$(GmRBYB@$);rUOz|qdS@3B&j#3&bchr{yp0XdEFTaf_cSMZ> zgTmDS#$eDbnS6Wj`_KYF{6FDR!s({4b>QNqonglON4QO*drwtyJ8+{c=>;m)lGYb+ z($2@bKfM7IU{GvYw=H`&uw*?q4ld)FUk8}erxOEjZqmsC`m3n0u+K_F^<#kz&3i9= zzOBo4gC9~Ht9-IPc%7Hc`Rlshq~4Uee)Der*OX1?l+!!b-!1{R=J!*m0S~Dp)u?^- zA?w!<|NGTeOeDdLZ}tYf#Mp3&)e854G7GMl)3XSqtAJTAN<_)hKn7~;L!!BmH>ZFT&*#f}aCmgs4n)pYT^WmwhVMTYd zF@723H)VSaC;@D7_F{p+B2>zG^z-J! z-WbI^{#&c~;`H$T`OLRbitX7+zfOSS99Kw4S8yRXWmS9b70SN;fiDvr!(2bEWgoi{ z-BbT_L0uFIZ8txoPkpID_s>Z4&*z~}HO+yUg}BOX5V|!+0pionw>?eGlIE852CkDS zYuKH7Wv+Cf+iMk7?6aQhJi^PSiW?bH1H9@=M~asHqI*>9US5h;L=fTz4KnJvfy$=x z!j%W}4`TOmpBgI5_sL=K5~_m-%CB^b-@ZMT`RO#-buxgID!wK)m$Uq6p*e&a$k%2a z0|0bk@ENuO7y%5T9?su$C48i^!3u`6m;lQV7tZ+GQLrIuL~*T7thX>Jez`CwStX0D z0~TD6hd|rmok1VLqjlrY+Kc;}FNrysIh`*i=XJ$+r7qY_*IFEYzi8mPS?lDK3@fD5 z>FNC1djC8pzdyGNAgmbo&_vl0n!DT2G)G9;_OVrxiro{py`M{y7~tpfn&zy`WkS~I z%cBBMQ4v0Ja#4*s$*+$EGgFTB8QGde>JKgD0HVEOws6l1_bG=@&%y4(aOPh@QVWuB zk=o#{%+Gp+rJNy98Y2p$QrJ5%2z(f4@wfWpoo=9uTAx=oPJqE!61dct=_&l~o19eg z>c?-!cTLx6-(STu{G1mrT92+LZ#zp;3qQlpFtJ;BO0QFQ7y6Oo&s)%~ON6yMl6y@= z7bB>f%6rxJb)D%@TYn~hIWDAMu?0q0*)RX`t0!}Zf^|3yeEKY32gkx6$1=*#-i?5IE{#>`2Y=21z^}B z%kE{It$ZwA15Q&VV5^P?{@_CcS0M`mV#>m;IL3|*0JjPXqUYrEf+h0$9b5cKeuh;IrhDJkAy(;3~nm%f4!;I87P^`2lUVM;53*J=- zqSib)9h9coRgUbc5XKqftcI1ueERt*3@UYC)JJ@(x;j*3LT3kAhfBL=ftH#RbHIq- z7)?MJlr*PkLlmsq$pxmHo;E#Q8z{JQ-=KMKzG~n_P-swGJw%SzK`xT&xwZ)~oxEwQ zYZaFGNni@JJxW7tmHR988bEdaAd-@uc8P;k+;H~s6M_DcA%w~5u_7YfqU9;y7@v3G zu-Y8lJ!l&L1@OA;aLN9ieQb(k^N8|7Pu8i)?5<8Ca)pO~5)hHQRd{>}N_AWSR#zSs zuze;}5Abq>S3S%n?p``>t)H#+yk_Bv)AL@Y$tgycWcxJ{)>k(tf z8dF8tY!+lXO~}SS&}N4`b?xN?5&TYE{uc}3UeUP?r6tbPR#lDIBG{MqiT;|DDO<$& zM<51}Oh{B7N&C&+vl9!tLxri*PnpxGL6o3#;^`eTWY)@+Kl8yOI=k3?UF^W!C;u@H zNK)cMS?1`Y=WK^bFIdoWbGPajc7!r_sH$9!x*lMuK->JxdX`m1wsPDf#&g~#N3$zm zh>-0a+~e6gFdVI~YNhWm*yj?7cFkfVBfb$X4o;dSw}`}HAeX@mMr1Y@=O^isslefE zjR7itvm)%^`A*MJ^f$H^0XF4R@x5()ad?;^vc?Fm2c~QJHN<#kwcAphT~%>2axPE7 z*^Wi82N5k9vPHUAY4dULD8x6{a|q4RcR}odc)f_9Q`v4G=r`Z8_^^GF(Ko39uI{HR z`i3(3bVU)K5|*tbKDEmVB>u3IO=VQyr*kyKwoGma;C}T`-|TFHb&Dpxg(R3-`r!+l zP-dhI3CkFc5HBFGU;g&myPer~z>WMN21g)-XX9Zwb93XNzGqWsr`a`Fx`-f&uw`f9 z%Njkn*5UeW>N{xKd|{B?OKyX+4t%6Fk|2J1)Yg>l(L%Z1c4)%+eExCsPkA9uGBXtD z{eN{l^D)HEb#1t0_2!PEcl`FqAw+Jmc3B*!bCiWbG+ z9togem(#v{lUjKOjSQkMDM3?F%ZQyjr^Ftv0cUK8lj451ly#B^IsIBhB^?vA{K^qg zFl1)c!ijCkIt6AkGlWeufwy}jS38g1O&xgidA&B9V>={9Mi(ft?ho8SGDBid&696#OO1k1=!$c% zV`X}B`aVYYGcks+#O$tO`_ZB_eZ`i&oHsdY2FE-*>6qR3J->rfks+{fvOW~`8!B9pI6$12IBwnTZGofxy@g-!ag$W>W5H7b$%DB?Hk5mQJq&F>rY>kA4RQc z7(J4C)sUQ)x3BXk{R>Dj79`$(`ITZ|30X2uUnq#B{O8g%F6JEfbKrz1&y~AX)RFii zv?_WyOj)qM*-f&oKy)p6txcLlEQwD=5=uJvP3!aJ@Ox3dQ7|u%Xvo@5ep>!5aTNHq zWqK|HSHcBu`DtjJ#1*}EH&MQ>>jt&63B7W9@Z0Vr>Mw_?J#Cln#)Vz(t6xh9vlpYa zEC!iPrz+-nYzn*B$`AC2p>lVBYG~lLtbt{PRK1xJOFFmqppS!6Mc{dxE|rJ`49$ z(*|zxt|bJ)4u9i*=?rwN%rW^}WVx!B3OX-+3ERR+#PvDW)ng+iq;e&>8)%yP1mGD3 z1hb0V`ZOgJ{GUKw_^1TjW_w+#W}Z4UOCSb;lj|@8fxpU2l}__(URA)B<&;Z2i`FJw z+}*UDl)1@htim~SM^=d10N90v^=-*Muye)=SD97?pPVcy_%wfsAY+u}Vn@lMP~YEb zn$Sxjlym1d!*t_lB%t(J`X4|5H{gSYFsYzrfk$iXvcb4WNy4Y1s)SSE&e~_NnW>wdqHB`n zzait3fE)Ia>3nl4)Z~Ws81O6{Rb}T9zijDaz}Y^7)sdrlN$1xkutq@Wvy0lThLs9R z@#RV!-z40Q3i01tS@7w$(`bmxI+rM6>C-wwQoOAD(lXMGGN9|N@bLZ5TR2URo_LA> zr>2`T=1`Jk>Z|={R%CA4w;@hE!{%s9*YH&W{Wbpm*T%Ue?seRoxn}M8Z?eaM$UA^e z{1rEm0L$f5nIBpKLNfePunqxn(Tc~FE)(N>u{WrULa%dz5i8p)r$Q*`dW+83!wl!~ zbLUSUMsG)$JZ*$Iwe&{?AawiWEah@PY#AwkYBwtlr^-K@;J(lMyEC=Sr5^sYRi1#J zyGW{;fSDt$;^Kg;rsj?xwIpx2pP%R_I~3zPk)2Ve9|Y6)c9TG`&*Q@*@c^~)>u#zW z0=p)}u>;|(Wv4EuS_zK%SjjmGn{x5!#1`~vX#SaTf4fB@>5X~!8m?acpD~VSH_t`t zvS~!$h)~Ycg}NnC$49&)5p5Qv!(-;ABxHn6(7uhe$ra?}ZwaM;hjareT#fM~VHH?Z zYm{*afdFMIPG_{U-fS=3R~)lVeZ&SVMT8&Y#b>cCfe8@ak&QQ5)Wg9e=6zHk9x=h|=TC&{_m7dLZvkZ9z`He@%_(ET|{6hHZbebWfcev`sh!CPk zQ?~EX72&?rOY^`Fb|U(myAq|kRt(3-Z{0Zk6^c@xI%vka7BoDL;;hpsy+HOn_Qh-U zJBRm3sf|u+tB*(SV1677k(qH(2%vTMU91dw0qxXn!SH9ON0kFaq~@5%Y4-8VgFLOE z%e+AeY|^hBc6^#-ls7{pWKk>)X1PnEy1V4zu2Emy+?I}&d`Wq3@0vc>%&1PIX$qfn zHx4%+_oTL)o!6Z>spIK_aBuenYy>@~rD7treMlFcM*ntY;Z_GWf6SVRgO>l5A`z^nOfi$O|$ zpZtjo_iGC}3)ToaDV}KTH#6PO(J)HvXTCLkrb+2R`HIV^i)_n3N;JQ}ts&@VuHdg= z3uAVh`0njQ;G~UkBn;QfPmZ}30FbB}&uD{~9ZmlLYmr=3#GQJSzyc4{`V&!j{;)&= zwB*X;KHngVOw`+34aSHBx0>766vB5RmL#g{zh)yP3=Vx?F^1kHT+vcoyv%^*l0ctT zrF(=4_|c>X+ihYT{=V}mkZf*-xW&RURUo=%Xw2#RYqu00r1)RSTi;`|KAZ2m>;LS} z%DRB&`RN@8Ta~^4hy;gz=W9GrB2*#~j542p!T9WGnHcIjTNtg_M)oO+x3$uMP3?v1 ze2zR^$vr%dAMSrMDk-43Ao+$0RCd;wMVrJoAg~1!vC|g)VVDY!6jx1{Lj5y)ebz?@ zWq3O7om00DzYhDL0;R$ifUDCibH)m)%+`tbjY9e8N`zh+pjBZiY6V5%WkKWR5qXmF zwT>u+*Pf0(gsoTR0Lp@Kl&z)eXsm|QyFe)WqdI2cA1$8D!J?yBU|g-ON9pUZ?-^6= z$*ZDlHkWI!49a`G6NbjB)9Fl~z+@6S5$Mrllg1>BDs&5TkVsYyQK6$be>3QodBe3d zDNn>rc!t{}mP+x%$S-^`50)~KG&xTLFAp;kyM;&c29sCj1cM@f8leSbTR5d4Kpf(uNzyx7YBpYbiDk4p!5@pII6mVz1O*nUH@Xsj`>OzoHU;Ioyy< z;?<|q=w#JhQ^K+SRzKANh&EQx@Ub~ zDSP}`L+*#C<*jPgr2KSL_iy&5+^LV7*-Pfd2wc-$_!aPP^K)X}B_rck_Rs zKsPH^Z#CO`IO&f*8XU}5A>p1OVf7Mjzj?tz&v@1s`V`~()!om*(**A6ba)6|obAB^ zA7LYdlNRyl^#~1;oasK91kc(++kIvQLkvV-F9>)#;tNKrM8h-*T&XU*I1%c z0VoaV|LY(>01(DQ-D`Wvz@F1cM{>;(3;6vifB7dx)(4NWQMwZAA^}19B)cUgRVb53 z{i;%&yl>7g?HoW_#ld~V#rH+V(lGC_*Wzg%swnnIARBgh>Pzb$TLGe)V({R3ieD-WTmSvWaq`Ign_Ytxennh$-tKoAp~uZ$#CK*a?ZR@yG_B) zkBj+E@uj`Y#Neo{1^d4PoI$GBekvB>sdjQ2YWMq*_C42*N9_-6+|%a z#7yuUKK@>ND+b~g9W49WpviwENI-9urDzgkIL*v?F;&UibUa&g<64iz_nSu2=MQ|y z#Lj%x`Q3mdT9W`Gm-wPtZj;Ld`nn3RW44csO85E$%FE#h*yfVl0dV)vR2IV8 z0{~2z_WTZ%knxgV$12p;C77J8SSC&7GARamwBGhI|3kvm1s`^m)mhcZpzLMu)Ke*B z^OD6;C^3iI6IHa+TIG@baN-1tSj@C^J|V@)zjQB(7!+2)ax=z)Uo3&K1TwF!$M1e?sZaGHz>j5im;;VbEo3Wq=Ng>lAByWnt#;3GgT zeU--IH8uH(`HE=(ojyNG4WLgL>|}-WSe1}r@y=Aqi}jZuU_luT50g@wjjulGE&tBCxAU! zakvwVj;3q4-~IkK5St#Whxi|Sd#${VGbQk*JQx8`$uNMmt#M$shTf&P-nR`=O2v*3G`R{N>F@$I|tB3S1t1YF_I9 z8SVc))TO(0{xzVY@_mYvCrBxjVJ4~|d+&8QQ5y`0nlG*66qqmk{m zQt)mR3^ie#d^^1}EW{ghr#w+(;h4O#{3S~L5L(^i@BaX4Uj6L{Y=rtfC<_>RhN52u zy2&rSC7^1Mr`{Irf#iMJOxv(X700QA|9Cu84yn&fTRIUNB@6~yeO;2~VV(23Eju&L z{eG#eO1X8DrdvBRg3h~CiS>1*!SbZP8k%x;Nxmfj)S+%CmnB+}i=>c>sQ5t*;(Kbb zffZR=(dR*idqXAK5~~CCMdc3t1E>3B?rcC|^w-+`=MxKj+~^=MMMqy)91p;D#KaUV z^nJ5K&R>4!KaGk`Tsm5vYG`16S@WP>{=&tCaL)Ya&7b8z+jxU}o%EfP` zF$xNQvIoU@p;lso_pJF4RJ3|>C!7cu)n~!J32_M%D}x_1r!T!4l=H;6j`Xh&5Wl`_ zyzSN22{YMV*JKcDN?Y2wy$GV86(A1W*L1;n3zo>OL>*sSG#x&Fk_ZyqBJVhpEs-G` z0Gs6E4rJwOZ{TiEAYO*m9yY#Sb=kmI@W1Gpj2~Y z$AN31mUO}g_Qz>-&)w126&KOh3w6^xeu^~Pa0H)hRR9}L+2CCqF9CYOuA`=&VtBVb z6Y@kZCujb#j>7${C8%N$CN;9|^fXzs+{QFeBDtqnS-KjojJe323uVIf!Fdf`gKAHI zfZF{hmYO@B6prZ>6m@r3C)Hh*q8|RzVW_Fbmdq z9M&oawbx_(?~X36GlCcf`X?{~TFSrZ!CRw*&HI{9pnqejWYnV zrV465xGleq90g|Lsrt-bbvsp>$Z|e91r5VEN+XK$c;%;~Av6MSd(xbE`XtL5Ozr62 z1v_UW4QWqc-T18aT|@U$3^P)-omaJMMy5mS3Y|Zup7_3C$oo5B{&UfBKfj8{rWgHa z4r>rQm4Hj1A z{kE-@KQHF_9+H#9MKxaE_Dcs0rJnRT?`Sn5>jj`?Z6Ffh=q~SNb*(L-Q6+eN4nLMoSH6U0MV-U16;N0Aoioj* z$34+pmo$wZG4=_f*!zJyV)T^R9bBfSZ4M;k(%jP8V2anW2=%}ZVxFu&*X=QkcIFU} zUF&btOiOV>SmFA^S%<(22U$2WZ{po->paQZ_i}+j#%3Ha{+**;!w7`tXO|HnDw6O` z6;$(mnb{~FhcyjrnPcZQS`jQFu|V-Wv zkJ;r045eNLH(oqFiu1o!$^p>w^cj zqg{iJWx@^gKJSgozw?_0rU!aVKng$PVk_;ja>ZiHt`u z3Y_?W1I?v;HpU$?rXH_e@n1;MAJ16@Ceudc&IK0&k`tD){1KyaFn9(In_QZQI|Rd* zas9^JrH28~y5IYa|oA6{!nl0cr9oD$kWOwx!pd2~13`<`e zUA$lPU<3#A!{@<}5p7JbYmn8!RB%JhB(-HN$Sq1{MH^{sqTc)A9E$=005WJGY+5^v zo7Lrmo{^^4F_y!1anoGA7?8>NunKgTjhB~tuUDcKswr{I5Kg@@ewA5R6BiD>)I%`R z{pr+W&&-0W@APz7(IC+~yLFjIp7zdb*W{*(yj zU;Ngf*<}w4y#IPNsWjJK$|H+9Ljklh#%n|6ny38HpcvY&(DC(uy|hyhQ#rUCRz=wo z{ncUkB1vY+_2$#_N2bB2UNzt*wvL;<*B^NtKGAgSzfo|sPWu{w4gS@`saU3T9V*bN zmbM23?KfjkT?u6hUJk=2+k^{>0T)l>MkL$$&kfxTt3t8S7e5wUo<~xFyMtZ~u(U zw=jgwfz{awIt3|aOO8w?`>U+qlcl<__BU+r{*w2FQV=$K$AX{f{E6~&>9=Vxy+gA} z7%*QFz#ZjB!(wB@5)n&v0s2PNlBbW!#>U1aS)DDJQsKm{a&6V1M{u?zL0AsSo_iKW z_e1T1GW2PP(^fd=?U5)UhYQenA>)egsrM>M8Fo5GMys=jH(x6|H8%DZ8SY%DFrQ@0 zz>Wx11k{au_c9vx&knHhcd1OgDtH+=%lS6VYo@A%RPP@0l(MvMY{TGjO3x>?Yz3Gs z7mMTVNlB>mRD8D7YCo}4TjANrQbIy0qQ$58lZwrMqY(n?M2|McwqE?irg~hX^!;&~+gpf)_YWIR*Ig&Bsu5CiTT^evl6b59)JTm7h6@6V%n}b{ zX_y}#Z7*!FG#0%2YSq7dyR&QN6$~(NnIvdHeU^cN8mRJYMh%R59<`am8lI#^F(bnL%jA6RKwGZ<=y}l+N*?$<|C{0 z)&Rr-k$woS-}T}}Je9FCK#kDSWGy#H+^pVbbhp7^_dzRqUcYS|$gy;wGlXe_2lsHD z6g3@NSK@-$#-jYG^`uI!1DAoSs$477!l*4no^T06k2&9y8k`b9M?T{JaP}5ZQMPN_ zuplTU3?SVgAdRH-Al*t2AvJWVbf*Z?Eg)UeQbU8%oze{w(%tdjJPOa=``vrL@At1Y zYu3%oFmv5koOztb*-rf6Akx3hUs9^Ecb-&xBT7Mg)xh6701P1KSZt5(U*Zn5)-w69 z64b2SB%{~U{c}I|c*%MCqoeD=5u`Eg8HDPwzZ7a7IS3W~`9yIXi2LYRFc!KZxFXGg zK57HKFXf3tSwq%|iTup3fu38vCT~1#ahNmL*|kPpfuJl;Rd;rE{Zp1$W7b}x7tgSi zLWE!Rp8*9hm2hM`nBe{u>|=Ec2GOrI+x0a%1*TLKFIV8%p4*57+oYje2MRvrh}cgz zx(&b9QG>Q>*yFNO=UoqB^8~7&VVzeUpqP@|tfT-12xiC@mkj~l&xp%4BEf1`KEY8F zJ34$(R=GKEHLa5g)_U1?=3SfY2(Dd+C$cR01JYd&!{ z8D7NAyP$r4F^i#@EE0NVpG?`ygyQQIX;nWlfi^Y z@gGk=zlx-Oa7ytJ13gT1olg9PuFuO&pr+?7dg1fd2v7tGP#_BfirF78enq6i&es0y z1~jD8Tj}mO&-c3ja9N8B{p)iB%ICtL8u?1K6ld$*5|y6a7o@n?9QT}Fiw9s4No;?x zg=F-m)(R-XwmECg5sdrF3UPa`bCdB2q-^C8MG{XV{ya|xa7$Kv-f-jeCKc8G+MF6M z`r21>W46}Grh+-r0~GiQZ$^Of=YqzH+mlg(@a{Ke;;fJ5k-|YCnC16zfoNOdWDxeo zO@H_rSyj>XzC8txGbI^tpNxj#|mRU_v1h5d~Sx)yS8Hfa?bR7{1kc$^>wAcQ1UxsDkv z0sum$5wWC<3n1vg3MM%&`Kzd#T>OlER_LAe3-Xq_P6-RU_}+F@(_@jS;x~H=4rRD@ltDL2J5g6pC3asnenw zhM-=!@81yTeK*@Z(L^=HSX;~GUWh)x+n_@jDUbI5+E$Dy#P%HC(Pp>nyF?BKdpe=$lPF_5tSPlg(YAm)B#G3vXi-QQtTeTerA) zE;M*K?*vs=BdcE-CU%Wo^G;^O+VaC6E%vhLB_{v4@+r@-{axP121#&OJM!@NT@5Tj z4Y__CzT%^qOMfb-SJ04Q*b8f;8LWxM97MsH}fh@<2M4wYAYe+GW1SOCDc_PtDi|ByjM*Kf^m zz=5~>si+C?**FoPE`mpCI??vkwx`kwJl5}f;t!HGYZuW+s?0;j+~`LO%B7O!icifa zHP5rwE%W4@)%S7Z+-ifEUNWG*&|O+#x9sjyfEjI0O!hilmTDXndlQp)y}%7}nxxUP z3n-sd|_>~MA0Ieo?~*VWjE z9{}0P&Sv+s_xj6wIxllPI8^jsr~KACy+IDf&+TyaGu+cWzjF?g%ZZ``jNJ(4r$446 zyO;SX{TAF(LVd*vo-49IN}9DFJ||sC@JA3&1nog1{1yFnm?zi6F8yI}>lVakO2Yw2 z>_3vf7(LhK_KT8BIGxU{HhQZe9wn(9lO7^1xQZ=*ZnNC|c7eT_I0vgCr_$!TGlJ;= zzz}wCKs5>lsEMn)2GCYx=IJo$uJVTVa`ywdDFYCk*f!^QOq_MHN_#a_^Z1RsJKq?l zfAiv2&wOo5QeQdqXH=|(T`2M-k_-8ey&_&OrW?kQtTxS=aN6OZJS8!n`OA-Qh-83x z(J0;MI+d0<^M0I`&iL3CKes62(GP~n!>Tf|a|`m9IvdFmF7Hwoe|}hv+?Ir_tc>Go zADyNv0l=5p-yw|OA`U7+KIG0B&r;p}YH`F+E#WMg=)sH;GJC)TAF%hBjtv7W*Z-d((Eh@QvUEySLr*-QBqxG|`Rm8Vqs)8gIYn z#>?zAgzj zm#F0N0_0QxiT`GeeFvqQV%}@FbuE6?6q+3T+qC@e5a(adPwC)AvLQ4qqjVPUc>QWI~m z3pjMRD|C#=JdgQU3kv{W(uA3Ngq!DKV&Kp(O&a5rFrStopXV9(C7nKg_0`R$0Cj~@ zyK{sqjoH6XhGO`=e*qA`VZGKW3VlOR)ouLF&CsBxEuig-8f@LhH1H@#2SHjM{6Ns% ze`a@l5lRB&qr2Q|lFv5Xc_4xf+JIC4C(wI=oUv{lX{i7cye1rOz|sxx4%uCg+})dW z%ZpsvpX9u&sBcdOS6^|BA3@jmi^8QrUX7TmlNCia(>Jp#kdVa9*rtgX8YP*yd?r zw=zGM!GQpm%|YGP8p|>5HjRos#!twZ_x- z<4x5Yl`?6P6Xhq1Z$}LJF1=0kd^Ym%k~j;$mj~jGeO=%FLL;7Vyv$%VS@KJ%z%*}U zBHEe>$ZHdx`0K*7&FeJ9Hu*aeu0M*kUrN( zC;L0ILEAw9g7@WHhV;R^VxHgX2n#`45iGu0E26^tVbyjLn`t=c7AOiXz}&fXEV-XG znPk!6S3hGTWjvcPIn&RR<96!=enfB;O3JtT1*4r*SQkrSMj{4GBsvT}yEWyCI(4!m zq3R8OHTP>w+N>Z(m}8?vfHT&6Mlv{v;gYjviS2v0(_z=iN@Gn128GLs$6k=gxdt&* zJj7RBTu5tJ(H*)*hod$d>uT5L(RpeU@!&59r;F)WE(MxZl+Qwue)*vG+3M3&u;DxE zkC)MLo#(XWZ+gmEOfp!bh(Zgdvi3#_EQe#0CkN@0AHe4%7EJcKJn7tJNBUClekvrt zC#oV&wP+9n%s#HbcVUI)YS!!860GjGxdK(H1D0|cKUi+ zjF)v-xvdKlsbGfzsm7_SYw&0dzw#0PJalr^rLD@+9Jg12I2mU>hDC;v+j3GKo=rmP`p$m+`vMFEsQ`Wo&0_tg z^LPM+-4&p}rm(4^gb5_>fp(N%>{k1~le!(eItToVspO(ZnBRd6o6t=a29|r8dqUQ~ zY`+$&unFum$F`ozpI?1cen8@1G)}TJD-+ypA+to!vyJZX4-g=Q^*Q0)t#^@wiFEuc zQ)QoU7a-l24*+xRfx7(_4cWmE&=8`4%#QNB#V3mLMev{5O1ZHRs4Sd1Nd zIJSOo9b1&%e8}39DUr9sNZ?%qHjA6{B@S#@ES5G68jd0SqqgF8Fiu!;(hr;M`_mlL zLOKn5WVE?vBlSLyc$XOQobt^!C&1t%n4A5I4*aWOyO9!2jP70`j-{|{U^29+$V#Ox0r1}UJtwWy2G73HNs3bCYlGpV&|u&HC8)pCoLs)GQ$%g zZ2+Q&%k|{VIlw)?36wq9zG~x|Frhlur0-jpPIUaUBW|l^9{YjqNguuEG3w3qB`I3? zoMXeR&Ug2j$M36 z-(WN!&N8TOQkkr`YS{yC*t%I9lo6zF!Is#w5F0bJEqBK8*dk&kD-6g#nOE#)9nD+! z79(yq80^ow_f&6I$4-v8Rn#SZHP`z}`brfDPz5X&%l`aI^L@2`+S~OPR(LJVtbJWH zr@55~b9Li{b-kf}?98mdRHtTHnN)?ArIOWk>84|sc7SDK#pHmI2PYrsIJjcVWg|ho zVaMm0-?w}~!@!<`dfpEWb|hCynk4$6%lOYXPAc_KVKHEIGFp!h8t!-H90g3O;`-OX zYW9rGXR2g^d-i9YnhMrEHUi}NTVFr|afw8oSK^t@8A0UCT5|}{s}tlSL&HLMPLyGk zTRY?*Y%(DEDy$2jj0^D&8O5mq>PO8WeH9}rs(!#x72)`YYP>&~uW78Od6P{m?zY4w zikC~TOOEcS722b~x%KM3Lvf1T{K<~Sz0y2?L<~?C`hyHFFu#*Y1%4-GSfMboMOJJB2`iFfC_oorp;Mdc7-GUv*IONNmSMn}cr9hLwzcpsEnzPFrhaunM zQiH)-QO{70-sdS4M^%O3q5xIYaGgHCL|-l}yD=as*L$gC&$EpizDPDyMi4;-u!M+e zx(21Nr_bCau2aOvk+PgOYbfA}F*{r-z12oZ9Ev-^8?d=chf6bV?UVUWx|j6pY#V$d z`P%1ZlMA>patR9)qi@$Ya|7C3XGmSh=F&0?F7|Blw5kS+VDes`L1oWv(Lw1<34$#o zHC^&G_yZlPu7XWVs4HTws%km=U+0S#o~`+)2bDnw+pGw$vH|rq)+)q1EY^%#G+KMB zq;HSb-%8+ryb^`wwczL+1x8&edks%33}njwEan##_!18@oC@@R06_(N-wSU&n)UDi zNf2=s(6GWNzz#wb?Def*}tYVvJcBZ@mOIsu_*;aR&8LU=n&jxt~Rp?mA9i&o4P zmAq^$XR+Jm8I3SUvF>hysS0ZWiYh{ny%JmXiH`geT<8;>NL`CUnsuM+E^kXK^R!x7 z-4V?gE|b$t zINfm*eq8cw#3&uk$|Eg0oY(q%^RRh0d)lo=lk8YwG||4i{sS3y1zonCLlC_gR=CN#=0l>%)8 z!yZj_m3}`&gBkP@2c$I5M@2D0YzjC4DQ_gFiC!xwSC7E_(`sSJ( zSNAn*98)>B$HsBppN|at@Egh{R5^n%AHk`sh`q<|qL?$AsS0H9@fcy!F_IC?A=vFQ zHkqzyNM>s1h(`L_mUNETrf$tnRy7-gh&g*g#kt-;;Ji^^bjY(|Vm@B*K{NXX4EcY3 zq&!9jxE($ki`o5qI1R82UPymsxzPdqNc%)L?s&yZWXy4KB1`CvvgwGVo!ps^Lylk* zsK;|RWS~S1Z1cOKC|{-5h%G6}k{|m~W~zi|$LP<1D~gwga;0Ovw4|b{`ufT;BM1E4 z$ng8@nQqNB3zE2MyYFgewxzpEaB_j5-62w1a-P^F}0mRf~4xZ;jV&c8+t&CRyB+K8)0zpK)4EnAVU0g);5> zfQK>!I7rw?-Tty8QG8i`cxfR)mzlz3 zIwmCk^9qq$|7DuqaO4Fvn0Qf1gvjPsU!AR6c1F z>fCsaX@>?kzPHrXl!wZdT;R`0Pb!ih<%9y&^+L+)zKni21ZKrWYVH@uwEKAI&bL0o zjr`Nl%hAFOXTAv(PmN3!&R)a@uAd z{&=ohg0smrK4ob(Qdnn4$jbPN?_E%*-z-3_0pqlS* z=>U|%0{Ay$t4W|f7c(In#DE!oNcJ|3DGp$)tvQ&=5L>1tolLpb&`~i}iH=r1?IGLW zVgY?rDP}U+KLZQE1V5!Q8qCmje|qq$6Fw30U8zQx2tf;V#)TcW@sT>vazJ967D0Vp z*76~G3D@Pr3GZT{6nCl1``6@+@Ex&=>}ecV?5!Xwqu5>uZG$XzMi)E9%AYn5dl~pD zCAi-&5L+qSnqsHM+m~m}%g@q{zY;3}sImdKqZ5U>|N6W0J zQKs*|=uBqot68_!H9pMkLB;r!pYBgK<9{f`f0fO^2f*6c0L@Xg;CiAF7{19j4xXNOaxn7y7^Q37UBtwMh`&P)3gHN(J5 zHz?5`3=@`wC7n_twS#DSJhqtBIYd%Y|g-Qp039Sg-=GfGWQD z;}TPc>*1`Kw~;D^8gVKI&(MA6&{9X!-Wpgga5j`v;A!g_GHEh?@H zlxgv}e|9UL?IAMR#hHIt8xWFzsINvZd$vqNtI3Eb4j9padlzznN${!k;ghXa# zp5|6dIaSG>3}yO(EQW@9i)Uu1$??;lso>zi=B6LPH}p2;N^F=9WagP~13?ap(}SE5 z`$akI&C$E?!vA4eesFmWUeN2@L$P{12OpJAc_-#0uub-Q{MR~cOk^wp3O=QTGCRh< z)T&pjH26rtKwv*}dg}#Xc`=0YEaPi_)%B8#=jga;OLl`#1Kfn6f`n%Veu1)njvD~l z;GpKQUA(NQDiRPEcZ5W;F)%PVc*w;oBM#AcJ9+N8Yx>V5g9k$&7?6=#67pzA@4S*zcJtjN1A#Gzw+8;Orw5! znhL0YkZhA0&3Ub=zTCAL`4~o^ZDc{6DCSZL)J^|H23{#kw%C;_^gYISv4I5N^~L@skUB2iU2K~KD!hXY!g%f0 zpnx@04A4KQCvaId*5KF)GE%x6esRkqF<&Js!v01#X#4}wX75Si)I7Hci+=C?OWYphBQm1u85SQ<5Q6;GFp za;@%W@qfK|^a&jKZ8zte!6I&`sz9#UF8LSet?8eQ@KZK%G9dCYl8Aeg`cL376P!{! zE~HoU{&Z&+u=jt-BZuclp-80khqnRI*x_82R-TQC@;o4nL;-pqd3J6!8UHnSm&dW~qGvlXmqWV3Mwv8RUyTUoPAQ6A#zA z)>;1W_(F1Yxu0)0Dep8&3xPu_R_#qP?3r{ZGa})o=~Df1h$Dli*;0}@k}F}2=a&EF zA;Uo9=);A^XdO4b9v?}Io(ba<7o@F#bydcSEX#=p-l7X5bOGQ+8djTS*@r0(+jFn6 zE@&D(l4K1^(_L%+j*^4C6lqhAg)-g!l!gAx$)PllpC3BO~5EMV$#UuQFKoTSRMwn@F`Bj%1jTa2+<>$hZ8x; zsZovna0Z=s%px03&rzZL3 zbTG&KXKyz9i}OfqPksq2h5IbUfTCieqgP<1NB_}~|F=W-qQrhG1qb=z6u+wfJe5VK zzLpT3GQk$u(8VE!f7gRnQ-Gl_v0jx(2I8^Uds{cpUX)u-jvP*k((MNb>QI(E;$SQG zxZ%|i^_c6E;Mb$~yZU&?w`dl6&y5>sN(R~az~t*s`mAmvd4dmvHv$O=e}PEo{pmCB zcFX?^_y4mpVW^lU^-FVqaBDH z%ElHeGiVEump!@$nzZTSs2sIoAWI=hNm77#QzeTAEuQM*VcMx^5f!dZ*r{DEqNJH? zzf~KBRc}oocCF?5YrjE!g(>X3U6-k*c-rT%=+>Liz0T6XFgu_(k*Mj;ZoT}oZog+> zF~h&R-9{H7C81~Sn%qYdDD=etVdmFth(!)}^Dxne2fY!&FKXEZIc8^Pqn3QY#lfM& zB)Ckb5tOn>LXhl%-_noYPRNery}0(B=?6)>0~^kLbKscXmF}P=O9+RdA8d@fj?n;`lIzZ;(LGD-KapxZFB{w3}!d3$-mYDB%cvs zVRK3(jIy^s44OdrYeX8NxRzH6WzbKLHuJ*j{;aT9KNXma;-DAVMfCRb|7FCWDuj4t zun{_L+dEU!oT#X%rxWe+FLu>`zIG%g_-k}vTkLP_uLIk6Ha=kJ9->l4huM8Ly3Pi? zt3iNRRg#3aP3+I_ypjVtWC1K?Pah2YyjH*8)KmXbSqDVS|K}z}>AWT;G_u1r-4L@A zwJ2^E{lD)uBtkD5?6A1|eqXhKO@xSuXr>DarQkyjzCA_c?~uWwen9tm!F#T7c^)9s z^oo$ajq5V2>G-%d%1vJz{yz(*OL6a-mWoQmG8p$-f~x=f{Emmo-C7RFfY0G4xcy&a z5%b)x$?xs*AD%gwy=XAQAU@g8ex{{SeovsKBQ>8w^(+Yg{duqwmZvVU*N+{zIn-|( z7rt2=245#&M6pL6SlHOqJUl$=a>b;#N6rgG6BZGHReTj%1Kt@MQ@2yK1!&5WDedoW zG6fFVLY7J>=>HLH$`P(f4LPW3~d36H6 zgPhjVeWl>+>|BPHu=wP5QCN{y8KJ-`a#+u3CAyGs^rCv*O*rrGu?$FgrPJJg{=Y4v zS1WD*Dm+`w29XAT>xMzF2i#Y&KeujT2Hy_$L(X!8=krL-IVX@jw_hAE5L+&;tgHm* zt`y&`kDmCwzN?IkC&T8O*kh-tdR+O=)11Z_16T55Vq$ggrtWq)NC2UXCB^N2(9{OI zCT!_Z0>Ll;dvM zR;hqxOM5`Vbfxg(g||WNfCG$2|Mp!tIq)@UhTHwRM4P*p{_BO8A9X(zo{fY!q(W}w z2SBg0Hn;0X!e;)rbmWBRy-(l@e@SDu$>6J@bN^Q;Y2=ZIzP`RMoRSx4>2|h2^$2tK zzv21YUP~mWo}4%a1P4d2t(oQI=l@9Hx%)PMO8B#L&|6+-gGL+GE1tdkE@AQ%H!sP3 z53N)wSy|;8fG=4KXWssHPP~w4UTSIOi)XueBaza75Wn51cPsnvE-3yQlJmhb*sR`8 zLuvkYIB5x4homt6lD3E$crMO9v|2+^jZ&cumO)1vv1XGYCLCqJl3Eu;U!X5PAL-Xnwu{&q?J zKHSFe!8GKh^}?D(ql6woLw7$Z3C8ZPhjT@=ArH6Hj>TB2I&!cjJFF&6M<*OT|A)QC z49|N{`22yYM_V;1y6s$pY4XF%^1|$l3`r-as`#+?Pw43Ai2YgwBW}lw08Yus5EVF| z$NPrIns8b}W>Ha?(Dg3vcDwy`JSh{u0lcC=7ej^6O+KxBwh0L$6B10}jX#@P8nTXU zRMmCO}GUBs{=ycNmd zA6WhM_gsD6pv4>=HOF0&k#KBn7BfoRZfFn$q3jd?;3e5UBrqT#9PoCe^z>4HE-$0t zvoh4hfnxv29`X_-Wo6|r#)9IAWcTXt-RXkgk|{;dOBX>QU6l!pDuD_4zP41dFvCau zh8)Yr5cJ73Jg$hcBtD*Sy!JdSf7VX@#4f{v^B;KN6eg?KucT$ix*)$ld5@$;oN#ah!k<)5TcN7=!V zuylo2Vi?R9$s4C9Zogcws3UmR9BZ1Yeh-q|7peamIW_Wo;qNmf`p8QhFD!2M1qo*q z&&#{r)qpJO{i!?px+#UOfd!RR^3Mce3V(}c0U=*u$cOQqf8t4y1gJ(4txuR37$SWh z29upkR;Ya^z2n~hl!iD_ z+dO2GSF%X(KJ+j*vn2Z@?6Hbn_gvKmy3_HZhk8ek4!CZ&@9lRIhJpcUXvWC&D6TxdwH7Bdm6%Nc(Tr1^ zt9-B1ET@o{akFGX=G{AnSd~_;(AW`Ef_E8dFQuhrGHNfrc9l#GI3m!a?x`3s@!6Ty zijQOcC6$2Lmc*V zxz!JqqmzaV zNO#e;TM<2dSY5K)llSYYQsort=EDx285pEArk5WiEdq7elX0vySX=}zUuu-~L~P7n z^}?njEE5cmCAOtp#m#@Yx0L4w&BXl3Ot2O7(63uG3&!&%{w$>S4wohB;}o%Q)d59Q zkRV#@Nm+IN;91Hgep@^a{gB#OO8TJ@C(C4=lKs`OT!2Df*p}MWj47EatnRc#nV8q) z;F8_|ZF6nYp2t$|@P$9C!W9X*y%x!a$!{cP1wxmKd(K#HR%k#4BH{ z)`_koq!$s5rkQId<}~Ra;&w*^1_5=k0qrlFF71$a<*iOL$4j(|WlnWbn-dgF6HqC| z(XGMx?%mc;8ho83S|>ssnrG>ct;bVfsXe(mqH!dBRbWNugLhF&@V_^e3Fs;3)^#GU zU4(gIl{f%lAR|oFXSrQ9WF%IUY~++usehIqw>Fi(Dm*WEiZMpS)5#mN%7Ze<ZyUun}(9_rA7c>tH>GtvV6TA-jd>2!Xc|T{IMggAWE2 z$>9M@fl5(bncn4iN%Gjf0}Fdy&;lKveX)qJqpyp*B<7UVp@lC8pzN4+3vN#TRfD_HEG5yFxs-TmXU8 z%!i|B4&^vFCF?#8PiO>RJI}hV6dgJhXF%4{0QHJYqn=9v8yZDK&|Y=u3Q0^vfbs~r z(=NFU%ZAFNhFN zrAtjmCxw{4?rDpVNySHStH315IRH6Zh&apZ@&&?bq}}@Tt6YK;#Cq{xg^C{X>h|Q0 z+mtsVDs-mS>D|tpaI{>d!}biDNk2J(psS;gEj*+}H>ug+X(X5K*Kj(s_ZfuaZBxiS zFGmtp)X2Deb%`?4Y>POG1fPf@c9hud>qR5x!;bt@S8_S)^O|i%kuzSZ>FFhHOjl{6 zprAl6&xon;#z9mDQVNUj3F_ZZZn|DGna;3D8CFaG8g4UTSCunKUw%`S@9r3n6>1pF zqs^P-mK1);p!qRK)_`v|k?xeiBgQUN=*i`_`^&>}C&iL7Qm0ztvn`?y$U#9k!Mc|6 zejdT4P??FBMj!9#flfsYWa6ZcHrg>?rKo=JFhVL~#33wddp4adYxDG{8|1QInSghZ z482(6te+PXr#EnTFZNowqGMHJW{;ZwJf2ypQZE>sA0zlCiesOAW~gn|sn6UhhEz?P zg>NRo(7%5sMt+ec$|Ajp6=|@x{IHLohHg5Pt=R$lNtLETi!xcw(vrv1UHsmrSEEyD z%{HKT;AiiP+Wd{62iMfig?U%g1zf zN=FYPP_os+5kwZUbie#s^JhbXFcEevB*fum+aG_Vn?V{GqGYY9n&x^WvOTo^`ClAJ z4s@@D1^wavm1GZQAg2)?Bc7FmPQu$>?{@wZplVef0ty15Q0^Z<8NgQqmL=tMi48X>{1ozcc7P zA=S`mI2C7!>83LsZyBT)-=p*i&1Jkwmr~6b*$}_HpWt3uvvFCWn(O&wk#xrq(~bWj zqRS;_SpOoGLxlBV>QG5eh4j{-ScC!e$js&f-_CX9(@>P>M*s2tI&wS8Xi<1)t(Fv5 zh+QXPR!IJ}0$_&Y6LbkiHrtaxzy0_?U8s^vAN8ZW=HRny&a0w^FcQDj?Jw(B zDM!>$C?REq75#m6vDYEGB&yn~^zDyFoSTayj`#IDG+|>9Fw7{EK31^VK~G=yGX)lV z7XG63OZ?^H0H)y*mTS*n-+p=I(CYexv3Rs7wvg#_LSOr|luJhfI#s@0MMVqxm9sTr z99BpsP6odj%Hn1W`ByE1^x!5g`d;QM#tdbt%dyq>SV|y0ps1md>m7TKOz7i6!Pu`~ zzapZesc#fi8OLn>6M!}wN^-mC0SI#pq8gxAl_x^cJPDbu=NO8`9_7l*R*~_8B8r-j zT;|eGCr<+8%&2w?YNTG&z(ss=%WpP53Tl=KGobvf#k|C6K>=47Paa; z!@|Nsh!mXBis`zumE>f;UDO5JL5gbP(^s5zhC;jx{%Ko*ZLyv*GAiGnEinw7vK^A6 zU&QB{doK^@GiA?upQYQZP(c$tAYkILhZJ zK^CSGL3p0!e5YtRTnp=au|(dCEfpbO)5 zohz!hs`EMAikFX16EI9!faF^Q5UOSi)gzm!_KDg85)kz7&w)mAQFCZ%rGU@Z`Bkqe zLzDYli2p7Boh{*s@WKoH%a7&Bbz5vkXFJz&sPG%VoHwVM5rSqVPYwl}lFb~^{<4K{ zmJ|WIKkb=-XkFp`?nC>(-MYp=&r?WYY=KRXr1emGY2o_jzfmec$BA)EksD@_T7a>- z#9{k29T4sToXKjY?XKR9fJo(C5`YKe^kCAk-ACc%T_u>`&p@x5SpjE`T7`2MM^Oc0 zRm*ts6?0#OX?U1ZT$K%q$45Er_bsOtBsq+qR>;d<5;ja2iSUgBG1w)ScMjoLXx;O;j>Si91JOv^+^!MYK@54dNX5qZMO+mVrZi}wIp$r)#r|i1?<-(Z??UL74 zRxJ-PPA+P-@ZhMpi;Mm_MPNrzif6ZNQvKzTCZwWptB09@fPf94{QWgu<4{M&bx48S zO4j&^oKa-tnX4(Vwhth6&gEDsHxy=r71lZg0?uWEzWZ}zZ> z8#3dOrbAio(kM3@Hf0wH;9-(z4ZWsLj|%Ns7}F(qT{#VapT2jM0kk_g3u)de+-n1k zEIMLPqusH&hf{%t`Io@~rp(WJ7Bi~C#ZVz_LACm=WKYXmuO*&v!A4F@*;V6P@Cn*< zPe|EYKZW3*A9^%wqOPo~I;zf(p^X+Qn1!4wo(PIBzeVLe z9-cW9cirjq3u&-Wq{sAvbBD%At<`JsM}&aSF-a8MBf1Z|$s&~yT!F%!+lv!x`wwvwASip??(%zZ{r zS^BYU@B!LxDykn^HwdZa3*E>kBJXD+uI#(M z*NWBVHO-l25kUO0RuCO==tIcMwA{vWhD^$eEsYL*uFh8vV~+dIWzB*r`TdK@d1cnO zU3>d=WK*F%XkL1)160F5EK?v>TmtZZI;LaeMX}tr2@j(erf3_eH}m0(>eYJS z(fA(uTcl-5)w?nE^hc3^)Ww!2`~>~0AG_h@=$;4xN))^ zCL~4I={C(C2L6UXPC9u#Zz=uLuz;~@_PNwAA>oBVUWh}^;V0aj2v54a=q zncett#gZfJ>^)FcYOwu^fEZ>RHo>2;JuocKd+_Z&`Ya?bLoA&Mmh#ufjEt+9_lxb9 zD({rUHy8LBLA3(lO_Kqugku4{e-3!~yTbFXT&w|4h?&tC&AkLDF_4-5ffuHO;ToOEe7=pXxrgNjtCf*w3G|}alxin1sOR{ zQKWUBk19yqK3ce4>Ueh>NNHC~0pi{Exw$v^-cmv4!79_ktK-a{_?seOM&(owsF1$g zV|D8vkgs7!gCjs&_}X-SB>lojQ)=yV0c<`wD3!_(P~LfrP%)wrX|q``iiEm6HX${1 zGX4}_ThM;oqZchBRH3mxsLN8P^#aSr{4XEo>e;5JJ+{H_;WwjB}v91Bqz zxb18GpzhtgZUdmvqj$y9=eMl{0Pq7;7H(u@lv}o^4ci`^6c!5gL#x&bs57z#{lF{pDsi~u-| znu@1K5l>cu+KMQEV^#6B+o4Jozzdfss^89^#h&ztlz(h=&5e0mN)-2tBN|ELaR4Xh zaI5lRmon9`hNRKccC%axnmko_c99oGNUd)`Y+)2K1T_9#uB7p8_sLH>As2NPPKSu5 z1BE_ir1n9J_(+W-{LV#>t!K!mX|-up;UKOW)f9t-6gQ#CX`30Pwi^$iZFh#TjK{ug z<802d|RtKCNzU>2KTI~Q&spUElQ^2i7{sJKGymk8kjQ@DdqWCPbE3hNk zT#hVw=6$i7b>JYZYddu-;cm_AMGb{)DEd(nBz93ZK3=$hZb-;YgzJJljQv+VFb!uC9V##g*qDF zqb?0dkm2~(dFz2Zdg3`{R5$^8-3COc*9c}%@z;=cS^!h9QTZC6-@EWcgtm|H8+JYh za?RlYpKA-;S0LQA2N3AC1DvW1!TT>;dxW0BFVdl-1qJPGbXO^XFOZEh6?A}ByF2_meTKwLu3RQ{w#Ar zpzS4qie)mZ2Kqi^DkKZix0(ReZ2(K85dh9mZh)IR_G@KTqb$+&Z?nBNh;NY$+8vaU z?TH^Iw5gq=7vHqP#Wt{LQjUF|LbF~s0h@kG?vhAYQDmPuG_lLUh7 z^4ju5&wn_En*}K^FLfR_)VxgO)9T8(boHRiQEK@E410;-y?G5{_#+*|JSBgiw1=6w zO;_8k5#qBO$-ZO{g|IOCxA(UKL~BJ8H(k;Co3#KiCKggS|2S1BKV{Pg3^lLeCcj7f z%Ae1r$bSO8p-ywMlN2xG0fLB5N4?D_K($^^ZGOeuzta2z@+r1Wc#0)PA=nS7N%@u( zp)KXZTC!Lio)jGi^Hz2B&-F#SmmP^nnEpGijMy5ofvI*(tA`Ai+2P3P=e$-LY* zA|0w)iB*^FWT#~U9><*&=Ri7Nt%-PUYi6K|Hxj6#Lv>g7^Pkn3EH{r`EM3nHx#2xE zQ)_U)RMt$5F+2j=l0*X=M9SH@+F2$q@9i5tKwP`PFMmVJQ%94CKdvbXaJe(7<0I}R zkIP9VTizL7H?ow?E0~B|Iwh{H+ZFKmegZ@XvD~w+N z)V@T{?r!7!SppH|y7pH398Y-hZ4tgWy1}nO1uIgM@Qj6ONc|8qAhakVcg>6n6;kkn z5Ymc<6BZRi#+9pf+7?zKE63UD4kcr^g-XB4`T@PNZ)|xBp-nX6AY*ulccp+bn*Y+~ zv6$cgN7`G*Mb&QY<1h>*HGtAFfJsPqhhR_&2q;K*cSsG5k}4$)N_Te)NOvP89fEZK z?s<-So^#&wp7;Ct{Qh}9`x(ZW*?ZsnUTa-|o}K7uAOn(wgZkW*6j=0Zgds zoQoA{r3jgqPEXnf(x8xH-%*R3S$2+f7b&GFS0BzoWG$~EXK1ff57e<|t!Kz$N2@Om zoxII$oTOm>R{sp_!Cy9X- zhb*Ogx7pjN0Dbk)^E<}gei~kBnehO<_|%MdJYFuyMZH-qyPqp6!e1Y4t5__rtmLq| zA!QFikbbQ{`03Gds>W?Z_#MR;FBpOKXX^Tj7b==Lx;~QbK34)GB{ixM{f_w+A6eju zNfNPnjCW}5zf;25jg=WOps|~zIKEaKyTv+r2Y_@`kttiBUS(v_YEe=8R3@X}&Lm>J z<`sjc{?_>B91E(I8=lq18(-V03ae<)M}A~*UcEo~WCPCxsP=l3>cLxns%p94%1AJD zt4CwgCy^}YED;wgwwe_I%JNmYYDE&j6p)Ej(>|g*o?l78epUPa&v;`9(TS;$cC9X74((fB$w*1#1*;bAgFsKf<$dC?EeTYzy2$Bm(a^NH^n<+x4Dw3 zp!OMXIr6>ggbz zZd>I7w8k6T0zf?XcJl^r-skRFOktOH>)tK!TrJYrAZ+h^^rO#CJsd;p&piF36p(Jd9rCXDt9mzQnY?K`XTb` zyd>tQ2hU#zSq!9ls1HTuzL&otD}yVp+cR%_Yn5|rnf|Yh%ZnCDF?hx9w1Si|b&329 ziNbC`Q=f_Xvp)a%^XE;#NCgGmu<;!Vi?#BDXu&2^Dj;<1w%1cWLYH?ALY;~u3bgI= zq|fuY)?vKEsCxNQRRpv-7Uc_M-tBPQ3B)7+n~JsTl3ATo%fnKqHe)X5gR^TWR;t0Q zV^5C|VcYgpi1LAe58|YJ<>+RpR#Lv>=%ThNlv>>_@VkqgbZWlp3S30TE23BTRNBI_ z?j+d1JFWQ|+5}cG6R<*!hbyTkLyE~313G{^!I5K6rbWlH8(6=Lh*jWg_G!{VJw^}& za{4!38D93+y6M;L?b!Yi_UIlr4(;(t0e7;0Hq?>pTnYvZ6a}du#r_nq`m`U@RV5!O zvhlRm{Q_lizPj=EYEG*gbsOUS}W%`&bSk7Bu%WyYJt2FIZ+ zZW{PUVGOy`Pj;y=SErBnJNrpQ-jZ^U3s;Bo@GqG~coz573dQ;{Grv=|EG#aL#GMjK zxdYPxoZ<+eEhHx$Og3_{(N2bh#@zAR1$ zAcoyKJNgmrxHVbDNU`JSR!++Liup(FUT9}wun0#Ww{~tWxa{62KhOznDE`KV`nOgA zFO-6*zC(_**+bRzMS8qL{;sXuEzCVDKG@`!*49%ewy`N|#1Tk^tB@1}r$v>Z4y2fS z)jY;Z=?usPlgz)>s>=g~u_~bEtKzi`ViAMr<#F20n>RD-+%}Nvep%*nyrXj~TM+07F98F{XC`xZa!w*i>5L-=VmYRT1?(VV!1iez(03*ygh{S zPEpZ8!w#p`6JuJdl;*O4zBb@4{s{=euTQp=y(v02)AsHg2GR<5knw5)(zH@OW%)iW zRN%4uZPC+J29w$Py7Mh7PdhFjT)K~FzQn6&`P9=^0Eta6_7(yFQ|M2%#uX<3(R=st zO*Y4XH~|O7r>O$bKVJ1qn`n#R1GoI_8$U6Yz( zo?=`KH?17kGT;Q|h$M69le=z}jp?rqe)is|1e{OJfXYxC<~9kynaN~Oj4e@TJj`=! zju`ax9&(k;O~xzn!gUwZTHt(*k;gA211Iqj?}pH(f8Ld@Y;Kl_1?IV~<&|c*MU#!hjk&T-QHSD~wZINlNqdIapPTu*Ft7pq)_yVhSj7?>6B$c(^e}uO2E%`Sf z#eD*FZ6j&Di<&TbUc&1Q;g=Mricg=WoZmfW>KG2#69fivNO&%?&u}}#g?v%Sel>j3 z9td>DIq|c!T=@|A?%_6(yZQKY=}Y=};ZDyV#a<=i42uq29QvIA5BQApFo2t6w#>K3 z^obT%e*Uy0_x>Zxzw^lct?IbhZx8+Ga^q^q{zC6}==po)+`j`AV$!3iCkUB@04X=v zd?j%emvTn`?MZ)YboU}+E^g(iOef%y@;DO#Z|ApL9wrW_Q@fs;4641az-DnBwm7F| zw!;85hHZR^iqfrUf$;^QJcH6pPNU9$Opr?w(fkI4)H5`(%)dZw2&E*k+We5t!17Cl z5V}Dt&$E}Hy%(ZK3pK!U^gCV#+T4ob->dPVVsUsINC9)A3AhiU99XztyS;M)V$U6{ zb6I)$(VC5(CR{`+tiTwVMr)q}cfjjtPKb(AvJI*+EGb>G_dLP;tgH&`r~5++HyEs- zmZ#3$gk)iJhFC}4{%|WxirfI&Q*b zu`I8E6k~SO00GuzH^#2_HmwM&(>Iq4H{h}oO24$U6l%aM#^y5cfRw+?Z|ftA_x$b& z6_+uLN07YO)2kh6)>R&-+W7DYvuVSSbJobZpz*+e;~B`Wrl7>zXn&O|wyW;0p&JY7 zahA`L(ChH*pdEV6Hl8P4T2OCgKwb8FcydS^&sMt1rwounehV|8l8Y$E|DnE|N#l;4 z?uARwK5YljMoMN=+X)ry$olY2BnbcPU|2uVyN{;BcpEEm)_D){AIa|F~?Sz0}TsQD=-Y;bbEZzeF^k4zRiD3gWbm z73TB}@o2f>m58Dw+5P7Ks@tmdEn%YS0z zzsZOH?G^ZSEU5&qP2jloMzHvZD>B6*(5F9ItXSz}$`kqwscv5kK(<@b5{Gwl#Jv!W z&-4cbPQJfKSO3xtVcw^mV20O9^sj>b9Z9o%>dm09C&5Ff&(-XxuUTkle+sN#w_sr* zRQ%7-ox&)%9|uX3Fsmg)g6X_$46p+Iyf7Eo1Am6wK*_QD6|nkY`)|Cg_M0NMaAh>z!R+g7~p*MJC&M00FE4y&>{`+@j zmijhgB;5Px?V8T>ezwincQW_TBZ%AlyPtvBP(gGh)XvB5t(|wWZs4_u5Xf}6 z3$&S1-%Rp08yh=i@6v~RO2fC~S@n(hPgm0-$*|SyV9CK|IH>cmhFCn*(hgkIU9#ed z1h9@DdkupoPoxeW+A-x*Ex$U;25@j1|Qe(!}QO{2B!?;al7A0I!1b|5W^7|oKAuci5CEL~lUJV6e zpMqYaZfnBm7hKy8LiT*R?{X0ZIzn!oCHU0@B?RzN5S1E`gsYzs8Oy+leAc@4)Y^p6 z`(8~eSbLW3IVj@y2~Trs?-=c90EBY!1Dwp8Y}zw?WFP@O4d3Zt!yPfr=|GL>6&BVC zcac5Ac0OEP!I9zy9v686cXrUbo88Tlz~hkX;8L?)P=M-*B0}jqw4m|5wEMdwBW#asN0p z70A8XK$tl>ON!J5CxiHbG1|_a8FQ{4QoQLmcQpASCaL@WB2}X!L=e0qBnogjf z)mY3=DF!6PRbV_)>SPS9{IE4+$Tm)_$0h{du-+;)0Bn0Eyo(V!t7mj_7DBOl_P zJ?+&XiNy+!HJ>as@n(KJ+3g_ag+WLn#f`-$)0oLWe&gan_!b(0P_mRhH#c{v$oeUp z42)@AEc_Jd6+P|;*VKO}@f=hCmRCo2{6*8#enZrY+U1XC%Kie-6p2m0s&YWcy4Fhv zb?gX+L?p3J(1cgvVxSU2lFG!Bfz)}a%npxtVh@CaCCVopwt|ORB5+3T`GA3=tz zd&>egx4@4t3Z-Ym(#`WX;wygEY@PJQjsRjrmRM3rAfasN@k;GST~nqc_v#nX%Ws@@ znUfpz+lj2OAo2aT%k@=N@vk$+upBnRAN|L&TDb`rg)s= zq4-n^k3*b1V;22z*e)b|NLXGRZ>D8mJO0-m=D(mFe}U@%+bdjbh!~7~(eK%;EG#PS zj~_iUDXw2DchI7!VR+H#??`xTYP6chv`f~hM_cSkXZAr|D1Ac$p4I!)KUmCAlIIq5 zgue2+Hw_C7XSDb-3`6MQ!Aj5MvFtnB(8Yn4+{u(5@39Wjk&iY3ZQP;^hM4ZjYa5$bc zZF*Zap*OQxBLch3VN!H3+A)k`X5-zMDqIe$`C0~IwB8b)Qk)1FZnG5fbDJEzg2`b1 z;>x9tTQBOE?%H8t=v3Z@-!Clz`bhaHtgLb`8M&58#f-q!d5=cTpV;V6(~15)+`pWkU3Ol z16y^`BiS0)^O@!C6NuKM1}fCcx8Tl9wUiJyYpIe17R+b&`cH?Nn>sGAmy!n-kOPwd z8rE|ba8-V^;K1!irvb5My+__o|G7`>m8CVK_6zptf%aHO%-Wdu@6&u!VP|HdB$o{{ zv#?7Z66WR0^1j9YmVx}2EG0Pw8zd*V>V(>O5pwNQ?>__S&E3OF?MP0{hYWjO2_Y2R zjC0Ad`j=j7xER&c)R}L152u3q?D_Sj3puf5!bfm1B7*qsVyc9^9~aGP4PCVFj<=DIbU_7r-!^2Zn)dF+!L4a=F68aRXy6tB@ZfzE7YeX%eh$GB%*R|J&96#Td6U2 z;f?a-Ej-VUj&TSvyzC)P<(ErX$l1%+;u@nz?JoJ88yddhN+pPmd; zJX%Dcugy>)y%;M_@)-<7%5vIN1yf+~eSxlk8IL-= z*zX##y~935q2!!xD(ts(hmNjkNxiwxR62n=A5$Z1+aZC`QfCWr_fU%N^9+Tg`}Kv6 z%FXCRfgF&sNC$|k@Mer}8}Z=Fsp7*2M_-ewNCFaEmSeqF(kI~30rM`tva-*IB$h+eaQQZP>j2-=D$~Re~+awd8o!03*RBKan;{Q4`PluP@k6WT|3D+6N38}Sx9Uj zhUGw;;<6uqEmWD9&4}7;C_UucCRc#s7fQ+7MZiq4tJt7Re=J|~uT*M7JKrZe@4$Fh z6@=uxn)p#o>_A7r%2}7u@!VkJ_1$E^y02BF>qmsU#_s%{9T#=w(W6Jp>+w;9WVmhG zp~wEY^7v5yJsnn{6NK`}fR7md&^UfNOZ_kmWG(Q9I3l(`zIC*cv8m{hL zpG6G=MH>|v(CQh!udlN=%Ec5|4cE6eI@XxmTkf59_c*9p9sK;Z)OeuTfE#N&AekU( z5e(#1Gn01UE9iZxYL>j7`qa(C-X-vEe*LMb%gItSIypYwbw3y$;=D2xshkzP;4608 zr3YFq5^qs_SzqJ|=`{PgCP+#@(*M$0N7eitscn`OOp+G!<4hjiLw(?grp6sCkNj6P z7Tc$YpZVLdjt(a^Ju`a`M7#PGR3Yr8I0*7YR>$VgVs3bz?bkbOww+@(4%+{UO%*v> z6x!d?qstm}k2tW8BPYA*dFy%vc%#{A%~)1?s(aZ?RY^o(BJCYw(=Za;WxN5_(cdhQ z|F}?6kY$gO0e0oEE6%p*`Eua`uY;38{8Z?<_z*EqQRSSL>?kVXSWW?J8iHW{&Q)ecI}N6P5+lU3mYgJazlzE&J&6>rZ6g4oj2Y zpX8uCCBpT&D?0^xd3lLuu9|&xG(J6v!Y|WhV;63k5B3=-9MSLDiI3&1fXrrW$z(e# zX?r_1aUH+SxqnN zw8a@5s~+cm#KSG9US~Y`iFIz#uZWC8xXa7+cK_R4z+WLGHN*=)Svol2q-N20v2pkJ zc2P>)znhps#YeqqCv|maTuPnx7Ygi4in?{>D_M{xFXnIl6bQ3)lx0En1sX>+m$UtA zo$F86nN);*g#gyKmy;!Wb<+0}I96uq1>jR>d-DS=d9iw6B zSsTI1figcPekOf~_d-Z)!CTT-&P_{nirMRp+6og&xsmbqgO9vTKvVrENE#GK0AN1r zew1*nH-XbA6iK1$=iv}+YJ`Z_z;L{WdU$8e^9GA7x1+a{dTkLKsF2%s>DSs3c$M1t z%IznOWE!y|TH{IY-YsOSDOPM;&Q(tXih3vgVm7MkSZU7B(XEeuF7cxruA0#%ckvTN zL}8BWvbO;_tAEC}JHiil2+$6gaY*kgkFj&S6ZZ|;)CZED?*Zs_FC}&nem`9715u!y z>Ecaz4&yWfcF0Y*TwHBiM_=78Cpne9++72|*f9`X}t;%Bc2am+MZS=}{bT*l+38GZ75B(q+~!FBUlS!N3C~U65M6Q8(AmLjuR6a;DS^MIcOE3)KR>ObwT%$nvGa0TpWP zLftRd9H=1ASZjBhT^*^q8j1TgB*7Jb6;+>1-V%-saQ5GM^tVP;OUU>_M-E-fv^ zzzcuC0IFUUb?Wd5RCo8Qi=&Yf=DT+l$rI~OmMKR_&wV`Ta>$BBPADqPdIdn!=oF)e zW`4EMM4a=>?NU!*gZ%MOfYoxmu&IbH9M?VcajlwHCXx8ivC!PdZD2&Q^|W#nawFV? zq~oJcKxB>RuuX%PI{#{4%X~|K#aU2Dr9Z$e`~+K8o)}?njuj+zrGgoVQf+VXRm5f> zvL#34F9fJ0jH}a2P1E9#rxNgb2VP|RkIZ7J3GZF_(y86jT{2(vQUjj-TZ%qpvN$z> zWxx5H>^wm9T%0?=C|+I6|Lhu6fBCFlvtfEB$NOo3W}M^H^a0vZU6m1r>umW(^f!zv zd?1ljJOfaH2S02-N@`;ywe*4wX>;AI)1v7oH#>&bd6{-Fxyapfv}5dVLVZ036bnC? zja>a3{MCv%5(5~w~x&?HO$|9j{j6HadD#twv~G2W}P)3{*&bp z3O1`y3~~O8r1YBJ@!x_;zC;M?pPsrB*cy8KfENtrxW~wPCdyMl-dn^nj6w;dESGu( zf7k~~->+V!Z+LM68dg-Pp~wzqxdWAuvm!c&UdF+e5)zARNAigbyJK`-3weJ^a$UbS zb46+z^{3O zxJAir`hhV_TLY@i8%5VLZV;_`d+gQgJX0d^14F`uZBpOY`OcN=OrawZw^+1GncjN+ zL^kR#fu(#GID@S>nHH5%?(A5}z-b^KU%lKsc1rTVLqF2y#`$(RMAVUfLjyG0Mk0=7 z=Sp;pkU*U(V%o8N-2zFRe<5Xf-AP?H96K*F^I_yj`>H^=1uXrCfoqKmKH}q@sk+w{ zk|?^W&y#SVzBNEmDeQ~;!PVuDE2@b-kJGg~dzSa#1LcZ`#=MOtn@crOe0jXz-;}YK zX`P!;>awXhI+jlZmlY13W@z*fwbOJ;C%qk^)XwC-9r=-jQ*-vMCmJQ!q^YY#6PH1L z42)2|JL`xgA6YoL`+CV5(V*J}CgweV_AJ%y>4sw+O<+OF2G;1bs#eRSWucp#SzY2e zx0#FQ=*Xp81Go12~O(OY?54T?UoeYQ&Ztc- z3;eg`|S)8U<4VMS3F2I0PA8^#x-NXv_n=olRMpU&}02l54 zh8Pc_zMdD~2Jmx;M3Qx2YIr`@=#WoYN*ULRlP6+n(4g7^;}aVAi0_$0lsHD3oKi;zj*$Gk~|^S8*LyeN~ns+)OG?g$4mp!pog5DUGXMZw-O&2eGy_E zy)R0QQ+OE8eEFZyc<<>TyMQaQd1{vfD`*$4-y>wGUK7f?4L-V)<)H8HUD(@81H5is zfQjA*=Y9&W+}Jrj7UtrdmJuG7>%Mb4AjTG06!nRm$s&o|Wdw^B-ITl>^K@bqE< z+#M;F3`m+*F}xG^7d@Q2SSm8vU*N#)Xp4gztqV*iia)1e<$3Yd=0%!4aHld;ksiM7l5JtM1)XA_ z&cEJC;_D=!ICh7*ta|IIyrfAPBN7C*K7U`YZ`vCa|7uu7;1AtL#=L%Td^C z)%mPmcC<(fRdCB#*PJZJp~o)Fwa=;hto+~}(?~0>kG;ULD?=PpEW4g-;t!9pRZ#u| z8rYVEcTE!PNyGBH8Z#UnEYa3*LLZFkC8QjHBHJ-=y5|66Aqm>4p(VKU-oa7IZnpA| z-rMik`}b^rKn$h9sb$l{C)9t}F8I%19R8BO@_D%Y*Sh|yw>16-QqTZeJzj@+8qwyb z!cXtOeePmFaP=RI7wSl+C82^vJ%G7?OAP~+Sc-qy&^f^UW&Kt zCDhL+xQ7!w~h2N{7#!a^Ns5{;im8DZlH!u}V8IA4_k20!t7&-)RZe`MA-q zdppp9%^ze0*|soUpsesXsQ7uot1Td;FJWkyzB${Vg{>ZL0udjKK@PxF&HGa-hjV$G zM99e*&Dp9%f5R`oI$se*UkixDrQ%!P3pM8k z(WF}J6I8PB2jEF8b-eM$z57D!^OV)<2~ZJD;6OOV%aLuUHZb*)oA98ME35R=S;v}JI0RP&vT%Q_Cqn)`XQ^ICt{WI@= zJpT=p_WARwuI03Alvi^ifw(#_U)@l(s%K_j-(DYByaK?aO1i@I51klb z?YqKwmU*}}j4yhHKsiOWeq|P40d7QePHvI0C+Pfj7Bsy@D}{BOG6Mv6r(`O$1#-Ym zb%Pvda%HD|47U|Px^&?N$FyuhW5VRcL(TBHpQEz}${7x#=O$0=-ZTEz0yy4eI}Y1X z$W1S>^E`hq78_SG+MF>{YV!W4S+_@dS;N1I+Wb~$_%-N)c*p>wr7ftx)Ar<{X5C%h z!M5(*KNv3`apT)ALNx!`(0NL!>Vd1Eea`OPUqmM$yf?pm#dRd~se=hshfqoshIJC> z*QLey;=}b#M>;B`-1CehPA{V`9hQGN#%8r}e=%{dFof?%%@2`VYH@rvsimePkAp&B zH*qAF;aH7uwqi3J^$<9Uk2VJCb&Ulykr2$xA#ZuZJSGbHc>UYw`8qe zhFu*U;UF`TyI(m6IXI~SGk+trZ#w){6cy+0UPDdRoVtsmLsYClr$pV$in~G)+a*Mv z|B~wMrWuw$2Ab?@biL(MOz+8vnY??KUL(30Akaz&)$Fu$<+mf{CkO7dg}EapZQ7|b zL|)IGheSNUCC=B37tHgLri5vOsmJnHcCgZUGW|zqfSfY&Au{r_h-l?u({%}4)s?5J zfqeo}$$YFG=l*7>?Qta^#hu5&$eerNM@gQ+q&*q+pnoK+5apZef#>~sq49+{rJ*D(gqsD@QbJYl#S7#ri_OLN zLxVpH;B0~+-H{8D1@+@wG4SVYcG%4Xffq)-@oOEe#w!G1pu?(d?uRh3!{P*imJJf> zAjcEM>mw0T*v&;)yS4@rmZwr#of_WvF=ATxKw>0&DrZs`rw2-x)NWKx>aWmtxw|iR zocIAcIc*52Dan@~t7tFpFFru|i%O=J9BiL<}Z7jueYpBCr!DDyzyylPJ5BMNHAu7{ght*ioy)quImsExG#I!gcOY5r{To-2VqFIJTe!X9F3<}4I5fzvO$dBd#ja>HWYY*~m>|Xm zZK(=y#)agu>$PD)&dPRrU73p;;X|apW_QE(d=87I0p%{1!{80k=UcaKsS~Jdba-JD z(M*nx`6f=$Xio(0(kD}+wpZh^(6rFz!J_Fn$)#-M3}6v-B_zGr#Z`1?RFKcRu|wVc zyjpD*yip*9S9O2x;7_Pg@xs{;?&&51$1mf&IBD{5PeAf=HLrk*Lv3f2|Hdq(&qE@5 zMJ&Eul#zv^%}w*jEEwv9BZdySuTiCC_&ow|*tDLF+_dpNbPrNc8??`3( z$!F;9WB^!Z+cwD2zYcY#h-JZo9_Gt)rfjYI@ebUh z9nfGW)VGVt(tD#dARjl06pL5~j|DDC>3KSo#HPf`D#jyNVzPXBdI!PQKFfU^2c>tn zBQaDRtE`&U_-}fr2>998tpZ4H6VhhLKmEEs%^Lz6-SOJ#e;Eg3SGA&R^w4XX6t^! z=qmzaWXBW`>INk8M#w?Wy&o55Yis+V5Ce}MKB458*C;dY%-y*AV3an{6%N6UN|6Ty z5bb3GPJKLaL)bo^1eK~I5PZ4u5D%5AION!@W3J3@MczReDBO!_vi1>n$%BoMer{573sBIre5}qedx!!c(Yo|kky?&9u3`?L(qrpv84p^Sfe6y}Ke7HVR?*CFuR{`N!%l zuOEtKI_d=*2DMToyC{L8JBMG=szv@bULTF(LE8SLdspxt$U(aar1f8oZp?E%+xn5* zH@U*j%D|4YV7zwaJEU%)^{c{#TSF$V5Y9kRY~oS=+H;HVFz=+esEhdm5 zE2-yz5@}W&wG>O_fgv;5+PHL&?g=8;Zz{e0(a-JIqYxZ!nuhWiuZubqw9|U?CGFT6PmoOLS(gx;hRg3De2#D8Ig1cazM)xeJ-FCSG*FDb0Om z{kj!kP7JR{02SA0>NeoNDcz!Jkyp5k<*jc6tXO4fxv93=>ElK;f`{M{tQ!Q_>+&@a zbJ2Fky4`mi$YW1-h%og}&>3n-(cw8Pxat}MeTp2Oq6}n`$=ztXITAs1XTNoQ{uFV4 zKX8QZP-pW8PF9CThtfM!5ks=JzBO8?vR3@z)cdlcwqBc?AZTbjh1i;N#yQN?vMNXC zU4}YPvtz>ghpw^x;;wkRL7f%n@OSs8=_P5}e~I%|C^hCBg> z#z2zv8jQ49Vq*}62wJt%u>k1=oH>Q1_!O3w4Iz`6bwP+jH#ma8&soE+E}XR}vP z0F6>jq2RUD5Z3RI^>5VIKdl6e8GYbp^|%$Ih`gMxW&l(i_koGTbI%XRF@}TnISeAK zTae0h0Pt8u-dG0lGC4w>E*NJ?eC2`fg#9WSdgI``wTbcc2)K#R7@Vkbj>& zZGlv)Nz;QxAZKIN+BK1kd#WjS^-R9P=f8(nsiXQWy^`f#=o5>P^Z^%@yR`V^y*ro$ zZk3l8XG}IU-%3$uw@+4*RN*_plA~Q>c(GEV$8$bj*|9tpAM?DJlOHq8%_+(AKe*WX z3C1Ejk!kSk<7FK>y;%j(i<=!}E;9~eu}(Jswb}9z{swyv-3An~MEVP0L{^3MF3$I* z!l%LSB!7zl7s9>B)P?qRc7Rs6R2(QI$~k*~b!DUk5!Q#EU@p@i=V(|-;fB71SD<-s zJU@qFH`&+jZro1p5U=O@G(OI_6KVY?JLPVm??_PtM{y)!`zshjNOhz$BmVY18E->DXxBF$SU9;71Mbc{sC9_^N3KWV zE(D0l80}Fr3i6?FcUHBdtZ?5Zd9awc?jnG`>7e5@L-AG1)Q50cUX1xMFm3YTyT{_q z&sWf(CmWxfsuEOhY(_0`mweXWx^vL^rEEKWQX;Oj;|@??T zRJ0zTbKdj`?~;e31EZz5xcECDWZ-5p9w&3XhU^UW3GK_coxxG-QHuH%)! z<|0yrMJ@mH_W4Vt=;0mh-g+I6I3AA`>2u5l-ko<<0Bsd?Z>L(*;1l`PLk}c@jEsz| ztB36_oP=QmEk-WPlBDDczYQwAfeE#q#nda}e4`J4BKjVUnllBUaOuPvH`N^WP8~WJjL?gGFv|a8RQ3=$iu$;<5uD za6L&o!K7rJVBqIe|3**=4XZ^ANPEV9TA}bh=_0LTxxSLJeWgrE-j46VF>;SMHdgOn z)gm6tO1zoWeEF1F#qaf}pK}=ZX3L}iOW07PyC@i(S2nlR$hV>poO)ucir2UE&yZ-Q z0bm;x12G3~eUaugd-A-!|u}a3=>kacP0G`?! z+kdEoBiL@k9$hMsC1E%w{GPJ;Hxf*v4CJ(eZI7zURl>n}p5qlqz$`jo{k4$3JL!n| z@;l&t0GfCNDSWy-5f;~NP}!(gfDTohOX!j{SIMl;rCEbaUs1>?{^*Lrh#UIG_3YD2pyV-EY{ue46oS4}=juS3CQS>q12o(L zSGRC~-#)T!oc2D*7@~lC!y}NX+!7J_mc$6ua(u5Nz?{N8&`nBxj4>H7oTXz#5iWKU zU2%go#OsOY(@!fY@MP7DqH<~c9(T3Jquto+>T=tnuO{OKy*s(7m?WdL$X;cN z{X@D8{}VHa3ck^jpjf)innUy%6Qtk1UW3yF$q1$7h>6!G1==fKL+D)2|f0WO3M z=4Y5vuDcTKk}ZgoY0LH%_0{H%u@k7KA(wvW@1>7u#Fl!4yf{lQ#BS$;F@J&hDIk3M zwYN74JXKEsK6gt09$rf> zKO1~_rAWd7Db|vg`Ykua=oFWuv^a8DIXZLGeOUj|y1T#Xl6v6pa}*nP!k&X+ldHLi z{K4)2RGa@eNDc5hs9+1$xFRup)m9En8bI$^$r=fN>zcyCB>!l#VzEL%y3SZm!g>}^ zW$*s(TFAW5qSaLZs>sGzZlGn4X6`q zT+gW>pSS_6qZt6hFuNj*^3TtiCI(tP!buo2uRlG1quLX-P)7UcOZ|ulcVxeZ*Qb3! z)n^#;Z1w2DyK8DBzrVv6c~=!mlb(bo{XXS?UHPDiUjsL-Be0VN6oN=)d3~u zlgr-nfPcv1Z-baZ21QLx7J$P)1I?FHd<0qIVo*@fL91>ABhAnqxib#6v96enM^^0u z7qoIAzlkDPqL7I7tDTo*q+|3@?HHtdBiM;-=NeJJ_Vq=BXIUnSU7!BRgx5a#Qcxjdn1JZ=9`3=ys14PV;x`aLe(9|WwKz{^KmI5EA}TH z5&6_HmvMh1xA}O#f5F= zJ^wU3QzVDNd>>tZPQLQ2?EiMpM0}+8O5+NB9@7(`G#Vg3%=ZyIev<^F!JO6npB6t{ z?)8bj*ZAXstmq9jZjsxu7?3pCJJB9+dAY)SX;sq`eKve5Fx;}-a&IH;f;P2m-Z?bT z9CQa>g=bt6eA55*+Z3yzWOM!qYvUHCtSbgo^|e=ajIsZ#qvU@uqWsGh@dGnZ3`zIm zp_Nys6?j?_ym%wx30d9iCU5k6cTC?p>ZWoHcK$KuGmS>s;=>Wz64RXLlf@ zs^V;Yd)GG3*vc$yhAJJNTTK~ueddbv%Kgym-%0<=C+?p&;y>9{{r#^7QYh`2vhu^v z6EZou(_Hq7E?5%M|GdFL0dDUR+B;=C_+fCWyt?4g?h~<@+$-I^c`hN{(kmZ$SlAYA z`p9on!9cMYBCIo3a7*MrKC_*AUQzZ?q#COK)x7ip^v~t^e?5R>LinD)o zwYW^>|6YZGVkR)Ggk%emp;E5LuWCLkUS&ACY#9H(!|$QF1ug96;IFs4l)7tg!I^H$ zE&X2ke@^ZHJU9sU;+K0_W-&pPYhL%yOS1F;Zr)`fBJf$dyw{Xev-}{E>vJg9e2;mR z$nea1?(g5IOphpJsW@5v;5sFs2Lo^W|8tKXqR3?N-7(G9o$73g&Bh(b>G*xFdeG)_ z!8n&|MCmz2-jNU6hE*<-i1^7F{eLa#>p^1U(O(S{Tm0AFCFa&P}1 zzRaB=jmaybdk;k1R?0f_Rv8Qa^ONxb3YI^I%(^wdrO24X%lfMAjQu~?vw^UX=cI!B ztKC59ye*#s{=m|A4JNa}C|!{`>?F25pO!1JgQGZ`rjJ_!N$|)r!{K`eW%UP!O z{8^__s+CsHUgZ6;&g%#jE8jBZ(zK6F`;ym{e?9X3HH=Xs>{zKY!GWclkf`YK+k}Iz zzn;C0gx_ywXwU1alPaqTfa;fZy_6yT*ZsIdOuNww)eN~PA zb4VGrl663@F$3E!d$9`5zg>%e`(Fbw6d6W4xAKLLc9D4%22++wQim7(Pv!94Na$FAZ4>m(ZFP+B# z(>~bcx?mH)t!Cz$eB8@3;%(nR^}k@`o+IyjG6@!#gKZTCbAOi)f%u9Y0PDI>GQV^% ztoV#J<70hm52O7db7Ny9N0o)@X~2I7N{F8f+W0E5RH>Z6wf$pG>#xhIcnQs=R>*#o zzV+x#<c^o?ZM}Zoso#O)ycpTz2aHAyec5Fzo1zRpih9hjakGG#J{f zGy^6{kz1dOb%EmWHmJ}Kd+Wf6dS8|ra(Xllp!!n)@2-1q%_A6%6aA_BdNWQynN`EZ z=oSEx^Fhw?D4_q8h#|bs;gzn6qRl_Pw=)pM9i2EVuc(b8A1L%#zL(>%0hKb#*B9M! zynP9P&0%@GGjFma>HK8{C?wbsh@KZx@>wTu41Rv{;-fXdF7KdRC@D^fxiCGs|hV zY(+kI8u@KO&KTr1xw+YA*zx!xX|w9y=U=Ps0|lZ`j+LJHH!QOVG-GwiopM4s)MXEm4#|H}} z%c(53+vV4 z+>LoGdFOXkTz&WC7%Aho-A?N=39eSx)f?Adxw!SuJ+ zKekq7zK{=0$_pPTv(mf-;+8WrPP1Dg=R12C8}oTQ7sIKl<_?mNY8i zT`!cr)-5G5o=KJ8Avie-ORc6yIf@pQy*n)Kw?8MMnqD!>q5`V#;PBwad?iq6%Z}qV zi#j`A3?sHK3CI0XBC>Xtl4sFNL(V8=WEggoJo%cU_N|ySHCFM_#ewd zY=T%!%n)=`xsCu;c3c;DZ9W0Bsh!BdKm#pOmH!dwkdF{NL2Nbr25(a0izk0}P;PN} zJ|6zqNGtn>T_W97<;iKcw8O7}ftaL+jbQ|AnC4KGxyKuro_Ptp+QrJP*{=@v8S%eLcmS=U}6M{^Is_cNN5O8j-VlWVczB#ZotfQjlR_1M%W8TV;1_#yx4 za&*R`^uFZy73{!L%2a?3Uu7v6y>z(oj{t|5yah*9-}-rfeE^8!EJUdrlJf$MGFE$a z#|eX>pB1Y(06P3h*!B*pe_QOm7c*YcKTWD1$2TIkZQ-No#aFItw~oLTSPf>?D)D&6 z8!am5{VhRb%wcP)LLs*aR3tNiD6&E0wj&-8eL=_Ip;$lZ}8yyefnd6X?{LWS#swTPzHY+NZjjl2_{Z?z;E3% z(mAHp#aGXIR{y;m(NJLuhz763cz_Bm;~Fy~`4#$Ir+3u$ z{o?h(U=H%y5-{W(tt za+LI|kR%Xb$^|SsxjW0=Afd8QW1DfnV^|5~Fp6-fq-ohWih5~jb6$WGvTw~`dtXCs zxxQUET(1?6hG@IMg%F15q}Lv3H-1~?Y3u0>h|4p8rA0B7k(E1{!}I5H{C_-%#d;_f z6{Lu5Wi|LI$Z7BkIeGgm*jbqKN|A~JTHnBM#&oi{PwkM&3-8Z3e47hwfLEhb(MDk= z#e3#%eeDu(Zfnt4@bj^Hvh6zZ-#sey#=`zUirEfo=_;V7G9kzV28{S0syG}16xeR_ ztxpC29i>?yw}#wtfY8a=B3*GykSUM{ImFMS5;WzDSag%$$Bd6j^G6{FP^8kevF;tU zwrsb#amO%tpaG1U8~q@Qv!HpjWW@KwyPJwu#TO!{lyTo_qpz^Dy0f5ckN|K%S z3OA#KY$t<8gZ@{dAAF%DOe@&sd`64=PfCMj4}qkhOUCP7Liwqk8F2CIu;4@W16zeO zfW?OF`d?&jP$gC8fw>0{{*NM-D2e>#Sa!oxKy<#ayvnkku-FzU91h838VaXu;9mX zHij1l{w&6*)WhB$C2IMT`Gww$-%;~rTI9upjyFjxf`UP#TqEjmemPz+2!4A2AeP%=7 z)Tu@~6))E$uHIMID9N-LWM0{#Qh)K;q8&Tw5M$*G1e;HvvH7W-=MeZQ{egrG&rFP4 zO3KXX5jH}-IHO>1U{s&tIaNFteaIp8z%WfF>`+(cWv^2;5R7M4Uiiq7HY?Sz4VbkD z5}h-SQ$0K?vGi?{;{hnFwKS_fJK|)1V%K+-fd=EnW#HOs$&hMV*oT{NhX0SWw}6Ve zUElo$kq`t%NdYNIX#|F@0aRKr=$4M5K{^M4K@m_IK>-XMw(8Hv?=JA)+U0m@(fm2U7Kwg1lxXk@ z0Gd2F#{gsFOtSSM>6MXh#YjJWD<{QVo8YifVVpQ0(tQlnWD6MA%T<$}1>kG*Vc~o~ z6KNt99$?*0k9bOeMhje_YLR?-O3-WIcebO%>uF>XN`8huv1`Qy(%#QjZQ;_*A9~yT z&DZ_=6q$WuuA}(QPj|T@(WCeg;;yT+>4X-hSa`@rv>~#$u1tjJf(%Vueq*Q~w!SDE z*yfe;R6B)u-~GwJ{x)R!_a_78!0r7I|MS&R$~MZBKqm)+OXkp|`G(P4P3HP@aC`2k zy@ocpZjACja6W8y;(4Yx)^OJn#J+ywJp<6sq~sTwGaJBSw6;=uoCI1J9@~x71oF8d zvjj>eEe}9<;?+6`1MMC{nHCyUPe91(xne=)E3ijRykeXrF+_w4PkSyr#-d(o7^BD@yW9?42J+ekCs?`jEKy|e9x$-e+>l!F zN{K-@1eVsO(uZjAeR(ggb|+YC45PO8w}0$48ty%}dimA%NxL?C$}0R>j#>i!2*C>Z zic@AiLxQqEO37WytB67zTUMPojku7)-0rX2a(%c-I_Tc>f@ITrP~t^`ndG9xK$%Pi#UPU$#ekz^O6v`o zX4+jcR6<{112#yQer5qds37Sl5Rz)m^S5w=z4~)KNV%k^2`w?bqqgwcEbNcZw>ffB z<|pVvOebp~TFkC*>RrLof4b}Bv-Q#UWPiuhcl^$l0aS?DLG~xz$P<^8q;`5m4Cjq< zXqM{yRsC73IBbDd^*AC=aY81k?Z(qCrJIE7c6(*${ZvFoNI>}c#mqVkAxA157*Ph5 znx7qByc6shEsXG8y?Eb0Ow%dCm6XSna0lU^NIxc%!WZX=8F4O|1+!bAPVKx`B2T_Yh=sDfq0=cc{Xp2{hE8O&E$q2w< zE;#KrLh!MAFv-+r}hZqCEpG_N;F>?O9nr^C~zvj4P}JuRBV?wCSD`!b>|;F@DySg;83 z8~iLMQu&RGW<4}LpHeJC0^eYQF!86?UaVtiFw*`}?a^jDYM-3eMm`#m!wp_5L1SKu zjF9(FId!%2pMu0;cjPPRiEm^foT6J4T$|y9jU>beDOo_c`gD$ZsqJp``aA$g^>pwP zzGwi2qwlHx5sNZ@n3#J6pDUMsL?-qQ|A%W#IJB>i4FH|zTe?UGBDCkLkXP!Q3{fXt zg4m$omDGXVWBd8CF9%^-j6M5N+&}fp2 z595dz%EQ?;b&M#3r9wTS7ehk&q>}9;>}7e#bX4_a%!d!Y;^`VKgiMhEIJYB)U zXTZh1jhr7$uL~;Q8GI$MK#Qz$0N7E(!5f$Rn`&2$4Bdtv)OF3B_^iOc<&Y?o2~rJ6 z%Rg41Nvx1qY~{aW`9Xl7-HOec_jr>`-nILn8;u=xZZ*o5lMZiZ4EJPY>iPL(?)Yum zS+zDasG8W+eg4>ZeGJK?C&0LuMtC>uWh>Z4Ns!Huf3<=Dc7RjJT8j-*G0 zo%jp<*W?*=qiX!_Hv1B?QU#3y1399KeMY<4% zHFJbDN2*w_T)-bEA{>{{BA( zqh0vbri3h@m*-L<1%-**m$y3vRN$TpGU1^;Wn&59zG{HkG`KnhWzwX_v5h+G7Oe${ zK&`R4jgTy|v(v-P+?%v*cJ(N<1ZO?Ed6tYqV zap%qPZ6S^Os!7Pbkzpypvh>5h&WJ0fm<{oKiB3ufyanY;t zj!V4^J1?as-b{@0Gb+Y0hoPHDxmXmw*8n=_=LL!2i?HaKOUUyf>ZT%Pp6Zr#-jjIN zlFS>3>1suYg5o9f{g+vY9l#;^0c66KVFFEJYs`w}}qTWHk|y%vf`K{OqYG7;m;0lI-=xdO`K1H{kWk z*u_o!2?#%*qMzr;_y89Ake3TuDFzl$(W)P1{YMoQMz z(JIKN_v&7iYuE~}lQDhTT~g}7C`(Eh!IBq2FDK&Db@JyswM1FIjConqy^d5Nc*uRT zpZ;`5Go#-G-_gxe)1oALu;kXORt)B(lKvm#=Oos?jBJvOGuwmQp9{eoIG)M93$+oJc_)30e0 zCI!AgMRdD+b=;+52DPuSm!&8!-fVrgLz=G@4s+-5J$#7Gu2}O6Ztrdlq>q2HdqFc> z&vEJumD<_a)&gxUMCqnz`_j`?%7xmo+&%cpo%LUfW`i>C=fzt};vp_hvHjD`WSAil z_d&oq0gG$0BI$;RCgFK86E%@84P<}O(Weh}-LK(0QND|!p?y)TabfWhj*(ERzf*3R zj_s}0b(TZ|ulb6FjA)2;tW;j&f%@D;mJ*4cfyMO^>D<`d0CE^rBO*4m)F)PlI>JZc zb_JCA(_Q}PLn=S$mjTCjyx{>+>(p=j2d!$lOCmnlS~sCa)9bDT3uqrjY?-aRoVjcf zE$DYKv~0wkJJw_0`?d*{oG=qjxZ+Kb6B~V7IGUiTth(pXqip@X4mMP-X4ZYpmHCsp z1U8h&wb)VLfr=%UI(s8b-hD6T!aN`Ds03cb+I&lQcV=F(W+jH2|a#XAGJbeLLcfLBJ04H_Cg`r5=vAiKMgW{ zV^^1Wim9fqjN;eV@y9(}^7W{kq_N#i>ekTCEbAkvg#4@<}3D@h;_)TL!b> z4>;xbWJaEL8~&KTRrilS^a(WxX&7yen1rs|Zr*x34c)~|;xMEQvkK3>gs2+i`Q06%S$rud&X#nh`_cYj$**rI>~ijve@vRM+$2ykE{jEc|WEseMxWEe@kYGn(VQh|5Z# zcLbL2{aT15x9e;+F{s1_p2*IEH0pqy#gt_}PCu%mW1Pj7{^cP_Xz7L$tTR_f`qroE z1ju?HUSuisjni!d)s>irNcQXd1dtNOBC~)%U?JtvjpOWu3EdS~&zkEZb~H1FIE#8v zKzMja9=pT<8?g7}a?r?_P+X_bg?uO>o(WEbQ_Qxt@9&_gln&-#C}f@jDApw5=K%^Gva?F{Q2Ndsm1A1A5#Of0ly0FewDgwAnjvIud;VUs;^_RHVT?0}5$p8QeUf;sze?yGiJ(1Nb^lZv z^!$LCslH^PJvfnpNJ)!Ujr(L29eWH}g)_9Qh5I5D!^X}NdQxO_RFjthOp#cRPP{dc z|K$RcxciUkDRI(;u87y6B#Mi9+!dou;yzcsID2B5uD77ryWf|E2Gsy~S_WiZcdpN)F8idKo?nK*<&w{$}) zw_o>rwcHEFBRM3lhY27`-zM8;@4kGM+FRvgpE?w|q%vX~yH~jszd6|Pz<};@b-F`ULG7$5gqd$!%jXy=zdQK8kvpxY7!#&J z4#B?!qJs!|w)?T|`GSkO=6v?OLESVo=E*6*gnR;cinhz`z*(No7x`hCkVESs9y{NQ zsWwts^Q(O0zEO>IKN%WcVSWV#)_G0xoxx1vFd-OD=yL)So_^}Aem&JQa<({Ix5xj*U8uUo9{C1oWW3^Z^J57~VVXQuegFr+Y-Jpc;HM z&;N~-&Tzi?rmpVa1;;!>v+0ljNQ>g|0=In&&MJ1rEg757ocj#_T$bf`8SHBQAycw9 zR1k9IV!F*hCHFkgEF=0do!bpL_OM`%etM_umWWr8qMQt+xe%Dm_x>y;yZ6VkMUJdF ztxhXINAPV&Rw8VGSWYDK#b+?SY+Ckb*??LnM?IfovWVqlTEAE#MHq^yi9)S%OxN>T zds$4p+2O{R;hhAsD+QmNpNQeUkc(}xwrl=C+a;I;&8!9%NM7=}$b&ayUfo~560m&$ z)!<1by5>YXu*~kLJ%H}br*yEdQlJuLvWWKAT-=} zju~uLbQk4O#1h*Ld^Kgqz{xtn$iTeI?ZzBLgiR3QjQ;_6^AZ!J2ITlV;?}4_9V$<$ zeBqfNA9&c03-zGWw*BP`S8DnMZ2iId4`yfgw?VP(k1#_imW&VU-2md+0Sq)yQ@~|m zw7-~eJ0oTWz(DwSix$Yl-W4Jm5ZBZ4A&t@QA-M?~F###PU|Qu`Iz2@5WqX2zzp?;R zOky+@f0NRd%5}1@->gAf`9I`g2N5!{y_b5QP@jda)YjG;_ua;|eetJxKX?Vpht4a! z^QmH5>Rur~trfT3fLG2fWmeLX%UYo*dLNy&)91n*zEvNW|A=y)DF>Vr(VxiFE_~cS zj{$;>&wk&zL}(4D+>)#=;J2@q3Ep?M`T$f3k(3T|+F$X)wNk9)&FI2hOttkXvO7KM z_U?y2kb>6D4?>-0WqAFbuDyGe=SJGS?70}J)520udR)?94P1{FXtp-ty&SwOmm8ML zuJNjDbnf_Y1gQ+&0&SGj&oYSxA{T6CB#5yA9(~ID!(e&Q=Z)vVJD>wg|DWq}9m< zMNOB5^$xW%rFM7YPx+Yq*3lv4Sur6j<#Q(E`pat{P4^+5$21;x70j_Ebr(8Yg$pkt z8-+AdbwuxKT^qSDzX@S_R&!WWMb?wY zq)b@ddz#&bx|w%N>UiqotzgMcGdFvni^)+tYf$IM?oX4B5RINNfJsTdPVs@*Z4r=lf>$2Rt}+Cb?T z%bJc~OXChvuQ_2atA|7=a!IPqif)+M^2*W(%UE&uzTD790~-zJCf9l zVm4-9qIU8#Eo2uDfP};gZ*WzLYe6C|lF_dTLZ~$O`EWeHqYyNf3QKrik#F>RA+JN0 z5yGJ^+Eg4tCrBWF5dZE_KJ>7E>P$7pr6;`_>d;ST2XjnmTwwa3NzAp?OS%r&)lX!8JKgL)s1+mrdFyf4Y`9evdbp3h<9?u zbr3iV*0Yko3|)S4#g}>f4d@JZ#e^w{7lB^v&!>h|j7$#x6KZINLUM0w-&GBXrqCJT5f>P1LT)33c z(@mix&|%b0Ca)iWma>aNC)y6;$Jz=NmKO?@PBJ#00>n!d2rY65+7W6A`Q*B+G-nOC z9}wbx?2C~T4(nXHDclpTKqs(`a`SYGW+iB^Qetv%u$ez8-?hSMcsy{dIycaq^?Q6` z=4INLfnWKncp>v_C!!LSKS2*Vv*s%vu z>+b67nwYzR-}rOeIi(ho*6%(reFj+BMy{0gJ}nTXpO*al)d>8y2Jy0Z;Hj~<^DZF! zhkD~*{~vfF!*F6pSxklQr(W%jYQ)}goHc`}zaAHVs+{v%z>1LRzLv4MOebtFOn;{2 zCDpU%JgvMvm+Assmjgb;qw4lYA6M9bJ(KNXbRJr3Z{#EL_hxcT+FpSMJk#Xc^k>eS z=-cghv4L-xd*2pYkZGgQxe;(%mFnE3n%(BzE&GLt< zhX_M85_c9bK{4MBXm!A~`ZU1^|o4{mvR|00(mFV8rN08sLDGp<*eV8rm>=vLA2Bv(3uvY2W1u zo>NVM>Z$byop2XHWH~;T$dv2A_mVsIrT7Bqlacz`0D*FoH6m>6OkE9;l&>X14!f@- z$}>+vVM1Z=tA*&y%o89;p(S=o_d9uCzcp+31>tbk1J3};p>DdYwiQ#*R~Ld$mvD%W zaB1#kj)J{D+`pe2V7lH~W@HP-4&ll?c#?=H>c@WsU)$AbYq%u5 z-9T-bGN(iyy(~|^0SW=pg*@K{R>CL1!jz=;{@RHxllZAdvaap?jqN< z17?OSX$s4-iDBISkH}|%?qHpd3pfXwoM^iD3#3xW|H>1f+0t9@_g zvIixac-Gf*9-cdfQC_B!%c*L__k{49w?9X}Q%ifT5#^pLoECVCR1+r3va&sqAlGTm zbQkyTovY6p--?+T<3z0%!Go^g&K9kQopYmVpjql*UO~-|)^`J9n1zR>K@ckn?G3DG z`@Mml%h!&IS1uBjUAwGp9m$95Ip>#RZsd=0`^HL75E~u3_~Nx!SJ+#~*Uh@l0O;_e zsI4B9=%cJ|*aur|`xDMNLc`9O3L-XfJ8N zr;gF;4PdX`NMGCaPdlQ5QLN}x(e|zPhi2x19y~|`;>fVZjmJ&L&C{L^DDIud3ny35 zL{_Xl478eXTwfo!-ErYz?dbz_j+DWry!>CHF_~%zxWlf2*R)|?qwJN3Z~o55-I<-H zrvcyFiD8jR?W)ci%lox6{+M7+r^!G{846eq$)Upz=$y;J~&UNfWxm? z()4}>a8(QD@m0u(GI{6te7>^0^0cI=kMoo|Or|CA`@W?s2qshatDj{RN>OHY5x zJ7Q(bOeGI?x!2fQuUBlsX`K<2zH?lW!DO@%4Xx4m;l)5BCdjQ!Yf8;RV`&v)$^7cs zF-C4Spv9`#zDzO`hPC>Ub5-898%lLT^NUuw^cPWDy&awm=EH_)%MU*Wx?E400- zX3WEKeJ$x4ibNuiNB3`3)IIuWc%Gzq7S0USY_H0mjk+eGa_6P8EBE)d@}^aKX!V}n z7{Dz_2qKezxIMAxu}u2m_;RK&^=ZrVr~ow-6(npg)J&|${w&+295l$2ppIj4XiTy< z!Y$VUm@;ouh9OUPX_|Iu;mM*-*BTM0*!16+7cr^wARX5Db=W+Reixy;zgfz1g=GYt z3im(9=(;D!?%hqMAIIp$m|sE2gM^#Mxk46Qw{=lo#Y)z+pbayP!|&(#4NN+=B)WD4F+Ro!IUZ%E|gy zw6(L+wTWXUqL}7~-|%jaiBe3zvO{9ej3W5iC&FYyhkcM#5=<=CP9O8>2qPv;S!;tA z8p|2I2&8e6Y9p51@8g8*tcs*McW@BPvW!ThC<;w%+ko@_M4ik`gnPuo~KOZEPb|WUs7Fs^EPOEkGwl~Wc)Cz&*Yrn(}W1$#!T`+ z`QvXnK4cqaPFYB6m3;1^c2n%+^sHWv3o~o@wAm>w_Z5&jW|ZJFV4E3Vk9um%%6#R> zZX6rdN+b|8CL?x6q9j4j23<11#lE44$akkTKJHiDhE8^(Z)w(Km5?W~AQ886nfID$9M&J1#vdZrl19SJtI_EOD zmZJ=#8hgH9R3Fm(>vi`6FZ6!(>WM}W8QsIhvFH#doc=LUqq2@S>dX=MS-8Xapu+4u z+U(}--}1{{7LE6)bfeGo9Y?jfi&$8hVT=sTYek>f<(8o#!K}nN@GzG{z=_+SlZF?` z`Y7ZiASHXs5ii9&wrDGDH^frzLf~_^gN-jU;)Y#YCstN^G7YTokyi;CiO<1Ey)m>& z<1twv5wT*38tY|B;$=9tc#G-aF$jqEv*h*4a9WsvLsV6iV`+CK3_%KQWZG@wPbO&# zq{qIQd40(if6KGz@&Fh&aboAh)jCE8d8{uAc`#=z;r!l{s5l||aZj)gZ9DkHqYnyt z`pkg)^-Xd>UK6#e?BCB#d#|N)>b{| zQvkwbLt{%~cy&Vl^Yz-%74GB`7m^0i*qO`q)Pgvd^u;F^y4KR{^~GUq&5So7g_w(G zi=Z!!d0RH%HV|i{`EyKQTvSKUt*7|X@>xHE??hC@R;&XZ&_4YQ*IlQ9D8Fw&Uh4DI zVx80EUV4~t0A)G8^6JIDL#DJ=C)$-c9@Lw+!nLHt`~K_~Gr3y4eVm%I>tTyfWW;tF ziN%Kq0S&*7fQ;~VLl}BqzMc$=+M>~la8@QgBb$i-;EKrP?5Q?%e}HZI`qFE}e)BrD z?A0Zt;9*vQoWwDxb&0j~mRTZpe)`L#s`w-p$VhKN=fqCRU@zYpMOw}HDZlv{vub~) zrrJ)Orhc*j3zqMTejY=DrX<~BG@tz>!}YA4nDFRIXX6E1xUsSP@BH&w80l_4S{xczX`%2J}l%oh`Jn)7Y z>cIhAWQI&{MN;{Ie$_V$M8V zp!|s+_&6H2t(k z_i(S?eRddukF53j+TEaZx>;#7?k|lqMbr{BW-QphtMJO2ZOxI1X@TVgV@gq&WDSYT z9x3@Py#BTO{-X}3eK`=iVm)0svFCt0-RdF#PqSef&Nlz7FUybNonnR(iXT}!6NEEs zNgu7fh6O6`=c8ZJ@V=w?M{phJ%&cLJN}u80tUasDR+sa{Uv4JJ$~LQp;pVOFa-#Ea zR=2N31R?$En67n_v#|kHs7zioUN97Y$MVw3>bCl`cs7T7FjgE5DDfk4s`yp zPR{e=Y_XxD(AIa|mUPHW38y8KTWa^lu9Mi91TjCXu$$k__SrC7moEULlYuVdnkM7t@r9~ZXM-5p@u81QjSCM z>3a&nH_G)#l#WK6=WtYvqkg`8D*Ll|lJK+AV<{m?5PxJ7i1Wt&8cQBgC(49u0qAoi zWdVb+y1)r8q7Qg{5-98=QIK*5smN>5OrCPaQINarJaU(iO^6owFe{UG3Is*8a}}E= zGd^j^^_&)O#fC|0j=kqIWtO_)zIuohDB`@U0oo`DrObpR#_cBS>+%;ALy*v54oDpz zZDAJbh93=n3#om-w7^1bqs4kb<)Nu_hyx;=r)EPyId+KbFy$gF0M>XDT?2jvmzQknY6Xgm-Q^Ab zu!%~C)o zUvr`I?w~QuOy7};wmK&yEC2_K3G%%vt-H#DzYnYb{4(mt6E7RxQXJ0rXsyz>Hf%>X zR-(4?ymy`%*scV4(O%-`9Jz8a^z|JPEn%Wbxj~DlKns=Gd#7+fUiN$uza;D5p7QCn zG?;z%`9k{UWMyXXE*Ue4xcj#_sY~|mR%IOc@%(8znj|z`VQzyjg!|K4NeduvgcOa~ zeGD5Uj{xjbZA$&U2uk84iXxFbP-MPjTNH9+iJSHY-QX)_gFj9hV?uP+a{e!_fj`Z^ zTy5;R8vgI?B@t~ue?;{v@|+XJcicU=`q!;;kFnu`P3_FGWT51un3H|jt6T539+DjR zM}_=0scA^#Ys;aPuuD$h1$ha7#n>7YIGkSt#eD9x`22hkP*?Sec^<-KGm8_&$ISUS zZ_5f_NtC{}q2(@>(#FYEYV6`G^Yl1-u<1L`RP^ZTv?e>8u=ci zd}RBsx=)#zm6Xdk;e3?^?*(m8J4S>+=e_!7Y)jYvlUxVv3ruT4g5eqR@=BhhQ_+i4 z8e;OHi1YW-^(;M-M|?Qu)suL^&DIr2eC_+_93&~lLD4%N2Ii|&^O{5^+>nG){w)X$ z`d0nf>v;CXCx}*rVFbH0+1slH*RceH-UFKL4=JydfT%02?adu8Z!1`#K&kA+kLCdX zlKF+ura z{@p-WJOlE|ub+22ZgrhF+f`1v`x*XiVq=Z-v)OST3p_^tmoaaYd$xM9p2bWdacolCXB4yLB?{Ed<-6WWeaK5L5P)Un%xh^M(47|fl zPn`HYWApE_Hfx;BAFYVh?hDS3fzXHC>%%v-s_)EyRmriinBaVOXuf3F5shBI+}3n# zTv?J1mc7M>GEJ6$k0J%1J5u_RiJr)VibfS0nQhT ziBXDuz}LPS*zBR3ADj15%YamOiH5(QSUXCB>*HGv-XuW*>u+yU@^eZee{XT-3=IK}_-&*y19(MPvno(UqsC=H^9RDo zz$(vF1eO=!9Q8}TBh4TJ*r_z&Kkq?C3wpIWQ1k@tm!(i0{}JB8GK2|e0UdA)%+7-Y zU&=wafo(zgBt(f;Gg+ap7^Am{YnT%sF~ZUbO}qa<`EMd*SOzYb2b3c^2rAkePMKf4 z^1xJiAx~Ee?%%x$4Ne^0a+{^)p44^37g?hWprzw+O(9-Ue%E!Jz+8wHbXit8@ZY_Z z_s5Q@LJ)$YKfzx5hPKwou6&V72tx@)oFt6&{tDnKBk>RRbv4TW zbS?ffn7#!D;W|8NL6UtJ&`0=&%wa+nP3pTc{t|F1K2OEsN=Oz#0F!GS;LL08`I zHs*85K<9Nd@aLeaAKd$oQ}M55$-jLZh=%a3Yy*l~4IntzfQ-3{RW%6_^E-r-k-RBG zA5eF}7yAVF^#M62LHLk0pfG$#Yk!M)VDQ&TWFWydL5J62J@E~dD9PV301{((i`eg5 zo`^? zRXO7|XV9N7OGjD+zG`rllsp|7$IkPs&sj42asNLY6Dal@t+?otf>ks4+cLGkF0Ah) zfnTC&PCImG0z!*=HMVXxeR@ncgyuLZ&D;HJ9gs1>>G(yxFj>)k`e$wUZx4XXXVxOC zekLO{2=#_-iSvF_9|k?JJGn}ul#G3Y0dvev8=Vu|Tk`$))tN{Tr-jZ@yJTK}I`uPCV-y7(yB;y<6?a}eTZHy;VCb@bzzhLg+gi>oCCA0w?( z3ECH_3@LN;+Wsn)2ktUv)X5#E+=>SZ%Ku#S{_UBJ^Q#Szj+B;e>%8-C8r^^0JsE!2 z`1r|vgYP>h@Eqz8tb>K2c#Tu~uOG_Ji#?2fGiXBphRjye5?dhHq-PEcTq%8kapnBu zbPUR44^tM^$x6a9IRC3NC8I-n#~ESMm(gSJq9Z8%GRI%nX8b*d_q@*sJ=ocZ`^83` z@27UYci{X-84-Mz3^2Fz8v9=C=Y0Gh9=NGzJj5{{dLT$N^3Xuc{-4W;-7gy~x%Ny(NpGnQ+yB4M z(Wt@s4y442B-VquFFx*cB?{VBE{i4oxfSnTEvmx`B|If!(RoaM@4qJsvIk3lT0Ob)*!$F+7Nph( z{@=IdzPL%AsiK(ve$pRe*C_)|Mm5QRDoiY&ou#n zG^rYxu*6f^SQzq)T?(Rpf8|AjKDOr(GQMn1m~IdlS6>5WdRH5M_8#(}&8z=?I{)si zF&`rnL8{RbeN`0l2Z$0U8hAgt9TE;WDNs(`KNs2aTY>l2K&PsFHZ(hiP~Ns@9^8+6 zn(db*!w&zbZQ1Fu@!KuCUe6KQ`34p3!+pb@YL*o;zTp$mi4B54!X9JiD=5o*|98r= z|N3@ulgUtHex4}rnWY%555C3JWVH)<=m%mRY`Xh@U8kUS=!)<#~^l6I+Ap8;@^bHCdZ@JT+Omo#5R#zRl3X9pl4>rU}fo=o{cSrwry z&5RbDK%Ex9H@s8v^vGf=y~1JP`WcV4`akhAxk#D!zkd8fx|A4 z02=`#)jyOZNqCji0F~Ml#<7bT2{nV>0MnP(2XbO2fGJuZ+;=4%Y)MvMV_7gD2{(+t z9Y7tO_8q|x_#eVku38?0no89`ts!Fn3NvKrV119$jdUZ6_y_u6 z6yw05N#Lg$&_{IuloKQhI4(sifgP|$o>;WyV6|Vq|16Jm;LrB|KkfCPIc?m-)?2ma zIK4%|6D^z&!w6jvbeZ%mv_Gn^qOd*cVx!soos)s9vRrYty0~=GpjTxtv&e_|-dh1F zk~)cIx_%e0qc+t6yoi>MbhVDPM1$x4)h}(|Slid1Mech?zBdUo4tp#P@?p=Km zKYWn+?XM+DMiU>yQX#Zyk2*{z@x?wJm2L71Dj3klVb}&u(P~hu;^A)E1XjbvpO`g3 za=YOowJhU?+)ZHs{{U(C8)?-3%cnrGHL0a8xdb2=4wYR3)gFnUKr_i{@fr+ISlGkp z6@kom%Dx_TXx-)u=JVX|?CPUm4tCodA5w4T-4z9G>gET;vb5+3@o@7Z5oOW_xyD6~{_i!Y$4AcqrK+G!+TyJr`c6G35s;L!XWV*nX)gZUdOCd`S}}u71D;5m>U0K5NTY+aXt#;&KQLT zhMVYRb(#b8j%}sqj;Vdw4?vAw-)&to%@S-v$ZUSMc0~k2q0r(LWfQI>+ zM%u4deC_Sa$zO)M&=+@e)KVt_h-h(7{-?t2VvJ`q)v1ZV&)~MeuMsFcV(VP>1%PSp z0F(hv$#x|Xr@)HmvsemPy;U@hwfzv)D=$+1t^@RMXNEJiAv2w=hCVEP9W1|ob`O#Z zC%c98+yqBFTgwfyhHus2s`^Fe6`P-PRXQzKIy91`R~gm$O?00gPH~1zr5H#JW0MYJ}L>Pg+xm4Rx9$(4HTF*@1tM_LqBkt9E6#ki&({SMoi0QSh{fegj`)&#C#8&gQe*f7GoSCpb@fQWBp@gn32@(`WG-)8{LUN*B2$J-d)u zgqdQ~4U$s~*y;+kKnr0*R2OEQ@;=(y1mX|}@U14)nVLdhTADNwd3aSg*a!(T*9D*OHbwI%JiGO)yr zFzU+dE8fIR$rDA^fR!s;$I9^k9vN~zyD(q;gI=;VvNn_4wt8!;aLD_!L6&enOyqb8 zS5>cu)#st^Ncnh1j2?7>Mr1v>ZE}MoJm;O#>o5G{Kiq<0=GNwAe>NBmN}M{h^&9bp zVMjVhb7sW^Mdv5U3Y*P`)|9+wHdC2z7E0A}vI~!f3#LT0C_k|&b-Sv^+>J2}~=B1hwO(0F9#15?zFKu~ks3M8lkz&d3uJZgOLsInf_O_8sH(Q<*5a|IlA z)PeOpzp~08Po}pCOsI1hqjBebJmK8QJr8QsdgvQ8x0MoybTeqwoqN)1lD*SU?{^LRXz1ezYiqm#87(QVEyoSf&o#aP& zr@hPlOiwNq$36V+(Qx0d%(s!Uae_!4nlCaD7%tE0*pQ~?PZ8d{;ktP+BoW?3y;SWM7+T!9V1JnJ_$4F#+0nGR$u<#>5Z|vp; z+`IKFv(a$HF24~-l;aeMZL+t_exooa8;Es208-eCEG)rr7v>CvxuTrb?~Ks^8&vNC z1Y524tY;!BT51ol?2@@B28RXXBQD@zI8r2;vcb5>J0^FBOD)ws8ZS|{IQW6jJ@YAcaOm4-DY1{g3PtTFe%n6$8GXCC+u63Yzx;`J9j4-95YjwOdt9& zMKUr)mRcm}d|`actgBP86w|4Mu~7YA{sVk472k6KCD)?9q>npzBZX~awHaVo&24p9 z$>CFjAK7)IGu^29_`y2bNVCEs<+GYx?IsCJ3=%JlgnkPniNMGT0Q>26hxJnYBX?eS3|d4H#m z(dnrjY2ZxO(@jd17xpCrJz9;PLv^cV>1M@5wng}l(Y*Y^@4hzMF=GG>K2TxHD2R2o zMIyRLdIZ!nZ?6jSH6~i7CF%}G{Yp(_P|ODBTEI`CKi^P zStgi4*S*Ni#~{>0Y5%j{UasB%Go=+Ji`KboH2|q$ID3;?Ss|5DS(fxn<|@|H+(yD@ z-%tE*6;@^XTPwaT%*7y%{K$DHfP{H|b$PHPqS4b+!0o#>n3!ENSW!jYqFdY7yj73( zI|6Q{FD!fOTqQibC}QYrK#MD!=EE7tG@Jplz)$~b{V$%F7LxH#TK=a>`0oz_@7?5E zd1(n2v$Q+;Nt7|0gS_?z(}c=1wiS9wBZKd#Lzo1RV?O0ug{|X~dp%+fO4G`8UW+fb zz;{4SY+&Z0iGZ0;ynHoapLV&C%O^a*RG1?9w4w$~N%KJhfQmcR=T-7Az8xSkpMN$2 zKc}3;yOm_J6b&jpCKu=@@@cX;O*+cQ; z7z0(trE>0xbLHxCl1KXRP|6s7e4(Rej3v9=(MSTz*sw_1m93nP#oJVy3rNkb zGitD53(&SUTbZ#^m2wDOS%KeXyC)CUK3XOLsgP=30? zNl=}BnEo9}=a3ac`)s~M^vf$FzcnMLolNEbV*MnS2kYnLet%`ogB-AY)+^pn*3EC0KV#%jz|Rwb&%-=s1M%+3JbbdE*4mA1h((Kej0n~re=Zu)rAz+V zZZ@{`+?O*m(O263&FMzX@%vQhp;|H*os0yU;p6+-rbLkV@anq~nIoOf!ME89mSWzp zI0m<=$`#$T3VAHTu|uPd0$(Z-hm@ReU@eSmsK1~>{yBdf`Aq6_9_Uudgvg}gx3kL^ zG6@_u?xeJ{M13y?^d9=m)OHBWdp20U;7`bx;eg*)!K^Vi0GKprlR?U1vtMvtZvf{7 zArOw3`^Kv5Xk_X4+?(%AG_VB~pQs4na>?LC?3nVr3_ZR9R9g)nQ)O>f_Cisf56VTm6D=&|X@jou|zR5cLUsR0Q1+h!NNPnj|-?z|xKjGj@%gZ`2 zOm1Ofowg{sv?F+b3~txaXVd&yYyEPf=+UGL*n>-Z#5yrSul1PQ*5ueGpw=MqX=|BH zWts=n#JdZ?p9_^=@mO1zYfxdesQZ|QLP*=1ep)+XmR1Dwb_M2Four8eEp_e2~cKFC=GHd1$x^p**LM( z9pFzF(YcQ{svrEu^^)caVo~F@VGYBK03Z3T8HM6aGXszupS2xUy8cVGR1$04rF6BH zn@x4Bw?gLz_zUDQkQbpgFmu`MwYi%*1$Q-43aaLx`MD(v+fM?;z|~hbKe{FGihr!# z?NI0z=OS%m%zLbQgIOZ&pWc=KakB%=&#sg0h%(c1eGiWj^LIuwEbr{uzhQg1M2*oC zt1sQ5e#Xc^Bjr;CT9zX|bpTIkPQLT_dw{YfLPgQ_W{Wvd6)ML6ta%FPd`+%)|Ech5 zvj@&Oo~Jx4ovL^|jH=TbD06GoXK+OB?7yBtDpNn>V8}15B`Q&A83G4!`ZRgKC^q1O zm}$L3=`0u596ihLWt&+e2V3A)h$@^yj0pb7^Lkl7U^9V-I${My>Bn* z*#OoKv}e(aWsdr$->EF)0R0s#QaR^Nv73P27%eRa3f`=(gU3-`G8^w4WGG_5S{zde5}4HBIvACrs7_v?8rLhVKDS z+fSOwbrOW{g&;fJ0_lW$*E%33)?j>qlNjkYQu1(=a}Cf27k>p8n3xp=7*q{#aAw>w zopj$5kaA`pdIA2?B!!Z)(;Dj$fc2fUf&pzYTL@-kk?Q+35Q?m0AcJlDV62-* zce2RQi+cANUyn+F60HH8mYi?nM8y3GBN!1LrgmavMBDK-+!>R8O6d|1@lDT6fuI3X z9dQ6%y6GKS#v7W`0P}C6lan1z=l+^<1#;yb;6A=Tz?5~Em5?gjk3>pAh+KmiFnMSmGsZ*2aaw}DnuRNWsS%D#L^X>C zSFjq*dvI$aE(y~@|JAMqUFdR53VeUPIT3W%PF>ExJD!x?`cM>PiJ5be!+-hc?!1*X zyY$F9u;2V(1r*C{fQbddU~V+=>k^FiKA~)U4Q%FHy`327*r`@w1jfCJp%E5>SafKM z#-SDvS*I`!?`*ZyBwf`q=~H_MR=CecQ0Jz<6mGi-R10eFqI)#x3pIUcMb#;=!cL@i zTCSbzTA)Q;mZ5&UDYvFCx=aBGBS!GKlX)E03EGctBof;JfF{;o-RiAyyI(=9fRdfK(!Tw5oph>kP+mcf2?;08pXZHN#!DpGJ?)$yU{Pr$`fD1oJnH~ zM=D)n#+MIns4H|hnrEYzn2>@0`_e6W63(j7F6lzCA5(?b7dGxF;qX!aM+DexO6=*I z1eUz%OMSthNx8PqE;*_0&XYf?+6Im?P%PUWps&kiz2OQ_&|AO^a)_c*mZ3+SQ&5aZ zzll*YimM=y=1iE2Rv%^zr=344u5Gd|lY9!wMYQ$;1N44B8+%>QZJ7s|sk2h*x+nf+ zQ?S|1zBj?@(ze4~9^hpsSQM*m1=Y(*g&>Kpvp19aYSs3>69dH*Ed-S>Vx!V%;qmrL z$xg1lWV=k(aU=**TaW73UV@?9Ia^@4IqVOz9s!$0?_=pos~LB&Gj01S^avgI#VpgB zR`ZD{ZfC^EdaXWfigDj3@&6g@n9NN#Aa@EiF~k@Y*bT7jrwG<_qgbz(Hcym@zMk;L zkO}^=!gfT;j3!L@xZaDlOC90?ttddO!Uy9z#m*bCNPK&s3q(iYc0O5pPE0b7shv4J z7?&W?@r1Mld)|=R7U;Zj5>DXtLhf7w!K4aoHO<|{dl;_ULL-C(Ms>iy#d3w078r`5 zZSofl@1fSz{qJ>l8s6U_W$3}wAn5TiSl}%X**k;n!ad$x0x=&-MiO5E0v8)E?J=EO z|KmRJ`v<@>S_sYr_@}%o);gy2LGnN7`Cb&aE$L{}@dun;nGsuHTIVyk8R|ChIp%Ss z;N+mx+gWRcu&<>NXs#Ylf!iBQl4()}C2Qb6S##=9yc3ekemmvWu>=rrZ2?~P9nsX- zG_$a5=_Uyx7hr%$(W9iYUa2G7jfZo zmcr0aEl@jrr{(;YmM%W<{oK=Li<7?;e5Z_dP3j2BTWh@%W}!ZY}3qz~4pz{0I?@w10htr4fl2n@c)iRnpnGqjwK zloQ^YSct+Rvdux8fxl$C1?5TB08gDS-!~W&J!`??3EAJM4Qr1Q_D2?%JesV_73(zz zUIEnyfS0^DUsbNH?{H0q=?E{tIES-72K?T{p+g9jn4YM+bszBjoPZH+!dJIKV&4|* zlJm?Q!=vowPD)2}@4s5z#M)z=hX%7Wa^EGT?Kh`&x7A zxO4i(C!poDfx~~T*C^A6|N2HsmGrtG;H}Fwf&d2q`L-w4r7?BixU%1DC*qn{rus?c z)#a-ue&){kE}18B?Lj49lb(_yh5RqsLzP@2OM2UUMvBA9<>4I`9*x3Xf#GBkM7^W~ z*=a%p?~SH%t~_bhoHq+cF`H>h2OQWYs2k&U2px6Zcv21N-@(=Q;Qq^3re4b9k(||& zCWG6#op{gQXf*JNvyWd3&~(h{EGA>Ry04m@mF9aT6VmnUN`2QgkNkQJ;NzSwm6y?) zgUi70(%E}~nwjU*Y?8hKWG6XiR>APgLjVCYkS{$J@}cu?&+#d?8K-(uS=6I+GQdMU zcWAX>r=MWn(V*McJyjb#p1Nm8HPljU{)dKb2=>E3mWa_2JxL~MQ0`G9o+zT8_?v^E zSO*Vua2MHHrhZlGEllYbbBfQYuxjq&2|kRP2g>JWDu|37qiKr>VUFk)0n8n~!>J~v zuNXw#X#z%rb&ls~nvaoML>};ZrUjs1>ymjiry=p=RVgysh2H3;z%w#FLd^ZT1{Y;} z(*#jQ?e(}oY8rSAX3+9QXOQJ3){DL0XbhvM86#u^uwCs%;3wWkqG%0+JwHdYlTAs? zP2v}9(Z41{ANMLz2MyZ&2jE_NM&04smlx63^skMjRL1D5(qkco@2(J71WP5n#0F|kqR{v1FW8EK6pzR zCOLMnsV>~@T&RpzdMPkgGo=<~er+v0G(E&zcxm}rLb@ zIMDU68$gm@fo~f%>8~K!PgLtvDAleJ$dJQohBJSiL9@14b(L24d-ttAsm8S|J|rg_ zVef)@+M`?4vi%nK#I!k?!;^B^qi=ZyXdreKR*AJbb~9R~xYLeR%U1#tuVfyitk~Td zdaO9KZTLnA`69p8#&+rz_C2l5vxR7O@8-3(9I3wGwAgW=8d@7BAG!wX_$5|Q{o~yy z4SC6qkJPnnta^RNO|(bwO_m|*Bhr00?8r2%bDO2=2@~kGrFnhz$}YeQkfkhjQwD6( z3V|xM0Xs>b2pl@2WsVn`tjjpEd#&qQ&auVuYSoBUY}Xh8gq$fdaR)hh(LqwXvpit4 zPlV;v>v2^I{ceUMi~X|gTZqBfV3CZHra_29AcG+6XYZYo;ETLX$FT79sKiwLBvP9F z*ox{~!Y5LPOZ`-{6MC~Fea3ZR-&!_O7XhI!%Yrx|@F}Up9KWM{2^0sSlau6Bc)<1X z_hi1#36_8B*x}Zufv`g*eRsUVBXMyZPz26132uE(4mpcP&o^XRGBU3_KVJ$>hI=Do znhcH6Jf<_WjGOB*eiyRGJe)gK;X;g2%={hSX~<$^`f*S(7=1go7Q+m&DvXskr|M;1 z&^AXhw>9`Ech>(B>Uj-XRq01H##P(l$wKHy69n*<=>|@@h?xcj<_OO%|FE-Le}Uis zM_=+6(DmjLXi$7owVyX%Ip$`)u76*Fq}N=jBW}sGVc{HmaO<^bvsW!|6X54)0;r%n z_w911W>XD^A_Mz(`BMSYTuk9R4d>y~pcVM?^^=H#B8egcZg?2903S7B^QNTMdQl-D z^{4{-6mb_B#MO;q3R&m&W(tlW{_NbjGUo%eBDkoEm`Psbw!la2?D;#PcA zMMt6C0jFhHl>!qEgL%v@+HUSe>W_W9wI?-LrTD1*z?tq+V!ftmIe?m8`*O@s{#Am4JGt}HLs8!wVVJ6QTzLTSb)%Fpe^udLO^YZKvRG@qY7h7`;$%b8`P*?S(%dZ-I$H6TW zo+7Pj5)r0U%>fq}&#zCUYQbr0II$ut5?M&2^rR%Oj&nLxu~X-? zgeB$1n1A7$`1F7&Fb8W5`E{rq_z%#qIHadke)gI=DRpO@xJ_}NPCD)??WG&!1aicz z=eW6ZXiia5DhXtpb=!64+37W0^lhlNB27W%SWr^RAt@hU#=_%VPUs3ZXSFg>H zR`(3+)$K<*-Zj-VjygV%1-aaHN9;#ibYmp$ZRqNHn5_heZ-w#WOo*DyrO)rWpskCu zuBDHA%riXU>=CuRb%~LUd<%!q7~LK{9N`Q+mfJ|_Atj({mM4Js;soB4IN74FAk_{Y z9lCt-G5FC{DmnZeIQJ#Xg!99|7i8N1I7X7b=Cx;D@3e0o+GsBAjh@@?T^}Hh&%$)J z%nl3HchLJ#ISu}p{)EM%JP!yP5hc ze&2_(b1-r#Cv%4A4>DWiTtRW_PsE^$QYt&4C`=(@JC+ z1G@DwiKjQNH{TS=XTC1=JNxecn4$hf>SEQrO>93}$*%M5=Iq_JpOP|96z3@olkRRc zd&O7qzrT2_E9V1XIFYz-0JEQ?GO+*5>_sTm$U{RSA?Qohfw(YvKXgMdkPA3++h=4! zt}+=u%W%&=`KJ_CzT^_9Q1P>4;Yzv#iU)t>UWNXc2<#7EIK!Q~9hJzdFY@&?R)eYM z4n|$|v6&F6VB>3jpao1~Y`r^>rB(mKgG5zoE!rF*Ctq?Q+eSe&aO&q1Y*f83s4SlH zCW1wp1ci7QvDI7QWGrH?CpfG3(ene{`z|ZGSF+eo*HOJDDb#{HrXX%9`o2okG#78u zWK;N=n;Qr`%z1na`L)+kK!#QdEPdqpIlvSM!}N5#w;KtE-^g@X(ry0G<)7bM4%mrU zU4EmF>ofk>Bb!XCv=9A@dlwfg;0cO^cA_&>Xq~sZ)phS^pX)rjFUWhntny+#`IuBO zxP?1B?wBEG!K98=M>};4<$5`3GTMHu1=Af!>>|Wtc4;3VXX%^~3`W-}#AyahCQmgQ zU{>WPd_kc~6m?wHCM7=TC151j5V2>3-okvk{G$dr&WB)3(jNFU;a!r|GE!8u_n{}5 z#poFGL#_F?DdQC>W5yv~ra*t)@_n)5&2PS7FooyPw6IRv5B(4dGYyTRmNrZL4O^7U z5FU#&=FNphwS>JsVny6~ntYk`<}bg{h3U5ALai6U8*SwR@Pr$CZ!&jFsPgPdWj9!P z_bv7E*N6V1e*90X>Jc2);=lf?L2(o>-0li2IW95^Bd8~}^1w)=IZzv?IZ4YIPuvA} zwyzp8qH+EsbD^M5UNS$#9iF! zHH4q0$XJYf%VaxQfG2779#X4QeiP&_sLS>p?~2M1?EWJ;qC)esFUyvB^Lb{TCYoT9QD)UPdSxfLVL> zR->y?Ysx`uW^F6TNSy0FQ2%^7)k!1J6X0s3d_JaB`JzVG4^upS4X0=PE|VhzJrY?M z9U8o3v!(cq(ucoXGR1jJp7NMVy$&XGnmFRm{R_YbJmV(w)7kqJob z(>Y=TyS6iEZg7&&4dS9FLj`5Jc3WE6Ql)8ouKl34+SbWw+A^ISNLCwXkN-r6S7>Yk z5cU&8ChOVuM0LfUshKmD+xi=dI{?6x$fjFKdHC5{&7v)1_ioBoXCvyW53youM%(9X z1%>eVNNIH&{170DYg)i5?h~YPP^6ozo_K7x{5sEgVYR>fuQRKcHOtzqSAvQAugs!< zeFXzj5`_+7Zu`BG0y=G#u-eBB+*j^>(wlMjb&S#Z%&E#wm402)W7DExNz;@rqh-Bt z8-PERp~LW4Tt8qAhSp5}@d#Ob2 zO&QVw=h4u$>zXdTRQ{0>A~<7KvASn)#WaAs!w z0Znkl)kX&_VXAk}jQyGqsi{eR+fd^zx7%W-sMK9{g-S&SW-Yxz9-SN`YFs}hEljaF7yMCj*v54uuy7Rzuhzs1}GK4sc;xXWKF|V)S{YE ztsp{W`9r^vt9+?NN9Qk>+?$D{*=_hBl4)gg)*|XO0YBUuTEV)#o!}8|ITIopqdWHI+&gsY%$G_RbG!b+=QYafQ*vH)>(_$?_JA91v1IHX zKPGOA%3ec5de6cD`ON8#so6(+<7qI42(h~Zi9?mhj^;3Bn24wKo`%l#XUc(-Wni=Q z>-Rb-Eww4JkAMm9DZim_9RttK(6L=ht$1|DkGQqQNOO70XM@v<-x4A z&Sa!SR>L}Oe_bGgefOrAuhm~dg<|+1c^0d1c!JPg23C~+a zA-FJLiM)6crlLP&34p2sz?IVm^Ab2}-w(tEI@??YOGF;^O&we!tO{8snG^T(-ExQ* z$x|$m<#E5YyfmPqi8fdK;`lEoeSdY-f4;b$CR_FFmi?EK#n@kT)JJCGl1Gc7tR+I3 zBGB`=i~`h+jI?2aZ{PwQ42~J;t1(M#sm?*L^eL0wJw54GMek zbIDrmbMtf`1Y*IeI5;=;E*y%+FYqSeIeo{R#XsX0cLTJ%mml`A}Y^V z%JFfO`2p$XyR4G#WN$<$O9?$1Q-q2s&@IM)0(nQGT1Oyc0Gq~v+L`Z4vzBwweFWp< z{wYr!b+FSYf-kz;7~B|IZf`gZrHr9sCIxuMK3apBV6T#MZNN|bX;#8hP|}JcVWc~^ zwGbg;374ygZin)$>)H0##?W569i#k&n5DZt@k*q$f5pT{Ho9HKOh<|F`Vxwt2f9W1 zXuGLUx1&;c&l@F|LgpjdMsu2@zIb&BuAW7G9LB}M*!Qbn6D1;g(l9}Z3XhKHV=p>v zmAPGY;;;?!)IwW0&-zfbQ#xSUwy3mUsqKqN8~T9xG{r5#y)}ihm>*qTYD@x}biaSK zj*DnskM^+qlhyV=6a#<$QxOBI^=*wx;n4fEBg4Y+y*)OG_X{O2<3)`Kih#Of7%;Y; z^AiW&1DwK-C}$R1Vm(;=JU_``pT>@bRhW8H%i;B!Qc36&C#(_+x$^>&N)DnXr zDFtK7@f8sGmq`|@&vO7KXsjXL>8(-nV;Jz4WE!Yz555*biI(k&;WDA0fcJZ0BX$Rr zc8PqsyR7`U8_cWIrN9L5ep47F+a8ig!vfo3)sx|%MsFqW3v?K4rkh@;t&G+KE6OlC zz>jYb6yo!+`y2S#`C{Fbfq9QkftJcG8NirqIeZZ<{Seg(hDyfsevKjFKO+&sNiOG; z`HWZ31G_H?@`$Z=1DZ~alxX@+XSPH;v_#$?jOS;P?uCHIdJ-nR?8|o18%#Lmqgkx# zriqgxJugeRUu8Q&`k5(bJ)RyhD_(n@&s%iyk23x6Dx8rP8Ety(+u&Bd7TPu@i3dh~ z(#k+d;XmTjXP{wZbEnbNw3IsX9PZFk8mf@~=F ziR0v`kQ!R~u5mDCuceiBb~J<7Y?*&Uw+L+?lF0Q%TD?6;8wO4TLN-maGZtr*HEI9S z!T!xg{vV42s6L?aI~RGOHL-ucN@n2I`25UJGLuYe0M4JvFlnOLq5_cl%#D8i1o-Zk zDdN)g<*oIG3&W84@g^`Nkt?+KmyZXh@TGo%lW8DA2;&;V*9<^2cN|xNenq!R+fTz! zhnc8>j{^-%`FG#OjhE@h$9ioqOyYU;%R3zb)8YEB2_k$d6jioj7Kh0XeP1tj=0jvM z2~MA1oaTZ(yoh`dEFZ^=F5tdmQq0aF1AL~sy>x+L8rxVuIpD2BFqZmfsKy!s)-NNg zfII$`$!%P6werPQO7MIVATN)vNdB4#a1G+ZGGWT<5H&wnhDC){(Yb&=_Sg+bHY9rW zZL++F7JDe$S{}4W+uL4@xr!K%{c4vF^!`zCN-hxrY0KP*S90?Ew_rzLn;9 z1F!{H<$ioGuro^d1+u&b)5RxurP<$2M@C)fPpD8Ubjeg6*ad#7J5BF3bt!^rQJr9Ix zFp0ALC2>`kC+X$gb3B6yYnM4LY@XA5bl<P?FrIp1uhY_Sq&UKkbi%<}g$33!+Es)&k=IH5m-2Kk96ugumOQCqh53Hw>uzf!UT&+|1HzQ5Al6OBwoIvv8~I-sC7C^=t--}K zm0Mu`NA1GA_PoTod?7sTP5u;Y^TZhb6zw8;X-2sA{ zNotXyui=)6%ivOMMkGjqK`e4j;bn9RiIWnxX5BOBgVXpJZl0^cd^i&%!Kx_Uf_EuL z(bH~l7kU1Cpn%?daOaQ}2_FC*v8G|XG89Ka_@<}(Y2hos5 zftIS0~=)|rMVh%Uz}38rINf89 zZNZ76*w^|2`$Xr_>IE!2!pf!Ag#1?+(RhIW3cb-9+bcIrrKY2Ovoii7E?qT0B zmC3cwHaU*Gu2g|&gxv~=e$w46!1%dL{>AI|mLz2NvNTZqV!H0b4!F~47`yltA7k!{ zgUKjqPk32kk;rNf6C;B$X7bE@sKEECt-T-murLxo!=+i>vibLN=Eu05trpY!ESdjjT2ycL~(iWf}Td;rPGqqgW~p>uA>a%ezGwGY7l-K_xinG z3R$)!zFINKk%>dATH-3`)hc1_6plOXhX0O<{m)hY`}J)$&D?Lr<)+7h*I#~%C(_Tg z3eoFUFJL_=sVX*|yu=orr4?*Xn?u}qUhT8xLk?DEY3v*ByKg3Nq%0GgZh!|e4ERtN zPK5e*Q5tAd>vWf3f!H0uqH*)5LL+~*y?_fL-mZs=G)h33Z7i$urTY)pWkwz+ zU2qJq+NFTX)3F!vRGanP=qLlTZHZMTFrjVkAH$tM<>Z6t~ zU+~t!xv3h^+e3A`SUvmfi(BSU;BtC@-hyBqgI}@}9aLwV1ui)E)*_!ml-BMm)ToXP zVdXSgi`f-GRw=ooF5Yw!;f_=%Hy0NzuD8*?7j;tk{Q8+sY?OB zSNv-l?K}w!ckr*M3-iLUuPLeJo+xI~AQr~5-`z^zNM1Kz5WQ01I^6y}r#Ev0AN#$93sRWwct}$5A+KW z?5l48x}JCU@`lDwj@@g1yvxJqDD6mrJ6#>7Y@`;LA!Ho|I5--Pc&@Ra^=-e3%f`*u z8y)B{>eaxv`nfwohW6W&vkg$3uN#Q}5bL2{-kn0QU!A_Z1p4t0fG&9U1;zdj@KRv4 ztfM2JO3`JCQlX3YKxXfG#%54QgMJy0IG((Ao@kLK=UPwomPod4ia^_tS1BGvDW8t# z4|K(pDokMKsXN145Vb7N%vdq#VlCf9y5Mwb)HYFs#!2^cuy#T=%pYhK{fyAT>)SvpRRVMmDmX%-j)b;rjA|VA zX*)r>-HGVNp^=)z=CSteNVQcdP1ExAG3mUor@9z9Kzi3U{v50MqIw zbxeSJyKYY_ICZ~XPCZsF=?PI=Ge1-ReZDvUzR)huB5;YXvEJm_m=b_lZPRWjYA39{ zC?j4yz*OghrZMj#2_-Y*5@5Y~b@!cwTBk}&E_iKqLJU^JlN4WOM&ZS2=00wlVEB7v zAB(|@lV}}Cbzb8{<(G9*cdVFn1Dvu$f1I)ynA?Ecoz{>F_8=XWS)RYwqLQC%QFxQv zdcy<80dNuBrU-i{_*dym!RiN~qUsS)(X1Kawl+tfco&Cll6V*^LoL)_Z~Nzq1aCqm zmqWWQz6OWh7=73J_XFD|d5?eHs@k#KH*dopIIK7s&)j^~-Fs4Yv&OyS17Dg9;x43- zb}ZqD*97ReB{pJRGa-z{nUw*?MRrjb3+IlzWeysa?gr%K27LAmZCj%Xa}YC8G)XbL zw~!WX4;zRZ7iBlNqx?y=nkC81On^|TIr5|CtC#(f`MzZWx^*uBmA0@TIOs~gPnl^u zHW{ZIyncaz*(?M|n7CIT`~TVmVokUHFJMYdeuG?t3xi@~!UcX7iTeN!E3sez#FQ#W zUJMFrHp@)}3+PH0=3v7Dt4W|>LZxx3^<(rNCA<}JW+3AiddhGjO}^DCc&pjZ@pJFg7H1S{$q8tC8ZbSp zy0+H)%M(>M$J35^a(><2?=EgnX!Bh)#iW?a5oc6kf88m*yD#?kWnK}hCOI)h^0CI| ziDg1#=}U?KO}C>;2(RSsp|{K9I3JO~l-(caQ2T(vjcwI|_2A3UfXL*-w$~@^Y>as$ z`vcyT(OTN_XTN z!u&A>y?oaoSz--FUBCwJ%ixUShym^76>SlhU7;INqf5f^c4*x z=oj>HTQ~SQX7zJ%J4rHPVrQ4Xa+k;?Mv{?m3~s*9D2`P1?V{v;y~?PZ@dxum z_mg)Olmp!?nxg@;7|#1(KiCH<9h2#n=n6>DyZ)ve!UDiHVj#!m0m`W>6h2)!4(3SX zMp|#jSYs#&MW2_)cNtXnvUlq;-MD}p^v_LO_FuhLp!DJ^j&x6vy+_Zfhs@}~oq31# zni2P<=GjOzq#_(XOYqaBJbEi%&oL9koeoR))I9iYwep`ogQkqS^SL+mpReu?`4i|! zu%y06;NJ%^8CfUlKd#^|@X{UpL3Wf~IiBX5X`aXKYm&!7){QE(?_$5ox0wKzv3)HJ zsKrR26asqyu$KehEr&5*w<0>n%6gBFgT8N5%pZa_V;EeK%Ya7j&e@*K=LDfI>1aB< z0f60)Uw;A(S0A%x_1E)m{ewT3hhEPQMF4PCP`lTWmwI8m(osB_+5<`xy(t17$jzO-dn<~k2+3pKGW_#={10DK=o4DL z`(9ezB4ZU!G#=N1qNS9FH^24{_*j7NKG3a_sL>yMK$d@3ol<8U3??9O+F?4!*nV_* z&HiYFNnU)ygEaf12b8Q??nDUG`^5k$6r0oq$kQ@l#+S22qXoG*F^faM-=N^Zw|6&! z_|*Ntb2A4x(g&!;1-+jw&_`GNTsql~Dg(WgJ~##o0Gt0tDYyD#o%>2z{P3>@THhI~ z-}sFlZyp+Cv~rTj^GkcJ=+zIcX!p9=rI`P;OZvb~c|uYDUazKU&S6Vi#Il>{z_(rR zz-6fVGxvnYa<}yG{{7)i$bAf49I4wbH>DZAX~J$2`7s<1SY3X>{VwS5Yleb>u>LC5 zaD5N3t1^&tAGA!)xnq*3_`7k)(u8-Wi+`Ebul4m2{oKi&dpu3j=mfCGe{oY$i1?Wa z9DjHm&U-w=s4wMWqV00e(I@|#^wgTwCOYX};Y~GI*cCtED?>AV{CMg6HJE9MGa<%0 zO~_h3l(I9ZU(bu>kKVW! z!XMKV@3(UMsCWsRa!=U6;2>}GjqrcIKmK~>B4U7j{oUwKCT*AG^X1<5#=~WgJSE;L zP9+o!Ho7f4XWSe5sBe)e@&_8g!O`+e*p?MR3{SXfI8;{TNO)a>hwwi0)4HX#k4rANglh84c(l^^|vYFKX;0_3!+N79XwN3G`Vvt&;6q^36eWi z-#@wXZlLbHZ$v2?CknWMp2wbK@$r1*VvNMrw7Tdhe*406>8HQv4Z4{V11 zdYpg07{2D`fPc^Jl`$brm#p^Tu~73s@EMf-w8(o4{qH>G1$6ylXlMr5m-s-x%3-Ye z;g3~Q%8N`Uvk$Hf7xup0{Oij##h=2zXJp8$=_%WzvtNFBP5ruv`J}S`;enNYjcHz< zZd3Yg?HW&7JKP;{1+nkh_bv~AFjC*hFT45Ikr^XQK-?Oqocr{zFA81^pN3qP2I4NO zE(7^ZDbNOAGMojrM|$AO%YU@k=LWKWE-`2jC}mwDPZ4*0<#V{v^1aAZK@#9Rs%Dh; zIR3|BhM$?@DY+Cy)24;Mw{QOXZ)s7o2zD*qW}3v`J1Bt@EP=!~U*5L=y{YPUR800Z zXCVx52*5upKz2|9Mw(VIQ+yz?h}Vui2#0C7O&;SgSkeTEWTBZ)HgPNHi!FgL-P-2J z_2I*OpnLibjQ;G#KYhIS-bhL~-7QR31b%pYu(s-{TWS>vvlu+}PWb3H9cgYgA35QbQ0C%@(=S#M!_LIbp|pxo{GdB6J6TX3Pe?||E4 z7+~>EBvd?{ojF5wey3MJLX7)(kRHPFD&gh8r-g6HAF|#f`yZe1zhGsyo+aFrO}e0& z`0^jelx#hcM#w4xG7JgE`~ct6qnx*!vmMk11YtJn5ZaZ<{j=W_2`;Y^peoV@Ry7U) z?b!jut|12Z5mPW(=1RE8?A%~SKMraGzfR(XXYJ|PxBq`rtN-YaesMP^-qYq@{t)~w z`Jdlm=w*nis$c1xeGRzI084gz>`P#spkua_cB831iP!GdGvQ)D6TySIw>g-9mAA!n zSjWAb`pXaQ@AdP0ZT;K7p*Rhml{Tq*T-ZNbX@vTzHS+;rUu*|@g(66XJJ1g_#_RBt zVM$=wasXP|=PFm-uGtTKjuM-K58J+eKGi%u0p4g2G_r2^4>uFJ2Z2%9kEy9MyoN8( z30}YrvD~cbT%K|5rxn10Eo7wRzI$DC@G}P9223>gAR*o|KrURCy=8YGubuOf%lwd4 z^5JUhE@&q0mj{Z0n5-s9@EBm82G0NqN3gw1d~!tCaYQVx8E8c9fF)58)K~dHK(?8P zZ)3YCx%h+Aj?h?c9&ClkRdk$A$aw}H4h|0P?MxXUfU^gFq>pDCQFQapU`@I+4at=i z7}k7;(p#?R6s7~$wP6n@g_mMJ`;YPf&jk{#l>_!trA?l8!9xS_U=S9X-y3F zr^Vwu$Q^qQ*!%~a+Z{< zfU?D_CB%&|8q^Mb@3adpCMDL#?Z~DBBZ|=t8=(9*C%?#2-wk@I_UF{y#^67W*lD!h zm}=_2!!tz1<3MC;Fe~>o=nYnIQotUt;nY}~8s$DdC7Qhc`3;FYJIuTzo0*2v+UO7fI{$fsGW0V16#<-Xh&1^P9JiD1p zpzVw?ctmKzlG%>rVQ{+72WCrOou|=ap8W`18aClm2JBpiH+G(FdL!M=GolAZulR_3 z8au9lT7&<^?Q@gLuhwcbG2ip8$X~ZAcyT$s?$^fj^XtT5Zb^qC%mkRSxRX%}y{j4{ zAzUuQ^9L74T)jSmF?f9;Fw6Yw8?BwGaK7ekd_c+^*tu@DP{t|<17+g4ZGHmgYlhVx zf@($Py*Wx(Z#B|kV-Ur63k?QC`__qqTXMi4YBV&P{8D0{>5uSlg@%&3m|{Yb%JMPHuS{2$NFRf9NTr)2LcBJe567oPq-YEug`a>UPY+y35DfupIA^(t%-(~RtXmxf zpK$0Z)?vk>T%%7RdJP~)I77q&a~PWp?w-pbs2bYi*$IWZn-X=57I9jD%hpLu!PQgR zBW+ivgPyL(Zf~RzY4in-_Np*3+z^T{R~$u5*Ta%9+HBE~c-m*$50c+T%``Q~uqdRb zkRa*slDGgC^owQZm)(mO4K{|(*rCC2+;}WE{4*q2j_L)OP_d4i9#ea+UhDN|!Hj1m zeOHuEQ^8^fFoq>IXm-!R%rW^2Cc(NMO)zy#N zeb*()R5^M--F?qB#KTAk5O@22D{&|9|A46ayYv5V%Om-zRcPXfYu>ZJ;ThRbc771v zp(6w18#^rDHJI5waB5_P%YaBK9WYYeO1C+i4X=eJ&A{l|)hGGYBe5cOx~`@B&*n4FJ2^WFgKdLD3W zI0o?XsChzyF(qolnf4;!ZmVFi5Gi_CoGCZ7L2lJ{Z zOu!b1hofg6fOv9SCP7&wJrBxg6_p1rCmT#P+I~Ha92B2VpWb03C$Xc(bXNl>tb%)a z+EFUcB_1z>&EYnTsmYPXmagZA^jCnhuBKci2h&HQ$LF^~x7M>pVoya|> zMKVRX#(RZ^sF-*v2h4$aDj-d(wfBs&_R4n2{^X8`6m`R7w=5+@^YS&bH3)j zYQTY(m-Uw=GaBSy6DQTWK$w=r!a5z#+n`S|pDf|b2y#Lpvx926Yq(Gk1y~@9gaR{# z1NH(msGUcWuIXda!bEW2mFVU}J=q9f_`nK)ziMGR;K4m+{D9CsLx#M)E&lYfLyFv8 zm_={!uCVoa5V(}*tdeW0MI>Ep{1o~2&hL8(AuF~+33Sm-HqjfzCCjT2# z51+@KWh5hMU;jac6FJ9iJo^vN$A51A|9TxG?gwrK+VHuJj86b`iG_K%AA^V`>D7(O)xVv}@vb83PZ)oO&o5`ly>nde%Huyjboh1IS8o42n>3f< z-au9aU^Oa^+j9IA!h!sliwz3*HD${^wye@*o_r#?$UC&Lf!t;$Jm;xDMdQy(>LgW+ zvuL{cMM-Vy0xR35DZ&IWI98`Wx)pC~yo185gOugI2I>^4b+&X1%Ned@%gd9iC~LG5jw@l2!=b>?P#y+c3&R94OH} zRzWBalWa9Ad7Uf8*s`MW_`WUM+@T~+HlsKA2#GK3$W@Q6eg&LJWAURi78`v(=X;Xt zleyxZx*Z;QZ7lA&p`2vtkfvo>(RSa%sW#-PeA2g(kIc#{{Dpgpn78i!Hh}-Mb&PJ-nsKV&|s9wcweW>6lX95MNgUq}hFcA2?9sS4^PPx#C06!tGjV5Z> zZzLKwXiPz2_7z)a4g4j8-<~!0 zYJz58>61fO(D^+K zrPa1Yjqqc@7pIk36Z9;jSun;}a2HyDAzsB5yGJ++Ur33f!+>-?0@gFaxC)kqo7O*Z z7^C+)<4>MU2Vh8@EI=}k2rd?i{6vWSK@m?+RvVlS+K?C4zIn4rEQHjX1s*o*&=DSF z=JDd@89gYr2m-duxw8uwy+=nT56N4R{Mzri>Pw9_+b~7+#4Z z{(95T`lI)B3@I6!j^;e&aa2o26c=wu{+pVYnTUX$(Ao=GPjlbaU7Eb^4mRI}c;e$4 z;BfH{s3rb(sHYGl_{l)B2jldD7BJ@}sG}ms{5O7O3?spsPd=ESf3I<0`>crg5+f7-t+J=#^Iazraa-1fe7;wJBW6cDPXOBh7*21}n}<-ZHKO8J)TUj57qECYXe-mZ zGNgvZIP&ci-WLC0P2zTHSER>T_qyRby}oaH1O{=vJ2+Ru%kmCC^*jL6LM{+N-Oseu zf5~>wtp?C$KED)o7_tB#Es0c;4Tl2(!61YJWcuv1q0+sGa@uUBeFFwuz^GTfXdx)N zck<7j{lDlY&iMoO`5C$U|IMM?BIp$UGE8#-6nWI#gwq28E%cBvMM)@%L!vi+mnd)n zMnG#z|KxB3)@50YO9ec&j?gMZI5WE~-~<<960T^E7!aJ6L44rREvj1qlhRugt(j>6 z`tNy$>Esv#GO~HHWza=@fcn229e!vq4G{%mAMRm}(=ffk1K^5g&9IsL25NkZ=aTN_ zP&p3#i4v}GXC(8dyfVXN;7?N-y~F>I)q@;sw|u{Uu+xF2+Nv2PK42!Z0|wgS#YScQ zuP>`64S=^$5if~^wPpG{s`~!CjqY?|#Hk2Ilk~E!a2lpbJbvdQUAgM7tlyBwOhpmX z+ijx(kck?U%-qZj>;>&&6H03C9R1JJ8orRe!A`Pfr95q`WImwo2s&qV@z;jv2?g7| z2TViuY+{{;q{lkAwewTvheBaDP1#26xPy2o{<4+&zczi$nZ*1%^;6zBYiqS|_bvuW zw=z|}k6(EcX!s5w*RgW@K{H^HY_#CD2#8X{ptra7-ioRPKJVo~NhaB&3dlsaGhTXJ z@CA2Z&C!#C;qej4hs_NcK0EhCjhek2sh&#$MRuE>jRE3AFH{8hVfdB9AXT7V=v1 zh$>~Hn@8(Eo=X=vZhzeAF)iH-97HQ@Y|)N9m8~C|eS*uIr?MlwAkM4fvJcq)op;<< zm7sLv5#OORyO#^;3i-rdF4eoO(s@88K z$2!J7-+Y9uLpD6;WFLXP9FlRMx0tZ>&wC)WZ4RD0%rP~#4{EmosG*vh2km^r&$d52 zfDX6KPwM@lbVw2B30Vkmg!nkC(uaVpTkSMAUDPEs0oW@Kdk?)YQF-m`+WuHvTZG;G z>V8R0!tyd>(u47>9^L&vnd&j)VD{SKgue+i-+wJzW;+;-nAxebNG%?|+ZMql5d?gV zMx@X9ulotu;7P(jg;_K8nUBQ_nJ&`BMg5qIrC& z8z_}V)+U&ygmmkeCjs(0*SFgOz|3VM%to4DNS4ca0U{B^1V3j&KA5j{kxk)%jgBL8 zJIOO_Pu(mK(2ydv_%*t(%|G`e?G_5)Gy=uUA~5lJIK@U3iJRab+@x@;1gAt9s!)dL zt_O=}6Qz#Wn6pVtm>&lb_m^u!4G@jA-@rA}>%OW)*<~W;4aQbk7w3s2*RDFAmP+M- zDNUGx)5o9M)k-d>!!X_E%n>`ykLymc1(=Tr(L8MuqQy7bOzSD2gIi>X)B@zSR?W+* zXoqph0`T@aqgP37*JihZrRJm8AfIlGR-`~ow-j-Pb%w_)FRqp8x?sGop=B+Acq3)zmE`F=zr6s|z2r!#tRe&iq~(1+3K+HgB7dB9 zOYrL5S85OL(9yn@|Ezc{XYM_qVW#r5l_r6S;}Siq5Dly;tp3-a*!u?+oWE{Ivg|U;Rk>6Y^w3PHh7K_CtU_PK#b{ZuCCT#bJt3Z@Qmd zyFyNc%>KjivX3Pu(pQlOOc~hgyos$*&ffk#mYzd4#OM zo2HwxINj)|`3}^M4?wphP0s}|gVBQPX?|SgWYdK!^n%!s&zI7gxnn>EI7$ z&ES}zL*O8Ob$1i)az5Y`>44@K0IFGaTxcrAf4q5-o)unCW27t)qd15>jJ; z2t34(_D72<+UVh=_|**l&(@voVYoU4PB&0{NwP4GeOVV)@_gBmbq8E#-V_|?6c)CD z5{c$?Q9k?zElmo3i-zwIbAL{!FG7)ro$kzF(nQCp9Y8T(N)c*p7PsaPlaqrvtXpe} zCN9;#urdkr<2DNGyQ+IRd?|u}GcY*6KE1qBF^&G%?} ze&8HN!ra?1Q6_|ZYjYd?N$(;77aPbmw5iElXbCSWUY}``G{(7ZMD2n$0$9fmJ7l*B zr9RuOXOMX0ycV@*MGued2cox;ouB>2OdG!_pI!f|4!g!Pbp1K)3;Yrk6foQDkwO#M zg1|`^XS#niqG+Ijp>X2CS=^N-FM9|bv9|nFl%zvKJ!lj%n#FlaN(!yZ6BRm(b%7}7 zqTTg1$5{db2M`RLbFuMZ1QR*an&o=E5PYhPUqikAk>FtPnJKYmW!*=y#YDKuVg%!S zz}7j*C*7#oCf!r!Zz9fs(MHf!G1gp2xa82R&=4U|4OCB(NZJft-4t>+I1-uL%ShvH z53G(07a}$$XCpVrqo$7_&-;gaLcSr^yv>1-TgtrYWt|zA%p1|^#4^f8hcfr}XwFF2 z4jKWY#dWF>oo5z2f86QH6HOS(>6(Phr69Yf#TwmGEfCLDG>IXfE{AYPcv@n;PL-vf z%v>iTw^*06pWbx6nabd$P|Eonr5|`Pr1>C^;sP}%S@4%Xw7@TKGSeNAuC8@nnW$=} zC&1|u1+8p*I95&)=?Jf8c0L!MczSw7DEt$74}3Kg^pu~{4p34Y_5ED&C7YzXmRWpF zrRnpRW{<)7lKv~Q>P*7(WAzjlrsiSJ9P2slU!PE}R-8h!4VBhgXe(bb9~mC)=OguR zWKt8Z(fRbenOgWWD^ivU&=!)EQf~e;wTbxz&OBjaDNO33%Q~GadS!@t$K*3ij<}hG zf~cQHc&h0flj3bKCrbB<4di6+MBvwR79vH*oCEF}UB`z%ZZs$DW@c7xLcEF*Eu1-e zCxdmuENXZl-dPSK?g^wc%CepIBwhHGY?UzU^yDB7g=20ut0S0JLh=27q) zASFmigM=cDbT=v>NH@~mEiJ8tG)PIegmia@l+xXeboc*$?i2f-|J;4=8Fvpi1Cd&5 zy)ox}Dpu7UJqQ>6pf%8&8SbTxu$Ny6EtYS>!)w{1)J67(CAjxZA)ER8K_8^XAQ#FH zA_dLu7puN;A>Nb-S6rk&MfvgR^-`npY|5#&hJbtUdPykWhulH~{3J2m8-|U__B`+k z*UK0(23`+a$Vm|p7h9W| z?)%28f^`&vevGn{lBZ*^hSO!k8aF=!rlwZ=rXi8fO*XZsr46s9S79cKPf#RX~hs{wps}}TVgWO2(m?gB|XB+<=8$!tS>p?i!QK1 znR0awOtnh{+%LI)KGI{Ok3L!%7C-KHzJDedHMugMnoCAwOJH1q)k|9+)*9e>1S^=-MWwMpuU_L+#-^N+BE?tE9@21 zo2r5UXSIi3>*Vgdmy(TPKY>t(a}eH^;OPP6r9K;!@$uJZe`dEWq4(|6Ki5*`wdgx% z5SkcyEDGl1V@3tTSU24|X%kNW7>gQ6>-byVWnM?Puuuqoj1`REqMck1FrsKG%}e_` z8$zfP&PS8J(w9`ZtdSaoeetC5O)eARB9dFG+< z(0$*}9Zk<9sFEx?TFCM4iy#eP)IBpV(D5H`%{yVLsWZ$`1g}r ze4KRsj47MW$%1M`7(Y$ay8!2}T?lQ3qYyyFeg4Wzq&739;2@O57P*txiBJDSNYH^a z0Srp(<5xWN`x_w-rX{;OG2pUzyyK7K+WTIaQEIxiVPVZ>I~RRgptvNaotsgWjOakY z9C6l{d;N-w{+>SuW#7I)>npq94*dA*U#P-ZSXG06Q{-IlYRn_`>7e3$Pz@N1WT*T_ zuG6N9QF6e6{%lTFD58UuAm{?{zhBHRqZ4t^FB!rycz8>th}K(o!Y}%?a8lPF9r&zA ziQGYf1D@35oa>)XeaH%|=NlvRk+!efJ=*mH`dfpU@h0p^l7R-gn9SvLktW!daQ96j z(STfOr-S!8TPI-?a7)$r$-=)LKgQjiXr9=?t%l7urD_u4=&!<6KPH=^7~Da8(1_*U zPxg5~UG`O=^Fmah5DT2d(0S~oU{B(~NSi@M3Z^9aWjq%BPblc8eV6a0n#Gq6|F(xP zgz2tLuM6-@;E%+sWIjwJ+cBwlHNKumgt@duI^Dcl5XTly;DpUlaE*j|6! zvRGItd>mF_i zTfeW%-taCs_VD3r!(n;MZUfeNRnsS5gHDF%l^>syGl)l{+P1!;IXFD%qNdVX7-Hso z9{q}Lqw+&{xQqw>I3ZnFw%#PR3G?f|H+srKhBiFa$drbyS5qGzU?n=!TAUQ=)R^X% z6ryU)l-8Q%bv85S2aBpxj$`}&(p_Rc3~)%2;KOxC`0GhpBo&kC&@;Tavu;U`P(v^R z4g%cyj}NBjD=pQj$n;y;NH{U5J6zEpc^oumEqc^3nO> z5p3B;^|evG*T+|whb#Va$*Sv&)LaR?PF51IrHZ{<{H-55j!<%!vgl19!IvO`N&ppQ zyEy?Y%Q=;K04$f2bE@uvVEx46HwLWUPUs}%wZ?h{!g9ZoCmZd*5UWezveo-OdipeQ z!~A(1hL7~`!*T`D+v1pYX*L5Ik*ipII5=2q`GNjYsMBWzsU!@zhVzX|RTbR2cujBv zNwjEi7x}}CJ*;hl*Q6b1Qis?KZ+Karn{!+ytL1%){3E0e38JziVekCS8Q~uY1oRF9 zq0_V_r@mKIG$AC~c-XjP8-iEqAu_8U%1ud*uJO?5s$4!TxgfSlaY#}1@7TqE`4)fw zptldjLI(+`j_sa?tJah;J$;HkCzqq=j7|s)=bwYn)8{drt)|XdIKXB2bf~7JPL>E zZ{;E_%lemlfUT1mC)sKAg3IrW&bhr5hfcZrrL$GrFz(tQ)^uZ|g+D?4;TxgO2@!hz z2w`hy<{p_h*^dG4@LdURfU)xyK<=#LB@5_`$Lhs8-p|!a+aooxA2GglW+W#`9{9px zxy4s=UP)r!>cOn=2-{MYwrUrk zPOb9T6wHOW+5F3VLg?UGv(Pfof&T*2lM2A4s|_o9kgs;SJIlL_L!ZEIZUkAn$Z%}# zU3)Mmz7xil{i{0a6`3V05;s#jLtroyXg}Xz(~sMJ5J1XSrA8fu{Cgo^lR@{m@u9Sr zh`iecWxu{=gnq|iJSUf%^y$i#0RtzWpZZp3Ag2$be36(w`3Ar}E@;c*{V3hQsTMbb zVFE~vXPtoChy8=Y7zWL)(<4OYN#M3jctLF5mO>PIW!Z_aBqdK}5suhYW?E7oX2=?5 zFeG6d{L~pOa#4nRA-TXSm}3UmZMiK4QfW*>7Bj(vV4}Oi=LAL8F;p+WuFq1$^B65B z8kY?OPANgul?n`rfjDOJSXo$fZ!iL^z;f=)cblldWvmbV{StB@J*#bk53{$Hu1pc0 ztS)jvPj7kG`aR@FHF)AX8xn5i<0vG^oo8aBS>W*Qy>lFNo3iYBVGBuF*zy8#_ z#aX;)7zk%@A)>bVPw)!R>z~1b)P_ulUlTtY!ky5cf!0L6z`u3K+EebaUBnys? z6>1WF!9KDDrq_<^PgZ~rN)Z73wFb&?o^t;JbhbX6BKa(di1~nkeI49hRg46uGw1h5 zYuh3&`%~D12};Q9f^F#;Cri-l%jHLv#`B)ge{Qaj!qknv6d z`-CUV5eg`HDsi|wlB+M>mitH+xT37D4h0R))89!1aYCNyakfEzj~F`Sa;mA<&8f6f%(1;0kBW*0c}j0 zi+HOUE&d(G(NI<@(NjpKhHvAX8=M2gRewKh z|LqA3l1p)61m_I_`^J`Eis`^*cczBGP`$y`fvVtzMhDy~#H%HFzb~8s0yz1>LF=bd zl)B$;+ZlZQR`4e&d0!{JKg2%cCDYgWg#Th4p)DVoq_#Ox#3>7|knTXX2Ma z9A+cbRJ(eZ)h6DmfVuNjZK38vb#9!XOnX}6&rQT(iFP`CN4KfdbuY&_+B-$=68uX* z6W9@exSmjSm7^ci0^ru#TMEj3fhK?jtUI*HIYOSqL${cIE^ffT^x*-%Bu2QOOWDEP z`_@ACl+fSIJ+daGXRcP4SL&rV!5emVjM=2o)THxx2L9 z@C%g4Fy1n?v3FO=7pnXezl+~#es6j3|IWR8uq@Wq%1J;gd#CoR$@6>>kq9ugr4l&4 zO^l1+{I4k0e|iBX8j;FD1F3{xga??w!D<)4tAJsx|==n^1*L!n?)kBA2ibUUvT z0U_=KvE3C{=;Cu)$;2fzgj=R@L}3(1@R$)ouPbUyex`T(OoCRlOB)eZeXe%`u;7B3 zka~)-q`97iZ3OrHaMo<~vCo|eeRfM0OsCygk8%N6?Onkofa|Oe>uSp}rRSjvXe}D0 z0niy0O{(@GJ8(R9uEC8cd7Y^~3S7ioY!)`gzxM_oNd3?`IJCHO+}xvqQ?0Qx%xp*j zzbC9x@+lzRw>aKW|ImZMQ26II3+vE0Zc<^YLA!J1wx&L_mydKPC&nit;<( z0jyd_IoH!)1cWE&%VADef*{ZiVxqrnqX(seiz$TfB{{K@BI#-XzUu5CU~2beOU5su zi!@@+Yk<5@TdEu}SiF)DKu#Btz)ln*os9n&0*d~b_X3z9S_lWYLLT>BXjKKn7VZcK0XqB{4lSvJDSV^N zn9*2ofuKPu9{2h-E!z&9T>@ty01*Y&z*U}e*+-ItnFW(uZrO@z@PAmZy$%G27|kNB zhj)W&FpiuJYnW6V)00il!XWJsrQdmW|Iy~5CV|5U;|Dp11NvhS85}YRd4fGzZW{Fs zFpwW4?I(UP&Nq0)*zy)kjHa`Ks<(h-gY&~v;hzJ*cn4CzIm*RR&jL=o&T+RRKoWm} z4zLo^y-|}_+AO|s1BR6ke-c5636z{U>zFQxq(Q4v_{(P&m|#esFMWI=xo~?me`f_v zF*5~TtHlQz)B=|TB#b<2qGwcyLu#WIzYNZAi~szvR+ob&hWI~>*gdmep&1> z1+XXNT%w_L0a73g1LiRC zB-iA~uh+N*K>V2#qd`LBFu2I~Hl96g8h%bk(qCAAC=rV`*a}g!LDKxncOk(gpsOf3 z8Wfxl9Cz`90@)(?h9^xxgk%s05H_483X$zyy$u}d{k^y-X*2#tU(1w9mAsV0Df^1G zpesX#xC}pNRkvewt|!9xW0=qGh}9sQRjP=ukHALe!8@q8Sjc({c(ow|kC$p+(Ju&*e7);Q zspj1&kJM1g31XnJ+!1#R~l-W(E~1oJoFrZ)zZT->Gz1Jx`gXU-e^m_ z0|XAj@0Zt^Tsi}ym!f&&tmGy|`OctHuu^!o7~l@WyMTOCfP-0NEBQstnG5Jj&RSmL zCYQzyuA*Ao2GB&Ye|YO0ohAi%1=gMH9gkVoKH3&yywUAD0XYKsky2xUn5_KklXC!GT7IYqPurD4D5JZtU?0G$0^_iy1=yy>4?bdW!K z%FKgvJzNELQr#XPz*M)o4H_Jny%2+`;J1&)-z72e|$6P-? zE`G#WVkM28XKXl*RNoAYHSHnP1*{79D%VFoY|0!<6n_5*^ZVaijNo&0uAbR|ybhwM zNK95;=NdgLX>i@{0CNxadde()BqNY#Y8CM6bpjh^6jPI5N7TUryFoVw;PJfdTfxj^ zO8e3?4g?%a%=NEIHta#Gr{9UrYtupP#VsZgI{;|nj=({2 z(Qkjrr<||+9MXFyo|V5|(5v(|#-4hz(;75??ZlDq(~T|{BWPVN&PbwfH4VA@00YS4 zpA7QMl)Yut+?J7!pQvqsOJQLHD8NT5v?+JW7My8gLhO@6coe8UBpN3<#9*mkZim}{ z$RR9jBV;#Q$t5JYy97K5+~9S>mT8hD=C%AMD{kOYe7epnW3U6=U*51};iNag#d^TG zJE^ef;{xu{l5H}lKZ)ztZR-nT1=aVbhHsTWG&{dsRtx&+uanH_b3Bm5TX)6o{#i1_ z7%!O$GbDl|W{Z`7_IE#TdV})^or8?So47JiEmEbiT{@?ol>673ZeeK3oRdLGF5MlI zG)Q~DDRYMy{C3MC+W;IgrYP?xcZTE(LWhn+IbM7<2TucIO-A+rK42&8V%mX1W1Sha z9~`<0Ic+=DDJ3jO@ZAmdIEj*bm;dHkK9zln1XrhOfhdR+z^wfB_XOm(CeUIY%HZC- zx8L-HamSZbhH^CaLLm9SSK^Q*z_Hy%OMNLBei7bYkKL{qQWaRb|M0UE`7Ge9)|7mA zHYMLWKv5z;1qZag1~WD3f!Z(dIyntUT&PaCg5Jl9#ldDkru3vUV*;=KSAQBLRQtE7?`EaX`2lii3Z`Zxa028pe#Diw;4uLz(`qfnql|(UmW2l)ZY+bX z*G!jI0jti+WY45W!3?j|eNeGCYabc}$&MgFb|1HVmY=33k!S{cQzR>5#UxR=A9=>& zMRuT{tp617=PVNtV|znsGS*g%jLE2640gn;p|0ngcP93a7ZoSAgaP7L0uu0Qxawz` zcWU?I_S4~*35Y3`Nk17*z9v_mLTcZj*KO1&2v|CUU;er2ec!hB-R6?A{6Uu*h?%vl zfA|Hoji5<-9_D2MQWqJxc6HDN&UHvf12=&>eTmDiq>M#D767666APpd>QkSPEI%$L z4AvGQ!;nn)=iK?f0U`e76Q*fk;E0i49GWvrto43yp^?DlT-6_tLO3(31S&%zFxD2cm~P{tQ?D{aaSPgq;R)D}y?@&WK0JT>=ez-FiPIF=%xII%LBTQNs+XExT^EmO6sI zfxfGytrDcqo+aQYfbn_Ew(7nZxNr24yGtWPnToDwP74PygBQ(ke-iuUj{&(N!Q6;w z7|D+ELo>jjdn*DWpkhnG7xEma#*sb$_5nxyKYm!11eeLJ$JU4@`cxWcO1y`vKqqg<+lT5Hk5H7bZK7}Yfu4Ox|R4ydb zx>m}OPSUu_@NDNz4q;0_>ODRKPUw~ciQLj;RgODvmpM~_bq%-C5Ogbm>d`H96oi^> z%v5ujkM-3QSp#L-3zZ#b?<+9uOL7jD3HGPl5g=BF8bHs~DoUVv0T11q%O{&mJ`r8~$Sg@W%`Azk7>K0SiV^r(m#wm-STSyInu~_ynjN%)z%U2QQD5?~%|5qh^*U@C8u&ZHeez-n~f|6>m{c9VdkU<4Rq z<||xtJu!^hR*!>>4?>N}L!4cx+$?$`DNcvpFiwIeArS*2Gy>~s%Y0zi3TX}@u?o{A z7y;;026izEfR$bbR0N~nbl5;+v)*6E+5}BbVq}mm6Ek0h!^V#m1hmH{&i+J9 zI$q!jqQieR{Xf6t|KA}gj`3Cb+n0lge`*Q;^i)2R5rQpUQNsxe4``_`HV1LoRba7p z(K`VR=PWZ{3_QGn^DscbCTNnOS?JoLMJ6We0XCW}Czyq*)&bc_e_aGBC72<7S{RI* z20l(UFPPeO08qj*B8XP9sjli|2H2Is)U9`&m%>i5xyGC*PfNg$?gRa=1rev!JCfP}*(xhd zD!aF!Cjct8$?u;ZSW^P3V`#hwsL11;yS<@V+b?#AYCb&=Tt{UO@DZ_GOi|ucTTGVz z_ETgufN(pXI>69S2RQ}y@Qgsjj1^W=20DBW;5zVIM3dZtG-&ic&0YWZQ;%*&*sMc3 z-7NKeI1KL_AlPMC1{d`+dM|We&ToM2FWL%tqXSlMV5G@m@*}nTcA*n^9a;3nF}G;e zRF*}E7Q*RYQvrlv? ze-66^kXt~sxoNN&Ex`0RLT9cGPiqXL9s&l5U$UJ68vNV&M)!~%rk8MH4d4ke1vIp5 zXpO5B0}aIF#?Opd0lvgVOZo^PoSgtOldbv&Xto47F09`?m*e}JcJlx7nE&>*-tRyp z30340uq4-l0{|ue`YLU_{8Kgn7#CuRFNWj;q7}niP;XlRi8lxE-Jt4wk@zw88#rQW zmMu~o#?&Caa%UeUk!ic+wI?E&?HL1%%B~5c_8?cYu2R!=Gs{XF3>uRbP!GmIRl6cE zVhdcs2T<^J!+<9SIA4U43ozUuw95~Tcni)9;tA->g7#{i`(X(oeoRM*naJywID;Xj3lIiJty9bTUpPoPhu5dz{L$S`)jf+iK-H;nz!H< z{{<2y1Ght-(~6&Ag&BfJTs$p$j}z1%#X3_||1BxzKRu%fFeetnEMw%5r^Q#=tVq_( zE;rr9tf<&;^S^+(KqXKH63sgg(yCYf(ngG$`7TNrSei~#1k67$KDhi;f0qcJhFVv$ zTUrH52gLUQgWdNB4L5B97{WaMATfQ`_>*f^2jrR+i6X=fM!n~rr@L^Hh3Rv5cTT5$ z29e?~UcBy>e*NMeR?NN9@7ZKQNG3wnaPS>&N(Pv#RIYbnu0_=_$Uf--^ywCuudBW2 zOFvRzJb0pu0uzZ*S`=k@dU2Lh?8i!#lM}nSxw-2yek6HW;E<=a-j^#OKhFS%A#~3> z6Ye^;1xl}VZwYFA+;MmQFujqfV{aJ?2KwiJdE;&IVE;~gGIEUviOlOBEYeDq(36`x zyqlD34_q34*xw(VeAEs4n=MSX$wz%9+mgJl7NOD9ZXI%|(XiP(Q7jQ+>D%T)Nk)&i zscCEqSaY?TJhDk2{qd!LeAD0G`9FDcK_+xhEz-$!ikY9&i(dRG+RK0az5nH5{PkbG zA7fDulpM-F{x?s+Uw`Gl{HyoF2N*&zPhOV_|DS#z7&tpAuY08$b>yEB|K%tAr+@7Z zzXxML;PZ^=KY3{0VenRf5L~yJolsCxaSjv?vO>y^74{o+1uFbmelV;y^|Pns1;0k>I?~Ei z9lw&xl#gNump}?UAtB+f7;IhP*k}o`Yq?pPk(<@bi`OnqZohJkmQNAVL1doo7 zPcHa|7JvFqTb7>Q%~D=j`Bv_i@p5Tat_wZUpT7K`-{>FjxfV79 zwWT4QazQcc09PB(dEUJa0A0u+;E!<=aahDbAV5S{0odanr)4Q>wzefVfZAUPWb7g& zu{$9Ua9&YfJ^`>%OG87$$;S6XF@4#*I4qHeFz9H3DJN{Wi_%sb{ht}G$T znjL^AFwLrfjdT3aTl;zmZJ%`&zYS$&WkIMeWTs*XK=l&fQdYjB|D;it$an&4%3H@C+0E8WKtJ>YezO3s2E+{+s+Bas#WqX+GcTnOFgoJ@ntROE4 z=CuT+6$6I$9_`HyUD9zkdDsMKluYKY=FWz=lk71zKHp;vclZ<*_0K2U)knzumtX}) zUy>#1?WS1eMUu*|*)EbwhdlRUpW8Ib8S%Y1WnHWCK08-f!)p zAFJsY-*C`L6v6(rsL1KcAvngK+x;*q<(>E2Ng$Lqi0xJWj0yu+D@`_$lbfHJh_kf zwp0nDJQW31Dq~x?n!SA)Z(3$%`?s9w`C&XyJ^(dxfP5+k8BL&eoaP=qEmUZ^_cokXbT-b&w$OdyCre~Y2#-7@f8r&y2G4e+ zW@%|T12cYkGvYz7w5i~PCmJX4a^r#YxPRp>Y8N;R4kxRa$Us*A}7kZ}F z?J%e~`@L6?aC=>_EhblM9hA(R@TW8ztci!Yf&>h_+ZW``4-GEti>PV-@gRi|VTthS z&16zs->L7%`Lr+HP&ZrjXjV-w)miP3b%i-rRF+R&P8^&Z87C;kPGvjISB9Wym1KV- zy;*Jw9eQZ^+}qmd=Vc`h=~T80qni1!a{gDE3Z+4QQ`8EgM_OU`|Nr~)&*!siXfv?l zvC7ISxqI`rBJcV6GgUXiX*po1J7d&D!YA4*a4+OuY4OADzr85oGO)-)kn5Z#P;^*1 zlJs966?xv!rQ`{zVRjS1kRD_2u^J`EXRTQ|R^)b8S zz-}}Qjtu_i?^XLos6`(HTgy9LL?{f3bCt!xc3}%u+6r4_m*x`3)|NERaWtG2Ds{LH z7)Dc!9o{~gu67NHRy?sS3mdhb%_|BoTbl6vHEKDlw;CO-Jd{85_B*Y`)uod1%uLr? ziJ$`ARm8DJy+I%Ta%p*a;eGx3wHUHrfsQjgxJtl9xYFD`g2v=25Dp93s#qbEIwH0! zL(W=YzEuHE+8UVg#T#TEH=yyd1l_l?f`UF2j+KyW0XFsn(k~;IiQM)YF3>n5y5x=s z^5&l{FaaZut^I3Ivn33ST9_h#QD{(_5B**O8es@ho;krb$g%GXBejNTT$X0BA{yl_)kbo5chZFPL0g>@T#~4vIU9 zh^uf~Gw9Ax$^|K8`ESpccWbx+?lMiB z0drLwx;uWlGi?d%>UJk18j`0KqaH#L6AJE-oE@@(U2OAD*!4}$co+3h5pgu@>(}nt z1ds&8b66v>egTm^bN2<4P z8@EZ`ud$|>^6r8;nf;l@VAMkg;+p}8L%~mu>^$mtb4wZZXi|h<>`R*HU|=#Yzc2FB zNl@8O_e+27tKdd}fjiVrt*)LBILVc%IZK9J_1(*dFzCYPa#z_L5|(vyL}rLU0X*Xv zJsIcg}J4$K};guQjgPIRH^8WS)plWkIu6}Hf@~Zu91Kxpt9{cn9qm& zNRCwM=Gpw&Cs&pHu%5G!_fMEd{JO<% z?x$!0mr96injclU$tRevUVob*$ay~b=*rF(GI4evKd~H%{mG7ljh!erm=d)iusvTDE!aT3rj@{ma;EXEbs4aWq!2xUQUamm+QT1_^ zdCG~DA=U&5PnN(pwn(tH@R8d+UHnPJe>(Nw6$$0F=+o|e%^lX*k28AuCh_gJnvy4{ zjC{{`jcw-j)Ol>E=<*0mh~~9T^0lsFPbLjNoDj25DfhXw(B`?R-|?T8EG7BBm713b z>PVa%yIfNxDWU6t?SK8JAM)=m88~>hbCvu4?EBpKLfJ5hga%(*0;dXL>IuDaTf&jA z_r=#~Xo{)$FkHb6aq0P5_z3Y_QV=5>ru`W}RO-I9bguVJ&@a{-();=`}U>jw1D##W? zIo++RKo^}b|{)D%_SXVz2g?a5-*ed*ClaG`zxUlvrb6zPWTl!{WT0$vI zXK3Lag&Mr?85@^s6QTgR_L|F)z@?`-{3pM?j|c>Gp8bkxsUOV?YdX0v=gC*IZssor zoTeJ^d{!SYZr^S_MioWB9iXKap5ETtnyFg?g|I2nyP_+KAi(VDfo|(FUhDzR`s85E z{l^XZkgwpG+wOMGRqi^JRB!K{*Rrf8de6HRPqsN`2+XFYl$3XpVFSQuKpXE}+5$C2 zgNpAaxVNhy$4kqo(3+-Rg3Sf8W_oLZB+`bA4x_!BIbg4r; ze`kZ(ar@(DG)x}s>uG}Xm&u;zZKN~o<&%P>TUdgp6Z#CQ;@WH&l7YKrg334g{4clY z=xD4@PH+Npj1R$_;=rHsWb=Nmq)LM&cMYc(?b|Y!H}9W@7lQU}^SdqZ zB>dZ+5~@PU#NvxFOY5a|RqKzNwLGX)-Y#*?kIvy~f6-_B_sb@ruiU5#nTy9&4Hj2g+;$xI@PJ??rA& zVzl&TFFi%+f05(8VmG3r8s9D9n{C|x#SminX#x@;ND)Se-uBo?ruiY^Ywj!VJ5-@5 ze%46^f6%Rb|2BHL=`ot%xBe9sq4Q@lm)uY)g?J=54ad)Z?4h5OCf4&bwS7%XVC_T5L^ zAW)d}yy(@g6+U)7J>kvG)VY^6f4#=Zup!|MBOwT)gk}W<12m^U`x^zzHOCrJbAz1W znc%0$aI!y^!EJ5+r6U6jTO6BV5H~(MiVJJjGV)l1zRwC5A9ZEi0_Sps-VjgwMibBD z?_L1!ZR_lZG=K8{bQ5tHy%N8liSr}ZoW}XZnbhj*&ygi4YqkKY=ONb+eYY>~GtZU!ig?`Ta_%0dpUDRQ5o2(Q)CJo2+oFfOBt(C!pC^pIW}N$o>k# zCVNgwM$l+g-|n$Abm4p;!WsEiYKBYKpPGF%+VmsLr+j2!gTLTZWn3w|JQDrW;dt1k zWR<4M^f#x*OIXMc!h9V2YmVzz!PL}mcQ^BQQWJO^;3z0-$R*8G%f{BoieDWujvT*_ z&bM$W4B7Vpdy%mN>SA@vxXU?L(c@q5K?UJ-6^V)@uakcHxHbm%0iZ0ZjUJ_Wxxnk> zdlI8P8WLHWHQpJHeFepI6%MAx>#`3gZDlq3PPy=lZC%0pHaTdCiE9s~mYQ@bP^{*h ze7$uw-WvV6m(G}SiMw^wEy)U#M}K*vxFsp5awE_mPAKisIiVxSnY8}aoi%j^94z6xJTJn2kJOeP0aLH6NZ2l) z6l5}#?63Dq0lHJIgWj)|-TW9naf1-KQI_l{G)eh_D(>qUB_%NN8b%YDL}5rsy`Rel zRR498T-fihqp{hJKQg{=K`kFyutKdK@v?}PDYJp!{&vJ}qJBR)4AiZh_tbr}9148Y zAjt@xK{{FC!b1eP@tt2BsF_O5F$hTJ*{J=8*)3CVQ-FaPiiuo!N+j$Dd8yoL6J;d$ z5>ufAP!F&AAh9neeot?vM{ORZM?sN>h(3Ol=BZnKZ^K{ADS=N(25TR zBOG0}EY&j7W+aQiU-Z1W-^H82ma5{dCm<_3SU={zA9om5RcP-%v=`=c!KV7QDT)xg zPzVN9bZjqkE6w=zU?VJlo45cnAs^@`X1Qs@5J){&>9lSA&1_soTo&I)s>OaYDjV+e zC$uTNDmqMlf7rA8ZuZVVp2e}{J+^FG^Q&1w{^_^l^wxPfTTNWJ^x`k>c_)*nI;Hzm zL?3&ENw^A{;J#_dz{W1(5Eb{9MwU=YdASp2WF=4fdXKGP`j}*_PQB&8qq5lMcI(Y% zQs(k#XWm{0Su~@^LC~)3N!m#4p?J$n<}|se3io1Qy+*2zS<^*F zyR5gtp55_<%`+%${J2~4okr}0_w$J8<+HNXB<*pI`LQeg3;_pze&el-yl;wvk~^8O zr6cnPWu@>%1i(tmeT*5IO{KXSmPCn)|Na);SDDjq*6zLTrarLqOD9#n;|IN4`X({* zq}Q3oZ?+fXoq5%ZoSVR${8BMR?c~Qp4<4=1+sW_m1XVm`R6!u&_HtfP{^wo$Zytet z$H@nq=|K#3O++62lQQnyALSMIZY1+^zUlq39tO)VOC4LO8G6uZ_q0b^X51z>)X)?2(KP1 z8Kw}bnz5GzDejf#hwy9-D>ECUDjjbds=F#pEy$4I^4?}xONm!KPW1olZR!k5n3&&8 zjrw`4Pf*}Oh*@wt0)cFNWTaY$h?F{AIN(eFoBK?@tPf0nWFoL{Pv5X_FekEoRrXDD zC`8DkjJj?%yz9ScvB!Ru-JI=wzn;CDE0L{w9FYM;5SCk3eb3P0LG2tRTeTT-B<)UD zE2(9<@WL6Df_dJOd6k`7J&>uW!N#Pu`ol|4lQ+&_36UQ0d4-fPmun$goIu=rSv4DF zgdG)~_(<63*72W0%7P0M)78Gb=Py~=zRt)w5aXao53_!A1J&LaG`qmLESQT$mMwuz zSBah&W}dS?tCPVzAM|vipOIk*3fpHK_;C32A|rhUm&8MRk#nS*_y|X5y{<;-9ChMHLvQ5;KCp^l9F-2U}l-u3eN9RG={d2|GKUQmt9d$te8HLYu#Z0_M zp^>k`y|+vk9)))-@H^WB>u<+Z!jtco9=MkvKJeasM7>jpVz2p+6$t}3gd-~(H`JZG zJ^^~fC8ILimikI}BJC98o72k;QiLfE${JacD~{MF{v`S+TJOJqs$?iDWk<2tPOvXf zxf`5lKGP~Ya6>O1N^2;%OPDTTaO_{ZIjgWdA}yJVCbC!_;>n-d!`~Kk^y#=gd)h;1 zhyRb__TQ~kA(=;UT(;?uc@hJcufi1qLK&9E?LM#}!2eN-b34{Z=|}Km9&3PKKQOkC-B(wX zPyHlsgTN9kc0Wex%$Zf#1ecydTc#>BenAPs#I2}n?03gNWRhUiJe2B4abbqQj9QD1;JB$F7_L2A6fifQmE`(sj(jx9etWip;h7L*YOlK59?%Dw-ZtKkXQ*#Cmh>xw^lJ1`8 ze{v5(e(;wa(LHZ!7(k#(%jems9(c2e*jK1t zH2}eBP27hH_bsCykPY9HM0I_?k>)Si!X!W@TEgny=*cv-|)gvVO)tm0AqGZsIB|!aiSGH;3H@zXp=sF3ObDK2U5;O1hgyf zjm7OP68I?CJGMBr`=;*q;*HG06A*k6jR$3u+-m`I<3?{Kr%5J)_a%|T4j>aZqgJBF zGQKkz$|r0lIk~33-(Q&Hz4j$d=Kl4Kq?5Su96X|HQE0Mx6XTYPJcdU7W#@FV6}!AU z!*GN2dA;*^2;OT#ffNTgjBagjoqGjy@W_ht^RHUAh~eow-0m*UzIqmk_ME$e!%?7f z58ZmacD@Sae^$;m?wtVkOoGP}MTPIASpv^+Aw;3DqGX4U0PxP>%~xsUeUDx_`oO|piUAXkB7@W?$qqm`+9*Wto+|L&5W37nO z2eu^}mTnjjilR2+22Sn46XC-KD3jZ_h1j>eFP!+t?e<~L50Vd3ae9&7Wr15+GxyEh z-&^c^umpIjcH@=|gP}$wM|h*mJ&)JJ!Y(Zei^`Pjji)Q4dkff44c+fkdJa|6Yg>>G z#2eEkJNKgzs2QS4u`Ac-{`^9eV7a_qG@)*!tA4?qX%fyx^A?-F7DiH>Rv{L0eJ00a@t{M zpe91zHB&zwl;R7kynolQ512Aj!1s3(_7)o>*N*N-acSvLKmAcu%5~;!f$8GW@;9fI zxtW<6j(kliDXDsT$BE?cM&elKLGFE2Q|#%tXFSY0M{$)V`IKlwVzbbNFGng>_??kdkl!s38= zHjVSqT@cWu+7A5iw#xk9w4+D)X;zI?Rh2IHG?&BFQJq z2h+bCt1;$^b^ph90SWAiWvjW?89Kb~lP~gm1m9c^`2hT8J0j<5oeKY&)J2Dos4h>d z2REziMkA?+U}MDp)A*p0TJ2HI>6z4ER#R-xrOjj5cx*B+`lv4}AOEo^eyqZNk&-O? zWT~-lX5m-TW2!CV@+|83=KZ%0!!c|Wl6=i`QTlL;5+&u6inWO4Z)~SwA}z@-|74cYdBt zv!0hQ^F46LJ<`6i?D$F!Bf&(AnO^iM#?IQ=kG;$hm$hwdxgIh z_3pOK(0$t2F2riH13-S7&(vl9dFa`VA(sMRLOqG5t(O}Al_lwz0v+&mZQV0TZ#Kku zgW(kfwP^AL$K=%BPtR)(%BYOyXYe4N8K$Q|&WqIq5jaB1a&o#?zsh9xAMM1{E!QZg zsEm)&w<14P2qy<69tQPpXpo)Me<|@cs>Yu=Z7q2YzKW3+2->S1P2#ZI;(j1w9SH9~ zYN=|Dx~;5E@7JfNy=mO9&Y>n}_)!TJ-y~}_OIc09DB8WZpuV76LeKLjU68w*#!H0; zz+*O{SjEZatL!pjGB-7obmm9x0jgH_(r7T5 z*ySrioe|xI@Q*J_42f(QO2FV$1ip)ALz0!jMCjWtKnRH-ro@iV-uvV^MOKqn6tj5z zoN|LN&Yk-ot?zyGwDRqO93jQ|JzMO3dKv5YU)WSwPR=uW-d%?d@R53uRd10-UwiBX z@pRS=#IsV_b+X?KY|l|&=+8>PTrXOtYapk(D#8H9k8E?3*eLoZVj9soF*!QclS9`eifpP&U>Ud__E17 z?%sb48^8I{AfNJNI5&SQ+JgJ$gm-#ylr`-hP@hg)`%fO!F4ag^dfajeqQrx%+WIWz zwr0dNuW4HVT>$g-Gf%)-)rz#6#OAA9nQt-vPN!>T zRk}9enWyxS#ORwy$C&EawBCVE$(;+cInDE`?6If$(_QU@C9kAWBwBOiI zLmZ`^i;T(38;KaMDsvlDU;Qr@SOhGD@WSweLG_n>PsQdC$Mcs;63g~UEJTHe+3c!D}jbCx#OJ^a*48#Hfc|f_2{w6jjfVi+#Y3le% zG83S%Q-=1#Qk-heHitkjyZ1dc9v%(op&et7?$-bzJ~yX*+-a(UFm;~N|>Q^U4o;yZlrd6zZB7-qTfeMGL5f^Rm zv>{i=rY~bT*KNXnUjkRa5$s=QUF+F062G3I{p-!EXfPl1vKczsF!l~YCiy{+{{>U( zOlTEtEsaci_T}sw_|r`f9C-L|-heg);;0|BufWyqT%zyLjwv))(f|E7Z=qzoc!G+G$NRiYcs;>sL z&d9Y2f(KNB7d>b&%Tw#VV+xyR4kGHQjFPg=A?O9ju3uBGfd@W3XNCId>gGl-?o`tL z9?m?e8<2s|N`7t8hg5Awm}pjS3@_sJLv8)F0UFK=7f7>lYb;wz%t@Zy$+FJ)iwXW^MG7>t7AgLl@proiEC^^^?k^|BxB`pX@!+>2NDIy`= zNOu{82%>Ze3W#*)5Z}FI2KRZ7dvDM0`)kj3n6;kuth=5&uB#j1LC0(;0A*l%(CC8! zr@Idiv>pM_=$p5ejwo^|x+@L*Xlod``Ss>~Bhtq4X)cV)M?0V)GRWo|Lb*2b&c-^!SRU&7Ccx0=DnD>L+nC5i4k!DK}nZvRS|Kc&hpp zW~O3`H`_(T63lF9{vp6*_rQFltM`zi3TuqeqPp`~m{U!F_u9lu&jYq~FvFd*Ik2v@ z$CFZv<~GV4K^G6oMJWsFDQ>oqk&zjNeqK3l57|ltfDr+kEi7+Df7>l;pKOB3no>Jb z50k0d6E)j!U)1+X&30RHYA`oPqAEb3xDqS%<++q>cWc@%wvxH*w9zAG_l)@JWtn%+ ztUwo9E4}}r{Zv`1Zb-4PMxbrqAnOaLfycIefjVpE=^v~JC{?XxgjCyZf3Aj}MRMMD4{1I+ls^})S+Puh3Zxqv|S`;q|JcOFv z$-|uI%deKy?G{Wk7d`=?w@o|`B*Z$h=ka)$JB*gC6 ze=bi1VJn6ffA-vD=a=|o+o6QGf*zb+NvNZQiZR(8t|L8#-7Bfi2TNCH({jlk4~n2q z`HVx4LvNUXxI0vza(F!5<`09nz`x^n`|7#Njvugtdr-lBi5|yT(z>fp$yB$-C>v89 zYZ;Gpn|ZN#^W_(Lw;ZWj(x@JB4smxkqn&)i^Fh#bbDOINFQuk!7r>{HRRuvk?fesk za16<5bZbgNg7tWRVq)TjTS!*+@H36_-KNaB0F00R_6e^+Qf~ z=M;=7*^yBI|4-$U%|U5@V&wFYcimdc7}wK-0NP7DS=tGl1ux-zYCQ+TROcBLEnY48 zB{tkFnPyR|gtN$}uFNXB)ndf~lL~=Z*V6go@%$Vul0MU#{>ar&NSC=HqxHNibYR-8 zIJ@q6P3<p?I%^vJ5eLis&I#qS{AE;XT_i95vWTS1#COk(+H*mpk+| z%Ay4tQv=+Kn$LyKaWGHacQrR0;SV#@eQwgMV$4Uy*L=CR-->_0yz+dJ6Djo(x`N+*f-lwmf0? zo`kl@NMG_yw_(k0o6MtJRWe=-$0t<05@-2V4u!j9FuUxrvuqTqMaP!c0I$SN66M{u z;-h;wsB|QNNWu?&?%{h;(+;598YK59frd#-g;er0s%mN>Mho>L>WU=xyLYCFn4Q~4 zwR2t|$|Rx>48ELjyi$uaN2`pN_i@epCH=Yr1%u~Xo`%CI^PVX4MX%coC+wl$s=(<3 zFnegLvI2XiMTiBvP8TwHwEI9>L}tADE>F99H*qykz5&H>X{Uq8WJ5!y&xa3oBIh$b zs%5;i8BWBqg(i_CA6p(@TeV^dRQ=5ELe=UHY%v}0<3&vCM~o$=gIT6VK1{!Ky5^H_ zG_HIk)F^_oZeQ%f!Qdu6Te6`=CvwV{0~0?p^Mz zCaw;>O}XB~bC2NPb}9Og|~Qy*c^Hk`j3nf3Qe`MLy(5N1=<_+Lc67GpYS0 zg5Z(8W^=!VO~xR$?1p&M(Ap3yJ~(m4d~i{*M@KC>HB~M0m~lpUl3td>Dx`_&ns|zI zSFBx+-VSSUK)jhdwG*^1%gw5kHXI_09t{4}J?%2_Yz{t*7(8dVtb69vsR+*IojI?6 z$*7MyPLD~ZraT;)?+PE5r1SoQd>QqtddY<$wxeE>5|s{X zd4u!Q_kX8U7$MSywKQ|io1@3+XCi}l2y$j;N^wKhVJu{vK_NOKHTBZ-7-<0+lX{zs zHKW8HRl3~1zXiOcOUP`*q%ozRoLVIG$mN8&Dd3)b6b^ zEf=SqmXvhEm3?-vs3|`3{qAhO1`Ay29V4=aLP@Mu_AVzOB@6E+;l@ng`x3rsrzeyR zmDUb2uN3##6&C1}o1Nv0Yxvl7BZXh1UKaQK_K9Fjf~;hVqTT&=d!T^G>yG0|D?0WS z*FB>Z6M*j*Lq?De)7r0kPfi<>A(-M8Xg5&SC@a^&>6b}*xk)cbx^Ue;XDlMF%rh6?8UFT)c zesVVA6)C*}>x+Ox0qrpzcZU+^iz?V-G=ps0?Z}dhGrFG+=9G2U*y2r01-@l7ON__M z&r%6AoqzCN7xyFB*1OZzH^yaoz(dJgwYHM~Oab6Ydm~0!++;<9&+H_RxR?6@#KFgn#q=HAyg5YMs|XHI!!vwF_E{J(TO1#KZU-sim37}cSz|Jge&!_8UFGM6tj;7+Sx3rD(@ zaB}jXl^oUM9P?)VoS~JQ$yOF#vx)pUvzj5bI!<+W(cHhTW`y21jWYXy~_nnmOrT?of?c zh-yBxP|tszW8P)zdeyx;iSdH(Q3u)EY_k5A`90#3`b6=RYtaEH5}N`kAJolfBm*V1_rand~~2YJa}LeFGx>DSh&qu4~bK$ zom=1I{#Yx%f_kbt%=_;qXcFcL`WD5V+?<^6*Di7~5~RxDbOa1nbs4^Py=^b5{=ZE1 zeMZvwawjfrj5K{_nDBZN5)#r->p4x>g@{e0F1ls&ROkq4Bn9}Vdt;*jGPtLRi=J4a zga-R4To34Ns;67M!)i<5Zo+8+BLb=F9z40Cqiti{J&`brUsC(8pD>r`t4h3o`~);rH$cRumdTZftuR&8xSo-{ zFi4kLKRY|SsOTU~4A->x_25w@RuKY* zWaMjxD+u7DHhn7bnAOGk^A`1w&wl;XNT zU+)ugJ6eVCU40DdxodKMe%tKUM&X}jt3SPwHd6XltM=t58oGKM#?UaPLsL_;qg-+1 zXS@qViBk-K@t>LWe4LKnR6K!+_{ab5C2UK9*(n0GgQ z{P?lxi1B9Pm#H4@ZnGr*F5&E#JK{@DUze=;(+7dS!*Iiv#YDbKC;kR=h)j@OOA_9@ zDi+&s(*aZNhi>%S5(KI05J~r35`TmQZk(-8nT3<*&!4K#8=mT~(_nqU7>7BZ2`6Ow z%42f0BR9A9l&>*1I*+gvpU5&8$&|GyT_PKzBvsB!qtT&et%07_zZ|^(c{6>G?yhQS z>pjHZ_*}t#`*sy3Y0_%!0Qz24S2z4Cj}Hss>powPcBkw`>7mW>{20Pp{39DspyBaU zTANRHmAEvFEc*$sdx0zRSZu&xTy}O70h=B)>6+g-9(zS58Fzt!@l@?S;}|8s*6@POoJDDBy3V6#zs!RY;eUily2>1{;eu5`(pdJ$CJ zk)4K>bBw~r4C4qpoKy~xlN`=lyiuckFku{;T|)#Dv2*WKA&BsPra zhSB)@bzovir3C_ZEdE;C8Om!O4rXRa9fLtD5tBXkEcH+i;NjuPY;V^{N=nLvL$)R& z&U2rY3M@apHea`l>^DiDKYwlx9HIzOv>IpjqG>n$sKc|;#U%UV{MO~TIkKRYbeDa9 zzm)%4?I8LH`lR;Bx(#P`jJ=2A9*@rlelripvuAH35H2}Z-D48j$z{hz8{}bFI>6sQ zPu^XJ{K08PqJ~9#w2uV_GMZUh+DoFBRSQ{Oh^tuSpvs#plZxjo?604!uCe~-UaD-IDa_6OTjzYDyWNK|G1h9;s>yJ^CtX@WDF%Wl+a zDZvy36&01GDjnI=#kNZ>Zd~+Ur-_1k8fDsXe1E)~pmMz1`%DJ2d3im#y19v7_Yak^+CGZ-N+x(zIZCz!Nbkn=`AVgz)Q5& z^~I=3RC!j{_`~@GU%YFVCS~g1Ob2&yAhXWSkO~sDTSOAJmqZ4mFZGvK6PJg{A^ovt zAoF~9U2-R$!dnsBy78?r`r4~JYI^8bzq&Z8L46nxV=e0|#aM13^(tGoiTv2fc{1kr z2Ljv}ebw6@lYnlDh#hB|LvQ+-?I-;B7^!2112w57T=cz_U`&bnD^z^VBziXSB;cvPgKmO{g8H-JGdyZ(Y!-ctdhOXBLTd z!GSRKTWF$x4`uK;em1L%{J3kup{ZqxvoTSaiX5n9`Je=g+= zb=TDO<`j%71m-o|!b}@>L4t8&bA>Cr`gL*B#a;nF&8fwMHwDiV{gA(hm0#4{?cCem zRH+m}b~+B?FPQ$$L}Jvo79mhbxuq+$LqkL6Q+?G?XiVExuCE;jl zAymv$l9NBw0oE4MjxxgBy+96q-}?RL#JI*92a~0Rv|*6O8TG8pnuI2 zqVGjP{UjOWU4I0|^@5=G_H0weg}p*QHJRQMH2(H=ri6_k@sEl~?Hu%aR zJ3HHQ4Ins0#GZr_E}jWXSag}^6eXB%`e@8`562UiWf``Q@n6`)O%PbzmU<(ms>jj0 z3ET9a8$<6?22+h1nCzDuISitM==_4GKYGt^AMQV2JqsnLgKVZZ zLdOI3>AWY@MuhW)<6%&cux`u);^AnE0||MS^HzfS`OU)r``K^{Kh+XpbSJ0UZGen` zfI{%DmXEBTpyAy6fHGqH|8nO2kDK6bp^&BuabVSMj+1A@gOM1OpbL9TLJ)?05C%uL z&0G?H?#ug1%RU4PG^Cy}u9L$@{u*tvRf-UBeP;X76@egFni)inDbP!~dDnUXjSFK} zXs6@8$ntwL{C})6!82&lp8%Ba(Q*nlbNtpID7IOdci1*z)!G2Xq@(!_<@;Y~3Vj8b zo3rlUYeS5YseS;2$?Hjn=A{7S%%dU_5fC)S*eeCaS(tm6mLHv~HP7Fr-@dlTr z8F*IuGi{s&s_bxMKh`+6tWmo!cm)ImwB2UXLC_T5+Z}wr9)x4gkv+rlM!hh&^9Ml* z@lT=;Mo2Y&?MVZCun0anHZdW~&J%^eGTo7rxuJi3Nf;r#Bm#1aOlLy?+xbBsdJi;9 zG88S>CH^xbBvdR!E)o3eKWNggM=ntH=t)nV<+w>Syy7_7Id^a;BjAJuT)De!8|18c z#2hB{JZF1{Uj3{Xuy-R)ZC>=k;-A0M2t6{!!&=uqh^fBH4SGOycegMH@sfa}fFRc7 zY8ygCZc+2~Hh9;&!s+Y57N&d)B%zMv`abwi?ffSN#=P9Zd5zc4E3P+R%Y9{b(*Bn* z1(YPU8F#?Pwi5p0pszYy{%(CMs?LJ(u$fF%I7rxsKhWYIpHMLNZK4SYlsgeqgay^> zL#Q|NOjGXc&%G&-ipXP5t>*aijRFmz-Exg_JD?b?KXJVua>eLEIqjbp$>0L(Bb1#_ z%)kBlwh)DF{TDvS6KCA3jrk=D|4*MFI)X4#&Vmr|{O3(Jg!d0tX@DG}d9U8!`tvvN z+n2;10&$|Da)=p0$o`*Kq>kh#AGT_t|45Nw^KhqVIk~yHqlXljh}z_X**m`joo~6T zV8wtCc6-xT%}Ssk4Ly|}O-va4`##xTVi!A-2yXqxE*l|&X!K=cpuwnc>MkBVYX5!k zL7LxM^qOCsu*lrKmm>ntsQ~4y|A4?B@2*pz2iu+|=rPaazGOj= z--u9;ams}fslrgQf^WlG5lvAV1S$2wu!k?f#&hHakDU9hQUA>@M#NFt3epq-4Af*_ zLqtNDn`DCI`m<^8{h4p1v3vYviC(et=0MJq_d~-!hC4(1``U?$;Yvu|aty}H@33=G zv)J#EoMceV^qV{Vc11W=b_ETMA=5!9;d^i^pCxR~J({2S+IuIW^@J8hmPD9j-^Fhs zY7ZT&*qv@g1+%jgx=8p;OxI3!`mF0#^h{;Og+bCk7Cq>vvR8EtfcbD5LJa zvX|YY-Hct`eU#D`q9hgk+<6?DW<hzl1!hjdlVv;Zff*t#5<7!Tk7Mk7WEf3CC~s?RQ(tZbb$M_7r%r z;HQ#bzT9gyELBdBA$C`i+LBM5og+)6L(KF}k!#97Za!ODS5}|P?A=R}AVno{d;Yji zu?fYpMMYJ$pcu4+WzV~x5RM=MoGLi*Dus!Q5>hXl1umx{U`f~|Nht%OsX6&}tY+ zmu`|Sk*7(vQ0d;AC&?BVHB=8ELu$55l8e_Vxc0B_b}+-1Id{kyJKRPx#_l(H=`hVK zLt4KDocx`5<4`p99-J%w0Rier0`3#g@t`A&Ho`|=h6z{)YKU%ORVrg(pu@Vv4T?73 zDIPg{xg=5c6NO=h)TJY>#AAuH#N9{7vhC!zM-oltrcwskiYi!jjSQdH{YHo1?penkDn(>Qvj3M&VuC)PFtr%`gns%(&akepe*C zzk&IGyy(WyB4^Jj6vtfF3Thm zi`qIEB=5>GOVY^n!{q*|ynJDA<4?;0Myc<{THL^FqtjA@^vWN5?jO;Z3FfTq5qD@P zl$A_LNy%}VH8nFe9qJ1>K|IXaC}J#%+MPJMSMjTuyl|g~{qk|LU!4}0mX;dUE}jn{ zKoeB4;atYoz^zJt+|BXF)tm@TGSAI%Sf7c4oTkRc%aC+L&=(&t@W6n;rI3pRtEs?_ zdhU1{Sp}p$@o%^~&u>Y)>;18R_Ilf!VQ$ftaIF$A1n>{>XLXeHr`F;)8ArdgJECp= zSo>j6o}FfoWwc@GSkTG@6d`HlR-#xc-A5 zT&Ua4u(sqlvHZpj?Y*Gb6TdcpPqa5&jWy_7@SeZPBNE@x4-^YkkR=3iduHALNU0rJYly)PL_WMoxwP!wlC^!2ZR4?XgcI)ZD zAPqtUk2Te3CC>Hrp;a&zHz5HCFl&WuwSuwioV7(? z{o2jRJd?V%Q#_pQo9k#1Ph5*C6RoX~UaOQmOUO6+h@z@z+y#eC?dR)mNouG4!cKO8n;+5^7QV7hc;VHg-1V~c#ynR9c zAheJ;t;d*9WhqV7l*?OCZ;x!oOh13Vd$_AGm-*2cMYNfMlZ8df_Cv(O%64=-)jUbJ z+nhr7;*uhoA8%nfP&$wAcUhZpWodfDPa&Bt-nsV4++w#wDtpG#k`t59`L**(gmRCK z8bA9E*Cp{%N$IyBukb{Dm9_IYgZ9*(qumrx;tMT->C7xQpsNF}b*f-Dd|53RL+$M-AtoRo;--gLnV!VS|I2 zMzuEG(#HW!5TTJibfcG8^8D=^jktl@y))n%O?K%iha=e~wVINvF7A6aQhh6^^74;g z4NFJ;0qjel>9c5fKZCm#*|-0zxwR|nvah!RSeC^;}4}tir7uRMD4#nVJ?(WKc5R( zDPYs<&)w((UF4uKuUWBKP(D7@;WGMq*v)ybYa+CO%vYz)-zvb15dILe7fmP-6t4(b z(df)~+!*u&XyyWDe`4V+`Kg<(#J1S>bR%;@o@@YaK4uWe!624e->;&!BzfB{D1i;xD~vqdmN`RT z^+5TFJgvEX9=t*0+YL9;@H7`LMnJCt*~7tTz=7(3DK=xIGeJ$w7}zs%aUS&X~~BSa*pd< zTje zRZbFK_Cz`q79_vWx^uahUl-3y-t&5R@&;eBc*&QNa9S;IjZ4{c65T2vdx^bS3zy4s ztJ$pXm(oiJ<*{n1ZvQ&FkpI1c73@~8gaUdaBE)Um!g)cq{3(lR5(l zvaEm~2l}}a^q`Ldx`MfyFEF{3%|z)XuPu15UCZS+<)CxCHEnV2+N=3)7-xm_op6Yo zKYbsgEV#3D1Z4UP0A%(UX{KMjjR!11wGp4w+tY!xJ+{j&h4b3j%e$<{SmG3S<^Vw4o4ikq&ae!4l?2rstqfdZQLD)}o{7bO~uFw}^w65wMJWCX{217%C)m9$LbfNJ}MF*Re^MH)M`^l<(I+7Ju-UI#fc#TTYy72*Gyd=W! z6JPu|SMtkTT~NH)4d`MtbFC(Z&@@%MaGGqo2DuXHoc&XKX4hCRF1;{0@11Q@`ABYQ zL6$YX=Lp$-E`;&YLVX-)m=9l*#WS3+1HAE^(P>HqHWw%o>QlCZ{*^5E^J|(6p4aY& z+2VI(eq4Ie0yo~t1Xu0X`GTflmT<}I7_Gr-Yj@@FIeY;V5$aWU5-<*tc~^@<3J7Qs z3^ZsOML=^$fJ-#{`ldEuXZrd?vd3fd2n_RBiK>;`B0S?#4oKn_{KLU*>1p#TlCqV?lwScS(VV2l&n!CE z%Pv$KecbxnnGm3j4w2%4ku{tO)LSeMrX?uH<&b%kQAT5u-#ugsp?-xPYp^*uwPhf< z&Z*RGWdx|x$0t+(s%%pR!t!8MGUc9N0;&xpn1weO%o#6h7QjhL!NXt`oHDCju?HEjfev zsyQk(r#Go5Ufr`1{r4q!7?H~u+8>deZk0?EJIrq?26bk&OJonB`yz`c)98TmrZzYt znZrmN!bf9|hna-I=HsHO@aToEvjd@{1-2n>u10K8-R_L?8>KPa0^Z@%A zuz!rXF7v*iCyl|xLIaF5&}5Fb>U&$oX7Sw6BS(0FR(^}eQ3kpQQ)&?h- zL#v-a%J4v~aQCB-S(v*uL8hNn5%32Kz@4@cD0sZ*RPzy%r@5>@G}V zv9rpTPQKg1>PPxdhT%2pKDoisG7;ViLPvZsSOHe!)d%9Dm1n-pxI4{FOO38)w)gwQ zi`QM^%5Z0Z%(PV^YhzmX9NS_aUYkBqR;*J%~SHg{N zQ!np7^=h*a@0s+y(m`K>wo@vtxp<%S6TLY;Qg=z;c>ab?+7%;9@p;$r58_E51-z}0 z$N(Tc990z*dJatz1I_;q#vlScz(KRTcJg9M8R6AKFcU_3WVL#l?!x@~rf^oG4)_H0 z`kihe$`T2wG*dl4KNr`BT!acN=;=ow>dOGa@@o5blektF>>=cBo9J9jiCzqDJ$Dg* z$zJEmm6zf$+m-`But8fOMbAQJvBRotw_l5 zJv}m=AQvvth2>`k$Pc;ag4LHK7W+=T>8Vgj_(`sSAaWKh)`VFz4y@-W>uEL((5@GDo;TodDT=pI@b5W)`=FBJ*KR&R5VGQG?yf z4A3Gnd78ye*}y`=Z#fAZgav&^}| z<;r!{k!<-%lJkKQYdaS8_Og4}{wFCX$x5Q!~TdhOj z*40*0vSy!cxV&E;{$D=%?7|HNw{6q>OV2+0JW66~GOR20J@%NmLS$QK{tazk|3qt` z%&SVVZ@qH24VdQ4!5JJrDpReVn2`-sk;1xZA5ZjdV-~!o@Vd+3D)Uz1)$Uyg3Bd{= z+l+}qpH)*djtjRP^0pi6Y(v-~ z0d#j+$dA>z(CNpG98Oq7Qk;=DuQe8{1yPigVF82c^*2qe3URZ*P)HWkIF zPskAbvY3DQq_U5M>_X5?{2BT^-0N!FAsZ3xe6(6NSd!1d_=`W^ddH!HD(=0LWNOB2 z*KFsxy@trYOKF3@|V1-SdyFy z;GSO``0>--O=+?Z-L;&?-?M3Ou8_>PHsW9Z70jOOd+ZL1Tfy*Jh!`#4(CiZ*suIRH z>qc7AQG2NF{nh7R=ADO^b?>H0Zws@ z!hCjfHo_k%c}){CR2PCC(95zodYD|2HCoQR@`hY^?o-D7K>1AOWMYn&W6L$MsJj)I zCEUsbiPgQhVI9pKQGVcIYxzj1_9ZDPHt5d6$9y=QN)DgA|t|?*_5DMIn6~A zkvmw|s%|V!^*?g=WTH$X#4qPj)lb|JzVbwWvcfQLWRaf6J}rN|Ms}Y-%n1jLi~8s= zRhsPQ+|L97Y9iyoMGa9SLxM-E%JWFPn+mkISemAafRPk-Qw~2eO$l;E3VisOS%u^v zI)l*u)PFuA@(IWhk7UbE@xPeEe|GOsroy6n*lnf@I zD)6xO5Vv2#fHZr9tN4o(jBeq&=hf%F99!io+-0^d?>_t}28-p>DD@I8#~I=g_*Yc- zH=l4e+%ybg+Lte1gA=WtxFxuWbZL(M8HFFj#t?t@S3o%ybRqVv|DG?vu_+yLreY!P z7UgY%^r^7p9vnji5~c0G2mKdc{?G3qpOKTxp#XFt2hv>XaBRBK#WzPR%Bj-=;d&^7 zJ0fKDMa#smYUi54;J2%p>zDLb#yvQ)nxJvXVvxAVUn>8%pP(z!Ga-mi^Ea^hAYSp&*U2t ztlvLBBjM8fXtpu73?ptEg3d0DL@`yU5Gm!9Z8WK#C+X^iTF6*Is&i?@rmxmg60B;+ zT(`3w>J2w&ybQc9@bYlWOjYxf)LRV}-KlIy|Kz?uccM>=eUDhNNy9;eF>UxfbVenJ z1x^dR-oCCsRVg0a)`BLV-;S#2Z+cAjy4S07juY=p$<_^KYuB1Vc&PaLhALQ+zV2oF z`4=_~Z3^cvuv6kD82>cXgF^-5J@gZee47}q>xsaI4RbTazQSc%1Qm;?LBSzkm`urR zTSU5tM&pT>`}UYOTBlr2_k~!hAX|HrBIT&mk+#H0X;7Sa zY-jRP^spKmW&q zMqJ%;YxB#QFBJD%AgOe9&w=yAE)TA)3+Wyej#77f*H?uergyPwjZ*{(ibG z%4&V@40OwYGpV)An_)TZ&G^cU#iT5%El0taSU>xB5mwnmLUwAA-I`4hOS1jpX~Lp$ z^rSAw0xHP+xh{*`KFwtv(35_2mFww);Pu<8IFJBq501QYOaElqMRp!<|Dm5seJLWD`TT4d;sOf z+fzwiQuuY=Z7Ij)duhA5jO*Ovf4|>9?g8{Jl4kIJ%P{$KUHt8P)zd`#U~>3o+l2qv zAOBwZp}Uh7x;txPiBa*tTKxEXC`b?`+`IekC^5dgL&p92*~@(_GI!(!LWt(p1LMdd z;Dcd2ak1#vS^2jQ^M7>zzyFup7m_>-gXT88zki6|Y`K9{MA52~J>&KOIpT;EBiWRR z>{EHy+HYL?4TKB%#9|zGDT96de%}C~m;c|ENBCJp5n6>mjU`I=j~B_V;0En){MUjG zW*L3A)tswk%CY%O%JW>HrkS5B>#^CxPSYl{mh|0nA?l$*7AaB#sm%`aVXC>>cRveN z6UV(ToWkhe=Ef!-NH`#$yO5ECFNKTO61B{#>%Ny=H zhjzZ05?NIoKLq6VbcZfwkx?=p5PJqmpthOI1-1!r+N$Mi$uN`|{v7krZm5y#tJ4R< z;&8rX@9_(FNi%#uvfcP&S;nw?lQMd*mKl{yy^ul6#B@lXXwV;HKAqfkF-~(@f+99! zSMx@gZ*%a7>yj-V*n72+oP6KA?Cwo--9@N@JZr_#cK+*T)mpwQ_rR^%5KPD&TSZ}e~MHZu+$B!&a*>? z2)ui6VdNPB4&T9-XamTgS#LE#xRc?Pr~^Xr`yx42qLfS>QZO`YUI?6O;d3H3`2EfD z|7z*`&$92l8r@P}S>!maCESs1mMd3~)R#UftZSUOlhKlIyI7;foakrMTvL`XhDEp0 zWyc)7KFyp7ulWbHX_==*huz*-9C*s$cZD!Iw?_BuyzwH2YO@k`okrnod2uO!mu}>{3yCCcn-o9K!D^96wmcBA8YX2leCs0^Jt)o82Qx5-J>_=EnbaGJ`kQP%ajMTsM;`*8>mc94% zoz|XmFN@`cNyD*b$d8Y}m{AsxR(~c_NYyPZ`Ou+9w(dH(3(FwGCRe>TQ4C3eB8Ogq zOOY0)9qo7LVq8Dd#D72m!$A_H=8WeM{%1%7W5>7j2|9_gRKN0KXbIu-y$B zLgoP5{dpKvgX;VXMC^uC=7k$6`HOr$Fa7`620zrp^X__-=Zl$hFLJnyx_s(4!Y00z zlOL>Ywz#JG^+3k$s4quHMMFjrHd&Gf?Ug{>6ZMNTE{-~cLWGcD+50S&mX``_1W>(-q;v`|nq13X^oy-!3nvQ3+`f}(i+ z^4&g*>y&o8Vr!(S9@2mHHJoHgg)^1!%__=DO(S)$buz<}e-WEmzaRgv~kFPsJwD ziM48l4xp*oBQ{^gp|a4{>n%Ap=L}Hl!L*ate%h1(VU9aU!u#pnI0H9qKVo=~TeJ(>1WyT0=Jh@iSkXHzC55wt?h7$H zzVW5cv2x6KXcv&vpOSE0q91lY)*_!C@czW!?$pv_tgH_Q6xc=A$oAi*C`5B=3B z|Bc|BK^0AIfm_!q3=P_*bvyJ@ zK`z%-B*c(N+*5S}cc1Q1!Twgpt$W?VOQ;<$T_hA!>ePsEa>YE;PycNu_LH8o#>_Nb0~ zJNA#n1nFdODaYpZi`tL;;C?Zh{^_@`0>^m4uw?af{6v*da!7FG*xJkvG=d!xj zR_C9V*1N;lY#R{S%i;52uCOZ>_$IZHl6WqobJA6BiKX}iY4ymTEUH+{AQTBh-B%Z_ zA0nkf0QTm>|A_K7uX}M)6>@E6-6h4y@U8vpt%oi{BWiD;{P)K$2)qCkq;i1LwE=1I zOWZOazP4P6Q1n`KG0CuCq=K|77>9QcsufwQB?uw@g3xy8jJ88t7m!{Y{!dLjT-BOu8_poK^w*8*_Z zo6~e9MSC9!n8RQsDb`1Ioo_;Qg$z0nji+T?ljfDVALYmcjAvw)}V? z3F#l}FW?_4=Dv`S2<7=uBk1P3*=ZWQ+b{Ztg}Ju_Cc(oJ1FsOe)`$o-NfiZ|2$D zd%kD;V@gE@EBF$sry#|2Gd4r{_7&{V=e)USze_eP1`aC|`JcL}R;?HxJ7aIRd3(cv za_htpM+qCkE(~Va+TEB`?J~4UYFoc!uvBV1p&@|8OUz;p*VCtyt+Ohoq4zQsu*Ib; znGN&ZI?*`y?{%TWtJ@p873dDiUhf`Wx-{Hf>fU$L;Syv+lBja5t$d(XKPgyy%leRvLrkqlXqc zuGI#pVBfd?ys>BEPE(5u&WYLnPzcIWQ9=dNR=~f;Zc-r==2mFWMb12>wjTlLvA7sy z!n%R}RpMQg6vK>T4PR~^W;X9O$_ls$FBU>K!e-?Ukjx$M%wkw@!jI-w);5H&xi5d3 z6?kSI!;U4J;U=*Fct!h8>q-Vqc{-KZw})D9`&Igr#vMq9l+(LrtU|IUz-up=F>Omc zaGWeAFsAm!$%a`qToAf$wQJmMz;|?6h<+lW5-GNNy3vuf0~EKrom8cpxHwPMWoohy zJi+5&(XU^$b=$>}w0L7E?lFsKbEz$EJY85*_lHBkql3MA4fZn*&}byrq6GaWo|#={ zWGmb+H5A z!2>>A_q)2gFP-eCZ+Ld*{>hR>d?0OzZMTxAKW%(~!?%zMDyJW;F@44yskcIW!;zMg ztMg|$q6S|cSU_+&5WtX1)!Mhu4us;ZllSl7_td9-oa=ur4gzE~^xi;k}WpC5fM_?+8r|Z_ZccuYyiXC>V zko3J73+VJtH&br#*BTE=b=J-WIPnR;Z($9)9-6wuSwEwF;VCyT?L{qdy(N*Gj^`zB zTkO&FwHJeVujO)jOiFy?7v3X(0Qk3sCiSb_jJ?%L;=YPZG0bUU_H|90@8c)Uj+XdPTmQuq1l9 zUG_JyB|!KYeL|exCz;);n|>sjdmqx?i9IH`g3$Mj?Dk2sLRVlJm_q5uK610Gos&MN zvMIGL*YiVvblIot*^E$FFzZJS8es8SI5;_v=vKx>G}Q2yc7iizGi%RE=;m9m)SjfB zxPMCVV%faSE^sU|bYNN!QD14-EjbKiz``SvE!-f0CyDP7Ct>H`8ZZw^w z79BZ~>sFxeYdcLF|#r7Dvd z^v*B%?CXvbV8lj-`DWQl*s%(RH99s>pMvnS0)TT^)sA1P)^Ow9({}%uY~#`4>6d*+ zv0)7Zr+Xc-DNT0K(k{>AO0KEv9<3ig6M)6&v%g3a?M>chj%n5GXZ7lngkkLGZb51$uoWD5PLr(EjVV14d5 z$L$0Y&6sSJR5tAvX^kdtjcXrL(B{XQyLqK)8@uTXSQ{nXLj#+sC3P7(XS{YuyEWX@ z0ID>(fVxI`EQenT_et`#FB8L4T8_{}lq5FreE%QM?6HrNJ^23Nf#@A4(Xl=A5+PQv z@#uMuP*)y3jf+=JD_NbBotq`m_LktB@i9(hWZ@7RraRu(;p|b_dRkHHjdcA~XUiKY=A@8AH|vGq6Fkn6xh7scb!@9a zyGP=+_^Tc$(UxR&W#00OHSy!7Xqy!1C~!{EZBYYw_G*R$iF!ZuUd7Y)71#|MNmnR+ z^GC%5%&0cUN|T^ZsM44pd3FQgIG5@`+algp8;kh#{W*?U;YnN-x&+HX(XFD6skVd= z@Hod8u6sI7G`2d8eF?Gp(-uI1azEMSD6oSt?c`=6lj6bE3C~VK2zwK+CD2W?n@z9gz(f-Q<@i>5#&pYrBavVerX-I z*71gqeqjJWfv;awE=T7|GdA7yV3m$lvdb`_tD0$Rp7&36=eS6|7OV6v5H#{hz|Q#I zXFv?v>23aFoGB$KwzOQ@EI~_h=&sw$srx!`g3vZ+YFC8>b0@V>JoQrHzJ*r>s|8mcxT{P(Yi{DNPvTn8 zD34Nct>BS~x_17_9(D78i+%^& zps%4aVcr1zc>c<19@Yu|P5UgvK2dB5G?{p1H@ z%v0u^WBl6?|Hsy*VQ#jDEwaN zTCNzXEf%sUIB;Vw`P-$xR%j{brqTJ9GV86?>JY^HlcA1bJm+Hx_{Y)wuII3o^IPf@ zR=h%vadLJaNj4{a7Iup-|cbIQqx8p8&tUp|nJyx}`RZx>z)ku!do@!ka6fazD zkdx3(S4Tvwr!wZ=)wmfEVlud%y8izc{~ z?V!B8hSFT}B8}&Xcx`PGZbfM+K)dN#zL-zH{pKW`-fL~3&+2>(wlY~=-uN?izTzWJ z!F)jSx{}Oy(AL?DkJ!d?pJ9BK`A$Q5aJS>4URRk+?4)&ZV zc1KfCz`LFA6x1++DxAH*Eyn`xvb?juqDALnB2;#jV>a+-IR4B65V>e{O74hefeiXS z0`qDfQ)L>3(nuh$a<#KgXMC0_0M?J1qi>3QU$kphOZPmtBS1J zUE|1o&45}_ME)HSqf?l*4d=nwit z7n~?3mh)NypB1S+8{6}3wN7EkEZhTsHjxmKZR8T0zAO?N5l~Y-<`{e^UM zKhuk!)HHTki&X-A`*A7%L@$9Qo47VPw{!b?GpfQk7s*~^8NTi>zHGv3N%h%}*?M8Q z)tUS=of;Ff6)`X6FvuIW7)0Xy8CtdZLsD0%&c=<9zG(k`!*TPf@6x3WvE~6aYV2Kq zE~kg3sGoKf5961MP)UsiYi(k$Rz5unpTaF0rGz(lC;#^83RYQRv^N7I&bT$F_N0C$ zH&Hot2b!)|=6j7)I!iWgVB{lExke%@UQP_= zLL@7I(%*fn9tCbn-c1 z3QY^^wH^?j5cw+2+X~}10pQnq-YDNSvVlKAS7BI&373d$;`ZuHEUYqAs2q8}1)S@n6jw z)-EaHNX1P&{P1GK=<8h}*J88C3NIES;`lA=vt7Ij*aS{yv` zWs~{F*}Tf!^T~5rcQ0wX;I^GLANHO!Fn&z~yWpaoNh1oW z&T-W`3Jav-0*K{v`i18T%K`XyaaAmw9sc#JgGN$_N|=Vo9wS#YlM{F602!8qU6t3{<8^`umI83yJT-CQWY`P1q=+!^(po3-Jr!RH_ zt+*Z3Z$JTqWU`=p>i zqMQD*V3~^7HpW-pqE2>e3$!tMt)H}KQO-&slk{sI=hWuHcNlgT%MFVog8k;!)Oz-* zfCoEppNRYRxwB^NR8M171^&{}c1J1%eL-VnYc>|SLH?sVVUFvDQ$A!TMbKz+X%4T` z&y9(eaU&iH0qhHXe#R~U*q38#f)^F86bj9V9h{SjUW0gLfHRg(Z9~u^n4Mcs|MCfd zbLNwep^)(V;7X;yKD5>wr5(QpY1e@V18W@3Ld|UtK|fVA+wPiIO6AVfsDJ?mdSJ}I z|39F!q!Vtp-nVBmojUrxQI{e5*Ha}!;-&LCZFaTV^^0?#8sXNOsr%_yg_TYgaL`3gX6$*q@)6mV1xt0yGFX!q@cL z_j$DFzwg%Wy?NYI14!IDk2?0F7CSr!SRd*~9KCW3NZSKsM*B}8$F(tEme;9Mq!}=H z>msa=$nu223lpcLfCJ`Tr-1ur6Wk5IFzpoKggG}va2B9BViCa>1C~`ZW$K-X4WV_K z9UwZFkP{V?bCsyCOj=@!;JJRM7hgGy(GbeoFw-lt#darE|1|&DXxFy(sWQlIwSkd# zqO2y@;&^*}uJXQBk@g%y$QLN9lm>b0?d>bo zlg`te?(yH)yS3k^3r}2yU7_yy3Z~K)eLkBEb-**WUxH5wAcA2T50&0tYX%n8=MJUu z3oAH=t~=Z~Q@AxoIxD2EP5Ii;Q)5~W7`)e;59;17u(b0eOm#_|+_b}H(mCHX37qI5Mr??_fu=KQ>T@sqG|Bws)9Gn$m{Fo%B_aPJe5?h!=0bP+U^5aWfxBn@u@<9^9gV;ongBMG-l^QpR*-_L z^XLsxF}w{pnnh@1Qri=rIh84+mn2kVK7t9prI1SnQx+rcnwwFUkkCtD%mgiLt)mRv zK~QalPt2wiNWdBl7pI#y)aUf&H2_)!GQgF}$XMyH7eb{qD0aUJfk;}B8< z1zHxx0iyO&)=bVXb*8i>gXDzC*5Br(pkT8CXQbYPTBX4I+39odTqvd0>xrhbH3+^3b z@!?EI04Dc5=XfG}l~pb2h~8N%yOpA+$Sid9rD{Y!Qb9=yl{i&j1UMf(;NeoLO&rm& zd!x*ti=+h2F*oiVK>beLQ5*azwY9)}0|XY#v}vdW zVr2K)33ANg!uMhVRn-kOHADhH-r}ck>J0aa8D2<93LV;Cv(lr!Ba_*%Vk)~7qLw_h zdY8uHy=M21Bn&^_O@R);u};ofYOF<2LZt z@fUsp7YPWZ^N(9aY$w5)kzR*`khHHW9)&Ert7tNJK}>>HyYE*m3y1 z&#pbUXS2b!laq6gx8@%BAtLc-Q!fq{4cy*7Rtv~B=hD##{b>M(h-MAP)(|a;&k5X> z&n-`wQ-`~3iuy8vO+xLZnN1AK$ZDUn(Ha&i)k_;ufC@%OR5^iSg=}W%G6d6ZSD~Mq z@aOcM+HI8fn9f-A$%^sOsbE^=>|=Y)>3=i0>#r3QGDW)2i7QhkZ5?U4?{-D_iphaF zS)8g-iv@~7BUMO*`;~6XDr;LYcnsuQ9;3M-5kWD|P>wb5?ftwDMOolKBjc4)cqX+C zT@gq3cbB`b>FjW7E6f!^2Rwq$1Mv#;4B+XUN*4m`hH$`5-U!*YG7QVf8JrL65Rp+K z!ycz0+nB-WUWn;L?&nYF)yDpMLE5>wQ!;pZpwU)f*7S^1D$giDIhqku7QP`LvWtJb zFz(yCJJ%A&H2{djA1p(faW|_vK(Sc};kKHow!l6HU=K}BahLa4kA>>*(&6L2K4rv~ zgcnCq_rZ8KZY5HDZ>0<2q4R4CWm6>8QqA zV7Ez?TjU=9*Un(#Jns{bKw3BR!?}_c*ABSP!W)={Ma-LRfQy%$%>(1AZV0YmrCvR( zg0V*#W}KJ<^u#fJ(MaJ*}nB%mr0 z%3-4a-;nWtJ>>uVh;$)LkJF<#>#g{y!dO4SlNolA?(AZ-H5PwO!jNI^@f;s`?uw(|RF94DVtV z9~}6(TmsB~c*}!uX^i86E`pm(QsICntqZ{Wvn)AaNt(H}W$LzSiZt-4Szs~jYB#md z$A+|P_6>z;DCf*oZudha)7oBl=gGD@#FC%j83GB=)p@`-YIxOYTF3c2>z52@1Z(LF zW4A2tt+aU0ZeU=RqfMm68@w<3Ua+d6qeHl5Fa=DJInsuRb~;E^7J=;)Ojl#ZYU_b- zO+SADE0}@O#WO^DO&r+%RS1UNN>GeEKU+aCJy8DLtW~o8QTc#okQyfco$Jrz&R!a$ z`OviAY$CDd7!bF;v{?nFN$0xO9HvBeGcJe?J~$&bq(3wKjKlUl@C()=CJ8N3H4><+ zi!)#d?R#kcYo*ZA<3C@oSHwJ|1#0*!B~#2r*x8nVfDqZ>xXV(51d`YZ=#@ z|EjEuj4qn_P?K-Baw-l#B8>1!=X(70qJkZYNgTCb-ERkGpM0u74hoYBQT7_`j3V*k zg`W=IDE5Xdqq_bFConpSsdk=Rh$|Zr1Zq?~$y_KIz6W&rk3)g>VN7Q+%D0c(ZTwUz zKuO}T56cb8vNh6PE6$36ej8ntZ`lv}vhMRGN*Gnv4=36+?QhoNP4;VfH!a`Qc%Q@I z$}Bd{*gH_%*S*&Vr>j>}-)XwmFa0JLWnf1>`{EkGtQ3Lt6- zEV}ESCnPI!0Tfum?Y|Z`Ue1EmOvQv-U~bj(1qlqz0Cj(IpUZGyfEL>A&z%UCgt9>q zCPCVnV$G6#Dwf0ZxDv3GUpGbpob zCx+7w@19YVs(BCM|Ji%8UKgmuOWKlaih-*NS*UdB$R&IF**xwD8J;5ym_pAw)1k^3 z(~}h`;v2tHj%$x&7)PC-G#8yTaAjS?vmAB1=x8 z*&|o6T3t=ek&t9Z=Js-JCR3C{os;62C+BP|O9?kPVV&(xUVmh2y$TMEKAiqA18_O6 z^R;GWdUlNiv{!LSEh&*mP8EBmWPT1g1(a+hPrngT(psqR>OH(XS9a}3v9#y#^@K&0 zJZL@*h2|+<)rhAv^PVjYd{JmXrl{OnBAlxY1;X>M1E-J;$A4b?efjm>SSEfStBE2L zn<0X;F>XG<@P?5~v`wH+5RfERcgU3p1oau6bIq)-^2bDtTr62Xn_-R2d%LFwBl#_pqQg$}de9J+*NQ*s8qvFTB?YqZivYAeM+$1QrYw!(&X?3zj{X^tdgx1u zG?-Upko%0tSq}Ccyc|hM)JCJHLo$pr2`Ekfp?Bt~1W-!D+|r%7-+m;7ddYyS9%v>6+r0J{&8 zQD0rij{T*j+rLlBrE&Se->J%r{zg?^yh7)|oYYv1`seQem~VkJP%ch`nkxUznLA`T z5|H{r`M=hHa#YB$0)#^z)aKX_7NbIH^M$($*$LRvLJ`~EP7vPke&&V-ig_`el*$Ru z1NYYlj!-pg=+H`h{rt&4Jp=#t_yQ7rM%h=(V(U?&bCGbPneJ-soedB6gmiXBpku8U z6H1|#5vn7$aSN)MfXE+(3__^Xg#5bcAgkc#*XY@C5CLX`A!-J=yBtL~`bRJib6w_|*?G=3?uN6|YTdP|YkWX+H(VQ31O+f*$WAksAZu0OzT-b&4e5lIeIpH! zjRNJB&hR(3n!kT!(sc|QEYexYI^xt_u^aV|wXV=2cdUj4om=P?yOE#g#207#jm8<} za_Z-w&-1Nx1*2-MqgYj}$BAu7EL=gI%+O)b0b zC|}R#fFqEi9m>5~lgDcSWo7<(ELkT_IW9!^t=XRok{Mc%pF(d({`P{D=E?D9snp|I zw`jAeNY?I}f?KwulLb>cf%tEk07L6Yc&u$z=B|>_^ZErx zfLZjPQ5U1S(oA>VAmt)>V@#mII6$Z01;81l@Y*)bfJ^{tfan_&tL7xX0*lrfV7S+O z$NaM54`fJsHP0cyQ-*ZCs;SKifs{ri9WoBwmwmYb3=fO5Va@k`ALIGkOXs-`z9{6evB3Y|@0o+% zhfQ_h&>(%+q;&kKeks_yfN+g#LRq6Al4sbr8U(A_^*B+u?AxE*{Bm&t#z`G zd|_=9rh%-@i0eMqAdAGd58Q#Xane^UTF%B^xaYev-4)81Ywh8!*m)o5(fd4UGZ1wI zWkILce}g8a0gS2;z@1s0F>txcl@5IyAQyB35_El_1bZp;i4kg5kMHc`JL$D)UqlG0 zMOra*t=3 z_$=}#?3e@^U)^vdruU2*Hzi9y^1)GPz^6|bqv!h2o;7+a*!7DlkVE4%0#LZT>CrHg zMg*nffJpXi@Ga!UzvP&K9UTxm8{)#t|G|ESeB({r0MutH3)e;e7dsew^rV?gErBHV zVWZU6dNL+UuRR6?WAyuP|B@mkO#zsD8hRfQg}`bhSa$5cl&%S!z=o)GPz8?tkN5ao z#CzAJ`>|InLLh^HrVoUkL5_e(D6C_lsRd-=bpk>%OCwFWgY0Pa%OU|DLM~AFi0Wfa zL5hg#PS~Gj2pgb=&q)SBR>9?q^@6kXQ~sRBU;w<9wc+|NgT)$s38dLZh3JCO_9|0d zd1>^mwMu8E_d}y}+Fu+Av!%9RF%*I>7g$i}(-2HEQ`qxeSnuZ;z>B*8SvvOm9>@^Y z($N`5UY`Y{?VJF0(5-fd%M5HAFMDRek25#&+(^~$Xk7oqy){@7y0Qh~)U~5yu=ug> zaaO|R%OQ1lL4F}*`}_s9cx`XZIzH^0pMne}V1t+l@n%1#Ge}KeQMoa5<;HlzlhYYP zmPVianVkpdAcZguurTKMrG&9tFOQZ`$fE13AWW(UH1qe}I&gSUL}VN7Iq8xBL0l^@ z5i8m2eN+j-ydFLtC-a+(A9eMP7+53$>L2=1r3&`;m5`oa~YDC zA#e*MKVQ7Mx&atGGYAU0D*2{gm^3!Ol;V=yZ(bw(*P_$F~H?D=d*o}jREmLgQj!m zy*=#vb=5`kz=H1rK13TZ=MhhVPuozkKkO^EPu}+evyuX} z4}%(9r3|WoimY9aJG)>D0=%F+Vkq?yvUYJj@qNa8ZE(j+)W?Nb&8AY~_4IAHxRx}@ zm$cSp9{**~CM&H%B~Gk8EBUcDpt7C6!Z$mpL--Fiae^?sW$6%p>mWG6p_n{|x1W}d zlxs_Qco+EI1xxscZ|oY_Bjhs9N?;X~9;ta}Wut+PS~=1|BI8BGYfM$uWUS;aJz?t& zK){zK^Z_)x6Gp%7h}yXb-<$)cCCBlmQ-#l^?qfwCX|(ucYjo9sVa zGH*@;If8L-d`sDu%fRbg+IUZwnmBg=bEvgIBNfFK`7~kb67soTPrIvH4_Kys3xYmM ztt^P(jk}K!1c7-E;1xZ8Pex_{G*|XDwokU{cN7kFzk96^&xJb=S+Xi3eH#`|>||Wj zmsSv>D(}16*Sf6QIwq;6@uL-xY@DL{!z?)GsT)6mXd)ik) zw1i&ckO=#-0yILMz@TLYTC&AFMUQN4(z~7_mb@gEFOpm9!%@kzK`7q+MgPlcAl^_; zkc*9CEvyqBz^@YlcNI;6A;$Om{s!lgwv&>?p#?G~!9iDmf{s0jZ2i^6ZtX^Jt3SNz^7F zb=c8kXL@s2HsFTN)VG2%E!_Up1o|YkeQXL?$O?dy^n9<#nqj;hHk8_Ps&g5eQYjn8 z3YorGX|qhTMkbL1^jT-y{o_T6_AgIDEW5r@os$}RfSGErJNA3lNvaYu2kj-=1cB2` zrX?Zw|FH4@PBG>!{fv>-g$m%+PoC5XzM@+QZ~hHg(EO)p`t8A>_ljnv?XW^@5iBHN zqsV!koxy0)^9Q{AVFdOH&~#qh*K^ z;HI_09LF7}=!L73t!jnrS&9bm?6f85(641kHA})f0?JOo4E|_Mrf0I0sslViUl=dJ ztfs`8DpY`lr!$)cE9$8ag$-jd5uNbVGWpTG43n0vFwQg+jo=c|ma*IMMwoW_u!o1* z5%KbgpV1=NMoTp&Q}WhwmnMu0^R-DNb&?aRqWRC{RU$<7(6H+o*bq_>?m`6yvDh8 zr%r;}-y)Ga*KyVe0iWtme<4SVNnt#IUg}w%61+YRq3QbCb;2ly<_d?#4xF~aMHEU6 zk>Ew2GCF^~hZOrYFXW}i$`!6y78$^wiaIm5tgS$~;3uiJ*W;Cts7-hTZ=0nc$ak2xcJ99)l=rL3_J} zAJy59qP_>#2$As+rK%4?#2__+trEAR*FoDmBn+D(B`2mZV@uH9&_rD%&?hOT#*jFY zdUgSDM;(1d;i{w&ckI9k!R-kZuSe}uzEkG3rBqy^@+b zQK9xeP|9qK%Qi#xM0d*DClw0Zm);Od&{0lo;f@eFS@*fr#vJ2KCy1vrecs&s}Os#`rFB}6o=DbZUU z#xKaP?ehx7sG&;oOf^!tHH3GCP6O;Iyh#qCyl{FnHCLP;i)JBI5;)>C`3+s=z#vQA^O|9GMo$1YMl!Ac44# zzYY(Y8vKX*n4lIXQ~VA)*druQ0Vwj+`d-K4Q<7@Ay?QZHsu!pbx9591{7{;-KJ4Vw zHC7!?TNF|4(kq5;TvF_2xF&wk9OK`Vvw^RW0&%_HyWG=HN1h8?PL{s6g1xU6F1qP- zX(5wQ5D_GB0ZWNP776HR(N(z}W>ULB*r_CpI!SI{5J*>}q!Pb>LF!8Fw8u_0 z$IXiyeY1sN*98-F@bFcMkziSaNQW7s@3ZV2D1IC<1fvlr^o)GAt3J46G@2cgy^XM< zRD%g|!3AlY#)oo-$j~gghr1ea%gT#~v|GHlITpO!t_S0PmTVCR1(x_&gT)Z>xc35V@+`;&^w2jH4kXqKZ zY%5gN07|pfwQWQFP&tci_aBb8oTFyXF&0b4T^1giB zCgw(%;Cyf$(IgN+%ExaB95<>>rB#H)dW8D36gX@*N$4o3qKF+jA4Re3dfMo1~DTG7O$iG#d>}_Jqd!3_(7~+5UK{XtU8}$2am$|!C?{^N!|>~ zY+ut8Ob`wHcQN0zGZv==nsjA8!+kY_Q+=Nlyz9`G&SSX=T+1~tEa9qJ?~@r!F{k7k ziF*@l2p@e|ltL_sjETt8M8>4MIkMpSL@w1G6Fvw*h-y6Ros6&Qz=R5!@;z?rb^VQtFd zQRVVyaALd5X-iB<;8BMK5t-cx#(tz%iS>Z_{LG7x6_Cf^A|rk8v8iS`hKY|J8DZ^= z&BCKNpyqPSuugn34|rYjvqsKgHQ?v9Uy9APP*Z2d-BfQT_(rZ6Qc^?e9I(g>;+mS16qIAEAzO?f46swkbu7Iuo(n4N8Yd^|=~W5?rMw1NZNdJW^XtlL2&3|b%pfQ9y> z=(b*bMhGwh%1po)wQ^%Z4m!MR3)`DGCytBf-?&*tk0Cu4*2ij4J*KFXT%Zvmlrd1Z z4)O-MGW7}nYA>}E?pM)*W{ZdnsrVF|zM_xlfizT%dh0r0v8PMdynCfhU*k4tmi^32 z*C1o>Ie}hb?vlG9M@T@$R6KIAGKS?X?$N7RY!!awOyHT7z6{1}!dW&EF9+@QJX?DO~B%DUe zR2k9m%eNNA7%$bCRN*Y%rsFT-S%h#6t78pwcN)pFPoVGGT2(WeNx zQ+-~No8l6J3XR)?Pb;;2m*`fQWBY&~X@acyJ?RB|VgV`Po z&yg=-vB-#Y0bL~0WgWmLc~;payyty*iz`%)F)6ohVVV_%$|?sRRZ%1l%d<6w?Pa$` zz0zP%&|IpD7IV4|>MV3s4MfQ+-0`fCa+=Wy&>q4Mnqmf2)dN`!QC6ta>Kcox7fMuG zS??0>n!+Au2oK>?@(A!VlJeK4$AffnLB#dMrKGzyFkHss?ZOypsbI{ThFD*9AG$mkIfO#2d3zz}1u+!SLPEywXa()eM8 zB*#|mb>G$%Jp~J@0Rh(d##2*P(h`AN^3+q1$?_kSOB2AjA# ztLn!$%$tGTa!Euc)VLbvBH}gBaCS(r7H1sIOiCO%&D}}(97MpQbbz(uRm>#hN5V zRN9l&EdmTSSJ<4GW@QyT$Q1>zB==O1hD<-alW^~b0B0jFdO-%y&m)_fx8xcuJuj%$ z@jaW+Ta+2EqEE(XYJBuD3L zX9fH%*)d843SiBG&6WMId4>+~Y0F^dixGxy?7^%%y}kr$aqNuv3T=t$vh!mD-N{@v5xv($@M< zxroQia%pZThKI2f07j$n8%pz=I@5ZUyQ#|!;@NbR%85`SvFC%&E-XyAPcTgW?c`cX zNM*he{g`)Q7BRuHit!TWjXJ|Nfb5StORcWi#(!p?&FklTY=gMe?hv@^h)BF#%A^h; zo!>|q2Y=n7yPRqEY>6{e=N=(isWAD-?D4`{3`B2vz=G~boo`B%^&dAmtK29#YxOV?`u*x+&VXVHCK zefPS|y!hs>T`qd-KD*W*U0xPX`^x=y8?cWDql1YlP_-@UPDXaY>&rG58?sTKzsKG1 ziaxwrKhT+}K(@z-UY(3wq?4BYg<_f%F}ly&J@)c-lN!IV;JN(5s=1UX$gS646}v!vDT0+rgqm9i4Z_DeAPUlf+3Sc^<2woLF@b(^4!-vB zvf%q@3M z&nJ^NU`3xk2?IZY5@B0s-{=bNgq170bs%jXl@5l1y(oI{fQ*bsZYDLU%Ea81C!Yt1 zxW570rI{(<%pW~@f(C*7ARi5iJIdneBOl5orU~#|aa}ZpVvBkQ=zy;%ZYo2T5(QH5 zhu->5gI+IxU;9+I+D^im*Vj(ZUVZ6ii!dezPW8UPz={&S+dHT1z5K#5c)C%0J)6HN zI{uC16EP`coTri71cLqk*E#?5AGiBhE9jerTosvKTw8s~7j#dL$!F%!wp?!WL^Cjc z2}xHl`cv%lU%AG=Rf>F&JgT~56r^4F(?r}cIoD>3hkFm?!)y6D@f?;?z)|yDjev}_ z?e7EPd^xjc&;4FZ1m3jn-b4T4S%&1?qO5=NPg!XL!xkoqx2j9KFzt+OA2UuuQ-^Fc zMAd40@cQXHw$)N|s-EmA^)&w$Gis}ciLwS7jM>CV3`F`$2j#H0drsjga%CUat~=TJ z#ZP7!xDMz@jEV?%EZ&NS#)y`njKvO;)eP7SHDNbJUu3|c9JiBs?m`(mqHmhOgC{&< zfaGl-$8GJ8Es_m}waxyAlW(*isHIv@T#hgj{Aw;*DY-W4(YHLE@!n#(A_TR3m2J9h zO?hp$FWG!_qdzt^Ep4oX^D;!aecU@v{!#?g!eWhwULaW~$fqkWM9q zq&3mT*<a0X{6pq+N6kl$%pK)6Ma~$AzL}uf65^Y|}JrZUxA;V~ILQ zQ__d`ThGQXI*d1o*B-XwAl}4#2P0nyNaN>=Z`uOQBwQ$)0uROkt?DfK!}d4zYvP9T z68VpI8a<8I2ebUFdka3HKM6KhV-s1w?G=?@9TR*jBjx+XXsJPN&&D>DQrQiu)h9vE zcR6k!xubO@F8lb3>JCH7wL0setJI>KhC6S2y`FBcS~s2Lz=eD6WH3$LK9;-Z_um!O zXN;QBis4?YFQ~vQUr0e$5HnNovCnWC1UwkWo{b8z&9w&67V((rMzXy|d#1zX9MTRp ziM>YA{2pZ68qLvX&e3u)s^?e#EMKiXYl9*CDSvYK8D))f~v;!?t#@K|Cy@&iM7$=0$oRpYk$F6VWi zktE60Gul*KkbplF^%^q5ScCsDXxs^K#E0iT4UF%0<2sT>8csEj6K!s<&3`R!mhqSb zg!4mvtdoxSBuo9eRYSBE+iM;Au|Q>i(H)3`Rr;=z%=Vq&X)Vbr6c!vSIWP}AJp7>y zLq7Jf*pQ7isj@jBPwfIjd{`(tr_2T%gtU6mCK${`SR!qCLgQSl_Bwq!uhEH_9tiz8 z4UmE>x}eJX`u+OYTh)~|x!n#BT?mnU45oU9r!E!%oU2a4zp}%zQ>dtyMNeyrw{&Be zL_c@F)pSl)jkdIVlCLYCG@mn3E9@Y2l+#VPqh`5G zyUdGZf&KhOeF+>~CtFwP<~$ubteKFN3F{aJ<{g%zOsSk)09|tznw7v{1+`jBE;-K{ zILmruZZx;TXU{xLkmtb#}EIlhK zWO2uCbS%>9tG02i1LNaXpLB-hSFg|mXMjeb54b23voX<`Jm~ghO(9DtBN~jQWj9#e z={XRT?cQBrHMVtr%I?KBN1-r-X}@N8$L4^O)a#JdGSc@9+{VU>t8F3=%kZdl;)TqP z9Fy86V|XFWY6}#A;#VX#{jyu>A`X|NILMMK+xHb#omJM?T?3`>G42g!yB+BG9~9I+ z^s|F@IvwANsE+h`h*s1HPu4+;&P50t^=n>~7sWgq;7>PNrI3~dqmFnknPqyu5Ssx> ziSI%8QyS|H>>e}EKSbE>zybL8G~UlnMRccNiU=@oupiwQpN6~*5#zBbhqPU80ACWe zQ(iP0QXnRBpbB0g9UwKj?SL7FU>JLUq+w%>NW*O9wx>242!yx}=dpclIZ)kw$7|`q zX9k!@ax8wTE!_l~!S+DduMo=A=?46%0Y6GqoA%RAU0WVWeXD8&w4_Tfd6zQ>&rYXv^A^*cP-1j9!UNm`I772Tas9ODqe z@8YMKO}LmHV83U+7XT_v^vC7ohpkXVBmnNwow@Jhu~P4TcxZ(mi>rmp)?|33Eqp;^ zaIE;3?9;DAZTs$KE$PRf!p%BL((qf53)6X4i=cYyGyuiZ0f|X51SHyXlcW#c$XDZ+ z4|{$pBSwk?Uhn)XJOv;fo!bn=>G4=*osG3RH?4#(dvMErhe+Lt*#XK@bceMj$D2tr zqLmwg`paO6<$#=9!Jn37Ls!V~UA9H1`7_vf4*hu8Yi#q13uFLw-j4GgISNW)$`aHu_M zC1kvTbxw(I1_ZW%3j+z=1g(t24t+_J55(>) z+g&@sP<<*`i<9FX$M2tMpe9;?IXp@CRa?*l)qu_52Orx)q9DIZqS3eQ*7&UvqR=?r z00f#bn2}wzPUVc_=j%airzJF9mrfhlE(Cd;mFJJ;8dt-eL$e|%fgLn4X}t7zASjy# z!#8t4l${rpdr98$;-d-KUSE_txw{F(4~V<5X99_X6CgxO--j^pO+s@eX7LX(hc&=B z>DK9|N0guIXp1%*0*CDRS?XZ*A5DM zZM@`&d>vqGi}6-Cm4EsBwKItq^vZ13C*b4bc-y{ZAz@5#YbV>&=8F{cKz}tU**uGq zXRgw^B?*Sreb+IpaEn>R&=KAFDq^@;n*Fn zbE)8XHQ(H1BkJWp7$TZXY&LIf0_%FW-~Qp1432sX(@$Vaef)A=T6cMoywTYs7zWtt z_>#s~A0vrjX)p9INr1fMB*0@=ypQjTikle@fNK)c_4GY!H8Aq5BS1T#{xSa4N|xtJ z+%ja~dh80C)!DZ#Yti2Y{BAgAg1$PTS{54k`Q4~iI(`MHk;twFiR9`h7PRKzO7_RgO~=IXR~uiHf&QQDw~hBqs0LuifO%SS3LBr zoP2;;RDh9W#e|z9A{vGuBkm~9fMDsPh|AUQ-RXz^$4rGz#7( zoR00l1iL`u@KXJEl7p#pP+QUNC@?&qppw+n9JH4|IE}9Qas``hb=U7X{SqyS8daFJ zq#fY}bVLTJpw0udShRpkHm+kO(ethJkQ+8_VopEzby{J(d}~Q+r62h_Mio_SKsi^( zSzEE`v4LxI^hO3i@*ZsHL>Unb(4qI{DP~e#vn>BxdUG_gF$}IHrP3)>4TkbgZ6A_~p&O?;A6EKo2+r zB$W?w0#8St$isI|UgMWfRn^Xo`KWxN)OJ>@`rKTqO*%Cc$^IG6L;T@q8`i$=k$S%G zxjU%fV;THlOu-gLni#Zeg+uxW{l|0e*u0*_IcJUFei;Q=w#zbX+xy z-={?@s^J3Lezw8ZZ_NQ$uTR!Yf+W&D7y}!pMytJA6lUxp=myS^TUS|6wmIN-djP9r z-oAJBx>f1}n)j4NzX@JRgw729;|$c&1yJdhPVK-k6Cf2_5dahC6gU!y!Sow@qxqi` zE04f$3LeU;e@EOJj@^ntT4RIpm827uH$Rh)mO^G$S)5&O@x`|AEnb04mZ=l66j|a| z;@lOOfmzZj@Q{~O&Lk?oSiea*M4oMR&hnI(W`=#kTvxn@6~X!o%tw4#^UNF?@7Am! zXP1tIC>mV2Gf?72syskF*ijJm(bCUit9B>r7xkBH#cJM)v{dh+?h1Ht`W$Ej`++D} zvUCC;+ZzNQ_lL3GZW%}b*)>*&DVhPOoq0cO#UeKgf_+hL;~q31O$)sm1`4FbCv8_* zD_X8Q0?B8omFIQAV?TQmWS-oV${$LbSV|v^l8hw(q%hl$_cpEMZhH`8CceBmgDq&) z*|uH8vHjHTX&zG=kRb1_1WG^yQL>YopSIB(Wl9I+{i1aGbse1IQC0PMR26A&E2C}f z`un9e{|$zrqGJ<|>#}S|+u-UsiPK+ZXcFz;{Nb-Ae#%O~TO1x|og|(}5HgTGZf9{9p=@YAt7tWZ@UJXd0oX&n*u+cP`tD%M8dsEE>vr?VH?ehrL3ct#4#gH z=sxQHiOX@698HlBop@I?rQ}d~HZvz{?O5Iw?kA?Nu;JJ?)`~X!ym7QfnJnw{(XP7<+Yo-GSjpm_s9WUNn7z2BxuPz}3$|vzbpzW4&G*so6vZ zy_CBU-kSo6bm6;bbGw96taxA{YzBhU1D9}i>2`i0pS%u9%XETjrF2JeHuDb=j4%#@ zW!~RuztzsFq;U&V0CuN#j7p31yN^8!-H_>fD(rW}l2A=!oUeeo9-mT4eecO`ievopm9j-i7>01cuMvC8Iws&m{ z+EEMOR=^#T?nZyj*kEPUvd+V-gjU^1PCBKkzCjECU$0a`2 z9<$HH-;Jm0mATlD=aJ@1KAKT??xr950Esk3uG6nQwQKHKYfX-4v)%;pvwh6x2x4{) z8s6&hcQ7~hZ_6CQNsaH}V?E!-d`qrKE(pEsRyN?pkUC2B-_f;o<4))A3*1w0dUFsI ztM3^H|DzT#3QbSk+9{0rq#kT=ip54) z7kx?xwvX+K7LR;lunwknvHRVA)~D$FTr)#lb!^&>I0kp3JbngP{?Fd$5$&f2C~LpB z1%3YP9o~?Mx8tiX-LKD(z6-(V%b!l<_*zv<@K#FrRW3g{KplGO`!2L1NbX%I=#%1f;f1@ueqvplpLTvi~GI?q7anLMJR6%#LV%@@xk~9a{o}?jwnb zKgWIk%ZGpS^7$_U2p07<@h;DQ)Pwx%hov9E_68#;q5c2UU-HL$=fiSF+B@?zCw#Z> z-#_Yq{jdL<&z;o<@5KMRMgPs+`SsTR-+YULwTy3nl>Q&SjR$pn-oE851(H$-`ga1z ztUfS4C~j6r&VSey@#f9FN|3TO{rQN>IRK*k+z}6O7idx{m+QzIVBFa@bwdAx)2KcN zUgoH(F3$hacA|O|#;g4H0T8x;xGqr8$&wT&UxGC89-z860g&vu$2)VGr8b+OF&8Bz zC14>>GSwG@OZH)esk0couKpih{UQGR4y{t+_!iM8%^ z#}#I4=S|zGa_MnD_(5*&yJXxFG}T%EkDi4xJKYd3dzg*tBSJbbBc_Skf&0O1hFJzB z1Ix2RqyJw>{ZEVd*FUCG#2n)i{BDy26JaM(ruW%QS%2Wj_3yDoCWKU;f#tes)^{hG z-@BGySLLgP5Yd!uY_ilGhGUwc$y#s{JdX?@_fA1%VL*sX513SGpy#2KZPtbG`X<)Y zSx#LLaVBhf073IH5iIqZ0TJD@045v;)XehNQer>6Z|s3Ko#+}4l4PtBGQk^z*;6K9 zG_E93&a<On@U?BI~g zbF20(!b(Bla0r`0dufRG&_dDr9ESm71`N`$uMm+q8!%2$2Je;Ew1b;A>KG;(1`O^A z1)Uh8Ed1w-PU7WTC(lGomPu98t9r>i(5oQ%I{eG8^@J?X5WduU^S%`sw2k|(~ zwcaY%jTMc&Z)JzsczJm3zFbrazI4Bfl1wML)9vLJ3Ub3uJx)Mg|}0To$!dz^R1HxL{*_1=aoyu?<7~ z&1n5cT2o)ojd!$o39s9Mq2?=)&#b1x%eIapO;l%KbKr6;`tL78E4pUfU&ZWB1$=xH zssJ$vqTRjn`6-9$7Aca<3iiB8ETbGx=F~u`4z#9H5l$3#1G1VBGH<5U7|k|Bk`M99 zfx#)S6PDIS?t=7qLV9%?%+-{DB`I}Gz@uHhN@@+^DkeoKEq+2;*@&@$eH=P?eg#oi zgKilo}&;Db%F=mp22!U;1YGb23Z59Dk6*>Zd ztE&vww25G+c;0SGQ$fvmd3G587I$3w7^g?1{2Zc)mXzyH@#rX+t8D^)Yg?gVI^wPY zGHyw*9PF2D5+yWTSHIA!eIQs4RwrpIc%Z2}9Yz*F*Xd3q`y4;GsO7{pgBk+gL3N1CS;@XP zLpHS{J6;h24P8r1b(GB(r~1sgpityHE-@(<>>=5RW{Iz?ho|OiE6z8x@*p5D#FtiR8-vAEcRCfNRE&*ddspE)@|8%J4;ve3^&wGnehycQ~&AYu6oc&xFU$ zkn5Ofz#(OZ*gwn-)s@PtvGVXVanL!aXBzpDy*4aCKwUsZCaZetk_zlsUPI^zp9hBK zLc4+kVj+SIOdb4cR}g|6jFpbwz*&KETq=pHyngG;mt z2{4;1dsIc7Zbb;TC$4&BAhg4&5K=26 z!TFA8=(Yh>%M8p_ExchTBJzb}KsV#Tjyk{+P1Jt>WNAVqr`NoYRQ2G&gYykHg!}WH zqR8TUAlkJCC-zBMK#!MsB(3w<48R-Zu$2rD_gjz^$#a&MF@YV3c(WotW@@!k zqegj!NShsNIy3n?+|t5=_0*~N*nKlIP{DpxPXZbG8&6h3K5*Sp(BHJz#XQ~zM}8Ff zjz3VPfmnSFk1@ObWp*OLq$Affz_c^1%SL}dF_F-pXya*w%h3*s!Q)R`TF(B=w8SYH zH45`XfrdB{Ie{>55h+DyXaa3opS7myAj3gvQ56C>W|H|p8MY0B} zCoMf)EgLx5PdnCtdSd1f$K;FHVdg}1f-b-q7`~+dP`RdxEcpt4L=S0|HSAxz@sRvz zXOxTTwPgSqZm19TwR>snG*!FRb!xSj%l%)R~7u)f6>g?m~ARiz) zY8ZMcNYot2m+6RmSK;DkvWE3#{1zoRQcZz>e_rQGcZ;k`=#+sHA)YJ9-5wNy$it61 z2@-4X~S;HJ%5(<>hy)BOsw`lO` ze)Aqtm+UBX&eJ$Gn-Ad~EC@S9C+#=Q8)TMIaTwgP_c6zxr^atA;28P0pa(C3;-nXq z(|C+KR`Ky8XV-0kJD)F|i9LKD&7H%&i1fBjwvBE=vWg zO<#mksx0-D%ktZr7b{8pmuITxcG*;EZ{FW2`3NW;<^jO;#z+MWM^a{LgnMQaKt}_I zjDVzzPkVf*zVPMQ{e>vd$lMe?1#>QT$OqO95Jz1g?iN}4Wj9VjaWYN_2Hr`k_T{{x zC=jHbhjWqY8lvW30K(C@bbV%=0r$;K~irZ^syFV!B4jb6Y zVbRBlJF>Q{vrv1BErKdZ!N z={rB*x$p*;QW^H?bfkx5-P7qNLHvLZshB^<9h2z{^s>xOS0#1x6 zi0B3g4@{O|!T8BK5)VO55r^~l1CS4P1x$u-x}A4HQf)-v2Zk*vE$WU{f>a5zwUUuc zNTVCk<;O+H6qKldmP}TFhD+OA;`-|q5Ys0hu8E*%_2m&KJ*a)!03`0sR2!n7?r`g% z$1?Tmv|q8j9~Z8@2(vbnKAbOU83gVG5_tA6_Mf>Z(bIa66Z!sk+YcC$ZHN;p z9Q)a1-quj%$(9iKs3U?&Ig|sZ6y13DWtGgUDNW!<#}B)p33p~6@AO`JU;jxV<$7qI z%FJ?8qQ0Mr3iY-RHamEw0_K}X>WO1hJHoRFRm#5YYHjNc78Tt&4XO-DlWmZpkIT>b znpn+o)oq+s@p zA5pxiY$Fq@TRy>B@u|~r&j{~s!sEtA9co6(D546{D{3_oXRZ+mP47YhnCsV+7@(m^Q?`*oPTXG(fN<*{FhC0V-h-Ko* zu1c8*V`wtjfWH``)n)>!FU=`hVu(jxm@&)UaD|3I1UuD^h)hA3CrQI2k6T|50FQg5 zD6oohF+7<7UNV-Y%Mn1Dkj_2rqH@d9a-&BgW(yC5`GDDKBJ~zY+stL zedS=&SwCWIWu##|JGve@PJGeSzUzzo(tgvH2XnYgLo#AlW?s{T#eHntTt!v8a^J(7 zHF z2@-mbbDfSHSIjJ7ZcN&5!r$uBaw6f=G3ip;^k??zru|oSREtK0^ZWG;I^12!(>uqG z7+beB`QtK`7fn=Fmh3t%jH~c3-hY{RJ^RE7s5r0avj`ssDCk};J-%W%8(f|IQE6)z_uADJKOxK9CgE?sZxj3y5Ailzkxz7I6z5VnvLAnz z1=G6Dd^SlMW#xWmk@s0*jlFZs?y_d_}b3_zJPw>6-&S~Bf8d+` zU^~_<*yVZUv#Q92oQrLdTiTN5MmuNQLn*SSw!A8f;Z!hfE*T#j$VqonDCYdQOFdT6 zhLS2|qwyYo%c~%FN0n@oROud90~R5>a^(>12} z?;^$D&lTV8ZuuK}s)y$9a{kd&_AATn562u8UVpNUInEkE&^B7~D9?~eEX{2lV7P!g z7bn#0)O$HdKF;4S^W0ANs%*6moU(E=U&Xa#eMy>eE5BF^3yXWZZ(jF#RexfqonJ@# zV<_j^KlMwp2?}-%RH@K69v=m^Usjs0uX~qzK!HwP)j=Cu8S8}bCjNnK#Ll?XnCLax zHIw3V-nmnO%pN@algEioh3UkU7-l7wZr2X|F6UtDyp4F7Q)%1J%%#%z*f%xb2)dQX zk$3vQWX;xfCH*zt{ax!vtQx=J&&s)&RvFOe$zYcb@!Wgc)|51@SUu4ta(B#Fg?lxg zL4M8$OHk-BvKbo7CCC>=l10SJzGA+OO;F*;cr4vew5Oo^Kt4Hz50gwl>aDQDa&x$G z(TY>kQQfI$l)6rMrOvkXbR@X0wh^*TjMdiHeN?a_IhQ)7vo~}Mu>|Ej<8|Gpjtnv{ zSAyfMH7vdNoxao&whqOW$ZVDV?VhX#E$kgrUA*TP`W#KfWtODzd@k0xbcW?c0%cgg z;B#Z_#OC}M>w>|Xyw5DO%Fox`N&V;iDWzx|dY+?mjYlHu=^yMt1{uP(&2Vde-0dve z%MTVyB)WR~ikZy9imx3y60dlKX0ccXC#tQz*3+NJ8XG$TektlQNB6^hv(u8-ShVw03vimEPGDqKjsQ#WKVllswH?&kBcd>+}m0! zrqnF2oa(bIv3*QNL6Ft4{JcV)u@YsjvEWw+-eifF`s|oYy>Ct(0=D{$t^NAjHP~pZ|FyC#T&|rHq0G|T2`4&Hu8< zmOEdz(=yC-+=!RC`4mNlfAekJzSI?1JioGWxB3%4vJMYEUHivRfBpX7zmj-*m+&|q z0-<{JF(Q{zl=S7?v~*jg>&^2F+*wU&Hm18yo22`8cKIu_H^_d{+kwsFVmrfcr;CbA zOOUFl?xbdYIV^hPV)2S^W3O%7Yl8Es+_eX>A$u+Bs%G?ahWD(@?(rxup%sXpY@0|d zk?c!!NfzuoOHVU1!*#Ac)OaZ^rjXYU6)2+9EQ@U>uo2FH*L7wESjr?2BsixnaZe&<%xbBr_&f}vpk)vkA3J`l{bmjaKR)Z+;?>h>cYudA#tY32uwZ=D% zwDQC$bwTo83S7 zkIDkGYd>`NO2~JX{=Vik$u{zBZb)UAm&&@+N4jY3%BVw2DXN_fj)A10NtPmVi+h@K zHqGo6odu;Zbu!GeHBiFgY-Idc%RS1|xUkl&EOy~*mI^r{lq_~{?!MZm-zHKkHJmP* zAwcjqUDJ9#dVB5+{VTdVDrd>DB*b>B8(RoYbBAyXk6xQXflqN|+TaT=#h2FKA2`ON4Swazx)W0i|`edno z?CtWIuze;cTKo$*KV`9o4AQm75ptM(Y_CBmlPy>lKe!|GpC#L=%g_NAzqs$&pZE$S zyba{kNr29wN4smHifk~23pMv88ales=>;uRdx5Vnw_FMnTioXuf{ut_1b<{JqJb%{57Hx(BXdsz7GiA z%SE*EPv*_@&oR({9WPkuCKHU}odIs!gVPAFjfPc`(t&Si1WtQ8J_p5FVWpdQcFM&`j_& zUAYqna2&V=55W=jFt1$ zlqy`Gl_V)hb^Y$$Zkw2u#$~VEjNH?Bag|Z!oR;cYR|iUl4oerK&>>uo$m=2Tl{M$N z=5Z-+yg|4*KW<&u@=+{a@%gjPKKTASd{uE~ZEG()TJ0FI5CO4{q1#XsHgAKdC_3 ze}E6jqFsU(nUS3o9r~W0fdR_9GMv86zyF@Dh&n63q*fX$EhAZ!j)KOs09%2x}3`J@+s>9yQJ6r%zIQd~42e zE|r=-Ux%gJv7+8UI=fxX8;NF@SYNgT6QqN7j2_Vn#@|S7qv$kz*yWHNBcE_US+8lM zI~%p(bRo_PSK;L{;a6+55oIHD(*$B``^Yz)L?}iRWY@O4_!9}Z*V2wE8*_vHIi^pW zCK{_g#rRdK?5~Kyw`h1Zfq;SpJD@KYA~6!XxSQxt9y_d9s>Bt?O8;TI4^uw4wJAnxvtrylIhv@kPyY> z6cGGU$C|u{p8*0W2MHIJkL6?Hot|`Qx0F*S!ZH&jY1{nY&vf0^>lw;eZ=Q}i=IAjb z3(Zci?A0ckf<-IJ#bEP;WCO|&TqUQ?xX%AGh>Aw2%B1msEb`k|Cv5(EO+VxzLqq+3 zk9KrRpEsh^QGg72n0hK+@T_i4oK|G*nj+}%@Y|#&*$N&pP9>G@$kOvjT>r)fK*CJD zX!DN!bY$+jpSwL>@f*#77As~jJbg{Tp5Ds9Yrh8X2J0qfSMwBMkc7;_aNl;qIl(ELBCLL|h%JWNB zyr?Ahq~k`+@}4i%EM5oujT_OTa+yzbz=}*c4v|)hquq zs`X;_0=g;Ui1_>;q<)l)Go&KcaS;Tn{~zh?viI6j|Ec7^-N}F6<^S7n$xk8;+4?$N zjsMd}xp6U{1q$@$pa}R3I}+Z`4mWfOxd4!4$C!|R(@{qdxi)D{(aM6^%D$^IFUoOL z37~}AjL@GO1_{xbeWefcY8>?S^~Db#`oa{0Ose7s~o6qd*Y;DHY@%M<0l@Q&BV>w&L z15c$11285XLDoWUs0k#JHXGPE&4dVEG`lJoGxs#&33RP7Qz6#>S?8 z1z(!R1ZZCqI@|ewuCM>?x&P0n&4_b@u}CX4*AX<>oou26#^oSNL7T_JBtr@|f1+%R zL@EtaW&_|Db&!$#@GBe5T>`-5pJ=TH>+9sBL>N)cWv|hD{?r1P=<0wDzdk_FT8-D& zLy%`LA0XtstO&T45a*jK+Rob~axu!{^bCJ+2)n&tl1Wm{d2#XVm7h3`73^K(`)i*x zqIkO_#daJPcF8BEQ5i>oP)!C53G$Qxos5sD0%$@`OB9INST!{ExHZe)WIJ)({TptG=qia;fsG^egIH;ItVN6NAh_RDDh#DpAlUfOTkaf6rBp zShTLu4(+?F4jT5~n+q5&$PfK@Uta#*7mA5^h8`NY4b^RWdRNt3Jzux3?`|{^m1IN8 z7|&kCSHjfO+v0%MnhB;~12y531fQc|aJRPtW<(tY;9{SSj0%%TmEMsS2Lt~aAb_LD zGC+(mt^fvAAu|>^PI`^hv5a{xLwPS>vj z(2ReMo^GVG3}Q`zxOfzhZ+It_W_nLIwq{mAKx_rf8TCSX+=xPt(~PGycrYo^S$sH# zca}fEQI~48yKbcjAY%yb7#S-2zj|c|vfpWlf(RHk&4hh!I z27DUaLZSQsr$_;4&W>Yq%|$o0-N06EQmnZR-1wAQzD;P=Y?QCYl0)9 zY4dRTh@eA;;Va;!L$_qHcdF`53tHXwwEu+u-8`c*PeX9e_JWb*R59*_B^sU=F(b6LxX!QDv;L;3LUeGnuw6 zSAXxeefzGhzI-lY%lZc}_Z>lZDIULXPX?H5gXisSAGC+he%~N&X(xKO>gJw*)Uq?+ z{Yxg525NcP1K0XOVBA1xWx5pY6XCFPuKAXVsr1@LZtW}|r3VKs3^8BsZh}txV$lD*my*oj|kJ)Cn z?rI14vwX%cjT_SQY#?g02V5_m(K4r+s+%rkqQpN`24NMQ?H|;^REO4Xrezde&-g6H z8GDu~ci58P?3*6cET?$A1IsXZ!*y9sRHrGoZzVaRF-5D?1ZW#cH&7kiG;@v!Y8}4K zl!#+G8Dp=kUYriDq>S7*+}L_DI>F;rb9i{z>_r)o@|CD1-;JcAbq8A6X%M8#H)osq z#FG4mK7Z;8deLwVyx*%vniCHf5*!oneujR+Xj#lIa86nm80Og^TyyX?CDnNw`RhlO&7J6JKyEpnM zTyGC*#=Q>L_%H{o=4Ad@7KNm-vKY%RPdN(DqCRAVJ=Q0QhVBMN4RUXv@LgYQK zM$%x(gL(mGtbd1!lJC3f=LI$s#)L~ePK&o``OwLj7@u}< z78)fzkDvm;>D>%WSFCAgZ~Ae1q*0xHOg$yDQzG&h)>HPZH1-J<_rZ%6(T>f_yq&kj z@*^MM7bbgp=8gr|xHI1(bjQd%4kCnH=JinLUJEi#+T{_4mwKh$Zi}sveakKo5j&^h zvZO~#Cr6#+vbLP_M4F%#WXN1bFNh7eRa zb(?&QWJiMox>gVrohDXyW@D#hwxctdsNzO$5n5x6w9!j(pPCV32JI6$nX~!B0<{7j zMeI?@M?W>}=ogW}vf+C5?FzPD}tr_%uUdx@#t?`<^ zq$Y$6d`)_ZQ6cqQEBr(!eyx7tu~%ePY)uGolgpL`XktEMoreV$K}cY5{)XT1?8UmA zvqp`K2(N0MAa%ev7@Zd%6;;je959@I#u2sKdUucGq@Znr)jBW&;OJ-iSE58^-J=RH`?z zj968cYYpDwjEh_VPo^EHv&8@eQ*G!VU5~cz1TD-dw!C5{Z9;V3%wn z8L^JC4A)Qdxl+l?Hl0gMmQhW>OK20o-GFd5vMlDw%}ri|HHXJN0BX>t60+il`6dWK zF>AFB?ehRc>?_el$ABM@?cUL0&+4rnP4Y|9T5Kq){wVy+nbixQy6DekW9T*@un@_v z7#=}PKggJvui@9N6F2}^vv7|N&Fztms8wX6F@^$0eBK#1xMU8b#r4#o<>O0&m!Aie zSRM)xGUp3tFIu&*t)wz(OheYwh@;p_#0(KChKU1Av-Y63lq)@SfI4P4J!bOgcmS#6 zdPw6p`C7Tb@RBHKH@I}vr!Eczo2y=sEteq?n~RruUF{tD+6Wz6N7)*Hly@=g&fmk( zZ_J2p-z6K;zsA#*FaD#3b4z3CO-8L|inRG@*39geVHCsOllQyoci(A7gcB9jNM%A$ zO2-qqziw3oJa(3T)ggs`N$RlAne1x0?-JT$7<_^V=a%p(kC-0}cOq>2wXe15%-ff~ zJxHciX0WRRZ0A(=L}s&G@1>O-Fik8NptW{)mrva-|4~xf4_^{Y;mh>(^%hyHnH4&7 z`qu#zuE`RH=nI##5yxZk5jpZYX*Yi1?jd`^atyvu2Q@^MTbC1ENZtL!Ou5`#*eT4N zA8}iM>3;>ai#Kvpd1$A;@|3u890|{c z5_u0^I6xko%qTsWRz|dJ4&UFm#x#3M7)7_=kPsb*uL-PP8p78^GY>N*(2S~jsfR7> zq{1;Irm&>Z{i8wnpI=nO;r-Yq5ni5&?gIV+&s@eIUVm@h*dn%E2d-V->8VJMt&ZMp zc~NNSG!z%E&8yIo%Vov_87xrr6g2*KqgbhWZw5+X)2Uo!A64wA&TvteCV8bOUA&)% z-mVdXB^6bjy#R<~O1Bf^nf-!FE&#gOD=^toow`Ds$Ml9@K*>G9RDYJr47-)M+EC?1 zp^<{JB>X3H!UL){*|qCkfFh7;IWcr@p ztUXM)xt*Rqp?+|rltS1l{1w8_@;HKhoB)1W?5wYz-C1T(%m0#W%6RQy_lr9wUrcLU z3+I&BCFJa+B5NP-KhqAz>HUP`%)afA61)kY%g+jUBnKtL%!s@F&XdT9O7_6;wtqX= z|Lte6JtBfn0e8`euye1o+^sgOR?YYEHOPaYKg10O-F<*LPKv%4zl3Scx1Uk%KdRwe zxljk-JX!`hYp%p}@b=}cNS+LM>f(jnBUy1@L1cQA5i`&M5ZSegz#7PaI*oJPadl0E zRnc$wm8Hw}UbItBK0L5jW~`=Ru>#ttv`EnCBA0lF3Hw;w93-Al{I<2Vn6n=qA*t^{;XnD6$g<% zUPdoPu~>Mnf5i*CR8jLZQ<~nPi8C3>Ta}Xn+ich7TFRBH*7&atisXNLryBog|Job* zrR$N&idFQy9&;rsaH5SPof|}Tv&M%s5G@wJ+=K8|?(Lv}?m(_bvTQ`lx`6nN8#n9< zbdPl0=f&MeSwE|ROm!4IqM3S`^Pmk9BpQt*GLFvUnJuTOjuTa~lZg9b-)iR@d0alg zOg!$B0um4R;}t3YZ7Kiz&q`3Md-~ANu<^1U!JkX+*nKBIV-D`E-Sf>Tm!_7-Es0{4 zNA%z^ODKEf>z8>mT?Qa!Z9hWkV`B<@f4mnn?6xF$-XBj`UO+5 zHY~lK42ETU#k}3~;|^k!!SW|1Kt_@~YXIK8ifZ;|42Or)Z0<>JR~I8E4?$r)d!Vf5 zJ`}y5TreMm5WLQVncZ>JhgHr6>a2a=B+62yb@@LkU-4U)KX}u-XMH{!u|swoiH}tc zw1%d&&0^of!91pmOsp)iNcEj3K*o@gyiIlx=F03NQ1mciNdjq zx97tIe{#PSNeSf9MQgd+A0<^%IVV!C3E^C&SX4-bcF!yghUZ22km?c6({wpu(>Cjd zyVIkWITTtK&}gQ{s9u?ThG(Kuz|OS(!a8QNPp!rk=j4}gsingFBK;*<6hTqijdlDr zfsHx?__Is{%rDQ}uqjUfS~e<4cC1u<TLGiF;Wm$fjZiieX2*_4FCeUtVXjAJa(JmbFXgcn58I;x z#J?6WXM!P773y&~pzsx*w_2TTIl!yT~ z#gwL-NC(cc7TYsDNx z&!B}6gFE)hfH6&@<0~~>r>-(2e%-5)V%h7-3M5iLq%!SiW*4IZPjY&7A91pvM_QrmDc9#}uJu;n*Jo}*9&rWMM zHjodTI#p97M>C)uY5P255SWEsa~q%;fH0P5k+vZ4Xg{WLY zdXB1(F1f`7o8^84g{~`^KpZKne|!VUiq*g_cOIlU14}N4JI}uwm0Q6ZVbNubnqY`H zc&ghlMHi8-1IaZWlpmFpaTCFh%rp`BhI0+jpX2YlzaQNgOM`nm1@F(Mn9<`U_xYY| z=JWBPK%Tg>0v^HXFk86 zPoeieYB-;n#QZj%s~yCOKUb%-B)vJVkK$oV#@Cd=3}5x^wWdC^H+|cAPor$9Ps;kS zt_4ft(C?S&7`A<|&`b12{O9?-SC900X&es@ zC`OF8*xzPTN#;tcx6 z?47Z^;4sTmu#imc8|^1evR-sfZ{|(<&z#^tXVS=TK{aKOFBu&L+vLqv=}Skl<_S7~O?p%Vbv^4tc;ow1G;2ambjcN2cbQq3Zq);8 zP==>N@iGnA}x#QJzz(_yEeB8|Pteb^R--?_n=_1S8U`=*|S_Ae$-|6Ojf^ zp^j%iqIx+Pm=$9wS7W4nLx^BUL)ZAE>1w_qAwP!lh3F-8OjRg9Z={4ST9@fAv?%Fw zWCB@dC%M{e$6D*E1!km->9&QG1dCoqixq-sEc;pf?dTw{mt)n!8%{)c9gEB!4s1_> zEZwf|x@K)VriaIm-!h?9z3oQ!`LeCLug>AFmO{H^%^ncq?Gg(Y5&W7cp*_t$WFR}L z=DIeAAF&yc?BnKf?zR%B2K`!vc(&)xH=B4-Td8lay3S8*l_E?#Z7i0OlCiQL^}md| z^yFGLFXr{FOUKL1_UU}2AiLFgYg*x+__MNB%A5DP4p6;+z}R~BNkJ6jBY8gpYp9+Q z-)c_JSHX+t_|vUzZ1v|?)LU*ZUz}VDNk5maI@o=6GPID1dkLljxjjYHS+mlU>1fT7 zu=rgghLA55!eLFrb4W#OSRYcQW@nL>lfn5l z&gMx)xrX07pddXNqi5>Cful}%!Mf_A7i*k2(=4c_B;6Eey=Hx6E-_<4-Z0rzZ!Rx- zjqsu!i054w{RSN_Pr8COM78*WulwVELkIImbCwZH=(Z~zqv|-8@dAx7p{B2<^8GiY zkEyji)aX979JIKEy%`E;(4lVG`S`bC0QY0EL^ zfzcT?iX!7q*B!MbQ&zL9UoRYX*rdiH!LLyj=HEOE?Un=o>8$-VVur6y%D)w6r6czn zCb3+zUV~;rE2QI{GGEaChOg9@jfV*6h{&F+qWopmKZd*!iX_f9lbtyYHe;=Q>S&iy zOBKIzrv`&8_uloHc2|Alq4Krd-M_Zc3rW~t98MeY^x>*&QM|u>VGKU+Nc+mYR_*K# z7^`BXX3yrTJ6sF>neKgLi%1Eia9SCO?0c&?`=Fhj({@YQ=wE&>9L7me%}k1+|_C4D-Dj0T~t zpG!DRF!@XjU0jQ~M=|*Qb1;NmL+4beMdoBox4|KvGIzI?m@YAp$ngbKojc_ z2WZ-}Ml3vmvm);+HPOx!6o5|a6%hj6N|C(iGNK-TOlwoj;2*E{f6cypuV5%1uha(6 zQ&5zyJR*OIu-|5HJDWzuC((J_MIys2l>Age0UYz>fEw2JJAN}6{ z3%LmDeYK^Zg&1iBXZh!6c#hI7R2=*<_{Lc5yf3Edk{_*QF&pxoWWRaUm&hm?p3-Rj z0s26KtyfIPWvlQw{n>??zdqh**L~rNHM?0EgRg^2=}*Jv|N0eNy?i*7&m-xBAAa51 zfB7of<1QVQ0uN_TNrOws!;b~zV&C_utQf;;n_AGFP^?`+;{{2F$3LGQBoVweaZh92cdfMFr7(QH zVy%{Aq2XKe%&%qf9wo7y@0l&oz4~O~k>IZ@KPd|hz2iK8;sk$zWCLR_?w0bxzx3xr z!E*Epmw!2$6W#wUOGoIhppBVB9v+>o*OQ;G@7MqM-@n3mQtlMiq&rHpA7f|lxux&q z_po>ECW%nG+-ymm>CdB1GkXgOm)X{z-~Npy^Y3jM%D8=QQ}+f_OLVdIyU2eIjACeZ zy4nOdocJkW2Y-8w4;GlXt@se-U$^n!E`FFprhe=2w#xbqy58?`nxGL8UGrsR@|fVS ziF^4Fnee|#1#)#$N%==;(v*;hHRL-tce^P zXCD5yyZq0~kw*#Ek#ym52>)+CwtxM==uCJ@8HM>Fzkfpf>*qA;B5`7A#B$HR+ce}L9ch+9&E$hwtu^m6xe4IMmb<=1~-LGuneLFAPVWWCIOsOyKYBgr;x*vC)ZN`61lq`dYFvsgScMVD>TrVSXK zEI6y%=f^utL53y^dT~?C&wi|23^iI;S630iumMB~LH$6BHyheND8Zes`2DBJ6c7Bx zPLLIaMJAzon(t@a`LFL51LqYz*Mgvej7jN(Jvc?hAyOR|p&y3~Wt|7OnC~F= ztYPPyJC~?m`tpnOeP>)_f_5=(!$Hr6;RxQx7GPacO=2@MGirCG!iNcn?vEVp>6vZ! zKjd%w`3x}(_K3RgWM-tne|;N2_gC~YjMZ(a2Iyt(A$TqAsKeSn`cfhOT`X1~R`13yzJqn(Uf!d|}o!u%X8&5U#rgcvkQ*DrrB7cTu^+6V%?(#DQ z8CAD$iajX88_0i*xaYKr2c_En#7ri9UlN6HA=_Wa<3ndmN2s^s5h-t{_#9~ z_L0JFvkm_ybO~RxK18V`5wbJ%uU&8Cg9$xkl@!AK+Yfi=Ng0OKls9F(W}UadVR2$7 zZ2K%eYdZlZx6U#2_qY|kx7NT3;vp*sM~(Bmfxf;n?94=f;3au4tM`__#5Y)-jNjBJ zflhpqO!#&RIuqfQwi@OPit|4plK7p#?8K`YR`37qjkpbc>0vn(SX!`{EU(_Gi$eL8 z@4Ho%^rIrYLV`VxEV|L4!mUGjnAwGUx?{Y~1Q)kU_sgwl&=H0jdZxKI5D`KsXIMt@ z2|r+;pU_ihTx93#>+byaE+kxKXfEwrT3UiQcpZc_+@Nh5=fGEX^JjxY0tJ}R#FUiU z^XA$uLZi_~Jm`+Z{zybHRePtf zA7<4sJ-YyWi;Ku8PF7rDsmMZeT@SfXN9QnfOeICrjmNaT5fn9b94B&O*#HBHK=cj+ zbdpT0jE`pK$CKXy$laJy?AIgz<)Hc%TjP$qDK?cm*-8181Jq9CGO&$*F6Z5(%VXxP zDUqg~Z|YE=sH=A=&_NL^<~l4^wI67b56B+#n02;-43`mDy6vKzo}M0qCRWx(%Yjz@ z$$XtNA-6?Sp8W{O_2QuCGHk_jk@ojrts;iPgO-LS_cb%-C&u3`=nS&0uPgWLD$$w= zI#Yb`%=D(-yh*y`UV>$pkK zOi?^EhXsJFbC^RQn_WVPIqwG((oL7D)^>|CZLKY-GjAL)MlVsP>5iRqCR`*%-VoW7 z@uH1&&KrEZye(B4AW2l&U->;0FdT(~_z&L^DGB|dnTPcmbo&%Q2x>b0uL5!pT!b5R zUKYAAZfP*m3c(THWmCXF3l-(xg}YZnZ`b0-!jw+HQXHMoW^tf$?U{}wumV~E=E z*qF&-?pr?LRo_RzZW;UGHMFbAUjJ?P05`(^R?u4GM^YN%M8uJw@9)L+i0h#n0{&w~ zhfk{Q7^Wo6LkX=;iOId^L>+}ziV1|oG(?#bCJl(4)`9O^%_j?v`TF^K3+*3k{J$P> zJ5OF`$aQ}d-koC^%m2vrmcX5>x;K7q5D8KtsfnV)LwTYwdv=$5^y9&!onWNEerbRL z&|1cbnpBVt1%g^K>)=m3|9`y>%qg-Vk=q+SZ(MKXzo7Uy@guG=h@+gg zT85_gzqxz>nP+FjrywJ-N(1>G-b?;Afh%nG2l6Xx2xI_jgNP&hiwB z6V-*0R{#>E5$UgjK*R4>S1$^&#_-O;i@Sb1*8KfxFf5^vQxeWga`ievmtMCW?n;Pw zDX1%<8tP88E8H=KK^j2txsB_hJdQd|72i?7Hl+eMT}4Dhq|;jQ`=Y`yLz76dpLn(B zx66lLQ5lrwsrD_l)wm2e5Gj@JByxi`Z?fHrA!M)xVApJR2Q29lwMrjc#&yBML`I`k zNNfIif93bj_`d`hQKZnq_SIdW`jMeT6YdtCYXrGhY~GC`mYd({x0h+vsE*Vl1Y`faC&CQ|wxHCh;u6hetF;;!4 zKzdq{{*jLQ*dPI5;)R9iZ?C(PxVuku9?$8TfB%a{c@pLqO^qxXSubNZDjOEZJPUXcLkI5!HewV{Bj1l_OFDg7U1nhy@SiV+J7uHU|jzuo#> z%*ZZAZvUaFK!rHDSg+7KWd|oRL5Ok%gjW-QHv-Roe-ZlsarWKuSnvJ+rG!fvAuX$I zL@6U>RVcFJvbQ87du3BsWS`33WL>uGb%jJJBRiYyS@y-n@Ac{AjC*|V&hMY|=D9EgWd5vt{|CC`@qzkQF!tUtdKW{J6u0~9)`sdspKA+k zm)UwM)0*SkjDifp&x4^*%xs2br&&kFyl6*`OWlXv`q@7p(1qPt|Mnd6828o+@bUEA zrAlN+Z%>b`5s=B8owGXh`@IAOAP?ai)=K7=AA+KXNZ!+WyV+i&h5?7#@BPl7zK?$j zV9%|vNSs6$-}@~SKOy+Kjxqn8W~pl9Md1S8JtV4`etyM0c{}$!Oisn zN0;=Bo>?TsL1E<|v>olIa=urj6;6cLX`aitrYSdgC)?n~S(S}Tjk!vM0L~_}E(jO@ z>!yNSz^$VQ7-r2nfw=Vj?~~`pfAUgUr?ZiPcb>_<6stelC*g1veL7O``x*7cQNs>{ zHFR0}Z|xLZ_jiEtzx>KuN8q=yTBl8%`}N=U_Fz}JUdgADku%CyI6A(c>2p$Tjd974 zuWM8iKHE9PYy4HIM@dd6a?v&4bAGI+G+g@&UiFfXY0T=_bfM9Ey`I%6Y9*X)zOJPYb8YQbfyYcET{o*jwm0Y+A_Y$C5jG#a?z`xywQZl?DR5Tr2+hAgaFIOn zd#9X8CYgTy@i0?K>2wA#@NNVg^L@Y6cISy|Cb4-+321X?JF zNY{P7XvCvD2>gS5>XYJKpeQ-)k>k8>bxg>)SktnWt`IO8Z-YC3KAhkGB-aNC80mBD zZ@&Hdp%JG+wD`{NGMa?E=nx5$Su|H^Z-!Fl!VI@RXyCE_pWJlvGq;v%bkqR|2)mj& zZGfX3L)(1qP&Y3CL(PHNvHFvNeqEZGedCBhrz&!?NCYx=0Il77^p0Z18iRm zMQ}QFLpkM1;m2^bL+jBf9Uq)MhV*C14{`rMfMHj|J174EuC@@p-(v9CrMg6?{}1LQ z&$V<$ofOW`f9gDmpRCrW*QUOh-Ahx(L@~cP;DWhv?~!@s{ZAXmA7tVgH0LzE_#n9K z{)Kg*8+&@y01b;1no3X z^Bxo#5z|HOX=-J^T7xiwwHAC80;0?d#>vyPu_TGT2axEd!73liCkEf~G zFUe;T0h24Qzh{O2D zJ`JE`*dd;l%-uk7F@;0)_A#GlkBE5gC9~cB-PrQ8#2e)!zP92>@E0g7kL}J=5%~DK zf*@{;bZu97<*~OW?}1X3>qd08znlA)#Z<^99VF5pnJqTMIzBPNQKr!8{peX#bEU1H zh40)A2i1f+=x21mv)Dw=b_T3(WtUjGb~ccgqHmNL7AgHhbrqC;Len0X4=xN4Z`wb; zC&a@Rbb7Hp{$~~OuiyQDS~pZIIhHND15@Q{Kyzinoqsd>706u{|tw& zj+Q~dWzdEK_N6bpwU!95KzV&UXXTn6a2OvGhUsxRG_u!n>#aT^l8qUNR*Y0fmc2=L zp22U+hoDUgy!PGO1@dfHfZeVFV2)%$_@f!C
  • ^b}?;gPzP47-1zsVx|iN&xE(vn+k!~eswHNf5wxX(}Lnl9efLVAZq=gJM6e` zIsX28$#~2q^Ad2Rw&z-!>28(bAKDAjTKnFI%T%LCo&%!RgR-p$fXoc2^b5gMxN9;c zc5bdk#VuZY4kd*}qBd;ipw+P+Uuaj>M$%U@fQ)JfG|C7(wHc!D@`s(VO?Duka#<7! zj7EreC6?QPE7`6>phd}wMc}f|Irlvj7Ehr?jMe7RJN%FU8*vE%NyI?pEcP*b_U*qw z&;X78z8+3sy=Ik+9p#&K3xEdxXfF*w3x*b3RpNeNSNxgu3Hx)1h3Q1L2Bg%^$jEp# zd6Hp==ZmFlw%^U;!nbfYmH?$H&@j^;9|p8JiF9%0^jw@i3>S!^|TD`OdJ;I zfD_-dFP#fb$J~0u2yFW;>X59i$3kn=#LBb|0#m7pn;9o+0152@U-pTy4X@s6c2;K_ zh@~!Oj)=uQXgSd;H53IN#C`rIObl0*q%9g(6EEK&j-i#gE63Rjt(=LYAPBN~!2zA# zm7HsJ#Jv35Q*viS{@Rq+{o1fBv=HsUsiol1)Waq>7@6gJ{dT2MxVG$Kq4~fZeMvk% z&ANH3T6#B61+9%EaH|n=-B7KW#!xyE-?P&1WDbkA&Qm1vkhoWykLhuq8zF``W3QK&Kt5uoIr>aHc#fsSdOF&U6kGZ%-A(Uw@vS#2R;2NN3K^ObOD z6gNXw@GG@k)g3PYX?xe93o%5huIji-`&JuxbDJ|dsjlMM%Cp*Bee43V#8nCEU3dUU zEIkSrTo#cGZ!NgAJo2GOZYAQY7Xiy%x~sq+05Ey7PoQa9 zdCo~G1WB>vA_)(?%C>XXBEQs{T!SUt&R#{i0YC77UWASq6b zSLgFLH=WDChhEd*%B+NR-4rx;>AUQPF!ZI5P;rw&a;+7|%_y%eh)^-M60&01G4nuH z8gp(RfEKg|Jn_w;ggRh;)Xxp<0yx9?AtmW5@G22KZI)+LRvGsBWaZrgVYe7q>DH^U zc5#ae6Vh}eoF!im7Bzt%0m;UFPzpU)7ilM6-pW|L3vbO^?9e-lzEKXYNDH8jQkn{!DctPlYb=do)XWugHv$O{VATCYguoQW9 zdx$4py5-lx9y4nX2EpQ#oDQ(5II<*8*W-$BjRlAH==;#cTZ;0dao?pWH(4$6feEFY zCWWrNHyg=8J9gLLf_6z}{`deWKZ}krY26h$r$j325|m3M2I7HS$eIyb8Ui&aH@Zgv z&Wt`6OVHJRfxTT%=vAtu6%yv&XVWS@=ZIfCH@lGSMo354t!B$e!Y)WO3QOr}?VcyG zJ)U&E2EtR%k@BU_QlcU<fPnNaKPpP%)uDEF;3uZV54*kVED#u#ok!=f3wzqV5UV&e8Pz|`n(sbIe@12?jx#R0C^}4n-rMp8NQUfg?lJ>Z zIx8>q5ZeVhioo?*x+wez)Aqz!8lg>atdNFm`%V({55swNL$J!oVhfM-#-9c5YVXj+ zJ}<=ZzbEnf1FX=YKHAR;V%IP+Z7JrJ>t|GIwMj5J!;ds=+tJB#u@TzBU7`=}O*F@6 z4Qo9JIff2vRNlJ*%|ar5s4*Uh#Hdl*Q2v(Q$AS0IDOgo#8VhtXB||3 z`*B<5oJvaa#v;I(oAVm`;Q3>TK!w5f*;f10U6#B&MMsXjllOm?b0QzeCSGd~>~7n% z_guLB7C%R&rNuC^w;p>VTL0GpPmz+nh30I2U0G&{;?%9dSEyYwV0T{XLXAAphPWYe zyLBXyT}QdtN+~DD^CYScOl-Pm4c@r#wp8gt;Z^RObQk$fI^khap%~sQe4!HDN4`!n{~=_Oq+f_7;5p;w z_d*_X5>qh|$vHKJ5~8d63Ogs=4(#)PEq#wX@}=p{CU87Zzjp&;h2VzRu**<;D0@im zjuqY^mKktVe6Vh}u-Jp{5?enj`4jnO$#LA%87Q$=hLndA2>E28zMf~-NE|X5^T5R_xGv1Wt`@(Qf z+4~U;?m5rR?lEX@RsVxrhGvnIlN%J;SgwHXuUdMs`n;n+c?PzQEC^k|U-z$;TmSt* zdsvYpkYNuw-@YF69>Snf-^})t+n(XUmlO0ck@&ma=dWJvq5T5>H!l&#P&0=Cm(}jU zs>coJ0~|_jbaxdHS)sxG`|s3FhtU%(G;-pON&w)?aJ(X4v;YcrlAg710Ss67Ee`uX zV9+*T?-v*ipTA+0H2HXL4{<$oj|wq2=*s-(C6Hhe9`CWD_T7>Kl+lmPzct>_E&1?Z zXhTdl5AlC_TeIeL%CYvtl>U-snD{P_uXJ*2YVk_MGRs>Ds8f}9?|om1h}oIgJ|b4s z?b()zpWlV&3}W-&rHa*H#s4yoW*1RNcY?u9cT?;BK=dKz*4%1om$VOd&;pe03J+L^ zV9nDUBFXL%5sXhZp!3Nro|3Or3-5`0xt&U+YQ*+TY(5L*$1Sh*WW3TVkkl(5^5q$z zJPQueQ}F*tAGHU6u#2lqF{%-^)zhJNy(Eh;ot5l;o1JK(n-G~jlVmJ_dXhG*W)vw* zl9?@p-(c%l**cz|!QFVW<07GafxvAuA$JwZdP2g98*aFlwej^bVF2kFoutYVI+S%L zp*a()F;!t*>q8e389D8F&&YZ>Y6sTj-;F-hVOS9%w7vYO+-{p@D`s%~bWPAM zRc;Mp{D10p|I6Pc9jyQII+~7Cl{Q0tq0hNtu8k)w>mxM-dv9AP*3^+%b9XG%WH28W zeH%~MV+`b|fH0;Q6&ScWa37wB`ivaS%7J9DzB>>!IkfhDZ@uDsY({&AXJfG5D^Q?S zsiB_Q&Z-q|=;8<~);$e2K&i6a^MJUFy&29|4t}K*5}Q|EwvjMcgHzaCGtBuU@6q>G zR(BdTMqPm*ORr%3VR&#Jg@WJ?Hez?h33ASXpR*C>pf5zgTXDF9<4gaNDzuRp zxn0rQ6bSU-bdxZFg3nkf?~#9So_r>~Jon{%0@w6?*CQ7-!)aRTeCDJK7}YnFmf10N z2&rJ?=~isT%9jTJsrY4w^8z+woeE;fKp-o5uWnw!V|Hr_3jP8Imdm*8sl#A*QdOnx zunqFU551VVzOu51AQ?6Wc9TyT0T7#EPWD+MhLcKH0SM?b6@0n&iErSoTJ0wV48I%Y z+QZ>2jR0cg9HENa`1(S2cup5~pA~>0yKYbl-a{reDy5Qq0J#F&d2pIy zsgf|X{|WrcF%aSJbk2_mT^nPk-I(9qGC+w<3{1LmW_RA_bGbid8vhOw|84mARV?mIIyGA~ zfWTA|9IbD`{A2c89TOM#KvVH(hM)4y{dOwLT(jgt5*$ z^XHduEZ?p=TYy*(gm7vCE{D`y08`di96FEJrYi#y9Qb>O^o+qPDXgxpKGBn{S=NzN zHdlILQR?aq7Qq50*R?7PDxnC0NH}1>{S?qif@#Pq|1Mc1g9HI3Ss}bFQz#+k4(q@3 zv!t6$*uYML>rJ*@t2AHtL`$M{&zch`bus~`EVB*-5?;`Di1zVw zGMTL*X-`-k-&hCaC>(z@9X^*2GJ?yB_P9Hs2JT>^ix}THk{w9*<;pQQ+LOp{3ZI)} zV(#2Cx^+n`HVySW&GYPzf!tkLk=P+TN2g(FgwV*c>b&r3B98LZ#*u^nyxV=yRhh^$ zcTg2$x{lK(3sLU4wREwKWcjrGLr^sWcv9}&2{7^uoIbB}_3OUC`!WAv*Aw*);u%j+ z07_)emx;Ou9#Qj}Yf_h%=s!c&su3h>7e4GSzoHkpa1-pVHP<95-=r}?`Tu$k1^*j> z_YG2_?IQe{g!^5;`D%9^F^n4GB^N$N-!E(HA9$4K1EvRhOd~Mp$&wD|K7B#X!3^kw zKay!@x?dwvJ{^@V8*%B5q;gf4qFcd4v9H7pkh(b!w{TXS%dkBc32%pvJ@%Knaxg2; z7OaL!M?l$IL%Uy5feA5uM9$4cCKxxQQDSA1ybjU1md)ff^cFx4Z($##B+gaU-es)3 zla2%)H%in6cS8oU4yrjVyYy_kTOXxyX}0r%bZe=(^De|0Z?0c6@7}XRB@4YsX@jay zV_h2GV`(Ptxdk(6d7Z_1x9uJ+aBfnlz5Hn7%)rS2{_0O<&_GEOAf7c`J!28ce(o!A z0cCD-Y+7P~zz6e)oOs;X%Iz&DC(!&!dlXnO(bzHDfx8+RHL2U&y5#{vF~x8S%y3Pi zy|Zk^AD4Gfp^T|RIh=iEJ+ot(agZ&pX$EmVY_f0(nZBeIJB#;Qja}VxA2RaaIK;TR zh;>p)DZTnn<|(^8@<_iPUsPy_<-6K-%6y8}Ys#^nj;` z#;uH3E?Z-KxM!+lQY>6(CI#CRF#RYEy?!4kX`I&*o7?>P`X3-J54|_`L+a;w#F0tE z`?l^O^axn)1QS+@aJC*t&r7{aX1facD4R z!W+PPz|t(llA*rfEi2qQLG}Yoxn8F=5ER|vBE}Tl;c}6gbWym0(`;XkIQg>{a~CRG zmQY?IXmep|m+Hc{Fu&d%~4^`M`TC32_oSu3}&iM1$@i#Y-#}OA|TFOl8>}RZQ7GpUfqcG zz$$$UTJSdd1yo)d^k}2oEHM^AY+3_!0DtN-q3_5$aA?eaBr$pZP4o(;23`&YN_$dN z#H~?)5;ISG;`1K&+z71hq{kN6`@JO;JYxFt9EUYx9ZcG#`bZ5XL7G&P2$T|k5%ak% zfk9Sa@)SL1vn66P$EdYb2k8Ow^w@{kSRY5u%f7n+->7U8XLl=O}-Etd#E&3p2IP@S6N?kc|Q znlM&ZbK?^wZeZfI>b$L^cAJx5|HiUNsTRti^=E^|e1&+)DbRBezrT|yR<6~sQY-fz z;aZW!s<5k|a5P7aS{W{Nb3F1+-jcWLuZ&QBFDgau0&V@`XNR?rTPb5zjLCNJ8qnF$jDZ00c{gr5c_Py}&<N20}@EwX*Y4=p2K*JSnlqlU+j#Sx?2Uk`k}eCMXUw?46cJ} zj8AK;+epuHjF2aCQ0jVQhe)65>S3|Q?$|3^cMQAgs=6F|dxmi{B}8q;;NzdNk^eHc{0n;UTq&+0 zXP`Uzv@eHS|4dvU_E6!YTC3>=-^KGV8`N=C73bv$Ga--NOnIoWrup{1f0@l|&YCQr zuux8#JtP$Qh(#wjEY5(ZLLm~0iqzUz-qG>#9w@9wuj`|JAm{ki`B=`B#z(&|X*rhN zf*e^EDjD$ux!PHi3&q-vJ5!tIH<*tTEsmT%@FH>i^r|Q7-sxkxzb>rgQDZLEdzws0 z7hn&XOh9-Qm(0sMQ1&G66Vw}9>Qp23NmL*A7Pk26$(ZB6k*IIYD|5iO@kGPx6=QS3 z?Cr94lW2u|ssbOIm&=Eq9y5h%|5|Rl zJWd^4pcGD*0zobIsz|a>+HhCYRWqN|o5|~yJd^zm5i2wL{sMM|_$wt!_V&c*3m%rG z8$E2?XhBs*nnOQiG;R24A@b&a^dr-ObO{wg$HNn2DI;%@@gb7u3BhPhFl--{k!Q&R zbG}Zbs)O&p1i09j8Dyiae~>C~xr<1nf}XK&GOz+f!qM+QRNwt0$rzdkVDKN`%l@gD zfZ3^BBIBokp@z@g4KY)Uthc*I!Ov2?IkpW$t8>CIjp{79~%uL`|m$g?lJKaa|xyEqkY>JC9(4<1S{dC z27*ob@}|}AbY2Kswe)x{WIl2}kPkO3i0u^wg{Fq~O2EJOjsNYqLUY6oD$jj;+-EY9 zFmDP2R}Qy1Q+AEguEH!WgC0J*QpWcG%(!ElJMXpQnrK74K>0G1mXzJ-QK^Fk+j>wha}>Ndct%qknW6B)9bN}-!Ji&rpJPz z{Zx!tOAHM&yK(jLzii9@;3nchkryQMh9karX8(^{^9Un4?ZQ~sd+xw}=p`Tf*0cV% zSMz@ri6X}2ZEYl96gIFePQPCmh^$ZYl-}n0b>h~40Zl&uM?51#@24o{&xiC+|Mbcm z=ytRvayGxL>-po=|NY9&rNa-(^U3{Fiu_M6<@YBXbb`qC?yJ~;bUmrLL`aiyUaP!| zLSTaV827zf{cF=J>Om3ZY-Ud>W0YlJ5pf2 zd~pW6^V3K#_H4@nK6iieOte6dsa4AJDdoO|yNt}e>MoWbUrU?Z8wOFCxeki5`< zfFDom)o&uVW9uf5UTC-{U)Z8)6p`I1@ko^p5oAU)INe`Jb;|x--u8})kTLwRIefm$yctv? zT!n-KKx+%tQ!`>#Vt8q1n>9YvJYJ}UvYB2~!>J>NI>wz@4}X`^KD3?MXa58!ZwDP^4128Wr1V-5kxQH6+4GtkIp*b;$I!)OQp_yTZ(iAi6n zZSSY$oIb=i8{tko9QzoqBqyhX;2209g_u++2q*N!Zf_bQ+BOCx;~h*qyPzsI0He5E zSz$sO%x?671{8=yyCa;o)zHDjqE4HPUER-5OU)p&;F{2Pd)-fEYX+xz&4GL~*hZrK=eAYq z4$R-|oP?=&0YZbaY2q>O@9o>hm$Vk@+!S z5^ucfXcs!9(ASsCVqHTO*3`4XO-dE!1byQL^O!=Z+9orids`^(pWn-WIkx`Z-C;!s z0gB7<ISoC zmw!HVUX3=lR9G1E0D+J;CS~1@=4w>!9tcG2V`=qDVgEeY@vT#JJar-HI{#4eh4=xl z#%b_A&z)!vuC{|`WIdFRL?e_xdb?)Zsj2)`OAXxXCX-Ck-J^({TBIpujd94qbTX?6 zF?@Ao-J9gz4@}m1#;pD3OqK5t5VFsr=0Mf3O6Mh&wE=1jn~n34b5XSH^+_X6iO6AG zZ`+(@GY`Cg(t5#(z!VePS~}$}V2O_zmN2Kd+R-k3F4%x$j*){ruwG_WqL=`bj^xm4 ztJ3W3(kbkM9$(hRZGw{AcVM6M^_?v3uUvN;0Yati&>hVC=Sk9G7vk%$Op2->aRYDm zIUxm+JCt9gpibpa@VV_t@yYCG!59}sgz{khm>C*D)Q{i8iQmJDPh>#_O4k#7Ym#?V8s;|IM&AR~Dm3r#Z zsd>Rf#)y|MY-#=ImAgDV!~u%Icf`T|yb$CFwA~#fb(?bRsa7xWX~_!#L}pm4lE9 z02rETTF6#i>Z3u;O&q7yYjv%e1q!ZZd%Yz}cD*{p&YZFi6!}DQ%Sj=062IVO zwin3UtWUU<7hlp1%csDx`RkUK@Me|t^p`2d4gr)V_Ddv@5$b>)c$dShs!gYC!JEh( zE0SVsa~%DowFdh|OIR3qjYWvO46{j_nm(7jO6%4L+(FCua!82zcx6)U+y!i`|MmuM z+nVk}f?NN+%!M$<&+P(mn&hM>q{J%poy1@HOu+hhIX00M!It=RwT_?Y8I?ChfRUQ6 zoVM*pVehOD`a781tpmH!${q7XDEH}&QnnXHsROOcWuDnWV>ptv$$P?AiSE63#Z2t* z&VQjSdzIvVT^A{n5fOl3STdXLkVPkAg;{+ayT8z&;gI1VliVWn7q4o4lr}P#{t;3T z_?SYV-W7(KrGtT#*mGge!^0=-b&LA!BFTwZn=KKd2EyRuKzIV0%;Wj3GS)09un%<1 z!KtKE5|ED4G)9hNgd<*+hq#1VcoRtp6naX6CgDKH1~uk7Z5;ggtzp9wk!ROUr^>LG z(>{a}DYooBik`c>i&LXSigKF$N#a-yJIZbSQI)9V#RLNTn?xM%Hk@=4iWUl^=Tupv z&X8dAhQVswbP7t8^x@GaUAQz`4^d5PjGrP#I{u1glZrIZP2Wq#^A7+(GDf72!?$N^ zgv}r%Kyo95r-MBx`8ez zJ(N6=ybz%VMS~{Y>xt2b4nclMbhF3dN3n`2a$(pQ)|q4rMShWFx%ld6wd7c|=GFOR z_oz81;!N6r^05e$-U@1l#@1Zg%kmC)Rvp%aI+|h_RS<@&W|(w4zPfIekntfN+s^8p zHr<=9%tbG`G=I7@bZIf$J{0SU4N}WH4*5xnHbB#tw_u^D{;PGh_?6}3kAlan&lXAD=pPs1-d*7hmW6n34zzS zP;XLMH>q89w9pNkHvF4oO8taD#temp`%q3o+PRvn?m@JQPkZB)@#B2z1Vx>*rK}vu zJ`aMIb7HVAY4fP}tQTnd+U(KVcNayICTuTf?ux8d7P@vwOM-5Kc1gi$#GkL)_ryE8 zRE6N2iR3pOzEYzZ$R7vYlx_hf+7(Yb0P4?23FAe1`NFph9qhn(cY~8FnhqEWQD81@7 z9k;eRmyoO@L**X1@r>z=%6`}YsYMkBSkZL~IWiAHO5Iq`^&*9>Y|<44{|BoB1j4H+ zhtgOVska+R1N1lc9%LC5-q@_XJX@phINxT-HFPoiXPxHJcBt9jmH7SAk!)dyxTZ}o zSb0w105#MGU4q-Mv?4z-fe<2;cG@J%W%L!FPRPGmbMW=d30kpin;R4_Pe$E_Qr+4Y z(LQ7(?}{K|F%}}F-*w9@FT zTs6y1<@PqkDw*?Iq#w`weG3$JJMUu{C#m%<%hFHtPMEjY#$shF=im_e`{Q7xM_R) z>BfK;4O&pPs@UNZE|ztdl7 zmqkkEQ1PcX2-7wg+dX1 zE6AM^pKsFHxO73SyaT)o6jHBKri$?~v9TI4q2|w>dPVgVduP26Fau#@82r6VKTP|P z)ZetH@O;=^ViqQ>5$NF&^*3TjJe4Zhv76+$4wSmZ=@YN8%BP9F+Oi!ofu>z`0&R(H zJi~`Rp>X;YfYy=KHZU!(RXVUpKo2GtC$pIwBSIOLa^O@Y)=wpMdl8|xDnC;w7JO2+ zJPM5pMAYTgyAt+Czlg}1hpJ)HkmLs1LxB|dFO_*np=cdi1-tEI+hPBS>}BOwX^vs| z`5K)sp`L-*yX{CX`#H%soiIbC8fWmx+w;;gS60iZu`vgr8pCXzEzy#*8%gdni`9%uRF+a15b)tuDF15 zZO*mbDbh8>Mz{h$l|Iz&Y3ZgNx}>GtyJ3)XNt`M*PGn8j(w}`s1^AUKSf>k0V$~?d z=bwJ!hRkHZ5zC(XjITL@pXpp(vk)_N;qpcoTp=r+D+Tii)vUdQ|9c1h>%a9ldOD8z zIda}eT{F)_{Qc=wo4h_qz77PoOV1B}B+ZN=d}LK?Z=caT{x&S`j3WqOuO+`}Mbfi~ zuA-JFl9JsK-RDe#FDJL4B2#)W?F9&&KsQ2f-ZTSoZTqV)0RxkQ_GY%i=VdakQ1gsk zst(Z;1d}gZ%5hR|)Hpc#4^>v8ULZ=YTweb$dKZM)YU~EA{~5RDK;A0hVHMA z+y89dWRyV$_Qv;OU2fx)$&DjWTWcp3%2uXtIr+A6Pn{GBjHUUS+EGZihQ@R zHp0xcooaiJwp>_!k=0%Q+ezPa`i(IVOy0LC8A$T1cD_SQCBxa)lU2-4n z{GXL%tqjeFtFW)RJn1CU)?QZFos)MNy>Qpzj&$c7l-}%l>kzH`_)+bVz3jo(_ujbg z=7f1DtH=siGN}O`hcJOCR~*{pB}#U6gFVv-G`mFMh0-=JGO<3vbv&T-!4f8;mR%J; z6J`bi+p-rnK0P6$(QvpUEP-g#HcEWv%GgHNe|$Kzs|?eI@;!8`u9K?`RA8Psu_(G4 zrN-|ZnM!!g^b@bWrL~)28HfOgF7$G788Xpd0}YerVqf3t-*Dd{QvVm&^zSXrX_O5l zeP$*a3;rOPZv7yc{-Bp~qkZt8Y#q*81*}pHP(Jm!qL#P79hhOeWzc6me+kjACBfDMe)r zw%9iR4*G?7!0{v21t8k%J0lY{5yD{cX7|O;mXCndeF1y6*{}u>{EQ8L5u2|e!D%^8 zo_3nfEYdT>fi?#T)9hQ0zHD?iM+SDk-eMwS)O|5znBVh4R_KUe+1+F(K!Wk?+l%8( zl;r{N{=N0nh~(z`E238c&KnE?g|V<+^iApgN4Ve4N}@^3%4Q40$`GraAB4TEQt`C@ z%`1qbA`+akXtT66Cy)nh@a`r_9?8gO3cCXgsV?6Y&=0ayW8AkjH3rC@U%YV0Ma*YQoW5dT>z}XU7yd*>FE@G$gM@vLUcZPCPXU~Jg9x)x zW9Mcr0Yenw6SE$sNjG9bB-QE8+~)n)5Ce)HFYM9-VU(+;UAIA&Krov+!Uq*w0TJgp zg&?WDm3M;F-pnP?$9CwtnM&Wjtq}pUF-7J7G0GCwz#A*hFc?v}5qNcBhmSr{uHT zdt{?qTl?Xq48(SRPG57-^BT}nslor1Qv}2Y=^aVm@T=MAKN2 zp1zCmzzwz-L_$0S=xWm^?NCaGSgL*cI%7bpW8@3&>&%~}WkV>r!>?@iPcDBcP08y3 z>Re#4K;!JA@o4(=U3qRA8!!pD-32J&9*=U+XYrdB4?Qg?nCvcOWUEXvSpq2=CFmNJ zu5BN`M7QyD|B-_OG}pB5{U%lok&^QFwOdOD7xfkftG)@o*}uQ|v|q_5-k!HjmE7cn z?Xv~n9;rU4kWq-k5*bWyC3)!Vy?Y2`$I?H^&s_VR-2QY6(Yt`;#tG2eUou)Fx^h3l7|C=|>4`;D(Z z%q-~e5xrb3rkFY`o^)|cx?Nsn3`$E1z}sB6hA&>TgB&d{*x!YmAuf6d#Pi;d2T6UY zizOe18-%dZld4*O;;DhDFFolCB&OtB2kb$IFDFhZeGx)`fLxd$CA9hK-bB)ZX2=rx z=m5R7Qwy8K`qg(O@s3AUo=hNl*a9{aLF78rT_<`a+|!#&ZckqYIfuT5uN)0uh;DS+ z`Qky(i*hg6l9ML8Hvr+{-JCUd^A+VRgl3|Lds;;oL#OA>TDCthlE>tbO30!V=>;@2 zQdydi=fyN!@Xi@}aY(^=p8lZjGS*ezb_#H_XX9auce;Yysm4Q0f`bM*%Vw%)=#IWU zV!YtOpA(g)`YyYzI^l0w*u#IGB`q|GwQtNAMkF*MC$zC^rn3TQqRFXUHZ$$8|O zB>VVE*?%tP9=%?nq5~n0g|f`XkFVu+?m`fVwI) z{T!Oq#P@t5DPk(70uDJN4Ir^=!W01tRHCwOT*qL~k^dk{oZnAUfA7aNVp}2s)@$OY zcoZ9&y8s?|HF2VkiKdw|mXmwoDh;XhxztvHk5*a;yoR5v&wJ4W>ObPY!2z|gUMhwsvzTj<5c3`ZRMK}2vy$1 zT=TTF?Iyi0AMA^=yj*R&SE{(bOQN5TRYy5=Lq2v|2<$mV43)r$X5_vC)o;@nl!dd| zdEDmrQM+eN{MWtra*=(x7`Fobu+Qp~JL~)P9K|wug}B(&aM`SKzlreP3c>o(ZuDk8 z5Ufo8`SPp-MDW6V%Ln-LOk?9&7>r)1UR{y6@r7ko?AN|@WJfp}B4X!F9r&7$t*-fy zw)3~A1rU2~PP#}{83Cv9ej52Ctbo4`HOtw?R_G>=rhA|b1Yu<5+dy-D8Z?eo%__Oe z1W>%?`W(qtU|_=(`h3!kZT)t7;(FY<1K-m>tXwGsGV&>^cL{j3L7h0MMYlnye`H+s z@hYyP8y8``tCIU{ScebMKtUcR%Ni~OWh;f_pb3NG@`x+v6zn|W@-$Gk*WDyZM zTr@3udr;~L?9W9nYpoXBI>rsmFhZ$39#A54XZgCb#Gda~|8grW_KML~w@cHqWJ5nq z@~D#s_T^s7hd;lO3-+i5w@ce3&8tmY=E3-@la(wJAG^1sFYnb|75(*RO?yt%UF4u> zdBoFiq^Hodl2}t^Quig0>g08!DjVZUra09tFa`Y71B#=W0_me&C^Q;7RoX>Kbcx4E zu{=Ic!&VLaSkhghsb3D>XXg@GKEKb;DpFldIw0I5pXU)1+}micRo1n}De_m%Drz?z zWxRjmO(79$wRGC~-Z8`zp`Y&#xL021y&SS#zMwW`XxxhL_EVSt#na*Mr^wMF5!7#% zv_{PiBSI%uwSGPdEPK#_7ls?8?V8$}oQCchoVJ=pzr5Z2Wm~#z?6J9fX!1(%n(5Aq zSVg_66q!19>e=SF5q_rJocAiZ15+;8NEnN7Z)ZSGV4|5#ieU+5mBw%;&@8OP3%)>a^LV^ZNTbNck9S^PhH>Hl_t z9^I#!O?e-7equw)rax}~SO4TM9v81jmA2pXYZ2~=E|Uy7lOO(y-%-Ak&Z{-%Ln+#> zfxZRC-IqB&7phLIq#V*+H(Puv)bNQZWU4JM4~;MV`72*Ci)hCK731_r)$P}CV{X<( zssCS>BNrF{wBB|5*;}bcxX`i}Si)x{m0!W%Q8G-#MTx$j!3v{k|pD z3#OGyJ}e%Enf%p(p7rDGXcH-3E89{X5y+%rU@_Ss+m*RTAS z*7-TkA_VZTqBNDh8N7FXm20v z$1kN^(EGY%ZTM0v{87Jw>(Q%g*h8LvDX_y!qt6EzV!KK#!7}Iy0}dYg#%3 z$Q1WCm`7$+>U5cY;*FQusIJQ9U2LK$UY-#!@3P9|9hxS?J+0H)xVZm_R-w<4s>_9z zEgrs41IX#Ml(!09vVJbO1Ill9sn!Vc&4vGi?}3V#6AJAMkG_A+X%Rn$LFg-VKObk9 z6!HD7EeZb7G4lpYUC3N7_Y7a0riz`?g$y?TxNeWgB1(di8uNZvXT7zVNNspba{B7Z zOqD8ODMl}Pm!5vt0rt)i@MNBqy#`jK7sS7g+06nYh!le8EW*Ijq#6iqF_CkRyHCos zltc(ReN{4%dSk7w{+vYvT0UJkS>u7HrQ2}6D5HX|>#|Ek-(;s*XYk8+j z!GP?{42;%wpPddN1=9`L+mVsn29h&OEfRP@`95$gf^$G^=Nz!wxLaMgo%XT`D8Dug z>@|K!=3r(b#r*`hDcr7R2bhG)SCpnAXzNK2GdJk0$^F6t+4)aWWj)dqQl0`C>1zLe zulAJkp1VK3wzzL(*A~ZKF1*coZ(tYort{)e8&YZGc#*@?I-2V&+=cH8r}GeJxFImT zdKOu{^2KD@O2OZ%Z{^6bQ6uXV*nU0sokqT>XbOAronQ9%r}v*8_1GB?qt;{$bc#a# zfEQiiV<@e|{#=1*sx?9&m6@xtUifKby&SJ_@#1bZ9wD2)*Vp~7u-mKD7_n+HYlk{j z%mG>u>n0Z}PZ#lQB4o*VM4(^?O^a(_|Nq+2ZO<)CqzgZh*Ef9GUG2K(OS|M~E;oDh z@)OB>8CQF{csJzeXETfXQHkRID8wWsQ|Q>a2I(b_pC5~&I($6^lN$fz)%^LiQk^{N zyrel_|0b=heSxFLwjXYLk!qQ}h!hMt;1c{4_+Ns6g>c4$fdGzu3#J?xpje)TUg;$A=?wu6 zcmTM254wPwR)YxWpktS_i43l|01ztt9p4iK9&rXRHXa0Vx+S9_y{bTWZ>^pzq zdyjTCNun#~>%hp&?&Ob)r4H4+Pxo(YTll-^Xd@?g2d~5}znsGlq3QJ=7ze353dZ01 z4gkGX1N5Y3((^$ZvE8Ww_=sua#FDRr3{DrAcKZQ~RG)yBHCzmVNI|;$l7AMuDWAoV zaNUjIjF+5wi|Q`>Wy291l@5PRoHd%nSJQPr$qSY*{#)V6yNt^(k2^iplKEoNClJ=gj=i zlEGQ?KyG~IG6dXVVz%bO=g)Yh-F%IJ?-@;Gle%H+FwrV)va6UGA;oULwC&$doFP6jN(S?mW*Zj8d zVonVOIRtT>@8tT#8Oex)*J;UcQryqm1>N|GyMcoy`$|9s+38*B-7rDyvFLeNgn@e& zYUTsh%lgQpp@@EH#8FzWjTCGj^(or-sYJuyThgyH4FM04a-PmOIkSRt-+TA-&cnKN2RpywUikA;sO_c9in}%gX4WQi`VgknTw%K zLWX6)x}(T=p+DsI0_6KoVZZ0+$Zx*h4R(7X(Xij9(`=c_9@5e?cfE~kH`S*) z$@c|Z6{20zKI-qw1dVsNL9z=VW0nhxaQ)gAIgriR6)IW-^A_E312QK|$OYf120h+! z&|xc%E#HmFnSm3IagR>-`jtk6usY;H!bn=wYb8}Og8$yYmAL1z-Ib>g3%k$w0YqAa zS_${aX@c)Y)}rk4318-m~IN;D)8%xe&;FlyBb^Vc6N@omS_J z|v{ln(V!t8G@;M2z&-h7MOQ+FbWj)*!++((q+%x?; ze<8!dmh91Yfn-!uEbht~)NihAF4X*hjw3M_4iI!)HQX(<*&Y>YR|s#GaS ztu03+4g!_ieIn+7Zf-@}Jh*#C>&FH&S=IAKc~LMNb&K;5GK?43eokoQb>;Us*7^U) zd&{t@)^~4IdQt+?ASH@A=|-dxR9c)9kPc~3LKKt^Q6wxHNs;al6iERE2|*gA7L9c0 zxrb}5{omL1zI&hLIv>xMbqNb}jxnC`Joo*pn|sJw7DWuobKZ*vi-Kz`&L62Nr=_k; zKV%DL5Bw;olQDMLBuNWn2NHwF9HP5j>x~7~yK{wub~)+Mt;2njZr8uNxf;E8h3JHl z#?CWl9p6x=q6Q`S``3;xms8$KY|E zY`T*zMU(AbC)WqBHopMs4%lhP0ChLE0cJCoug=tn@II^0{z_3jeh)8+DB+S&e|(4? zhO#zTK7*{uvXF16HfRF@af5WmME-P+K7w0+n^7xq8z2gl0XoESC zzRD1`qu(XH;62x%PF~4{F%#n z4M}FR&nwe$2d9h0=xNzM){^pIV;xua-D^L?m?O==%Kw_A-0(0R3+l|@(rZ6Mc#NhiK_h?t=3~ZyLIC5 zl)Ez965z*S)1fksDR;lS^)=SgPbamQVd~DfyTLg~g#P0E{aQ+xip@aNh7*`Mnyv;m zNEEE6XPv&>cp=K-)qs=MT@Ti73XS<0*d+TMO4@LnKT%xJ5)7YTgy$7HR^s^fyO_@k zNs@)H_<>P7@7`rm;dVSfrCxQPgd>ib`Dxw3?AG}=<-O_^;n}w@{w%$otJ6Gg;4+K1fGf zssmAixUNUHPXxFy7JfR`@GbL4Bku1_@uSXGeu zh@U|7$l>N&2~Ed?6a_k*`%Gg|4vi_GNZ{LKL=91IbBuP#@RWQJa`xUeJTFIg_U0jF zYO34MK~b$US*gbuoAp$3RFa;tOXHkoI$#YK7Trv$X5CZPd#GZDu}qKC%L)sz4NSK| zs*l)~Lj3(K+*Yy7E;0AzQN0g&ofJfrZ&GmkfnrV^x&x=DIos1tY8=_}7vxWo7{C?% z6pBw2^oXIT(vtWN)g|!U-6u02Gv<-ogt|45JHO)8I`Fe^r6PTZ1Dw<9Y4)PXpHiJj zyRF_IY)ToKD#4!xvUPEt!_?<|9H;cXpN66>)<-UgP1QhhtHt&skIE?&XV>NQ6SQ7l zxN5U;7KtHDDV*)%L$$#w`U7@N4iRj2qdo+i5q3?OL6tndg7`s0@gx4_H2OwwwNosb zDSIFXmP#}@)U1TMr4@f>+a%;D3{`aEBj;;99>9@5T`-UR78C9IDZ)}KB|;0yGDt8E zPZ7vZf@Yq?k~d3Y_&4(Tf9rVukMAXW z<0DAB&{$C^mT(&OlKhqP93>0MiiD?r04cU2n*G$W!NS&qFjGh`vPo`nVbwO#dns!?IiOS2lsxO;&ePWH zYf32Ejq2Z-KfK!X;8&m2#J>EUq9$^nt^H?Qw1;uD=IYzX8h+6Mu{xgW7l;D7VcFJb z-5!bQ;`j+y<&HMTj`wip5n184X4M-Bahsc zrD`-IcNOrz+PzOdWc7V@o=XkWqnaM9lB&@O@tpuO~ zce6YVGK(C<#3)VaBKCPEkwk4H0y3ASq zT4QLFB;3BzCE;?|-_BqhXi?wSJ@sHk@jUJK6H(wgq_wdS>Q^zNJ+HNvam$M7v^ zQ;e?8((Hvn$QdEpSuDJ6IE|HvS}eulFQ+9gqGG82e`TNK1o2K(RF;kAW; z1tE<46~EF2DO%}6Xa*ZV8%O6ekmRTV?TLWX%RLdN;{H|8K%i84iY^sJD}v@l0c?d9 zq9Nuu#g@@V7db(CM*j9n!)w~*>Pd8}yGbIujUv0@jkxAj8nvMt^dvRu zhZ6Eth|ptzv>fC>k{X&rJQCM`e7tiDC9Zun2mNcyHWtS|wojv?e0_pZ_FP@r%R>`r znXJ)9Ug!HLX#XhYJy@#Wxmx#OVSZL{Nm0QeYtSfe@dIudQZR^#8b$vGYN-{ByYJ$K z9RdNZ>k}#HBr2O}r8Dh<@}W%;H3T`dQjYX%$8^88S&w&Tb9KJ@8crF&&T8SC+h4tM zUnvZyj7*B<;@w=@PiX&D(O;V?;n~h?%Wi?6(??j2_|@(&omPkSk>Pd^rU!J&i}=gF zW(K}QtSYP^!fII;xuRnL-zV8eqXNx7ErrU zP?((?BF>qO)11#=sG=V<)sN~!8&qfasT<|L?<~TIh0RZa?HG05N!Q`f{HQ>{$1Oi; zy++ltIycEf`;2_z5KX2duu)~abG!e?q4z%{{C&9Iy>^y`{zd;1t&SeYn%zL~Y(?gBh>9rYvhp*fOPgbPuyxLo$EfGO?w6dY%Mx zT5Ik0a!Bu@{XfAy{tIj@!6M~&G$mh{O>=N7l(Oe*)qeXM|PnI4BrD8^@ZIa=3y1z8V#U$IEXT~ z+*4ZT1ze;oHTcCYD{!;?-N77W-#|*jUQcRi2ENDH@atgex0spF8?TN!lNch?T- zF+e)Q4*2Uia_zw?(9w3?fTFlrDai&POrCdhcMM^GU(QQq+P-gkva$?XNns#c!J+JW z07>e2J@#t`*?P_E=3edlmMR|A<00Hl1E}^eR%yvQ;8q_sN3fqCYHK{_f43 zLV2q4VGE-Blz1$kV#{uQC?)e3)5t->Gm__^w~(j#M0X?i=RwDa&S5pi`az(d4dxiM z(l6>kL3CsNE+X~wNP>7py}I)srxSz0>XzA7m)obrVj`SR2W^Rr#^kadM-dKhvseg_)jB*Pgl z7S*ZA;ReW92!=s791!^^5y~Wr7XR>u;4E=uV#%%S;%gJZKC!P@zZoWQ^SbB z(pBcMB!H$ReOwkVc$b1|>23X?(=9)=lpd5pemoMI;2cNM>L#2NVknj!nvhUrUuyp}3O=3yjZo;F8lGB%|t`7@IE&g_?`tsgJu zh<+7jvd^E6#8~>ZoZJbMe|NOqEIWP^jm`zwc&Fs!G})#Uz=ae1d($1r7@Z(^C&V?3 zL5ZpeK?SSUE0uqKE^?jZ4ws{O{=yf48B##r6`Oh1Pdrm*2kxQOtuuT2=OeO=cM+%l zjko>gPgLj!0Bo9&!hew|h3!@@dxMdlN1!oy-nMmE1TE#jmIAJp2b&x2&A=>U&y~jQ z`y`?1v7i(B2}7Yv;435S+YtTpUQMM*M~7QA4d7LNdN=LM0eD~P;bf)Dpc>{D{n88j z^V4t-I9<#j7S*yhJ~06XFpj|#EfNTWxnUYRXcxJ0VRqz%Q0|i^XJiB~)We>~LGG>R z6)x8a!4@>jKM+CZ!E_Lvejse0P@A_2XjmQy0w+oexJsB{s(H~1525;8h3`9HCJ z-+a)9C;;ywIFllXLtNLs0Zte_-_9a;hGGh0A%vO@Y&H?(Tjvq? zy1se_xLbv{YKS-#^JDjw-QN2gt|jfffaW3(2;&?#ZQZ{s!GE$VzvL>c#U=fN&{HVp zh2K}Qr-?9q&6fL|bG|BH(0Ld@aLkI^WQ9nZLINK7sjDQx_S!?z(n->k8vHMtR zB+IHe1bY_L3U&hGQ6T`0z;Lzjqo}%ajO3@|+HEF89gH;UJ%I?$2Wm}WXVWu;xe?2H z*-W*ji=cp^*H@CN1~N$cr1$oi--D>>eg-u)H<9q@(SArw#W;DK{ZoR`sYL)Bi_jms zhxZrCj`mm!TD{sw2={8MzrFt2w*!lL0TpLD*o`4sIXVko`~~?VK%rag6*_pO6{UU$&2V!Q$%m1p_>l<_LRAVEKWVfj(@*gAb4$cdR%WQIO zu;#$IbVxMr6G?;5WBH*yP0kHJ4r|R3{agC5Ocor%e(leGPV}_oHe_1q{)&#G^%h{T zbnS=ppaD7fiK39$$cK$EfA#6m7laJTuNV&*UTb0fBHSS*C~+5@@c zg&~P0jamC{Kod2}7w-hvf^Mw_dWs7I645vb7$(j;U`F^RqS_B{KJGk!uUNlnfSel% zPgZVSvSqzHez&&8s4(`}Us5s=F+UtHIx>*$)Qr;Z$=uxjqw{t;L4C2&blwZa9ryJP zXXb&(5(-hr^Y}=H?ggI8Kc1h-3r}V=bMc?VzX?&g+FdSl2zPUepc8AD8YSc`G9%QGdq$6j_)v({aRI2Vb6 zz(==#hl5>7w;|%BR?n{iPOz~$R(-ww=J^d0Z1D)jiPIhMrwB>P@KXsN_X3AtyQbHD zw)w)XgaQ$I$6^t>BYK|Cl`>Ll%!emidhL*F|I-mupiFZpBX#s^ZKkoj_*?I?H1c1m zi+>mKZeRAHqb04R;+YscGt*qjq4z1wEBDF#+Y_fu5>@fz+Rrr4n*EL%i(K2+4j)5c zD&We*6SHXV8cZB~%{Ej%jqJHqp({y*Aj2l?XcS~~`E&du*ZutDKamYvet;R#;Q=p! z1!T&HWD|);l`ki*1QccoDU=1$uv!RgA;V=5f>uShA=%7(EJ+R-N8~bA1c~hg*@fUT zsp)c)2>9#3gB0zu!H2h43|-qm%MSWyvT7gg)3~CzK(7X+Lmjp z*`RBu++)DJOP#|ymO?)#x%mWjk;)~-cU)UTj$Qx0V>4zv7#b64mEm92oyuqcw#&|7h#iEqBo;~J6{I( z!jzS@0B>a1AmsAqsKSg!o-O@DyzBr3=2!rXw#Z!Z{;L)SjK>Tx{IO2P_rL#%rVi3? z15G)h0&^rzDv|`A>*96H(H6 zSQ(4lI@Be2x$&ypI-~GwcAovaIl@XQ`Q!DD>vh^SDSUfoWqw+K**_)oa`P5QhGA(d z{raWnm=$tASDzN&49d2`MC3&@J$TXLj9(B146ndamD}~80?FoLD4T*H)SS@Y923gj zi{c4qla<-T&MxtRKcUF~cF|6b4 zU}FHqxay%;_=2r6Gw-NjZjE7B$HT9w>*)NUiQA5aOUQ53qRDbBBm&FjGK3@AwElk8 zW#9GqX+PQxX0kuaK8v|$gx{}1T!g)Mz?bo>OOf*;r5t5CTq#AQNtNmu$$ejk?#0l; z`;gy@*Ye!Z-DGE3??{HUy=Y7@IrAxo{vg%vRp1GFbb3dBmB-pPCxzRFB1K7S7$v%{ zXx9#s7f{G4LdF2KhUt#Z0)<6`A>jW)5wXRzWim_J+Qr>-fs z`vQ&dSWRZq@5d^ehHc$6`oKRw$v%7~jaERe*GBWz#lK~9|E~-5zqeklFKSmV9-a5R za7%gH^jk+|1J@<7yW<6BH8?-v=*iIyo1OS78w^_sS(4Y9>a7n_deuW!evX4QF$M&g zgT2tH3Lun>ZS=7rfC5yiFAdCDolI~icoOn%7a@NU=NtVDDuknd;wv~kW%T_3eKdBlfJ3kIQmA8cFK z{&&gpM?>cEVgyrGexN!y=Lxm28O-z=18h579DVg#+g!BCA^p1rFkn?cYcy?zjxYi* zLLu}ygq|+LzaX`Ls3|kmpo@WCt6qVWmxd0oJ3BTjh$5Jf)GxEc{&cHI{&Ss%T}_^- zZ)*r5;$hPGFgYX?`ALG%-*i|95j*5u&go23ZSAZyTI+n*Beg=Au`eR*DV(D}@ZV*e z{=piPMcrEqH2qQPew9YPhjYN3(jm${JxAC*WJm$(CI$SA41`inxyrq7Z;uoL9UKI3 zRr^mvM3N<<<;Ugo#g6>W$T07pjP^f4$!w0{4sa+-wL|9CRD4A+B3i=hzkcs;+ksU^ zEeLuT#YZ5Xt`h)2p|_w1Jmn@8{0Hm$tRFEya@NknX_HdzXgf^eIeZ^L=(jpIv6neztUDbG8b5lj){1X#E>+}LEGjVS@vr0vFZciL}NnSaUW z{3@^b*7gy8&=3Ao`<%lx03xpZuCM$fjz0uUb$W{0`s|pkEW7^8L_h>W!FW8)?BLh` z{oVYhFS2XIvAP1@z4EZP&qfYUJoJ*_CH$-$7Ee{ZH}-b9o4@9As19%ZL#076((i}g zPEnqmFB#r9%hKSTW<3{y`4hmZ#MB-eFuXr5?eNdn!GFYpF>Cm!Kt_`Iwf3CLe_jF5 zPI0|A&7!gYGs^nU-X@z0T+n|nRyue5{XqZO@BQb){rymwh@n@dN+SJtV$Aflf2Ugi&yBS^4a|kICtvQrS%v?(LnI=G zepcl7`i6!7-Ie)WP#Q%aW*(3@jki=G}vR{ zP9u?iuo+5srl6Mb&kZ8;A#B=q$(4_Ory%&x70dPD!(jSI#2h?Dhs=U^iI{#!B)h+? z*bn<_J;bp+y*LbjIum=V?e?F-<$Q!=jm(|@ozFjJD$@&xPz%xPjR8$_90urqax?`U8#!6=FEv{X&z3*Ml%yZxvh##24>O2h zy!{QQ7-o>1MpUIM63EOm|LGL~9>@_$#0F|&2{0ozKtHGJR1Mv>Ffzf@41yMjk!QR1 zg;)b|QzEu%kj~*D#3U)}dun*xeoZ``VAWj)$!Xv-&dU!WQ6xi5=VLd#Qr@$``b<7f5Z62Q&Zz8nR*M_~F0^gO5unE% z7{Pit<`f`c>X+awz=CHJfVPK-w1_gh=)6`EE}5My2&%?K^$do70?iQvf_rz60*B;3 z?~4g`>IcZ$(5V{A<0cg^|^sMb7BEb%e$m+bDF7uaTDooz@*bNfYTM#h`E)?(m!VLw8U}ugG(0CL48*IRYbRp>y-}^ zx~oQuVdJtR+r0gk82tDzkQnX~3nFCaZsaTbrd{MR2%=iOvCTEzLxd(GVs&SyXPt0E zdlg5N0*(?4=!%q#h7ZaGNirRSEM9Wp<&R4(K~(QA&$D2mTFPAn0<_$A#`X3bg+iPh z5zLQEkCaF)eoecaqBKzoB2n~7P&=*&E|wxdFVax12p;snfDzfw2{aBD+d~2Sko5vH zjh@@BE>OBN-+DLuW*O#}GCA_ASPLmc$*sRizU`-mYMp@sEg!=^FC2zk_U z(%vfu2_A5MDijdUC~?qhaGOAlcz26mOJ~q3zh}K28rA=IqBtp;9<5#j2nr zUs-`10PP91yP?I&i`b8=csI`rltb*Jaw~G!7$@!Yd1uQty$dOulNkG4>*@fc6Ke(C zg|ia0*@u_eedlij#UJ`!(4oJuVgaEVK>JMtc`LdiueBU%?1f(0Q!xJkS%4a35426I zdABagrby%B8lF9Q9l)J&Q*U&wsBPD2ACR47dxn2omwqvnNdf!pSJGu^<)BswoT?fv zLL?4jAU6o*NEg8yVHtK0>nQk@i2z~6D*V%nJ7manJvs)t-L7dSLDL1S=IDK2T*s1 zjsy+RLk2W$1r;t5CsPkZL!#FOnW^`_jw=I4Fb^%T=HTaTKW}BbNG#ptMG*7OUUW)J zUuGO3$6R{==ICl#T*x8UB%U4Mk_D7SofYsfC zavcdx@-;!mZIIYT(Cb5XPGRKtG4mb)f0{$7pc4L z@`pk^5u(%abrXSjHxefW(n3^I>`pJiNW$FRx+;;)XOlPH0RA+F1TaqXR7=cL?6r-q zeJjQrX8dB@tvvH&{>8jVP5LoLKM7n-{7*4agz>^h;L@W6>)U&YM^y&ToXp)4U~u4` z6C89+%QQoE#6$_1&fiDc(=`Ku z2a@oblswthgM!uOCDI)JW&Znz1#EH=sa9+V&S!kS%+xwxU0k^VzfM{f&Vbi9!V8J; zTo_AL&yeBDl1*726AO5_Mnp$_|CDbT5SD>ZHJ)F@3y2(u0A@t|cxn1BC2gsSEm@%@ zyKunWEr_`Xs-vzRKN^V}TJBV&Xq0aqKy#4wTe2|(ei@yhVK8T`$6~5Z$u%BZ+E>0p z$VvD}_*1l&8cEZa_uhj&lwx z%^>IWlV*)iA$1))KVb(8$NNO=HKwjbK|!d899Ko=I(I20KFBU?w8+nbQm*O1nhl9>Z#MdToT+2vt#%UiuDP6)*%@^1s9ZeIu~m03yv3-G zCAc_{B`=BRJlC~5@2>2Ycjrg9{cLr%27bF!@+zHK0T}f72`Ny1*SrFKr(xW71BjFj zo#K(y7^y9ylTLDm;ZK>TV~*i2WkHlskxkFb(hkwe3|tPKiq#AC8x3xsys1}Dp_I#B z!OmVbYIO^$E4|1d*S2CqT~AggGQ%4D8HR63j-op!v*sRfy*FaxPOeSht-W_TDIN29 zeD4{h?i~G!(Z{XxBOZZoh{dGA=vTxaKr+I)P9CFiMhmTKiD$lEw0-g>OW+gK_9|mE zdCpm*>OPNGPj&1t`=>#Bo0;GSuFYVC&?cy%?-H6#?4%RVHcxN5XOxnih7@ZH4T5ag zN|aA}leI|ml}5g53&b6B39p)Zjd?`L^N8|(>n8c?bgNJJy}^R@51J!<>aFdXXRi4> zV)Q2VinV-0y-$s7;Wu1wY+sOcS91@2It<*?%e6oDsS_touClc4UZ4w?72V~Ajp_D6 z0pbT-KIrhWLkO*XzlVsTths@%G2)O#TO|q*jW@-)5AlW$J z!mK~>a!zNT-$2Ryl)2>OLgdJC=m;f+B{o3p5JoG6D!_bWxT$)E6c?NihIz@T)9J?stMmNJHlU!`iq7BS1+sk+iUY!Im9N`} z6D37j6D5Uujak1~{rW9#vzb8${4c1bE>t0+;lJp4`8bovxlNpYB89t+gEy>SVbhl( zF^49;{hnqvTAAU=(&l~?`p1cC)q{`w9x)n9Z@+DQs`ma!b@>l;uC^E7&~}~Qw}RB8 z1oDXVo$VCd-OOM8gL?QDA`+_VAS5pl*76JU$lSMb=i#2PfVG*6?9%hGt~LLBX+pIq zAQ$UbM0V>Z2r0;HwM1vY%Rx%!Ed%wmc}ysY*+7%8S+=x5ZCvtYZwn)QXNFI$$7a8| zt5F6XqriE!uYB%_7nArcL$b9$YK&(*vWMldIr~kcw+QK|KVA)cN^N%b4Q)0?UT+$R zmr%YS!V}l?LQOTiPWP&*CTT{i^67(6Lnwzl*fms5fsiDRMRErGnLZC5Voc|F?^jWaDv@1N?)HVk5j$l zhi>EJNyKhTKLUE^)}SqvN%~q{nL*~Y$TLU!XJ)RrG3p-1^`Poen^&|%TDb!D8#aPYQW_IVjaesVS85I4;0_5Isog{&sa5zx;G1QUzI zH-tAg{0_9v6nPAXHv5iq8p#RTXjG}z$|!J5Pt1hsZ(vX=c!|UjR7_@1SC+>bNLl&k zQ>iwQM%XpNLyqBQf1#PP{vlhoNvCoItC0Xhq^xX;u)=Ljk@-lL`K9FZSc{e<*&rwP z4|<%(z{V-S{mm-+YS9GyX+>4Mx^9{4lXK9PhGMl53cfbkmav7t=;MjXwfL#FngR!d z+2Nv-(-HQsuV-jX)~nlo_$e^I?B0-sX zm?d$ovvm4|+I-gH^c8*0L$N0xtXHSk{(S7SYf+S*SOfiX$cv-ZX*>xmB?K!W4uUly=iliW&zhBgd*E4Ga z-ZF9o3f$m;V1|NzpY$3p(3=J$-nLu-`HF6r!}pun?wxz5ZGwQ;Oo)U~*}ZGn@}Gmm zF~S5W7pJs2{D9|Bls7toXFeEFJVC_fX{0AvsqOZ?kvI%x5Uu%5qRSbR&@SuEx{!6| zIV=k?FM_<13@vCAX(?dXN|vJ=82B@eV$JrES>?I}7uCwkCD9F^yed z3W+GL5$4rI)d{jcs$49j16wnTuVqS}oJW`EDd2rnbp|n7(1c_LWB@R{G|DVCNU_MA z6(KC+2M@cTz}1;BN_w0#ga_6{Q`avLTqfLc{h2Xm5lKLrJ^s;j^&650x?VWyCDi6q zgdS=&DSy*(U8^*8>-zn?{=16OO>s<=AXWdO5bmn5NSfq=v=LBG;4C=O*919$PRyS!0NfN2 z;8M~PheRhtM9*0Q+GSd2Va+ZUU_$JY9#ww~lbJq=X0Avux(kpVY8XTuVWG9m zJ)e+{a~T-ihnx{oLgJKhohNw7PjuvGa78f3T~%uC0&LF-V5w#_1Lnv0a5Z2EMT2l$ zf1m~EvPOtj3azhO)Thnh0IAoFR*&)8vj*$Rl--{0I$$_B*{?ndCowX-hdJ3Qw)q%m z6@yCizj~kIHHp=LN6wzahqHQzkcP}(5x1Urj^-P8g`Bho&!kj_J$qYx&4byE{aGo^ zg7hu=?&migeZmWG!L5S)!>o?_X$_KQ9VJe$2-@t^u{DVzn&lBMWjhw!6T|(SHUR2r zSsz>7I?IALGPX`+Z4Cp{d?X->)MNawfZAhRO5$Im>)Ct|U=;Sf29 zlu6=yV3vx1kZ|Oie1G@2X3v){slaYRaweL+^mT(Q&s}iWepIo>@J%2x<{-u67f$nz zfB5$R8~aTqEL;7hffkaT=28f$Zw6r3WqB7+K2|U6JcmmB%y{u z%t3D(s0{4Hu^TRYI&L8>+wlA*ytO_D;LL0cX#0k$um?8SfRR=tjPgv~C1~B;4@Z|O zoJ5b7jgu8vv1&-p#~XcPQQaE_Ptw;C@+hNf@Mf8=tkKY66S@%?7E=XyG?50OHdBB`(_&ncbtgEeppKZKS_1}Ud6 zh@extX5yDWXy<+{P)UlmjWu8E-MZr~!tQm1u>gi1^?rIrrwb(XK3s(jq`&E6z(@nHd( zDzI?05ET6iGzR`H2(iylVpQ{>B=Kv}#P7(5I0zRGu56_QP?y2T?OP~712vz}ez2xo zf}GR(3)2ZNhB`!q1L7}34t0{%)+;-zoZMoS7_dxN0BqcHQk<48v%ax*3FgY-E7)Ld z$?IMhA6S}-HvJ0zxIw(yxvYZsskIFgM9l0^D4!57zd1n3M%`VeBpLx*()(fktdH^l znrxY$3EyYTaDbM}b$9<%^w(A?AY=aIQt*!}h5PM)tk3W?lWm z4O@W=_8Hc=>$NZh$xn(`wWw$$ zlw;-mh@xnoeq^tK!PfeNUPITm3dvokEN%V6UE+ZZbSjv9u!pT>n+Z-Ac?l}e`hs4> zyY8M-C(7>wfjGV}L6`QGPPg z`9)U$v;WK~B!jE$S6-1>9-_lW%LiIANU6;{X^}m@-f(Oh0d&6H5}=GCG3I&Db@glz zq*4U7zq&|7_)(}Lu8@4~X3lY{&I`cS*8eIVv;`mC|9mEz4C+BsvRJLM&;zIvKd6vA z61w~4YJUE2sbuueiHziyI2sL3%nRKg=G7}(o|$hs_(Mf@lU z@ovKwXZ!5=60`qR%Zu+nbH!g`t~bZOhcxEgcFygn(o#rqMSp7neV}rbS6umtnUb+9y6#bMhDYjfRt;` zyIT|Whu7r%B&pa9ePH%#6Z$p&Qw@o+z(Oc|nq?@H)FC`eABo~Imk8~sgx?VcV~@`X z&vc3g>)H{ZA`2nzr%48tWZ=1U;yxFHx=l>SgKRgkQstvZowV{iyAFY4NQSv=>#PAH z{a*R&?Cbh(f};&vB>kbejWu&+@8;CBNYepGG6*xIh9*m5A%9@YgA1+&~67S!Nc zj{F(?#$#=Xn9Fr>dj(KV!obDv@0-!3{9ksdf*=ouyIsTNnT$m_FIYvKD-l{|<>Dxi zq2be2x&_A0M(c{i)N2hW&x|6^!7U}a8>b2TvYJ{%{!g0xpGbKHrim#-IrfzZgzDMI+^3W+3SD8y?S$!f*ym}awxRyw zZC7mM!@YuWO{E$%KemW)%C|1~>j$&mw@FUL!+S5oC2nXxK2G0!H3of8>Mjb8yS;6&pOBOkW_;KJ2{x!B7-2OW2Z9bq1<6 z12SN6tp@HwFWdZ-Rkpg;t=VP$vb#o*X|-xrwz8<|Up_**YbAl5)>t9m*f3noR zh5Z$EO}O2qlEtSb{y=;>H?jo=mqp-{P9G{=DF#W-xFlBUmyEoL~`CL{3aeYw7(K-P?&JO4GMaEpR-qu0MmX0PfO zTM693CS;i_S(v(&J6GG^Z@byor^TAFWe(z0ythrg?y{~wb#-n`zr3#TnATX^O)~sN z2Oii1sk6fd&TW&`4-wj(ew#oFXT{skPYCeBS%{QVWc7c~g6D#A> zB~&tzXwO~dFcRFn>GND|W09C+C2STKU9p+lFZ>j7bKV5T0I? z^tG>O>^ZeHs^h7vT#>~jq6#;VR5tld%nsT|rd>KR+Xi7v*-LfoI6o?DC5qW}CL8vA zRA{}v^F*Kr8O>to6uyIsp;}0-*H2k8t=Bkt(F{yXUge$HIU+y7szQuJ!jq*?kEXex zWfin?!2)GfWXCvWQQyB#Oe(rdho}KOXOSpFziJSbNovjVFmG}$c*E49#x-LbY1=`> zzZb#$*1>`qlH9ef`f%4!VGttO+|(OfOqJ0)&iLN7e)f6L0#uUkAr)V`oW<-BX!Bl1 zM_qIqE4bi9*lDAr)&{ zHfPs`0J`wO4mI1n`Ks_#Y%UA% z7rjwFcyYlW{(3oSl9vSydJ)X`uK#cU*#G(fI^78}t6dSJKi+%OlYY5=fhvH`xKcUobG%Nn~_l!h~-KE zoP(VJNIpM)Dr2I@1Aa zzB6nFeYFM#le&(PMo;Xj~8fE=%4IQ17K zREY1MHf1Ke5;sW;*J&P(z|#v?eI0}cUfl4W_NuS^G5qCb)R&u!YKcjkQ;8d{GSeQ5 zZPMEk1y#h9>~g-xaB#mx8J<== z{jV?M9^A@zX;y6i@)O{r*74vfyq%trJ^R;}@&ES)VY)?%Ae^(UCWkJd8H~TbFpB6| z-mSK9cY{pwyM@=L&gGwB8$da$MjPL^)h~A#;A7hb__ISA(Oqb4^)UCPcN4uG^QA;m zgS#O}^7$0>rR?p^S1D(%BE!%r*q^Qyya7hIm`27`Jwoo?1CQ^e6J)6!w5rb`Mp=3 zl-`-`T8H~1)D|mjU7HY1&C!_%qS^;SQPh8KD*yZil8Yd@w4G^VQ0{P^s~d#L-EpG! zUH$~5T`<#ne!cx(weTx&X{T>^i8@1zKRH$en$Ob9^%n14SmVWSYb5OrPp|Uv0rDin ztm)FcP%)azJ=c#`4^C!m<9L^OSqFG!%ainwH>M!I_8l3=6;3~`{Q3ZO^4K7D# z5P&Duq4ma(K!tQ$%kB+SOROJnc5rl54+{(1S&dn2y$j0Bt;w!^Xqjx~`rDGB3LyFu311)&eI9pWM)uRFXJ zU9;Z2;gW{ngjsNrt3t5sRRDdbjvvrOcBkIgcVMRNHa=X9&Onfh?|@2pV9TI17Gv@F z&XO!9Zy}>&!!HxiALs;u4Dk_Mh+wRsazKxadOWxu=y}fTB zAvXii{f+cV7WGRe*CrhyG|3h!OS>W1BIvSCQ9J>PyC#^u_Azu|MiT2@A4+@NrHhes$!yY)m<*v{4g zh{x2&ib^_^t!1w_T5~p0^ESEnV09ZN4@u3Zp3WX*PXzdMk#&>`iQNN2Nm`$M8k$l>o+7;?UHXYo%hQ#k_J z%J0ZhmkR(tKgBgAiS)c0u;p`f4^hP1uJ!izdP*vs zD^kZdL<0g77B*{gIBBx#tKx8S>@AYI#x@NClt`is^AS`}DJ}aG_OB2%7ZrT{R4$!a z7DIP|_eRdTAB8773+$&m45uXM4qm=R)m(aFszW7&HW}%?vrgS?P-rS&E!o6u7LWS6 zKTcnB<+kSp^F4{?^4-UlNR)nNto8oLPL*6g1er8Ua{$<*E~Ac|k! z62E|%w5N`ws-~rvuJS(^Xl=PSG<)adn(WbHSz8Me%_TeoV$rKDQx>ov-QsH!>QYYWY63tg=x(iU<(T^ zh>1`MR`TUhFe{Ssca6j;-ahFys|uoJba_OfwdXCFmB*TY)V+1dG1^&(+_H$1yG@LG zx)GJ@{o9pXayKs3_G1-QDx1g4{oqM38Wi_ubDjF~x#7k&EIL~iTaL^n+(~_*A(`dU zqcP1nOg$F8RlW6L$C>jBZNaND;A-Ch`y@pXq101|3RQATMHL`3+0H8{USn~v{uwO0 zZ)Uu+@c$6^o?%UH+Zw1MXcQGt0Tl^tiPA-y^e99WqzR!4p^B7%Nbkmmf)tkqkS<6I zC3K`CND-t+hX7HK-aCYL=cjn~-RrD#HtXCU*B?HX@a3CxjydW(-eI@1Vz+2@o6hk? z)+Xp_XnL#x3d!}4AE@KTN!!z;+fU+5i1$M8Jh*ulR1LY#<>d^0D$0arXfMv`Xlh7; zG{hpeWwomva4t@v2yyQE>cgq=GDJNVwseRTmIgEp=Mfs^&?hgbdZfka+ZOcuKpSuu=%7uvg z2+>+o#FJe)W2u{4V&&_~-pWIZOsM%d3ayvJV2=R(CuX3;ZTyhz+Ew>j$pQ5;eM<=n zJvu|cM@GFEYkG(9LFM}bFq&6rIIokK^I*}{%RyV{c|YwRYz;6K?Y3R7 zU6$Q8dHdXj%IDgKZsvw`(_pxuhaao4rv(I3@VrCU?!V{(a^C2vKiMyx`B<5p#_+MA zO+}JVHVO6#`B3oI_K@s0#};X4!>52rPFq%kPW0uh5+z4`IV{m@LL;WW_NyT(x0N;L z#Twju+8W)E9(P%vQfo*OPJg^gT1JwzRwK5MsjqoH)y80J3N>RF{r^Fhl(Dm(qmpiy zIJK_p+yks+mY{OVg-0MOhMfo={l~HIU{Uh)*)TuU!MZrVuYUAAx1YpAPL*g-&p;&% zCqEny`t$M&J|A!3a6I`j6!7l-pw9!<(6@Fc-$iznjEHbulkNf)n&TTdfz#6Nj_{Bd z2=&}B08n3S8?5$U^fREF;o?q5>ZFxadk$wWEaTef>izEdHJ6*Kw#AKa4++x@^CFs+y*g7hANa^h*?A zV_?ogZ$_LJrd@Y9S|ugn{G4D+CMdu6z(YFs(YQ2P22J_SRY z@yJ--N)I~90Edeq3LQCP7r4EFA=#i_Y8R*kw&oW?%cYQEHWqvon#j5Y&th1+yuaEV)x1mo3`6}8>V8a=`v&s)493nw z-%#4d_n1T$EBAXOE)n*lbX?i4*ElHoJ;S?<VnLL zr>0*R`S72R{))Q8=@&9A+G`*Q-bJn8kNfKsH^6y)u3j73ID_lw*4LKxz->fa zXwj$O{y!>pWh^Ki5j3&9qR;Utx@Rxuu4|h4bpfKWOoQ`rFo#G$+XMNC4XLMa+HC&& zbe~A5NX>r|4JycaI{oymbG|CwgBO1C(|Kov?!E_zkFwGZH!6I-*7beo^)y{4QnY|R zHO%YsQ@iakDX9nl9uK<(+$cBS3H$0Yb@lXQycRFdz>sIWl|JQ>_#;|wIJ`+jQ(1va z^iz!IK)wF=9G2{+9dQm3behK8XfFL&5eH_i4U5C|?R z6OYK}btv44NnT;Ze)L)M^{GpZKvoFhodeE_Sos>nk=VoNQFXm!Lnv3h?mf&V&#J(aBu*iE|wCLux^92Am_qxFil4b_w4y4a%$iXKg+5 zaX5lslgFStgBShm(^}w2Yw-4dFV)e062dKZZ&s>k@yrWT&sh&r!($BH8>>|0zDyxL ze5}{P>zG@zo8M{L02sFo3UJFS#jcsD>+)4bBlXKX-2~rel&<&(p1c`27BZ7-(A+t&)lRSOmop|QSFVGf|mnqcR>7%|=!v+Z~mFn78XPcC_v z+DrRiG6lbihc0%~6Z4C|^JhGtZ7AQKEKdYs$a_$El11ia!epQ>KA$Z>R;WVF$UoJp z&d$0Hc?RpF6TqcZ0Z>I(IH$k&AU*EWz(PpD4=)BB$zS2OwRSP;#cwuE@rQQ?iHA(I@-Ws|}m_$96-Wt|M^vM^Sa`2nM!z(1B3onPV6g z4e%gv)(BZ2ZwWAc%=trF!r0wuz7&)XQW~43>9R*sO^EsV<1fqs z!a;lHEb61o9F}IP#atbeDv8Qwf5Na;GYL_ugTjS}AEFlu4;(vnEfSJhPZMB|ksTSZ zOAH?~nGfF1G6Eh9eZSKceKa}-^6pDc7;17@r!MGHHViJF(V~-Thb=K;!?!Q14ec>u zSb;b>_F_&aOnx69dBVznf>xc&2!sX({T(a2B8)XW`FySeWT~Q7Nm|`pkGR#(Tzq6o z=jRvO1F#tpV6t|rwJCmT4YXm^*WL$%4H99aZwhw(-jdqctokZx<93`DrTq-BGVSf{ zxm6i-&kMnz@;1<68m?{FYy4P+_xXe}*z3Eg;!IHM6+;s8u*-T`n00b=B!8JI=*js5TsOi_;_NTH#>sqP@-W7Br^Fiqm45pW(!F|Ym2H;)RN0&g!@+Q=uN$#$d35oGI`k}B; zd}m62-{pMCsmv<(A5y)Oe>BYkOj=#)=`ug(A>GJhPyTl7QcxWQkfHSse z#yimuVd8m#1JTuEWeoK}g-g2F!tcEFs^?(>W+Nw|+`(`euZ?ReEZ`h0UXR&Xk6B-K zBW(Yrp4g}E0$5yLfpV4c<%xLd}7qS+7}-w)t8X z^weO~ZpyBOhXM^wu?;Y_q9!CM=#Cvb=9bCHaGiCqie>x0rPr`LWerewAA@12bB--n zaS=;oPfF#%ZEk#Ub*UyWqdFI^G2?Kb-Axd5!hU$vJPpMraK{^)H=<@eEqo1XOGyf{ zo$=+diMl24_NzyL%4Bpk zg6@Q$&j(hDYl6{%dQT|PpjST$f-2H{l~?1UP%7?OAUH>cv zrkxZeD>B4HC3iD?%%rsjX06PT08e z$!75h`pUTQ9-zTn0Uu#FKpy2z*L>}7)}&lymj~7zN=&!SMJEZxHjIQxAtkO-uy0d;bcs^{QIqI5DjCuWP6ph(xj z&aT6N5)$6c-y-aer0HbEwR=6mu&Xi9r^Zb*1LpQd2asn4N#7>8s3aDtB;kDUCRRSK|4&2r*&+-@L?+yVHm>Vedhp*h!z|2}oi$L^E*q+X8Ihjwla`U`%V(2aZW`u+A*81ijNbVDJ@vQz+^8+k;@LbZxuF~2XBq?gJr|pA--&QV`cIxCkzj}O z=_g+9)5c&haBps!t4P#GSmaX${h09?&&0SG8t=KsZV9=`b@cSzD}ZLgGm?3Wu8Wfw zA_b9hWHe466Tpkqx|nM}4q;|4*I{{Ayp|^aA)~|!9jWldhU1Mm2s=#{OH53k)WqHH z1=der&-M`lcC>zbp=Txa)8jqn(J`<$vL>h6h6#Y;WyIstffssRRB`NAb3vviZc;LI z`fHE3%tlXhqN~~l%g#K@qAztrQQd_hY~LCqd5EoR;m|3b0wL9(dG+2CAl^t?sGe8z zka9(DbLY?6TzS`BMi}VdS;Bda1~Jh$u+yHT&+RQP827a6CtjAhAh~f%;hQB$(3Cpc z(SI+5Z7JMKO2vQ-t=kv|lz_M@B}=~!o~oNh$P!1HKNi<_0+(Rqda$3{Z!UnaeB1usyR?J{K8w;EE$A5^ ziPgrbGbc;;TERuI92OQ9{z0R3y;}f2Ws}Mb*oxN&!QP4dz9k~mKa*@#rs^-!N2peUVU7jO{Z7)8lam_gXSJ0V@Nw07vng{rOJ~?V0X66%A;qxqX_P~TDe71d{f6VH z5dFKX%vmc}-oP^(@~Dq9-d%A)2A1}lD`m3N0V(O+w#AnZZX7>~%}@w9RO2Q|y~o1L zlsW})pKb!?o_UpKaqdI%5m)R7RSI(c{B0)~DF6exBHfZMFqwY)baR0@E*5z9=UtFT zIW934n|uFz<{)yi3l1#qXtpA$;Vd$T}n7WkY-=aK8xc2=B~9)byuFV_PO1(`+(E;DF9HdQBHTh3;>A|TxT0Z&FX@e zIt$7~2#*+yH-{TSlVE|6e*;bNu>@@AUgA=bialf9sWL!W))6p%K=Ec`kmnB$%eikKJ0x{DIQ~*ZF5+cH zbedn5+~eglGJHbU0IJ|xrQ{wn4CEW%KtsgT z%B$kyS;)a%f(#%Omx9DP)#ZS{Xx`JV6ix?b-$c^w_36G9P`?1g=hK?{pdIp1Ex$t1 z2?PHfop3_r^D+q{G#&y<2MB{goRkzG)y{32v6B4D8OO#PPDXS#^M`#u@z?eKty6gE zK4lX?EVsY?rfpGa`W0lzp0t!Lr`sifDoj$4*OV!A7o&O_MgMZ92w8eHY+8)rl`77^ z9N6D}4Fa5t{9NkgO()Qn6QYs<3t|S|;5bOxa`VkLebP{s#+88@{rkkkL{NAIwZP)G zfWM-5u-<dAGNvWm+6wGIO;7!Q?n-uu+)y1;?wFRzO2 z=VnFZ>lZS={L5+nPdgdKsPo~z@x+UIQ~OU)niiC0Lyix$w5Ww=L?#mmgga)@e|gea z63A<9EmfWo-J4(>&}O}6Dt!h{odVUKfqgdl7AG$B*E3fJk}RsryT^zdK{|W~v_vKB z(Uw`x9ii{($;Awp9)?b#mx1ERNT`d8u0_ARe)c-HX_&*86UoHvwsbWZ^QXj4S zAFwgM9tOgFSTJh*sUYv3wz7jC0xwvx#Le%bKD=1J!QaueF#k5hnJ0m;M19ji{>_g4 z_f;Z@6gZk^1^M~;rSB4cy-)?5t);a!yWdS~fXAkw_2}>Itgxl0WhJKf9lySpCmR_Z zK1JgzCMHIccG6*2xgbI*{XDRP1F=ey#IWD*5~~d*G;!La|9x-&=3mI=6-{tTLV9|m zYNqSGlAV}zq2048;!x|OKDBxfvz(RV;g_FZ@L!ia)&kf|_ZoG9zj@wYGz3`d$_;E$ zQPF0Jzi-Xz4ay73zZUy`&@lFc7~6|LD_riG|0M^d4g#< zn2dtpUvJed^y}$H%~z}~exq>4SRfTOByr~a@2~pbmVm{dIt^%>@agHw;Fl$EvryvK zAMf5-cWqXDkcgPr=qjbXUF?6skTgTV)pjzViQf}6vSpSMkoZLh6=r2+kplW3{<_Ur z14f-f)#r;XlyDQs1Pg}nAb<5K0w1r77<-tIN zwUSbAYkOp8Iw?{sy+2qKgSlxsc__&~ULo~q|1Q6O z^Dk396!WaE*1E%w>em5}X96%~BZTB@x6$Zwi^t*~KX)VZ5DY@k?Mw%4Jo>_3eOVm4j-Mdd_jhLnV^}i}nPM2ljf7 z!{(NKuWA#=?Yy+huP{FT0})#Ut~`Fy{q(Uttsl>LkszaGsB8u(Te-O5AW~*41po+3 z(3QVlg-7{ZJ9y)lQgXZ*o07t{lO7Z`xGHOCuc}t!*Hk}y($9S0@Trf4|H>R6tkVO~ zF9J)*S?4Bb+F*m`u&)H?_+i-Y<_ja*l8t=-FpbQn&t+DXjk?(1@d)5t38*1^n zcJv;z#4OI`dRO=54nJKV{}g{W>C6U8f=e&g68i(&vZ{H6waHAGXAHJO>o%m7@%611dPhWRp4U!MIbLa`+3Pj;S^)f_KRc3dASD9=V6tmPi%DG)2S zIN~U}))AsIrBC^_R}Wn{1rSQNAP|W==#^AT9Te&#rl)?-I<2b74A2bfPt$TtZLE63 z&x&=uUrvoy;b^OOY|Gf)r(P+Ku`$dIDcByu$ua{9{sB^1zk>_lij7Lyo z{u#~QjB@3pa1n`VkCli8qmBWBE6RsyJEkUL%cWC8wvaO>W_^Gr(aUgaG{sil%W~^| zThonWx~?{T>a{Z=bKMh#s|i%-;y*f?0j6+$T}g51(p3;<1A{(U-qlpMCkJZjEyB$; zZS&n6EDR_ReyCtb^GX^(KitfHfmT`W(P7>->SJfH5P%UdISxl5U3tA1&l4~=dgwnM1j>hX^NBhz?#}Y{3R6DC~k4+eiSlU`CG8G6X zB&J8S%Dm=G0u;>!L<>xRu(0veT6<9;Te^NZKc??PNCQtY;C+G(FOU{n28 zb+ly+Y$l^BW=`modwYe0naD-o9#Oac`25{KJEJ5j{TF_9&=H7z2Uu@5qfPkHXDulqO&$_qFo~9A9Ik}-qIb%nL>`2 z%$>CC*jjy0zuNcqEK5X8Vx*f&_(E@2=!(ChmO!7ke*Sh~uG=t39h0^#`yx%-KEwwq z$<^4Vn&{YUesUpvDR}EX<7W9|{~-qd0uP@BU((HpXmoU9994oizq`J+jzf!p% zyp=wySao5xxPL`3$9=}ja-CpzlPOd>^w~?M7-mVy?Z~0l=U%HsTVf4W(EEh)62Vz9 zvVdKBW25DFF#+ZDMn20H%kbwts zhSNOx#1ET=x!*|J=Sk*EAAQY32n|VH(peX!J*re4$}R1rWYG*hpWM>j?%9SrPNWLu z=vww*#FEyI+Uk~GX7(5_$fu4kbse=^aIy}Sik^5DbYr=V=7vZ4;F7Ra=f{L?zabmL zb(1pQJO1-ebk8YpAYy%vtf7s`qfSCrznr80&7B3l80vzW6f68{wuuD%5=*%Bry}R+ z-n62RHJj3j96Ah>gY+m?D{Je;Rg-eOr1*hf?&1L*R_|hfE?(ePZq&VDqQSuZf;7D_ z@oqkX`Rd$Se;{dcP^{R~ecws(Ja6tx9xGFh03tiO8eKej3bN6gYHiIvF5&ju9=+02 z;l87|&U81k0e-5w@Cbbkxgm0{V~?L>g$##=@^q6a1>L2FvTDm^e1~pFcE+Jez3i5r z#eyAGcwG4X&70%ze8@KS+qf5-p6q{U<#vuFF11wqgi=MqyYnw@6mw80X4zr1KF^K$ zl<{_`MyT6F@5s?t7abtNf-xAK*U{VKtF5t9<;-`zzEve`X>HGEQ~OSaF-RMV88WyP-w4`E&A~i~;Q!66>l~QqrqKcN##A zS^&g4c0Ekc^fqW`*uLaGk8qcI1Mm2}TQ-W7pc)h_fq61^$Tb`=#kJWpWTo93ZmR}1 z);XyH6sUCq@M1wMsOmVUQ*eJwO_L0_h}p+1LEYu7D5^#iVpLvYqOvaSR93FrR;y;$ zl8MzFq04-_xm*OPj@H(2^XGcm9*eH#`w5|C(Z`OZwzek4+_LUWyGhNER%i99@iTXB zV?9Njfj^_LU0?7B+TC8uX{t|n{=G))9G8ZMa(@gyhHrD#rxE1qxopV9f!8%~cQZp{ z9=w_KDrpA?FIy8DA5$t*$IIt8^EBURzO!1DJD4Haie>Z^-oDl|)2`j;rQj{&5w&K) zRe6g!Z`8-Z8je3J<$jCd%Ek>tw>0yH5MIQJZ|)e8RCf)9R;l7tQ8Ya+d3n~V`~7FP zeSF+FBvr<{lbj*Pv)pG&6UI?Jj&2WmDVzfQ8Ge|a6`2ffb&h%)=DNVs_GCy!(Hib{ zNqV!oIZ<7RMnz$3D0I<)<6>9O%976(Yezt`s;}pgU0d?wd zlYAO|1(Ta7KK_Rx(kCl@H?uHhh+Sh2@{67KQ+ziMkp^?oGEBzf%0pE{ z38|5RZUGh1taI%_8J|^igs_?2i9$rDADy{*f&u5|<-;%A%bk@r)95X6@^Uv`7wYj^ z37LWypT~4(a;59_2WvC*b!szkH*khWglBKejx4QhQl-pSBgelu$o~1PD`PVI4jcA18v!>ta|+|1dT85Aae zt5Ph!{}7B5eCe(GQmGi*kwsvF939ltTFOm``j zNrpY$`&(J-LfAb|8*i&dsaj?y8+ael*8GqV-HFsjavHNJFDW~0)~JA4OX2?Pn1DCm zu`{y9zD{&?{-VHyH4zkUb(x{!IF>?X-nRB4b@$nK)Jq|>&XwP-Yw6}CUP@(%3Qz@S zy+aK!?K{?ENB4BpOD_;o!iG=E{Kgkn7p|h7eSUVAhPNiQyWCU1?N=~{ARRgNG4nKX z*in!);4v)Y<-r-KVzhchUL-4-JAdSRq3+Wx@qQWCrLR2@qG#X>4Sgh{#gzJSD)RfN!`_{&>>-yE3^`s_<5c5U-=}S(Xn4YrtpXMwl zPnkR@UVTPIGrIV?`AX6$I1kB)Ln2+wQfBBnJTaSDGNrGj+=I?3HIET)%V+ zZ-MEpB{Wlyk<}v`N6<7t@}#gNmQLEuNS9?U3ajRf(`Y}0RMeG0vXNRj~aQX z>eyfAJAbasoz=Cg!@mr;rMk7&o4ft?g2qD8O7u?^#b#()IaOnbPm=V58C%75jp{x=g`F+>0S&}aWxona5bKTX`e zgsL)5{&rzI*wiRLnFv=qD$I5WK8R;+aiK7^u%ix^ev4v{XlvXD+H8>-_aI}Mr20Nj zWTq;o5$$gGc|bp#N>_&0Cn#{?>?5}uKoIhoG+*=CG;Wu3>W31hm*)MBO2+XXFf9dJ!43Kf8mbPya|TGB5ky(C8)?qBH#I+Q?RUc~fY?a&1fLii)rIpb#c~ zqBEO3zEMz&*0j-=o(&p@qR6Ln*+zX0=(jcJyv@!Q?qCfv!a8TJrh%|=0%Vi$+b7Pj z?kR4Zpuc#{v>N8WKDd9;q!1h$bTeXo4!_w6VQj4Q1q4}W8!eST|{Q{d?ASbA(pAX#q#E~>^T}?)7 zWo7*Wv&o3;^^wq`dVFx689~a3;c(6f?>&a`9NXL|O+NkAPjMwx!{yuNhL&ml13C8c z^qJ(Xe5%-kL1&{l&#h+X4$eqIYRCdr7g*;K;Ai$V?tzX)FZlxFXavUH*iCQFZl|Qp zpi_2Bo(rKRX`^%2VT{gl`SEHJpS4y3n`vzlil#5r>elZ1(|21KEhu6_vZPmX#yDHBRoqM}lb9?K0j|(&VqTCy z9ojxOd4vI5;?*oIa4h1AW!FI?I|@p?A?QAy5O}qJPZghJTi|m@!4Z6V>z;zs#tYYK ze--yYMsv8lKk98@4mT;oCo(~OC7~ifY#O8(= zWi@e|GGZc|+fdz!Hx z*nat~qcbnSa>PUSjc;o2ln9Gb7~uZ(W^xPDH5QYm zHhd9cNqPP(4cE-{Ti4=MyEB54lbtJvyKD>6JQGI}{H%u?+#TFoQwTTbL8<-8P^Z)q zLNBT`x^&!P{3&UNlX;mYG%@;k-tx%$Sj0YT22kWq{a@g})bQ_2>i?u(G-0P`UNT#08W|LymzU-cpV<-3tp@T&v^`CFplpjoOHL*cI-Nx2^R2%F z3@V{BWTd^dFESkMUhSylpj7Yo%AEdl_BgL6{c1Yd!nsD9ct$i>VebYtfoyZifB&_6qQvelp0fS^}x)z0G1 z!rz8In-LL2!{24a1w=U9k(q(ih^QG`VXtvjYnWWnMJ??PkHth~%PkG1*4U!nDXD^| z6Mp-zU$L#%C8$yhlnYb8me%GSSlPavdEdG!d^$7&_#z}wBwHpbS$x~mmg6;8;eQA` zLIYLp+u%Q3?U_~PD$vQeIE~RxTUGfb_)|p)h4O;wbUVBCjG!Ad2Mkyrp>f{{fEp#! zu@~tI&3ab^6FAi^-Fza(F3RVFRNmb4jnR>j#HqaH1Z@W^?nh?2kJ1XcD$SJLDtP^a z&9PbCT-?D(T(&FnL)xhMh3F-}r7uphUs8Rg*B__0zAPwp(eLGx)NBZ89G~YAP-?I% z7Ehg8&Ss`C6AXt%As|=Q#*)aY}V5?ksW0qe< zM9w#4#b8BtCyK#)kw-TnCu`iCME16H6BOi6y_mn*Rq%eeyhuEt+ePoJsAY@^$`FNF zy6T%q@3V&KE%L^kb@}vF7m+Fvf9A23bz9ZW!YbDzqeI)nwXJWu%E}z!e4wEa=R$hh z93;E)1h|=}C5#E4-i!5&ZAIsUl3pD;_o3fi2#_|&Vkb8B@jK#Y1@~e*_fwctR38{- zrmB?CLw6?J{AD|h#15Y-ADU*)h+m$bwh+fQ!H&L})3MK(ep=_wE~RxY{;rxbJ|(3Q z{rF&>+3Y-xMEj4__y=9FHd`wsqK!emf!0f2qG+f2N$GR!OqXr1Nes^Jh&OJ1scqAc zUAJ|g8Hq{C@@0N|sIyb1j1{AsBSDxEnS2z)kd)Q$p-IIgh;erpq_#v7lLEN!5~tO~ zUq`ink0JY5&Wvtzr+d$BJB}8kW3ID!>YSCjdq;2Q$6)UFLW_l#E;g2p2u-0MsvooC zB0wP)C@d%slo-7+Vq!lo&HX3x5`XVnd;tv_CyIacBK+gyHt*4`nA|mDXj1JC2le#U zM5u0FZVxb}A${kY1S*}O)XemCNl-V?eQsmox37mqcKMw!xk9e>y$1TVHZRdu4%%}j zP$2PkNIClEKPhpjx({Gf7k$+7F7q;2Xq1)hL`Bj4%yD9+6)Nmjq8-vV$hR2z?}U*( zhO-o_7HE5>?c6(@Q-jF0N^RXe4*B|>xVLMz$63VL8+^=hHQ{<~!EE|%or#HQM|72} zKI2~|@Ji)-4<)8Glx*v~;cY-S_K=fhLWb)WDs-bcC+o42S(q*FjU)~kpPPE_4aaop zvktZTdE}#t{VF`l-;N*>mRtgHp?+Xo5x z*dYp!2lvu84bLYwpaH2sBVhnE6K;G&P07lgyN9do{ZoJ-Av!V_-x?|4nULOClxwrq zJKDNn;T;m~?e1oEC&ydgm6!TYq%$wx4>OQ`UPRRP25=ZZ=a^<)dStq8AwjKhECr+7 zmdJu@@>)b%eyX!KkZ{%(8(7-RzLA<>>@m%}^QXMF3u$<|Ks4i~ewS$C_t%L(I%=H@ ztGv6fS~KwXWlr@7|B?Dh)O9JWDeCHqi%}cdDJ8?(Eapx@)3H`9O0vo~&~0B&BV(?( z;-a+TqQ9Pc8YR-FaX6S>yK0XBD-?&?c8hbz(R#$saI#|G$>e9gZ&Pu(n}+YDq!`*L z%t~E4Ks!aL%M)yuLsd9qo1M?rPx+?pQmS&^XXTx=m_jPe2w^q(-YD7>m zS!J(YP2r>#m#;~?t7a|nBh$1ka!5rPB(9lU5lzp*Eh&ZIWepWY{}i8ru!8}M^9(QJ zp}?AYyrVtRiP=7LCNDgVTSu9JzwM{vKS{B59--B>tdVnQZ<6tE#;awO;_+>RC>;a| zeTW0Pu1?hLnyYg!1NU;b|Nb*YJYcZ~;v4@}iQgm0=f7OR*m@`)+N3xG|356~my7uS z-#c`$LC~0q)6dm+myJ5FHoXc12%lwp!P9$6Yyazj@anOymr7jiFqrfjf4FZba0PV5gH!w*NYupBm)vufV_lYs!s6&i8nusyl$hcno}& zH2t;m*gt-4OaeXX3L8S}DPwi;zkX&<_a#{c%O>~ieQ$3s0G7W2L`t`#9t(5tK3$tC zj;!P0;NY!FyLzx=0NkdnBWGCt;ohLmUjo&9PbpA*Ly7P|-i6UP2UUR9!NmjgtCYo~ z$^Eh*^jn<<#A*L&BmQks75f;$NZXd<7CNB)M?fEx<$6K8T6z#^^PW8o__D2p<(OA1jOu&sll=WEMu@|2v}s?A4~hT=q*DYy1+xS? zm>}Tney0JIXTLty%}HB6Kd;Y{zP2SWbBKHPWd5|efzOd(RM+yQv;XjhRV^hi#K8e75h5 zpuPx*sqvovupodw$k2Qte9Z)@mgXrT${#ZOezLzv@u5w@1Ig3>@TP6ujD@|d4)Y&p z7Y04^BTP(8ZO@J|Ewq95FCF+FOaRCwGfT63wRd1P{Y4@)plJaK7~fw3F(@@~UX=>9n$5A z2*81Xt9D%X7#V-)j5=JKw_ z#>RCX?f@iAiaUs&4<8tCPCR?b!(j7n0sT3i&g!z^HYD0>iyzV1rCl-q4__m zdJ>r>@^*iI%mKSVt0UO|)kAR1q}ZgacVH5aLDb0o)5lwZy2K~{Or4imVT6@KwW%F# zAAXuwL>_E6OD@=HqANI4zi#3tQksg;Qr520`G*F0jFDoPE&KHSbx(`Ljq00c|M+?7 zyB~v<8AZK49=JL@DE6V`31Wm|8DhI zp8bShdC#GXxJ5~LVNnRcZvP*2F8M7&-0 zku@?r!{GlK5SZDiwpRRHLj|1mQm}UpRo%)%nlz2QHb^8OfSxM?BcB(m6_;h>9`#{AWPGNRn+)9FRZ!0V9S|<%xi%uC6qVLVqZh$8GP!|y| z@{%o8oqJqR^p())8PjS%`a%eSeS&q;(qIdSwNW$u*cjGve~$EO&i60SW`KQmT=FQ{ zxSs71^amo}qm=otT}%Iy@EDv36SFgf!~LUXz$g$nb+D5qZE5a21XTkKn8ArEQQ^ly z`@ErqpY6|GN9@pcYp~p#Wznwv<+LMq7?Q_HRbuXYTRiNj4HghRpxc@AAgK>&n0Trecj)n15rWxKJtRLvEsh=I|tqjEwY)AFcgsBMUhT zVIT`Hez(Wy(5T{w{0&f${u+2?@HuFnI+OrK8K4a?0Z>=*LT!_h(yPE7gnIWKA-)yR ziz!GGr5t%hkQvbZj|1LF(s)^Qee_uTSgI=;uoghlwa`;jQ?t1Rb({j`E@c^M=c(?c zqOQ`6?vf=LmzloYdtc*zI+)L%J%c*dh20i@ocdlA$Xm%4m<8xXPSpl^T~H2x6DUI- z%LVOSJe_7-t0>;+QC z26PFIgMRxa5{>we;3e><#N=C@>h~r9@2N6iH|cUdEcQcfbDA!r-$)6Rtz;tGJ9lrWi5%nt}|-h0{u&RgB>BETlz23TMhmL{~z z-HVq6PqLMu0sSFYK9^l}+4nUIpB0O7FkegQ@xf!%IA4pBMR zGy}eW?<|Ww3*olEbDuu&?|bk+T{lW@O7^}}>B%7L1*poJ4w$LGum(Y@CBSiKx%x6} zFnrJA(n$P)sy%+?+r!)k!}TR6w4cOyujIr`XQJ01fdeinH*xR#U_ZV!>*FJ{0XTPr zk@VSDYGDtM{uOuJ{1wq4w0hVD1~5iyA0+~!u7xf3(+r~z07=CNTLwhvF3F_bGolXc;(MB7o(yX;cVU|RNQ?Kv4wSNBm# z(%VYyU%*mnHrjHb-4LOrm?CPcR?gk!RB^e>{_K9cndf_p=ceK+Itus{wRf!4Lp{W| zW^KopWM7+l&qm_08 zsyxa_0^wZ(+=v1l9T*Qy8;B>g%8V||ul~+-9@w?gG7eU#tl-*uyoq%XnA=)j_Dw0S=%>b#Rr22h5o9l~<)2d)7jAK1l(wmilOa0p$ zvoXGN(O~bEDh|*%o@Vv;B}4O&NB5V(W=c2uXH{NvDswNd@8r3#d_w`+vf7>f*Qn1Q zen+W}cjP&0v|n9aGfgM+F~+erYjW&M(V|rG%)}MRrtVI9`s%Es3~FXmI#-|4z2SVP zIQH&5;>N?4PEwC}*Q()+vhAM{+tSSrg?1pn9kcqBDSC8!!D9b@N?OD|?4Ojd=eR#U zc|(8MPswc<`@VUo_v|GOgw}jB0|)EFeH5@g{+4h;?TXFL_Eskdt0z0BM`^={tvesypc#`NJPYB6RMjxd;9}LA^E`J%Q6uAD-KWlL1=}+Ke{dl z7C?)L{R8`F*?Ys*^(lp)f8U3#r-ykvZ|tD8W{z^-6{awwA5tXjbx|-@HEg=+1E=3y z02KJ6THzB$WeeR&G*Rl<9K}0b4x>#@QCz%Q<=$JFfv8uv_Gg3EAtKjN^(Hl0WrqSU81gvCFLUJIQo0o9>pUC7Q|@^3r&Q zUN;yvm1vM)dn71DQP-b=?~W_49&37g)B_6WKoIF*P4iN&ugH01bPIhO-JB_!VpYq3kmH5iI zL2?^qW`wtGgSnL?SP=5H2@|yHhm?=dmsi>GN5W%bW@U<3rir6si-EhVMe%-<>m&Qb z$Pj>;vLxnX9Lhf-%ah-`Eshw|mu`)EDj)lkjx}}gP~dkuNYww+dUu5<_8~zg5d&xp zo_ehhhkoq0)%`A*x4t+^%rvg*12%@qn=FU=+HH_@_D1eC#BDNtYJ*Qz&4Lr(s@mJW-(|hS3|@`u9xVP(?ANo{tOC@d~}W0a9I< z&9!+gHMMV#jDT;N1!&Lp6&3wNZ2P*s_M@-Ic#|!^*cLlYj^G1_M@D*E6Os4oBSKv0-`IFLAnnv{kFA>vyJmVM zXk2OB3U3tG+9j;2N!no^By-Y=ds>X@HWN`(A3YlYF<{?R)8Tg6mm_tySo=rKjJ!?NV-TUqnB#4 z3-bX)2-CoW32+|(80kL7!^>3HP*3zf+<&JWBhwF2KPK1a(EU_)GcfsswYeG1Mrfxm zK6KLJ;)OG@_Y;0ePy7A-RAtLM3RD%#{x>w=-kJqUbY|y$898i6yn>*;+Q5m>>Yt@u z{G~VdawV`59I{NnK z(`JBwTW~{Fo<&eHDBF}&=B1t=4w(GDU}gcgVEbH{bBJaFpI$AQ9Sq0W>Sx?9yZ+;K zOX$|)a&^N|Fc7BsX>G0)7%B?#&ZWR9`$W}j_I~27@Xu2%;`&xDJVP*?#7CwWW$UGC zrB`y})`nbvYyEJx*d4Ka46$?TPe!V`Q?y+>211uF_X&v4Yrl)xZ*}c?T6D~%-Fvo2 z3x~Q8OS&74!wqxZ2XorrT%q%MiMNDY`gcPR19rh39i4m7z&knOV`}g|*>+{?oFBMs zfNgu?blSAqcK~oSom_^YY`HQp{Y4#AV{y#!b3Fh;Vg%aeT+m}d&M#@YEF*#GxGwpJ z4G~an8L%SIw2@cr<2Lw~j1Of#f^?nQ1xi2aATH0eV0*KRg(?;IU+o_Ewf!h|jo@1` z^GE!6F2ScQuoK?nz|q`bHu3)TiM=cnJpB{}vDk%Bti^JiXQr~PwH0F9wf9}CH`g0) zPkDXp^d;8ZttuK>VHAgkMzRec?pXm$7&^d4_2u95`6Djq-qv+njRcWAaL^EkNLp-c z#mX#+MdFM0+HIT&)xg5yV!zDOkq~|ZE0Dbu;#06b@^QRKJL8Te7;K#h#OMigzUTUb z2pO*;V&V}C@@1o&>7ZlG8Q{ahAK4W_~F69d5{0O%GI-^WH60*5glqDr$Rg29)=6m~~^z`O#5nFQ;;d`!efc61=Ks7+WY zm_GK=wm-Y9#0Ml9h+u@`EQJ-AvX)ys^YZ0UZSh;iB6(oGcsH1S(f>foXKWM9eXMv| zYbNEkU{(wm4Tr>Wraujx6&5kqFsRo#`ZxwC6LV3d?gX9zow zCw7v^Q(XcKH*em|djI|pmp9)0a}C%we51+d^2-Umw{S1^B1OO5#ykzgcL7xWZT}>4 znD!VL3_eC}h36fK@a7?di6JIi$Nj8td50!=XpK)-13ER4#RK@NlrM;AD3 zD^RR)L|6K+ASJ!d%mR){Cr)y}tX1}H$&oPAJFq4@7bcGFmgPx3l)5r{=Jm&kj#Pv5 zqED9&(!gz?5H_o$o4v>}6|VzWb7%|F_Voc%9LHQE`csMManhcFYjoV&DSY2d&mGi} z&D1pfYkjmpefW@flqN0qZSm5sFJAq`)p1v3Jn02ISv1F(eeW0QA%Y4Pxj>}3Lx_=a zyiT=bSX$f%uGjGJ@Y?~DG!M|&?I%^_Saeza>jjd?ei2F!w6MQ@r5zz>`4_@Gp;M;@LxdFyQiTfb71d zrR7ZA*$f7UH((XD1N0=T5?i$C~l_P5{VHs)- zN3;p(@&SYUU|{26&aMIdW*pnkbH5*45iRWjiXTq49(V61ZcttL*rIcPJ@$3#y#xER zx&NQit~;v9?Ar<&OR$@O1;K{Wi!|v?RC-B5k4PJksz9g$0uwu80|cb0v;d(7|8^W}c`o_o&T`<(4(srT2T{`!+3cT>U&{rw(+ zN<9M4)YKGlU>D)t^S?gss%+w|0zZz>h_Z}l-I`|um6ps z{&VBPq2IFs!_LLc?ToX7u&ws^q|@miDd7eN_ET|jQCs{>rZ((&m`2-tkL}KbyTA8s z{>nh3v(fW>*O{=`)*`RPBl2ujz&k(O~1J6eY~c6qxFg<*;G9# zg9t(WPNeT|Ge^F!>rUPp7;%tOvT7S0)Lp%` z=dAAde!2|GjHUCMHiR6#=NygnBE`7ads~<=PVvX-3KZ z4>PRgTUe82%~89GiyXS7UAx9>I>i$_RVAo)uYe%K8WuO0RtNNlbhh%kpbDaZz6pFtQx}l~r zhRS2T@amCV`X4Vo;gavjH$ezw=;E2J|2*#6e!>IfoJ*caR>@OyUH-(Y?Id; zD=I2p`1#RuadJAw3j^Art*yx#%cDtpIhX2 za&t&=O6UQxV<4~`kiL>DY~8@#bCjYnGtPDY;>TO|HqF$mBx-)SxGT*TF*NUZ9k5UE zU4*Db`J>!wjtSp|g@sudpqJYWT$E0-o{7G`K5afm;kwQ_w~rcU4xbE&i4zcZQOwTyw}-v`+ZzRJ)xrlVA|)&I8+&Cg$cM7S_J2F=^B zBlXXmIip{2b5SxNCcR;)<#Lo!`Fa?MzE@nqBx|C0RXVduK37&w&KDZWoM>5B7QRkK zB>$DH?gWK|{?@%B-|N=jds}eBG|FB0@PG|~aGT-bVVC~C_#=Qc-qz?bN3&D7wl)1ll{lC46GoT>uOO<mEp368F!dUin2$JnEN!`Z~wnZXer3Dc5O&Jy{xJ#4ZXqH2_ zej}#66QE6-{JX#)wP#pVB-^!TH^pnPN{l2tvz`82YZ5eYyAUb|vn?;7$^S)$qsgcpeT*wE6V;sCJHjnFUwu8;h`)Kz4 z(ZCk)zS-F}!~~3k70|dL2=3|NI59O;Em{bp<%J8tYhxTnzi;bwB5y8+!MtgG!gtSG zql@0QgLTpHH|+}mu#rR@`_BPRukd*q_y+_-WN2Q7nZoJ7D#&D3^MO%786qKQK@hl2 z+nFcB5nS7u57ht@+66rUa7h8zn3!dQ&398@wSi;aV5#RybaFCx{U|t*ZII==(dBpo>M5rs2Gr+(ZUzjf;Iu5_$pA3lCe z&PcSjMZFhdBE%`x92rTi+~RW%`6}`ZySRrUN#FOc6ie zl3#^$OZHy=7Q<;w%y+&#lpx*=Q+VvgTGE^1)DGa-c!bHr=6nx<7Z0&-hpxXrpoPMv zf^tQtE!%6+1;KGt2@QCjvHph|*^t{5D4U1*`<(|^J1Xgp3t*>zl2Xept7TSSwu_j) z*^EO8Rr1NmbV)By;}E)j40iEJ!mfJ9%s89cTr_*Ra!|X_2?7>3uQCh1bgP4r*FpSA zCLLx)jW=NG>N_M{X=Ajm=SmMdymCRNL)@9p$vH<>3&uj^iQW&Af~1Y2z8t@`@PGeu z?FM|UGSAVYN84!1t%GH=PD*d0(K|Sf#kqWPAIfuG764d@=}ny;S^)9Ci1E5<;5Jb> zry7*ia3)~?0O!SpA{b3`5e9w5B2%ko0WZ(ze@HRsc!FugFOPx)Y|?i`H3`yBkxSjO zICeEcK3u7cjE8VoQKBnc&_r@NEQq)>)enz;I^L02ACR;&e8)Ww)wqxyn2}?ZN-;?p z*&zJLlWhZ!^WMR+MXm1fuN8bbFjKo73}MFTZ77WKVo8Z#+f?`p`3O&wu0T6EAlGu&ybJDmBX`)n83oTS-ZY zMXu2B5KaXGVajYV@0ckI`Z|YR14K=U;pY$Ki4@KdPJ_h62YAIyVBrhwv9sFmISdLw z!C|y{3_Ls2ftNom@umv==F%n~%OrsIlX@h$X{a)MNVLFp94vN<5b&OHYanWeHoJ;i zV~sif{y5k=Y-R{tNQbKA0J?Rczdv{3n-^u{Y{@3pTsulX#J_%5@~35C3?pM3WEb-7 zN15;@+cAkh2d5%!D zyA>dJBEO1PB-jiOrt&!6fvwq^d%4dRrq{WELy98JWt5VMO(Ko8)Q)pjECJ}>k%t~* zJDJI3M+JO4FuT=GqUX;&$v|=0>-*-^3HfXjKcOeg({i2SH#1y+B9|lcNm$rODY*?% zUe~y|&&zgQE<4E7#*$Y9v)yVI-lAHLRGT5JV?qjjgGq9VYw)Q2zpC_KuMsFQSLF%P z4Nh?S4hp?qSza^*j1e%PPpDjPutH&RR@E0x&>*C0j{C3lW>82fCC3*8)#5 zSDH~f2pc}{M>w1p#>EPaEvBe>=Q~?1GC|bfbIbGi6+$*RAhy8Sm0vu<cYy4SUsfTcQ=TrAo4qA_DGTxuX1*fk z06EC!O1<_8JFOiq>7KDXC|aBj<>U3)AWJzpp00f7;a;YS>GM#)os0;1_|Ob8=OiyM z=4FeVcx}(dqIYdQo-O5=?mndK1XgChh+pJQ$mZsFyP3ASkq=H+2kA9y*0t1rYlE|A z^&;|qh_Sa=CX3BsN4PS~B#`VP9LX*Q3o5dHV6wmUC1nE`&nYQgraMW9qfpj`zSF5U zDsRV2DFfyF$H&J#OwWoOTGC3ub%W~wh^HHtV>>@{`43AHK8W|;II7&Pn0MDW+cuO4 zJ2~5Z>W?8YxKh9nCLD^~HbO_;lKEH2C?457aZ}g1m-2it@FE1d&zh+Hgjy9s8HQd0 z?6f1y01=gMjvlcH0k`wdPfqh}h$;cwpb~rvuTFchPccV-NN_OY=+0~;dm@3%T0bJM z(TII5S9*gG9oZPr2Vyt-(WB3l<5JTe8XWOEh4$yb#JPZE4SS#)Ns2lzgC0m(?<$f9 zQZ<&-A;3z2SG2-tPln;eM~_c2K%d6f+gl2+fw<|GJU^`L3|%WsbE@{ zw*J=-+ z*YthB?2kRCHvk5F=5y_9%$;v#GAmkR^N2d6M~WP;4gxCEzyQ}F*l@$!35`^%9)a;C zux63(Jb3ETp-kpHO*|fxm)I~0?z9 zGizI68KxZVYcd%6MYvx&L(}C|O6(Eiiky6>A$8ppuH00~3dHeC!V9M9Lynu9Kmqe-Qj{=4s~RjqrJNIoh9~5F zYCT7?5P!=zRD8@RxUxBxEtFfZMPkb6nu)Fv+gPPL4laNdcdKBvq!}eUHqP26wRpuN zLEHe&={Ss*bz0p0rA+BWM1Q{4JsRkLvw$Mboq?1d{IRNS``_O`{LHFP*rw@Y9b8*f zuqe#G5JB$(tki86xAb<*8QkWvYX|JpAT@3g+BEa5+!h^J86nXeu?jjoJ*eap_nDD%{ihVmM*#c*n4~W z-P@K0JA64FHNt33H}x&3N{qEOiF#Uyfbj&@7@ z&!sPAdj!lAb`ahIF&ctY!vs;>DLZgbM(~3+a10rh_n@E$4Yjo&7;i1)VvfzeSbv-; zdZe=;2UWf0pkAq;yl;LH%w=ig^I1@l`1bi(CnDgRg`-^X0wKBUJ<^6(7S?r#I}{C< zy5(;t`g2zB0AN7wTN10KmP~L}c!D_A7HWqot)4u@w95tX0s}yNH1e0A9V5P*M7&PxaH~@47eE&cPsDEvP||XCKe$i9jEB-;qfN?JKKK7x(?G2>jLE^5ge3hv_MQ!qvnF zD#Z+_O*_EElNs6SGkVATJe=tCu+d3E6x+Z|<;O@PkH;IjpH-s&y7JBk6;v|}uq-#8a^Rn3* zp!ky{4&#FnT!UQ-)HNmVBR6EBpdE+X2MxpJgf2dSlryzMH&wbJBvmp_K!`DAc8d_~ zZ;0f{inkfFCVF#^e1~om=#@5kTWigweV4uc_Gc&fgI+?A^84% z6IiDl=rqmu)WYM<0eVLgT?Ekr0d+gDA|2AGnxBNx=#uY`?3)dC1Xt^gqyNg#ena_c zeM0jgy*Y~mfO1H64>;_X@LmsxW@-fFcJ=wL6D-YNeyqtldKrd>N9*+cqvAjAUQ134 z5nm0XxlT0|R8ei9T(O1zhTxD8OB4zfS8iraIUW4qfhnk2nzHQ-M{8pIVf0 zn6)j;-<6bRDC88JxbXD<=M(uVBZTGsl4G2?lrCYKW8|4 zHx!SABO(fGsU83Q9fCL@Hl57cw>WdZ(M1utuXhLEgk_ik-S z$3IWRsTD29cK7X?p9k;h3o!8~P+>a2p!RGi6s%>s!lX;YoCaF}BOZfBnKa+^o0_I8 z64R$rE32id^#Z)OL*4u~B*+FII+y>KVC0`S_KQEUpYIOzS$ft99g2wcbnlMj-a_aJ zOBv3Bc*_~7)VbFiQ2HuQkX4fU{E~(V$9wa1cTPfmmwmwDWi6V4LFHv#`8QEt%j7qP zC3IOvaFBS4ON?07bdofQ8_;Mpw~S2G1szh};mcKKbF@yEYN@&0kYJVeIMvYJszwP= z%|fax9s)gdV?zPLS1v*`Mm7LEu2^Wj;{9T6JzBga>&vHLH$kyz1LVSO%DMhwt@~Cp ziyml)G*FKhAdi5gP2V4Z4wcfM51xNfqD|egNJM<9cw1g~5_qUTgGbxs?Fw>8<13Bt zMxmYdzyxRWU-#0#55h0+Tl~{kV6LV{_ZoqU+j1NnDnj^j07@qGZrzKf+hDpy=th?R z_%Hu+|LZ{Duf2kf2D{r#eA%$O42G&A#sSFA00yN!&nX@u(!dU0)ut^oF}xhmWmP#W z3Ww0)kmKZT+jsH}s6R^M#4pwzLs&gXk=>i1rynW$j7Z1qY#J#++x82+zbiKQ*uRQl z^w_)dQZj>@)2H0a&!E|+4j2LpNKaj+Zb}Xy?FtBk2VJTB5;F}rJ1DznLBiYuSE|wb zGtJ1g;)>imV_>wNj?{KyuETY2uWdhwRNePG^JkWpt~Ad;i>HOY~fnZ@) zeFRHdCTb>(LTR40NBvX@n6En4d>QEM=DG`v#Ve_!4^L>gR4;JH|(_WW6sPN9DUtMN-I-w-I z_xNI!#6$~pmyK@!vW!5TDaJt9@PciRanB)QJG8T?#vDO;FS&>1(946hYEJm*{FgpE zs8eH>(Z*izp)Sx6d5zw=$bk%Y=bsNVZLJfTNnF9m;y#avg3qwr;gb$e`Rfo0R^AO( z-pP!rmtI=w1mtaujpij)ryU~hNf)=0r*7FmcK}+#_%L%}1JWp)K$n3a#}J}fPSyx> zXeL{)ym z5n1W85aM&$H~W44%tvYHq^QzfTw1Q_z@C2zq!>_GuOs4${Hc&r#gI^JUV5q}d1pB7?XFe%E}0h@_Cq<#1#>mi)t z$$+T$I{PQyUshSX6ZG!nC(i?7Cz^I8Si!}K3^s<%3d)|b}P5YHn&rxy(o-{JkZ0t&R6!jLL!ktkFLieU%1O z-aGy*P})(Bowenrq^Kj&goRv&2%-VqO-yo(y?Xasy(B(GrICWi@?;+)2 zvgMVP!YF;rpYA|I+5&_G4Ltn1C{=7M#@qvptc><5`%)0rzhQvZSwPfNYHYwOjRVW+ zVvqJkWJ6Ssb_k_5#oroJRq4{-$6b9yiR*Oh3!q7o&-ce%dQ9yDEZRASjZoJOFjH_GX7pvqtS(fWP|<$`9F%AxmsOqW+q(Fc&)Wnp9ha%Pm!!be zuOY=P&}-jaHCi7Z=tPj!oKrG+=}F5gQ&Xz8b`Pf-&uRIboqobXYS5yE5;Lvtdkzvv z>U8qtw%v_>jb#n-rH+*7`0l94WhD?E3;p{Z&Fc&O8hYvqraY+!zcm zHT75+Y{v3(B@T;|UhYs_Alcn!w8in$X4@TdKq#I+<=g>r;qw*YV83%Eaov%Arup$1 zL7|a{iBUc}<`SUL>b@utLTE%_K|}+AK$%82(t*#XiQ#vuR99C;NDveFT5fWdU8H$X zG56}{zt&0-&S^~HHfztFR%@o(OdS?4X30d)8n;=H_h?9r3xPlHs8O!woUR$iUbk9B zraT%(6Munsml~lPBaKhs-#b~~wM&?lSLKb~$g|8(CEo)>Q(afZt^Ax48}dRcVshVW9YB93)?S}`Ixs7P;i3^WmDlnKv|gv%SFFJrOTyh{fC zEAL4J1zb(?*+3R*hIao--(86+)Ezj=-JC9pv}R@uH(G?O3hB;-2!}1Ebvx3#rR24- z9aJ@)BcYa&?wV};3yJ%~4a_G$+AR(5AU{8{-U#iwfVQXP4tc3zo{1J&xPYuMecXDH^^sa@ z(w!#YBV7+lzrr%(e4=35z;I+Oq+Tf3Ab0(s2FyKtkN}F)3-?&Hx)rz-wV-diYs*K8 zZI;OyJbO$|vu-{O<67-rTNP&fZ2kDBUih`2e6`V;HqEqX!7DSIFf84JpKkdNMg zH9e|eSmKZQtfi;ydx*6OP20h{xbp#L3^K?fmn#$c+&%|4Mp1lGhM6|?-acNn)XM9_ ze$8U#`i> znH^%9qxL~lv>k}DgaeYw%_teMjL99bMI@h-f`VqVshR|SJwiwB%}?=pqvA;GnDA$D zXzLriw&na;_jfbccN@3v-Psfnd4jwOXpU{w6EQ}f8b%j+X0Cx5-f=<3C)yTz8_Uf0 z`JRSiOy&7;zz^4!Ds%bjmGG$5P2f<855nY6SwlB(I$YUBEw8cNx3=D6V`Ia5s=t)* z4{AE^F&t~EF(sGr-XE{VWpF!LnQ{E_tqw-6Zfr$W*F#`8+NN(cVkWgUYjiztlb&Q( zj0NeQzuY6iDtlW}dhci44GlHAjFATXj18Fc(enML)TWsk(C9Jf|8nhw!`pm?a7yNG zshKr8l)4r($82UGh`&VWxj$5Wlt|kiP*VJ%JNvaoX-3m3j#~ z^(x9`e#Gc3i~I8k$8rv>9R$s@Ch@TRXF8*91bDNIj6zHbY>SOLOW0KURGruN0I3T! zU2q|*HTFLhcDNrI$ztc)lFjO~RLkNutp)nP40wLSC}}UFV%Y4$h39>iNroBbN-bg_ zb9EebcXu~wPjVc9OY{ZgM34RaAd4n7$G9V?H|WL3K)8Va+UR9Vdm-9E6v!GCM zp8=p{|D-F7)m>Tdo%~0G#)+Z9C8Or>&Y?t8$z)$%>pMR{M|h;Yligqnn~zMiu`2M( zXJ}iuZsVfTX*vAsY(y`SA_~kC6dTy=)RVeGMe;(FKM{>oj!|fzZhX4423|@%CgF6) zLlC31K+a(I>M9+=@*Z?fgr-54c0X+Gl2cDqtiL*E*)^mW?uF}k8#XHh=mW*h6%f?q zjz2pSkOB7F*AG6Eji5eDOXIio)Yrx9tJ=W;5CN_`$kmP141$(bne`eng~cB`^jB{2sHpQu z!v{Nqmu~5A(bEZj1RWin(o(VePLre3rv*VUQOq$W1+uP6GwAF#X|KrNy;U`FqE5ue zTfd6OKKTJN;1LtdP|o0uL}R=lC3dW!oMdX9-nuYihBjFUh6|AbBA_M^K~IQYFHCX_ zrFe75VpHBaUIY+Q0`ab`RfoDJ_+X|N2>62^KJ3e8z5Hg^rg7tRQ^nFqjY^eeP&K~? zyI6aGQMHT_MNIg0dXE9So0E54x8F>=LvrYgSYLMd9y{c%Hy=D_T^o|+YkeYmXXBq+ z_8=0fm^_Y#F9^$Vp_R}33xjS6XQtpgzfu9D77Z$1ne$m~2Hj5S-6tTrmjXrvD34Pr z>gwCuLp}$A$~laJD}-!a1g7?+(V*6}){tI!E(NSxT$*NC(&xe!t+gJ> z(YhC|?+;(kHS?O`_UQ$}Y7Ygkgex3_hGzh~qdZc2xh`hud%%^HV?QRbv!LyL` z8?}+3uNsFg;b0dAf-}u2(-C@&^Do5snNoz})`ietr|gWgY05Ho>mhGKVF@Oxaz~*H zenl&&0QBLZ^nTVJ*+_>h`h+x0L82`*e(`7$iZ^+Etrd#rvAf$=5LqKG`rL7Vy|Q5@ zYMv7&Zmc;qio+=0Jt+P|i!S~E{{`7}BF7EVM}e}(^p+lPabHq%w^xi1jiSlCA9-W~PR~hlnY!2j zreK7UWHcl0W2@hV{X?6S{OA#8ZY-oBkaIb4xsP>~pDbF@UfxR#7O1dJEcRsUY}cEr zor<&6p)2h!J^@`vB2p7@J7+-+E$*DZ!lP}aT3t-0z42-Ccw0;E$4` L`e~~C1;76R6_`RX diff --git a/demo-vault-v2/attachments/1771850902033-Untitled_design__3_.png b/demo-vault-v2/attachments/laputa-reference.png similarity index 100% rename from demo-vault-v2/attachments/1771850902033-Untitled_design__3_.png rename to demo-vault-v2/attachments/laputa-reference.png diff --git a/demo-vault-v2/b2b-content-is-trust-not-traffic.md b/demo-vault-v2/b2b-content-is-trust-not-traffic.md deleted file mode 100644 index 00e6c306..00000000 --- a/demo-vault-v2/b2b-content-is-trust-not-traffic.md +++ /dev/null @@ -1,28 +0,0 @@ ---- -aliases: ["B2B Content Is About Trust, Not Traffic"] -Is A: Evergreen -Topics: ["[[topic-b2b-marketing]]", "[[topic-content-strategy]]"] -Status: Published ---- -# B2B Content Is About Trust, Not Traffic -The classic content marketing mistake in B2B is optimizing for pageviews. But in B2B software, the buying cycle is long, the decision-makers are sophisticated, and the research is deep. - -What actually moves enterprise deals is trust built over months or years of consistent, genuinely useful content. A VP Engineering who has read your newsletter for 18 months before their budget cycle starts is a fundamentally different prospect than one who found you via Google last week. - -This is why the ROI of B2B content is almost always underestimated when measured on short time horizons. - -I have seen this pattern repeatedly in conversations with Refactoring sponsors. The companies that get the best results from newsletter sponsorship are not the ones running a single campaign optimized for clicks. They are the ones who commit to 6-12 months of consistent presence, letting the audience develop familiarity and trust with their brand. By month eight, readers start to associate the sponsor with the newsletter's own authority. That transfer of trust is extraordinarily valuable and almost impossible to achieve through paid acquisition alone. - -The implication for content strategy is uncomfortable for anyone who reports to a quarterly-driven board. The most effective B2B content programs look like failures for the first 6-12 months by conventional metrics. Traffic is modest, leads are sparse, and the attribution is murky. But the companies that persist past that phase build a moat that is nearly impossible for competitors to replicate quickly. You cannot buy 18 months of accumulated reader trust in a sprint. - -This also explains why B2B content works best when it is opinionated rather than encyclopedic. Encyclopedic content competes with documentation and Stack Overflow. Opinionated content from a trusted voice competes with nothing — it occupies a unique position in the reader's mental model. When a VP Engineering trusts your perspective on build-vs-buy decisions, they are not going to Google for a second opinion. They are going to ask you. - -## Key insight -The fundamental asymmetry in B2B content is that trust takes time to build and cannot be accelerated with budget. This makes patience the primary competitive advantage. Companies that commit to useful, opinionated content for 18+ months create a compounding asset that generates leads at near-zero marginal cost. The mistake most companies make is measuring content ROI on the same timeline as paid ads — and pulling the plug just before the compounding kicks in. - -## Related -- [[why-b2b-newsletters-work]] — The mechanics of why newsletters are especially effective for B2B trust-building -- [[newsletter-growth-is-about-trust]] — Trust as the core growth lever for newsletters -- [[the-sponsorship-relationship]] — How the trust dynamic applies to sponsor relationships specifically -- [[the-real-job-of-a-newsletter]] — Understanding the job readers hire a newsletter to do -- [[the-compound-effect-in-knowledge-work]] — The compounding dynamic applies to content programs as well as individual knowledge work diff --git a/demo-vault-v2/career-tracks-depend-on-company-shape.md b/demo-vault-v2/career-tracks-depend-on-company-shape.md deleted file mode 100644 index a69dde29..00000000 --- a/demo-vault-v2/career-tracks-depend-on-company-shape.md +++ /dev/null @@ -1,4 +0,0 @@ ---- -type: Note -status: Active ---- diff --git a/demo-vault-v2/cycling-teaches-patience.md b/demo-vault-v2/cycling-teaches-patience.md deleted file mode 100644 index 6da68d10..00000000 --- a/demo-vault-v2/cycling-teaches-patience.md +++ /dev/null @@ -1,28 +0,0 @@ ---- -aliases: ["Cycling Teaches Patience"] -Is A: Evergreen -Topics: ["[[topic-cycling-training]]"] -Status: Published ---- -# Cycling Teaches Patience -Road cycling has a specific kind of suffering that's worth reflecting on. You can't sprint a 4-hour gran fondo. If you go out too hard in hour one, you pay for it in hour three. The only strategy is to hold your power steady and let the race come to you. - -This is completely unlike how most knowledge workers operate. We're trained to sprint — to push hard when motivated, coast when not. But sustainable high output looks more like cycling: consistent effort, below maximum, sustained over long periods. - -The athletes who finish best in long races are rarely the ones who looked strongest at the start. - -The deeper lesson I keep returning to is about the relationship between perceived effort and actual output. In cycling, you learn to ride by power meter rather than by feel. What feels like a sustainable pace on a fresh morning is often 15-20% above what you can actually hold for four hours. The power meter tells you the truth your body cannot. Without it, you go out too hard, blow up at kilometer 120, and limp home wondering what went wrong. - -Knowledge work has no power meter, which makes the problem worse. When you are motivated and energized on a Monday morning, it feels like you can sustain eight hours of deep focus. But cognitive load accumulates invisibly. By Wednesday, you are making decisions with degraded judgment and do not even notice. The cycling analogy suggests that the right approach is to hold something in reserve — to work at 70-80% of your peak capacity consistently rather than alternating between 100% and 30%. - -I started applying this after my first real cycling season. I began structuring my work weeks with the same periodization logic I use for training: hard focus blocks followed by deliberate recovery, with one lighter day per week that I treat as a cognitive recovery ride. The results were noticeable within a month. Not more hours of output, but more consistently good hours of output. Fewer days where I stare at a screen accomplishing nothing because I am depleted from the previous day's overexertion. - -## Key insight -Patience in cycling is not passive — it is the disciplined application of restraint when your body wants to attack. The same discipline applies to creative and intellectual work. The people who produce the best work over years are not the ones who work the hardest on any given day. They are the ones who have learned to meter their effort, protect their recovery, and resist the temptation to sprint when a steady pace will carry them further. The power meter does not lie, and neither does burnout. - -## Related -- [[training-load-and-knowledge-work]] — The direct parallel between athletic training load and cognitive load -- [[recovery-week-in-training]] — Why recovery weeks are non-negotiable in both training and work -- [[on-founder-energy-management]] — Energy management as a founder mirrors pacing strategy in endurance sport -- [[the-two-types-of-hard]] — Distinguishing between difficulty types, which maps to knowing when to push and when to hold back -- [[sleeping-more-is-a-superpower]] — Sleep as the ultimate recovery tool for both athletic and cognitive performance diff --git a/demo-vault-v2/dark.md b/demo-vault-v2/dark.md deleted file mode 100644 index e6a14e51..00000000 --- a/demo-vault-v2/dark.md +++ /dev/null @@ -1,54 +0,0 @@ ---- -Is A: Theme -Description: Dark variant with deep navy tones -background: "#0f0f1a" -foreground: "#e0e0e0" -card: "#16162a" -popover: "#1e1e3a" -primary: "#155DFF" -primary-foreground: "#FFFFFF" -secondary: "#2a2a4a" -secondary-foreground: "#e0e0e0" -muted: "#1e1e3a" -muted-foreground: "#888888" -accent: "#2a2a4a" -accent-foreground: "#e0e0e0" -destructive: "#f44336" -border: "#2a2a4a" -input: "#2a2a4a" -ring: "#155DFF" -sidebar: "#1a1a2e" -sidebar-foreground: "#e0e0e0" -sidebar-border: "#2a2a4a" -sidebar-accent: "#2a2a4a" -text-primary: "#e0e0e0" -text-secondary: "#888888" -text-muted: "#666666" -text-heading: "#e0e0e0" -bg-primary: "#0f0f1a" -bg-sidebar: "#1a1a2e" -bg-hover: "#2a2a4a" -bg-hover-subtle: "#1e1e3a" -bg-selected: "#155DFF22" -border-primary: "#2a2a4a" -accent-blue: "#155DFF" -accent-green: "#00B38B" -accent-orange: "#D9730D" -accent-red: "#f44336" -accent-purple: "#A932FF" -accent-yellow: "#F0B100" -accent-blue-light: "#155DFF33" -accent-green-light: "#00B38B33" -accent-purple-light: "#A932FF33" -accent-red-light: "#f4433633" -accent-yellow-light: "#F0B10033" -font-family: "'Inter', -apple-system, BlinkMacSystemFont, sans-serif" -font-size-base: 14px -editor-font-size: 16 -editor-line-height: 1.5 -editor-max-width: 720 ---- - -# Dark Theme - -A dark theme with deep navy tones for comfortable night-time reading. diff --git a/demo-vault-v2/default-theme.md b/demo-vault-v2/default-theme.md deleted file mode 100644 index 450957e2..00000000 --- a/demo-vault-v2/default-theme.md +++ /dev/null @@ -1,21 +0,0 @@ ---- -type: Theme -title: Default Theme -primary: "#155DFF" -background: "#1a1a2e" -foreground: "#37352F" -sidebar: "#2a2a3e" -border: "#E9E9E7" -muted: "#F0F0EF" -muted-foreground: "#9B9A97" -accent: "#F0F7FF" -accent-foreground: "#0A3B8F" -font-family: "'Inter', -apple-system, BlinkMacSystemFont, sans-serif" -font-size-base: 14 -line-height-base: 1.6 ---- -# Default Theme - -Light theme with warm, paper-like tones. - -[[Ma diff --git a/demo-vault-v2/enter-rename-test.md b/demo-vault-v2/enter-rename-test.md deleted file mode 100644 index 94913fd4..00000000 --- a/demo-vault-v2/enter-rename-test.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled note 4 -type: Note -status: Active ---- - -# Enter Rename Test - diff --git a/demo-vault-v2/event-1on1-matteo-2024-01-10.md b/demo-vault-v2/event-1on1-matteo-2024-01-10.md deleted file mode 100644 index d12c6269..00000000 --- a/demo-vault-v2/event-1on1-matteo-2024-01-10.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -aliases: ["1:1 Matteo — 2024-01-10"] -Is A: Event -Date: "2024-01-10" -Belongs to: "[[2024-01]]" -Related to: ["[[person-matteo-cellini]]"] -Tags: ["Work"] ---- -# 1:1 Matteo — 2024-01-10 -Bi-weekly 1:1. Covered sponsor pipeline and Q1 priorities. - -## Notes -- Pipeline tracking still in Google Sheets — discussed moving to proper CRM in Q2 -- Neon responded positively — scheduling intro call this week -- Media kit needs final polish — [[person-matteo-cellini]] to add case study metrics -- Discussed [[24q1-launch-sponsorship-packages]] pricing strategy — three tiers confirmed (EUR 500 / 1200 / 2000) -- Reviewed initial sponsor outreach — 12 companies contacted, 4 expressing interest - -## Follow-up -- [ ] [[person-matteo-cellini]] to finalize media kit with audience demographics -- [ ] [[person-matteo-cellini]] to schedule calls with interested leads this week -- [ ] [[person-luca-rossi]] to approve sponsor contract template diff --git a/demo-vault-v2/event-1on1-matteo-2024-01-24.md b/demo-vault-v2/event-1on1-matteo-2024-01-24.md deleted file mode 100644 index 8819a703..00000000 --- a/demo-vault-v2/event-1on1-matteo-2024-01-24.md +++ /dev/null @@ -1,21 +0,0 @@ ---- -aliases: ["1:1 Matteo — 2024-01-24"] -Is A: Event -Date: "2024-01-24" -Belongs to: "[[2024-01]]" -Related to: ["[[person-matteo-cellini]]"] -Tags: ["Work"] ---- -# 1:1 Matteo — 2024-01-24 -Bi-weekly 1:1. Covered sponsor pipeline and Q1 priorities. - -## Notes -- Media kit needs final polish — [[person-matteo-cellini]] to add case study metrics -- Pipeline tracking still in Google Sheets — discussed moving to proper CRM in Q2 -- Reviewed initial sponsor outreach — 12 companies contacted, 3 expressing interest -- WorkOS responded positively — scheduling intro call this week - -## Follow-up -- [ ] [[person-matteo-cellini]] to research competitor rates for benchmarking -- [ ] [[person-matteo-cellini]] to finalize media kit with audience demographics -- [ ] [[person-matteo-cellini]] to send intro emails to top 5 sponsor prospects diff --git a/demo-vault-v2/event-1on1-matteo-2024-02-07.md b/demo-vault-v2/event-1on1-matteo-2024-02-07.md deleted file mode 100644 index 89b11f25..00000000 --- a/demo-vault-v2/event-1on1-matteo-2024-02-07.md +++ /dev/null @@ -1,21 +0,0 @@ ---- -aliases: ["1:1 Matteo — 2024-02-07"] -Is A: Event -Date: "2024-02-07" -Belongs to: "[[2024-02]]" -Related to: ["[[person-matteo-cellini]]"] -Tags: ["Work"] ---- -# 1:1 Matteo — 2024-02-07 -Bi-weekly 1:1. Covered sponsor pipeline and Q1 priorities. - -## Notes -- Reviewed initial sponsor outreach — 10 companies contacted, 4 expressing interest -- Discussed [[24q1-launch-sponsorship-packages]] pricing strategy — three tiers confirmed (EUR 600 / 1200 / 2500) -- Resend responded positively — scheduling intro call this week -- Media kit needs final polish — [[person-matteo-cellini]] to add case study metrics - -## Follow-up -- [ ] [[person-matteo-cellini]] to schedule calls with interested leads this week -- [ ] [[person-luca-rossi]] to approve sponsor contract template -- [ ] [[person-matteo-cellini]] to research competitor rates for benchmarking diff --git a/demo-vault-v2/event-1on1-matteo-2024-02-21.md b/demo-vault-v2/event-1on1-matteo-2024-02-21.md deleted file mode 100644 index 2c0ec6fa..00000000 --- a/demo-vault-v2/event-1on1-matteo-2024-02-21.md +++ /dev/null @@ -1,20 +0,0 @@ ---- -aliases: ["1:1 Matteo — 2024-02-21"] -Is A: Event -Date: "2024-02-21" -Belongs to: "[[2024-02]]" -Related to: ["[[person-matteo-cellini]]"] -Tags: ["Work"] ---- -# 1:1 Matteo — 2024-02-21 -Bi-weekly 1:1. Covered sponsor pipeline and Q1 priorities. - -## Notes -- Pipeline tracking still in Google Sheets — discussed moving to proper CRM in Q2 -- Reviewed initial sponsor outreach — 8 companies contacted, 3 expressing interest -- First sponsor invoice template drafted — needs legal review -- Discussed [[24q1-launch-sponsorship-packages]] pricing strategy — three tiers confirmed (EUR 500 / 1200 / 2000) - -## Follow-up -- [ ] [[person-luca-rossi]] to approve sponsor contract template -- [ ] [[person-matteo-cellini]] to finalize media kit with audience demographics diff --git a/demo-vault-v2/event-1on1-matteo-2024-03-06.md b/demo-vault-v2/event-1on1-matteo-2024-03-06.md deleted file mode 100644 index 6b0f63e9..00000000 --- a/demo-vault-v2/event-1on1-matteo-2024-03-06.md +++ /dev/null @@ -1,21 +0,0 @@ ---- -aliases: ["1:1 Matteo — 2024-03-06"] -Is A: Event -Date: "2024-03-06" -Belongs to: "[[2024-03]]" -Related to: ["[[person-matteo-cellini]]"] -Tags: ["Work"] ---- -# 1:1 Matteo — 2024-03-06 -Bi-weekly 1:1. Covered sponsor pipeline and Q1 priorities. - -## Notes -- Reviewed initial sponsor outreach — 12 companies contacted, 3 expressing interest -- Reviewed competitor sponsorship rates — our pricing is competitive for the audience size -- Discussed [[24q1-launch-sponsorship-packages]] pricing strategy — three tiers confirmed (EUR 500 / 1000 / 2500) -- Media kit needs final polish — [[person-matteo-cellini]] to add case study metrics - -## Follow-up -- [ ] [[person-matteo-cellini]] to finalize media kit with audience demographics -- [ ] [[person-matteo-cellini]] to schedule calls with interested leads this week -- [ ] [[person-matteo-cellini]] to research competitor rates for benchmarking diff --git a/demo-vault-v2/event-1on1-matteo-2024-03-20.md b/demo-vault-v2/event-1on1-matteo-2024-03-20.md deleted file mode 100644 index 994db77c..00000000 --- a/demo-vault-v2/event-1on1-matteo-2024-03-20.md +++ /dev/null @@ -1,21 +0,0 @@ ---- -aliases: ["1:1 Matteo — 2024-03-20"] -Is A: Event -Date: "2024-03-20" -Belongs to: "[[2024-03]]" -Related to: ["[[person-matteo-cellini]]"] -Tags: ["Work"] ---- -# 1:1 Matteo — 2024-03-20 -Bi-weekly 1:1. Covered sponsor pipeline and Q1 priorities. - -## Notes -- First sponsor invoice template drafted — needs legal review -- Reviewed initial sponsor outreach — 10 companies contacted, 4 expressing interest -- Pipeline tracking still in Google Sheets — discussed moving to proper CRM in Q2 -- Discussed [[24q1-launch-sponsorship-packages]] pricing strategy — three tiers confirmed (EUR 600 / 1000 / 2500) - -## Follow-up -- [ ] [[person-matteo-cellini]] to send intro emails to top 5 sponsor prospects -- [ ] [[person-matteo-cellini]] to finalize media kit with audience demographics -- [ ] [[person-matteo-cellini]] to schedule calls with interested leads this week diff --git a/demo-vault-v2/event-1on1-matteo-2024-04-03.md b/demo-vault-v2/event-1on1-matteo-2024-04-03.md deleted file mode 100644 index 4a4814f5..00000000 --- a/demo-vault-v2/event-1on1-matteo-2024-04-03.md +++ /dev/null @@ -1,20 +0,0 @@ ---- -aliases: ["1:1 Matteo — 2024-04-03"] -Is A: Event -Date: "2024-04-03" -Belongs to: "[[2024-04]]" -Related to: ["[[person-matteo-cellini]]"] -Tags: ["Work"] ---- -# 1:1 Matteo — 2024-04-03 -Bi-weekly 1:1. Covered sponsor pipeline and Q2 priorities. - -## Notes -- Discussed adding "dedicated edition" as top-tier offering at EUR 3500 -- Sponsor feedback survey results: 4.2/5 satisfaction, main request is more detailed analytics -- Active sponsors: Clerk, Linear, Clerk — all performing well -- [[person-matteo-cellini]] building relationships at tech conferences — 3 warm intros expected - -## Follow-up -- [ ] [[person-matteo-cellini]] to send Q2 performance reports to all active sponsors -- [ ] [[person-matteo-cellini]] to set up sponsor satisfaction survey diff --git a/demo-vault-v2/event-1on1-matteo-2024-04-17.md b/demo-vault-v2/event-1on1-matteo-2024-04-17.md deleted file mode 100644 index 6a845045..00000000 --- a/demo-vault-v2/event-1on1-matteo-2024-04-17.md +++ /dev/null @@ -1,21 +0,0 @@ ---- -aliases: ["1:1 Matteo — 2024-04-17"] -Is A: Event -Date: "2024-04-17" -Belongs to: "[[2024-04]]" -Related to: ["[[person-matteo-cellini]]"] -Tags: ["Work"] ---- -# 1:1 Matteo — 2024-04-17 -Bi-weekly 1:1. Covered sponsor pipeline and Q2 priorities. - -## Notes -- [[24q2-sponsor-crm]] implementation update — HubSpot pipeline configured with 5 stages -- Active sponsors: Deno, Neon, Notion — all performing well -- Discussed adding "dedicated edition" as top-tier offering at EUR 3500 -- Q1 sponsor renewals: 2/3 renewed — strong signal for value delivery -- Monthly sponsor revenue at EUR 4k — 20% above Q1 forecast - -## Follow-up -- [ ] [[person-luca-rossi]] to review dedicated edition pricing model -- [ ] [[person-matteo-cellini]] to send Q2 performance reports to all active sponsors diff --git a/demo-vault-v2/event-1on1-matteo-2024-05-01.md b/demo-vault-v2/event-1on1-matteo-2024-05-01.md deleted file mode 100644 index a2cbdd79..00000000 --- a/demo-vault-v2/event-1on1-matteo-2024-05-01.md +++ /dev/null @@ -1,19 +0,0 @@ ---- -aliases: ["1:1 Matteo — 2024-05-01"] -Is A: Event -Date: "2024-05-01" -Belongs to: "[[2024-05]]" -Related to: ["[[person-matteo-cellini]]"] -Tags: ["Work"] ---- -# 1:1 Matteo — 2024-05-01 -Bi-weekly 1:1. Covered sponsor pipeline and Q2 priorities. - -## Notes -- [[24q2-sponsor-crm]] implementation update — HubSpot pipeline configured with 5 stages -- Active sponsors: Vercel, Neon, Supabase — all performing well -- Q1 sponsor renewals: 2/3 renewed — strong signal for value delivery - -## Follow-up -- [ ] [[person-matteo-cellini]] to send Q2 performance reports to all active sponsors -- [ ] [[person-matteo-cellini]] to set up sponsor satisfaction survey diff --git a/demo-vault-v2/event-1on1-matteo-2024-05-15.md b/demo-vault-v2/event-1on1-matteo-2024-05-15.md deleted file mode 100644 index 0b64a511..00000000 --- a/demo-vault-v2/event-1on1-matteo-2024-05-15.md +++ /dev/null @@ -1,20 +0,0 @@ ---- -aliases: ["1:1 Matteo — 2024-05-15"] -Is A: Event -Date: "2024-05-15" -Belongs to: "[[2024-05]]" -Related to: ["[[person-matteo-cellini]]"] -Tags: ["Work"] ---- -# 1:1 Matteo — 2024-05-15 -Bi-weekly 1:1. Covered sponsor pipeline and Q2 priorities. - -## Notes -- Monthly sponsor revenue at EUR 4k — 15% above Q1 forecast -- Discussed adding "dedicated edition" as top-tier offering at EUR 3500 -- [[24q2-sponsor-crm]] implementation update — HubSpot pipeline configured with 5 stages -- Q1 sponsor renewals: 2/3 renewed — strong signal for value delivery - -## Follow-up -- [ ] [[person-luca-rossi]] to review dedicated edition pricing model -- [ ] [[person-matteo-cellini]] to set up sponsor satisfaction survey diff --git a/demo-vault-v2/event-1on1-matteo-2024-05-29.md b/demo-vault-v2/event-1on1-matteo-2024-05-29.md deleted file mode 100644 index 32a7f649..00000000 --- a/demo-vault-v2/event-1on1-matteo-2024-05-29.md +++ /dev/null @@ -1,20 +0,0 @@ ---- -aliases: ["1:1 Matteo — 2024-05-29"] -Is A: Event -Date: "2024-05-29" -Belongs to: "[[2024-05]]" -Related to: ["[[person-matteo-cellini]]"] -Tags: ["Work"] ---- -# 1:1 Matteo — 2024-05-29 -Bi-weekly 1:1. Covered sponsor pipeline and Q2 priorities. - -## Notes -- New lead from Retool — interested in Premium tier, scheduling demo -- Active sponsors: Neon, Fly.io, Railway — all performing well -- Monthly sponsor revenue at EUR 4k — 15% above Q1 forecast - -## Follow-up -- [ ] [[person-matteo-cellini]] to prepare renewal proposals for Q1 sponsors -- [ ] [[person-matteo-cellini]] to follow up on Deno demo request -- [ ] [[person-matteo-cellini]] to set up sponsor satisfaction survey diff --git a/demo-vault-v2/event-1on1-matteo-2024-06-12.md b/demo-vault-v2/event-1on1-matteo-2024-06-12.md deleted file mode 100644 index 1ea17a20..00000000 --- a/demo-vault-v2/event-1on1-matteo-2024-06-12.md +++ /dev/null @@ -1,19 +0,0 @@ ---- -aliases: ["1:1 Matteo — 2024-06-12"] -Is A: Event -Date: "2024-06-12" -Belongs to: "[[2024-06]]" -Related to: ["[[person-matteo-cellini]]"] -Tags: ["Work"] ---- -# 1:1 Matteo — 2024-06-12 -Bi-weekly 1:1. Covered sponsor pipeline and Q2 priorities. - -## Notes -- Discussed adding "dedicated edition" as top-tier offering at EUR 3500 -- [[24q2-sponsor-crm]] implementation update — HubSpot pipeline configured with 5 stages -- Sponsor feedback survey results: 4.2/5 satisfaction, main request is more detailed analytics - -## Follow-up -- [ ] [[person-matteo-cellini]] to prepare renewal proposals for Q1 sponsors -- [ ] [[person-luca-rossi]] to review dedicated edition pricing model diff --git a/demo-vault-v2/event-1on1-matteo-2024-06-26.md b/demo-vault-v2/event-1on1-matteo-2024-06-26.md deleted file mode 100644 index a2a4ac13..00000000 --- a/demo-vault-v2/event-1on1-matteo-2024-06-26.md +++ /dev/null @@ -1,21 +0,0 @@ ---- -aliases: ["1:1 Matteo — 2024-06-26"] -Is A: Event -Date: "2024-06-26" -Belongs to: "[[2024-06]]" -Related to: ["[[person-matteo-cellini]]"] -Tags: ["Work"] ---- -# 1:1 Matteo — 2024-06-26 -Bi-weekly 1:1. Covered sponsor pipeline and Q2 priorities. - -## Notes -- Sponsor feedback survey results: 4.2/5 satisfaction, main request is more detailed analytics -- Monthly sponsor revenue at EUR 5k — 20% above Q1 forecast -- Q1 sponsor renewals: 3/3 renewed — strong signal for value delivery -- [[24q2-sponsor-crm]] implementation update — HubSpot pipeline configured with 5 stages -- [[person-matteo-cellini]] building relationships at tech conferences — 3 warm intros expected - -## Follow-up -- [ ] [[person-matteo-cellini]] to follow up on Turso demo request -- [ ] [[person-matteo-cellini]] to send Q2 performance reports to all active sponsors diff --git a/demo-vault-v2/event-1on1-matteo-2024-07-10.md b/demo-vault-v2/event-1on1-matteo-2024-07-10.md deleted file mode 100644 index d16bb140..00000000 --- a/demo-vault-v2/event-1on1-matteo-2024-07-10.md +++ /dev/null @@ -1,21 +0,0 @@ ---- -aliases: ["1:1 Matteo — 2024-07-10"] -Is A: Event -Date: "2024-07-10" -Belongs to: "[[2024-07]]" -Related to: ["[[person-matteo-cellini]]"] -Tags: ["Work"] ---- -# 1:1 Matteo — 2024-07-10 -Bi-weekly 1:1. Covered sponsor pipeline and Q3 priorities. - -## Notes -- Renewal pipeline for Q4: 4 sponsors up for renewal, confidence high -- Explored bundling podcast sponsorship with newsletter — Vercel interested -- Pipeline has 7 active opportunities worth EUR 15k total -- Two sponsors requesting exclusivity in their category — need policy decision -- Tinybird signed annual contract — EUR 15k committed - -## Follow-up -- [ ] [[person-matteo-cellini]] to draft Q4 rate increase communication -- [ ] [[person-matteo-cellini]] to prepare exclusivity policy document diff --git a/demo-vault-v2/event-1on1-matteo-2024-07-24.md b/demo-vault-v2/event-1on1-matteo-2024-07-24.md deleted file mode 100644 index a06a7c66..00000000 --- a/demo-vault-v2/event-1on1-matteo-2024-07-24.md +++ /dev/null @@ -1,21 +0,0 @@ ---- -aliases: ["1:1 Matteo — 2024-07-24"] -Is A: Event -Date: "2024-07-24" -Belongs to: "[[2024-07]]" -Related to: ["[[person-matteo-cellini]]"] -Tags: ["Work"] ---- -# 1:1 Matteo — 2024-07-24 -Bi-weekly 1:1. Covered sponsor pipeline and Q3 priorities. - -## Notes -- Pipeline has 6 active opportunities worth EUR 20k total -- Inngest signed annual contract — EUR 15k committed -- Discussed Q4 rate increase with [[person-matteo-cellini]] — 15% proposed, he recommends phased approach -- Renewal pipeline for Q4: 5 sponsors up for renewal, confidence high - -## Follow-up -- [ ] [[person-matteo-cellini]] to schedule renewal calls for Q4 sponsors -- [ ] [[person-luca-rossi]] to approve podcast bundling pricing -- [ ] [[person-matteo-cellini]] to send pipeline forecast for Q4 diff --git a/demo-vault-v2/event-1on1-matteo-2024-08-07.md b/demo-vault-v2/event-1on1-matteo-2024-08-07.md deleted file mode 100644 index 10ba6a97..00000000 --- a/demo-vault-v2/event-1on1-matteo-2024-08-07.md +++ /dev/null @@ -1,21 +0,0 @@ ---- -aliases: ["1:1 Matteo — 2024-08-07"] -Is A: Event -Date: "2024-08-07" -Belongs to: "[[2024-08]]" -Related to: ["[[person-matteo-cellini]]"] -Tags: ["Work"] ---- -# 1:1 Matteo — 2024-08-07 -Bi-weekly 1:1. Covered sponsor pipeline and Q3 priorities. - -## Notes -- Pipeline has 7 active opportunities worth EUR 20k total -- Renewal pipeline for Q4: 4 sponsors up for renewal, confidence high -- Explored bundling podcast sponsorship with newsletter — Inngest interested -- Neon signed annual contract — EUR 12k committed - -## Follow-up -- [ ] [[person-luca-rossi]] to approve podcast bundling pricing -- [ ] [[person-matteo-cellini]] to draft Q4 rate increase communication -- [ ] [[person-matteo-cellini]] to prepare exclusivity policy document diff --git a/demo-vault-v2/event-1on1-matteo-2024-08-21.md b/demo-vault-v2/event-1on1-matteo-2024-08-21.md deleted file mode 100644 index ece4872d..00000000 --- a/demo-vault-v2/event-1on1-matteo-2024-08-21.md +++ /dev/null @@ -1,21 +0,0 @@ ---- -aliases: ["1:1 Matteo — 2024-08-21"] -Is A: Event -Date: "2024-08-21" -Belongs to: "[[2024-08]]" -Related to: ["[[person-matteo-cellini]]"] -Tags: ["Work"] ---- -# 1:1 Matteo — 2024-08-21 -Bi-weekly 1:1. Covered sponsor pipeline and Q3 priorities. - -## Notes -- Two sponsors requesting exclusivity in their category — need policy decision -- Sponsor ROI data looking strong — average CTR 2.8% vs industry 0.8% -- Discussed Q4 rate increase with [[person-matteo-cellini]] — 20% proposed, he recommends phased approach -- Notion signed annual contract — EUR 12k committed - -## Follow-up -- [ ] [[person-matteo-cellini]] to prepare exclusivity policy document -- [ ] [[person-matteo-cellini]] to schedule renewal calls for Q4 sponsors -- [ ] [[person-matteo-cellini]] to send pipeline forecast for Q4 diff --git a/demo-vault-v2/event-1on1-matteo-2024-09-04.md b/demo-vault-v2/event-1on1-matteo-2024-09-04.md deleted file mode 100644 index d79210d1..00000000 --- a/demo-vault-v2/event-1on1-matteo-2024-09-04.md +++ /dev/null @@ -1,21 +0,0 @@ ---- -aliases: ["1:1 Matteo — 2024-09-04"] -Is A: Event -Date: "2024-09-04" -Belongs to: "[[2024-09]]" -Related to: ["[[person-matteo-cellini]]"] -Tags: ["Work"] ---- -# 1:1 Matteo — 2024-09-04 -Bi-weekly 1:1. Covered sponsor pipeline and Q3 priorities. - -## Notes -- Sponsor ROI data looking strong — average CTR 2.8% vs industry 0.8% -- Two sponsors requesting exclusivity in their category — need policy decision -- Renewal pipeline for Q4: 4 sponsors up for renewal, confidence high -- Discussed Q4 rate increase with [[person-matteo-cellini]] — 20% proposed, he recommends phased approach -- Explored bundling podcast sponsorship with newsletter — Deno interested - -## Follow-up -- [ ] [[person-matteo-cellini]] to schedule renewal calls for Q4 sponsors -- [ ] [[person-matteo-cellini]] to draft Q4 rate increase communication diff --git a/demo-vault-v2/event-1on1-matteo-2024-09-18.md b/demo-vault-v2/event-1on1-matteo-2024-09-18.md deleted file mode 100644 index b8944646..00000000 --- a/demo-vault-v2/event-1on1-matteo-2024-09-18.md +++ /dev/null @@ -1,20 +0,0 @@ ---- -aliases: ["1:1 Matteo — 2024-09-18"] -Is A: Event -Date: "2024-09-18" -Belongs to: "[[2024-09]]" -Related to: ["[[person-matteo-cellini]]"] -Tags: ["Work"] ---- -# 1:1 Matteo — 2024-09-18 -Bi-weekly 1:1. Covered sponsor pipeline and Q3 priorities. - -## Notes -- [[24q3-premium-tier]] could unlock "Premium Sponsor" slot at higher rate -- Sponsor ROI data looking strong — average CTR 2.1% vs industry 1.0% -- Explored bundling podcast sponsorship with newsletter — Convex interested - -## Follow-up -- [ ] [[person-luca-rossi]] to approve podcast bundling pricing -- [ ] [[person-matteo-cellini]] to schedule renewal calls for Q4 sponsors -- [ ] [[person-matteo-cellini]] to send pipeline forecast for Q4 diff --git a/demo-vault-v2/event-1on1-matteo-2024-10-02.md b/demo-vault-v2/event-1on1-matteo-2024-10-02.md deleted file mode 100644 index c1a7574e..00000000 --- a/demo-vault-v2/event-1on1-matteo-2024-10-02.md +++ /dev/null @@ -1,19 +0,0 @@ ---- -aliases: ["1:1 Matteo — 2024-10-02"] -Is A: Event -Date: "2024-10-02" -Belongs to: "[[2024-10]]" -Related to: ["[[person-matteo-cellini]]"] -Tags: ["Work"] ---- -# 1:1 Matteo — 2024-10-02 -Bi-weekly 1:1. Covered sponsor pipeline and Q4 priorities. - -## Notes -- 2025 rate card review: Basic EUR 800, Standard EUR 1800, Premium EUR 3000 -- Discussed sponsoring our own community events for sponsor visibility -- [[person-matteo-cellini]] negotiating 4 annual contracts for 2025 — total value EUR 40k - -## Follow-up -- [ ] [[person-luca-rossi]] to approve new rate card -- [ ] [[person-matteo-cellini]] to finalize 2025 annual contracts by Dec 15 diff --git a/demo-vault-v2/event-1on1-matteo-2024-10-16.md b/demo-vault-v2/event-1on1-matteo-2024-10-16.md deleted file mode 100644 index 5f995b6a..00000000 --- a/demo-vault-v2/event-1on1-matteo-2024-10-16.md +++ /dev/null @@ -1,21 +0,0 @@ ---- -aliases: ["1:1 Matteo — 2024-10-16"] -Is A: Event -Date: "2024-10-16" -Belongs to: "[[2024-10]]" -Related to: ["[[person-matteo-cellini]]"] -Tags: ["Work"] ---- -# 1:1 Matteo — 2024-10-16 -Bi-weekly 1:1. Covered sponsor pipeline and Q4 priorities. - -## Notes -- Discussed sponsoring our own community events for sponsor visibility -- Sponsor pipeline for Q1 2025: 8 warm leads, 3 in contract stage -- [[person-matteo-cellini]] negotiating 3 annual contracts for 2025 — total value EUR 35k -- 2025 rate card review: Basic EUR 900, Standard EUR 1800, Premium EUR 3000 -- 2024 total sponsor revenue on track for EUR 55k — exceeding initial target of EUR 45k - -## Follow-up -- [ ] [[person-matteo-cellini]] to order sponsor appreciation gifts -- [ ] [[person-matteo-cellini]] to send year-end thank you notes to all 2024 sponsors diff --git a/demo-vault-v2/event-1on1-matteo-2024-10-30.md b/demo-vault-v2/event-1on1-matteo-2024-10-30.md deleted file mode 100644 index 92c3522e..00000000 --- a/demo-vault-v2/event-1on1-matteo-2024-10-30.md +++ /dev/null @@ -1,20 +0,0 @@ ---- -aliases: ["1:1 Matteo — 2024-10-30"] -Is A: Event -Date: "2024-10-30" -Belongs to: "[[2024-10]]" -Related to: ["[[person-matteo-cellini]]"] -Tags: ["Work"] ---- -# 1:1 Matteo — 2024-10-30 -Bi-weekly 1:1. Covered sponsor pipeline and Q4 priorities. - -## Notes -- Reviewed 2024 learnings: longer commitments = better ROI for sponsors and us -- Sponsor pipeline for Q1 2025: 10 warm leads, 4 in contract stage -- Planning sponsor appreciation gifts for year-end — budget EUR 500 -- [[person-matteo-cellini]] negotiating 3 annual contracts for 2025 — total value EUR 40k - -## Follow-up -- [ ] [[person-luca-rossi]] to approve new rate card -- [ ] [[person-matteo-cellini]] to prepare 2025 Q1 forecast diff --git a/demo-vault-v2/event-1on1-matteo-2024-11-13.md b/demo-vault-v2/event-1on1-matteo-2024-11-13.md deleted file mode 100644 index a224fe27..00000000 --- a/demo-vault-v2/event-1on1-matteo-2024-11-13.md +++ /dev/null @@ -1,19 +0,0 @@ ---- -aliases: ["1:1 Matteo — 2024-11-13"] -Is A: Event -Date: "2024-11-13" -Belongs to: "[[2024-11]]" -Related to: ["[[person-matteo-cellini]]"] -Tags: ["Work"] ---- -# 1:1 Matteo — 2024-11-13 -Bi-weekly 1:1. Covered sponsor pipeline and Q4 priorities. - -## Notes -- Reviewed 2024 learnings: longer commitments = better ROI for sponsors and us -- 2025 rate card review: Basic EUR 800, Standard EUR 1500, Premium EUR 3000 -- [[person-matteo-cellini]] negotiating 3 annual contracts for 2025 — total value EUR 45k - -## Follow-up -- [ ] [[person-matteo-cellini]] to send year-end thank you notes to all 2024 sponsors -- [ ] [[person-matteo-cellini]] to order sponsor appreciation gifts diff --git a/demo-vault-v2/event-1on1-matteo-2024-11-27.md b/demo-vault-v2/event-1on1-matteo-2024-11-27.md deleted file mode 100644 index 67e8af87..00000000 --- a/demo-vault-v2/event-1on1-matteo-2024-11-27.md +++ /dev/null @@ -1,20 +0,0 @@ ---- -aliases: ["1:1 Matteo — 2024-11-27"] -Is A: Event -Date: "2024-11-27" -Belongs to: "[[2024-11]]" -Related to: ["[[person-matteo-cellini]]"] -Tags: ["Work"] ---- -# 1:1 Matteo — 2024-11-27 -Bi-weekly 1:1. Covered sponsor pipeline and Q4 priorities. - -## Notes -- Planning sponsor appreciation gifts for year-end — budget EUR 500 -- 2025 rate card review: Basic EUR 900, Standard EUR 1500, Premium EUR 3000 -- 2024 total sponsor revenue on track for EUR 55k — exceeding initial target of EUR 45k - -## Follow-up -- [ ] [[person-matteo-cellini]] to prepare 2025 Q1 forecast -- [ ] [[person-matteo-cellini]] to finalize 2025 annual contracts by Dec 15 -- [ ] [[person-matteo-cellini]] to send year-end thank you notes to all 2024 sponsors diff --git a/demo-vault-v2/event-1on1-matteo-2024-12-11.md b/demo-vault-v2/event-1on1-matteo-2024-12-11.md deleted file mode 100644 index 07d3463a..00000000 --- a/demo-vault-v2/event-1on1-matteo-2024-12-11.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -aliases: ["1:1 Matteo — 2024-12-11"] -Is A: Event -Date: "2024-12-11" -Belongs to: "[[2024-12]]" -Related to: ["[[person-matteo-cellini]]"] -Tags: ["Work"] ---- -# 1:1 Matteo — 2024-12-11 -Bi-weekly 1:1. Covered sponsor pipeline and Q4 priorities. - -## Notes -- Reviewed 2024 learnings: longer commitments = better ROI for sponsors and us -- [[person-matteo-cellini]] negotiating 4 annual contracts for 2025 — total value EUR 35k -- Category exclusivity policy finalized — max 1 sponsor per vertical, 20% premium -- Sponsor pipeline for Q1 2025: 10 warm leads, 3 in contract stage -- 2024 total sponsor revenue on track for EUR 65k — exceeding initial target of EUR 45k - -## Follow-up -- [ ] [[person-matteo-cellini]] to finalize 2025 annual contracts by Dec 15 -- [ ] [[person-matteo-cellini]] to send year-end thank you notes to all 2024 sponsors -- [ ] [[person-matteo-cellini]] to prepare 2025 Q1 forecast diff --git a/demo-vault-v2/event-1on1-matteo-2024-12-25.md b/demo-vault-v2/event-1on1-matteo-2024-12-25.md deleted file mode 100644 index 87dc65dc..00000000 --- a/demo-vault-v2/event-1on1-matteo-2024-12-25.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -aliases: ["1:1 Matteo — 2024-12-25"] -Is A: Event -Date: "2024-12-25" -Belongs to: "[[2024-12]]" -Related to: ["[[person-matteo-cellini]]"] -Tags: ["Work"] ---- -# 1:1 Matteo — 2024-12-25 -Bi-weekly 1:1. Covered sponsor pipeline and Q4 priorities. - -## Notes -- Discussed sponsoring our own community events for sponsor visibility -- Planning sponsor appreciation gifts for year-end — budget EUR 500 -- 2024 total sponsor revenue on track for EUR 55k — exceeding initial target of EUR 45k -- 2025 rate card review: Basic EUR 900, Standard EUR 1500, Premium EUR 3500 -- Reviewed 2024 learnings: longer commitments = better ROI for sponsors and us - -## Follow-up -- [ ] [[person-matteo-cellini]] to finalize 2025 annual contracts by Dec 15 -- [ ] [[person-matteo-cellini]] to send year-end thank you notes to all 2024 sponsors -- [ ] [[person-matteo-cellini]] to order sponsor appreciation gifts diff --git a/demo-vault-v2/event-1on1-matteo-2025-01-08.md b/demo-vault-v2/event-1on1-matteo-2025-01-08.md deleted file mode 100644 index ce48c1ac..00000000 --- a/demo-vault-v2/event-1on1-matteo-2025-01-08.md +++ /dev/null @@ -1,20 +0,0 @@ ---- -aliases: ["1:1 Matteo — 2025-01-08"] -Is A: Event -Date: "2025-01-08" -Belongs to: "[[2025-01]]" -Related to: ["[[person-matteo-cellini]]"] -Tags: ["Work"] ---- -# 1:1 Matteo — 2025-01-08 -Bi-weekly 1:1. Covered sponsor pipeline and Q1 priorities. - -## Notes -- Discussed enterprise tier for larger companies — minimum EUR 6k/month, 6-month minimum -- Q1 2025 starting strong — 7 confirmed sponsors, 4 more in negotiation -- New rate card in effect — no pushback from existing sponsors, 3 new sponsors at higher rates - -## Follow-up -- [ ] [[person-luca-rossi]] to review affiliate model proposal -- [ ] [[person-matteo-cellini]] to onboard new sponsors with updated welcome kit -- [ ] [[person-matteo-cellini]] to prepare Q1 sponsor performance reports diff --git a/demo-vault-v2/event-1on1-matteo-2025-01-22.md b/demo-vault-v2/event-1on1-matteo-2025-01-22.md deleted file mode 100644 index b7d2193b..00000000 --- a/demo-vault-v2/event-1on1-matteo-2025-01-22.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -aliases: ["1:1 Matteo — 2025-01-22"] -Is A: Event -Date: "2025-01-22" -Belongs to: "[[2025-01]]" -Related to: ["[[person-matteo-cellini]]"] -Tags: ["Work"] ---- -# 1:1 Matteo — 2025-01-22 -Bi-weekly 1:1. Covered sponsor pipeline and Q1 priorities. - -## Notes -- Podcast sponsorship bundle proving popular — 3 sponsors opted in -- Exploring affiliate/performance-based model as complement to flat-rate sponsorships -- Monthly revenue now EUR 7k — up 40% year-over-year -- [[person-matteo-cellini]] attending 3 conferences in Q1 for business development -- [[25q1-referral-program]] creating organic buzz — sponsors noticing growth acceleration - -## Follow-up -- [ ] [[person-matteo-cellini]] to prepare Q1 sponsor performance reports -- [ ] [[person-matteo-cellini]] to follow up on enterprise tier proposals -- [ ] [[person-matteo-cellini]] to onboard new sponsors with updated welcome kit diff --git a/demo-vault-v2/event-1on1-matteo-2025-02-05.md b/demo-vault-v2/event-1on1-matteo-2025-02-05.md deleted file mode 100644 index 0e3a9ef1..00000000 --- a/demo-vault-v2/event-1on1-matteo-2025-02-05.md +++ /dev/null @@ -1,20 +0,0 @@ ---- -aliases: ["1:1 Matteo — 2025-02-05"] -Is A: Event -Date: "2025-02-05" -Belongs to: "[[2025-02]]" -Related to: ["[[person-matteo-cellini]]"] -Tags: ["Work"] ---- -# 1:1 Matteo — 2025-02-05 -Bi-weekly 1:1. Covered sponsor pipeline and Q1 priorities. - -## Notes -- Q1 2025 starting strong — 8 confirmed sponsors, 4 more in negotiation -- Exploring affiliate/performance-based model as complement to flat-rate sponsorships -- New rate card in effect — no pushback from existing sponsors, 3 new sponsors at higher rates - -## Follow-up -- [ ] [[person-matteo-cellini]] to prepare Q1 sponsor performance reports -- [ ] [[person-luca-rossi]] to review affiliate model proposal -- [ ] [[person-matteo-cellini]] to follow up on enterprise tier proposals diff --git a/demo-vault-v2/event-1on1-matteo-2025-02-19.md b/demo-vault-v2/event-1on1-matteo-2025-02-19.md deleted file mode 100644 index a16126c9..00000000 --- a/demo-vault-v2/event-1on1-matteo-2025-02-19.md +++ /dev/null @@ -1,19 +0,0 @@ ---- -aliases: ["1:1 Matteo — 2025-02-19"] -Is A: Event -Date: "2025-02-19" -Belongs to: "[[2025-02]]" -Related to: ["[[person-matteo-cellini]]"] -Tags: ["Work"] ---- -# 1:1 Matteo — 2025-02-19 -Bi-weekly 1:1. Covered sponsor pipeline and Q1 priorities. - -## Notes -- Monthly revenue now EUR 7k — up 50% year-over-year -- [[person-matteo-cellini]] attending 2 conferences in Q1 for business development -- [[25q1-referral-program]] creating organic buzz — sponsors noticing growth acceleration - -## Follow-up -- [ ] [[person-luca-rossi]] to review affiliate model proposal -- [ ] [[person-matteo-cellini]] to follow up on enterprise tier proposals diff --git a/demo-vault-v2/event-1on1-matteo-2025-03-05.md b/demo-vault-v2/event-1on1-matteo-2025-03-05.md deleted file mode 100644 index 950e9ac1..00000000 --- a/demo-vault-v2/event-1on1-matteo-2025-03-05.md +++ /dev/null @@ -1,21 +0,0 @@ ---- -aliases: ["1:1 Matteo — 2025-03-05"] -Is A: Event -Date: "2025-03-05" -Belongs to: "[[2025-03]]" -Related to: ["[[person-matteo-cellini]]"] -Tags: ["Work"] ---- -# 1:1 Matteo — 2025-03-05 -Bi-weekly 1:1. Covered sponsor pipeline and Q1 priorities. - -## Notes -- [[25q1-referral-program]] creating organic buzz — sponsors noticing growth acceleration -- Exploring affiliate/performance-based model as complement to flat-rate sponsorships -- Monthly revenue now EUR 8k — up 50% year-over-year -- [[person-matteo-cellini]] attending 2 conferences in Q1 for business development -- Podcast sponsorship bundle proving popular — 3 sponsors opted in - -## Follow-up -- [ ] [[person-matteo-cellini]] to onboard new sponsors with updated welcome kit -- [ ] [[person-luca-rossi]] to review affiliate model proposal diff --git a/demo-vault-v2/event-1on1-matteo-2025-03-19.md b/demo-vault-v2/event-1on1-matteo-2025-03-19.md deleted file mode 100644 index 5cd6fb73..00000000 --- a/demo-vault-v2/event-1on1-matteo-2025-03-19.md +++ /dev/null @@ -1,20 +0,0 @@ ---- -aliases: ["1:1 Matteo — 2025-03-19"] -Is A: Event -Date: "2025-03-19" -Belongs to: "[[2025-03]]" -Related to: ["[[person-matteo-cellini]]"] -Tags: ["Work"] ---- -# 1:1 Matteo — 2025-03-19 -Bi-weekly 1:1. Covered sponsor pipeline and Q1 priorities. - -## Notes -- Monthly revenue now EUR 7k — up 50% year-over-year -- New rate card in effect — no pushback from existing sponsors, 2 new sponsors at higher rates -- Exploring affiliate/performance-based model as complement to flat-rate sponsorships -- [[person-matteo-cellini]] attending 3 conferences in Q1 for business development - -## Follow-up -- [ ] [[person-matteo-cellini]] to attend SaaStr Europe conference for lead gen -- [ ] [[person-matteo-cellini]] to onboard new sponsors with updated welcome kit diff --git a/demo-vault-v2/event-1on1-matteo-2025-04-02.md b/demo-vault-v2/event-1on1-matteo-2025-04-02.md deleted file mode 100644 index 56bc0fe2..00000000 --- a/demo-vault-v2/event-1on1-matteo-2025-04-02.md +++ /dev/null @@ -1,21 +0,0 @@ ---- -aliases: ["1:1 Matteo — 2025-04-02"] -Is A: Event -Date: "2025-04-02" -Belongs to: "[[2025-04]]" -Related to: ["[[person-matteo-cellini]]"] -Tags: ["Work"] ---- -# 1:1 Matteo — 2025-04-02 -Bi-weekly 1:1. Covered sponsor pipeline and Q2 priorities. - -## Notes -- Exploring international sponsor outreach — US-based companies showing interest -- Sponsor satisfaction at 4.5/5 — highest ever -- Waitlist management process formalized — transparent queue with estimated slot dates -- Conference sponsorship packages being developed for fall event -- Community sponsorship tier launched — sponsors can host AMA sessions - -## Follow-up -- [ ] [[person-matteo-cellini]] to develop conference sponsorship packages -- [ ] [[person-matteo-cellini]] to send mid-year performance reports to all sponsors diff --git a/demo-vault-v2/event-1on1-matteo-2025-04-16.md b/demo-vault-v2/event-1on1-matteo-2025-04-16.md deleted file mode 100644 index 512726fa..00000000 --- a/demo-vault-v2/event-1on1-matteo-2025-04-16.md +++ /dev/null @@ -1,20 +0,0 @@ ---- -aliases: ["1:1 Matteo — 2025-04-16"] -Is A: Event -Date: "2025-04-16" -Belongs to: "[[2025-04]]" -Related to: ["[[person-matteo-cellini]]"] -Tags: ["Work"] ---- -# 1:1 Matteo — 2025-04-16 -Bi-weekly 1:1. Covered sponsor pipeline and Q2 priorities. - -## Notes -- Community sponsorship tier launched — sponsors can host AMA sessions -- Conference sponsorship packages being developed for fall event -- Sponsor satisfaction at 4.7/5 — highest ever -- [[person-matteo-cellini]] closed Fly.io on annual deal worth EUR 24k - -## Follow-up -- [ ] [[person-matteo-cellini]] to manage sponsor waitlist communications -- [ ] [[person-matteo-cellini]] to develop conference sponsorship packages diff --git a/demo-vault-v2/event-1on1-matteo-2025-04-30.md b/demo-vault-v2/event-1on1-matteo-2025-04-30.md deleted file mode 100644 index 41bda896..00000000 --- a/demo-vault-v2/event-1on1-matteo-2025-04-30.md +++ /dev/null @@ -1,19 +0,0 @@ ---- -aliases: ["1:1 Matteo — 2025-04-30"] -Is A: Event -Date: "2025-04-30" -Belongs to: "[[2025-04]]" -Related to: ["[[person-matteo-cellini]]"] -Tags: ["Work"] ---- -# 1:1 Matteo — 2025-04-30 -Bi-weekly 1:1. Covered sponsor pipeline and Q2 priorities. - -## Notes -- Revenue run rate at EUR 12k/month — projecting EUR 140k for full year -- Waitlist management process formalized — transparent queue with estimated slot dates -- Conference sponsorship packages being developed for fall event - -## Follow-up -- [ ] [[person-matteo-cellini]] to explore US market outreach strategy -- [ ] [[person-luca-rossi]] to approve community AMA sponsorship pricing diff --git a/demo-vault-v2/event-1on1-matteo-2025-05-14.md b/demo-vault-v2/event-1on1-matteo-2025-05-14.md deleted file mode 100644 index 9914dd6e..00000000 --- a/demo-vault-v2/event-1on1-matteo-2025-05-14.md +++ /dev/null @@ -1,20 +0,0 @@ ---- -aliases: ["1:1 Matteo — 2025-05-14"] -Is A: Event -Date: "2025-05-14" -Belongs to: "[[2025-05]]" -Related to: ["[[person-matteo-cellini]]"] -Tags: ["Work"] ---- -# 1:1 Matteo — 2025-05-14 -Bi-weekly 1:1. Covered sponsor pipeline and Q2 priorities. - -## Notes -- Revenue run rate at EUR 14k/month — projecting EUR 140k for full year -- Sponsor satisfaction at 4.5/5 — highest ever -- Waitlist management process formalized — transparent queue with estimated slot dates - -## Follow-up -- [ ] [[person-matteo-cellini]] to develop conference sponsorship packages -- [ ] [[person-luca-rossi]] to approve community AMA sponsorship pricing -- [ ] [[person-matteo-cellini]] to manage sponsor waitlist communications diff --git a/demo-vault-v2/event-1on1-matteo-2025-05-28.md b/demo-vault-v2/event-1on1-matteo-2025-05-28.md deleted file mode 100644 index 0ea521b1..00000000 --- a/demo-vault-v2/event-1on1-matteo-2025-05-28.md +++ /dev/null @@ -1,19 +0,0 @@ ---- -aliases: ["1:1 Matteo — 2025-05-28"] -Is A: Event -Date: "2025-05-28" -Belongs to: "[[2025-05]]" -Related to: ["[[person-matteo-cellini]]"] -Tags: ["Work"] ---- -# 1:1 Matteo — 2025-05-28 -Bi-weekly 1:1. Covered sponsor pipeline and Q2 priorities. - -## Notes -- Waitlist management process formalized — transparent queue with estimated slot dates -- Community sponsorship tier launched — sponsors can host AMA sessions -- [[person-matteo-cellini]] closed Turso on annual deal worth EUR 18k - -## Follow-up -- [ ] [[person-matteo-cellini]] to manage sponsor waitlist communications -- [ ] [[person-matteo-cellini]] to explore US market outreach strategy diff --git a/demo-vault-v2/event-1on1-matteo-2025-06-11.md b/demo-vault-v2/event-1on1-matteo-2025-06-11.md deleted file mode 100644 index 8fb0fac5..00000000 --- a/demo-vault-v2/event-1on1-matteo-2025-06-11.md +++ /dev/null @@ -1,20 +0,0 @@ ---- -aliases: ["1:1 Matteo — 2025-06-11"] -Is A: Event -Date: "2025-06-11" -Belongs to: "[[2025-06]]" -Related to: ["[[person-matteo-cellini]]"] -Tags: ["Work"] ---- -# 1:1 Matteo — 2025-06-11 -Bi-weekly 1:1. Covered sponsor pipeline and Q2 priorities. - -## Notes -- Waitlist management process formalized — transparent queue with estimated slot dates -- Revenue run rate at EUR 10k/month — projecting EUR 140k for full year -- [[person-matteo-cellini]] closed Resend on annual deal worth EUR 20k - -## Follow-up -- [ ] [[person-luca-rossi]] to approve community AMA sponsorship pricing -- [ ] [[person-matteo-cellini]] to develop conference sponsorship packages -- [ ] [[person-matteo-cellini]] to send mid-year performance reports to all sponsors diff --git a/demo-vault-v2/event-1on1-paco-2024-01-04.md b/demo-vault-v2/event-1on1-paco-2024-01-04.md deleted file mode 100644 index 0537f44d..00000000 --- a/demo-vault-v2/event-1on1-paco-2024-01-04.md +++ /dev/null @@ -1,20 +0,0 @@ ---- -aliases: ["1:1 Paco — 2024-01-04"] -Is A: Event -Date: "2024-01-04" -Belongs to: "[[2024-01]]" -Related to: ["[[person-paco-furiani]]"] -Tags: ["Work"] ---- -# 1:1 Paco — 2024-01-04 -Monthly 1:1. Operations review, tooling updates, and process improvements. - -## Notes -- Discussed automation for sponsor link tracking — UTM parameters standardized -- Set up Google Analytics 4 tracking for newsletter landing page — 2.5k monthly visitors -- Set up Zapier integrations between Beehiiv and Google Sheets for subscriber data - -## Follow-up -- [ ] [[person-paco-furiani]] to complete CRM evaluation and present recommendation -- [ ] [[person-paco-furiani]] to set up automated subscriber growth alerts -- [ ] [[person-paco-furiani]] to finalize UTM tracking documentation for sponsors diff --git a/demo-vault-v2/event-1on1-paco-2024-02-01.md b/demo-vault-v2/event-1on1-paco-2024-02-01.md deleted file mode 100644 index 87f64076..00000000 --- a/demo-vault-v2/event-1on1-paco-2024-02-01.md +++ /dev/null @@ -1,21 +0,0 @@ ---- -aliases: ["1:1 Paco — 2024-02-01"] -Is A: Event -Date: "2024-02-01" -Belongs to: "[[2024-02]]" -Related to: ["[[person-paco-furiani]]"] -Tags: ["Work"] ---- -# 1:1 Paco — 2024-02-01 -Monthly 1:1. Operations review, tooling updates, and process improvements. - -## Notes -- Set up Zapier integrations between Beehiiv and Google Sheets for subscriber data -- Set up Google Analytics 4 tracking for newsletter landing page — 2.1k monthly visitors -- Email deliverability at 97.8% — monitoring closely after migration -- Evaluated CRM options for sponsor management — shortlisted HubSpot, Pipedrive, Attio - -## Follow-up -- [ ] [[person-paco-furiani]] to complete CRM evaluation and present recommendation -- [ ] [[person-paco-furiani]] to configure DMARC reporting for deliverability monitoring -- [ ] [[person-luca-rossi]] to review Notion workspace structure diff --git a/demo-vault-v2/event-1on1-paco-2024-03-07.md b/demo-vault-v2/event-1on1-paco-2024-03-07.md deleted file mode 100644 index 233b3c48..00000000 --- a/demo-vault-v2/event-1on1-paco-2024-03-07.md +++ /dev/null @@ -1,21 +0,0 @@ ---- -aliases: ["1:1 Paco — 2024-03-07"] -Is A: Event -Date: "2024-03-07" -Belongs to: "[[2024-03]]" -Related to: ["[[person-paco-furiani]]"] -Tags: ["Work"] ---- -# 1:1 Paco — 2024-03-07 -Monthly 1:1. Operations review, tooling updates, and process improvements. - -## Notes -- Beehiiv setup finalized — all automations tested, welcome sequence performing at 62% open rate -- Email deliverability at 97.8% — monitoring closely after migration -- DNS and email authentication (DKIM, SPF, DMARC) verified for new sending domain -- Set up Zapier integrations between Beehiiv and Google Sheets for subscriber data -- Discussed automation for sponsor link tracking — UTM parameters standardized - -## Follow-up -- [ ] [[person-paco-furiani]] to set up automated subscriber growth alerts -- [ ] [[person-paco-furiani]] to complete CRM evaluation and present recommendation diff --git a/demo-vault-v2/event-1on1-paco-2024-04-04.md b/demo-vault-v2/event-1on1-paco-2024-04-04.md deleted file mode 100644 index ea51e0f0..00000000 --- a/demo-vault-v2/event-1on1-paco-2024-04-04.md +++ /dev/null @@ -1,21 +0,0 @@ ---- -aliases: ["1:1 Paco — 2024-04-04"] -Is A: Event -Date: "2024-04-04" -Belongs to: "[[2024-04]]" -Related to: ["[[person-paco-furiani]]"] -Tags: ["Work"] ---- -# 1:1 Paco — 2024-04-04 -Monthly 1:1. Operations review, tooling updates, and process improvements. - -## Notes -- CRM migration to HubSpot complete — [[person-paco-furiani]] trained [[person-matteo-cellini]] on pipeline views -- Built automated sponsor invoice generation using Zapier + Google Docs templates -- Email deliverability improved to 98.3% after sender reputation warmup -- Podcast hosting on Transistor set up — RSS feed connected to all major platforms -- Implemented A/B testing framework in Beehiiv — testing subject lines and send times - -## Follow-up -- [ ] [[person-paco-furiani]] to automate podcast RSS feed verification -- [ ] [[person-paco-furiani]] to train team on HubSpot pipeline management diff --git a/demo-vault-v2/event-1on1-paco-2024-05-02.md b/demo-vault-v2/event-1on1-paco-2024-05-02.md deleted file mode 100644 index adfbe7a1..00000000 --- a/demo-vault-v2/event-1on1-paco-2024-05-02.md +++ /dev/null @@ -1,21 +0,0 @@ ---- -aliases: ["1:1 Paco — 2024-05-02"] -Is A: Event -Date: "2024-05-02" -Belongs to: "[[2024-05]]" -Related to: ["[[person-paco-furiani]]"] -Tags: ["Work"] ---- -# 1:1 Paco — 2024-05-02 -Monthly 1:1. Operations review, tooling updates, and process improvements. - -## Notes -- Podcast hosting on Transistor set up — RSS feed connected to all major platforms -- Email deliverability improved to 98.6% after sender reputation warmup -- Built automated sponsor invoice generation using Zapier + Google Docs templates -- Discussed migrating from Notion to dedicated project management tool -- CRM migration to HubSpot complete — [[person-paco-furiani]] trained [[person-matteo-cellini]] on pipeline views - -## Follow-up -- [ ] [[person-paco-furiani]] to create sponsor onboarding checklist in Notion -- [ ] [[person-luca-rossi]] to approve analytics dashboard access levels diff --git a/demo-vault-v2/event-1on1-paco-2024-06-06.md b/demo-vault-v2/event-1on1-paco-2024-06-06.md deleted file mode 100644 index 213a66e6..00000000 --- a/demo-vault-v2/event-1on1-paco-2024-06-06.md +++ /dev/null @@ -1,21 +0,0 @@ ---- -aliases: ["1:1 Paco — 2024-06-06"] -Is A: Event -Date: "2024-06-06" -Belongs to: "[[2024-06]]" -Related to: ["[[person-paco-furiani]]"] -Tags: ["Work"] ---- -# 1:1 Paco — 2024-06-06 -Monthly 1:1. Operations review, tooling updates, and process improvements. - -## Notes -- Analytics dashboard v2 live — now tracking open rate, CTR, growth rate, and churn -- Automated weekly subscriber growth report — sent to team every Monday -- Podcast hosting on Transistor set up — RSS feed connected to all major platforms -- Built automated sponsor invoice generation using Zapier + Google Docs templates - -## Follow-up -- [ ] [[person-paco-furiani]] to document A/B testing methodology and results -- [ ] [[person-paco-furiani]] to automate podcast RSS feed verification -- [ ] [[person-paco-furiani]] to create sponsor onboarding checklist in Notion diff --git a/demo-vault-v2/event-1on1-paco-2024-07-04.md b/demo-vault-v2/event-1on1-paco-2024-07-04.md deleted file mode 100644 index 44fc8ccf..00000000 --- a/demo-vault-v2/event-1on1-paco-2024-07-04.md +++ /dev/null @@ -1,20 +0,0 @@ ---- -aliases: ["1:1 Paco — 2024-07-04"] -Is A: Event -Date: "2024-07-04" -Belongs to: "[[2024-07]]" -Related to: ["[[person-paco-furiani]]"] -Tags: ["Work"] ---- -# 1:1 Paco — 2024-07-04 -Monthly 1:1. Operations review, tooling updates, and process improvements. - -## Notes -- Payment integration research for [[24q3-premium-tier]] — evaluating Stripe vs Lemon Squeezy -- Built sponsor ROI dashboard — auto-pulls click data from Beehiiv API -- Implemented subscriber segmentation by engagement level (active, casual, at-risk) - -## Follow-up -- [ ] [[person-paco-furiani]] to complete Stripe integration testing for premium tier -- [ ] [[person-paco-furiani]] to build sponsor ROI calculation template -- [ ] [[person-luca-rossi]] to review infrastructure budget proposal diff --git a/demo-vault-v2/event-1on1-paco-2024-08-01.md b/demo-vault-v2/event-1on1-paco-2024-08-01.md deleted file mode 100644 index e76164fe..00000000 --- a/demo-vault-v2/event-1on1-paco-2024-08-01.md +++ /dev/null @@ -1,21 +0,0 @@ ---- -aliases: ["1:1 Paco — 2024-08-01"] -Is A: Event -Date: "2024-08-01" -Belongs to: "[[2024-08]]" -Related to: ["[[person-paco-furiani]]"] -Tags: ["Work"] ---- -# 1:1 Paco — 2024-08-01 -Monthly 1:1. Operations review, tooling updates, and process improvements. - -## Notes -- Set up automated podcast episode publishing pipeline — record to publish in 48h -- Built sponsor ROI dashboard — auto-pulls click data from Beehiiv API -- Evaluated social media scheduling tools — selected Buffer for cross-platform posting -- Payment integration research for [[24q3-premium-tier]] — evaluating Stripe vs Lemon Squeezy -- Email list hygiene: removed 800 inactive subscribers, deliverability now 98.7% - -## Follow-up -- [ ] [[person-paco-furiani]] to build sponsor ROI calculation template -- [ ] [[person-paco-furiani]] to set up Buffer for social media scheduling diff --git a/demo-vault-v2/event-1on1-paco-2024-09-05.md b/demo-vault-v2/event-1on1-paco-2024-09-05.md deleted file mode 100644 index d6d4798c..00000000 --- a/demo-vault-v2/event-1on1-paco-2024-09-05.md +++ /dev/null @@ -1,20 +0,0 @@ ---- -aliases: ["1:1 Paco — 2024-09-05"] -Is A: Event -Date: "2024-09-05" -Belongs to: "[[2024-09]]" -Related to: ["[[person-paco-furiani]]"] -Tags: ["Work"] ---- -# 1:1 Paco — 2024-09-05 -Monthly 1:1. Operations review, tooling updates, and process improvements. - -## Notes -- Website performance audit — page load under 1.8s, Core Web Vitals passing -- Set up automated podcast episode publishing pipeline — record to publish in 48h -- Payment integration research for [[24q3-premium-tier]] — evaluating Stripe vs Lemon Squeezy - -## Follow-up -- [ ] [[person-paco-furiani]] to complete Stripe integration testing for premium tier -- [ ] [[person-luca-rossi]] to review infrastructure budget proposal -- [ ] [[person-paco-furiani]] to implement subscriber re-engagement automation diff --git a/demo-vault-v2/event-1on1-paco-2024-10-03.md b/demo-vault-v2/event-1on1-paco-2024-10-03.md deleted file mode 100644 index 8c61be27..00000000 --- a/demo-vault-v2/event-1on1-paco-2024-10-03.md +++ /dev/null @@ -1,20 +0,0 @@ ---- -aliases: ["1:1 Paco — 2024-10-03"] -Is A: Event -Date: "2024-10-03" -Belongs to: "[[2024-10]]" -Related to: ["[[person-paco-furiani]]"] -Tags: ["Work"] ---- -# 1:1 Paco — 2024-10-03 -Monthly 1:1. Operations review, tooling updates, and process improvements. - -## Notes -- Discussed [[25q1-referral-program]] technical implementation — referral tracking via Beehiiv -- Evaluated community platforms: Circle vs Discord vs Mighty Networks — leaning Circle -- Upgraded email template with responsive design — mobile open rate improved 10% - -## Follow-up -- [ ] [[person-luca-rossi]] to review disaster recovery plan -- [ ] [[person-paco-furiani]] to set up referral tracking infrastructure -- [ ] [[person-paco-furiani]] to prepare community platform comparison document diff --git a/demo-vault-v2/event-1on1-paco-2024-11-07.md b/demo-vault-v2/event-1on1-paco-2024-11-07.md deleted file mode 100644 index 6f572083..00000000 --- a/demo-vault-v2/event-1on1-paco-2024-11-07.md +++ /dev/null @@ -1,21 +0,0 @@ ---- -aliases: ["1:1 Paco — 2024-11-07"] -Is A: Event -Date: "2024-11-07" -Belongs to: "[[2024-11]]" -Related to: ["[[person-paco-furiani]]"] -Tags: ["Work"] ---- -# 1:1 Paco — 2024-11-07 -Monthly 1:1. Operations review, tooling updates, and process improvements. - -## Notes -- Discussed [[25q1-referral-program]] technical implementation — referral tracking via Beehiiv -- Stripe integration for premium tier live and tested — first 50 subscribers onboarded -- Year-end tooling audit: consolidated 3 redundant subscriptions, saving EUR 120/month -- Set up automated year-end reporting — sponsor metrics, growth charts, revenue breakdown -- Upgraded email template with responsive design — mobile open rate improved 10% - -## Follow-up -- [ ] [[person-luca-rossi]] to review disaster recovery plan -- [ ] [[person-paco-furiani]] to set up referral tracking infrastructure diff --git a/demo-vault-v2/event-1on1-paco-2024-12-05.md b/demo-vault-v2/event-1on1-paco-2024-12-05.md deleted file mode 100644 index 63763a6d..00000000 --- a/demo-vault-v2/event-1on1-paco-2024-12-05.md +++ /dev/null @@ -1,20 +0,0 @@ ---- -aliases: ["1:1 Paco — 2024-12-05"] -Is A: Event -Date: "2024-12-05" -Belongs to: "[[2024-12]]" -Related to: ["[[person-paco-furiani]]"] -Tags: ["Work"] ---- -# 1:1 Paco — 2024-12-05 -Monthly 1:1. Operations review, tooling updates, and process improvements. - -## Notes -- Stripe integration for premium tier live and tested — first 100 subscribers onboarded -- Evaluated community platforms: Circle vs Discord vs Mighty Networks — leaning Circle -- Upgraded email template with responsive design — mobile open rate improved 10% -- [[person-paco-furiani]] built custom webhook for real-time subscriber milestone alerts - -## Follow-up -- [ ] [[person-paco-furiani]] to complete year-end system audit -- [ ] [[person-paco-furiani]] to prepare community platform comparison document diff --git a/demo-vault-v2/event-1on1-paco-2025-01-02.md b/demo-vault-v2/event-1on1-paco-2025-01-02.md deleted file mode 100644 index 1d3a3fb8..00000000 --- a/demo-vault-v2/event-1on1-paco-2025-01-02.md +++ /dev/null @@ -1,20 +0,0 @@ ---- -aliases: ["1:1 Paco — 2025-01-02"] -Is A: Event -Date: "2025-01-02" -Belongs to: "[[2025-01]]" -Related to: ["[[person-paco-furiani]]"] -Tags: ["Work"] ---- -# 1:1 Paco — 2025-01-02 -Monthly 1:1. Operations review, tooling updates, and process improvements. - -## Notes -- Set up monitoring alerts for deliverability drops and unusual unsubscribe spikes -- Referral program technical setup complete — custom landing page with tracking pixel -- Investigated AI tools for content assistance — testing Notion AI and Claude for draft generation - -## Follow-up -- [ ] [[person-luca-rossi]] to review tech stack costs and approve budget -- [ ] [[person-paco-furiani]] to onboard community moderators on Circle tools -- [ ] [[person-paco-furiani]] to set up deliverability monitoring alerts diff --git a/demo-vault-v2/event-1on1-paco-2025-02-06.md b/demo-vault-v2/event-1on1-paco-2025-02-06.md deleted file mode 100644 index 65828d13..00000000 --- a/demo-vault-v2/event-1on1-paco-2025-02-06.md +++ /dev/null @@ -1,19 +0,0 @@ ---- -aliases: ["1:1 Paco — 2025-02-06"] -Is A: Event -Date: "2025-02-06" -Belongs to: "[[2025-02]]" -Related to: ["[[person-paco-furiani]]"] -Tags: ["Work"] ---- -# 1:1 Paco — 2025-02-06 -Monthly 1:1. Operations review, tooling updates, and process improvements. - -## Notes -- Investigated AI tools for content assistance — testing Notion AI and Claude for draft generation -- Referral program technical setup complete — custom landing page with tracking pixel -- Email warm-up sequence optimized — new subscribers now get 5 emails in first 2 weeks - -## Follow-up -- [ ] [[person-paco-furiani]] to set up deliverability monitoring alerts -- [ ] [[person-paco-furiani]] to evaluate AI content tools for team use diff --git a/demo-vault-v2/event-1on1-paco-2025-03-06.md b/demo-vault-v2/event-1on1-paco-2025-03-06.md deleted file mode 100644 index aa6376ff..00000000 --- a/demo-vault-v2/event-1on1-paco-2025-03-06.md +++ /dev/null @@ -1,20 +0,0 @@ ---- -aliases: ["1:1 Paco — 2025-03-06"] -Is A: Event -Date: "2025-03-06" -Belongs to: "[[2025-03]]" -Related to: ["[[person-paco-furiani]]"] -Tags: ["Work"] ---- -# 1:1 Paco — 2025-03-06 -Monthly 1:1. Operations review, tooling updates, and process improvements. - -## Notes -- Email warm-up sequence optimized — new subscribers now get 4 emails in first 2 weeks -- Referral program technical setup complete — custom landing page with tracking pixel -- New analytics dashboard launched with real-time subscriber and revenue metrics -- Set up monitoring alerts for deliverability drops and unusual unsubscribe spikes - -## Follow-up -- [ ] [[person-luca-rossi]] to review tech stack costs and approve budget -- [ ] [[person-paco-furiani]] to onboard community moderators on Circle tools diff --git a/demo-vault-v2/event-1on1-paco-2025-04-03.md b/demo-vault-v2/event-1on1-paco-2025-04-03.md deleted file mode 100644 index e7d67935..00000000 --- a/demo-vault-v2/event-1on1-paco-2025-04-03.md +++ /dev/null @@ -1,21 +0,0 @@ ---- -aliases: ["1:1 Paco — 2025-04-03"] -Is A: Event -Date: "2025-04-03" -Belongs to: "[[2025-04]]" -Related to: ["[[person-paco-furiani]]"] -Tags: ["Work"] ---- -# 1:1 Paco — 2025-04-03 -Monthly 1:1. Operations review, tooling updates, and process improvements. - -## Notes -- Video podcast setup for YouTube — evaluated StreamYard for recording -- Sponsor reporting fully automated — PDF reports generated and emailed monthly -- Evaluated Laputa app integration points — API for pulling subscriber stats into vault -- Deliverability maintained at 99.0% despite list growth to 70k -- Community platform scaling — added 4 discussion channels, automated welcome flow - -## Follow-up -- [ ] [[person-paco-furiani]] to build Laputa API integration prototype -- [ ] [[person-paco-furiani]] to complete YouTube video podcast setup diff --git a/demo-vault-v2/event-1on1-paco-2025-05-01.md b/demo-vault-v2/event-1on1-paco-2025-05-01.md deleted file mode 100644 index 5723b201..00000000 --- a/demo-vault-v2/event-1on1-paco-2025-05-01.md +++ /dev/null @@ -1,21 +0,0 @@ ---- -aliases: ["1:1 Paco — 2025-05-01"] -Is A: Event -Date: "2025-05-01" -Belongs to: "[[2025-05]]" -Related to: ["[[person-paco-furiani]]"] -Tags: ["Work"] ---- -# 1:1 Paco — 2025-05-01 -Monthly 1:1. Operations review, tooling updates, and process improvements. - -## Notes -- Community platform scaling — added 4 discussion channels, automated welcome flow -- Sponsor reporting fully automated — PDF reports generated and emailed monthly -- [[person-paco-furiani]] built internal tool for newsletter edition scheduling and status tracking -- Deliverability maintained at 99.0% despite list growth to 65k -- Video podcast setup for YouTube — evaluated Riverside for recording - -## Follow-up -- [ ] [[person-paco-furiani]] to complete YouTube video podcast setup -- [ ] [[person-paco-furiani]] to build Laputa API integration prototype diff --git a/demo-vault-v2/event-1on1-paco-2025-06-05.md b/demo-vault-v2/event-1on1-paco-2025-06-05.md deleted file mode 100644 index e5754675..00000000 --- a/demo-vault-v2/event-1on1-paco-2025-06-05.md +++ /dev/null @@ -1,20 +0,0 @@ ---- -aliases: ["1:1 Paco — 2025-06-05"] -Is A: Event -Date: "2025-06-05" -Belongs to: "[[2025-06]]" -Related to: ["[[person-paco-furiani]]"] -Tags: ["Work"] ---- -# 1:1 Paco — 2025-06-05 -Monthly 1:1. Operations review, tooling updates, and process improvements. - -## Notes -- Community platform scaling — added 4 discussion channels, automated welcome flow -- Sponsor reporting fully automated — PDF reports generated and emailed monthly -- Deliverability maintained at 99.0% despite list growth to 65k - -## Follow-up -- [ ] [[person-paco-furiani]] to renegotiate Beehiiv annual contract -- [ ] [[person-paco-furiani]] to build Laputa API integration prototype -- [ ] [[person-paco-furiani]] to document community moderation escalation process diff --git a/demo-vault-v2/event-cycling-2024-01-02.md b/demo-vault-v2/event-cycling-2024-01-02.md deleted file mode 100644 index 0109173a..00000000 --- a/demo-vault-v2/event-cycling-2024-01-02.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Cycling intervals — 2024-01-02"] -Is A: Event -Date: "2024-01-02" -Belongs to: "[[2024-01]]" -Related to: ["[[person-luca-rossi]]"] -Tags: ["Health", "Sport"] ---- -# Cycling intervals — 2024-01-02 -60-min interval session. 4x8min at threshold power. - -## Notes -- Set up in the pain cave. TrainerRoad workout, no escape from the intervals. -- Forgot to eat enough before — bonked slightly on the last interval. -- Held 212W average across the intervals. Not pushing too hard this time of year. diff --git a/demo-vault-v2/event-cycling-2024-01-09.md b/demo-vault-v2/event-cycling-2024-01-09.md deleted file mode 100644 index a0c89239..00000000 --- a/demo-vault-v2/event-cycling-2024-01-09.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -aliases: ["Cycling intervals — 2024-01-09"] -Is A: Event -Date: "2024-01-09" -Belongs to: "[[2024-01]]" -Related to: ["[[person-luca-rossi]]"] -Tags: ["Health", "Sport"] ---- -# Cycling intervals — 2024-01-09 -60-min interval session. 4x8min at threshold power. - -## Notes -- Felt strong through the first three intervals, legs faded a bit on the last one. -- Indoor session. Opened the garage door halfway for some air circulation. -- Good recovery week last week is paying off. Felt fresher than expected. -- Matched last week's numbers despite feeling more tired. Consistency is key. diff --git a/demo-vault-v2/event-cycling-2024-01-16.md b/demo-vault-v2/event-cycling-2024-01-16.md deleted file mode 100644 index 85ea6024..00000000 --- a/demo-vault-v2/event-cycling-2024-01-16.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -aliases: ["Cycling intervals — 2024-01-16"] -Is A: Event -Date: "2024-01-16" -Belongs to: "[[2024-01]]" -Related to: ["[[person-luca-rossi]]"] -Tags: ["Health", "Sport"] ---- -# Cycling intervals — 2024-01-16 -60-min interval session. 4x8min at threshold power. - -## Notes -- Cadence averaged 88rpm. Trying to stay smooth through the intervals. -- Pushed 226W on the intervals, 202W overall. Good pacing. -- Heavy legs — probably need more recovery between strength and interval days. -- Tight hamstrings from sitting at the desk all day. Need to stretch more. diff --git a/demo-vault-v2/event-cycling-2024-01-23.md b/demo-vault-v2/event-cycling-2024-01-23.md deleted file mode 100644 index 9931f9b6..00000000 --- a/demo-vault-v2/event-cycling-2024-01-23.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -aliases: ["Cycling intervals — 2024-01-23"] -Is A: Event -Date: "2024-01-23" -Belongs to: "[[2024-01]]" -Related to: ["[[person-luca-rossi]]"] -Tags: ["Health", "Sport"] ---- -# Cycling intervals — 2024-01-23 -60-min interval session. 4x8min at threshold power. - -## Notes -- Indoor on the smart trainer. Podcasts and suffering. -- Low cadence strength work at 65rpm for the first set, then normal cadence. -- Had a big pasta dinner last night, felt properly fueled today. -- Legs felt heavy from yesterday's gym session. Kept power in check. diff --git a/demo-vault-v2/event-cycling-2024-01-30.md b/demo-vault-v2/event-cycling-2024-01-30.md deleted file mode 100644 index 96b582c0..00000000 --- a/demo-vault-v2/event-cycling-2024-01-30.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -aliases: ["Cycling intervals — 2024-01-30"] -Is A: Event -Date: "2024-01-30" -Belongs to: "[[2024-01]]" -Related to: ["[[person-luca-rossi]]"] -Tags: ["Health", "Sport"] ---- -# Cycling intervals — 2024-01-30 -60-min interval session. 4x8min at threshold power. - -## Notes -- Power numbers: 198W avg, 216W NP. Consistent across all intervals. -- Had oatmeal and coffee 2 hours before. Fueling was fine. -- Still some DOMS from Monday's squats. Didn't affect the bike too much. -- Indoor trainer session. Zwift kept it entertaining at least. diff --git a/demo-vault-v2/event-cycling-2024-02-06.md b/demo-vault-v2/event-cycling-2024-02-06.md deleted file mode 100644 index b9366d01..00000000 --- a/demo-vault-v2/event-cycling-2024-02-06.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -aliases: ["Cycling intervals — 2024-02-06"] -Is A: Event -Date: "2024-02-06" -Belongs to: "[[2024-02]]" -Related to: ["[[person-luca-rossi]]"] -Tags: ["Health", "Sport"] ---- -# Cycling intervals — 2024-02-06 -60-min interval session. 4x8min at threshold power. - -## Notes -- Smart trainer session. The power match feature is working well with the Stages. -- Held 202W average across the intervals. Not pushing too hard this time of year. -- HRV was good this morning. Body seems to be adapting to the training load. -- Legs were stiff for the first two intervals, loosened up after that. diff --git a/demo-vault-v2/event-cycling-2024-02-13.md b/demo-vault-v2/event-cycling-2024-02-13.md deleted file mode 100644 index 4eda83f5..00000000 --- a/demo-vault-v2/event-cycling-2024-02-13.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -aliases: ["Cycling intervals — 2024-02-13"] -Is A: Event -Date: "2024-02-13" -Belongs to: "[[2024-02]]" -Related to: ["[[person-luca-rossi]]"] -Tags: ["Health", "Sport"] ---- -# Cycling intervals — 2024-02-13 -60-min interval session. 4x8min at threshold power. - -## Notes -- Focused on high cadence drills during recovery — 100-110rpm. -- Indoor session. Opened the garage door halfway for some air circulation. -- Legs felt decent once I got going, but the warmup was sluggish. -- Tight hamstrings from sitting at the desk all day. Need to stretch more. diff --git a/demo-vault-v2/event-cycling-2024-02-20.md b/demo-vault-v2/event-cycling-2024-02-20.md deleted file mode 100644 index 0a3d1ff5..00000000 --- a/demo-vault-v2/event-cycling-2024-02-20.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -aliases: ["Cycling intervals — 2024-02-20"] -Is A: Event -Date: "2024-02-20" -Belongs to: "[[2024-02]]" -Related to: ["[[person-luca-rossi]]"] -Tags: ["Health", "Sport"] ---- -# Cycling intervals — 2024-02-20 -60-min interval session. 4x8min at threshold power. - -## Notes -- Indoor session. Opened the garage door halfway for some air circulation. -- Good recovery week last week is paying off. Felt fresher than expected. -- Legs were stiff for the first two intervals, loosened up after that. -- Avg power 201W, NP 227W. Keeping things controlled for base building. diff --git a/demo-vault-v2/event-cycling-2024-02-27.md b/demo-vault-v2/event-cycling-2024-02-27.md deleted file mode 100644 index d99f8ac9..00000000 --- a/demo-vault-v2/event-cycling-2024-02-27.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -aliases: ["Cycling intervals — 2024-02-27"] -Is A: Event -Date: "2024-02-27" -Belongs to: "[[2024-02]]" -Related to: ["[[person-luca-rossi]]"] -Tags: ["Health", "Sport"] ---- -# Cycling intervals — 2024-02-27 -60-min interval session. 4x8min at threshold power. - -## Notes -- Surprisingly fresh legs today despite the cold. Good session overall. -- Kept cadence at 85-90rpm for the threshold work. -- NP 223W for the session. Intervals felt manageable at 232W. -- Similar effort to last week but heart rate was 3-4 beats lower. Good sign. diff --git a/demo-vault-v2/event-cycling-2024-03-05.md b/demo-vault-v2/event-cycling-2024-03-05.md deleted file mode 100644 index 94be2763..00000000 --- a/demo-vault-v2/event-cycling-2024-03-05.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -aliases: ["Cycling intervals — 2024-03-05"] -Is A: Event -Date: "2024-03-05" -Belongs to: "[[2024-03]]" -Related to: ["[[person-luca-rossi]]"] -Tags: ["Health", "Sport"] ---- -# Cycling intervals — 2024-03-05 -60-min interval session. 4x8min at threshold power. - -## Notes -- Light DOMS from the gym but nothing that affected the bike. -- Power up 10W from the same workout in January. The base work paid off. -- Beautiful spring morning. 16C, light wind. Best conditions in months. -- First outdoor intervals of the season. Legs felt different on real terrain. diff --git a/demo-vault-v2/event-cycling-2024-03-12.md b/demo-vault-v2/event-cycling-2024-03-12.md deleted file mode 100644 index 4e350aaa..00000000 --- a/demo-vault-v2/event-cycling-2024-03-12.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -aliases: ["Cycling intervals — 2024-03-12"] -Is A: Event -Date: "2024-03-12" -Belongs to: "[[2024-03]]" -Related to: ["[[person-luca-rossi]]"] -Tags: ["Health", "Sport"] ---- -# Cycling intervals — 2024-03-12 -60-min interval session. 4x8min at threshold power. - -## Notes -- Pushed 242W on the hard efforts. Power is trending up nicely. -- First proper outside session in weeks. Forgot how much harder wind makes everything. -- Heart rate was 5 beats lower at the same power as February. Fitness is building. -- A bit of heaviness early on, but legs came alive after the warmup. diff --git a/demo-vault-v2/event-cycling-2024-03-19.md b/demo-vault-v2/event-cycling-2024-03-19.md deleted file mode 100644 index 318f5bb3..00000000 --- a/demo-vault-v2/event-cycling-2024-03-19.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -aliases: ["Cycling intervals — 2024-03-19"] -Is A: Event -Date: "2024-03-19" -Belongs to: "[[2024-03]]" -Related to: ["[[person-luca-rossi]]"] -Tags: ["Health", "Sport"] ---- -# Cycling intervals — 2024-03-19 -60-min interval session. 4x8min at threshold power. - -## Notes -- Interval power 230W, felt sustainable. Might need to bump FTP up. -- Pre-ride meal was rice and eggs. Plenty of energy for the efforts. -- First outdoor intervals of the season. Legs felt different on real terrain. -- Outdoor on the regular interval route. Cherry blossoms are out along the canal. diff --git a/demo-vault-v2/event-cycling-2024-03-26.md b/demo-vault-v2/event-cycling-2024-03-26.md deleted file mode 100644 index 866634d7..00000000 --- a/demo-vault-v2/event-cycling-2024-03-26.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Cycling intervals — 2024-03-26"] -Is A: Event -Date: "2024-03-26" -Belongs to: "[[2024-03]]" -Related to: ["[[person-luca-rossi]]"] -Tags: ["Health", "Sport"] ---- -# Cycling intervals — 2024-03-26 -60-min interval session. 4x8min at threshold power. - -## Notes -- Beautiful spring morning. 16C, light wind. Best conditions in months. -- NP 231W. Interval power was right at 258W — hitting the targets. -- Legs were punchy today. Spring energy is real. diff --git a/demo-vault-v2/event-cycling-2024-04-02.md b/demo-vault-v2/event-cycling-2024-04-02.md deleted file mode 100644 index 58714074..00000000 --- a/demo-vault-v2/event-cycling-2024-04-02.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -aliases: ["Cycling intervals — 2024-04-02"] -Is A: Event -Date: "2024-04-02" -Belongs to: "[[2024-04]]" -Related to: ["[[person-luca-rossi]]"] -Tags: ["Health", "Sport"] ---- -# Cycling intervals — 2024-04-02 -60-min interval session. 4x8min at threshold power. - -## Notes -- 17C and sunny. Hard to believe this is the same sport as the indoor suffer-fests. -- Pushed 260W on the hard efforts. Power is trending up nicely. -- Compared to 6 weeks ago, holding these numbers feels significantly easier. -- Legs were responsive today — hit every power target cleanly. diff --git a/demo-vault-v2/event-cycling-2024-04-09.md b/demo-vault-v2/event-cycling-2024-04-09.md deleted file mode 100644 index 17c7cf2b..00000000 --- a/demo-vault-v2/event-cycling-2024-04-09.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -aliases: ["Cycling intervals — 2024-04-09"] -Is A: Event -Date: "2024-04-09" -Belongs to: "[[2024-04]]" -Related to: ["[[person-luca-rossi]]"] -Tags: ["Health", "Sport"] ---- -# Cycling intervals — 2024-04-09 -60-min interval session. 4x8min at threshold power. - -## Notes -- Mixed session — warmup on trainer, then headed outside for the intervals. -- Cadence naturally higher outside — averaged 92rpm vs 88 on the trainer. -- Legs felt strong through all the intervals. No fade at all. -- Averaged 216W with peaks at 278W. FTP has definitely gone up since winter. diff --git a/demo-vault-v2/event-cycling-2024-04-16.md b/demo-vault-v2/event-cycling-2024-04-16.md deleted file mode 100644 index db739851..00000000 --- a/demo-vault-v2/event-cycling-2024-04-16.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Cycling intervals — 2024-04-16"] -Is A: Event -Date: "2024-04-16" -Belongs to: "[[2024-04]]" -Related to: ["[[person-luca-rossi]]"] -Tags: ["Health", "Sport"] ---- -# Cycling intervals — 2024-04-16 -60-min interval session. 4x8min at threshold power. - -## Notes -- First outdoor intervals of the season. Legs felt different on real terrain. -- Strong numbers today: 222W avg, 236W NP. Spring form is building. -- Mixed cadence work: low gear grinding at 70rpm and high spin at 100rpm. diff --git a/demo-vault-v2/event-cycling-2024-04-23.md b/demo-vault-v2/event-cycling-2024-04-23.md deleted file mode 100644 index 0f56e4fd..00000000 --- a/demo-vault-v2/event-cycling-2024-04-23.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -aliases: ["Cycling intervals — 2024-04-23"] -Is A: Event -Date: "2024-04-23" -Belongs to: "[[2024-04]]" -Related to: ["[[person-luca-rossi]]"] -Tags: ["Health", "Sport"] ---- -# Cycling intervals — 2024-04-23 -60-min interval session. 4x8min at threshold power. - -## Notes -- Power was 221W average. The structured winter training is paying off. -- 17C and sunny. Hard to believe this is the same sport as the indoor suffer-fests. -- Started experimenting with carb drink during intervals. 60g/hr target. -- Quads were burning by the end but held the power. Good suffering. diff --git a/demo-vault-v2/event-cycling-2024-04-30.md b/demo-vault-v2/event-cycling-2024-04-30.md deleted file mode 100644 index 8d87057b..00000000 --- a/demo-vault-v2/event-cycling-2024-04-30.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -aliases: ["Cycling intervals — 2024-04-30"] -Is A: Event -Date: "2024-04-30" -Belongs to: "[[2024-04]]" -Related to: ["[[person-luca-rossi]]"] -Tags: ["Health", "Sport"] ---- -# Cycling intervals — 2024-04-30 -60-min interval session. 4x8min at threshold power. - -## Notes -- Mixed session — warmup on trainer, then headed outside for the intervals. -- Good snap in the legs. Ready to start racing soon. -- Avg power 223W, peaked at 320W on the final interval. Legs are coming around. -- Light DOMS from the gym but nothing that affected the bike. diff --git a/demo-vault-v2/event-cycling-2024-05-07.md b/demo-vault-v2/event-cycling-2024-05-07.md deleted file mode 100644 index 47c234c2..00000000 --- a/demo-vault-v2/event-cycling-2024-05-07.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -aliases: ["Cycling intervals — 2024-05-07"] -Is A: Event -Date: "2024-05-07" -Belongs to: "[[2024-05]]" -Related to: ["[[person-luca-rossi]]"] -Tags: ["Health", "Sport"] ---- -# Cycling intervals — 2024-05-07 -60-min interval session. 4x8min at threshold power. - -## Notes -- First outdoor intervals of the season. Legs felt different on real terrain. -- Power was 228W average. The structured winter training is paying off. -- Monday's rest day was needed. Came in with good energy today. -- Ate a PB&J wrap before heading out. Energy was solid throughout. diff --git a/demo-vault-v2/event-cycling-2024-05-14.md b/demo-vault-v2/event-cycling-2024-05-14.md deleted file mode 100644 index 53e0ccc2..00000000 --- a/demo-vault-v2/event-cycling-2024-05-14.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Cycling intervals — 2024-05-14"] -Is A: Event -Date: "2024-05-14" -Belongs to: "[[2024-05]]" -Related to: ["[[person-luca-rossi]]"] -Tags: ["Health", "Sport"] ---- -# Cycling intervals — 2024-05-14 -60-min interval session. 4x8min at threshold power. - -## Notes -- Mixed cadence work: low gear grinding at 70rpm and high spin at 100rpm. -- Beautiful spring morning. 16C, light wind. Best conditions in months. -- Fresh legs after the rest day. Nailed every interval. diff --git a/demo-vault-v2/event-cycling-2024-05-21.md b/demo-vault-v2/event-cycling-2024-05-21.md deleted file mode 100644 index e611ee44..00000000 --- a/demo-vault-v2/event-cycling-2024-05-21.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -aliases: ["Cycling intervals — 2024-05-21"] -Is A: Event -Date: "2024-05-21" -Belongs to: "[[2024-05]]" -Related to: ["[[person-luca-rossi]]"] -Tags: ["Health", "Sport"] ---- -# Cycling intervals — 2024-05-21 -60-min interval session. 4x8min at threshold power. - -## Notes -- Outside on the local loop. Still a bit chilly but manageable with arm warmers. -- Good snap in the legs. Ready to start racing soon. -- Averaged 231W with peaks at 305W. FTP has definitely gone up since winter. -- Power up 10W from the same workout in January. The base work paid off. diff --git a/demo-vault-v2/event-cycling-2024-05-28.md b/demo-vault-v2/event-cycling-2024-05-28.md deleted file mode 100644 index 3babd9c8..00000000 --- a/demo-vault-v2/event-cycling-2024-05-28.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -aliases: ["Cycling intervals — 2024-05-28"] -Is A: Event -Date: "2024-05-28" -Belongs to: "[[2024-05]]" -Related to: ["[[person-luca-rossi]]"] -Tags: ["Health", "Sport"] ---- -# Cycling intervals — 2024-05-28 -60-min interval session. 4x8min at threshold power. - -## Notes -- Used the foam roller last night. Legs felt noticeably better today. -- Focused on keeping cadence high — averaged 93rpm on the intervals. -- Finally rode outside! 14C and partly cloudy. Perfect interval weather. -- Pushed 269W on the hard efforts. Power is trending up nicely. diff --git a/demo-vault-v2/event-cycling-2024-06-04.md b/demo-vault-v2/event-cycling-2024-06-04.md deleted file mode 100644 index 5501f919..00000000 --- a/demo-vault-v2/event-cycling-2024-06-04.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Cycling intervals — 2024-06-04"] -Is A: Event -Date: "2024-06-04" -Belongs to: "[[2024-06]]" -Related to: ["[[person-luca-rossi]]"] -Tags: ["Health", "Sport"] ---- -# Cycling intervals — 2024-06-04 -60-min interval session. 4x8min at threshold power. - -## Notes -- 30C and humid. Hydration was critical today. -- Power-to-heart-rate ratio is the best it's ever been. -- Power was 237W average. Could have pushed harder, saving legs for the weekend race. diff --git a/demo-vault-v2/event-cycling-2024-06-11.md b/demo-vault-v2/event-cycling-2024-06-11.md deleted file mode 100644 index 63dba2fa..00000000 --- a/demo-vault-v2/event-cycling-2024-06-11.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -aliases: ["Cycling intervals — 2024-06-11"] -Is A: Event -Date: "2024-06-11" -Belongs to: "[[2024-06]]" -Related to: ["[[person-luca-rossi]]"] -Tags: ["Health", "Sport"] ---- -# Cycling intervals — 2024-06-11 -60-min interval session. 4x8min at threshold power. - -## Notes -- Hot and windy. Intervals into the headwind were brutal. -- Powerful legs — could have done another set easily. -- Naturally high cadence today — legs were spinning freely. -- Better than the same workout 3 weeks ago. Still making gains. diff --git a/demo-vault-v2/event-cycling-2024-06-18.md b/demo-vault-v2/event-cycling-2024-06-18.md deleted file mode 100644 index 15264a00..00000000 --- a/demo-vault-v2/event-cycling-2024-06-18.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Cycling intervals — 2024-06-18"] -Is A: Event -Date: "2024-06-18" -Belongs to: "[[2024-06]]" -Related to: ["[[person-luca-rossi]]"] -Tags: ["Health", "Sport"] ---- -# Cycling intervals — 2024-06-18 -60-min interval session. 4x8min at threshold power. - -## Notes -- 30C and humid. Hydration was critical today. -- Better than the same workout 3 weeks ago. Still making gains. -- Legs felt incredible. Everything just clicked today. diff --git a/demo-vault-v2/event-cycling-2024-06-25.md b/demo-vault-v2/event-cycling-2024-06-25.md deleted file mode 100644 index c1d81de2..00000000 --- a/demo-vault-v2/event-cycling-2024-06-25.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -aliases: ["Cycling intervals — 2024-06-25"] -Is A: Event -Date: "2024-06-25" -Belongs to: "[[2024-06]]" -Related to: ["[[person-luca-rossi]]"] -Tags: ["Health", "Sport"] ---- -# Cycling intervals — 2024-06-25 -60-min interval session. 4x8min at threshold power. - -## Notes -- Early morning session to beat the heat. 22C at 6am, still warm. -- Training load is high but managing with good sleep and nutrition. -- Interval power right on target at 262W. Pacing was spot-on. -- This session would have been impossible 6 months ago. Stoked. diff --git a/demo-vault-v2/event-cycling-2024-07-02.md b/demo-vault-v2/event-cycling-2024-07-02.md deleted file mode 100644 index 3115a2c6..00000000 --- a/demo-vault-v2/event-cycling-2024-07-02.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -aliases: ["Cycling intervals — 2024-07-02"] -Is A: Event -Date: "2024-07-02" -Belongs to: "[[2024-07]]" -Related to: ["[[person-luca-rossi]]"] -Tags: ["Health", "Sport"] ---- -# Cycling intervals — 2024-07-02 -60-min interval session. 4x8min at threshold power. - -## Notes -- Matched my best-ever numbers for this workout. Peak form confirmed. -- Dialed in the race nutrition: 80g carbs/hour. Felt strong throughout. -- Best power numbers of the year: 233W avg, 341W peak. -- Powerful legs — could have done another set easily. diff --git a/demo-vault-v2/event-cycling-2024-07-09.md b/demo-vault-v2/event-cycling-2024-07-09.md deleted file mode 100644 index 2c79273b..00000000 --- a/demo-vault-v2/event-cycling-2024-07-09.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -aliases: ["Cycling intervals — 2024-07-09"] -Is A: Event -Date: "2024-07-09" -Belongs to: "[[2024-07]]" -Related to: ["[[person-luca-rossi]]"] -Tags: ["Health", "Sport"] ---- -# Cycling intervals — 2024-07-09 -60-min interval session. 4x8min at threshold power. - -## Notes -- Legs felt race-ready. Saving the sharpness for Saturday. -- High cadence session — averaged 97rpm. Working on speed. -- Evening session after work. Still 28C but a nice breeze helped. -- Training load is high but managing with good sleep and nutrition. diff --git a/demo-vault-v2/event-cycling-2024-07-16.md b/demo-vault-v2/event-cycling-2024-07-16.md deleted file mode 100644 index 247b5fb5..00000000 --- a/demo-vault-v2/event-cycling-2024-07-16.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -aliases: ["Cycling intervals — 2024-07-16"] -Is A: Event -Date: "2024-07-16" -Belongs to: "[[2024-07]]" -Related to: ["[[person-luca-rossi]]"] -Tags: ["Health", "Sport"] ---- -# Cycling intervals — 2024-07-16 -60-min interval session. 4x8min at threshold power. - -## Notes -- Started at dawn — 20C and misty. Roads to myself. -- Mixed cadence: seated at 90rpm, standing at 75rpm for the surges. -- Took an extra rest day this week. Quality over quantity. -- Legs felt incredible. Everything just clicked today. diff --git a/demo-vault-v2/event-cycling-2024-07-23.md b/demo-vault-v2/event-cycling-2024-07-23.md deleted file mode 100644 index c71c8996..00000000 --- a/demo-vault-v2/event-cycling-2024-07-23.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Cycling intervals — 2024-07-23"] -Is A: Event -Date: "2024-07-23" -Belongs to: "[[2024-07]]" -Related to: ["[[person-luca-rossi]]"] -Tags: ["Health", "Sport"] ---- -# Cycling intervals — 2024-07-23 -60-min interval session. 4x8min at threshold power. - -## Notes -- Light legs, sharp power. This is what peak form feels like. -- 27C and sunny. Took extra bottles and soaked my jersey at the fountain. -- NP 250W. Interval average was 255W — new PB for this workout. diff --git a/demo-vault-v2/event-cycling-2024-07-30.md b/demo-vault-v2/event-cycling-2024-07-30.md deleted file mode 100644 index 9b854b9f..00000000 --- a/demo-vault-v2/event-cycling-2024-07-30.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Cycling intervals — 2024-07-30"] -Is A: Event -Date: "2024-07-30" -Belongs to: "[[2024-07]]" -Related to: ["[[person-luca-rossi]]"] -Tags: ["Health", "Sport"] ---- -# Cycling intervals — 2024-07-30 -60-min interval session. 4x8min at threshold power. - -## Notes -- Legs were a bit tired from the weekend race but still hit the numbers. -- Pre-ride was rice cakes and coffee. Took 3 gels during the session. -- Avg power 233W, NP 260W. Peak fitness right now. diff --git a/demo-vault-v2/event-cycling-2024-08-06.md b/demo-vault-v2/event-cycling-2024-08-06.md deleted file mode 100644 index d0ea81ab..00000000 --- a/demo-vault-v2/event-cycling-2024-08-06.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -aliases: ["Cycling intervals — 2024-08-06"] -Is A: Event -Date: "2024-08-06" -Belongs to: "[[2024-08]]" -Related to: ["[[person-luca-rossi]]"] -Tags: ["Health", "Sport"] ---- -# Cycling intervals — 2024-08-06 -60-min interval session. 4x8min at threshold power. - -## Notes -- Snappy legs today. The taper is working. -- Recovery shake immediately after. Need to stay on top of nutrition in this heat. -- Crushed the intervals at 262W. Hit 308W on the last one. -- Had a big bowl of pasta 3 hours before. Energy was never an issue. diff --git a/demo-vault-v2/event-cycling-2024-08-13.md b/demo-vault-v2/event-cycling-2024-08-13.md deleted file mode 100644 index 5aa51a53..00000000 --- a/demo-vault-v2/event-cycling-2024-08-13.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -aliases: ["Cycling intervals — 2024-08-13"] -Is A: Event -Date: "2024-08-13" -Belongs to: "[[2024-08]]" -Related to: ["[[person-luca-rossi]]"] -Tags: ["Health", "Sport"] ---- -# Cycling intervals — 2024-08-13 -60-min interval session. 4x8min at threshold power. - -## Notes -- NP 259W. Interval average was 275W — new PB for this workout. -- Early morning session to beat the heat. 22C at 6am, still warm. -- Better than the same workout 3 weeks ago. Still making gains. -- Legs felt race-ready. Saving the sharpness for Saturday. diff --git a/demo-vault-v2/event-cycling-2024-08-20.md b/demo-vault-v2/event-cycling-2024-08-20.md deleted file mode 100644 index 78fc6730..00000000 --- a/demo-vault-v2/event-cycling-2024-08-20.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Cycling intervals — 2024-08-20"] -Is A: Event -Date: "2024-08-20" -Belongs to: "[[2024-08]]" -Related to: ["[[person-luca-rossi]]"] -Tags: ["Health", "Sport"] ---- -# Cycling intervals — 2024-08-20 -60-min interval session. 4x8min at threshold power. - -## Notes -- Held 271W across all intervals with no fade. Season peak form. -- 20W above my January FTP for these intervals. Massive progress. -- Evening session after work. Still 28C but a nice breeze helped. diff --git a/demo-vault-v2/event-cycling-2024-08-27.md b/demo-vault-v2/event-cycling-2024-08-27.md deleted file mode 100644 index 09459adb..00000000 --- a/demo-vault-v2/event-cycling-2024-08-27.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Cycling intervals — 2024-08-27"] -Is A: Event -Date: "2024-08-27" -Belongs to: "[[2024-08]]" -Related to: ["[[person-luca-rossi]]"] -Tags: ["Health", "Sport"] ---- -# Cycling intervals — 2024-08-27 -60-min interval session. 4x8min at threshold power. - -## Notes -- Started at dawn — 20C and misty. Roads to myself. -- Interval power right on target at 283W. Pacing was spot-on. -- Took an extra rest day this week. Quality over quantity. diff --git a/demo-vault-v2/event-cycling-2024-09-03.md b/demo-vault-v2/event-cycling-2024-09-03.md deleted file mode 100644 index a8986469..00000000 --- a/demo-vault-v2/event-cycling-2024-09-03.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -aliases: ["Cycling intervals — 2024-09-03"] -Is A: Event -Date: "2024-09-03" -Belongs to: "[[2024-09]]" -Related to: ["[[person-luca-rossi]]"] -Tags: ["Health", "Sport"] ---- -# Cycling intervals — 2024-09-03 -60-min interval session. 4x8min at threshold power. - -## Notes -- 15C and breezy. Beautiful fall riding, leaves everywhere. -- Tired legs from the long ride over the weekend but managed the session. -- Hot chocolate post-ride. The important recovery drink. -- Averaged 229W. Still strong enough for the occasional autumn sportive. diff --git a/demo-vault-v2/event-cycling-2024-09-10.md b/demo-vault-v2/event-cycling-2024-09-10.md deleted file mode 100644 index 0ac1ce00..00000000 --- a/demo-vault-v2/event-cycling-2024-09-10.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -aliases: ["Cycling intervals — 2024-09-10"] -Is A: Event -Date: "2024-09-10" -Belongs to: "[[2024-09]]" -Related to: ["[[person-luca-rossi]]"] -Tags: ["Health", "Sport"] ---- -# Cycling intervals — 2024-09-10 -60-min interval session. 4x8min at threshold power. - -## Notes -- Wet roads but not raining. Autumn colors were spectacular though. -- Last year at this point I was more burned out. Better periodization this year. -- Power 246W average. Not bad considering the reduced training. -- Foam rolling while watching TV. Low-key recovery routine. diff --git a/demo-vault-v2/event-cycling-2024-09-17.md b/demo-vault-v2/event-cycling-2024-09-17.md deleted file mode 100644 index 94d499f7..00000000 --- a/demo-vault-v2/event-cycling-2024-09-17.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -aliases: ["Cycling intervals — 2024-09-17"] -Is A: Event -Date: "2024-09-17" -Belongs to: "[[2024-09]]" -Related to: ["[[person-luca-rossi]]"] -Tags: ["Health", "Sport"] ---- -# Cycling intervals — 2024-09-17 -60-min interval session. 4x8min at threshold power. - -## Notes -- Interval power was 269W. Accepting the off-season decline gracefully. -- Last year at this point I was more burned out. Better periodization this year. -- Last outdoor session of the season probably. 10C, wind from the north. -- Steady legs, nothing spectacular. Fine for an off-season workout. diff --git a/demo-vault-v2/event-cycling-2024-09-24.md b/demo-vault-v2/event-cycling-2024-09-24.md deleted file mode 100644 index b717ab5e..00000000 --- a/demo-vault-v2/event-cycling-2024-09-24.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Cycling intervals — 2024-09-24"] -Is A: Event -Date: "2024-09-24" -Belongs to: "[[2024-09]]" -Related to: ["[[person-luca-rossi]]"] -Tags: ["Health", "Sport"] ---- -# Cycling intervals — 2024-09-24 -60-min interval session. 4x8min at threshold power. - -## Notes -- Indoor trainer session. Set up the fan and settled in for winter. -- Averaged 85rpm. Legs are naturally turning over slower now. -- Interval power at 263W. Slightly below peak but that's expected. diff --git a/demo-vault-v2/event-cycling-2024-10-01.md b/demo-vault-v2/event-cycling-2024-10-01.md deleted file mode 100644 index e7dd5780..00000000 --- a/demo-vault-v2/event-cycling-2024-10-01.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -aliases: ["Cycling intervals — 2024-10-01"] -Is A: Event -Date: "2024-10-01" -Belongs to: "[[2024-10]]" -Related to: ["[[person-luca-rossi]]"] -Tags: ["Health", "Sport"] ---- -# Cycling intervals — 2024-10-01 -60-min interval session. 4x8min at threshold power. - -## Notes -- Feeling the cumulative fatigue from a long season. Almost time for a proper break. -- Good enough legs for a maintenance session. Not fighting for PRs. -- Coffee and toast pre-ride. Simple fueling for maintenance sessions. -- Indoor trainer session. Set up the fan and settled in for winter. diff --git a/demo-vault-v2/event-cycling-2024-10-08.md b/demo-vault-v2/event-cycling-2024-10-08.md deleted file mode 100644 index ffccab79..00000000 --- a/demo-vault-v2/event-cycling-2024-10-08.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Cycling intervals — 2024-10-08"] -Is A: Event -Date: "2024-10-08" -Belongs to: "[[2024-10]]" -Related to: ["[[person-luca-rossi]]"] -Tags: ["Health", "Sport"] ---- -# Cycling intervals — 2024-10-08 -60-min interval session. 4x8min at threshold power. - -## Notes -- Low cadence strength work — 70rpm for the intervals. Off-season drills. -- Last outdoor intervals before the clocks change. 12C, overcast. -- Avg power 224W, NP 240W. Season is winding down but maintaining fitness. diff --git a/demo-vault-v2/event-cycling-2024-10-15.md b/demo-vault-v2/event-cycling-2024-10-15.md deleted file mode 100644 index 1cd50fc8..00000000 --- a/demo-vault-v2/event-cycling-2024-10-15.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Cycling intervals — 2024-10-15"] -Is A: Event -Date: "2024-10-15" -Belongs to: "[[2024-10]]" -Related to: ["[[person-luca-rossi]]"] -Tags: ["Health", "Sport"] ---- -# Cycling intervals — 2024-10-15 -60-min interval session. 4x8min at threshold power. - -## Notes -- Foam rolling while watching TV. Low-key recovery routine. -- Crisp autumn morning. 8C, clear sky. Needed full-finger gloves. -- Legs felt okay. Not the spring in them from summer but still solid. diff --git a/demo-vault-v2/event-cycling-2024-10-22.md b/demo-vault-v2/event-cycling-2024-10-22.md deleted file mode 100644 index cd11b827..00000000 --- a/demo-vault-v2/event-cycling-2024-10-22.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Cycling intervals — 2024-10-22"] -Is A: Event -Date: "2024-10-22" -Belongs to: "[[2024-10]]" -Related to: ["[[person-luca-rossi]]"] -Tags: ["Health", "Sport"] ---- -# Cycling intervals — 2024-10-22 -60-min interval session. 4x8min at threshold power. - -## Notes -- A bit sluggish but pushed through. Autumn fatigue is real. -- Last outdoor session of the season probably. 10C, wind from the north. -- NP 241W. Power is naturally coming down as the volume drops. diff --git a/demo-vault-v2/event-cycling-2024-10-29.md b/demo-vault-v2/event-cycling-2024-10-29.md deleted file mode 100644 index 5a22969f..00000000 --- a/demo-vault-v2/event-cycling-2024-10-29.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -aliases: ["Cycling intervals — 2024-10-29"] -Is A: Event -Date: "2024-10-29" -Belongs to: "[[2024-10]]" -Related to: ["[[person-luca-rossi]]"] -Tags: ["Health", "Sport"] ---- -# Cycling intervals — 2024-10-29 -60-min interval session. 4x8min at threshold power. - -## Notes -- Good power for this time of year — 226W avg, 293W on the hard efforts. -- 15C and breezy. Beautiful fall riding, leaves everywhere. -- More rest days now, which helps keep the quality sessions decent. -- Steady legs, nothing spectacular. Fine for an off-season workout. diff --git a/demo-vault-v2/event-cycling-2024-11-05.md b/demo-vault-v2/event-cycling-2024-11-05.md deleted file mode 100644 index 8d32c37c..00000000 --- a/demo-vault-v2/event-cycling-2024-11-05.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Cycling intervals — 2024-11-05"] -Is A: Event -Date: "2024-11-05" -Belongs to: "[[2024-11]]" -Related to: ["[[person-luca-rossi]]"] -Tags: ["Health", "Sport"] ---- -# Cycling intervals — 2024-11-05 -60-min interval session. 4x8min at threshold power. - -## Notes -- Moved back to the trainer today. Dark at 5pm now. -- Legs felt okay. Not the spring in them from summer but still solid. -- Feeling the cumulative fatigue from a long season. Almost time for a proper break. diff --git a/demo-vault-v2/event-cycling-2024-11-12.md b/demo-vault-v2/event-cycling-2024-11-12.md deleted file mode 100644 index ecef2396..00000000 --- a/demo-vault-v2/event-cycling-2024-11-12.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Cycling intervals — 2024-11-12"] -Is A: Event -Date: "2024-11-12" -Belongs to: "[[2024-11]]" -Related to: ["[[person-luca-rossi]]"] -Tags: ["Health", "Sport"] ---- -# Cycling intervals — 2024-11-12 -60-min interval session. 4x8min at threshold power. - -## Notes -- Power 224W average. Not bad considering the reduced training. -- Crisp autumn morning. 8C, clear sky. Needed full-finger gloves. -- Legs felt better than expected after a week of just easy rides. diff --git a/demo-vault-v2/event-cycling-2024-11-19.md b/demo-vault-v2/event-cycling-2024-11-19.md deleted file mode 100644 index 72978d4d..00000000 --- a/demo-vault-v2/event-cycling-2024-11-19.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Cycling intervals — 2024-11-19"] -Is A: Event -Date: "2024-11-19" -Belongs to: "[[2024-11]]" -Related to: ["[[person-luca-rossi]]"] -Tags: ["Health", "Sport"] ---- -# Cycling intervals — 2024-11-19 -60-min interval session. 4x8min at threshold power. - -## Notes -- Avg power 224W, NP 235W. Season is winding down but maintaining fitness. -- Feeling the cumulative fatigue from a long season. Almost time for a proper break. -- Crisp autumn morning. 8C, clear sky. Needed full-finger gloves. diff --git a/demo-vault-v2/event-cycling-2024-11-26.md b/demo-vault-v2/event-cycling-2024-11-26.md deleted file mode 100644 index 01149686..00000000 --- a/demo-vault-v2/event-cycling-2024-11-26.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Cycling intervals — 2024-11-26"] -Is A: Event -Date: "2024-11-26" -Belongs to: "[[2024-11]]" -Related to: ["[[person-luca-rossi]]"] -Tags: ["Health", "Sport"] ---- -# Cycling intervals — 2024-11-26 -60-min interval session. 4x8min at threshold power. - -## Notes -- Avg power 214W, NP 239W. Season is winding down but maintaining fitness. -- Feeling the cumulative fatigue from a long season. Almost time for a proper break. -- Heavy legs today. The shorter days are sapping motivation. diff --git a/demo-vault-v2/event-cycling-2024-12-03.md b/demo-vault-v2/event-cycling-2024-12-03.md deleted file mode 100644 index db89aed4..00000000 --- a/demo-vault-v2/event-cycling-2024-12-03.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -aliases: ["Cycling intervals — 2024-12-03"] -Is A: Event -Date: "2024-12-03" -Belongs to: "[[2024-12]]" -Related to: ["[[person-luca-rossi]]"] -Tags: ["Health", "Sport"] ---- -# Cycling intervals — 2024-12-03 -60-min interval session. 4x8min at threshold power. - -## Notes -- Similar effort to last week but heart rate was 3-4 beats lower. Good sign. -- Cadence averaged 88rpm. Trying to stay smooth through the intervals. -- Trainer session in the garage. Had to wear leg warmers, it was freezing. -- Avg power 221W, NP 232W. Keeping things controlled for base building. diff --git a/demo-vault-v2/event-cycling-2024-12-10.md b/demo-vault-v2/event-cycling-2024-12-10.md deleted file mode 100644 index 80d789b4..00000000 --- a/demo-vault-v2/event-cycling-2024-12-10.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Cycling intervals — 2024-12-10"] -Is A: Event -Date: "2024-12-10" -Belongs to: "[[2024-12]]" -Related to: ["[[person-luca-rossi]]"] -Tags: ["Health", "Sport"] ---- -# Cycling intervals — 2024-12-10 -60-min interval session. 4x8min at threshold power. - -## Notes -- Indoor session with the fan on full blast. Still sweating buckets. -- NP 234W for the session. Intervals felt manageable at 250W. -- Only 6 hours of sleep. Could feel it in the last two intervals. diff --git a/demo-vault-v2/event-cycling-2024-12-17.md b/demo-vault-v2/event-cycling-2024-12-17.md deleted file mode 100644 index bd4bf3c9..00000000 --- a/demo-vault-v2/event-cycling-2024-12-17.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Cycling intervals — 2024-12-17"] -Is A: Event -Date: "2024-12-17" -Belongs to: "[[2024-12]]" -Related to: ["[[person-luca-rossi]]"] -Tags: ["Health", "Sport"] ---- -# Cycling intervals — 2024-12-17 -60-min interval session. 4x8min at threshold power. - -## Notes -- Interval power averaged 233W. Trying to keep it aerobic-dominant. -- Smart trainer session. The power match feature is working well with the Stages. -- Tried a new energy drink mix during the session. Stomach was fine. diff --git a/demo-vault-v2/event-cycling-2024-12-24.md b/demo-vault-v2/event-cycling-2024-12-24.md deleted file mode 100644 index 7f2b674b..00000000 --- a/demo-vault-v2/event-cycling-2024-12-24.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -aliases: ["Cycling intervals — 2024-12-24"] -Is A: Event -Date: "2024-12-24" -Belongs to: "[[2024-12]]" -Related to: ["[[person-luca-rossi]]"] -Tags: ["Health", "Sport"] ---- -# Cycling intervals — 2024-12-24 -60-min interval session. 4x8min at threshold power. - -## Notes -- Trainer session in the garage. Had to wear leg warmers, it was freezing. -- Had oatmeal and coffee 2 hours before. Fueling was fine. -- Power was steady at 222W. Heart rate stayed in zone 3-4 for most of the session. -- Legs felt heavy from yesterday's gym session. Kept power in check. diff --git a/demo-vault-v2/event-cycling-2024-12-31.md b/demo-vault-v2/event-cycling-2024-12-31.md deleted file mode 100644 index ca633bef..00000000 --- a/demo-vault-v2/event-cycling-2024-12-31.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Cycling intervals — 2024-12-31"] -Is A: Event -Date: "2024-12-31" -Belongs to: "[[2024-12]]" -Related to: ["[[person-luca-rossi]]"] -Tags: ["Health", "Sport"] ---- -# Cycling intervals — 2024-12-31 -60-min interval session. 4x8min at threshold power. - -## Notes -- On the Wahoo KICKR today. Watched a race replay while grinding. -- Interval power averaged 249W. Trying to keep it aerobic-dominant. -- Slept well last night — 7.5 hours. Made a difference in how I felt. diff --git a/demo-vault-v2/event-cycling-2025-01-07.md b/demo-vault-v2/event-cycling-2025-01-07.md deleted file mode 100644 index a11d28e5..00000000 --- a/demo-vault-v2/event-cycling-2025-01-07.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -aliases: ["Cycling intervals — 2025-01-07"] -Is A: Event -Date: "2025-01-07" -Belongs to: "[[2025-01]]" -Related to: ["[[person-luca-rossi]]"] -Tags: ["Health", "Sport"] ---- -# Cycling intervals — 2025-01-07 -60-min interval session. 4x8min at threshold power. - -## Notes -- Indoor on the smart trainer. Podcasts and suffering. -- Legs were okay, not great. Typical for this time of year. -- Cadence averaged 88rpm. Trying to stay smooth through the intervals. -- Avg 218W, max 294W on the final surge. Staying disciplined with the power targets. diff --git a/demo-vault-v2/event-cycling-2025-01-14.md b/demo-vault-v2/event-cycling-2025-01-14.md deleted file mode 100644 index 3b68831f..00000000 --- a/demo-vault-v2/event-cycling-2025-01-14.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Cycling intervals — 2025-01-14"] -Is A: Event -Date: "2025-01-14" -Belongs to: "[[2025-01]]" -Related to: ["[[person-luca-rossi]]"] -Tags: ["Health", "Sport"] ---- -# Cycling intervals — 2025-01-14 -60-min interval session. 4x8min at threshold power. - -## Notes -- Interval power averaged 257W. Trying to keep it aerobic-dominant. -- Indoor session. Opened the garage door halfway for some air circulation. -- Only 6 hours of sleep. Could feel it in the last two intervals. diff --git a/demo-vault-v2/event-cycling-2025-01-21.md b/demo-vault-v2/event-cycling-2025-01-21.md deleted file mode 100644 index 9f01373a..00000000 --- a/demo-vault-v2/event-cycling-2025-01-21.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -aliases: ["Cycling intervals — 2025-01-21"] -Is A: Event -Date: "2025-01-21" -Belongs to: "[[2025-01]]" -Related to: ["[[person-luca-rossi]]"] -Tags: ["Health", "Sport"] ---- -# Cycling intervals — 2025-01-21 -60-min interval session. 4x8min at threshold power. - -## Notes -- Legs were okay, not great. Typical for this time of year. -- Interval power trending up slightly week over week. Patient progress. -- Interval power averaged 255W. Trying to keep it aerobic-dominant. -- Forgot to eat enough before — bonked slightly on the last interval. diff --git a/demo-vault-v2/event-cycling-2025-01-28.md b/demo-vault-v2/event-cycling-2025-01-28.md deleted file mode 100644 index 58dd7301..00000000 --- a/demo-vault-v2/event-cycling-2025-01-28.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Cycling intervals — 2025-01-28"] -Is A: Event -Date: "2025-01-28" -Belongs to: "[[2025-01]]" -Related to: ["[[person-luca-rossi]]"] -Tags: ["Health", "Sport"] ---- -# Cycling intervals — 2025-01-28 -60-min interval session. 4x8min at threshold power. - -## Notes -- Surprisingly fresh legs today despite the cold. Good session overall. -- Pushed 240W on the intervals, 227W overall. Good pacing. -- Indoor trainer session. Zwift kept it entertaining at least. diff --git a/demo-vault-v2/event-cycling-2025-02-04.md b/demo-vault-v2/event-cycling-2025-02-04.md deleted file mode 100644 index 405cd818..00000000 --- a/demo-vault-v2/event-cycling-2025-02-04.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -aliases: ["Cycling intervals — 2025-02-04"] -Is A: Event -Date: "2025-02-04" -Belongs to: "[[2025-02]]" -Related to: ["[[person-luca-rossi]]"] -Tags: ["Health", "Sport"] ---- -# Cycling intervals — 2025-02-04 -60-min interval session. 4x8min at threshold power. - -## Notes -- Pushed 252W on the intervals, 223W overall. Good pacing. -- Matched last week's numbers despite feeling more tired. Consistency is key. -- Had a big pasta dinner last night, felt properly fueled today. -- Trainer day. Paired it with a cycling documentary for motivation. diff --git a/demo-vault-v2/event-cycling-2025-02-11.md b/demo-vault-v2/event-cycling-2025-02-11.md deleted file mode 100644 index 1782fa7f..00000000 --- a/demo-vault-v2/event-cycling-2025-02-11.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -aliases: ["Cycling intervals — 2025-02-11"] -Is A: Event -Date: "2025-02-11" -Belongs to: "[[2025-02]]" -Related to: ["[[person-luca-rossi]]"] -Tags: ["Health", "Sport"] ---- -# Cycling intervals — 2025-02-11 -60-min interval session. 4x8min at threshold power. - -## Notes -- Interval power averaged 249W. Trying to keep it aerobic-dominant. -- Trainer day. Paired it with a cycling documentary for motivation. -- Legs felt heavy from yesterday's gym session. Kept power in check. -- FTP test is coming up next month. These sessions are building a good base. diff --git a/demo-vault-v2/event-cycling-2025-02-18.md b/demo-vault-v2/event-cycling-2025-02-18.md deleted file mode 100644 index a01bb62e..00000000 --- a/demo-vault-v2/event-cycling-2025-02-18.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Cycling intervals — 2025-02-18"] -Is A: Event -Date: "2025-02-18" -Belongs to: "[[2025-02]]" -Related to: ["[[person-luca-rossi]]"] -Tags: ["Health", "Sport"] ---- -# Cycling intervals — 2025-02-18 -60-min interval session. 4x8min at threshold power. - -## Notes -- Zwift race simulation workout. The ERG mode kept me honest. -- Pushed 237W on the intervals, 216W overall. Good pacing. -- Good leg feel today. The extra rest day helped. diff --git a/demo-vault-v2/event-cycling-2025-02-25.md b/demo-vault-v2/event-cycling-2025-02-25.md deleted file mode 100644 index 78a86ffb..00000000 --- a/demo-vault-v2/event-cycling-2025-02-25.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Cycling intervals — 2025-02-25"] -Is A: Event -Date: "2025-02-25" -Belongs to: "[[2025-02]]" -Related to: ["[[person-luca-rossi]]"] -Tags: ["Health", "Sport"] ---- -# Cycling intervals — 2025-02-25 -60-min interval session. 4x8min at threshold power. - -## Notes -- Focused on high cadence drills during recovery — 100-110rpm. -- Power numbers: 214W avg, 230W NP. Consistent across all intervals. -- Good leg feel today. The extra rest day helped. diff --git a/demo-vault-v2/event-cycling-2025-03-04.md b/demo-vault-v2/event-cycling-2025-03-04.md deleted file mode 100644 index 81d517c4..00000000 --- a/demo-vault-v2/event-cycling-2025-03-04.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Cycling intervals — 2025-03-04"] -Is A: Event -Date: "2025-03-04" -Belongs to: "[[2025-03]]" -Related to: ["[[person-luca-rossi]]"] -Tags: ["Health", "Sport"] ---- -# Cycling intervals — 2025-03-04 -60-min interval session. 4x8min at threshold power. - -## Notes -- First proper outside session in weeks. Forgot how much harder wind makes everything. -- Used the foam roller last night. Legs felt noticeably better today. -- Legs felt strong through all the intervals. No fade at all. diff --git a/demo-vault-v2/event-cycling-2025-03-11.md b/demo-vault-v2/event-cycling-2025-03-11.md deleted file mode 100644 index 00726b11..00000000 --- a/demo-vault-v2/event-cycling-2025-03-11.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -aliases: ["Cycling intervals — 2025-03-11"] -Is A: Event -Date: "2025-03-11" -Belongs to: "[[2025-03]]" -Related to: ["[[person-luca-rossi]]"] -Tags: ["Health", "Sport"] ---- -# Cycling intervals — 2025-03-11 -60-min interval session. 4x8min at threshold power. - -## Notes -- Legs felt strong through all the intervals. No fade at all. -- Used the foam roller last night. Legs felt noticeably better today. -- Mixed session — warmup on trainer, then headed outside for the intervals. -- Power up 10W from the same workout in January. The base work paid off. diff --git a/demo-vault-v2/event-cycling-2025-03-18.md b/demo-vault-v2/event-cycling-2025-03-18.md deleted file mode 100644 index 183de958..00000000 --- a/demo-vault-v2/event-cycling-2025-03-18.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -aliases: ["Cycling intervals — 2025-03-18"] -Is A: Event -Date: "2025-03-18" -Belongs to: "[[2025-03]]" -Related to: ["[[person-luca-rossi]]"] -Tags: ["Health", "Sport"] ---- -# Cycling intervals — 2025-03-18 -60-min interval session. 4x8min at threshold power. - -## Notes -- Practiced race-pace cadence around 95rpm for the threshold efforts. -- Good snap in the legs. Ready to start racing soon. -- Outdoor session on the hill circuit. Wind from the west made the return legs harder. -- Avg power 221W, peaked at 313W on the final interval. Legs are coming around. diff --git a/demo-vault-v2/event-cycling-2025-03-25.md b/demo-vault-v2/event-cycling-2025-03-25.md deleted file mode 100644 index f9a27ad1..00000000 --- a/demo-vault-v2/event-cycling-2025-03-25.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -aliases: ["Cycling intervals — 2025-03-25"] -Is A: Event -Date: "2025-03-25" -Belongs to: "[[2025-03]]" -Related to: ["[[person-luca-rossi]]"] -Tags: ["Health", "Sport"] ---- -# Cycling intervals — 2025-03-25 -60-min interval session. 4x8min at threshold power. - -## Notes -- Overcast but dry. Used the long drag on the A-road for the efforts. -- Hit 289W on a sprint finish to the last interval. Average was 237W. -- Started experimenting with carb drink during intervals. 60g/hr target. -- Quads were burning by the end but held the power. Good suffering. diff --git a/demo-vault-v2/event-cycling-2025-04-01.md b/demo-vault-v2/event-cycling-2025-04-01.md deleted file mode 100644 index 32cb628d..00000000 --- a/demo-vault-v2/event-cycling-2025-04-01.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -aliases: ["Cycling intervals — 2025-04-01"] -Is A: Event -Date: "2025-04-01" -Belongs to: "[[2025-04]]" -Related to: ["[[person-luca-rossi]]"] -Tags: ["Health", "Sport"] ---- -# Cycling intervals — 2025-04-01 -60-min interval session. 4x8min at threshold power. - -## Notes -- A bit of heaviness early on, but legs came alive after the warmup. -- Ate a PB&J wrap before heading out. Energy was solid throughout. -- Pushed 259W on the hard efforts. Power is trending up nicely. -- Better than last week — power was similar but RPE was lower. diff --git a/demo-vault-v2/event-cycling-2025-04-08.md b/demo-vault-v2/event-cycling-2025-04-08.md deleted file mode 100644 index 3c2e53e0..00000000 --- a/demo-vault-v2/event-cycling-2025-04-08.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -aliases: ["Cycling intervals — 2025-04-08"] -Is A: Event -Date: "2025-04-08" -Belongs to: "[[2025-04]]" -Related to: ["[[person-luca-rossi]]"] -Tags: ["Health", "Sport"] ---- -# Cycling intervals — 2025-04-08 -60-min interval session. 4x8min at threshold power. - -## Notes -- Heart rate was 5 beats lower at the same power as February. Fitness is building. -- Fresh legs after the rest day. Nailed every interval. -- NP 251W. Interval power was right at 274W — hitting the targets. -- Monday's rest day was needed. Came in with good energy today. diff --git a/demo-vault-v2/event-cycling-2025-04-15.md b/demo-vault-v2/event-cycling-2025-04-15.md deleted file mode 100644 index e50cd6dd..00000000 --- a/demo-vault-v2/event-cycling-2025-04-15.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -aliases: ["Cycling intervals — 2025-04-15"] -Is A: Event -Date: "2025-04-15" -Belongs to: "[[2025-04]]" -Related to: ["[[person-luca-rossi]]"] -Tags: ["Health", "Sport"] ---- -# Cycling intervals — 2025-04-15 -60-min interval session. 4x8min at threshold power. - -## Notes -- Quads were burning by the end but held the power. Good suffering. -- Compared to 6 weeks ago, holding these numbers feels significantly easier. -- Power was 242W average. The structured winter training is paying off. -- Pre-ride meal was rice and eggs. Plenty of energy for the efforts. diff --git a/demo-vault-v2/event-cycling-2025-04-22.md b/demo-vault-v2/event-cycling-2025-04-22.md deleted file mode 100644 index 3bf720fb..00000000 --- a/demo-vault-v2/event-cycling-2025-04-22.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Cycling intervals — 2025-04-22"] -Is A: Event -Date: "2025-04-22" -Belongs to: "[[2025-04]]" -Related to: ["[[person-luca-rossi]]"] -Tags: ["Health", "Sport"] ---- -# Cycling intervals — 2025-04-22 -60-min interval session. 4x8min at threshold power. - -## Notes -- Better than last week — power was similar but RPE was lower. -- Strong numbers today: 239W avg, 253W NP. Spring form is building. -- First outdoor intervals of the season. Legs felt different on real terrain. diff --git a/demo-vault-v2/event-cycling-2025-04-29.md b/demo-vault-v2/event-cycling-2025-04-29.md deleted file mode 100644 index 8b6e1c5f..00000000 --- a/demo-vault-v2/event-cycling-2025-04-29.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Cycling intervals — 2025-04-29"] -Is A: Event -Date: "2025-04-29" -Belongs to: "[[2025-04]]" -Related to: ["[[person-luca-rossi]]"] -Tags: ["Health", "Sport"] ---- -# Cycling intervals — 2025-04-29 -60-min interval session. 4x8min at threshold power. - -## Notes -- Pushed 251W on the hard efforts. Power is trending up nicely. -- Outside on the local loop. Still a bit chilly but manageable with arm warmers. -- Legs were responsive today — hit every power target cleanly. diff --git a/demo-vault-v2/event-cycling-2025-05-06.md b/demo-vault-v2/event-cycling-2025-05-06.md deleted file mode 100644 index 02a6a878..00000000 --- a/demo-vault-v2/event-cycling-2025-05-06.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Cycling intervals — 2025-05-06"] -Is A: Event -Date: "2025-05-06" -Belongs to: "[[2025-05]]" -Related to: ["[[person-luca-rossi]]"] -Tags: ["Health", "Sport"] ---- -# Cycling intervals — 2025-05-06 -60-min interval session. 4x8min at threshold power. - -## Notes -- Averaged 242W with peaks at 341W. FTP has definitely gone up since winter. -- Had a proper breakfast — porridge, banana, and coffee. Well fueled. -- A bit of heaviness early on, but legs came alive after the warmup. diff --git a/demo-vault-v2/event-cycling-2025-05-13.md b/demo-vault-v2/event-cycling-2025-05-13.md deleted file mode 100644 index 45ec6aa1..00000000 --- a/demo-vault-v2/event-cycling-2025-05-13.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Cycling intervals — 2025-05-13"] -Is A: Event -Date: "2025-05-13" -Belongs to: "[[2025-05]]" -Related to: ["[[person-luca-rossi]]"] -Tags: ["Health", "Sport"] ---- -# Cycling intervals — 2025-05-13 -60-min interval session. 4x8min at threshold power. - -## Notes -- Finally rode outside! 14C and partly cloudy. Perfect interval weather. -- Pushed 277W on the hard efforts. Power is trending up nicely. -- Legs were responsive today — hit every power target cleanly. diff --git a/demo-vault-v2/event-cycling-2025-05-20.md b/demo-vault-v2/event-cycling-2025-05-20.md deleted file mode 100644 index 7177ec45..00000000 --- a/demo-vault-v2/event-cycling-2025-05-20.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -aliases: ["Cycling intervals — 2025-05-20"] -Is A: Event -Date: "2025-05-20" -Belongs to: "[[2025-05]]" -Related to: ["[[person-luca-rossi]]"] -Tags: ["Health", "Sport"] ---- -# Cycling intervals — 2025-05-20 -60-min interval session. 4x8min at threshold power. - -## Notes -- Good snap in the legs. Ready to start racing soon. -- Beautiful spring morning. 16C, light wind. Best conditions in months. -- FTP test last week confirmed a 12W gain since December. On track. -- NP 259W. Interval power was right at 281W — hitting the targets. diff --git a/demo-vault-v2/event-cycling-2025-05-27.md b/demo-vault-v2/event-cycling-2025-05-27.md deleted file mode 100644 index 02f1bc44..00000000 --- a/demo-vault-v2/event-cycling-2025-05-27.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Cycling intervals — 2025-05-27"] -Is A: Event -Date: "2025-05-27" -Belongs to: "[[2025-05]]" -Related to: ["[[person-luca-rossi]]"] -Tags: ["Health", "Sport"] ---- -# Cycling intervals — 2025-05-27 -60-min interval session. 4x8min at threshold power. - -## Notes -- Compared to 6 weeks ago, holding these numbers feels significantly easier. -- Strong numbers today: 239W avg, 255W NP. Spring form is building. -- Fresh legs after the rest day. Nailed every interval. diff --git a/demo-vault-v2/event-cycling-2025-06-03.md b/demo-vault-v2/event-cycling-2025-06-03.md deleted file mode 100644 index de5bf7bc..00000000 --- a/demo-vault-v2/event-cycling-2025-06-03.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -aliases: ["Cycling intervals — 2025-06-03"] -Is A: Event -Date: "2025-06-03" -Belongs to: "[[2025-06]]" -Related to: ["[[person-luca-rossi]]"] -Tags: ["Health", "Sport"] ---- -# Cycling intervals — 2025-06-03 -60-min interval session. 4x8min at threshold power. - -## Notes -- Legs were a bit tired from the weekend race but still hit the numbers. -- Early morning session to beat the heat. 22C at 6am, still warm. -- Held 284W across all intervals with no fade. Season peak form. -- Took an extra rest day this week. Quality over quantity. diff --git a/demo-vault-v2/event-cycling-2025-06-10.md b/demo-vault-v2/event-cycling-2025-06-10.md deleted file mode 100644 index 275461f3..00000000 --- a/demo-vault-v2/event-cycling-2025-06-10.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -aliases: ["Cycling intervals — 2025-06-10"] -Is A: Event -Date: "2025-06-10" -Belongs to: "[[2025-06]]" -Related to: ["[[person-luca-rossi]]"] -Tags: ["Health", "Sport"] ---- -# Cycling intervals — 2025-06-10 -60-min interval session. 4x8min at threshold power. - -## Notes -- Legs felt race-ready. Saving the sharpness for Saturday. -- Sleeping with AC on helps recovery enormously in this weather. -- Strong session — 252W avg, 269W NP. Power-to-weight is the best it's been. -- Evening session after work. Still 28C but a nice breeze helped. diff --git a/demo-vault-v2/event-cycling-2025-06-17.md b/demo-vault-v2/event-cycling-2025-06-17.md deleted file mode 100644 index d6cb9486..00000000 --- a/demo-vault-v2/event-cycling-2025-06-17.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Cycling intervals — 2025-06-17"] -Is A: Event -Date: "2025-06-17" -Belongs to: "[[2025-06]]" -Related to: ["[[person-luca-rossi]]"] -Tags: ["Health", "Sport"] ---- -# Cycling intervals — 2025-06-17 -60-min interval session. 4x8min at threshold power. - -## Notes -- Sleeping with AC on helps recovery enormously in this weather. -- Legs felt incredible. Everything just clicked today. -- Early morning session to beat the heat. 22C at 6am, still warm. diff --git a/demo-vault-v2/event-cycling-endurance-2024-01-04.md b/demo-vault-v2/event-cycling-endurance-2024-01-04.md deleted file mode 100644 index 9e1823a8..00000000 --- a/demo-vault-v2/event-cycling-endurance-2024-01-04.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Cycling endurance — 2024-01-04"] -Is A: Event -Date: "2024-01-04" -Belongs to: "[[2024-01]]" -Tags: ["Health", "Sport"] ---- -# Cycling endurance — 2024-01-04 -90-min endurance ride at zone 2. Avg HR 135. - -## Notes -- Indoor trainer session, watched the first half of a documentary on alpine cycling routes -- Kept HR steady at 132-138 the entire time, felt very controlled -- Legs still a bit heavy from New Year's break — took 20 min to warm up properly -- Water only, no fuel needed for this effort level diff --git a/demo-vault-v2/event-cycling-endurance-2024-01-11.md b/demo-vault-v2/event-cycling-endurance-2024-01-11.md deleted file mode 100644 index 98c6e8ff..00000000 --- a/demo-vault-v2/event-cycling-endurance-2024-01-11.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Cycling endurance — 2024-01-11"] -Is A: Event -Date: "2024-01-11" -Belongs to: "[[2024-01]]" -Tags: ["Health", "Sport"] ---- -# Cycling endurance — 2024-01-11 -90-min endurance ride at zone 2. Avg HR 135. - -## Notes -- Zwift free ride through the Watopia flat route, kept it social pace -- HR averaged 134, very comfortable — could hold a conversation the whole time -- Listened to a long podcast episode on training periodization -- Easy day after Tuesday's threshold intervals, legs felt fresh by the end diff --git a/demo-vault-v2/event-cycling-endurance-2024-01-18.md b/demo-vault-v2/event-cycling-endurance-2024-01-18.md deleted file mode 100644 index fa7d04c6..00000000 --- a/demo-vault-v2/event-cycling-endurance-2024-01-18.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Cycling endurance — 2024-01-18"] -Is A: Event -Date: "2024-01-18" -Belongs to: "[[2024-01]]" -Tags: ["Health", "Sport"] ---- -# Cycling endurance — 2024-01-18 -90-min endurance ride at zone 2. Avg HR 135. - -## Notes -- Indoor trainer, put on a cycling race replay from last year's Giro -- Cadence stayed around 85-90 rpm, power very consistent at 165W -- HR drifted up to 140 in the last 20 minutes — mild cardiac drift, probably slightly dehydrated -- Had coffee and a banana before the ride, felt good throughout diff --git a/demo-vault-v2/event-cycling-endurance-2024-01-25.md b/demo-vault-v2/event-cycling-endurance-2024-01-25.md deleted file mode 100644 index 9990209e..00000000 --- a/demo-vault-v2/event-cycling-endurance-2024-01-25.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Cycling endurance — 2024-01-25"] -Is A: Event -Date: "2024-01-25" -Belongs to: "[[2024-01]]" -Tags: ["Health", "Sport"] ---- -# Cycling endurance — 2024-01-25 -90-min endurance ride at zone 2. Avg HR 135. - -## Notes -- Trainer session with a movie playing — less boring than staring at Zwift numbers -- Cold garage, wore arm warmers even on the trainer -- HR 130-136 the whole session, very disciplined zone 2 cap -- Recovery ride before tomorrow's rest day, wanted to flush the legs out diff --git a/demo-vault-v2/event-cycling-endurance-2024-02-01.md b/demo-vault-v2/event-cycling-endurance-2024-02-01.md deleted file mode 100644 index d3a40afb..00000000 --- a/demo-vault-v2/event-cycling-endurance-2024-02-01.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Cycling endurance — 2024-02-01"] -Is A: Event -Date: "2024-02-01" -Belongs to: "[[2024-02]]" -Tags: ["Health", "Sport"] ---- -# Cycling endurance — 2024-02-01 -90-min endurance ride at zone 2. Avg HR 135. - -## Notes -- Indoor trainer, Zwift group ride with some club mates — kept the chat going -- Avg power 160W, HR 133 — aerobic base is building nicely -- Finished the podcast series on ultra-endurance racing, pretty inspiring stuff -- Drank a full bottle of water plus electrolyte tabs, better hydration than last week diff --git a/demo-vault-v2/event-cycling-endurance-2024-02-08.md b/demo-vault-v2/event-cycling-endurance-2024-02-08.md deleted file mode 100644 index 04276122..00000000 --- a/demo-vault-v2/event-cycling-endurance-2024-02-08.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Cycling endurance — 2024-02-08"] -Is A: Event -Date: "2024-02-08" -Belongs to: "[[2024-02]]" -Tags: ["Health", "Sport"] ---- -# Cycling endurance — 2024-02-08 -90-min endurance ride at zone 2. Avg HR 135. - -## Notes -- Trainer session, watched a film — the time passes faster with a good movie -- Legs felt dead for the first 30 minutes, yesterday's strength work really loaded them up -- HR stayed below 137 but effort felt harder than usual, RPE 4-5 vs normal 3 -- Skipped the warm-down stretch, should have done it — hamstrings tight now diff --git a/demo-vault-v2/event-cycling-endurance-2024-02-15.md b/demo-vault-v2/event-cycling-endurance-2024-02-15.md deleted file mode 100644 index e3fdf47f..00000000 --- a/demo-vault-v2/event-cycling-endurance-2024-02-15.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Cycling endurance — 2024-02-15"] -Is A: Event -Date: "2024-02-15" -Belongs to: "[[2024-02]]" -Tags: ["Health", "Sport"] ---- -# Cycling endurance — 2024-02-15 -90-min endurance ride at zone 2. Avg HR 135. - -## Notes -- Still on the trainer, but weather is starting to tease — saw sunshine through the garage window -- Solid session, HR 131-136, power 162W avg -- Listened to two episodes of a tech podcast, good multi-tasking -- Ate oatmeal an hour before, stomach was fine, energy stayed level throughout diff --git a/demo-vault-v2/event-cycling-endurance-2024-02-22.md b/demo-vault-v2/event-cycling-endurance-2024-02-22.md deleted file mode 100644 index c33a44b8..00000000 --- a/demo-vault-v2/event-cycling-endurance-2024-02-22.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Cycling endurance — 2024-02-22"] -Is A: Event -Date: "2024-02-22" -Belongs to: "[[2024-02]]" -Tags: ["Health", "Sport"] ---- -# Cycling endurance — 2024-02-22 -90-min endurance ride at zone 2. Avg HR 135. - -## Notes -- Indoor trainer, Zwift Richmond flat course on loop -- Focused on pedaling technique — smooth circles, no dead spots -- HR never went above 135, very meditative session -- Day after a rest day, legs felt incredibly fresh, had to resist pushing harder diff --git a/demo-vault-v2/event-cycling-endurance-2024-02-29.md b/demo-vault-v2/event-cycling-endurance-2024-02-29.md deleted file mode 100644 index 5672aee1..00000000 --- a/demo-vault-v2/event-cycling-endurance-2024-02-29.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Cycling endurance — 2024-02-29"] -Is A: Event -Date: "2024-02-29" -Belongs to: "[[2024-02]]" -Tags: ["Health", "Sport"] ---- -# Cycling endurance — 2024-02-29 -90-min endurance ride at zone 2. Avg HR 135. - -## Notes -- Leap day ride! Indoor trainer session with a 90s movie playlist -- Tried a slightly higher cadence today — 92 rpm vs usual 85-88 -- HR was stable at 134, power a touch lower at 155W but that's fine for Z2 -- Two bottles of water, feeling like hydration is dialed in for these sessions now diff --git a/demo-vault-v2/event-cycling-endurance-2024-03-07.md b/demo-vault-v2/event-cycling-endurance-2024-03-07.md deleted file mode 100644 index fda9d019..00000000 --- a/demo-vault-v2/event-cycling-endurance-2024-03-07.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Cycling endurance — 2024-03-07"] -Is A: Event -Date: "2024-03-07" -Belongs to: "[[2024-03]]" -Tags: ["Health", "Sport"] ---- -# Cycling endurance — 2024-03-07 -90-min endurance ride at zone 2. Avg HR 135. - -## Notes -- First outdoor ride of the year! Cold but dry, finally escaped the trainer -- Flat loop along the river path, about 38 km total -- HR ran a bit higher outdoors — avg 138, probably excitement plus wind -- Hands were freezing even with winter gloves, need to get some lobster mitts diff --git a/demo-vault-v2/event-cycling-endurance-2024-03-14.md b/demo-vault-v2/event-cycling-endurance-2024-03-14.md deleted file mode 100644 index 97ab3644..00000000 --- a/demo-vault-v2/event-cycling-endurance-2024-03-14.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Cycling endurance — 2024-03-14"] -Is A: Event -Date: "2024-03-14" -Belongs to: "[[2024-03]]" -Tags: ["Health", "Sport"] ---- -# Cycling endurance — 2024-03-14 -90-min endurance ride at zone 2. Avg HR 135. - -## Notes -- Back on the trainer due to rain all week, Zwift London course -- Starting to get really bored of indoor riding — spring can't come soon enough -- HR 132-137, power 163W, very consistent -- Listened to an audiobook chapter, helps break the monotony diff --git a/demo-vault-v2/event-cycling-endurance-2024-03-21.md b/demo-vault-v2/event-cycling-endurance-2024-03-21.md deleted file mode 100644 index 4beabe76..00000000 --- a/demo-vault-v2/event-cycling-endurance-2024-03-21.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Cycling endurance — 2024-03-21"] -Is A: Event -Date: "2024-03-21" -Belongs to: "[[2024-03]]" -Tags: ["Health", "Sport"] ---- -# Cycling endurance — 2024-03-21 -90-min endurance ride at zone 2. Avg HR 135. - -## Notes -- Outdoor ride, first day of spring and it felt like it — 12C and partly sunny -- Explored a new route heading north along the canal towpath, nice and flat -- HR 134 avg, very relaxed pace, stopped once to take a photo of daffodils -- Legs are responding well to the consistent Z2 base work these past months diff --git a/demo-vault-v2/event-cycling-endurance-2024-03-28.md b/demo-vault-v2/event-cycling-endurance-2024-03-28.md deleted file mode 100644 index 7f1b7017..00000000 --- a/demo-vault-v2/event-cycling-endurance-2024-03-28.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Cycling endurance — 2024-03-28"] -Is A: Event -Date: "2024-03-28" -Belongs to: "[[2024-03]]" -Tags: ["Health", "Sport"] ---- -# Cycling endurance — 2024-03-28 -90-min endurance ride at zone 2. Avg HR 135. - -## Notes -- Outdoor ride on the rolling hills loop south of town -- HR spiked to 148 on the steeper climbs — need to gear down earlier to stay in Z2 -- Total distance 40 km, a bit more elevation than usual -- Beautiful morning, crisp air, saw a couple of other cyclists out on the same route diff --git a/demo-vault-v2/event-cycling-endurance-2024-04-04.md b/demo-vault-v2/event-cycling-endurance-2024-04-04.md deleted file mode 100644 index f2579ac6..00000000 --- a/demo-vault-v2/event-cycling-endurance-2024-04-04.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Cycling endurance — 2024-04-04"] -Is A: Event -Date: "2024-04-04" -Belongs to: "[[2024-04]]" -Tags: ["Health", "Sport"] ---- -# Cycling endurance — 2024-04-04 -90-min endurance ride at zone 2. Avg HR 135. - -## Notes -- Outdoor ride, finally consistently warm enough to ditch the winter kit -- Headed out on the western loop through the farmland — flat and quiet roads -- HR 133 avg, felt effortless, spring fitness is coming together -- Stopped at a bench by the river for 5 minutes to enjoy the view diff --git a/demo-vault-v2/event-cycling-endurance-2024-04-11.md b/demo-vault-v2/event-cycling-endurance-2024-04-11.md deleted file mode 100644 index 80f8e0b1..00000000 --- a/demo-vault-v2/event-cycling-endurance-2024-04-11.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Cycling endurance — 2024-04-11"] -Is A: Event -Date: "2024-04-11" -Belongs to: "[[2024-04]]" -Tags: ["Health", "Sport"] ---- -# Cycling endurance — 2024-04-11 -90-min endurance ride at zone 2. Avg HR 135. - -## Notes -- Tried a completely new route heading east toward the reservoir -- Rolling terrain, HR crept into Z3 on two short hills — backed off each time -- 42 km total, slightly more than my usual Z2 distance -- Cherry blossoms everywhere, really gorgeous ride diff --git a/demo-vault-v2/event-cycling-endurance-2024-04-18.md b/demo-vault-v2/event-cycling-endurance-2024-04-18.md deleted file mode 100644 index 954a5287..00000000 --- a/demo-vault-v2/event-cycling-endurance-2024-04-18.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Cycling endurance — 2024-04-18"] -Is A: Event -Date: "2024-04-18" -Belongs to: "[[2024-04]]" -Tags: ["Health", "Sport"] ---- -# Cycling endurance — 2024-04-18 -90-min endurance ride at zone 2. Avg HR 135. - -## Notes -- Outdoor ride, overcast but mild — perfect endurance weather honestly -- Canal towpath north, then looped back on the main road -- Power 168W avg at HR 136 — efficiency improving compared to January trainer numbers -- Had toast and jam before leaving, one bottle of plain water diff --git a/demo-vault-v2/event-cycling-endurance-2024-04-25.md b/demo-vault-v2/event-cycling-endurance-2024-04-25.md deleted file mode 100644 index 9e430f3d..00000000 --- a/demo-vault-v2/event-cycling-endurance-2024-04-25.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Cycling endurance — 2024-04-25"] -Is A: Event -Date: "2024-04-25" -Belongs to: "[[2024-04]]" -Tags: ["Health", "Sport"] ---- -# Cycling endurance — 2024-04-25 -90-min endurance ride at zone 2. Avg HR 135. - -## Notes -- Easy spin day after Wednesday's hard interval session -- Flat river path out and back, very gentle effort -- HR 130-134, legs spinning freely, good recovery stimulus -- Listened to music for a change instead of podcasts — felt more relaxing diff --git a/demo-vault-v2/event-cycling-endurance-2024-05-02.md b/demo-vault-v2/event-cycling-endurance-2024-05-02.md deleted file mode 100644 index 169e7d46..00000000 --- a/demo-vault-v2/event-cycling-endurance-2024-05-02.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Cycling endurance — 2024-05-02"] -Is A: Event -Date: "2024-05-02" -Belongs to: "[[2024-05]]" -Tags: ["Health", "Sport"] ---- -# Cycling endurance — 2024-05-02 -90-min endurance ride at zone 2. Avg HR 135. - -## Notes -- Gorgeous May morning, out the door at 7am before work -- Explored the countryside lanes south — rapeseed fields in full bloom, bright yellow everywhere -- HR 135 avg, nailed the zone perfectly, 43 km covered -- Brought two bottles, drank one and a half — starting to need more as it warms up diff --git a/demo-vault-v2/event-cycling-endurance-2024-05-09.md b/demo-vault-v2/event-cycling-endurance-2024-05-09.md deleted file mode 100644 index 215b7779..00000000 --- a/demo-vault-v2/event-cycling-endurance-2024-05-09.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Cycling endurance — 2024-05-09"] -Is A: Event -Date: "2024-05-09" -Belongs to: "[[2024-05]]" -Tags: ["Health", "Sport"] ---- -# Cycling endurance — 2024-05-09 -90-min endurance ride at zone 2. Avg HR 135. - -## Notes -- Windy day, headwind on the way out made it tough to stay in Z2 without crawling -- Tailwind return was glorious though, felt like flying at 35 km/h in zone 1 -- HR avg 136, but with big variance — 128 to 145 depending on wind direction -- Mental note: pick sheltered routes on windy days for better Z2 compliance diff --git a/demo-vault-v2/event-cycling-endurance-2024-05-16.md b/demo-vault-v2/event-cycling-endurance-2024-05-16.md deleted file mode 100644 index 3cfab676..00000000 --- a/demo-vault-v2/event-cycling-endurance-2024-05-16.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Cycling endurance — 2024-05-16"] -Is A: Event -Date: "2024-05-16" -Belongs to: "[[2024-05]]" -Tags: ["Health", "Sport"] ---- -# Cycling endurance — 2024-05-16 -90-min endurance ride at zone 2. Avg HR 135. - -## Notes -- Rode to the cafe on the edge of town and back — 45 km round trip -- Stopped for an espresso at the halfway point, sat outside for 10 min -- HR 132 avg not counting the cafe stop, very easy effort -- Fitness is in a great place right now, these rides feel sustainable all day diff --git a/demo-vault-v2/event-cycling-endurance-2024-05-23.md b/demo-vault-v2/event-cycling-endurance-2024-05-23.md deleted file mode 100644 index 55bdffb6..00000000 --- a/demo-vault-v2/event-cycling-endurance-2024-05-23.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Cycling endurance — 2024-05-23"] -Is A: Event -Date: "2024-05-23" -Belongs to: "[[2024-05]]" -Tags: ["Health", "Sport"] ---- -# Cycling endurance — 2024-05-23 -90-min endurance ride at zone 2. Avg HR 135. - -## Notes -- Pre-rest-day easy spin, kept everything very controlled -- Flat loop through the park and along the river, no hills at all -- HR 130-133, power 160W — deliberately on the lower end of Z2 -- Warm evening ride after work, sun didn't set until 9pm, lovely light diff --git a/demo-vault-v2/event-cycling-endurance-2024-05-30.md b/demo-vault-v2/event-cycling-endurance-2024-05-30.md deleted file mode 100644 index c2cb7327..00000000 --- a/demo-vault-v2/event-cycling-endurance-2024-05-30.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Cycling endurance — 2024-05-30"] -Is A: Event -Date: "2024-05-30" -Belongs to: "[[2024-05]]" -Tags: ["Health", "Sport"] ---- -# Cycling endurance — 2024-05-30 -90-min endurance ride at zone 2. Avg HR 135. - -## Notes -- Morning ride before the heat kicked in, out at 6:30am -- Took the long way around the lake — beautiful mirror-still water at dawn -- HR 134, cadence 88, power 170W — numbers are all trending the right direction -- Ate a proper breakfast after: eggs, toast, coffee. Earned it. diff --git a/demo-vault-v2/event-cycling-endurance-2024-06-06.md b/demo-vault-v2/event-cycling-endurance-2024-06-06.md deleted file mode 100644 index c2eb92b3..00000000 --- a/demo-vault-v2/event-cycling-endurance-2024-06-06.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Cycling endurance — 2024-06-06"] -Is A: Event -Date: "2024-06-06" -Belongs to: "[[2024-06]]" -Tags: ["Health", "Sport"] ---- -# Cycling endurance — 2024-06-06 -90-min endurance ride at zone 2. Avg HR 135. - -## Notes -- Early morning start at 6am to avoid the afternoon heat wave -- River path heading west, mostly shaded by trees — good choice -- HR 136 avg, felt comfortable but the humidity made it feel harder than numbers suggest -- Two full bottles drained plus electrolyte mix, hydration is critical now diff --git a/demo-vault-v2/event-cycling-endurance-2024-06-13.md b/demo-vault-v2/event-cycling-endurance-2024-06-13.md deleted file mode 100644 index 5fd4623d..00000000 --- a/demo-vault-v2/event-cycling-endurance-2024-06-13.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Cycling endurance — 2024-06-13"] -Is A: Event -Date: "2024-06-13" -Belongs to: "[[2024-06]]" -Tags: ["Health", "Sport"] ---- -# Cycling endurance — 2024-06-13 -90-min endurance ride at zone 2. Avg HR 135. - -## Notes -- Rode out to the village with the bakery, picked up pastries on the way back -- Gentle rolling terrain, one short climb where HR hit 142 briefly -- 46 km total — rides are naturally getting longer as the days stretch out -- Legs felt great, recovery from Tuesday's VO2max session was complete diff --git a/demo-vault-v2/event-cycling-endurance-2024-06-20.md b/demo-vault-v2/event-cycling-endurance-2024-06-20.md deleted file mode 100644 index 9f8b00c5..00000000 --- a/demo-vault-v2/event-cycling-endurance-2024-06-20.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Cycling endurance — 2024-06-20"] -Is A: Event -Date: "2024-06-20" -Belongs to: "[[2024-06]]" -Tags: ["Health", "Sport"] ---- -# Cycling endurance — 2024-06-20 -90-min endurance ride at zone 2. Avg HR 135. - -## Notes -- Summer solstice ride! Longest day of the year, out at 5:45am -- Scenic route through the countryside, golden morning light over the fields -- HR 133, power 172W — best power-at-Z2 ratio this year -- Stopped to refill water at a public fountain, smart move in this heat diff --git a/demo-vault-v2/event-cycling-endurance-2024-06-27.md b/demo-vault-v2/event-cycling-endurance-2024-06-27.md deleted file mode 100644 index e5a75894..00000000 --- a/demo-vault-v2/event-cycling-endurance-2024-06-27.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Cycling endurance — 2024-06-27"] -Is A: Event -Date: "2024-06-27" -Belongs to: "[[2024-06]]" -Tags: ["Health", "Sport"] ---- -# Cycling endurance — 2024-06-27 -90-min endurance ride at zone 2. Avg HR 135. - -## Notes -- Hot and humid, went out early but it was already 24C at 6:30am -- Kept to the shaded canal path, flat and protected from sun -- HR ran higher than usual at 139 avg — heat effect on cardiac output -- Took a gel at the 60-min mark even though it's Z2, just felt low on energy diff --git a/demo-vault-v2/event-cycling-endurance-2024-07-04.md b/demo-vault-v2/event-cycling-endurance-2024-07-04.md deleted file mode 100644 index f3682274..00000000 --- a/demo-vault-v2/event-cycling-endurance-2024-07-04.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Cycling endurance — 2024-07-04"] -Is A: Event -Date: "2024-07-04" -Belongs to: "[[2024-07]]" -Tags: ["Health", "Sport"] ---- -# Cycling endurance — 2024-07-04 -90-min endurance ride at zone 2. Avg HR 135. - -## Notes -- Out at 5:30am to beat the heat, still warm even at dawn -- Scenic route along the lake shore, mist rising off the water — magical -- HR 137 avg, slightly elevated from the heat even early morning -- Froze a bottle overnight, best trick for summer riding diff --git a/demo-vault-v2/event-cycling-endurance-2024-07-11.md b/demo-vault-v2/event-cycling-endurance-2024-07-11.md deleted file mode 100644 index 27ddd403..00000000 --- a/demo-vault-v2/event-cycling-endurance-2024-07-11.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Cycling endurance — 2024-07-11"] -Is A: Event -Date: "2024-07-11" -Belongs to: "[[2024-07]]" -Tags: ["Health", "Sport"] ---- -# Cycling endurance — 2024-07-11 -90-min endurance ride at zone 2. Avg HR 135. - -## Notes -- Evening ride after the heat broke, out at 7pm with golden hour light -- Countryside loop past the lavender fields — incredible smell -- HR 134, power 173W, feeling strong in the peak summer fitness block -- Ran into another cyclist and rode together for 20 min, good chat about training diff --git a/demo-vault-v2/event-cycling-endurance-2024-07-18.md b/demo-vault-v2/event-cycling-endurance-2024-07-18.md deleted file mode 100644 index afc1e66a..00000000 --- a/demo-vault-v2/event-cycling-endurance-2024-07-18.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Cycling endurance — 2024-07-18"] -Is A: Event -Date: "2024-07-18" -Belongs to: "[[2024-07]]" -Tags: ["Health", "Sport"] ---- -# Cycling endurance — 2024-07-18 -90-min endurance ride at zone 2. Avg HR 135. - -## Notes -- Early morning, 6am start, route through the forest roads for shade -- Perfect Z2 compliance, HR 132-137 the whole ride -- Brought an extra bottle with electrolyte mix, drank everything -- Recovery day after a hard Tuesday — legs felt like butter by minute 30 diff --git a/demo-vault-v2/event-cycling-endurance-2024-07-25.md b/demo-vault-v2/event-cycling-endurance-2024-07-25.md deleted file mode 100644 index ba367635..00000000 --- a/demo-vault-v2/event-cycling-endurance-2024-07-25.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Cycling endurance — 2024-07-25"] -Is A: Event -Date: "2024-07-25" -Belongs to: "[[2024-07]]" -Tags: ["Health", "Sport"] ---- -# Cycling endurance — 2024-07-25 -90-min endurance ride at zone 2. Avg HR 135. - -## Notes -- Rode to the hilltop cafe, 22 km each way with a decent climb in the middle -- HR popped to 150 on the climb, walked it back down on the descent -- Iced coffee at the top, sat on the terrace overlooking the valley -- Total ride felt more like 2 hours with the stop, but moving time was 90 min diff --git a/demo-vault-v2/event-cycling-endurance-2024-08-01.md b/demo-vault-v2/event-cycling-endurance-2024-08-01.md deleted file mode 100644 index 3285b95c..00000000 --- a/demo-vault-v2/event-cycling-endurance-2024-08-01.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Cycling endurance — 2024-08-01"] -Is A: Event -Date: "2024-08-01" -Belongs to: "[[2024-08]]" -Tags: ["Health", "Sport"] ---- -# Cycling endurance — 2024-08-01 -90-min endurance ride at zone 2. Avg HR 135. - -## Notes -- Dawn patrol ride, out before sunrise, watched it come up over the fields -- Flat river path, 47 km total — longest Z2 distance this month -- HR 135 avg, nailed it perfectly, power 170W -- Ate a banana at the turnaround point, stomach handled it fine at this intensity diff --git a/demo-vault-v2/event-cycling-endurance-2024-08-08.md b/demo-vault-v2/event-cycling-endurance-2024-08-08.md deleted file mode 100644 index 01aece5b..00000000 --- a/demo-vault-v2/event-cycling-endurance-2024-08-08.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Cycling endurance — 2024-08-08"] -Is A: Event -Date: "2024-08-08" -Belongs to: "[[2024-08]]" -Tags: ["Health", "Sport"] ---- -# Cycling endurance — 2024-08-08 -90-min endurance ride at zone 2. Avg HR 135. - -## Notes -- Too hot to ride outside even early morning, back on the trainer with AC -- Zwift pace partner ride in Watopia, just sat in the group and spun -- HR 131, very low end of Z2 — the cool air made a huge difference vs outdoor heat -- Listened to a true crime podcast, time flew by diff --git a/demo-vault-v2/event-cycling-endurance-2024-08-15.md b/demo-vault-v2/event-cycling-endurance-2024-08-15.md deleted file mode 100644 index e0ba7b74..00000000 --- a/demo-vault-v2/event-cycling-endurance-2024-08-15.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Cycling endurance — 2024-08-15"] -Is A: Event -Date: "2024-08-15" -Belongs to: "[[2024-08]]" -Tags: ["Health", "Sport"] ---- -# Cycling endurance — 2024-08-15 -90-min endurance ride at zone 2. Avg HR 135. - -## Notes -- Holiday ride, no work today so went out at 8am — still warm but manageable -- Longer loop through three villages, stopped at each for a quick water refill -- HR 136, comfortable pace, waved at other holiday cyclists -- Total distance 48 km, nearly broke 50 — next time for sure diff --git a/demo-vault-v2/event-cycling-endurance-2024-08-22.md b/demo-vault-v2/event-cycling-endurance-2024-08-22.md deleted file mode 100644 index 926ea3b5..00000000 --- a/demo-vault-v2/event-cycling-endurance-2024-08-22.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Cycling endurance — 2024-08-22"] -Is A: Event -Date: "2024-08-22" -Belongs to: "[[2024-08]]" -Tags: ["Health", "Sport"] ---- -# Cycling endurance — 2024-08-22 -90-min endurance ride at zone 2. Avg HR 135. - -## Notes -- Late summer evening ride, temperature finally dropping into the low 20s -- Took the scenic ridge road with views over the valley -- HR 134, cadence 90, felt smooth and efficient -- Sunflower fields on both sides of the road, peak summer vibes diff --git a/demo-vault-v2/event-cycling-endurance-2024-08-29.md b/demo-vault-v2/event-cycling-endurance-2024-08-29.md deleted file mode 100644 index 0ec5923e..00000000 --- a/demo-vault-v2/event-cycling-endurance-2024-08-29.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Cycling endurance — 2024-08-29"] -Is A: Event -Date: "2024-08-29" -Belongs to: "[[2024-08]]" -Tags: ["Health", "Sport"] ---- -# Cycling endurance — 2024-08-29 -90-min endurance ride at zone 2. Avg HR 135. - -## Notes -- End of summer ride, can feel the season changing — cooler mornings now -- River path heading south, mostly flat with one gentle rise -- HR 133, power 168W — slightly backing off intensity as the season winds down -- Thought a lot about autumn goals during the ride, very meditative diff --git a/demo-vault-v2/event-cycling-endurance-2024-09-05.md b/demo-vault-v2/event-cycling-endurance-2024-09-05.md deleted file mode 100644 index a79aedf3..00000000 --- a/demo-vault-v2/event-cycling-endurance-2024-09-05.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Cycling endurance — 2024-09-05"] -Is A: Event -Date: "2024-09-05" -Belongs to: "[[2024-09]]" -Tags: ["Health", "Sport"] ---- -# Cycling endurance — 2024-09-05 -90-min endurance ride at zone 2. Avg HR 135. - -## Notes -- Perfect September morning, 16C and sunny — ideal cycling weather -- Rode the countryside loop with the gentle rollers -- HR 135, consistent and controlled, no Z3 spikes even on the rises -- First ride where I didn't need to worry about heat or hydration strategy diff --git a/demo-vault-v2/event-cycling-endurance-2024-09-12.md b/demo-vault-v2/event-cycling-endurance-2024-09-12.md deleted file mode 100644 index d62904b3..00000000 --- a/demo-vault-v2/event-cycling-endurance-2024-09-12.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Cycling endurance — 2024-09-12"] -Is A: Event -Date: "2024-09-12" -Belongs to: "[[2024-09]]" -Tags: ["Health", "Sport"] ---- -# Cycling endurance — 2024-09-12 -90-min endurance ride at zone 2. Avg HR 135. - -## Notes -- Golden light ride through the orchard roads, apples ripening on the trees -- Cooler air, wore a gilet for the first time since spring -- HR 132, very easy effort — entering recovery phase after summer build -- One bottle of water was plenty, no electrolytes needed in this weather diff --git a/demo-vault-v2/event-cycling-endurance-2024-09-19.md b/demo-vault-v2/event-cycling-endurance-2024-09-19.md deleted file mode 100644 index 9e533d1f..00000000 --- a/demo-vault-v2/event-cycling-endurance-2024-09-19.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Cycling endurance — 2024-09-19"] -Is A: Event -Date: "2024-09-19" -Belongs to: "[[2024-09]]" -Tags: ["Health", "Sport"] ---- -# Cycling endurance — 2024-09-19 -90-min endurance ride at zone 2. Avg HR 135. - -## Notes -- Misty morning ride, visibility was low for the first 30 min then it burned off -- Canal path with the autumn colors just starting to show -- HR 136, power 166W — body feels rested, transitioning into fall base phase -- Saw a heron standing in the canal, absolutely still diff --git a/demo-vault-v2/event-cycling-endurance-2024-09-26.md b/demo-vault-v2/event-cycling-endurance-2024-09-26.md deleted file mode 100644 index e0176e80..00000000 --- a/demo-vault-v2/event-cycling-endurance-2024-09-26.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Cycling endurance — 2024-09-26"] -Is A: Event -Date: "2024-09-26" -Belongs to: "[[2024-09]]" -Tags: ["Health", "Sport"] ---- -# Cycling endurance — 2024-09-26 -90-min endurance ride at zone 2. Avg HR 135. - -## Notes -- Stunning autumn day, leaves turning orange and red on the tree-lined roads -- Rode the western farmland loop, 42 km, gentle rolling terrain -- HR 134 avg, legs spinning smoothly — the summer base is really paying off -- Coffee and cake after the ride, perfect way to cap off a Thursday spin diff --git a/demo-vault-v2/event-cycling-endurance-2024-10-03.md b/demo-vault-v2/event-cycling-endurance-2024-10-03.md deleted file mode 100644 index b764c625..00000000 --- a/demo-vault-v2/event-cycling-endurance-2024-10-03.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Cycling endurance — 2024-10-03"] -Is A: Event -Date: "2024-10-03" -Belongs to: "[[2024-10]]" -Tags: ["Health", "Sport"] ---- -# Cycling endurance — 2024-10-03 -90-min endurance ride at zone 2. Avg HR 135. - -## Notes -- October ride in the golden hour light, absolutely stunning colors on the tree-lined lane -- Cooler air at 13C, wore arm warmers and a gilet — perfect layering -- HR 133, power 165W, comfortable and controlled -- These fall rides are the best of the year, no question diff --git a/demo-vault-v2/event-cycling-endurance-2024-10-10.md b/demo-vault-v2/event-cycling-endurance-2024-10-10.md deleted file mode 100644 index 3d2f24d9..00000000 --- a/demo-vault-v2/event-cycling-endurance-2024-10-10.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Cycling endurance — 2024-10-10"] -Is A: Event -Date: "2024-10-10" -Belongs to: "[[2024-10]]" -Tags: ["Health", "Sport"] ---- -# Cycling endurance — 2024-10-10 -90-min endurance ride at zone 2. Avg HR 135. - -## Notes -- Rode through the forest, leaves crunching on the road, red and gold everywhere -- Easy Z2 spin, HR 135, cadence 86 rpm -- Slight headwind on the return, had to watch power to keep HR in zone -- Good recovery ride after Sunday's long group ride diff --git a/demo-vault-v2/event-cycling-endurance-2024-10-17.md b/demo-vault-v2/event-cycling-endurance-2024-10-17.md deleted file mode 100644 index ec0353be..00000000 --- a/demo-vault-v2/event-cycling-endurance-2024-10-17.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Cycling endurance — 2024-10-17"] -Is A: Event -Date: "2024-10-17" -Belongs to: "[[2024-10]]" -Tags: ["Health", "Sport"] ---- -# Cycling endurance — 2024-10-17 -90-min endurance ride at zone 2. Avg HR 135. - -## Notes -- Rainy day, almost bailed but went out anyway with mudguards and waterproof jacket -- Quieter roads than usual, had the lanes mostly to myself -- HR 137, slightly higher — probably the extra effort of riding in wet conditions -- Cleaned the bike straight after, chain was filthy diff --git a/demo-vault-v2/event-cycling-endurance-2024-10-24.md b/demo-vault-v2/event-cycling-endurance-2024-10-24.md deleted file mode 100644 index 353a6f96..00000000 --- a/demo-vault-v2/event-cycling-endurance-2024-10-24.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Cycling endurance — 2024-10-24"] -Is A: Event -Date: "2024-10-24" -Belongs to: "[[2024-10]]" -Tags: ["Health", "Sport"] ---- -# Cycling endurance — 2024-10-24 -90-min endurance ride at zone 2. Avg HR 135. - -## Notes -- Last proper outdoor ride of the month, clocks go back this weekend -- Rode the reservoir loop, beautiful mirror reflections of autumn trees in the water -- HR 132, deliberately easy as a deload week -- Bittersweet knowing the outdoor riding season is winding down diff --git a/demo-vault-v2/event-cycling-endurance-2024-10-31.md b/demo-vault-v2/event-cycling-endurance-2024-10-31.md deleted file mode 100644 index c92f4ab6..00000000 --- a/demo-vault-v2/event-cycling-endurance-2024-10-31.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Cycling endurance — 2024-10-31"] -Is A: Event -Date: "2024-10-31" -Belongs to: "[[2024-10]]" -Tags: ["Health", "Sport"] ---- -# Cycling endurance — 2024-10-31 -90-min endurance ride at zone 2. Avg HR 135. - -## Notes -- Halloween ride! Dark at 5pm now, had to use front and rear lights -- Short outdoor loop on well-lit roads, then finished the last 30 min on the trainer -- HR 134, mixed indoor/outdoor session felt a bit disjointed -- Time to accept the trainer is going to be the main venue for a while diff --git a/demo-vault-v2/event-cycling-endurance-2024-11-07.md b/demo-vault-v2/event-cycling-endurance-2024-11-07.md deleted file mode 100644 index a2af0b63..00000000 --- a/demo-vault-v2/event-cycling-endurance-2024-11-07.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Cycling endurance — 2024-11-07"] -Is A: Event -Date: "2024-11-07" -Belongs to: "[[2024-11]]" -Tags: ["Health", "Sport"] ---- -# Cycling endurance — 2024-11-07 -90-min endurance ride at zone 2. Avg HR 135. - -## Notes -- Indoor trainer, back to the Zwift routine for winter -- Watched a documentary about cycling in Colombia while pedaling -- HR 133, power 162W — trying to maintain base through the off-season -- Set up a proper fan and towel station, makes indoor riding more bearable diff --git a/demo-vault-v2/event-cycling-endurance-2024-11-14.md b/demo-vault-v2/event-cycling-endurance-2024-11-14.md deleted file mode 100644 index 49067f55..00000000 --- a/demo-vault-v2/event-cycling-endurance-2024-11-14.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Cycling endurance — 2024-11-14"] -Is A: Event -Date: "2024-11-14" -Belongs to: "[[2024-11]]" -Tags: ["Health", "Sport"] ---- -# Cycling endurance — 2024-11-14 -90-min endurance ride at zone 2. Avg HR 135. - -## Notes -- Trainer session, Zwift group workout with club — social element helps motivation -- Cadence drills: alternated between 80 and 100 rpm every 10 minutes -- HR stayed in Z2 throughout despite cadence changes, good control -- Feeling a bit of indoor fatigue already, only a few weeks in diff --git a/demo-vault-v2/event-cycling-endurance-2024-11-21.md b/demo-vault-v2/event-cycling-endurance-2024-11-21.md deleted file mode 100644 index 0df9890d..00000000 --- a/demo-vault-v2/event-cycling-endurance-2024-11-21.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Cycling endurance — 2024-11-21"] -Is A: Event -Date: "2024-11-21" -Belongs to: "[[2024-11]]" -Tags: ["Health", "Sport"] ---- -# Cycling endurance — 2024-11-21 -90-min endurance ride at zone 2. Avg HR 135. - -## Notes -- Indoor trainer with a long movie — discovered this is the best way to survive 90 min inside -- Power 158W, HR 131 — low end of Z2, not pushing hard during base phase -- Cold in the garage, had to close the door and run a small heater -- Recovery ride before a big strength session tomorrow diff --git a/demo-vault-v2/event-cycling-endurance-2024-11-28.md b/demo-vault-v2/event-cycling-endurance-2024-11-28.md deleted file mode 100644 index 53097d7c..00000000 --- a/demo-vault-v2/event-cycling-endurance-2024-11-28.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Cycling endurance — 2024-11-28"] -Is A: Event -Date: "2024-11-28" -Belongs to: "[[2024-11]]" -Tags: ["Health", "Sport"] ---- -# Cycling endurance — 2024-11-28 -90-min endurance ride at zone 2. Avg HR 135. - -## Notes -- Trainer session, played music instead of video today for a change -- Focused purely on pedaling smoothness and breathing rhythm -- HR 134, very steady, almost meditative once I stopped watching the numbers -- Proper warm-down with 10 min of stretching — hamstrings thanked me diff --git a/demo-vault-v2/event-cycling-endurance-2024-12-05.md b/demo-vault-v2/event-cycling-endurance-2024-12-05.md deleted file mode 100644 index fb1d5fdd..00000000 --- a/demo-vault-v2/event-cycling-endurance-2024-12-05.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Cycling endurance — 2024-12-05"] -Is A: Event -Date: "2024-12-05" -Belongs to: "[[2024-12]]" -Tags: ["Health", "Sport"] ---- -# Cycling endurance — 2024-12-05 -90-min endurance ride at zone 2. Avg HR 135. - -## Notes -- Indoor trainer, Zwift Innsbruck course for some virtual scenery -- Struggled with motivation today, almost cut it short at 60 min but pushed through -- HR 136, power 160W — numbers are fine, just the head wasn't in it -- Rewarded myself with hot chocolate afterwards diff --git a/demo-vault-v2/event-cycling-endurance-2024-12-12.md b/demo-vault-v2/event-cycling-endurance-2024-12-12.md deleted file mode 100644 index bffbdc67..00000000 --- a/demo-vault-v2/event-cycling-endurance-2024-12-12.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Cycling endurance — 2024-12-12"] -Is A: Event -Date: "2024-12-12" -Belongs to: "[[2024-12]]" -Tags: ["Health", "Sport"] ---- -# Cycling endurance — 2024-12-12 -90-min endurance ride at zone 2. Avg HR 135. - -## Notes -- Trainer session with a new podcast series — bingeing it keeps the sessions interesting -- Power 163W, HR 135, cadence 87 rpm — all very consistent -- Garage was properly cold, wore a base layer even while riding -- Noticing my resting HR has dropped 2 bpm over the year — base training working diff --git a/demo-vault-v2/event-cycling-endurance-2024-12-19.md b/demo-vault-v2/event-cycling-endurance-2024-12-19.md deleted file mode 100644 index a0e248b6..00000000 --- a/demo-vault-v2/event-cycling-endurance-2024-12-19.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Cycling endurance — 2024-12-19"] -Is A: Event -Date: "2024-12-19" -Belongs to: "[[2024-12]]" -Tags: ["Health", "Sport"] ---- -# Cycling endurance — 2024-12-19 -90-min endurance ride at zone 2. Avg HR 135. - -## Notes -- Last proper training ride before the Christmas break -- Indoor trainer, watched a holiday movie to get in the spirit -- HR 132, very easy spin — winding down the training volume for the year -- Reflected on a good year of consistent Z2 base work, fitness is in a great place diff --git a/demo-vault-v2/event-cycling-endurance-2024-12-26.md b/demo-vault-v2/event-cycling-endurance-2024-12-26.md deleted file mode 100644 index cbd973bd..00000000 --- a/demo-vault-v2/event-cycling-endurance-2024-12-26.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Cycling endurance — 2024-12-26"] -Is A: Event -Date: "2024-12-26" -Belongs to: "[[2024-12]]" -Tags: ["Health", "Sport"] ---- -# Cycling endurance — 2024-12-26 -90-min endurance ride at zone 2. Avg HR 135. - -## Notes -- Boxing Day spin on the trainer, needed to move after yesterday's feast -- Legs felt sluggish from two days of rest and heavy food -- HR 138, slightly elevated — probably the Christmas dinner still processing -- Light and easy, just ticking over, no pressure on power or pace diff --git a/demo-vault-v2/event-cycling-endurance-2025-01-02.md b/demo-vault-v2/event-cycling-endurance-2025-01-02.md deleted file mode 100644 index 3127384a..00000000 --- a/demo-vault-v2/event-cycling-endurance-2025-01-02.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Cycling endurance — 2025-01-02"] -Is A: Event -Date: "2025-01-02" -Belongs to: "[[2025-01]]" -Tags: ["Health", "Sport"] ---- -# Cycling endurance — 2025-01-02 -90-min endurance ride at zone 2. Avg HR 135. - -## Notes -- New Year's resolution ride, back on the trainer after the holiday break -- Legs felt surprisingly okay despite a week of eating and drinking -- HR 136, power 158W — starting the year with honest base-building -- Set a goal to ride more consistently outdoors this year once spring arrives diff --git a/demo-vault-v2/event-cycling-endurance-2025-01-09.md b/demo-vault-v2/event-cycling-endurance-2025-01-09.md deleted file mode 100644 index 046ec11c..00000000 --- a/demo-vault-v2/event-cycling-endurance-2025-01-09.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Cycling endurance — 2025-01-09"] -Is A: Event -Date: "2025-01-09" -Belongs to: "[[2025-01]]" -Tags: ["Health", "Sport"] ---- -# Cycling endurance — 2025-01-09 -90-min endurance ride at zone 2. Avg HR 135. - -## Notes -- Indoor trainer, Zwift Makuri Islands — at least the virtual scenery is tropical -- Binge-watching a series while pedaling, knocked out two episodes -- HR 133, cadence 86 rpm, very stable — second year of Z2 base and I know exactly how to pace -- One bottle of water, light snack before riding diff --git a/demo-vault-v2/event-cycling-endurance-2025-01-16.md b/demo-vault-v2/event-cycling-endurance-2025-01-16.md deleted file mode 100644 index 52983f9b..00000000 --- a/demo-vault-v2/event-cycling-endurance-2025-01-16.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Cycling endurance — 2025-01-16"] -Is A: Event -Date: "2025-01-16" -Belongs to: "[[2025-01]]" -Tags: ["Health", "Sport"] ---- -# Cycling endurance — 2025-01-16 -90-min endurance ride at zone 2. Avg HR 135. - -## Notes -- Trainer session, tried a new podcast on sports science — really interesting episode on mitochondrial density -- Power 165W at HR 132 — noticeably better efficiency than January last year at the same HR -- Garage was cold enough to see my breath, but the effort kept me warm -- Easy day, legs recovering from a tough Tuesday diff --git a/demo-vault-v2/event-cycling-endurance-2025-01-23.md b/demo-vault-v2/event-cycling-endurance-2025-01-23.md deleted file mode 100644 index bbf4e3b3..00000000 --- a/demo-vault-v2/event-cycling-endurance-2025-01-23.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Cycling endurance — 2025-01-23"] -Is A: Event -Date: "2025-01-23" -Belongs to: "[[2025-01]]" -Tags: ["Health", "Sport"] ---- -# Cycling endurance — 2025-01-23 -90-min endurance ride at zone 2. Avg HR 135. - -## Notes -- Indoor trainer with a film, getting through my winter movie backlog -- Experimented with a new saddle position — 2mm higher, felt more open in the hips -- HR 135, power 167W — numbers suggest the position change is neutral or slightly better -- Stretched properly after, hip flexors were tight from the desk all day diff --git a/demo-vault-v2/event-cycling-endurance-2025-01-30.md b/demo-vault-v2/event-cycling-endurance-2025-01-30.md deleted file mode 100644 index 94ece183..00000000 --- a/demo-vault-v2/event-cycling-endurance-2025-01-30.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Cycling endurance — 2025-01-30"] -Is A: Event -Date: "2025-01-30" -Belongs to: "[[2025-01]]" -Tags: ["Health", "Sport"] ---- -# Cycling endurance — 2025-01-30 -90-min endurance ride at zone 2. Avg HR 135. - -## Notes -- End of January, one month of consistent trainer base in the books -- Zwift pace partner ride, nice to draft in a virtual group -- HR 134, very controlled, zero Z3 spikes today -- Motivation is solid this year — I think having a structured plan makes the trainer more bearable diff --git a/demo-vault-v2/event-cycling-endurance-2025-02-06.md b/demo-vault-v2/event-cycling-endurance-2025-02-06.md deleted file mode 100644 index 44571cbd..00000000 --- a/demo-vault-v2/event-cycling-endurance-2025-02-06.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Cycling endurance — 2025-02-06"] -Is A: Event -Date: "2025-02-06" -Belongs to: "[[2025-02]]" -Tags: ["Health", "Sport"] ---- -# Cycling endurance — 2025-02-06 -90-min endurance ride at zone 2. Avg HR 135. - -## Notes -- Indoor trainer, Netflix documentary on pro cycling training camps -- Power 168W at HR 133 — aerobic engine is clearly stronger than this time last year -- Did 5 min single-leg drills at the start, working on eliminating dead spots -- Drank a full bottle of electrolyte mix, staying on top of hydration even indoors diff --git a/demo-vault-v2/event-cycling-endurance-2025-02-13.md b/demo-vault-v2/event-cycling-endurance-2025-02-13.md deleted file mode 100644 index 625a831e..00000000 --- a/demo-vault-v2/event-cycling-endurance-2025-02-13.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Cycling endurance — 2025-02-13"] -Is A: Event -Date: "2025-02-13" -Belongs to: "[[2025-02]]" -Tags: ["Health", "Sport"] ---- -# Cycling endurance — 2025-02-13 -90-min endurance ride at zone 2. Avg HR 135. - -## Notes -- Trainer session, club Zwift ride — good to chat with riding mates during the dark months -- Kept the effort honest, HR 135, let faster riders go when they pushed the pace -- Feeling a bit stale from indoor riding, counting down the weeks to spring -- Had porridge with honey an hour before, energy was steady throughout diff --git a/demo-vault-v2/event-cycling-endurance-2025-02-20.md b/demo-vault-v2/event-cycling-endurance-2025-02-20.md deleted file mode 100644 index 1ce6e5d6..00000000 --- a/demo-vault-v2/event-cycling-endurance-2025-02-20.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Cycling endurance — 2025-02-20"] -Is A: Event -Date: "2025-02-20" -Belongs to: "[[2025-02]]" -Tags: ["Health", "Sport"] ---- -# Cycling endurance — 2025-02-20 -90-min endurance ride at zone 2. Avg HR 135. - -## Notes -- Indoor trainer, put on an old Tour de France stage replay — col du Tourmalet -- Played with cadence: 15 min blocks at 80, 90, and 100 rpm to break up the monotony -- HR stayed at 134 across all cadences, good aerobic control -- Stretching session after — foam roller on quads and IT band diff --git a/demo-vault-v2/event-cycling-endurance-2025-02-27.md b/demo-vault-v2/event-cycling-endurance-2025-02-27.md deleted file mode 100644 index 21eede8c..00000000 --- a/demo-vault-v2/event-cycling-endurance-2025-02-27.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Cycling endurance — 2025-02-27"] -Is A: Event -Date: "2025-02-27" -Belongs to: "[[2025-02]]" -Tags: ["Health", "Sport"] ---- -# Cycling endurance — 2025-02-27 -90-min endurance ride at zone 2. Avg HR 135. - -## Notes -- Last February session, can feel spring approaching — longer daylight now -- Trainer ride with music, upbeat playlist to keep spirits high -- HR 131, very easy effort — deload week before ramping up in March -- Planning some outdoor routes for next month, excited to get back on real roads diff --git a/demo-vault-v2/event-cycling-endurance-2025-03-06.md b/demo-vault-v2/event-cycling-endurance-2025-03-06.md deleted file mode 100644 index da251e60..00000000 --- a/demo-vault-v2/event-cycling-endurance-2025-03-06.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Cycling endurance — 2025-03-06"] -Is A: Event -Date: "2025-03-06" -Belongs to: "[[2025-03]]" -Tags: ["Health", "Sport"] ---- -# Cycling endurance — 2025-03-06 -90-min endurance ride at zone 2. Avg HR 135. - -## Notes -- First outdoor ride of 2025! Cold but clear, 8C and bright sunshine -- Flat river path, 40 km, felt amazing to be outside after months on the trainer -- HR 137, slightly higher outdoors as expected — the wind and terrain variation -- Wore full winter kit including overshoes, hands were still cold for the first 20 min diff --git a/demo-vault-v2/event-cycling-endurance-2025-03-13.md b/demo-vault-v2/event-cycling-endurance-2025-03-13.md deleted file mode 100644 index 038298d8..00000000 --- a/demo-vault-v2/event-cycling-endurance-2025-03-13.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Cycling endurance — 2025-03-13"] -Is A: Event -Date: "2025-03-13" -Belongs to: "[[2025-03]]" -Tags: ["Health", "Sport"] ---- -# Cycling endurance — 2025-03-13 -90-min endurance ride at zone 2. Avg HR 135. - -## Notes -- Outdoor ride on the canal towpath, exploring the northern extension I discovered last spring -- HR 135, power 172W — year-on-year comparison shows about 8W more at the same HR -- Mild day at 11C, just a jersey and gilet, spring is here -- Saw the first cyclists in club kit out training, the roads are waking up diff --git a/demo-vault-v2/event-cycling-endurance-2025-03-20.md b/demo-vault-v2/event-cycling-endurance-2025-03-20.md deleted file mode 100644 index 07090ac9..00000000 --- a/demo-vault-v2/event-cycling-endurance-2025-03-20.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Cycling endurance — 2025-03-20"] -Is A: Event -Date: "2025-03-20" -Belongs to: "[[2025-03]]" -Tags: ["Health", "Sport"] ---- -# Cycling endurance — 2025-03-20 -90-min endurance ride at zone 2. Avg HR 135. - -## Notes -- Spring equinox, rode out to watch the sunset at the hilltop viewpoint -- Gentle climbing route, HR peaked at 145 on the final hill but otherwise solid Z2 -- 44 km total, feeling confident on longer routes now -- Stopped at the village pub for a quick water refill, chatted with the barman about cycling diff --git a/demo-vault-v2/event-cycling-endurance-2025-03-27.md b/demo-vault-v2/event-cycling-endurance-2025-03-27.md deleted file mode 100644 index 8c7c464f..00000000 --- a/demo-vault-v2/event-cycling-endurance-2025-03-27.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Cycling endurance — 2025-03-27"] -Is A: Event -Date: "2025-03-27" -Belongs to: "[[2025-03]]" -Tags: ["Health", "Sport"] ---- -# Cycling endurance — 2025-03-27 -90-min endurance ride at zone 2. Avg HR 135. - -## Notes -- Outdoor ride through the rolling farmland, hedgerows budding green -- Used the small ring on climbs to keep HR honest — worked much better than last year -- HR 134 avg, only one brief Z3 excursion, disciplined effort -- Clocks forward this weekend — evening rides are about to get much more feasible diff --git a/demo-vault-v2/event-cycling-endurance-2025-04-03.md b/demo-vault-v2/event-cycling-endurance-2025-04-03.md deleted file mode 100644 index 4962b301..00000000 --- a/demo-vault-v2/event-cycling-endurance-2025-04-03.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Cycling endurance — 2025-04-03"] -Is A: Event -Date: "2025-04-03" -Belongs to: "[[2025-04]]" -Tags: ["Health", "Sport"] ---- -# Cycling endurance — 2025-04-03 -90-min endurance ride at zone 2. Avg HR 135. - -## Notes -- Outdoor ride through the blossoming orchards, petals drifting across the road -- 14C and overcast, perfect endurance weather — no wind today -- HR 133, power 175W — power at Z2 HR is the best it's ever been -- Easy recovery spin after a tough interval block this week diff --git a/demo-vault-v2/event-cycling-endurance-2025-04-10.md b/demo-vault-v2/event-cycling-endurance-2025-04-10.md deleted file mode 100644 index bd858cf4..00000000 --- a/demo-vault-v2/event-cycling-endurance-2025-04-10.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Cycling endurance — 2025-04-10"] -Is A: Event -Date: "2025-04-10" -Belongs to: "[[2025-04]]" -Tags: ["Health", "Sport"] ---- -# Cycling endurance — 2025-04-10 -90-min endurance ride at zone 2. Avg HR 135. - -## Notes -- Explored a completely new route west, through villages I've never cycled through -- Rolling terrain with a couple of sharp little kickers — geared down to stay in Z2 -- HR 136 avg, 46 km total, expanding my usual radius -- Stopped at a farm shop for a cold drink, chatted with the owner about local cycling routes diff --git a/demo-vault-v2/event-cycling-endurance-2025-04-17.md b/demo-vault-v2/event-cycling-endurance-2025-04-17.md deleted file mode 100644 index e3cb2ed8..00000000 --- a/demo-vault-v2/event-cycling-endurance-2025-04-17.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Cycling endurance — 2025-04-17"] -Is A: Event -Date: "2025-04-17" -Belongs to: "[[2025-04]]" -Tags: ["Health", "Sport"] ---- -# Cycling endurance — 2025-04-17 -90-min endurance ride at zone 2. Avg HR 135. - -## Notes -- After-work ride in gorgeous evening light, didn't get out until 6pm but still warm -- Canal towpath south, completely flat, meditative spinning -- HR 132, cadence 90, very relaxed, mind wandering freely -- Brought one bottle, drank half — not hot enough yet to need more diff --git a/demo-vault-v2/event-cycling-endurance-2025-04-24.md b/demo-vault-v2/event-cycling-endurance-2025-04-24.md deleted file mode 100644 index d30779ea..00000000 --- a/demo-vault-v2/event-cycling-endurance-2025-04-24.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Cycling endurance — 2025-04-24"] -Is A: Event -Date: "2025-04-24" -Belongs to: "[[2025-04]]" -Tags: ["Health", "Sport"] ---- -# Cycling endurance — 2025-04-24 -90-min endurance ride at zone 2. Avg HR 135. - -## Notes -- Morning ride before a busy work day, out at 6:30am -- Took the reservoir loop, water was glassy and still in the early light -- HR 135, power 174W — hitting these numbers consistently now -- Quick shower and breakfast, at my desk by 9am feeling energized diff --git a/demo-vault-v2/event-cycling-endurance-2025-05-01.md b/demo-vault-v2/event-cycling-endurance-2025-05-01.md deleted file mode 100644 index 05b073c9..00000000 --- a/demo-vault-v2/event-cycling-endurance-2025-05-01.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Cycling endurance — 2025-05-01"] -Is A: Event -Date: "2025-05-01" -Belongs to: "[[2025-05]]" -Tags: ["Health", "Sport"] ---- -# Cycling endurance — 2025-05-01 -90-min endurance ride at zone 2. Avg HR 135. - -## Notes -- May Day ride, holiday so no rush — left at 9am and took the scenic route -- Through the rapeseed fields again, same brilliant yellow as last year -- HR 134, easy and comfortable, legs spinning freely -- Stopped at the village cafe for an espresso and a croissant, sat in the sun for 15 min diff --git a/demo-vault-v2/event-cycling-endurance-2025-05-08.md b/demo-vault-v2/event-cycling-endurance-2025-05-08.md deleted file mode 100644 index 603a74f9..00000000 --- a/demo-vault-v2/event-cycling-endurance-2025-05-08.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Cycling endurance — 2025-05-08"] -Is A: Event -Date: "2025-05-08" -Belongs to: "[[2025-05]]" -Tags: ["Health", "Sport"] ---- -# Cycling endurance — 2025-05-08 -90-min endurance ride at zone 2. Avg HR 135. - -## Notes -- Windy day, picked a sheltered valley route to avoid fighting headwinds -- HR 135, power 170W, cadence 88 — dialed in and automatic -- Saw a pair of red kites circling above the fields, stopped briefly to watch -- Pre-rest-day easy effort, keeping the legs moving before a day off tomorrow diff --git a/demo-vault-v2/event-cycling-endurance-2025-05-15.md b/demo-vault-v2/event-cycling-endurance-2025-05-15.md deleted file mode 100644 index 3bec5e2f..00000000 --- a/demo-vault-v2/event-cycling-endurance-2025-05-15.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Cycling endurance — 2025-05-15"] -Is A: Event -Date: "2025-05-15" -Belongs to: "[[2025-05]]" -Tags: ["Health", "Sport"] ---- -# Cycling endurance — 2025-05-15 -90-min endurance ride at zone 2. Avg HR 135. - -## Notes -- Rode with a friend for the first time in weeks, matched paces at Z2 -- Great conversation about summer cycling plans, time flew by -- HR 136, slightly higher than solo because we pushed a bit on the false flat -- 48 km together, longest Z2 ride this month diff --git a/demo-vault-v2/event-cycling-endurance-2025-05-22.md b/demo-vault-v2/event-cycling-endurance-2025-05-22.md deleted file mode 100644 index c4b15fde..00000000 --- a/demo-vault-v2/event-cycling-endurance-2025-05-22.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Cycling endurance — 2025-05-22"] -Is A: Event -Date: "2025-05-22" -Belongs to: "[[2025-05]]" -Tags: ["Health", "Sport"] ---- -# Cycling endurance — 2025-05-22 -90-min endurance ride at zone 2. Avg HR 135. - -## Notes -- Warm evening ride after work, 22C and light breeze -- Countryside lanes heading east, wildflowers blooming in the verges -- HR 133, power 176W — these are the best numbers I've posted at Z2, ever -- Two bottles, one plain water, one with electrolyte mix diff --git a/demo-vault-v2/event-cycling-endurance-2025-05-29.md b/demo-vault-v2/event-cycling-endurance-2025-05-29.md deleted file mode 100644 index 1c4a7e12..00000000 --- a/demo-vault-v2/event-cycling-endurance-2025-05-29.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Cycling endurance — 2025-05-29"] -Is A: Event -Date: "2025-05-29" -Belongs to: "[[2025-05]]" -Tags: ["Health", "Sport"] ---- -# Cycling endurance — 2025-05-29 -90-min endurance ride at zone 2. Avg HR 135. - -## Notes -- Early morning ride to beat the afternoon thunderstorms forecast -- Flat loop through the park and along the river, 45 km -- HR 134, cadence 89, feeling strong and efficient mid-season -- Fueled with toast and peanut butter before, one banana in the jersey pocket just in case diff --git a/demo-vault-v2/event-cycling-endurance-2025-06-05.md b/demo-vault-v2/event-cycling-endurance-2025-06-05.md deleted file mode 100644 index 94300b7d..00000000 --- a/demo-vault-v2/event-cycling-endurance-2025-06-05.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Cycling endurance — 2025-06-05"] -Is A: Event -Date: "2025-06-05" -Belongs to: "[[2025-06]]" -Tags: ["Health", "Sport"] ---- -# Cycling endurance — 2025-06-05 -90-min endurance ride at zone 2. Avg HR 135. - -## Notes -- Out at 6am to beat the heat, already 20C at sunrise -- River path heading west, shaded sections through the woodland -- HR 137, slightly elevated from the warmth despite the early start -- Drained both bottles, need to start bringing a third or planning a refill stop diff --git a/demo-vault-v2/event-cycling-endurance-2025-06-12.md b/demo-vault-v2/event-cycling-endurance-2025-06-12.md deleted file mode 100644 index f9c8258e..00000000 --- a/demo-vault-v2/event-cycling-endurance-2025-06-12.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Cycling endurance — 2025-06-12"] -Is A: Event -Date: "2025-06-12" -Belongs to: "[[2025-06]]" -Tags: ["Health", "Sport"] ---- -# Cycling endurance — 2025-06-12 -90-min endurance ride at zone 2. Avg HR 135. - -## Notes -- Cafe ride to the hilltop spot, the terrace has the best views in the area -- Gentle climb there, fast descent back, moving time 90 min exactly -- HR 135 avg, one brief Z3 moment on the final ramp before the cafe -- Iced latte at the top, watched other cyclists coming and going — peak summer cycling scene diff --git a/demo-vault-v2/event-cycling-endurance-2025-06-19.md b/demo-vault-v2/event-cycling-endurance-2025-06-19.md deleted file mode 100644 index 6304d279..00000000 --- a/demo-vault-v2/event-cycling-endurance-2025-06-19.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Cycling endurance — 2025-06-19"] -Is A: Event -Date: "2025-06-19" -Belongs to: "[[2025-06]]" -Tags: ["Health", "Sport"] ---- -# Cycling endurance — 2025-06-19 -90-min endurance ride at zone 2. Avg HR 135. - -## Notes -- Nearly the longest day again, rode out at 5:30am with golden light flooding the fields -- Countryside loop past the wheat fields, swaying in the breeze -- HR 132, power 178W — new all-time best power at this HR, eighteen months of Z2 base paying off -- Stopped at the public fountain to refill, summer hydration strategy is locked in now diff --git a/demo-vault-v2/event-dinner-2024-01-05.md b/demo-vault-v2/event-dinner-2024-01-05.md deleted file mode 100644 index 40e8d4da..00000000 --- a/demo-vault-v2/event-dinner-2024-01-05.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -aliases: ["Dinner — 2024-01-05"] -Is A: Event -Date: "2024-01-05" -Belongs to: "[[2024-01]]" -Related to: ["[[person-elisa-barbieri]]"] -Tags: ["Personal"] ---- -# Dinner — 2024-01-05 -Evening dinner with Elisa Barbieri. - -## Notes -- Went to a small trattoria near Porta Venezia that Elisa had been wanting to try for weeks -- She's been thinking about switching jobs — we talked through the pros and cons over a bottle of Barbera -- The homemade pappardelle with wild boar ragu was outstanding, easily the best I've had in Milan -- Relaxed Friday night vibe, no rush — we stayed until they started putting chairs on tables diff --git a/demo-vault-v2/event-dinner-2024-01-12.md b/demo-vault-v2/event-dinner-2024-01-12.md deleted file mode 100644 index 456c1dfd..00000000 --- a/demo-vault-v2/event-dinner-2024-01-12.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -aliases: ["Dinner — 2024-01-12"] -Is A: Event -Date: "2024-01-12" -Belongs to: "[[2024-01]]" -Related to: ["[[person-marta-pellegrini]]"] -Tags: ["Personal"] ---- -# Dinner — 2024-01-12 -Evening dinner with Marta Pellegrini. - -## Notes -- Marta cooked at her place — a risotto alla milanese that was genuinely perfect -- Talked about her recent trip to Lisbon and how she's considering doing a remote work stint there -- She recommended a podcast on urban design that I've been meaning to listen to -- Cozy evening in, rain outside — exactly the kind of January night you want diff --git a/demo-vault-v2/event-dinner-2024-01-19.md b/demo-vault-v2/event-dinner-2024-01-19.md deleted file mode 100644 index 4c65bc74..00000000 --- a/demo-vault-v2/event-dinner-2024-01-19.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -aliases: ["Dinner — 2024-01-19"] -Is A: Event -Date: "2024-01-19" -Belongs to: "[[2024-01]]" -Related to: ["[[person-giulia-conti]]"] -Tags: ["Personal"] ---- -# Dinner — 2024-01-19 -Evening dinner with Giulia Conti. - -## Notes -- Met at a new sushi spot in Navigli that Giulia spotted on Instagram -- She's deep into her PhD thesis — talked about the stress of her advisor's feedback cycles -- Ordered way too much food, but the tuna tataki was worth every bite -- Giulia was in great spirits despite the thesis pressure — always a fun evening with her diff --git a/demo-vault-v2/event-dinner-2024-02-23.md b/demo-vault-v2/event-dinner-2024-02-23.md deleted file mode 100644 index 65d6f3e9..00000000 --- a/demo-vault-v2/event-dinner-2024-02-23.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -aliases: ["Dinner — 2024-02-23"] -Is A: Event -Date: "2024-02-23" -Belongs to: "[[2024-02]]" -Related to: ["[[person-elisa-barbieri]]"] -Tags: ["Personal"] ---- -# Dinner — 2024-02-23 -Evening dinner with Elisa Barbieri. - -## Notes -- Pizza night at Spontini — classic choice, nothing fancy but always satisfying -- Elisa got the job offer she was hoping for — we celebrated with a prosecco -- Talked about how the tech scene in Milan is changing, more startups popping up -- Lively energy, felt like a proper celebration dinner even at a pizzeria diff --git a/demo-vault-v2/event-dinner-2024-03-01.md b/demo-vault-v2/event-dinner-2024-03-01.md deleted file mode 100644 index 90ebcb43..00000000 --- a/demo-vault-v2/event-dinner-2024-03-01.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -aliases: ["Dinner — 2024-03-01"] -Is A: Event -Date: "2024-03-01" -Belongs to: "[[2024-03]]" -Related to: ["[[person-tommaso-greco]]"] -Tags: ["Personal"] ---- -# Dinner — 2024-03-01 -Evening dinner with Tommaso Greco. - -## Notes -- Grabbed burgers at a new American-style diner near Centrale that Tommaso had been raving about -- He's working on a side project — some kind of music recommendation app — and wanted my take on the architecture -- Got into a friendly debate about whether Rust or Go is the better choice for backends -- Fun, nerdy evening — the kind of conversation that makes you want to go home and code diff --git a/demo-vault-v2/event-dinner-2024-04-05.md b/demo-vault-v2/event-dinner-2024-04-05.md deleted file mode 100644 index f1b293a3..00000000 --- a/demo-vault-v2/event-dinner-2024-04-05.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -aliases: ["Dinner — 2024-04-05"] -Is A: Event -Date: "2024-04-05" -Belongs to: "[[2024-04]]" -Related to: ["[[person-giulia-conti]]"] -Tags: ["Personal"] ---- -# Dinner — 2024-04-05 -Evening dinner with Giulia Conti. - -## Notes -- Giulia picked a wine bar in Brera with an amazing tagliere di formaggi -- Her thesis defense date is set for June — she's nervous but well-prepared -- We split a bottle of Gewurztraminer that paired perfectly with the cheese selection -- Warm spring evening, sat outside for the first time this year — the city felt alive diff --git a/demo-vault-v2/event-dinner-2024-04-19.md b/demo-vault-v2/event-dinner-2024-04-19.md deleted file mode 100644 index 74641d26..00000000 --- a/demo-vault-v2/event-dinner-2024-04-19.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -aliases: ["Dinner — 2024-04-19"] -Is A: Event -Date: "2024-04-19" -Belongs to: "[[2024-04]]" -Related to: ["[[person-tommaso-greco]]"] -Tags: ["Personal"] ---- -# Dinner — 2024-04-19 -Evening dinner with Tommaso Greco. - -## Notes -- Cooked pasta aglio olio e peperoncino at my place — quick and honest -- Tommaso showed me a demo of his music app — the UI needs work but the concept is solid -- Ended up watching a documentary about the early days of the internet after dinner -- Chill Friday evening, no agenda — just good food and good company diff --git a/demo-vault-v2/event-dinner-2024-05-24.md b/demo-vault-v2/event-dinner-2024-05-24.md deleted file mode 100644 index c7a23095..00000000 --- a/demo-vault-v2/event-dinner-2024-05-24.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -aliases: ["Dinner — 2024-05-24"] -Is A: Event -Date: "2024-05-24" -Belongs to: "[[2024-05]]" -Related to: ["[[person-gianluca-esposito]]"] -Tags: ["Personal"] ---- -# Dinner — 2024-05-24 -Evening dinner with Gianluca Esposito. - -## Notes -- Met at a Neapolitan pizzeria in Isola — Gianluca is particular about his pizza and this place passed the test -- He's been traveling for work a lot lately, told stories about a chaotic conference in Berlin -- Tried their frittura di paranza as an appetizer — crispy, light, excellent -- Haven't seen Gianluca in months so it was good to properly catch up over a long dinner diff --git a/demo-vault-v2/event-dinner-2024-06-21.md b/demo-vault-v2/event-dinner-2024-06-21.md deleted file mode 100644 index 65dfb3ba..00000000 --- a/demo-vault-v2/event-dinner-2024-06-21.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -aliases: ["Dinner — 2024-06-21"] -Is A: Event -Date: "2024-06-21" -Belongs to: "[[2024-06]]" -Related to: ["[[person-anna-fontana]]"] -Tags: ["Personal"] ---- -# Dinner — 2024-06-21 -Evening dinner with Anna Fontana. - -## Notes -- Anna suggested a rooftop aperitivo spot near Duomo, then we walked to a Thai place for dinner -- She's been promoted at her firm — managing a small team now, adjusting to the new responsibilities -- The pad thai was mediocre but the conversation more than made up for it -- Longest day of the year — still light outside when we left the restaurant at 9:30 diff --git a/demo-vault-v2/event-dinner-2024-06-28.md b/demo-vault-v2/event-dinner-2024-06-28.md deleted file mode 100644 index 300c4f3e..00000000 --- a/demo-vault-v2/event-dinner-2024-06-28.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -aliases: ["Dinner — 2024-06-28"] -Is A: Event -Date: "2024-06-28" -Belongs to: "[[2024-06]]" -Related to: ["[[person-federico-moretti]]"] -Tags: ["Personal"] ---- -# Dinner — 2024-06-28 -Evening dinner with Federico Moretti. - -## Notes -- Federico hosted a BBQ on his terrace — perfect summer evening for it -- Talked about his plans to buy an apartment in Milan, the market is insane right now -- He grilled some incredible sausages from a butcher in Bergamo his family knows -- A few other friends dropped by later, turned into a mini party until midnight diff --git a/demo-vault-v2/event-dinner-2024-07-19.md b/demo-vault-v2/event-dinner-2024-07-19.md deleted file mode 100644 index c939f283..00000000 --- a/demo-vault-v2/event-dinner-2024-07-19.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -aliases: ["Dinner — 2024-07-19"] -Is A: Event -Date: "2024-07-19" -Belongs to: "[[2024-07]]" -Related to: ["[[person-mattia-de-luca]]"] -Tags: ["Personal"] ---- -# Dinner — 2024-07-19 -Evening dinner with Mattia De Luca. - -## Notes -- Tried a new poke bowl place near Porta Garibaldi — decent, nothing special -- Mattia is deep into a startup idea around AI-assisted legal document review, picked my brain on technical feasibility -- We walked along the Naviglio afterwards, gelato in hand — stracciatella for me, pistachio for him -- Hot July evening but the breeze off the canal made it bearable diff --git a/demo-vault-v2/event-dinner-2024-08-02.md b/demo-vault-v2/event-dinner-2024-08-02.md deleted file mode 100644 index 878b80e9..00000000 --- a/demo-vault-v2/event-dinner-2024-08-02.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -aliases: ["Dinner — 2024-08-02"] -Is A: Event -Date: "2024-08-02" -Belongs to: "[[2024-08]]" -Related to: ["[[person-lorenzo-galli]]"] -Tags: ["Personal"] ---- -# Dinner — 2024-08-02 -Evening dinner with Lorenzo Galli. - -## Notes -- Lorenzo picked an osteria in Porta Romana with a courtyard garden — hidden gem -- He just got back from two weeks in Sardinia, looked tanned and completely recharged -- Shared a massive bistecca alla fiorentina — perfectly cooked, rare in the center -- Talked about potentially doing a hiking trip together in the Dolomites this autumn diff --git a/demo-vault-v2/event-dinner-2024-08-09.md b/demo-vault-v2/event-dinner-2024-08-09.md deleted file mode 100644 index b84eb194..00000000 --- a/demo-vault-v2/event-dinner-2024-08-09.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -aliases: ["Dinner — 2024-08-09"] -Is A: Event -Date: "2024-08-09" -Belongs to: "[[2024-08]]" -Related to: ["[[person-tommaso-greco]]"] -Tags: ["Personal"] ---- -# Dinner — 2024-08-09 -Evening dinner with Tommaso Greco. - -## Notes -- Quick dinner at a kebab place near his apartment — August in Milan, everything good is closed -- Tommaso launched his music app in beta — showed me the first user feedback, mostly positive -- We brainstormed some UX improvements over baklava and Turkish tea -- Low-key summer evening, half the city is on vacation but we're both still here working diff --git a/demo-vault-v2/event-dinner-2024-08-16.md b/demo-vault-v2/event-dinner-2024-08-16.md deleted file mode 100644 index 6f86c95c..00000000 --- a/demo-vault-v2/event-dinner-2024-08-16.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -aliases: ["Dinner — 2024-08-16"] -Is A: Event -Date: "2024-08-16" -Belongs to: "[[2024-08]]" -Related to: ["[[person-chiara-romano]]"] -Tags: ["Personal"] ---- -# Dinner — 2024-08-16 -Evening dinner with Chiara Romano. - -## Notes -- Chiara invited me over — she made an incredible caprese with burrata from Puglia and fresh basil from her balcony -- We talked about her photography project documenting abandoned buildings in Lombardy -- She opened a bottle of Vermentino that was crisp and perfect for the heat -- Quiet post-Ferragosto dinner, the neighborhood was deserted — felt like we had the city to ourselves diff --git a/demo-vault-v2/event-dinner-2024-08-23.md b/demo-vault-v2/event-dinner-2024-08-23.md deleted file mode 100644 index d2c2d043..00000000 --- a/demo-vault-v2/event-dinner-2024-08-23.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -aliases: ["Dinner — 2024-08-23"] -Is A: Event -Date: "2024-08-23" -Belongs to: "[[2024-08]]" -Related to: ["[[person-alessandro-ferrari]]"] -Tags: ["Personal"] ---- -# Dinner — 2024-08-23 -Evening dinner with Alessandro Ferrari. - -## Notes -- Met Alessandro at a craft beer pub in Lambrate — he wanted to try their new IPA lineup -- He's been dealing with burnout at work, we had an honest conversation about setting boundaries -- The beer was excellent but the food was just okay — stick to the drinks menu there -- Good to see him opening up; sometimes a Friday beer is all the therapy you need diff --git a/demo-vault-v2/event-dinner-2024-09-13.md b/demo-vault-v2/event-dinner-2024-09-13.md deleted file mode 100644 index 42c862cc..00000000 --- a/demo-vault-v2/event-dinner-2024-09-13.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -aliases: ["Dinner — 2024-09-13"] -Is A: Event -Date: "2024-09-13" -Belongs to: "[[2024-09]]" -Related to: ["[[person-nicola-fabbri]]"] -Tags: ["Personal"] ---- -# Dinner — 2024-09-13 -Evening dinner with Nicola Fabbri. - -## Notes -- Nicola booked a table at a proper Milanese restaurant near Sant'Ambrogio — old school, white tablecloths -- He ordered cotoletta alla milanese (of course) and I went with ossobuco — both fantastic -- Talked about his kids starting school and how fast time flies -- Warm, unhurried evening — Nicola always brings a calm energy that makes everything feel grounded diff --git a/demo-vault-v2/event-dinner-2024-10-04.md b/demo-vault-v2/event-dinner-2024-10-04.md deleted file mode 100644 index a85d895d..00000000 --- a/demo-vault-v2/event-dinner-2024-10-04.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -aliases: ["Dinner — 2024-10-04"] -Is A: Event -Date: "2024-10-04" -Belongs to: "[[2024-10]]" -Related to: ["[[person-mattia-de-luca]]"] -Tags: ["Personal"] ---- -# Dinner — 2024-10-04 -Evening dinner with Mattia De Luca. - -## Notes -- Indian restaurant in Città Studi — Mattia's been on a curry kick lately -- His startup got into a pre-seed accelerator, he was buzzing with nervous excitement -- The chicken tikka masala was solid but the garlic naan stole the show -- Talked through his pitch deck over chai tea — I think the story is compelling diff --git a/demo-vault-v2/event-dinner-2024-10-11.md b/demo-vault-v2/event-dinner-2024-10-11.md deleted file mode 100644 index 96052240..00000000 --- a/demo-vault-v2/event-dinner-2024-10-11.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -aliases: ["Dinner — 2024-10-11"] -Is A: Event -Date: "2024-10-11" -Belongs to: "[[2024-10]]" -Related to: ["[[person-chiara-romano]]"] -Tags: ["Personal"] ---- -# Dinner — 2024-10-11 -Evening dinner with Chiara Romano. - -## Notes -- Tried a new Ethiopian restaurant near Colonne di San Lorenzo that Chiara read about -- We shared a big injera platter — the doro wat was incredible, perfectly spiced -- She showed me prints from her abandoned buildings series, really striking work -- Rainy October evening, the restaurant was half-empty and we lingered for hours diff --git a/demo-vault-v2/event-dinner-2024-10-18.md b/demo-vault-v2/event-dinner-2024-10-18.md deleted file mode 100644 index ad3541fd..00000000 --- a/demo-vault-v2/event-dinner-2024-10-18.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -aliases: ["Dinner — 2024-10-18"] -Is A: Event -Date: "2024-10-18" -Belongs to: "[[2024-10]]" -Related to: ["[[person-mattia-de-luca]]"] -Tags: ["Personal"] ---- -# Dinner — 2024-10-18 -Evening dinner with Mattia De Luca. - -## Notes -- Quick pasta at my place — threw together a cacio e pepe that turned out surprisingly well -- Mattia needed to vent about investor meetings — the fundraising grind is real -- We compared notes on productivity tools, he's switched to Obsidian and wanted tips -- Short but needed catch-up on a Friday when we were both running on fumes diff --git a/demo-vault-v2/event-dinner-2024-10-25.md b/demo-vault-v2/event-dinner-2024-10-25.md deleted file mode 100644 index 7936c12f..00000000 --- a/demo-vault-v2/event-dinner-2024-10-25.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -aliases: ["Dinner — 2024-10-25"] -Is A: Event -Date: "2024-10-25" -Belongs to: "[[2024-10]]" -Related to: ["[[person-silvia-mancini]]"] -Tags: ["Personal"] ---- -# Dinner — 2024-10-25 -Evening dinner with Silvia Mancini. - -## Notes -- Silvia chose a seafood place in Porta Genova, right by the canal -- She's been freelancing as a UX consultant and business is picking up — we swapped client war stories -- The grilled octopus was perfectly tender, served with potatoes and olives -- Lively evening with lots of laughing — Silvia has the best stories about difficult stakeholders diff --git a/demo-vault-v2/event-dinner-2024-11-01.md b/demo-vault-v2/event-dinner-2024-11-01.md deleted file mode 100644 index 2d8843f3..00000000 --- a/demo-vault-v2/event-dinner-2024-11-01.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -aliases: ["Dinner — 2024-11-01"] -Is A: Event -Date: "2024-11-01" -Belongs to: "[[2024-11]]" -Related to: ["[[person-marta-pellegrini]]"] -Tags: ["Personal"] ---- -# Dinner — 2024-11-01 -Evening dinner with Marta Pellegrini. - -## Notes -- Ognissanti holiday so we did a long lunch that turned into dinner at a bistrot in Brera -- Marta came back from a week in Lisbon — she's seriously considering the move now -- We shared a charcuterie board and then she ordered the best tiramisu I've ever tasted -- Deep conversation about what it means to feel at home somewhere — one of those talks you remember diff --git a/demo-vault-v2/event-dinner-2024-11-29.md b/demo-vault-v2/event-dinner-2024-11-29.md deleted file mode 100644 index d2712556..00000000 --- a/demo-vault-v2/event-dinner-2024-11-29.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -aliases: ["Dinner — 2024-11-29"] -Is A: Event -Date: "2024-11-29" -Belongs to: "[[2024-11]]" -Related to: ["[[person-giulia-marchetti]]"] -Tags: ["Personal"] ---- -# Dinner — 2024-11-29 -Evening dinner with Giulia Marchetti. - -## Notes -- Giulia picked a cozy enoteca near Corso Como with an excellent wine list -- She's been working on a documentary about migration in southern Italy — fascinating project -- Tried a Nero d'Avola from Sicily that was bold and earthy, perfect for the season -- November fog outside, warm candlelight inside — the contrast made it feel special diff --git a/demo-vault-v2/event-dinner-2024-12-06.md b/demo-vault-v2/event-dinner-2024-12-06.md deleted file mode 100644 index 505925c3..00000000 --- a/demo-vault-v2/event-dinner-2024-12-06.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -aliases: ["Dinner — 2024-12-06"] -Is A: Event -Date: "2024-12-06" -Belongs to: "[[2024-12]]" -Related to: ["[[person-andrea-colombo]]"] -Tags: ["Personal"] ---- -# Dinner — 2024-12-06 -Evening dinner with Andrea Colombo. - -## Notes -- Met Andrea at a steakhouse near Moscova — his choice, he's been craving red meat all week -- He just wrapped up a big consulting project and was visibly relieved -- We split a Barolo that was maybe too nice for a random Friday, but why not -- Talked about holiday plans — he's heading to the mountains, I'm staying in Milan for most of it diff --git a/demo-vault-v2/event-dinner-2024-12-13.md b/demo-vault-v2/event-dinner-2024-12-13.md deleted file mode 100644 index 610f3dc0..00000000 --- a/demo-vault-v2/event-dinner-2024-12-13.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -aliases: ["Dinner — 2024-12-13"] -Is A: Event -Date: "2024-12-13" -Belongs to: "[[2024-12]]" -Related to: ["[[person-giulia-marchetti]]"] -Tags: ["Personal"] ---- -# Dinner — 2024-12-13 -Evening dinner with Giulia Marchetti. - -## Notes -- Christmas market aperitivo first, then dinner at a trattoria near Piazza Gae Aulenti -- Giulia finished the rough cut of her documentary — she's both exhausted and proud -- I had pumpkin tortelli with butter and sage, she went for the classic veal milanese -- The Christmas lights in the piazza were beautiful — festive mood all around diff --git a/demo-vault-v2/event-dinner-2024-12-20.md b/demo-vault-v2/event-dinner-2024-12-20.md deleted file mode 100644 index 4b3adc68..00000000 --- a/demo-vault-v2/event-dinner-2024-12-20.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -aliases: ["Dinner — 2024-12-20"] -Is A: Event -Date: "2024-12-20" -Belongs to: "[[2024-12]]" -Related to: ["[[person-giulia-marchetti]]"] -Tags: ["Personal"] ---- -# Dinner — 2024-12-20 -Evening dinner with Giulia Marchetti. - -## Notes -- Pre-Christmas dinner at her place — she made a fantastic lasagna from scratch -- Exchanged small gifts, nothing big but thoughtful — she got me a beautiful notebook -- Talked about the year in review, what went well, what we'd do differently -- Warm, reflective evening — the kind of dinner that closes out a year properly diff --git a/demo-vault-v2/event-dinner-2024-12-27.md b/demo-vault-v2/event-dinner-2024-12-27.md deleted file mode 100644 index 7af07818..00000000 --- a/demo-vault-v2/event-dinner-2024-12-27.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -aliases: ["Dinner — 2024-12-27"] -Is A: Event -Date: "2024-12-27" -Belongs to: "[[2024-12]]" -Related to: ["[[person-francesca-marino]]"] -Tags: ["Personal"] ---- -# Dinner — 2024-12-27 -Evening dinner with Francesca Marino. - -## Notes -- Post-Christmas catch-up at a Vietnamese place in Chinatown — needed something light after days of panettone -- Francesca spent Christmas with her family in Naples and had hilarious stories about her aunts -- The pho was surprisingly good and exactly what we needed -- Relaxed holiday-week energy, no pressure, no plans after — just enjoying the quiet city diff --git a/demo-vault-v2/event-dinner-2025-01-03.md b/demo-vault-v2/event-dinner-2025-01-03.md deleted file mode 100644 index a7ad5cf4..00000000 --- a/demo-vault-v2/event-dinner-2025-01-03.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -aliases: ["Dinner — 2025-01-03"] -Is A: Event -Date: "2025-01-03" -Belongs to: "[[2025-01]]" -Related to: ["[[person-francesca-marino]]"] -Tags: ["Personal"] ---- -# Dinner — 2025-01-03 -Evening dinner with Francesca Marino. - -## Notes -- First dinner of the new year — went to a Middle Eastern place near Porta Venezia -- Francesca is setting new year resolutions around fitness and reading more, I'm skeptical but supportive -- The falafel platter was generous and the hummus was the best I've had in Milan -- Still in that liminal holiday period where nothing feels fully real — nice to ease into the year gently diff --git a/demo-vault-v2/event-dinner-2025-01-10.md b/demo-vault-v2/event-dinner-2025-01-10.md deleted file mode 100644 index 06f0432e..00000000 --- a/demo-vault-v2/event-dinner-2025-01-10.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -aliases: ["Dinner — 2025-01-10"] -Is A: Event -Date: "2025-01-10" -Belongs to: "[[2025-01]]" -Related to: ["[[person-giulia-marchetti]]"] -Tags: ["Personal"] ---- -# Dinner — 2025-01-10 -Evening dinner with Giulia Marchetti. - -## Notes -- Back to our usual spot — the enoteca near Corso Como, they remember us now -- Giulia submitted her documentary to three film festivals, fingers crossed -- I tried the truffle tagliatelle special and it was absurdly good -- January blues setting in for both of us, but the wine and the conversation helped diff --git a/demo-vault-v2/event-dinner-2025-01-17.md b/demo-vault-v2/event-dinner-2025-01-17.md deleted file mode 100644 index 783c671d..00000000 --- a/demo-vault-v2/event-dinner-2025-01-17.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -aliases: ["Dinner — 2025-01-17"] -Is A: Event -Date: "2025-01-17" -Belongs to: "[[2025-01]]" -Related to: ["[[person-lorenzo-galli]]"] -Tags: ["Personal"] ---- -# Dinner — 2025-01-17 -Evening dinner with Lorenzo Galli. - -## Notes -- Lorenzo suggested a Sardinian restaurant near Porta Romana — he's nostalgic after his summer there -- Had culurgiones (Sardinian ravioli) and a roasted suckling pig that was out of this world -- He's training for a half-marathon in March, so he was very disciplined about not ordering wine (I was not) -- Talked about our Dolomites hiking trip plans — thinking late September when the colors change diff --git a/demo-vault-v2/event-dinner-2025-01-24.md b/demo-vault-v2/event-dinner-2025-01-24.md deleted file mode 100644 index d630d8ab..00000000 --- a/demo-vault-v2/event-dinner-2025-01-24.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -aliases: ["Dinner — 2025-01-24"] -Is A: Event -Date: "2025-01-24" -Belongs to: "[[2025-01]]" -Related to: ["[[person-giulia-conti]]"] -Tags: ["Personal"] ---- -# Dinner — 2025-01-24 -Evening dinner with Giulia Conti. - -## Notes -- Giulia cooked at her place — an impressive mushroom risotto with porcini she brought from her parents' place -- She defended her PhD successfully last year and is now navigating the post-doc job market -- We opened a Franciacorta to celebrate her recent paper being accepted in a good journal -- Quiet, intimate dinner — just the two of us, good food, and honest conversation about what comes next diff --git a/demo-vault-v2/event-dinner-2025-02-14.md b/demo-vault-v2/event-dinner-2025-02-14.md deleted file mode 100644 index a9f3fc5c..00000000 --- a/demo-vault-v2/event-dinner-2025-02-14.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -aliases: ["Dinner — 2025-02-14"] -Is A: Event -Date: "2025-02-14" -Belongs to: "[[2025-02]]" -Related to: ["[[person-mattia-de-luca]]"] -Tags: ["Personal"] ---- -# Dinner — 2025-02-14 -Evening dinner with Mattia De Luca. - -## Notes -- Valentine's Day but neither of us had plans, so we declared it "anti-Valentine's" dinner -- Went to a ramen place in Isola — packed with other singles and friend groups, great atmosphere -- Mattia's startup closed their pre-seed round, he was on cloud nine -- The tonkotsu ramen was rich and warming, exactly what a cold February evening demands diff --git a/demo-vault-v2/event-dinner-2025-02-28.md b/demo-vault-v2/event-dinner-2025-02-28.md deleted file mode 100644 index 91ceaf54..00000000 --- a/demo-vault-v2/event-dinner-2025-02-28.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -aliases: ["Dinner — 2025-02-28"] -Is A: Event -Date: "2025-02-28" -Belongs to: "[[2025-02]]" -Related to: ["[[person-alessandro-ferrari]]"] -Tags: ["Personal"] ---- -# Dinner — 2025-02-28 -Evening dinner with Alessandro Ferrari. - -## Notes -- Alessandro wanted to try a new Pugliese restaurant near Cadorna — orecchiette with cime di rapa, the real deal -- He seems to be in a much better place mentally than last summer, the boundary-setting is working -- We discovered a great Primitivo from Manduria on their wine list -- End-of-February feeling — winter is dragging but spring is close, you can almost smell it diff --git a/demo-vault-v2/event-dinner-2025-03-07.md b/demo-vault-v2/event-dinner-2025-03-07.md deleted file mode 100644 index 45d9eb6b..00000000 --- a/demo-vault-v2/event-dinner-2025-03-07.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -aliases: ["Dinner — 2025-03-07"] -Is A: Event -Date: "2025-03-07" -Belongs to: "[[2025-03]]" -Related to: ["[[person-francesca-marino]]"] -Tags: ["Personal"] ---- -# Dinner — 2025-03-07 -Evening dinner with Francesca Marino. - -## Notes -- Francesca picked a Mexican place in Navigli — tacos, guacamole, and frozen margaritas -- She's actually sticking to her reading resolution — already finished four books this year -- We got into a spirited debate about whether audiobooks count as "reading" (I say yes, she says no) -- Fun, energetic evening — the margaritas definitely contributed to the volume of our debate diff --git a/demo-vault-v2/event-dinner-2025-03-14.md b/demo-vault-v2/event-dinner-2025-03-14.md deleted file mode 100644 index 5829d09e..00000000 --- a/demo-vault-v2/event-dinner-2025-03-14.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -aliases: ["Dinner — 2025-03-14"] -Is A: Event -Date: "2025-03-14" -Belongs to: "[[2025-03]]" -Related to: ["[[person-nicola-fabbri]]"] -Tags: ["Personal"] ---- -# Dinner — 2025-03-14 -Evening dinner with Nicola Fabbri. - -## Notes -- Nicola's wife was away so he had a rare free Friday — we went all out at a seafood ristorante near Porta Genova -- Started with crudo misto, then spaghetti alle vongole — the clams were perfectly briny -- He talked about coaching his daughter's soccer team and how much he enjoys it -- Nicola is one of those friends who makes you feel calm just by being around him diff --git a/demo-vault-v2/event-dinner-2025-03-28.md b/demo-vault-v2/event-dinner-2025-03-28.md deleted file mode 100644 index f18023c4..00000000 --- a/demo-vault-v2/event-dinner-2025-03-28.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -aliases: ["Dinner — 2025-03-28"] -Is A: Event -Date: "2025-03-28" -Belongs to: "[[2025-03]]" -Related to: ["[[person-mattia-de-luca]]"] -Tags: ["Personal"] ---- -# Dinner — 2025-03-28 -Evening dinner with Mattia De Luca. - -## Notes -- Mattia was in a celebratory mood — his first paying customer signed up this week -- We went to a Georgian restaurant in Porta Venezia, a total surprise find — the khachapuri was incredible -- He's hiring his first engineer and wanted advice on what to look for -- Spring is here, we walked through Indro Montanelli park afterwards and talked about the road ahead diff --git a/demo-vault-v2/event-dinner-2025-04-04.md b/demo-vault-v2/event-dinner-2025-04-04.md deleted file mode 100644 index c6900822..00000000 --- a/demo-vault-v2/event-dinner-2025-04-04.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -aliases: ["Dinner — 2025-04-04"] -Is A: Event -Date: "2025-04-04" -Belongs to: "[[2025-04]]" -Related to: ["[[person-alessandro-ferrari]]"] -Tags: ["Personal"] ---- -# Dinner — 2025-04-04 -Evening dinner with Alessandro Ferrari. - -## Notes -- Home dinner at my place — I attempted carbonara and it turned out pretty well, the egg was creamy not scrambled -- Alessandro brought a really nice Trebbiano and some taralli from a trip to Bari -- He's thinking about taking a sabbatical and traveling through Southeast Asia -- Mellow evening, we put on some jazz records and just talked about life — no agenda, no rush diff --git a/demo-vault-v2/event-dinner-2025-04-11.md b/demo-vault-v2/event-dinner-2025-04-11.md deleted file mode 100644 index c1dd4b7d..00000000 --- a/demo-vault-v2/event-dinner-2025-04-11.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -aliases: ["Dinner — 2025-04-11"] -Is A: Event -Date: "2025-04-11" -Belongs to: "[[2025-04]]" -Related to: ["[[person-mattia-de-luca]]"] -Tags: ["Personal"] ---- -# Dinner — 2025-04-11 -Evening dinner with Mattia De Luca. - -## Notes -- Quick dinner at a dumpling place near Loreto — Mattia was running late from a client meeting -- He hired his first engineer, a backend developer from Turin — seems like a good fit -- We shared steamed and fried dumplings, the chili oil was dangerously addictive -- Short but sweet — sometimes a 90-minute dinner is all you need to reset diff --git a/demo-vault-v2/event-dinner-2025-04-25.md b/demo-vault-v2/event-dinner-2025-04-25.md deleted file mode 100644 index 173c6193..00000000 --- a/demo-vault-v2/event-dinner-2025-04-25.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -aliases: ["Dinner — 2025-04-25"] -Is A: Event -Date: "2025-04-25" -Belongs to: "[[2025-04]]" -Related to: ["[[person-francesca-marino]]"] -Tags: ["Personal"] ---- -# Dinner — 2025-04-25 -Evening dinner with Francesca Marino. - -## Notes -- Festa della Liberazione — the city was buzzing, we started with an aperitivo at a bar in Arco della Pace -- Francesca is planning a trip to Japan in autumn and was full of research and excitement -- We ended up at a Sicilian restaurant where the arancini were perfectly crispy -- Warm spring holiday, everyone was out — the kind of evening that reminds you why you live in Milan diff --git a/demo-vault-v2/event-dinner-2025-05-02.md b/demo-vault-v2/event-dinner-2025-05-02.md deleted file mode 100644 index 80cac33e..00000000 --- a/demo-vault-v2/event-dinner-2025-05-02.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -aliases: ["Dinner — 2025-05-02"] -Is A: Event -Date: "2025-05-02" -Belongs to: "[[2025-05]]" -Related to: ["[[person-federico-moretti]]"] -Tags: ["Personal"] ---- -# Dinner — 2025-05-02 -Evening dinner with Federico Moretti. - -## Notes -- Federico finally bought his apartment — we celebrated at a wine bar near his new place in Bovisa -- He's stressed about renovation costs but excited about having his own space -- The wine bar had an incredible selection of natural wines, we tried a funky orange wine from Friuli -- Spring evening on a Friday before a long weekend — the whole city felt light and optimistic diff --git a/demo-vault-v2/event-dinner-2025-05-16.md b/demo-vault-v2/event-dinner-2025-05-16.md deleted file mode 100644 index aa4ebdf3..00000000 --- a/demo-vault-v2/event-dinner-2025-05-16.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -aliases: ["Dinner — 2025-05-16"] -Is A: Event -Date: "2025-05-16" -Belongs to: "[[2025-05]]" -Related to: ["[[person-silvia-mancini]]"] -Tags: ["Personal"] ---- -# Dinner — 2025-05-16 -Evening dinner with Silvia Mancini. - -## Notes -- Silvia suggested a new farm-to-table restaurant in Porta Romana — everything seasonal and local -- She landed a big UX contract with a fintech company and was in great form -- The asparagus risotto was phenomenal, made with local asparagus from the Po Valley -- We sat in their garden, surrounded by fairy lights — one of those perfect May evenings diff --git a/demo-vault-v2/event-dinner-2025-05-23.md b/demo-vault-v2/event-dinner-2025-05-23.md deleted file mode 100644 index bf7f0b07..00000000 --- a/demo-vault-v2/event-dinner-2025-05-23.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -aliases: ["Dinner — 2025-05-23"] -Is A: Event -Date: "2025-05-23" -Belongs to: "[[2025-05]]" -Related to: ["[[person-anna-fontana]]"] -Tags: ["Personal"] ---- -# Dinner — 2025-05-23 -Evening dinner with Anna Fontana. - -## Notes -- Anna chose a Greek restaurant near Porta Ticinese — she's been dreaming about a Greece trip -- She's growing into her management role and talked about the challenges of giving feedback -- The lamb souvlaki was perfectly seasoned and the tzatziki was fresh and garlicky -- Walked along the Naviglio Grande after dinner, the sunset reflecting on the water was gorgeous diff --git a/demo-vault-v2/event-dinner-2025-06-06.md b/demo-vault-v2/event-dinner-2025-06-06.md deleted file mode 100644 index 384d1c26..00000000 --- a/demo-vault-v2/event-dinner-2025-06-06.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -aliases: ["Dinner — 2025-06-06"] -Is A: Event -Date: "2025-06-06" -Belongs to: "[[2025-06]]" -Related to: ["[[person-nicola-fabbri]]"] -Tags: ["Personal"] ---- -# Dinner — 2025-06-06 -Evening dinner with Nicola Fabbri. - -## Notes -- Nicola and I went to a pizzeria in Sempione that does proper Neapolitan-style pizza -- His daughter's team won their first tournament — he was prouder than I've ever seen him -- I had a diavola with spicy nduja, he went classic margherita — we agreed both were excellent -- Summer evenings in the park afterwards, kids playing, couples walking — Milan at its best diff --git a/demo-vault-v2/event-dinner-2025-06-13.md b/demo-vault-v2/event-dinner-2025-06-13.md deleted file mode 100644 index 3eb98d27..00000000 --- a/demo-vault-v2/event-dinner-2025-06-13.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -aliases: ["Dinner — 2025-06-13"] -Is A: Event -Date: "2025-06-13" -Belongs to: "[[2025-06]]" -Related to: ["[[person-anna-fontana]]"] -Tags: ["Personal"] ---- -# Dinner — 2025-06-13 -Evening dinner with Anna Fontana. - -## Notes -- Anna hosted dinner on her rooftop terrace — she grilled vegetables and made bruschette -- She booked the Greece trip for August and was radiating excitement about it -- We opened a cold Falanghina that was crisp and perfect for the warm evening -- Sat out until late watching the city lights and talking about summer plans — no rush to be anywhere diff --git a/demo-vault-v2/event-family-call-2024-01-14.md b/demo-vault-v2/event-family-call-2024-01-14.md deleted file mode 100644 index 93d20e75..00000000 --- a/demo-vault-v2/event-family-call-2024-01-14.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -aliases: ["Family call — 2024-01-14"] -Is A: Event -Date: "2024-01-14" -Belongs to: "[[2024-01]]" -Related to: ["[[person-elena-rossi]]", "[[person-roberto-rossi]]"] -Tags: ["Personal", "Family"] ---- -# Family call — 2024-01-14 -Sunday family call with Elena and parents. - -## Notes -- First call of the new year — everyone shared their holiday highlights -- Mamma asked about work, as always; papà wanted to know if I'm eating well -- Elena is settling into her new apartment in Bologna, she seems happy there -- Quick call, about 40 minutes — everyone was still in holiday mode diff --git a/demo-vault-v2/event-family-call-2024-01-28.md b/demo-vault-v2/event-family-call-2024-01-28.md deleted file mode 100644 index 071af14c..00000000 --- a/demo-vault-v2/event-family-call-2024-01-28.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Family call — 2024-01-28"] -Is A: Event -Date: "2024-01-28" -Belongs to: "[[2024-01]]" -Related to: ["[[person-elena-rossi]]", "[[person-roberto-rossi]]"] -Tags: ["Personal", "Family"] ---- -# Family call — 2024-01-28 -Sunday family call with Elena and parents. - -## Notes -- Papà mentioned his knee has been bothering him again — mamma wants him to see the specialist -- Elena started a new project at work she's excited about, something in sustainable architecture -- We talked about planning a family weekend in February, maybe going to the lake diff --git a/demo-vault-v2/event-family-call-2024-02-11.md b/demo-vault-v2/event-family-call-2024-02-11.md deleted file mode 100644 index 3f7c179e..00000000 --- a/demo-vault-v2/event-family-call-2024-02-11.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Family call — 2024-02-11"] -Is A: Event -Date: "2024-02-11" -Belongs to: "[[2024-02]]" -Related to: ["[[person-elena-rossi]]", "[[person-roberto-rossi]]"] -Tags: ["Personal", "Family"] ---- -# Family call — 2024-02-11 -Sunday family call with Elena and parents. - -## Notes -- Papà went to the doctor — it's just normal wear and tear, nothing serious, everyone relieved -- Mamma is organizing carnevale preparations, making chiacchiere for the whole neighborhood -- Elena couldn't stay long, she had a deadline — short but sweet check-in from her end diff --git a/demo-vault-v2/event-family-call-2024-02-25.md b/demo-vault-v2/event-family-call-2024-02-25.md deleted file mode 100644 index a00adcbe..00000000 --- a/demo-vault-v2/event-family-call-2024-02-25.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -aliases: ["Family call — 2024-02-25"] -Is A: Event -Date: "2024-02-25" -Belongs to: "[[2024-02]]" -Related to: ["[[person-elena-rossi]]", "[[person-roberto-rossi]]"] -Tags: ["Personal", "Family"] ---- -# Family call — 2024-02-25 -Sunday family call with Elena and parents. - -## Notes -- Talked about Easter plans — mamma wants everyone home, no excuses -- Papà is feeling better, back to his morning walks -- Elena showed us photos of her apartment renovation — the kitchen looks great -- Warm, routine call — the kind that makes you feel grounded even from a distance diff --git a/demo-vault-v2/event-family-call-2024-03-10.md b/demo-vault-v2/event-family-call-2024-03-10.md deleted file mode 100644 index bc7449d2..00000000 --- a/demo-vault-v2/event-family-call-2024-03-10.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Family call — 2024-03-10"] -Is A: Event -Date: "2024-03-10" -Belongs to: "[[2024-03]]" -Related to: ["[[person-elena-rossi]]", "[[person-roberto-rossi]]"] -Tags: ["Personal", "Family"] ---- -# Family call — 2024-03-10 -Sunday family call with Elena and parents. - -## Notes -- Daylight savings — everyone confused about the time, papà called an hour early -- Mamma has started a small vegetable garden on the balcony, very enthusiastic about it -- Discussed train schedules for Easter — Elena and I will coordinate our trips home diff --git a/demo-vault-v2/event-family-call-2024-03-24.md b/demo-vault-v2/event-family-call-2024-03-24.md deleted file mode 100644 index e92d7da4..00000000 --- a/demo-vault-v2/event-family-call-2024-03-24.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -aliases: ["Family call — 2024-03-24"] -Is A: Event -Date: "2024-03-24" -Belongs to: "[[2024-03]]" -Related to: ["[[person-elena-rossi]]", "[[person-roberto-rossi]]"] -Tags: ["Personal", "Family"] ---- -# Family call — 2024-03-24 -Sunday family call with Elena and parents. - -## Notes -- Palm Sunday — mamma went to mass and brought home the olive branch, very traditional -- Final Easter logistics: I'll arrive Thursday evening, Elena on Friday morning -- Papà asked me to bring some specialty coffee from Milan, his usual request -- Everyone in good spirits, looking forward to the long weekend together diff --git a/demo-vault-v2/event-family-call-2024-04-07.md b/demo-vault-v2/event-family-call-2024-04-07.md deleted file mode 100644 index 28ac41ab..00000000 --- a/demo-vault-v2/event-family-call-2024-04-07.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -aliases: ["Family call — 2024-04-07"] -Is A: Event -Date: "2024-04-07" -Belongs to: "[[2024-04]]" -Related to: ["[[person-elena-rossi]]", "[[person-roberto-rossi]]"] -Tags: ["Personal", "Family"] ---- -# Family call — 2024-04-07 -Sunday family call with Elena and parents. - -## Notes -- Post-Easter debrief — everyone agreed it was one of the best Easters in years -- Mamma's lamb was incredible as always, papà overdid it with the colomba cake -- Elena and I agreed we should visit more often, not just holidays -- Longer call than usual, almost an hour — still riding the warmth of the weekend together diff --git a/demo-vault-v2/event-family-call-2024-04-21.md b/demo-vault-v2/event-family-call-2024-04-21.md deleted file mode 100644 index 69512c40..00000000 --- a/demo-vault-v2/event-family-call-2024-04-21.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Family call — 2024-04-21"] -Is A: Event -Date: "2024-04-21" -Belongs to: "[[2024-04]]" -Related to: ["[[person-elena-rossi]]", "[[person-roberto-rossi]]"] -Tags: ["Personal", "Family"] ---- -# Family call — 2024-04-21 -Sunday family call with Elena and parents. - -## Notes -- Routine check-in, everyone healthy and busy -- Mamma's balcony garden is sprouting — she gave us a tour via video call, very cute -- Papà is planning a short trip with his old university friends, mamma is encouraging it diff --git a/demo-vault-v2/event-family-call-2024-05-05.md b/demo-vault-v2/event-family-call-2024-05-05.md deleted file mode 100644 index 06dd9328..00000000 --- a/demo-vault-v2/event-family-call-2024-05-05.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -aliases: ["Family call — 2024-05-05"] -Is A: Event -Date: "2024-05-05" -Belongs to: "[[2024-05]]" -Related to: ["[[person-elena-rossi]]", "[[person-roberto-rossi]]"] -Tags: ["Personal", "Family"] ---- -# Family call — 2024-05-05 -Sunday family call with Elena and parents. - -## Notes -- Talked about Mother's Day plans for next week — Elena and I are coordinating a gift -- Mamma pretended she doesn't want anything, but we know she loves surprises -- Papà went on his trip with friends to Cinque Terre, came back sunburnt and happy -- Elena's architecture project got shortlisted for an award — proud family moment diff --git a/demo-vault-v2/event-family-call-2024-05-19.md b/demo-vault-v2/event-family-call-2024-05-19.md deleted file mode 100644 index 05c7b452..00000000 --- a/demo-vault-v2/event-family-call-2024-05-19.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Family call — 2024-05-19"] -Is A: Event -Date: "2024-05-19" -Belongs to: "[[2024-05]]" -Related to: ["[[person-elena-rossi]]", "[[person-roberto-rossi]]"] -Tags: ["Personal", "Family"] ---- -# Family call — 2024-05-19 -Sunday family call with Elena and parents. - -## Notes -- Mamma loved her Mother's Day gift — a nice silk scarf Elena picked out, I chipped in -- She got emotional on the call, which made all of us emotional too -- Papà is reading a new history book about the Roman Empire and wouldn't stop talking about it diff --git a/demo-vault-v2/event-family-call-2024-06-02.md b/demo-vault-v2/event-family-call-2024-06-02.md deleted file mode 100644 index 92bdf96b..00000000 --- a/demo-vault-v2/event-family-call-2024-06-02.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -aliases: ["Family call — 2024-06-02"] -Is A: Event -Date: "2024-06-02" -Belongs to: "[[2024-06]]" -Related to: ["[[person-elena-rossi]]", "[[person-roberto-rossi]]"] -Tags: ["Personal", "Family"] ---- -# Family call — 2024-06-02 -Sunday family call with Elena and parents. - -## Notes -- Summer planning is in full swing — papà wants to rent the same house in Puglia again -- Elena might not be able to come for the full two weeks because of work -- Mamma is harvesting tomatoes from her balcony garden, sent us photos -- Light, cheerful call — the prospect of summer makes everyone happier diff --git a/demo-vault-v2/event-family-call-2024-06-16.md b/demo-vault-v2/event-family-call-2024-06-16.md deleted file mode 100644 index e68e5fa4..00000000 --- a/demo-vault-v2/event-family-call-2024-06-16.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -aliases: ["Family call — 2024-06-16"] -Is A: Event -Date: "2024-06-16" -Belongs to: "[[2024-06]]" -Related to: ["[[person-elena-rossi]]", "[[person-roberto-rossi]]"] -Tags: ["Personal", "Family"] ---- -# Family call — 2024-06-16 -Sunday family call with Elena and parents. - -## Notes -- Father's Day — papà was touched by the book on WWII aviation Elena found for him -- He's in good health, walking every morning, eating well (mamma supervises) -- Booked the Puglia house for the first two weeks of August -- Quick call, papà wanted to get back to his new book already diff --git a/demo-vault-v2/event-family-call-2024-06-30.md b/demo-vault-v2/event-family-call-2024-06-30.md deleted file mode 100644 index 948d6847..00000000 --- a/demo-vault-v2/event-family-call-2024-06-30.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -aliases: ["Family call — 2024-06-30"] -Is A: Event -Date: "2024-06-30" -Belongs to: "[[2024-06]]" -Related to: ["[[person-elena-rossi]]", "[[person-roberto-rossi]]"] -Tags: ["Personal", "Family"] ---- -# Family call — 2024-06-30 -Sunday family call with Elena and parents. - -## Notes -- End of June already — mamma can't believe how fast the year is going -- Elena confirmed she can come to Puglia for the second week at least -- Talked about nonna Lucia — mamma visited her during the week, she's doing well -- Routine call, everyone in good spirits, summer anticipation building diff --git a/demo-vault-v2/event-family-call-2024-07-14.md b/demo-vault-v2/event-family-call-2024-07-14.md deleted file mode 100644 index 72f03ffa..00000000 --- a/demo-vault-v2/event-family-call-2024-07-14.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -aliases: ["Family call — 2024-07-14"] -Is A: Event -Date: "2024-07-14" -Belongs to: "[[2024-07]]" -Related to: ["[[person-elena-rossi]]", "[[person-roberto-rossi]]"] -Tags: ["Personal", "Family"] ---- -# Family call — 2024-07-14 -Sunday family call with Elena and parents. - -## Notes -- Packing lists and logistics for Puglia — mamma has a spreadsheet, of course -- Papà is excited about the seafood restaurants he found online near the rental -- Elena is bringing a friend for a few days, a colleague from work -- Hot July, everyone counting down to the beach diff --git a/demo-vault-v2/event-family-call-2024-07-28.md b/demo-vault-v2/event-family-call-2024-07-28.md deleted file mode 100644 index dceeba7b..00000000 --- a/demo-vault-v2/event-family-call-2024-07-28.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -aliases: ["Family call — 2024-07-28"] -Is A: Event -Date: "2024-07-28" -Belongs to: "[[2024-07]]" -Related to: ["[[person-elena-rossi]]", "[[person-roberto-rossi]]"] -Tags: ["Personal", "Family"] ---- -# Family call — 2024-07-28 -Sunday family call with Elena and parents. - -## Notes -- Last call before Puglia — final details about who's driving what -- Mamma already prepared some provisions to bring: olive oil, coffee, her special biscotti -- Papà tested the car AC, says it's working fine (mamma is skeptical) -- Short, practical call — we'll all be together in a few days diff --git a/demo-vault-v2/event-family-call-2024-08-11.md b/demo-vault-v2/event-family-call-2024-08-11.md deleted file mode 100644 index 661ebfc4..00000000 --- a/demo-vault-v2/event-family-call-2024-08-11.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -aliases: ["Family call — 2024-08-11"] -Is A: Event -Date: "2024-08-11" -Belongs to: "[[2024-08]]" -Related to: ["[[person-elena-rossi]]", "[[person-roberto-rossi]]"] -Tags: ["Personal", "Family"] ---- -# Family call — 2024-08-11 -Sunday family call with Elena and parents. - -## Notes -- Calling from Puglia — technically we're all in the same house, but papà insisted on the "Sunday call tradition" -- So we sat around the table with coffee and did it face-to-face, which was lovely -- Talked about the week ahead: boat trip, fish market, Elena's friend arriving Tuesday -- Ferragosto preparations already on mamma's mind diff --git a/demo-vault-v2/event-family-call-2024-08-25.md b/demo-vault-v2/event-family-call-2024-08-25.md deleted file mode 100644 index 1a09bb75..00000000 --- a/demo-vault-v2/event-family-call-2024-08-25.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -aliases: ["Family call — 2024-08-25"] -Is A: Event -Date: "2024-08-25" -Belongs to: "[[2024-08]]" -Related to: ["[[person-elena-rossi]]", "[[person-roberto-rossi]]"] -Tags: ["Personal", "Family"] ---- -# Family call — 2024-08-25 -Sunday family call with Elena and parents. - -## Notes -- Back from Puglia — everyone sunburnt, rested, and a little sad it's over -- Mamma already misses the sea, keeps looking at photos from the trip -- Papà gained a few kilos from all the seafood and gelato but has no regrets -- We agreed it was one of the best family holidays — already talking about next year diff --git a/demo-vault-v2/event-family-call-2024-09-08.md b/demo-vault-v2/event-family-call-2024-09-08.md deleted file mode 100644 index a876aeb6..00000000 --- a/demo-vault-v2/event-family-call-2024-09-08.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Family call — 2024-09-08"] -Is A: Event -Date: "2024-09-08" -Belongs to: "[[2024-09]]" -Related to: ["[[person-elena-rossi]]", "[[person-roberto-rossi]]"] -Tags: ["Personal", "Family"] ---- -# Family call — 2024-09-08 -Sunday family call with Elena and parents. - -## Notes -- Back to routine — Elena started a new semester of evening classes alongside work -- Papà is back to his morning walks, trying to lose the holiday weight -- Mamma is already planning the mushroom-picking trip to the hills in October diff --git a/demo-vault-v2/event-family-call-2024-09-22.md b/demo-vault-v2/event-family-call-2024-09-22.md deleted file mode 100644 index fcb745df..00000000 --- a/demo-vault-v2/event-family-call-2024-09-22.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -aliases: ["Family call — 2024-09-22"] -Is A: Event -Date: "2024-09-22" -Belongs to: "[[2024-09]]" -Related to: ["[[person-elena-rossi]]", "[[person-roberto-rossi]]"] -Tags: ["Personal", "Family"] ---- -# Family call — 2024-09-22 -Sunday family call with Elena and parents. - -## Notes -- First day of autumn — papà noted the leaves changing on his morning walk -- Elena is stressed with work and classes but says she can handle it -- Mamma made the first batch of minestrone of the season, says it's the best yet -- Talked about visiting nonna Lucia together in November for her birthday diff --git a/demo-vault-v2/event-family-call-2024-10-06.md b/demo-vault-v2/event-family-call-2024-10-06.md deleted file mode 100644 index 4c9c1ddd..00000000 --- a/demo-vault-v2/event-family-call-2024-10-06.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -aliases: ["Family call — 2024-10-06"] -Is A: Event -Date: "2024-10-06" -Belongs to: "[[2024-10]]" -Related to: ["[[person-elena-rossi]]", "[[person-roberto-rossi]]"] -Tags: ["Personal", "Family"] ---- -# Family call — 2024-10-06 -Sunday family call with Elena and parents. - -## Notes -- Mamma and papà went mushroom picking in the hills — brought home porcini and chiodini -- She's already planning what to cook with them: risotto, trifolati, dried for winter -- Elena's architecture project didn't win the award but she's philosophical about it -- Cozy October call, everyone settling into autumn routines diff --git a/demo-vault-v2/event-family-call-2024-10-20.md b/demo-vault-v2/event-family-call-2024-10-20.md deleted file mode 100644 index ad2aea7f..00000000 --- a/demo-vault-v2/event-family-call-2024-10-20.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -aliases: ["Family call — 2024-10-20"] -Is A: Event -Date: "2024-10-20" -Belongs to: "[[2024-10]]" -Related to: ["[[person-elena-rossi]]", "[[person-roberto-rossi]]"] -Tags: ["Personal", "Family"] ---- -# Family call — 2024-10-20 -Sunday family call with Elena and parents. - -## Notes -- Nonna Lucia's birthday is coming up in November — coordinating plans for a family visit to Lecco -- Mamma is knitting a scarf for nonna, a new pattern she found online -- Papà's morning walks have paid off — he says his knee feels the best it has in months -- Elena is considering getting a dog, which led to a lively family debate diff --git a/demo-vault-v2/event-family-call-2024-11-03.md b/demo-vault-v2/event-family-call-2024-11-03.md deleted file mode 100644 index 3b8c4fdc..00000000 --- a/demo-vault-v2/event-family-call-2024-11-03.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -aliases: ["Family call — 2024-11-03"] -Is A: Event -Date: "2024-11-03" -Belongs to: "[[2024-11]]" -Related to: ["[[person-elena-rossi]]", "[[person-roberto-rossi]]"] -Tags: ["Personal", "Family"] ---- -# Family call — 2024-11-03 -Sunday family call with Elena and parents. - -## Notes -- Finalized nonna's birthday visit — we'll all go to Lecco on the 24th -- Mamma wants to bake a torta della nonna (the irony is not lost on anyone) -- Papà is doing a furniture restoration project in the garage, very absorbed by it -- Elena decided against the dog for now — her schedule is too unpredictable diff --git a/demo-vault-v2/event-family-call-2024-11-17.md b/demo-vault-v2/event-family-call-2024-11-17.md deleted file mode 100644 index 51327f95..00000000 --- a/demo-vault-v2/event-family-call-2024-11-17.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -aliases: ["Family call — 2024-11-17"] -Is A: Event -Date: "2024-11-17" -Belongs to: "[[2024-11]]" -Related to: ["[[person-elena-rossi]]", "[[person-roberto-rossi]]"] -Tags: ["Personal", "Family"] ---- -# Family call — 2024-11-17 -Sunday family call with Elena and parents. - -## Notes -- Next week is nonna's birthday visit — everyone confirmed, mamma has the logistics down -- Papà finished his furniture project: a restored wooden bookshelf, it looks beautiful -- Talked about Christmas plans — the usual debate about whether to do Christmas Eve or Christmas Day lunch -- Grey November but the family warmth on these calls makes it brighter diff --git a/demo-vault-v2/event-family-call-2024-12-01.md b/demo-vault-v2/event-family-call-2024-12-01.md deleted file mode 100644 index b3179c79..00000000 --- a/demo-vault-v2/event-family-call-2024-12-01.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -aliases: ["Family call — 2024-12-01"] -Is A: Event -Date: "2024-12-01" -Belongs to: "[[2024-12]]" -Related to: ["[[person-elena-rossi]]", "[[person-roberto-rossi]]"] -Tags: ["Personal", "Family"] ---- -# Family call — 2024-12-01 -Sunday family call with Elena and parents. - -## Notes -- First Sunday of Advent — mamma set up the little nativity scene at home -- Recapped nonna's birthday celebration, everyone still glowing from it -- Christmas gift brainstorming — papà claims he doesn't want anything, we know better -- Elena is wrapping up her evening classes, final exam in two weeks diff --git a/demo-vault-v2/event-family-call-2024-12-15.md b/demo-vault-v2/event-family-call-2024-12-15.md deleted file mode 100644 index 0494d318..00000000 --- a/demo-vault-v2/event-family-call-2024-12-15.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -aliases: ["Family call — 2024-12-15"] -Is A: Event -Date: "2024-12-15" -Belongs to: "[[2024-12]]" -Related to: ["[[person-elena-rossi]]", "[[person-roberto-rossi]]"] -Tags: ["Personal", "Family"] ---- -# Family call — 2024-12-15 -Sunday family call with Elena and parents. - -## Notes -- Christmas plans finalized: I arrive the 23rd, Elena the 22nd -- Mamma is already cooking and freezing things — her holiday prep is legendary -- Papà bought a new panettone from a bakery in Como that he swears is the best -- Elena passed her exam with top marks — the family WhatsApp group exploded with celebration diff --git a/demo-vault-v2/event-family-call-2024-12-29.md b/demo-vault-v2/event-family-call-2024-12-29.md deleted file mode 100644 index f56a6ad6..00000000 --- a/demo-vault-v2/event-family-call-2024-12-29.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -aliases: ["Family call — 2024-12-29"] -Is A: Event -Date: "2024-12-29" -Belongs to: "[[2024-12]]" -Related to: ["[[person-elena-rossi]]", "[[person-roberto-rossi]]"] -Tags: ["Personal", "Family"] ---- -# Family call — 2024-12-29 -Sunday family call with Elena and parents. - -## Notes -- Post-Christmas call — still digesting mamma's seven-course Christmas Eve dinner -- Everyone loved their gifts; papà was especially happy with a new pair of walking shoes -- Talked about New Year's Eve plans — mamma and papà staying home, Elena going to a friend's party -- Year-end reflection: a good year for the family, grateful to be healthy and together diff --git a/demo-vault-v2/event-family-call-2025-01-12.md b/demo-vault-v2/event-family-call-2025-01-12.md deleted file mode 100644 index be6d334e..00000000 --- a/demo-vault-v2/event-family-call-2025-01-12.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -aliases: ["Family call — 2025-01-12"] -Is A: Event -Date: "2025-01-12" -Belongs to: "[[2025-01]]" -Related to: ["[[person-elena-rossi]]", "[[person-roberto-rossi]]"] -Tags: ["Personal", "Family"] ---- -# Family call — 2025-01-12 -Sunday family call with Elena and parents. - -## Notes -- First proper call of 2025 — everyone sharing new year's resolutions -- Mamma wants to take a watercolor painting class, papà wants to read more -- Elena is applying for a more senior position at her firm -- Cold January, papà complained about the heating bill — some things never change diff --git a/demo-vault-v2/event-family-call-2025-01-26.md b/demo-vault-v2/event-family-call-2025-01-26.md deleted file mode 100644 index 03be3948..00000000 --- a/demo-vault-v2/event-family-call-2025-01-26.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -aliases: ["Family call — 2025-01-26"] -Is A: Event -Date: "2025-01-26" -Belongs to: "[[2025-01]]" -Related to: ["[[person-elena-rossi]]", "[[person-roberto-rossi]]"] -Tags: ["Personal", "Family"] ---- -# Family call — 2025-01-26 -Sunday family call with Elena and parents. - -## Notes -- Mamma enrolled in the watercolor class — she's already bought all the supplies -- Papà has a slight cold but insists it's nothing, mamma is monitoring him anyway -- Elena had her interview for the senior role, she thinks it went well -- Talked about visiting nonna in February — I'll try to combine it with my monthly trip diff --git a/demo-vault-v2/event-family-call-2025-02-09.md b/demo-vault-v2/event-family-call-2025-02-09.md deleted file mode 100644 index 55173af4..00000000 --- a/demo-vault-v2/event-family-call-2025-02-09.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -aliases: ["Family call — 2025-02-09"] -Is A: Event -Date: "2025-02-09" -Belongs to: "[[2025-02]]" -Related to: ["[[person-elena-rossi]]", "[[person-roberto-rossi]]"] -Tags: ["Personal", "Family"] ---- -# Family call — 2025-02-09 -Sunday family call with Elena and parents. - -## Notes -- Elena got the promotion — she's now a senior architect at her firm, everyone thrilled -- Mamma showed us her first watercolor attempt — a landscape of Lake Como, surprisingly good -- Papà recovered from his cold and is back to morning walks -- Talked about carnival traditions — mamma is making frittelle di carnevale this week diff --git a/demo-vault-v2/event-family-call-2025-02-23.md b/demo-vault-v2/event-family-call-2025-02-23.md deleted file mode 100644 index 2b8ab108..00000000 --- a/demo-vault-v2/event-family-call-2025-02-23.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -aliases: ["Family call — 2025-02-23"] -Is A: Event -Date: "2025-02-23" -Belongs to: "[[2025-02]]" -Related to: ["[[person-elena-rossi]]", "[[person-roberto-rossi]]"] -Tags: ["Personal", "Family"] ---- -# Family call — 2025-02-23 -Sunday family call with Elena and parents. - -## Notes -- Routine check-in, everyone healthy and busy with their things -- Mamma's watercolor class is going well, she's made friends there too -- Papà discovered a new walking route through a nature reserve nearby -- Elena is adjusting to her new responsibilities, managing two junior architects now diff --git a/demo-vault-v2/event-family-call-2025-03-09.md b/demo-vault-v2/event-family-call-2025-03-09.md deleted file mode 100644 index 21fd335b..00000000 --- a/demo-vault-v2/event-family-call-2025-03-09.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -aliases: ["Family call — 2025-03-09"] -Is A: Event -Date: "2025-03-09" -Belongs to: "[[2025-03]]" -Related to: ["[[person-elena-rossi]]", "[[person-roberto-rossi]]"] -Tags: ["Personal", "Family"] ---- -# Family call — 2025-03-09 -Sunday family call with Elena and parents. - -## Notes -- Spring is around the corner — mamma is already planning her balcony garden for this year -- She wants to try growing zucchini this time, papà is skeptical about the space -- Elena might come to Milan for a weekend in April, we're trying to coordinate -- Lighthearted call, lots of jokes about papà's garden skepticism diff --git a/demo-vault-v2/event-family-call-2025-03-23.md b/demo-vault-v2/event-family-call-2025-03-23.md deleted file mode 100644 index 3c23fb0f..00000000 --- a/demo-vault-v2/event-family-call-2025-03-23.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -aliases: ["Family call — 2025-03-23"] -Is A: Event -Date: "2025-03-23" -Belongs to: "[[2025-03]]" -Related to: ["[[person-elena-rossi]]", "[[person-roberto-rossi]]"] -Tags: ["Personal", "Family"] ---- -# Family call — 2025-03-23 -Sunday family call with Elena and parents. - -## Notes -- Easter planning — same drill as last year, everyone coming home -- Mamma is debating between lamb and a vegetarian main this year (she'll do both, we all know it) -- Papà's nature reserve walks have turned into a birdwatching hobby, he bought binoculars -- Elena confirmed her Milan trip for mid-April — she'll stay with me diff --git a/demo-vault-v2/event-family-call-2025-04-06.md b/demo-vault-v2/event-family-call-2025-04-06.md deleted file mode 100644 index b7cfc944..00000000 --- a/demo-vault-v2/event-family-call-2025-04-06.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -aliases: ["Family call — 2025-04-06"] -Is A: Event -Date: "2025-04-06" -Belongs to: "[[2025-04]]" -Related to: ["[[person-elena-rossi]]", "[[person-roberto-rossi]]"] -Tags: ["Personal", "Family"] ---- -# Family call — 2025-04-06 -Sunday family call with Elena and parents. - -## Notes -- Pre-Easter final logistics — I'm arriving Wednesday evening by train -- Mamma has been cooking for days already, the freezer is full -- Papà spotted a rare woodpecker on his walk and won't stop telling everyone about it -- Elena is driving up from Bologna on Thursday with a friend joining for lunch on Sunday diff --git a/demo-vault-v2/event-family-call-2025-04-20.md b/demo-vault-v2/event-family-call-2025-04-20.md deleted file mode 100644 index 3b7a95b0..00000000 --- a/demo-vault-v2/event-family-call-2025-04-20.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -aliases: ["Family call — 2025-04-20"] -Is A: Event -Date: "2025-04-20" -Belongs to: "[[2025-04]]" -Related to: ["[[person-elena-rossi]]", "[[person-roberto-rossi]]"] -Tags: ["Personal", "Family"] ---- -# Family call — 2025-04-20 -Sunday family call with Elena and parents. - -## Notes -- Post-Easter glow — mamma outdid herself this year, the lamb was perfection -- Papà ate too much colomba again but claims it was "only two slices" (it was more) -- Elena's friend loved the family, mamma is already asking if they're dating -- We talked about summer plans — maybe Croatia this year instead of Puglia diff --git a/demo-vault-v2/event-family-call-2025-05-04.md b/demo-vault-v2/event-family-call-2025-05-04.md deleted file mode 100644 index a9383675..00000000 --- a/demo-vault-v2/event-family-call-2025-05-04.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -aliases: ["Family call — 2025-05-04"] -Is A: Event -Date: "2025-05-04" -Belongs to: "[[2025-05]]" -Related to: ["[[person-elena-rossi]]", "[[person-roberto-rossi]]"] -Tags: ["Personal", "Family"] ---- -# Family call — 2025-05-04 -Sunday family call with Elena and parents. - -## Notes -- Mother's Day planning for next week — Elena and I found a nice ceramic vase from a local artisan -- Mamma's watercolor paintings are getting really good, she's thinking of framing one for the living room -- Papà is researching Croatia accommodations, he's become the family travel agent -- Warm, happy call — spring energy is infectious even through a screen diff --git a/demo-vault-v2/event-family-call-2025-05-18.md b/demo-vault-v2/event-family-call-2025-05-18.md deleted file mode 100644 index 0c902eac..00000000 --- a/demo-vault-v2/event-family-call-2025-05-18.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -aliases: ["Family call — 2025-05-18"] -Is A: Event -Date: "2025-05-18" -Belongs to: "[[2025-05]]" -Related to: ["[[person-elena-rossi]]", "[[person-roberto-rossi]]"] -Tags: ["Personal", "Family"] ---- -# Family call — 2025-05-18 -Sunday family call with Elena and parents. - -## Notes -- Mamma loved the ceramic vase, she cried a little — says she'll use it for fresh flowers from the market -- She painted a watercolor of the family house and it's genuinely beautiful -- Papà found a villa in Istria for August, waiting for everyone to confirm dates -- Elena is thriving in her new role, leading her first major project independently diff --git a/demo-vault-v2/event-family-call-2025-06-01.md b/demo-vault-v2/event-family-call-2025-06-01.md deleted file mode 100644 index 40ec0e3b..00000000 --- a/demo-vault-v2/event-family-call-2025-06-01.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -aliases: ["Family call — 2025-06-01"] -Is A: Event -Date: "2025-06-01" -Belongs to: "[[2025-06]]" -Related to: ["[[person-elena-rossi]]", "[[person-roberto-rossi]]"] -Tags: ["Personal", "Family"] ---- -# Family call — 2025-06-01 -Sunday family call with Elena and parents. - -## Notes -- Confirmed the Croatia villa — two weeks in August, everyone is in -- Papà started learning a few Croatian phrases from YouTube, very endearing -- Mamma's balcony zucchini are actually growing — papà admitted he was wrong, graciously -- Elena mentioned she might be seeing someone but wouldn't give details yet — teasing us diff --git a/demo-vault-v2/event-family-call-2025-06-15.md b/demo-vault-v2/event-family-call-2025-06-15.md deleted file mode 100644 index e90d3de4..00000000 --- a/demo-vault-v2/event-family-call-2025-06-15.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -aliases: ["Family call — 2025-06-15"] -Is A: Event -Date: "2025-06-15" -Belongs to: "[[2025-06]]" -Related to: ["[[person-elena-rossi]]", "[[person-roberto-rossi]]"] -Tags: ["Personal", "Family"] ---- -# Family call — 2025-06-15 -Sunday family call with Elena and parents. - -## Notes -- Father's Day — papà was touched by the birdwatching field guide we got him -- He showed us his "bird journal" where he sketches and logs every species he spots -- Mamma made his favorite meal: polenta with brasato -- Elena still cagey about the mystery person, but she was smiling the whole call — that says enough diff --git a/demo-vault-v2/event-gym-2024-01-03.md b/demo-vault-v2/event-gym-2024-01-03.md deleted file mode 100644 index 1bf0c0dc..00000000 --- a/demo-vault-v2/event-gym-2024-01-03.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Gym — 2024-01-03"] -Is A: Event -Date: "2024-01-03" -Belongs to: "[[2024-01]]" -Tags: ["Health"] ---- -# Gym — 2024-01-03 -Strength training. Squat, deadlift, pull-ups. 75 minutes. - -## Notes -- Back squat 5x5 at 80kg — felt solid after the holiday break -- Conventional deadlift 3x5 at 100kg, grip held up well -- Pull-ups 4x8, added 5kg vest on last two sets -- Good energy despite being the first session of the year diff --git a/demo-vault-v2/event-gym-2024-01-17.md b/demo-vault-v2/event-gym-2024-01-17.md deleted file mode 100644 index 57fbe09e..00000000 --- a/demo-vault-v2/event-gym-2024-01-17.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Gym — 2024-01-17"] -Is A: Event -Date: "2024-01-17" -Belongs to: "[[2024-01]]" -Tags: ["Health"] ---- -# Gym — 2024-01-17 -Strength training. Squat, deadlift, pull-ups. 75 minutes. - -## Notes -- Front squat 4x6 at 65kg — working on depth and core bracing -- Romanian deadlift 3x8 at 80kg, hamstrings were tight from cycling -- Weighted pull-ups 3x6 with 10kg plate -- Finished with hanging leg raises 3x12 diff --git a/demo-vault-v2/event-gym-2024-01-31.md b/demo-vault-v2/event-gym-2024-01-31.md deleted file mode 100644 index a5624817..00000000 --- a/demo-vault-v2/event-gym-2024-01-31.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Gym — 2024-01-31"] -Is A: Event -Date: "2024-01-31" -Belongs to: "[[2024-01]]" -Tags: ["Health"] ---- -# Gym — 2024-01-31 -Strength training. Squat, deadlift, pull-ups. 75 minutes. - -## Notes -- Back squat 5x5 at 85kg — squat PR: 85kg x 5 for all sets -- Deadlift 3x3 at 110kg, focused on hip hinge cue -- Pull-ups 5x5 bodyweight, super-setted with dips -- Strong session overall, sleep has been consistent this month diff --git a/demo-vault-v2/event-gym-2024-02-14.md b/demo-vault-v2/event-gym-2024-02-14.md deleted file mode 100644 index 374634d9..00000000 --- a/demo-vault-v2/event-gym-2024-02-14.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Gym — 2024-02-14"] -Is A: Event -Date: "2024-02-14" -Belongs to: "[[2024-02]]" -Tags: ["Health"] ---- -# Gym — 2024-02-14 -Strength training. Squat, deadlift, pull-ups. 75 minutes. - -## Notes -- Back squat 5x5 at 82.5kg — deload week, focusing on form -- Sumo deadlift 3x5 at 95kg, experimenting with wider stance -- Pull-ups 4x8 bodyweight, controlled negatives -- Lower back felt a bit stiff, spent extra time on mobility after diff --git a/demo-vault-v2/event-gym-2024-02-28.md b/demo-vault-v2/event-gym-2024-02-28.md deleted file mode 100644 index a2dc5d66..00000000 --- a/demo-vault-v2/event-gym-2024-02-28.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Gym — 2024-02-28"] -Is A: Event -Date: "2024-02-28" -Belongs to: "[[2024-02]]" -Tags: ["Health"] ---- -# Gym — 2024-02-28 -Strength training. Squat, deadlift, pull-ups. 75 minutes. - -## Notes -- Back squat 5x5 at 87.5kg — grinding through the last set but completed all reps -- Conventional deadlift 3x5 at 105kg, used chalk for grip -- Chin-ups 4x6 with 7.5kg added -- Finished with ab wheel rollouts 3x10, core still weak point diff --git a/demo-vault-v2/event-gym-2024-03-13.md b/demo-vault-v2/event-gym-2024-03-13.md deleted file mode 100644 index 2b28c603..00000000 --- a/demo-vault-v2/event-gym-2024-03-13.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Gym — 2024-03-13"] -Is A: Event -Date: "2024-03-13" -Belongs to: "[[2024-03]]" -Tags: ["Health"] ---- -# Gym — 2024-03-13 -Strength training. Squat, deadlift, pull-ups. 75 minutes. - -## Notes -- Back squat 5x5 at 90kg — felt heavy but moved well -- Deadlift 3x3 at 115kg, new 3-rep max -- Pull-ups 3x8 bodyweight, focused on full range of motion -- Legs were fatigued from a long ride on Sunday diff --git a/demo-vault-v2/event-gym-2024-03-27.md b/demo-vault-v2/event-gym-2024-03-27.md deleted file mode 100644 index 2e3c6348..00000000 --- a/demo-vault-v2/event-gym-2024-03-27.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Gym — 2024-03-27"] -Is A: Event -Date: "2024-03-27" -Belongs to: "[[2024-03]]" -Tags: ["Health"] ---- -# Gym — 2024-03-27 -Strength training. Squat, deadlift, pull-ups. 75 minutes. - -## Notes -- Front squat 4x5 at 70kg — ankle mobility improving -- Romanian deadlift 3x8 at 85kg, slow eccentric -- Weighted chin-ups 4x5 at 10kg -- Added farmer's walks 3x40m with 32kg kettlebells, grip endurance work diff --git a/demo-vault-v2/event-gym-2024-04-10.md b/demo-vault-v2/event-gym-2024-04-10.md deleted file mode 100644 index 2dc07a2d..00000000 --- a/demo-vault-v2/event-gym-2024-04-10.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Gym — 2024-04-10"] -Is A: Event -Date: "2024-04-10" -Belongs to: "[[2024-04]]" -Tags: ["Health"] ---- -# Gym — 2024-04-10 -Strength training. Squat, deadlift, pull-ups. 75 minutes. - -## Notes -- Back squat 5x5 at 90kg — consistent, no grinding -- Conventional deadlift 3x5 at 107.5kg, belt on for top sets -- Pull-ups 4x8, last set to failure got 10 -- Spring weather helping energy levels, good session diff --git a/demo-vault-v2/event-gym-2024-04-24.md b/demo-vault-v2/event-gym-2024-04-24.md deleted file mode 100644 index c009b9b1..00000000 --- a/demo-vault-v2/event-gym-2024-04-24.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Gym — 2024-04-24"] -Is A: Event -Date: "2024-04-24" -Belongs to: "[[2024-04]]" -Tags: ["Health"] ---- -# Gym — 2024-04-24 -Strength training. Squat, deadlift, pull-ups. 75 minutes. - -## Notes -- Back squat 3x3 at 95kg — heavy singles day, Squat PR: 100kg x 1 -- Deadlift 5x3 at 100kg, speed pulls focusing on bar velocity -- Weighted pull-ups 3x5 at 12.5kg -- Felt strong, best session in a while diff --git a/demo-vault-v2/event-gym-2024-05-08.md b/demo-vault-v2/event-gym-2024-05-08.md deleted file mode 100644 index fb8c3195..00000000 --- a/demo-vault-v2/event-gym-2024-05-08.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Gym — 2024-05-08"] -Is A: Event -Date: "2024-05-08" -Belongs to: "[[2024-05]]" -Tags: ["Health"] ---- -# Gym — 2024-05-08 -Strength training. Squat, deadlift, pull-ups. 75 minutes. - -## Notes -- Back squat 5x5 at 87.5kg — deload after the PR week -- Trap bar deadlift 3x8 at 90kg, easier on the lower back -- Pull-ups 5x5 with slow tempo (3 sec up, 3 sec down) -- Hamstrings tight from cycling, extra foam rolling after diff --git a/demo-vault-v2/event-gym-2024-05-22.md b/demo-vault-v2/event-gym-2024-05-22.md deleted file mode 100644 index 5ebb57a7..00000000 --- a/demo-vault-v2/event-gym-2024-05-22.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Gym — 2024-05-22"] -Is A: Event -Date: "2024-05-22" -Belongs to: "[[2024-05]]" -Tags: ["Health"] ---- -# Gym — 2024-05-22 -Strength training. Squat, deadlift, pull-ups. 75 minutes. - -## Notes -- Front squat 4x5 at 72.5kg — depth is getting better each week -- Conventional deadlift 3x5 at 110kg, focused on lats engagement -- Chin-ups 4x8 bodyweight, superset with hanging knee raises -- Solid mid-week session despite poor sleep the night before diff --git a/demo-vault-v2/event-gym-2024-06-05.md b/demo-vault-v2/event-gym-2024-06-05.md deleted file mode 100644 index 60d31c5d..00000000 --- a/demo-vault-v2/event-gym-2024-06-05.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Gym — 2024-06-05"] -Is A: Event -Date: "2024-06-05" -Belongs to: "[[2024-06]]" -Tags: ["Health"] ---- -# Gym — 2024-06-05 -Strength training. Squat, deadlift, pull-ups. 75 minutes. - -## Notes -- Back squat 5x5 at 92.5kg — tough but completed every rep -- Romanian deadlift 3x8 at 87.5kg, really feeling the stretch -- Pull-ups 4x6 with 10kg vest -- Summer heat in the gym, had to take longer rest periods diff --git a/demo-vault-v2/event-gym-2024-06-19.md b/demo-vault-v2/event-gym-2024-06-19.md deleted file mode 100644 index 28e2131e..00000000 --- a/demo-vault-v2/event-gym-2024-06-19.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Gym — 2024-06-19"] -Is A: Event -Date: "2024-06-19" -Belongs to: "[[2024-06]]" -Tags: ["Health"] ---- -# Gym — 2024-06-19 -Strength training. Squat, deadlift, pull-ups. 75 minutes. - -## Notes -- Back squat 5x5 at 92.5kg — moved faster than last time at this weight -- Deadlift 3x3 at 120kg, Deadlift PR: 120kg x 3 -- Weighted chin-ups 3x5 at 12.5kg -- Farmer's walks 3x40m with 36kg, grip improving steadily diff --git a/demo-vault-v2/event-gym-2024-07-03.md b/demo-vault-v2/event-gym-2024-07-03.md deleted file mode 100644 index 6c71c292..00000000 --- a/demo-vault-v2/event-gym-2024-07-03.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Gym — 2024-07-03"] -Is A: Event -Date: "2024-07-03" -Belongs to: "[[2024-07]]" -Tags: ["Health"] ---- -# Gym — 2024-07-03 -Strength training. Squat, deadlift, pull-ups. 75 minutes. - -## Notes -- Back squat 4x4 at 95kg — working towards 100kg for reps -- Sumo deadlift 3x5 at 105kg, sumo feels more natural lately -- Pull-ups 5x5 bodyweight, focusing on clean form -- Ab wheel rollouts 3x12, core strength noticeably better diff --git a/demo-vault-v2/event-gym-2024-07-17.md b/demo-vault-v2/event-gym-2024-07-17.md deleted file mode 100644 index 87f2ed96..00000000 --- a/demo-vault-v2/event-gym-2024-07-17.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Gym — 2024-07-17"] -Is A: Event -Date: "2024-07-17" -Belongs to: "[[2024-07]]" -Tags: ["Health"] ---- -# Gym — 2024-07-17 -Strength training. Squat, deadlift, pull-ups. 75 minutes. - -## Notes -- Front squat 4x5 at 75kg — paused reps, 2 sec in the hole -- Conventional deadlift 3x5 at 112.5kg, hook grip holding well -- Weighted pull-ups 4x5 at 10kg -- Legs still recovering from a hilly ride on Saturday diff --git a/demo-vault-v2/event-gym-2024-07-31.md b/demo-vault-v2/event-gym-2024-07-31.md deleted file mode 100644 index 7b9c48ba..00000000 --- a/demo-vault-v2/event-gym-2024-07-31.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Gym — 2024-07-31"] -Is A: Event -Date: "2024-07-31" -Belongs to: "[[2024-07]]" -Tags: ["Health"] ---- -# Gym — 2024-07-31 -Strength training. Squat, deadlift, pull-ups. 75 minutes. - -## Notes -- Back squat 5x5 at 95kg — Squat PR: 95kg x 5 x 5 complete -- Trap bar deadlift 3x6 at 100kg, focusing on explosive drive -- Chin-ups 4x8, last set got 11 -- Great session to close out July, consistency paying off diff --git a/demo-vault-v2/event-gym-2024-08-14.md b/demo-vault-v2/event-gym-2024-08-14.md deleted file mode 100644 index a03596e4..00000000 --- a/demo-vault-v2/event-gym-2024-08-14.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Gym — 2024-08-14"] -Is A: Event -Date: "2024-08-14" -Belongs to: "[[2024-08]]" -Tags: ["Health"] ---- -# Gym — 2024-08-14 -Strength training. Squat, deadlift, pull-ups. 75 minutes. - -## Notes -- Back squat 5x5 at 90kg — deload week, holiday mode -- Romanian deadlift 3x10 at 75kg, high rep hypertrophy block -- Pull-ups 3x10 bodyweight, easy pace -- Light session, saving energy for a long ride this weekend diff --git a/demo-vault-v2/event-gym-2024-08-28.md b/demo-vault-v2/event-gym-2024-08-28.md deleted file mode 100644 index a1251542..00000000 --- a/demo-vault-v2/event-gym-2024-08-28.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Gym — 2024-08-28"] -Is A: Event -Date: "2024-08-28" -Belongs to: "[[2024-08]]" -Tags: ["Health"] ---- -# Gym — 2024-08-28 -Strength training. Squat, deadlift, pull-ups. 75 minutes. - -## Notes -- Back squat 5x5 at 92.5kg — back to regular programming post-holiday -- Conventional deadlift 3x5 at 115kg, felt heavy after the break -- Pull-ups 4x6 with 7.5kg added -- Needed to rebuild momentum, slightly sluggish but got through it diff --git a/demo-vault-v2/event-gym-2024-09-11.md b/demo-vault-v2/event-gym-2024-09-11.md deleted file mode 100644 index ff113a07..00000000 --- a/demo-vault-v2/event-gym-2024-09-11.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Gym — 2024-09-11"] -Is A: Event -Date: "2024-09-11" -Belongs to: "[[2024-09]]" -Tags: ["Health"] ---- -# Gym — 2024-09-11 -Strength training. Squat, deadlift, pull-ups. 75 minutes. - -## Notes -- Back squat 5x5 at 95kg — consistent again, bar speed improving -- Deadlift 3x3 at 122.5kg, straps on the top set -- Weighted chin-ups 3x6 at 12.5kg -- Autumn energy kicking in, best lifting block of the year so far diff --git a/demo-vault-v2/event-gym-2024-09-25.md b/demo-vault-v2/event-gym-2024-09-25.md deleted file mode 100644 index e913832b..00000000 --- a/demo-vault-v2/event-gym-2024-09-25.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Gym — 2024-09-25"] -Is A: Event -Date: "2024-09-25" -Belongs to: "[[2024-09]]" -Tags: ["Health"] ---- -# Gym — 2024-09-25 -Strength training. Squat, deadlift, pull-ups. 75 minutes. - -## Notes -- Front squat 4x4 at 80kg — working on clean rack position -- Romanian deadlift 3x8 at 90kg, hamstrings getting stronger -- Pull-ups 5x5 with 10kg vest -- Finished with plank holds 3x60sec and Pallof press 3x12 diff --git a/demo-vault-v2/event-gym-2024-10-09.md b/demo-vault-v2/event-gym-2024-10-09.md deleted file mode 100644 index 3703d70e..00000000 --- a/demo-vault-v2/event-gym-2024-10-09.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Gym — 2024-10-09"] -Is A: Event -Date: "2024-10-09" -Belongs to: "[[2024-10]]" -Tags: ["Health"] ---- -# Gym — 2024-10-09 -Strength training. Squat, deadlift, pull-ups. 75 minutes. - -## Notes -- Back squat 3x3 at 100kg — Squat PR: 100kg x 3, finally triple digits for triples -- Conventional deadlift 3x5 at 115kg, speed work -- Weighted pull-ups 4x5 at 15kg -- Huge morale boost from hitting 100kg squat for reps diff --git a/demo-vault-v2/event-gym-2024-10-23.md b/demo-vault-v2/event-gym-2024-10-23.md deleted file mode 100644 index 4c9aaceb..00000000 --- a/demo-vault-v2/event-gym-2024-10-23.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Gym — 2024-10-23"] -Is A: Event -Date: "2024-10-23" -Belongs to: "[[2024-10]]" -Tags: ["Health"] ---- -# Gym — 2024-10-23 -Strength training. Squat, deadlift, pull-ups. 75 minutes. - -## Notes -- Back squat 5x5 at 95kg — volume day, felt smooth after the PR -- Deadlift 3x5 at 117.5kg, mixed grip on last set -- Chin-ups 4x8 bodyweight, super-setted with face pulls -- Solid maintenance session, keeping intensity steady diff --git a/demo-vault-v2/event-gym-2024-11-06.md b/demo-vault-v2/event-gym-2024-11-06.md deleted file mode 100644 index 470ecf1b..00000000 --- a/demo-vault-v2/event-gym-2024-11-06.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Gym — 2024-11-06"] -Is A: Event -Date: "2024-11-06" -Belongs to: "[[2024-11]]" -Tags: ["Health"] ---- -# Gym — 2024-11-06 -Strength training. Squat, deadlift, pull-ups. 75 minutes. - -## Notes -- Back squat 5x5 at 97.5kg — pushing towards 100kg for fives -- Sumo deadlift 3x5 at 110kg, stance feels dialed in now -- Pull-ups 4x6 with 12.5kg vest -- Cold morning but warmed up fast, good energy throughout diff --git a/demo-vault-v2/event-gym-2024-11-20.md b/demo-vault-v2/event-gym-2024-11-20.md deleted file mode 100644 index d9705462..00000000 --- a/demo-vault-v2/event-gym-2024-11-20.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Gym — 2024-11-20"] -Is A: Event -Date: "2024-11-20" -Belongs to: "[[2024-11]]" -Tags: ["Health"] ---- -# Gym — 2024-11-20 -Strength training. Squat, deadlift, pull-ups. 75 minutes. - -## Notes -- Front squat 4x5 at 77.5kg — paused reps for depth work -- Conventional deadlift 3x3 at 125kg, Deadlift PR: 125kg x 3 -- Weighted chin-ups 3x6 at 15kg -- Lower back slightly tight so did extra stretching afterwards diff --git a/demo-vault-v2/event-gym-2024-12-04.md b/demo-vault-v2/event-gym-2024-12-04.md deleted file mode 100644 index 56e6720e..00000000 --- a/demo-vault-v2/event-gym-2024-12-04.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Gym — 2024-12-04"] -Is A: Event -Date: "2024-12-04" -Belongs to: "[[2024-12]]" -Tags: ["Health"] ---- -# Gym — 2024-12-04 -Strength training. Squat, deadlift, pull-ups. 75 minutes. - -## Notes -- Back squat 5x5 at 97.5kg — one more session before attempting 100kg x 5 -- Romanian deadlift 3x8 at 92.5kg, controlled tempo -- Pull-ups 5x5 with 10kg, strong and consistent -- Feeling well-prepared for end-of-year strength test diff --git a/demo-vault-v2/event-gym-2024-12-18.md b/demo-vault-v2/event-gym-2024-12-18.md deleted file mode 100644 index ef710565..00000000 --- a/demo-vault-v2/event-gym-2024-12-18.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Gym — 2024-12-18"] -Is A: Event -Date: "2024-12-18" -Belongs to: "[[2024-12]]" -Tags: ["Health"] ---- -# Gym — 2024-12-18 -Strength training. Squat, deadlift, pull-ups. 75 minutes. - -## Notes -- Back squat 5x5 at 100kg — Squat PR: 100kg x 5 x 5, massive milestone -- Conventional deadlift 3x5 at 120kg, smooth and confident -- Weighted pull-ups 4x5 at 15kg -- Perfect way to close the year, all major lifts at yearly highs diff --git a/demo-vault-v2/event-gym-2025-01-01.md b/demo-vault-v2/event-gym-2025-01-01.md deleted file mode 100644 index 281f1de3..00000000 --- a/demo-vault-v2/event-gym-2025-01-01.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Gym — 2025-01-01"] -Is A: Event -Date: "2025-01-01" -Belongs to: "[[2025-01]]" -Tags: ["Health"] ---- -# Gym — 2025-01-01 -Strength training. Squat, deadlift, pull-ups. 75 minutes. - -## Notes -- Back squat 3x5 at 90kg — New Year's Day deload, just getting moving -- Light deadlifts 3x8 at 85kg, focusing on form reset for the new cycle -- Pull-ups 4x8 bodyweight, easy and controlled -- Gym was empty, peaceful start to the year diff --git a/demo-vault-v2/event-gym-2025-01-15.md b/demo-vault-v2/event-gym-2025-01-15.md deleted file mode 100644 index 4afdb833..00000000 --- a/demo-vault-v2/event-gym-2025-01-15.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Gym — 2025-01-15"] -Is A: Event -Date: "2025-01-15" -Belongs to: "[[2025-01]]" -Tags: ["Health"] ---- -# Gym — 2025-01-15 -Strength training. Squat, deadlift, pull-ups. 75 minutes. - -## Notes -- Back squat 5x5 at 95kg — ramping back up after the holiday deload -- Conventional deadlift 3x5 at 112.5kg, hook grip back in play -- Weighted chin-ups 3x6 at 10kg -- Cold January morning but session went well, caffeinated heavily diff --git a/demo-vault-v2/event-gym-2025-01-29.md b/demo-vault-v2/event-gym-2025-01-29.md deleted file mode 100644 index 6a2d506a..00000000 --- a/demo-vault-v2/event-gym-2025-01-29.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Gym — 2025-01-29"] -Is A: Event -Date: "2025-01-29" -Belongs to: "[[2025-01]]" -Tags: ["Health"] ---- -# Gym — 2025-01-29 -Strength training. Squat, deadlift, pull-ups. 75 minutes. - -## Notes -- Back squat 5x5 at 100kg — maintaining the PR weight from December -- Romanian deadlift 3x8 at 90kg, good hamstring engagement -- Pull-ups 4x6 with 12.5kg vest -- Abs circuit at the end: hanging leg raises, Russian twists, plank diff --git a/demo-vault-v2/event-gym-2025-02-12.md b/demo-vault-v2/event-gym-2025-02-12.md deleted file mode 100644 index 034f7675..00000000 --- a/demo-vault-v2/event-gym-2025-02-12.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Gym — 2025-02-12"] -Is A: Event -Date: "2025-02-12" -Belongs to: "[[2025-02]]" -Tags: ["Health"] ---- -# Gym — 2025-02-12 -Strength training. Squat, deadlift, pull-ups. 75 minutes. - -## Notes -- Front squat 4x5 at 80kg — really clean reps, wrists feeling better -- Deadlift 3x3 at 127.5kg, new 3RM attempt next session -- Weighted pull-ups 4x5 at 15kg -- Strong session despite a stressful work week diff --git a/demo-vault-v2/event-gym-2025-02-26.md b/demo-vault-v2/event-gym-2025-02-26.md deleted file mode 100644 index 6ffc5909..00000000 --- a/demo-vault-v2/event-gym-2025-02-26.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Gym — 2025-02-26"] -Is A: Event -Date: "2025-02-26" -Belongs to: "[[2025-02]]" -Tags: ["Health"] ---- -# Gym — 2025-02-26 -Strength training. Squat, deadlift, pull-ups. 75 minutes. - -## Notes -- Back squat 5x5 at 100kg — felt routine now, good sign -- Conventional deadlift 3x3 at 130kg, Deadlift PR: 130kg x 3 -- Chin-ups 4x8 bodyweight, superset with dips 4x10 -- Riding high after the deadlift PR, grip was the limiting factor diff --git a/demo-vault-v2/event-gym-2025-03-12.md b/demo-vault-v2/event-gym-2025-03-12.md deleted file mode 100644 index 0e1fc474..00000000 --- a/demo-vault-v2/event-gym-2025-03-12.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Gym — 2025-03-12"] -Is A: Event -Date: "2025-03-12" -Belongs to: "[[2025-03]]" -Tags: ["Health"] ---- -# Gym — 2025-03-12 -Strength training. Squat, deadlift, pull-ups. 75 minutes. - -## Notes -- Back squat 4x4 at 102.5kg — inching up, felt heavy on rep 4 -- Sumo deadlift 3x5 at 112.5kg, alternating sumo and conventional weeks -- Pull-ups 5x5 with 12.5kg -- Core work: ab wheel 3x10, Pallof press 3x12 each side diff --git a/demo-vault-v2/event-gym-2025-03-26.md b/demo-vault-v2/event-gym-2025-03-26.md deleted file mode 100644 index 27a9973c..00000000 --- a/demo-vault-v2/event-gym-2025-03-26.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Gym — 2025-03-26"] -Is A: Event -Date: "2025-03-26" -Belongs to: "[[2025-03]]" -Tags: ["Health"] ---- -# Gym — 2025-03-26 -Strength training. Squat, deadlift, pull-ups. 75 minutes. - -## Notes -- Back squat 5x5 at 100kg — volume day, all reps clean -- Romanian deadlift 3x8 at 95kg, slow eccentric 3 seconds -- Weighted chin-ups 4x5 at 15kg -- Legs felt fresh, cycling has been lighter this month diff --git a/demo-vault-v2/event-gym-2025-04-09.md b/demo-vault-v2/event-gym-2025-04-09.md deleted file mode 100644 index 9cd1ed54..00000000 --- a/demo-vault-v2/event-gym-2025-04-09.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Gym — 2025-04-09"] -Is A: Event -Date: "2025-04-09" -Belongs to: "[[2025-04]]" -Tags: ["Health"] ---- -# Gym — 2025-04-09 -Strength training. Squat, deadlift, pull-ups. 75 minutes. - -## Notes -- Back squat 3x3 at 105kg — Squat PR: 105kg x 3, grinding on the last rep -- Conventional deadlift 3x5 at 120kg, belt and chalk -- Pull-ups 4x6 with 10kg vest -- Adrenaline rush after the squat PR, everything felt lighter after diff --git a/demo-vault-v2/event-gym-2025-04-23.md b/demo-vault-v2/event-gym-2025-04-23.md deleted file mode 100644 index bd01cb89..00000000 --- a/demo-vault-v2/event-gym-2025-04-23.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Gym — 2025-04-23"] -Is A: Event -Date: "2025-04-23" -Belongs to: "[[2025-04]]" -Tags: ["Health"] ---- -# Gym — 2025-04-23 -Strength training. Squat, deadlift, pull-ups. 75 minutes. - -## Notes -- Front squat 4x5 at 82.5kg — paused reps, bracing much improved -- Trap bar deadlift 3x6 at 110kg, explosive focus -- Weighted pull-ups 3x6 at 12.5kg -- Farmer's walks 3x40m with 40kg per hand, forearms burning diff --git a/demo-vault-v2/event-gym-2025-05-07.md b/demo-vault-v2/event-gym-2025-05-07.md deleted file mode 100644 index bab759c3..00000000 --- a/demo-vault-v2/event-gym-2025-05-07.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Gym — 2025-05-07"] -Is A: Event -Date: "2025-05-07" -Belongs to: "[[2025-05]]" -Tags: ["Health"] ---- -# Gym — 2025-05-07 -Strength training. Squat, deadlift, pull-ups. 75 minutes. - -## Notes -- Back squat 5x5 at 102.5kg — volume PR, all sets completed -- Conventional deadlift 3x5 at 122.5kg, grip holding with hook -- Chin-ups 4x8 bodyweight, easy day for pulling -- Felt powerful, sleep and nutrition have been consistent this week diff --git a/demo-vault-v2/event-gym-2025-05-21.md b/demo-vault-v2/event-gym-2025-05-21.md deleted file mode 100644 index e9c33e8b..00000000 --- a/demo-vault-v2/event-gym-2025-05-21.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Gym — 2025-05-21"] -Is A: Event -Date: "2025-05-21" -Belongs to: "[[2025-05]]" -Tags: ["Health"] ---- -# Gym — 2025-05-21 -Strength training. Squat, deadlift, pull-ups. 75 minutes. - -## Notes -- Back squat 5x5 at 100kg — slight deload, hip felt off during warm-up -- Romanian deadlift 3x10 at 80kg, high-rep week for variation -- Pull-ups 5x5 with slow negatives (4 sec down) -- Took it easier today, listening to the body rather than pushing through diff --git a/demo-vault-v2/event-gym-2025-06-04.md b/demo-vault-v2/event-gym-2025-06-04.md deleted file mode 100644 index e906f3d2..00000000 --- a/demo-vault-v2/event-gym-2025-06-04.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Gym — 2025-06-04"] -Is A: Event -Date: "2025-06-04" -Belongs to: "[[2025-06]]" -Tags: ["Health"] ---- -# Gym — 2025-06-04 -Strength training. Squat, deadlift, pull-ups. 75 minutes. - -## Notes -- Back squat 4x4 at 105kg — building back to heavy triples -- Deadlift 3x3 at 130kg, matched the February PR comfortably -- Weighted pull-ups 4x5 at 15kg -- Summer session, great energy, gym was quiet mid-afternoon diff --git a/demo-vault-v2/event-gym-2025-06-18.md b/demo-vault-v2/event-gym-2025-06-18.md deleted file mode 100644 index a084e92c..00000000 --- a/demo-vault-v2/event-gym-2025-06-18.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Gym — 2025-06-18"] -Is A: Event -Date: "2025-06-18" -Belongs to: "[[2025-06]]" -Tags: ["Health"] ---- -# Gym — 2025-06-18 -Strength training. Squat, deadlift, pull-ups. 75 minutes. - -## Notes -- Back squat 3x3 at 107.5kg — Squat PR: 107.5kg x 3, new all-time best -- Conventional deadlift 3x5 at 125kg, strong lockout -- Chin-ups 4x6 with 15kg -- Best session of the year, everything clicked today diff --git a/demo-vault-v2/event-gym-fri-2024-01-12.md b/demo-vault-v2/event-gym-fri-2024-01-12.md deleted file mode 100644 index 60efa2de..00000000 --- a/demo-vault-v2/event-gym-fri-2024-01-12.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Gym — 2024-01-12"] -Is A: Event -Date: "2024-01-12" -Belongs to: "[[2024-01]]" -Tags: ["Health"] ---- -# Gym — 2024-01-12 -Strength session. Bench press, rows, overhead press. Core work. - -## Notes -- Bench press 4x6 at 60kg — easing back in after the holidays -- Barbell rows 4x8 at 55kg, focused on squeezing at the top -- Overhead press 3x8 at 35kg, shoulders still warming up -- Plank holds 3x45sec to finish, core felt weak diff --git a/demo-vault-v2/event-gym-fri-2024-01-26.md b/demo-vault-v2/event-gym-fri-2024-01-26.md deleted file mode 100644 index f26d4630..00000000 --- a/demo-vault-v2/event-gym-fri-2024-01-26.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Gym — 2024-01-26"] -Is A: Event -Date: "2024-01-26" -Belongs to: "[[2024-01]]" -Tags: ["Health"] ---- -# Gym — 2024-01-26 -Strength session. Bench press, rows, overhead press. Core work. - -## Notes -- Bench press 4x6 at 62.5kg — slight increase, felt stable -- Pendlay rows 4x6 at 60kg, explosive off the floor -- Seated OHP 3x8 at 32.5kg with dumbbells -- Face pulls 3x15, cable flyes 3x12 to finish diff --git a/demo-vault-v2/event-gym-fri-2024-02-09.md b/demo-vault-v2/event-gym-fri-2024-02-09.md deleted file mode 100644 index a7d38d2f..00000000 --- a/demo-vault-v2/event-gym-fri-2024-02-09.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Gym — 2024-02-09"] -Is A: Event -Date: "2024-02-09" -Belongs to: "[[2024-02]]" -Tags: ["Health"] ---- -# Gym — 2024-02-09 -Strength session. Bench press, rows, overhead press. Core work. - -## Notes -- Bench press 4x5 at 65kg — progressing nicely on the linear plan -- Barbell rows 4x8 at 57.5kg, controlled tempo -- Standing OHP 3x6 at 40kg, strict form no leg drive -- Finished with lateral raises 3x12 and tricep pushdowns 3x15 diff --git a/demo-vault-v2/event-gym-fri-2024-02-23.md b/demo-vault-v2/event-gym-fri-2024-02-23.md deleted file mode 100644 index 9301a378..00000000 --- a/demo-vault-v2/event-gym-fri-2024-02-23.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Gym — 2024-02-23"] -Is A: Event -Date: "2024-02-23" -Belongs to: "[[2024-02]]" -Tags: ["Health"] ---- -# Gym — 2024-02-23 -Strength session. Bench press, rows, overhead press. Core work. - -## Notes -- Incline bench 4x8 at 50kg — mixing up the pressing angle -- Cable rows 4x10 at 55kg, really squeezing the lats -- OHP 3x6 at 42.5kg, right shoulder felt slightly tight -- Ab wheel rollouts 3x10, hanging leg raises 3x12 diff --git a/demo-vault-v2/event-gym-fri-2024-03-08.md b/demo-vault-v2/event-gym-fri-2024-03-08.md deleted file mode 100644 index c6f543f0..00000000 --- a/demo-vault-v2/event-gym-fri-2024-03-08.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Gym — 2024-03-08"] -Is A: Event -Date: "2024-03-08" -Belongs to: "[[2024-03]]" -Tags: ["Health"] ---- -# Gym — 2024-03-08 -Strength session. Bench press, rows, overhead press. Core work. - -## Notes -- Bench press 4x5 at 67.5kg — smooth, Bench PR: 67.5kg x 5 -- Barbell rows 4x6 at 62.5kg, heavier than usual -- Push press 3x5 at 45kg, using leg drive for the last set -- Band pull-aparts 3x20 for shoulder health diff --git a/demo-vault-v2/event-gym-fri-2024-03-22.md b/demo-vault-v2/event-gym-fri-2024-03-22.md deleted file mode 100644 index 336afd0e..00000000 --- a/demo-vault-v2/event-gym-fri-2024-03-22.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Gym — 2024-03-22"] -Is A: Event -Date: "2024-03-22" -Belongs to: "[[2024-03]]" -Tags: ["Health"] ---- -# Gym — 2024-03-22 -Strength session. Bench press, rows, overhead press. Core work. - -## Notes -- Bench press 5x5 at 65kg — volume day, all sets clean -- Dumbbell rows 4x8 at 30kg each, unilateral work -- OHP 3x8 at 37.5kg, lighter weight higher reps -- Finished with cable crunches 3x15 and Pallof press 3x12 diff --git a/demo-vault-v2/event-gym-fri-2024-04-05.md b/demo-vault-v2/event-gym-fri-2024-04-05.md deleted file mode 100644 index 01051dbd..00000000 --- a/demo-vault-v2/event-gym-fri-2024-04-05.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Gym — 2024-04-05"] -Is A: Event -Date: "2024-04-05" -Belongs to: "[[2024-04]]" -Tags: ["Health"] ---- -# Gym — 2024-04-05 -Strength session. Bench press, rows, overhead press. Core work. - -## Notes -- Bench press 4x5 at 70kg — Bench PR: 70kg x 5, first time at this weight -- Pendlay rows 4x6 at 65kg, keeping momentum -- Standing OHP 3x6 at 42.5kg, strict and controlled -- Dips 3x10 bodyweight, feeling light and strong diff --git a/demo-vault-v2/event-gym-fri-2024-04-19.md b/demo-vault-v2/event-gym-fri-2024-04-19.md deleted file mode 100644 index 1db8a040..00000000 --- a/demo-vault-v2/event-gym-fri-2024-04-19.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Gym — 2024-04-19"] -Is A: Event -Date: "2024-04-19" -Belongs to: "[[2024-04]]" -Tags: ["Health"] ---- -# Gym — 2024-04-19 -Strength session. Bench press, rows, overhead press. Core work. - -## Notes -- Incline dumbbell press 4x8 at 27.5kg each — hypertrophy focus -- Seated cable rows 4x10 at 60kg, slow eccentric -- Arnold press 3x10 at 20kg dumbbells -- Face pulls 3x15, lateral raises 3x12, nice pump session diff --git a/demo-vault-v2/event-gym-fri-2024-05-03.md b/demo-vault-v2/event-gym-fri-2024-05-03.md deleted file mode 100644 index 37adc167..00000000 --- a/demo-vault-v2/event-gym-fri-2024-05-03.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Gym — 2024-05-03"] -Is A: Event -Date: "2024-05-03" -Belongs to: "[[2024-05]]" -Tags: ["Health"] ---- -# Gym — 2024-05-03 -Strength session. Bench press, rows, overhead press. Core work. - -## Notes -- Bench press 4x5 at 70kg — maintaining, consistent -- Barbell rows 4x8 at 60kg, lighter day for recovery -- OHP 3x5 at 45kg, getting closer to a plate -- Tricep dips 3x12, skull crushers 3x10 at 25kg diff --git a/demo-vault-v2/event-gym-fri-2024-05-17.md b/demo-vault-v2/event-gym-fri-2024-05-17.md deleted file mode 100644 index 0488f822..00000000 --- a/demo-vault-v2/event-gym-fri-2024-05-17.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Gym — 2024-05-17"] -Is A: Event -Date: "2024-05-17" -Belongs to: "[[2024-05]]" -Tags: ["Health"] ---- -# Gym — 2024-05-17 -Strength session. Bench press, rows, overhead press. Core work. - -## Notes -- Bench press 3x3 at 75kg — heavy triples day, felt strong -- Dumbbell rows 4x8 at 32.5kg each, pulling hard -- Push press 3x5 at 47.5kg, using the momentum well -- Band pull-aparts 3x20, rotator cuff warm-up paying off diff --git a/demo-vault-v2/event-gym-fri-2024-05-31.md b/demo-vault-v2/event-gym-fri-2024-05-31.md deleted file mode 100644 index bb750b8b..00000000 --- a/demo-vault-v2/event-gym-fri-2024-05-31.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Gym — 2024-05-31"] -Is A: Event -Date: "2024-05-31" -Belongs to: "[[2024-05]]" -Tags: ["Health"] ---- -# Gym — 2024-05-31 -Strength session. Bench press, rows, overhead press. Core work. - -## Notes -- Bench press 5x5 at 67.5kg — deload after heavy week -- Cable rows 4x10 at 57.5kg, mind-muscle connection -- Seated dumbbell OHP 3x10 at 22.5kg each -- Core circuit: plank 60sec, side plank 30sec each, dead bug 3x10 diff --git a/demo-vault-v2/event-gym-fri-2024-06-14.md b/demo-vault-v2/event-gym-fri-2024-06-14.md deleted file mode 100644 index 0e2752a1..00000000 --- a/demo-vault-v2/event-gym-fri-2024-06-14.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Gym — 2024-06-14"] -Is A: Event -Date: "2024-06-14" -Belongs to: "[[2024-06]]" -Tags: ["Health"] ---- -# Gym — 2024-06-14 -Strength session. Bench press, rows, overhead press. Core work. - -## Notes -- Bench press 4x5 at 72.5kg — building back up after deload -- Barbell rows 4x6 at 65kg, straps on last set -- Standing OHP 3x6 at 45kg, OHP PR: 45kg x 6 -- Lateral raises 4x12, rear delt flyes 3x15 diff --git a/demo-vault-v2/event-gym-fri-2024-06-28.md b/demo-vault-v2/event-gym-fri-2024-06-28.md deleted file mode 100644 index 195b13b3..00000000 --- a/demo-vault-v2/event-gym-fri-2024-06-28.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Gym — 2024-06-28"] -Is A: Event -Date: "2024-06-28" -Belongs to: "[[2024-06]]" -Tags: ["Health"] ---- -# Gym — 2024-06-28 -Strength session. Bench press, rows, overhead press. Core work. - -## Notes -- Close-grip bench 4x6 at 60kg — tricep emphasis -- Pendlay rows 4x5 at 67.5kg, explosive and heavy -- OHP 3x5 at 47.5kg, grinding on the last rep -- Finished with hammer curls 3x12 and overhead tricep extensions 3x12 diff --git a/demo-vault-v2/event-gym-fri-2024-07-12.md b/demo-vault-v2/event-gym-fri-2024-07-12.md deleted file mode 100644 index 15c1f84b..00000000 --- a/demo-vault-v2/event-gym-fri-2024-07-12.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Gym — 2024-07-12"] -Is A: Event -Date: "2024-07-12" -Belongs to: "[[2024-07]]" -Tags: ["Health"] ---- -# Gym — 2024-07-12 -Strength session. Bench press, rows, overhead press. Core work. - -## Notes -- Bench press 4x5 at 75kg — Bench PR: 75kg x 5, solid milestone -- Dumbbell rows 4x8 at 35kg each, strong pulling -- Push press 3x5 at 50kg, first time at 50 -- Sweating buckets in the summer heat, extra water breaks needed diff --git a/demo-vault-v2/event-gym-fri-2024-07-26.md b/demo-vault-v2/event-gym-fri-2024-07-26.md deleted file mode 100644 index 15192cdb..00000000 --- a/demo-vault-v2/event-gym-fri-2024-07-26.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Gym — 2024-07-26"] -Is A: Event -Date: "2024-07-26" -Belongs to: "[[2024-07]]" -Tags: ["Health"] ---- -# Gym — 2024-07-26 -Strength session. Bench press, rows, overhead press. Core work. - -## Notes -- Incline bench 4x6 at 57.5kg — upper chest focus -- Barbell rows 4x8 at 62.5kg, lighter high-rep day -- OHP 3x8 at 40kg, endurance work -- Cable crunches 3x15, hanging knee raises 3x12 diff --git a/demo-vault-v2/event-gym-fri-2024-08-09.md b/demo-vault-v2/event-gym-fri-2024-08-09.md deleted file mode 100644 index eb80448a..00000000 --- a/demo-vault-v2/event-gym-fri-2024-08-09.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Gym — 2024-08-09"] -Is A: Event -Date: "2024-08-09" -Belongs to: "[[2024-08]]" -Tags: ["Health"] ---- -# Gym — 2024-08-09 -Strength session. Bench press, rows, overhead press. Core work. - -## Notes -- Bench press 5x5 at 70kg — lighter session, pre-holiday -- Seated cable rows 4x10 at 55kg, easy pace -- Dumbbell OHP 3x10 at 22.5kg each -- Quick 45-minute session before heading out for the weekend diff --git a/demo-vault-v2/event-gym-fri-2024-08-23.md b/demo-vault-v2/event-gym-fri-2024-08-23.md deleted file mode 100644 index fd2ececc..00000000 --- a/demo-vault-v2/event-gym-fri-2024-08-23.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Gym — 2024-08-23"] -Is A: Event -Date: "2024-08-23" -Belongs to: "[[2024-08]]" -Tags: ["Health"] ---- -# Gym — 2024-08-23 -Strength session. Bench press, rows, overhead press. Core work. - -## Notes -- Bench press 4x5 at 72.5kg — back from holiday, rust shaking off -- Barbell rows 4x6 at 62.5kg, form felt sloppy on set 1 -- Standing OHP 3x6 at 42.5kg, played it safe -- Face pulls 3x20 for shoulder rehab after too much swimming diff --git a/demo-vault-v2/event-gym-fri-2024-09-06.md b/demo-vault-v2/event-gym-fri-2024-09-06.md deleted file mode 100644 index 2256b4df..00000000 --- a/demo-vault-v2/event-gym-fri-2024-09-06.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Gym — 2024-09-06"] -Is A: Event -Date: "2024-09-06" -Belongs to: "[[2024-09]]" -Tags: ["Health"] ---- -# Gym — 2024-09-06 -Strength session. Bench press, rows, overhead press. Core work. - -## Notes -- Bench press 4x5 at 75kg — back to pre-holiday strength -- Pendlay rows 4x5 at 67.5kg, crisp reps -- OHP 3x5 at 47.5kg, pressing feels strong again -- Dips 3x12 with 5kg added, triceps on fire diff --git a/demo-vault-v2/event-gym-fri-2024-09-20.md b/demo-vault-v2/event-gym-fri-2024-09-20.md deleted file mode 100644 index e42a32c5..00000000 --- a/demo-vault-v2/event-gym-fri-2024-09-20.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Gym — 2024-09-20"] -Is A: Event -Date: "2024-09-20" -Belongs to: "[[2024-09]]" -Tags: ["Health"] ---- -# Gym — 2024-09-20 -Strength session. Bench press, rows, overhead press. Core work. - -## Notes -- Bench press 3x3 at 80kg — Bench PR: 80kg x 3, huge jump -- Dumbbell rows 4x8 at 35kg each, stable and strong -- Push press 3x3 at 52.5kg, heavy overhead work -- Celebrated the bench PR with extra accessory volume diff --git a/demo-vault-v2/event-gym-fri-2024-10-04.md b/demo-vault-v2/event-gym-fri-2024-10-04.md deleted file mode 100644 index 76eca3e9..00000000 --- a/demo-vault-v2/event-gym-fri-2024-10-04.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Gym — 2024-10-04"] -Is A: Event -Date: "2024-10-04" -Belongs to: "[[2024-10]]" -Tags: ["Health"] ---- -# Gym — 2024-10-04 -Strength session. Bench press, rows, overhead press. Core work. - -## Notes -- Bench press 5x5 at 72.5kg — volume work after the PR -- Barbell rows 4x8 at 65kg, controlled and steady -- OHP 3x8 at 40kg, lighter hypertrophy phase -- Core finisher: plank 3x60sec, Russian twists 3x20 diff --git a/demo-vault-v2/event-gym-fri-2024-10-18.md b/demo-vault-v2/event-gym-fri-2024-10-18.md deleted file mode 100644 index 6efae2b9..00000000 --- a/demo-vault-v2/event-gym-fri-2024-10-18.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Gym — 2024-10-18"] -Is A: Event -Date: "2024-10-18" -Belongs to: "[[2024-10]]" -Tags: ["Health"] ---- -# Gym — 2024-10-18 -Strength session. Bench press, rows, overhead press. Core work. - -## Notes -- Bench press 4x5 at 77.5kg — building towards 80kg for fives -- Cable rows 4x10 at 62.5kg, high rep back work -- Standing OHP 3x5 at 47.5kg, felt like autopilot -- Lateral raises 4x12, rear delt flyes 3x15 to round it out diff --git a/demo-vault-v2/event-gym-fri-2024-11-01.md b/demo-vault-v2/event-gym-fri-2024-11-01.md deleted file mode 100644 index 3198d2f1..00000000 --- a/demo-vault-v2/event-gym-fri-2024-11-01.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Gym — 2024-11-01"] -Is A: Event -Date: "2024-11-01" -Belongs to: "[[2024-11]]" -Tags: ["Health"] ---- -# Gym — 2024-11-01 -Strength session. Bench press, rows, overhead press. Core work. - -## Notes -- Bench press 4x5 at 77.5kg — last rep of set 4 was a grind -- Pendlay rows 4x6 at 67.5kg, heavy and explosive -- OHP 3x6 at 45kg, shoulders fatigued from bench -- Tricep pushdowns 3x15, bicep curls 3x12 for arms diff --git a/demo-vault-v2/event-gym-fri-2024-11-15.md b/demo-vault-v2/event-gym-fri-2024-11-15.md deleted file mode 100644 index bd57fadc..00000000 --- a/demo-vault-v2/event-gym-fri-2024-11-15.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Gym — 2024-11-15"] -Is A: Event -Date: "2024-11-15" -Belongs to: "[[2024-11]]" -Tags: ["Health"] ---- -# Gym — 2024-11-15 -Strength session. Bench press, rows, overhead press. Core work. - -## Notes -- Incline bench 4x6 at 60kg — variation week -- Dumbbell rows 4x8 at 35kg each, solid work -- Arnold press 3x10 at 22.5kg dumbbells, nice shoulder pump -- Hanging leg raises 3x15, ab wheel 3x10 diff --git a/demo-vault-v2/event-gym-fri-2024-11-29.md b/demo-vault-v2/event-gym-fri-2024-11-29.md deleted file mode 100644 index 7e4e949f..00000000 --- a/demo-vault-v2/event-gym-fri-2024-11-29.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Gym — 2024-11-29"] -Is A: Event -Date: "2024-11-29" -Belongs to: "[[2024-11]]" -Tags: ["Health"] ---- -# Gym — 2024-11-29 -Strength session. Bench press, rows, overhead press. Core work. - -## Notes -- Bench press 4x5 at 80kg — Bench PR: 80kg x 5, matching the triple from September -- Barbell rows 4x6 at 70kg, strong session all around -- Standing OHP 3x5 at 50kg, OHP PR: 50kg x 5 -- Two PRs in one session, ending November on a high note diff --git a/demo-vault-v2/event-gym-fri-2024-12-13.md b/demo-vault-v2/event-gym-fri-2024-12-13.md deleted file mode 100644 index c5651610..00000000 --- a/demo-vault-v2/event-gym-fri-2024-12-13.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Gym — 2024-12-13"] -Is A: Event -Date: "2024-12-13" -Belongs to: "[[2024-12]]" -Tags: ["Health"] ---- -# Gym — 2024-12-13 -Strength session. Bench press, rows, overhead press. Core work. - -## Notes -- Bench press 5x5 at 75kg — high volume day, maintaining strength -- Seated cable rows 4x10 at 60kg, back pump -- Push press 3x5 at 52.5kg, explosive overhead -- Face pulls 3x20, band pull-aparts 3x20 to keep shoulders healthy diff --git a/demo-vault-v2/event-gym-fri-2024-12-27.md b/demo-vault-v2/event-gym-fri-2024-12-27.md deleted file mode 100644 index 4e3a9333..00000000 --- a/demo-vault-v2/event-gym-fri-2024-12-27.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Gym — 2024-12-27"] -Is A: Event -Date: "2024-12-27" -Belongs to: "[[2024-12]]" -Tags: ["Health"] ---- -# Gym — 2024-12-27 -Strength session. Bench press, rows, overhead press. Core work. - -## Notes -- Bench press 4x6 at 70kg — easy holiday session between meals -- Dumbbell rows 4x8 at 30kg each, light and controlled -- Seated dumbbell OHP 3x10 at 22.5kg each -- Short session, just keeping the habit alive over the break diff --git a/demo-vault-v2/event-gym-fri-2025-01-10.md b/demo-vault-v2/event-gym-fri-2025-01-10.md deleted file mode 100644 index c75e2931..00000000 --- a/demo-vault-v2/event-gym-fri-2025-01-10.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Gym — 2025-01-10"] -Is A: Event -Date: "2025-01-10" -Belongs to: "[[2025-01]]" -Tags: ["Health"] ---- -# Gym — 2025-01-10 -Strength session. Bench press, rows, overhead press. Core work. - -## Notes -- Bench press 4x5 at 75kg — new year, ramping back to PR weights -- Barbell rows 4x8 at 65kg, focused on pulling to the sternum -- Standing OHP 3x6 at 45kg, solid start to the year -- Core: plank 3x60sec, hanging leg raises 3x12 diff --git a/demo-vault-v2/event-gym-fri-2025-01-24.md b/demo-vault-v2/event-gym-fri-2025-01-24.md deleted file mode 100644 index 02e45a63..00000000 --- a/demo-vault-v2/event-gym-fri-2025-01-24.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Gym — 2025-01-24"] -Is A: Event -Date: "2025-01-24" -Belongs to: "[[2025-01]]" -Tags: ["Health"] ---- -# Gym — 2025-01-24 -Strength session. Bench press, rows, overhead press. Core work. - -## Notes -- Bench press 4x5 at 80kg — back to November PR weight, felt routine -- Pendlay rows 4x5 at 70kg, heavy and crisp -- OHP 3x5 at 50kg, maintaining the PR easily -- Dips 3x10 with 10kg added, tricep strength improving diff --git a/demo-vault-v2/event-gym-fri-2025-02-07.md b/demo-vault-v2/event-gym-fri-2025-02-07.md deleted file mode 100644 index 54160d24..00000000 --- a/demo-vault-v2/event-gym-fri-2025-02-07.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Gym — 2025-02-07"] -Is A: Event -Date: "2025-02-07" -Belongs to: "[[2025-02]]" -Tags: ["Health"] ---- -# Gym — 2025-02-07 -Strength session. Bench press, rows, overhead press. Core work. - -## Notes -- Bench press 3x3 at 82.5kg — testing new territory, Bench PR: 82.5kg x 3 -- Dumbbell rows 4x8 at 37.5kg each, balancing the pressing -- Push press 3x3 at 55kg, heavy overhead -- Feeling confident, bench is finally catching up to squat progress diff --git a/demo-vault-v2/event-gym-fri-2025-02-21.md b/demo-vault-v2/event-gym-fri-2025-02-21.md deleted file mode 100644 index 71bf48c2..00000000 --- a/demo-vault-v2/event-gym-fri-2025-02-21.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Gym — 2025-02-21"] -Is A: Event -Date: "2025-02-21" -Belongs to: "[[2025-02]]" -Tags: ["Health"] ---- -# Gym — 2025-02-21 -Strength session. Bench press, rows, overhead press. Core work. - -## Notes -- Bench press 5x5 at 77.5kg — volume block after the PR -- Cable rows 4x10 at 65kg, steady back work -- Standing OHP 3x8 at 42.5kg, lighter but controlled -- Lateral raises 3x15, face pulls 3x15, shoulder prehab circuit diff --git a/demo-vault-v2/event-gym-fri-2025-03-07.md b/demo-vault-v2/event-gym-fri-2025-03-07.md deleted file mode 100644 index ed34fd91..00000000 --- a/demo-vault-v2/event-gym-fri-2025-03-07.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Gym — 2025-03-07"] -Is A: Event -Date: "2025-03-07" -Belongs to: "[[2025-03]]" -Tags: ["Health"] ---- -# Gym — 2025-03-07 -Strength session. Bench press, rows, overhead press. Core work. - -## Notes -- Bench press 4x5 at 80kg — routine now, aiming for 82.5 x 5 -- Barbell rows 4x6 at 72.5kg, heaviest rows to date -- OHP 3x5 at 50kg, consistent pressing -- Finished with skull crushers 3x10 at 27.5kg and hammer curls 3x12 diff --git a/demo-vault-v2/event-gym-fri-2025-03-21.md b/demo-vault-v2/event-gym-fri-2025-03-21.md deleted file mode 100644 index 51cd2588..00000000 --- a/demo-vault-v2/event-gym-fri-2025-03-21.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Gym — 2025-03-21"] -Is A: Event -Date: "2025-03-21" -Belongs to: "[[2025-03]]" -Tags: ["Health"] ---- -# Gym — 2025-03-21 -Strength session. Bench press, rows, overhead press. Core work. - -## Notes -- Incline bench 4x6 at 62.5kg — variation week for upper chest -- Dumbbell rows 4x8 at 37.5kg each, both sides even -- Arnold press 3x8 at 25kg dumbbells, shoulder pump -- Ab circuit: hanging leg raises 3x15, Russian twists 3x20, plank 60sec diff --git a/demo-vault-v2/event-gym-fri-2025-04-04.md b/demo-vault-v2/event-gym-fri-2025-04-04.md deleted file mode 100644 index 29404b1c..00000000 --- a/demo-vault-v2/event-gym-fri-2025-04-04.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Gym — 2025-04-04"] -Is A: Event -Date: "2025-04-04" -Belongs to: "[[2025-04]]" -Tags: ["Health"] ---- -# Gym — 2025-04-04 -Strength session. Bench press, rows, overhead press. Core work. - -## Notes -- Bench press 4x5 at 82.5kg — Bench PR: 82.5kg x 5, finally hit fives at this weight -- Pendlay rows 4x5 at 72.5kg, explosive pulling -- OHP 3x5 at 52.5kg, OHP PR: 52.5kg x 5 -- Incredible session, both pressing movements hit PRs diff --git a/demo-vault-v2/event-gym-fri-2025-04-18.md b/demo-vault-v2/event-gym-fri-2025-04-18.md deleted file mode 100644 index 4e680d75..00000000 --- a/demo-vault-v2/event-gym-fri-2025-04-18.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Gym — 2025-04-18"] -Is A: Event -Date: "2025-04-18" -Belongs to: "[[2025-04]]" -Tags: ["Health"] ---- -# Gym — 2025-04-18 -Strength session. Bench press, rows, overhead press. Core work. - -## Notes -- Close-grip bench 4x6 at 65kg — tricep emphasis after last week's PRs -- Seated cable rows 4x10 at 65kg, slow and controlled -- Seated dumbbell OHP 3x10 at 25kg each, hypertrophy -- Dips 3x12 bodyweight, band pull-aparts 3x20 for prehab diff --git a/demo-vault-v2/event-gym-fri-2025-05-02.md b/demo-vault-v2/event-gym-fri-2025-05-02.md deleted file mode 100644 index 808d0420..00000000 --- a/demo-vault-v2/event-gym-fri-2025-05-02.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Gym — 2025-05-02"] -Is A: Event -Date: "2025-05-02" -Belongs to: "[[2025-05]]" -Tags: ["Health"] ---- -# Gym — 2025-05-02 -Strength session. Bench press, rows, overhead press. Core work. - -## Notes -- Bench press 5x5 at 80kg — high volume, all reps smooth -- Barbell rows 4x8 at 67.5kg, good back engagement -- Standing OHP 3x6 at 50kg, steady overhead pressing -- Cable crunches 3x15, Pallof press 3x12 each side diff --git a/demo-vault-v2/event-gym-fri-2025-05-16.md b/demo-vault-v2/event-gym-fri-2025-05-16.md deleted file mode 100644 index 8df42a26..00000000 --- a/demo-vault-v2/event-gym-fri-2025-05-16.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Gym — 2025-05-16"] -Is A: Event -Date: "2025-05-16" -Belongs to: "[[2025-05]]" -Tags: ["Health"] ---- -# Gym — 2025-05-16 -Strength session. Bench press, rows, overhead press. Core work. - -## Notes -- Bench press 3x3 at 85kg — Bench PR: 85kg x 3, approaching bodyweight bench -- Dumbbell rows 4x8 at 37.5kg each, strong pulling day -- Push press 3x3 at 55kg, comfortable overhead -- Treating the bench progress like compound interest — small jumps add up diff --git a/demo-vault-v2/event-gym-fri-2025-05-30.md b/demo-vault-v2/event-gym-fri-2025-05-30.md deleted file mode 100644 index f383a3ef..00000000 --- a/demo-vault-v2/event-gym-fri-2025-05-30.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Gym — 2025-05-30"] -Is A: Event -Date: "2025-05-30" -Belongs to: "[[2025-05]]" -Tags: ["Health"] ---- -# Gym — 2025-05-30 -Strength session. Bench press, rows, overhead press. Core work. - -## Notes -- Bench press 4x5 at 82.5kg — volume at near-max, challenging -- Cable rows 4x10 at 67.5kg, upper back pumped -- OHP 3x5 at 52.5kg, slow and strict -- Finished with lateral raises 4x12, tricep pushdowns 3x15 diff --git a/demo-vault-v2/event-gym-fri-2025-06-13.md b/demo-vault-v2/event-gym-fri-2025-06-13.md deleted file mode 100644 index f15a9212..00000000 --- a/demo-vault-v2/event-gym-fri-2025-06-13.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Gym — 2025-06-13"] -Is A: Event -Date: "2025-06-13" -Belongs to: "[[2025-06]]" -Tags: ["Health"] ---- -# Gym — 2025-06-13 -Strength session. Bench press, rows, overhead press. Core work. - -## Notes -- Bench press 4x5 at 85kg — Bench PR: 85kg x 5, bodyweight bench for reps -- Barbell rows 4x6 at 75kg, heaviest rows ever -- Standing OHP 3x5 at 52.5kg, consistent pressing -- Best upper body session of the year, summer strength peak diff --git a/demo-vault-v2/event-long-ride-2024-01-06.md b/demo-vault-v2/event-long-ride-2024-01-06.md deleted file mode 100644 index 14c4db81..00000000 --- a/demo-vault-v2/event-long-ride-2024-01-06.md +++ /dev/null @@ -1,21 +0,0 @@ ---- -aliases: ["Long ride — 2024-01-06"] -Is A: Event -Date: "2024-01-06" -Belongs to: "[[2024-01]]" -Related to: ["[[person-luca-rossi]]", "[[person-alessandro-ferrari]]"] -Tags: ["Health", "Sport"] ---- -# Long ride — 2024-01-06 -Long ride with Alessandro. 128km, 1489m elevation. - -## Notes -- Out via the SP45 toward Castellina in Chianti, then looped through Radda and back along the Arbia valley. Classic Chianti rolling terrain. -- Alessandro was in great form after the holidays — pushed hard on the climb up to Radda, averaged 320W for the 8-minute effort. -- Talked a lot about his plans to switch jobs this year. He's been considering a move to a smaller company for more autonomy. -- Espresso stop at the bar in Castellina — the one with the terrace overlooking the valley. Cold but sunny, perfect winter light. -- Legs felt surprisingly good given the holiday break. Kept a solid tempo on the flats, around 30 km/h average. -- New winter gloves worked well — finally no frozen fingers on the descents. The Castelli Perfettos are worth every euro. - -## Follow-up -- [ ] Check cleat alignment — left knee felt slightly off after km 100 diff --git a/demo-vault-v2/event-long-ride-2024-01-13.md b/demo-vault-v2/event-long-ride-2024-01-13.md deleted file mode 100644 index d8e10679..00000000 --- a/demo-vault-v2/event-long-ride-2024-01-13.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -aliases: ["Long ride — 2024-01-13"] -Is A: Event -Date: "2024-01-13" -Belongs to: "[[2024-01]]" -Related to: ["[[person-luca-rossi]]", "[[person-alessandro-ferrari]]"] -Tags: ["Health", "Sport"] ---- -# Long ride — 2024-01-13 -Long ride with Alessandro. 102km, 1341m elevation. - -## Notes -- Headed south toward Montalcino through the Crete Senesi. Stark winter landscape — almost lunar with the bare clay hills. -- Crosswind was brutal on the exposed ridge sections between Asciano and San Giovanni d'Asso. Had to sit up and grind. -- Alessandro got a flat at km 40. Quick tube change but his CO2 cartridge failed, so we used my mini pump — took forever. -- Stopped at a bakery in Buonconvento for espresso and a slice of schiacciata. Best mid-ride fuel. -- Talked about the upcoming Strade Bianche race and whether we should go watch from one of the climbs. -- Moving average 26.3 km/h — headwind segments dragged it down. Normalized power was decent though, around 210W. diff --git a/demo-vault-v2/event-long-ride-2024-01-20.md b/demo-vault-v2/event-long-ride-2024-01-20.md deleted file mode 100644 index a43beb2f..00000000 --- a/demo-vault-v2/event-long-ride-2024-01-20.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -aliases: ["Long ride — 2024-01-20"] -Is A: Event -Date: "2024-01-20" -Belongs to: "[[2024-01]]" -Related to: ["[[person-luca-rossi]]"] -Tags: ["Health", "Sport"] ---- -# Long ride — 2024-01-20 -Solo long ride. 104km, 961m elevation. - -## Notes -- Flat-ish loop through the Val d'Elsa. Out toward Poggibonsi, then north to Certaldo and back via San Gimignano. -- Focused on keeping a steady Z2 heart rate for the whole ride — stayed between 130-145 bpm. Good base-building session. -- Roads were quiet, typical January. Only passed a couple of other riders near San Gimignano. -- Light rain started around km 70 but never got heavy. Roads stayed mostly dry. -- Stopped at a fountain in Certaldo Alta to refill bottles. The medieval town is beautiful even in grey weather. -- Averaged 28.5 km/h on the flat sections. Cadence felt smooth at 90 rpm, finally getting used to the new chainring. diff --git a/demo-vault-v2/event-long-ride-2024-01-27.md b/demo-vault-v2/event-long-ride-2024-01-27.md deleted file mode 100644 index 69c0e7fd..00000000 --- a/demo-vault-v2/event-long-ride-2024-01-27.md +++ /dev/null @@ -1,21 +0,0 @@ ---- -aliases: ["Long ride — 2024-01-27"] -Is A: Event -Date: "2024-01-27" -Belongs to: "[[2024-01]]" -Related to: ["[[person-luca-rossi]]"] -Tags: ["Health", "Sport"] ---- -# Long ride — 2024-01-27 -Solo long ride. 119km, 1540m elevation. - -## Notes -- Big solo effort. Rode out to Volterra via the SS68, then climbed up to the town and continued south toward Massa Marittima before turning back. -- The climb to Volterra from the west side is relentless — 6km at 6% average with some 10% ramps. Legs burned but held a good rhythm. -- Wind picked up in the afternoon, direct headwind for the last 30km home. Had to dig deep in the final hour. -- Fueling was better today — ate a gel every 45 minutes and had rice cakes in the back pocket. No bonk this time. -- Stunning views from the Volterra ridge — you can see all the way to the sea on a clear day like today. -- Total moving time 4h15m. Elevation gain was serious for January — felt like a proper spring epic. - -## Follow-up -- [ ] Order more rice cake ingredients — running low on sushi rice diff --git a/demo-vault-v2/event-long-ride-2024-02-03.md b/demo-vault-v2/event-long-ride-2024-02-03.md deleted file mode 100644 index 4666ed37..00000000 --- a/demo-vault-v2/event-long-ride-2024-02-03.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -aliases: ["Long ride — 2024-02-03"] -Is A: Event -Date: "2024-02-03" -Belongs to: "[[2024-02]]" -Related to: ["[[person-luca-rossi]]", "[[person-alessandro-ferrari]]"] -Tags: ["Health", "Sport"] ---- -# Long ride — 2024-02-03 -Long ride with Alessandro. 94km, 1392m elevation. - -## Notes -- Shorter but punchy route through the Chianti hills — lots of short steep climbs between Gaiole and Castelnuovo Berardenga. -- Alessandro wanted to do threshold intervals on the climbs. Did 4x5min efforts on the steeper pitches, hovering around 280-300W. -- Some gravel sections near Brolio castle — the Strade Bianche terrain. Rear tire slipped a few times on the loose stuff. -- Coffee stop at Bar Gallo in Gaiole. They do a great cappuccino and the owner always wants to talk about pro cycling. -- Talked about signing up for a granfondo together in spring — maybe the Eroica or the Nova Eroica in March. -- Cold start at 4°C but warmed up to 11°C by midday. Arm warmers came off after the first hour. diff --git a/demo-vault-v2/event-long-ride-2024-02-10.md b/demo-vault-v2/event-long-ride-2024-02-10.md deleted file mode 100644 index d16e15bb..00000000 --- a/demo-vault-v2/event-long-ride-2024-02-10.md +++ /dev/null @@ -1,21 +0,0 @@ ---- -aliases: ["Long ride — 2024-02-10"] -Is A: Event -Date: "2024-02-10" -Belongs to: "[[2024-02]]" -Related to: ["[[person-luca-rossi]]"] -Tags: ["Health", "Sport"] ---- -# Long ride — 2024-02-10 -Solo long ride. 86km, 1578m elevation. - -## Notes -- Mountain day — rode up Monte Amiata from the Castiglione d'Orcia side. The big climb is 18km, gradual at first then kicks up to 8-9% in the forest sections. -- Snow on the upper slopes from last week but the road was clear and dry. Temperature dropped to 2°C near the summit. -- Legs felt heavy in the first 30 minutes — might be residual fatigue from Wednesday's intervals. Loosened up after the warm-up. -- Stopped at the rifugio near the top for a hot chocolate. Proper winter riding fuel. -- Descent was technical — hairpins through the chestnut forest, gravel on some corners. Took it easy with cold tires. -- Only 86km but almost 1600m of climbing makes this one of the harder routes in the area. HR averaged 152 bpm. - -## Follow-up -- [ ] Check brake pads — rear felt soft on the long descent diff --git a/demo-vault-v2/event-long-ride-2024-02-17.md b/demo-vault-v2/event-long-ride-2024-02-17.md deleted file mode 100644 index e2163fa7..00000000 --- a/demo-vault-v2/event-long-ride-2024-02-17.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -aliases: ["Long ride — 2024-02-17"] -Is A: Event -Date: "2024-02-17" -Belongs to: "[[2024-02]]" -Related to: ["[[person-luca-rossi]]", "[[person-alessandro-ferrari]]"] -Tags: ["Health", "Sport"] ---- -# Long ride — 2024-02-17 -Long ride with Alessandro. 103km, 1527m elevation. - -## Notes -- Took the classic Chianti loop: Siena to Greve via Panzano, then back through Castellina. Rolling terrain with a couple of serious climbs. -- Alessandro and I took turns pulling on the flats. Good drafting practice — sat at 38 km/h on the straight section before Panzano. -- The climb to Panzano from the south is always a wake-up call — 4km at 7% average. Pushed 290W, felt strong. -- Stopped at Dario Cecchini's butcher shop in Panzano for a quick panino. The porchetta one is legendary. -- Talked about our training plans for spring. Alessandro is thinking about focusing on climbing power, wants to do some structured blocks. -- Beautiful day for February — 14°C, sunny, barely any wind. Spring is coming early this year. diff --git a/demo-vault-v2/event-long-ride-2024-02-24.md b/demo-vault-v2/event-long-ride-2024-02-24.md deleted file mode 100644 index 9021d666..00000000 --- a/demo-vault-v2/event-long-ride-2024-02-24.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -aliases: ["Long ride — 2024-02-24"] -Is A: Event -Date: "2024-02-24" -Belongs to: "[[2024-02]]" -Related to: ["[[person-luca-rossi]]"] -Tags: ["Health", "Sport"] ---- -# Long ride — 2024-02-24 -Solo long ride. 123km, 946m elevation. - -## Notes -- Long flat loop through the Val d'Orcia and out toward Montepulciano. Low elevation gain but plenty of distance to build endurance. -- Focused on keeping power steady at 180-190W the whole ride. Z2 endurance work, trying to keep it honest. -- Roads were in great shape after recent maintenance. Smooth tarmac on the SP146 toward Pienza. -- Stopped in Pienza for a quick espresso and a piece of pecorino from the deli. Best cheese stop on any ride route. -- Tailwind on the way out, headwind on the return — as always. Last 30km was a proper grind at 24 km/h. -- Moving time 4h32m, average speed 27.1 km/h. These flat rides are great for the aerobic base even if they're mentally tough. diff --git a/demo-vault-v2/event-long-ride-2024-03-02.md b/demo-vault-v2/event-long-ride-2024-03-02.md deleted file mode 100644 index e16515ce..00000000 --- a/demo-vault-v2/event-long-ride-2024-03-02.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -aliases: ["Long ride — 2024-03-02"] -Is A: Event -Date: "2024-03-02" -Belongs to: "[[2024-03]]" -Related to: ["[[person-luca-rossi]]", "[[person-alessandro-ferrari]]"] -Tags: ["Health", "Sport"] ---- -# Long ride — 2024-03-02 -Long ride with Alessandro. 104km, 1352m elevation. - -## Notes -- Strade Bianche recon ride — tried to cover as many of the white gravel sectors as possible. Hit sectors 6, 7, and 8 south of Siena. -- The gravel was in rough condition after the winter rains. Loose stones and some deep ruts. My 28mm tires were at the limit. -- Alessandro had a great idea — we'll go watch the pro race next week from the Santa Maria climb in Siena. -- Stopped at a small trattoria in Radi for pasta and water. Proper refueling for the second half. -- Wind was calm, overcast but dry. Perfect conditions for gravel — not too hot, good grip on the packed sections. -- Avg power 195W, plenty of spikes on the gravel where you have to stamp to keep momentum. Good for building punch. diff --git a/demo-vault-v2/event-long-ride-2024-03-09.md b/demo-vault-v2/event-long-ride-2024-03-09.md deleted file mode 100644 index 50b6de52..00000000 --- a/demo-vault-v2/event-long-ride-2024-03-09.md +++ /dev/null @@ -1,21 +0,0 @@ ---- -aliases: ["Long ride — 2024-03-09"] -Is A: Event -Date: "2024-03-09" -Belongs to: "[[2024-03]]" -Related to: ["[[person-luca-rossi]]"] -Tags: ["Health", "Sport"] ---- -# Long ride — 2024-03-09 -Solo long ride. 115km, 1249m elevation. - -## Notes -- Out toward Colle Val d'Elsa and then a big loop through the hills south of Poggibonsi. Some roads I'd never explored before. -- Found a beautiful quiet road between Staggia and Monteriggioni — smooth tarmac, no cars, cypress trees lining the route. -- Legs felt great after three weeks of consistent base miles. Power at threshold feels like it's coming up — did a spontaneous 10-min effort at 270W on a climb and it felt sustainable. -- Stopped at a bar in Monteriggioni, right by the medieval walls. Tourist spot but the view from the café terrace is worth it. -- Noticed the chain is starting to stretch — the power meter showed some unusual cadence readings on the steep sections. -- 115km in 4h05m moving time. Good pace for a solo ride with this much climbing. - -## Follow-up -- [ ] Measure chain wear and replace if over 0.5% diff --git a/demo-vault-v2/event-long-ride-2024-03-16.md b/demo-vault-v2/event-long-ride-2024-03-16.md deleted file mode 100644 index 8a6622a9..00000000 --- a/demo-vault-v2/event-long-ride-2024-03-16.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -aliases: ["Long ride — 2024-03-16"] -Is A: Event -Date: "2024-03-16" -Belongs to: "[[2024-03]]" -Related to: ["[[person-luca-rossi]]"] -Tags: ["Health", "Sport"] ---- -# Long ride — 2024-03-16 -Solo long ride. 94km, 865m elevation. - -## Notes -- Recovery ride disguised as a long ride. Kept it easy through the flat sections around Monteroni d'Arbia and Buonconvento. -- Legs were still sore from Thursday's hard session. Stayed in Z1-Z2 the whole time, never above 150 bpm. -- Spring is definitely here — wildflowers along the roadside, almond trees in bloom. Rode in just a base layer for the first time this year. -- Roads were busier than usual with weekend drivers heading to the Crete Senesi for lunch. Had to be extra careful on the narrow sections. -- Stopped at a bar in Buonconvento for a cornetto and caffè. Sat in the sun for 15 minutes just enjoying the warmth. -- 94km felt long for the legs I had today but the low intensity was what I needed. Sometimes the best rides are the easy ones. diff --git a/demo-vault-v2/event-long-ride-2024-03-23.md b/demo-vault-v2/event-long-ride-2024-03-23.md deleted file mode 100644 index 29f52e2e..00000000 --- a/demo-vault-v2/event-long-ride-2024-03-23.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -aliases: ["Long ride — 2024-03-23"] -Is A: Event -Date: "2024-03-23" -Belongs to: "[[2024-03]]" -Related to: ["[[person-luca-rossi]]"] -Tags: ["Health", "Sport"] ---- -# Long ride — 2024-03-23 -Solo long ride. 84km, 1232m elevation. - -## Notes -- Decided to explore the roads east of Siena toward Rapolano Terme. Lots of short punchy climbs, some with 12-15% gradients. -- Found an amazing descent on a tiny road between Asciano and Trequanda — fast sweeping curves through olive groves. Need to remember this one. -- Thermal baths visible from the road near Rapolano — tempting to stop but didn't want to lose momentum. -- Tried a new energy bar brand (Namedsport) — too sweet, stuck to my teeth. Going back to homemade rice cakes. -- Spring conditions: 17°C, light breeze, high clouds. Perfect riding weather. Could smell the freshly turned soil from the farms. -- Despite only 84km, the climbing made it feel much harder. Average gradient on the climbs was steep enough to need the 34x32. diff --git a/demo-vault-v2/event-long-ride-2024-03-30.md b/demo-vault-v2/event-long-ride-2024-03-30.md deleted file mode 100644 index 1af06fcb..00000000 --- a/demo-vault-v2/event-long-ride-2024-03-30.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -aliases: ["Long ride — 2024-03-30"] -Is A: Event -Date: "2024-03-30" -Belongs to: "[[2024-03]]" -Related to: ["[[person-luca-rossi]]", "[[person-alessandro-ferrari]]"] -Tags: ["Health", "Sport"] ---- -# Long ride — 2024-03-30 -Long ride with Alessandro. 121km, 1822m elevation. - -## Notes -- Epic spring ride. Headed south to Montalcino then climbed up to the fortress. The view from the top was crystal clear — you could see Monte Amiata with its last patches of snow. -- Alessandro was flying today — dropped me on the climb to Montalcino. Had to chase for 2km to close the gap. -- Long descent from Montalcino to Sant'Antimo abbey, then climbed back up via Castelnuovo dell'Abate. Beautiful rolling terrain. -- Lunch stop at an osteria in Sant'Angelo in Colle — split a plate of pici cacio e pepe. Proper mid-ride nutrition. -- Talked about summer plans — Alessandro might join a cycling camp in the Dolomites in July. Trying to convince me to come along. -- 121km with 1822m of climbing — biggest day of the year so far. Moved to summer schedule: out at 8am, back by 1pm. -- Strava kudos immediately from the local cycling group. This route is a classic. - -## Follow-up -- [ ] Look into Dolomites cycling camp dates and costs for July diff --git a/demo-vault-v2/event-long-ride-2024-04-06.md b/demo-vault-v2/event-long-ride-2024-04-06.md deleted file mode 100644 index 529e395e..00000000 --- a/demo-vault-v2/event-long-ride-2024-04-06.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -aliases: ["Long ride — 2024-04-06"] -Is A: Event -Date: "2024-04-06" -Belongs to: "[[2024-04]]" -Related to: ["[[person-luca-rossi]]", "[[person-alessandro-ferrari]]"] -Tags: ["Health", "Sport"] ---- -# Long ride — 2024-04-06 -Long ride with Alessandro. 88km, 1305m elevation. - -## Notes -- Shorter ride today — both had afternoon plans. Packed the climbing into a loop through the Chianti hills near Vagliagli and Fonterutoli. -- Pushed hard on every climb, treating it like an informal hill repeat session. 6 climbs, all between 3-6 minutes. Fun and painful. -- Alessandro brought his new Wahoo Kickr and was comparing power numbers — his FTP has gone up 15W since January. -- Quick coffee stop at the bar in Fonterutoli, right on the main road. Simple but good espresso. -- Talked about gear ratios. Alessandro is considering going 1x for his gravel bike but isn't sure about the range for road riding. -- Sunny and warm, 19°C. Arm warmers stayed in the pocket the whole ride. Bidon was empty by km 70 — need to carry more water now. diff --git a/demo-vault-v2/event-long-ride-2024-04-13.md b/demo-vault-v2/event-long-ride-2024-04-13.md deleted file mode 100644 index 0eab562f..00000000 --- a/demo-vault-v2/event-long-ride-2024-04-13.md +++ /dev/null @@ -1,21 +0,0 @@ ---- -aliases: ["Long ride — 2024-04-13"] -Is A: Event -Date: "2024-04-13" -Belongs to: "[[2024-04]]" -Related to: ["[[person-luca-rossi]]"] -Tags: ["Health", "Sport"] ---- -# Long ride — 2024-04-13 -Solo long ride. 107km, 1995m elevation. - -## Notes -- Massive climbing day. Rode the "3 passes" route south of Siena: Trequanda climb, Monte Oliveto Maggiore, and then the long drag up to San Giovanni d'Asso from the valley. -- Nearly 2000m of elevation in 107km — that's an average gradient that keeps your legs honest the whole ride. Very little flat. -- The road through the Monte Oliveto cypress avenue is one of the most beautiful in Tuscany. Took a moment to appreciate it mid-effort. -- Bonked slightly at km 85 — should have eaten more in the first two hours. Had to soft-pedal the last climb to recover. -- Stopped at the abbey of Monte Oliveto for water. The monks were doing their afternoon prayers, completely surreal setting. -- Total moving time 4h28m. Power faded in the last hour — went from 220W average to barely 180W. Need to work on fueling. - -## Follow-up -- [ ] Try eating 80-90g carbs per hour instead of 60g on rides over 3 hours diff --git a/demo-vault-v2/event-long-ride-2024-04-20.md b/demo-vault-v2/event-long-ride-2024-04-20.md deleted file mode 100644 index e496ec95..00000000 --- a/demo-vault-v2/event-long-ride-2024-04-20.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -aliases: ["Long ride — 2024-04-20"] -Is A: Event -Date: "2024-04-20" -Belongs to: "[[2024-04]]" -Related to: ["[[person-luca-rossi]]"] -Tags: ["Health", "Sport"] ---- -# Long ride — 2024-04-20 -Solo long ride. 88km, 1843m elevation. - -## Notes -- Another big climbing day. Focused on the hills east of Siena — Chiusure, Serre di Rapolano, and the steep ramp up to Castelmuzio. -- Castelmuzio climb is a beast — only 2.5km but averaging 9% with pitches over 14%. Did it seated in the 34x32, grinding at 55 rpm. -- Weather was warm and hazy, 22°C. First ride in summer kit — short sleeves, no warmers. Felt fast. -- Saw a group of about 15 riders on a guided cycling tour near Trequanda. They had a support van and matching jerseys — looked like they were having a great time. -- Experimented with higher carb intake — 80g/hour using a mix of gels and drink mix. Felt noticeably better in the last hour compared to last week. -- Only 88km but the elevation makes it equivalent to a much longer ride. Suffer score on Strava was 187. diff --git a/demo-vault-v2/event-long-ride-2024-04-27.md b/demo-vault-v2/event-long-ride-2024-04-27.md deleted file mode 100644 index 8350a517..00000000 --- a/demo-vault-v2/event-long-ride-2024-04-27.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -aliases: ["Long ride — 2024-04-27"] -Is A: Event -Date: "2024-04-27" -Belongs to: "[[2024-04]]" -Related to: ["[[person-luca-rossi]]"] -Tags: ["Health", "Sport"] ---- -# Long ride — 2024-04-27 -Solo long ride. 89km, 1127m elevation. - -## Notes -- Mixed terrain ride — half road, half white roads through the Crete Senesi. Ran 30mm tires at 4.5 bar for the gravel sections. -- The gravel sector near the farm at Le Crete was in perfect condition — packed and fast, like riding on hardpack. Best surface I've ridden on. -- Picked up a thorn in the rear tire at km 52. Sealant sealed it within a minute — tubeless setup paying for itself. -- Quiet morning — left at 7am and had the roads entirely to myself until about 10am. Peaceful riding. -- Spotted a fox crossing the gravel road near Asciano. It stopped and stared for a few seconds before disappearing into the wheat field. -- Average speed 24.8 km/h — slower because of the gravel sections but the variety makes the ride more interesting than pure road. diff --git a/demo-vault-v2/event-long-ride-2024-05-04.md b/demo-vault-v2/event-long-ride-2024-05-04.md deleted file mode 100644 index 59e73ba1..00000000 --- a/demo-vault-v2/event-long-ride-2024-05-04.md +++ /dev/null @@ -1,21 +0,0 @@ ---- -aliases: ["Long ride — 2024-05-04"] -Is A: Event -Date: "2024-05-04" -Belongs to: "[[2024-05]]" -Related to: ["[[person-luca-rossi]]"] -Tags: ["Health", "Sport"] ---- -# Long ride — 2024-05-04 -Solo long ride. 84km, 1588m elevation. - -## Notes -- Hill repeat day on the climb to Monteriggioni from the south side. Did the 4km climb three times with descents in between. -- First rep felt smooth — 285W average, 12:30 elapsed. Second was similar. Third rep the legs were screaming — dropped to 260W. -- The view of Monteriggioni's towers from below is iconic. Dante mentioned this place in the Inferno and you can see why. -- Hot day for May — 26°C. Went through two bidons in 3 hours. Need to start carrying a third or planning water stops. -- Finished with a cool-down loop through the flat valley near Colle Val d'Elsa. Spun easy at 85 rpm to flush the legs. -- Good structured session embedded in a long ride. This format works well — ride to the climb, do repeats, ride home. - -## Follow-up -- [ ] Buy a third bidon cage or larger bottles for summer diff --git a/demo-vault-v2/event-long-ride-2024-05-11.md b/demo-vault-v2/event-long-ride-2024-05-11.md deleted file mode 100644 index f739b5e0..00000000 --- a/demo-vault-v2/event-long-ride-2024-05-11.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -aliases: ["Long ride — 2024-05-11"] -Is A: Event -Date: "2024-05-11" -Belongs to: "[[2024-05]]" -Related to: ["[[person-luca-rossi]]"] -Tags: ["Health", "Sport"] ---- -# Long ride — 2024-05-11 -Solo long ride. 115km, 823m elevation. - -## Notes -- Long flat endurance ride toward the coast. Rode out to Massa Marittima via the SP73, mostly rolling with one real climb. -- Flat rides are great for working on aero position. Spent 40 minutes on the drops practicing a low, narrow arm position. -- Roads were smooth and fast — averaged 30.2 km/h, best average speed on a long ride in months. -- Stopped at a bar in Massa Marittima in the main piazza. The cathedral there is stunning and there's almost no tourists in May. -- Legs felt light and springy — the reduced climbing volume this week was a good decision. Power was consistent start to finish. -- Saw several other riders on the SP73, including a fast group doing paceline work. Almost jumped in but decided to stick to the plan. diff --git a/demo-vault-v2/event-long-ride-2024-05-18.md b/demo-vault-v2/event-long-ride-2024-05-18.md deleted file mode 100644 index 8e888b26..00000000 --- a/demo-vault-v2/event-long-ride-2024-05-18.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -aliases: ["Long ride — 2024-05-18"] -Is A: Event -Date: "2024-05-18" -Belongs to: "[[2024-05]]" -Related to: ["[[person-luca-rossi]]", "[[person-alessandro-ferrari]]"] -Tags: ["Health", "Sport"] ---- -# Long ride — 2024-05-18 -Long ride with Alessandro. 114km, 1346m elevation. - -## Notes -- Classic Chianti loop but extended it further north through Greve and almost to the outskirts of Florence. -- Alessandro is in peak form — was chatting comfortably on every climb while I was gasping. Need to close that gap. -- Beautiful day, 23°C, light southerly breeze. The vineyards are lush green and the roses at the end of each row are blooming. -- Long coffee and pastry stop in Greve at the café on the main piazza. Sat for 20 minutes watching the Saturday market. -- Talked about whether to do the Nove Colli in Cesenatico next year. 200km and 3800m of climbing — would need serious preparation. -- Paced the last 30km well. Kept the power at 190W and the conversation flowing. Arrived home feeling tired but not destroyed. diff --git a/demo-vault-v2/event-long-ride-2024-05-25.md b/demo-vault-v2/event-long-ride-2024-05-25.md deleted file mode 100644 index 26a621c6..00000000 --- a/demo-vault-v2/event-long-ride-2024-05-25.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -aliases: ["Long ride — 2024-05-25"] -Is A: Event -Date: "2024-05-25" -Belongs to: "[[2024-05]]" -Related to: ["[[person-luca-rossi]]"] -Tags: ["Health", "Sport"] ---- -# Long ride — 2024-05-25 -Solo long ride. 109km, 806m elevation. - -## Notes -- Flat endurance loop north through the Val d'Elsa. Out to Poggibonsi, then Certaldo, Castelfiorentino, and back via the SP429. -- Practiced fueling at 90g carbs per hour — 2 bottles of mix plus a gel every 40 minutes. Stomach handled it fine. -- Roads were busy with Saturday traffic. The SP429 has no shoulder in places — had a couple of close passes from trucks. -- Stopped at a gelateria in Certaldo for a scoop of pistachio. Best mid-ride treat when it's 27°C. -- Legs felt steady the whole ride. Power stayed in a narrow band, 175-195W. This is what proper endurance pace should feel like. -- 109km in 3h42m moving time. Fastest long ride of the season so far — the flat terrain helps but fitness is clearly improving. diff --git a/demo-vault-v2/event-long-ride-2024-06-01.md b/demo-vault-v2/event-long-ride-2024-06-01.md deleted file mode 100644 index 1a133ce2..00000000 --- a/demo-vault-v2/event-long-ride-2024-06-01.md +++ /dev/null @@ -1,21 +0,0 @@ ---- -aliases: ["Long ride — 2024-06-01"] -Is A: Event -Date: "2024-06-01" -Belongs to: "[[2024-06]]" -Related to: ["[[person-luca-rossi]]"] -Tags: ["Health", "Sport"] ---- -# Long ride — 2024-06-01 -Solo long ride. 96km, 1825m elevation. - -## Notes -- Big climbing day in the Chianti hills. Focused on the hardest climbs: Badia a Coltibuono from the east, the ramp to Vertine, and the steep kick to Castagnoli. -- Badia a Coltibuono is relentless — 7km of constant 6-7% through dense forest. Pushed 275W and it felt honest. -- Very hot already at 9am — 28°C and humid. Went through three bottles. Had to stop at a fountain halfway up the second climb. -- The descent from Castagnoli toward Gaiole is technical — tight hairpins through vineyard walls. Great practice for bike handling. -- Saw a fellow rider fixing a broken spoke on the roadside near Vertine. Stopped to help — he was from Milan, doing a cycling holiday. -- Nearly 1900m of climbing in under 100km. This is the steepest route I know in the area. Moving time 3h55m, average power 215W. - -## Follow-up -- [ ] Check tire pressure — felt sluggish on the descents, might be running too low diff --git a/demo-vault-v2/event-long-ride-2024-06-08.md b/demo-vault-v2/event-long-ride-2024-06-08.md deleted file mode 100644 index ba50a30f..00000000 --- a/demo-vault-v2/event-long-ride-2024-06-08.md +++ /dev/null @@ -1,19 +0,0 @@ ---- -aliases: ["Long ride — 2024-06-08"] -Is A: Event -Date: "2024-06-08" -Belongs to: "[[2024-06]]" -Related to: ["[[person-luca-rossi]]", "[[person-alessandro-ferrari]]"] -Tags: ["Health", "Sport"] ---- -# Long ride — 2024-06-08 -Long ride with Alessandro. 120km, 1411m elevation. - -## Notes -- Started early at 6:30am to beat the heat. Good decision — was already 30°C by noon when we finished. -- Rode out toward Montepulciano through the Val d'Orcia. The golden wheat fields and rolling hills are Tuscany at its most iconic. -- Alessandro suggested a sprint for the Montepulciano town sign. He won by half a wheel — I ran out of gear in the final meters. -- Espresso stop at Caffè Poliziano in Montepulciano, one of the classic old cafés. Terrace view over the entire Val di Chiana. -- Talked about his daughter starting school next year and how weekday riding might get harder to schedule. -- Pacing was perfect — held 200W average for 4 hours. Both finished strong, no fade in the last 30km despite the heat. -- Hydration was key: 4 bottles total, plus electrolyte tabs. No cramping despite the temperature. diff --git a/demo-vault-v2/event-long-ride-2024-06-15.md b/demo-vault-v2/event-long-ride-2024-06-15.md deleted file mode 100644 index a38b8d43..00000000 --- a/demo-vault-v2/event-long-ride-2024-06-15.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -aliases: ["Long ride — 2024-06-15"] -Is A: Event -Date: "2024-06-15" -Belongs to: "[[2024-06]]" -Related to: ["[[person-luca-rossi]]"] -Tags: ["Health", "Sport"] ---- -# Long ride — 2024-06-15 -Solo long ride. 92km, 1113m elevation. - -## Notes -- Mellow solo ride through the Crete Senesi. Left at dawn, 5:45am — the light on the clay hills was extraordinary. -- Took the quiet roads through San Quirico d'Orcia and Bagno Vignoni. Almost no cars at that hour. -- Focused on staying in Z2 the entire ride. Heart rate locked between 135-148 bpm. Pure aerobic work. -- The thermal spring at Bagno Vignoni was steaming in the cool morning air. Tempting but kept pedaling. -- Nutrition plan worked well — ate every 30 minutes, alternating between gels and rice cakes. Energy was stable throughout. -- Back home by 9:30am with the whole day ahead. Early summer morning rides are the best way to do long distance. diff --git a/demo-vault-v2/event-long-ride-2024-06-22.md b/demo-vault-v2/event-long-ride-2024-06-22.md deleted file mode 100644 index 9f1c7b5b..00000000 --- a/demo-vault-v2/event-long-ride-2024-06-22.md +++ /dev/null @@ -1,21 +0,0 @@ ---- -aliases: ["Long ride — 2024-06-22"] -Is A: Event -Date: "2024-06-22" -Belongs to: "[[2024-06]]" -Related to: ["[[person-luca-rossi]]"] -Tags: ["Health", "Sport"] ---- -# Long ride — 2024-06-22 -Solo long ride. 118km, 1463m elevation. - -## Notes -- Long route going west toward Volterra and then looping back through Colle Val d'Elsa. The western hills are less traveled — felt like exploration. -- The climb from the Cecina valley up to Volterra is never easy. 8km of steady climbing in full sun. Drained a whole bottle on this one climb. -- Stopped in Volterra at the Roman amphitheater viewpoint. Even with tourists around, the setting is impressive. -- Tried a new saddle position — 3mm further back. Felt better on the long climbs, more power from the glutes. Will keep it. -- Some rough road surface on the descent toward San Gimignano. Potholes and patches — had to stay alert. -- 118km at this intensity is getting more comfortable. Normalized power 198W, and I wasn't digging deep. Fitness is in a good place. - -## Follow-up -- [ ] Confirm saddle position with a bike fit session if the improvement holds over a few more rides diff --git a/demo-vault-v2/event-long-ride-2024-06-29.md b/demo-vault-v2/event-long-ride-2024-06-29.md deleted file mode 100644 index 3a1645a7..00000000 --- a/demo-vault-v2/event-long-ride-2024-06-29.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -aliases: ["Long ride — 2024-06-29"] -Is A: Event -Date: "2024-06-29" -Belongs to: "[[2024-06]]" -Related to: ["[[person-luca-rossi]]"] -Tags: ["Health", "Sport"] ---- -# Long ride — 2024-06-29 -Solo long ride. 99km, 1290m elevation. - -## Notes -- Mid-summer heat ride. Left at 5:30am and it was already 22°C. By 9am it was 34°C. Had to cut the planned route short. -- Rode south through Monteroni then east to Rapolano. The road along the ridge between the two valleys has amazing views in the morning light. -- Drank 4 liters of fluid in under 4 hours. Pre-loaded with electrolytes and it made a real difference — no cramping despite the heat. -- Found shade at a bar in Rapolano Terme and sat for 15 minutes to cool down. The old men at the bar thought I was crazy riding in this heat. -- Legs actually felt good — summer heat seems to help with muscle flexibility. Power numbers were normal despite the temperature. -- Need to plan routes with more water stops during the hot months. Running out of water on an exposed ridge is not fun. diff --git a/demo-vault-v2/event-long-ride-2024-07-06.md b/demo-vault-v2/event-long-ride-2024-07-06.md deleted file mode 100644 index 0f9a6997..00000000 --- a/demo-vault-v2/event-long-ride-2024-07-06.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -aliases: ["Long ride — 2024-07-06"] -Is A: Event -Date: "2024-07-06" -Belongs to: "[[2024-07]]" -Related to: ["[[person-luca-rossi]]"] -Tags: ["Health", "Sport"] ---- -# Long ride — 2024-07-06 -Solo long ride. 85km, 1795m elevation. - -## Notes -- Mountain ride to escape the valley heat. Headed to Monte Amiata via the north side from Castiglione d'Orcia. The forest roads are 10°C cooler. -- The main climb is 22km with a few false flats. Stayed in Z3, around 240W average. Cadence was low on the steeper sections — 65 rpm. -- Summit temperature was 19°C while the valley was 36°C. Like riding into a different season. -- Long, fast descent on the east side through Abbadia San Salvatore. Fresh tarmac made it a joy — reached 68 km/h on the straight section. -- Stopped at a rifugio for a panino with prosciutto and a Coca-Cola. Nothing tastes better after a big climb. -- Only 85km but nearly 1800m of climbing. Moving time 3h40m. This route is all about the vertical, not the distance. diff --git a/demo-vault-v2/event-long-ride-2024-07-13.md b/demo-vault-v2/event-long-ride-2024-07-13.md deleted file mode 100644 index afe1e847..00000000 --- a/demo-vault-v2/event-long-ride-2024-07-13.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -aliases: ["Long ride — 2024-07-13"] -Is A: Event -Date: "2024-07-13" -Belongs to: "[[2024-07]]" -Related to: ["[[person-luca-rossi]]"] -Tags: ["Health", "Sport"] ---- -# Long ride — 2024-07-13 -Solo long ride. 114km, 1057m elevation. - -## Notes -- Long rolling ride through the Val d'Orcia toward Pienza and Montepulciano. Moderate climbing, focused on steady effort. -- Watched the Tour de France stage on the phone during the espresso stop in Pienza. Great to follow the racing while doing my own ride. -- The SP146 between San Quirico and Pienza is one of the most photographed roads in Tuscany — the cypress avenue. Never gets old. -- Tried to ride the whole thing as a tempo effort. Averaged 205W for 3h50m — a new endurance PR for sustained power at this duration. -- Heat was manageable — left early and the route has plenty of shade through forests and along rivers. -- Filled bottles at the fountain in San Quirico and again at Pienza. Summer riding requires planning around water sources. diff --git a/demo-vault-v2/event-long-ride-2024-07-20.md b/demo-vault-v2/event-long-ride-2024-07-20.md deleted file mode 100644 index 79181351..00000000 --- a/demo-vault-v2/event-long-ride-2024-07-20.md +++ /dev/null @@ -1,21 +0,0 @@ ---- -aliases: ["Long ride — 2024-07-20"] -Is A: Event -Date: "2024-07-20" -Belongs to: "[[2024-07]]" -Related to: ["[[person-luca-rossi]]", "[[person-alessandro-ferrari]]"] -Tags: ["Health", "Sport"] ---- -# Long ride — 2024-07-20 -Long ride with Alessandro. 113km, 1666m elevation. - -## Notes -- Big ride together — hadn't ridden with Alessandro for three weeks due to schedules. Went through the Chianti hills toward Radda and Gaiole. -- Alessandro came back from the Dolomites cycling camp fired up. He's noticeably stronger on the climbs — FTP reportedly at 310W now. -- Tried to follow his pace on the climb to Radda. Held on for 4 minutes then had to let go. He waited at the top, grinning. -- Stopped at the alimentari in Gaiole for bread, mortadella, and water. Sat under a tree for a proper lunch break. -- Talked about the Dolomites camp — he did the Stelvio, Passo Gavia, and Mortirolo in five days. Sounds incredible. -- Heat was intense but manageable with early start. Average HR was higher than usual — 158 bpm — due to the temperature and climbing effort. - -## Follow-up -- [ ] Look into booking the same Dolomites camp for next summer diff --git a/demo-vault-v2/event-long-ride-2024-07-27.md b/demo-vault-v2/event-long-ride-2024-07-27.md deleted file mode 100644 index 64841030..00000000 --- a/demo-vault-v2/event-long-ride-2024-07-27.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -aliases: ["Long ride — 2024-07-27"] -Is A: Event -Date: "2024-07-27" -Belongs to: "[[2024-07]]" -Related to: ["[[person-luca-rossi]]"] -Tags: ["Health", "Sport"] ---- -# Long ride — 2024-07-27 -Solo long ride. 128km, 1211m elevation. - -## Notes -- Longest ride of the month. Went south along the Via Cassia toward Radicofani, then looped back through Sarteano and Chiusi. -- The approach to Radicofani from the north is dramatic — the fortress on top of the hill is visible for 20km. Iconic Tuscan silhouette. -- Kept it steady at endurance pace. 128km in 4h35m moving time. Consistent pacing is finally becoming natural. -- Stopped twice for water — once at a bar in San Quirico, once at a fountain outside Sarteano. Essential in July heat. -- The road from Sarteano to Chiusi drops through beautiful oak forest. Shade and a gentle descent — perfect for recovering before the last push home. -- Ate 6 rice cakes and 3 gels over the ride, plus 2 bottles of electrolyte mix. Fueling strategy is dialed in for rides of this length. diff --git a/demo-vault-v2/event-long-ride-2024-08-03.md b/demo-vault-v2/event-long-ride-2024-08-03.md deleted file mode 100644 index 9bd894d8..00000000 --- a/demo-vault-v2/event-long-ride-2024-08-03.md +++ /dev/null @@ -1,21 +0,0 @@ ---- -aliases: ["Long ride — 2024-08-03"] -Is A: Event -Date: "2024-08-03" -Belongs to: "[[2024-08]]" -Related to: ["[[person-luca-rossi]]"] -Tags: ["Health", "Sport"] ---- -# Long ride — 2024-08-03 -Solo long ride. 113km, 1724m elevation. - -## Notes -- Big August adventure. Rode south to Montalcino then continued to Monte Amiata for the long climb. Two major ascents in one ride. -- Left at 5:15am to beat the worst of the heat. First 50km in the pre-dawn light were magical — the Val d'Orcia slowly emerging from the mist. -- Montalcino climb went well — legs fresh, power steady at 260W. Stopped briefly at the top for a quick refill. -- The climb to Amiata from the south side is longer but more gradual. 15km at 5% average. Settled into a rhythm and let the mind wander. -- Ate steadily throughout — 5 gels, 4 rice cakes, 3 bottles of electrolyte mix. No energy dip at all. The 90g/hour strategy is working. -- Descended via the west side and looped back through Castiglione d'Orcia. Total moving time 4h48m. This is close to my limit for a single ride. - -## Follow-up -- [ ] Check chain and cassette wear after this big block of climbing miles diff --git a/demo-vault-v2/event-long-ride-2024-08-10.md b/demo-vault-v2/event-long-ride-2024-08-10.md deleted file mode 100644 index 38462234..00000000 --- a/demo-vault-v2/event-long-ride-2024-08-10.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -aliases: ["Long ride — 2024-08-10"] -Is A: Event -Date: "2024-08-10" -Belongs to: "[[2024-08]]" -Related to: ["[[person-luca-rossi]]", "[[person-alessandro-ferrari]]"] -Tags: ["Health", "Sport"] ---- -# Long ride — 2024-08-10 -Long ride with Alessandro. 81km, 1934m elevation. - -## Notes -- Pure climbing day with Alessandro. Short in distance but massive in elevation — almost 2000m in 81km means it was either going up or going down. -- Did the double ascent of Chianti: up through Vagliagli to Radda, down, then up again via a different road to Volpaia. -- The climb to Volpaia is the steepest in our area — switchbacks through vineyards with 15% ramps. Stood on the pedals for most of it. -- Alessandro cramped on the second climb at km 65. Had to slow down, stretch, and eat extra salt. The heat was brutal — 35°C in the valley. -- Stopped at the tiny bar in Volpaia — the one with 4 tables and a view over the entire Chianti valley. Espresso and sparkling water. -- Talked about pacing strategies for long climbs. We both agreed we go too hard at the bottom and pay for it at the top. diff --git a/demo-vault-v2/event-long-ride-2024-08-17.md b/demo-vault-v2/event-long-ride-2024-08-17.md deleted file mode 100644 index 4a6f65e7..00000000 --- a/demo-vault-v2/event-long-ride-2024-08-17.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -aliases: ["Long ride — 2024-08-17"] -Is A: Event -Date: "2024-08-17" -Belongs to: "[[2024-08]]" -Related to: ["[[person-luca-rossi]]"] -Tags: ["Health", "Sport"] ---- -# Long ride — 2024-08-17 -Solo long ride. 83km, 1268m elevation. - -## Notes -- Ferragosto weekend ride. Roads were empty — everyone at the beach or in the mountains. Had the Chianti hills almost to myself. -- Explored a new road between Lecchi and San Sano. Narrow, steep, and lined with stone walls. Beautiful and quiet. -- Legs felt heavy after a busy week. Kept intensity low, staying below 200W. Some days are about just turning the pedals. -- Heat was relentless — 37°C by 10am. Poured water over my head at every fountain I passed. -- Stopped at a small agriturismo near Castagnoli that was open despite the holiday. Had a granita al limone — pure refreshment. -- Shorter ride but the heat and climbing made it feel like a 130km day. TSS was 185 despite the moderate distance. diff --git a/demo-vault-v2/event-long-ride-2024-08-24.md b/demo-vault-v2/event-long-ride-2024-08-24.md deleted file mode 100644 index 21c1f4c5..00000000 --- a/demo-vault-v2/event-long-ride-2024-08-24.md +++ /dev/null @@ -1,21 +0,0 @@ ---- -aliases: ["Long ride — 2024-08-24"] -Is A: Event -Date: "2024-08-24" -Belongs to: "[[2024-08]]" -Related to: ["[[person-luca-rossi]]"] -Tags: ["Health", "Sport"] ---- -# Long ride — 2024-08-24 -Solo long ride. 84km, 1852m elevation. - -## Notes -- Another high-elevation short ride. Focused on the steep climbs east of Siena — Asciano, then up to Chiusure, then the brutal wall up to the ridge at Mucigliani. -- Mucigliani climb averages 11% for 2.5km. Hit max HR of 182 bpm near the top. Felt like my legs were filled with concrete. -- Beautiful abbey of Monte Oliveto Maggiore halfway through the route. The cypress-lined approach is as stunning from a bike as it is by car. -- New tires (Continental GP5000S) felt noticeably faster on the descents. Lower rolling resistance and better grip on the corners. -- Stopped at the bar in Chiusure — tiny hamlet, maybe 30 residents. The bartender remembered me from last time. -- Power-to-weight is the key on these climbs. Current weight is 72kg, FTP around 280W. That's 3.9 W/kg — want to push above 4.0. - -## Follow-up -- [ ] Schedule a proper FTP test to get accurate numbers for training zones diff --git a/demo-vault-v2/event-long-ride-2024-08-31.md b/demo-vault-v2/event-long-ride-2024-08-31.md deleted file mode 100644 index 96b2a771..00000000 --- a/demo-vault-v2/event-long-ride-2024-08-31.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -aliases: ["Long ride — 2024-08-31"] -Is A: Event -Date: "2024-08-31" -Belongs to: "[[2024-08]]" -Related to: ["[[person-luca-rossi]]", "[[person-alessandro-ferrari]]"] -Tags: ["Health", "Sport"] ---- -# Long ride — 2024-08-31 -Long ride with Alessandro. 88km, 1969m elevation. - -## Notes -- Last ride of summer with Alessandro before the weather turns. Went all-in on the climbing — nearly 2000m in 88km. -- Did the Chianti "grand tour": Castellina, Radda, Gaiole, and back. Every connecting road is a climb. -- Both of us in peak summer form. Pushed hard on every ascent, then recovered on the descents. Natural interval training. -- Espresso stop at the enoteca in Radda. Sat in the shade and talked about autumn plans — Alessandro wants to do a late-season granfondo. -- The light in late August is different — golden, low, long shadows even at midday. Perfect for riding. -- Total climbing was the most we've ever done together in a single ride. Both set personal bests on the Radda segment on Strava. diff --git a/demo-vault-v2/event-long-ride-2024-09-07.md b/demo-vault-v2/event-long-ride-2024-09-07.md deleted file mode 100644 index f5faa3de..00000000 --- a/demo-vault-v2/event-long-ride-2024-09-07.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -aliases: ["Long ride — 2024-09-07"] -Is A: Event -Date: "2024-09-07" -Belongs to: "[[2024-09]]" -Related to: ["[[person-luca-rossi]]", "[[person-alessandro-ferrari]]"] -Tags: ["Health", "Sport"] ---- -# Long ride — 2024-09-07 -Long ride with Alessandro. 110km, 1633m elevation. - -## Notes -- First ride in September weather — cooler air, sharper light. Still 25°C but felt fresh after the August furnace. -- Long loop through the Val d'Orcia: Pienza, Monticchiello, Montepulciano. The road between Pienza and Monticchiello has the most photographed cypress trees in Tuscany. -- Alessandro proposed we sign up for the granfondo in Chianti next month. 130km, 2500m climbing. Committed on the spot. -- Stopped in Monticchiello for a quick caffè. The village was setting up for a sagra (food festival) — the smell of roasting meat was torture. -- Legs felt rested after an easy week. Power was strong — averaged 210W over 4 hours without feeling strained. -- Tailwind for the last 20km home. Cruised at 35 km/h with barely any effort. Perfect way to end a ride. diff --git a/demo-vault-v2/event-long-ride-2024-09-14.md b/demo-vault-v2/event-long-ride-2024-09-14.md deleted file mode 100644 index 0b4bd13f..00000000 --- a/demo-vault-v2/event-long-ride-2024-09-14.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -aliases: ["Long ride — 2024-09-14"] -Is A: Event -Date: "2024-09-14" -Belongs to: "[[2024-09]]" -Related to: ["[[person-luca-rossi]]", "[[person-alessandro-ferrari]]"] -Tags: ["Health", "Sport"] ---- -# Long ride — 2024-09-14 -Long ride with Alessandro. 106km, 1756m elevation. - -## Notes -- Granfondo training ride. Simulated the first 100km of the Chianti event — same roads, similar climbing profile. -- The climb sequence from Gaiole to Radda to Castellina is relentless. 40km of constant up and down with no real flat. -- Alessandro paced us perfectly — kept the power at 75% of threshold on every climb. Smart riding instead of attacking everything. -- Practiced eating while climbing. Had a gel at the bottom of each major climb so the sugar would kick in near the top. -- Stopped briefly in Castellina for water and a quick stretch. Legs felt good at km 80 — encouraging for the granfondo. -- Rain threatened from the west but held off. The dark clouds over the hills made for dramatic scenery. -- 106km in 4h10m. If we can maintain this for 130km at the event, we'll finish well under the cutoff. - -## Follow-up -- [ ] Confirm granfondo registration and select wave start time diff --git a/demo-vault-v2/event-long-ride-2024-09-21.md b/demo-vault-v2/event-long-ride-2024-09-21.md deleted file mode 100644 index e71f1dfa..00000000 --- a/demo-vault-v2/event-long-ride-2024-09-21.md +++ /dev/null @@ -1,19 +0,0 @@ ---- -aliases: ["Long ride — 2024-09-21"] -Is A: Event -Date: "2024-09-21" -Belongs to: "[[2024-09]]" -Related to: ["[[person-luca-rossi]]", "[[person-alessandro-ferrari]]"] -Tags: ["Health", "Sport"] ---- -# Long ride — 2024-09-21 -Long ride with Alessandro. 121km, 1001m elevation. - -## Notes -- Flat recovery ride after two big climbing weeks. Rode out along the Arbia valley, then north through Staggia and Poggibonsi. -- Kept it social — easy pace, lots of talking. Alessandro shared updates on his job search. Sounds like he has a promising lead. -- 121km on flat terrain feels very different from 80km in the hills. Less intense but more time in the saddle. -- Stopped in Poggibonsi at the bakery near the station. Fresh focaccia and a cappuccino. Proper recovery fuel. -- Roads were in excellent condition after recent resurfacing on the SP541. Smooth as a velodrome. -- Average speed 29.8 km/h — nearly cracked 30 on a long ride. The flat terrain and gentle tailwind helped. -- Legs felt tired but not sore. Good sign of adaptation — the big volume is paying off. diff --git a/demo-vault-v2/event-long-ride-2024-09-28.md b/demo-vault-v2/event-long-ride-2024-09-28.md deleted file mode 100644 index 308be43b..00000000 --- a/demo-vault-v2/event-long-ride-2024-09-28.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -aliases: ["Long ride — 2024-09-28"] -Is A: Event -Date: "2024-09-28" -Belongs to: "[[2024-09]]" -Related to: ["[[person-luca-rossi]]"] -Tags: ["Health", "Sport"] ---- -# Long ride — 2024-09-28 -Solo long ride. 86km, 1309m elevation. - -## Notes -- Pre-granfondo taper ride. Moderate distance, moderate climbing, moderate effort. Saving the legs for next weekend. -- Rode the familiar Chianti loop: Castellina, Fonterutoli, back through Quercegrossa. Comfortable roads I know well. -- Tested all the gear I'll use for the granfondo — same jersey, shorts, bottles, nutrition. No surprises on race day. -- Legs felt snappy. Short efforts on a couple of climbs showed power numbers 10-15W above recent averages. The taper is working. -- Perfect autumn weather — 20°C, clear skies, gentle breeze. The vines are starting to change color. Vendemmia (grape harvest) has begun. -- Mental state is good. Feeling confident about the 130km event. The training block has been consistent. diff --git a/demo-vault-v2/event-long-ride-2024-10-05.md b/demo-vault-v2/event-long-ride-2024-10-05.md deleted file mode 100644 index 3a262673..00000000 --- a/demo-vault-v2/event-long-ride-2024-10-05.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -aliases: ["Long ride — 2024-10-05"] -Is A: Event -Date: "2024-10-05" -Belongs to: "[[2024-10]]" -Related to: ["[[person-luca-rossi]]"] -Tags: ["Health", "Sport"] ---- -# Long ride — 2024-10-05 -Solo long ride. 107km, 1175m elevation. - -## Notes -- Post-granfondo recovery ride. Easy pace, no power targets, just spinning the legs through the Val d'Orcia. -- The granfondo last weekend went well — finished the 130km in 5h15m. This ride is the first easy spin after the effort. -- Autumn colors are spectacular this year. The vineyards are golden-red, the oak forests are turning amber. -- Legs felt surprisingly fresh. The human body recovers faster than you'd expect when you fuel and sleep properly. -- Stopped at a farm stand near Buonconvento and bought a bottle of new olive oil. Fresh olio nuovo — the green, peppery kind. -- Rode some sections I normally skip — tiny dead-end roads to hilltop farms. No purpose except curiosity and enjoying the scenery. diff --git a/demo-vault-v2/event-long-ride-2024-10-12.md b/demo-vault-v2/event-long-ride-2024-10-12.md deleted file mode 100644 index 653efa77..00000000 --- a/demo-vault-v2/event-long-ride-2024-10-12.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -aliases: ["Long ride — 2024-10-12"] -Is A: Event -Date: "2024-10-12" -Belongs to: "[[2024-10]]" -Related to: ["[[person-luca-rossi]]"] -Tags: ["Health", "Sport"] ---- -# Long ride — 2024-10-12 -Solo long ride. 115km, 1000m elevation. - -## Notes -- Mellow autumn ride along the Val d'Orcia. Mixed flat and rolling terrain, nothing too steep. Enjoyed the fall scenery. -- The harvest is in full swing — tractors loaded with grapes on every road. Had to wait behind a slow tractor for 3km near Montalcino. -- Air smells different in October — wood smoke, fermenting grapes, damp leaves. Distinctly autumn. -- Tried a new route north of San Quirico, following a ridge road I'd never noticed. It connects to the SP146 via a tiny hamlet with no name on the map. -- Legs felt smooth and effortless at Z2 pace. The big summer training block has built a strong aerobic engine. -- Stopped at a bar in Torrenieri for a late-morning cornetto. The barista asked about the granfondo — apparently the local riders were talking about it. diff --git a/demo-vault-v2/event-long-ride-2024-10-19.md b/demo-vault-v2/event-long-ride-2024-10-19.md deleted file mode 100644 index aca7f373..00000000 --- a/demo-vault-v2/event-long-ride-2024-10-19.md +++ /dev/null @@ -1,21 +0,0 @@ ---- -aliases: ["Long ride — 2024-10-19"] -Is A: Event -Date: "2024-10-19" -Belongs to: "[[2024-10]]" -Related to: ["[[person-luca-rossi]]"] -Tags: ["Health", "Sport"] ---- -# Long ride — 2024-10-19 -Solo long ride. 85km, 1284m elevation. - -## Notes -- Rainy start — waited until 9am for a break in the clouds and went out in light drizzle. Full rain gear, mudguards on. -- Roads were slippery with wet leaves. Took the corners very carefully, especially the descent from Castellina where the road is shaded. -- Found a new climb near Fonterutoli that I'd overlooked — a side road climbing steeply to a farm called "Il Poggetto." 2km at 10%. Hidden gem. -- Wet riding has its own appeal — the colors are more vivid, the air smells fresh, and there's no one else out. Pure solitude. -- Stopped at a covered terrace bar in Castellina to warm up with a macchiato. Dripping water all over their floor but they didn't mind. -- Back home in 3h20m. Bike needs a thorough clean — the grit from wet roads gets into everything. - -## Follow-up -- [ ] Clean and re-lube the drivetrain — wet ride always accelerates wear diff --git a/demo-vault-v2/event-long-ride-2024-10-26.md b/demo-vault-v2/event-long-ride-2024-10-26.md deleted file mode 100644 index f6b22332..00000000 --- a/demo-vault-v2/event-long-ride-2024-10-26.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -aliases: ["Long ride — 2024-10-26"] -Is A: Event -Date: "2024-10-26" -Belongs to: "[[2024-10]]" -Related to: ["[[person-luca-rossi]]"] -Tags: ["Health", "Sport"] ---- -# Long ride — 2024-10-26 -Solo long ride. 83km, 1137m elevation. - -## Notes -- Last warm weekend of autumn. Rode south through the Crete Senesi in golden afternoon light — left late to catch the sunset on the way back. -- The clay hills of the Crete are bare now after harvest. They look like a moonscape in the low October sun. Extraordinary scenery. -- Focused on a new cadence drill: alternating between 80 rpm and 100 rpm every 5 minutes on the climbs. Working on pedaling efficiency. -- Stopped at the thermal baths viewpoint near Bagno Vignoni. Steam rising from the hot spring into the cool air — magical. -- Saw a huge murmuration of starlings near Pienza. Must have been thousands of birds swirling in formation. Stopped to watch for 5 minutes. -- Late start meant I finished in near-darkness. Need to carry lights or start earlier as the days get shorter. diff --git a/demo-vault-v2/event-long-ride-2024-11-02.md b/demo-vault-v2/event-long-ride-2024-11-02.md deleted file mode 100644 index a5e9e9a1..00000000 --- a/demo-vault-v2/event-long-ride-2024-11-02.md +++ /dev/null @@ -1,19 +0,0 @@ ---- -aliases: ["Long ride — 2024-11-02"] -Is A: Event -Date: "2024-11-02" -Belongs to: "[[2024-11]]" -Related to: ["[[person-luca-rossi]]", "[[person-alessandro-ferrari]]"] -Tags: ["Health", "Sport"] ---- -# Long ride — 2024-11-02 -Long ride with Alessandro. 130km, 1731m elevation. - -## Notes -- End-of-season epic with Alessandro. Last big ride before winter mode kicks in. Went all out — 130km, nearly 1800m climbing. -- Route: south to Montalcino, west to Massa Marittima, then back north through the hills. A proper Tuscan grand tour. -- Alessandro brought a flask of vin brule (mulled wine) in his jersey pocket — we each had a sip at the turnaround point. Warming and festive. -- The climb to Massa Marittima from the east is a hidden gem — 9km of gentle gradient through cork oak forest. Beautiful and quiet. -- Weather was crisp autumn perfection — 14°C, blue sky, no wind. The kind of day that makes you grateful to ride. -- Talked about our season totals: Alessandro estimated 8000km, I'm closer to 9500km. Both personal bests. -- Legs held up well for 130km. Fueling was on point — ate and drank consistently from km 1. No bonk, no cramps. diff --git a/demo-vault-v2/event-long-ride-2024-11-09.md b/demo-vault-v2/event-long-ride-2024-11-09.md deleted file mode 100644 index 8c85a53f..00000000 --- a/demo-vault-v2/event-long-ride-2024-11-09.md +++ /dev/null @@ -1,21 +0,0 @@ ---- -aliases: ["Long ride — 2024-11-09"] -Is A: Event -Date: "2024-11-09" -Belongs to: "[[2024-11]]" -Related to: ["[[person-luca-rossi]]"] -Tags: ["Health", "Sport"] ---- -# Long ride — 2024-11-09 -Solo long ride. 130km, 1938m elevation. - -## Notes -- Monster solo ride — longest of the season. Felt strong and decided to keep going. Extended the planned route by 30km through Chianciano and Sarteano. -- The road from Chianciano to Sarteano follows a beautiful wooded ridge. Autumn foliage at peak — red maples, golden oaks, green pines. -- Crossed the 10,000km mark for the year somewhere around km 90. Not a bad milestone for a hobby cyclist. -- Stopped three times for water — Torrenieri, Chianciano, and Sarteano. Hydration even in autumn is critical for long efforts. -- Paced it well. First 100km felt controlled. Last 30km were harder but manageable. Power dropped only 10W in the final hour. -- Total moving time 5h02m. First time over 5 hours in the saddle. Felt it in the lower back by the end. - -## Follow-up -- [ ] Do some core strength work — lower back fatigue suggests weakness there diff --git a/demo-vault-v2/event-long-ride-2024-11-16.md b/demo-vault-v2/event-long-ride-2024-11-16.md deleted file mode 100644 index 895b7b79..00000000 --- a/demo-vault-v2/event-long-ride-2024-11-16.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -aliases: ["Long ride — 2024-11-16"] -Is A: Event -Date: "2024-11-16" -Belongs to: "[[2024-11]]" -Related to: ["[[person-luca-rossi]]"] -Tags: ["Health", "Sport"] ---- -# Long ride — 2024-11-16 -Solo long ride. 92km, 1407m elevation. - -## Notes -- Cool November ride through the Chianti hills. Temperature was 8°C at start — full winter kit, thick gloves, shoe covers. -- The climbs warm you up but the descents are brutal in November. Wind chill makes 8°C feel like -2°C at 50 km/h. -- Took the road through Radda and continued to the ridge above Badia a Coltibuono. Views over the misty valley below were stunning. -- Legs felt strong — the recovery week after last weekend's monster ride did the trick. Power was up 5% compared to two weeks ago. -- Stopped at a bar in Radda for a caffè corretto (espresso with grappa). The bartender's cure for November cycling. -- Olive harvest is underway — nets under every tree, families picking by hand. The smell of freshly pressed oil drifts across the road. diff --git a/demo-vault-v2/event-long-ride-2024-11-23.md b/demo-vault-v2/event-long-ride-2024-11-23.md deleted file mode 100644 index 156b1c4f..00000000 --- a/demo-vault-v2/event-long-ride-2024-11-23.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -aliases: ["Long ride — 2024-11-23"] -Is A: Event -Date: "2024-11-23" -Belongs to: "[[2024-11]]" -Related to: ["[[person-luca-rossi]]"] -Tags: ["Health", "Sport"] ---- -# Long ride — 2024-11-23 -Solo long ride. 127km, 1442m elevation. - -## Notes -- Long endurance ride on the flat-ish Val d'Elsa route. Extended it with an extra loop through Barberino Val d'Elsa and San Donato in Poggio. -- Cold start, 5°C, but warmed to 13°C by midday. Removed arm warmers and vest around km 50. -- Focused on nutrition timing — set a 20-minute alarm on the bike computer to remind me to eat. Consumed 360g of carbs total. No energy dip. -- The road through San Donato is lined with old stone walls and has virtually no traffic. One of the most peaceful stretches in the area. -- Saw a group of about 20 riders from the local cycling club doing their Saturday social ride. Waved and chatted briefly at a junction. -- 127km in 4h28m moving time. Average speed 28.4 km/h, normalized power 195W. Consistent and controlled. diff --git a/demo-vault-v2/event-long-ride-2024-11-30.md b/demo-vault-v2/event-long-ride-2024-11-30.md deleted file mode 100644 index 1ba35ace..00000000 --- a/demo-vault-v2/event-long-ride-2024-11-30.md +++ /dev/null @@ -1,21 +0,0 @@ ---- -aliases: ["Long ride — 2024-11-30"] -Is A: Event -Date: "2024-11-30" -Belongs to: "[[2024-11]]" -Related to: ["[[person-luca-rossi]]"] -Tags: ["Health", "Sport"] ---- -# Long ride — 2024-11-30 -Solo long ride. 113km, 1122m elevation. - -## Notes -- Last ride of November. Mixed route through the Arbia valley and then east toward Asciano. Moderate climbing, good for end-of-month legs. -- Frost on the roads at the start — had to be careful on shaded corners for the first 45 minutes until the sun warmed things up. -- The Arbia river valley in late autumn is moody and beautiful. Morning mist hanging in the fields, bare trees along the riverbank. -- Legs have that late-season heaviness. Not tired exactly, just the accumulated fatigue of 10 months of riding. CTL is high but so is fatigue. -- Stopped at the thermal pool bar in Rapolano for hot chocolate. The steam from the thermal water creates a surreal atmosphere. -- Looking at the numbers: November totals around 500km. Down from summer peak but still maintaining base fitness well. - -## Follow-up -- [ ] Plan December training — reduce volume, maintain some intensity diff --git a/demo-vault-v2/event-long-ride-2024-12-07.md b/demo-vault-v2/event-long-ride-2024-12-07.md deleted file mode 100644 index f7684806..00000000 --- a/demo-vault-v2/event-long-ride-2024-12-07.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -aliases: ["Long ride — 2024-12-07"] -Is A: Event -Date: "2024-12-07" -Belongs to: "[[2024-12]]" -Related to: ["[[person-luca-rossi]]", "[[person-alessandro-ferrari]]"] -Tags: ["Health", "Sport"] ---- -# Long ride — 2024-12-07 -Long ride with Alessandro. 84km, 1281m elevation. - -## Notes -- Winter ride with Alessandro. Short but climby — perfect for cold weather when you want to keep moving without long flat stretches. -- Rode the loop through Vagliagli, Pianella, and back via the ridge road above Montaperti. Historic battlefield site — Alessandro loves the medieval history. -- The climb to Pianella was icy on the north-facing side. Had to ride on the sunny strip in the center of the road. Heart rate up from anxiety, not effort. -- Alessandro is settling into his new job. Sounds much happier — more responsibility, better team. Good for him. -- Stopped at a farmhouse osteria near Montaperti for ribollita and bruschetta. Proper Tuscan winter fuel. -- Both wore full winter kit — thermal bibs, jacket, overshoes, thick gloves. Still cold on the descents. Winter cycling requires commitment. diff --git a/demo-vault-v2/event-long-ride-2024-12-14.md b/demo-vault-v2/event-long-ride-2024-12-14.md deleted file mode 100644 index bff010ae..00000000 --- a/demo-vault-v2/event-long-ride-2024-12-14.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -aliases: ["Long ride — 2024-12-14"] -Is A: Event -Date: "2024-12-14" -Belongs to: "[[2024-12]]" -Related to: ["[[person-luca-rossi]]", "[[person-alessandro-ferrari]]"] -Tags: ["Health", "Sport"] ---- -# Long ride — 2024-12-14 -Long ride with Alessandro. 118km, 881m elevation. - -## Notes -- Long flat winter ride. Avoided the hills due to ice risk above 500m. Stayed in the valleys — Arbia, Val d'Orcia, Val di Chiana. -- 118km on flat roads means lots of pedaling and not much rest. Headwind on the return made the last 40km feel like climbing. -- Alessandro and I discussed New Year's resolutions. His: more structured training. Mine: focus on recovery and sleep quality. -- Stopped twice — once at a bar in Sinalunga for espresso, and again at a tabaccaio in Trequanda for a panino. -- Roads were quiet — December riding in Tuscany means you have the roads almost to yourself. Occasionally passed olive oil tankers. -- Average speed 27.2 km/h, HR average 138 bpm. Classic Zone 2 ride. The long winter base miles are what build next year's fitness. diff --git a/demo-vault-v2/event-long-ride-2024-12-21.md b/demo-vault-v2/event-long-ride-2024-12-21.md deleted file mode 100644 index d3c8dfbf..00000000 --- a/demo-vault-v2/event-long-ride-2024-12-21.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -aliases: ["Long ride — 2024-12-21"] -Is A: Event -Date: "2024-12-21" -Belongs to: "[[2024-12]]" -Related to: ["[[person-luca-rossi]]"] -Tags: ["Health", "Sport"] ---- -# Long ride — 2024-12-21 -Solo long ride. 100km, 1334m elevation. - -## Notes -- Winter solstice ride. Shortest day of the year — left at first light and had to time it carefully to finish before dark at 4:30pm. -- Rode through Chianti toward Greve, then south through Panzano and back. The winter-stripped vineyards have a stark beauty. -- Temperature hovered around 4°C the entire ride. Never warmed up. Numbness in the toes set in at km 60 despite thick overshoes. -- Motivation for winter riding comes from knowing that spring fitness is built in December. Every cold ride now pays dividends in April. -- Stopped at a bar in Panzano for a hot cappuccino. The heat of the cup on my frozen hands was bliss. -- 100km in 3h48m. Pushed the pace a bit to stay warm — average power was 205W, higher than a typical endurance ride. diff --git a/demo-vault-v2/event-long-ride-2024-12-28.md b/demo-vault-v2/event-long-ride-2024-12-28.md deleted file mode 100644 index 5e68e40d..00000000 --- a/demo-vault-v2/event-long-ride-2024-12-28.md +++ /dev/null @@ -1,19 +0,0 @@ ---- -aliases: ["Long ride — 2024-12-28"] -Is A: Event -Date: "2024-12-28" -Belongs to: "[[2024-12]]" -Related to: ["[[person-luca-rossi]]", "[[person-alessandro-ferrari]]"] -Tags: ["Health", "Sport"] ---- -# Long ride — 2024-12-28 -Long ride with Alessandro. 105km, 1068m elevation. - -## Notes -- Post-Christmas ride with Alessandro. Both needed to burn off the panettone and tortellini. Easy pace, social riding. -- Route followed the Arbia valley south, then looped through Buonconvento and back via Monte Oliveto. Gentle terrain for holiday legs. -- Alessandro got a new Garmin Edge 1050 for Christmas — spent half the ride fiddling with the settings and comparing features to his old unit. -- Stopped in Buonconvento at the pasticceria for a slice of panforte and caffè. Sweet, dense, and perfect for cold-weather riding fuel. -- Year-end reflections: talked about how much our riding has improved this year. Both did more kilometers and more climbing than ever before. -- Roads were very quiet between Christmas and New Year. Some sections we had entirely to ourselves for 10-15km. -- Finished at 1pm, plenty of time for a hot shower and leftover Christmas lunch. diff --git a/demo-vault-v2/event-long-ride-2025-01-04.md b/demo-vault-v2/event-long-ride-2025-01-04.md deleted file mode 100644 index 5f1cde4c..00000000 --- a/demo-vault-v2/event-long-ride-2025-01-04.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -aliases: ["Long ride — 2025-01-04"] -Is A: Event -Date: "2025-01-04" -Belongs to: "[[2025-01]]" -Related to: ["[[person-luca-rossi]]"] -Tags: ["Health", "Sport"] ---- -# Long ride — 2025-01-04 -Solo long ride. 84km, 819m elevation. - -## Notes -- First ride of the new year. Easy spin through the Val d'Orcia to shake off the holiday sluggishness. No power targets, no route plan, just ride. -- Legs felt surprisingly decent after two weeks of reduced volume. The rest did its job — cadence was smooth and power came easily. -- New Year's resolution in action: focusing more on recovery quality this year. Slept 9 hours last night before this ride. -- Flat-ish route through Monteroni, San Quirico, and Bagno Vignoni. Low elevation gain for an easy start to the season. -- Cold and grey but dry. 6°C, overcast. Classic January in Tuscany. At least the roads are clean after recent rain. -- Only 84km — short by last year's standards but perfect for a reset ride. The big miles will come soon enough. diff --git a/demo-vault-v2/event-long-ride-2025-01-11.md b/demo-vault-v2/event-long-ride-2025-01-11.md deleted file mode 100644 index 16ecf030..00000000 --- a/demo-vault-v2/event-long-ride-2025-01-11.md +++ /dev/null @@ -1,21 +0,0 @@ ---- -aliases: ["Long ride — 2025-01-11"] -Is A: Event -Date: "2025-01-11" -Belongs to: "[[2025-01]]" -Related to: ["[[person-luca-rossi]]"] -Tags: ["Health", "Sport"] ---- -# Long ride — 2025-01-11 -Solo long ride. 84km, 1901m elevation. - -## Notes -- Big climbing day despite the short distance. Rode to Monte Amiata from the west via Santa Fiora — the steepest approach. -- The Santa Fiora climb is savage — 12km averaging 7.5% with a 2km section at 12%. Hit 350W at the steepest point just to keep moving. -- Snow visible on the summit from the lower slopes. Turned around at 1200m elevation as ice patches started appearing on the road. -- Stopped in Santa Fiora at a bar in the main piazza. Warming up with a caffè lungo while watching snow flurries drift down. -- The descent was cold — possibly the coldest I've ever ridden. Fingers went numb within 5 minutes despite winter gloves. Had to stop twice to warm up. -- 84km but nearly 1900m of elevation. This is a proper mountain day crammed into a short ride. Average gradient on climbed sections was 8.3%. - -## Follow-up -- [ ] Invest in heated glove liners for winter mountain descents diff --git a/demo-vault-v2/event-long-ride-2025-01-18.md b/demo-vault-v2/event-long-ride-2025-01-18.md deleted file mode 100644 index e6d9985e..00000000 --- a/demo-vault-v2/event-long-ride-2025-01-18.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -aliases: ["Long ride — 2025-01-18"] -Is A: Event -Date: "2025-01-18" -Belongs to: "[[2025-01]]" -Related to: ["[[person-luca-rossi]]"] -Tags: ["Health", "Sport"] ---- -# Long ride — 2025-01-18 -Solo long ride. 95km, 1556m elevation. - -## Notes -- Climbed to Volterra from the south via Pomarance. A road less traveled — almost no traffic and beautiful views of the metalliferous hills. -- Geothermal steam vents near Larderello are visible from the road. The landscape looks otherworldly — pipes, steam, and the smell of sulfur. -- Felt sluggish for the first hour, then the engine warmed up. By km 40 the power was flowing naturally. Sometimes you just need patience. -- Stopped at a bar in Volterra for a quick espresso. The Etruscan museum was open — tempting but saved it for another day. -- Tried a new chamois cream — much better than the old one. No saddle discomfort at all despite 3.5 hours in the saddle. -- Descended via the main road toward Colle Val d'Elsa. Fast, sweeping bends through rolling farmland. Reached 72 km/h on the straight. diff --git a/demo-vault-v2/event-long-ride-2025-01-25.md b/demo-vault-v2/event-long-ride-2025-01-25.md deleted file mode 100644 index 09bffc03..00000000 --- a/demo-vault-v2/event-long-ride-2025-01-25.md +++ /dev/null @@ -1,21 +0,0 @@ ---- -aliases: ["Long ride — 2025-01-25"] -Is A: Event -Date: "2025-01-25" -Belongs to: "[[2025-01]]" -Related to: ["[[person-luca-rossi]]"] -Tags: ["Health", "Sport"] ---- -# Long ride — 2025-01-25 -Solo long ride. 125km, 1419m elevation. - -## Notes -- Big January ride. Pushed the distance to build endurance ahead of the spring season. Out past Montalcino and south toward Arcidosso. -- The road from Montalcino to Arcidosso follows the west flank of Monte Amiata. Rolling terrain with constant views of the mountain above. -- Ate a gel every 30 minutes from the start. No waiting until hungry — proactive fueling makes a huge difference on long rides. -- Stopped at a small cafe in Arcidosso. The town is quiet in January — mainly locals. Had a brioche and cappuccino. -- Wind picked up at km 90, gusting from the west. The last 35km home were a battle. Average speed dropped to 23 km/h. -- 125km in 4h45m. Strong ride for January. If I can maintain this consistency, spring form will be ahead of last year's. - -## Follow-up -- [ ] Plan a progressive long ride schedule: 130km, 140km, 150km through Feb-March diff --git a/demo-vault-v2/event-long-ride-2025-02-01.md b/demo-vault-v2/event-long-ride-2025-02-01.md deleted file mode 100644 index f01316e2..00000000 --- a/demo-vault-v2/event-long-ride-2025-02-01.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -aliases: ["Long ride — 2025-02-01"] -Is A: Event -Date: "2025-02-01" -Belongs to: "[[2025-02]]" -Related to: ["[[person-luca-rossi]]", "[[person-alessandro-ferrari]]"] -Tags: ["Health", "Sport"] ---- -# Long ride — 2025-02-01 -Long ride with Alessandro. 115km, 1413m elevation. - -## Notes -- First proper long ride with Alessandro this year. His off-season gym work is showing — noticeably more power on the short climbs. -- Rode the classic Chianti route: Castellina, Radda, Gaiole, and back through Castelnuovo Berardenga. The roads we know best. -- Alessandro shared that his daughter started school last month. He's adjusting to the early morning school run before work. Less sleep, more coffee. -- Stopped at the enoteca in Castellina for a mid-ride espresso. They have a new barista who makes an excellent crema. -- Temperature was 9°C but sunny — warm enough to ride without a jacket after the first climb. February in Tuscany can surprise you. -- Both felt strong at km 100. Good sign — last year at this point in the season, 100km+ rides were a struggle. diff --git a/demo-vault-v2/event-long-ride-2025-02-08.md b/demo-vault-v2/event-long-ride-2025-02-08.md deleted file mode 100644 index 00add824..00000000 --- a/demo-vault-v2/event-long-ride-2025-02-08.md +++ /dev/null @@ -1,21 +0,0 @@ ---- -aliases: ["Long ride — 2025-02-08"] -Is A: Event -Date: "2025-02-08" -Belongs to: "[[2025-02]]" -Related to: ["[[person-luca-rossi]]", "[[person-alessandro-ferrari]]"] -Tags: ["Health", "Sport"] ---- -# Long ride — 2025-02-08 -Long ride with Alessandro. 88km, 1341m elevation. - -## Notes -- Strade Bianche hype ride — the pro race is next week and we wanted to ride some of the same gravel sectors. Hit sectors 3, 4, and 5 south of Siena. -- The gravel was loose after winter rains. Front wheel washed out once on a corner — caught it, but heart rate spiked to 190 bpm from the scare. -- Alessandro ran 32mm tires and I had 28mm. The difference was obvious — his bike was noticeably more stable on the rough stuff. -- Stopped at a farmer's bar in Radi. Three tables, no menu, just what's available. Had bread with olive oil and a glass of Chianti. -- Discussed tire widths and pressure for gravel. Consensus: minimum 30mm for Strade Bianche terrain, 4 bar or less. -- The piazza in Siena where the race finishes was already being prepared with barriers and signage. Exciting to see. - -## Follow-up -- [ ] Try fitting 30mm tires on the road bike for mixed terrain rides diff --git a/demo-vault-v2/event-long-ride-2025-02-15.md b/demo-vault-v2/event-long-ride-2025-02-15.md deleted file mode 100644 index 62a933a2..00000000 --- a/demo-vault-v2/event-long-ride-2025-02-15.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -aliases: ["Long ride — 2025-02-15"] -Is A: Event -Date: "2025-02-15" -Belongs to: "[[2025-02]]" -Related to: ["[[person-luca-rossi]]", "[[person-alessandro-ferrari]]"] -Tags: ["Health", "Sport"] ---- -# Long ride — 2025-02-15 -Long ride with Alessandro. 98km, 1231m elevation. - -## Notes -- Rode out to watch the Strade Bianche passing through the countryside. Positioned ourselves near sector 6, rode there and waited for the peloton. -- Seeing the pros on the white roads in person is incredible. The speed, the noise of tires on gravel, the dust cloud. Electrifying. -- After the race passed, we continued our ride along the now-empty sectors. Fresh tire tracks from the pros on the gravel — surreal. -- Alessandro was so hyped by the race he attacked every climb on the way home. Couldn't hold his wheel on the last two. -- Quick espresso stop in Monteroni. The bar had the race on TV — watched the final climb into Siena while catching our breath. -- 98km with the race-watching break in the middle. Effective riding time was closer to 3 hours. Fun ride, not a training ride. diff --git a/demo-vault-v2/event-long-ride-2025-02-22.md b/demo-vault-v2/event-long-ride-2025-02-22.md deleted file mode 100644 index 85d85f05..00000000 --- a/demo-vault-v2/event-long-ride-2025-02-22.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -aliases: ["Long ride — 2025-02-22"] -Is A: Event -Date: "2025-02-22" -Belongs to: "[[2025-02]]" -Related to: ["[[person-luca-rossi]]", "[[person-alessandro-ferrari]]"] -Tags: ["Health", "Sport"] ---- -# Long ride — 2025-02-22 -Long ride with Alessandro. 120km, 1340m elevation. - -## Notes -- Longest ride of the winter. Took the Montepulciano route — south through the Val d'Orcia, then east to Montepulciano and back via Chianciano. -- Alessandro set a hard pace on the climb to Montepulciano. Average 295W for 6 minutes. I held on but was breathing hard at the top. -- The Val d'Orcia is starting to green up. First signs of spring — grass growing, wildflowers in the sheltered spots, more birds singing. -- Long lunch stop in Montepulciano at the trattoria near Piazza Grande. Shared a plate of pici all'aglione and a glass of Nobile. Mid-ride wine — dangerous but delicious. -- Talked about summer plans. Alessandro wants to do a multi-day tour through Sardinia. Sounds amazing but logistically complex. -- 120km in 4h35m. Strong winter ride. Both felt we could have gone further. Spring form is building ahead of schedule. diff --git a/demo-vault-v2/event-long-ride-2025-03-01.md b/demo-vault-v2/event-long-ride-2025-03-01.md deleted file mode 100644 index f5bdec88..00000000 --- a/demo-vault-v2/event-long-ride-2025-03-01.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -aliases: ["Long ride — 2025-03-01"] -Is A: Event -Date: "2025-03-01" -Belongs to: "[[2025-03]]" -Related to: ["[[person-luca-rossi]]", "[[person-alessandro-ferrari]]"] -Tags: ["Health", "Sport"] ---- -# Long ride — 2025-03-01 -Long ride with Alessandro. 107km, 1366m elevation. - -## Notes -- First day of March and it felt like spring. 16°C, sunny, light breeze from the south. Rode in short sleeves for the first time in four months. -- Took the route toward Greve in Chianti, then south through Panzano and back via Castellina. Rolling Chianti classics. -- Alessandro is considering signing up for a local time trial series. He's been working on his TT position on the trainer — looks fast. -- The wisteria is starting to bloom on the farmhouse walls around Panzano. Purple cascades everywhere — makes every climb scenic. -- Stopped at the alimentari in Greve for a mortadella panino and a Chinotto. Old-school Italian mid-ride nutrition. -- Power felt effortless at 210W. The winter base is translating into real fitness. Best power-to-RPE ratio in months. diff --git a/demo-vault-v2/event-long-ride-2025-03-08.md b/demo-vault-v2/event-long-ride-2025-03-08.md deleted file mode 100644 index e3fb758d..00000000 --- a/demo-vault-v2/event-long-ride-2025-03-08.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -aliases: ["Long ride — 2025-03-08"] -Is A: Event -Date: "2025-03-08" -Belongs to: "[[2025-03]]" -Related to: ["[[person-luca-rossi]]"] -Tags: ["Health", "Sport"] ---- -# Long ride — 2025-03-08 -Solo long ride. 120km, 1336m elevation. - -## Notes -- Long solo ride exploring new roads west of Colle Val d'Elsa toward Casole d'Elsa and the Colline Metallifere. -- The hills near Casole d'Elsa are less manicured than Chianti — more wild, more forested, fewer tourists. A different kind of beauty. -- Discovered a stunning viewpoint near the village of Mensano — you can see from the metalliferous hills all the way to the coast on a clear day. -- Legs were strong from km 1. Hit Z3 power on every climb without feeling like I was pushing. Aerobic fitness is in a great place. -- Stopped at a tiny bar in Casole d'Elsa that had no other customers. The owner came out to admire the bike and talk about the Giro d'Italia coming through in May. -- 120km in 4h12m. Feeling confident about building toward 150km rides this spring. diff --git a/demo-vault-v2/event-long-ride-2025-03-15.md b/demo-vault-v2/event-long-ride-2025-03-15.md deleted file mode 100644 index 1b2c8eae..00000000 --- a/demo-vault-v2/event-long-ride-2025-03-15.md +++ /dev/null @@ -1,21 +0,0 @@ ---- -aliases: ["Long ride — 2025-03-15"] -Is A: Event -Date: "2025-03-15" -Belongs to: "[[2025-03]]" -Related to: ["[[person-luca-rossi]]"] -Tags: ["Health", "Sport"] ---- -# Long ride — 2025-03-15 -Solo long ride. 87km, 954m elevation. - -## Notes -- Recovery week ride. Kept it short and moderate. Flat-ish loop through the Arbia valley with just a couple of gentle climbs. -- Used the ride to test new handlebar tape — Supacaz, the sticky kind. Much better grip than the old tape, especially when hands get sweaty. -- Noticed some clicking from the bottom bracket around km 30. Might be the bearings wearing out — it happens every 6000km or so. -- Spring is in full bloom. Poppies in the fields, green grass, warm air. The Tuscan countryside at its absolute best. -- Stopped at a farm near Lucignano d'Arbia that sells eggs and honey. Bought a jar of wildflower honey — great on toast before rides. -- 87km in 3h05m. Easy day. The body needs these lighter weeks to absorb the hard training. - -## Follow-up -- [ ] Have the bottom bracket checked and possibly replaced at the bike shop diff --git a/demo-vault-v2/event-long-ride-2025-03-22.md b/demo-vault-v2/event-long-ride-2025-03-22.md deleted file mode 100644 index b33e34dd..00000000 --- a/demo-vault-v2/event-long-ride-2025-03-22.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -aliases: ["Long ride — 2025-03-22"] -Is A: Event -Date: "2025-03-22" -Belongs to: "[[2025-03]]" -Related to: ["[[person-luca-rossi]]"] -Tags: ["Health", "Sport"] ---- -# Long ride — 2025-03-22 -Solo long ride. 89km, 1917m elevation. - -## Notes -- Pure climbing day. Focused on the steepest climbs in the area — Castelmuzio wall, the ramp to Montefollonico, and two repeats of the Chiusure hill. -- Nearly 1900m of climbing in 89km — that's an average of 21.5m per km. Basically went uphill the entire ride. -- The Montefollonico climb has a section of rough cobblestones near the top. Handlebar vibration was intense — glad for the new grippy bar tape. -- Legs were on fire after the second Chiusure repeat. Held 270W on the first, dropped to 245W on the second. Still strong. -- Stopped briefly at the fountain in Trequanda to refill bottles. The town was deserted — everyone was at the weekly market in Sinalunga. -- Descended carefully on roads I'd only climbed before. The reverse perspective reveals different features — you notice things going down that you miss going up. diff --git a/demo-vault-v2/event-long-ride-2025-03-29.md b/demo-vault-v2/event-long-ride-2025-03-29.md deleted file mode 100644 index 14eeaf73..00000000 --- a/demo-vault-v2/event-long-ride-2025-03-29.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -aliases: ["Long ride — 2025-03-29"] -Is A: Event -Date: "2025-03-29" -Belongs to: "[[2025-03]]" -Related to: ["[[person-luca-rossi]]", "[[person-alessandro-ferrari]]"] -Tags: ["Health", "Sport"] ---- -# Long ride — 2025-03-29 -Long ride with Alessandro. 88km, 885m elevation. - -## Notes -- Easy social ride with Alessandro. Low climbing, gentle pace. Both agreed we needed a lighter day after hard training weeks. -- Rode the flat valley roads south of Siena — Monteroni, Buonconvento, and along the Ombrone river valley. Simple and scenic. -- Alessandro confirmed he signed up for the TT series starting in April. Three races over six weeks. He's excited and nervous. -- The river Ombrone had high water levels from spring rain. The road near the bridge at Buonconvento was partially flooded — had to dismount and walk through. -- Stopped at the osteria in Buonconvento for a long lunch. Pappa al pomodoro, bread, and a glass of rosso. The kind of ride that becomes a social event. -- 88km in 3h25m including the lunch break. Average moving speed was 28.2 km/h — easy pace on flat roads. Good conversation ride. diff --git a/demo-vault-v2/event-long-ride-2025-04-05.md b/demo-vault-v2/event-long-ride-2025-04-05.md deleted file mode 100644 index 01fb8c49..00000000 --- a/demo-vault-v2/event-long-ride-2025-04-05.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -aliases: ["Long ride — 2025-04-05"] -Is A: Event -Date: "2025-04-05" -Belongs to: "[[2025-04]]" -Related to: ["[[person-luca-rossi]]"] -Tags: ["Health", "Sport"] ---- -# Long ride — 2025-04-05 -Solo long ride. 93km, 1311m elevation. - -## Notes -- April riding is the best — warm enough for summer kit, cool enough for hard efforts. 20°C, light clouds, gentle breeze. -- Rode through the Chianti hills toward Lecchi in Chianti and then up the steep back road to Badia a Coltibuono. -- The Badia road from the east is a proper climb — 5km at 7.5% average through dense chestnut forest. Beautiful and brutal. -- Wildflowers everywhere. Yellow broom, red poppies, purple irises. The roadsides look like an Impressionist painting. -- Power meter showed a new 20-minute best: 285W at 72kg. That's just under 4.0 W/kg. The target is getting closer. -- Stopped at the Badia a Coltibuono wine estate. They have a small bar for cyclists — espresso and a view over the Arno valley. diff --git a/demo-vault-v2/event-long-ride-2025-04-12.md b/demo-vault-v2/event-long-ride-2025-04-12.md deleted file mode 100644 index a8b1c0af..00000000 --- a/demo-vault-v2/event-long-ride-2025-04-12.md +++ /dev/null @@ -1,21 +0,0 @@ ---- -aliases: ["Long ride — 2025-04-12"] -Is A: Event -Date: "2025-04-12" -Belongs to: "[[2025-04]]" -Related to: ["[[person-luca-rossi]]"] -Tags: ["Health", "Sport"] ---- -# Long ride — 2025-04-12 -Solo long ride. 106km, 1116m elevation. - -## Notes -- Mixed route through the Val d'Orcia and Crete Senesi. Moderate climbing with one serious effort on the climb to Pienza from the south. -- The Pienza climb from the Orcia valley side is often overlooked — 3km at 8% with switchbacks through olive groves. Fast and steep. -- Pacing has improved dramatically compared to last year. The same routes feel easier at the same power — fitness translating to efficiency. -- Stopped in Pienza for a quick slice of pizza bianca from the bakery on the main street. Thin, crispy, perfect. -- Noticed that the Giro d'Italia route markers are already up on some roads. The race passes through this area in three weeks. -- 106km in 3h42m. Average speed 28.6 km/h. Settling into a rhythm where 100km rides feel routine rather than ambitious. - -## Follow-up -- [ ] Check Giro d'Italia stage route — might be able to watch from a good spot diff --git a/demo-vault-v2/event-long-ride-2025-04-19.md b/demo-vault-v2/event-long-ride-2025-04-19.md deleted file mode 100644 index e3d370af..00000000 --- a/demo-vault-v2/event-long-ride-2025-04-19.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -aliases: ["Long ride — 2025-04-19"] -Is A: Event -Date: "2025-04-19" -Belongs to: "[[2025-04]]" -Related to: ["[[person-luca-rossi]]", "[[person-alessandro-ferrari]]"] -Tags: ["Health", "Sport"] ---- -# Long ride — 2025-04-19 -Long ride with Alessandro. 90km, 1162m elevation. - -## Notes -- Post-TT ride with Alessandro. He did his first time trial yesterday and finished mid-pack — happy with the result but wants to improve his aero position. -- Rode the familiar loop through Castellina and Fonterutoli. A comfort route when you want to chat more than suffer. -- Alessandro analyzed his TT data all morning — power was good but his CdA (aerodynamic drag) is too high. Needs a skinsuit and aero helmet. -- Beautiful spring day — 22°C, high thin clouds, the hills bright green. Peak Tuscan spring. -- Stopped at the bar in Fonterutoli for two espressos and a cornetto each. Talked for 30 minutes about bike fitting, aerodynamics, and marginal gains. -- Easy pace throughout. Average power only 175W but that's the point — social rides are for recovery and friendship, not fitness. diff --git a/demo-vault-v2/event-long-ride-2025-04-26.md b/demo-vault-v2/event-long-ride-2025-04-26.md deleted file mode 100644 index a6079fe6..00000000 --- a/demo-vault-v2/event-long-ride-2025-04-26.md +++ /dev/null @@ -1,21 +0,0 @@ ---- -aliases: ["Long ride — 2025-04-26"] -Is A: Event -Date: "2025-04-26" -Belongs to: "[[2025-04]]" -Related to: ["[[person-luca-rossi]]"] -Tags: ["Health", "Sport"] ---- -# Long ride — 2025-04-26 -Solo long ride. 106km, 1308m elevation. - -## Notes -- Late April ride through rolling Chianti terrain. The vines are leafing out, covering the trellises with fresh green growth. -- Explored a loop I'd been planning: Castelnuovo Berardenga, Pianella, Villa a Sesta, and back. Some narrow, quiet roads with beautiful old farmhouses. -- Found a perfect stretch for tempo efforts — 5km of false flat between Villa a Sesta and Castelnuovo. Did two 10-minute intervals at 250W. -- Temperature climbed to 25°C by midday. First ride where I genuinely felt the summer heat building. Drank 3 liters total. -- Stopped at an enoteca in Castelnuovo Berardenga. They offered a tasting but declined — mid-ride wine is tempting but impractical solo. -- Chain started skipping on the smallest sprocket. Need to replace the cassette soon — the teeth are getting worn on the 11 and 12. - -## Follow-up -- [ ] Order a new cassette — Shimano Ultegra 11-30 diff --git a/demo-vault-v2/event-long-ride-2025-05-03.md b/demo-vault-v2/event-long-ride-2025-05-03.md deleted file mode 100644 index e29a5ad9..00000000 --- a/demo-vault-v2/event-long-ride-2025-05-03.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -aliases: ["Long ride — 2025-05-03"] -Is A: Event -Date: "2025-05-03" -Belongs to: "[[2025-05]]" -Related to: ["[[person-luca-rossi]]", "[[person-alessandro-ferrari]]"] -Tags: ["Health", "Sport"] ---- -# Long ride — 2025-05-03 -Long ride with Alessandro. 82km, 1763m elevation. - -## Notes -- Climbing day with Alessandro. Short distance, massive elevation — every road we chose went uphill. Chianti hills at their steepest. -- Route hit the trifecta: climb to Volpaia (savage ramps), descent to Gaiole, climb to Barbischio, descent, then the long climb to Badia a Coltibuono. -- Alessandro's TT training is paying off — his sustained power has improved. Stayed together on all the climbs for the first time in months. -- The climb to Barbischio has a 16% wall at km 1. Had to stand and grind at 50 rpm. Quads were on fire. -- Quick caffè stop at the osteria in Gaiole between the climbs. The owner now recognizes us and has our espressos ready when we walk in. -- 82km but 1763m of elevation is a ratio of 21.5m/km. One of our hardest rides by climbing density. Both set Strava PRs on the Volpaia segment. diff --git a/demo-vault-v2/event-long-ride-2025-05-10.md b/demo-vault-v2/event-long-ride-2025-05-10.md deleted file mode 100644 index 858f4e05..00000000 --- a/demo-vault-v2/event-long-ride-2025-05-10.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -aliases: ["Long ride — 2025-05-10"] -Is A: Event -Date: "2025-05-10" -Belongs to: "[[2025-05]]" -Related to: ["[[person-luca-rossi]]"] -Tags: ["Health", "Sport"] ---- -# Long ride — 2025-05-10 -Solo long ride. 99km, 1266m elevation. - -## Notes -- Giro d'Italia fever — the race passes through the area this week. Pink banners on every road, advertisements everywhere. The excitement is contagious. -- Rode part of the Giro stage route to preview it. The roads have been freshly paved for the race — smooth as glass. Incredible tarmac. -- The new cassette makes a noticeable difference. Crisp shifting, no skipping, silence under power. Should have replaced it weeks ago. -- Warm spring day, 24°C. The wheat fields are tall and golden-green, almost ready for harvest. Tuscany is at peak beauty. -- Stopped at a bar in Buonconvento that had Giro memorabilia all over the walls. The owner remembered a stage passing through in 2010. -- 99km in 3h28m. Felt strong and motivated. The combination of good weather, fresh legs, and race excitement makes for great rides. diff --git a/demo-vault-v2/event-long-ride-2025-05-17.md b/demo-vault-v2/event-long-ride-2025-05-17.md deleted file mode 100644 index 87c3b177..00000000 --- a/demo-vault-v2/event-long-ride-2025-05-17.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -aliases: ["Long ride — 2025-05-17"] -Is A: Event -Date: "2025-05-17" -Belongs to: "[[2025-05]]" -Related to: ["[[person-luca-rossi]]", "[[person-alessandro-ferrari]]"] -Tags: ["Health", "Sport"] ---- -# Long ride — 2025-05-17 -Long ride with Alessandro. 97km, 942m elevation. - -## Notes -- Moderate ride with Alessandro — kept it conversational. He had his second TT race yesterday and improved his time by 45 seconds. -- Flat-ish route through the Arbia valley and out toward Asciano. Low climbing to save the legs — both had hard weeks. -- Alessandro shared that his new skinsuit and aero helmet made a measurable difference — 8 watts saved at the same speed. The marginal gains are real. -- Stopped at the Crete Senesi viewpoint above Asciano. The landscape looks different every season — right now the wheat is chest-high and rippling in the wind. -- Discussed the possibility of doing a bike-packing trip together in autumn. Maybe along the Via Francigena from Siena to Rome. 250km in 3 days. -- Easy pace: 26.5 km/h average, 170W average power. Social ride disguised as training. The best kind. diff --git a/demo-vault-v2/event-long-ride-2025-05-24.md b/demo-vault-v2/event-long-ride-2025-05-24.md deleted file mode 100644 index 78fcfb06..00000000 --- a/demo-vault-v2/event-long-ride-2025-05-24.md +++ /dev/null @@ -1,19 +0,0 @@ ---- -aliases: ["Long ride — 2025-05-24"] -Is A: Event -Date: "2025-05-24" -Belongs to: "[[2025-05]]" -Related to: ["[[person-luca-rossi]]", "[[person-alessandro-ferrari]]"] -Tags: ["Health", "Sport"] ---- -# Long ride — 2025-05-24 -Long ride with Alessandro. 114km, 1478m elevation. - -## Notes -- Long ride south through the Val d'Orcia and up to Radicofani. The fortress on the hilltop is visible for 30km — a beacon guiding you on the approach. -- The climb to Radicofani from the north is 10km at 5.5% average. Not steep but relentless. Alessandro and I paced it together, alternating pulls. -- View from the top extends in every direction — Monte Amiata to the west, Lago Trasimeno to the east, the Orcia valley below. Worth every meter of climbing. -- Stopped at the bar next to the fortress. Tourist prices but the view justifies it. Had a panino and a Coca-Cola. -- Descended via the south side — fast sweeping road through open grassland. Reached 65 km/h on the straights. -- Talked about the bike-packing trip idea. Alessandro has started researching routes and accommodation. Looking like autumn is realistic. -- 114km in 4h15m. Solid ride, well-paced, great company. These are the rides you remember. diff --git a/demo-vault-v2/event-long-ride-2025-05-31.md b/demo-vault-v2/event-long-ride-2025-05-31.md deleted file mode 100644 index a2f23f93..00000000 --- a/demo-vault-v2/event-long-ride-2025-05-31.md +++ /dev/null @@ -1,21 +0,0 @@ ---- -aliases: ["Long ride — 2025-05-31"] -Is A: Event -Date: "2025-05-31" -Belongs to: "[[2025-05]]" -Related to: ["[[person-luca-rossi]]", "[[person-alessandro-ferrari]]"] -Tags: ["Health", "Sport"] ---- -# Long ride — 2025-05-31 -Long ride with Alessandro. 96km, 1165m elevation. - -## Notes -- End of May ride. Warm and slightly humid — 27°C, air thick with pollen. Both sneezed our way through the first 20km. -- Rode through the Chianti hills between Castellina and Greve, staying on the quieter secondary roads away from weekend traffic. -- Alessandro finished his TT series last week — 3rd overall in his age group. Very proud of the progress. His race power was 315W for 22 minutes. -- The vineyards are in full canopy now. The rows of vines form green walls along the road, creating a tunnel effect on the narrow lanes. -- Long stop at a farmhouse bar near Panzano. Shared a plate of bruschetta with fresh tomatoes and basil. Summer flavors on summer roads. -- 96km in 3h30m. Average power 195W. Comfortable ride to close out a strong month. May total: 480km across 5 long rides. - -## Follow-up -- [ ] Research bikepacking bags — need frame bag and seat pack for the autumn tour diff --git a/demo-vault-v2/event-long-ride-2025-06-07.md b/demo-vault-v2/event-long-ride-2025-06-07.md deleted file mode 100644 index 30bd2c86..00000000 --- a/demo-vault-v2/event-long-ride-2025-06-07.md +++ /dev/null @@ -1,19 +0,0 @@ ---- -aliases: ["Long ride — 2025-06-07"] -Is A: Event -Date: "2025-06-07" -Belongs to: "[[2025-06]]" -Related to: ["[[person-luca-rossi]]", "[[person-alessandro-ferrari]]"] -Tags: ["Health", "Sport"] ---- -# Long ride — 2025-06-07 -Long ride with Alessandro. 130km, 1442m elevation. - -## Notes -- Big June ride — 130km, the longest of the year so far. Headed south to Montalcino, then east through Sant'Angelo in Colle and Castelnuovo dell'Abate. -- Left at 5:30am to beat the heat. By 6am the sun was already warm. Summer is here — no doubt about it. -- Alessandro brought a new route he'd planned on Komoot. Several roads I'd never ridden, including a beautiful ridge road above the Orcia river. -- The new ridge road was spectacular — 15km of false flat with views on both sides, vineyards below, and no traffic at all. Added it to favorites immediately. -- Stopped at the abbey of Sant'Antimo for water and a 10-minute rest. The Romanesque architecture is stunning in the early morning light. -- Fueling was dialed — 90g carbs per hour, electrolytes in every bottle, a real food stop at km 80 for a panino. No fade at all. -- 130km in 4h50m. Both felt we had more in the tank. The early start and proper fueling make all the difference on big days. diff --git a/demo-vault-v2/event-long-ride-2025-06-14.md b/demo-vault-v2/event-long-ride-2025-06-14.md deleted file mode 100644 index b0e57554..00000000 --- a/demo-vault-v2/event-long-ride-2025-06-14.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -aliases: ["Long ride — 2025-06-14"] -Is A: Event -Date: "2025-06-14" -Belongs to: "[[2025-06]]" -Related to: ["[[person-luca-rossi]]", "[[person-alessandro-ferrari]]"] -Tags: ["Health", "Sport"] ---- -# Long ride — 2025-06-14 -Long ride with Alessandro. 116km, 1189m elevation. - -## Notes -- Mid-June ride through the Val d'Orcia. The wheat harvest has started — combines working in the fields, golden stubble left behind. -- Took the route through Pienza and Montepulciano, then a long loop back via Chianciano and Sarteano. Rolling terrain, scenic throughout. -- Alessandro is already planning the autumn bikepacking trip in detail — has mapped a 4-day route from Siena to Rome via the Via Francigena. Getting excited. -- Temperature hit 32°C by 10am. Poured water over our heads at every fountain. Summer riding demands respect for the heat. -- Stopped in Montepulciano at the gelateria near the fortress. Two scoops each — pistachio and stracciatella. Best mid-ride fuel in summer. -- Talked about overall training philosophy. Both agreed that consistency matters more than intensity. The riders who show up every weekend are the ones who get fast. -- 116km in 4h05m. Smooth, steady ride. Average power 200W, HR 145 bpm. Sweet spot between effort and enjoyment. - -## Follow-up -- [ ] Book accommodation for the Via Francigena bikepacking trip — autumn fills up fast diff --git a/demo-vault-v2/event-nonna-visit-2024-01-28.md b/demo-vault-v2/event-nonna-visit-2024-01-28.md deleted file mode 100644 index ce8240dd..00000000 --- a/demo-vault-v2/event-nonna-visit-2024-01-28.md +++ /dev/null @@ -1,17 +0,0 @@ ---- -aliases: ["Visita dalla Nonna — 2024-01-28"] -Is A: Event -Date: "2024-01-28" -Belongs to: "[[2024-01]]" -Related to: ["[[person-nonna-lucia]]"] -Tags: ["Personal", "Family"] ---- -# Visita dalla Nonna — 2024-01-28 -Visita mensile alla nonna a Lecco. Pranzo con risotto. - -## Notes -- Drive to Lecco was smooth, clear January sky with the mountains sharp against the blue -- Nonna made risotto alla milanese with ossobuco — her version is still unbeatable after all these years -- She told stories about her childhood winters in Lecco, when the lake would partially freeze -- She's in good health, walking to the market every morning by herself, fiercely independent as always -- "Dice sempre 'mangia, mangia!' e poi si preoccupa che mangio troppo" diff --git a/demo-vault-v2/event-nonna-visit-2024-02-25.md b/demo-vault-v2/event-nonna-visit-2024-02-25.md deleted file mode 100644 index 79b3e488..00000000 --- a/demo-vault-v2/event-nonna-visit-2024-02-25.md +++ /dev/null @@ -1,17 +0,0 @@ ---- -aliases: ["Visita dalla Nonna — 2024-02-25"] -Is A: Event -Date: "2024-02-25" -Belongs to: "[[2024-02]]" -Related to: ["[[person-nonna-lucia]]"] -Tags: ["Personal", "Family"] ---- -# Visita dalla Nonna — 2024-02-25 -Visita mensile alla nonna a Lecco. Pranzo con risotto. - -## Notes -- Rainy February drive, the lake was grey and moody but beautiful in its own way -- Nonna prepared polenta taragna with gorgonzola and salsiccia — perfect winter comfort food -- She mentioned her neighbor Signora Brambilla isn't doing well, she visits her every afternoon -- We looked through old photo albums together — found a picture of nonno at their wedding, nonna got quiet -- Left with a bag full of her homemade biscotti and a jar of preserved chestnuts diff --git a/demo-vault-v2/event-nonna-visit-2024-03-24.md b/demo-vault-v2/event-nonna-visit-2024-03-24.md deleted file mode 100644 index 6637684c..00000000 --- a/demo-vault-v2/event-nonna-visit-2024-03-24.md +++ /dev/null @@ -1,17 +0,0 @@ ---- -aliases: ["Visita dalla Nonna — 2024-03-24"] -Is A: Event -Date: "2024-03-24" -Belongs to: "[[2024-03]]" -Related to: ["[[person-nonna-lucia]]"] -Tags: ["Personal", "Family"] ---- -# Visita dalla Nonna — 2024-03-24 -Visita mensile alla nonna a Lecco. Pranzo con risotto. - -## Notes -- Palm Sunday visit — nonna had the olive branch by the front door, her house smelled of broth -- She made tortelli di zucca, a recipe she learned from her mother-in-law decades ago -- Talked about Easter preparations — she insists on making the colomba herself despite her age -- The first hints of spring along the lake, crocuses pushing through in her small garden -- "Mi ha detto: 'Quando ti sposi?' — come ogni volta" diff --git a/demo-vault-v2/event-nonna-visit-2024-03-31.md b/demo-vault-v2/event-nonna-visit-2024-03-31.md deleted file mode 100644 index e2ad65e0..00000000 --- a/demo-vault-v2/event-nonna-visit-2024-03-31.md +++ /dev/null @@ -1,17 +0,0 @@ ---- -aliases: ["Visita dalla Nonna — 2024-03-31"] -Is A: Event -Date: "2024-03-31" -Belongs to: "[[2024-03]]" -Related to: ["[[person-nonna-lucia]]"] -Tags: ["Personal", "Family"] ---- -# Visita dalla Nonna — 2024-03-31 -Visita mensile alla nonna a Lecco. Pranzo con risotto. - -## Notes -- Easter Sunday — the whole family gathered at nonna's for pranzo di Pasqua -- She made her legendary lasagna, layer upon layer of ragu, besciamella, and love -- The colomba she baked turned out perfectly — crusty on top, soft inside, she was so proud -- Nonna wore her best dress and her mother's brooch, she looked radiant -- After lunch we walked by the lake, the sun was warm and the mountains were snow-capped — a perfect Easter diff --git a/demo-vault-v2/event-nonna-visit-2024-04-28.md b/demo-vault-v2/event-nonna-visit-2024-04-28.md deleted file mode 100644 index 3af26a23..00000000 --- a/demo-vault-v2/event-nonna-visit-2024-04-28.md +++ /dev/null @@ -1,17 +0,0 @@ ---- -aliases: ["Visita dalla Nonna — 2024-04-28"] -Is A: Event -Date: "2024-04-28" -Belongs to: "[[2024-04]]" -Related to: ["[[person-nonna-lucia]]"] -Tags: ["Personal", "Family"] ---- -# Visita dalla Nonna — 2024-04-28 -Visita mensile alla nonna a Lecco. Pranzo con risotto. - -## Notes -- Beautiful spring drive along the lake, windows down, wildflowers on the hills -- Nonna made cotoletta alla milanese with insalata di patate — simple and perfect -- She was full of energy, had just reorganized her entire pantry -- Told me about a new priest at her parish who she thinks is "troppo giovane ma simpatico" -- We sat in her garden after lunch with espresso, watching the boats on the lake diff --git a/demo-vault-v2/event-nonna-visit-2024-05-26.md b/demo-vault-v2/event-nonna-visit-2024-05-26.md deleted file mode 100644 index 647cf98c..00000000 --- a/demo-vault-v2/event-nonna-visit-2024-05-26.md +++ /dev/null @@ -1,17 +0,0 @@ ---- -aliases: ["Visita dalla Nonna — 2024-05-26"] -Is A: Event -Date: "2024-05-26" -Belongs to: "[[2024-05]]" -Related to: ["[[person-nonna-lucia]]"] -Tags: ["Personal", "Family"] ---- -# Visita dalla Nonna — 2024-05-26 -Visita mensile alla nonna a Lecco. Pranzo con risotto. - -## Notes -- Late May warmth, the lake was sparkling and Lecco felt almost Mediterranean -- Nonna made vitello tonnato as antipasto and then risotto ai funghi porcini -- She mentioned her knees are bothering her on the stairs — gently suggested she see the doctor -- "Non ho bisogno del dottore, ho bisogno che vieni piu spesso" — classic nonna deflection -- Left feeling both happy and a little worried; she's strong but she's getting older diff --git a/demo-vault-v2/event-nonna-visit-2024-06-30.md b/demo-vault-v2/event-nonna-visit-2024-06-30.md deleted file mode 100644 index aa4d8a09..00000000 --- a/demo-vault-v2/event-nonna-visit-2024-06-30.md +++ /dev/null @@ -1,17 +0,0 @@ ---- -aliases: ["Visita dalla Nonna — 2024-06-30"] -Is A: Event -Date: "2024-06-30" -Belongs to: "[[2024-06]]" -Related to: ["[[person-nonna-lucia]]"] -Tags: ["Personal", "Family"] ---- -# Visita dalla Nonna — 2024-06-30 -Visita mensile alla nonna a Lecco. Pranzo con risotto. - -## Notes -- Hot summer day — nonna had all the shutters closed, the house cool and dim like a cave -- She prepared a cold lunch: insalata di riso, prosciutto e melone, and her famous torta di mele -- Signora Brambilla passed away last week — nonna was sad but composed, said "la vita e cosi" -- We sat inside mostly, she told stories about summers at the lake when she was young, swimming with her sisters -- Brought her a fan from Milan since hers broke, she was grateful but insisted she doesn't need "modern things" diff --git a/demo-vault-v2/event-nonna-visit-2024-07-28.md b/demo-vault-v2/event-nonna-visit-2024-07-28.md deleted file mode 100644 index 17d64f25..00000000 --- a/demo-vault-v2/event-nonna-visit-2024-07-28.md +++ /dev/null @@ -1,17 +0,0 @@ ---- -aliases: ["Visita dalla Nonna — 2024-07-28"] -Is A: Event -Date: "2024-07-28" -Belongs to: "[[2024-07]]" -Related to: ["[[person-nonna-lucia]]"] -Tags: ["Personal", "Family"] ---- -# Visita dalla Nonna — 2024-07-28 -Visita mensile alla nonna a Lecco. Pranzo con risotto. - -## Notes -- Peak summer heat, even Lecco felt tropical — nonna had the new fan running non-stop -- She made a light minestrone with vegetables from a neighbor's garden and bruschette with fresh tomatoes -- Talked about the Puglia trip coming up — she said "andate, divertitevi, io sto bene qui" -- She showed me a letter she found from nonno, written during his military service — tender and beautiful -- Her knees seem a bit better, she's been doing exercises the doctor finally convinced her to try diff --git a/demo-vault-v2/event-nonna-visit-2024-08-25.md b/demo-vault-v2/event-nonna-visit-2024-08-25.md deleted file mode 100644 index 4782be3b..00000000 --- a/demo-vault-v2/event-nonna-visit-2024-08-25.md +++ /dev/null @@ -1,17 +0,0 @@ ---- -aliases: ["Visita dalla Nonna — 2024-08-25"] -Is A: Event -Date: "2024-08-25" -Belongs to: "[[2024-08]]" -Related to: ["[[person-nonna-lucia]]"] -Tags: ["Personal", "Family"] ---- -# Visita dalla Nonna — 2024-08-25 -Visita mensile alla nonna a Lecco. Pranzo con risotto. - -## Notes -- Just back from Puglia, brought nonna taralli and olive oil from the south — she approved -- She made her classic risotto allo zafferano, golden and creamy, the benchmark all others are measured against -- Told her about the holiday — she listened to every detail, asked about the sea, the food, whether we got enough sun -- "Mi ha chiesto se ho trovato una ragazza in Puglia — le ho detto di no e ha sospirato" -- Late August breeze off the lake, summer winding down — these visits feel more precious each time diff --git a/demo-vault-v2/event-nonna-visit-2024-09-29.md b/demo-vault-v2/event-nonna-visit-2024-09-29.md deleted file mode 100644 index 016e04c8..00000000 --- a/demo-vault-v2/event-nonna-visit-2024-09-29.md +++ /dev/null @@ -1,17 +0,0 @@ ---- -aliases: ["Visita dalla Nonna — 2024-09-29"] -Is A: Event -Date: "2024-09-29" -Belongs to: "[[2024-09]]" -Related to: ["[[person-nonna-lucia]]"] -Tags: ["Personal", "Family"] ---- -# Visita dalla Nonna — 2024-09-29 -Visita mensile alla nonna a Lecco. Pranzo con risotto. - -## Notes -- Early autumn colors along the lake road — golden and copper, absolutely stunning -- Nonna made pizzoccheri, the hearty buckwheat pasta with potatoes, cabbage, and fontina from Valtellina -- She's been watching a lot of quiz shows on TV and has gotten surprisingly competitive about it -- We walked slowly to the lakefront after lunch, she held my arm — the view of Monte Resegone was crystal clear -- A moment of quiet gratitude sitting there together, watching the water diff --git a/demo-vault-v2/event-nonna-visit-2024-10-27.md b/demo-vault-v2/event-nonna-visit-2024-10-27.md deleted file mode 100644 index d12d3949..00000000 --- a/demo-vault-v2/event-nonna-visit-2024-10-27.md +++ /dev/null @@ -1,17 +0,0 @@ ---- -aliases: ["Visita dalla Nonna — 2024-10-27"] -Is A: Event -Date: "2024-10-27" -Belongs to: "[[2024-10]]" -Related to: ["[[person-nonna-lucia]]"] -Tags: ["Personal", "Family"] ---- -# Visita dalla Nonna — 2024-10-27 -Visita mensile alla nonna a Lecco. Pranzo con risotto. - -## Notes -- Foggy October drive, the lake appeared and disappeared through the mist — mysterious and beautiful -- Nonna prepared casoncelli alla bergamasca with burnt butter and sage, rich and comforting -- She asked about work — tried to explain what I do with computers, she nodded politely and said "l'importante e che ti piace" -- Her birthday is next month — she says she doesn't want a party but we're planning one anyway -- The house smelled of cinnamon and apples, she'd been baking all morning diff --git a/demo-vault-v2/event-nonna-visit-2024-11-24.md b/demo-vault-v2/event-nonna-visit-2024-11-24.md deleted file mode 100644 index d94a1de2..00000000 --- a/demo-vault-v2/event-nonna-visit-2024-11-24.md +++ /dev/null @@ -1,17 +0,0 @@ ---- -aliases: ["Visita dalla Nonna — 2024-11-24"] -Is A: Event -Date: "2024-11-24" -Belongs to: "[[2024-11]]" -Related to: ["[[person-nonna-lucia]]"] -Tags: ["Personal", "Family"] ---- -# Visita dalla Nonna — 2024-11-24 -Visita mensile alla nonna a Lecco. Pranzo con risotto. - -## Notes -- Birthday visit — the whole family came: mamma, papa, Elena, and me -- Nonna pretended to be surprised even though she definitely heard us coordinating on the phone -- Mamma brought the torta della nonna she baked, nonna said "e buona ma non come la mia" -- She blew out the candles with a wish she wouldn't tell us, but her eyes were shining -- The scarf mamma knitted fit perfectly — nonna wore it the rest of the day, even indoors diff --git a/demo-vault-v2/event-nonna-visit-2024-12-29.md b/demo-vault-v2/event-nonna-visit-2024-12-29.md deleted file mode 100644 index a07b6139..00000000 --- a/demo-vault-v2/event-nonna-visit-2024-12-29.md +++ /dev/null @@ -1,17 +0,0 @@ ---- -aliases: ["Visita dalla Nonna — 2024-12-29"] -Is A: Event -Date: "2024-12-29" -Belongs to: "[[2024-12]]" -Related to: ["[[person-nonna-lucia]]"] -Tags: ["Personal", "Family"] ---- -# Visita dalla Nonna — 2024-12-29 -Visita mensile alla nonna a Lecco. Pranzo con risotto. - -## Notes -- Post-Christmas visit, brought her a piece of the panettone from Como that papa loved -- Nonna had made cappelletti in brodo, the traditional holiday soup — her broth is like liquid gold -- She showed us her Christmas cards from friends and neighbors, neatly arranged on the mantelpiece -- Cold December day but her house was warm, the wood stove going, tinsel on the windowsill -- "Ha detto che il Natale piu bello e quando ci siamo tutti insieme — ha ragione" diff --git a/demo-vault-v2/event-nonna-visit-2025-01-26.md b/demo-vault-v2/event-nonna-visit-2025-01-26.md deleted file mode 100644 index b155bda5..00000000 --- a/demo-vault-v2/event-nonna-visit-2025-01-26.md +++ /dev/null @@ -1,17 +0,0 @@ ---- -aliases: ["Visita dalla Nonna — 2025-01-26"] -Is A: Event -Date: "2025-01-26" -Belongs to: "[[2025-01]]" -Related to: ["[[person-nonna-lucia]]"] -Tags: ["Personal", "Family"] ---- -# Visita dalla Nonna — 2025-01-26 -Visita mensile alla nonna a Lecco. Pranzo con risotto. - -## Notes -- Crisp January day, fresh snow on the peaks above Lecco — the drive was scenic -- Nonna made risotto al tastasal, the traditional pork-and-rice dish she only makes in deep winter -- She's been re-reading old novels — currently on "I Promessi Sposi," set right here in Lecco -- We talked about nonno, how he used to take her dancing at the circolo on Saturday nights -- Left with a container of her ribollita and strict instructions to eat it within two days diff --git a/demo-vault-v2/event-nonna-visit-2025-03-30.md b/demo-vault-v2/event-nonna-visit-2025-03-30.md deleted file mode 100644 index 450def63..00000000 --- a/demo-vault-v2/event-nonna-visit-2025-03-30.md +++ /dev/null @@ -1,17 +0,0 @@ ---- -aliases: ["Visita dalla Nonna — 2025-03-30"] -Is A: Event -Date: "2025-03-30" -Belongs to: "[[2025-03]]" -Related to: ["[[person-nonna-lucia]]"] -Tags: ["Personal", "Family"] ---- -# Visita dalla Nonna — 2025-03-30 -Visita mensile alla nonna a Lecco. Pranzo con risotto. - -## Notes -- Spring is arriving at the lake — nonna's garden has daffodils pushing up, she was pointing them out proudly -- She prepared agnolotti del plin in butter and sage, tiny and delicate — a labor of love -- Talked about Easter plans, she wants to host again but we convinced her to come to our parents' house instead -- "Dice che sta invecchiando, poi si alza e va a prendere il dolce come se avesse vent'anni" -- The lake was pale blue and calm, almost turquoise near the shore — one of those days you photograph with your eyes diff --git a/demo-vault-v2/event-nonna-visit-2025-04-27.md b/demo-vault-v2/event-nonna-visit-2025-04-27.md deleted file mode 100644 index 870c9751..00000000 --- a/demo-vault-v2/event-nonna-visit-2025-04-27.md +++ /dev/null @@ -1,17 +0,0 @@ ---- -aliases: ["Visita dalla Nonna — 2025-04-27"] -Is A: Event -Date: "2025-04-27" -Belongs to: "[[2025-04]]" -Related to: ["[[person-nonna-lucia]]"] -Tags: ["Personal", "Family"] ---- -# Visita dalla Nonna — 2025-04-27 -Visita mensile alla nonna a Lecco. Pranzo con risotto. - -## Notes -- Post-Easter visit, brought her leftover colomba from mamma's kitchen — she critiqued it lovingly -- Nonna made frittata di asparagi with asparagus from the market and a side of patate al forno -- She was in high spirits, said Easter at our parents' house was "quasi bello come a casa mia" -- Her garden is in full bloom — roses, herbs, the jasmine climbing the wall -- We sat outside in the April sun, she told me about a dream she had about nonno, smiling the whole time diff --git a/demo-vault-v2/event-nonna-visit-2025-05-25.md b/demo-vault-v2/event-nonna-visit-2025-05-25.md deleted file mode 100644 index 6d47f149..00000000 --- a/demo-vault-v2/event-nonna-visit-2025-05-25.md +++ /dev/null @@ -1,17 +0,0 @@ ---- -aliases: ["Visita dalla Nonna — 2025-05-25"] -Is A: Event -Date: "2025-05-25" -Belongs to: "[[2025-05]]" -Related to: ["[[person-nonna-lucia]]"] -Tags: ["Personal", "Family"] ---- -# Visita dalla Nonna — 2025-05-25 -Visita mensile alla nonna a Lecco. Pranzo con risotto. - -## Notes -- Gorgeous late May day, drove with the windows down, the mountains green and lush -- Nonna made her famous pollo alla cacciatora with roasted peppers — the whole neighborhood could probably smell it -- She's been helping a new young family on her street, bringing them food and advice — still the nonna of the block -- We walked to the gelateria by the lake, she had nocciola, I had limone — a perfect tradition -- "Mi ha stretto il braccio e ha detto 'sei un bravo ragazzo' — queste visite mi riempiono il cuore" diff --git a/demo-vault-v2/event-podcast-rec-2024-02-01.md b/demo-vault-v2/event-podcast-rec-2024-02-01.md deleted file mode 100644 index fe094dab..00000000 --- a/demo-vault-v2/event-podcast-rec-2024-02-01.md +++ /dev/null @@ -1,24 +0,0 @@ ---- -aliases: ["Podcast recording — 2024-02-01"] -Is A: Event -Date: "2024-02-01" -Belongs to: "[[2024-02]]" -Related to: ["[[person-sarah-oconnor]]"] -Tags: ["Work", "Podcast"] ---- -# Podcast recording — 2024-02-01 -Recorded episode with Sarah O'Connor. Great conversation. - -## Notes -- Episode theme: building resilient engineering cultures in hypergrowth startups -- Sarah shared her experience scaling the platform team at her previous company from 12 to 80 engineers in 18 months, including the organizational pain points that emerged around the 40-person mark -- Her background in both infrastructure engineering and people management gave her a unique lens on why technical leaders often underestimate the cultural debt that accumulates during rapid hiring -- Excellent chemistry throughout the session — the conversation flowed naturally and we barely needed to redirect; ran about 15 minutes long but the extra material is strong -- Memorable insight: "The best architecture decision you can make at scale is hiring someone who will disagree with you and giving them the authority to act on it" -- Audio quality was clean on both ends; recorded via Riverside with local backup tracks - -## Follow-up -- [ ] Send thank-you email to Sarah -- [ ] Draft show notes and pull key timestamps for chapter markers -- [ ] Schedule editing session with [[person-paco-furiani]] -- [ ] Create social media clips — the quote about hiring disagreeable people is highly shareable diff --git a/demo-vault-v2/event-podcast-rec-2024-02-15.md b/demo-vault-v2/event-podcast-rec-2024-02-15.md deleted file mode 100644 index b044659f..00000000 --- a/demo-vault-v2/event-podcast-rec-2024-02-15.md +++ /dev/null @@ -1,23 +0,0 @@ ---- -aliases: ["Podcast recording — 2024-02-15"] -Is A: Event -Date: "2024-02-15" -Belongs to: "[[2024-02]]" -Related to: ["[[person-diego-santos]]"] -Tags: ["Work", "Podcast"] ---- -# Podcast recording — 2024-02-15 -Recorded episode with Diego Santos. Great conversation. - -## Notes -- Episode theme: the intersection of developer experience and platform engineering -- Diego walked through how his team built an internal developer portal that reduced onboarding time from two weeks to two days, with concrete metrics on developer satisfaction scores before and after -- His background running DevRel at a major cloud provider gave him strong opinions on what developers actually need versus what platform teams assume they need -- Good energy overall, though the first 10 minutes were a bit slow as Diego was warming up — may want to trim the intro during editing -- Standout moment: his analogy comparing internal platforms to public transit systems — "Nobody thanks the bus driver, but everyone notices when the bus is late" -- Recorded on Riverside; slight echo on Diego's end for the first few minutes until he switched to his wired headset - -## Follow-up -- [ ] Send thank-you email to Diego with link to the raw recording -- [ ] Draft show notes emphasizing the developer portal case study -- [ ] Schedule editing with [[person-paco-furiani]] — flag the audio issue in the first segment diff --git a/demo-vault-v2/event-podcast-rec-2024-02-29.md b/demo-vault-v2/event-podcast-rec-2024-02-29.md deleted file mode 100644 index 2568812d..00000000 --- a/demo-vault-v2/event-podcast-rec-2024-02-29.md +++ /dev/null @@ -1,24 +0,0 @@ ---- -aliases: ["Podcast recording — 2024-02-29"] -Is A: Event -Date: "2024-02-29" -Belongs to: "[[2024-02]]" -Related to: ["[[person-adeel-khan]]"] -Tags: ["Work", "Podcast"] ---- -# Podcast recording — 2024-02-29 -Recorded episode with Adeel Khan. Great conversation. - -## Notes -- Episode theme: navigating the shift from monolith to microservices without losing velocity -- Adeel described the three-year migration journey at his fintech company, including the critical mistake of trying to decompose too many services at once and the rollback strategy they had to implement mid-migration -- His CTO perspective was valuable — he spoke candidly about the political dynamics of convincing the board to invest in infrastructure work that has no visible product impact for 6+ months -- Excellent episode overall; very tight and focused, finished right at the 50-minute mark with no real dead spots -- Key quote: "Every microservice boundary is a communication boundary. If your org chart doesn't match your service graph, you're going to have a bad time" -- Clean audio on both sides; Adeel had a professional podcast setup with treated room acoustics - -## Follow-up -- [ ] Send thank-you email to Adeel and ask if he has any internal diagrams we can reference in show notes -- [ ] Draft show notes with the migration timeline as a visual element -- [ ] Schedule editing with [[person-paco-furiani]] -- [ ] Create social media clips — the Conway's Law angle will resonate with the audience diff --git a/demo-vault-v2/event-podcast-rec-2024-03-14.md b/demo-vault-v2/event-podcast-rec-2024-03-14.md deleted file mode 100644 index aff6b60f..00000000 --- a/demo-vault-v2/event-podcast-rec-2024-03-14.md +++ /dev/null @@ -1,23 +0,0 @@ ---- -aliases: ["Podcast recording — 2024-03-14"] -Is A: Event -Date: "2024-03-14" -Belongs to: "[[2024-03]]" -Related to: ["[[person-matteo-gentile]]"] -Tags: ["Work", "Podcast"] ---- -# Podcast recording — 2024-03-14 -Recorded episode with Matteo Gentile. Great conversation. - -## Notes -- Episode theme: the role of technical debt in product strategy and how to make it visible to non-technical stakeholders -- Matteo presented a framework he developed for quantifying technical debt in terms of opportunity cost — translating code complexity metrics into projected delays on upcoming features -- His dual background in software architecture and product management made this an unusually business-oriented conversation for the show, which is a welcome change of pace -- Strong recording session with natural back-and-forth; Matteo is an engaging storyteller who illustrates abstract concepts with concrete war stories from his consulting work -- Memorable line: "Technical debt is not a mess you made — it's a loan you took. The problem is most teams never read the interest rate" -- Audio was solid throughout; both on Riverside with backup tracks, no issues detected - -## Follow-up -- [ ] Send thank-you email to Matteo and request his debt quantification spreadsheet template for the show notes -- [ ] Draft show notes focusing on the framework and practical takeaways -- [ ] Schedule editing with [[person-paco-furiani]] diff --git a/demo-vault-v2/event-podcast-rec-2024-03-28.md b/demo-vault-v2/event-podcast-rec-2024-03-28.md deleted file mode 100644 index ea20d326..00000000 --- a/demo-vault-v2/event-podcast-rec-2024-03-28.md +++ /dev/null @@ -1,24 +0,0 @@ ---- -aliases: ["Podcast recording — 2024-03-28"] -Is A: Event -Date: "2024-03-28" -Belongs to: "[[2024-03]]" -Related to: ["[[person-andrea-provaglio]]"] -Tags: ["Work", "Podcast"] ---- -# Podcast recording — 2024-03-28 -Recorded episode with Andrea Provaglio. Great conversation. - -## Notes -- Episode theme: systems thinking applied to engineering organizations — treating teams as complex adaptive systems rather than machines -- Andrea drew on his coaching background to explain why traditional management approaches fail in knowledge work, using examples from organizations he has worked with across Europe and the US -- His perspective as both a former developer and an organizational coach gave the conversation a depth that purely technical guests rarely achieve — he challenged several assumptions I had about team productivity metrics -- The session ran about 20 minutes over our planned time, but the extra content is some of the strongest material we have recorded this quarter; will likely split into a two-part episode -- Powerful insight: "You cannot optimize a system by optimizing its parts independently. Every time you speed up one team, you create a bottleneck somewhere else" -- Audio quality was excellent; Andrea recorded from his home studio with professional-grade equipment - -## Follow-up -- [ ] Send thank-you email to Andrea and discuss whether he is open to a follow-up part two -- [ ] Draft show notes — consider splitting into two episodes given the length and density of content -- [ ] Schedule editing with [[person-paco-furiani]] and flag the two-part option -- [ ] Create social media clips from the systems thinking segment diff --git a/demo-vault-v2/event-podcast-rec-2024-04-11.md b/demo-vault-v2/event-podcast-rec-2024-04-11.md deleted file mode 100644 index e0adf929..00000000 --- a/demo-vault-v2/event-podcast-rec-2024-04-11.md +++ /dev/null @@ -1,24 +0,0 @@ ---- -aliases: ["Podcast recording — 2024-04-11"] -Is A: Event -Date: "2024-04-11" -Belongs to: "[[2024-04]]" -Related to: ["[[person-lucia-martinez]]"] -Tags: ["Work", "Podcast"] ---- -# Podcast recording — 2024-04-11 -Recorded episode with Lucia Martinez. Great conversation. - -## Notes -- Episode theme: diversity in engineering leadership and the structural barriers that prevent underrepresented groups from reaching principal engineer and VP-level roles -- Lucia shared data from her research on promotion patterns at large tech companies, revealing that the biggest drop-off happens at the senior-to-staff transition, not at the entry level as commonly assumed -- Her background leading DEI initiatives at a Fortune 500 tech company while simultaneously serving as a staff engineer gave her credibility that pure HR-focused guests often lack -- Very candid conversation — Lucia did not shy away from naming specific failure modes she has witnessed, which makes this episode feel authentic rather than performative -- Key quote: "Mentorship without sponsorship is just friendship. If nobody is putting your name forward in rooms you are not in, nothing changes" -- Clean audio; recorded via Riverside with no technical issues - -## Follow-up -- [ ] Send thank-you email to Lucia and ask permission to link to her published research -- [ ] Draft show notes with references to the studies she cited -- [ ] Schedule editing with [[person-paco-furiani]] -- [ ] Create social media clips — the mentorship vs sponsorship distinction will drive engagement diff --git a/demo-vault-v2/event-podcast-rec-2024-04-25.md b/demo-vault-v2/event-podcast-rec-2024-04-25.md deleted file mode 100644 index add00504..00000000 --- a/demo-vault-v2/event-podcast-rec-2024-04-25.md +++ /dev/null @@ -1,23 +0,0 @@ ---- -aliases: ["Podcast recording — 2024-04-25"] -Is A: Event -Date: "2024-04-25" -Belongs to: "[[2024-04]]" -Related to: ["[[person-nina-petersen]]"] -Tags: ["Work", "Podcast"] ---- -# Podcast recording — 2024-04-25 -Recorded episode with Nina Petersen. Great conversation. - -## Notes -- Episode theme: observability-driven development and how modern teams should think about instrumenting code from day one rather than bolting on monitoring after the fact -- Nina walked through a real incident postmortem from her time at a large-scale e-commerce platform, showing how proper distributed tracing would have reduced their mean time to resolution from 4 hours to under 20 minutes -- Her background as both an SRE lead and an open-source contributor to OpenTelemetry gave her deep technical credibility — she could speak to both the theory and the implementation details -- Good pacing throughout the episode; Nina is concise and structured in her answers, which will make editing straightforward -- Standout insight: "If your first instinct during an incident is to SSH into a box and tail a log file, your observability stack has failed you" -- Audio quality was very good; minor background noise from construction near Nina's office in the first 5 minutes, but it cleared up - -## Follow-up -- [ ] Send thank-you email to Nina with the recording link -- [ ] Draft show notes and include links to the OpenTelemetry resources she mentioned -- [ ] Schedule editing with [[person-paco-furiani]] — note the minor background noise at the start diff --git a/demo-vault-v2/event-podcast-rec-2024-05-09.md b/demo-vault-v2/event-podcast-rec-2024-05-09.md deleted file mode 100644 index 84343754..00000000 --- a/demo-vault-v2/event-podcast-rec-2024-05-09.md +++ /dev/null @@ -1,24 +0,0 @@ ---- -aliases: ["Podcast recording — 2024-05-09"] -Is A: Event -Date: "2024-05-09" -Belongs to: "[[2024-05]]" -Related to: ["[[person-francesca-deluca]]"] -Tags: ["Work", "Podcast"] ---- -# Podcast recording — 2024-05-09 -Recorded episode with Francesca De Luca. Great conversation. - -## Notes -- Episode theme: the art and science of API design — building interfaces that developers actually want to use -- Francesca shared lessons from designing the public API at her developer tools company, including the decision to adopt a spec-first approach with OpenAPI and how that changed their entire development workflow -- Her background in both backend engineering and developer advocacy meant she could speak fluently about technical trade-offs while keeping the conversation accessible to a broader audience -- Very polished session — Francesca clearly prepared well and brought specific examples and anecdotes; the episode practically edits itself -- Memorable quote: "A good API is like a good joke — if you have to explain it, it is not working" -- Pristine audio quality on both ends; Francesca recorded from a professional podcast studio - -## Follow-up -- [ ] Send thank-you email to Francesca -- [ ] Draft show notes with the API design principles she outlined as a checklist -- [ ] Schedule editing with [[person-paco-furiani]] -- [ ] Create social media clips — the API-as-joke analogy will play well on social diff --git a/demo-vault-v2/event-podcast-rec-2024-05-23.md b/demo-vault-v2/event-podcast-rec-2024-05-23.md deleted file mode 100644 index 3670180d..00000000 --- a/demo-vault-v2/event-podcast-rec-2024-05-23.md +++ /dev/null @@ -1,23 +0,0 @@ ---- -aliases: ["Podcast recording — 2024-05-23"] -Is A: Event -Date: "2024-05-23" -Belongs to: "[[2024-05]]" -Related to: ["[[person-james-murphy]]"] -Tags: ["Work", "Podcast"] ---- -# Podcast recording — 2024-05-23 -Recorded episode with James Murphy. Great conversation. - -## Notes -- Episode theme: remote-first engineering teams and the tooling, rituals, and cultural practices that make distributed work actually effective -- James described the transition his 200-person engineering org made from office-first to fully remote during 2020, and more importantly, the intentional redesign they did in 2022 when they realized their initial remote setup was just "office work over Zoom" -- His VP of Engineering perspective was grounded in real operational data — he shared specific metrics on cycle time, deployment frequency, and developer satisfaction before and after their remote redesign -- Solid recording with good energy; James has a natural podcast presence and keeps answers focused without being terse -- Key insight: "Async-first does not mean slow. It means thoughtful. The fastest teams I have seen are the ones where nobody is waiting for a meeting to make a decision" -- Clean audio throughout; James recorded from a quiet home office with a high-quality USB microphone - -## Follow-up -- [ ] Send thank-you email to James -- [ ] Draft show notes highlighting the remote redesign framework -- [ ] Schedule editing with [[person-paco-furiani]] diff --git a/demo-vault-v2/event-podcast-rec-2024-06-06.md b/demo-vault-v2/event-podcast-rec-2024-06-06.md deleted file mode 100644 index 8a8e25cb..00000000 --- a/demo-vault-v2/event-podcast-rec-2024-06-06.md +++ /dev/null @@ -1,24 +0,0 @@ ---- -aliases: ["Podcast recording — 2024-06-06"] -Is A: Event -Date: "2024-06-06" -Belongs to: "[[2024-06]]" -Related to: ["[[person-james-murphy]]"] -Tags: ["Work", "Podcast"] ---- -# Podcast recording — 2024-06-06 -Recorded episode with James Murphy. Great conversation. - -## Notes -- Episode theme: follow-up session with James on engineering team rituals — deep dive into design reviews, RFC processes, and blameless postmortems -- This second recording picks up where the previous episode left off, focusing specifically on the written communication practices that make remote engineering orgs function at a high level -- James brought concrete examples of RFC templates and design doc formats his team uses, along with metrics on how many RFCs lead to actual implementation versus getting abandoned -- Great chemistry again — the rapport from the first session carried over and we were able to go deeper on controversial topics like whether code reviews are worth the time investment at scale -- Standout quote: "An RFC that nobody comments on is worse than an RFC that gets rejected. Silence means nobody cares, and that is the real organizational failure" -- Audio quality consistent with the previous session; clean and professional on both ends - -## Follow-up -- [ ] Send James the final cut of part one before publishing this follow-up -- [ ] Draft show notes linking both episodes together as a series -- [ ] Schedule editing with [[person-paco-furiani]] — coordinate release timing with the first episode -- [ ] Create social media clips comparing key points from both sessions diff --git a/demo-vault-v2/event-podcast-rec-2024-06-20.md b/demo-vault-v2/event-podcast-rec-2024-06-20.md deleted file mode 100644 index d66c2084..00000000 --- a/demo-vault-v2/event-podcast-rec-2024-06-20.md +++ /dev/null @@ -1,24 +0,0 @@ ---- -aliases: ["Podcast recording — 2024-06-20"] -Is A: Event -Date: "2024-06-20" -Belongs to: "[[2024-06]]" -Related to: ["[[person-marco-cecconi]]"] -Tags: ["Work", "Podcast"] ---- -# Podcast recording — 2024-06-20 -Recorded episode with Marco Cecconi. Great conversation. - -## Notes -- Episode theme: lessons from building and scaling Stack Overflow's architecture — what worked, what they would do differently, and how the landscape has changed since -- Marco shared detailed technical stories about the performance optimization culture at Stack Overflow, including their famous approach of running one of the world's largest sites on a surprisingly small number of servers -- His deep experience with .NET at scale and his pragmatic approach to technology choices made for a conversation that challenged the "always use microservices" orthodoxy that dominates the industry -- Exceptional recording — Marco is an incredibly articulate speaker who combines technical depth with humor; this will likely be one of our most popular episodes -- Memorable quote: "The best performance optimization is the code you never write. Every abstraction layer is a tax on your users, and most of them are not paying for the feature you think they are" -- Perfect audio quality; Marco recorded from a professional setup in his home office - -## Follow-up -- [ ] Send thank-you email to Marco -- [ ] Draft show notes with architecture diagrams if Marco can share any publicly -- [ ] Schedule editing with [[person-paco-furiani]] — this one should be a priority given its quality -- [ ] Create social media clips — the performance optimization segment is gold diff --git a/demo-vault-v2/event-podcast-rec-2024-07-04.md b/demo-vault-v2/event-podcast-rec-2024-07-04.md deleted file mode 100644 index a0a98d53..00000000 --- a/demo-vault-v2/event-podcast-rec-2024-07-04.md +++ /dev/null @@ -1,23 +0,0 @@ ---- -aliases: ["Podcast recording — 2024-07-04"] -Is A: Event -Date: "2024-07-04" -Belongs to: "[[2024-07]]" -Related to: ["[[person-elena-konstantinou]]"] -Tags: ["Work", "Podcast"] ---- -# Podcast recording — 2024-07-04 -Recorded episode with Elena Konstantinou. Great conversation. - -## Notes -- Episode theme: the evolution of CI/CD pipelines and why most teams are still doing continuous deployment wrong -- Elena walked through a maturity model she developed for deployment pipelines, from basic build automation through canary deployments to full progressive delivery with feature flags and automated rollback -- Her background running platform teams at multiple scale-ups across Europe gave her a broad comparative view — she could point to patterns that succeed across different tech stacks and organizational sizes -- Energetic session with strong opinions; Elena is not afraid to call out industry hype, which makes for compelling listening even if some viewers may disagree -- Key insight: "If your deployment pipeline takes more than 15 minutes, you do not have continuous delivery. You have batch processing with extra steps" -- Good audio overall; slight room reverb on Elena's end but nothing that will require significant post-processing - -## Follow-up -- [ ] Send thank-you email to Elena and request the maturity model document for show notes -- [ ] Draft show notes with the pipeline maturity levels as a visual -- [ ] Schedule editing with [[person-paco-furiani]] diff --git a/demo-vault-v2/event-podcast-rec-2024-07-18.md b/demo-vault-v2/event-podcast-rec-2024-07-18.md deleted file mode 100644 index fa28d96e..00000000 --- a/demo-vault-v2/event-podcast-rec-2024-07-18.md +++ /dev/null @@ -1,24 +0,0 @@ ---- -aliases: ["Podcast recording — 2024-07-18"] -Is A: Event -Date: "2024-07-18" -Belongs to: "[[2024-07]]" -Related to: ["[[person-yusuf-osman]]"] -Tags: ["Work", "Podcast"] ---- -# Podcast recording — 2024-07-18 -Recorded episode with Yusuf Osman. Great conversation. - -## Notes -- Episode theme: building developer communities in emerging tech ecosystems — lessons from growing a thriving open-source community from zero to 10,000 contributors -- Yusuf shared the playbook he used to build community around an open-source infrastructure project, including the counterintuitive decision to slow down feature development in order to invest in documentation and contributor experience -- His background spans both community management and core engineering, which meant he could address the tension between community requests and architectural integrity with genuine nuance -- Very warm and thoughtful session; Yusuf's communication style is calm and measured, which contrasts nicely with our more high-energy episodes — good variety for the feed -- Standout quote: "Open source is not free. Someone is always paying — either with money, time, or burnout. The sustainable projects are the ones that are honest about which currency they are using" -- Clean audio; Yusuf recorded from a co-working space but managed to find a quiet room with good acoustics - -## Follow-up -- [ ] Send thank-you email to Yusuf -- [ ] Draft show notes with links to his open-source project and contributor guidelines -- [ ] Schedule editing with [[person-paco-furiani]] -- [ ] Create social media clips — the open-source sustainability angle is timely diff --git a/demo-vault-v2/event-podcast-rec-2024-08-01.md b/demo-vault-v2/event-podcast-rec-2024-08-01.md deleted file mode 100644 index d24cc0a6..00000000 --- a/demo-vault-v2/event-podcast-rec-2024-08-01.md +++ /dev/null @@ -1,23 +0,0 @@ ---- -aliases: ["Podcast recording — 2024-08-01"] -Is A: Event -Date: "2024-08-01" -Belongs to: "[[2024-08]]" -Related to: ["[[person-piergiorgio-conte]]"] -Tags: ["Work", "Podcast"] ---- -# Podcast recording — 2024-08-01 -Recorded episode with Piergiorgio Conte. Great conversation. - -## Notes -- Episode theme: the intersection of data engineering and machine learning operations — building reliable ML pipelines that actually make it to production -- Piergiorgio shared war stories from deploying ML models in a regulated financial services environment, including the compliance and auditability challenges that most MLOps content completely ignores -- His background combining traditional data engineering with modern ML infrastructure gave the conversation a practical grounding that pure research-focused guests often miss -- Solid episode that will appeal strongly to our data engineering audience segment; Piergiorgio is methodical in his explanations and provides clear, actionable frameworks -- Key quote: "Ninety percent of ML projects fail not because the model is wrong, but because the data pipeline is unreliable. Fix your plumbing before you tune your hyperparameters" -- Audio was good; Piergiorgio recorded via Riverside from his office in Milan with a decent condenser microphone - -## Follow-up -- [ ] Send thank-you email to Piergiorgio -- [ ] Draft show notes emphasizing the MLOps pipeline architecture he described -- [ ] Schedule editing with [[person-paco-furiani]] diff --git a/demo-vault-v2/event-podcast-rec-2024-08-15.md b/demo-vault-v2/event-podcast-rec-2024-08-15.md deleted file mode 100644 index 774b8351..00000000 --- a/demo-vault-v2/event-podcast-rec-2024-08-15.md +++ /dev/null @@ -1,24 +0,0 @@ ---- -aliases: ["Podcast recording — 2024-08-15"] -Is A: Event -Date: "2024-08-15" -Belongs to: "[[2024-08]]" -Related to: ["[[person-priya-sharma]]"] -Tags: ["Work", "Podcast"] ---- -# Podcast recording — 2024-08-15 -Recorded episode with Priya Sharma. Great conversation. - -## Notes -- Episode theme: scaling mobile engineering teams and the unique challenges of shipping on platforms you do not control (iOS and Android release cycles, app store review, etc.) -- Priya described how her team restructured their mobile development workflow to support bi-weekly releases across both platforms, including the feature flag infrastructure and automated testing pipeline that made it possible -- Her experience as a mobile engineering director at a consumer fintech company gave her practical insights into the regulatory and security constraints that add complexity beyond what typical mobile development content covers -- Very well-paced recording; Priya is a natural communicator who balances technical detail with strategic thinking seamlessly -- Memorable insight: "The app store is your deployment pipeline's final boss. If you are not designing your release process around review times and rejection risks, you are going to have a bad quarter" -- Excellent audio quality; Priya recorded from a sound-treated room with a professional microphone setup - -## Follow-up -- [ ] Send thank-you email to Priya -- [ ] Draft show notes with the bi-weekly release workflow diagram she mentioned -- [ ] Schedule editing with [[person-paco-furiani]] -- [ ] Create social media clips — the app store as "final boss" framing will resonate with mobile devs diff --git a/demo-vault-v2/event-podcast-rec-2024-08-29.md b/demo-vault-v2/event-podcast-rec-2024-08-29.md deleted file mode 100644 index 84d957e8..00000000 --- a/demo-vault-v2/event-podcast-rec-2024-08-29.md +++ /dev/null @@ -1,23 +0,0 @@ ---- -aliases: ["Podcast recording — 2024-08-29"] -Is A: Event -Date: "2024-08-29" -Belongs to: "[[2024-08]]" -Related to: ["[[person-priya-sharma]]"] -Tags: ["Work", "Podcast"] ---- -# Podcast recording — 2024-08-29 -Recorded episode with Priya Sharma. Great conversation. - -## Notes -- Episode theme: part two with Priya — deep dive into testing strategies for mobile apps, including the role of visual regression testing and real-device testing farms -- Building on the previous episode about release workflows, Priya explained her team's testing pyramid for mobile: heavy unit tests at the base, integration tests with mocked backends in the middle, and a lean set of end-to-end tests on real devices at the top -- Her candid assessment of the limitations of emulator-based testing versus real-device testing was particularly valuable — she shared specific bugs that would have shipped to production if they had relied solely on simulators -- Another strong session; the continuity from the first recording made the conversation feel more like a masterclass than an interview -- Key quote: "If you are only testing on emulators, you are testing your assumption of what a phone is, not what your users actually have in their hands" -- Audio quality matched the first session — clean and professional throughout - -## Follow-up -- [ ] Send thank-you email to Priya with links to both episode recordings -- [ ] Draft show notes connecting both episodes as a mobile engineering series -- [ ] Schedule editing with [[person-paco-furiani]] — coordinate release with part one diff --git a/demo-vault-v2/event-podcast-rec-2024-09-12.md b/demo-vault-v2/event-podcast-rec-2024-09-12.md deleted file mode 100644 index 4ea678c9..00000000 --- a/demo-vault-v2/event-podcast-rec-2024-09-12.md +++ /dev/null @@ -1,24 +0,0 @@ ---- -aliases: ["Podcast recording — 2024-09-12"] -Is A: Event -Date: "2024-09-12" -Belongs to: "[[2024-09]]" -Related to: ["[[person-hiroshi-tanaka]]"] -Tags: ["Work", "Podcast"] ---- -# Podcast recording — 2024-09-12 -Recorded episode with Hiroshi Tanaka. Great conversation. - -## Notes -- Episode theme: engineering leadership in Japan's tech scene — bridging traditional corporate culture with modern agile practices -- Hiroshi shared his experience introducing continuous delivery and cross-functional teams at a large Japanese enterprise, including the cultural considerations that Western agile frameworks rarely address -- His perspective as someone who has worked in both Silicon Valley and Tokyo gave him a unique ability to compare organizational patterns without falling into cultural stereotypes — very thoughtful and nuanced throughout -- Fascinating episode that expands our show's geographic perspective; Hiroshi is articulate in English and chose his words carefully, which gave the conversation a reflective quality -- Standout insight: "In Japan, consensus is not the enemy of speed. It is the precondition for speed. When everyone understands the decision, execution is almost instant" -- Good audio quality; recorded via Riverside with a slight time zone challenge (early morning for Hiroshi) but no technical issues - -## Follow-up -- [ ] Send thank-you email to Hiroshi -- [ ] Draft show notes highlighting the cross-cultural engineering leadership themes -- [ ] Schedule editing with [[person-paco-furiani]] -- [ ] Create social media clips — the consensus vs speed framing will generate discussion diff --git a/demo-vault-v2/event-podcast-rec-2024-09-26.md b/demo-vault-v2/event-podcast-rec-2024-09-26.md deleted file mode 100644 index 4cd77595..00000000 --- a/demo-vault-v2/event-podcast-rec-2024-09-26.md +++ /dev/null @@ -1,23 +0,0 @@ ---- -aliases: ["Podcast recording — 2024-09-26"] -Is A: Event -Date: "2024-09-26" -Belongs to: "[[2024-09]]" -Related to: ["[[person-elena-konstantinou]]"] -Tags: ["Work", "Podcast"] ---- -# Podcast recording — 2024-09-26 -Recorded episode with Elena Konstantinou. Great conversation. - -## Notes -- Episode theme: second session with Elena — this time focused on infrastructure as code practices and the evolution from Terraform to newer tools like Pulumi and CDK -- Elena provided a comparative analysis of IaC approaches she has seen work across different organizational contexts, with honest assessments of where Terraform still excels and where newer alternatives offer genuine advantages -- Her hands-on experience migrating a large-scale Terraform codebase to Pulumi gave her credibility to discuss the trade-offs without it feeling like vendor advocacy -- Excellent technical depth while remaining accessible; Elena has a talent for explaining complex infrastructure concepts with relatable analogies -- Key quote: "Infrastructure as code solved the 'it works on my machine' problem for servers. But now we have a new problem: 'it works in my Terraform state file'" -- Audio was cleaner than the first session — Elena set up in a better room this time with improved acoustics - -## Follow-up -- [ ] Send thank-you email to Elena -- [ ] Draft show notes with a comparison table of IaC tools she discussed -- [ ] Schedule editing with [[person-paco-furiani]] diff --git a/demo-vault-v2/event-podcast-rec-2024-10-10.md b/demo-vault-v2/event-podcast-rec-2024-10-10.md deleted file mode 100644 index f09e35f8..00000000 --- a/demo-vault-v2/event-podcast-rec-2024-10-10.md +++ /dev/null @@ -1,24 +0,0 @@ ---- -aliases: ["Podcast recording — 2024-10-10"] -Is A: Event -Date: "2024-10-10" -Belongs to: "[[2024-10]]" -Related to: ["[[person-diego-santos]]"] -Tags: ["Work", "Podcast"] ---- -# Podcast recording — 2024-10-10 -Recorded episode with Diego Santos. Great conversation. - -## Notes -- Episode theme: return visit with Diego — this time focused on the emerging role of AI-assisted development tools and how they are changing developer workflows -- Diego shared early results from a pilot program at his company where they rolled out GitHub Copilot to 50 developers and tracked productivity metrics over three months, including the surprising finding that senior developers benefited more than juniors -- His DevRel background made him especially attuned to the gap between how AI tools are marketed versus how developers actually use them in practice -- High-energy session with some genuinely provocative takes; Diego pushed back hard on the narrative that AI will replace developers, arguing instead that it raises the floor on code quality while potentially lowering the ceiling on architectural thinking -- Memorable quote: "Copilot is the best junior developer you have ever paired with — and the worst senior developer. Know which one you need before you hit Tab" -- Clean audio; Diego fixed the echo issue from his previous recording by switching to a dedicated headset - -## Follow-up -- [ ] Send thank-you email to Diego -- [ ] Draft show notes with the Copilot pilot results he shared (with his permission) -- [ ] Schedule editing with [[person-paco-furiani]] -- [ ] Create social media clips — the AI takes will drive significant engagement diff --git a/demo-vault-v2/event-podcast-rec-2024-10-24.md b/demo-vault-v2/event-podcast-rec-2024-10-24.md deleted file mode 100644 index 621e158c..00000000 --- a/demo-vault-v2/event-podcast-rec-2024-10-24.md +++ /dev/null @@ -1,24 +0,0 @@ ---- -aliases: ["Podcast recording — 2024-10-24"] -Is A: Event -Date: "2024-10-24" -Belongs to: "[[2024-10]]" -Related to: ["[[person-clara-dupont]]"] -Tags: ["Work", "Podcast"] ---- -# Podcast recording — 2024-10-24 -Recorded episode with Clara Dupont. Great conversation. - -## Notes -- Episode theme: product engineering — how to build engineering teams that think in outcomes rather than outputs, and the organizational design patterns that support this shift -- Clara described the transformation her organization underwent when they moved from project-based teams to empowered product teams, including the three failed attempts before they found a model that worked -- Her background as both a product manager and an engineering leader gave her a rare ability to speak both languages fluently — she understands why engineers resist product thinking and why PMs struggle to communicate technical constraints -- Extremely engaging episode; Clara is a dynamic speaker who uses vivid examples and is willing to share failures openly, which makes the conversation feel honest and practical -- Key insight: "If your engineers cannot explain who the customer is and why they care about this feature, you do not have a product team. You have a feature factory with a product manager attached" -- Excellent audio quality throughout; Clara recorded from a media room at her company's office - -## Follow-up -- [ ] Send thank-you email to Clara -- [ ] Draft show notes with the product team evolution framework she outlined -- [ ] Schedule editing with [[person-paco-furiani]] -- [ ] Create social media clips — the "feature factory" line is quotable and will spark discussion diff --git a/demo-vault-v2/event-podcast-rec-2024-11-07.md b/demo-vault-v2/event-podcast-rec-2024-11-07.md deleted file mode 100644 index 8230dbc0..00000000 --- a/demo-vault-v2/event-podcast-rec-2024-11-07.md +++ /dev/null @@ -1,24 +0,0 @@ ---- -aliases: ["Podcast recording — 2024-11-07"] -Is A: Event -Date: "2024-11-07" -Belongs to: "[[2024-11]]" -Related to: ["[[person-katja-mueller]]"] -Tags: ["Work", "Podcast"] ---- -# Podcast recording — 2024-11-07 -Recorded episode with Katja Mueller. Great conversation. - -## Notes -- Episode theme: security engineering as a first-class discipline — moving beyond compliance checklists to building genuinely secure software from the ground up -- Katja walked through her approach to embedding security engineers directly into product teams rather than keeping them siloed in a centralized security org, including the political challenges of getting buy-in from engineering managers who saw it as overhead -- Her background as a former penetration tester turned security engineering director gave her stories a visceral quality — she could describe exactly how attackers think and why that perspective needs to be present during design, not just review -- Strong episode with real depth; Katja does not sugarcoat the current state of application security and is willing to say that most companies are doing it wrong -- Standout quote: "If your security team only talks to engineering during a pentest report readout, you do not have a security program. You have a security theater program" -- Audio quality was very good; Katja recorded from her company's podcast room in Berlin - -## Follow-up -- [ ] Send thank-you email to Katja -- [ ] Draft show notes with the embedded security team model she described -- [ ] Schedule editing with [[person-paco-furiani]] -- [ ] Create social media clips — the security theater quote will resonate widely diff --git a/demo-vault-v2/event-podcast-rec-2024-11-21.md b/demo-vault-v2/event-podcast-rec-2024-11-21.md deleted file mode 100644 index 88138068..00000000 --- a/demo-vault-v2/event-podcast-rec-2024-11-21.md +++ /dev/null @@ -1,23 +0,0 @@ ---- -aliases: ["Podcast recording — 2024-11-21"] -Is A: Event -Date: "2024-11-21" -Belongs to: "[[2024-11]]" -Related to: ["[[person-hiroshi-tanaka]]"] -Tags: ["Work", "Podcast"] ---- -# Podcast recording — 2024-11-21 -Recorded episode with Hiroshi Tanaka. Great conversation. - -## Notes -- Episode theme: second session with Hiroshi — focused on the technical side of building reliable distributed systems in environments with strict data residency requirements across Asian markets -- Hiroshi detailed the multi-region architecture his team built to comply with data sovereignty laws in Japan, Singapore, and South Korea, while maintaining a consistent user experience and reasonable latency -- His practical experience navigating regulatory frameworks that most Western engineers never encounter made this an eye-opening episode — the compliance constraints fundamentally shaped their technical architecture in ways that typical distributed systems content does not cover -- More technically dense than the first episode, which is a good complement; the two recordings together form a comprehensive picture of engineering in the Japanese tech ecosystem -- Key insight: "Data residency is not just a legal requirement — it is an architecture pattern. Once you accept it as a constraint rather than fighting it, your system design becomes clearer" -- Good audio quality; Hiroshi upgraded his microphone since the last recording session - -## Follow-up -- [ ] Send thank-you email to Hiroshi -- [ ] Draft show notes with a map of data residency requirements he discussed -- [ ] Schedule editing with [[person-paco-furiani]] — link this with the first Hiroshi episode in show notes diff --git a/demo-vault-v2/event-podcast-rec-2024-12-05.md b/demo-vault-v2/event-podcast-rec-2024-12-05.md deleted file mode 100644 index dc7d0780..00000000 --- a/demo-vault-v2/event-podcast-rec-2024-12-05.md +++ /dev/null @@ -1,24 +0,0 @@ ---- -aliases: ["Podcast recording — 2024-12-05"] -Is A: Event -Date: "2024-12-05" -Belongs to: "[[2024-12]]" -Related to: ["[[person-elena-konstantinou]]"] -Tags: ["Work", "Podcast"] ---- -# Podcast recording — 2024-12-05 -Recorded episode with Elena Konstantinou. Great conversation. - -## Notes -- Episode theme: third session with Elena — year-end retrospective on platform engineering trends, what lived up to the hype and what fizzled -- Elena reviewed the major platform engineering developments of 2024, from the continued maturation of Backstage to the rise of score-based developer productivity frameworks, providing a candid assessment of each trend's staying power -- Her hands-on perspective was invaluable — she could compare vendor marketing claims against what she actually experienced deploying these tools across multiple organizations throughout the year -- Fun and opinionated session that felt like a natural end-of-year wrap-up; good energy and plenty of strong takes that will generate discussion in the comments -- Memorable quote: "Platform engineering in 2024 was like DevOps in 2014 — everyone says they are doing it, most people are just renaming their ops team, and the ones actually doing it well are too busy to tweet about it" -- Excellent audio; Elena's setup has gotten progressively better across her three appearances - -## Follow-up -- [ ] Send thank-you email to Elena and discuss scheduling her as a regular quarterly guest -- [ ] Draft show notes as a 2024 platform engineering scorecard format -- [ ] Schedule editing with [[person-paco-furiani]] — aim for release before the holiday break -- [ ] Create social media clips — the trend predictions format works well for year-end engagement diff --git a/demo-vault-v2/event-podcast-rec-2024-12-19.md b/demo-vault-v2/event-podcast-rec-2024-12-19.md deleted file mode 100644 index dd73906e..00000000 --- a/demo-vault-v2/event-podcast-rec-2024-12-19.md +++ /dev/null @@ -1,23 +0,0 @@ ---- -aliases: ["Podcast recording — 2024-12-19"] -Is A: Event -Date: "2024-12-19" -Belongs to: "[[2024-12]]" -Related to: ["[[person-adeel-khan]]"] -Tags: ["Work", "Podcast"] ---- -# Podcast recording — 2024-12-19 -Recorded episode with Adeel Khan. Great conversation. - -## Notes -- Episode theme: second session with Adeel — focused on the human side of large-scale migrations, including how to keep engineering teams motivated during multi-year infrastructure overhauls -- Adeel shared the framework he uses for breaking up migration projects into meaningful milestones that provide visible progress, rather than the typical "big bang" approach that demoralizes teams -- His honesty about the emotional toll of leading a migration — the political pressure from leadership, the fatigue of the team, the constant temptation to cut corners — made this an unusually personal and relatable episode -- Great session that balances the technical depth of his first appearance with more leadership and management insights; together the two episodes tell a complete story -- Key quote: "The hardest part of a migration is not the technical work. It is convincing your team on month fourteen that the finish line is worth running toward when they cannot see it yet" -- Audio quality was clean and professional; Adeel continues to record from his home studio with excellent equipment - -## Follow-up -- [ ] Send thank-you email to Adeel -- [ ] Draft show notes connecting this with the first migration-focused episode -- [ ] Schedule editing with [[person-paco-furiani]] diff --git a/demo-vault-v2/event-podcast-rec-2025-01-02.md b/demo-vault-v2/event-podcast-rec-2025-01-02.md deleted file mode 100644 index 0b6105d2..00000000 --- a/demo-vault-v2/event-podcast-rec-2025-01-02.md +++ /dev/null @@ -1,24 +0,0 @@ ---- -aliases: ["Podcast recording — 2025-01-02"] -Is A: Event -Date: "2025-01-02" -Belongs to: "[[2025-01]]" -Related to: ["[[person-matteo-gentile]]"] -Tags: ["Work", "Podcast"] ---- -# Podcast recording — 2025-01-02 -Recorded episode with Matteo Gentile. Great conversation. - -## Notes -- Episode theme: second session with Matteo — 2025 planning edition, focused on how engineering leaders should approach annual technical roadmapping and capacity planning -- Matteo shared his template for balancing feature work, tech debt reduction, and platform investment across quarterly planning cycles, including how he presents these trade-offs to non-technical executives -- His consulting experience across dozens of organizations gave him a broad dataset of what works — he identified three common anti-patterns in annual planning that he sees repeatedly: overcommitting to features, underbudgeting for reliability work, and treating security as a project rather than a continuous investment -- Strong start to the new year of recordings; Matteo's structured thinking makes for clear, actionable content that listeners can apply immediately -- Memorable insight: "If your annual plan does not have at least 20 percent unallocated capacity, you are not planning — you are writing fiction" -- Clean audio throughout; both on Riverside with backup tracks - -## Follow-up -- [ ] Send thank-you email to Matteo and ask for a redacted version of his planning template -- [ ] Draft show notes with the planning framework as a downloadable resource -- [ ] Schedule editing with [[person-paco-furiani]] -- [ ] Create social media clips — the 20 percent unallocated capacity rule will get shares diff --git a/demo-vault-v2/event-podcast-rec-2025-01-16.md b/demo-vault-v2/event-podcast-rec-2025-01-16.md deleted file mode 100644 index b3589a1b..00000000 --- a/demo-vault-v2/event-podcast-rec-2025-01-16.md +++ /dev/null @@ -1,23 +0,0 @@ ---- -aliases: ["Podcast recording — 2025-01-16"] -Is A: Event -Date: "2025-01-16" -Belongs to: "[[2025-01]]" -Related to: ["[[person-hiroshi-tanaka]]"] -Tags: ["Work", "Podcast"] ---- -# Podcast recording — 2025-01-16 -Recorded episode with Hiroshi Tanaka. Great conversation. - -## Notes -- Episode theme: third session with Hiroshi — exploring the rise of developer productivity engineering as a dedicated function, drawing on examples from Japanese and American companies -- Hiroshi compared how productivity engineering teams are structured at major tech companies in Tokyo versus Silicon Valley, noting that the Japanese approach tends to be more holistic and includes developer well-being metrics alongside throughput measures -- His insider knowledge of how companies like Mercari and LINE approach internal developer tooling provided a rare window into a tech ecosystem that the English-speaking podcast world rarely covers -- Another strong recording; Hiroshi has become one of our most valuable recurring guests, bringing fresh perspectives each time while building on themes from previous episodes -- Key quote: "Developer productivity is not about making people work faster. It is about removing the things that make them work slower. The distinction matters because one burns people out and the other energizes them" -- Good audio quality; Hiroshi has settled into a reliable recording setup that produces consistent results - -## Follow-up -- [ ] Send thank-you email to Hiroshi -- [ ] Draft show notes with the productivity metrics framework he outlined -- [ ] Schedule editing with [[person-paco-furiani]] diff --git a/demo-vault-v2/event-podcast-rec-2025-01-30.md b/demo-vault-v2/event-podcast-rec-2025-01-30.md deleted file mode 100644 index 346ebd7d..00000000 --- a/demo-vault-v2/event-podcast-rec-2025-01-30.md +++ /dev/null @@ -1,24 +0,0 @@ ---- -aliases: ["Podcast recording — 2025-01-30"] -Is A: Event -Date: "2025-01-30" -Belongs to: "[[2025-01]]" -Related to: ["[[person-adeel-khan]]"] -Tags: ["Work", "Podcast"] ---- -# Podcast recording — 2025-01-30 -Recorded episode with Adeel Khan. Great conversation. - -## Notes -- Episode theme: third session with Adeel — this time covering the CTO's role in M&A integration, specifically how to evaluate and merge technology stacks when companies are acquired -- Adeel shared a detailed playbook from three acquisitions he led the technical due diligence and integration for, including the decision framework for which systems to keep, replace, or merge -- His fintech background made the compliance and data migration aspects particularly relevant — he addressed how to merge customer data across different regulatory regimes without creating a compliance nightmare -- Slightly more niche than his previous episodes but extremely valuable for listeners in leadership positions at growing companies; the practical frameworks are immediately usable -- Standout insight: "Technical due diligence is not about evaluating the code — it is about evaluating the team that wrote the code. The codebase you can fix; the engineering culture is much harder to change" -- Excellent audio quality; Adeel's home studio setup continues to deliver professional results - -## Follow-up -- [ ] Send thank-you email to Adeel -- [ ] Draft show notes with the M&A technical integration checklist he walked through -- [ ] Schedule editing with [[person-paco-furiani]] -- [ ] Create social media clips — the due diligence framing is fresh and will appeal to CTOs and VPs diff --git a/demo-vault-v2/event-podcast-rec-2025-02-13.md b/demo-vault-v2/event-podcast-rec-2025-02-13.md deleted file mode 100644 index 10f2f698..00000000 --- a/demo-vault-v2/event-podcast-rec-2025-02-13.md +++ /dev/null @@ -1,24 +0,0 @@ ---- -aliases: ["Podcast recording — 2025-02-13"] -Is A: Event -Date: "2025-02-13" -Belongs to: "[[2025-02]]" -Related to: ["[[person-anna-lindberg]]"] -Tags: ["Work", "Podcast"] ---- -# Podcast recording — 2025-02-13 -Recorded episode with Anna Lindberg. Great conversation. - -## Notes -- Episode theme: sustainable engineering practices — how to build software organizations that do not burn people out while still shipping at a competitive pace -- Anna drew on her experience leading engineering at a Nordic SaaS company known for its work-life balance culture, sharing how they maintained high shipping velocity with a strict 35-hour work week and no on-call outside business hours -- Her perspective challenged the Silicon Valley assumption that intensity equals output — she presented convincing data showing that her team's deployment frequency and incident rates were comparable to companies with much more demanding cultures -- Refreshing and important conversation; Anna is calm, data-driven, and persuasive without being preachy about the Nordic model -- Key quote: "Sustainable pace is not a luxury. It is a competitive advantage. The teams that ship the fastest over a five-year period are never the ones working 60-hour weeks" -- Very clean audio; Anna recorded from a professional studio in Stockholm - -## Follow-up -- [ ] Send thank-you email to Anna -- [ ] Draft show notes with the team health metrics dashboard she described -- [ ] Schedule editing with [[person-paco-furiani]] -- [ ] Create social media clips — the 35-hour work week with competitive metrics angle will generate significant engagement diff --git a/demo-vault-v2/event-podcast-rec-2025-02-27.md b/demo-vault-v2/event-podcast-rec-2025-02-27.md deleted file mode 100644 index 90a454f9..00000000 --- a/demo-vault-v2/event-podcast-rec-2025-02-27.md +++ /dev/null @@ -1,23 +0,0 @@ ---- -aliases: ["Podcast recording — 2025-02-27"] -Is A: Event -Date: "2025-02-27" -Belongs to: "[[2025-02]]" -Related to: ["[[person-tom-richardson]]"] -Tags: ["Work", "Podcast"] ---- -# Podcast recording — 2025-02-27 -Recorded episode with Tom Richardson. Great conversation. - -## Notes -- Episode theme: the evolution of backend frameworks and why the pendulum is swinging back toward server-rendered architectures after a decade of SPA dominance -- Tom shared his experience migrating a large consumer application from a React SPA to a server-rendered approach with partial hydration, including the performance improvements and developer experience trade-offs they discovered -- His deep expertise in web performance optimization gave the conversation a quantitative rigor — he cited specific Core Web Vitals improvements and showed how architectural decisions directly impacted business metrics like conversion rates -- Technically dense but accessible episode; Tom is skilled at explaining complex rendering strategies with clear mental models and diagrams he described verbally -- Memorable quote: "We spent five years building increasingly complex client-side JavaScript to solve problems that servers solved in 2005. Sometimes progress is admitting you went in a circle" -- Good audio quality; Tom recorded from a home office with adequate sound treatment - -## Follow-up -- [ ] Send thank-you email to Tom and request the performance comparison data for show notes -- [ ] Draft show notes with before/after performance metrics -- [ ] Schedule editing with [[person-paco-furiani]] diff --git a/demo-vault-v2/event-podcast-rec-2025-03-13.md b/demo-vault-v2/event-podcast-rec-2025-03-13.md deleted file mode 100644 index d28cbfa3..00000000 --- a/demo-vault-v2/event-podcast-rec-2025-03-13.md +++ /dev/null @@ -1,24 +0,0 @@ ---- -aliases: ["Podcast recording — 2025-03-13"] -Is A: Event -Date: "2025-03-13" -Belongs to: "[[2025-03]]" -Related to: ["[[person-clara-dupont]]"] -Tags: ["Work", "Podcast"] ---- -# Podcast recording — 2025-03-13 -Recorded episode with Clara Dupont. Great conversation. - -## Notes -- Episode theme: second session with Clara — focused on engineering hiring at scale, including how to design interview processes that actually predict on-the-job performance -- Clara shared the complete interview redesign she led at her company, replacing the traditional whiteboard algorithm rounds with take-home projects followed by pair-programming sessions on the candidate's own code -- Her data on hire quality before and after the redesign was compelling — new hire retention at 12 months increased from 72 percent to 91 percent, and time-to-productivity decreased measurably -- Another excellent episode with Clara; she brings the same product thinking to organizational design that she advocates for engineering teams -- Key insight: "Your interview process is a product, and candidates are your users. If your conversion rate is low and your churn is high, you have a product problem, not a pipeline problem" -- Audio quality was excellent; Clara again recorded from her company's media room - -## Follow-up -- [ ] Send thank-you email to Clara and ask if she can share a redacted version of her interview rubric -- [ ] Draft show notes with the interview redesign framework -- [ ] Schedule editing with [[person-paco-furiani]] -- [ ] Create social media clips — the interview-as-product analogy is highly shareable diff --git a/demo-vault-v2/event-podcast-rec-2025-03-27.md b/demo-vault-v2/event-podcast-rec-2025-03-27.md deleted file mode 100644 index f58e8001..00000000 --- a/demo-vault-v2/event-podcast-rec-2025-03-27.md +++ /dev/null @@ -1,24 +0,0 @@ ---- -aliases: ["Podcast recording — 2025-03-27"] -Is A: Event -Date: "2025-03-27" -Belongs to: "[[2025-03]]" -Related to: ["[[person-elena-konstantinou]]"] -Tags: ["Work", "Podcast"] ---- -# Podcast recording — 2025-03-27 -Recorded episode with Elena Konstantinou. Great conversation. - -## Notes -- Episode theme: fourth session with Elena — Q1 2025 platform engineering retrospective and preview of her keynote at the upcoming KubeCon Europe -- Elena previewed the core thesis of her KubeCon talk: that the platform engineering movement is at a critical inflection point where it either matures into a genuine discipline with standards and career paths, or fragments into vendor-driven hype -- She shared early data from a survey of 500 platform teams she conducted, showing that teams with a dedicated platform product manager ship internal tools that see 3x higher adoption than those run purely by infrastructure engineers -- Elena is now firmly one of our marquee recurring guests; the audience engagement on her episodes consistently outperforms our average by 40 percent -- Standout quote: "A platform without a product manager is just infrastructure with a landing page. Users do not adopt platforms — they adopt solutions to their problems" -- Audio quality continues to be excellent; Elena has fully dialed in her recording setup at this point - -## Follow-up -- [ ] Send thank-you email to Elena and coordinate timing with her KubeCon talk for maximum impact -- [ ] Draft show notes with preview of the survey results -- [ ] Schedule editing with [[person-paco-furiani]] — prioritize fast turnaround to align with KubeCon timing -- [ ] Create social media clips and coordinate cross-promotion with KubeCon diff --git a/demo-vault-v2/event-podcast-rec-2025-04-10.md b/demo-vault-v2/event-podcast-rec-2025-04-10.md deleted file mode 100644 index 5f6c00d6..00000000 --- a/demo-vault-v2/event-podcast-rec-2025-04-10.md +++ /dev/null @@ -1,23 +0,0 @@ ---- -aliases: ["Podcast recording — 2025-04-10"] -Is A: Event -Date: "2025-04-10" -Belongs to: "[[2025-04]]" -Related to: ["[[person-matteo-gentile]]"] -Tags: ["Work", "Podcast"] ---- -# Podcast recording — 2025-04-10 -Recorded episode with Matteo Gentile. Great conversation. - -## Notes -- Episode theme: third session with Matteo — the organizational cost of context switching and how engineering leaders can design work systems that protect deep focus time -- Matteo presented research-backed findings on the impact of interruptions on engineering productivity, including a study he ran with three client organizations that measured output before and after implementing "focus blocks" and meeting-free days -- His consulting perspective gave him breadth across different company sizes and industries — the interventions that worked at a 50-person startup were fundamentally different from what worked at a 2,000-person enterprise -- Practical and immediately applicable episode; Matteo provided specific calendar and Slack configuration recommendations that listeners can implement the same week -- Key quote: "Every Slack notification is a context switch, and every context switch costs 23 minutes. Do the math on your team's daily notification count and you will understand where your velocity went" -- Clean audio; Matteo recorded from his consulting office with good room treatment - -## Follow-up -- [ ] Send thank-you email to Matteo -- [ ] Draft show notes with the focus time implementation playbook he described -- [ ] Schedule editing with [[person-paco-furiani]] diff --git a/demo-vault-v2/event-podcast-rec-2025-04-24.md b/demo-vault-v2/event-podcast-rec-2025-04-24.md deleted file mode 100644 index a37925cc..00000000 --- a/demo-vault-v2/event-podcast-rec-2025-04-24.md +++ /dev/null @@ -1,24 +0,0 @@ ---- -aliases: ["Podcast recording — 2025-04-24"] -Is A: Event -Date: "2025-04-24" -Belongs to: "[[2025-04]]" -Related to: ["[[person-benedetta-vitali]]"] -Tags: ["Work", "Podcast"] ---- -# Podcast recording — 2025-04-24 -Recorded episode with Benedetta Vitali. Great conversation. - -## Notes -- Episode theme: design systems engineering — building and scaling component libraries that actually get adopted across large organizations -- Benedetta shared her experience leading the design system team at a major European bank, including the governance model they developed to balance consistency with the flexibility that product teams need -- Her unique position bridging design and engineering gave the conversation a perspective that pure frontend or pure design guests rarely achieve — she could speak to the technical architecture of the component library, the design token strategy, and the organizational change management required to drive adoption -- Excellent first appearance; Benedetta is articulate, passionate about the topic, and brought numerous concrete examples from her work -- Memorable insight: "A design system nobody uses is just a museum of components. Adoption is the only metric that matters, and adoption requires empathy for the teams you are asking to change their workflow" -- Very clean audio; Benedetta recorded from a well-treated office space with professional equipment - -## Follow-up -- [ ] Send thank-you email to Benedetta -- [ ] Draft show notes with the design system governance framework she outlined -- [ ] Schedule editing with [[person-paco-furiani]] -- [ ] Create social media clips — the museum of components line will resonate with frontend engineers diff --git a/demo-vault-v2/event-podcast-rec-2025-05-08.md b/demo-vault-v2/event-podcast-rec-2025-05-08.md deleted file mode 100644 index 9c09912a..00000000 --- a/demo-vault-v2/event-podcast-rec-2025-05-08.md +++ /dev/null @@ -1,24 +0,0 @@ ---- -aliases: ["Podcast recording — 2025-05-08"] -Is A: Event -Date: "2025-05-08" -Belongs to: "[[2025-05]]" -Related to: ["[[person-priya-sharma]]"] -Tags: ["Work", "Podcast"] ---- -# Podcast recording — 2025-05-08 -Recorded episode with Priya Sharma. Great conversation. - -## Notes -- Episode theme: third session with Priya — the impact of AI code assistants on mobile development specifically, and how her team is integrating these tools into their existing development workflow -- Priya shared six months of data from her team's structured rollout of AI coding tools across iOS and Android development, with granular metrics on which tasks benefited most (boilerplate UI code, test generation) and which saw no improvement (complex state management, platform-specific API integration) -- Her rigorous, metrics-driven approach to evaluating AI tools stands in contrast to the usual anecdotal takes — she ran controlled experiments with and without AI assistance on comparable features -- Strong technical episode that will age well; the data she shared provides a snapshot of where AI tools genuinely help mobile development versus where the hype exceeds reality -- Key quote: "AI tools are fantastic at writing the code you already know how to write. The question is whether that is actually your bottleneck" -- Audio quality was excellent as always; Priya continues to record from her professional setup - -## Follow-up -- [ ] Send thank-you email to Priya and request permission to publish the before/after metrics -- [ ] Draft show notes with the AI tool evaluation framework -- [ ] Schedule editing with [[person-paco-furiani]] -- [ ] Create social media clips — the controlled experiment results will drive engagement among mobile devs diff --git a/demo-vault-v2/event-podcast-rec-2025-05-22.md b/demo-vault-v2/event-podcast-rec-2025-05-22.md deleted file mode 100644 index 4115d10a..00000000 --- a/demo-vault-v2/event-podcast-rec-2025-05-22.md +++ /dev/null @@ -1,23 +0,0 @@ ---- -aliases: ["Podcast recording — 2025-05-22"] -Is A: Event -Date: "2025-05-22" -Belongs to: "[[2025-05]]" -Related to: ["[[person-james-murphy]]"] -Tags: ["Work", "Podcast"] ---- -# Podcast recording — 2025-05-22 -Recorded episode with James Murphy. Great conversation. - -## Notes -- Episode theme: third session with James — focused on engineering career ladders and how to design progression frameworks that work for individual contributors and managers without creating artificial hierarchies -- James shared the IC career ladder overhaul his organization completed, moving from a traditional level-based system to a competency matrix that allows engineers to grow in multiple dimensions without requiring management responsibility -- His candid discussion of the mistakes they made in the first two iterations of the ladder — including levels that existed on paper but had no real difference in scope or expectations — made the conversation practically useful for anyone building or revising their own career framework -- Strong session that rounds out James's recurring guest arc nicely; the combination of remote work, team rituals, and now career design gives listeners a comprehensive view of his organizational philosophy -- Standout quote: "If your staff engineer title is just a reward for tenure rather than a description of impact, you have created a participation trophy system that devalues the role for everyone" -- Clean audio; James continues to have a reliable home office setup - -## Follow-up -- [ ] Send thank-you email to James -- [ ] Draft show notes with a sample competency matrix framework -- [ ] Schedule editing with [[person-paco-furiani]] diff --git a/demo-vault-v2/event-podcast-rec-2025-06-05.md b/demo-vault-v2/event-podcast-rec-2025-06-05.md deleted file mode 100644 index a1cce05e..00000000 --- a/demo-vault-v2/event-podcast-rec-2025-06-05.md +++ /dev/null @@ -1,24 +0,0 @@ ---- -aliases: ["Podcast recording — 2025-06-05"] -Is A: Event -Date: "2025-06-05" -Belongs to: "[[2025-06]]" -Related to: ["[[person-sarah-oconnor]]"] -Tags: ["Work", "Podcast"] ---- -# Podcast recording — 2025-06-05 -Recorded episode with Sarah O'Connor. Great conversation. - -## Notes -- Episode theme: second session with Sarah — focused on the challenges of maintaining engineering culture during periods of significant organizational change, including layoffs, reorgs, and leadership transitions -- Sarah shared her firsthand experience navigating a major reorganization at her company where three engineering teams were merged, two managers were let go, and the surviving team had to rebuild trust and productivity from a fragile emotional state -- Her willingness to discuss the human cost of these decisions — not just the strategic rationale — made this one of our most emotionally honest episodes; she spoke about her own doubts as a leader during the process -- Powerful and necessary recording; this is the kind of content that the engineering leadership space needs more of, beyond the typical success-story podcast format -- Key quote: "You cannot optimize for resilience and pretend that the humans in your system are interchangeable. Resilience starts with acknowledging that your team is made of people who remember what happened to them" -- Audio quality was very good; Sarah recorded from a quiet conference room at her office - -## Follow-up -- [ ] Send thank-you email to Sarah and confirm she is comfortable with the level of candor in the recording -- [ ] Draft show notes with sensitivity to the personal nature of the content -- [ ] Schedule editing with [[person-paco-furiani]] — discuss tone and pacing for this more serious episode -- [ ] Create social media clips carefully — select moments that are impactful without being exploitative diff --git a/demo-vault-v2/event-podcast-rec-2025-06-19.md b/demo-vault-v2/event-podcast-rec-2025-06-19.md deleted file mode 100644 index a4ecc9bc..00000000 --- a/demo-vault-v2/event-podcast-rec-2025-06-19.md +++ /dev/null @@ -1,24 +0,0 @@ ---- -aliases: ["Podcast recording — 2025-06-19"] -Is A: Event -Date: "2025-06-19" -Belongs to: "[[2025-06]]" -Related to: ["[[person-diego-santos]]"] -Tags: ["Work", "Podcast"] ---- -# Podcast recording — 2025-06-19 -Recorded episode with Diego Santos. Great conversation. - -## Notes -- Episode theme: third session with Diego — mid-year check-in on the AI development tools landscape, six months after his initial assessment, focusing on what has changed and what has not -- Diego provided an updated view of AI tool adoption across developer communities, noting that the initial hype cycle has normalized and usage patterns have stabilized around specific workflows — code completion, test generation, and documentation are the clear winners while architecture and design tasks remain largely human-driven -- His DevRel network gave him access to aggregate usage data from multiple companies, making his analysis more rigorous than the usual single-company anecdotes that dominate the conversation -- Excellent bookend to his earlier AI episode; together they document a full year of the industry's relationship with AI coding tools in real time -- Memorable quote: "The AI hype cycle in developer tools has reached the 'actually useful but boring' phase, which is exactly where good tools should be. Nobody gets excited about their linter, and that is a sign it works" -- Clean audio throughout; Diego has completely resolved his earlier setup issues and now delivers consistently professional recordings - -## Follow-up -- [ ] Send thank-you email to Diego -- [ ] Draft show notes comparing his predictions from 6 months ago with current reality -- [ ] Schedule editing with [[person-paco-furiani]] -- [ ] Create social media clips — the before/after prediction comparison format works well for engagement diff --git a/demo-vault-v2/event-reading-2024-01-07.md b/demo-vault-v2/event-reading-2024-01-07.md deleted file mode 100644 index 50f31251..00000000 --- a/demo-vault-v2/event-reading-2024-01-07.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Reading session — 2024-01-07"] -Is A: Event -Date: "2024-01-07" -Belongs to: "[[2024-01]]" -Tags: ["Learning"] ---- -# Reading session — 2024-01-07 -Sunday morning reading block. 2 hours with coffee. - -## Notes -- Continued [[note-atomic-habits]] — chapters 5-7 on cue-based habit design -- Key idea: "You do not rise to the level of your goals. You fall to the level of your systems." -- Read about 40 pages, took margin notes on identity-based habits -- Connects directly to how I'm thinking about building the daily review routine diff --git a/demo-vault-v2/event-reading-2024-01-21.md b/demo-vault-v2/event-reading-2024-01-21.md deleted file mode 100644 index 5933c2d5..00000000 --- a/demo-vault-v2/event-reading-2024-01-21.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -aliases: ["Reading session — 2024-01-21"] -Is A: Event -Date: "2024-01-21" -Belongs to: "[[2024-01]]" -Tags: ["Learning"] ---- -# Reading session — 2024-01-21 -Sunday morning reading block. 2 hours with coffee. - -## Notes -- Finished [[note-atomic-habits]] — the last section on advanced tactics and the plateau of latent potential -- The compounding metaphor for habits really landed today -- About 50 pages to wrap it up, plus re-read the summary chapter -- Already thinking about what to read next — leaning towards Deep Work - -## Follow-up -- [ ] Write evergreen note on identity-based habit change diff --git a/demo-vault-v2/event-reading-2024-02-04.md b/demo-vault-v2/event-reading-2024-02-04.md deleted file mode 100644 index 3d31b9d3..00000000 --- a/demo-vault-v2/event-reading-2024-02-04.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Reading session — 2024-02-04"] -Is A: Event -Date: "2024-02-04" -Belongs to: "[[2024-02]]" -Tags: ["Learning"] ---- -# Reading session — 2024-02-04 -Sunday morning reading block. 2 hours with coffee. - -## Notes -- Started [[note-deep-work]] — read the introduction and Part 1 on the value of deep work -- Newport's distinction between deep work and shallow work is clarifying -- About 60 pages in, the examples of Carl Jung and Mark Twain stood out -- Relevant to how I manage focus time at work — too many Slack interruptions diff --git a/demo-vault-v2/event-reading-2024-02-18.md b/demo-vault-v2/event-reading-2024-02-18.md deleted file mode 100644 index 933e5e56..00000000 --- a/demo-vault-v2/event-reading-2024-02-18.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Reading session — 2024-02-18"] -Is A: Event -Date: "2024-02-18" -Belongs to: "[[2024-02]]" -Tags: ["Learning"] ---- -# Reading session — 2024-02-18 -Sunday morning reading block. 2 hours with coffee. - -## Notes -- Continued [[note-deep-work]] — Part 2 on rules for focused work -- The "shutdown ritual" concept is powerful — need to implement this -- Read chapters 4-5, about 45 pages -- Thinking about blocking 2-hour deep work sessions on my calendar diff --git a/demo-vault-v2/event-reading-2024-03-03.md b/demo-vault-v2/event-reading-2024-03-03.md deleted file mode 100644 index 90abdc90..00000000 --- a/demo-vault-v2/event-reading-2024-03-03.md +++ /dev/null @@ -1,19 +0,0 @@ ---- -aliases: ["Reading session — 2024-03-03"] -Is A: Event -Date: "2024-03-03" -Belongs to: "[[2024-03]]" -Tags: ["Learning"] ---- -# Reading session — 2024-03-03 -Sunday morning reading block. 2 hours with coffee. - -## Notes -- Finished [[note-deep-work]] — the last section on scheduling and draining the shallows -- Key takeaway: treat deep work like a skill to be trained, not just a preference -- About 50 pages to close it out -- This book fundamentally changed how I think about structuring my workday - -## Follow-up -- [ ] Write evergreen note on deep work scheduling strategies -- [ ] Discuss shutdown ritual idea with Matteo diff --git a/demo-vault-v2/event-reading-2024-03-17.md b/demo-vault-v2/event-reading-2024-03-17.md deleted file mode 100644 index b6425984..00000000 --- a/demo-vault-v2/event-reading-2024-03-17.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Reading session — 2024-03-17"] -Is A: Event -Date: "2024-03-17" -Belongs to: "[[2024-03]]" -Tags: ["Learning"] ---- -# Reading session — 2024-03-17 -Sunday morning reading block. 2 hours with coffee. - -## Notes -- Started [[note-the-obstacle-is-the-way]] — read Part 1 on perception -- Holiday's framing of obstacles as fuel is very Stoic, reminds me of Seneca -- About 55 pages in, enjoyed the historical anecdotes -- The Rockefeller story about seeing opportunity in crisis was memorable diff --git a/demo-vault-v2/event-reading-2024-03-31.md b/demo-vault-v2/event-reading-2024-03-31.md deleted file mode 100644 index 64df901b..00000000 --- a/demo-vault-v2/event-reading-2024-03-31.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Reading session — 2024-03-31"] -Is A: Event -Date: "2024-03-31" -Belongs to: "[[2024-03]]" -Tags: ["Learning"] ---- -# Reading session — 2024-03-31 -Sunday morning reading block. 2 hours with coffee. - -## Notes -- Continued [[note-the-obstacle-is-the-way]] — Parts 2-3 on action and will -- "The impediment to action advances action. What stands in the way becomes the way." -- Read about 70 pages, fast and engaging -- Applies to the current product challenges at work — reframing blockers as design constraints diff --git a/demo-vault-v2/event-reading-2024-04-14.md b/demo-vault-v2/event-reading-2024-04-14.md deleted file mode 100644 index 5a4ed189..00000000 --- a/demo-vault-v2/event-reading-2024-04-14.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Reading session — 2024-04-14"] -Is A: Event -Date: "2024-04-14" -Belongs to: "[[2024-04]]" -Tags: ["Learning"] ---- -# Reading session — 2024-04-14 -Sunday morning reading block. 2 hours with coffee. - -## Notes -- Started [[note-good-strategy-bad-strategy]] — the first 3 chapters on the kernel of strategy -- Rumelt's clarity on what strategy actually is vs. what people call strategy is refreshing -- About 50 pages, dense but rewarding reading -- The concept of "bad strategy" as a list of goals without a plan hit close to home diff --git a/demo-vault-v2/event-reading-2024-04-28.md b/demo-vault-v2/event-reading-2024-04-28.md deleted file mode 100644 index 373365b1..00000000 --- a/demo-vault-v2/event-reading-2024-04-28.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -aliases: ["Reading session — 2024-04-28"] -Is A: Event -Date: "2024-04-28" -Belongs to: "[[2024-04]]" -Tags: ["Learning"] ---- -# Reading session — 2024-04-28 -Sunday morning reading block. 2 hours with coffee. - -## Notes -- Continued [[note-good-strategy-bad-strategy]] — chapters on leverage and proximate objectives -- "A good strategy works by focusing energy and resources on one, or a very few, pivotal objectives" -- Read about 60 pages, taking detailed notes -- Directly applicable to how we prioritize features — need to share this with the team - -## Follow-up -- [ ] Write evergreen note on the kernel of strategy (diagnosis, guiding policy, coherent actions) diff --git a/demo-vault-v2/event-reading-2024-05-12.md b/demo-vault-v2/event-reading-2024-05-12.md deleted file mode 100644 index 6134be50..00000000 --- a/demo-vault-v2/event-reading-2024-05-12.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Reading session — 2024-05-12"] -Is A: Event -Date: "2024-05-12" -Belongs to: "[[2024-05]]" -Tags: ["Learning"] ---- -# Reading session — 2024-05-12 -Sunday morning reading block. 2 hours with coffee. - -## Notes -- Started [[note-thinking-fast-and-slow]] — Part 1 on the two systems -- Kahneman's System 1 / System 2 framework is foundational, glad I'm finally reading the source -- About 45 pages, it's dense academic writing but fascinating -- The anchoring effect examples are eye-opening for product design diff --git a/demo-vault-v2/event-reading-2024-05-26.md b/demo-vault-v2/event-reading-2024-05-26.md deleted file mode 100644 index 50986687..00000000 --- a/demo-vault-v2/event-reading-2024-05-26.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Reading session — 2024-05-26"] -Is A: Event -Date: "2024-05-26" -Belongs to: "[[2024-05]]" -Tags: ["Learning"] ---- -# Reading session — 2024-05-26 -Sunday morning reading block. 2 hours with coffee. - -## Notes -- Continued [[note-thinking-fast-and-slow]] — chapters on heuristics and biases -- The availability heuristic explains so much about how teams make risk assessments -- Read about 40 pages, slower going than other books this year -- Making connections to [[note-thinking-in-bets]] which I want to read next diff --git a/demo-vault-v2/event-reading-2024-06-09.md b/demo-vault-v2/event-reading-2024-06-09.md deleted file mode 100644 index bf446147..00000000 --- a/demo-vault-v2/event-reading-2024-06-09.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Reading session — 2024-06-09"] -Is A: Event -Date: "2024-06-09" -Belongs to: "[[2024-06]]" -Tags: ["Learning"] ---- -# Reading session — 2024-06-09 -Sunday morning reading block. 2 hours with coffee. - -## Notes -- Continued [[note-thinking-fast-and-slow]] — Part 3 on overconfidence and the illusion of understanding -- "The confidence people have in their beliefs is not a measure of the quality of evidence" -- About 50 pages, reaching the halfway point -- This is reshaping how I evaluate my own certainty about product decisions diff --git a/demo-vault-v2/event-reading-2024-06-23.md b/demo-vault-v2/event-reading-2024-06-23.md deleted file mode 100644 index e57c6143..00000000 --- a/demo-vault-v2/event-reading-2024-06-23.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -aliases: ["Reading session — 2024-06-23"] -Is A: Event -Date: "2024-06-23" -Belongs to: "[[2024-06]]" -Tags: ["Learning"] ---- -# Reading session — 2024-06-23 -Sunday morning reading block. 2 hours with coffee. - -## Notes -- Started [[note-the-effective-executive]] alongside Kahneman — light palate cleanser -- Drucker's first chapter on effectiveness being learnable is encouraging -- Read about 30 pages of Drucker, quick and punchy -- The idea that managing yourself is the prerequisite to managing others resonates - -## Follow-up -- [ ] Write evergreen note on Drucker's five practices of effective executives diff --git a/demo-vault-v2/event-reading-2024-07-07.md b/demo-vault-v2/event-reading-2024-07-07.md deleted file mode 100644 index e9cae203..00000000 --- a/demo-vault-v2/event-reading-2024-07-07.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Reading session — 2024-07-07"] -Is A: Event -Date: "2024-07-07" -Belongs to: "[[2024-07]]" -Tags: ["Learning"] ---- -# Reading session — 2024-07-07 -Sunday morning reading block. 2 hours with coffee. - -## Notes -- Continued [[note-the-effective-executive]] — chapters on time management and contribution -- "Know thy time" — Drucker's insistence on tracking time before trying to manage it -- Finished about 60 pages, halfway through -- Thinking about doing a time audit of my own work week diff --git a/demo-vault-v2/event-reading-2024-07-21.md b/demo-vault-v2/event-reading-2024-07-21.md deleted file mode 100644 index 60f8b8ad..00000000 --- a/demo-vault-v2/event-reading-2024-07-21.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Reading session — 2024-07-21"] -Is A: Event -Date: "2024-07-21" -Belongs to: "[[2024-07]]" -Tags: ["Learning"] ---- -# Reading session — 2024-07-21 -Sunday morning reading block. 2 hours with coffee. - -## Notes -- Started [[note-range]] — the opening contrast between Tiger Woods and Roger Federer -- Epstein's argument for breadth over premature specialization is compelling -- About 55 pages, read on the balcony in the summer heat -- Connects to my own path — generalist skills serving me well in product work diff --git a/demo-vault-v2/event-reading-2024-08-04.md b/demo-vault-v2/event-reading-2024-08-04.md deleted file mode 100644 index 5ee1a12b..00000000 --- a/demo-vault-v2/event-reading-2024-08-04.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Reading session — 2024-08-04"] -Is A: Event -Date: "2024-08-04" -Belongs to: "[[2024-08]]" -Tags: ["Learning"] ---- -# Reading session — 2024-08-04 -Sunday morning reading block. 2 hours with coffee. - -## Notes -- Continued [[note-range]] — chapters on learning slowly and the benefits of struggle -- "Desirable difficulties" in learning — making things harder actually improves retention -- About 45 pages, taking notes on the spacing effect -- Want to apply this to how I study technical topics for Laputa development diff --git a/demo-vault-v2/event-reading-2024-08-18.md b/demo-vault-v2/event-reading-2024-08-18.md deleted file mode 100644 index 279a2b85..00000000 --- a/demo-vault-v2/event-reading-2024-08-18.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Reading session — 2024-08-18"] -Is A: Event -Date: "2024-08-18" -Belongs to: "[[2024-08]]" -Tags: ["Learning"] ---- -# Reading session — 2024-08-18 -Sunday morning reading block. 2 hours with coffee. - -## Notes -- Light reading day — re-read sections of [[note-show-your-work]] on the balcony -- Kleon's emphasis on sharing process, not just finished work, is a good reminder -- Skimmed about 30 pages, mostly the chapters on being findable -- Holiday mode, not trying to go too deep this week diff --git a/demo-vault-v2/event-reading-2024-09-01.md b/demo-vault-v2/event-reading-2024-09-01.md deleted file mode 100644 index 243d7b4a..00000000 --- a/demo-vault-v2/event-reading-2024-09-01.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -aliases: ["Reading session — 2024-09-01"] -Is A: Event -Date: "2024-09-01" -Belongs to: "[[2024-09]]" -Tags: ["Learning"] ---- -# Reading session — 2024-09-01 -Sunday morning reading block. 2 hours with coffee. - -## Notes -- Started [[note-never-split-difference]] — first 3 chapters on tactical empathy -- Voss's negotiation techniques are surprisingly applicable to everyday conversations -- About 55 pages, the "mirroring" technique is immediately usable -- Back to focused reading after the summer break, felt good to engage deeply - -## Follow-up -- [ ] Discuss mirroring technique with Matteo diff --git a/demo-vault-v2/event-reading-2024-09-15.md b/demo-vault-v2/event-reading-2024-09-15.md deleted file mode 100644 index 1f0fbd02..00000000 --- a/demo-vault-v2/event-reading-2024-09-15.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Reading session — 2024-09-15"] -Is A: Event -Date: "2024-09-15" -Belongs to: "[[2024-09]]" -Tags: ["Learning"] ---- -# Reading session — 2024-09-15 -Sunday morning reading block. 2 hours with coffee. - -## Notes -- Continued [[note-never-split-difference]] — calibrated questions and the accusation audit -- "How am I supposed to do that?" as a powerful deflection tool -- Read about 50 pages, making margin notes on every technique -- Already used the labeling technique in a stakeholder meeting last week diff --git a/demo-vault-v2/event-reading-2024-09-29.md b/demo-vault-v2/event-reading-2024-09-29.md deleted file mode 100644 index b717def6..00000000 --- a/demo-vault-v2/event-reading-2024-09-29.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Reading session — 2024-09-29"] -Is A: Event -Date: "2024-09-29" -Belongs to: "[[2024-09]]" -Tags: ["Learning"] ---- -# Reading session — 2024-09-29 -Sunday morning reading block. 2 hours with coffee. - -## Notes -- Started [[note-the-hard-thing-about-hard-things]] — Horowitz on the struggle of building companies -- Raw and honest, very different from the typical startup book -- About 60 pages in, the "peacetime CEO vs wartime CEO" distinction is sharp -- Resonates with the harder product decisions I've been wrestling with lately diff --git a/demo-vault-v2/event-reading-2024-10-13.md b/demo-vault-v2/event-reading-2024-10-13.md deleted file mode 100644 index f494395f..00000000 --- a/demo-vault-v2/event-reading-2024-10-13.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -aliases: ["Reading session — 2024-10-13"] -Is A: Event -Date: "2024-10-13" -Belongs to: "[[2024-10]]" -Tags: ["Learning"] ---- -# Reading session — 2024-10-13 -Sunday morning reading block. 2 hours with coffee. - -## Notes -- Continued [[note-the-hard-thing-about-hard-things]] — chapters on hiring, firing, and culture -- "Take care of the people, the products, and the profits — in that order" -- About 50 pages, the writing is gripping despite being a business book -- Makes me think about team dynamics differently - -## Follow-up -- [ ] Write evergreen note on wartime vs peacetime leadership diff --git a/demo-vault-v2/event-reading-2024-10-27.md b/demo-vault-v2/event-reading-2024-10-27.md deleted file mode 100644 index b2890e03..00000000 --- a/demo-vault-v2/event-reading-2024-10-27.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Reading session — 2024-10-27"] -Is A: Event -Date: "2024-10-27" -Belongs to: "[[2024-10]]" -Tags: ["Learning"] ---- -# Reading session — 2024-10-27 -Sunday morning reading block. 2 hours with coffee. - -## Notes -- Started [[note-man-search-for-meaning]] — Part 1 on Frankl's experience in the camps -- Harrowing but essential reading, the most profound book I've picked up this year -- About 40 pages, had to stop and sit with it a few times -- "He who has a why to live can bear almost any how" — keeps echoing diff --git a/demo-vault-v2/event-reading-2024-11-10.md b/demo-vault-v2/event-reading-2024-11-10.md deleted file mode 100644 index a83510e2..00000000 --- a/demo-vault-v2/event-reading-2024-11-10.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -aliases: ["Reading session — 2024-11-10"] -Is A: Event -Date: "2024-11-10" -Belongs to: "[[2024-11]]" -Tags: ["Learning"] ---- -# Reading session — 2024-11-10 -Sunday morning reading block. 2 hours with coffee. - -## Notes -- Finished [[note-man-search-for-meaning]] — Part 2 on logotherapy -- The idea that meaning can be found in suffering, not just in success, is transformative -- About 50 pages to finish, slower and more reflective reading than usual -- Connects to [[note-the-obstacle-is-the-way]] — different traditions arriving at similar truths - -## Follow-up -- [ ] Write evergreen note on meaning-making as a core human drive diff --git a/demo-vault-v2/event-reading-2024-11-24.md b/demo-vault-v2/event-reading-2024-11-24.md deleted file mode 100644 index 786c6d8b..00000000 --- a/demo-vault-v2/event-reading-2024-11-24.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Reading session — 2024-11-24"] -Is A: Event -Date: "2024-11-24" -Belongs to: "[[2024-11]]" -Tags: ["Learning"] ---- -# Reading session — 2024-11-24 -Sunday morning reading block. 2 hours with coffee. - -## Notes -- Started [[note-the-lean-startup]] — first chapters on validated learning -- Ries's build-measure-learn loop is something I've heard about but never read firsthand -- About 55 pages, the IMVU case study is a great concrete example -- Directly relevant to how I'm approaching Laputa feature development diff --git a/demo-vault-v2/event-reading-2024-12-08.md b/demo-vault-v2/event-reading-2024-12-08.md deleted file mode 100644 index 7b480c36..00000000 --- a/demo-vault-v2/event-reading-2024-12-08.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Reading session — 2024-12-08"] -Is A: Event -Date: "2024-12-08" -Belongs to: "[[2024-12]]" -Tags: ["Learning"] ---- -# Reading session — 2024-12-08 -Sunday morning reading block. 2 hours with coffee. - -## Notes -- Continued [[note-the-lean-startup]] — chapters on MVP and innovation accounting -- The MVP concept is simple but the discipline to actually ship the minimum is hard -- About 45 pages, making notes on how to apply this to Laputa's roadmap -- "If we do not know who the customer is, we do not know what quality is" diff --git a/demo-vault-v2/event-reading-2024-12-22.md b/demo-vault-v2/event-reading-2024-12-22.md deleted file mode 100644 index 053d33fb..00000000 --- a/demo-vault-v2/event-reading-2024-12-22.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Reading session — 2024-12-22"] -Is A: Event -Date: "2024-12-22" -Belongs to: "[[2024-12]]" -Tags: ["Learning"] ---- -# Reading session — 2024-12-22 -Sunday morning reading block. 2 hours with coffee. - -## Notes -- Light end-of-year reading — re-read parts of [[note-on-the-shortness-of-life]] -- Seneca on not wasting time on things that don't matter — perfect year-end reflection -- About 25 pages, it's short enough to re-read in a sitting -- Taking stock of the reading year: 10+ books finished, best habit I built this year diff --git a/demo-vault-v2/event-reading-2025-01-05.md b/demo-vault-v2/event-reading-2025-01-05.md deleted file mode 100644 index 45fe2ea1..00000000 --- a/demo-vault-v2/event-reading-2025-01-05.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -aliases: ["Reading session — 2025-01-05"] -Is A: Event -Date: "2025-01-05" -Belongs to: "[[2025-01]]" -Tags: ["Learning"] ---- -# Reading session — 2025-01-05 -Sunday morning reading block. 2 hours with coffee. - -## Notes -- Started [[note-zero-to-one]] — Thiel on contrarian thinking and competition -- "What important truth do very few people agree with you on?" — great opening question -- About 50 pages, compact and provocative writing -- The definite optimism framework is thought-provoking for building Laputa - -## Follow-up -- [ ] Write evergreen note on definite vs indefinite optimism diff --git a/demo-vault-v2/event-reading-2025-01-19.md b/demo-vault-v2/event-reading-2025-01-19.md deleted file mode 100644 index 15bbedb7..00000000 --- a/demo-vault-v2/event-reading-2025-01-19.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Reading session — 2025-01-19"] -Is A: Event -Date: "2025-01-19" -Belongs to: "[[2025-01]]" -Tags: ["Learning"] ---- -# Reading session — 2025-01-19 -Sunday morning reading block. 2 hours with coffee. - -## Notes -- Continued [[note-zero-to-one]] — chapters on monopoly, competition, and secrets -- The idea that competition is overrated and monopoly is the goal challenges conventional wisdom -- Read about 60 pages, nearly finished -- "The most contrarian thing of all is not to oppose the crowd but to think for yourself" diff --git a/demo-vault-v2/event-reading-2025-02-02.md b/demo-vault-v2/event-reading-2025-02-02.md deleted file mode 100644 index a60a0604..00000000 --- a/demo-vault-v2/event-reading-2025-02-02.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Reading session — 2025-02-02"] -Is A: Event -Date: "2025-02-02" -Belongs to: "[[2025-02]]" -Tags: ["Learning"] ---- -# Reading session — 2025-02-02 -Sunday morning reading block. 2 hours with coffee. - -## Notes -- Started [[note-the-art-of-learning]] — Waitzkin on the learning process across chess and martial arts -- His concept of "investment in loss" — learning from failure deliberately — stood out -- About 50 pages, engaging storytelling mixed with practical frameworks -- Reminds me of [[note-grit]] in how it frames perseverance through struggle diff --git a/demo-vault-v2/event-reading-2025-02-16.md b/demo-vault-v2/event-reading-2025-02-16.md deleted file mode 100644 index d6cf3e11..00000000 --- a/demo-vault-v2/event-reading-2025-02-16.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -aliases: ["Reading session — 2025-02-16"] -Is A: Event -Date: "2025-02-16" -Belongs to: "[[2025-02]]" -Tags: ["Learning"] ---- -# Reading session — 2025-02-16 -Sunday morning reading block. 2 hours with coffee. - -## Notes -- Continued [[note-the-art-of-learning]] — chapters on the soft zone and making smaller circles -- "Making smaller circles" means mastering fundamentals so deeply that complex moves emerge naturally -- About 55 pages, read in one focused sprint -- Directly applicable to how I approach learning new technologies — depth before breadth - -## Follow-up -- [ ] Write evergreen note on investment in loss as a learning strategy diff --git a/demo-vault-v2/event-reading-2025-03-02.md b/demo-vault-v2/event-reading-2025-03-02.md deleted file mode 100644 index aab79e55..00000000 --- a/demo-vault-v2/event-reading-2025-03-02.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Reading session — 2025-03-02"] -Is A: Event -Date: "2025-03-02" -Belongs to: "[[2025-03]]" -Tags: ["Learning"] ---- -# Reading session — 2025-03-02 -Sunday morning reading block. 2 hours with coffee. - -## Notes -- Started [[note-radical-candor]] — Kim Scott on caring personally while challenging directly -- The 2x2 framework (Radical Candor vs Ruinous Empathy vs Obnoxious Aggression) is immediately useful -- About 50 pages, lots of practical management advice -- Thinking about how this applies to code reviews and team feedback diff --git a/demo-vault-v2/event-reading-2025-03-16.md b/demo-vault-v2/event-reading-2025-03-16.md deleted file mode 100644 index 3968e729..00000000 --- a/demo-vault-v2/event-reading-2025-03-16.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -aliases: ["Reading session — 2025-03-16"] -Is A: Event -Date: "2025-03-16" -Belongs to: "[[2025-03]]" -Tags: ["Learning"] ---- -# Reading session — 2025-03-16 -Sunday morning reading block. 2 hours with coffee. - -## Notes -- Continued [[note-radical-candor]] — chapters on building a culture of feedback -- "It's not mean, it's clear" — the distinction between being kind and being nice -- About 45 pages, lots of highlighting -- Want to practice giving more direct feedback at work this month - -## Follow-up -- [ ] Discuss radical candor framework with Matteo diff --git a/demo-vault-v2/event-reading-2025-03-30.md b/demo-vault-v2/event-reading-2025-03-30.md deleted file mode 100644 index 76d37ec2..00000000 --- a/demo-vault-v2/event-reading-2025-03-30.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Reading session — 2025-03-30"] -Is A: Event -Date: "2025-03-30" -Belongs to: "[[2025-03]]" -Tags: ["Learning"] ---- -# Reading session — 2025-03-30 -Sunday morning reading block. 2 hours with coffee. - -## Notes -- Started [[note-the-mom-test]] — Fitzpatrick on how to talk to customers without leading them -- Incredibly practical, the shortest and most actionable book I've read in a while -- Read about 70 pages, almost finished it in one sitting -- Rule: never tell customers about your idea, ask about their life and problems instead diff --git a/demo-vault-v2/event-reading-2025-04-13.md b/demo-vault-v2/event-reading-2025-04-13.md deleted file mode 100644 index e0fb101a..00000000 --- a/demo-vault-v2/event-reading-2025-04-13.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -aliases: ["Reading session — 2025-04-13"] -Is A: Event -Date: "2025-04-13" -Belongs to: "[[2025-04]]" -Tags: ["Learning"] ---- -# Reading session — 2025-04-13 -Sunday morning reading block. 2 hours with coffee. - -## Notes -- Started [[note-the-willpower-instinct]] — McGonigal on the science of self-control -- The distinction between "I will," "I won't," and "I want" power is a useful framework -- About 45 pages, science-backed and well-structured -- Connects to [[note-atomic-habits]] — willpower as a muscle vs environment design - -## Follow-up -- [ ] Write evergreen note on willpower depletion vs habit design diff --git a/demo-vault-v2/event-reading-2025-04-27.md b/demo-vault-v2/event-reading-2025-04-27.md deleted file mode 100644 index de4ebd08..00000000 --- a/demo-vault-v2/event-reading-2025-04-27.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Reading session — 2025-04-27"] -Is A: Event -Date: "2025-04-27" -Belongs to: "[[2025-04]]" -Tags: ["Learning"] ---- -# Reading session — 2025-04-27 -Sunday morning reading block. 2 hours with coffee. - -## Notes -- Continued [[note-the-willpower-instinct]] — chapters on stress, sleep, and the "what-the-hell" effect -- The "what-the-hell" effect — once you break a rule, you abandon the whole effort — very relatable -- About 50 pages, strong practical exercises at the end of each chapter -- Sleep quality directly affects willpower reserves, reinforcing the importance of my sleep routine diff --git a/demo-vault-v2/event-reading-2025-05-11.md b/demo-vault-v2/event-reading-2025-05-11.md deleted file mode 100644 index 720ad3d8..00000000 --- a/demo-vault-v2/event-reading-2025-05-11.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Reading session — 2025-05-11"] -Is A: Event -Date: "2025-05-11" -Belongs to: "[[2025-05]]" -Tags: ["Learning"] ---- -# Reading session — 2025-05-11 -Sunday morning reading block. 2 hours with coffee. - -## Notes -- Started [[note-the-innovators-dilemma]] — Christensen on why great companies fail -- The disk drive industry case study is the most detailed business analysis I've read -- About 55 pages, dense but the framework is powerful -- Disruptive innovation vs sustaining innovation — crucial distinction for product thinking diff --git a/demo-vault-v2/event-reading-2025-05-25.md b/demo-vault-v2/event-reading-2025-05-25.md deleted file mode 100644 index bcbae487..00000000 --- a/demo-vault-v2/event-reading-2025-05-25.md +++ /dev/null @@ -1,19 +0,0 @@ ---- -aliases: ["Reading session — 2025-05-25"] -Is A: Event -Date: "2025-05-25" -Belongs to: "[[2025-05]]" -Tags: ["Learning"] ---- -# Reading session — 2025-05-25 -Sunday morning reading block. 2 hours with coffee. - -## Notes -- Continued [[note-the-innovators-dilemma]] — chapters on value networks and the dilemma itself -- Companies fail not because they do wrong things, but because they do right things for the wrong market -- About 50 pages, the examples from steel and excavators are compelling -- Connects to [[note-zero-to-one]] on thinking about building for new markets - -## Follow-up -- [ ] Write evergreen note on disruptive vs sustaining innovation -- [ ] Discuss with Matteo how this applies to Laputa's positioning diff --git a/demo-vault-v2/event-reading-2025-06-08.md b/demo-vault-v2/event-reading-2025-06-08.md deleted file mode 100644 index fef7d0c1..00000000 --- a/demo-vault-v2/event-reading-2025-06-08.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -aliases: ["Reading session — 2025-06-08"] -Is A: Event -Date: "2025-06-08" -Belongs to: "[[2025-06]]" -Tags: ["Learning"] ---- -# Reading session — 2025-06-08 -Sunday morning reading block. 2 hours with coffee. - -## Notes -- Started [[note-the-courage-to-be-disliked]] — Adlerian psychology through Socratic dialogue -- The format of a philosopher and a young man debating is unusual but engaging -- About 60 pages, the core idea that all problems are interpersonal relationship problems is bold -- "The courage to be happy also includes the courage to be disliked" — sitting with this one diff --git a/demo-vault-v2/event-sponsor-call-2024-01-05.md b/demo-vault-v2/event-sponsor-call-2024-01-05.md deleted file mode 100644 index 65d19e9c..00000000 --- a/demo-vault-v2/event-sponsor-call-2024-01-05.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -aliases: ["Sponsor call — 2024-01-05"] -Is A: Event -Date: "2024-01-05" -Belongs to: "[[2024-01]]" -Related to: ["[[person-yuki-sato]]"] -Tags: ["Work"] ---- -# Sponsor call — 2024-01-05 -Sponsor discovery/renewal call. Discussed placement and campaign goals. - -## Notes -- Yuki reached out on behalf of NovaCLI, a developer-focused command-line tools company looking to reach engineering leaders and senior developers -- Discussed a potential 3-month pre-roll sponsorship package with mid-roll mentions on selected episodes; Yuki was particularly interested in episodes covering developer productivity and tooling -- NovaCLI's budget range aligns well with our current rate card — they are looking at the mid-tier package with a possible upgrade to premium if Q1 performance metrics are strong -- New lead; Yuki found us through a recommendation from another sponsor contact and has been listening to the show for about six months -- Good cultural fit — their product genuinely solves a problem our audience cares about, which makes the sponsorship read feel authentic rather than forced - -## Follow-up -- [ ] Send media kit and rate card to Yuki by end of week -- [ ] Update CRM with NovaCLI as a new prospect in the pipeline -- [ ] Follow up in two weeks to gauge interest after they review the proposal diff --git a/demo-vault-v2/event-sponsor-call-2024-01-19.md b/demo-vault-v2/event-sponsor-call-2024-01-19.md deleted file mode 100644 index a5a2b207..00000000 --- a/demo-vault-v2/event-sponsor-call-2024-01-19.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -aliases: ["Sponsor call — 2024-01-19"] -Is A: Event -Date: "2024-01-19" -Belongs to: "[[2024-01]]" -Related to: ["[[person-olivia-martinez]]"] -Tags: ["Work"] ---- -# Sponsor call — 2024-01-19 -Sponsor discovery/renewal call. Discussed placement and campaign goals. - -## Notes -- Olivia represents CloudForge, a cloud infrastructure automation platform targeting mid-market engineering teams -- Discovery call to explore sponsorship options; CloudForge is planning a major product launch in Q2 and wants to build brand awareness among engineering leaders ahead of the release -- Discussed pricing for a 6-episode sponsorship block with dedicated landing page tracking; Olivia requested custom promo codes for attribution -- CloudForge has a healthy marketing budget and Olivia mentioned they are evaluating three other podcasts in the engineering leadership space — we need to differentiate on audience quality and engagement metrics -- Relationship status: new lead, inbound through our sponsorship inquiry form on the website - -## Follow-up -- [ ] Send proposal with audience demographics and engagement data by Monday -- [ ] Update CRM with CloudForge details and Olivia's contact information -- [ ] Sync with [[person-matteo-cellini]] on pricing — they want a volume discount for the 6-episode block diff --git a/demo-vault-v2/event-sponsor-call-2024-02-02.md b/demo-vault-v2/event-sponsor-call-2024-02-02.md deleted file mode 100644 index 5fc187bd..00000000 --- a/demo-vault-v2/event-sponsor-call-2024-02-02.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -aliases: ["Sponsor call — 2024-02-02"] -Is A: Event -Date: "2024-02-02" -Belongs to: "[[2024-02]]" -Related to: ["[[person-lisa-chen]]"] -Tags: ["Work"] ---- -# Sponsor call — 2024-02-02 -Sponsor discovery/renewal call. Discussed placement and campaign goals. - -## Notes -- Lisa is the marketing lead at DevMetrics, a developer analytics and DORA metrics platform that helps engineering orgs measure team performance -- Initial discovery call; DevMetrics wants to sponsor episodes specifically related to engineering productivity, team scaling, and technical leadership — strong alignment with our content themes -- Discussed a trial sponsorship of 4 episodes to test audience response before committing to a longer campaign; Lisa wants to measure sign-up conversions through a dedicated URL -- Revenue potential is significant — DevMetrics has indicated a willingness to move to a premium sponsorship tier if the trial performs well, which could represent one of our larger deals this year -- Lisa asked about the possibility of having their CEO appear as a podcast guest as part of a broader partnership — need to evaluate whether that fits editorially - -## Follow-up -- [ ] Send media kit with trial sponsorship pricing and audience demographics -- [ ] Update CRM with DevMetrics opportunity and estimated deal value -- [ ] Follow up in 10 days with Lisa after her team reviews the proposal diff --git a/demo-vault-v2/event-sponsor-call-2024-02-16.md b/demo-vault-v2/event-sponsor-call-2024-02-16.md deleted file mode 100644 index 52728004..00000000 --- a/demo-vault-v2/event-sponsor-call-2024-02-16.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -aliases: ["Sponsor call — 2024-02-16"] -Is A: Event -Date: "2024-02-16" -Belongs to: "[[2024-02]]" -Related to: ["[[person-rachel-green]]"] -Tags: ["Work"] ---- -# Sponsor call — 2024-02-16 -Sponsor discovery/renewal call. Discussed placement and campaign goals. - -## Notes -- Rachel represents StackBridge, a code review and pull request automation tool aimed at reducing review bottlenecks in engineering teams -- Discovery call focused on StackBridge's Q2 marketing plans; they want to target senior engineers and engineering managers who feel the pain of slow code review cycles -- Discussed mid-roll sponsorship placement on 8 episodes with a focus on content about team workflow, developer experience, and engineering efficiency -- Rachel expressed concern about audience overlap with another podcast they already sponsor — I shared our unique listener demographics data showing we skew more senior and international than competitors -- New relationship; Rachel was referred by a mutual contact in the developer marketing space - -## Follow-up -- [ ] Send detailed audience overlap analysis and unique listener data to Rachel -- [ ] Update CRM with StackBridge as a warm lead -- [ ] Sync with [[person-matteo-cellini]] on pricing for the 8-episode package diff --git a/demo-vault-v2/event-sponsor-call-2024-03-01.md b/demo-vault-v2/event-sponsor-call-2024-03-01.md deleted file mode 100644 index 4722f9e0..00000000 --- a/demo-vault-v2/event-sponsor-call-2024-03-01.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -aliases: ["Sponsor call — 2024-03-01"] -Is A: Event -Date: "2024-03-01" -Belongs to: "[[2024-03]]" -Related to: ["[[person-peter-schmidt]]"] -Tags: ["Work"] ---- -# Sponsor call — 2024-03-01 -Sponsor discovery/renewal call. Discussed placement and campaign goals. - -## Notes -- Peter is the partnerships director at InfraWatch, an infrastructure monitoring and alerting platform competing in the observability space alongside Datadog and Grafana -- Renewal discussion for their existing 6-month sponsorship; their current deal expires at the end of April and they want to extend with updated terms -- Reviewed campaign performance metrics from the first half of their sponsorship — click-through rates are above their internal benchmarks and they are satisfied with the quality of leads generated -- Peter requested an upgrade to include newsletter sponsorship alongside the podcast placements, which would increase the deal value by approximately 30 percent -- Strong existing relationship; InfraWatch has been one of our most consistent sponsors and the product resonates genuinely with our audience - -## Follow-up -- [ ] Prepare renewal proposal with newsletter add-on pricing -- [ ] Update CRM with renewal status and updated deal value -- [ ] Follow up with Peter by mid-March to finalize the extended contract diff --git a/demo-vault-v2/event-sponsor-call-2024-03-15.md b/demo-vault-v2/event-sponsor-call-2024-03-15.md deleted file mode 100644 index 4fc3c03e..00000000 --- a/demo-vault-v2/event-sponsor-call-2024-03-15.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -aliases: ["Sponsor call — 2024-03-15"] -Is A: Event -Date: "2024-03-15" -Belongs to: "[[2024-03]]" -Related to: ["[[person-sophie-laurent]]"] -Tags: ["Work"] ---- -# Sponsor call — 2024-03-15 -Sponsor discovery/renewal call. Discussed placement and campaign goals. - -## Notes -- Sophie represents DeployPilot, a deployment automation SaaS platform focused on reducing failed deployments and rollback complexity for mid-size engineering teams -- Discovery call; DeployPilot is a Series B startup that recently closed funding and is allocating budget to developer-focused content marketing for the first time -- Discussed a 4-episode trial sponsorship with pre-roll placement; Sophie was interested in aligning their sponsorship with episodes about CI/CD, platform engineering, and deployment practices -- Sophie's main concern was measuring ROI — she asked about attribution tracking, custom URLs, and whether we can provide post-campaign analytics reports with download numbers by episode -- New lead; Sophie found us through the podcast directories and has been evaluating our content for about two months before reaching out - -## Follow-up -- [ ] Send proposal with detailed attribution tracking capabilities and sample post-campaign report -- [ ] Update CRM with DeployPilot details and Sophie's requirements -- [ ] Follow up in one week after Sophie presents the proposal to her VP of Marketing diff --git a/demo-vault-v2/event-sponsor-call-2024-03-29.md b/demo-vault-v2/event-sponsor-call-2024-03-29.md deleted file mode 100644 index b3388aae..00000000 --- a/demo-vault-v2/event-sponsor-call-2024-03-29.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -aliases: ["Sponsor call — 2024-03-29"] -Is A: Event -Date: "2024-03-29" -Belongs to: "[[2024-03]]" -Related to: ["[[person-emma-wilson]]"] -Tags: ["Work"] ---- -# Sponsor call — 2024-03-29 -Sponsor discovery/renewal call. Discussed placement and campaign goals. - -## Notes -- Emma is the head of marketing at SecureShip, a software supply chain security platform that helps engineering teams secure their build pipelines and dependency management -- Discovery call to explore a content partnership; Emma is interested in going beyond standard ad reads to include a co-branded mini-series on supply chain security topics -- Discussed a premium package that would include 6 sponsored episodes plus a dedicated 3-episode mini-series where their CTO joins as a recurring guest — this would be a first for our show format -- Revenue potential is high — the combined package would be our largest single sponsor deal if it closes; Emma indicated budget is pre-approved for the right partner -- Relationship status: new lead, but Emma has a strong reputation in the developer marketing space and came with a clear vision for the partnership - -## Follow-up -- [ ] Draft a custom proposal for the mini-series format with pricing -- [ ] Sync with [[person-matteo-cellini]] on pricing for the premium co-branded package -- [ ] Follow up with Emma in two weeks with the proposal and sample content calendar diff --git a/demo-vault-v2/event-sponsor-call-2024-04-12.md b/demo-vault-v2/event-sponsor-call-2024-04-12.md deleted file mode 100644 index 8186b8fe..00000000 --- a/demo-vault-v2/event-sponsor-call-2024-04-12.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -aliases: ["Sponsor call — 2024-04-12"] -Is A: Event -Date: "2024-04-12" -Belongs to: "[[2024-04]]" -Related to: ["[[person-carlos-mendez]]"] -Tags: ["Work"] ---- -# Sponsor call — 2024-04-12 -Sponsor discovery/renewal call. Discussed placement and campaign goals. - -## Notes -- Carlos manages partnerships at CodeVault, an enterprise code hosting and collaboration platform positioning itself as a GitHub alternative for organizations with strict compliance requirements -- Discovery call; CodeVault is targeting regulated industries (finance, healthcare, government) and sees our audience of engineering leaders as the key decision-makers for platform adoption -- Discussed a 6-month sponsorship commitment with mid-roll placements and quarterly performance reviews; Carlos wants to align messaging with our episodes on security, compliance, and enterprise engineering practices -- Carlos raised a concern about exclusivity — they want assurance that no direct competitor (GitHub, GitLab) will sponsor adjacent episodes; we discussed a category exclusivity add-on -- New lead with strong revenue potential; CodeVault is well-funded and has an ambitious marketing plan for 2024 - -## Follow-up -- [ ] Send proposal with category exclusivity pricing and terms -- [ ] Update CRM with CodeVault opportunity and Carlos's contact information -- [ ] Follow up in two weeks after Carlos reviews with his leadership team diff --git a/demo-vault-v2/event-sponsor-call-2024-04-26.md b/demo-vault-v2/event-sponsor-call-2024-04-26.md deleted file mode 100644 index 739f0090..00000000 --- a/demo-vault-v2/event-sponsor-call-2024-04-26.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -aliases: ["Sponsor call — 2024-04-26"] -Is A: Event -Date: "2024-04-26" -Belongs to: "[[2024-04]]" -Related to: ["[[person-anna-kowalski]]"] -Tags: ["Work"] ---- -# Sponsor call — 2024-04-26 -Sponsor discovery/renewal call. Discussed placement and campaign goals. - -## Notes -- Anna is the developer marketing manager at TestGrid, a cloud-based testing infrastructure platform that provides on-demand browser and device farms for automated testing -- Discovery call to explore podcast sponsorship; TestGrid is expanding into the engineering leadership segment after previously focusing on individual developer audiences -- Discussed a 4-episode trial with pre-roll placement, specifically targeting episodes about testing strategies, quality engineering, and mobile development — strong content alignment with their product -- Anna asked about the possibility of running A/B tests on different ad copy across episodes to optimize messaging; we discussed how to structure that within our standard sponsorship framework -- New lead; Anna found our show through industry conference networking and has been tracking our download metrics for the past quarter - -## Follow-up -- [ ] Send media kit with trial sponsorship options and A/B testing structure -- [ ] Update CRM with TestGrid details and estimated deal size -- [ ] Sync with [[person-matteo-cellini]] on whether the A/B copy testing is feasible operationally diff --git a/demo-vault-v2/event-sponsor-call-2024-05-10.md b/demo-vault-v2/event-sponsor-call-2024-05-10.md deleted file mode 100644 index 882ebbd0..00000000 --- a/demo-vault-v2/event-sponsor-call-2024-05-10.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -aliases: ["Sponsor call — 2024-05-10"] -Is A: Event -Date: "2024-05-10" -Belongs to: "[[2024-05]]" -Related to: ["[[person-emma-wilson]]"] -Tags: ["Work"] ---- -# Sponsor call — 2024-05-10 -Sponsor discovery/renewal call. Discussed placement and campaign goals. - -## Notes -- Follow-up call with Emma from SecureShip to finalize the co-branded mini-series proposal and standard sponsorship package -- Emma confirmed budget approval for the premium package; her team is ready to move forward with 6 sponsored episodes plus the 3-episode security mini-series starting in July -- Discussed content calendar and agreed on a monthly cadence for the mini-series episodes; their CTO will join as guest but we retain full editorial control over questions and topic framing -- Deal value is confirmed as our largest single-sponsor commitment this year — significant revenue milestone for the show -- Emma requested a contract review period of two weeks before signing; their legal team needs to approve the co-branding terms - -## Follow-up -- [ ] Send final contract and content calendar to Emma for legal review -- [ ] Update CRM with confirmed deal value and expected signing date -- [ ] Sync with [[person-matteo-cellini]] on production planning for the mini-series episodes diff --git a/demo-vault-v2/event-sponsor-call-2024-05-24.md b/demo-vault-v2/event-sponsor-call-2024-05-24.md deleted file mode 100644 index 56f958c1..00000000 --- a/demo-vault-v2/event-sponsor-call-2024-05-24.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -aliases: ["Sponsor call — 2024-05-24"] -Is A: Event -Date: "2024-05-24" -Belongs to: "[[2024-05]]" -Related to: ["[[person-peter-schmidt]]"] -Tags: ["Work"] ---- -# Sponsor call — 2024-05-24 -Sponsor discovery/renewal call. Discussed placement and campaign goals. - -## Notes -- Follow-up with Peter from InfraWatch to finalize the renewal contract with the newsletter add-on that was discussed in March -- Peter confirmed the extended deal: 6-month podcast sponsorship renewal plus bi-weekly newsletter sponsorship, representing a 30 percent increase over their previous contract value -- Reviewed updated campaign performance data from Q1 — InfraWatch's conversion rates from our audience are approximately 2x their industry average for podcast sponsorship, which justified the budget increase internally -- Peter mentioned they are planning a major product release in Q3 and want to coordinate a sponsored episode around the launch with a special offer for our listeners -- Strong ongoing relationship; InfraWatch continues to be one of our best sponsor partnerships in terms of both revenue and audience fit - -## Follow-up -- [ ] Send renewal contract with newsletter add-on terms for Peter's signature -- [ ] Update CRM with renewed deal value and contract dates -- [ ] Follow up in one week to confirm signed contract and coordinate Q3 launch episode diff --git a/demo-vault-v2/event-sponsor-call-2024-06-07.md b/demo-vault-v2/event-sponsor-call-2024-06-07.md deleted file mode 100644 index 1e8dd93c..00000000 --- a/demo-vault-v2/event-sponsor-call-2024-06-07.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -aliases: ["Sponsor call — 2024-06-07"] -Is A: Event -Date: "2024-06-07" -Belongs to: "[[2024-06]]" -Related to: ["[[person-thomas-mueller]]"] -Tags: ["Work"] ---- -# Sponsor call — 2024-06-07 -Sponsor discovery/renewal call. Discussed placement and campaign goals. - -## Notes -- Thomas represents APIForge, a developer-focused API management and gateway platform that recently expanded into the European market -- Discovery call; APIForge is building brand awareness among engineering teams evaluating API infrastructure solutions and sees podcast sponsorship as a key channel for reaching technical decision-makers -- Discussed a 3-month sponsorship with pre-roll placements; Thomas was particularly interested in targeting episodes about API design, backend architecture, and developer experience -- Thomas asked about geographical audience breakdown — their European expansion makes our international listener base (approximately 40 percent outside the US) especially attractive compared to US-centric competitors -- New lead; Thomas reached out after hearing a recommendation from another sponsor in the dev tools space - -## Follow-up -- [ ] Send media kit with geographic audience breakdown data -- [ ] Update CRM with APIForge details and Thomas's contact information -- [ ] Follow up in two weeks once Thomas has reviewed the proposal with his marketing team diff --git a/demo-vault-v2/event-sponsor-call-2024-06-21.md b/demo-vault-v2/event-sponsor-call-2024-06-21.md deleted file mode 100644 index 93722b87..00000000 --- a/demo-vault-v2/event-sponsor-call-2024-06-21.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -aliases: ["Sponsor call — 2024-06-21"] -Is A: Event -Date: "2024-06-21" -Belongs to: "[[2024-06]]" -Related to: ["[[person-olivia-martinez]]"] -Tags: ["Work"] ---- -# Sponsor call — 2024-06-21 -Sponsor discovery/renewal call. Discussed placement and campaign goals. - -## Notes -- Follow-up with Olivia from CloudForge to review results from their initial 6-episode sponsorship block and discuss renewal options -- Campaign performance exceeded CloudForge's expectations — landing page conversions from our custom tracking URL outperformed their other podcast sponsorships by 45 percent -- Olivia wants to renew with an expanded package: 12 episodes over 6 months with both pre-roll and mid-roll placements, plus a dedicated sponsored segment in the newsletter -- Discussed timing the renewal to coincide with CloudForge's Q3 product launch; they want heavier placement density in August and September around the launch window -- Relationship has matured from cold lead to one of our top sponsors; Olivia has become an advocate for podcast sponsorship internally at CloudForge - -## Follow-up -- [ ] Prepare renewal proposal with the expanded package and launch-aligned scheduling -- [ ] Update CRM with renewed opportunity value — this is now a top-3 sponsor by revenue -- [ ] Sync with [[person-matteo-cellini]] on pricing for the expanded package with launch surge diff --git a/demo-vault-v2/event-sponsor-call-2024-07-05.md b/demo-vault-v2/event-sponsor-call-2024-07-05.md deleted file mode 100644 index fab93edf..00000000 --- a/demo-vault-v2/event-sponsor-call-2024-07-05.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -aliases: ["Sponsor call — 2024-07-05"] -Is A: Event -Date: "2024-07-05" -Belongs to: "[[2024-07]]" -Related to: ["[[person-lisa-chen]]"] -Tags: ["Work"] ---- -# Sponsor call — 2024-07-05 -Sponsor discovery/renewal call. Discussed placement and campaign goals. - -## Notes -- Follow-up with Lisa from DevMetrics to review the results of their 4-episode trial sponsorship and discuss converting to a longer-term deal -- Trial performance was solid — DevMetrics saw a measurable uptick in trial sign-ups from our audience, though conversion to paid was slightly below their target; Lisa attributes this to the trial length rather than audience quality -- Lisa wants to extend to a 6-month commitment with adjusted messaging that emphasizes the ROI case for engineering leaders rather than the individual developer value proposition -- Discussed the CEO guest appearance idea again — after reviewing it editorially, we agreed on a format where the CEO joins a panel discussion episode rather than a solo interview, which preserves editorial independence while giving DevMetrics the visibility they want -- Relationship progressing well; the trial-to-long-term conversion validates our approach of offering trial packages to new sponsors - -## Follow-up -- [ ] Send renewal proposal with updated messaging framework and 6-month pricing -- [ ] Update CRM with DevMetrics conversion from trial to long-term and revised deal value -- [ ] Follow up with Lisa in one week to align on the panel episode timing diff --git a/demo-vault-v2/event-sponsor-call-2024-07-19.md b/demo-vault-v2/event-sponsor-call-2024-07-19.md deleted file mode 100644 index 8807d094..00000000 --- a/demo-vault-v2/event-sponsor-call-2024-07-19.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -aliases: ["Sponsor call — 2024-07-19"] -Is A: Event -Date: "2024-07-19" -Belongs to: "[[2024-07]]" -Related to: ["[[person-peter-schmidt]]"] -Tags: ["Work"] ---- -# Sponsor call — 2024-07-19 -Sponsor discovery/renewal call. Discussed placement and campaign goals. - -## Notes -- Quarterly check-in with Peter from InfraWatch to review campaign performance and plan the Q3 product launch episode discussed in May -- InfraWatch's listener engagement continues to be strong — Peter shared internal attribution data showing our podcast drives more qualified leads per dollar than their paid search campaigns -- Finalized plans for the sponsored product launch episode in September: a dedicated 10-minute segment where we discuss the new features in a conversational format rather than a scripted ad read -- Peter also raised the idea of sponsoring a live recording at an upcoming conference where InfraWatch will have a booth — exploring logistics and pricing for this -- Relationship remains one of our strongest; Peter has been easy to work with and InfraWatch's product continues to be genuinely relevant to our audience - -## Follow-up -- [ ] Draft the product launch segment script framework and send to Peter for review -- [ ] Update CRM with the live recording sponsorship as a potential upsell opportunity -- [ ] Follow up on conference logistics with Peter by end of July diff --git a/demo-vault-v2/event-sponsor-call-2024-08-02.md b/demo-vault-v2/event-sponsor-call-2024-08-02.md deleted file mode 100644 index a9e435be..00000000 --- a/demo-vault-v2/event-sponsor-call-2024-08-02.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -aliases: ["Sponsor call — 2024-08-02"] -Is A: Event -Date: "2024-08-02" -Belongs to: "[[2024-08]]" -Related to: ["[[person-michael-brown]]"] -Tags: ["Work"] ---- -# Sponsor call — 2024-08-02 -Sponsor discovery/renewal call. Discussed placement and campaign goals. - -## Notes -- Michael is the VP of Marketing at PipelineHQ, a CI/CD platform that differentiates on speed and simplicity for small-to-medium engineering teams -- Discovery call; PipelineHQ is a bootstrapped company that has grown primarily through word of mouth and is now investing in podcast sponsorship for the first time as part of a broader brand awareness push -- Discussed a conservative 3-episode trial with mid-roll placement; Michael is budget-conscious and wants to see clear ROI data before committing to a longer run -- Michael's main concern was whether our audience skews too senior for their product — PipelineHQ targets teams of 5-30 engineers, and Michael worried that VP-level listeners might not be hands-on enough to evaluate a CI/CD tool; I shared data showing that 60 percent of our audience is still IC or team lead level -- New lead; Michael found us through podcast analytics platforms and has been comparing our metrics against two other shows - -## Follow-up -- [ ] Send proposal with the 3-episode trial package and audience seniority breakdown -- [ ] Update CRM with PipelineHQ as a new prospect -- [ ] Follow up in two weeks with Michael after he presents to his co-founder diff --git a/demo-vault-v2/event-sponsor-call-2024-08-16.md b/demo-vault-v2/event-sponsor-call-2024-08-16.md deleted file mode 100644 index 0721649c..00000000 --- a/demo-vault-v2/event-sponsor-call-2024-08-16.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -aliases: ["Sponsor call — 2024-08-16"] -Is A: Event -Date: "2024-08-16" -Belongs to: "[[2024-08]]" -Related to: ["[[person-emma-wilson]]"] -Tags: ["Work"] ---- -# Sponsor call — 2024-08-16 -Sponsor discovery/renewal call. Discussed placement and campaign goals. - -## Notes -- Mid-campaign check-in with Emma from SecureShip; the co-branded security mini-series launched in July and the first two episodes have performed well -- Download numbers for the mini-series episodes are tracking at 85 percent of regular episode performance, which exceeds Emma's expectations for sponsored content — she was concerned it might underperform due to the overtly sponsored nature -- Discussed adjustments to the remaining mini-series episode topics based on listener feedback — pivoting the third episode from supply chain attacks to dependency management, which generated more engagement in previous episodes -- Emma is already thinking about a renewal for 2025 and wants to explore expanding the partnership to include a sponsored research report on software supply chain security -- Relationship continues to strengthen; this partnership is becoming a model for how we want to structure premium sponsorships going forward - -## Follow-up -- [ ] Send updated content plan for the remaining mini-series episode to Emma for approval -- [ ] Update CRM with 2025 renewal pipeline opportunity -- [ ] Sync with [[person-matteo-cellini]] on pricing for the research report sponsorship concept diff --git a/demo-vault-v2/event-sponsor-call-2024-08-30.md b/demo-vault-v2/event-sponsor-call-2024-08-30.md deleted file mode 100644 index ca0655d9..00000000 --- a/demo-vault-v2/event-sponsor-call-2024-08-30.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -aliases: ["Sponsor call — 2024-08-30"] -Is A: Event -Date: "2024-08-30" -Belongs to: "[[2024-08]]" -Related to: ["[[person-michael-brown]]"] -Tags: ["Work"] ---- -# Sponsor call — 2024-08-30 -Sponsor discovery/renewal call. Discussed placement and campaign goals. - -## Notes -- Follow-up with Michael from PipelineHQ after the first episode of their 3-episode trial aired; initial results are promising -- Michael reported a noticeable spike in trial sign-ups that correlated with the episode publish date — approximately 40 new trial accounts in the first week, which is above their threshold for a successful channel test -- Discussed adjusting the ad copy for the remaining two episodes based on what resonated: the "setup in 5 minutes" messaging performed better than the feature comparison angle -- Michael is now open to discussing a longer commitment if the remaining trial episodes maintain similar performance; mentioned budget for a 6-episode extension -- Relationship warming quickly; Michael's initial skepticism about audience fit has been addressed by the trial data - -## Follow-up -- [ ] Prepare updated ad copy for the remaining two trial episodes -- [ ] Update CRM with PipelineHQ trial performance data and potential extension deal -- [ ] Follow up after the third trial episode airs to discuss the 6-episode extension diff --git a/demo-vault-v2/event-sponsor-call-2024-09-13.md b/demo-vault-v2/event-sponsor-call-2024-09-13.md deleted file mode 100644 index ff144d07..00000000 --- a/demo-vault-v2/event-sponsor-call-2024-09-13.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -aliases: ["Sponsor call — 2024-09-13"] -Is A: Event -Date: "2024-09-13" -Belongs to: "[[2024-09]]" -Related to: ["[[person-anna-kowalski]]"] -Tags: ["Work"] ---- -# Sponsor call — 2024-09-13 -Sponsor discovery/renewal call. Discussed placement and campaign goals. - -## Notes -- Follow-up with Anna from TestGrid to review results from their 4-episode trial sponsorship that wrapped up in August -- The A/B copy testing produced useful data: the messaging focused on "eliminate flaky tests" outperformed the broader "testing infrastructure" messaging by a significant margin, suggesting our audience feels the pain of test reliability more than test coverage -- Anna wants to convert to a 6-month sponsorship with the winning ad copy, and is requesting a discount for the extended commitment — we discussed a 10 percent volume discount which aligns with our standard rate card -- TestGrid's CEO was impressed with the trial results and has approved a larger marketing budget for podcast sponsorship in Q4 and into 2025 -- Relationship has progressed smoothly from trial to long-term; the data-driven approach with A/B testing built trust on both sides - -## Follow-up -- [ ] Send 6-month sponsorship contract with the volume discount applied -- [ ] Update CRM with TestGrid conversion from trial to long-term and updated revenue forecast -- [ ] Sync with [[person-matteo-cellini]] on the volume discount approval diff --git a/demo-vault-v2/event-sponsor-call-2024-09-27.md b/demo-vault-v2/event-sponsor-call-2024-09-27.md deleted file mode 100644 index 42cecf36..00000000 --- a/demo-vault-v2/event-sponsor-call-2024-09-27.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -aliases: ["Sponsor call — 2024-09-27"] -Is A: Event -Date: "2024-09-27" -Belongs to: "[[2024-09]]" -Related to: ["[[person-kenji-tanaka]]"] -Tags: ["Work"] ---- -# Sponsor call — 2024-09-27 -Sponsor discovery/renewal call. Discussed placement and campaign goals. - -## Notes -- Kenji represents KubeScale, an enterprise Kubernetes management platform that simplifies cluster operations for teams without dedicated platform engineering resources -- Discovery call; KubeScale is targeting engineering leaders at mid-size companies who are adopting Kubernetes but struggling with operational complexity — a segment that aligns well with our audience -- Discussed a 4-episode sponsorship focused on episodes about infrastructure, platform engineering, and cloud-native architecture -- Kenji asked about the possibility of sponsoring a specific recurring guest's episodes — he wants to align KubeScale's messaging with Elena Konstantinou's platform engineering segments, which are our highest-performing content in that category -- New lead; Kenji was introduced through a mutual connection at a Kubernetes community event - -## Follow-up -- [ ] Send proposal with standard and guest-aligned sponsorship options -- [ ] Update CRM with KubeScale details and Kenji's contact information -- [ ] Follow up in two weeks after Kenji reviews the proposal with his team diff --git a/demo-vault-v2/event-sponsor-call-2024-10-11.md b/demo-vault-v2/event-sponsor-call-2024-10-11.md deleted file mode 100644 index b079a98e..00000000 --- a/demo-vault-v2/event-sponsor-call-2024-10-11.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -aliases: ["Sponsor call — 2024-10-11"] -Is A: Event -Date: "2024-10-11" -Belongs to: "[[2024-10]]" -Related to: ["[[person-rachel-green]]"] -Tags: ["Work"] ---- -# Sponsor call — 2024-10-11 -Sponsor discovery/renewal call. Discussed placement and campaign goals. - -## Notes -- Follow-up with Rachel from StackBridge to convert their initial interest into a signed sponsorship; they have been in the pipeline since February -- Rachel confirmed they are ready to proceed with an 8-episode sponsorship starting in November, having resolved her earlier concerns about audience overlap with their other podcast partnerships -- Discussed ad copy and positioning: StackBridge wants to lead with a "speed up code reviews by 40 percent" claim backed by their customer data, which fits naturally into episodes about developer productivity and team efficiency -- Rachel negotiated a 5 percent discount for upfront payment of the full 8-episode block, which is within our standard terms -- Long sales cycle but worth the wait; StackBridge's deal represents solid mid-tier revenue and their product is a genuine fit for our audience - -## Follow-up -- [ ] Send final contract with upfront payment terms and the 5 percent discount -- [ ] Update CRM with StackBridge as a closed deal and adjust Q4 revenue forecast -- [ ] Follow up in one week to confirm contract signature and coordinate ad copy review diff --git a/demo-vault-v2/event-sponsor-call-2024-10-25.md b/demo-vault-v2/event-sponsor-call-2024-10-25.md deleted file mode 100644 index ee85637e..00000000 --- a/demo-vault-v2/event-sponsor-call-2024-10-25.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -aliases: ["Sponsor call — 2024-10-25"] -Is A: Event -Date: "2024-10-25" -Belongs to: "[[2024-10]]" -Related to: ["[[person-kenji-tanaka]]"] -Tags: ["Work"] ---- -# Sponsor call — 2024-10-25 -Sponsor discovery/renewal call. Discussed placement and campaign goals. - -## Notes -- Follow-up with Kenji from KubeScale to finalize sponsorship terms after their initial discovery call in September -- Kenji confirmed a 4-episode sponsorship with guest-aligned placement on platform engineering episodes; this is a new sponsorship format for us and sets a precedent for content-matched advertising -- Discussed pricing for the guest-aligned premium: a 15 percent uplift over standard placement, which Kenji accepted given the higher expected relevance and engagement for their target audience -- KubeScale will provide a unique discount code for our listeners, offering an extended trial period for their platform management tools -- Relationship has moved quickly from discovery to close; Kenji is decisive and has internal approval authority, which speeds up the process - -## Follow-up -- [ ] Send signed contract with the guest-aligned placement schedule -- [ ] Update CRM with KubeScale as a closed deal and log the premium pricing model -- [ ] Sync with [[person-matteo-cellini]] on operationalizing the guest-aligned placement format diff --git a/demo-vault-v2/event-sponsor-call-2024-11-08.md b/demo-vault-v2/event-sponsor-call-2024-11-08.md deleted file mode 100644 index 5e792068..00000000 --- a/demo-vault-v2/event-sponsor-call-2024-11-08.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -aliases: ["Sponsor call — 2024-11-08"] -Is A: Event -Date: "2024-11-08" -Belongs to: "[[2024-11]]" -Related to: ["[[person-kenji-tanaka]]"] -Tags: ["Work"] ---- -# Sponsor call — 2024-11-08 -Sponsor discovery/renewal call. Discussed placement and campaign goals. - -## Notes -- Check-in with Kenji from KubeScale after their first sponsored episode aired last week; early performance data is encouraging -- The guest-aligned placement on Elena Konstantinou's platform engineering episode generated 3x the click-through rate compared to KubeScale's standard digital ad campaigns — Kenji is very pleased with the results -- Discussed extending the sponsorship beyond the initial 4 episodes; Kenji wants to explore a 2025 annual commitment that covers all platform engineering and infrastructure episodes -- Kenji also raised the possibility of co-sponsoring a live event or webinar with us in 2025, which would be a new revenue stream to explore -- The guest-aligned sponsorship model is proving its value; this data point will help us sell the premium format to other sponsors - -## Follow-up -- [ ] Prepare a 2025 annual sponsorship proposal with pricing tiers for KubeScale -- [ ] Update CRM with the upsell opportunity and live event interest -- [ ] Follow up with Kenji in December to align on 2025 planning timelines diff --git a/demo-vault-v2/event-sponsor-call-2024-11-22.md b/demo-vault-v2/event-sponsor-call-2024-11-22.md deleted file mode 100644 index d4257657..00000000 --- a/demo-vault-v2/event-sponsor-call-2024-11-22.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -aliases: ["Sponsor call — 2024-11-22"] -Is A: Event -Date: "2024-11-22" -Belongs to: "[[2024-11]]" -Related to: ["[[person-james-mitchell]]"] -Tags: ["Work"] ---- -# Sponsor call — 2024-11-22 -Sponsor discovery/renewal call. Discussed placement and campaign goals. - -## Notes -- James represents DocuDev, a developer documentation platform that generates and maintains API documentation from code annotations and OpenAPI specs -- Discovery call; DocuDev is a well-funded Series C company looking to shift their marketing focus from developer-focused grassroots campaigns to targeting engineering leaders who make tooling decisions for their teams -- Discussed a 6-month sponsorship with mid-roll placements; James is interested in aligning messaging with episodes about developer experience, API design, and documentation practices -- James asked about case study sponsorships — a format where we interview a DocuDev customer about their documentation workflow, blending editorial content with sponsor messaging; an interesting concept that needs editorial evaluation -- New lead with significant revenue potential; DocuDev has a large marketing budget and is evaluating podcast sponsorship as a long-term channel - -## Follow-up -- [ ] Send media kit with 6-month pricing and case study sponsorship concept outline -- [ ] Update CRM with DocuDev as a high-value prospect -- [ ] Sync with [[person-matteo-cellini]] on the editorial implications of the case study format diff --git a/demo-vault-v2/event-sponsor-call-2024-12-06.md b/demo-vault-v2/event-sponsor-call-2024-12-06.md deleted file mode 100644 index 8c990fd2..00000000 --- a/demo-vault-v2/event-sponsor-call-2024-12-06.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -aliases: ["Sponsor call — 2024-12-06"] -Is A: Event -Date: "2024-12-06" -Belongs to: "[[2024-12]]" -Related to: ["[[person-carlos-mendez]]"] -Tags: ["Work"] ---- -# Sponsor call — 2024-12-06 -Sponsor discovery/renewal call. Discussed placement and campaign goals. - -## Notes -- Follow-up with Carlos from CodeVault; they have been in the pipeline since April and are now ready to commit after completing their internal budget planning for 2025 -- Carlos confirmed a 6-month sponsorship starting in January 2025 with category exclusivity in the code hosting and version control space — no GitHub or GitLab ads during their sponsorship period -- The category exclusivity premium was agreed at 20 percent above standard rates, which Carlos's leadership approved given the competitive advantage of owning the category in our audience's mind -- Discussed messaging strategy: CodeVault wants to position themselves as the enterprise-grade alternative for teams with compliance requirements, targeting the subset of our audience at regulated companies -- Long sales cycle finally closing; the 8-month pipeline duration is our longest to date, but the deal value justifies the patience - -## Follow-up -- [ ] Send final contract with category exclusivity terms and 2025 scheduling -- [ ] Update CRM with CodeVault as a closed deal and adjust 2025 revenue projections -- [ ] Follow up with Carlos by mid-December to finalize contract before the holiday break diff --git a/demo-vault-v2/event-sponsor-call-2024-12-20.md b/demo-vault-v2/event-sponsor-call-2024-12-20.md deleted file mode 100644 index 18a7ec3e..00000000 --- a/demo-vault-v2/event-sponsor-call-2024-12-20.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -aliases: ["Sponsor call — 2024-12-20"] -Is A: Event -Date: "2024-12-20" -Belongs to: "[[2024-12]]" -Related to: ["[[person-anna-kowalski]]"] -Tags: ["Work"] ---- -# Sponsor call — 2024-12-20 -Sponsor discovery/renewal call. Discussed placement and campaign goals. - -## Notes -- Year-end review call with Anna from TestGrid to assess the full 6-month sponsorship performance and discuss 2025 renewal -- TestGrid's sponsorship has been consistently strong throughout the second half of 2024; their "eliminate flaky tests" messaging continues to drive high engagement and the custom landing page conversion rate has held steady -- Anna wants to renew for all of 2025 with an expanded scope: adding newsletter sponsorship and exploring a co-produced testing best practices guide that we would promote through our channels -- Discussed pricing for the expanded 2025 package — Anna is targeting a 10 percent overall budget increase from her leadership, which should accommodate the expanded scope within our pricing framework -- TestGrid has become one of our most reliable and easiest-to-work-with sponsors; the A/B testing approach they brought to ad copy has become something we now offer to all sponsors - -## Follow-up -- [ ] Prepare 2025 renewal proposal with newsletter and content guide add-ons -- [ ] Update CRM with TestGrid renewal pipeline and estimated 2025 deal value -- [ ] Sync with [[person-matteo-cellini]] on pricing and production costs for the testing guide diff --git a/demo-vault-v2/event-sponsor-call-2025-01-03.md b/demo-vault-v2/event-sponsor-call-2025-01-03.md deleted file mode 100644 index bbe3c88d..00000000 --- a/demo-vault-v2/event-sponsor-call-2025-01-03.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -aliases: ["Sponsor call — 2025-01-03"] -Is A: Event -Date: "2025-01-03" -Belongs to: "[[2025-01]]" -Related to: ["[[person-peter-schmidt]]"] -Tags: ["Work"] ---- -# Sponsor call — 2025-01-03 -Sponsor discovery/renewal call. Discussed placement and campaign goals. - -## Notes -- New year kick-off call with Peter from InfraWatch to align on their 2025 sponsorship strategy and review 2024 annual performance -- InfraWatch's 2024 sponsorship delivered strong results across all metrics — Peter shared that podcast-sourced leads had a 35 percent higher close rate than leads from any other marketing channel, making us their highest-performing partnership -- Peter confirmed InfraWatch's 2025 commitment: a full 12-month sponsorship with podcast, newsletter, and the live conference event discussed last year, making them our largest annual sponsor -- Discussed new initiatives for 2025: InfraWatch wants to co-produce a quarterly "State of Observability" report that we would publish and promote through our channels, adding a content marketing dimension to the partnership -- Flagship sponsor relationship; Peter's advocacy internally at InfraWatch has been instrumental in growing this partnership from a standard sponsorship to a comprehensive media partnership - -## Follow-up -- [ ] Send 2025 annual contract with all components (podcast, newsletter, conference, quarterly report) -- [ ] Update CRM with InfraWatch's 2025 annual commitment — largest deal in our history -- [ ] Follow up with Peter by mid-January to finalize the contract and Q1 content calendar diff --git a/demo-vault-v2/event-sponsor-call-2025-01-17.md b/demo-vault-v2/event-sponsor-call-2025-01-17.md deleted file mode 100644 index 5b24fb39..00000000 --- a/demo-vault-v2/event-sponsor-call-2025-01-17.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -aliases: ["Sponsor call — 2025-01-17"] -Is A: Event -Date: "2025-01-17" -Belongs to: "[[2025-01]]" -Related to: ["[[person-carlos-mendez]]"] -Tags: ["Work"] ---- -# Sponsor call — 2025-01-17 -Sponsor discovery/renewal call. Discussed placement and campaign goals. - -## Notes -- First check-in with Carlos from CodeVault after their 6-month sponsorship launched in January; reviewed ad copy and placement schedule for Q1 -- Carlos approved the first batch of ad copy focused on compliance-driven engineering teams; the messaging highlights CodeVault's SOC 2 and HIPAA compliance features, which differentiates them clearly from GitHub and GitLab -- Discussed coordination with upcoming episodes about security engineering and regulated industry practices — Carlos wants to ensure his ads run alongside these thematically relevant episodes whenever possible -- Carlos mentioned that CodeVault is planning a free tier launch in Q2 and wants to adjust messaging mid-contract to promote the new offering — we agreed this is within the standard terms as long as the core positioning stays consistent -- Relationship starting strong; Carlos is engaged and proactive about optimizing the sponsorship - -## Follow-up -- [ ] Confirm Q1 episode schedule with ad placements aligned to relevant content themes -- [ ] Update CRM with the Q2 messaging adjustment note -- [ ] Follow up with Carlos in February to review first month performance data diff --git a/demo-vault-v2/event-sponsor-call-2025-01-31.md b/demo-vault-v2/event-sponsor-call-2025-01-31.md deleted file mode 100644 index c49fb67c..00000000 --- a/demo-vault-v2/event-sponsor-call-2025-01-31.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -aliases: ["Sponsor call — 2025-01-31"] -Is A: Event -Date: "2025-01-31" -Belongs to: "[[2025-01]]" -Related to: ["[[person-olivia-martinez]]"] -Tags: ["Work"] ---- -# Sponsor call — 2025-01-31 -Sponsor discovery/renewal call. Discussed placement and campaign goals. - -## Notes -- 2025 planning call with Olivia from CloudForge; she has been promoted to Senior Director of Marketing and now oversees a larger budget allocation for podcast partnerships -- Olivia wants to expand CloudForge's sponsorship to include a year-long commitment with premium placements, newsletter integration, and exclusive sponsorship of our quarterly audience survey reports -- Discussed a new format idea: CloudForge would sponsor a "Cloud Infrastructure Corner" segment as a recurring feature within select episodes, giving them deeper brand integration than standard ad reads -- Revenue implications are significant — if CloudForge commits to the full package, they would become our second-largest sponsor behind InfraWatch, meaningfully increasing our annual revenue baseline -- Olivia's promotion and expanded authority signals that CloudForge views podcast sponsorship as a strategic marketing channel, not just an experiment - -## Follow-up -- [ ] Draft the "Cloud Infrastructure Corner" segment concept with format and pricing -- [ ] Update CRM with CloudForge's expanded 2025 opportunity and projected deal value -- [ ] Sync with [[person-matteo-cellini]] on production requirements for the recurring segment format diff --git a/demo-vault-v2/event-sponsor-call-2025-02-14.md b/demo-vault-v2/event-sponsor-call-2025-02-14.md deleted file mode 100644 index 710c29d7..00000000 --- a/demo-vault-v2/event-sponsor-call-2025-02-14.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -aliases: ["Sponsor call — 2025-02-14"] -Is A: Event -Date: "2025-02-14" -Belongs to: "[[2025-02]]" -Related to: ["[[person-david-kim]]"] -Tags: ["Work"] ---- -# Sponsor call — 2025-02-14 -Sponsor discovery/renewal call. Discussed placement and campaign goals. - -## Notes -- David represents FeatureFlagPro, a feature management and experimentation platform that competes with LaunchDarkly in the mid-market segment -- Discovery call; FeatureFlagPro is a growing startup that recently raised Series A funding and is investing heavily in developer-focused marketing to build brand awareness before their larger competitors dominate mindshare -- Discussed a 4-episode trial sponsorship with pre-roll placement; David is particularly interested in episodes about deployment practices, progressive delivery, and product engineering -- David asked about competitive exclusivity with respect to feature flag tools — we currently do not have any sponsors in that category, so exclusivity is not an issue at this time -- New lead with moderate revenue potential; FeatureFlagPro's budget is startup-scale but their enthusiasm for the partnership and product-audience fit are strong - -## Follow-up -- [ ] Send media kit with trial sponsorship pricing and available episode schedule -- [ ] Update CRM with FeatureFlagPro details and David's contact information -- [ ] Follow up in two weeks after David reviews the proposal with his marketing team diff --git a/demo-vault-v2/event-sponsor-call-2025-02-28.md b/demo-vault-v2/event-sponsor-call-2025-02-28.md deleted file mode 100644 index b00626a6..00000000 --- a/demo-vault-v2/event-sponsor-call-2025-02-28.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -aliases: ["Sponsor call — 2025-02-28"] -Is A: Event -Date: "2025-02-28" -Belongs to: "[[2025-02]]" -Related to: ["[[person-rachel-green]]"] -Tags: ["Work"] ---- -# Sponsor call — 2025-02-28 -Sponsor discovery/renewal call. Discussed placement and campaign goals. - -## Notes -- Renewal discussion with Rachel from StackBridge; their 8-episode sponsorship is completing this month and they want to evaluate results before committing to a 2025 extension -- Campaign performance was solid — StackBridge's click-through rates were consistent across all 8 episodes, and Rachel reported a measurable increase in demo requests from engineering leaders at companies with 50+ developers -- Rachel wants to renew with a 12-episode commitment for 2025 but requested a pricing adjustment to reflect the longer commitment; we discussed a tiered discount structure that rewards annual commitments -- She also asked about adding a case study format where we feature an engineering team that uses StackBridge to improve their code review process — similar to the format James Mitchell proposed for DocuDev -- StackBridge is now a proven sponsor with consistent results; the renewal should be straightforward once pricing is agreed - -## Follow-up -- [ ] Send renewal proposal with annual pricing and case study format option -- [ ] Update CRM with StackBridge renewal status and projected 2025 revenue -- [ ] Sync with [[person-matteo-cellini]] on the case study format pricing — standardize it across sponsors diff --git a/demo-vault-v2/event-sponsor-call-2025-03-14.md b/demo-vault-v2/event-sponsor-call-2025-03-14.md deleted file mode 100644 index 34379d3f..00000000 --- a/demo-vault-v2/event-sponsor-call-2025-03-14.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -aliases: ["Sponsor call — 2025-03-14"] -Is A: Event -Date: "2025-03-14" -Belongs to: "[[2025-03]]" -Related to: ["[[person-yuki-sato]]"] -Tags: ["Work"] ---- -# Sponsor call — 2025-03-14 -Sponsor discovery/renewal call. Discussed placement and campaign goals. - -## Notes -- Renewal call with Yuki from NovaCLI; their initial 3-month sponsorship has completed and they are ready to discuss next steps -- NovaCLI's Q1 sponsorship produced strong results — the developer productivity episodes drove particularly high engagement, with their custom promo code seeing redemption rates approximately 2x their industry benchmark -- Yuki confirmed budget approval for a 6-month extension at the premium tier, which includes both pre-roll and mid-roll placements plus newsletter mentions -- Discussed shifting NovaCLI's messaging for the renewal period: moving from general brand awareness to promoting their newly launched team collaboration features, targeting the engineering manager segment of our audience -- Relationship has matured nicely from initial discovery call to committed, longer-term sponsor; Yuki is responsive and understands our audience well - -## Follow-up -- [ ] Send renewal contract with premium tier pricing and updated messaging guidelines -- [ ] Update CRM with NovaCLI renewal and upgraded deal value -- [ ] Follow up with Yuki in one week to confirm contract signature diff --git a/demo-vault-v2/event-sponsor-call-2025-03-28.md b/demo-vault-v2/event-sponsor-call-2025-03-28.md deleted file mode 100644 index a32d9679..00000000 --- a/demo-vault-v2/event-sponsor-call-2025-03-28.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -aliases: ["Sponsor call — 2025-03-28"] -Is A: Event -Date: "2025-03-28" -Belongs to: "[[2025-03]]" -Related to: ["[[person-henrik-johansson]]"] -Tags: ["Work"] ---- -# Sponsor call — 2025-03-28 -Sponsor discovery/renewal call. Discussed placement and campaign goals. - -## Notes -- Henrik represents BuildStream, a European developer productivity platform that combines build caching, remote execution, and CI analytics into a single tool -- Discovery call; BuildStream is positioning themselves as an alternative to Bazel and Gradle's enterprise offering, targeting engineering teams frustrated by slow build times and complex build system configurations -- Discussed a 4-episode sponsorship trial with mid-roll placement; Henrik is specifically interested in episodes about developer productivity, build systems, and engineering efficiency -- Henrik emphasized that BuildStream's European headquarters makes our international audience particularly attractive — he wants to reach engineering leaders in both European and North American markets simultaneously -- New lead; Henrik was referred by Anna from TestGrid, who spoke positively about her experience sponsoring with us — cross-referral from existing sponsors is a strong signal - -## Follow-up -- [ ] Send proposal with trial sponsorship pricing and international audience data -- [ ] Update CRM with BuildStream details and note the TestGrid referral source -- [ ] Follow up in two weeks after Henrik presents the proposal to his CEO diff --git a/demo-vault-v2/event-sponsor-call-2025-04-11.md b/demo-vault-v2/event-sponsor-call-2025-04-11.md deleted file mode 100644 index ba54aef6..00000000 --- a/demo-vault-v2/event-sponsor-call-2025-04-11.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -aliases: ["Sponsor call — 2025-04-11"] -Is A: Event -Date: "2025-04-11" -Belongs to: "[[2025-04]]" -Related to: ["[[person-anna-kowalski]]"] -Tags: ["Work"] ---- -# Sponsor call — 2025-04-11 -Sponsor discovery/renewal call. Discussed placement and campaign goals. - -## Notes -- Quarterly review with Anna from TestGrid; their 2025 annual sponsorship is well underway and this is the first formal performance check-in of the year -- Q1 performance metrics are strong — TestGrid's landing page conversion rate has actually improved compared to 2024, which Anna attributes to the refined messaging and our growing audience -- Discussed production of the co-produced testing best practices guide: outline is finalized and Anna's team has started producing content for their sections; target publication date is Q3 -- Anna raised the idea of TestGrid sponsoring a live episode recording at a testing conference later this year — they would cover venue costs in exchange for branded presence and a sponsored segment -- TestGrid continues to be one of our most collaborative and lowest-maintenance sponsors; the relationship essentially runs itself at this point - -## Follow-up -- [ ] Confirm testing guide production timeline and assign internal resources -- [ ] Update CRM with live event sponsorship as a new pipeline opportunity -- [ ] Follow up with Anna in May to review Q2 mid-point data diff --git a/demo-vault-v2/event-sponsor-call-2025-04-25.md b/demo-vault-v2/event-sponsor-call-2025-04-25.md deleted file mode 100644 index 9a2882a6..00000000 --- a/demo-vault-v2/event-sponsor-call-2025-04-25.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -aliases: ["Sponsor call — 2025-04-25"] -Is A: Event -Date: "2025-04-25" -Belongs to: "[[2025-04]]" -Related to: ["[[person-kenji-tanaka]]"] -Tags: ["Work"] ---- -# Sponsor call — 2025-04-25 -Sponsor discovery/renewal call. Discussed placement and campaign goals. - -## Notes -- Renewal discussion with Kenji from KubeScale; their initial guest-aligned sponsorship proved highly successful and he wants to lock in a full 2025 annual commitment -- KubeScale's guest-aligned sponsorship on Elena Konstantinou's platform engineering episodes generated exceptional results: the click-through rate was 4x their standard digital ad benchmarks, validating the premium pricing model -- Kenji confirmed a 12-month renewal covering all platform engineering and infrastructure episodes, with the option to expand into adjacent episodes about cloud architecture and DevOps practices -- Discussed co-hosting a webinar series with KubeScale in the second half of 2025, featuring conversations between their engineering team and our regular podcast guests — a new revenue stream that builds on the existing partnership -- KubeScale has become our proof case for the guest-aligned sponsorship model; the data from their campaigns is now used in our sales pitch to other prospects - -## Follow-up -- [ ] Send annual contract with guest-aligned placement schedule for 2025 -- [ ] Update CRM with KubeScale's annual commitment and webinar pipeline opportunity -- [ ] Sync with [[person-matteo-cellini]] on pricing and logistics for the webinar series concept diff --git a/demo-vault-v2/event-sponsor-call-2025-05-09.md b/demo-vault-v2/event-sponsor-call-2025-05-09.md deleted file mode 100644 index 37ea5add..00000000 --- a/demo-vault-v2/event-sponsor-call-2025-05-09.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -aliases: ["Sponsor call — 2025-05-09"] -Is A: Event -Date: "2025-05-09" -Belongs to: "[[2025-05]]" -Related to: ["[[person-lisa-chen]]"] -Tags: ["Work"] ---- -# Sponsor call — 2025-05-09 -Sponsor discovery/renewal call. Discussed placement and campaign goals. - -## Notes -- Annual review and renewal discussion with Lisa from DevMetrics; their sponsorship has been running for over a year now and this is the most comprehensive performance review to date -- DevMetrics has seen sustained lead generation from our audience throughout 2024 and into 2025; Lisa shared that podcast-sourced enterprise leads have a 25 percent higher average contract value compared to leads from other channels -- Lisa wants to renew for another year with expanded scope: adding a quarterly "Engineering Metrics Spotlight" segment where we discuss anonymized benchmarking data from DevMetrics' platform — this creates valuable content for listeners while providing brand integration for DevMetrics -- Discussed pricing for the expanded package; Lisa's budget has increased significantly based on the demonstrated ROI, putting DevMetrics in our top-5 sponsors by revenue -- The CEO panel episode from last year was well-received and they want to do a follow-up this year with updated data - -## Follow-up -- [ ] Draft proposal for the "Engineering Metrics Spotlight" segment with format and pricing -- [ ] Update CRM with DevMetrics renewal and expanded deal value -- [ ] Follow up with Lisa in two weeks to align on the segment format details diff --git a/demo-vault-v2/event-sponsor-call-2025-05-23.md b/demo-vault-v2/event-sponsor-call-2025-05-23.md deleted file mode 100644 index f640562c..00000000 --- a/demo-vault-v2/event-sponsor-call-2025-05-23.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -aliases: ["Sponsor call — 2025-05-23"] -Is A: Event -Date: "2025-05-23" -Belongs to: "[[2025-05]]" -Related to: ["[[person-michael-brown]]"] -Tags: ["Work"] ---- -# Sponsor call — 2025-05-23 -Sponsor discovery/renewal call. Discussed placement and campaign goals. - -## Notes -- Renewal discussion with Michael from PipelineHQ; their sponsorship has been running since the initial trial in mid-2024 and has expanded steadily through three contract extensions -- Michael shared that PipelineHQ's podcast sponsorship is now their single most cost-effective customer acquisition channel, with a customer acquisition cost approximately 60 percent lower than their paid search campaigns -- He wants to commit to a full 12-month sponsorship for the remainder of 2025 and into 2026, signaling a major shift from his initial skepticism about whether our audience was the right fit -- Discussed an upgrade to premium placement with both pre-roll and mid-roll spots, plus newsletter mentions — Michael's budget has grown significantly as PipelineHQ has scaled their revenue -- Remarkable relationship arc: from cautious 3-episode trial to annual commitment in under a year, driven entirely by measurable performance data - -## Follow-up -- [ ] Send annual contract proposal with premium tier pricing -- [ ] Update CRM with PipelineHQ's annual commitment and updated lifetime deal value -- [ ] Follow up with Michael in one week to finalize the contract diff --git a/demo-vault-v2/event-sponsor-call-2025-06-06.md b/demo-vault-v2/event-sponsor-call-2025-06-06.md deleted file mode 100644 index 90ca9745..00000000 --- a/demo-vault-v2/event-sponsor-call-2025-06-06.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -aliases: ["Sponsor call — 2025-06-06"] -Is A: Event -Date: "2025-06-06" -Belongs to: "[[2025-06]]" -Related to: ["[[person-michael-brown]]"] -Tags: ["Work"] ---- -# Sponsor call — 2025-06-06 -Sponsor discovery/renewal call. Discussed placement and campaign goals. - -## Notes -- Follow-up with Michael from PipelineHQ to finalize the annual contract discussed two weeks ago and plan the H2 2025 content calendar -- Contract signed and finalized — PipelineHQ is now committed through Q2 2026 with premium placement across podcast and newsletter channels -- Discussed H2 messaging strategy: PipelineHQ is launching a new enterprise tier and wants to shift ad copy from their small-team positioning to emphasize scalability and compliance features for larger organizations -- Michael asked about the possibility of PipelineHQ sponsoring our end-of-year awards episode and being the exclusive sponsor for the year-end retrospective — exploring this as a premium one-off opportunity -- The PipelineHQ partnership has become a case study in how trial sponsorships can grow into flagship relationships; their journey from skeptical 3-episode trial to annual premium commitment is a story we can use in sales conversations with other prospects - -## Follow-up -- [ ] Confirm H2 content calendar and updated ad copy with Michael -- [ ] Update CRM with signed contract details and explore the year-end exclusive sponsorship pricing -- [ ] Sync with [[person-matteo-cellini]] on the year-end awards episode sponsorship concept diff --git a/demo-vault-v2/event-team-sync-2024-01-01.md b/demo-vault-v2/event-team-sync-2024-01-01.md deleted file mode 100644 index e84e2a66..00000000 --- a/demo-vault-v2/event-team-sync-2024-01-01.md +++ /dev/null @@ -1,23 +0,0 @@ ---- -aliases: ["Team sync — 2024-01-01"] -Is A: Event -Date: "2024-01-01" -Belongs to: "[[2024-01]]" -Related to: ["[[person-matteo-cellini]]", "[[person-paco-furiani]]"] -Tags: ["Work"] ---- -# Team sync — 2024-01-01 -Weekly Monday team alignment. Covered priorities, blockers, and sponsor updates. - -## Notes -- Podcast season 1 production schedule reviewed — first episode recording next week -- Reviewed [[24q1-launch-sponsorship-packages]] timeline — on track for February launch -- Agreed to publish case studies from early sponsor conversations -- [[person-paco-furiani]] demoed new email template designs in Beehiiv -- Blocker: Beehiiv API rate limits causing issues with bulk subscriber imports -- Decision: Approved three-tier sponsorship pricing: Basic, Standard, Premium - -## Follow-up -- [ ] [[person-matteo-cellini]] to send media kit draft for review -- [ ] [[person-paco-furiani]] to finalize Beehiiv template customizations -- [ ] [[person-paco-furiani]] to test email automation sequence for new subscribers diff --git a/demo-vault-v2/event-team-sync-2024-01-08.md b/demo-vault-v2/event-team-sync-2024-01-08.md deleted file mode 100644 index d568480a..00000000 --- a/demo-vault-v2/event-team-sync-2024-01-08.md +++ /dev/null @@ -1,24 +0,0 @@ ---- -aliases: ["Team sync — 2024-01-08"] -Is A: Event -Date: "2024-01-08" -Belongs to: "[[2024-01]]" -Related to: ["[[person-matteo-cellini]]", "[[person-paco-furiani]]"] -Tags: ["Work"] ---- -# Team sync — 2024-01-08 -Weekly Monday team alignment. Covered priorities, blockers, and sponsor updates. - -## Notes -- Reviewed analytics dashboard setup — tracking UTM links for sponsors -- Newsletter growth at ~37k subscribers, open rate holding at 44% -- Discussed initial sponsor outreach list with [[person-matteo-cellini]] — 12 leads identified -- Podcast season 1 production schedule reviewed — first episode recording next week -- Discussed pricing tiers for sponsorship packages — settled on three tiers -- [[person-sara-ricci]] not yet onboarded — discussed timeline for editor hire -- Blocker: Beehiiv API rate limits causing issues with bulk subscriber imports -- Decision: Decided to launch podcast on Spotify and Apple Podcasts simultaneously - -## Follow-up -- [ ] [[person-paco-furiani]] to set up UTM tracking for all sponsor links -- [ ] [[person-paco-furiani]] to test email automation sequence for new subscribers diff --git a/demo-vault-v2/event-team-sync-2024-01-15.md b/demo-vault-v2/event-team-sync-2024-01-15.md deleted file mode 100644 index acd74f84..00000000 --- a/demo-vault-v2/event-team-sync-2024-01-15.md +++ /dev/null @@ -1,24 +0,0 @@ ---- -aliases: ["Team sync — 2024-01-15"] -Is A: Event -Date: "2024-01-15" -Belongs to: "[[2024-01]]" -Related to: ["[[person-matteo-cellini]]", "[[person-paco-furiani]]"] -Tags: ["Work"] ---- -# Team sync — 2024-01-15 -Weekly Monday team alignment. Covered priorities, blockers, and sponsor updates. - -## Notes -- [[person-paco-furiani]] demoed new email template designs in Beehiiv -- Beehiiv migration complete, all automations tested and working -- Discussed pricing tiers for sponsorship packages — settled on three tiers -- Reviewed [[24q1-launch-sponsorship-packages]] timeline — on track for February launch -- Podcast season 1 production schedule reviewed — first episode recording next week -- Blocker: Still waiting on legal review for sponsor contract template -- Decision: Will use Google Sheets as interim CRM until proper tool is selected - -## Follow-up -- [ ] [[person-luca-rossi]] to write first 2 sponsor package descriptions -- [ ] [[person-luca-rossi]] to record podcast intro and outro -- [ ] [[person-matteo-cellini]] to send media kit draft for review diff --git a/demo-vault-v2/event-team-sync-2024-01-22.md b/demo-vault-v2/event-team-sync-2024-01-22.md deleted file mode 100644 index 44af1805..00000000 --- a/demo-vault-v2/event-team-sync-2024-01-22.md +++ /dev/null @@ -1,23 +0,0 @@ ---- -aliases: ["Team sync — 2024-01-22"] -Is A: Event -Date: "2024-01-22" -Belongs to: "[[2024-01]]" -Related to: ["[[person-matteo-cellini]]", "[[person-paco-furiani]]"] -Tags: ["Work"] ---- -# Team sync — 2024-01-22 -Weekly Monday team alignment. Covered priorities, blockers, and sponsor updates. - -## Notes -- Reviewed [[24q1-launch-sponsorship-packages]] timeline — on track for February launch -- Beehiiv migration complete, all automations tested and working -- Content calendar for January/February finalized — 8 editions planned -- Podcast season 1 production schedule reviewed — first episode recording next week -- Blocker: Still waiting on legal review for sponsor contract template -- Decision: Decided to launch podcast on Spotify and Apple Podcasts simultaneously - -## Follow-up -- [ ] [[person-matteo-cellini]] to finalize sponsor outreach list by Friday -- [ ] [[person-paco-furiani]] to finalize Beehiiv template customizations -- [ ] [[person-paco-furiani]] to set up UTM tracking for all sponsor links diff --git a/demo-vault-v2/event-team-sync-2024-01-29.md b/demo-vault-v2/event-team-sync-2024-01-29.md deleted file mode 100644 index 283b271d..00000000 --- a/demo-vault-v2/event-team-sync-2024-01-29.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -aliases: ["Team sync — 2024-01-29"] -Is A: Event -Date: "2024-01-29" -Belongs to: "[[2024-01]]" -Related to: ["[[person-matteo-cellini]]", "[[person-paco-furiani]]"] -Tags: ["Work"] ---- -# Team sync — 2024-01-29 -Weekly Monday team alignment. Covered priorities, blockers, and sponsor updates. - -## Notes -- Agreed to publish case studies from early sponsor conversations -- Reviewed [[24q1-launch-sponsorship-packages]] timeline — on track for February launch -- Discussed initial sponsor outreach list with [[person-matteo-cellini]] — 12 leads identified -- Newsletter growth at ~36k subscribers, open rate holding at 43% -- Blocker: Need finalized brand guidelines before sending sponsor media kits -- Decision: Decided to launch podcast on Spotify and Apple Podcasts simultaneously - -## Follow-up -- [ ] [[person-luca-rossi]] to record podcast intro and outro -- [ ] [[person-matteo-cellini]] to finalize sponsor outreach list by Friday diff --git a/demo-vault-v2/event-team-sync-2024-02-05.md b/demo-vault-v2/event-team-sync-2024-02-05.md deleted file mode 100644 index eaee386b..00000000 --- a/demo-vault-v2/event-team-sync-2024-02-05.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -aliases: ["Team sync — 2024-02-05"] -Is A: Event -Date: "2024-02-05" -Belongs to: "[[2024-02]]" -Related to: ["[[person-matteo-cellini]]", "[[person-paco-furiani]]"] -Tags: ["Work"] ---- -# Team sync — 2024-02-05 -Weekly Monday team alignment. Covered priorities, blockers, and sponsor updates. - -## Notes -- Reviewed [[24q1-launch-sponsorship-packages]] timeline — on track for February launch -- Discussed initial sponsor outreach list with [[person-matteo-cellini]] — 12 leads identified -- Beehiiv migration complete, all automations tested and working -- Reviewed analytics dashboard setup — tracking UTM links for sponsors -- Blocker: No dedicated CRM yet — tracking sponsors in spreadsheets is error-prone -- Decision: Approved three-tier sponsorship pricing: Basic, Standard, Premium - -## Follow-up -- [ ] [[person-paco-furiani]] to test email automation sequence for new subscribers -- [ ] [[person-matteo-cellini]] to finalize sponsor outreach list by Friday diff --git a/demo-vault-v2/event-team-sync-2024-02-12.md b/demo-vault-v2/event-team-sync-2024-02-12.md deleted file mode 100644 index c9b30f8c..00000000 --- a/demo-vault-v2/event-team-sync-2024-02-12.md +++ /dev/null @@ -1,24 +0,0 @@ ---- -aliases: ["Team sync — 2024-02-12"] -Is A: Event -Date: "2024-02-12" -Belongs to: "[[2024-02]]" -Related to: ["[[person-matteo-cellini]]", "[[person-paco-furiani]]"] -Tags: ["Work"] ---- -# Team sync — 2024-02-12 -Weekly Monday team alignment. Covered priorities, blockers, and sponsor updates. - -## Notes -- Blog post backlog has 6 drafts in various stages — need to prioritize -- Discussed pricing tiers for sponsorship packages — settled on three tiers -- Beehiiv migration complete, all automations tested and working -- Reviewed [[24q1-launch-sponsorship-packages]] timeline — on track for February launch -- Discussed initial sponsor outreach list with [[person-matteo-cellini]] — 12 leads identified -- [[person-sara-ricci]] not yet onboarded — discussed timeline for editor hire -- Blocker: Still waiting on legal review for sponsor contract template -- Decision: Decided to launch podcast on Spotify and Apple Podcasts simultaneously - -## Follow-up -- [ ] [[person-paco-furiani]] to finalize Beehiiv template customizations -- [ ] [[person-matteo-cellini]] to send media kit draft for review diff --git a/demo-vault-v2/event-team-sync-2024-02-19.md b/demo-vault-v2/event-team-sync-2024-02-19.md deleted file mode 100644 index 00622f4d..00000000 --- a/demo-vault-v2/event-team-sync-2024-02-19.md +++ /dev/null @@ -1,23 +0,0 @@ ---- -aliases: ["Team sync — 2024-02-19"] -Is A: Event -Date: "2024-02-19" -Belongs to: "[[2024-02]]" -Related to: ["[[person-matteo-cellini]]", "[[person-paco-furiani]]"] -Tags: ["Work"] ---- -# Team sync — 2024-02-19 -Weekly Monday team alignment. Covered priorities, blockers, and sponsor updates. - -## Notes -- Blog post backlog has 6 drafts in various stages — need to prioritize -- Reviewed [[24q1-launch-sponsorship-packages]] timeline — on track for February launch -- [[person-sara-ricci]] not yet onboarded — discussed timeline for editor hire -- Content calendar for January/February finalized — 8 editions planned -- Blocker: Beehiiv API rate limits causing issues with bulk subscriber imports -- Decision: Decided to launch podcast on Spotify and Apple Podcasts simultaneously - -## Follow-up -- [ ] [[person-matteo-cellini]] to send media kit draft for review -- [ ] [[person-paco-furiani]] to test email automation sequence for new subscribers -- [ ] [[person-luca-rossi]] to record podcast intro and outro diff --git a/demo-vault-v2/event-team-sync-2024-02-26.md b/demo-vault-v2/event-team-sync-2024-02-26.md deleted file mode 100644 index 58c038f7..00000000 --- a/demo-vault-v2/event-team-sync-2024-02-26.md +++ /dev/null @@ -1,24 +0,0 @@ ---- -aliases: ["Team sync — 2024-02-26"] -Is A: Event -Date: "2024-02-26" -Belongs to: "[[2024-02]]" -Related to: ["[[person-matteo-cellini]]", "[[person-paco-furiani]]"] -Tags: ["Work"] ---- -# Team sync — 2024-02-26 -Weekly Monday team alignment. Covered priorities, blockers, and sponsor updates. - -## Notes -- Reviewed [[24q1-launch-sponsorship-packages]] timeline — on track for February launch -- Discussed pricing tiers for sponsorship packages — settled on three tiers -- Blog post backlog has 6 drafts in various stages — need to prioritize -- Reviewed analytics dashboard setup — tracking UTM links for sponsors -- Discussed initial sponsor outreach list with [[person-matteo-cellini]] — 12 leads identified -- Podcast season 1 production schedule reviewed — first episode recording next week -- Blocker: No dedicated CRM yet — tracking sponsors in spreadsheets is error-prone -- Decision: Approved three-tier sponsorship pricing: Basic, Standard, Premium - -## Follow-up -- [ ] [[person-matteo-cellini]] to finalize sponsor outreach list by Friday -- [ ] [[person-paco-furiani]] to finalize Beehiiv template customizations diff --git a/demo-vault-v2/event-team-sync-2024-03-04.md b/demo-vault-v2/event-team-sync-2024-03-04.md deleted file mode 100644 index 0ab39288..00000000 --- a/demo-vault-v2/event-team-sync-2024-03-04.md +++ /dev/null @@ -1,25 +0,0 @@ ---- -aliases: ["Team sync — 2024-03-04"] -Is A: Event -Date: "2024-03-04" -Belongs to: "[[2024-03]]" -Related to: ["[[person-matteo-cellini]]", "[[person-paco-furiani]]"] -Tags: ["Work"] ---- -# Team sync — 2024-03-04 -Weekly Monday team alignment. Covered priorities, blockers, and sponsor updates. - -## Notes -- Discussed pricing tiers for sponsorship packages — settled on three tiers -- Content calendar for January/February finalized — 8 editions planned -- Discussed initial sponsor outreach list with [[person-matteo-cellini]] — 12 leads identified -- Beehiiv migration complete, all automations tested and working -- Podcast season 1 production schedule reviewed — first episode recording next week -- Reviewed [[24q1-launch-sponsorship-packages]] timeline — on track for February launch -- Blocker: No dedicated CRM yet — tracking sponsors in spreadsheets is error-prone -- Decision: Will use Google Sheets as interim CRM until proper tool is selected - -## Follow-up -- [ ] [[person-luca-rossi]] to record podcast intro and outro -- [ ] [[person-matteo-cellini]] to finalize sponsor outreach list by Friday -- [ ] [[person-paco-furiani]] to test email automation sequence for new subscribers diff --git a/demo-vault-v2/event-team-sync-2024-03-11.md b/demo-vault-v2/event-team-sync-2024-03-11.md deleted file mode 100644 index f5173572..00000000 --- a/demo-vault-v2/event-team-sync-2024-03-11.md +++ /dev/null @@ -1,23 +0,0 @@ ---- -aliases: ["Team sync — 2024-03-11"] -Is A: Event -Date: "2024-03-11" -Belongs to: "[[2024-03]]" -Related to: ["[[person-matteo-cellini]]", "[[person-paco-furiani]]"] -Tags: ["Work"] ---- -# Team sync — 2024-03-11 -Weekly Monday team alignment. Covered priorities, blockers, and sponsor updates. - -## Notes -- Podcast season 1 production schedule reviewed — first episode recording next week -- Newsletter growth at ~35k subscribers, open rate holding at 43% -- Blog post backlog has 6 drafts in various stages — need to prioritize -- Reviewed [[24q1-launch-sponsorship-packages]] timeline — on track for February launch -- Discussed initial sponsor outreach list with [[person-matteo-cellini]] — 12 leads identified -- Blocker: Need finalized brand guidelines before sending sponsor media kits -- Decision: Decided to launch podcast on Spotify and Apple Podcasts simultaneously - -## Follow-up -- [ ] [[person-matteo-cellini]] to finalize sponsor outreach list by Friday -- [ ] [[person-paco-furiani]] to finalize Beehiiv template customizations diff --git a/demo-vault-v2/event-team-sync-2024-03-18.md b/demo-vault-v2/event-team-sync-2024-03-18.md deleted file mode 100644 index 8e15859a..00000000 --- a/demo-vault-v2/event-team-sync-2024-03-18.md +++ /dev/null @@ -1,23 +0,0 @@ ---- -aliases: ["Team sync — 2024-03-18"] -Is A: Event -Date: "2024-03-18" -Belongs to: "[[2024-03]]" -Related to: ["[[person-matteo-cellini]]", "[[person-paco-furiani]]"] -Tags: ["Work"] ---- -# Team sync — 2024-03-18 -Weekly Monday team alignment. Covered priorities, blockers, and sponsor updates. - -## Notes -- Discussed pricing tiers for sponsorship packages — settled on three tiers -- Discussed initial sponsor outreach list with [[person-matteo-cellini]] — 12 leads identified -- Beehiiv migration complete, all automations tested and working -- Reviewed analytics dashboard setup — tracking UTM links for sponsors -- Blocker: No dedicated CRM yet — tracking sponsors in spreadsheets is error-prone -- Decision: Decided to launch podcast on Spotify and Apple Podcasts simultaneously - -## Follow-up -- [ ] [[person-paco-furiani]] to test email automation sequence for new subscribers -- [ ] [[person-paco-furiani]] to set up UTM tracking for all sponsor links -- [ ] [[person-luca-rossi]] to record podcast intro and outro diff --git a/demo-vault-v2/event-team-sync-2024-03-25.md b/demo-vault-v2/event-team-sync-2024-03-25.md deleted file mode 100644 index 0ac9633d..00000000 --- a/demo-vault-v2/event-team-sync-2024-03-25.md +++ /dev/null @@ -1,23 +0,0 @@ ---- -aliases: ["Team sync — 2024-03-25"] -Is A: Event -Date: "2024-03-25" -Belongs to: "[[2024-03]]" -Related to: ["[[person-matteo-cellini]]", "[[person-paco-furiani]]"] -Tags: ["Work"] ---- -# Team sync — 2024-03-25 -Weekly Monday team alignment. Covered priorities, blockers, and sponsor updates. - -## Notes -- [[person-paco-furiani]] demoed new email template designs in Beehiiv -- [[person-sara-ricci]] not yet onboarded — discussed timeline for editor hire -- Agreed to publish case studies from early sponsor conversations -- Newsletter growth at ~36k subscribers, open rate holding at 43% -- Blog post backlog has 6 drafts in various stages — need to prioritize -- Blocker: Beehiiv API rate limits causing issues with bulk subscriber imports -- Decision: Approved three-tier sponsorship pricing: Basic, Standard, Premium - -## Follow-up -- [ ] [[person-paco-furiani]] to test email automation sequence for new subscribers -- [ ] [[person-matteo-cellini]] to finalize sponsor outreach list by Friday diff --git a/demo-vault-v2/event-team-sync-2024-04-01.md b/demo-vault-v2/event-team-sync-2024-04-01.md deleted file mode 100644 index dbf9e139..00000000 --- a/demo-vault-v2/event-team-sync-2024-04-01.md +++ /dev/null @@ -1,23 +0,0 @@ ---- -aliases: ["Team sync — 2024-04-01"] -Is A: Event -Date: "2024-04-01" -Belongs to: "[[2024-04]]" -Related to: ["[[person-matteo-cellini]]", "[[person-paco-furiani]]", "[[person-sara-ricci]]"] -Tags: ["Work"] ---- -# Team sync — 2024-04-01 -Weekly Monday team alignment. Covered priorities, blockers, and sponsor updates. - -## Notes -- Social media cross-promotion strategy discussed — LinkedIn performing best -- Newsletter at ~38k subs, growth rate 3% month-over-month -- Reviewed Q1 sponsor feedback — all renewals looking positive -- Brainstormed premium newsletter tier — early concept phase -- Blocker: CRM migration in progress — some data inconsistencies to resolve -- Decision: Will add "Sponsor Spotlight" as optional add-on to Premium tier - -## Follow-up -- [ ] [[person-luca-rossi]] to review and approve Q2 content calendar -- [ ] [[person-paco-furiani]] to complete CRM data migration by end of week -- [ ] [[person-paco-furiani]] to automate sponsor invoice generation diff --git a/demo-vault-v2/event-team-sync-2024-04-08.md b/demo-vault-v2/event-team-sync-2024-04-08.md deleted file mode 100644 index 0eae64d4..00000000 --- a/demo-vault-v2/event-team-sync-2024-04-08.md +++ /dev/null @@ -1,25 +0,0 @@ ---- -aliases: ["Team sync — 2024-04-08"] -Is A: Event -Date: "2024-04-08" -Belongs to: "[[2024-04]]" -Related to: ["[[person-matteo-cellini]]", "[[person-paco-furiani]]", "[[person-sara-ricci]]"] -Tags: ["Work"] ---- -# Team sync — 2024-04-08 -Weekly Monday team alignment. Covered priorities, blockers, and sponsor updates. - -## Notes -- Content pipeline review — [[person-sara-ricci]] editing 3 articles in parallel -- Discussed adding a "Sponsor Spotlight" section to the newsletter -- Newsletter at ~38k subs, growth rate 3% month-over-month -- Discussed A/B testing subject lines to improve open rates -- Podcast season 1 mid-season check: downloads averaging 1.5k per episode -- Social media cross-promotion strategy discussed — LinkedIn performing best -- Blocker: A/B testing tool integration with Beehiiv delayed -- Decision: Approved hiring [[person-sara-ricci]] as part-time editor - -## Follow-up -- [ ] [[person-paco-furiani]] to complete CRM data migration by end of week -- [ ] [[person-matteo-cellini]] to follow up with 3 pending sponsor proposals -- [ ] [[person-paco-furiani]] to automate sponsor invoice generation diff --git a/demo-vault-v2/event-team-sync-2024-04-15.md b/demo-vault-v2/event-team-sync-2024-04-15.md deleted file mode 100644 index 4fa34945..00000000 --- a/demo-vault-v2/event-team-sync-2024-04-15.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -aliases: ["Team sync — 2024-04-15"] -Is A: Event -Date: "2024-04-15" -Belongs to: "[[2024-04]]" -Related to: ["[[person-matteo-cellini]]", "[[person-paco-furiani]]", "[[person-sara-ricci]]"] -Tags: ["Work"] ---- -# Team sync — 2024-04-15 -Weekly Monday team alignment. Covered priorities, blockers, and sponsor updates. - -## Notes -- Reviewed Q1 sponsor feedback — all renewals looking positive -- Social media cross-promotion strategy discussed — LinkedIn performing best -- [[person-paco-furiani]] presented automation for sponsor invoice tracking -- Sponsor revenue update from [[person-matteo-cellini]] — 5 active sponsors this month -- Blocker: Podcast audio quality issues with remote guests — need better setup guide -- Decision: Selected HubSpot as CRM for sponsor pipeline management - -## Follow-up -- [ ] [[person-sara-ricci]] to create style guide first draft -- [ ] [[person-sara-ricci]] to deliver edited drafts by Wednesday diff --git a/demo-vault-v2/event-team-sync-2024-04-22.md b/demo-vault-v2/event-team-sync-2024-04-22.md deleted file mode 100644 index 3ac306a3..00000000 --- a/demo-vault-v2/event-team-sync-2024-04-22.md +++ /dev/null @@ -1,24 +0,0 @@ ---- -aliases: ["Team sync — 2024-04-22"] -Is A: Event -Date: "2024-04-22" -Belongs to: "[[2024-04]]" -Related to: ["[[person-matteo-cellini]]", "[[person-paco-furiani]]", "[[person-sara-ricci]]"] -Tags: ["Work"] ---- -# Team sync — 2024-04-22 -Weekly Monday team alignment. Covered priorities, blockers, and sponsor updates. - -## Notes -- Social media cross-promotion strategy discussed — LinkedIn performing best -- Newsletter at ~42k subs, growth rate 3.2% month-over-month -- Editor onboarding going well — [[person-sara-ricci]] handling first solo edition next week -- Discussed [[24q2-sponsor-crm]] setup — need structured pipeline tracking -- Content pipeline review — [[person-sara-ricci]] editing 3 articles in parallel -- Blocker: CRM migration in progress — some data inconsistencies to resolve -- Decision: Selected HubSpot as CRM for sponsor pipeline management - -## Follow-up -- [ ] [[person-matteo-cellini]] to follow up with 3 pending sponsor proposals -- [ ] [[person-sara-ricci]] to deliver edited drafts by Wednesday -- [ ] [[person-sara-ricci]] to create style guide first draft diff --git a/demo-vault-v2/event-team-sync-2024-04-29.md b/demo-vault-v2/event-team-sync-2024-04-29.md deleted file mode 100644 index b1fd790d..00000000 --- a/demo-vault-v2/event-team-sync-2024-04-29.md +++ /dev/null @@ -1,24 +0,0 @@ ---- -aliases: ["Team sync — 2024-04-29"] -Is A: Event -Date: "2024-04-29" -Belongs to: "[[2024-04]]" -Related to: ["[[person-matteo-cellini]]", "[[person-paco-furiani]]", "[[person-sara-ricci]]"] -Tags: ["Work"] ---- -# Team sync — 2024-04-29 -Weekly Monday team alignment. Covered priorities, blockers, and sponsor updates. - -## Notes -- Sponsor revenue update from [[person-matteo-cellini]] — 3 active sponsors this month -- [[person-paco-furiani]] presented automation for sponsor invoice tracking -- Discussed adding a "Sponsor Spotlight" section to the newsletter -- Content pipeline review — [[person-sara-ricci]] editing 3 articles in parallel -- Discussed [[24q2-sponsor-crm]] setup — need structured pipeline tracking -- Blocker: A/B testing tool integration with Beehiiv delayed -- Decision: Agreed to invest in professional newsletter design template - -## Follow-up -- [ ] [[person-sara-ricci]] to deliver edited drafts by Wednesday -- [ ] [[person-matteo-cellini]] to prepare renewal proposals for Q1 sponsors -- [ ] [[person-luca-rossi]] to review and approve Q2 content calendar diff --git a/demo-vault-v2/event-team-sync-2024-05-06.md b/demo-vault-v2/event-team-sync-2024-05-06.md deleted file mode 100644 index b644e792..00000000 --- a/demo-vault-v2/event-team-sync-2024-05-06.md +++ /dev/null @@ -1,24 +0,0 @@ ---- -aliases: ["Team sync — 2024-05-06"] -Is A: Event -Date: "2024-05-06" -Belongs to: "[[2024-05]]" -Related to: ["[[person-matteo-cellini]]", "[[person-paco-furiani]]", "[[person-sara-ricci]]"] -Tags: ["Work"] ---- -# Team sync — 2024-05-06 -Weekly Monday team alignment. Covered priorities, blockers, and sponsor updates. - -## Notes -- Editor onboarding going well — [[person-sara-ricci]] handling first solo edition next week -- [[person-paco-furiani]] presented automation for sponsor invoice tracking -- Newsletter at ~38k subs, growth rate 3% month-over-month -- Reviewed Q1 sponsor feedback — all renewals looking positive -- Social media cross-promotion strategy discussed — LinkedIn performing best -- Blocker: Sponsor invoicing still partially manual — automation pending -- Decision: Agreed to invest in professional newsletter design template - -## Follow-up -- [ ] [[person-matteo-cellini]] to prepare renewal proposals for Q1 sponsors -- [ ] [[person-sara-ricci]] to deliver edited drafts by Wednesday -- [ ] [[person-sara-ricci]] to create style guide first draft diff --git a/demo-vault-v2/event-team-sync-2024-05-13.md b/demo-vault-v2/event-team-sync-2024-05-13.md deleted file mode 100644 index 3e02c6a5..00000000 --- a/demo-vault-v2/event-team-sync-2024-05-13.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -aliases: ["Team sync — 2024-05-13"] -Is A: Event -Date: "2024-05-13" -Belongs to: "[[2024-05]]" -Related to: ["[[person-matteo-cellini]]", "[[person-paco-furiani]]", "[[person-sara-ricci]]"] -Tags: ["Work"] ---- -# Team sync — 2024-05-13 -Weekly Monday team alignment. Covered priorities, blockers, and sponsor updates. - -## Notes -- Newsletter at ~38k subs, growth rate 3% month-over-month -- Sponsor revenue update from [[person-matteo-cellini]] — 3 active sponsors this month -- Social media cross-promotion strategy discussed — LinkedIn performing best -- [[person-paco-furiani]] presented automation for sponsor invoice tracking -- Blocker: Podcast audio quality issues with remote guests — need better setup guide -- Decision: Selected HubSpot as CRM for sponsor pipeline management - -## Follow-up -- [ ] [[person-paco-furiani]] to automate sponsor invoice generation -- [ ] [[person-matteo-cellini]] to follow up with 3 pending sponsor proposals diff --git a/demo-vault-v2/event-team-sync-2024-05-20.md b/demo-vault-v2/event-team-sync-2024-05-20.md deleted file mode 100644 index 651ab883..00000000 --- a/demo-vault-v2/event-team-sync-2024-05-20.md +++ /dev/null @@ -1,23 +0,0 @@ ---- -aliases: ["Team sync — 2024-05-20"] -Is A: Event -Date: "2024-05-20" -Belongs to: "[[2024-05]]" -Related to: ["[[person-matteo-cellini]]", "[[person-paco-furiani]]", "[[person-sara-ricci]]"] -Tags: ["Work"] ---- -# Team sync — 2024-05-20 -Weekly Monday team alignment. Covered priorities, blockers, and sponsor updates. - -## Notes -- Discussed [[24q2-sponsor-crm]] setup — need structured pipeline tracking -- Sponsor revenue update from [[person-matteo-cellini]] — 5 active sponsors this month -- Reviewed Q1 sponsor feedback — all renewals looking positive -- Brainstormed premium newsletter tier — early concept phase -- Discussed A/B testing subject lines to improve open rates -- Blocker: A/B testing tool integration with Beehiiv delayed -- Decision: Approved hiring [[person-sara-ricci]] as part-time editor - -## Follow-up -- [ ] [[person-sara-ricci]] to deliver edited drafts by Wednesday -- [ ] [[person-luca-rossi]] to review and approve Q2 content calendar diff --git a/demo-vault-v2/event-team-sync-2024-05-27.md b/demo-vault-v2/event-team-sync-2024-05-27.md deleted file mode 100644 index ba89bc4b..00000000 --- a/demo-vault-v2/event-team-sync-2024-05-27.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -aliases: ["Team sync — 2024-05-27"] -Is A: Event -Date: "2024-05-27" -Belongs to: "[[2024-05]]" -Related to: ["[[person-matteo-cellini]]", "[[person-paco-furiani]]", "[[person-sara-ricci]]"] -Tags: ["Work"] ---- -# Team sync — 2024-05-27 -Weekly Monday team alignment. Covered priorities, blockers, and sponsor updates. - -## Notes -- [[person-paco-furiani]] presented automation for sponsor invoice tracking -- Discussed A/B testing subject lines to improve open rates -- Sponsor revenue update from [[person-matteo-cellini]] — 5 active sponsors this month -- Reviewed Q1 sponsor feedback — all renewals looking positive -- Blocker: [[person-sara-ricci]] needs access to analytics dashboard -- Decision: Selected HubSpot as CRM for sponsor pipeline management - -## Follow-up -- [ ] [[person-sara-ricci]] to deliver edited drafts by Wednesday -- [ ] [[person-matteo-cellini]] to follow up with 3 pending sponsor proposals diff --git a/demo-vault-v2/event-team-sync-2024-06-03.md b/demo-vault-v2/event-team-sync-2024-06-03.md deleted file mode 100644 index 6b793aad..00000000 --- a/demo-vault-v2/event-team-sync-2024-06-03.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -aliases: ["Team sync — 2024-06-03"] -Is A: Event -Date: "2024-06-03" -Belongs to: "[[2024-06]]" -Related to: ["[[person-matteo-cellini]]", "[[person-paco-furiani]]", "[[person-sara-ricci]]"] -Tags: ["Work"] ---- -# Team sync — 2024-06-03 -Weekly Monday team alignment. Covered priorities, blockers, and sponsor updates. - -## Notes -- Discussed A/B testing subject lines to improve open rates -- Discussed [[24q2-sponsor-crm]] setup — need structured pipeline tracking -- [[person-paco-furiani]] presented automation for sponsor invoice tracking -- Discussed adding a "Sponsor Spotlight" section to the newsletter -- Blocker: A/B testing tool integration with Beehiiv delayed -- Decision: Agreed to invest in professional newsletter design template - -## Follow-up -- [ ] [[person-sara-ricci]] to create style guide first draft -- [ ] [[person-matteo-cellini]] to follow up with 3 pending sponsor proposals diff --git a/demo-vault-v2/event-team-sync-2024-06-10.md b/demo-vault-v2/event-team-sync-2024-06-10.md deleted file mode 100644 index e193427e..00000000 --- a/demo-vault-v2/event-team-sync-2024-06-10.md +++ /dev/null @@ -1,23 +0,0 @@ ---- -aliases: ["Team sync — 2024-06-10"] -Is A: Event -Date: "2024-06-10" -Belongs to: "[[2024-06]]" -Related to: ["[[person-matteo-cellini]]", "[[person-paco-furiani]]", "[[person-sara-ricci]]"] -Tags: ["Work"] ---- -# Team sync — 2024-06-10 -Weekly Monday team alignment. Covered priorities, blockers, and sponsor updates. - -## Notes -- Sponsor revenue update from [[person-matteo-cellini]] — 3 active sponsors this month -- Discussed adding a "Sponsor Spotlight" section to the newsletter -- Brainstormed premium newsletter tier — early concept phase -- Social media cross-promotion strategy discussed — LinkedIn performing best -- Discussed [[24q2-sponsor-crm]] setup — need structured pipeline tracking -- Blocker: [[person-sara-ricci]] needs access to analytics dashboard -- Decision: Agreed to invest in professional newsletter design template - -## Follow-up -- [ ] [[person-paco-furiani]] to automate sponsor invoice generation -- [ ] [[person-luca-rossi]] to review and approve Q2 content calendar diff --git a/demo-vault-v2/event-team-sync-2024-06-17.md b/demo-vault-v2/event-team-sync-2024-06-17.md deleted file mode 100644 index c17671d2..00000000 --- a/demo-vault-v2/event-team-sync-2024-06-17.md +++ /dev/null @@ -1,23 +0,0 @@ ---- -aliases: ["Team sync — 2024-06-17"] -Is A: Event -Date: "2024-06-17" -Belongs to: "[[2024-06]]" -Related to: ["[[person-matteo-cellini]]", "[[person-paco-furiani]]", "[[person-sara-ricci]]"] -Tags: ["Work"] ---- -# Team sync — 2024-06-17 -Weekly Monday team alignment. Covered priorities, blockers, and sponsor updates. - -## Notes -- Discussed [[24q2-sponsor-crm]] setup — need structured pipeline tracking -- Discussed adding a "Sponsor Spotlight" section to the newsletter -- Discussed A/B testing subject lines to improve open rates -- Content pipeline review — [[person-sara-ricci]] editing 3 articles in parallel -- Blocker: A/B testing tool integration with Beehiiv delayed -- Decision: Will add "Sponsor Spotlight" as optional add-on to Premium tier - -## Follow-up -- [ ] [[person-paco-furiani]] to complete CRM data migration by end of week -- [ ] [[person-matteo-cellini]] to prepare renewal proposals for Q1 sponsors -- [ ] [[person-luca-rossi]] to review and approve Q2 content calendar diff --git a/demo-vault-v2/event-team-sync-2024-06-24.md b/demo-vault-v2/event-team-sync-2024-06-24.md deleted file mode 100644 index 6e757a73..00000000 --- a/demo-vault-v2/event-team-sync-2024-06-24.md +++ /dev/null @@ -1,24 +0,0 @@ ---- -aliases: ["Team sync — 2024-06-24"] -Is A: Event -Date: "2024-06-24" -Belongs to: "[[2024-06]]" -Related to: ["[[person-matteo-cellini]]", "[[person-paco-furiani]]", "[[person-sara-ricci]]"] -Tags: ["Work"] ---- -# Team sync — 2024-06-24 -Weekly Monday team alignment. Covered priorities, blockers, and sponsor updates. - -## Notes -- Newsletter at ~40k subs, growth rate 2.5% month-over-month -- Discussed [[24q2-sponsor-crm]] setup — need structured pipeline tracking -- Content pipeline review — [[person-sara-ricci]] editing 3 articles in parallel -- Podcast season 1 mid-season check: downloads averaging 1.8k per episode -- Reviewed Q1 sponsor feedback — all renewals looking positive -- Sponsor revenue update from [[person-matteo-cellini]] — 3 active sponsors this month -- Blocker: CRM migration in progress — some data inconsistencies to resolve -- Decision: Podcast will shift to biweekly cadence for season 2 - -## Follow-up -- [ ] [[person-sara-ricci]] to create style guide first draft -- [ ] [[person-paco-furiani]] to automate sponsor invoice generation diff --git a/demo-vault-v2/event-team-sync-2024-07-01.md b/demo-vault-v2/event-team-sync-2024-07-01.md deleted file mode 100644 index bee75f2b..00000000 --- a/demo-vault-v2/event-team-sync-2024-07-01.md +++ /dev/null @@ -1,25 +0,0 @@ ---- -aliases: ["Team sync — 2024-07-01"] -Is A: Event -Date: "2024-07-01" -Belongs to: "[[2024-07]]" -Related to: ["[[person-matteo-cellini]]", "[[person-paco-furiani]]", "[[person-sara-ricci]]"] -Tags: ["Work"] ---- -# Team sync — 2024-07-01 -Weekly Monday team alignment. Covered priorities, blockers, and sponsor updates. - -## Notes -- [[person-matteo-cellini]] reported 6 sponsors in pipeline for Q3 -- [[person-paco-furiani]] presented new analytics dashboard with sponsor ROI metrics -- Community Slack channel idea raised — tabled for now, revisit in Q4 -- Reviewed summer content calendar — lighter schedule in August -- Email deliverability at 98.7% — solid numbers -- Explored cross-promotion partnerships with 2 complementary newsletters -- Blocker: Premium tier payment integration needs more testing -- Decision: Approved 15% rate increase for Q4 sponsor renewals - -## Follow-up -- [ ] [[person-matteo-cellini]] to negotiate custom placement terms with 2 sponsors -- [ ] [[person-sara-ricci]] to finalize summer content buffer — 4 pre-written editions -- [ ] [[person-luca-rossi]] to approve podcast season 2 guest list diff --git a/demo-vault-v2/event-team-sync-2024-07-08.md b/demo-vault-v2/event-team-sync-2024-07-08.md deleted file mode 100644 index 60a294a2..00000000 --- a/demo-vault-v2/event-team-sync-2024-07-08.md +++ /dev/null @@ -1,23 +0,0 @@ ---- -aliases: ["Team sync — 2024-07-08"] -Is A: Event -Date: "2024-07-08" -Belongs to: "[[2024-07]]" -Related to: ["[[person-matteo-cellini]]", "[[person-paco-furiani]]", "[[person-sara-ricci]]"] -Tags: ["Work"] ---- -# Team sync — 2024-07-08 -Weekly Monday team alignment. Covered priorities, blockers, and sponsor updates. - -## Notes -- Sponsor rate card review — considering 15% increase for Q4 -- Discussed hiring a part-time social media manager -- Podcast season 2 planning kicked off — guest list being finalized -- Email deliverability at 98.7% — solid numbers -- Blocker: Premium tier payment integration needs more testing -- Decision: Postponed social media hire — redirecting budget to content - -## Follow-up -- [ ] [[person-matteo-cellini]] to prepare Q4 rate increase communication -- [ ] [[person-sara-ricci]] to finalize summer content buffer — 4 pre-written editions -- [ ] [[person-matteo-cellini]] to negotiate custom placement terms with 2 sponsors diff --git a/demo-vault-v2/event-team-sync-2024-07-15.md b/demo-vault-v2/event-team-sync-2024-07-15.md deleted file mode 100644 index eac28691..00000000 --- a/demo-vault-v2/event-team-sync-2024-07-15.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -aliases: ["Team sync — 2024-07-15"] -Is A: Event -Date: "2024-07-15" -Belongs to: "[[2024-07]]" -Related to: ["[[person-matteo-cellini]]", "[[person-paco-furiani]]", "[[person-sara-ricci]]"] -Tags: ["Work"] ---- -# Team sync — 2024-07-15 -Weekly Monday team alignment. Covered priorities, blockers, and sponsor updates. - -## Notes -- Newsletter at ~45k subs — discussed strategies to hit 50k by year end -- [[person-matteo-cellini]] reported 6 sponsors in pipeline for Q3 -- Community Slack channel idea raised — tabled for now, revisit in Q4 -- Explored cross-promotion partnerships with 2 complementary newsletters -- Blocker: Podcast guest scheduling backed up — 3-week wait time -- Decision: Postponed social media hire — redirecting budget to content - -## Follow-up -- [ ] [[person-paco-furiani]] to build sponsor ROI reporting template -- [ ] [[person-sara-ricci]] to finalize summer content buffer — 4 pre-written editions diff --git a/demo-vault-v2/event-team-sync-2024-07-22.md b/demo-vault-v2/event-team-sync-2024-07-22.md deleted file mode 100644 index 3694d72b..00000000 --- a/demo-vault-v2/event-team-sync-2024-07-22.md +++ /dev/null @@ -1,24 +0,0 @@ ---- -aliases: ["Team sync — 2024-07-22"] -Is A: Event -Date: "2024-07-22" -Belongs to: "[[2024-07]]" -Related to: ["[[person-matteo-cellini]]", "[[person-paco-furiani]]", "[[person-sara-ricci]]"] -Tags: ["Work"] ---- -# Team sync — 2024-07-22 -Weekly Monday team alignment. Covered priorities, blockers, and sponsor updates. - -## Notes -- Discussed hiring a part-time social media manager -- [[24q3-premium-tier]] early design review — surveyed 200 readers for interest -- Email deliverability at 98.5% — solid numbers -- [[person-matteo-cellini]] reported 5 sponsors in pipeline for Q3 -- Newsletter at ~43k subs — discussed strategies to hit 50k by year end -- Reviewed summer content calendar — lighter schedule in August -- Blocker: Two sponsors requesting custom placements outside standard tiers -- Decision: Premium tier priced at EUR 15/month — launching October - -## Follow-up -- [ ] [[person-luca-rossi]] to approve podcast season 2 guest list -- [ ] [[person-matteo-cellini]] to negotiate custom placement terms with 2 sponsors diff --git a/demo-vault-v2/event-team-sync-2024-07-29.md b/demo-vault-v2/event-team-sync-2024-07-29.md deleted file mode 100644 index 37d4ccfa..00000000 --- a/demo-vault-v2/event-team-sync-2024-07-29.md +++ /dev/null @@ -1,23 +0,0 @@ ---- -aliases: ["Team sync — 2024-07-29"] -Is A: Event -Date: "2024-07-29" -Belongs to: "[[2024-07]]" -Related to: ["[[person-matteo-cellini]]", "[[person-paco-furiani]]", "[[person-sara-ricci]]"] -Tags: ["Work"] ---- -# Team sync — 2024-07-29 -Weekly Monday team alignment. Covered priorities, blockers, and sponsor updates. - -## Notes -- [[24q3-premium-tier]] early design review — surveyed 200 readers for interest -- Podcast season 2 planning kicked off — guest list being finalized -- [[person-paco-furiani]] presented new analytics dashboard with sponsor ROI metrics -- Newsletter at ~43k subs — discussed strategies to hit 50k by year end -- Community Slack channel idea raised — tabled for now, revisit in Q4 -- Blocker: Summer vacations creating content bottleneck in August -- Decision: Approved 15% rate increase for Q4 sponsor renewals - -## Follow-up -- [ ] [[person-luca-rossi]] to approve podcast season 2 guest list -- [ ] [[person-sara-ricci]] to update style guide with podcast show notes format diff --git a/demo-vault-v2/event-team-sync-2024-08-05.md b/demo-vault-v2/event-team-sync-2024-08-05.md deleted file mode 100644 index e9e272e3..00000000 --- a/demo-vault-v2/event-team-sync-2024-08-05.md +++ /dev/null @@ -1,23 +0,0 @@ ---- -aliases: ["Team sync — 2024-08-05"] -Is A: Event -Date: "2024-08-05" -Belongs to: "[[2024-08]]" -Related to: ["[[person-matteo-cellini]]", "[[person-paco-furiani]]", "[[person-sara-ricci]]"] -Tags: ["Work"] ---- -# Team sync — 2024-08-05 -Weekly Monday team alignment. Covered priorities, blockers, and sponsor updates. - -## Notes -- Email deliverability at 98.5% — solid numbers -- [[24q3-premium-tier]] early design review — surveyed 200 readers for interest -- Content quality review — [[person-sara-ricci]] flagged need for style guide updates -- Sponsor rate card review — considering 15% increase for Q4 -- Blocker: Social media scheduling tool contract expiring — need to evaluate alternatives -- Decision: Postponed social media hire — redirecting budget to content - -## Follow-up -- [ ] [[person-paco-furiani]] to evaluate premium tier payment integration options -- [ ] [[person-luca-rossi]] to approve podcast season 2 guest list -- [ ] [[person-sara-ricci]] to update style guide with podcast show notes format diff --git a/demo-vault-v2/event-team-sync-2024-08-12.md b/demo-vault-v2/event-team-sync-2024-08-12.md deleted file mode 100644 index 848614c8..00000000 --- a/demo-vault-v2/event-team-sync-2024-08-12.md +++ /dev/null @@ -1,24 +0,0 @@ ---- -aliases: ["Team sync — 2024-08-12"] -Is A: Event -Date: "2024-08-12" -Belongs to: "[[2024-08]]" -Related to: ["[[person-matteo-cellini]]", "[[person-paco-furiani]]", "[[person-sara-ricci]]"] -Tags: ["Work"] ---- -# Team sync — 2024-08-12 -Weekly Monday team alignment. Covered priorities, blockers, and sponsor updates. - -## Notes -- Explored cross-promotion partnerships with 2 complementary newsletters -- Sponsor rate card review — considering 15% increase for Q4 -- Newsletter at ~44k subs — discussed strategies to hit 50k by year end -- Reviewed summer content calendar — lighter schedule in August -- Content quality review — [[person-sara-ricci]] flagged need for style guide updates -- Blocker: Two sponsors requesting custom placements outside standard tiers -- Decision: Will cross-promote with "Tech Leadership Weekly" newsletter - -## Follow-up -- [ ] [[person-paco-furiani]] to build sponsor ROI reporting template -- [ ] [[person-sara-ricci]] to finalize summer content buffer — 4 pre-written editions -- [ ] [[person-luca-rossi]] to approve podcast season 2 guest list diff --git a/demo-vault-v2/event-team-sync-2024-08-19.md b/demo-vault-v2/event-team-sync-2024-08-19.md deleted file mode 100644 index 772dcbf4..00000000 --- a/demo-vault-v2/event-team-sync-2024-08-19.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -aliases: ["Team sync — 2024-08-19"] -Is A: Event -Date: "2024-08-19" -Belongs to: "[[2024-08]]" -Related to: ["[[person-matteo-cellini]]", "[[person-paco-furiani]]", "[[person-sara-ricci]]"] -Tags: ["Work"] ---- -# Team sync — 2024-08-19 -Weekly Monday team alignment. Covered priorities, blockers, and sponsor updates. - -## Notes -- Content quality review — [[person-sara-ricci]] flagged need for style guide updates -- [[person-paco-furiani]] presented new analytics dashboard with sponsor ROI metrics -- Newsletter at ~43k subs — discussed strategies to hit 50k by year end -- Community Slack channel idea raised — tabled for now, revisit in Q4 -- Blocker: Social media scheduling tool contract expiring — need to evaluate alternatives -- Decision: Approved 15% rate increase for Q4 sponsor renewals - -## Follow-up -- [ ] [[person-sara-ricci]] to update style guide with podcast show notes format -- [ ] [[person-matteo-cellini]] to negotiate custom placement terms with 2 sponsors diff --git a/demo-vault-v2/event-team-sync-2024-08-26.md b/demo-vault-v2/event-team-sync-2024-08-26.md deleted file mode 100644 index cc6a2482..00000000 --- a/demo-vault-v2/event-team-sync-2024-08-26.md +++ /dev/null @@ -1,24 +0,0 @@ ---- -aliases: ["Team sync — 2024-08-26"] -Is A: Event -Date: "2024-08-26" -Belongs to: "[[2024-08]]" -Related to: ["[[person-matteo-cellini]]", "[[person-paco-furiani]]", "[[person-sara-ricci]]"] -Tags: ["Work"] ---- -# Team sync — 2024-08-26 -Weekly Monday team alignment. Covered priorities, blockers, and sponsor updates. - -## Notes -- [[person-matteo-cellini]] reported 7 sponsors in pipeline for Q3 -- Newsletter at ~43k subs — discussed strategies to hit 50k by year end -- Community Slack channel idea raised — tabled for now, revisit in Q4 -- Discussed hiring a part-time social media manager -- [[person-paco-furiani]] presented new analytics dashboard with sponsor ROI metrics -- Blocker: Two sponsors requesting custom placements outside standard tiers -- Decision: Approved 15% rate increase for Q4 sponsor renewals - -## Follow-up -- [ ] [[person-paco-furiani]] to evaluate premium tier payment integration options -- [ ] [[person-matteo-cellini]] to prepare Q4 rate increase communication -- [ ] [[person-luca-rossi]] to approve podcast season 2 guest list diff --git a/demo-vault-v2/event-team-sync-2024-09-02.md b/demo-vault-v2/event-team-sync-2024-09-02.md deleted file mode 100644 index 80de2c9a..00000000 --- a/demo-vault-v2/event-team-sync-2024-09-02.md +++ /dev/null @@ -1,23 +0,0 @@ ---- -aliases: ["Team sync — 2024-09-02"] -Is A: Event -Date: "2024-09-02" -Belongs to: "[[2024-09]]" -Related to: ["[[person-matteo-cellini]]", "[[person-paco-furiani]]", "[[person-sara-ricci]]"] -Tags: ["Work"] ---- -# Team sync — 2024-09-02 -Weekly Monday team alignment. Covered priorities, blockers, and sponsor updates. - -## Notes -- [[person-matteo-cellini]] reported 6 sponsors in pipeline for Q3 -- Newsletter at ~45k subs — discussed strategies to hit 50k by year end -- Explored cross-promotion partnerships with 2 complementary newsletters -- Content quality review — [[person-sara-ricci]] flagged need for style guide updates -- [[person-paco-furiani]] presented new analytics dashboard with sponsor ROI metrics -- Blocker: Two sponsors requesting custom placements outside standard tiers -- Decision: Approved 15% rate increase for Q4 sponsor renewals - -## Follow-up -- [ ] [[person-sara-ricci]] to finalize summer content buffer — 4 pre-written editions -- [ ] [[person-matteo-cellini]] to negotiate custom placement terms with 2 sponsors diff --git a/demo-vault-v2/event-team-sync-2024-09-09.md b/demo-vault-v2/event-team-sync-2024-09-09.md deleted file mode 100644 index ace30a0b..00000000 --- a/demo-vault-v2/event-team-sync-2024-09-09.md +++ /dev/null @@ -1,24 +0,0 @@ ---- -aliases: ["Team sync — 2024-09-09"] -Is A: Event -Date: "2024-09-09" -Belongs to: "[[2024-09]]" -Related to: ["[[person-matteo-cellini]]", "[[person-paco-furiani]]", "[[person-sara-ricci]]"] -Tags: ["Work"] ---- -# Team sync — 2024-09-09 -Weekly Monday team alignment. Covered priorities, blockers, and sponsor updates. - -## Notes -- Content quality review — [[person-sara-ricci]] flagged need for style guide updates -- Sponsor rate card review — considering 15% increase for Q4 -- Newsletter at ~43k subs — discussed strategies to hit 50k by year end -- Discussed hiring a part-time social media manager -- Email deliverability at 98.7% — solid numbers -- Blocker: Premium tier payment integration needs more testing -- Decision: Postponed social media hire — redirecting budget to content - -## Follow-up -- [ ] [[person-matteo-cellini]] to prepare Q4 rate increase communication -- [ ] [[person-sara-ricci]] to finalize summer content buffer — 4 pre-written editions -- [ ] [[person-luca-rossi]] to approve podcast season 2 guest list diff --git a/demo-vault-v2/event-team-sync-2024-09-16.md b/demo-vault-v2/event-team-sync-2024-09-16.md deleted file mode 100644 index 6e1df284..00000000 --- a/demo-vault-v2/event-team-sync-2024-09-16.md +++ /dev/null @@ -1,23 +0,0 @@ ---- -aliases: ["Team sync — 2024-09-16"] -Is A: Event -Date: "2024-09-16" -Belongs to: "[[2024-09]]" -Related to: ["[[person-matteo-cellini]]", "[[person-paco-furiani]]", "[[person-sara-ricci]]"] -Tags: ["Work"] ---- -# Team sync — 2024-09-16 -Weekly Monday team alignment. Covered priorities, blockers, and sponsor updates. - -## Notes -- Podcast season 2 planning kicked off — guest list being finalized -- Content quality review — [[person-sara-ricci]] flagged need for style guide updates -- Newsletter at ~43k subs — discussed strategies to hit 50k by year end -- Email deliverability at 98.2% — solid numbers -- [[24q3-premium-tier]] early design review — surveyed 200 readers for interest -- Blocker: Social media scheduling tool contract expiring — need to evaluate alternatives -- Decision: Will cross-promote with "Tech Leadership Weekly" newsletter - -## Follow-up -- [ ] [[person-luca-rossi]] to approve podcast season 2 guest list -- [ ] [[person-paco-furiani]] to evaluate premium tier payment integration options diff --git a/demo-vault-v2/event-team-sync-2024-09-23.md b/demo-vault-v2/event-team-sync-2024-09-23.md deleted file mode 100644 index c766f0fd..00000000 --- a/demo-vault-v2/event-team-sync-2024-09-23.md +++ /dev/null @@ -1,23 +0,0 @@ ---- -aliases: ["Team sync — 2024-09-23"] -Is A: Event -Date: "2024-09-23" -Belongs to: "[[2024-09]]" -Related to: ["[[person-matteo-cellini]]", "[[person-paco-furiani]]", "[[person-sara-ricci]]"] -Tags: ["Work"] ---- -# Team sync — 2024-09-23 -Weekly Monday team alignment. Covered priorities, blockers, and sponsor updates. - -## Notes -- Email deliverability at 98.5% — solid numbers -- Sponsor rate card review — considering 15% increase for Q4 -- Discussed hiring a part-time social media manager -- [[person-paco-furiani]] presented new analytics dashboard with sponsor ROI metrics -- [[24q3-premium-tier]] early design review — surveyed 200 readers for interest -- Blocker: Premium tier payment integration needs more testing -- Decision: Will cross-promote with "Tech Leadership Weekly" newsletter - -## Follow-up -- [ ] [[person-luca-rossi]] to approve podcast season 2 guest list -- [ ] [[person-matteo-cellini]] to negotiate custom placement terms with 2 sponsors diff --git a/demo-vault-v2/event-team-sync-2024-09-30.md b/demo-vault-v2/event-team-sync-2024-09-30.md deleted file mode 100644 index 966da6e3..00000000 --- a/demo-vault-v2/event-team-sync-2024-09-30.md +++ /dev/null @@ -1,25 +0,0 @@ ---- -aliases: ["Team sync — 2024-09-30"] -Is A: Event -Date: "2024-09-30" -Belongs to: "[[2024-09]]" -Related to: ["[[person-matteo-cellini]]", "[[person-paco-furiani]]", "[[person-sara-ricci]]"] -Tags: ["Work"] ---- -# Team sync — 2024-09-30 -Weekly Monday team alignment. Covered priorities, blockers, and sponsor updates. - -## Notes -- Content quality review — [[person-sara-ricci]] flagged need for style guide updates -- Podcast season 2 planning kicked off — guest list being finalized -- Reviewed summer content calendar — lighter schedule in August -- Newsletter at ~45k subs — discussed strategies to hit 50k by year end -- Email deliverability at 98.2% — solid numbers -- Community Slack channel idea raised — tabled for now, revisit in Q4 -- Blocker: Podcast guest scheduling backed up — 3-week wait time -- Decision: Premium tier priced at EUR 15/month — launching October - -## Follow-up -- [ ] [[person-matteo-cellini]] to prepare Q4 rate increase communication -- [ ] [[person-matteo-cellini]] to negotiate custom placement terms with 2 sponsors -- [ ] [[person-sara-ricci]] to update style guide with podcast show notes format diff --git a/demo-vault-v2/event-team-sync-2024-10-07.md b/demo-vault-v2/event-team-sync-2024-10-07.md deleted file mode 100644 index 7296146f..00000000 --- a/demo-vault-v2/event-team-sync-2024-10-07.md +++ /dev/null @@ -1,23 +0,0 @@ ---- -aliases: ["Team sync — 2024-10-07"] -Is A: Event -Date: "2024-10-07" -Belongs to: "[[2024-10]]" -Related to: ["[[person-matteo-cellini]]", "[[person-paco-furiani]]", "[[person-sara-ricci]]"] -Tags: ["Work"] ---- -# Team sync — 2024-10-07 -Weekly Monday team alignment. Covered priorities, blockers, and sponsor updates. - -## Notes -- [[person-sara-ricci]] proposed editorial calendar restructure for 2025 -- Laputa app development update from [[person-luca-rossi]] — MVP scope defined -- Newsletter at ~49k subs — [[25q1-referral-program]] discussion started -- [[person-paco-furiani]] demoed improved automation for subscriber segmentation -- Blocker: Sponsor contract renewals piling up — [[person-matteo-cellini]] needs support -- Decision: Referral program will use milestone-based rewards (5, 10, 25 referrals) - -## Follow-up -- [ ] [[person-matteo-cellini]] to send 2025 rate card to all current sponsors -- [ ] [[person-luca-rossi]] to share Laputa app MVP spec with team -- [ ] [[person-matteo-cellini]] to close pending Q4 renewals diff --git a/demo-vault-v2/event-team-sync-2024-10-14.md b/demo-vault-v2/event-team-sync-2024-10-14.md deleted file mode 100644 index 3f488b7c..00000000 --- a/demo-vault-v2/event-team-sync-2024-10-14.md +++ /dev/null @@ -1,24 +0,0 @@ ---- -aliases: ["Team sync — 2024-10-14"] -Is A: Event -Date: "2024-10-14" -Belongs to: "[[2024-10]]" -Related to: ["[[person-matteo-cellini]]", "[[person-paco-furiani]]", "[[person-sara-ricci]]"] -Tags: ["Work"] ---- -# Team sync — 2024-10-14 -Weekly Monday team alignment. Covered priorities, blockers, and sponsor updates. - -## Notes -- [[person-sara-ricci]] proposed editorial calendar restructure for 2025 -- Laputa app development update from [[person-luca-rossi]] — MVP scope defined -- Budget review for 2025 — tooling costs, contractor fees, potential new hires -- Holiday content schedule finalized — pre-written editions for Dec 23 and Dec 30 -- [[person-matteo-cellini]] presented Q4 sponsor pipeline — 9 sponsors confirmed -- Rate increases for 2025 sponsors discussed — [[person-matteo-cellini]] to prepare proposals -- Blocker: Sponsor contract renewals piling up — [[person-matteo-cellini]] needs support -- Decision: Laputa app MVP scope locked — shipping internal alpha in January - -## Follow-up -- [ ] [[person-sara-ricci]] to draft 2025 editorial calendar proposal -- [ ] [[person-paco-furiani]] to set up subscriber segmentation for premium tier diff --git a/demo-vault-v2/event-team-sync-2024-10-21.md b/demo-vault-v2/event-team-sync-2024-10-21.md deleted file mode 100644 index 0b4a2a4e..00000000 --- a/demo-vault-v2/event-team-sync-2024-10-21.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -aliases: ["Team sync — 2024-10-21"] -Is A: Event -Date: "2024-10-21" -Belongs to: "[[2024-10]]" -Related to: ["[[person-matteo-cellini]]", "[[person-paco-furiani]]", "[[person-sara-ricci]]"] -Tags: ["Work"] ---- -# Team sync — 2024-10-21 -Weekly Monday team alignment. Covered priorities, blockers, and sponsor updates. - -## Notes -- Budget review for 2025 — tooling costs, contractor fees, potential new hires -- [[person-paco-furiani]] demoed improved automation for subscriber segmentation -- Newsletter at ~48k subs — [[25q1-referral-program]] discussion started -- Reviewed annual metrics: open rate 43%, click rate 8.5% -- Blocker: Laputa app development pulling [[person-luca-rossi]] away from editorial -- Decision: Referral program will use milestone-based rewards (5, 10, 25 referrals) - -## Follow-up -- [ ] [[person-matteo-cellini]] to close pending Q4 renewals -- [ ] [[person-luca-rossi]] to share Laputa app MVP spec with team diff --git a/demo-vault-v2/event-team-sync-2024-10-28.md b/demo-vault-v2/event-team-sync-2024-10-28.md deleted file mode 100644 index 0a7eaad8..00000000 --- a/demo-vault-v2/event-team-sync-2024-10-28.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -aliases: ["Team sync — 2024-10-28"] -Is A: Event -Date: "2024-10-28" -Belongs to: "[[2024-10]]" -Related to: ["[[person-matteo-cellini]]", "[[person-paco-furiani]]", "[[person-sara-ricci]]"] -Tags: ["Work"] ---- -# Team sync — 2024-10-28 -Weekly Monday team alignment. Covered priorities, blockers, and sponsor updates. - -## Notes -- [[person-sara-ricci]] proposed editorial calendar restructure for 2025 -- Laputa app development update from [[person-luca-rossi]] — MVP scope defined -- Budget review for 2025 — tooling costs, contractor fees, potential new hires -- Holiday content schedule finalized — pre-written editions for Dec 23 and Dec 30 -- Blocker: Laputa app development pulling [[person-luca-rossi]] away from editorial -- Decision: Rate card increases effective January 1, 2025 - -## Follow-up -- [ ] [[person-matteo-cellini]] to send 2025 rate card to all current sponsors -- [ ] [[person-paco-furiani]] to prepare year-end analytics report diff --git a/demo-vault-v2/event-team-sync-2024-11-04.md b/demo-vault-v2/event-team-sync-2024-11-04.md deleted file mode 100644 index 3b002493..00000000 --- a/demo-vault-v2/event-team-sync-2024-11-04.md +++ /dev/null @@ -1,24 +0,0 @@ ---- -aliases: ["Team sync — 2024-11-04"] -Is A: Event -Date: "2024-11-04" -Belongs to: "[[2024-11]]" -Related to: ["[[person-matteo-cellini]]", "[[person-paco-furiani]]", "[[person-sara-ricci]]"] -Tags: ["Work"] ---- -# Team sync — 2024-11-04 -Weekly Monday team alignment. Covered priorities, blockers, and sponsor updates. - -## Notes -- Year-end planning: reviewed 2024 revenue targets — on track to exceed by 15% -- Discussed expanding into adjacent verticals (engineering management, startup ops) -- Rate increases for 2025 sponsors discussed — [[person-matteo-cellini]] to prepare proposals -- [[person-sara-ricci]] proposed editorial calendar restructure for 2025 -- Reviewed annual metrics: open rate 43%, click rate 8.2% -- Blocker: Year-end reporting requirements more complex than expected -- Decision: 2025 budget approved with 30% increase over 2024 - -## Follow-up -- [ ] [[person-matteo-cellini]] to close pending Q4 renewals -- [ ] [[person-luca-rossi]] to share Laputa app MVP spec with team -- [ ] [[person-paco-furiani]] to prepare year-end analytics report diff --git a/demo-vault-v2/event-team-sync-2024-11-11.md b/demo-vault-v2/event-team-sync-2024-11-11.md deleted file mode 100644 index d0a26720..00000000 --- a/demo-vault-v2/event-team-sync-2024-11-11.md +++ /dev/null @@ -1,25 +0,0 @@ ---- -aliases: ["Team sync — 2024-11-11"] -Is A: Event -Date: "2024-11-11" -Belongs to: "[[2024-11]]" -Related to: ["[[person-matteo-cellini]]", "[[person-paco-furiani]]", "[[person-sara-ricci]]"] -Tags: ["Work"] ---- -# Team sync — 2024-11-11 -Weekly Monday team alignment. Covered priorities, blockers, and sponsor updates. - -## Notes -- Year-end planning: reviewed 2024 revenue targets — on track to exceed by 12% -- Discussed expanding into adjacent verticals (engineering management, startup ops) -- Holiday content schedule finalized — pre-written editions for Dec 23 and Dec 30 -- Podcast season 2 wrapping up — listener survey results shared -- Newsletter at ~48k subs — [[25q1-referral-program]] discussion started -- Rate increases for 2025 sponsors discussed — [[person-matteo-cellini]] to prepare proposals -- Blocker: Sponsor contract renewals piling up — [[person-matteo-cellini]] needs support -- Decision: 2025 budget approved with 30% increase over 2024 - -## Follow-up -- [ ] [[person-matteo-cellini]] to send 2025 rate card to all current sponsors -- [ ] [[person-sara-ricci]] to pre-write holiday editions by Dec 15 -- [ ] [[person-luca-rossi]] to share Laputa app MVP spec with team diff --git a/demo-vault-v2/event-team-sync-2024-11-18.md b/demo-vault-v2/event-team-sync-2024-11-18.md deleted file mode 100644 index c3403540..00000000 --- a/demo-vault-v2/event-team-sync-2024-11-18.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -aliases: ["Team sync — 2024-11-18"] -Is A: Event -Date: "2024-11-18" -Belongs to: "[[2024-11]]" -Related to: ["[[person-matteo-cellini]]", "[[person-paco-furiani]]", "[[person-sara-ricci]]"] -Tags: ["Work"] ---- -# Team sync — 2024-11-18 -Weekly Monday team alignment. Covered priorities, blockers, and sponsor updates. - -## Notes -- [[person-sara-ricci]] proposed editorial calendar restructure for 2025 -- Podcast season 2 wrapping up — listener survey results shared -- Discussed expanding into adjacent verticals (engineering management, startup ops) -- Rate increases for 2025 sponsors discussed — [[person-matteo-cellini]] to prepare proposals -- Blocker: Holiday scheduling conflicts — several editions need pre-writing -- Decision: Laputa app MVP scope locked — shipping internal alpha in January - -## Follow-up -- [ ] [[person-matteo-cellini]] to send 2025 rate card to all current sponsors -- [ ] [[person-paco-furiani]] to set up subscriber segmentation for premium tier diff --git a/demo-vault-v2/event-team-sync-2024-11-25.md b/demo-vault-v2/event-team-sync-2024-11-25.md deleted file mode 100644 index 8e7e0b2b..00000000 --- a/demo-vault-v2/event-team-sync-2024-11-25.md +++ /dev/null @@ -1,24 +0,0 @@ ---- -aliases: ["Team sync — 2024-11-25"] -Is A: Event -Date: "2024-11-25" -Belongs to: "[[2024-11]]" -Related to: ["[[person-matteo-cellini]]", "[[person-paco-furiani]]", "[[person-sara-ricci]]"] -Tags: ["Work"] ---- -# Team sync — 2024-11-25 -Weekly Monday team alignment. Covered priorities, blockers, and sponsor updates. - -## Notes -- Year-end planning: reviewed 2024 revenue targets — on track to exceed by 10% -- [[person-matteo-cellini]] presented Q4 sponsor pipeline — 8 sponsors confirmed -- Podcast season 2 wrapping up — listener survey results shared -- [[person-paco-furiani]] demoed improved automation for subscriber segmentation -- Laputa app development update from [[person-luca-rossi]] — MVP scope defined -- Newsletter at ~46k subs — [[25q1-referral-program]] discussion started -- Blocker: Holiday scheduling conflicts — several editions need pre-writing -- Decision: Referral program will use milestone-based rewards (5, 10, 25 referrals) - -## Follow-up -- [ ] [[person-paco-furiani]] to prepare year-end analytics report -- [ ] [[person-sara-ricci]] to pre-write holiday editions by Dec 15 diff --git a/demo-vault-v2/event-team-sync-2024-12-02.md b/demo-vault-v2/event-team-sync-2024-12-02.md deleted file mode 100644 index db0a4936..00000000 --- a/demo-vault-v2/event-team-sync-2024-12-02.md +++ /dev/null @@ -1,23 +0,0 @@ ---- -aliases: ["Team sync — 2024-12-02"] -Is A: Event -Date: "2024-12-02" -Belongs to: "[[2024-12]]" -Related to: ["[[person-matteo-cellini]]", "[[person-paco-furiani]]", "[[person-sara-ricci]]"] -Tags: ["Work"] ---- -# Team sync — 2024-12-02 -Weekly Monday team alignment. Covered priorities, blockers, and sponsor updates. - -## Notes -- Newsletter at ~49k subs — [[25q1-referral-program]] discussion started -- Holiday content schedule finalized — pre-written editions for Dec 23 and Dec 30 -- [[person-paco-furiani]] demoed improved automation for subscriber segmentation -- Budget review for 2025 — tooling costs, contractor fees, potential new hires -- [[person-matteo-cellini]] presented Q4 sponsor pipeline — 8 sponsors confirmed -- Blocker: Budget approval for 2025 tools pending -- Decision: Laputa app MVP scope locked — shipping internal alpha in January - -## Follow-up -- [ ] [[person-paco-furiani]] to set up subscriber segmentation for premium tier -- [ ] [[person-matteo-cellini]] to send 2025 rate card to all current sponsors diff --git a/demo-vault-v2/event-team-sync-2024-12-09.md b/demo-vault-v2/event-team-sync-2024-12-09.md deleted file mode 100644 index 59b57679..00000000 --- a/demo-vault-v2/event-team-sync-2024-12-09.md +++ /dev/null @@ -1,24 +0,0 @@ ---- -aliases: ["Team sync — 2024-12-09"] -Is A: Event -Date: "2024-12-09" -Belongs to: "[[2024-12]]" -Related to: ["[[person-matteo-cellini]]", "[[person-paco-furiani]]", "[[person-sara-ricci]]"] -Tags: ["Work"] ---- -# Team sync — 2024-12-09 -Weekly Monday team alignment. Covered priorities, blockers, and sponsor updates. - -## Notes -- Reviewed annual metrics: open rate 41%, click rate 8.2% -- Budget review for 2025 — tooling costs, contractor fees, potential new hires -- Laputa app development update from [[person-luca-rossi]] — MVP scope defined -- Discussed expanding into adjacent verticals (engineering management, startup ops) -- [[person-sara-ricci]] proposed editorial calendar restructure for 2025 -- Blocker: Year-end reporting requirements more complex than expected -- Decision: Rate card increases effective January 1, 2025 - -## Follow-up -- [ ] [[person-luca-rossi]] to share Laputa app MVP spec with team -- [ ] [[person-matteo-cellini]] to send 2025 rate card to all current sponsors -- [ ] [[person-matteo-cellini]] to close pending Q4 renewals diff --git a/demo-vault-v2/event-team-sync-2024-12-16.md b/demo-vault-v2/event-team-sync-2024-12-16.md deleted file mode 100644 index 0b8d5865..00000000 --- a/demo-vault-v2/event-team-sync-2024-12-16.md +++ /dev/null @@ -1,23 +0,0 @@ ---- -aliases: ["Team sync — 2024-12-16"] -Is A: Event -Date: "2024-12-16" -Belongs to: "[[2024-12]]" -Related to: ["[[person-matteo-cellini]]", "[[person-paco-furiani]]", "[[person-sara-ricci]]"] -Tags: ["Work"] ---- -# Team sync — 2024-12-16 -Weekly Monday team alignment. Covered priorities, blockers, and sponsor updates. - -## Notes -- [[person-sara-ricci]] proposed editorial calendar restructure for 2025 -- Podcast season 2 wrapping up — listener survey results shared -- Holiday content schedule finalized — pre-written editions for Dec 23 and Dec 30 -- Reviewed annual metrics: open rate 41%, click rate 9.1% -- Year-end planning: reviewed 2024 revenue targets — on track to exceed by 10% -- Blocker: Laputa app development pulling [[person-luca-rossi]] away from editorial -- Decision: Referral program will use milestone-based rewards (5, 10, 25 referrals) - -## Follow-up -- [ ] [[person-luca-rossi]] to share Laputa app MVP spec with team -- [ ] [[person-sara-ricci]] to draft 2025 editorial calendar proposal diff --git a/demo-vault-v2/event-team-sync-2024-12-23.md b/demo-vault-v2/event-team-sync-2024-12-23.md deleted file mode 100644 index d42241a3..00000000 --- a/demo-vault-v2/event-team-sync-2024-12-23.md +++ /dev/null @@ -1,24 +0,0 @@ ---- -aliases: ["Team sync — 2024-12-23"] -Is A: Event -Date: "2024-12-23" -Belongs to: "[[2024-12]]" -Related to: ["[[person-matteo-cellini]]", "[[person-paco-furiani]]", "[[person-sara-ricci]]"] -Tags: ["Work"] ---- -# Team sync — 2024-12-23 -Weekly Monday team alignment. Covered priorities, blockers, and sponsor updates. - -## Notes -- Newsletter at ~48k subs — [[25q1-referral-program]] discussion started -- [[person-matteo-cellini]] presented Q4 sponsor pipeline — 9 sponsors confirmed -- Discussed expanding into adjacent verticals (engineering management, startup ops) -- Budget review for 2025 — tooling costs, contractor fees, potential new hires -- Rate increases for 2025 sponsors discussed — [[person-matteo-cellini]] to prepare proposals -- Blocker: Year-end reporting requirements more complex than expected -- Decision: Laputa app MVP scope locked — shipping internal alpha in January - -## Follow-up -- [ ] [[person-matteo-cellini]] to close pending Q4 renewals -- [ ] [[person-paco-furiani]] to prepare year-end analytics report -- [ ] [[person-luca-rossi]] to share Laputa app MVP spec with team diff --git a/demo-vault-v2/event-team-sync-2024-12-30.md b/demo-vault-v2/event-team-sync-2024-12-30.md deleted file mode 100644 index d37b119b..00000000 --- a/demo-vault-v2/event-team-sync-2024-12-30.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -aliases: ["Team sync — 2024-12-30"] -Is A: Event -Date: "2024-12-30" -Belongs to: "[[2024-12]]" -Related to: ["[[person-matteo-cellini]]", "[[person-paco-furiani]]", "[[person-sara-ricci]]"] -Tags: ["Work"] ---- -# Team sync — 2024-12-30 -Weekly Monday team alignment. Covered priorities, blockers, and sponsor updates. - -## Notes -- [[person-matteo-cellini]] presented Q4 sponsor pipeline — 9 sponsors confirmed -- Podcast season 2 wrapping up — listener survey results shared -- Holiday content schedule finalized — pre-written editions for Dec 23 and Dec 30 -- Newsletter at ~49k subs — [[25q1-referral-program]] discussion started -- Blocker: Holiday scheduling conflicts — several editions need pre-writing -- Decision: Rate card increases effective January 1, 2025 - -## Follow-up -- [ ] [[person-sara-ricci]] to pre-write holiday editions by Dec 15 -- [ ] [[person-matteo-cellini]] to send 2025 rate card to all current sponsors diff --git a/demo-vault-v2/event-team-sync-2025-01-06.md b/demo-vault-v2/event-team-sync-2025-01-06.md deleted file mode 100644 index 431ff04f..00000000 --- a/demo-vault-v2/event-team-sync-2025-01-06.md +++ /dev/null @@ -1,24 +0,0 @@ ---- -aliases: ["Team sync — 2025-01-06"] -Is A: Event -Date: "2025-01-06" -Belongs to: "[[2025-01]]" -Related to: ["[[person-matteo-cellini]]", "[[person-paco-furiani]]", "[[person-sara-ricci]]"] -Tags: ["Work"] ---- -# Team sync — 2025-01-06 -Weekly Monday team alignment. Covered priorities, blockers, and sponsor updates. - -## Notes -- 2025 kickoff: [[25q1-referral-program]] launch timeline reviewed — targeting February -- Newsletter at ~52k subs — aggressive growth target of 70k by June -- Content strategy refresh: more case studies, fewer opinion pieces based on reader survey -- Podcast season 3 pre-production — theme and format changes discussed -- [[person-paco-furiani]] migrated analytics to new dashboard with real-time metrics -- [[person-sara-ricci]] onboarding freelance writer for additional content capacity -- Blocker: Referral program reward fulfillment logistics still being worked out -- Decision: Freelance writer contracted for 4 articles/month - -## Follow-up -- [ ] [[person-paco-furiani]] to set up community platform accounts for team -- [ ] [[person-sara-ricci]] to create content templates for community posts diff --git a/demo-vault-v2/event-team-sync-2025-01-13.md b/demo-vault-v2/event-team-sync-2025-01-13.md index 6b986b7a..716cbe08 100644 --- a/demo-vault-v2/event-team-sync-2025-01-13.md +++ b/demo-vault-v2/event-team-sync-2025-01-13.md @@ -1,25 +1,13 @@ --- -aliases: ["Team sync — 2025-01-13"] -Is A: Event -Date: "2025-01-13" -Belongs to: "[[2025-01]]" -Related to: ["[[person-matteo-cellini]]", "[[person-paco-furiani]]", "[[person-sara-ricci]]"] -Tags: ["Work"] +type: Event +belongs_to: "[[25q1-laputa-v1]]" +related_to: + - "[[person-luca-rossi]]" + - "[[person-matteo-cellini]]" +date: 2025-01-13 --- + # Team sync — 2025-01-13 -Weekly Monday team alignment. Covered priorities, blockers, and sponsor updates. -## Notes -- [[person-matteo-cellini]] shared new rate card — 20% increase over 2024 rates -- Discussed cross-selling between newsletter, podcast, and future community -- Newsletter at ~55k subs — aggressive growth target of 70k by June -- Reviewed Q4 2024 churn: 2.1% monthly — within targets -- Podcast season 3 pre-production — theme and format changes discussed -- [[person-paco-furiani]] migrated analytics to new dashboard with real-time metrics -- Blocker: Referral program reward fulfillment logistics still being worked out -- Decision: Podcast season 3 approved with new interview-only format +Short checkpoint on V1 priorities: stabilize quick open, tighten keyboard navigation, and keep the inspector fast. -## Follow-up -- [ ] [[person-sara-ricci]] to create content templates for community posts -- [ ] [[person-luca-rossi]] to share Laputa alpha access with full team -- [ ] [[person-matteo-cellini]] to onboard 3 new sponsors with updated contracts diff --git a/demo-vault-v2/event-team-sync-2025-01-20.md b/demo-vault-v2/event-team-sync-2025-01-20.md deleted file mode 100644 index d596cd28..00000000 --- a/demo-vault-v2/event-team-sync-2025-01-20.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -aliases: ["Team sync — 2025-01-20"] -Is A: Event -Date: "2025-01-20" -Belongs to: "[[2025-01]]" -Related to: ["[[person-matteo-cellini]]", "[[person-paco-furiani]]", "[[person-sara-ricci]]"] -Tags: ["Work"] ---- -# Team sync — 2025-01-20 -Weekly Monday team alignment. Covered priorities, blockers, and sponsor updates. - -## Notes -- 2025 kickoff: [[25q1-referral-program]] launch timeline reviewed — targeting February -- Content strategy refresh: more case studies, fewer opinion pieces based on reader survey -- [[person-sara-ricci]] onboarding freelance writer for additional content capacity -- Laputa app alpha testing underway — internal team using daily -- Blocker: Podcast equipment upgrade delayed — shipping issues -- Decision: Podcast season 3 approved with new interview-only format - -## Follow-up -- [ ] [[person-paco-furiani]] to set up community platform accounts for team -- [ ] [[person-sara-ricci]] to brief freelance writer on tone and style diff --git a/demo-vault-v2/event-team-sync-2025-01-27.md b/demo-vault-v2/event-team-sync-2025-01-27.md deleted file mode 100644 index bc8ce9ed..00000000 --- a/demo-vault-v2/event-team-sync-2025-01-27.md +++ /dev/null @@ -1,25 +0,0 @@ ---- -aliases: ["Team sync — 2025-01-27"] -Is A: Event -Date: "2025-01-27" -Belongs to: "[[2025-01]]" -Related to: ["[[person-matteo-cellini]]", "[[person-paco-furiani]]", "[[person-sara-ricci]]"] -Tags: ["Work"] ---- -# Team sync — 2025-01-27 -Weekly Monday team alignment. Covered priorities, blockers, and sponsor updates. - -## Notes -- Laputa app alpha testing underway — internal team using daily -- Podcast season 3 pre-production — theme and format changes discussed -- Sponsor pipeline strong: 10 active sponsors, 5 in negotiation -- [[person-paco-furiani]] migrated analytics to new dashboard with real-time metrics -- Community launch planning — Discord vs Circle vs custom solution debate -- [[person-matteo-cellini]] shared new rate card — 20% increase over 2024 rates -- Blocker: Referral program reward fulfillment logistics still being worked out -- Decision: Podcast season 3 approved with new interview-only format - -## Follow-up -- [ ] [[person-sara-ricci]] to create content templates for community posts -- [ ] [[person-luca-rossi]] to share Laputa alpha access with full team -- [ ] [[person-paco-furiani]] to set up community platform accounts for team diff --git a/demo-vault-v2/event-team-sync-2025-02-03.md b/demo-vault-v2/event-team-sync-2025-02-03.md deleted file mode 100644 index 2d21e938..00000000 --- a/demo-vault-v2/event-team-sync-2025-02-03.md +++ /dev/null @@ -1,24 +0,0 @@ ---- -aliases: ["Team sync — 2025-02-03"] -Is A: Event -Date: "2025-02-03" -Belongs to: "[[2025-02]]" -Related to: ["[[person-matteo-cellini]]", "[[person-paco-furiani]]", "[[person-sara-ricci]]"] -Tags: ["Work"] ---- -# Team sync — 2025-02-03 -Weekly Monday team alignment. Covered priorities, blockers, and sponsor updates. - -## Notes -- Reviewed Q4 2024 churn: 2.3% monthly — within targets -- [[person-paco-furiani]] migrated analytics to new dashboard with real-time metrics -- [[person-sara-ricci]] onboarding freelance writer for additional content capacity -- 2025 kickoff: [[25q1-referral-program]] launch timeline reviewed — targeting February -- Sponsor pipeline strong: 11 active sponsors, 5 in negotiation -- Laputa app alpha testing underway — internal team using daily -- Blocker: Community platform migration from beta causing some member confusion -- Decision: Laputa app alpha extended by 4 weeks for stability fixes - -## Follow-up -- [ ] [[person-matteo-cellini]] to onboard 3 new sponsors with updated contracts -- [ ] [[person-matteo-cellini]] to present Q1 revenue forecast at next sync diff --git a/demo-vault-v2/event-team-sync-2025-02-10.md b/demo-vault-v2/event-team-sync-2025-02-10.md deleted file mode 100644 index d42fec07..00000000 --- a/demo-vault-v2/event-team-sync-2025-02-10.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -aliases: ["Team sync — 2025-02-10"] -Is A: Event -Date: "2025-02-10" -Belongs to: "[[2025-02]]" -Related to: ["[[person-matteo-cellini]]", "[[person-paco-furiani]]", "[[person-sara-ricci]]"] -Tags: ["Work"] ---- -# Team sync — 2025-02-10 -Weekly Monday team alignment. Covered priorities, blockers, and sponsor updates. - -## Notes -- [[person-paco-furiani]] migrated analytics to new dashboard with real-time metrics -- Community launch planning — Discord vs Circle vs custom solution debate -- Podcast season 3 pre-production — theme and format changes discussed -- [[person-sara-ricci]] onboarding freelance writer for additional content capacity -- Blocker: Community platform migration from beta causing some member confusion -- Decision: Freelance writer contracted for 4 articles/month - -## Follow-up -- [ ] [[person-matteo-cellini]] to onboard 3 new sponsors with updated contracts -- [ ] [[person-sara-ricci]] to create content templates for community posts diff --git a/demo-vault-v2/event-team-sync-2025-02-17.md b/demo-vault-v2/event-team-sync-2025-02-17.md deleted file mode 100644 index c8c0b285..00000000 --- a/demo-vault-v2/event-team-sync-2025-02-17.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -aliases: ["Team sync — 2025-02-17"] -Is A: Event -Date: "2025-02-17" -Belongs to: "[[2025-02]]" -Related to: ["[[person-matteo-cellini]]", "[[person-paco-furiani]]", "[[person-sara-ricci]]"] -Tags: ["Work"] ---- -# Team sync — 2025-02-17 -Weekly Monday team alignment. Covered priorities, blockers, and sponsor updates. - -## Notes -- Content strategy refresh: more case studies, fewer opinion pieces based on reader survey -- Newsletter at ~57k subs — aggressive growth target of 70k by June -- Laputa app alpha testing underway — internal team using daily -- Reviewed Q4 2024 churn: 1.8% monthly — within targets -- Blocker: Community platform migration from beta causing some member confusion -- Decision: Referral program launched — tracking via dedicated landing page - -## Follow-up -- [ ] [[person-paco-furiani]] to set up community platform accounts for team -- [ ] [[person-luca-rossi]] to share Laputa alpha access with full team diff --git a/demo-vault-v2/event-team-sync-2025-02-24.md b/demo-vault-v2/event-team-sync-2025-02-24.md deleted file mode 100644 index da1e1c22..00000000 --- a/demo-vault-v2/event-team-sync-2025-02-24.md +++ /dev/null @@ -1,24 +0,0 @@ ---- -aliases: ["Team sync — 2025-02-24"] -Is A: Event -Date: "2025-02-24" -Belongs to: "[[2025-02]]" -Related to: ["[[person-matteo-cellini]]", "[[person-paco-furiani]]", "[[person-sara-ricci]]"] -Tags: ["Work"] ---- -# Team sync — 2025-02-24 -Weekly Monday team alignment. Covered priorities, blockers, and sponsor updates. - -## Notes -- Sponsor pipeline strong: 10 active sponsors, 5 in negotiation -- [[person-matteo-cellini]] shared new rate card — 20% increase over 2024 rates -- Laputa app alpha testing underway — internal team using daily -- Content strategy refresh: more case studies, fewer opinion pieces based on reader survey -- Discussed cross-selling between newsletter, podcast, and future community -- Blocker: Freelance writer onboarding slower than expected -- Decision: Freelance writer contracted for 4 articles/month - -## Follow-up -- [ ] [[person-paco-furiani]] to set up community platform accounts for team -- [ ] [[person-sara-ricci]] to brief freelance writer on tone and style -- [ ] [[person-sara-ricci]] to create content templates for community posts diff --git a/demo-vault-v2/event-team-sync-2025-03-03.md b/demo-vault-v2/event-team-sync-2025-03-03.md deleted file mode 100644 index 1de15c1b..00000000 --- a/demo-vault-v2/event-team-sync-2025-03-03.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -aliases: ["Team sync — 2025-03-03"] -Is A: Event -Date: "2025-03-03" -Belongs to: "[[2025-03]]" -Related to: ["[[person-matteo-cellini]]", "[[person-paco-furiani]]", "[[person-sara-ricci]]"] -Tags: ["Work"] ---- -# Team sync — 2025-03-03 -Weekly Monday team alignment. Covered priorities, blockers, and sponsor updates. - -## Notes -- Podcast season 3 pre-production — theme and format changes discussed -- Content strategy refresh: more case studies, fewer opinion pieces based on reader survey -- Sponsor pipeline strong: 11 active sponsors, 5 in negotiation -- Reviewed Q4 2024 churn: 1.8% monthly — within targets -- Blocker: Referral program reward fulfillment logistics still being worked out -- Decision: Podcast season 3 approved with new interview-only format - -## Follow-up -- [ ] [[person-paco-furiani]] to set up community platform accounts for team -- [ ] [[person-sara-ricci]] to brief freelance writer on tone and style diff --git a/demo-vault-v2/event-team-sync-2025-03-10.md b/demo-vault-v2/event-team-sync-2025-03-10.md deleted file mode 100644 index 4d665b7b..00000000 --- a/demo-vault-v2/event-team-sync-2025-03-10.md +++ /dev/null @@ -1,25 +0,0 @@ ---- -aliases: ["Team sync — 2025-03-10"] -Is A: Event -Date: "2025-03-10" -Belongs to: "[[2025-03]]" -Related to: ["[[person-matteo-cellini]]", "[[person-paco-furiani]]", "[[person-sara-ricci]]"] -Tags: ["Work"] ---- -# Team sync — 2025-03-10 -Weekly Monday team alignment. Covered priorities, blockers, and sponsor updates. - -## Notes -- Podcast season 3 pre-production — theme and format changes discussed -- [[person-paco-furiani]] migrated analytics to new dashboard with real-time metrics -- [[person-matteo-cellini]] shared new rate card — 25% increase over 2024 rates -- [[person-sara-ricci]] onboarding freelance writer for additional content capacity -- Laputa app alpha testing underway — internal team using daily -- Discussed cross-selling between newsletter, podcast, and future community -- Blocker: Podcast equipment upgrade delayed — shipping issues -- Decision: Podcast season 3 approved with new interview-only format - -## Follow-up -- [ ] [[person-sara-ricci]] to brief freelance writer on tone and style -- [ ] [[person-matteo-cellini]] to present Q1 revenue forecast at next sync -- [ ] [[person-matteo-cellini]] to onboard 3 new sponsors with updated contracts diff --git a/demo-vault-v2/event-team-sync-2025-03-17.md b/demo-vault-v2/event-team-sync-2025-03-17.md deleted file mode 100644 index 8647b3cc..00000000 --- a/demo-vault-v2/event-team-sync-2025-03-17.md +++ /dev/null @@ -1,24 +0,0 @@ ---- -aliases: ["Team sync — 2025-03-17"] -Is A: Event -Date: "2025-03-17" -Belongs to: "[[2025-03]]" -Related to: ["[[person-matteo-cellini]]", "[[person-paco-furiani]]", "[[person-sara-ricci]]"] -Tags: ["Work"] ---- -# Team sync — 2025-03-17 -Weekly Monday team alignment. Covered priorities, blockers, and sponsor updates. - -## Notes -- Sponsor pipeline strong: 12 active sponsors, 5 in negotiation -- Reviewed Q4 2024 churn: 1.8% monthly — within targets -- [[person-matteo-cellini]] shared new rate card — 20% increase over 2024 rates -- Discussed cross-selling between newsletter, podcast, and future community -- Podcast season 3 pre-production — theme and format changes discussed -- Laputa app alpha testing underway — internal team using daily -- Blocker: Community platform migration from beta causing some member confusion -- Decision: Referral program launched — tracking via dedicated landing page - -## Follow-up -- [ ] [[person-sara-ricci]] to brief freelance writer on tone and style -- [ ] [[person-matteo-cellini]] to onboard 3 new sponsors with updated contracts diff --git a/demo-vault-v2/event-team-sync-2025-03-24.md b/demo-vault-v2/event-team-sync-2025-03-24.md deleted file mode 100644 index 759fc5f3..00000000 --- a/demo-vault-v2/event-team-sync-2025-03-24.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -aliases: ["Team sync — 2025-03-24"] -Is A: Event -Date: "2025-03-24" -Belongs to: "[[2025-03]]" -Related to: ["[[person-matteo-cellini]]", "[[person-paco-furiani]]", "[[person-sara-ricci]]"] -Tags: ["Work"] ---- -# Team sync — 2025-03-24 -Weekly Monday team alignment. Covered priorities, blockers, and sponsor updates. - -## Notes -- Newsletter at ~57k subs — aggressive growth target of 70k by June -- 2025 kickoff: [[25q1-referral-program]] launch timeline reviewed — targeting February -- Content strategy refresh: more case studies, fewer opinion pieces based on reader survey -- [[person-sara-ricci]] onboarding freelance writer for additional content capacity -- Blocker: Community platform migration from beta causing some member confusion -- Decision: Community founding member pricing set at EUR 9/month - -## Follow-up -- [ ] [[person-paco-furiani]] to set up community platform accounts for team -- [ ] [[person-luca-rossi]] to share Laputa alpha access with full team diff --git a/demo-vault-v2/event-team-sync-2025-03-31.md b/demo-vault-v2/event-team-sync-2025-03-31.md deleted file mode 100644 index 4624fdfe..00000000 --- a/demo-vault-v2/event-team-sync-2025-03-31.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -aliases: ["Team sync — 2025-03-31"] -Is A: Event -Date: "2025-03-31" -Belongs to: "[[2025-03]]" -Related to: ["[[person-matteo-cellini]]", "[[person-paco-furiani]]", "[[person-sara-ricci]]"] -Tags: ["Work"] ---- -# Team sync — 2025-03-31 -Weekly Monday team alignment. Covered priorities, blockers, and sponsor updates. - -## Notes -- [[person-paco-furiani]] migrated analytics to new dashboard with real-time metrics -- Community launch planning — Discord vs Circle vs custom solution debate -- Podcast season 3 pre-production — theme and format changes discussed -- [[person-sara-ricci]] onboarding freelance writer for additional content capacity -- Blocker: Community platform migration from beta causing some member confusion -- Decision: Podcast season 3 approved with new interview-only format - -## Follow-up -- [ ] [[person-matteo-cellini]] to present Q1 revenue forecast at next sync -- [ ] [[person-matteo-cellini]] to onboard 3 new sponsors with updated contracts diff --git a/demo-vault-v2/event-team-sync-2025-04-07.md b/demo-vault-v2/event-team-sync-2025-04-07.md deleted file mode 100644 index 921e4b70..00000000 --- a/demo-vault-v2/event-team-sync-2025-04-07.md +++ /dev/null @@ -1,24 +0,0 @@ ---- -aliases: ["Team sync — 2025-04-07"] -Is A: Event -Date: "2025-04-07" -Belongs to: "[[2025-04]]" -Related to: ["[[person-matteo-cellini]]", "[[person-paco-furiani]]", "[[person-sara-ricci]]"] -Tags: ["Work"] ---- -# Team sync — 2025-04-07 -Weekly Monday team alignment. Covered priorities, blockers, and sponsor updates. - -## Notes -- [[person-sara-ricci]] managing content pipeline fully independently now -- [[person-paco-furiani]] implemented automated sponsor reporting dashboards -- Podcast season 3 recording in progress — first 4 episodes edited -- Evaluated hiring a growth marketer — decided to wait until 80k subs -- Newsletter format experiment: added "Quick Links" section, testing engagement -- Community beta launched — 350 founding members signed up -- Blocker: Laputa beta feedback volume higher than expected — prioritization needed -- Decision: Community officially launched — free trial for first 500 members - -## Follow-up -- [ ] [[person-matteo-cellini]] to manage sponsor waitlist communications -- [ ] [[person-matteo-cellini]] to explore conference sponsorship packages diff --git a/demo-vault-v2/event-team-sync-2025-04-14.md b/demo-vault-v2/event-team-sync-2025-04-14.md deleted file mode 100644 index a7939bc1..00000000 --- a/demo-vault-v2/event-team-sync-2025-04-14.md +++ /dev/null @@ -1,24 +0,0 @@ ---- -aliases: ["Team sync — 2025-04-14"] -Is A: Event -Date: "2025-04-14" -Belongs to: "[[2025-04]]" -Related to: ["[[person-matteo-cellini]]", "[[person-paco-furiani]]", "[[person-sara-ricci]]"] -Tags: ["Work"] ---- -# Team sync — 2025-04-14 -Weekly Monday team alignment. Covered priorities, blockers, and sponsor updates. - -## Notes -- Laputa app public beta planned for Q3 — collecting internal feedback -- [[person-matteo-cellini]] closed 3 new annual sponsor contracts -- Community beta launched — 350 founding members signed up -- Discussed potential conference/event for community members in fall -- Referral program driving 12% of new subscriber growth -- Blocker: Content calendar getting tight with podcast + newsletter + community -- Decision: Podcast distribution expanded to YouTube with video - -## Follow-up -- [ ] [[person-sara-ricci]] to develop community content guidelines -- [ ] [[person-paco-furiani]] to automate sponsor reporting dashboard -- [ ] [[person-paco-furiani]] to evaluate video hosting for podcast YouTube expansion diff --git a/demo-vault-v2/event-team-sync-2025-04-21.md b/demo-vault-v2/event-team-sync-2025-04-21.md deleted file mode 100644 index 5c63bc0b..00000000 --- a/demo-vault-v2/event-team-sync-2025-04-21.md +++ /dev/null @@ -1,23 +0,0 @@ ---- -aliases: ["Team sync — 2025-04-21"] -Is A: Event -Date: "2025-04-21" -Belongs to: "[[2025-04]]" -Related to: ["[[person-matteo-cellini]]", "[[person-paco-furiani]]", "[[person-sara-ricci]]"] -Tags: ["Work"] ---- -# Team sync — 2025-04-21 -Weekly Monday team alignment. Covered priorities, blockers, and sponsor updates. - -## Notes -- [[25q2-reach-70k]] progress review — at ~65k subs, pacing well -- Referral program driving 12% of new subscriber growth -- [[person-matteo-cellini]] closed 3 new annual sponsor contracts -- Community beta launched — 350 founding members signed up -- Blocker: Content calendar getting tight with podcast + newsletter + community -- Decision: Growth marketer hire pushed to Q4 pending revenue milestone - -## Follow-up -- [ ] [[person-sara-ricci]] to plan podcast season 3 show notes workflow -- [ ] [[person-paco-furiani]] to automate sponsor reporting dashboard -- [ ] [[person-sara-ricci]] to develop community content guidelines diff --git a/demo-vault-v2/event-team-sync-2025-04-28.md b/demo-vault-v2/event-team-sync-2025-04-28.md deleted file mode 100644 index 7621c645..00000000 --- a/demo-vault-v2/event-team-sync-2025-04-28.md +++ /dev/null @@ -1,24 +0,0 @@ ---- -aliases: ["Team sync — 2025-04-28"] -Is A: Event -Date: "2025-04-28" -Belongs to: "[[2025-04]]" -Related to: ["[[person-matteo-cellini]]", "[[person-paco-furiani]]", "[[person-sara-ricci]]"] -Tags: ["Work"] ---- -# Team sync — 2025-04-28 -Weekly Monday team alignment. Covered priorities, blockers, and sponsor updates. - -## Notes -- Laputa app public beta planned for Q3 — collecting internal feedback -- [[person-sara-ricci]] managing content pipeline fully independently now -- Newsletter format experiment: added "Quick Links" section, testing engagement -- [[25q2-reach-70k]] progress review — at ~60k subs, pacing well -- Referral program driving 15% of new subscriber growth -- Blocker: Community moderation scaling challenges — need clear guidelines -- Decision: Community officially launched — free trial for first 500 members - -## Follow-up -- [ ] [[person-sara-ricci]] to develop community content guidelines -- [ ] [[person-luca-rossi]] to review Laputa beta feedback and prioritize fixes -- [ ] [[person-paco-furiani]] to automate sponsor reporting dashboard diff --git a/demo-vault-v2/event-team-sync-2025-05-05.md b/demo-vault-v2/event-team-sync-2025-05-05.md deleted file mode 100644 index 6d870fcb..00000000 --- a/demo-vault-v2/event-team-sync-2025-05-05.md +++ /dev/null @@ -1,24 +0,0 @@ ---- -aliases: ["Team sync — 2025-05-05"] -Is A: Event -Date: "2025-05-05" -Belongs to: "[[2025-05]]" -Related to: ["[[person-matteo-cellini]]", "[[person-paco-furiani]]", "[[person-sara-ricci]]"] -Tags: ["Work"] ---- -# Team sync — 2025-05-05 -Weekly Monday team alignment. Covered priorities, blockers, and sponsor updates. - -## Notes -- Laputa app public beta planned for Q3 — collecting internal feedback -- Discussed potential conference/event for community members in fall -- Revenue growing 35% year-over-year -- [[person-paco-furiani]] implemented automated sponsor reporting dashboards -- Newsletter format experiment: added "Quick Links" section, testing engagement -- [[person-sara-ricci]] managing content pipeline fully independently now -- Blocker: Content calendar getting tight with podcast + newsletter + community -- Decision: Podcast distribution expanded to YouTube with video - -## Follow-up -- [ ] [[person-paco-furiani]] to automate sponsor reporting dashboard -- [ ] [[person-matteo-cellini]] to explore conference sponsorship packages diff --git a/demo-vault-v2/event-team-sync-2025-05-12.md b/demo-vault-v2/event-team-sync-2025-05-12.md deleted file mode 100644 index 364d1613..00000000 --- a/demo-vault-v2/event-team-sync-2025-05-12.md +++ /dev/null @@ -1,23 +0,0 @@ ---- -aliases: ["Team sync — 2025-05-12"] -Is A: Event -Date: "2025-05-12" -Belongs to: "[[2025-05]]" -Related to: ["[[person-matteo-cellini]]", "[[person-paco-furiani]]", "[[person-sara-ricci]]"] -Tags: ["Work"] ---- -# Team sync — 2025-05-12 -Weekly Monday team alignment. Covered priorities, blockers, and sponsor updates. - -## Notes -- [[25q2-reach-70k]] progress review — at ~70k subs, pacing well -- Evaluated hiring a growth marketer — decided to wait until 80k subs -- Discussed potential conference/event for community members in fall -- Revenue growing 30% year-over-year -- [[person-sara-ricci]] managing content pipeline fully independently now -- Blocker: Laputa beta feedback volume higher than expected — prioritization needed -- Decision: Podcast distribution expanded to YouTube with video - -## Follow-up -- [ ] [[person-luca-rossi]] to review Laputa beta feedback and prioritize fixes -- [ ] [[person-paco-furiani]] to automate sponsor reporting dashboard diff --git a/demo-vault-v2/event-team-sync-2025-05-19.md b/demo-vault-v2/event-team-sync-2025-05-19.md deleted file mode 100644 index 8747212e..00000000 --- a/demo-vault-v2/event-team-sync-2025-05-19.md +++ /dev/null @@ -1,24 +0,0 @@ ---- -aliases: ["Team sync — 2025-05-19"] -Is A: Event -Date: "2025-05-19" -Belongs to: "[[2025-05]]" -Related to: ["[[person-matteo-cellini]]", "[[person-paco-furiani]]", "[[person-sara-ricci]]"] -Tags: ["Work"] ---- -# Team sync — 2025-05-19 -Weekly Monday team alignment. Covered priorities, blockers, and sponsor updates. - -## Notes -- Community beta launched — 350 founding members signed up -- [[person-sara-ricci]] managing content pipeline fully independently now -- Revenue growing 35% year-over-year -- [[person-matteo-cellini]] closed 4 new annual sponsor contracts -- [[person-paco-furiani]] implemented automated sponsor reporting dashboards -- Blocker: Growth marketer hiring on hold due to budget reallocation -- Decision: Sponsor waitlist process formalized — first-come-first-served - -## Follow-up -- [ ] [[person-paco-furiani]] to evaluate video hosting for podcast YouTube expansion -- [ ] [[person-paco-furiani]] to automate sponsor reporting dashboard -- [ ] [[person-sara-ricci]] to plan podcast season 3 show notes workflow diff --git a/demo-vault-v2/event-team-sync-2025-05-26.md b/demo-vault-v2/event-team-sync-2025-05-26.md deleted file mode 100644 index 96a2786a..00000000 --- a/demo-vault-v2/event-team-sync-2025-05-26.md +++ /dev/null @@ -1,23 +0,0 @@ ---- -aliases: ["Team sync — 2025-05-26"] -Is A: Event -Date: "2025-05-26" -Belongs to: "[[2025-05]]" -Related to: ["[[person-matteo-cellini]]", "[[person-paco-furiani]]", "[[person-sara-ricci]]"] -Tags: ["Work"] ---- -# Team sync — 2025-05-26 -Weekly Monday team alignment. Covered priorities, blockers, and sponsor updates. - -## Notes -- Revenue growing 30% year-over-year -- Laputa app public beta planned for Q3 — collecting internal feedback -- Community beta launched — 350 founding members signed up -- [[person-paco-furiani]] implemented automated sponsor reporting dashboards -- [[person-matteo-cellini]] closed 4 new annual sponsor contracts -- Blocker: Community moderation scaling challenges — need clear guidelines -- Decision: Community officially launched — free trial for first 500 members - -## Follow-up -- [ ] [[person-paco-furiani]] to automate sponsor reporting dashboard -- [ ] [[person-luca-rossi]] to review Laputa beta feedback and prioritize fixes diff --git a/demo-vault-v2/event-team-sync-2025-06-02.md b/demo-vault-v2/event-team-sync-2025-06-02.md deleted file mode 100644 index 574fad1a..00000000 --- a/demo-vault-v2/event-team-sync-2025-06-02.md +++ /dev/null @@ -1,25 +0,0 @@ ---- -aliases: ["Team sync — 2025-06-02"] -Is A: Event -Date: "2025-06-02" -Belongs to: "[[2025-06]]" -Related to: ["[[person-matteo-cellini]]", "[[person-paco-furiani]]", "[[person-sara-ricci]]"] -Tags: ["Work"] ---- -# Team sync — 2025-06-02 -Weekly Monday team alignment. Covered priorities, blockers, and sponsor updates. - -## Notes -- Referral program driving 18% of new subscriber growth -- [[person-matteo-cellini]] closed 3 new annual sponsor contracts -- Discussed potential conference/event for community members in fall -- Evaluated hiring a growth marketer — decided to wait until 80k subs -- Newsletter format experiment: added "Quick Links" section, testing engagement -- [[person-paco-furiani]] implemented automated sponsor reporting dashboards -- Blocker: Laputa beta feedback volume higher than expected — prioritization needed -- Decision: Community officially launched — free trial for first 500 members - -## Follow-up -- [ ] [[person-paco-furiani]] to automate sponsor reporting dashboard -- [ ] [[person-sara-ricci]] to develop community content guidelines -- [ ] [[person-paco-furiani]] to evaluate video hosting for podcast YouTube expansion diff --git a/demo-vault-v2/event-team-sync-2025-06-09.md b/demo-vault-v2/event-team-sync-2025-06-09.md deleted file mode 100644 index 59738310..00000000 --- a/demo-vault-v2/event-team-sync-2025-06-09.md +++ /dev/null @@ -1,24 +0,0 @@ ---- -aliases: ["Team sync — 2025-06-09"] -Is A: Event -Date: "2025-06-09" -Belongs to: "[[2025-06]]" -Related to: ["[[person-matteo-cellini]]", "[[person-paco-furiani]]", "[[person-sara-ricci]]"] -Tags: ["Work"] ---- -# Team sync — 2025-06-09 -Weekly Monday team alignment. Covered priorities, blockers, and sponsor updates. - -## Notes -- Discussed potential conference/event for community members in fall -- Referral program driving 18% of new subscriber growth -- Laputa app public beta planned for Q3 — collecting internal feedback -- [[person-sara-ricci]] managing content pipeline fully independently now -- [[25q2-reach-70k]] progress review — at ~65k subs, pacing well -- Blocker: Community moderation scaling challenges — need clear guidelines -- Decision: Podcast distribution expanded to YouTube with video - -## Follow-up -- [ ] [[person-matteo-cellini]] to manage sponsor waitlist communications -- [ ] [[person-paco-furiani]] to evaluate video hosting for podcast YouTube expansion -- [ ] [[person-sara-ricci]] to develop community content guidelines diff --git a/demo-vault-v2/event-team-sync-2025-06-16.md b/demo-vault-v2/event-team-sync-2025-06-16.md deleted file mode 100644 index bd1a0de2..00000000 --- a/demo-vault-v2/event-team-sync-2025-06-16.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -aliases: ["Team sync — 2025-06-16"] -Is A: Event -Date: "2025-06-16" -Belongs to: "[[2025-06]]" -Related to: ["[[person-matteo-cellini]]", "[[person-paco-furiani]]", "[[person-sara-ricci]]"] -Tags: ["Work"] ---- -# Team sync — 2025-06-16 -Weekly Monday team alignment. Covered priorities, blockers, and sponsor updates. - -## Notes -- [[25q2-reach-70k]] progress review — at ~65k subs, pacing well -- Evaluated hiring a growth marketer — decided to wait until 80k subs -- Newsletter format experiment: added "Quick Links" section, testing engagement -- Discussed potential conference/event for community members in fall -- Blocker: Community moderation scaling challenges — need clear guidelines -- Decision: Sponsor waitlist process formalized — first-come-first-served - -## Follow-up -- [ ] [[person-matteo-cellini]] to manage sponsor waitlist communications -- [ ] [[person-matteo-cellini]] to explore conference sponsorship packages diff --git a/demo-vault-v2/event.md b/demo-vault-v2/event.md deleted file mode 100644 index 8b6d8274..00000000 --- a/demo-vault-v2/event.md +++ /dev/null @@ -1,7 +0,0 @@ ---- -Is A: Type ---- - -# Event - -An Event is a point-in-time occurrence — a meeting, a milestone, a trip, or anything that happened on a specific date. Events are linked to the entities they relate to. diff --git a/demo-vault-v2/evergreen.md b/demo-vault-v2/evergreen.md deleted file mode 100644 index e5532e0c..00000000 --- a/demo-vault-v2/evergreen.md +++ /dev/null @@ -1,7 +0,0 @@ ---- -Is A: Type ---- - -# Evergreen - -An Evergreen note captures a durable idea or insight that remains relevant over time. Unlike fleeting notes, evergreens are refined, stand-alone thoughts worth revisiting. diff --git a/demo-vault-v2/experiment-failed-podcast.md b/demo-vault-v2/experiment-failed-podcast.md deleted file mode 100644 index ffb1cf9f..00000000 --- a/demo-vault-v2/experiment-failed-podcast.md +++ /dev/null @@ -1,21 +0,0 @@ ---- -Is A: Experiment -Status: Open -trashed: true -trashed_at: "2026-02-05" ---- -# Failed Podcast Experiment - -Tried launching a weekly podcast alongside the newsletter. The production overhead was too high for the audience growth it generated. - -## Hypothesis -A companion podcast would increase newsletter subscribers by 30% within 3 months. - -## Results -- Produced 8 episodes over 2 months -- Gained only ~200 new subscribers (vs 2000 target) -- Each episode took 4-6 hours to produce -- ROI was negative compared to writing time - -## Decision -Dropped the podcast and reallocated time back to writing. The newsletter remains the primary channel. diff --git a/demo-vault-v2/experiment.md b/demo-vault-v2/experiment.md deleted file mode 100644 index 2e5f3d88..00000000 --- a/demo-vault-v2/experiment.md +++ /dev/null @@ -1,7 +0,0 @@ ---- -Is A: Type ---- - -# Experiment - -An Experiment is a hypothesis-driven investigation with a clear test and measurable outcome. Experiments are time-bound and have explicit success criteria. diff --git a/demo-vault-v2/final-renamed.md b/demo-vault-v2/final-renamed.md deleted file mode 100644 index b449dc77..00000000 --- a/demo-vault-v2/final-renamed.md +++ /dev/null @@ -1,10 +0,0 @@ ---- -title: Final Renamed -type: Note -status: Active ---- -# Final Renamed - -Title - -Snippet test content 1773604558993 diff --git a/demo-vault-v2/final-title-r-renamed.md b/demo-vault-v2/final-title-r-renamed.md deleted file mode 100644 index 1ff5bbe9..00000000 --- a/demo-vault-v2/final-title-r-renamed.md +++ /dev/null @@ -1,12 +0,0 @@ ---- -title: Final Title R Renamed -type: Note -status: Active ---- -# Final Title R Renamed - -Snippet test content 1773607529878enamed - -Snippet test content 1773607534349 - -[[Ma diff --git a/demo-vault-v2/final-title-r.md b/demo-vault-v2/final-title-r.md deleted file mode 100644 index a54a40dc..00000000 --- a/demo-vault-v2/final-title-r.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Final Title R -type: Note -status: Active ---- -# Final Title R - -[[Maenamed diff --git a/demo-vault-v2/final-title-renamed-renamed.md b/demo-vault-v2/final-title-renamed-renamed.md deleted file mode 100644 index 586e51db..00000000 --- a/demo-vault-v2/final-title-renamed-renamed.md +++ /dev/null @@ -1,12 +0,0 @@ ---- -title: Final Title Renamed Renamed -type: Note -status: Active ---- -# Final Title Renamed Renamed - -[[MaSnippet test content 1773614740678 - -Snippet test content 1773614745082 - -[[Ma diff --git a/demo-vault-v2/final-title-renamed.md b/demo-vault-v2/final-title-renamed.md deleted file mode 100644 index 57589b2e..00000000 --- a/demo-vault-v2/final-title-renamed.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Final Title Renamed -type: Note -status: Active ---- -# Final Title Renamed - -[[Ma diff --git a/demo-vault-v2/final-title.md b/demo-vault-v2/final-title.md deleted file mode 100644 index a69dde29..00000000 --- a/demo-vault-v2/final-title.md +++ /dev/null @@ -1,4 +0,0 @@ ---- -type: Note -status: Active ---- diff --git a/demo-vault-v2/goal.md b/demo-vault-v2/goal.md deleted file mode 100644 index 87e8b940..00000000 --- a/demo-vault-v2/goal.md +++ /dev/null @@ -1,7 +0,0 @@ ---- -Is A: Type ---- - -# Goal - -A Goal is a specific, measurable outcome you want to achieve within a defined timeframe. Goals belong to Areas and are tracked with Key Results or Measures. diff --git a/demo-vault-v2/index-funds-and-intellectual-humility.md b/demo-vault-v2/index-funds-and-intellectual-humility.md deleted file mode 100644 index e0369b34..00000000 --- a/demo-vault-v2/index-funds-and-intellectual-humility.md +++ /dev/null @@ -1,27 +0,0 @@ ---- -aliases: ["Index Funds as an Act of Intellectual Humility"] -Is A: Evergreen -Topics: ["[[topic-personal-finance]]"] -Status: Published ---- -# Index Funds as an Act of Intellectual Humility -Choosing index funds over stock picking isn't financial laziness — it's a philosophical position about knowledge and markets. - -The efficient market hypothesis, imperfect as it is, says that publicly available information is already priced in. When I buy a stock because I think it's undervalued, I'm saying I know something the combined intelligence of millions of market participants, with full access to company data and professional analysis tools, has missed. - -Index funds are the humble answer: I don't know which stocks will outperform, so I'll own all of them. The humility is the strategy. - -This principle extends well beyond investing. In most domains, the people who perform best over long time horizons are the ones who have accurate models of what they know and what they do not. Overconfidence in stock picking is just one instance of a broader pattern: humans systematically overestimate the quality of their predictions, especially in complex systems with many interacting variables. The research on expert prediction accuracy — Tetlock's work on superforecasting, Kahneman's studies on clinical judgment — consistently shows that simple models and broad diversification outperform confident expertise. - -What I find particularly interesting is how this maps to the tech industry. Many engineers and founders I know are index fund investors in their personal finances but stock-pickers in their professional decisions. They diversify their portfolio but bet everything on a single product idea, a single architectural decision, a single hiring philosophy. The intellectual humility they apply to markets disappears when they enter domains where they feel expert. This is not irrational — they genuinely know more about their domain than about equity markets — but the magnitude of their confidence often exceeds the magnitude of their actual edge. - -The practical takeaway I have settled on is a barbell approach. The vast majority of investable assets go into broad index funds where I acknowledge my lack of edge. A small allocation — small enough that losing it all would not matter — goes into individual bets where I have genuine information advantages, such as angel investing in spaces I know deeply. This respects the humility principle while leaving room for the rare cases where specific knowledge creates real edge. - -## Key insight -Index fund investing is not just a financial strategy — it is a worldview. It says: I respect the complexity of this system enough to admit I cannot predict it. This same intellectual humility, applied to product decisions, hiring, and strategy, produces better long-term outcomes than confident expertise in most domains. The paradox is that admitting you do not know is often the highest-return decision you can make. - -## Related -- [[investing-in-yourself-vs-markets]] — When self-investment offers better returns than market investment -- [[the-compound-effect-in-knowledge-work]] — Compounding applies to both financial returns and intellectual capital -- [[topic-personal-finance]] — Broader personal finance thinking -- [[note-thinking-fast-and-slow]] — Kahneman's work on cognitive biases that drive overconfident prediction diff --git a/demo-vault-v2/investing-in-yourself-vs-markets.md b/demo-vault-v2/investing-in-yourself-vs-markets.md deleted file mode 100644 index 7a9c242a..00000000 --- a/demo-vault-v2/investing-in-yourself-vs-markets.md +++ /dev/null @@ -1,27 +0,0 @@ ---- -aliases: ["Investing in Yourself vs. Markets"] -Is A: Evergreen -Topics: ["[[topic-personal-finance]]"] -Status: Published ---- -# Investing in Yourself vs. Markets -The standard personal finance advice is to maximize your savings rate and invest in index funds. This is correct for most people. But there's a prior question for founders and early-career professionals: what's the expected return on investing in yourself versus the market? - -If a €5,000 course or coaching program increases your earning power by €10,000/year, that's a 200% annual return — far above market rates. The window for these investments narrows as your career matures. - -Index funds are the right answer when skill development opportunities are exhausted. Most founders and ambitious professionals haven't reached that point yet. - -The framework I use is borrowed from venture capital: think of self-investment as a portfolio of bets with different risk profiles. Some investments — like learning a new programming language or getting better at writing — have near-certain positive returns because they compound across everything you do. Others — like attending a specific conference or hiring a coach — have higher variance but potentially transformative upside. The key is to maintain a portfolio that includes both, rather than defaulting entirely to the safe bet of index funds because the returns are easier to calculate. - -This is particularly relevant in the early years of building a content business. When I started Refactoring, the temptation was to save aggressively and invest conventionally. Instead, I spent money on writing courses, podcast equipment, design tools, and conferences where I could meet potential guests and sponsors. Each of those investments had ambiguous ROI at the time. In retrospect, the conference where I met three future sponsors returned more than any stock position I could have taken. The writing course that improved my newsletter open rates by 5 percentage points paid for itself within two months through increased sponsor value. - -The critical nuance is knowing when self-investment reaches diminishing returns. There is a phase in every career where the marginal return on skill development drops below the market return on financial investment. For most knowledge workers, that crossover happens later than they think — often not until their 40s or 50s. For founders, it may never happen at all, because the optionality of new skills in a rapidly changing environment maintains its value indefinitely. The mistake is defaulting to financial investment too early, when the right move is to invest in becoming more valuable. - -## Key insight -The expected return on self-investment is highest early in your career and when building a business, often exceeding market returns by an order of magnitude. The difficulty is that self-investment returns are uncertain and hard to measure, which makes them feel riskier than they are. Index funds feel safe because the return distribution is well-understood. But "feeling safe" and "being optimal" are different things. The rational approach is to invest heavily in yourself while the ROI exceeds market rates, then gradually shift to market investment as skill development returns diminish. - -## Related -- [[index-funds-and-intellectual-humility]] — The complementary case for index funds when you lack information edge -- [[the-compound-effect-in-knowledge-work]] — Self-investment compounds: each skill makes the next one more valuable -- [[on-founder-energy-management]] — Investing in your own capacity (sleep, health, energy) as a form of self-investment -- [[topic-personal-finance]] — Broader personal finance thinking diff --git a/demo-vault-v2/italian-startup-ecosystem-observations.md b/demo-vault-v2/italian-startup-ecosystem-observations.md deleted file mode 100644 index b1d2812d..00000000 --- a/demo-vault-v2/italian-startup-ecosystem-observations.md +++ /dev/null @@ -1,27 +0,0 @@ ---- -aliases: ["Observations on the Italian Startup Ecosystem"] -Is A: Evergreen -Topics: ["[[topic-italian-startups]]"] -Status: Published ---- -# Observations on the Italian Startup Ecosystem -Italy produces exceptional technical talent — some of the best engineers in Europe come from Politecnico di Milano and La Sapienza. But the startup ecosystem is immature in specific ways that are interesting to understand. - -The first is risk appetite. Italian professional culture, shaped partly by the importance of stable employment and family obligations, is less tolerant of career risk than US or UK equivalents. This makes recruiting for equity difficult and exit timelines different. - -The second is capital infrastructure. The VC ecosystem is smaller and more conservative than Northern Europe. The best Italian founders often move to Berlin, London, or Amsterdam to raise Series A — not because Italy is bad, but because the capital isn't there yet. - -There is a third dimension that gets less attention: the role of networks and relationships in Italian business culture. Italy runs on trust networks more than most Northern European economies. This means that warm introductions are not just helpful but essentially required for meaningful business conversations. A cold email to an Italian executive has near-zero conversion. A warm introduction from a mutual contact opens every door. This is neither better nor worse than the more transactional Anglo-Saxon approach — it is simply different, and founders who do not understand it waste enormous energy on tactics that work elsewhere but fail in Italy. - -The newsletter and content business community in Italy is also at a fascinating inflection point. When I started Refactoring, there were essentially no Italian-language professional newsletters with real scale. The concept of a paid or sponsor-supported newsletter was foreign to most Italian professionals. This is changing rapidly, partly because the creator economy narrative has reached Italy, and partly because Italian professionals who worked abroad are returning and bringing different models with them. The opportunity for a first mover in Italian-language B2B content is substantial, but the monetization playbook needs significant adaptation from the US model because the advertising market structure is fundamentally different. - -What gives me genuine optimism about the Italian ecosystem is the quality of the people. The engineering talent is world-class, the design sensibility is unmatched, and the combination of technical rigor with aesthetic awareness produces products that are genuinely beautiful in ways that most Silicon Valley companies cannot replicate. The constraint is not talent — it is infrastructure, capital, and cultural willingness to take risk. These are all solvable problems, and they are being solved, slowly. - -## Key insight -The Italian startup ecosystem's challenges are structural and cultural, not talent-related. The most impactful interventions are the ones that address risk tolerance and capital access — things like angel networks that normalize small-check investing, entrepreneurship programs at top universities that make startup careers visible and viable, and success stories that demonstrate the path is real. The ecosystem does not need to become Silicon Valley. It needs to become the best version of itself, leveraging Italy's unique strengths in design, engineering depth, and relationship-driven business culture. - -## Related -- [[small-teams-scale-through-systems]] — Small Italian teams can compete globally through systematization -- [[open-source-as-marketing]] — Open source as a path for Italian developer tools companies to build global distribution -- [[investing-in-yourself-vs-markets]] — The self-investment calculus for Italian founders navigating a smaller VC market -- [[topic-italian-startups]] — Broader topic on the Italian startup scene diff --git a/demo-vault-v2/knowledge-management-is-not-filing.md b/demo-vault-v2/knowledge-management-is-not-filing.md deleted file mode 100644 index 5fd8e04d..00000000 --- a/demo-vault-v2/knowledge-management-is-not-filing.md +++ /dev/null @@ -1,28 +0,0 @@ ---- -aliases: ["Knowledge Management Is Not Filing"] -Is A: Evergreen -Topics: ["[[topic-productivity-systems]]", "[[topic-reading-books]]"] -Status: Published ---- -# Knowledge Management Is Not Filing -The dominant metaphor for personal knowledge management is the filing cabinet: put things in labeled folders, retrieve when needed. This metaphor is mostly wrong. - -Knowledge becomes useful through connection, not storage. An idea you've filed carefully but never connected to your other ideas is almost as useless as an idea you forgot. - -The goal of a note-taking system should be to maximize the probability of unexpected connections — serendipitous collisions between ideas from different domains. This is why spatial proximity (notes near related notes) and links matter more than tags or folders. - -I spent years building elaborate folder hierarchies in Evernote and Notion before realizing that I almost never retrieved notes through the folder structure. The notes I actually used were the ones I stumbled across while working on something adjacent, or the ones that were linked from a note I was already reading. The filing metaphor assumes you know what you need before you need it. In practice, the most valuable moments in a knowledge system are the ones where you discover a connection you did not know existed — where a note about newsletter subject lines surfaces next to a note about cognitive load and you suddenly see the relationship between attention management and email engagement. - -This insight reshaped how I think about note-taking tools and led directly to building Laputa. The system should optimize for collision, not retrieval. This means flat structures with rich linking, evergreen notes that evolve over time rather than static captures, and an interface that makes it easy to see what is adjacent to what you are currently thinking about. The four-panel layout exists because context matters — seeing your current note alongside related notes, topics, and people creates the conditions for unexpected connections that a single-document view cannot. - -The practical implication is that the "writing" part of note-taking is more important than the "storing" part. When I process a book or an article, the act of writing a note in my own words — connecting the new idea to ideas I already hold — is where the value is created. The note itself is almost a byproduct. If I just highlight passages and file them, I have created the illusion of knowledge capture without the reality of knowledge integration. - -## Key insight -Knowledge management systems should be optimized for connection density, not storage efficiency. The most productive knowledge workers are not the ones with the most notes — they are the ones whose notes are most densely connected to each other. Every link between notes is a potential path for future insight. The filing cabinet metaphor fails because it treats knowledge as static objects to be retrieved. The better metaphor is a garden: ideas grow, connect, and produce unexpected fruit when tended over time. - -## Related -- [[the-compound-effect-in-knowledge-work]] — Connected knowledge compounds in value as the network of links grows -- [[reading-more-by-reading-better]] — Writing after reading is how knowledge integration happens -- [[procedure-evergreen-note-writing]] — The practical procedure for writing notes that connect rather than just store -- [[on-consistency-in-creative-work]] — Consistent note-taking practice is what builds the connection density over time -- [[topic-productivity-systems]] — Broader thinking on productivity and systems diff --git a/demo-vault-v2/laputa-qa-reference.md b/demo-vault-v2/laputa-qa-reference.md new file mode 100644 index 00000000..5c0e482d --- /dev/null +++ b/demo-vault-v2/laputa-qa-reference.md @@ -0,0 +1,16 @@ +--- +type: Note +aliases: + - "[[Laputa QA Reference]]" +related_to: + - "[[25q2-laputa-v2]]" +--- + +# Laputa QA Reference + +This note anchors the fixture's binary attachment scenario and gives native QA a simple note with an embedded image. + +![Fixture reference image](attachments/laputa-reference.png) + +Use this note to confirm that the editor renders an attached asset without dragging in a huge demo corpus. + diff --git a/demo-vault-v2/measure-articles-per-week.md b/demo-vault-v2/measure-articles-per-week.md deleted file mode 100644 index 585bcad4..00000000 --- a/demo-vault-v2/measure-articles-per-week.md +++ /dev/null @@ -1,27 +0,0 @@ ---- -aliases: ["Articles Per Week"] -Is A: Measure -Belongs to: "[[responsibility-content-production]]" -Unit: "articles" ---- -# Articles Per Week - -Articles per week is the primary output metric for [[responsibility-content-production]]. It measures the cadence of published newsletter essays and directly reflects content production capacity. Consistency in publishing is the single most important factor for audience trust, retention, and growth. Missed weeks erode subscriber engagement and reduce the inventory available for [[responsibility-sponsorships]]. - -This metric is tightly coupled with [[measure-subscribers]] growth and [[measure-open-rate]]. A steady publishing cadence builds habit formation in readers, which is the foundation of a healthy newsletter business. - -## How it's tracked - -Counted weekly based on published newsletter issues. Each distinct essay or curated edition counts as one article. Republished or cross-posted content (e.g., LinkedIn adaptations) does not count. The count is logged in the monthly tracking spreadsheet and reviewed during the [[procedure-weekly-newsletter]] workflow. - -## Targets - -- **Minimum**: 1 article per week (52/year). Missing a week should be exceptional. -- **Target**: 1.5 articles per week on average (including bonus mid-week posts). Roughly 75-80 articles per year. -- **Stretch**: 2 articles per week during high-output quarters (e.g., when running [[24q2-10-pillar-articles]]). - -## Notes - -- Quality matters more than quantity. A single high-quality essay that drives engagement and shares is worth more than two mediocre posts. Use [[measure-essay-quality-score]] as the balancing metric. -- Publishing cadence tends to drop during periods of heavy project work (e.g., [[25q1-laputa-v1]]) or travel. Pre-writing a buffer of 2-3 essays helps maintain consistency. -- If the rate drops below 1/week for two consecutive weeks, treat it as an escalation and assess bandwidth allocation across responsibilities. diff --git a/demo-vault-v2/measure-books-per-month.md b/demo-vault-v2/measure-books-per-month.md deleted file mode 100644 index 6e007f9f..00000000 --- a/demo-vault-v2/measure-books-per-month.md +++ /dev/null @@ -1,28 +0,0 @@ ---- -aliases: ["Books Per Month"] -Is A: Measure -Belongs to: "[[responsibility-learning]]" -Unit: "books" ---- -# Books Per Month - -Books per month tracks the rate of deliberate learning through long-form reading. Reading is the primary input for original thinking and content ideation across [[responsibility-content-production]]. This metric exists because reading is easily deprioritized under business pressure, and tracking it ensures [[responsibility-learning]] maintains its share of time and attention. - -This measure is a leading indicator for content quality: months with higher reading volume tend to correlate with more original newsletter essays and stronger engagement on those essays. - -## How it's tracked - -Each completed book (physical, Kindle, or audiobook) is logged in the monthly tracking spreadsheet. A book counts as "read" when finished or when at least 80% has been consumed (for reference books where cover-to-cover reading is not the goal). Audiobooks count fully. Re-reads count if substantial new notes are taken. - -## Targets - -- **Minimum**: 1 book per month. No month should pass without at least one completed book. -- **Target**: 1.5-2 books per month (18-24 per year), as set by [[2024-read-24-books]] and [[2025-read-20-books]]. -- **Stretch**: 2.5 books per month, achievable when audiobook consumption during cycling training is high. - -## Notes - -- Audiobooks during cycling rides are the most reliable channel for volume. In 2024, roughly a third of all books were consumed this way. This channel scales with [[measure-cycling-km-per-month]]. -- Non-fiction relevant to the newsletter (engineering, business, leadership) should represent at least 50-60% of the mix, but fiction and unrelated reading have value for creative cross-pollination. -- Track this alongside [[measure-evergreen-notes-created]] to ensure reading translates into lasting, reusable knowledge rather than passive consumption. -- Months with zero books are a red flag for burnout or unsustainable workload distribution. diff --git a/demo-vault-v2/measure-close-rate.md b/demo-vault-v2/measure-close-rate.md index 0f73a6c5..b04a404b 100644 --- a/demo-vault-v2/measure-close-rate.md +++ b/demo-vault-v2/measure-close-rate.md @@ -1,28 +1,12 @@ --- -aliases: ["Sponsorship Close Rate"] -Is A: Measure -Belongs to: "[[responsibility-sponsorships]]" -Unit: "percent" +type: Measure +aliases: + - "[[Sponsorship Close Rate]]" +belongs_to: "[[responsibility-sponsorships]]" +unit: percent --- + # Sponsorship Close Rate -Close rate measures the percentage of qualified sponsorship leads that convert into signed deals. It is the key efficiency metric for [[responsibility-sponsorships]] and directly determines how much sales effort is needed to hit revenue targets like [[2024-double-revenue]] and [[2025-reach-22k-mrr]]. A higher close rate means less time spent on outreach and follow-ups, freeing bandwidth for content production and other priorities. +Tracks how many qualified sponsor conversations become signed deals. -This metric also serves as a signal for product-market fit of the sponsorship offering. A declining close rate may indicate that pricing is too high, that the value proposition is unclear, or that the audience demographics are shifting away from what sponsors need. - -## How it's tracked - -Calculated monthly as: (signed deals in the month) / (qualified leads that received a proposal in the month) x 100. A "qualified lead" is any sponsor or potential sponsor who has received a formal proposal or rate card. Leads that are disqualified before the proposal stage are excluded. Tracked in the sponsor CRM ([[24q2-sponsor-crm]]) and summarized in the monthly spreadsheet. - -## Targets - -- **Minimum**: 25%. Below this, the sales process needs diagnosis (pricing, targeting, or pitch quality). -- **Target**: 30-35%. This is the range that supports the [[2025-reach-22k-mrr]] goal without excessive sales effort. -- **Stretch**: 40%+. Achievable with a strong inbound pipeline and well-positioned sponsorship packages. - -## Notes - -- Close rate tends to be higher for returning sponsors (renewals) than for first-time buyers. Track these separately to understand pipeline health. -- The launch of tiered sponsorship packages in [[24q1-launch-sponsorship-packages]] improved close rate by approximately 5 percentage points because prospects could self-select into a price tier. -- If close rate drops below 25% for two consecutive months, review whether [[measure-subscribers]] growth has slowed or whether competitive landscape has shifted. -- Seasonal variation is real: Q1 and Q4 tend to have higher close rates due to annual budget allocation cycles. diff --git a/demo-vault-v2/measure-cycling-km-per-month.md b/demo-vault-v2/measure-cycling-km-per-month.md deleted file mode 100644 index cb5c206d..00000000 --- a/demo-vault-v2/measure-cycling-km-per-month.md +++ /dev/null @@ -1,30 +0,0 @@ ---- -aliases: ["Cycling Km Per Month"] -Is A: Measure -Belongs to: "[[responsibility-health-fitness]]" -Unit: "km" ---- -# Cycling Km Per Month - -Cycling kilometers per month is the primary volume metric for [[responsibility-health-fitness]]. It tracks total distance ridden across all types of rides (structured training, commuting, long weekend rides, events). Consistent cycling volume is foundational for endurance goals like [[2024-complete-two-gran-fondos]] and [[2025-ride-stelvio]], and serves as a proxy for overall physical fitness and stress management. - -Beyond fitness, cycling time is also productive time: audiobook consumption during rides directly feeds [[measure-books-per-month]] and [[responsibility-learning]]. - -## How it's tracked - -Total monthly kilometers are pulled from Strava at the end of each month and logged in the tracking spreadsheet. All ride types count (indoor trainer, outdoor road, gravel). Virtual rides (Zwift) count at face value. The metric is reviewed monthly and compared against the seasonal training plan. - -## Targets - -- **Off-season (Nov-Feb)**: 200-300 km/month. Maintenance volume to preserve base fitness. -- **Build phase (Mar-May)**: 400-500 km/month. Ramp-up for spring/summer events. -- **Peak season (Jun-Sep)**: 500-700 km/month. Event preparation and racing. -- **Recovery (Oct)**: 200-300 km/month. Active recovery before off-season. - -## Notes - -- Monthly volume is more informative than weekly because weather and travel create natural week-to-week variability. -- During peak training for [[2025-ride-stelvio]], monthly volume exceeded 600 km for three consecutive months. This required careful time management to avoid crowding out business priorities. -- Indoor trainer sessions during winter are essential for maintaining the 200 km minimum. Without them, off-season volume drops to near zero. -- Track alongside [[measure-resting-hr]] to monitor whether volume translates into aerobic fitness gains. High volume with no HR improvement suggests overtraining or insufficient recovery. -- A sustained drop below 200 km/month outside of planned rest periods is a warning sign for either schedule overload or declining motivation. diff --git a/demo-vault-v2/measure-essay-quality-score.md b/demo-vault-v2/measure-essay-quality-score.md deleted file mode 100644 index 74528fd5..00000000 --- a/demo-vault-v2/measure-essay-quality-score.md +++ /dev/null @@ -1,36 +0,0 @@ ---- -aliases: ["Essay Quality Score"] -Is A: Measure -Belongs to: "[[responsibility-content-production]]" -Unit: "score (1-5)" ---- -# Essay Quality Score - -Essay quality score is a self-assessed rating applied to each published newsletter essay, measuring depth, originality, and reader value on a 1-5 scale. While [[measure-articles-per-week]] tracks output quantity, this metric ensures that production cadence does not come at the expense of quality. High-quality essays drive shares, organic growth, and long-term brand authority, all of which support [[responsibility-grow-newsletter]] and [[responsibility-sponsorships]]. - -This is intentionally a subjective metric. External proxies like open rate or share count are influenced by subject line, timing, and audience mood. A self-assessed quality score captures whether the essay met the author's own standard for depth and craft. - -## How it's tracked - -After each essay is published, assign a score from 1 to 5 based on the following rubric: - -- **5 (Exceptional)**: Original framework or insight, well-researched, likely to be referenced and shared widely. Pillar article quality. -- **4 (Strong)**: Clear thesis, good depth, adds genuine value. Standard high-quality issue. -- **3 (Solid)**: Competent and useful but not particularly original. Gets the job done. -- **2 (Weak)**: Shallow, derivative, or rushed. Published to maintain cadence but below standard. -- **1 (Poor)**: Should not have been published. Indicates a process failure. - -Scores are logged in the tracking spreadsheet alongside each essay's publication date and topic. - -## Targets - -- **Minimum monthly average**: 3.5. Consistently publishing below this indicates either burnout, insufficient research time, or too-aggressive publishing cadence. -- **Target monthly average**: 4.0. This represents consistently strong output with occasional exceptional pieces. -- **Stretch**: At least two 5-rated essays per quarter. These become pillar content for SEO and long-term value. - -## Notes - -- A score of 2 or below should trigger a retrospective: was the issue time pressure, topic selection, or insufficient preparation? The answer informs whether to adjust [[measure-articles-per-week]] targets. -- Quality score tends to inversely correlate with publishing frequency during crunch periods. If the average drops below 3.5, consider temporarily reducing to 1 article per week. -- The best-performing essays in terms of engagement (shares, replies) tend to score 4 or 5. However, some 3-rated tactical pieces perform well because the topic is timely. -- Review quality scores quarterly to identify patterns in topic selection and preparation time allocation. diff --git a/demo-vault-v2/measure-evergreen-notes-created.md b/demo-vault-v2/measure-evergreen-notes-created.md deleted file mode 100644 index eec7f7e9..00000000 --- a/demo-vault-v2/measure-evergreen-notes-created.md +++ /dev/null @@ -1,29 +0,0 @@ ---- -aliases: ["Evergreen Notes Created"] -Is A: Measure -Belongs to: "[[responsibility-learning]]" -Unit: "notes/month" ---- -# Evergreen Notes Created - -Evergreen notes created per month tracks the rate at which raw learning inputs (books, articles, conversations, experiences) are distilled into permanent, reusable knowledge notes in the vault. This is the output metric for [[responsibility-learning]] and measures whether reading and research are translating into lasting intellectual capital rather than being passively consumed and forgotten. - -Evergreen notes are the building blocks of original content. A healthy flow of new notes feeds newsletter essay ideation, podcast topics, and long-term thinking. The concept draws from the Zettelkasten tradition: each note should express one idea, link to related notes, and be written in the author's own words. - -## How it's tracked - -Counted monthly by reviewing new notes added to the vault that meet the evergreen criteria: (1) expresses a single atomic idea, (2) is written in original language (not a copy-paste highlight), (3) includes at least one wiki-link to a related note. Quick capture notes, drafts, and meeting notes do not count. The count is logged in the monthly tracking spreadsheet. - -## Targets - -- **Minimum**: 5 notes per month. Below this, the learning pipeline is stalling. -- **Target**: 10-15 notes per month. This sustains a healthy ideas pipeline for content production. -- **Stretch**: 20+ notes per month, typically achievable during heavy reading periods or after conferences. - -## Notes - -- Quality matters more than quantity. A well-linked, deeply considered note is worth more than five shallow highlights. However, a minimum volume ensures the habit is active. -- Track alongside [[measure-books-per-month]]. Expect roughly 3-5 evergreen notes per book. If the ratio is lower, the reading is not being processed deeply enough. -- Since shipping [[2025-ship-laputa]], the note creation workflow has improved significantly. Having the vault open in a dedicated app reduces friction compared to the previous file-browser approach. -- Notes created from podcast guest conversations tend to be among the most original and well-connected. The [[responsibility-podcast]] is an underrated source of evergreen content. -- Review the backlog of unprocessed highlights quarterly. A growing backlog means the creation rate needs to increase or the reading rate needs to decrease. diff --git a/demo-vault-v2/measure-net-worth.md b/demo-vault-v2/measure-net-worth.md deleted file mode 100644 index dc4f0434..00000000 --- a/demo-vault-v2/measure-net-worth.md +++ /dev/null @@ -1,29 +0,0 @@ ---- -aliases: ["Net Worth"] -Is A: Measure -Belongs to: "[[responsibility-personal-finance]]" -Unit: "EUR" ---- -# Net Worth - -Net worth is the comprehensive measure of financial health for [[responsibility-personal-finance]]. It captures the cumulative effect of income growth, savings discipline, and investment returns in a single number. Tracking net worth monthly provides a long-term perspective that smooths out the noise of individual income or expense fluctuations. - -For an indie business owner, net worth is particularly important because income is variable and there is no employer-provided safety net. A growing net worth trajectory indicates that the business is not only generating revenue but also building durable personal wealth. - -## How it's tracked - -Calculated monthly during the [[procedure-monthly-portfolio-review]]. Sum of all assets (bank accounts, investment portfolios, retirement accounts, real estate equity) minus all liabilities (mortgage, any outstanding debt). Crypto and illiquid assets are included at conservative market valuations. Logged in the financial tracking spreadsheet with month-end snapshots. - -## Targets - -- **Minimum**: Net worth should increase in at least 8 of 12 months in a given year. Negative months are expected (market corrections, large purchases) but should be the exception. -- **Target**: 15-20% year-over-year net worth growth, driven by a combination of business income, [[measure-savings-rate]], and market returns. -- **Stretch**: 25%+ year-over-year growth, achievable in strong market years combined with business revenue growth. - -## Notes - -- Net worth is a lagging indicator. It reflects decisions made months or years ago. Use it for long-term trend analysis, not short-term decision-making. -- The [[procedure-quarterly-financial-planning]] session is where net worth trends are reviewed and adjustments are made to savings and investment allocations. -- Business revenue growth ([[measure-sponsorship-mrr]]) is the largest controllable input to net worth. Market returns matter but are not controllable. -- Avoid over-indexing on month-to-month changes. Market volatility can swing net worth by 5-10% in a single month without reflecting any real change in financial behavior. -- Track separately from business revenue to maintain a clear boundary between personal and business finances. The business funds personal wealth via salary and distributions, but they are distinct. diff --git a/demo-vault-v2/measure-open-rate.md b/demo-vault-v2/measure-open-rate.md deleted file mode 100644 index 0f17f263..00000000 --- a/demo-vault-v2/measure-open-rate.md +++ /dev/null @@ -1,29 +0,0 @@ ---- -aliases: ["Newsletter Open Rate"] -Is A: Measure -Belongs to: "[[responsibility-grow-newsletter]]" -Unit: "percent" ---- -# Newsletter Open Rate - -Open rate is the primary engagement metric for the newsletter and a critical input to [[responsibility-sponsorships]] pricing conversations. It measures the percentage of delivered emails that are opened, serving as a proxy for audience trust, content relevance, and list health. A consistently high open rate signals that subscribers find the content valuable enough to prioritize in their inbox. - -Open rate is also the metric sponsors care about most (alongside click rate). The newsletter's ability to command premium sponsorship pricing for [[measure-sponsorship-mrr]] is directly tied to maintaining an above-industry open rate. - -## How it's tracked - -Reported by the email platform (Substack/ConvertKit) for each issue. The monthly average is calculated across all issues published in the month and logged in the tracking spreadsheet. Note that email open tracking relies on pixel loading, which undercounts opens on privacy-focused email clients (Apple Mail Privacy Protection, Hey, etc.). The true open rate is likely 5-10% higher than reported. - -## Targets - -- **Minimum**: 40%. Below this for a list of this size suggests declining content quality, list hygiene issues, or audience mismatch. -- **Target**: 45-50%. This range is well above the industry average for newsletters (typically 20-30%) and supports premium sponsorship pricing. -- **Stretch**: 55%+. Achievable on high-interest topics or following a viral social media post that drives engaged subscribers. - -## Notes - -- Open rate naturally declines as [[measure-subscribers]] grows because larger lists include a higher proportion of passive subscribers. The goal is to slow this decay, not prevent it entirely. -- Subject line quality is the single biggest lever for open rate. Specific, curiosity-driven subject lines consistently outperform generic ones. -- Regular list hygiene (removing subscribers who have not opened in 90+ days) can boost open rate by 3-5 percentage points. Run this quarterly. -- The 47% open rate achieved at 53,000 subscribers in 2024 is exceptional. Maintaining above 43% at 85,000 subscribers ([[2025-reach-85k-subscribers]]) would be a strong result. -- Track per-issue open rates to identify topic patterns. Some topics reliably over- or under-perform, which informs editorial planning. diff --git a/demo-vault-v2/measure-podcast-downloads.md b/demo-vault-v2/measure-podcast-downloads.md deleted file mode 100644 index 62fae463..00000000 --- a/demo-vault-v2/measure-podcast-downloads.md +++ /dev/null @@ -1,29 +0,0 @@ ---- -aliases: ["Podcast Downloads"] -Is A: Measure -Belongs to: "[[responsibility-podcast]]" -Unit: "downloads/episode" ---- -# Podcast Downloads - -Podcast downloads per episode is the primary audience metric for [[responsibility-podcast]]. It measures reach and listener interest at the episode level, providing a clearer signal than total downloads (which inflate with back-catalog listens). Growing downloads per episode indicates that the podcast is building a loyal, returning audience rather than relying on one-off spikes. - -This metric is also the foundation for podcast-specific sponsorship pricing. Sponsors price based on CPM (cost per mille downloads), so episode-level downloads directly determine [[measure-sponsorship-mrr]] contribution from the podcast channel. - -## How it's tracked - -Measured as 30-day downloads per episode, which is the industry standard for podcast measurement. Each episode's download count is pulled from the podcast hosting platform 30 days after publication and logged in the tracking spreadsheet. Monthly averages are calculated across all episodes published that month. Reviewed during [[procedure-podcast-analytics]]. - -## Targets - -- **Minimum**: 500 downloads per episode. Below this, the podcast is not reaching a viable audience and may not justify the production investment. -- **Target**: 1,500-2,000 downloads per episode. This range supports meaningful sponsor CPM rates and indicates a growing, engaged listener base. -- **Stretch**: 3,000+ downloads per episode. At this level, the podcast becomes a significant independent revenue channel. - -## Notes - -- Downloads grew from ~400 in early Season 1 ([[24q1-podcast-season-1]]) to ~1,300 by late Season 2 ([[24q3-podcast-season-2]]). The growth trajectory is healthy. -- Interview episodes consistently outperform solo episodes in downloads (roughly 1.5x). However, solo episodes have higher completion rates, suggesting deeper engagement per listener. -- Cross-promotion from the newsletter is the primary discovery channel. Mentions in the newsletter drive 60-70% of initial episode downloads. -- Consider tracking unique listeners in addition to downloads for a more accurate audience size picture. One listener may download on multiple devices. -- Seasonal patterns exist: downloads dip in summer and around holidays. Plan high-investment episodes for high-attention windows (September, January). diff --git a/demo-vault-v2/measure-podcast-episodes-per-month.md b/demo-vault-v2/measure-podcast-episodes-per-month.md deleted file mode 100644 index ff15dab3..00000000 --- a/demo-vault-v2/measure-podcast-episodes-per-month.md +++ /dev/null @@ -1,29 +0,0 @@ ---- -aliases: ["Podcast Episodes Per Month"] -Is A: Measure -Belongs to: "[[responsibility-podcast]]" -Unit: "episodes" ---- -# Podcast Episodes Per Month - -Podcast episodes per month tracks the production output cadence for [[responsibility-podcast]]. Like [[measure-articles-per-week]] for the newsletter, publishing consistency is the foundation of audience habit formation. Listeners need to know when to expect new episodes, and irregular publishing erodes the routine that drives loyal listenership and [[measure-podcast-downloads]] growth. - -This metric ensures that the podcast maintains a sustainable rhythm without compromising the production quality that [[person-paco-furiani]] and the team have established. - -## How it's tracked - -Counted as the number of podcast episodes published in a given calendar month. Both full-length episodes and bonus/short episodes count. Recorded episodes that are not yet published do not count. Logged in the monthly tracking spreadsheet and reviewed as part of [[procedure-podcast-analytics]]. - -## Targets - -- **During active seasons**: 3-4 episodes per month (roughly weekly cadence). This was the pace for [[24q1-podcast-season-1]] and [[24q3-podcast-season-2]]. -- **Between seasons**: 0-1 episodes per month. Breaks between seasons are intentional to avoid burnout and allow for guest booking and content planning. -- **Annual target**: 20-25 episodes across the year, distributed across 2-3 seasons. - -## Notes - -- The seasonal model (8-12 episode seasons with breaks in between) works well for this format. It prevents podcast fatigue for both the host and listeners. -- Production bottleneck is typically guest scheduling, not editing. [[person-paco-furiani]] handles editing and post-production efficiently, usually within 48 hours of receiving raw audio. -- During active seasons, batching 2-3 recordings in a single week and releasing them weekly is the most efficient approach. This reduces context-switching costs. -- If the cadence drops below 2 episodes per month during an active season, assess whether the issue is guest pipeline, recording time, or editorial direction. -- Coordinate season launches with the newsletter calendar to maximize cross-promotion. The first episode of a season should coincide with a newsletter feature. diff --git a/demo-vault-v2/measure-resting-hr.md b/demo-vault-v2/measure-resting-hr.md deleted file mode 100644 index 50ad9588..00000000 --- a/demo-vault-v2/measure-resting-hr.md +++ /dev/null @@ -1,29 +0,0 @@ ---- -aliases: ["Resting Heart Rate"] -Is A: Measure -Belongs to: "[[responsibility-health-fitness]]" -Unit: "bpm" ---- -# Resting Heart Rate - -Resting heart rate (RHR) is the primary physiological indicator of cardiovascular fitness and recovery status for [[responsibility-health-fitness]]. It provides an objective, daily signal of how the body is adapting to training load, stress, and sleep quality. Unlike subjective measures like "how do I feel," RHR is quantifiable, trend-able, and difficult to game. - -For endurance goals like [[2024-complete-two-gran-fondos]] and [[2025-ride-stelvio]], a declining RHR over a training block confirms that aerobic fitness is improving. Conversely, a rising RHR trend can signal overtraining, illness, poor sleep, or excessive business-related stress. - -## How it's tracked - -Measured daily via a wearable device (smartwatch or chest strap) during the first waking minutes. The monthly average is logged in the tracking spreadsheet. Weekly trends are monitored through the wearable's companion app. The most reliable readings come from overnight averages, which eliminate the influence of morning caffeine or activity. - -## Targets - -- **Healthy baseline**: 52-58 bpm. This is the typical range during moderate training periods. -- **Peak fitness**: Below 50 bpm. Achievable during peak training blocks (e.g., the months leading up to the Stelvio climb). -- **Warning threshold**: Above 60 bpm sustained for 3+ days. Indicates potential overtraining, illness, or accumulated stress. Trigger a rest day or reduced training volume. - -## Notes - -- RHR averaged 50 bpm during peak training for [[2025-ride-stelvio]], confirming strong aerobic adaptation. -- Spikes of 5+ bpm above the rolling average are a reliable early warning for incoming illness. Taking a preemptive rest day when this happens has avoided several full-blown colds. -- Alcohol consumption the previous evening reliably elevates RHR by 5-8 bpm. This is useful feedback for moderating intake during training blocks. -- Business stress and poor sleep affect RHR almost as much as physical training does. During high-stress periods (product launches, sponsor negotiations), expect RHR to be 3-5 bpm higher than the training-adjusted baseline. -- Track alongside [[measure-cycling-km-per-month]] to correlate volume with fitness outcomes. High volume without RHR improvement suggests the training needs more intensity, not more miles. diff --git a/demo-vault-v2/measure-savings-rate.md b/demo-vault-v2/measure-savings-rate.md deleted file mode 100644 index eab17c60..00000000 --- a/demo-vault-v2/measure-savings-rate.md +++ /dev/null @@ -1,29 +0,0 @@ ---- -aliases: ["Savings Rate"] -Is A: Measure -Belongs to: "[[responsibility-personal-finance]]" -Unit: "percent" ---- -# Savings Rate - -Savings rate measures the percentage of after-tax income that is saved or invested each month. It is the most actionable metric within [[responsibility-personal-finance]] because, unlike market returns or income growth, it is directly controllable through spending decisions. A consistently high savings rate is the primary driver of long-term [[measure-net-worth]] growth and provides the financial buffer necessary to take entrepreneurial risks. - -For an indie business owner with variable income, savings rate is also a resilience metric. Maintaining discipline during high-income months builds the runway needed to weather slower periods without anxiety. - -## How it's tracked - -Calculated monthly as: (income - expenses) / income x 100. Income includes business salary/distributions and any side income. Expenses include all personal and household spending. Business expenses are excluded (they reduce income before it reaches the personal layer). Logged during the [[procedure-monthly-portfolio-review]] and reviewed in detail during [[procedure-quarterly-financial-planning]]. - -## Targets - -- **Minimum**: 20%. Below this for more than two consecutive months indicates either a spending issue or an income problem that needs attention. -- **Target**: 30-40%. This range balances quality of life with aggressive wealth building. At this rate, meaningful investment contributions happen every month. -- **Stretch**: 50%+. Achievable in high-revenue months (e.g., when annual sponsor contracts are paid upfront). Not sustainable year-round but should be the norm in peak months. - -## Notes - -- Savings rate is highly seasonal for indie businesses. Months with large sponsor payments can push the rate above 60%, while months between contracts may dip below 20%. The annual average matters more than any single month. -- Automate savings where possible. A fixed monthly transfer to investment accounts on the 1st of each month ensures baseline savings regardless of spending temptations. -- Housing and travel are the two largest expense categories. Optimizing either one has an outsized impact on annual savings rate. -- Track savings rate alongside [[measure-sponsorship-mrr]] to understand the relationship between business revenue and personal wealth building. Revenue growth without corresponding savings discipline is a vanity metric. -- Review annually during [[procedure-quarterly-financial-planning]] to adjust target ranges based on income trajectory and life goals. diff --git a/demo-vault-v2/measure-sponsorship-mrr.md b/demo-vault-v2/measure-sponsorship-mrr.md index 94b7b8f5..539ed40f 100644 --- a/demo-vault-v2/measure-sponsorship-mrr.md +++ b/demo-vault-v2/measure-sponsorship-mrr.md @@ -1,29 +1,12 @@ --- -aliases: ["Sponsorship MRR"] -Is A: Measure -Belongs to: "[[responsibility-sponsorships]]" -Unit: "EUR/month" +type: Measure +aliases: + - "[[Sponsorship MRR]]" +belongs_to: "[[responsibility-sponsorships]]" +unit: EUR/month --- + # Sponsorship MRR -Sponsorship MRR (monthly recurring revenue) is the top-line financial metric for the business and the north star for [[responsibility-sponsorships]]. It measures the total monthly revenue from all active sponsorship contracts, normalized to a monthly figure even for contracts billed quarterly or annually. This is the number that determines whether the business can sustain its current team, fund product development, and grow. +Tracks monthly recurring sponsorship revenue so the responsibility note has a real linked metric. -MRR is the single metric that connects audience growth ([[measure-subscribers]]), engagement quality ([[measure-open-rate]]), and sales effectiveness ([[measure-close-rate]]) into a financial outcome. It is the ultimate downstream measure of whether the newsletter business model is working. - -## How it's tracked - -Calculated monthly by summing all active sponsorship contracts and normalizing to monthly amounts. Annual contracts are divided by 12; quarterly contracts by 3. New contracts are included from their start month; churned contracts are excluded from their end month. Tracked in the sponsor CRM ([[24q2-sponsor-crm]]) and the financial spreadsheet. Reviewed monthly and reported alongside other financial metrics during [[procedure-monthly-portfolio-review]]. - -## Targets - -- **2024 target**: 14,000 EUR/month, as set by [[2024-double-revenue]]. Achieved ~15,200 EUR by December 2024. -- **2025 target**: 22,000 EUR/month, as set by [[2025-reach-22k-mrr]]. Currently tracking at ~19,000 EUR. -- **Long-term**: 30,000+ EUR/month. At this level, the business comfortably supports a team of 4-5 and funds product investments without external capital. - -## Notes - -- MRR growth is driven by three levers: new sponsor acquisition, existing sponsor upsells (larger packages or more frequent placements), and pricing increases. All three should be active simultaneously. -- Renewal rate is as important as new business. Losing a 2,000 EUR/month sponsor and acquiring a 2,000 EUR/month sponsor is zero progress despite the sales effort. Track renewal rate separately. -- [[measure-subscribers]] growth is the primary enabler of pricing power. Every 10,000 subscriber increase supports approximately 1,500 EUR in additional monthly pricing. -- Diversification matters: no single sponsor should represent more than 20% of MRR. Concentration risk makes the business fragile to individual sponsor decisions. -- Revenue from the podcast ([[measure-podcast-downloads]]) is tracked within this metric when podcast sponsors overlap with newsletter sponsors. Separate the podcast contribution for channel-level analysis. diff --git a/demo-vault-v2/measure-subscribers.md b/demo-vault-v2/measure-subscribers.md deleted file mode 100644 index dfff9add..00000000 --- a/demo-vault-v2/measure-subscribers.md +++ /dev/null @@ -1,29 +0,0 @@ ---- -aliases: ["Newsletter Subscribers"] -Is A: Measure -Belongs to: "[[responsibility-grow-newsletter]]" -Unit: "subscribers" ---- -# Newsletter Subscribers - -Total newsletter subscribers is the foundational audience metric for the business. It measures the size of the addressable audience for content distribution, sponsorship inventory, and future product launches. Subscriber count is the number that sponsors evaluate first when considering a partnership, and it directly underpins the pricing power that drives [[measure-sponsorship-mrr]]. - -Growth in subscribers is the result of all [[responsibility-grow-newsletter]] activities: content quality, SEO, social distribution, referral programs, and cross-promotion. It is simultaneously a vanity metric (raw count without engagement is meaningless) and the most important metric (without scale, the business model does not work). - -## How it's tracked - -Reported by the email platform as total active subscribers at month-end. "Active" means the subscriber has not unsubscribed and has not been removed via list hygiene. Unconfirmed signups (double opt-in pending) are excluded. Logged in the monthly tracking spreadsheet. Net growth (new subscribers minus unsubscribes and removals) is tracked alongside the total to monitor churn. - -## Targets - -- **2024 target**: 50,000 subscribers by December 2024 ([[2024-reach-50k-subscribers]]). Achieved 53,000. -- **2025 target**: 85,000 subscribers by December 2025 ([[2025-reach-85k-subscribers]]). Currently at ~75,000. -- **Monthly net growth target**: 2,500+ new subscribers per month to stay on pace for year-end goals. - -## Notes - -- Subscriber count is a necessary but insufficient metric. Always review alongside [[measure-open-rate]] to ensure list quality. A list of 100,000 with 20% open rate is less valuable than 60,000 with 50% open rate. -- Growth channels as of 2025: Twitter/X (~35%), SEO/organic search (~25%), referral program ([[25q1-referral-program]], ~20%), direct/word-of-mouth (~15%), other (~5%). -- Quarterly list hygiene (removing 90-day inactive subscribers) temporarily reduces the total count but improves all engagement metrics. This trade-off is always worth making. -- The [[25q1-newsletter-seo-sprint]] is a long-term investment in organic subscriber acquisition. SEO-sourced subscribers tend to have higher retention than social-sourced ones. -- Milestone moments (crossing 50k, 75k, 100k) are content opportunities. The "behind the scenes" posts about growth milestones consistently perform well in engagement. diff --git a/demo-vault-v2/measure-task-completion-rate.md b/demo-vault-v2/measure-task-completion-rate.md deleted file mode 100644 index b903d037..00000000 --- a/demo-vault-v2/measure-task-completion-rate.md +++ /dev/null @@ -1,29 +0,0 @@ ---- -aliases: ["Task Completion Rate"] -Is A: Measure -Belongs to: "[[responsibility-team-management]]" -Unit: "percent" ---- -# Task Completion Rate - -Task completion rate measures the percentage of planned tasks that are completed within their committed timeframe. It is the primary throughput metric for [[responsibility-team-management]] and reflects the team's ability to plan realistically and execute reliably. A consistently high completion rate indicates healthy planning, clear priorities, and manageable workload. A low rate signals overcommitment, unclear requirements, or blocked workflows. - -This metric applies to the entire team's output, not just individual contributors. It surfaces systemic issues (too many priorities, poor task definition, dependency bottlenecks) rather than individual performance problems. - -## How it's tracked - -Calculated per sprint or per week, depending on the team's current workflow. Formula: (tasks completed on time) / (tasks committed for the period) x 100. Tasks that are explicitly descoped or deprioritized mid-period are removed from the denominator. Tasks that roll over to the next period count as incomplete. Tracked in the project management tool and summarized monthly in the tracking spreadsheet. - -## Targets - -- **Minimum**: 65%. Below this suggests chronic overcommitment or unclear task definitions. Requires a planning process review. -- **Target**: 75-85%. This range indicates realistic planning with a healthy margin for unexpected work and interruptions. -- **Stretch**: 90%+. Achievable in well-scoped sprints with low interrupt load. Sustained 90%+ may indicate under-commitment. - -## Notes - -- A completion rate consistently above 90% is a warning sign, not a success. It likely means the team is sandbagging estimates or not taking on enough ambitious work. -- The most common cause of low completion rate is not underperformance but overcommitment. The fix is usually better planning, not faster execution. -- Track alongside [[measure-team-nps]] to understand whether high completion rates are coming at the cost of team satisfaction (burnout, unsustainable pace). -- Differentiate between "completed" and "completed well." A task rushed to completion with quality shortcuts should not count the same as a properly finished task. Use [[measure-essay-quality-score]] as a proxy for content-related tasks. -- Review monthly trends rather than individual weeks. Single-week dips are normal; sustained trends over 4+ weeks require intervention. diff --git a/demo-vault-v2/measure-team-nps.md b/demo-vault-v2/measure-team-nps.md deleted file mode 100644 index daff4f5f..00000000 --- a/demo-vault-v2/measure-team-nps.md +++ /dev/null @@ -1,29 +0,0 @@ ---- -aliases: ["Team NPS"] -Is A: Measure -Belongs to: "[[responsibility-team-management]]" -Unit: "score (1-10)" ---- -# Team NPS - -Team NPS (Net Promoter Score) is a simplified satisfaction metric that captures how team members feel about working on the project. It is the primary people metric for [[responsibility-team-management]] and serves as an early warning system for disengagement, burnout, or cultural issues. In a small team where each contributor's motivation directly impacts output quality, keeping team satisfaction high is not a nice-to-have but a business requirement. - -The metric is adapted from the traditional NPS framework: instead of "Would you recommend this product?", the question is "How satisfied are you working on this project this month?" scored from 1-10. - -## How it's tracked - -Collected monthly via a brief anonymous survey sent to all team members (currently [[person-matteo-cellini]] and [[person-paco-furiani]]). The survey includes the 1-10 satisfaction score plus an optional free-text comment field. The monthly average score is logged in the tracking spreadsheet. Free-text comments are reviewed by [[person-luca-rossi]] but not stored in the spreadsheet to maintain anonymity. - -## Targets - -- **Minimum**: 7.0. Below this for any individual month requires a direct conversation to understand the root cause. -- **Target**: 8.0-9.0. This range indicates a healthy, motivated team that feels valued and appropriately challenged. -- **Stretch**: 9.5+. Occasional peaks here after a successful launch or milestone are natural. Sustained 9.5+ may indicate the survey is not being answered honestly. - -## Notes - -- With a team of 2-3 people, anonymity is limited. Acknowledge this openly and emphasize that the goal is to surface issues early, not to evaluate individuals. -- Declining NPS over 2-3 months is a stronger signal than any single month's score. People tolerate short-term stress but erode under sustained pressure. -- Common drivers of low scores: unclear priorities, scope creep, feeling overloaded, lack of recognition. Common drivers of high scores: clear goals, ownership of outcomes, shipping visible work, being heard. -- Track alongside [[measure-task-completion-rate]]. A high completion rate combined with declining NPS suggests the team is hitting targets at the expense of their wellbeing. This is unsustainable. -- Use the monthly score as a conversation starter in 1:1s, not as a judgment. The number is less important than the trend and the discussion it generates. diff --git a/demo-vault-v2/measure.md b/demo-vault-v2/measure.md deleted file mode 100644 index 2a3ab919..00000000 --- a/demo-vault-v2/measure.md +++ /dev/null @@ -1,7 +0,0 @@ ---- -Is A: Type ---- - -# Measure - -A Measure tracks a metric that matters — revenue, subscribers, conversion rate. Measures are linked to Goals or Areas and updated regularly. diff --git a/demo-vault-v2/minimal.md b/demo-vault-v2/minimal.md deleted file mode 100644 index 7d758714..00000000 --- a/demo-vault-v2/minimal.md +++ /dev/null @@ -1,54 +0,0 @@ ---- -Is A: Theme -Description: High contrast, minimal chrome -background: "#FAFAFA" -foreground: "#111111" -card: "#FFFFFF" -popover: "#FFFFFF" -primary: "#000000" -primary-foreground: "#FFFFFF" -secondary: "#F0F0F0" -secondary-foreground: "#111111" -muted: "#F5F5F5" -muted-foreground: "#666666" -accent: "#F0F0F0" -accent-foreground: "#111111" -destructive: "#CC0000" -border: "#E0E0E0" -input: "#E0E0E0" -ring: "#000000" -sidebar: "#F5F5F5" -sidebar-foreground: "#111111" -sidebar-border: "#E0E0E0" -sidebar-accent: "#E8E8E8" -text-primary: "#111111" -text-secondary: "#666666" -text-muted: "#999999" -text-heading: "#111111" -bg-primary: "#FAFAFA" -bg-sidebar: "#F5F5F5" -bg-hover: "#EBEBEB" -bg-hover-subtle: "#F5F5F5" -bg-selected: "#00000014" -border-primary: "#E0E0E0" -accent-blue: "#000000" -accent-green: "#006600" -accent-orange: "#996600" -accent-red: "#CC0000" -accent-purple: "#660099" -accent-yellow: "#996600" -accent-blue-light: "#00000014" -accent-green-light: "#00660014" -accent-purple-light: "#66009914" -accent-red-light: "#CC000014" -accent-yellow-light: "#99660014" -font-family: "'SF Mono', 'Menlo', monospace" -font-size-base: 13px -editor-font-size: 15 -editor-line-height: 1.6 -editor-max-width: 680 ---- - -# Minimal Theme - -High contrast, minimal chrome. Monospace typography throughout. diff --git a/demo-vault-v2/month.md b/demo-vault-v2/month.md deleted file mode 100644 index d7962549..00000000 --- a/demo-vault-v2/month.md +++ /dev/null @@ -1,7 +0,0 @@ ---- -Is A: Type ---- - -# Month - -A Month note captures the focus, highlights, and reflections for a calendar month. It provides a mid-level time horizon between weeks and quarters. diff --git a/demo-vault-v2/my-renamed-note.md b/demo-vault-v2/my-renamed-note.md deleted file mode 100644 index 9c47d8bf..00000000 --- a/demo-vault-v2/my-renamed-note.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled note -type: Note -status: Active ---- - -# My Renamed Note - diff --git a/demo-vault-v2/newsletter-growth-is-about-trust.md b/demo-vault-v2/newsletter-growth-is-about-trust.md deleted file mode 100644 index 50ea7b83..00000000 --- a/demo-vault-v2/newsletter-growth-is-about-trust.md +++ /dev/null @@ -1,28 +0,0 @@ ---- -aliases: ["Newsletter Growth Is About Trust"] -Is A: Evergreen -Topics: ["[[topic-newsletter-growth]]", "[[topic-content-strategy]]"] -Status: Published ---- -# Newsletter Growth Is About Trust -The metric that actually predicts newsletter growth isn't subscriber count, open rate, or even click rate — it's whether readers feel like the author is genuinely on their side. - -Trust compounds. A reader who opens 40 consecutive newsletters before clicking anything is still more valuable than a subscriber who clicks on issue #1 and unsubscribes on issue #3. Long-term readers become advocates, paying customers, and referral sources. - -The implication: optimize for retention before acquisition. A 60% open rate with 1,000 subscribers will grow faster than a 20% open rate with 5,000. - -This is counterintuitive to anyone coming from a growth marketing background, where the playbook is to maximize top-of-funnel and optimize conversion rates. Newsletter growth does not work that way because the product is the relationship, and relationships cannot be scaled through the same mechanisms as e-commerce transactions. Every tactic that inflates subscriber count at the expense of trust — giveaways that attract freebie-seekers, clickbait subject lines that erode credibility, cross-promotions with misaligned audiences — creates a subscriber base that looks healthy in the dashboard but is actually dying in engagement. - -I learned this the hard way with Refactoring. In the early days, I ran a few cross-promotions that brought in thousands of subscribers quickly. The open rate dropped, engagement dropped, and it took months to recover through natural churn. The subscribers who came through organic discovery — word of mouth, social sharing, conference mentions — had 3-4x higher engagement than the ones who came through growth tactics. The lesson was clear: growth that does not come with trust is not growth. It is noise. - -The practical framework I now use is simple. Before any growth initiative, I ask: "Will the people this brings in trust me more or less than my current average reader?" If the answer is less, the initiative is not worth it regardless of the subscriber numbers. This single filter has been more valuable than any growth hack I have ever tried. It keeps the audience aligned with the content, which keeps engagement high, which keeps sponsors happy, which funds the business. - -## Key insight -Trust is the only newsletter metric that compounds. Subscriber count is additive — each new subscriber adds a fixed amount of potential. But trust is multiplicative — each reader who trusts you enough to share your newsletter with a colleague creates a new trust-carrying distribution channel. This is why the most successful newsletters grow slowly at first and then accelerate. They are building the trust infrastructure that eventually turns every engaged reader into a growth channel. The math only works if you protect trust above all other metrics. - -## Related -- [[the-real-job-of-a-newsletter]] — Understanding what job readers hire a newsletter to do is the foundation of trust -- [[b2b-content-is-trust-not-traffic]] — The trust-over-traffic principle applied to B2B content broadly -- [[newsletter-subject-lines]] — Subject lines as a trust signal: accuracy over clickbait -- [[why-b2b-newsletters-work]] — The opt-in dynamic that makes trust possible in the first place -- [[the-compound-effect-in-knowledge-work]] — Trust compounds in the same way that consistent knowledge work does diff --git a/demo-vault-v2/newsletter-subject-lines.md b/demo-vault-v2/newsletter-subject-lines.md deleted file mode 100644 index b1c28ac0..00000000 --- a/demo-vault-v2/newsletter-subject-lines.md +++ /dev/null @@ -1,28 +0,0 @@ ---- -aliases: ["Newsletter Subject Lines Are User Experience"] -Is A: Evergreen -Topics: ["[[topic-newsletter-growth]]", "[[topic-writing]]"] -Status: Published ---- -# Newsletter Subject Lines Are User Experience -A subject line isn't marketing copy — it's the first screen of your product. It sets expectations, attracts the right readers, and repels the wrong ones. - -The biggest mistake I see in newsletter subject lines is optimizing for opens over fit. Clickbait subject lines improve short-term open rates and hurt long-term engagement. Readers who open expecting one thing and find another don't become loyal readers. - -The best subject lines I've used are boring but accurate. They tell you exactly what you're going to read. High-fit readers open, low-fit readers skip, and the engaged list that results is worth more than the inflated raw number. - -Over 200+ issues of Refactoring, I have tested enough subject line approaches to have strong opinions backed by data. The subject lines that perform best on open rate are usually curiosity gaps — "The mistake that cost us $2M" or "Why I fired our best engineer." But when I track downstream metrics — replies, shares, sponsor clicks, unsubscribes — these high-open-rate subject lines consistently underperform descriptive ones. The readers they attract are looking for drama, not insight. They open, skim, and either unsubscribe or become ghost subscribers who never engage again. - -The subject line I am most proud of was something like "How we restructured our engineering team around product outcomes." It had a below-average open rate but generated more replies, more forwards, and more sponsor clicks than any issue that quarter. The readers who opened it were exactly the right readers — engineering leaders dealing with that exact problem — and they engaged deeply because the subject line told them this was for them. That precision in audience selection is worth far more than raw opens. - -There is also a compounding effect to honest subject lines. Readers learn to trust that your subject line accurately represents the content. This trust becomes a pattern: they see your name in their inbox, read the subject line, and make a quick decision based on whether the topic is relevant today. Some weeks they skip, and that is fine. But they never feel tricked, so they never unsubscribe out of irritation. Over 52 weeks, this trust-based pattern produces far more total engaged opens than the clickbait approach, even though any single issue might have a lower open rate. - -## Key insight -Subject lines should be designed as a filtering mechanism, not an attraction mechanism. The goal is not to maximize opens — it is to maximize the overlap between people who open and people who will find the content genuinely useful. This reframing changes everything about how you write them. Instead of asking "What will make someone click?" you ask "What will help the right person decide this is for them?" The result is lower vanity metrics and higher real engagement, which is the only thing that matters for a sustainable newsletter business. - -## Related -- [[newsletter-growth-is-about-trust]] — Subject line honesty is a direct trust-building mechanism -- [[the-real-job-of-a-newsletter]] — Subject lines should communicate the job the issue will do for the reader -- [[writing-for-clarity-vs-writing-for-credit]] — Clarity over cleverness applies to subject lines as much as to body copy -- [[why-b2b-newsletters-work]] — The opt-in dynamic makes honest subject lines especially important in B2B -- [[procedure-weekly-newsletter]] — The practical workflow for writing and testing subject lines diff --git a/demo-vault-v2/note-atomic-habits.md b/demo-vault-v2/note-atomic-habits.md deleted file mode 100644 index ee6ef33c..00000000 --- a/demo-vault-v2/note-atomic-habits.md +++ /dev/null @@ -1,43 +0,0 @@ ---- -aliases: ["Atomic Habits"] -Is A: Note -Author: "James Clear" -Topics: ["[[topic-productivity-systems]]"] -URL: "https://example.com/atomic-habits" ---- -# Atomic Habits -*James Clear* - -Clear's central argument is that outcomes are a lagging indicator of habits, and habits are a lagging indicator of identity. Rather than setting goals and hoping willpower carries you there, the book advocates for designing systems that make good behavior automatic and bad behavior difficult. The four laws of behavior change -- make it obvious, attractive, easy, and satisfying -- provide a practical framework that applies far beyond personal productivity. For anyone running a content business, the implication is clear: consistency in publishing, outreach, and learning is not about motivation but about environment design and identity reinforcement. - -The most immediately useful concept is the two-minute rule: when starting a new habit, scale it down until it takes less than two minutes. This sounds trivial, but it addresses the real bottleneck in habit formation, which is simply showing up. Once you establish the routine of sitting down to write every morning, increasing the duration is comparatively easy. The same principle applies to reading, exercise, and any creative practice. Clear also emphasizes implementation intentions ("I will [behavior] at [time] in [location]"), which I have found remarkably effective for protecting deep work blocks against the entropy of a busy schedule. - -What makes this book especially relevant for indie founders is the compounding metaphor. Clear argues that 1% improvements compound just like interest, and that the difference between someone who writes daily and someone who writes occasionally becomes enormous over a year or two. This maps directly to newsletter growth, audience building, and skill development. The book does not dwell on entrepreneurship specifically, but every principle applies: your newsletter output, your product development cadence, and your learning practice are all habit systems, not one-time efforts. - -## Key takeaways - -- Systems beat goals: focus on the process rather than the outcome, and the outcomes will follow -- Identity-based habits are stickier than outcome-based habits -- ask "who do I want to become?" not "what do I want to achieve?" -- The two-minute rule: reduce any new habit to a trivially small starting version to overcome activation energy -- Implementation intentions ("I will write at 7am at my desk") dramatically increase follow-through -- Environment design matters more than willpower: make good habits obvious and convenient, bad habits invisible and inconvenient -- Habit stacking lets you attach new behaviors to existing routines, reducing the cognitive load of building new systems -- The plateau of latent potential explains why most people quit: results are delayed, but the work compounds beneath the surface - -## How I apply this - -- I use habit stacking to anchor my morning writing session to my coffee routine. The trigger is automatic, which means I rarely have to decide whether to write -- I just do it after pouring coffee. This has been the single biggest driver of my publishing consistency. -- I applied the two-minute rule to my reading habit. Instead of committing to "read for an hour," I committed to "open a book and read one page." Within two weeks, I was naturally reading 30-40 minutes per session because the hard part was never the reading itself -- it was starting. -- I redesigned my phone home screen using Clear's environment design principles: all social media apps are off the first screen, and my Kindle app and note-taking tools are front and center. This small change reduced my mindless scrolling by roughly half. - -## Related - -- [[the-compound-effect-in-knowledge-work]] -- [[on-consistency-in-creative-work]] -- [[sleeping-more-is-a-superpower]] -- [[training-load-and-knowledge-work]] -- [[note-deep-work]] -- [[note-the-willpower-instinct]] -- [[note-grit]] -- [[topic-productivity-systems]] -- [[procedure-weekly-reading-session]] diff --git a/demo-vault-v2/note-born-to-run.md b/demo-vault-v2/note-born-to-run.md deleted file mode 100644 index 8b097d77..00000000 --- a/demo-vault-v2/note-born-to-run.md +++ /dev/null @@ -1,42 +0,0 @@ ---- -aliases: ["Born to Run"] -Is A: Note -Author: "Christopher McDougall" -Topics: ["[[topic-running]]"] -URL: "https://example.com/born-to-run" ---- -# Born to Run -*Christopher McDougall* - -McDougall's investigation into the Tarahumara ultrarunners of Mexico's Copper Canyons is part anthropology, part adventure story, and part argument against the modern running shoe industry. The core thesis is that humans evolved to run long distances and that much of what we consider "running injury" is actually a product of overengineered footwear and poor form. The Tarahumara run extraordinary distances in thin sandals, with joy and without the chronic injuries that plague Western recreational runners. The book makes a compelling case that we have been overthinking movement and that simplicity in training often outperforms complexity. - -What resonated most with me was not the barefoot running debate but the deeper point about intrinsic motivation and play. The Tarahumara do not run to hit PRs or post Strava segments -- they run because running is woven into their culture and their sense of community. McDougall contrasts this with the grim, data-obsessed approach many Western athletes take, and the comparison is unflattering. As someone who tracks every cycling metric obsessively, this was a useful corrective. There is a version of endurance sport that is about joy and connection rather than optimization, and finding that balance matters for longevity in any pursuit. - -The book also introduced me to the idea that the human body is not fragile but remarkably adaptable when given the right conditions. This principle extends well beyond running. In building a newsletter or a content business, the instinct is often to add more tools, more structure, more process. But sometimes the answer is to strip things back to fundamentals: write clearly, publish consistently, connect with readers directly. The Tarahumara do not have coaches or recovery protocols. They just run, a lot, and they have been doing it for centuries. - -## Key takeaways - -- Humans evolved as persistence hunters -- long-distance running is not an aberration but a core human capability -- Modern running shoes may cause more injuries than they prevent by encouraging heel striking and weakening foot muscles -- The Tarahumara's longevity in running comes from community, joy, and simplicity rather than technology and optimization -- Intrinsic motivation (running for the love of it) produces better long-term outcomes than extrinsic motivation (PRs, races, metrics) -- Overcomplication is the enemy of consistency -- in running and in most other pursuits -- The best training program is the one you enjoy enough to sustain for decades - -## How I apply this - -- After reading this, I started incorporating one "unstructured" ride per week into my cycling schedule -- no power targets, no intervals, just riding for enjoyment. It has improved my overall consistency because I actually look forward to those rides. -- I use the Tarahumara principle when I feel the urge to add more tools or systems to my workflow: sometimes the answer is less infrastructure, not more. My best newsletter editions often come from simple prompts, not elaborate content calendars. -- The book reinforced my belief that longevity matters more than peak performance. I would rather publish a solid newsletter every week for ten years than burn out chasing viral growth for six months. - -## Related - -- [[cycling-teaches-patience]] -- [[training-load-and-knowledge-work]] -- [[on-founder-energy-management]] -- [[on-consistency-in-creative-work]] -- [[note-atomic-habits]] -- [[note-grit]] -- [[note-the-art-of-learning]] -- [[topic-cycling-training]] -- [[topic-sleep-recovery]] diff --git a/demo-vault-v2/note-building-a-second-brain.md b/demo-vault-v2/note-building-a-second-brain.md deleted file mode 100644 index 7ae71a2d..00000000 --- a/demo-vault-v2/note-building-a-second-brain.md +++ /dev/null @@ -1,43 +0,0 @@ ---- -aliases: ["Building a Second Brain"] -Is A: Note -Author: "Tiago Forte" -Topics: ["[[topic-productivity-systems]]"] -URL: "https://example.com/second-brain" ---- -# Building a Second Brain -*Tiago Forte* - -Forte's BASB methodology centers on the CODE framework: Capture interesting ideas, Organize them for actionability, Distill notes down to their essence, and Express what you know through creative output. The underlying philosophy is that our brains are for having ideas, not storing them, and that an external system (a "second brain") lets us offload the storage function so we can focus on the thinking function. For anyone managing a content business, this is directly relevant -- a well-maintained knowledge system reduces the friction between learning and publishing, making it easier to turn reading and research into newsletter content. - -Where I diverge from Forte is his emphasis on organizing by projects. The PARA system (Projects, Areas, Resources, Archive) is practical for task management, but it creates an inherently transient structure. When a project ends, the notes associated with it become orphans. For a knowledge worker whose primary output is writing and thinking, I find an evergreen-notes approach more durable: notes organized by concept rather than by project, linked associatively rather than filed hierarchically. That said, Forte's emphasis on progressive summarization -- layering highlights on top of highlights to distill notes over time -- is genuinely useful regardless of your organizational scheme. - -The most actionable insight from the book is the idea of "intermediate packets": discrete, reusable chunks of work (outlines, research summaries, drafted paragraphs) that can be assembled into larger outputs. This maps perfectly to how I write my newsletter. Rather than starting each edition from scratch, I draw on a library of notes, highlights, and half-formed ideas that I have accumulated throughout the week. The intermediate packet concept also helps with the psychological burden of creating: you are never starting from zero, only assembling and refining existing pieces. - -## Key takeaways - -- The CODE framework (Capture, Organize, Distill, Express) provides a clear pipeline from information consumption to creative output -- Progressive summarization (layered highlighting) helps you distill notes without losing context -- Intermediate packets -- reusable chunks of work -- dramatically reduce the cost of producing new content -- PARA (Projects, Areas, Resources, Archive) is a practical organizational system, though it biases toward short-term project work over long-term knowledge building -- Your second brain should be organized for actionability, not for completeness -- store what you will use, not everything you encounter -- The value of a note system is realized only when you express what you know -- capturing without creating is just hoarding - -## How I apply this - -- My vault is essentially a second brain, but I use an evergreen-notes structure rather than PARA. Each concept gets its own note, linked to related ideas, and I revisit and refine them regularly. This gives me a durable knowledge base that survives project changes. -- I practice progressive summarization on book highlights: first pass captures everything interesting, second pass bolds the key points, third pass extracts the core insight into my own words. This is how most of my book notes end up in this vault. -- The intermediate packets idea directly shapes my newsletter workflow. Throughout the week, I capture observations, half-formed arguments, and interesting data points. By the time I sit down to write on Thursday, I am assembling rather than inventing. - -## Related - -- [[knowledge-management-is-not-filing]] -- [[the-compound-effect-in-knowledge-work]] -- [[reading-more-by-reading-better]] -- [[writing-for-clarity-vs-writing-for-credit]] -- [[note-on-writing-well]] -- [[note-deep-work]] -- [[note-show-your-work]] -- [[topic-productivity-systems]] -- [[procedure-evergreen-note-writing]] -- [[procedure-weekly-reading-session]] diff --git a/demo-vault-v2/note-deep-work.md b/demo-vault-v2/note-deep-work.md deleted file mode 100644 index 03ee33c3..00000000 --- a/demo-vault-v2/note-deep-work.md +++ /dev/null @@ -1,44 +0,0 @@ ---- -aliases: ["Deep Work"] -Is A: Note -Author: "Cal Newport" -Topics: ["[[topic-productivity-systems]]"] -URL: "https://example.com/deep-work" ---- -# Deep Work -*Cal Newport* - -Newport defines deep work as professional activities performed in a state of distraction-free concentration that push your cognitive capabilities to their limit. These efforts create new value, improve your skill, and are hard to replicate. Shallow work, by contrast, is logistical-style work that can be performed while distracted and tends not to create much new value. The thesis is simple but powerful: in an economy increasingly dominated by knowledge work, the ability to perform deep work is becoming simultaneously more rare and more valuable. Those who cultivate this ability will thrive; those who do not will fall behind. - -For someone running a newsletter and building software products, this framework is immediately applicable. Writing a long-form newsletter edition is deep work. Responding to emails, scheduling social posts, and tweaking website layouts is shallow work. The danger is that shallow work feels productive because it generates visible activity, while deep work often feels uncomfortable because it requires sustained concentration on hard problems. Newport argues that most knowledge workers default to shallow work because it is easier and because their organizations do not protect deep work time. As an indie founder without a boss to impose structure, this is entirely your own responsibility. - -The book offers several practical strategies: time blocking, the shutdown ritual, quitting social media (or at least drastically reducing it), and embracing boredom. The most impactful for me was the rhythmic philosophy of deep work scheduling -- designating specific blocks for deep work and defending them ruthlessly. Newport also makes a compelling case that the ability to concentrate deeply is a skill that must be trained, not a talent you either have or lack. This connects directly to the ideas in Atomic Habits about building systems and in The Art of Learning about deliberate practice. - -## Key takeaways - -- Deep work is rare, valuable, and meaningful -- it is the skill that produces your best output as a knowledge worker -- Shallow work expands to fill available time unless you deliberately constrain it through scheduling and boundaries -- The ability to concentrate without distraction is a trainable skill, not an innate talent -- Time blocking (scheduling every minute of your day) is the most effective way to protect deep work from the pull of shallow obligations -- A shutdown ritual at the end of the work day helps you mentally release from work, which paradoxically improves your deep work capacity the next day -- Embracing boredom trains your attention muscles -- if you reach for your phone every time you are understimulated, you weaken your ability to focus -- The four disciplines of execution (focus on the wildly important, act on lead measures, keep a compelling scoreboard, create a cadence of accountability) provide a useful implementation framework - -## How I apply this - -- I block my mornings (7am to 11am) exclusively for deep work: writing newsletter content, coding on product features, or working through complex strategic problems. No email, no Slack, no meetings. This is non-negotiable and has been the single biggest productivity lever in my work life. -- I use a shutdown ritual at the end of each work day: review my task list, write tomorrow's plan, and say "shutdown complete." This sounds silly but it genuinely prevents my mind from continuing to churn on work problems during evening and rest time. -- I have removed all social media apps from my phone and check Twitter and LinkedIn only from my laptop during designated shallow work blocks. The reduction in context switching has been noticeable in both my writing quality and my ability to sustain focus during coding sessions. - -## Related - -- [[on-consistency-in-creative-work]] -- [[on-founder-energy-management]] -- [[the-compound-effect-in-knowledge-work]] -- [[sleeping-more-is-a-superpower]] -- [[note-atomic-habits]] -- [[note-makers-schedule-managers]] -- [[note-essentialism]] -- [[note-so-good-they-cant-ignore]] -- [[topic-productivity-systems]] -- [[topic-writing]] diff --git a/demo-vault-v2/note-deprecated-workflow.md b/demo-vault-v2/note-deprecated-workflow.md deleted file mode 100644 index acee3619..00000000 --- a/demo-vault-v2/note-deprecated-workflow.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -Is A: Note -trashed: true -trashed_at: 2026-02-21 -Topics: ["[[topic-productivity-systems]]"] ---- -# Deprecated Workflow - -An old workflow for managing sponsorship outreach that was replaced by the new CRM-based process. Keeping in trash in case any of the templates are useful later. - -## Old Process -1. Find potential sponsors via LinkedIn -2. Send cold email using template A -3. Follow up after 3 days -4. Schedule call if interested - -## Why Deprecated -The manual process was too slow and error-prone. Switched to automated pipeline with CRM integration. diff --git a/demo-vault-v2/note-essentialism.md b/demo-vault-v2/note-essentialism.md deleted file mode 100644 index f87ac33a..00000000 --- a/demo-vault-v2/note-essentialism.md +++ /dev/null @@ -1,43 +0,0 @@ ---- -aliases: ["Essentialism"] -Is A: Note -Author: "Greg McKeown" -Topics: ["[[topic-productivity-systems]]"] -URL: "https://example.com/essentialism" ---- -# Essentialism -*Greg McKeown* - -McKeown's thesis is deceptively simple: if you do not prioritize your life, someone else will. Essentialism is not about getting more done in less time -- it is about getting only the right things done. The book draws a sharp distinction between the "non-essentialist" who tries to do everything and makes a millimeter of progress in a million directions, and the "essentialist" who makes a focused effort on the few things that truly matter and achieves significant results. For indie founders, who face an almost unlimited number of things they could be doing at any given moment, this is a critical mindset shift. - -The most useful framework in the book is the idea of a strict "hell yes or no" filter for commitments. If something is not a clear, enthusiastic yes, it is a no. This sounds extreme, but McKeown argues persuasively that our default mode is to say yes to too many things out of social pressure, FOMO, or a misguided sense of obligation. Every yes to a mediocre opportunity is an implicit no to something that could be great. Applied to a content business, this means being ruthless about which projects, partnerships, sponsorships, and features deserve your time, and saying no gracefully to everything else. - -McKeown also makes an important distinction between being busy and being productive. Many founders wear busyness as a badge of honor, but busyness without direction is just motion without progress. The essentialist approach is to step back regularly, evaluate what is actually moving the needle, and have the discipline to eliminate or delegate everything else. This requires a kind of courage -- the courage to disappoint people, to leave opportunities on the table, and to trust that less really can be more. - -## Key takeaways - -- "If it's not a hell yes, it's a no" -- apply a strict filter to every commitment, project, and opportunity -- The non-essentialist tries to do everything; the essentialist does fewer things but does them exceptionally well -- Saying no is a skill that must be practiced -- most of us default to yes out of social pressure or fear of missing out -- Being busy is not the same as being productive; busyness without strategic direction is just motion -- Trade-offs are real and unavoidable -- pretending you can "have it all" leads to mediocrity in everything -- Regular reflection and pruning of commitments is essential to prevent scope creep in your life and work -- Protecting space for thinking and planning is itself a productive activity, not a luxury - -## How I apply this - -- Every quarter, I review all my active commitments (newsletter, product work, sponsorships, side projects, social obligations) and explicitly cut anything that is not clearly contributing to my top two priorities. This pruning exercise is uncomfortable but consistently frees up 5-10 hours per week. -- I use the "hell yes or no" filter for sponsorship inquiries and collaboration requests. Before reading this book, I would accept almost any reasonable offer. Now I only work with sponsors whose products I genuinely use and believe in, which has improved both my credibility and my own satisfaction. -- I schedule a weekly "think day" on Fridays where I do no execution work -- only reflection, planning, and strategic thinking. McKeown convinced me that this is not wasted time but the most leveraged activity in my week. - -## Related - -- [[on-founder-energy-management]] -- [[on-consistency-in-creative-work]] -- [[small-teams-scale-through-systems]] -- [[the-real-job-of-a-newsletter]] -- [[note-deep-work]] -- [[note-the-effective-executive]] -- [[note-makers-schedule-managers]] -- [[topic-productivity-systems]] -- [[topic-content-strategy]] diff --git a/demo-vault-v2/note-good-strategy-bad-strategy.md b/demo-vault-v2/note-good-strategy-bad-strategy.md deleted file mode 100644 index c739249e..00000000 --- a/demo-vault-v2/note-good-strategy-bad-strategy.md +++ /dev/null @@ -1,44 +0,0 @@ ---- -aliases: ["Good Strategy Bad Strategy"] -Is A: Note -Author: "Richard Rumelt" -Topics: ["[[topic-saas-business]]"] -URL: "https://example.com/good-strategy" ---- -# Good Strategy Bad Strategy -*Richard Rumelt* - -Rumelt's core argument is that most of what passes for strategy in organizations is not strategy at all -- it is a mixture of vague aspirations, financial targets, and motivational slogans. Real strategy, he argues, has a specific structure he calls "the kernel": a diagnosis of the challenge, a guiding policy for dealing with the challenge, and a set of coherent actions designed to carry out the guiding policy. This simple framework is extraordinarily clarifying. When you force yourself to articulate the kernel of your strategy, you quickly discover whether you actually have one or are just hoping things work out. - -The diagnosis component is particularly valuable. Rumelt insists that good strategy begins with an honest, clear-eyed assessment of the situation -- not with goals or vision statements. What is the actual challenge you face? What are the constraints? Where is the leverage? For an indie founder running a newsletter and content business, this means being honest about things like: your audience is small, your time is limited, you compete for attention with everyone from the New York Times to random threads on Twitter. Only by diagnosing the real challenge can you design a guiding policy that exploits your specific advantages (depth of expertise, personal voice, niche focus) rather than trying to compete on dimensions where you will lose. - -The distinction between good strategy and bad strategy has stuck with me as a daily filter. Bad strategy is fluffy, avoids hard choices, and tries to please everyone. Good strategy identifies the critical challenge, makes deliberate trade-offs, and focuses resources where they will have the most impact. This maps perfectly to product decisions, content strategy, and even personal time management. Every time I catch myself writing a "strategy" that is really just a wish list, I hear Rumelt's voice asking: "But what is the kernel?" - -## Key takeaways - -- The kernel of good strategy: diagnosis (what is the challenge?), guiding policy (how will you approach it?), and coherent actions (what specifically will you do?) -- Most "strategy" is actually bad strategy: vague goals, buzzwords, and a refusal to make hard choices -- Good strategy requires saying no to many things so you can focus resources on the few things that matter -- The diagnosis is the most underrated step -- without an honest assessment of the challenge, no strategy can work -- Proximate objectives (achievable near-term goals) are more useful than distant aspirations for driving action -- Leverage is the key strategic concept: find the point where focused effort produces disproportionate results -- Strategic thinking is a skill that improves with practice, not a talent reserved for executives - -## How I apply this - -- Before any major initiative (product launch, content pivot, new revenue stream), I force myself to write a one-page strategy kernel: what is the diagnosis, what is the guiding policy, and what are the three coherent actions? If I cannot fill in all three, I do not proceed. This has prevented me from chasing several shiny objects that had no real strategic basis. -- I use Rumelt's "bad strategy" checklist as a filter when evaluating my own plans. If my strategy document contains phrases like "leverage synergies" or "become the leading platform," I know I am fooling myself and need to get more specific. -- The proximate objectives concept has improved my quarterly planning. Instead of setting ambitious annual goals, I focus on what is the most important thing I can accomplish in the next 90 days, given current constraints. This has made my planning more realistic and my execution more focused. - -## Related - -- [[small-teams-scale-through-systems]] -- [[the-saas-metric-that-matters]] -- [[b2b-content-is-trust-not-traffic]] -- [[the-real-job-of-a-newsletter]] -- [[note-zero-to-one]] -- [[note-the-lean-startup]] -- [[note-essentialism]] -- [[note-the-effective-executive]] -- [[topic-saas-business]] -- [[topic-content-strategy]] diff --git a/demo-vault-v2/note-grit.md b/demo-vault-v2/note-grit.md deleted file mode 100644 index 4800d411..00000000 --- a/demo-vault-v2/note-grit.md +++ /dev/null @@ -1,44 +0,0 @@ ---- -aliases: ["Grit"] -Is A: Note -Author: "Angela Duckworth" -Topics: ["[[topic-mental-health]]"] -URL: "https://example.com/grit" ---- -# Grit -*Angela Duckworth* - -Duckworth defines grit as the combination of passion and perseverance for long-term goals. Her research shows that grit is a better predictor of success than talent, IQ, or socioeconomic background in contexts ranging from West Point cadets to National Spelling Bee finalists. The key insight is not that hard work matters -- everyone knows that -- but that the specific combination of sustained interest (passion) and sustained effort (perseverance) over years is what separates high achievers from the rest. Talent helps, but without grit, talent is just unmet potential. - -For anyone running an indie business, the implication is both encouraging and sobering. Encouraging because it means you do not need to be the smartest person in the room to build something meaningful. Sobering because it means there are no shortcuts: the path to a successful newsletter, a profitable SaaS product, or a respected personal brand requires years of consistent effort. Duckworth's research on "grit paragons" -- people who have achieved extraordinary things through sustained effort -- consistently reveals that they found their work deeply meaningful, not just lucrative. This connects to the idea that intrinsic motivation is more durable than extrinsic motivation, which is critical for solo founders who lack external accountability. - -The book also explores how grit can be cultivated rather than being a fixed trait. Duckworth identifies four psychological assets of gritty people: interest (you have to find the work fascinating), practice (deliberate practice specifically), purpose (the work must connect to something beyond yourself), and hope (not wishful thinking, but the belief that your efforts can improve things). This framework is useful for self-diagnosis: if your motivation is flagging, which of these four pillars is weak? Often the answer reveals a specific, addressable problem rather than a vague sense of burnout. - -## Key takeaways - -- Grit (passion + perseverance) is a stronger predictor of success than talent alone in most complex, long-term endeavors -- Passion in this context means sustained interest over years, not momentary enthusiasm -- it is more about consistency than intensity -- Deliberate practice is the mechanism through which grit produces results: working at the edge of your ability with feedback -- The four pillars of grit -- interest, practice, purpose, and hope -- can each be developed deliberately -- "Grit paragons" view setbacks as learning opportunities rather than evidence of inadequacy -- A "hard thing rule" can build grit: commit to one hard thing that requires daily practice, and do not quit during a natural cycle -- Effort counts twice: talent multiplied by effort equals skill, and skill multiplied by effort equals achievement - -## How I apply this - -- I use Duckworth's four-pillar framework as a diagnostic when I feel motivation dropping. Last quarter, I realized my flagging energy around the newsletter was not about burnout but about a weak "purpose" pillar -- I had lost sight of why I was writing. Reconnecting with reader feedback and impact stories restored my drive. -- I adopted the "hard thing rule" for both cycling and writing: I committed to not quitting either during a low period. The rule forces me to push through the inevitable troughs, and I have found that motivation often returns once you survive the dip. -- The distinction between passion as sustained interest versus fleeting excitement has changed how I evaluate new project ideas. I now ask "will I still care about this in two years?" rather than "does this excite me right now?" - -## Related - -- [[on-consistency-in-creative-work]] -- [[the-two-types-of-hard]] -- [[cycling-teaches-patience]] -- [[on-founder-energy-management]] -- [[note-atomic-habits]] -- [[note-so-good-they-cant-ignore]] -- [[note-the-art-of-learning]] -- [[note-man-search-for-meaning]] -- [[topic-mental-health]] -- [[topic-cycling-training]] diff --git a/demo-vault-v2/note-how-minds-change.md b/demo-vault-v2/note-how-minds-change.md deleted file mode 100644 index 18c0936f..00000000 --- a/demo-vault-v2/note-how-minds-change.md +++ /dev/null @@ -1,43 +0,0 @@ ---- -aliases: ["How Minds Change"] -Is A: Note -Author: "David McRaney" -Topics: ["[[topic-productivity-systems]]"] -URL: "https://example.com/how-minds-change" ---- -# How Minds Change -*David McRaney* - -McRaney explores the science of belief change -- why people hold the beliefs they do, why facts alone rarely change minds, and what techniques actually work when you want to help someone see things differently. The book covers deep canvassing (a technique where volunteers have extended, empathetic conversations with strangers), motivational interviewing, and the psychology of reasoning. The central finding is counterintuitive: the most effective way to change someone's mind is not to argue with them but to ask them to explain their reasoning, listen without judgment, and let them discover the gaps in their own logic. - -This has profound implications for anyone in the content business. If you write a newsletter or create educational content, your instinct might be to present your strongest arguments and hope the logic speaks for itself. But McRaney shows that this approach often backfires, triggering the backfire effect where people dig in harder when confronted with contradictory evidence. Instead, the most persuasive content creates space for the reader to think through the problem alongside you. This is why "thinking out loud" writing -- where you show your reasoning process rather than just your conclusions -- tends to be more influential than polished arguments. - -The SIFT framework (Stop, Investigate the source, Find better coverage, Trace claims) is also valuable as a personal epistemic tool. In an age of information overload, the ability to quickly evaluate claims before incorporating them into your worldview is essential. McRaney makes the case that intellectual humility -- the willingness to update your beliefs when presented with good evidence -- is not a weakness but a cognitive superpower. For a founder making decisions under uncertainty every day, this is a critical skill. - -## Key takeaways - -- Facts alone rarely change minds -- belief change happens through empathy, questioning, and self-reflection, not through argument -- Deep canvassing works by asking people to explain their reasoning and genuinely listening, which lets them discover inconsistencies on their own -- The backfire effect means that direct contradiction can actually strengthen the beliefs you are trying to change -- Motivational interviewing -- a non-judgmental, collaborative conversation technique -- is effective in professional, personal, and content contexts -- SIFT (Stop, Investigate, Find better coverage, Trace claims) is a practical framework for evaluating information quality -- People change their minds when they feel safe and respected, not when they feel attacked or condescended to -- Showing your reasoning process ("thinking out loud") is more persuasive than presenting polished conclusions - -## How I apply this - -- My newsletter writing style shifted after reading this book. Instead of presenting conclusions, I now walk readers through my reasoning process, including doubts and counterarguments. Engagement metrics improved noticeably -- readers respond more when they feel invited into the thinking rather than lectured at. -- In sponsorship negotiations and business conversations, I use motivational interviewing techniques: asking open-ended questions, reflecting back what I hear, and avoiding the urge to argue. This has made difficult conversations far more productive. -- I apply SIFT to every claim I consider including in my newsletter. If I cannot trace a statistic to a credible primary source, I do not use it. This has cost me some compelling anecdotes but built long-term trust with my audience. - -## Related - -- [[ai-wont-replace-thinking]] -- [[writing-for-clarity-vs-writing-for-credit]] -- [[b2b-content-is-trust-not-traffic]] -- [[newsletter-growth-is-about-trust]] -- [[note-thinking-fast-and-slow]] -- [[note-never-split-difference]] -- [[note-the-courage-to-be-disliked]] -- [[topic-content-strategy]] -- [[topic-writing]] diff --git a/demo-vault-v2/note-makers-schedule-managers.md b/demo-vault-v2/note-makers-schedule-managers.md deleted file mode 100644 index 501a0c4c..00000000 --- a/demo-vault-v2/note-makers-schedule-managers.md +++ /dev/null @@ -1,43 +0,0 @@ ---- -aliases: ["Maker's Schedule Manager's Schedule"] -Is A: Note -Author: "Paul Graham" -Topics: ["[[topic-productivity-systems]]"] -URL: "https://example.com/makers-schedule" ---- -# Maker's Schedule Manager's Schedule -*Paul Graham* - -Graham's essay (it is more essay than book, but its influence warrants a full note) articulates a distinction that every founder-creator instinctively feels but struggles to name. Makers -- programmers, writers, designers -- need long, uninterrupted blocks of time to do their best work. A single meeting in the middle of an afternoon can destroy an entire half-day of productive output, because the maker's mind needs time to load context, reach flow state, and produce meaningful work. Managers, by contrast, operate on an hourly schedule where meetings are the work and switching between topics is normal and expected. - -The conflict arises when you are both maker and manager, which is the default state for any indie founder. You need deep blocks for writing newsletter content and coding product features, but you also need to handle sponsor communications, answer reader emails, coordinate with freelancers, and make strategic decisions. Graham's insight is that the solution is not better time management -- it is schedule segregation. You need to designate certain days or blocks as maker time and others as manager time, and defend the boundary fiercely. A single "quick call" dropped into a maker block is not a 30-minute cost; it is a half-day cost. - -What makes this essay particularly relevant for the solo operator is that no one else will protect your maker time. In a company, a good manager might shield their engineers from meeting creep. When you work alone, you must build that protection yourself through calendar discipline, communication norms (e.g., "I respond to email between 2pm and 3pm"), and the willingness to disappoint people who want your time on their schedule. - -## Key takeaways - -- Makers need long, uninterrupted blocks (4+ hours) to do their best work; managers operate effectively in 1-hour chunks -- A single meeting in the middle of a maker block destroys the entire block, not just the meeting duration -- The cost of context switching is highest for creative and technical work -- writing, coding, designing -- Schedule segregation (maker days vs. manager days, or maker mornings vs. manager afternoons) is the most effective solution -- As a solo founder, you are responsible for protecting your own maker time -- no one else will do it for you -- Communication norms (batch email, async-first, office hours) are the infrastructure that makes maker time possible -- The "speculative meeting" (meetings that might be useful but have no clear agenda) is the maker's worst enemy - -## How I apply this - -- My week is split: Monday through Wednesday mornings are maker time (writing, coding, deep thinking), and Wednesday afternoon through Friday is manager time (calls, emails, admin, planning). This structure has been in place for over a year and is the single most important scheduling decision I have made. -- I tell sponsors and collaborators that I am available for calls only on Wednesday afternoon, Thursday, or Friday. Initially this felt restrictive, but no one has ever pushed back meaningfully -- and it protects 60% of my week for deep work. -- I batch all email and Slack responses into two daily windows (noon and 4pm). This was uncomfortable at first because I worried about appearing unresponsive, but response time expectations are usually self-imposed rather than real. - -## Related - -- [[on-founder-energy-management]] -- [[on-consistency-in-creative-work]] -- [[small-teams-scale-through-systems]] -- [[the-compound-effect-in-knowledge-work]] -- [[note-deep-work]] -- [[note-essentialism]] -- [[note-the-effective-executive]] -- [[topic-productivity-systems]] -- [[person-luca-rossi]] diff --git a/demo-vault-v2/note-man-search-for-meaning.md b/demo-vault-v2/note-man-search-for-meaning.md deleted file mode 100644 index 99e55711..00000000 --- a/demo-vault-v2/note-man-search-for-meaning.md +++ /dev/null @@ -1,43 +0,0 @@ ---- -aliases: ["Man's Search for Meaning"] -Is A: Note -Author: "Viktor Frankl" -Topics: ["[[topic-mental-health]]"] -URL: "https://example.com/frankl" ---- -# Man's Search for Meaning -*Viktor Frankl* - -Frankl's account of surviving the Nazi concentration camps and his subsequent development of logotherapy is one of the most important books I have ever read. The core thesis is that the primary human drive is not pleasure (Freud) or power (Adler) but meaning. Even in the most extreme suffering imaginable, those who could find a sense of purpose -- a reason to endure -- were more likely to survive. Frankl quotes Nietzsche: "He who has a why to live can bear almost any how." Logotherapy, the therapeutic approach Frankl built from this insight, holds that meaning can be found in three ways: through work (creating something), through love (encountering someone), or through suffering (finding purpose in unavoidable pain). - -The implications extend far beyond extreme circumstances. For anyone building something -- a business, a creative practice, a career -- Frankl's framework is a powerful antidote to the nihilism and burnout that can creep in during difficult periods. When the newsletter is not growing, when the product launch flops, when you question why you are doing any of this, the answer is not to optimize harder or hustle more. The answer is to reconnect with the meaning behind the work. Why does this matter? Who does it help? What would be lost if you stopped? These are not soft questions; they are the foundation of sustainable motivation. - -Frankl also introduces the concept of the "existential vacuum" -- the feeling of emptiness that comes from a life without meaning, often masked by busyness, consumption, or distraction. This resonates in the context of the modern tech/startup world, where it is easy to chase metrics, revenue, and growth as ends in themselves. The book is a reminder that those are means, not ends, and that the founders who last are the ones who have connected their work to something they genuinely care about beyond the numbers. - -## Key takeaways - -- Meaning is the primary human motivation -- more fundamental than pleasure or power -- Meaning can be found through work (creation), love (connection), or attitude toward suffering (finding purpose in pain) -- The "existential vacuum" -- emptiness masked by busyness -- is a common modern condition that leads to burnout and depression -- You cannot always control your circumstances, but you can always choose your attitude toward them -- this is the "last of the human freedoms" -- Purpose is not something you find once; it is something you actively construct and reconstruct throughout your life -- Hyper-focusing on outcomes (metrics, revenue, followers) without connecting to deeper meaning leads to fragile motivation that collapses under pressure -- Suffering without meaning is unbearable; suffering with meaning is transformative - -## How I apply this - -- When I feel the pull of burnout, I return to Frankl's question: "What is the meaning of this work?" For me, the answer is that my newsletter helps engineers and founders make better decisions and feel less alone in their struggles. Reconnecting with reader stories and feedback is my version of Frankl's "encountering someone." -- I use the three sources of meaning as a diagnostic for life balance. If I am over-indexed on work (creation) and neglecting love (relationships) and attitude (reflection), my overall sense of purpose suffers. This framework helps me notice imbalance before it becomes a crisis. -- The "last of the human freedoms" idea -- choosing your attitude -- has become a practical tool for dealing with setbacks. A failed product launch is not a verdict on my worth; it is an opportunity to learn. This reframing is not toxic positivity but a genuine shift in perspective that Frankl earned through the most extreme circumstances imaginable. - -## Related - -- [[on-founder-energy-management]] -- [[the-two-types-of-hard]] -- [[on-consistency-in-creative-work]] -- [[sleeping-more-is-a-superpower]] -- [[note-the-obstacle-is-the-way]] -- [[note-on-the-shortness-of-life]] -- [[note-the-courage-to-be-disliked]] -- [[note-grit]] -- [[topic-mental-health]] diff --git a/demo-vault-v2/note-never-split-difference.md b/demo-vault-v2/note-never-split-difference.md deleted file mode 100644 index 39af9805..00000000 --- a/demo-vault-v2/note-never-split-difference.md +++ /dev/null @@ -1,43 +0,0 @@ ---- -aliases: ["Never Split the Difference"] -Is A: Note -Author: "Chris Voss" -Topics: ["[[topic-b2b-marketing]]"] -URL: "https://example.com/never-split" ---- -# Never Split the Difference -*Chris Voss* - -Voss, a former FBI lead international kidnapping negotiator, distills decades of high-stakes negotiation experience into a set of techniques that are surprisingly applicable to everyday business situations. The central premise is that negotiation is not about rational argument or splitting the difference -- it is about understanding and influencing emotions. People make decisions emotionally and justify them rationally, so the most effective negotiator is not the one with the best logic but the one who best understands and addresses the other side's emotional needs. This reframing alone changed how I approach every business conversation. - -The specific techniques are practical and immediately usable. Mirroring (repeating the last few words someone said) encourages them to elaborate and feel heard. Labeling ("It sounds like you're concerned about...") validates emotions and defuses tension. Calibrated questions ("How am I supposed to do that?") redirect pressure without confrontation. The "accusation audit" (preemptively acknowledging every negative thing the other side might think about you) disarms defensiveness before it starts. Each technique is backed by real negotiation stories that make the concepts memorable and concrete. - -For someone running a content business with sponsorships, partnerships, and vendor relationships, this book is directly applicable. Sponsor negotiations are not adversarial, but they do involve competing interests -- the sponsor wants maximum exposure at minimum cost, and you want fair compensation for your audience's attention. Voss's approach of tactical empathy (understanding the other side's perspective without necessarily agreeing) has made these conversations more productive and more pleasant. The goal is not to "win" but to reach an agreement that both sides feel good about, which is essential for long-term business relationships. - -## Key takeaways - -- Negotiation is fundamentally about emotions, not logic -- address feelings first, facts second -- Mirroring (repeating last words) is a simple technique that builds rapport and encourages the other side to share more -- Labeling emotions ("It seems like...") validates the other person's experience and reduces defensive reactions -- Calibrated questions ("How" and "What" questions) guide the conversation without making demands -- The accusation audit -- listing every bad thing the other side might think about you upfront -- is disarmingly effective -- "No" is not the end of a negotiation; it is often the beginning, because it makes people feel safe and in control -- Never split the difference: a compromise where both sides are unhappy is worse than finding a creative solution where both sides get what they actually need - -## How I apply this - -- In sponsor negotiations, I now start with an accusation audit: "You probably think our rates are too high for a newsletter of our size, and you might be worried that the ROI will not justify the spend." This consistently disarms tension and leads to more honest conversations about value and expectations. -- I use calibrated questions when freelancers or collaborators propose timelines or budgets that do not work: "How would we handle the quality review in that timeframe?" This redirects the conversation to problem-solving rather than confrontation. -- Mirroring has become a default habit in all my conversations, not just negotiations. When a reader emails with a complaint, repeating their concern back to them ("You felt the last edition was too surface-level...") before responding makes them feel heard and reduces the emotional charge. - -## Related - -- [[b2b-content-is-trust-not-traffic]] -- [[newsletter-growth-is-about-trust]] -- [[podcasting-is-relationship-building]] -- [[the-real-job-of-a-newsletter]] -- [[note-how-minds-change]] -- [[note-radical-candor]] -- [[note-thinking-fast-and-slow]] -- [[topic-b2b-marketing]] -- [[topic-newsletter-growth]] diff --git a/demo-vault-v2/note-old-meeting-notes.md b/demo-vault-v2/note-old-meeting-notes.md deleted file mode 100644 index fc238455..00000000 --- a/demo-vault-v2/note-old-meeting-notes.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -Is A: Note -trashed: true -trashed_at: "2026-02-10" -Topics: ["[[topic-productivity-systems]]"] ---- -# Old Meeting Notes - -These are meeting notes from a brainstorming session that didn't lead anywhere. The project was shelved and these notes are no longer relevant. - -## Attendees -- Luca -- Matteo - -## Discussion -- Explored potential partnership with a media company -- Decided not to pursue after evaluating the terms -- Follow-up was scheduled but never happened diff --git a/demo-vault-v2/note-on-clear-prose.md b/demo-vault-v2/note-on-clear-prose.md new file mode 100644 index 00000000..38791b1c --- /dev/null +++ b/demo-vault-v2/note-on-clear-prose.md @@ -0,0 +1,9 @@ +--- +type: Note +topics: + - "[[topic-writing]]" +--- + +# On Clear Prose + +Reference note for a book worth reopening whenever prose starts to feel bloated. diff --git a/demo-vault-v2/note-on-the-shortness-of-life.md b/demo-vault-v2/note-on-the-shortness-of-life.md deleted file mode 100644 index f0733b75..00000000 --- a/demo-vault-v2/note-on-the-shortness-of-life.md +++ /dev/null @@ -1,44 +0,0 @@ ---- -aliases: ["On the Shortness of Life"] -Is A: Note -Author: "Seneca" -Topics: ["[[topic-mental-health]]"] -URL: "https://example.com/shortness" ---- -# On the Shortness of Life -*Seneca* - -Seneca's central argument, written nearly two thousand years ago, remains devastatingly relevant: life is not short; we make it short by wasting it. We squander our time on trivial pursuits, on trying to please people who do not matter, on accumulating things we do not need, and on postponing the activities that would actually give our lives meaning. The essay is a direct challenge to anyone who claims to be "too busy" -- Seneca would argue that busyness is not a sign of importance but of poor prioritization. The person who spends their life preparing to live, but never actually living, has wasted the only resource that cannot be replenished. - -What makes this essay hit differently for a founder is the specificity of Seneca's critique. He is not talking about lazy people wasting time. He is talking about ambitious, accomplished people who fill their days with activity but never step back to ask whether that activity is aligned with what they actually value. This is the default mode for anyone building a business: there is always another email to send, another feature to ship, another metric to optimize. Seneca would say that if you cannot articulate why you are doing any of it, you are not living -- you are merely occupied. The question is not "are you busy?" but "are you spending your time on what matters?" - -I re-read this essay every December as part of my annual review. Each time, different passages land differently depending on what I have been doing that year. The core message -- that time is the only truly scarce resource and that how you spend it is the most consequential decision you make every day -- is simple enough to understand on first reading but takes a lifetime to internalize. Seneca is the antidote to the "hustle culture" that pervades the startup world, not because he opposes hard work, but because he insists that hard work without reflection is just a more respectable form of wasting time. - -## Key takeaways - -- Life is not short -- we waste it through poor prioritization, social obligations, and failure to reflect on what matters -- Busyness is not a virtue; it is often a sign that you are avoiding the harder question of whether your activities are meaningful -- Time is the only truly non-renewable resource -- money can be earned back, time cannot -- The "preoccupied" person (busy but unintentional) is Seneca's primary target: they are always preparing to live but never actually living -- Philosophical leisure (time spent in reflection, reading, and meaningful conversation) is not wasted time but the highest use of time -- Most people would not give away their money freely, yet they give away their time -- the more valuable resource -- without a second thought -- Annual reflection on how you spend your time is essential for staying aligned with your values - -## How I apply this - -- Every December, I do an annual time audit inspired by this essay. I look at how I actually spent my time over the past year (using calendar data and journal entries) and compare it to how I wanted to spend it. The gap is always humbling, but the exercise consistently redirects my priorities for the coming year. -- Seneca's critique of social obligations gave me permission to say no to events, dinners, and "coffee chats" that do not serve a genuine purpose. I no longer feel guilty about protecting my time -- I feel responsible for it. -- The distinction between being busy and being productive has become a daily filter. Before starting any task, I ask: "Is this important, or does it just feel urgent?" If the answer is the latter, it goes to the bottom of the list or gets eliminated entirely. - -## Related - -- [[on-founder-energy-management]] -- [[on-consistency-in-creative-work]] -- [[the-two-types-of-hard]] -- [[sleeping-more-is-a-superpower]] -- [[note-man-search-for-meaning]] -- [[note-the-obstacle-is-the-way]] -- [[note-essentialism]] -- [[note-the-effective-executive]] -- [[topic-mental-health]] -- [[topic-productivity-systems]] diff --git a/demo-vault-v2/note-on-writing-well.md b/demo-vault-v2/note-on-writing-well.md deleted file mode 100644 index 2e46a2a9..00000000 --- a/demo-vault-v2/note-on-writing-well.md +++ /dev/null @@ -1,44 +0,0 @@ ---- -aliases: ["On Writing Well"] -Is A: Note -Author: "William Zinsser" -Topics: ["[[topic-writing]]"] -URL: "https://example.com/writing-well" ---- -# On Writing Well -*William Zinsser* - -Zinsser's guide to non-fiction writing is built on a single conviction: clutter is the disease of American writing, and surgery is the cure. Every word in a sentence must earn its place; every sentence must advance the piece. This is not about writing short -- it is about writing clean. Zinsser rails against corporate jargon, unnecessary qualifiers, passive voice, and the kind of throat-clearing preambles that plague most business writing. His ideal is prose that is so clear that the reader never has to re-read a sentence, and so economical that removing any word would damage the meaning. - -For a newsletter writer, this book is effectively a technical manual. Newsletter readers are impatient -- they are reading during a coffee break, between meetings, on their phones. Every unnecessary sentence is a reason to stop reading. Zinsser's principles -- cut adverbs, prefer active voice, lead with the interesting part, never use a complicated word when a simple one will do -- directly translate to higher open rates, better engagement, and more trust. Readers may not be able to articulate why they find one newsletter better than another, but clarity of writing is almost always a major factor. - -Beyond the sentence-level craft, Zinsser makes an important argument about voice and authenticity. He insists that good non-fiction writing sounds like a person talking, not a corporation communicating. This means using "I" when appropriate, having opinions, and letting your personality come through. For indie creators who compete against faceless media companies, this is a strategic advantage, not just a stylistic choice. Your voice is what makes your newsletter irreplaceable. Zinsser's advice is to find your natural voice and then refine it relentlessly, cutting away everything that is not genuinely you. - -## Key takeaways - -- Clutter is the enemy of good writing -- every word must earn its place, every sentence must advance the piece -- Rewriting is the essence of writing: the first draft is for getting ideas down, subsequent drafts are for cutting and clarifying -- Active voice is almost always better than passive voice: it is clearer, more direct, and more engaging -- Write for yourself first -- if you are bored writing it, the reader will be bored reading it -- Unity of pronoun, tense, mood, and tone is essential: pick your approach and stick with it throughout the piece -- Good non-fiction sounds like a person talking, not an institution communicating -- warmth and personality are assets, not indulgences -- The lead (opening) is the most critical part of any piece: if you do not hook the reader in the first two sentences, nothing else matters - -## How I apply this - -- My editing process is directly shaped by Zinsser. After drafting a newsletter edition, I do a "clutter pass" where my only goal is to cut words and simplify sentences. I typically cut 20-30% of the draft in this pass, and the result is always better. If a sentence does not survive scrutiny, it goes. -- I read every edition aloud before publishing. Zinsser's emphasis on writing that sounds like a person talking is best tested by literally hearing it spoken. Awkward phrasing, unnecessary qualifiers, and convoluted sentences become immediately obvious when you say them out loud. -- I use Zinsser's "lead" advice to force myself to start every newsletter edition with the most interesting or surprising point, not with context or preamble. This was hard to adopt -- my instinct is to "set the stage" -- but it has measurably improved my open-to-read-through rates. - -## Related - -- [[writing-for-clarity-vs-writing-for-credit]] -- [[the-real-job-of-a-newsletter]] -- [[newsletter-growth-is-about-trust]] -- [[on-consistency-in-creative-work]] -- [[note-show-your-work]] -- [[note-building-a-second-brain]] -- [[note-how-minds-change]] -- [[topic-writing]] -- [[topic-content-strategy]] -- [[topic-newsletter-growth]] diff --git a/demo-vault-v2/note-radical-candor.md b/demo-vault-v2/note-radical-candor.md deleted file mode 100644 index bb027c91..00000000 --- a/demo-vault-v2/note-radical-candor.md +++ /dev/null @@ -1,43 +0,0 @@ ---- -aliases: ["Radical Candor"] -Is A: Note -Author: "Kim Scott" -Topics: ["[[topic-team-leadership]]"] -URL: "https://example.com/radical-candor" ---- -# Radical Candor -*Kim Scott* - -Scott's framework sits at the intersection of two dimensions: caring personally and challenging directly. When you do both, you achieve radical candor -- honest feedback delivered with genuine concern for the person. When you care but do not challenge, you fall into "ruinous empathy" -- the most common failure mode, where you avoid difficult conversations to spare feelings and end up enabling mediocrity. When you challenge without caring, you get "obnoxious aggression." When you do neither, you get "manipulative insincerity." The two-by-two matrix is simple, but it captures the dynamics of almost every feedback conversation I have ever had. - -The book's most important insight is that ruinous empathy is far more damaging than obnoxious aggression. Most managers and team leaders avoid giving honest feedback because they do not want to hurt people's feelings. But by withholding feedback, they deny people the information they need to improve, which is ultimately a far greater disservice. Scott argues that it is unkind, not kind, to let someone continue doing subpar work without telling them. For a small team leader, this reframing is critical: your obligation is not to keep everyone comfortable but to help everyone grow, and growth requires honest, direct feedback. - -For an indie founder managing freelancers, contractors, or a small team, this framework is directly applicable even outside traditional management contexts. Giving feedback to a freelance writer about their draft quality, having a candid conversation with a co-host about podcast performance, or addressing a sponsor about campaign results all require the same balance of caring and directness. The techniques Scott offers -- SBI (Situation-Behavior-Impact) for structuring feedback, "kind and clear" as a mantra, and the guidance of praising in public and criticizing in private -- are immediately usable. - -## Key takeaways - -- Radical candor requires both caring personally and challenging directly -- you need both dimensions, not just one -- Ruinous empathy (caring without challenging) is the most common and most damaging feedback failure mode -- It is unkind to withhold honest feedback -- you are denying people the information they need to improve -- SBI (Situation-Behavior-Impact) is a reliable structure for delivering feedback: describe the situation, the specific behavior, and its impact -- Praise in public, criticize in private -- and be as specific in praise as you are in criticism -- Feedback should be frequent, immediate, and focused on behavior (not personality) to be effective -- The goal of feedback is not to make someone feel good or bad but to help them do their best work - -## How I apply this - -- I use the radical candor framework with my freelance writers. When a draft does not meet the standard, I provide specific, behavior-focused feedback ("The opening section restated the obvious rather than leading with the insight") rather than vague critiques ("This needs work"). The SBI structure ensures the feedback is actionable rather than demoralizing. -- In my podcast, I apply the "kind and clear" mantra when debriefing episodes with my co-host. Instead of saying "that was great" when it was not, or avoiding the conversation entirely, I point out specific moments that worked and specific moments that fell flat, with suggestions for improvement. -- I have started asking collaborators and team members to practice radical candor with me. This required explicitly inviting criticism and then receiving it without defensiveness, which is harder than it sounds. But the quality of feedback I receive has improved dramatically since I created that permission structure. - -## Related - -- [[small-teams-scale-through-systems]] -- [[on-founder-energy-management]] -- [[writing-for-clarity-vs-writing-for-credit]] -- [[the-two-types-of-hard]] -- [[note-the-hard-thing-about-hard-things]] -- [[note-never-split-difference]] -- [[note-the-courage-to-be-disliked]] -- [[topic-team-leadership]] -- [[topic-podcasting]] diff --git a/demo-vault-v2/note-range.md b/demo-vault-v2/note-range.md deleted file mode 100644 index b10386e4..00000000 --- a/demo-vault-v2/note-range.md +++ /dev/null @@ -1,44 +0,0 @@ ---- -aliases: ["Range"] -Is A: Note -Author: "David Epstein" -Topics: ["[[topic-reading-books]]"] -URL: "https://example.com/range" ---- -# Range -*David Epstein* - -Epstein's thesis is a direct challenge to the "10,000 hours" narrative popularized by Malcolm Gladwell and Anders Ericsson: in complex, unpredictable domains, generalists often outperform specialists. While early specialization works in "kind" learning environments (like chess or golf, where the rules are clear and feedback is immediate), most real-world challenges are "wicked" environments where the rules are unclear, feedback is delayed, and the ability to draw on diverse experiences is more valuable than deep expertise in a single area. Epstein marshals evidence from sports, science, music, and business to argue that the winding path -- sampling broadly, integrating across domains, and specializing later -- is often the superior strategy. - -This is particularly relevant for indie founders and content creators. Running a newsletter business requires skills in writing, marketing, product thinking, negotiation, design, technology, and strategy. No single specialization prepares you for this. The most effective founders I know are not world-class at any one thing but are competent across many things and unusually good at connecting ideas from different domains. Epstein calls this "lateral thinking with withered technology" -- using existing, well-understood tools in novel combinations. This is exactly what happens when you apply lessons from cycling to content strategy, or from behavioral science to newsletter growth. - -Epstein also argues that "match quality" -- the fit between a person and their work -- is more important than early commitment. People who try many things before committing tend to find better matches and ultimately achieve more, even though they start "later" by conventional metrics. This is a reassuring message for anyone who arrived at their current work through a non-linear path, and a caution against the advice to "pick one thing and go all-in" without sufficient exploration. - -## Key takeaways - -- In complex, unpredictable domains, generalists often outperform specialists because they can draw on a wider range of mental models -- "Kind" learning environments (clear rules, immediate feedback) favor early specialization; "wicked" environments (ambiguous rules, delayed feedback) favor breadth -- Lateral thinking -- applying solutions from one domain to problems in another -- is a core advantage of generalists -- Match quality (the fit between person and work) is more important than early commitment; exploration improves match quality -- Analogical reasoning (drawing parallels between dissimilar situations) is a learnable skill that improves with breadth of experience -- The "outside view" (looking at a problem through the lens of similar problems in other fields) consistently outperforms the "inside view" (relying only on domain-specific knowledge) -- A broad foundation makes later specialization more effective, not less -- breadth and depth are complements, not substitutes - -## How I apply this - -- My career path -- from engineering to product management to newsletter writing to indie building -- used to feel scattered. After reading Range, I reframed it as a deliberate sampling period that gave me the cross-domain perspective I need to create distinctive content. The ability to connect engineering thinking with content strategy is directly attributable to that breadth. -- I deliberately read across fields (behavioral science, endurance sports, philosophy, business) rather than staying narrowly in "content marketing" or "SaaS." Range validated this approach: the most original ideas in my newsletter come from cross-pollination between unrelated domains. -- When evaluating potential collaborators or hires, I now weight diverse experience more heavily. Someone who has worked in three different fields and understands the patterns that connect them is often more valuable than someone who has spent ten years in a single specialty. - -## Related - -- [[the-compound-effect-in-knowledge-work]] -- [[reading-more-by-reading-better]] -- [[knowledge-management-is-not-filing]] -- [[ai-wont-replace-thinking]] -- [[note-the-art-of-learning]] -- [[note-grit]] -- [[note-so-good-they-cant-ignore]] -- [[topic-reading-books]] -- [[topic-productivity-systems]] -- [[procedure-weekly-reading-session]] diff --git a/demo-vault-v2/note-show-your-work.md b/demo-vault-v2/note-show-your-work.md deleted file mode 100644 index 738ecb4f..00000000 --- a/demo-vault-v2/note-show-your-work.md +++ /dev/null @@ -1,44 +0,0 @@ ---- -aliases: ["Show Your Work"] -Is A: Note -Author: "Austin Kleon" -Topics: ["[[topic-writing]]"] -URL: "https://example.com/show-your-work" ---- -# Show Your Work -*Austin Kleon* - -Kleon's premise is simple and liberating: you do not need to be a genius to share your work. You do not even need to be an expert. You just need to be willing to learn in public and share your process, not just your polished outputs. The book is a practical guide for anyone who creates things and wants to build an audience around their work without resorting to self-promotion tactics that feel slimy. Kleon's approach is generous rather than transactional: share useful things, teach what you know, credit your influences, and the audience will come as a byproduct. - -This book fundamentally shaped my approach to the newsletter. Before reading it, I felt pressure to present myself as an authority -- someone who had figured things out and was dispensing wisdom from above. Kleon convinced me that sharing the learning process itself is more valuable and more authentic. Readers connect more deeply with "here is what I am figuring out" than with "here is what you should do." This shift made writing more enjoyable (less pressure to be perfect) and more effective (readers trust vulnerability more than polish). The concept of "learning in public" has become central to how I think about content creation. - -Kleon also offers practical advice on the mechanics of sharing: keep a daily dispatch of what you are working on, maintain a "cabinet of curiosities" (things that inspire you and that you share with your audience), and build a body of work over time rather than chasing individual viral moments. The emphasis on consistency over spectacle is particularly relevant for newsletter operators. You are not trying to go viral; you are trying to build a trusted relationship with a specific audience over months and years. That requires showing up regularly with genuine, useful content, which is exactly what Kleon advocates. - -## Key takeaways - -- Share your process, not just your polished output -- audiences connect more with the journey than with the destination -- You do not need to be an expert to share; being a dedicated learner in public is valuable and authentic -- "Learning in public" builds trust and attracts an audience of people who are on a similar path -- Consistency beats virality: regular sharing builds a body of work and a loyal audience over time -- A "cabinet of curiosities" (things that inspire you, tools you use, influences you draw from) is content that only you can create -- Credit your influences generously -- this builds relationships with other creators and demonstrates intellectual honesty -- The "So what?" test: before sharing anything, ask what value it provides to the reader, not just to you - -## How I apply this - -- My newsletter follows Kleon's "learning in public" philosophy directly. Rather than positioning myself as the expert with all the answers, I share what I am reading, testing, and thinking about. This approach has generated the strongest reader engagement and the most organic growth because it invites readers into a conversation rather than a lecture. -- I maintain a running list of interesting tools, articles, books, and ideas that I share in a "links" section of my newsletter. This is Kleon's "cabinet of curiosities" in practice -- it costs almost nothing to produce, adds genuine value, and gives readers a window into my thinking process. -- I share early drafts and work-in-progress publicly more often than I used to. A half-finished framework posted on Twitter generates more useful feedback and engagement than a polished final product, and it builds anticipation for the full version in the newsletter. - -## Related - -- [[open-source-as-marketing]] -- [[writing-for-clarity-vs-writing-for-credit]] -- [[newsletter-growth-is-about-trust]] -- [[the-real-job-of-a-newsletter]] -- [[on-consistency-in-creative-work]] -- [[note-on-writing-well]] -- [[note-building-a-second-brain]] -- [[topic-writing]] -- [[topic-newsletter-growth]] -- [[topic-content-strategy]] diff --git a/demo-vault-v2/note-so-good-they-cant-ignore.md b/demo-vault-v2/note-so-good-they-cant-ignore.md deleted file mode 100644 index f2f6042f..00000000 --- a/demo-vault-v2/note-so-good-they-cant-ignore.md +++ /dev/null @@ -1,44 +0,0 @@ ---- -aliases: ["So Good They Can't Ignore You"] -Is A: Note -Author: "Cal Newport" -Topics: ["[[topic-productivity-systems]]"] -URL: "https://example.com/so-good" ---- -# So Good They Can't Ignore You -*Cal Newport* - -Newport's argument is a direct assault on the "follow your passion" career advice that dominates popular culture. His thesis: passion is not something you discover and then pursue; it is something that develops as you become excellent at something valuable. The mechanism is career capital -- rare and valuable skills that you build through deliberate practice, which then give you leverage to negotiate for the work conditions you want (autonomy, creativity, impact, flexibility). The implication is that instead of asking "what am I passionate about?" you should ask "what rare and valuable skill can I develop?" - -This reframing is profoundly useful for indie founders and content creators. The temptation is to wait for a "passion" to reveal itself or to chase whatever feels exciting in the moment. Newport argues this is backwards. Passion follows mastery, not the other way around. The newsletter writers who love their work are not the ones who started with a burning passion for email marketing -- they are the ones who developed the skill of clear writing, the knowledge of their niche, and the audience trust that makes the work meaningful. They became passionate about their work because they became good at it. - -The book introduces the "craftsman mindset" (what can I offer the world?) as an alternative to the "passion mindset" (what can the world offer me?). The craftsman mindset focuses on deliberate practice, skill development, and creating value for others. Newport also identifies three "career capital markets": winner-take-all (where one skill matters, like writing quality), auction (where a combination of skills matters), and mission-driven (where work is organized around a clear purpose). Understanding which market you are in shapes which skills to develop and how to invest your practice time. - -## Key takeaways - -- "Follow your passion" is bad advice -- passion develops from mastery, not the other way around -- Career capital (rare and valuable skills) is the currency that buys you autonomy, creativity, and meaningful work -- The craftsman mindset ("what can I offer?") is more productive than the passion mindset ("what do I want?") -- Deliberate practice -- stretching beyond your comfort zone with immediate feedback -- is how career capital is built -- Control over your work conditions must be earned through career capital; claiming it prematurely leads to failure -- Mission comes after mastery: you need to be at the cutting edge of a field before you can identify a meaningful mission within it -- Small, consistent investments in skill development compound into significant career advantages over time - -## How I apply this - -- I treat writing as a deliberate practice discipline. Each week, I focus on a specific aspect of craft (clarity of argument, quality of opening, use of concrete examples) and actively seek feedback on that dimension. This is the career capital approach applied to content creation -- I am investing in the skill that makes everything else possible. -- When I feel tempted to pivot to a new topic or medium because it seems "more exciting," I remind myself of Newport's core argument: the excitement of novelty is not passion. Real passion will come from going deeper into what I am already building, not from starting over somewhere new. -- I use the career capital framework when advising other newsletter operators. Instead of asking "what are you passionate about?" I ask "what rare skill have you developed?" and "what would make your writing irreplaceable?" This reframing consistently leads to more productive conversations about growth and differentiation. - -## Related - -- [[the-compound-effect-in-knowledge-work]] -- [[on-consistency-in-creative-work]] -- [[the-two-types-of-hard]] -- [[writing-for-clarity-vs-writing-for-credit]] -- [[note-deep-work]] -- [[note-grit]] -- [[note-atomic-habits]] -- [[note-range]] -- [[topic-productivity-systems]] -- [[topic-writing]] diff --git a/demo-vault-v2/note-the-art-of-learning.md b/demo-vault-v2/note-the-art-of-learning.md deleted file mode 100644 index a8b681d8..00000000 --- a/demo-vault-v2/note-the-art-of-learning.md +++ /dev/null @@ -1,44 +0,0 @@ ---- -aliases: ["The Art of Learning"] -Is A: Note -Author: "Josh Waitzkin" -Topics: ["[[topic-productivity-systems]]"] -URL: "https://example.com/art-of-learning" ---- -# The Art of Learning -*Josh Waitzkin* - -Waitzkin is one of the rare people who has achieved world-class mastery in two completely different fields -- chess (as a child prodigy and national champion) and martial arts (as a Push Hands world champion). This book is his attempt to articulate the meta-skill of learning itself: how to approach new domains, how to push through plateaus, and how to develop the kind of deep, intuitive understanding that separates true experts from competent practitioners. The result is the most practically useful book on learning I have encountered, far more actionable than the academic literature on deliberate practice. - -Waitzkin's concept of "investment in loss" is particularly powerful. He argues that the willingness to lose, to fail, and to look foolish is the single biggest determinant of learning speed. Most people protect their ego by staying in their comfort zone, doing what they already know how to do. True learners deliberately seek out situations where they will struggle, because struggle is where learning happens. This applies directly to content creation: the newsletter editions where I try something new and fail are far more valuable for my development as a writer than the ones where I repeat a proven formula. - -The book also introduces the idea of "making smaller circles" -- taking a complex skill and reducing it to its essential components, then practicing those components to an extraordinarily deep level before re-integrating them. This is the opposite of the superficial breadth that most people settle for. In chess, it means understanding a single endgame position so deeply that the principles generalize outward. In writing, it means mastering the craft of a single paragraph type (an argument, a narrative, an opening hook) before trying to orchestrate a full piece. Depth of understanding in fundamentals creates flexibility at higher levels of complexity. - -## Key takeaways - -- "Investment in loss" -- the willingness to fail and look foolish -- is the key accelerant of learning -- "Making smaller circles": reduce a skill to its fundamental components, master each one deeply, then re-integrate -- Plateaus are not signs of stagnation but natural phases where deep processing is happening beneath the surface -- The "soft zone" (working with distractions rather than against them) is more resilient than the "hard zone" (requiring perfect conditions) -- Stress and recovery cycles apply to cognitive learning just as they do to physical training -- rest is not optional -- Intuition is not mystical; it is the product of so much deliberate practice that pattern recognition becomes automatic -- The transition between disciplines (chess to martial arts) reveals transferable meta-skills that are more valuable than domain-specific knowledge - -## How I apply this - -- I practice "investment in loss" by deliberately experimenting with writing formats I am not good at. Long-form analysis, personal essays, data-driven pieces -- each requires different skills, and I allocate time to practice the ones where I am weakest, even though the results are initially worse than my standard format. -- I apply "making smaller circles" to my editing process. Rather than trying to improve "writing quality" in general, I focus on one specific element per month (opening hooks, transition sentences, paragraph rhythm) and practice it obsessively. This focused approach has improved my craft faster than trying to improve everything at once. -- The stress-recovery insight from Waitzkin (and from endurance sports generally) has convinced me that rest and recovery are not luxuries but essential parts of the creative process. My best ideas consistently come after rest periods, not during marathon work sessions. - -## Related - -- [[the-compound-effect-in-knowledge-work]] -- [[training-load-and-knowledge-work]] -- [[reading-more-by-reading-better]] -- [[cycling-teaches-patience]] -- [[note-deep-work]] -- [[note-grit]] -- [[note-range]] -- [[note-atomic-habits]] -- [[topic-productivity-systems]] -- [[topic-cycling-training]] diff --git a/demo-vault-v2/note-the-courage-to-be-disliked.md b/demo-vault-v2/note-the-courage-to-be-disliked.md deleted file mode 100644 index 1ead9317..00000000 --- a/demo-vault-v2/note-the-courage-to-be-disliked.md +++ /dev/null @@ -1,43 +0,0 @@ ---- -aliases: ["The Courage to Be Disliked"] -Is A: Note -Author: "Kishimi & Koga" -Topics: ["[[topic-mental-health]]"] -URL: "https://example.com/courage" ---- -# The Courage to Be Disliked -*Kishimi & Koga* - -This book presents Adlerian psychology through a Socratic dialogue between a philosopher and a young person. The core framework is built around three ideas: task separation (distinguishing between what is your task and what is someone else's task), the rejection of the need for recognition (the desire for approval is the root of much unhappiness), and the concept that all problems are interpersonal relationship problems. Adler's position is that we choose our responses to our circumstances, and that freedom comes from accepting responsibility for those choices rather than blaming our past, our genes, or our environment. - -The concept of task separation has been the most practically transformative idea from this book. In Adler's framework, you are responsible for your own tasks (your effort, your behavior, your choices) and not responsible for other people's tasks (their reactions, their opinions, their feelings). When you publish a newsletter, your task is to write something honest and valuable. Whether a reader likes it, shares it, or cancels their subscription is their task, not yours. This separation is not about callousness -- it is about focusing your energy where you actually have control and letting go of the rest. For anyone who creates things publicly, this is an essential survival skill. - -The dialogue format makes the ideas accessible, but also reveals their radical nature. Adler's position is that even trauma does not determine your behavior -- you always have a choice in how you respond to your past. This is controversial (and the book acknowledges this through the young person's objections), but the practical application is powerful: if you accept that your current behavior is a choice, you can change it. You are not stuck with your habits, your fears, or your patterns. This is both liberating and uncomfortable, because it removes the excuses we use to avoid difficult changes. - -## Key takeaways - -- Task separation: focus only on what is your task and release what is someone else's task -- this is the foundation of inner peace -- The desire for recognition and approval is a major source of unhappiness; freedom comes from accepting that not everyone will like you -- All problems are ultimately interpersonal relationship problems -- even the ones that seem purely internal -- You are not determined by your past; you choose how to interpret and respond to your experiences in the present -- Courage means being willing to be disliked in pursuit of what you believe is right -- Contribution to the community (feeling useful to others) is the deepest source of happiness, deeper than achievement or recognition -- Horizontal relationships (treating others as equals) are healthier than vertical relationships (ranking people as superior/inferior) - -## How I apply this - -- Task separation has transformed how I handle negative feedback on my newsletter. When a reader sends a harsh critique, I evaluate whether it contains useful information (my task: improve), and then release any emotional reaction to their tone or judgment (their task: how they express themselves). This has made me far more receptive to criticism because I no longer experience it as a personal attack. -- I apply the recognition rejection principle to social media. I stopped tracking follower counts and engagement metrics as measures of self-worth. The numbers inform my strategy, but they do not determine my mood or my sense of whether I am doing good work. -- The "courage to be disliked" mantra has given me permission to take stronger editorial positions in my writing. Some readers will disagree, unsubscribe, or complain. That is their task. My task is to write what I genuinely believe, with honesty and care. - -## Related - -- [[on-founder-energy-management]] -- [[the-two-types-of-hard]] -- [[writing-for-clarity-vs-writing-for-credit]] -- [[on-consistency-in-creative-work]] -- [[note-man-search-for-meaning]] -- [[note-the-obstacle-is-the-way]] -- [[note-radical-candor]] -- [[note-on-the-shortness-of-life]] -- [[topic-mental-health]] diff --git a/demo-vault-v2/note-the-effective-executive.md b/demo-vault-v2/note-the-effective-executive.md deleted file mode 100644 index 7b7176a9..00000000 --- a/demo-vault-v2/note-the-effective-executive.md +++ /dev/null @@ -1,44 +0,0 @@ ---- -aliases: ["The Effective Executive"] -Is A: Note -Author: "Peter Drucker" -Topics: ["[[topic-team-leadership]]"] -URL: "https://example.com/effective-executive" ---- -# The Effective Executive -*Peter Drucker* - -Drucker wrote this in 1967, and it remains the best book on personal effectiveness for knowledge workers. His premise is that effectiveness is not about intelligence or education but about a set of practices that can be learned. The five practices he identifies are: know where your time goes (track it systematically), focus on contribution (ask "what can I contribute?" rather than "what do I need?"), make strengths productive (your own and others'), concentrate on the few major areas where superior performance will produce outstanding results, and make effective decisions. Each of these sounds obvious, but Drucker's genius is in showing how systematically most people fail to do them. - -The time management chapter alone justifies the book. Drucker insists that effective executives start by tracking how they actually spend their time -- not how they think they spend it, but what the calendar and the log actually show. The gap between perception and reality is usually alarming. He then advocates for consolidating discretionary time into the largest possible blocks, because creative and analytical work requires sustained attention. This insight, written six decades ago, is the same argument Cal Newport makes in Deep Work. Drucker got there first, and his version is more practical because it comes with specific techniques for eliminating time wasters (unnecessary meetings, redundant reports, activities that produce no results). - -For an indie founder, the "focus on contribution" practice is the most valuable. Drucker distinguishes between people who focus on effort ("I work hard") and people who focus on contribution ("My work produces this result"). This shift in orientation changes everything: how you prioritize, what you measure, and how you evaluate your own performance. Applied to a newsletter business, it means asking not "how many hours did I work this week?" but "what value did I create for my readers, my sponsors, and my own learning?" - -## Key takeaways - -- Effectiveness is a learnable practice, not an innate trait -- it consists of specific habits that anyone can develop -- Time tracking reveals the gap between how you think you spend your time and how you actually spend it -- this gap is always larger than you expect -- Consolidate discretionary time into large blocks; fragmented time produces fragmented work -- Focus on contribution ("what results can I produce?") rather than effort ("how hard am I working?") -- Make strengths productive: build on what you and your team do well rather than trying to fix weaknesses -- Effective decisions are few, important, and made systematically: define the problem, specify the boundary conditions, decide, act, and verify -- The most important question for any knowledge worker: "What can I contribute that will significantly affect the performance and results of this organization?" - -## How I apply this - -- I do a quarterly time audit where I track every hour for one full week and compare it to my intended allocation. Without fail, I discover that I am spending more time on low-value activities (email, admin, reactive tasks) than I thought, and less time on high-value creation (writing, strategy, relationship building). The audit always prompts a meaningful reallocation. -- I start each week by asking Drucker's contribution question: "What is the most important thing I can contribute this week?" This forces me to prioritize outcomes over activities and prevents me from filling my days with busy work that feels productive but produces no meaningful results. -- I apply the "make strengths productive" principle to how I work with freelancers and collaborators. Rather than hiring generalists and hoping they cover all bases, I identify what each person does exceptionally well and organize work around those strengths. The results are consistently better than trying to shore up weaknesses. - -## Related - -- [[small-teams-scale-through-systems]] -- [[on-founder-energy-management]] -- [[on-consistency-in-creative-work]] -- [[the-real-job-of-a-newsletter]] -- [[note-essentialism]] -- [[note-deep-work]] -- [[note-makers-schedule-managers]] -- [[note-good-strategy-bad-strategy]] -- [[topic-team-leadership]] -- [[topic-productivity-systems]] diff --git a/demo-vault-v2/note-the-hard-thing-about-hard-things.md b/demo-vault-v2/note-the-hard-thing-about-hard-things.md deleted file mode 100644 index f74fd67a..00000000 --- a/demo-vault-v2/note-the-hard-thing-about-hard-things.md +++ /dev/null @@ -1,44 +0,0 @@ ---- -aliases: ["The Hard Thing About Hard Things"] -Is A: Note -Author: "Ben Horowitz" -Topics: ["[[topic-team-leadership]]"] -URL: "https://example.com/hard-things" ---- -# The Hard Thing About Hard Things -*Ben Horowitz* - -Most business books describe how to do things correctly. Horowitz's book describes what happens when everything goes wrong and there is no right answer. Drawing from his experience as CEO of Opsware (through near-death experiences including almost running out of money, mass layoffs, and multiple pivots), Horowitz provides the most honest account I have found of what leading under extreme uncertainty actually feels like. The "struggle" chapter -- describing the psychological reality of being a founder when the company is failing and the weight is entirely on your shoulders -- is the best thing written about the emotional dimension of entrepreneurship. - -What makes this book different from the typical startup advice is its willingness to sit with ambiguity. Horowitz does not pretend that there are clean frameworks for every situation. Sometimes you have to lay off friends. Sometimes you have to fire an executive you personally hired and championed. Sometimes the honest answer is "I don't know what to do." The book's value is not in providing solutions but in normalizing the difficulty and providing a set of heuristics for navigating impossible situations. For any founder who has ever felt alone in their struggle, this book is a companion. - -The management advice is also unusually practical. Horowitz's frameworks for hiring executives, giving feedback, and managing through crises are informed by hard-won experience rather than theory. His distinction between "peacetime CEO" and "wartime CEO" -- and the argument that different situations require fundamentally different leadership styles -- is something I return to regularly. As an indie founder, you shift between peacetime (steady growth, routine operations) and wartime (revenue crisis, market shift, team issues) more frequently than you might expect, and recognizing which mode you are in determines which playbook to follow. - -## Key takeaways - -- The "struggle" is the normal state of being a founder -- not a sign of failure but an inherent part of the journey -- There are no clean answers in hard situations; the goal is to make the least bad decision with imperfect information -- Peacetime CEO (expand, optimize, grow) and wartime CEO (survive, cut, focus) require different behaviors and mindsets -- Hiring for the role you need now is more important than hiring the most impressive resume -- When you have to deliver bad news (layoffs, pivots, failures), be direct, be honest, and do it quickly -- transparency builds trust even in terrible situations -- "Take care of the people, the products, and the profits -- in that order" is a reliable priority framework -- The lonely moments of leadership are normal; seeking out other founders who understand is essential for mental health - -## How I apply this - -- During a period when my newsletter revenue dropped significantly due to a sponsorship market contraction, I returned to the "struggle" chapter. It did not solve the problem, but it normalized the experience and reminded me that difficulty is not evidence of failure. That psychological reframe helped me make clear-headed decisions about cost cutting and revenue diversification rather than panicking. -- I use Horowitz's peacetime/wartime distinction to calibrate my management style. During stable growth periods, I focus on exploration and experimentation. During challenging periods, I narrow focus ruthlessly to the few things that will move the needle. Recognizing the shift is the key skill. -- His advice on delivering hard feedback ("clear is kind, unclear is unkind") has directly influenced how I give notes to freelance writers and collaborators. Being direct about what is not working, with specific examples and a constructive path forward, is more respectful than vague praise followed by a quiet phase-out. - -## Related - -- [[on-founder-energy-management]] -- [[the-two-types-of-hard]] -- [[small-teams-scale-through-systems]] -- [[the-saas-metric-that-matters]] -- [[note-radical-candor]] -- [[note-the-effective-executive]] -- [[note-good-strategy-bad-strategy]] -- [[note-zero-to-one]] -- [[topic-team-leadership]] -- [[topic-saas-business]] diff --git a/demo-vault-v2/note-the-innovators-dilemma.md b/demo-vault-v2/note-the-innovators-dilemma.md deleted file mode 100644 index 673a1889..00000000 --- a/demo-vault-v2/note-the-innovators-dilemma.md +++ /dev/null @@ -1,46 +0,0 @@ ---- -aliases: ["The Innovator's Dilemma"] -Is A: Note -Author: "Clayton Christensen" -Topics: ["[[topic-saas-business]]"] -URL: "https://example.com/innovators-dilemma" -trashed: true -trashed_at: 2026-03-04 ---- -# The Innovator's Dilemma -*Clayton Christensen* - -Christensen's central question is paradoxical: why do well-managed, successful companies fail? His answer is disruptive innovation -- technologies or business models that start by serving a low-end or new market segment with a "worse" product that is cheaper, simpler, or more convenient. Established companies ignore these disruptions because their best customers do not want them and their financial models do not support them. By the time the disruptive product improves enough to compete for the mainstream market, it is too late for the incumbents to respond. The companies that fail are not poorly managed; they are rationally optimizing for their current customers, which is precisely what makes them vulnerable. - -This framework is directly relevant to the media and content business landscape. Traditional media companies (newspapers, magazines, broadcast networks) were disrupted not by better journalism but by cheaper, more accessible content delivery mechanisms -- blogs, newsletters, podcasts, social media. Each of these was initially "worse" by traditional quality metrics but better on accessibility, cost, and personalization. The newsletter renaissance that enables indie creators to build sustainable content businesses is itself a disruptive innovation: lower production quality than a magazine, but higher relevance, more personal, and directly delivered to the reader's inbox. - -For an indie founder, the lesson is dual. On one hand, you are the disruptor: a solo operator competing with established media through a simpler, more focused, more personal product. On the other hand, you are not immune to disruption yourself. AI-generated content, new distribution platforms, or shifts in reader behavior could disrupt the newsletter model just as newsletters disrupted traditional media. The strategic response is to stay close to your audience, remain nimble, and avoid the complacency that comes from early success -- exactly the behaviors that incumbents in Christensen's case studies failed to maintain. - -## Key takeaways - -- Disruptive innovation starts with a "worse" product that is cheaper, simpler, or more convenient -- and improves over time until it overtakes the incumbent -- Well-managed companies fail precisely because they listen to their best customers and optimize rationally -- these behaviors are exactly what makes them vulnerable to disruption -- Sustaining innovation (making existing products better for existing customers) is different from disruptive innovation (creating new products for new or underserved markets) -- Incumbents cannot respond to disruption by using their existing business model -- they need a separate organization with different metrics and incentives -- The technology itself is not disruptive; the business model around it is what creates disruption -- Small markets are unattractive to large companies but perfect for startups -- this is the disruptor's advantage -- The best defense against disruption is staying close to your customers and remaining willing to cannibalize your own products - -## How I apply this - -- I view my newsletter as a disruptive product relative to traditional tech media: lower production cost, higher personalization, direct distribution. This framing helps me focus on the dimensions where I have a structural advantage (authenticity, niche depth, reader relationship) rather than trying to compete with incumbents on dimensions where I will lose (production scale, brand recognition, breadth of coverage). -- I actively monitor potential disruptions to the newsletter model itself. AI-generated personalized content, algorithm-curated feeds, and audio-first platforms are all potential disruptors. I invest time in understanding these trends so I can adapt early rather than being caught flat-footed. -- When evaluating new features or product ideas, I use Christensen's framework to ask: "Am I making a sustaining improvement to my current product, or am I creating something that serves a new need?" Both are valid, but they require different strategies and different success metrics. - -## Related - -- [[the-saas-metric-that-matters]] -- [[ai-wont-replace-thinking]] -- [[open-source-as-marketing]] -- [[b2b-content-is-trust-not-traffic]] -- [[note-zero-to-one]] -- [[note-the-lean-startup]] -- [[note-good-strategy-bad-strategy]] -- [[topic-saas-business]] -- [[topic-ai-ml]] -- [[topic-content-strategy]] diff --git a/demo-vault-v2/note-the-lean-startup.md b/demo-vault-v2/note-the-lean-startup.md deleted file mode 100644 index ef017633..00000000 --- a/demo-vault-v2/note-the-lean-startup.md +++ /dev/null @@ -1,44 +0,0 @@ ---- -aliases: ["The Lean Startup"] -Is A: Note -Author: "Eric Ries" -Topics: ["[[topic-saas-business]]"] -URL: "https://example.com/lean-startup" ---- -# The Lean Startup -*Eric Ries* - -Ries's contribution is the formalization of what many successful entrepreneurs do intuitively: treat every business idea as a hypothesis, test it with the minimum viable product (MVP), measure the results with actionable metrics, and iterate based on what you learn. The Build-Measure-Learn feedback loop is the book's core framework, and the key insight is that the goal is not to build a perfect product but to learn as quickly as possible whether your assumptions are correct. Speed of learning, not speed of building, is the competitive advantage. - -The concept of validated learning is perhaps the book's most durable contribution. Instead of measuring progress by lines of code written or features shipped, Ries argues that startups should measure progress by the validated learnings they have accumulated. A validated learning is a rigorous demonstration (through data, not opinion) that a hypothesis about the business is true or false. This shifts the founder's mindset from "build more, ship faster" to "learn faster, waste less." For a newsletter business, this means treating each new format, topic, or distribution experiment as a hypothesis to be validated, not a commitment to be maintained. - -While the lean startup methodology has become mainstream to the point of being cliched, the underlying principles remain sound and underappreciated. Most creators and founders still default to "build it and hope" rather than systematically testing their assumptions. The concept of the pivot (a structured course correction based on validated learning) is also valuable: it gives you permission to change direction without feeling like you failed, as long as the change is driven by evidence rather than impulse. The book's weakness is its overemphasis on metrics and speed at the expense of craft and vision, but used as one tool among many, the lean startup framework remains essential. - -## Key takeaways - -- Build-Measure-Learn: the goal is to complete this loop as quickly as possible, minimizing time and resources wasted on unvalidated ideas -- The MVP (minimum viable product) is the smallest thing you can build to test your most important assumption -- it is a learning tool, not a product -- Validated learning is the only meaningful measure of progress for an early-stage venture -- vanity metrics (pageviews, downloads, signups) are misleading without context -- Actionable metrics (metrics that inform a specific decision) are more useful than vanity metrics (numbers that make you feel good but do not guide action) -- A pivot is a structured change in strategy without a change in vision -- it is driven by evidence, not panic -- Innovation accounting: measure progress toward a validated business model, not just product milestones -- The methodology applies beyond startups -- any creative or business endeavor under uncertainty benefits from faster feedback loops - -## How I apply this - -- Every time I try a new newsletter format (a reader Q&A edition, a data-driven deep dive, a guest co-write), I treat it as an MVP experiment. I define what I am testing (e.g., "Will reader engagement increase with a Q&A format?"), set a specific metric to measure (reply rate, click-through rate), and make a keep/kill decision based on the results rather than my intuition. -- I distinguish between vanity metrics (subscriber count, social media impressions) and actionable metrics (open rate trends, paid conversion rate, reply rate) in my monthly reviews. The vanity metrics feel good but do not inform decisions; the actionable metrics tell me whether I am actually serving my audience well. -- The pivot concept has been valuable for navigating content strategy changes. When I shifted my newsletter's focus from broad tech commentary to a narrower niche, I framed it as a pivot based on validated learning (engagement data showed the niche content performed 3x better) rather than as a failure of the original strategy. - -## Related - -- [[the-saas-metric-that-matters]] -- [[small-teams-scale-through-systems]] -- [[b2b-content-is-trust-not-traffic]] -- [[newsletter-growth-is-about-trust]] -- [[note-the-mom-test]] -- [[note-the-innovators-dilemma]] -- [[note-zero-to-one]] -- [[note-good-strategy-bad-strategy]] -- [[topic-saas-business]] -- [[topic-product-management]] diff --git a/demo-vault-v2/note-the-mom-test.md b/demo-vault-v2/note-the-mom-test.md deleted file mode 100644 index a75f268c..00000000 --- a/demo-vault-v2/note-the-mom-test.md +++ /dev/null @@ -1,44 +0,0 @@ ---- -aliases: ["The Mom Test"] -Is A: Note -Author: "Rob Fitzpatrick" -Topics: ["[[topic-saas-business]]"] -URL: "https://example.com/mom-test" ---- -# The Mom Test -*Rob Fitzpatrick* - -The Mom Test is the most practical book on customer research I have read. The title comes from a simple observation: if you ask your mom "Do you think my business idea is good?" she will say yes, because she loves you and wants to be supportive. The same is true of almost everyone you ask about your idea -- people are polite, and they will tell you what you want to hear. Fitzpatrick's solution is to never ask about your idea at all. Instead, ask about their life, their problems, their behavior, and their past actions. These are facts that are hard to lie about, and they give you the real information you need to validate (or invalidate) your assumptions. - -The three rules of the Mom Test are: talk about their life instead of your idea, ask about specifics in the past instead of generics or opinions about the future, and talk less and listen more. These rules sound simple but require significant discipline to follow. The natural instinct when you are excited about an idea is to pitch it and seek validation. Fitzpatrick argues this is worse than useless -- it gives you false confidence and wastes time. The counterintuitive move is to approach conversations with genuine curiosity about the other person's reality, not with an agenda to prove your idea is good. - -For anyone running a content business, these principles apply directly to understanding your audience. When a reader says "I love your newsletter," that is a compliment, not data. When they say "I forwarded last week's edition to three colleagues because the framework for evaluating SaaS metrics saved us two hours in our board prep," that is data. The specificity and the past behavior are what matter. Fitzpatrick's framework has changed how I think about reader feedback, audience surveys, and sponsorship conversations -- I now optimize for learning about real behavior rather than collecting opinions. - -## Key takeaways - -- Never ask people if your idea is good -- they will lie to be polite, and you will get false validation -- Talk about their life, not your idea: ask about real problems, real behaviors, and real spending patterns -- Ask about the past, not the future: "What did you do last time this happened?" is far more reliable than "Would you use this?" -- Compliments are not data: "That sounds great!" tells you nothing about whether someone will actually pay for or use your product -- The most important signal is commitment: will someone give you time, money, or reputation to get your product? -- Keep conversations short and specific -- a 15-minute focused conversation yields more insight than an hour of unfocused chat -- Bad customer conversations are not just unhelpful; they are actively harmful because they create false confidence - -## How I apply this - -- When I survey readers about potential new content formats or products, I follow the Mom Test rules. Instead of asking "Would you pay for a premium tier?" I ask "Tell me about the last time you paid for a newsletter subscription. What made you decide to do it? What problem was it solving?" The answers reveal genuine willingness-to-pay patterns rather than hypothetical enthusiasm. -- In sponsor conversations, I apply the same principle. Instead of asking "Does this sound like a good fit for your brand?" I ask "Walk me through how you evaluated the last three sponsorships you purchased. What worked? What did not? What metrics did your team use?" This gives me real information about their decision-making process rather than polite interest. -- I use commitment as my signal for reader interest rather than verbal enthusiasm. When readers ask to be notified about a product launch, that is moderate signal. When they prepay or share the waitlist link with their network, that is strong signal. This distinction has prevented me from overinvesting in products that generated excitement but not actual demand. - -## Related - -- [[b2b-content-is-trust-not-traffic]] -- [[newsletter-growth-is-about-trust]] -- [[the-saas-metric-that-matters]] -- [[the-real-job-of-a-newsletter]] -- [[note-the-lean-startup]] -- [[note-never-split-difference]] -- [[note-thinking-in-bets]] -- [[topic-saas-business]] -- [[topic-product-management]] -- [[topic-b2b-marketing]] diff --git a/demo-vault-v2/note-the-obstacle-is-the-way.md b/demo-vault-v2/note-the-obstacle-is-the-way.md deleted file mode 100644 index 686baaa8..00000000 --- a/demo-vault-v2/note-the-obstacle-is-the-way.md +++ /dev/null @@ -1,43 +0,0 @@ ---- -aliases: ["The Obstacle Is the Way"] -Is A: Note -Author: "Ryan Holiday" -Topics: ["[[topic-mental-health]]"] -URL: "https://example.com/obstacle" ---- -# The Obstacle Is the Way -*Ryan Holiday* - -Holiday draws on Stoic philosophy, particularly Marcus Aurelius's Meditations, to argue that obstacles are not impediments to the path -- they are the path. The book is organized around three disciplines: perception (how you see the obstacle), action (how you respond to it), and will (how you endure what you cannot change). The core idea is that every difficulty contains within it an opportunity for growth, learning, or strategic advantage, and that the practice of reframing obstacles as opportunities is not naive optimism but a practical skill that can be developed through deliberate effort. - -The perception discipline is the most immediately actionable. Holiday argues that most of our suffering comes not from the obstacle itself but from our interpretation of it. A product launch that fails is not a catastrophe -- it is information. A subscriber wave that unsubscribes is not a rejection -- it is feedback about product-market fit. A competitor entering your niche is not a threat -- it is validation of the market. This is not about ignoring reality or pretending everything is fine; it is about separating objective facts from emotional interpretation so you can respond rationally rather than reactively. - -The historical examples Holiday uses (from Marcus Aurelius to Amelia Earhart to Steve Jobs) make the abstract principles concrete, but the real test is applying them to your own life. For a solo founder, the Stoic framework is particularly valuable because you lack the support systems that come with a large organization. When things go wrong, there is no VP of Operations to handle the crisis or HR department to manage the fallout. You are the one who must see clearly, act decisively, and endure the uncertainty. Holiday's framework provides a mental operating system for doing exactly that, not by eliminating difficulty but by transmuting it into fuel. - -## Key takeaways - -- The obstacle is not in the way -- it is the way. Every difficulty contains an opportunity for growth or advantage -- Perception: separate objective facts from emotional interpretation to see the obstacle clearly rather than reactively -- Action: focus on what you can control and take disciplined, persistent action rather than waiting for conditions to improve -- Will: endure what you cannot change with equanimity, knowing that some obstacles can only be outlasted, not solved -- Amor fati (love of fate): the practice of not merely accepting difficulty but embracing it as an essential part of your journey -- Premortem thinking: imagining what could go wrong before it happens reduces the emotional shock when it does -- Obstacle reframing is a skill that improves with practice -- like a muscle, it gets stronger the more you use it - -## How I apply this - -- When a major sponsor cancelled unexpectedly, my initial reaction was panic. Applying Holiday's perception discipline, I separated the facts (revenue reduction, need to find replacement) from the story I was telling myself (my newsletter is failing, sponsors do not see value). The facts were manageable; the story was paralyzing. Addressing the facts without the emotional overlay led to a much faster and more effective response. -- I use premortem thinking before every major decision: product launches, content pivots, pricing changes. By imagining failure scenarios in advance, I can prepare contingency plans and reduce the emotional impact if things go wrong. This does not prevent failure, but it makes failure less disorienting. -- The amor fati concept has become a daily practice for me. When I encounter a problem -- a technical issue, a negative review, a competitive threat -- I try to ask "how can I use this?" before asking "how can I fix this?" Often the obstacle itself reveals an opportunity that would not have been visible otherwise. - -## Related - -- [[on-founder-energy-management]] -- [[the-two-types-of-hard]] -- [[cycling-teaches-patience]] -- [[on-consistency-in-creative-work]] -- [[note-man-search-for-meaning]] -- [[note-on-the-shortness-of-life]] -- [[note-the-courage-to-be-disliked]] -- [[note-thinking-in-bets]] -- [[topic-mental-health]] diff --git a/demo-vault-v2/note-the-willpower-instinct.md b/demo-vault-v2/note-the-willpower-instinct.md deleted file mode 100644 index 26f0a816..00000000 --- a/demo-vault-v2/note-the-willpower-instinct.md +++ /dev/null @@ -1,44 +0,0 @@ ---- -aliases: ["The Willpower Instinct"] -Is A: Note -Author: "Kelly McGonigal" -Topics: ["[[topic-mental-health]]"] -URL: "https://example.com/willpower" ---- -# The Willpower Instinct -*Kelly McGonigal* - -McGonigal, a health psychologist at Stanford, presents willpower not as a moral virtue but as a physiological resource -- a biological capacity that depletes with use, fluctuates with physical state, and can be strengthened through specific practices. The book reframes every "willpower failure" as a biology problem rather than a character defect. When you reach for your phone instead of writing, when you skip a workout, when you eat poorly under stress -- these are not failures of discipline but predictable responses from a nervous system that prioritizes short-term comfort over long-term goals. Understanding this biology is the first step to working with it rather than against it. - -The "pause and plan" response is the book's central concept. While the "fight or flight" response mobilizes the body for immediate action, the "pause and plan" response slows you down, directs blood to the prefrontal cortex, and gives you the cognitive space to make a deliberate choice rather than an impulsive one. McGonigal identifies specific factors that strengthen the pause-and-plan response: sleep (the single biggest factor), exercise, meditation, stable blood sugar, and stress management. Conversely, sleep deprivation, chronic stress, decision fatigue, and low blood sugar all undermine willpower by weakening the prefrontal cortex's ability to override impulse. - -For a founder managing their own energy and productivity without external accountability, this is essential knowledge. The implication is that willpower is not unlimited and should not be the primary mechanism for maintaining good habits. Instead, you should design your environment to reduce willpower demands (as James Clear also argues in Atomic Habits) and invest in the physical foundations that keep your willpower capacity high. Getting enough sleep, exercising regularly, managing stress, and structuring your most demanding work during your peak energy hours are not luxuries -- they are the infrastructure of sustainable productivity. - -## Key takeaways - -- Willpower is a physiological resource that depletes with use, not a fixed character trait -- treat it like a battery that needs recharging -- The "pause and plan" response is the biological mechanism of self-control: it slows you down and engages the prefrontal cortex -- Sleep is the single most important factor in willpower capacity -- even mild sleep deprivation significantly impairs self-control -- Stress triggers the fight-or-flight response, which undermines the pause-and-plan response -- chronic stress is willpower's worst enemy -- Decision fatigue is real: every decision you make depletes the same resource, so reduce trivial decisions through routines and automation -- Exercise, meditation, and stable blood sugar all strengthen the pause-and-plan response and increase willpower capacity -- Self-compassion after a willpower failure is more effective than self-criticism -- guilt and shame trigger the very stress response that undermines self-control - -## How I apply this - -- I schedule my highest-willpower tasks (writing, strategic thinking, difficult conversations) in the morning when my prefrontal cortex is freshest. Routine tasks that require little self-control (email, admin, content scheduling) go in the afternoon. This simple scheduling change has dramatically improved the quality of my deep work. -- I treat sleep as a non-negotiable productivity investment rather than a luxury. After reading this book, I committed to 7.5+ hours per night and stopped treating late-night work sessions as a sign of dedication. The improvement in my daytime focus, creativity, and willpower was immediate and measurable. -- I apply the self-compassion principle when I fail to follow through on a plan. Instead of beating myself up (which McGonigal shows triggers more stress and more impulsive behavior), I acknowledge the failure neutrally and recommit. This approach has paradoxically made me more disciplined, not less, because it breaks the shame-spiral that used to follow every slip. - -## Related - -- [[sleeping-more-is-a-superpower]] -- [[on-founder-energy-management]] -- [[training-load-and-knowledge-work]] -- [[on-consistency-in-creative-work]] -- [[note-atomic-habits]] -- [[note-deep-work]] -- [[note-the-obstacle-is-the-way]] -- [[topic-mental-health]] -- [[topic-sleep-recovery]] -- [[topic-productivity-systems]] diff --git a/demo-vault-v2/note-thinking-fast-and-slow.md b/demo-vault-v2/note-thinking-fast-and-slow.md deleted file mode 100644 index 62414246..00000000 --- a/demo-vault-v2/note-thinking-fast-and-slow.md +++ /dev/null @@ -1,44 +0,0 @@ ---- -aliases: ["Thinking, Fast and Slow"] -Is A: Note -Author: "Daniel Kahneman" -Topics: ["[[topic-productivity-systems]]"] -URL: "https://example.com/thinking" ---- -# Thinking, Fast and Slow -*Daniel Kahneman* - -Kahneman's magnum opus synthesizes decades of research in behavioral economics and cognitive psychology into a framework built around two systems of thinking. System 1 is fast, intuitive, and automatic -- it is the system that recognizes faces, completes familiar phrases, and generates gut feelings. System 2 is slow, deliberate, and effortful -- it is the system that solves math problems, evaluates arguments, and makes careful decisions. The central insight is that System 1 does most of our thinking, and it is both remarkably efficient and systematically biased. We believe we are making rational decisions, but we are usually running on heuristics that work well enough most of the time and fail spectacularly in predictable ways. - -The catalog of cognitive biases Kahneman documents is essential reading for anyone making decisions under uncertainty -- which is to say, every founder and creator. Anchoring (being disproportionately influenced by the first number you hear), the availability heuristic (judging probability by how easily examples come to mind), loss aversion (feeling losses roughly twice as strongly as equivalent gains), and the planning fallacy (systematically underestimating the time and cost of future tasks) are not occasional errors but permanent features of human cognition. You cannot eliminate them, but you can learn to recognize and mitigate them. - -For a content creator, the implications run in two directions. First, understanding these biases improves your own decision-making: pricing, product strategy, time estimation, and investment decisions are all distorted by predictable biases. Second, understanding how your audience's minds work makes you a more effective communicator. Framing effects (how you present information matters as much as the information itself), the peak-end rule (people remember the most intense moment and the ending), and narrative bias (people prefer stories to statistics) are all tools for writing more engaging, more memorable content. The ethical obligation is to use these tools to serve your audience, not to manipulate them. - -## Key takeaways - -- System 1 (fast, intuitive) handles most thinking; System 2 (slow, deliberate) is engaged only when System 1 encounters something it cannot handle -- Anchoring: the first number or reference point you encounter disproportionately influences your judgment, even when it is irrelevant -- Loss aversion: losses feel roughly twice as painful as equivalent gains feel pleasurable, which makes people irrationally risk-averse -- The planning fallacy: we systematically underestimate the time, cost, and risk of future projects -- the "outside view" (looking at similar past projects) is the corrective -- Framing effects: how information is presented matters as much as the information itself -- the same data framed as a gain vs. a loss produces different decisions -- WYSIATI ("What You See Is All There Is"): System 1 creates coherent stories from limited information, leading to overconfidence -- The peak-end rule: people judge experiences primarily by their most intense moment and their ending, not by the average or the duration - -## How I apply this - -- I use the planning fallacy correction in all my project estimates. Whenever I think a newsletter edition will take 3 hours to write, I multiply by 1.5 and plan for 4.5 hours. This "outside view" adjustment has made my scheduling far more realistic and reduced the stress of running behind. -- I apply framing effects consciously in my newsletter writing. When presenting a counterintuitive finding, I lead with the framing that creates the most cognitive tension (e.g., "Most of what you believe about productivity is backwards") because that engages System 2 and makes the reader slow down and think rather than skimming on System 1 autopilot. -- Loss aversion awareness has improved my pricing and business decisions. When evaluating whether to drop an underperforming product, I ask "Would I start this product today if it did not already exist?" rather than "Should I keep this product?" The reframing eliminates the loss aversion that biases toward maintaining the status quo. - -## Related - -- [[ai-wont-replace-thinking]] -- [[index-funds-and-intellectual-humility]] -- [[the-compound-effect-in-knowledge-work]] -- [[knowledge-management-is-not-filing]] -- [[note-thinking-in-bets]] -- [[note-how-minds-change]] -- [[note-the-willpower-instinct]] -- [[note-never-split-difference]] -- [[topic-productivity-systems]] -- [[topic-personal-finance]] diff --git a/demo-vault-v2/note-thinking-in-bets.md b/demo-vault-v2/note-thinking-in-bets.md deleted file mode 100644 index bfa639da..00000000 --- a/demo-vault-v2/note-thinking-in-bets.md +++ /dev/null @@ -1,44 +0,0 @@ ---- -aliases: ["Thinking in Bets"] -Is A: Note -Author: "Annie Duke" -Topics: ["[[topic-personal-finance]]"] -URL: "https://example.com/thinking-bets" ---- -# Thinking in Bets -*Annie Duke* - -Duke, a former professional poker player turned decision scientist, builds her entire book around one insight: the quality of a decision and the quality of its outcome are different things, and confusing the two -- a mistake she calls "resulting" -- is the single most common error in human reasoning. A good decision made with the best available information can produce a bad outcome (because the world is uncertain), and a bad decision made recklessly can produce a good outcome (because sometimes you get lucky). If you judge decisions by their outcomes, you learn the wrong lessons: you abandon good strategies after a run of bad luck and double down on bad strategies after a run of good luck. - -This framework is critical for anyone operating under uncertainty, which includes every founder, investor, and creator. When a newsletter edition underperforms, the instinct is to assume the content was bad. But maybe the content was excellent and the timing was wrong, or the subject line misfired, or there was a competing news event. Conversely, when an edition goes viral, the instinct is to assume you cracked the code. But maybe you just got lucky with the algorithm or the topic happened to catch a cultural moment. Duke argues that the disciplined response is to evaluate the decision process separately from the outcome and to learn from both. - -Duke also introduces the concept of "thinking in bets" -- framing every belief and every decision as a bet with a probability attached. Instead of saying "this strategy will work," you say "I am 70% confident this strategy will work, and here is what I would need to see to change my mind." This probabilistic thinking reduces overconfidence, encourages intellectual humility, and makes it easier to update your beliefs when new evidence arrives. For someone making dozens of decisions a week about content, product, and business strategy, this is a powerful cognitive operating system. - -## Key takeaways - -- "Resulting" -- judging decisions by outcomes -- is the most common reasoning error and leads to learning the wrong lessons -- Good decisions can have bad outcomes, and bad decisions can have good outcomes, because the world is inherently uncertain -- Think of every decision as a bet: what is your confidence level, and what evidence would change your mind? -- Probabilistic thinking reduces overconfidence and makes belief updating more natural and less ego-threatening -- Outcome fielding: after any result, deliberately separate the contribution of decision quality from the contribution of luck -- A "decision group" (trusted peers who challenge your reasoning) is one of the most effective tools for improving decision quality -- The goal is not to be right all the time but to be well-calibrated -- your 70% confident predictions should come true about 70% of the time - -## How I apply this - -- After every major business decision (content pivot, pricing change, product launch), I do a decision journal entry that records: what I decided, why, what alternatives I considered, and what my confidence level was. When the outcome arrives, I compare it to the journal entry. This practice has helped me distinguish between decisions that were genuinely flawed and decisions that were sound but unlucky. -- I use probabilistic language in my strategic planning. Instead of "we will launch in Q2," I write "I am 80% confident we will launch in Q2, with the main risk being [X]." This forces me to think explicitly about uncertainty and plan for contingencies rather than operating on false certainty. -- When a newsletter edition performs unusually well or poorly, I resist the urge to immediately draw conclusions. Instead, I wait for a sample of 3-5 editions before changing my approach. This prevents me from overreacting to noise and ensures that any strategic change is based on a meaningful pattern rather than a single data point. - -## Related - -- [[index-funds-and-intellectual-humility]] -- [[investing-in-yourself-vs-markets]] -- [[the-saas-metric-that-matters]] -- [[ai-wont-replace-thinking]] -- [[note-thinking-fast-and-slow]] -- [[note-good-strategy-bad-strategy]] -- [[note-the-lean-startup]] -- [[topic-personal-finance]] -- [[topic-saas-business]] -- [[topic-product-management]] diff --git a/demo-vault-v2/note-traffic-secrets.md b/demo-vault-v2/note-traffic-secrets.md deleted file mode 100644 index f3b831a4..00000000 --- a/demo-vault-v2/note-traffic-secrets.md +++ /dev/null @@ -1,45 +0,0 @@ ---- -aliases: ["Traffic Secrets"] -Is A: Note -Author: "Russell Brunson" -Topics: ["[[topic-newsletter-growth]]"] -URL: "https://example.com/traffic" ---- -# Traffic Secrets -*Russell Brunson* - -Brunson's book is the most practical guide I have found on the mechanics of audience growth and top-of-funnel thinking. While the language and framing lean heavily into direct-response marketing (which can feel aggressive to someone from a content/editorial background), the underlying frameworks are genuinely useful. The core idea is that traffic (attention) already exists -- your dream customers are already congregating somewhere online. Your job is not to "create" traffic but to identify where your ideal audience gathers, earn the right to be seen there, and give them a compelling reason to enter your world (email list, community, product). - -The "Dream 100" concept is the book's most actionable framework. Identify the 100 people, publications, podcasts, communities, and platforms where your ideal audience already pays attention. Then systematically build relationships with those gatekeepers through genuine engagement, contribution, and collaboration. This is not about cold outreach or growth hacking -- it is about showing up consistently in the places your audience already trusts. For a newsletter operator, this means guest appearances on relevant podcasts, writing guest posts for complementary publications, and engaging authentically in communities where your potential readers spend time. - -The hook-story-offer framework is also valuable for thinking about any piece of content or marketing. Every piece needs a hook (something that stops the scroll), a story (something that creates connection and builds trust), and an offer (a clear next step for the reader). Brunson argues that most people fail at traffic not because they lack content but because their hooks are weak -- they never earn the initial attention. This is directly applicable to newsletter subject lines, social media posts, and landing pages. The framework is simple enough to internalize and use daily without becoming formulaic. - -## Key takeaways - -- Traffic already exists -- your job is to find where your ideal audience congregates and earn the right to be seen there -- The Dream 100: identify the top 100 people, publications, and platforms where your audience pays attention, and build relationships systematically -- Hook-story-offer: every piece of content needs something that captures attention (hook), builds connection (story), and provides a clear next step (offer) -- "Work your way in, then buy your way in": start with organic relationship building, then use paid amplification once you know what works -- Funnel thinking: every piece of traffic should lead somewhere -- a random visitor should have a clear path to becoming a subscriber, then a customer -- Platform diversification is critical: do not build your entire audience on rented land (social platforms); always drive toward owned channels (email list) -- Consistency in showing up where your audience gathers is more important than any single viral moment - -## How I apply this - -- I maintain a "Dream 50" list (scaled down from 100) of podcasts, newsletters, and communities where my ideal readers spend time. Each week, I dedicate two hours to engaging with these communities -- commenting on posts, sharing useful insights, and building genuine relationships. This has been my most effective organic growth channel, generating roughly 40% of new subscribers. -- I apply the hook-story-offer framework to every newsletter subject line and opening paragraph. The subject line is the hook (it must create enough curiosity to earn the open), the first paragraph is the story (it must build enough connection to earn the read), and the call-to-action is the offer (it must provide a clear, valuable next step). -- I prioritize email list growth over social media following, following Brunson's principle of owning your audience rather than renting it. Social media is a distribution channel, not a destination. Every social post, guest appearance, and collaboration is designed to drive people toward the newsletter, which I control. - -## Related - -- [[newsletter-growth-is-about-trust]] -- [[b2b-content-is-trust-not-traffic]] -- [[the-real-job-of-a-newsletter]] -- [[open-source-as-marketing]] -- [[podcasting-is-relationship-building]] -- [[note-show-your-work]] -- [[note-the-mom-test]] -- [[note-never-split-difference]] -- [[topic-newsletter-growth]] -- [[topic-b2b-marketing]] -- [[topic-content-strategy]] diff --git a/demo-vault-v2/note-zero-to-one.md b/demo-vault-v2/note-zero-to-one.md deleted file mode 100644 index cb15f6f1..00000000 --- a/demo-vault-v2/note-zero-to-one.md +++ /dev/null @@ -1,44 +0,0 @@ ---- -aliases: ["Zero to One"] -Is A: Note -Author: "Peter Thiel" -Topics: ["[[topic-saas-business]]"] -URL: "https://example.com/zero-to-one" ---- -# Zero to One -*Peter Thiel* - -Thiel's central distinction is between going from 0 to 1 (creating something genuinely new) and going from 1 to n (copying something that already works). Most businesses are 1-to-n -- incremental improvements on existing ideas. The truly transformative businesses, Thiel argues, are 0-to-1: they discover or create something that did not exist before. The mechanism for finding these opportunities is "secrets" -- important truths about the world that most people do not know or do not agree with. If you can identify a secret and build a business around it, you create a monopoly (in the positive sense) rather than competing in a commodity market. - -The "competition is for losers" framing is the most provocative idea in the book. Thiel argues that perfect competition is not a desirable state but a trap: in a perfectly competitive market, no one makes above-average returns. The goal should be to build a small monopoly -- a business that does something so unique that it has no direct competitors. For a newsletter operator, this means finding a niche where your specific combination of expertise, perspective, and voice is irreplaceable. The goal is not to be the best tech newsletter; it is to be the only newsletter that offers your particular combination of engineering depth, management insight, and indie founder perspective. - -Where I diverge from Thiel is his emphasis on grand, venture-scale ambition. Not every valuable business needs to be a monopoly that dominates a market. But the underlying principle -- differentiate or die -- is universally applicable. The newsletters, products, and creators that thrive are the ones that have found their "secret": a unique perspective, a distinctive format, an audience connection that others cannot easily replicate. The ones that struggle are the ones competing on the same dimensions as everyone else. Thiel's framework is a useful lens even if you disagree with his specific conclusions about scale and competition. - -## Key takeaways - -- 0-to-1 innovation (creating something new) is fundamentally different from 1-to-n innovation (copying what exists) and requires different thinking -- "Secrets" -- important truths that most people do not know or agree with -- are the foundation of unique, defensible businesses -- Competition is for losers: in a perfectly competitive market, no one earns above-average returns. The goal is to build a small monopoly through differentiation -- Start with a small market you can dominate, then expand -- trying to address a large market from day one is almost always a mistake -- Definite optimism (having a specific plan to create a better future) is more productive than indefinite optimism (assuming the future will be better without knowing how) -- The power law applies to everything: a small number of investments, projects, or bets will produce the vast majority of your returns -- "What important truth do very few people agree with you on?" is the most valuable question a founder can answer - -## How I apply this - -- I use Thiel's "secret" question as a strategic filter. My newsletter's "secret" is that most engineering leadership content is written by people who have never built and shipped a product independently. My combination of hands-on engineering, management experience, and indie founder perspective is my differentiator, and I orient all content decisions around protecting and deepening that differentiation. -- The "start small and dominate" principle has shaped my growth strategy. Rather than trying to reach all engineers, I focus on a specific niche (engineering leaders at growing startups) and aim to be the default newsletter for that audience. Expansion comes from depth, not breadth. -- I apply the power law to my content experiments. Not all newsletter editions will perform equally, and that is expected. Instead of trying to make every edition equally good, I invest disproportionate effort in the editions that have the potential to be exceptional -- deep dives, original frameworks, and pieces that only I could write. These "power law" editions drive the majority of growth and reputation. - -## Related - -- [[the-saas-metric-that-matters]] -- [[b2b-content-is-trust-not-traffic]] -- [[small-teams-scale-through-systems]] -- [[open-source-as-marketing]] -- [[note-the-innovators-dilemma]] -- [[note-good-strategy-bad-strategy]] -- [[note-the-lean-startup]] -- [[note-the-hard-thing-about-hard-things]] -- [[topic-saas-business]] -- [[topic-content-strategy]] diff --git a/demo-vault-v2/note.md b/demo-vault-v2/note.md deleted file mode 100644 index 0a81fe74..00000000 --- a/demo-vault-v2/note.md +++ /dev/null @@ -1,7 +0,0 @@ ---- -Is A: Type ---- - -# Note - -A Note is a general-purpose document — research notes, meeting notes, strategy docs, or anything that doesn't fit a more specific type. diff --git a/demo-vault-v2/note/final-title-r-renamed.md b/demo-vault-v2/note/final-title-r-renamed.md deleted file mode 100644 index e784cc98..00000000 --- a/demo-vault-v2/note/final-title-r-renamed.md +++ /dev/null @@ -1,10 +0,0 @@ ---- -title: Final Title R Renamed -type: Note -status: Active -Trashed: true -Trashed at: '2026-03-13' ---- -# Final Title R Renamed - -[[Maenamed diff --git a/demo-vault-v2/note/final-title-r.md b/demo-vault-v2/note/final-title-r.md deleted file mode 100644 index a54a40dc..00000000 --- a/demo-vault-v2/note/final-title-r.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Final Title R -type: Note -status: Active ---- -# Final Title R - -[[Maenamed diff --git a/demo-vault-v2/note/final-title-renamed-renamed.md b/demo-vault-v2/note/final-title-renamed-renamed.md deleted file mode 100644 index 20c448c7..00000000 --- a/demo-vault-v2/note/final-title-renamed-renamed.md +++ /dev/null @@ -1,10 +0,0 @@ ---- -title: Final Title Renamed -type: Note -status: Active ---- -# Final Title Renamed Renamed - -Snippet test content 1773606979013 - -Snippet test content 1773607012674 diff --git a/demo-vault-v2/note/untitled-save-no-rename-te.md b/demo-vault-v2/note/untitled-save-no-rename-te.md deleted file mode 100644 index 51a3e604..00000000 --- a/demo-vault-v2/note/untitled-save-no-rename-te.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled Save No Rename Te -type: Note -status: Active ---- -# Untitled Save No Rename Te - -[[Mast 2 diff --git a/demo-vault-v2/note/untitled-save-no-rename-test-2.md b/demo-vault-v2/note/untitled-save-no-rename-test-2.md deleted file mode 100644 index fb1cbf1f..00000000 --- a/demo-vault-v2/note/untitled-save-no-rename-test-2.md +++ /dev/null @@ -1,6 +0,0 @@ ---- -title: Untitled Save No Rename Test 2 -type: Note -status: Active ---- -# Untitled Save No Rename Test 2 diff --git a/demo-vault-v2/note/untitled-save-no-rename-test.md b/demo-vault-v2/note/untitled-save-no-rename-test.md deleted file mode 100644 index 48f3ee39..00000000 --- a/demo-vault-v2/note/untitled-save-no-rename-test.md +++ /dev/null @@ -1,6 +0,0 @@ ---- -title: Untitled Save No Rename Test -type: Note -status: Active ---- -# Untitled Save No Rename Test diff --git a/demo-vault-v2/note/untitled-tes-renamed.md b/demo-vault-v2/note/untitled-tes-renamed.md deleted file mode 100644 index 9498d7c1..00000000 --- a/demo-vault-v2/note/untitled-tes-renamed.md +++ /dev/null @@ -1,10 +0,0 @@ ---- -title: Untitled Tes Renamed -type: Note -status: Active ---- -# Untitled Tes Renamed - -[[Mat Note ABC - -[[Ma diff --git a/demo-vault-v2/note/untitled-test-note-abc-2.md b/demo-vault-v2/note/untitled-test-note-abc-2.md deleted file mode 100644 index 76b75530..00000000 --- a/demo-vault-v2/note/untitled-test-note-abc-2.md +++ /dev/null @@ -1,6 +0,0 @@ ---- -title: Untitled Test Note ABC 2 -type: Note -status: Active ---- -# Untitled Test Note ABC 2 diff --git a/demo-vault-v2/note/untitled-test-note-abc-3.md b/demo-vault-v2/note/untitled-test-note-abc-3.md deleted file mode 100644 index 0bf7612d..00000000 --- a/demo-vault-v2/note/untitled-test-note-abc-3.md +++ /dev/null @@ -1,6 +0,0 @@ ---- -title: Untitled Test Note ABC 3 -type: Note -status: Active ---- -# Untitled Test Note ABC 3 diff --git a/demo-vault-v2/note/untitled-test-note-abc-renamed.md b/demo-vault-v2/note/untitled-test-note-abc-renamed.md deleted file mode 100644 index 768f5b39..00000000 --- a/demo-vault-v2/note/untitled-test-note-abc-renamed.md +++ /dev/null @@ -1,10 +0,0 @@ ---- -title: Untitled Test Note ABC Renamed -type: Note -status: Active -Trashed: true -Trashed at: '2026-03-13' ---- -# Untitled Test Note ABC Renamed - -[[Ma diff --git a/demo-vault-v2/on-consistency-in-creative-work.md b/demo-vault-v2/on-consistency-in-creative-work.md deleted file mode 100644 index 12f366a5..00000000 --- a/demo-vault-v2/on-consistency-in-creative-work.md +++ /dev/null @@ -1,28 +0,0 @@ ---- -aliases: ["On Consistency in Creative Work"] -Is A: Evergreen -Topics: ["[[topic-writing]]", "[[topic-productivity-systems]]"] -Status: Published ---- -# On Consistency in Creative Work -The most counterintuitive lesson from 5 years of publishing weekly: the newsletters I agonized over for days are not consistently better than the ones I wrote in 3 hours. - -What does correlate with quality is freshness of thinking — whether I'm saying something I actually believe and find interesting, rather than something I think I should say. - -Consistency forces this freshness. When you have to ship every week, you can't hide behind a blank page. You develop a practice of noticing: what actually caught my attention this week? What made me change my mind? That noticing becomes the raw material. - -There is a mechanical explanation for why consistency works that has nothing to do with discipline or willpower. When you publish on a fixed schedule, you create a forcing function that makes you process your experiences into communicable ideas. Without the deadline, interesting observations accumulate in your head as vague impressions. With the deadline, those impressions become structured arguments, concrete examples, and clear recommendations. The newsletter does not just capture your thinking — it creates your thinking. I have lost count of the times I started writing a piece thinking I knew what I believed, only to discover halfway through that I actually believed something more nuanced or even contradictory. - -This is why I push back when people say they are "not ready" to start a newsletter or blog. The readiness comes from the doing, not from some prerequisite period of quiet reflection. Every writer I admire has told me some version of the same story: they did not start writing because they had something to say. They discovered what they had to say because they started writing. The consistency created the content, not the other way around. - -The risk of consistency is mechanical repetition — going through the motions of publishing without the genuine engagement that makes the work valuable. I have hit this several times with Refactoring, usually around the 6-8 month mark of a continuous streak. The antidote is not to break the streak but to change the input. Read something outside your domain. Have a conversation with someone who thinks differently. Travel. The consistency is the container; the input is the fuel. If the container is empty, the problem is not the container — it is that you have been consuming the same ideas for too long. - -## Key insight -Consistency in creative work is not primarily about discipline — it is about creating the conditions for thinking to happen. A fixed publishing schedule transforms vague impressions into concrete ideas, forces engagement with new material, and builds a compounding body of work. The common fear that consistency leads to lower quality is almost always wrong. What leads to lower quality is inconsistency, because without regular practice, every piece feels like starting from scratch rather than building on a foundation. - -## Related -- [[the-compound-effect-in-knowledge-work]] — Consistency is the mechanism through which knowledge work compounds -- [[writing-for-clarity-vs-writing-for-credit]] — Consistent writing practice develops the clarity muscle -- [[the-two-types-of-hard]] — Resistance to writing is usually the "hard of resistance," not skill gap -- [[ai-wont-replace-thinking]] — AI can accelerate consistent production but cannot replace the thinking that consistency forces -- [[procedure-weekly-newsletter]] — The practical procedure that maintains weekly consistency diff --git a/demo-vault-v2/on-founder-energy-management.md b/demo-vault-v2/on-founder-energy-management.md deleted file mode 100644 index 32f45ac0..00000000 --- a/demo-vault-v2/on-founder-energy-management.md +++ /dev/null @@ -1,28 +0,0 @@ ---- -aliases: ["On Founder Energy Management"] -Is A: Evergreen -Topics: ["[[topic-mental-health]]", "[[topic-productivity-systems]]"] -Status: Published ---- -# On Founder Energy Management -Most advice about founder productivity focuses on time management. But time is a renewable resource — you get 24 hours every day. Energy isn't. - -The founders I know who sustain high output for years are almost universally careful about energy: they protect sleep, have physical activity habits, and are selective about which meetings they take. Not because they're less dedicated, but because they've learned that a fresh 4-hour work block produces more than a tired 10-hour one. - -This isn't about self-care as a trend. It's about treating yourself as the primary asset in your company and investing accordingly. - -The energy management framework I have converged on after years of experimentation has three tiers. The first is physiological: sleep, exercise, nutrition. These are non-negotiable and should be treated as infrastructure, not luxuries. When I skip a morning ride or sleep less than 7 hours, the impact on my writing quality and decision-making is measurable within the same day. The second tier is cognitive: protecting deep work blocks, batching meetings, eliminating context switching. This is well-understood in theory but hard to execute because other people's urgencies constantly erode your schedule. The third tier is emotional: choosing which relationships and situations to invest emotional energy in, and which to deliberately limit. This is the tier most founders neglect, and it is often the one that causes burnout. - -The emotional tier deserves special attention because it is invisible in most productivity discourse. A single difficult conversation with a co-founder, investor, or employee can drain more energy than a full day of deep work. Founders who do not account for this end up mystified about why they are exhausted despite having a "good schedule." The schedule looks fine on paper, but it does not capture the emotional load of managing conflict, making difficult personnel decisions, or absorbing the anxiety of an uncertain fundraise. Acknowledging this cost is the first step to managing it. - -Running a content business is less emotionally volatile than running a venture-backed startup, but the energy management principles are identical. The weeks when Refactoring's content is best are always the weeks when I have slept well, exercised, and had enough unstructured time for ideas to develop. The weeks when the content feels forced are always the weeks when I sacrificed recovery for productivity. The correlation is so reliable that I now treat my energy state as a leading indicator of content quality and adjust my schedule accordingly. - -## Key insight -Energy, not time, is the binding constraint on founder productivity. Time management without energy management is like optimizing a factory's schedule without maintaining the machines. The most leveraged investments a founder can make are the ones that protect and restore energy: consistent sleep, regular physical activity, emotional boundary-setting, and the discipline to leave margin in the schedule. These investments feel unproductive in the moment but are the foundation on which all productive work depends. - -## Related -- [[sleeping-more-is-a-superpower]] — Sleep as the single most important energy management intervention -- [[cycling-teaches-patience]] — Physical activity as both energy management and a metaphor for sustainable pacing -- [[training-load-and-knowledge-work]] — The recovery model from athletics applied to cognitive work -- [[the-two-types-of-hard]] — Distinguishing between genuine difficulty and resistance caused by depleted energy -- [[recovery-week-in-training]] — Periodic recovery as a structural element of sustained performance diff --git a/demo-vault-v2/open-source-as-marketing.md b/demo-vault-v2/open-source-as-marketing.md deleted file mode 100644 index e19f3fa0..00000000 --- a/demo-vault-v2/open-source-as-marketing.md +++ /dev/null @@ -1,28 +0,0 @@ ---- -aliases: ["Open Source as Marketing"] -Is A: Evergreen -Topics: ["[[topic-open-source]]", "[[topic-developer-tools]]"] -Status: Published ---- -# Open Source as Marketing -The most successful developer tools companies have figured out something the traditional software industry took decades to learn: giving your software away isn't charity, it's distribution. - -HashiCorp, Elastic, Redis — all built massive developer adoption through open-source and monetized through enterprise features, support, and cloud hosting. The open-source version is a top-of-funnel lead generation engine. - -For developer tools, open source has become so effective that a closed-source tool now carries an implicit trust deficit it has to overcome. - -The economics of this model are worth examining in detail. Traditional software marketing requires spending money to acquire each user through ads, sales teams, or channel partnerships. Open-source marketing inverts this: the product distributes itself through GitHub stars, word of mouth, Stack Overflow answers, and blog posts by users solving real problems. Each user becomes a potential marketing channel. The cost of acquisition approaches zero at scale, which is why open-source developer tools companies can achieve adoption levels that would cost hundreds of millions in marketing spend through traditional channels. - -But the model is not without tension. The companies that pioneered open-source-as-marketing are now navigating the uncomfortable transition from community darling to revenue-generating business. Elastic's license change, Redis's shift to dual licensing, HashiCorp's move from MPL to BSL — these are all symptoms of the same problem: cloud providers can take the open-source product, offer it as a managed service, and capture the monetization opportunity without contributing back. The marketing benefit of open source is real, but so is the risk of building a business on infrastructure that your competitors can freely use. - -For smaller developer tools companies and indie hackers, the lesson is nuanced. Open source works brilliantly for distribution and trust-building, but the monetization strategy needs to be designed from the beginning, not bolted on later. The companies that navigate this well are the ones that clearly separate the open-source community value from the commercial enterprise value — things like team collaboration, SSO, audit logs, and managed hosting. The ones that struggle are the ones that open-sourced too much of the commercial value and then had to claw it back, damaging community trust in the process. - -## Key insight -Open source is the most efficient distribution mechanism for developer tools ever invented, but it is a marketing strategy, not a business model. The distinction matters enormously. Companies that treat open source as their business model end up in a trap where they have massive adoption and no revenue. Companies that treat it as a marketing strategy — with a clear, pre-planned path to commercial value — build sustainable businesses on top of genuine community goodwill. The key decision is what to open-source (everything the individual developer needs) and what to keep commercial (everything the enterprise procurement team requires). - -## Related -- [[the-saas-metric-that-matters]] — NRR is especially critical for open-source companies converting free users to paid -- [[small-teams-scale-through-systems]] — Open-source communities are a system that scales without headcount -- [[b2b-content-is-trust-not-traffic]] — Open source builds trust with developers the same way content builds trust with buyers -- [[topic-open-source]] — Broader observations on open source -- [[topic-developer-tools]] — The developer tools market and its unique dynamics diff --git a/demo-vault-v2/person-adeel-khan.md b/demo-vault-v2/person-adeel-khan.md deleted file mode 100644 index 5c9ca44b..00000000 --- a/demo-vault-v2/person-adeel-khan.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -aliases: ["Adeel Khan"] -Is A: Person -Tier: "3rd 🥉" -Tags: ["Podcast Guest"] ---- -# Adeel Khan - -Staff engineer specializing in ML platform infrastructure at a large Bay Area tech company. Adeel joined the podcast to discuss the often-overlooked challenge of building reliable ML pipelines at scale, covering topics from feature stores to model serving and the organizational dynamics of platform teams. Luca connected with him through a mutual contact in the DevOps community on Twitter. - -## Notes - -- Extremely methodical communicator; breaks down complex ML infrastructure concepts into digestible analogies -- Strong opinions on the separation between ML research and ML engineering, advocates for dedicated platform teams -- Deeply interested in developer experience for data scientists, sees it as a largely unsolved problem -- Quiet on social media but maintains a well-regarded technical blog with infrequent, high-quality posts - -## Collaborations - -- [[24q3-podcast-season-2]] — recorded episode on ML infrastructure and platform engineering -- [[topic-ai-ml]] — primary topic area for his episode -- [[procedure-podcast-guest-outreach]] — sourced through DevOps Twitter community diff --git a/demo-vault-v2/person-alberto-ferro.md b/demo-vault-v2/person-alberto-ferro.md deleted file mode 100644 index 5e218e35..00000000 --- a/demo-vault-v2/person-alberto-ferro.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -aliases: ["Alberto Ferro"] -Is A: Person -Tier: "3rd 🥉" -Tags: ["Podcast Guest"] ---- -# Alberto Ferro - -Italian software engineer and author of a well-received book on software craftsmanship in the Italian tech community. Alberto appeared on the podcast to discuss code quality culture, testing strategies, and how to bring craftsmanship principles into fast-moving startup environments. Based in Bologna, he is active in the Italian software engineering conference circuit and co-organizes a local meetup on extreme programming. - -## Notes - -- Passionate about TDD to the point of being almost evangelical, but backs it up with practical experience -- Has a gift for explaining testing philosophy without being dogmatic; the episode resonated well with listeners -- Writes in both Italian and English, which gives him a unique bridge perspective on the Italian dev scene -- Recommended several useful books during the recording that Luca added to his reading list - -## Collaborations - -- [[24q1-podcast-season-1]] — recorded episode on code quality and testing culture -- [[topic-italian-startups]] — discussed the state of software engineering practices in Italy -- [[procedure-podcast-guest-outreach]] — introduced through the Italian tech conference network diff --git a/demo-vault-v2/person-alessandro-ferrari.md b/demo-vault-v2/person-alessandro-ferrari.md deleted file mode 100644 index 733f05cc..00000000 --- a/demo-vault-v2/person-alessandro-ferrari.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -aliases: ["Alessandro Ferrari"] -Is A: Person -Tier: "2nd 🥈" -Tags: ["Friend"] ---- -# Alessandro Ferrari - -Cycling buddy and close friend based in Milan. Alessandro works as a mechanical engineer at a mid-sized Italian manufacturing company but lives for weekends on the bike. He and Luca ride together most Saturdays and have completed several gran fondos across northern Italy, including the Maratona dles Dolomites and the Nove Colli. They met through a local cycling club about four years ago and quickly became regular training partners. - -## Notes - -- Incredibly strong climber, especially on long alpine ascents; Luca struggles to keep his wheel on anything over 8% -- Meticulous about bike setup and nutrition planning; always has a spreadsheet for race prep -- Good-natured and competitive without being annoying about it; the kind of riding partner who pushes you just enough -- Also into trail running, which he uses as cross-training during the off-season -- They often debrief rides over espresso at the same bar near Navigli - -## Collaborations - -- [[topic-cycling-training]] — regular training partner and race planning collaborator -- [[event-dinner-family]] — has joined a few of Luca and Giulia's casual dinner gatherings diff --git a/demo-vault-v2/person-andrea-colombo.md b/demo-vault-v2/person-andrea-colombo.md deleted file mode 100644 index 230b435a..00000000 --- a/demo-vault-v2/person-andrea-colombo.md +++ /dev/null @@ -1,21 +0,0 @@ ---- -aliases: ["Andrea Colombo"] -Is A: Person -Tier: "2nd 🥈" -Tags: ["Friend"] ---- -# Andrea Colombo - -Works in corporate finance at a large Italian bank in Milan. Andrea is Luca's go-to person for investment discussions and portfolio sanity checks. They met through mutual friends in the Milan tech-finance crossover scene and have maintained a steady friendship built around occasional dinners and WhatsApp threads about markets, ETFs, and macro trends. Andrea brings a grounded, institutional perspective that balances Luca's more startup-oriented worldview. - -## Notes - -- Has a rare ability to explain complex financial instruments in plain language without being condescending -- Conservative investor by nature, which makes him a good counterweight to Luca's more aggressive tech-stock instincts -- Curious about the indie hacking and content business model; asks genuinely good questions about it -- Reliable and consistent; the kind of friend who always follows up and remembers details from past conversations -- Wine enthusiast, particularly Piedmontese reds; always brings a great bottle to dinner - -## Collaborations - -- [[event-dinner-family]] — regular at Luca's dinner gatherings, always brings interesting conversation diff --git a/demo-vault-v2/person-andrea-provaglio.md b/demo-vault-v2/person-andrea-provaglio.md deleted file mode 100644 index 04887c4d..00000000 --- a/demo-vault-v2/person-andrea-provaglio.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -aliases: ["Andrea Provaglio"] -Is A: Person -Tier: "3rd 🥉" -Tags: ["Podcast Guest"] ---- -# Andrea Provaglio - -Agile coach, author, and organizational consultant based in Italy with extensive international experience. Andrea appeared on the podcast to discuss what agile really means beyond the buzzwords, drawing on decades of experience helping teams move past ceremonial Scrum toward genuine adaptive practices. He has worked with both startups and large enterprises across Europe and the US, and brings a systems-thinking perspective that is refreshingly grounded. - -## Notes - -- One of the most thoughtful guests on the topic of organizational culture; avoids simplistic frameworks -- Strongly critical of "Agile Industrial Complex" certifications and consultancies that miss the point -- Has a coaching background that shows in how he listens and asks questions; the conversation flowed naturally -- His writing on complexity theory applied to software teams influenced how Luca thinks about team dynamics - -## Collaborations - -- [[24q1-podcast-season-1]] — recorded episode on agile beyond the buzzwords -- [[topic-team-leadership]] — discussed team dynamics and adaptive organizations -- [[procedure-podcast-guest-outreach]] — connected through the Italian agile community diff --git a/demo-vault-v2/person-anna-fontana.md b/demo-vault-v2/person-anna-fontana.md deleted file mode 100644 index 7d60d1db..00000000 --- a/demo-vault-v2/person-anna-fontana.md +++ /dev/null @@ -1,20 +0,0 @@ ---- -aliases: ["Anna Fontana"] -Is A: Person -Tier: "3rd 🥉" -Tags: ["Friend"] ---- -# Anna Fontana - -Runs a small yoga and wellness studio near Luca's apartment in Milan. Giulia introduced them a couple of years ago, and while Luca is not a regular yoga practitioner, he and Giulia occasionally attend Anna's classes. Anna is warm, grounded, and has built a successful small business entirely through word of mouth and community connection, which Luca respects as a fellow indie business owner. - -## Notes - -- Entrepreneurial mindset despite not coming from a tech background; runs her studio lean and profitably -- Great at building community around her business; her retention rate is remarkably high -- Luca finds conversations with her refreshing precisely because they are outside the tech bubble -- Introduced Luca and Giulia to a few good restaurants in the neighborhood - -## Collaborations - -- [[event-dinner-family]] — occasional guest at neighborhood dinners with Luca and Giulia diff --git a/demo-vault-v2/person-anna-kowalski.md b/demo-vault-v2/person-anna-kowalski.md deleted file mode 100644 index fc66964c..00000000 --- a/demo-vault-v2/person-anna-kowalski.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -aliases: ["Anna Kowalski"] -Is A: Person -Tier: "3rd 🥉" -Tags: ["Sponsor"] ---- -# Anna Kowalski - -Sponsor contact at Vercel, managing their newsletter and podcast sponsorship programs across the European developer content ecosystem. Anna reached out after discovering Luca's podcast through organic developer community channels. She handles the partnership logistics professionally and is responsive, making the sponsorship process smooth and low-friction. - -## Notes - -- Very organized and proactive with campaign briefs; always provides clear deliverables and timelines -- Understands the developer audience well, which makes ad copy collaboration much easier than with generic marketing contacts -- Based in Poland, works remotely for Vercel's EMEA partnerships team -- Expressed interest in expanding the sponsorship to include newsletter placements in addition to podcast spots - -## Collaborations - -- [[24q1-launch-sponsorship-packages]] — one of the early sponsors onboarded -- [[procedure-sponsor-onboarding]] — smooth onboarding process, good reference example -- [[event-sponsor-call-vercel]] — regular check-in calls on campaign performance diff --git a/demo-vault-v2/person-anna-lindberg.md b/demo-vault-v2/person-anna-lindberg.md deleted file mode 100644 index fdc53c30..00000000 --- a/demo-vault-v2/person-anna-lindberg.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -aliases: ["Anna Lindberg"] -Is A: Person -Tier: "3rd 🥉" -Tags: ["Podcast Guest"] ---- -# Anna Lindberg - -Product lead at a fast-growing Nordic fintech company based in Stockholm. Anna appeared on the podcast to discuss product-led growth strategies, self-serve onboarding, and how to balance data-driven product decisions with intuition. She has a background in both engineering and product management, which gives her a technical depth that many pure PM guests lack. - -## Notes - -- Articulate and structured thinker; her episode was one of the most well-organized conversations in the season -- Strong advocate for empowering product teams with direct access to analytics rather than relying on centralized data teams -- Shared a compelling framework for prioritizing features based on activation impact rather than feature requests -- Scandinavian directness in communication style; says what she means without unnecessary hedging - -## Collaborations - -- [[24q3-podcast-season-2]] — recorded episode on product-led growth in fintech -- [[topic-saas-business]] — discussed SaaS growth mechanics and product strategy -- [[procedure-podcast-guest-outreach]] — connected through Nordic tech community on LinkedIn diff --git a/demo-vault-v2/person-antonio-marchetti.md b/demo-vault-v2/person-antonio-marchetti.md deleted file mode 100644 index f4e10c82..00000000 --- a/demo-vault-v2/person-antonio-marchetti.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -aliases: ["Antonio Marchetti"] -Is A: Person -Tier: "2nd 🥈" -Tags: ["Family"] ---- -# Antonio Marchetti - -Giulia's older brother, an architect based in Turin specializing in sustainable residential design. Antonio is a warm, thoughtful person whom Luca enjoys spending time with at family gatherings and the occasional weekend visit to Turin. They share a mutual appreciation for craftsmanship and attention to detail, even though their fields are quite different. Antonio has been practicing architecture for over fifteen years and recently started his own small studio. - -## Notes - -- Quietly passionate about his work; can talk for hours about material choices and building physics -- His approach to architecture mirrors Luca's approach to software: prefer simplicity, respect constraints, build things that last -- Great cook, especially traditional Piedmontese dishes; Sunday lunches at his place are a highlight -- Supportive of Giulia and Luca's life in Milan; no family drama, which Luca appreciates -- Recently got interested in smart home technology, occasionally asks Luca for recommendations - -## Collaborations - -- [[event-dinner-family]] — regular presence at family dinners and holiday gatherings -- [[25q2-team-retreat]] — recommended the venue in Piedmont that Luca considered for the team retreat diff --git a/demo-vault-v2/person-benedetta-vitali.md b/demo-vault-v2/person-benedetta-vitali.md deleted file mode 100644 index 319cabe7..00000000 --- a/demo-vault-v2/person-benedetta-vitali.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -aliases: ["Benedetta Vitali"] -Is A: Person -Tier: "3rd 🥉" -Tags: ["Podcast Guest"] ---- -# Benedetta Vitali - -Startup founder based in Naples, building a B2B SaaS product for the hospitality industry. Benedetta joined the podcast to share her experience of building a venture-backed startup in southern Europe, covering the challenges of fundraising outside traditional hubs, hiring technical talent in Italy, and navigating the gap between Italian business culture and Silicon Valley expectations. - -## Notes - -- Energetic and candid; did not shy away from discussing the real difficulties of building in southern Italy -- Her perspective on bootstrapping vs. raising VC in the Italian context was one of the most-discussed episodes on social media -- Deeply embedded in the Italian startup ecosystem; knows everyone and is generous with introductions -- Balances technical credibility (she was a developer before becoming a founder) with strong business instincts - -## Collaborations - -- [[24q1-podcast-season-1]] — recorded episode on building a startup in southern Europe -- [[topic-italian-startups]] — core topic of the conversation -- [[procedure-podcast-guest-outreach]] — introduced through the Italian startup community diff --git a/demo-vault-v2/person-carlos-mendez.md b/demo-vault-v2/person-carlos-mendez.md deleted file mode 100644 index 948da163..00000000 --- a/demo-vault-v2/person-carlos-mendez.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -aliases: ["Carlos Mendez"] -Is A: Person -Tier: "3rd 🥉" -Tags: ["Sponsor"] ---- -# Carlos Mendez - -Sponsor contact at PlanetScale, handling developer marketing and content partnerships. Carlos manages the relationship for PlanetScale's podcast sponsorship, focusing on database tooling and developer platform messaging. He is based in Austin, Texas, and came to content partnerships from a developer relations background, which makes him easier to work with than typical marketing contacts. - -## Notes - -- Understands the developer audience from personal experience, having been a backend engineer before moving into DevRel -- Provides well-crafted talking points that actually sound natural in a podcast context -- Responsive on Slack and email; turnaround on approvals is usually within 24 hours -- Interested in exploring deeper integrations like sponsored tutorial content alongside standard ad reads - -## Collaborations - -- [[24q1-launch-sponsorship-packages]] — PlanetScale sponsorship onboarded in the first batch -- [[procedure-sponsor-onboarding]] — clean onboarding; good template for future database-category sponsors -- [[event-sponsor-call-planetscale]] — quarterly check-in calls on campaign metrics diff --git a/demo-vault-v2/person-chiara-romano.md b/demo-vault-v2/person-chiara-romano.md deleted file mode 100644 index 4cd3d343..00000000 --- a/demo-vault-v2/person-chiara-romano.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -aliases: ["Chiara Romano"] -Is A: Person -Tier: "2nd 🥈" -Tags: ["Friend"] ---- -# Chiara Romano - -UX designer at a well-known design agency in Milan, specializing in product design for B2B SaaS applications. Luca met Chiara through the Milan tech scene at a design-meets-engineering meetup a few years ago, and they have maintained a friendship built around shared curiosity about how products get made. She brings a design perspective that consistently challenges Luca's engineering-first instincts, which he values. - -## Notes - -- Has a sharp eye for interaction patterns and is quick to spot UX antipatterns in any product she uses -- Great at articulating design decisions in terms that engineers understand; bridges the design-dev gap naturally -- Luca occasionally consults her informally on UI decisions for his projects; her feedback is always actionable -- Active in the Italian design community; speaks at local events and mentors junior designers -- Shares Luca's interest in tools for thought and personal knowledge management - -## Collaborations - -- [[event-dinner-family]] — regular at casual dinners and Milan tech scene gatherings -- [[topic-saas-business]] — ongoing conversations about product design and UX in SaaS diff --git a/demo-vault-v2/person-clara-dupont.md b/demo-vault-v2/person-clara-dupont.md deleted file mode 100644 index e5247c67..00000000 --- a/demo-vault-v2/person-clara-dupont.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -aliases: ["Clara Dupont"] -Is A: Person -Tier: "3rd 🥉" -Tags: ["Podcast Guest"] ---- -# Clara Dupont - -CTO of a French SaaS startup in the HR-tech space, based in Paris. Clara appeared on the podcast to discuss the transition from senior engineer to technical leadership, covering topics like architecture ownership, hiring your first engineers, and maintaining technical credibility while taking on management responsibilities. She has a background in distributed systems and spent several years at a large French tech company before co-founding her current venture. - -## Notes - -- Thoughtful and precise communicator; every answer felt like it had been carefully considered -- Shared a practical framework for "CTO time allocation" across quarters that resonated with the audience -- Her perspective on being a female CTO in the European startup scene added important nuance to the conversation -- Followed up after the episode with a detailed blog post expanding on one of the topics, which drove additional traffic - -## Collaborations - -- [[24q3-podcast-season-2]] — recorded episode on technical leadership and the CTO role -- [[topic-team-leadership]] — discussed engineering management and leadership transitions -- [[procedure-podcast-guest-outreach]] — connected through European CTO network on Twitter diff --git a/demo-vault-v2/person-david-eriksson.md b/demo-vault-v2/person-david-eriksson.md deleted file mode 100644 index a9c7afcc..00000000 --- a/demo-vault-v2/person-david-eriksson.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -aliases: ["David Eriksson"] -Is A: Person -Tier: "3rd 🥉" -Tags: ["Podcast Guest"] ---- -# David Eriksson - -CTO of a Stockholm-based startup building developer tooling for cloud-native applications. David joined the podcast to discuss remote-first engineering culture, asynchronous communication practices, and how his fully distributed team across five countries maintains velocity and cohesion without real-time meetings. He has strong opinions shaped by years of building distributed teams across Scandinavia and Eastern Europe. - -## Notes - -- Highly opinionated on async-first workflows; his team runs almost entirely on written documentation and recorded video updates -- Practical and data-driven in his approach; brought concrete metrics on how async practices affected cycle time -- Admitted candidly that remote-first is not universally better, just better for certain team profiles and cultures -- The episode sparked one of the longest comment threads in the podcast community Discord - -## Collaborations - -- [[24q1-podcast-season-1]] — recorded episode on remote-first engineering culture -- [[topic-team-leadership]] — discussed remote team management and async workflows -- [[procedure-podcast-guest-outreach]] — introduced through the European developer tools community diff --git a/demo-vault-v2/person-david-kim.md b/demo-vault-v2/person-david-kim.md deleted file mode 100644 index 59516721..00000000 --- a/demo-vault-v2/person-david-kim.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -aliases: ["David Kim"] -Is A: Person -Tier: "3rd 🥉" -Tags: ["Sponsor"] ---- -# David Kim - -Sponsor contact at Railway, managing cloud platform partnerships and developer content sponsorships. David oversees Railway's investment in podcast and newsletter sponsorships targeting the indie developer and small-team audience. Based in San Francisco, he has a product marketing background and is focused on positioning Railway as the go-to deployment platform for small, fast-moving teams. - -## Notes - -- Professional and low-maintenance as a sponsor contact; provides clear briefs and does not micromanage messaging -- Genuinely uses Railway himself, which makes the partnership feel more authentic -- Interested in long-term brand building rather than just short-term conversion metrics -- Occasionally shares useful data on developer platform trends that informs podcast content planning - -## Collaborations - -- [[24q1-launch-sponsorship-packages]] — Railway onboarded as a sponsor for the podcast -- [[procedure-sponsor-onboarding]] — straightforward onboarding process -- [[event-sponsor-call-railway]] — periodic check-in calls on sponsorship performance diff --git a/demo-vault-v2/person-davide-conti.md b/demo-vault-v2/person-davide-conti.md deleted file mode 100644 index 12d41256..00000000 --- a/demo-vault-v2/person-davide-conti.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -aliases: ["Davide Conti"] -Is A: Person -Tier: "2nd 🥈" -Tags: ["Friend"] ---- -# Davide Conti - -College friend and fellow software engineer, currently working as a senior backend developer at a growing Milan-based startup in the logistics space. Luca and Davide studied computer science together at Politecnico di Milano and have stayed close ever since. They grab dinner regularly, usually somewhere in Navigli or Isola, and the conversation inevitably drifts to tech, career moves, and the Italian startup ecosystem. Davide is one of the few people Luca can talk to about both deep technical problems and the personal side of running an indie business. - -## Notes - -- Rock-solid engineer with a preference for Go and PostgreSQL; skeptical of hype cycles but open to being convinced -- Gave Luca valuable early feedback on the podcast concept before it launched -- Quietly ambitious; has been thinking about going indie himself but values the stability of a salary for now -- Shared taste in music and restaurants; they have a running list of places to try in Milan -- Reliable sounding board for technical architecture decisions - -## Collaborations - -- [[event-dinner-family]] — regular dinner companion, sometimes joins group gatherings -- [[topic-italian-startups]] — frequent discussions about the Milan startup scene diff --git a/demo-vault-v2/person-diego-santos.md b/demo-vault-v2/person-diego-santos.md deleted file mode 100644 index c2d0bf77..00000000 --- a/demo-vault-v2/person-diego-santos.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -aliases: ["Diego Santos"] -Is A: Person -Tier: "3rd 🥉" -Tags: ["Podcast Guest"] ---- -# Diego Santos - -Founder of a developer platform serving the Latin American tech community, based in Sao Paulo. Diego appeared on the podcast to discuss building global developer communities, the unique challenges and opportunities of the LatAm tech ecosystem, and how developer tooling companies can think beyond English-speaking markets. His platform helps connect Brazilian and Latin American developers with remote work opportunities and educational resources. - -## Notes - -- Charismatic and energetic speaker; his enthusiasm for the LatAm developer community is infectious -- Offered a perspective rarely heard on English-language tech podcasts, which the audience appreciated -- Shared concrete data on the growth of the Brazilian developer population and its implications for global tech companies -- Bilingual content strategy (Portuguese/English) that Luca found interesting as a parallel to his own Italian/English situation - -## Collaborations - -- [[24q3-podcast-season-2]] — recorded episode on global developer communities -- [[topic-podcasting]] — discussed community building through content and media -- [[procedure-podcast-guest-outreach]] — connected through developer community Twitter diff --git a/demo-vault-v2/person-elena-konstantinou.md b/demo-vault-v2/person-elena-konstantinou.md deleted file mode 100644 index 8b61ee4f..00000000 --- a/demo-vault-v2/person-elena-konstantinou.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -aliases: ["Elena Konstantinou"] -Is A: Person -Tier: "3rd 🥉" -Tags: ["Podcast Guest"] ---- -# Elena Konstantinou - -VP of Engineering at a European fintech unicorn headquartered in Athens with offices across Europe. Elena joined the podcast to discuss the challenges of scaling an engineering organization from 20 to 200 engineers, covering hiring pipelines, team topology, technical debt management, and maintaining culture through hypergrowth. She has a background in distributed systems and previously held senior engineering roles at Amazon and Spotify. - -## Notes - -- Extremely structured in her thinking; provided clear mental models for each stage of engineering org growth -- Honest about mistakes made during rapid scaling, which made the conversation feel authentic -- Strong advocate for staff-plus engineering tracks as an alternative to management -- The episode performed well with engineering managers in the audience; several reached out to Luca saying it was exactly what they needed - -## Collaborations - -- [[24q3-podcast-season-2]] — recorded episode on scaling engineering organizations -- [[topic-team-leadership]] — discussed org design and engineering leadership at scale -- [[procedure-podcast-guest-outreach]] — introduced through European fintech CTO network diff --git a/demo-vault-v2/person-elena-rossi.md b/demo-vault-v2/person-elena-rossi.md deleted file mode 100644 index 20ed25d7..00000000 --- a/demo-vault-v2/person-elena-rossi.md +++ /dev/null @@ -1,23 +0,0 @@ ---- -aliases: ["Elena Rossi"] -Is A: Person -Tier: "1st 🥇" -Tags: ["Family"] ---- -# Elena Rossi - -Luca's younger sister, based in Rome where she works as an editor at a mid-sized Italian publishing house. Elena is warm, sharp-witted, and one of the people Luca trusts most in the world. They talk on the phone every week, usually on Sunday evenings, catching up on everything from work to family to what they are reading. Despite living in different cities, they have maintained a close bond through consistent communication and shared sensibilities. - -Elena studied comparative literature at La Sapienza and has built a solid career in Italian publishing, working primarily on literary fiction and translated works. She has an editorial eye that extends beyond books; Luca sometimes runs newsletter drafts past her for a perspective outside the tech bubble. - -## Notes - -- Voracious reader with impeccable taste; her book recommendations are always worth following -- Has a dry, deadpan sense of humor that perfectly complements Luca's more enthusiastic energy -- Fiercely independent but deeply loyal to family; will drop everything if someone she loves needs help -- Curious about Luca's tech world even though it is far from her own; asks surprisingly insightful questions about the business -- They share a love of good coffee and have a running debate about which Italian city has the best espresso (she says Rome, he says Milan, neither will concede) - -## Collaborations - -- [[event-dinner-family]] — central figure at family gatherings; always makes the trip to Milan for important occasions diff --git a/demo-vault-v2/person-elisa-barbieri.md b/demo-vault-v2/person-elisa-barbieri.md deleted file mode 100644 index 391142b3..00000000 --- a/demo-vault-v2/person-elisa-barbieri.md +++ /dev/null @@ -1,20 +0,0 @@ ---- -aliases: ["Elisa Barbieri"] -Is A: Person -Tier: "3rd 🥉" -Tags: ["Friend"] ---- -# Elisa Barbieri - -High school teacher and an old friend from Luca's pre-tech life. Elisa teaches Italian literature at a liceo in Milan and is part of Luca's broader social circle. They see each other at group dinners every few months, typically organized by mutual friends. While their professional worlds are completely different, Elisa brings a grounding perspective and a reminder that there is an entire world beyond startups and software. - -## Notes - -- Passionate educator who genuinely cares about her students; talks about teaching with the same energy Luca brings to engineering -- Wellread and opinionated on Italian culture and politics; always sparks good dinner table debates -- Helps Luca stay connected to a non-tech social circle, which he values -- Quietly impressed by what Luca has built but would never admit it directly - -## Collaborations - -- [[event-dinner-family]] — regular at group dinners with the broader Milan friend circle diff --git a/demo-vault-v2/person-emilia-hoffmann.md b/demo-vault-v2/person-emilia-hoffmann.md deleted file mode 100644 index decf0a53..00000000 --- a/demo-vault-v2/person-emilia-hoffmann.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -aliases: ["Emilia Hoffmann"] -Is A: Person -Tier: "3rd 🥉" -Tags: ["Podcast Guest"] ---- -# Emilia Hoffmann - -AI startup founder based in Berlin, building a product that helps mid-market companies integrate large language models into their existing workflows. Emilia appeared on the podcast to discuss the elusive challenge of finding product-market fit for AI products, the gap between AI demos and production-ready features, and why so many AI startups struggle to convert technical capability into business value. She previously worked as a machine learning engineer at a large German enterprise software company. - -## Notes - -- Refreshingly skeptical about AI hype while still being deeply technical and optimistic about specific applications -- Her framework for distinguishing "AI-native" products from "AI-augmented" products was one of the most shared clips from the episode -- Direct and pragmatic communicator; does not indulge in handwaving about AGI timelines -- Followed up after the recording asking about future collaboration on a written piece about AI in European startups - -## Collaborations - -- [[25q2-podcast-season-3]] — recorded episode on AI product-market fit -- [[topic-ai-ml]] — primary topic of the conversation -- [[procedure-podcast-guest-outreach]] — connected through the Berlin tech startup scene diff --git a/demo-vault-v2/person-emma-wilson.md b/demo-vault-v2/person-emma-wilson.md deleted file mode 100644 index 2c7b05f3..00000000 --- a/demo-vault-v2/person-emma-wilson.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -aliases: ["Emma Wilson"] -Is A: Person -Tier: "3rd 🥉" -Tags: ["Sponsor"] ---- -# Emma Wilson - -Sponsor contact at Clerk, managing their developer content marketing and podcast sponsorship programs. Emma handles the partnership for Clerk's authentication and identity product, targeting indie developers and small SaaS teams. Based in New York, she comes from a content marketing background and is thoughtful about how sponsorship messaging lands with technical audiences. - -## Notes - -- Provides well-written ad copy that requires minimal editing to sound natural in a podcast context -- Responsive and professional; approvals and asset delivery are consistently on time -- Genuinely interested in podcast analytics and audience demographics, asks good questions about performance -- Has expressed interest in sponsoring specific episodes related to authentication and security topics - -## Collaborations - -- [[24q1-launch-sponsorship-packages]] — Clerk onboarded as a podcast sponsor -- [[procedure-sponsor-onboarding]] — smooth process with clear deliverables -- [[event-sponsor-call-clerk]] — regular check-in calls on campaign results diff --git a/demo-vault-v2/person-federico-moretti.md b/demo-vault-v2/person-federico-moretti.md deleted file mode 100644 index cc9e8478..00000000 --- a/demo-vault-v2/person-federico-moretti.md +++ /dev/null @@ -1,23 +0,0 @@ ---- -aliases: ["Federico Moretti"] -Is A: Person -Tier: "2nd 🥈" -Tags: ["Friend"] ---- -# Federico Moretti - -Startup founder running a small developer tools company based in Milan, building a CLI-based deployment platform for European cloud infrastructure. Federico is one of Luca's closest friends in the Italian indie tech scene. They meet regularly for aperitivo in Brera or Navigli and swap war stories about the realities of running a small software business in Italy: dealing with Italian bureaucracy, finding customers outside the local market, and staying motivated as a solo founder. - -## Notes - -- Technical founder who codes most of the product himself; shares Luca's preference for staying hands-on -- More cautious and methodical than Luca when it comes to product decisions; good counterbalance in conversations -- Has deep knowledge of European cloud regulations and data sovereignty, which comes up in interesting conversations -- They have discussed collaborating on a joint content piece about the Italian indie developer scene but have not found the time yet -- Dry sense of humor; their WhatsApp thread is equal parts founder therapy and comedy - -## Collaborations - -- [[event-dinner-family]] — regular at Luca's social gatherings in Milan -- [[topic-italian-startups]] — ongoing conversations about building software businesses in Italy -- [[topic-saas-business]] — mutual interest in indie SaaS economics and growth strategies diff --git a/demo-vault-v2/person-francesca-deluca.md b/demo-vault-v2/person-francesca-deluca.md deleted file mode 100644 index db4691c3..00000000 --- a/demo-vault-v2/person-francesca-deluca.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -aliases: ["Francesca De Luca"] -Is A: Person -Tier: "3rd 🥉" -Tags: ["Podcast Guest"] ---- -# Francesca De Luca - -Product lead at a Milan-based fintech company, specializing in product management within highly regulated financial services environments. Francesca appeared on the podcast to discuss the unique challenges of building product in industries with strict compliance requirements, from navigating regulatory constraints to working with legal teams and turning compliance into a competitive advantage rather than a blocker. - -## Notes - -- Articulate and precise; the kind of PM who can explain regulatory complexity without putting the audience to sleep -- Shared a useful framework for "compliance-aware product development" that resonated with listeners in regulated industries -- Based in Milan, which made the recording logistics easy; they met in person at a local coworking space -- Her background in economics before transitioning to product management gives her a different analytical lens than most tech PMs - -## Collaborations - -- [[24q1-podcast-season-1]] — recorded episode on product management in regulated industries -- [[topic-saas-business]] — discussed fintech product strategy and regulatory navigation -- [[procedure-podcast-guest-outreach]] — connected through the Milan fintech community diff --git a/demo-vault-v2/person-francesca-marino.md b/demo-vault-v2/person-francesca-marino.md deleted file mode 100644 index 30eab7da..00000000 --- a/demo-vault-v2/person-francesca-marino.md +++ /dev/null @@ -1,21 +0,0 @@ ---- -aliases: ["Francesca Marino"] -Is A: Person -Tier: "3rd 🥉" -Tags: ["Friend"] ---- -# Francesca Marino - -Professional photographer based in Milan, specializing in branding and editorial photography for tech companies and creative businesses. Francesca shot the photos for the Refactoring website and brand identity, including headshots, workspace imagery, and social media assets. Luca connected with her through a recommendation from Chiara Romano and was impressed by her ability to make a solo tech project feel visually polished and professional. - -## Notes - -- Has a natural talent for making technical products look approachable and human in photos -- Easy to work with; understood the Refactoring brand aesthetic quickly without extensive briefing -- Runs her own photography business as a solo practitioner, so she and Luca share notes on freelance life -- Occasionally posts behind-the-scenes content from shoots that Luca has reshared for the Refactoring brand - -## Collaborations - -- [[24q1-podcast-season-1]] — provided brand photography used in the podcast launch materials -- [[event-dinner-family]] — has attended a couple of casual gatherings through the Milan creative-tech circle diff --git a/demo-vault-v2/person-gianluca-esposito.md b/demo-vault-v2/person-gianluca-esposito.md deleted file mode 100644 index 758e2604..00000000 --- a/demo-vault-v2/person-gianluca-esposito.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -aliases: ["Gianluca Esposito"] -Is A: Person -Tier: "2nd 🥈" -Tags: ["Friend"] ---- -# Gianluca Esposito - -Chef and owner of a small, acclaimed restaurant in the Navigli district of Milan. Gianluca runs the kitchen with a focus on contemporary Italian cuisine using seasonal ingredients sourced from small producers across southern Italy. His restaurant has become Luca's go-to spot for a weeknight dinner, a casual client meeting, or a celebratory meal after a big launch. They have developed a genuine friendship over years of regular visits, fueled by a shared appreciation for quality craftsmanship in their respective fields. - -## Notes - -- Treats cooking with the same obsessive attention to detail that Luca brings to code; they respect each other's craft -- Always experimenting with new dishes and seasonal specials; Luca is often an eager test subject for new menu items -- Originally from Naples, brought authentic southern Italian flavors to the Milan dining scene -- Has a small but fiercely loyal customer base; runs the business on reputation and word of mouth, no social media marketing -- Luca sometimes brings team members or podcast guests to the restaurant for dinners - -## Collaborations - -- [[event-dinner-family]] — the restaurant is a frequent venue for Luca's personal and professional dinners -- [[25q2-team-retreat]] — Luca considered having Gianluca cater a team dinner during the retreat planning diff --git a/demo-vault-v2/person-giulia-conti.md b/demo-vault-v2/person-giulia-conti.md deleted file mode 100644 index 647b42b8..00000000 --- a/demo-vault-v2/person-giulia-conti.md +++ /dev/null @@ -1,20 +0,0 @@ ---- -aliases: ["Giulia Conti"] -Is A: Person -Tier: "3rd 🥉" -Tags: ["Friend"] ---- -# Giulia Conti - -Giulia Marchetti's best friend since university, working as a marketing manager at a fashion brand in Milan. She and Luca see each other regularly on weekends when the three of them, plus other friends, get together for brunch, aperitivo, or day trips around Lombardy. Luca appreciates her warmth and the fact that she treats him as a genuine friend rather than just her best friend's boyfriend. - -## Notes - -- Social connector who is always organizing group activities and keeping the friend circle together -- Works in fashion marketing, which gives her a completely different perspective on branding that Luca finds interesting -- Has been supportive of Luca's relationship with Giulia Marchetti from the very beginning -- Fun and easygoing in group settings; brings good energy to weekend plans - -## Collaborations - -- [[event-dinner-family]] — frequent presence at weekend gatherings and group outings diff --git a/demo-vault-v2/person-giulia-marchetti.md b/demo-vault-v2/person-giulia-marchetti.md deleted file mode 100644 index 6f117fc1..00000000 --- a/demo-vault-v2/person-giulia-marchetti.md +++ /dev/null @@ -1,24 +0,0 @@ ---- -aliases: ["Giulia Marchetti"] -Is A: Person -Tier: "1st 🥇" -Tags: ["Personal"] ---- -# Giulia Marchetti - -Luca's girlfriend since early 2024. Giulia works as a UX researcher at a well-known Milan-based fintech company, where she leads qualitative research for the mobile banking experience. They met at a design-tech crossover event in Milan and connected immediately over a shared love of thoughtful product design, hiking in the Alps, and contemporary art exhibitions. Giulia is intelligent, creative, and grounded, with a natural curiosity about how things work that makes her the perfect partner for someone who builds things for a living. - -She brings balance to Luca's life, gently pulling him away from the screen when he is deep in a coding session and pushing him to explore the city, visit galleries, and maintain a life outside of work. Their weekends often involve long walks, museum visits, dinners with friends, or drives into the Lombard countryside. - -## Notes - -- Her UX research background means she asks incisive questions about Luca's products; her feedback on the podcast website was invaluable -- Genuinely supportive of Luca's indie business journey but also honest when she thinks he is overworking -- Loves hiking and has introduced Luca to several alpine trails he would never have found on his own -- Her circle of friends has become part of Luca's social life, which he appreciates -- They are planning a longer trip together, possibly to Japan, which both have wanted to visit - -## Collaborations - -- [[event-dinner-family]] — co-hosts dinners and gatherings at their apartment -- [[25q2-team-retreat]] — helped Luca brainstorm retreat activities and venue options diff --git a/demo-vault-v2/person-henrik-johansson.md b/demo-vault-v2/person-henrik-johansson.md deleted file mode 100644 index 46e574c4..00000000 --- a/demo-vault-v2/person-henrik-johansson.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -aliases: ["Henrik Johansson"] -Is A: Person -Tier: "3rd 🥉" -Tags: ["Sponsor"] ---- -# Henrik Johansson - -Sponsor contact at PostHog, managing developer marketing partnerships and content sponsorships across European tech media. Henrik oversees PostHog's podcast and newsletter sponsorship investments, with a focus on reaching engineering-led teams and indie developers. Based in Stockholm, he has a developer advocacy background and understands the nuances of speaking authentically to a technical audience. - -## Notes - -- One of the more hands-off sponsor contacts; trusts Luca to craft messaging that fits the audience -- Provides useful product context and positioning updates that make ad reads feel current and relevant -- PostHog's open-source ethos aligns well with the podcast audience, making the sponsorship feel natural -- Occasionally shares listener feedback and conversion data from their side, which helps with pricing discussions - -## Collaborations - -- [[24q1-launch-sponsorship-packages]] — PostHog onboarded as a sponsor early in the sponsorship program -- [[procedure-sponsor-onboarding]] — clean onboarding with minimal back-and-forth -- [[event-sponsor-call-posthog]] — quarterly alignment calls on campaign direction diff --git a/demo-vault-v2/person-hiroshi-tanaka.md b/demo-vault-v2/person-hiroshi-tanaka.md deleted file mode 100644 index 92afd0ee..00000000 --- a/demo-vault-v2/person-hiroshi-tanaka.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -aliases: ["Hiroshi Tanaka"] -Is A: Person -Tier: "3rd 🥉" -Tags: ["Podcast Guest"] ---- -# Hiroshi Tanaka - -Principal engineer specializing in observability and distributed systems at a major US-based cloud infrastructure company. Hiroshi joined the podcast to discuss the art and science of debugging production systems at scale, covering observability tooling, incident response workflows, and the human factors that determine whether a team can effectively diagnose complex failures. He brought deep technical expertise honed over a decade of working on large-scale distributed systems. - -## Notes - -- Methodical and deeply technical; the episode required more editing than usual because of the density of content, but the result was excellent -- His concept of "observability as a team capability rather than a tooling choice" resonated strongly with the audience -- Quiet and thoughtful in conversation; takes time to formulate precise answers rather than giving quick reactions -- Shared a post-mortem template that Luca adopted for his own incident review process - -## Collaborations - -- [[24q3-podcast-season-2]] — recorded episode on debugging production systems and observability -- [[topic-ai-ml]] — touched on ML-assisted anomaly detection in observability -- [[procedure-podcast-guest-outreach]] — connected through SRE community on Twitter diff --git a/demo-vault-v2/person-james-mitchell.md b/demo-vault-v2/person-james-mitchell.md deleted file mode 100644 index bf3a7478..00000000 --- a/demo-vault-v2/person-james-mitchell.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -aliases: ["James Mitchell"] -Is A: Person -Tier: "3rd 🥉" -Tags: ["Sponsor"] ---- -# James Mitchell - -Sponsor contact at Linear, running their developer marketing and content partnership programs. James manages Linear's investment in podcast sponsorships targeting engineering leaders and technically sophisticated audiences. Based in San Francisco, he has a product marketing background and is focused on positioning Linear as the preferred project management tool for high-velocity engineering teams. - -## Notes - -- Very brand-conscious; provides tight guidelines on messaging but is flexible on delivery format -- Understands the engineering audience deeply because he previously worked as a product manager at a developer tools company -- Quick to respond on email and Slack; approvals rarely take more than a day -- Linear's brand resonates naturally with the podcast audience, making ad reads feel like genuine recommendations - -## Collaborations - -- [[24q1-launch-sponsorship-packages]] — Linear onboarded as a podcast sponsor -- [[procedure-sponsor-onboarding]] — smooth process with well-prepared brand assets -- [[event-sponsor-call-linear]] — periodic alignment calls on messaging and campaign performance diff --git a/demo-vault-v2/person-james-murphy.md b/demo-vault-v2/person-james-murphy.md deleted file mode 100644 index 1b9e8c67..00000000 --- a/demo-vault-v2/person-james-murphy.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -aliases: ["James Murphy"] -Is A: Person -Tier: "3rd 🥉" -Tags: ["Podcast Guest"] ---- -# James Murphy - -Founder of a bootstrapped SaaS company based in Dublin, building project management tooling for small agencies. James appeared on the podcast to discuss the bootstrapping vs. venture capital funding decision, drawing from his own experience of growing a profitable software business to seven-figure ARR without external investment. His perspective is grounded in the realities of building a sustainable business outside of Silicon Valley. - -## Notes - -- Refreshingly transparent about revenue numbers and growth rates, which is rare for bootstrapped founders -- Strong advocate for profitability-first thinking; his framework for evaluating when VC might actually make sense was nuanced and fair -- Irish humor came through naturally in the conversation, making the episode entertaining as well as informative -- The episode became one of the most downloaded in the season, resonating with the indie hacker segment of the audience - -## Collaborations - -- [[24q1-podcast-season-1]] — recorded episode on bootstrapping vs. VC funding -- [[topic-saas-business]] — discussed indie SaaS economics and growth strategies -- [[procedure-podcast-guest-outreach]] — connected through the Indie Hackers community diff --git a/demo-vault-v2/person-katja-mueller.md b/demo-vault-v2/person-katja-mueller.md deleted file mode 100644 index 716bad44..00000000 --- a/demo-vault-v2/person-katja-mueller.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -aliases: ["Katja Mueller"] -Is A: Person -Tier: "3rd 🥉" -Tags: ["Podcast Guest"] ---- -# Katja Mueller - -VP of Engineering at a large German enterprise software company, leading a multi-year legacy modernization initiative to migrate core systems from monolithic Java applications to a cloud-native microservices architecture. Katja joined the podcast to discuss the technical and organizational challenges of legacy modernization at scale, covering topics from strangler fig patterns to convincing executive leadership to invest in infrastructure that does not directly generate new features. - -## Notes - -- Extremely pragmatic about the realities of enterprise modernization; no idealism about big-bang rewrites -- Shared a compelling case study of a partial migration that delivered business value while keeping the old system running -- Her experience managing a 150-person engineering organization through a multi-year transformation provided rare insight into the human side of technical change -- German directness made the conversation efficient and packed with actionable takeaways - -## Collaborations - -- [[24q3-podcast-season-2]] — recorded episode on legacy modernization in enterprise -- [[topic-team-leadership]] — discussed engineering leadership during large-scale technical transitions -- [[procedure-podcast-guest-outreach]] — connected through European engineering leadership network diff --git a/demo-vault-v2/person-kenji-tanaka.md b/demo-vault-v2/person-kenji-tanaka.md deleted file mode 100644 index ecb8ffed..00000000 --- a/demo-vault-v2/person-kenji-tanaka.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -aliases: ["Kenji Tanaka"] -Is A: Person -Tier: "3rd 🥉" -Tags: ["Sponsor"] ---- -# Kenji Tanaka - -Sponsor contact at Supabase, managing growth partnerships and developer content sponsorships. Kenji oversees Supabase's investment in podcast and newsletter sponsorships aimed at full-stack developers and indie hackers. Based in Singapore, he brings a growth marketing perspective and is focused on expanding Supabase's presence in the European and Asian developer communities. - -## Notes - -- Enthusiastic about the Supabase product and genuinely engaged with the developer community, which makes the partnership feel authentic -- Provides creative sponsorship ideas beyond standard ad reads, such as tutorial integrations and code-along episodes -- Responsive across time zones despite the Singapore-Milan gap; usually replies within a few hours -- Interested in co-creating content rather than just buying ad slots, which aligns with Luca's approach to sponsorships - -## Collaborations - -- [[24q1-launch-sponsorship-packages]] — Supabase onboarded as a podcast and newsletter sponsor -- [[procedure-sponsor-onboarding]] — collaborative onboarding with creative brief development -- [[event-sponsor-call-supabase]] — regular check-in calls on partnership direction diff --git a/demo-vault-v2/person-lisa-chen.md b/demo-vault-v2/person-lisa-chen.md deleted file mode 100644 index 6ff9addf..00000000 --- a/demo-vault-v2/person-lisa-chen.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -aliases: ["Lisa Chen"] -Is A: Person -Tier: "3rd 🥉" -Tags: ["Sponsor"] ---- -# Lisa Chen - -Sponsor contact at Notion, running their B2B content partnerships and developer-focused sponsorship programs. Lisa manages the relationship for Notion's podcast sponsorship, targeting engineering teams and knowledge workers who are the natural audience for productivity and documentation tooling. Based in San Francisco, she has a content strategy background and thinks carefully about how sponsorship integrates with editorial content. - -## Notes - -- Very deliberate about brand alignment; only sponsors content that genuinely fits Notion's positioning -- Provides detailed campaign briefs with specific talking points, but is open to Luca adapting them for natural delivery -- Notion is a product Luca genuinely uses daily, which makes the sponsorship easy to endorse authentically -- Occasionally shares research and data about productivity workflows that has been useful for newsletter content - -## Collaborations - -- [[24q1-launch-sponsorship-packages]] — Notion onboarded as a premium podcast sponsor -- [[procedure-sponsor-onboarding]] — thorough onboarding with well-prepared assets and guidelines -- [[event-sponsor-call-notion]] — quarterly strategic alignment calls diff --git a/demo-vault-v2/person-lorenzo-galli.md b/demo-vault-v2/person-lorenzo-galli.md deleted file mode 100644 index eb63c199..00000000 --- a/demo-vault-v2/person-lorenzo-galli.md +++ /dev/null @@ -1,21 +0,0 @@ ---- -aliases: ["Lorenzo Galli"] -Is A: Person -Tier: "3rd 🥉" -Tags: ["Friend"] ---- -# Lorenzo Galli - -Lawyer based in Milan, specializing in intellectual property and commercial contracts for digital businesses. Lorenzo handles the legal side of Refactoring's operations, including sponsor contracts, freelancer agreements, and terms of service. Luca connected with him through a mutual friend in the Milan tech scene and appreciates his no-nonsense, efficient approach to legal work, which is a refreshing contrast to the stereotypical Italian legal bureaucracy. - -## Notes - -- Efficient and straightforward; reviews contracts quickly and flags only what genuinely matters -- Understands the digital content business model well enough that Luca does not have to explain basic concepts every time -- Charges fairly and transparently, which Luca values as a small business owner -- Their relationship is primarily professional but they occasionally grab a coffee when meeting to discuss contract matters - -## Collaborations - -- [[24q1-launch-sponsorship-packages]] — drafted the standard sponsorship agreement template -- [[procedure-sponsor-onboarding]] — created the legal framework for sponsor contracts diff --git a/demo-vault-v2/person-luca-rossi.md b/demo-vault-v2/person-luca-rossi.md index aa2eb011..52f7f595 100644 --- a/demo-vault-v2/person-luca-rossi.md +++ b/demo-vault-v2/person-luca-rossi.md @@ -1,27 +1,11 @@ --- -aliases: ["Luca Rossi"] -Is A: Person -Tier: "1st 🥇" -Tags: ["Self"] +type: Person +aliases: + - "[[Luca Rossi]]" +tier: 1st --- + # Luca Rossi -Founder of Refactoring, a B2B tech newsletter and podcast focused on engineering leadership, team dynamics, and the craft of building software. Based in Milan, Italy. Luca is a software engineer by training who transitioned into content creation and indie business after years of working in the Italian and European tech industry. He writes weekly for an audience of engineering managers, senior developers, and tech leads, and hosts a podcast featuring conversations with practitioners across the global tech scene. +Owns the Laputa product work and remains the primary owner on the fixture's project notes. -Outside of work, Luca is an avid cyclist who trains regularly and competes in gran fondos across northern Italy. He plays guitar in his downtime, reads widely across technology, business, and fiction, and shares an apartment in Milan with his girlfriend Giulia. He is building the Laputa app as a personal knowledge management tool to organize his notes, relationships, and projects. - -## Notes - -- Driven by curiosity and a desire to understand how things work, from distributed systems to team dynamics -- Prefers building over theorizing; ships fast and iterates based on feedback -- Values autonomy and independence; chose the indie path over a traditional career deliberately -- Balances introversion with a genuine interest in people, which comes through in podcast conversations -- Believes strongly that engineering leadership is a craft that can be learned and taught - -## Collaborations - -- [[24q1-podcast-season-1]] — created and hosted the first season of the Refactoring podcast -- [[24q3-podcast-season-2]] — hosted the second season with expanded guest roster -- [[25q2-podcast-season-3]] — ongoing season with deeper focus on AI and leadership topics -- [[24q1-launch-sponsorship-packages]] — designed and launched the sponsorship program -- [[procedure-weekly-team-sync]] — runs the weekly team sync for Refactoring diff --git a/demo-vault-v2/person-lucia-martinez.md b/demo-vault-v2/person-lucia-martinez.md deleted file mode 100644 index 3f9bcf03..00000000 --- a/demo-vault-v2/person-lucia-martinez.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -aliases: ["Lucia Martinez"] -Is A: Person -Tier: "3rd 🥉" -Tags: ["Podcast Guest"] ---- -# Lucia Martinez - -Tech journalist based in Madrid, covering the European tech and startup scene for a prominent Spanish-language technology publication. Lucia appeared on the podcast to discuss how the European tech ecosystem is perceived from the media side, the challenges of covering a fragmented market across many languages and cultures, and the growing maturity of European tech compared to five years ago. - -## Notes - -- Brings a journalist's rigor to conversation; well-prepared and asks sharp follow-up questions even as a guest -- Her pan-European perspective helped frame the European tech scene in a way that resonated beyond any single country -- Candid about the challenges of tech journalism, including access issues and the pressure from PR-driven narratives -- Expressed interest in being quoted or featured in future Refactoring newsletter issues covering European tech trends - -## Collaborations - -- [[25q2-podcast-season-3]] — recorded episode on covering the European tech scene -- [[topic-italian-startups]] — discussed Italy's position within the broader European tech landscape -- [[procedure-podcast-guest-outreach]] — connected through the European tech media network diff --git a/demo-vault-v2/person-marco-bianchi.md b/demo-vault-v2/person-marco-bianchi.md deleted file mode 100644 index 269a666b..00000000 --- a/demo-vault-v2/person-marco-bianchi.md +++ /dev/null @@ -1,24 +0,0 @@ ---- -aliases: ["Marco Bianchi"] -Is A: Person -Tier: "2nd 🥈" -Tags: ["Team"] ---- -# Marco Bianchi - -Freelance web developer and a key contributor to Refactoring's technical operations. Marco builds and maintains the Refactoring website, landing pages, and various internal tools that support the newsletter and podcast workflows. He joined the team as a contractor in mid-2023 and has proven himself to be reliable, technically sharp, and self-directed. Based in Milan, he works primarily with React, Next.js, and Tailwind CSS, and handles everything from design implementation to performance optimization. - -## Notes - -- Strong frontend skills with good design sensibility; can take a rough mockup and turn it into a polished, responsive page -- Works independently and communicates proactively; rarely needs hand-holding on tasks -- Fast and reliable with turnaround; Luca can trust him with time-sensitive landing page launches for sponsor campaigns -- Growing interest in full-stack development; has been picking up backend skills and contributing to API work -- Luca sees potential for Marco to take on a larger role as the business grows - -## Collaborations - -- [[procedure-weekly-team-sync]] — regular participant in the weekly team sync -- [[event-team-sync-weekly]] — attends and contributes to weekly standups -- [[24q1-launch-sponsorship-packages]] — built the sponsor landing pages and tracking infrastructure -- [[24q2-hire-editor]] — helped set up the hiring page and application workflow diff --git a/demo-vault-v2/person-marco-cecconi.md b/demo-vault-v2/person-marco-cecconi.md deleted file mode 100644 index b201575d..00000000 --- a/demo-vault-v2/person-marco-cecconi.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -aliases: ["Marco Cecconi"] -Is A: Person -Tier: "3rd 🥉" -Tags: ["Podcast Guest"] ---- -# Marco Cecconi - -Engineering director at a major gaming company, leading a distributed team that builds backend infrastructure for multiplayer online games. Marco appeared on the podcast to discuss what high-performance engineering teams look like in the gaming industry, where latency requirements are extreme and the cost of downtime is measured in player churn rather than SLA breaches. He has deep experience managing large-scale, performance-critical systems and the specialized engineering cultures that support them. - -## Notes - -- Engaging storyteller with vivid examples from the gaming industry that made complex infrastructure concepts accessible -- His perspective on how gaming engineering differs from enterprise engineering was eye-opening for the audience -- Italian by origin but has worked internationally for most of his career; brings a global perspective with an Italian sensibility -- Strong opinions on hiring for performance-critical roles; shared a unique interview process that prioritizes systems thinking - -## Collaborations - -- [[24q1-podcast-season-1]] — recorded episode on high-performance engineering teams -- [[topic-team-leadership]] — discussed engineering culture and team management in high-stakes environments -- [[procedure-podcast-guest-outreach]] — connected through the Italian tech diaspora network diff --git a/demo-vault-v2/person-marcus-weber.md b/demo-vault-v2/person-marcus-weber.md deleted file mode 100644 index ba1221b1..00000000 --- a/demo-vault-v2/person-marcus-weber.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -aliases: ["Marcus Weber"] -Is A: Person -Tier: "3rd 🥉" -Tags: ["Podcast Guest"] ---- -# Marcus Weber - -Software architect and author of "Scaling Teams," a well-regarded book on engineering culture and organizational design for growing tech companies. Based in Munich, Marcus has spent two decades in the European tech industry and now consults with scale-ups on engineering organization design. He appeared on the podcast to discuss the principles from his book and how engineering culture evolves as companies scale from 10 to 1000 engineers. - -## Notes - -- Thoughtful and measured in conversation; brings an academic rigor to practical topics without being dry -- His book heavily influenced how Luca thinks about team structure, and having him on the podcast was a personal highlight -- Shared specific case studies from his consulting work (anonymized) that made abstract concepts concrete -- Advocates for "culture as architecture" — the idea that organizational design is as important as system design - -## Collaborations - -- [[24q3-podcast-season-2]] — recorded episode on engineering culture and scaling teams -- [[topic-team-leadership]] — core topic area aligned with his book and consulting work -- [[procedure-podcast-guest-outreach]] — reached out directly after reading his book diff --git a/demo-vault-v2/person-maria-colombo.md b/demo-vault-v2/person-maria-colombo.md deleted file mode 100644 index b0b44f29..00000000 --- a/demo-vault-v2/person-maria-colombo.md +++ /dev/null @@ -1,23 +0,0 @@ ---- -aliases: ["Maria Colombo"] -Is A: Person -Tier: "1st 🥇" -Tags: ["Family"] ---- -# Maria Colombo - -Luca's mother, a retired school teacher living near Lake Como in a house where Luca and Elena grew up. Maria spent thirty years teaching elementary school in the local community and is beloved by generations of former students. Now retired, she tends a beautiful garden, cooks elaborate meals for family visits, and stays active in local community activities. She is the emotional anchor of the Rossi family and the source of most of Luca's best recipes. - -Maria is proud of both her children, even if she does not fully understand what Luca does for a living ("something with computers and a podcast"). She worries about him working too much and not eating enough, as Italian mothers do, and never misses an opportunity to remind him that there is more to life than staring at a screen. Luca visits her most weekends when he is not traveling, often bringing Giulia along. - -## Notes - -- An incredible cook whose pasta recipes are Luca's most treasured family heirloom; her risotto alla milanese is legendary -- Warm, nurturing, and gently persistent; the kind of person who makes everyone feel at home within minutes -- Has adapted to technology more than expected; uses WhatsApp proficiently and video calls with Elena in Rome regularly -- Her garden near Lake Como produces tomatoes, basil, and zucchini that she insists are superior to anything available in Milan -- Loves Giulia and has already started dropping hints about grandchildren, which Luca deflects with practiced skill - -## Collaborations - -- [[event-dinner-family]] — the heart of every family gathering; her home near Lake Como is the family meeting point diff --git a/demo-vault-v2/person-marta-pellegrini.md b/demo-vault-v2/person-marta-pellegrini.md deleted file mode 100644 index 5c42a6cf..00000000 --- a/demo-vault-v2/person-marta-pellegrini.md +++ /dev/null @@ -1,20 +0,0 @@ ---- -aliases: ["Marta Pellegrini"] -Is A: Person -Tier: "3rd 🥉" -Tags: ["Friend"] ---- -# Marta Pellegrini - -Personal trainer at Luca's gym in Milan, specializing in functional strength training and injury prevention for endurance athletes. Marta helped Luca design a strength and mobility program to complement his cycling training, addressing the common cyclist issues of tight hip flexors and weak core stability. They have a friendly relationship that extends slightly beyond the trainer-client dynamic, occasionally chatting about fitness, nutrition, and Milan life. - -## Notes - -- Knowledgeable and practical; does not push fads or unnecessary supplements, just solid evidence-based programming -- Her strength program noticeably improved Luca's climbing power and reduced his lower back discomfort on long rides -- Encouraging but not pushy; good at motivating without the aggressive personal trainer stereotype -- Also works with several other cyclists and runners, so she understands endurance athlete needs well - -## Collaborations - -- [[topic-cycling-training]] — designed Luca's complementary strength training program for cycling performance diff --git a/demo-vault-v2/person-massimo-artusi.md b/demo-vault-v2/person-massimo-artusi.md deleted file mode 100644 index b66196e9..00000000 --- a/demo-vault-v2/person-massimo-artusi.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -aliases: ["Massimo Artusi"] -Is A: Person -Tier: "3rd 🥉" -Tags: ["Podcast Guest"] ---- -# Massimo Artusi - -Open source community leader and advocate for sustainable funding models in open source software. Based in Rome, Massimo has spent years organizing and contributing to Italian and European open source communities. He appeared on the podcast to discuss the sustainability crisis in open source, covering funding models, maintainer burnout, and the tension between corporate reliance on OSS and the lack of financial support for the people who build it. - -## Notes - -- Passionate and articulate on OSS sustainability; his personal experience as a burnt-out maintainer gave the episode emotional weight -- Practical rather than ideological; acknowledges that different projects need different funding models -- Well-connected in the European open source community; offered to introduce Luca to several potential future guests -- The episode resonated particularly well with the audience, generating significant discussion in the community Discord - -## Collaborations - -- [[24q3-podcast-season-2]] — recorded episode on sustainability in open source software -- [[topic-italian-startups]] — discussed the Italian open source ecosystem and its challenges -- [[procedure-podcast-guest-outreach]] — connected through the Italian open source conference circuit diff --git a/demo-vault-v2/person-matteo-cellini.md b/demo-vault-v2/person-matteo-cellini.md index 758bf932..e8cd716b 100644 --- a/demo-vault-v2/person-matteo-cellini.md +++ b/demo-vault-v2/person-matteo-cellini.md @@ -1,29 +1,11 @@ --- -aliases: ["Matteo Cellini"] -Is A: Person -Tier: "1st 🥇" -Tags: ["Team"] +type: Person +aliases: + - "[[Matteo Cellini]]" +tier: 1st --- + # Matteo Cellini -Head of Partnerships at Refactoring, responsible for managing sponsor relationships, driving revenue growth, and developing new business opportunities. Matteo joined the team in 2022 and has been instrumental in building Refactoring's sponsorship program from scratch into a sustainable revenue stream. He handles the entire sponsor lifecycle from outreach and negotiation through onboarding and ongoing relationship management, freeing Luca to focus on content creation and product development. +Owns sponsor outreach and makes the responsibility/procedure relationships feel like real working notes. -Matteo has a background in business development at Italian tech companies and brings a structured, relationship-driven approach to partnerships that works well with the developer-focused brands that sponsor Refactoring. He is based in Milan and works closely with Luca on business strategy and growth planning. - -## Notes - -- Excellent relationship builder; sponsors consistently praise the quality of their interactions with him -- Structured and organized in his approach to pipeline management; uses a clear system for tracking opportunities -- Has grown significantly in the role; started handling small sponsorships and now manages the entire partnerships function -- Good at pushing back on Luca's tendency to over-customize for individual sponsors, keeping processes scalable -- They have developed a strong working rhythm; biweekly 1-on-1s keep alignment without excessive meetings - -## Collaborations - -- [[procedure-biweekly-1on1-matteo]] — regular biweekly check-ins with Luca on partnerships and revenue -- [[event-1on1-matteo-weekly]] — recurring 1-on-1 meetings -- [[procedure-weekly-team-sync]] — core participant in the weekly team sync -- [[event-team-sync-weekly]] — attends weekly standups -- [[24q1-launch-sponsorship-packages]] — led the design and launch of the sponsorship program -- [[procedure-sponsor-onboarding]] — built and owns the sponsor onboarding workflow -- [[25q2-team-retreat]] — key participant in team retreat planning and activities diff --git a/demo-vault-v2/person-matteo-gentile.md b/demo-vault-v2/person-matteo-gentile.md deleted file mode 100644 index 1e9fe915..00000000 --- a/demo-vault-v2/person-matteo-gentile.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -aliases: ["Matteo Gentile"] -Is A: Person -Tier: "3rd 🥉" -Tags: ["Podcast Guest"] ---- -# Matteo Gentile - -Active Node.js contributor and open source developer based in Italy, working as a senior engineer at a European tech company while maintaining significant involvement in the Node.js ecosystem. Matteo appeared on the podcast to discuss the reality of contributing to large open source projects, from navigating governance structures and review processes to balancing OSS work with a full-time job. His hands-on experience as a contributor gave the episode a practitioner's perspective that resonated with developers thinking about getting involved in open source. - -## Notes - -- Humble and practical; demystified the process of contributing to a major project like Node.js -- Shared a step-by-step approach for new contributors that the audience found immediately actionable -- Honest about the time commitment and occasional frustrations of open source contribution -- His Italian perspective on the global open source community added a personal dimension to the conversation - -## Collaborations - -- [[24q1-podcast-season-1]] — recorded episode on open source contributions and the Node.js ecosystem -- [[topic-italian-startups]] — discussed the Italian developer community's presence in global open source -- [[procedure-podcast-guest-outreach]] — connected through the Italian Node.js community diff --git a/demo-vault-v2/person-mattia-de-luca.md b/demo-vault-v2/person-mattia-de-luca.md deleted file mode 100644 index c88accb0..00000000 --- a/demo-vault-v2/person-mattia-de-luca.md +++ /dev/null @@ -1,20 +0,0 @@ ---- -aliases: ["Mattia De Luca"] -Is A: Person -Tier: "3rd 🥉" -Tags: ["Friend"] ---- -# Mattia De Luca - -Davide Conti's roommate and a data engineer working at a Milan-based analytics company. Mattia is part of the extended friend group that Luca sees through Davide, usually at weekend outings, group dinners, or casual evenings at their apartment. He is friendly, low-key, and has a quiet expertise in data engineering that occasionally makes for interesting technical conversations when the group gathers. - -## Notes - -- Specializes in data pipelines and Spark; has interesting perspectives on the intersection of data engineering and ML -- More introverted than Davide but opens up over a couple of beers and a good technical topic -- Shares Luca's interest in productivity tools and note-taking systems; they have compared setups -- Easy to be around; adds to the group dynamic without needing to be the center of attention - -## Collaborations - -- [[event-dinner-family]] — occasional presence at group dinners through the Davide connection diff --git a/demo-vault-v2/person-michael-brown.md b/demo-vault-v2/person-michael-brown.md deleted file mode 100644 index 0e72be34..00000000 --- a/demo-vault-v2/person-michael-brown.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -aliases: ["Michael Brown"] -Is A: Person -Tier: "3rd 🥉" -Tags: ["Sponsor"] ---- -# Michael Brown - -Sponsor contact at GitHub, working in developer relations and sponsorship programs. Michael manages GitHub's content partnership investments across the European developer media landscape, including podcast and newsletter sponsorships. Based in London, he has a developer relations background and is focused on expanding GitHub's community presence beyond traditional channels. - -## Notes - -- Professional and well-organized; provides comprehensive campaign briefs with clear brand guidelines -- GitHub's brand is so well-known that the sponsorship requires minimal explanation to the audience -- Thoughtful about how sponsorship integrates with editorial content; does not push for disruptive ad formats -- Has connected Luca with other people at GitHub for potential guest appearances and content collaborations - -## Collaborations - -- [[24q1-launch-sponsorship-packages]] — GitHub onboarded as a premium sponsor -- [[procedure-sponsor-onboarding]] — well-structured onboarding with established processes -- [[event-sponsor-call-github]] — regular alignment calls on campaign strategy diff --git a/demo-vault-v2/person-natalie-chang.md b/demo-vault-v2/person-natalie-chang.md deleted file mode 100644 index 846ad971..00000000 --- a/demo-vault-v2/person-natalie-chang.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -aliases: ["Natalie Chang"] -Is A: Person -Tier: "3rd 🥉" -Tags: ["Podcast Guest"] ---- -# Natalie Chang - -Investor at a deep-tech focused venture capital fund based in San Francisco, specializing in B2B SaaS and developer tools investments. Natalie appeared on the podcast to discuss what VCs actually look for when evaluating B2B SaaS companies, covering topics from metrics and traction thresholds to founder qualities and market timing. Her perspective from the investor side offered the audience a rare window into how funding decisions are made. - -## Notes - -- Unusually candid for a VC; willing to discuss the limitations and biases of the venture model -- Shared specific frameworks for evaluating B2B SaaS metrics (NRR, CAC payback, logo retention) that were immediately useful -- Her balanced view on bootstrapping vs. venture funding made the episode a natural companion piece to the James Murphy episode -- The episode attracted a slightly different audience segment (more founder-oriented) which helped broaden the podcast's reach - -## Collaborations - -- [[24q3-podcast-season-2]] — recorded episode on VC perspectives in B2B SaaS -- [[topic-saas-business]] — discussed SaaS metrics, funding, and growth from the investor perspective -- [[procedure-podcast-guest-outreach]] — connected through the venture capital Twitter community diff --git a/demo-vault-v2/person-nicola-fabbri.md b/demo-vault-v2/person-nicola-fabbri.md deleted file mode 100644 index 2f91c7f9..00000000 --- a/demo-vault-v2/person-nicola-fabbri.md +++ /dev/null @@ -1,20 +0,0 @@ ---- -aliases: ["Nicola Fabbri"] -Is A: Person -Tier: "3rd 🥉" -Tags: ["Friend"] ---- -# Nicola Fabbri - -Luca's neighbor in Milan, a retired university professor who taught philosophy at the Universita Statale for over thirty years. Nicola lives in the apartment directly above Luca's and they have developed a pleasant neighborly friendship, often sharing conversations on the building's shared terrace in the evenings. He brings a philosophical depth and historical perspective to discussions that Luca finds intellectually refreshing and completely outside his usual tech-focused world. - -## Notes - -- Remarkably well-read across philosophy, history, and literature; every conversation introduces Luca to something new -- Has a gentle, Socratic way of asking questions that makes Luca rethink assumptions about technology and progress -- Enjoys espresso with Luca on the terrace, especially on warm evenings; their conversations can stretch for hours -- Curious about technology in an abstract sense; asks questions about AI and automation from a philosophical perspective - -## Collaborations - -- [[event-dinner-family]] — occasionally joins building community gatherings and terrace dinners diff --git a/demo-vault-v2/person-nina-petersen.md b/demo-vault-v2/person-nina-petersen.md deleted file mode 100644 index b0512696..00000000 --- a/demo-vault-v2/person-nina-petersen.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -aliases: ["Nina Petersen"] -Is A: Person -Tier: "3rd 🥉" -Tags: ["Podcast Guest"] ---- -# Nina Petersen - -AI researcher based in Copenhagen, working at the intersection of machine learning research and production engineering at a Nordic AI startup. Nina appeared on the podcast to discuss the gap between AI research and practical AI deployment, covering the challenges of putting ML models into production, managing model drift, and building teams that bridge the research-engineering divide. She has a PhD in machine learning and several years of industry experience deploying models at scale. - -## Notes - -- Rare combination of deep research expertise and practical production experience; can speak to both audiences -- Her framework for evaluating when ML is the right solution (vs. simpler approaches) was a standout moment in the episode -- Candid about the failures and false starts in her own work, which made the conversation honest and relatable -- Follows up with thoughtful commentary on social media after episodes air; good at extending the conversation - -## Collaborations - -- [[25q2-podcast-season-3]] — recorded episode on practical AI in production environments -- [[topic-ai-ml]] — core topic area for the conversation -- [[procedure-podcast-guest-outreach]] — connected through the Nordic AI research community diff --git a/demo-vault-v2/person-nonna-lucia.md b/demo-vault-v2/person-nonna-lucia.md deleted file mode 100644 index 05f54bfe..00000000 --- a/demo-vault-v2/person-nonna-lucia.md +++ /dev/null @@ -1,23 +0,0 @@ ---- -aliases: ["Nonna Lucia"] -Is A: Person -Tier: "1st 🥇" -Tags: ["Family"] ---- -# Nonna Lucia - -Luca's maternal grandmother, 87 years old, living in Lecco on the eastern branch of Lake Como. Nonna Lucia is the matriarch of the family, a woman of extraordinary warmth, resilience, and unshakeable opinions about how things should be done, particularly in the kitchen. Luca visits her at least once a month, usually on a Sunday, and these visits are among his most cherished rituals. Her risotto is legendary in the family, and Luca has spent years trying to replicate it without ever quite matching her version. - -She grew up in Lecco, married young, raised three children, and has lived through the complete transformation of the Italian economy from agricultural to industrial to digital. She does not pretend to understand what Luca does for work, but she is fiercely proud of him and never fails to tell her friends at church about "her grandson's important computer business." - -## Notes - -- Makes the best risotto in Lombardy, possibly in all of Italy; the recipe is allegedly simple but no one else can replicate it -- Sharp as a tack despite her age; follows Italian politics closely and has strong opinions about everything -- Tells stories about Lecco in the 1950s and 60s that Luca finds both fascinating and grounding -- Absolutely adores Giulia and insists she is "the one" every time Luca visits, whether Giulia is there or not -- Her home in Lecco is filled with decades of family photos, handwritten recipe cards, and the smell of something always cooking - -## Collaborations - -- [[event-dinner-family]] — the anchor of family gatherings; her home in Lecco is where the extended family convenes for holidays diff --git a/demo-vault-v2/person-olivia-martinez.md b/demo-vault-v2/person-olivia-martinez.md deleted file mode 100644 index a4a3a673..00000000 --- a/demo-vault-v2/person-olivia-martinez.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -aliases: ["Olivia Martinez"] -Is A: Person -Tier: "3rd 🥉" -Tags: ["Sponsor"] ---- -# Olivia Martinez - -Sponsor contact at Lemon Squeezy, managing creator economy partnerships and content sponsorships. Olivia handles the relationship for Lemon Squeezy's podcast and newsletter sponsorship, targeting indie developers and creators who build and sell digital products. Based in Austin, Texas, she comes from a creator economy background and understands the audience of solo founders and small teams. - -## Notes - -- Enthusiastic and proactive; regularly suggests creative ways to integrate Lemon Squeezy into content beyond standard ad reads -- Lemon Squeezy's positioning as a merchant of record for digital products aligns well with the indie developer audience -- Provides ad copy that is conversational and natural; minimal editing needed before delivery -- Interested in long-term partnership and has discussed potential co-branded content around digital product launches - -## Collaborations - -- [[24q1-launch-sponsorship-packages]] — Lemon Squeezy onboarded as a sponsor -- [[procedure-sponsor-onboarding]] — straightforward onboarding process with clear expectations -- [[event-sponsor-call-lemonsqueezy]] — periodic check-in calls on campaign performance diff --git a/demo-vault-v2/person-paco-furiani.md b/demo-vault-v2/person-paco-furiani.md deleted file mode 100644 index 4b902957..00000000 --- a/demo-vault-v2/person-paco-furiani.md +++ /dev/null @@ -1,29 +0,0 @@ ---- -aliases: ["Paco Furiani"] -Is A: Person -Tier: "1st 🥇" -Tags: ["Team"] ---- -# Paco Furiani - -Head of Operations at Refactoring, responsible for keeping the entire business running smoothly behind the scenes. Paco manages billing, subscriptions, internal tools, workflows, logistics, and the operational infrastructure that allows Luca to focus on content and product. He joined Refactoring in its early days and has grown with the business, building operational systems from scratch as the company scaled from a solo newsletter to a multi-format content business with sponsors, a team, and complex workflows. - -Paco has a background in operations and project management at Italian tech startups, and brings a methodical, systems-oriented approach to everything he touches. Based in Milan, he works closely with Luca and Matteo on day-to-day business operations and is the person the team turns to when something needs to get done reliably and on time. - -## Notes - -- Exceptionally organized and process-driven; has built the operational backbone that makes Refactoring run efficiently -- Calm under pressure and imperturbable; the person everyone trusts when things go sideways -- Takes ownership of problems end-to-end; Luca can hand off operational concerns and trust they will be resolved -- Has a talent for finding and implementing the right tools for workflows without over-engineering the stack -- Luca considers him indispensable to the business; their biweekly 1-on-1s are among the most productive meetings on the calendar - -## Collaborations - -- [[procedure-biweekly-1on1-paco]] — regular biweekly check-ins with Luca on operations and logistics -- [[event-1on1-paco-weekly]] — recurring 1-on-1 meetings -- [[procedure-weekly-team-sync]] — core participant in the weekly team sync -- [[event-team-sync-weekly]] — attends and contributes to weekly standups -- [[24q1-launch-sponsorship-packages]] — built the billing and invoicing workflow for sponsors -- [[procedure-sponsor-onboarding]] — manages the operational side of sponsor onboarding -- [[25q2-team-retreat]] — handled logistics and planning for the team retreat diff --git a/demo-vault-v2/person-paolo-bergamo.md b/demo-vault-v2/person-paolo-bergamo.md deleted file mode 100644 index ddf8d120..00000000 --- a/demo-vault-v2/person-paolo-bergamo.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -aliases: ["Paolo Bergamo"] -Is A: Person -Tier: "3rd 🥉" -Tags: ["Podcast Guest"] ---- -# Paolo Bergamo - -CTO of an Italian edtech startup building a learning management platform for European universities. Based in Milan, Paolo appeared on the podcast to discuss the specific challenges and opportunities of building technology companies in Italy, from navigating bureaucracy and talent markets to leveraging the unique advantages of the Italian tech ecosystem. His perspective as a CTO building a venture-backed company in Italy provided a grounded, realistic view that contrasted with both Silicon Valley optimism and European tech pessimism. - -## Notes - -- Balanced and honest about both the difficulties and the underappreciated strengths of building tech in Italy -- His comments on Italian engineering talent (high quality, undervalued internationally) resonated strongly with local listeners -- Practical advice on dealing with Italian fiscal and regulatory requirements was uniquely useful for the Italian audience segment -- Well-connected in the Milan and Italian startup ecosystem; has made several useful introductions since the episode - -## Collaborations - -- [[24q1-podcast-season-1]] — recorded episode on building tech companies in Italy -- [[topic-italian-startups]] — core topic of the conversation -- [[procedure-podcast-guest-outreach]] — connected through the Milan startup community diff --git a/demo-vault-v2/person-patrick-nguyen.md b/demo-vault-v2/person-patrick-nguyen.md deleted file mode 100644 index 3249bc19..00000000 --- a/demo-vault-v2/person-patrick-nguyen.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -aliases: ["Patrick Nguyen"] -Is A: Person -Tier: "3rd 🥉" -Tags: ["Podcast Guest"] ---- -# Patrick Nguyen - -CEO and co-founder of an API platform company based in San Francisco, building infrastructure that helps developers build, manage, and monetize APIs. Patrick appeared on the podcast to discuss API-first business models, the economics of developer platforms, and how to build a company around API infrastructure in an increasingly competitive market. He has a technical background as a former software engineer at AWS before transitioning to the business side. - -## Notes - -- Clear and structured thinker; broke down the API economy into accessible segments that resonated with both technical and business-minded listeners -- His framework for evaluating API-first vs. API-adjacent business models provided a useful mental model -- Candid about the competitive dynamics of the API infrastructure space and the challenges of developer go-to-market -- The episode attracted listeners from the developer tools community, broadening the podcast's reach - -## Collaborations - -- [[24q3-podcast-season-2]] — recorded episode on API-first business models -- [[topic-saas-business]] — discussed developer platform economics and API business strategy -- [[procedure-podcast-guest-outreach]] — connected through the developer tools community on Twitter diff --git a/demo-vault-v2/person-peter-schmidt.md b/demo-vault-v2/person-peter-schmidt.md deleted file mode 100644 index 656d0ad6..00000000 --- a/demo-vault-v2/person-peter-schmidt.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -aliases: ["Peter Schmidt"] -Is A: Person -Tier: "3rd 🥉" -Tags: ["Sponsor"] ---- -# Peter Schmidt - -Sponsor contact at Raycast, managing productivity tools marketing and developer content sponsorships. Peter oversees Raycast's investment in podcast and newsletter sponsorships targeting power users and developers who care about workflow optimization. Based in Berlin, he has a product marketing background and is focused on growing Raycast's presence in the European developer community. - -## Notes - -- Raycast's product aligns naturally with the audience; Luca is a genuine user, which makes the sponsorship authentic -- Professional and efficient in communication; sends clear briefs and approves content quickly -- Understands that developer audiences are skeptical of marketing; crafts messaging that focuses on genuine productivity benefits -- Has explored creative sponsorship formats including sponsored "workflow of the week" segments - -## Collaborations - -- [[24q1-launch-sponsorship-packages]] — Raycast onboarded as a podcast sponsor -- [[procedure-sponsor-onboarding]] — clean onboarding process with well-prepared materials -- [[event-sponsor-call-raycast]] — periodic alignment calls on campaign strategy and messaging diff --git a/demo-vault-v2/person-piergiorgio-conte.md b/demo-vault-v2/person-piergiorgio-conte.md deleted file mode 100644 index 0e7e2876..00000000 --- a/demo-vault-v2/person-piergiorgio-conte.md +++ /dev/null @@ -1,23 +0,0 @@ ---- -aliases: ["Piergiorgio Conte"] -Is A: Person -Tier: "3rd 🥉" -Tags: ["Podcast Guest"] ---- -# Piergiorgio Conte - -CTO of a large Italian enterprise software company, leading a digital transformation initiative that spans legacy system modernization, cloud migration, and cultural change across a 500-person engineering organization. Piergiorgio appeared on the podcast to discuss the reality of digital transformation in established Italian companies, where technical challenges are often secondary to organizational inertia and cultural resistance to change. - -## Notes - -- Remarkably candid for a CTO of a large company; spoke openly about failures and missteps in the transformation journey -- His perspective on the gap between digital transformation as sold by consultancies and as experienced by practitioners was eye-opening -- Deep understanding of Italian business culture and how it affects technology adoption and organizational change -- The episode resonated particularly with listeners working in mid-to-large companies going through similar transitions - -## Collaborations - -- [[24q3-podcast-season-2]] — recorded episode on digital transformation in Italian enterprise -- [[topic-italian-startups]] — discussed the Italian enterprise tech landscape and its evolution -- [[topic-team-leadership]] — covered organizational change management and leadership during transformation -- [[procedure-podcast-guest-outreach]] — connected through the Italian CTO network diff --git a/demo-vault-v2/person-priya-sharma.md b/demo-vault-v2/person-priya-sharma.md deleted file mode 100644 index e8852e84..00000000 --- a/demo-vault-v2/person-priya-sharma.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -aliases: ["Priya Sharma"] -Is A: Person -Tier: "3rd 🥉" -Tags: ["Podcast Guest"] ---- -# Priya Sharma - -Engineering manager leading a growth engineering team at a mid-sized SaaS company based in London. Priya appeared on the podcast to discuss experimentation culture in engineering teams, covering how to build a systematic approach to A/B testing, how to balance experimentation velocity with engineering quality, and how to create a culture where learning from failed experiments is valued as much as winning ones. - -## Notes - -- Energetic and data-driven communicator; backs up every opinion with specific metrics and examples -- Her practical framework for prioritizing experiments based on learning value rather than expected uplift was a standout insight -- Honest about the organizational friction that experimentation teams face, especially when experiments conflict with roadmap commitments -- The episode performed particularly well with engineering managers looking to introduce more systematic experimentation - -## Collaborations - -- [[25q2-podcast-season-3]] — recorded episode on experimentation culture in engineering teams -- [[topic-saas-business]] — discussed growth engineering and experimentation in SaaS -- [[procedure-podcast-guest-outreach]] — connected through the London engineering management community diff --git a/demo-vault-v2/person-rachel-green.md b/demo-vault-v2/person-rachel-green.md deleted file mode 100644 index 8a2351b8..00000000 --- a/demo-vault-v2/person-rachel-green.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -aliases: ["Rachel Green"] -Is A: Person -Tier: "3rd 🥉" -Tags: ["Sponsor"] ---- -# Rachel Green - -Sponsor contact at Retool, managing developer content sponsorships and partnership programs. Rachel handles Retool's podcast and newsletter sponsorship investments targeting engineering teams and technical leaders who build internal tools. Based in San Francisco, she has a developer marketing background and is focused on reaching engineering decision-makers through high-quality content partnerships. - -## Notes - -- Well-organized and professional; provides detailed campaign briefs with specific messaging guidelines -- Retool's positioning around internal tools resonates with the engineering leader audience, making ad reads feel relevant -- Responsive and low-maintenance; a reliable partner who delivers on commitments without drama -- Has expressed interest in sponsoring specific themed episodes related to developer productivity and internal tooling - -## Collaborations - -- [[24q1-launch-sponsorship-packages]] — Retool onboarded as a podcast sponsor -- [[procedure-sponsor-onboarding]] — efficient onboarding with clear deliverables -- [[event-sponsor-call-retool]] — periodic check-in calls on campaign performance diff --git a/demo-vault-v2/person-raj-patel.md b/demo-vault-v2/person-raj-patel.md deleted file mode 100644 index fd701590..00000000 --- a/demo-vault-v2/person-raj-patel.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -aliases: ["Raj Patel"] -Is A: Person -Tier: "3rd 🥉" -Tags: ["Podcast Guest"] ---- -# Raj Patel - -Founder and CEO of DevToolsCo, a developer tools company building IDE extensions and workflow automation for engineering teams. Based in London, Raj appeared on the podcast to discuss the art and business of building developer tools, covering topics from developer experience design to go-to-market strategies for tools that sell to engineers. His background as a former staff engineer at a large tech company gives him both the technical credibility and the product instincts needed to build in this competitive space. - -## Notes - -- Deeply passionate about developer experience; can articulate exactly why certain tools feel magical while others feel frustrating -- Shared a practical framework for measuring developer tool adoption that went beyond simple usage metrics -- Honest about the difficulty of building a business selling to developers, who are notoriously resistant to paying for tools -- The episode resonated particularly well with the developer tools founders in the audience - -## Collaborations - -- [[24q3-podcast-season-2]] — recorded episode on building developer tools -- [[topic-saas-business]] — discussed developer tools as a business category -- [[procedure-podcast-guest-outreach]] — connected through the London developer tools community diff --git a/demo-vault-v2/person-roberto-rossi.md b/demo-vault-v2/person-roberto-rossi.md deleted file mode 100644 index 91567f9d..00000000 --- a/demo-vault-v2/person-roberto-rossi.md +++ /dev/null @@ -1,23 +0,0 @@ ---- -aliases: ["Roberto Rossi"] -Is A: Person -Tier: "1st 🥇" -Tags: ["Family"] ---- -# Roberto Rossi - -Luca's father, a retired mechanical engineer living near Lake Como with Maria. Roberto spent his career working at engineering firms in the Lombardy industrial district, designing mechanical components for manufacturing equipment. Now retired, he has thrown himself into woodworking with the same precision and methodical approach he brought to engineering. His workshop in the garage is immaculate, and he produces beautiful handmade furniture and small wooden objects that he gives as gifts to family and friends. - -Roberto is a quiet, steady presence in the Rossi family. He is proud of both his children but expresses it through actions rather than words: fixing things around Luca's apartment when he visits Milan, building a custom bookshelf for Elena's apartment in Rome, ensuring the family home is always in perfect order. He understands Luca's engineering mindset better than Maria does and occasionally asks thoughtful questions about the business side of Refactoring. - -## Notes - -- The source of Luca's engineering discipline; Roberto's approach to problem-solving clearly shaped how Luca thinks about software -- His woodworking has become genuinely impressive; the bookshelves he built for Luca's apartment are a favorite conversation piece -- Dry, understated humor that Luca has inherited; they can communicate entire sentiments with a look or a half-sentence -- Enjoys cycling casually and sometimes joins Luca for easy rides along the lake when Luca visits -- Reads the Refactoring newsletter, though he admits most of the software-specific content is beyond him; still, he reads every issue - -## Collaborations - -- [[event-dinner-family]] — central figure at family gatherings at the Lake Como home diff --git a/demo-vault-v2/person-sara-ricci.md b/demo-vault-v2/person-sara-ricci.md deleted file mode 100644 index f3d24308..00000000 --- a/demo-vault-v2/person-sara-ricci.md +++ /dev/null @@ -1,29 +0,0 @@ ---- -aliases: ["Sara Ricci"] -Is A: Person -Tier: "1st 🥇" -Tags: ["Team"] ---- -# Sara Ricci - -Editor at Refactoring, hired in Q2 2024 to bring editorial rigor and consistency to the newsletter and podcast show notes. Sara has a sharp eye for structure and clarity in technical writing, helping transform Luca's raw drafts into polished, well-organized pieces that maintain his voice while improving readability. Before joining Refactoring, she worked as an editor at a Milan-based tech publication, where she developed deep familiarity with writing for engineering audiences. - -Sara has quickly become an essential part of the content pipeline. She reviews and edits every newsletter issue before publication, writes show notes for podcast episodes, and has started contributing to the editorial calendar with topic suggestions and series concepts. Based in Milan, she works closely with Luca on content strategy and quality. - -## Notes - -- Excellent at preserving the author's voice while improving structure and flow; Luca's drafts are noticeably better after her pass -- Fast and reliable with turnaround; rarely misses a deadline, even on tight publication schedules -- Has good instincts for what will resonate with the audience; her topic suggestions consistently perform well -- Growing into a more strategic editorial role beyond pure editing; taking on more ownership of the content calendar -- Their biweekly 1-on-1s have evolved from pure editing feedback to broader content strategy discussions - -## Collaborations - -- [[procedure-biweekly-1on1-sara]] — regular biweekly check-ins with Luca on editorial quality and content strategy -- [[procedure-weekly-team-sync]] — core participant in the weekly team sync -- [[event-team-sync-weekly]] — attends and contributes to weekly standups -- [[24q2-hire-editor]] — hired through a structured search process in Q2 2024 -- [[24q3-podcast-season-2]] — edited show notes and contributed to episode planning -- [[25q2-podcast-season-3]] — increasingly involved in editorial planning for the current season -- [[25q2-team-retreat]] — participant in team retreat planning and activities diff --git a/demo-vault-v2/person-sarah-oconnor.md b/demo-vault-v2/person-sarah-oconnor.md deleted file mode 100644 index 6989533c..00000000 --- a/demo-vault-v2/person-sarah-oconnor.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -aliases: ["Sarah O'Connor"] -Is A: Person -Tier: "3rd 🥉" -Tags: ["Podcast Guest"] ---- -# Sarah O'Connor - -Engineering director at a large US-based tech company, leading multiple teams across infrastructure and platform engineering. Sarah appeared on the podcast to discuss engineering career ladders, the IC vs. management track decision, and how to design progression frameworks that actually work for engineers at different career stages. She has extensive experience both as an individual contributor who reached the staff-plus level and as a manager who now oversees engineering directors. - -## Notes - -- Uniquely qualified to discuss career ladders having experienced both sides; her perspective bridges the IC and management worlds -- Shared a practical, open-source career progression framework that several listeners adopted at their own companies -- Thoughtful about the failure modes of career ladders, including "title inflation" and the tendency to conflate seniority with management -- The episode generated significant discussion in the community, particularly around the "senior engineer plateau" topic - -## Collaborations - -- [[24q1-podcast-season-1]] — recorded episode on engineering career ladders -- [[topic-team-leadership]] — discussed career progression and engineering management -- [[procedure-podcast-guest-outreach]] — connected through the engineering management community on Twitter diff --git a/demo-vault-v2/person-silvia-mancini.md b/demo-vault-v2/person-silvia-mancini.md deleted file mode 100644 index 8e298d7a..00000000 --- a/demo-vault-v2/person-silvia-mancini.md +++ /dev/null @@ -1,20 +0,0 @@ ---- -aliases: ["Silvia Mancini"] -Is A: Person -Tier: "3rd 🥉" -Tags: ["Friend"] ---- -# Silvia Mancini - -Doctor working in internal medicine at a hospital in Milan. Silvia and Luca studied together at Politecnico di Milano before she switched to medicine, and they have maintained a friendship that spans nearly fifteen years. They catch up every few months over dinner or a long walk, and these conversations are valuable to Luca precisely because they are entirely outside the tech world. Silvia provides a grounding perspective on life, work-life balance, and what meaningful work looks like in a completely different profession. - -## Notes - -- Intellectually sharp and empathetic; the kind of person who listens carefully and asks questions that cut through noise -- Her perspective on burnout, work-life balance, and high-pressure careers is informed by first-hand medical experience -- Luca appreciates that she never asks about his subscriber count or revenue; their friendship operates on a different register -- Occasional running partner when their schedules align; they have done a couple of 10k races together - -## Collaborations - -- [[event-dinner-family]] — occasional participant in broader friend group gatherings in Milan diff --git a/demo-vault-v2/person-simone-bianchi.md b/demo-vault-v2/person-simone-bianchi.md deleted file mode 100644 index ec6f35ae..00000000 --- a/demo-vault-v2/person-simone-bianchi.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -aliases: ["Simone Bianchi"] -Is A: Person -Tier: "3rd 🥉" -Tags: ["Podcast Guest"] ---- -# Simone Bianchi - -Platform architect at a European scale-up, leading the design and implementation of their internal developer platform. Based in Milan, Simone appeared on the podcast to discuss the emerging discipline of platform engineering, covering how to build internal developer platforms that actually get adopted, the organizational dynamics of platform teams, and the difference between platform engineering and traditional DevOps. His practical experience building a platform serving over 200 developers gave the conversation real-world grounding. - -## Notes - -- Deeply knowledgeable about the platform engineering space; follows the community closely and contributes to open standards discussions -- Practical and opinionated; willing to say what does not work in platform engineering, not just what does -- His framework for measuring platform adoption (developer satisfaction surveys, time-to-first-deployment) was actionable and well-received -- Being based in Milan made the recording logistics easy; they recorded in person at a local coworking space - -## Collaborations - -- [[25q2-podcast-season-3]] — recorded episode on internal developer platforms -- [[topic-team-leadership]] — discussed platform team organizational design and developer experience -- [[procedure-podcast-guest-outreach]] — connected through the Milan engineering community diff --git a/demo-vault-v2/person-sophie-laurent.md b/demo-vault-v2/person-sophie-laurent.md deleted file mode 100644 index f7b75e17..00000000 --- a/demo-vault-v2/person-sophie-laurent.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -aliases: ["Sophie Laurent"] -Is A: Person -Tier: "3rd 🥉" -Tags: ["Sponsor"] ---- -# Sophie Laurent - -Sponsor contact at Figma, managing design and developer marketing partnerships. Sophie oversees Figma's content sponsorship program targeting the intersection of design and engineering, which is a natural fit for Refactoring's audience of engineering leaders who work closely with design teams. Based in Paris, she has a background in design community building and understands the nuances of marketing to a technical-creative audience. - -## Notes - -- Figma's brand is well-respected among the audience, making the sponsorship feel like a natural fit -- Provides thoughtful campaign briefs that position Figma as a collaboration tool for engineers, not just designers -- Creative about sponsorship formats; proposed sponsored episodes on design-engineering collaboration topics -- Professional and easy to work with; communication is always clear and timely - -## Collaborations - -- [[24q1-launch-sponsorship-packages]] — Figma onboarded as a podcast sponsor -- [[procedure-sponsor-onboarding]] — clean onboarding with well-defined deliverables -- [[event-sponsor-call-figma]] — quarterly alignment calls on campaign strategy diff --git a/demo-vault-v2/person-stefano-villa.md b/demo-vault-v2/person-stefano-villa.md deleted file mode 100644 index a35abb15..00000000 --- a/demo-vault-v2/person-stefano-villa.md +++ /dev/null @@ -1,21 +0,0 @@ ---- -aliases: ["Stefano Villa"] -Is A: Person -Tier: "3rd 🥉" -Tags: ["Friend"] ---- -# Stefano Villa - -Old colleague from Luca's pre-Refactoring days when they worked together at a Milan-based tech company. Stefano is now VP of Engineering at a fast-growing Milan scale-up, managing a team of about 60 engineers. They stay in touch through occasional lunches and WhatsApp exchanges, sharing perspectives from their very different vantage points: Luca running an indie content business, Stefano navigating the politics and growth challenges of a scale-up engineering organization. - -## Notes - -- His career trajectory represents the path Luca chose not to take, which makes their conversations interesting to both of them -- Provides Luca with useful insider perspective on what engineering leaders at scale-ups actually care about, which informs podcast content -- Pragmatic and politically savvy; understands organizational dynamics in a way that Luca respects -- Has recommended several good podcast guests from his professional network - -## Collaborations - -- [[topic-team-leadership]] — ongoing conversations about engineering leadership at different scales -- [[procedure-podcast-guest-outreach]] — has referred several guests from his professional network diff --git a/demo-vault-v2/person-thomas-mueller.md b/demo-vault-v2/person-thomas-mueller.md deleted file mode 100644 index ca709f1e..00000000 --- a/demo-vault-v2/person-thomas-mueller.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -aliases: ["Thomas Mueller"] -Is A: Person -Tier: "3rd 🥉" -Tags: ["Sponsor"] ---- -# Thomas Mueller - -Sponsor contact at Datadog, focused on developer audience reach and content partnerships across European tech media. Thomas manages Datadog's podcast and newsletter sponsorship portfolio, targeting engineering teams and platform engineers who make infrastructure tooling decisions. Based in Munich, he has a technical marketing background and understands how to position observability and monitoring products for a sophisticated engineering audience. - -## Notes - -- Datadog's brand and product category are highly relevant to the podcast audience, making ad reads straightforward -- Provides detailed messaging frameworks but trusts Luca to adapt them for natural podcast delivery -- Data-oriented in his approach to sponsorship; always wants to understand audience engagement metrics -- Professional and reliable; one of the more established sponsor relationships in the portfolio - -## Collaborations - -- [[24q1-launch-sponsorship-packages]] — Datadog onboarded as a premium podcast sponsor -- [[procedure-sponsor-onboarding]] — enterprise-grade onboarding with detailed brand guidelines -- [[event-sponsor-call-datadog]] — regular alignment calls on campaign performance and strategy diff --git a/demo-vault-v2/person-tom-richardson.md b/demo-vault-v2/person-tom-richardson.md deleted file mode 100644 index f97f1229..00000000 --- a/demo-vault-v2/person-tom-richardson.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -aliases: ["Tom Richardson"] -Is A: Person -Tier: "3rd 🥉" -Tags: ["Podcast Guest"] ---- -# Tom Richardson - -CEO and co-founder of a developer tools startup based in London, building infrastructure for code review and collaboration workflows. Tom appeared on the podcast to discuss founder-led sales in the developer tools space, covering the unique dynamics of selling to engineers, building trust through technical credibility, and the transition from founder-led sales to a scalable go-to-market motion. He has a strong technical background and has personally closed the company's first 100 customers. - -## Notes - -- Engaging and honest storyteller; shared specific sales conversations (anonymized) that illustrated key principles vividly -- His framework for "technical-first selling" — leading with product demos rather than pitch decks — resonated strongly -- Candid about the mistakes he made in early sales attempts, which made the episode both educational and entertaining -- The episode performed well with the founder segment of the audience and was one of the most shared of the season - -## Collaborations - -- [[25q2-podcast-season-3]] — recorded episode on founder-led sales in developer tools -- [[topic-saas-business]] — discussed go-to-market strategy for developer-focused products -- [[procedure-podcast-guest-outreach]] — connected through the London startup community diff --git a/demo-vault-v2/person-tommaso-greco.md b/demo-vault-v2/person-tommaso-greco.md deleted file mode 100644 index 0ee7c68d..00000000 --- a/demo-vault-v2/person-tommaso-greco.md +++ /dev/null @@ -1,21 +0,0 @@ ---- -aliases: ["Tommaso Greco"] -Is A: Person -Tier: "2nd 🥈" -Tags: ["Friend"] ---- -# Tommaso Greco - -Musician and music teacher based in Milan, teaching piano and music theory at a local conservatory while performing with a jazz trio on weekends. Tommaso and Luca met through mutual friends and bonded over a shared love of music. They jam together occasionally, with Luca on guitar and Tommaso on keys, usually at Tommaso's apartment where he has a proper setup. These sessions are one of Luca's favorite ways to disconnect from screens and engage a completely different part of his brain. - -## Notes - -- Talented musician with deep knowledge of jazz harmony and improvisation; pushes Luca to improve his guitar playing -- Patient and encouraging as a jam partner; adapts to Luca's amateur level without condescension -- Their musical taste overlaps in jazz, blues, and classic rock; they share playlists and concert recommendations regularly -- Luca finds that music sessions with Tommaso leave him more creative and focused when he returns to work -- Has introduced Luca to several live music venues in Milan that have become regular spots - -## Collaborations - -- [[event-dinner-family]] — occasional guest at Luca's social gatherings; music often comes up at dinner parties diff --git a/demo-vault-v2/person-valentina-rizzo.md b/demo-vault-v2/person-valentina-rizzo.md deleted file mode 100644 index 103dcba1..00000000 --- a/demo-vault-v2/person-valentina-rizzo.md +++ /dev/null @@ -1,23 +0,0 @@ ---- -aliases: ["Valentina Rizzo"] -Is A: Person -Tier: "2nd 🥈" -Tags: ["Friend"] ---- -# Valentina Rizzo - -Journalist covering the Italian tech and startup ecosystem for a well-known Italian business publication. Valentina has written about Refactoring several times and is a valuable source of news and perspective on what is happening in the Italian tech scene. She and Luca have built a mutually beneficial relationship: she provides media coverage and ecosystem intelligence, and Luca offers candid perspective from the practitioner side. They meet regularly for coffee or lunch in Milan to exchange notes. - -## Notes - -- Sharp journalist with excellent sources across the Italian startup ecosystem; often has news before it is public -- Fair and thorough in her reporting; Luca trusts her to represent his comments accurately -- Their relationship goes beyond transactional media relations; they genuinely enjoy each other's company and have become real friends -- Has introduced Luca to several interesting people in the Italian tech scene through her extensive network -- Occasionally asks Luca to review technical details in her articles for accuracy, which he is happy to do - -## Collaborations - -- [[topic-italian-startups]] — primary source of information on the Italian tech ecosystem -- [[topic-podcasting]] — has covered the Refactoring podcast in her publication -- [[event-dinner-family]] — occasional guest at Milan gatherings, bridging the tech and media worlds diff --git a/demo-vault-v2/person-yuki-sato.md b/demo-vault-v2/person-yuki-sato.md deleted file mode 100644 index 2acbda71..00000000 --- a/demo-vault-v2/person-yuki-sato.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -aliases: ["Yuki Sato"] -Is A: Person -Tier: "3rd 🥉" -Tags: ["Sponsor"] ---- -# Yuki Sato - -Sponsor contact at Fly.io, managing infrastructure marketing and developer content sponsorships. Yuki oversees Fly.io's investment in podcast and newsletter sponsorships targeting developers who care about deployment infrastructure, edge computing, and application performance. Based in Tokyo, she brings an international perspective to developer marketing and is focused on growing Fly.io's presence in the European and Asian developer communities. - -## Notes - -- Fly.io's product positioning around deploying apps close to users resonates well with the audience of hands-on engineers -- Despite the Tokyo-Milan time zone gap, communication is smooth; she is responsive and organized -- Provides concise, well-written ad copy that focuses on technical differentiation rather than generic marketing language -- Has explored creative sponsorship ideas including sponsored infrastructure case studies and deployment tutorials - -## Collaborations - -- [[24q1-launch-sponsorship-packages]] — Fly.io onboarded as a podcast sponsor -- [[procedure-sponsor-onboarding]] — efficient onboarding despite time zone challenges -- [[event-sponsor-call-flyio]] — periodic check-in calls scheduled to accommodate the time difference diff --git a/demo-vault-v2/person-yusuf-osman.md b/demo-vault-v2/person-yusuf-osman.md deleted file mode 100644 index 20bfe221..00000000 --- a/demo-vault-v2/person-yusuf-osman.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -aliases: ["Yusuf Osman"] -Is A: Person -Tier: "3rd 🥉" -Tags: ["Podcast Guest"] ---- -# Yusuf Osman - -Staff engineer specializing in distributed systems at a large European tech company, with deep expertise in system design for high-throughput, low-latency applications. Yusuf appeared on the podcast to discuss system design at scale, covering architecture patterns for distributed systems, the trade-offs between consistency and availability in real-world applications, and how to build systems that degrade gracefully under load. His practical experience running systems serving millions of users gave the conversation weight and specificity. - -## Notes - -- Technical depth is outstanding; can discuss distributed systems theory and practical implementation with equal fluency -- The episode was one of the most technically dense of the season, but Yusuf's clear explanations kept it accessible -- Shared a mental model for "designing for failure" that Luca has referenced in subsequent newsletter issues -- Quiet confidence in conversation; does not oversell his expertise but delivers genuinely insightful analysis when prompted - -## Collaborations - -- [[25q2-podcast-season-3]] — recorded episode on system design at scale -- [[topic-ai-ml]] — touched on ML system design patterns and their distributed systems implications -- [[procedure-podcast-guest-outreach]] — connected through the distributed systems community on Twitter diff --git a/demo-vault-v2/person.md b/demo-vault-v2/person.md deleted file mode 100644 index d6d0ec03..00000000 --- a/demo-vault-v2/person.md +++ /dev/null @@ -1,7 +0,0 @@ ---- -Is A: Type ---- - -# Person - -A Person is someone you interact with — colleagues, collaborators, mentors, friends. People can own projects, be linked to events, and appear in relationships. diff --git a/demo-vault-v2/podcasting-is-relationship-building.md b/demo-vault-v2/podcasting-is-relationship-building.md deleted file mode 100644 index cd000a9f..00000000 --- a/demo-vault-v2/podcasting-is-relationship-building.md +++ /dev/null @@ -1,31 +0,0 @@ ---- -aliases: ["Podcasting Is Relationship Building at Scale"] -Is A: Evergreen -Topics: ["[[topic-podcasting]]", "[[topic-b2b-marketing]]"] -Status: Published ---- -# Podcasting Is Relationship Building at Scale - -A podcast guest who has a good experience will often become an advocate for your brand in ways that are hard to manufacture any other way. They share the episode with their audience, mention it in talks, and remember you warmly when your paths cross again. - -The distribution value of a podcast episode is real but often secondary to the relationship value. Some of Refactoring's best sponsor introductions came from guests who had been on the show and recommended us to a contact. - -This reframes how to think about guest selection. The right question isn't just 'who has the biggest audience?' but 'who do I want a real relationship with?' - -The mechanism behind this is worth understanding. A podcast conversation is one of the few formats where two professionals spend 45-90 minutes in genuine, focused dialogue. In an era of five-minute video calls and fragmented attention, this is remarkably intimate. The guest has your full attention, you have theirs, and the conversation goes deep enough to build real mutual understanding. After recording, both parties walk away with a qualitatively different relationship than they had before. This is not replicable through social media interactions, email exchanges, or even most in-person networking events where conversations are shallow by necessity. - -I have been deliberate about using the podcast as a relationship-building tool for Refactoring's broader business. When I identify a company that would be an ideal sponsor, I look for someone at that company who would be a genuinely interesting guest — not as a quid-pro-quo, but because the Venn diagram of "interesting engineering leaders" and "people at companies that sponsor engineering newsletters" has substantial overlap. The podcast conversation builds a relationship. The relationship sometimes leads to a sponsorship conversation months later, initiated by them rather than by me. This indirect path produces better, longer-lasting sponsor relationships than cold outreach ever could. - -The broader principle extends beyond podcasting to any content format that creates genuine human connection. Interviews, co-authored pieces, collaborative projects — anything that requires two people to spend meaningful time together creates relationship capital that pure content creation does not. The podcast just happens to be the format that does this most efficiently, because the recording creates a distributable artifact (the episode) and a non-distributable artifact (the relationship) simultaneously. Both are valuable, but the relationship is usually worth more. - -## Key insight - -Podcasting is undervalued as a business development channel because the relationship value is hard to attribute in a spreadsheet. The most important outcomes — warm introductions, sponsor relationships, co-marketing opportunities, hiring referrals — emerge months or years after the recording and cannot be traced to a single episode. This makes podcasting look like a vanity project in most ROI analyses. The founders and creators who understand this asymmetry invest in podcasting not for downloads but for the network effects of genuine professional relationships built one conversation at a time. - -## Related - -- [[what-makes-a-good-podcast-guest]] — The criteria for selecting guests that maximize both content and relationship value -- [[the-sponsorship-relationship]] — How podcast-built relationships translate into better sponsor partnerships -- [[b2b-content-is-trust-not-traffic]] — Podcasting as a trust-building channel, not a traffic-building one -- [[procedure-podcast-recording]] — The practical procedure for recording and producing podcast episodes -- [[topic-podcasting]] — Broader thinking on podcasting as a medium diff --git a/demo-vault-v2/procedure-biweekly-1on1-matteo.md b/demo-vault-v2/procedure-biweekly-1on1-matteo.md deleted file mode 100644 index 1005e352..00000000 --- a/demo-vault-v2/procedure-biweekly-1on1-matteo.md +++ /dev/null @@ -1,30 +0,0 @@ ---- -aliases: ["1:1 with Matteo"] -Is A: Procedure -Belongs to: "[[responsibility-team-management]]" -Cadence: Bi-weekly -Owner: "[[person-luca-rossi]]" ---- -# 1:1 with Matteo - -The bi-weekly 1:1 with [[person-matteo-cellini]] is the primary touchpoint for aligning on the sponsorship pipeline, surfacing blockers early, and investing in Matteo's professional growth. Without a consistent rhythm for these conversations, small misalignments compound into missed deals and frustration on both sides. This procedure ensures each session is focused, actionable, and genuinely useful. - -## Steps - -- [ ] Review Matteo's updates in the shared CRM or task board before the meeting — arrive informed, not cold -- [ ] Open by asking about energy and workload: "How are you feeling about the current pace?" -- [ ] Walk through the active [[responsibility-sponsorships]] pipeline together — focus on deals that moved, stalled, or closed since last session -- [ ] Review [[measure-sponsorship-mrr]] and [[measure-close-rate]] trends to ground the conversation in data -- [ ] Identify the top 1-2 blockers Matteo is facing and brainstorm solutions on the spot -- [ ] Discuss one professional development topic — a skill Matteo wants to build, a resource to explore, or a stretch project -- [ ] Share direct, specific feedback (positive or constructive) on something from the past two weeks -- [ ] Ask Matteo for upward feedback: "What could I do differently to make your work easier?" -- [ ] Agree on 2-3 action items with clear owners and deadlines before ending the call - -## Notes - -- Keep the meeting to 30 minutes. If it consistently runs over, that signals the agenda is too packed or there are unresolved systemic issues worth addressing separately. -- Avoid turning this into a status update. Status should be async; the 1:1 is for the conversations that need nuance, trust, and real-time thinking. -- Rotate between leading with pipeline review and leading with personal check-in to avoid the meeting feeling formulaic. -- Document action items immediately after the call — memory decays fast, and accountability depends on a written record. -- If Matteo raises something sensitive, give it space. Cutting short a trust-building moment to stay on schedule is a false economy. diff --git a/demo-vault-v2/procedure-biweekly-1on1-paco.md b/demo-vault-v2/procedure-biweekly-1on1-paco.md deleted file mode 100644 index 12969ee9..00000000 --- a/demo-vault-v2/procedure-biweekly-1on1-paco.md +++ /dev/null @@ -1,30 +0,0 @@ ---- -aliases: ["1:1 with Paco"] -Is A: Procedure -Belongs to: "[[responsibility-team-management]]" -Cadence: Bi-weekly -Owner: "[[person-luca-rossi]]" ---- -# 1:1 with Paco - -The bi-weekly 1:1 with [[person-paco-furiani]] keeps the operational backbone of the business healthy. Paco handles the systems, tooling, and processes that everyone else depends on, which means his blockers can silently cascade across the entire team. This meeting creates a reliable space to surface those issues, align on priorities, and make sure Paco feels supported and challenged in his role. - -## Steps - -- [ ] Review Paco's recent task completions and in-progress work before the meeting -- [ ] Open with a check-in on workload and energy — operations work can be invisible and draining if not acknowledged -- [ ] Walk through any ongoing process improvement initiatives and their current status -- [ ] Discuss tooling updates, migrations, or infrastructure changes that affect the team -- [ ] Review [[measure-task-completion-rate]] together to identify any patterns in velocity or bottlenecks -- [ ] Identify the top 1-2 blockers and decide on next steps collaboratively -- [ ] Discuss one area of professional growth — automation skills, new tools, or cross-functional exposure -- [ ] Exchange direct feedback in both directions: what is working, what could improve -- [ ] Lock in 2-3 action items with owners and deadlines - -## Notes - -- Paco often solves problems before anyone notices them. Make a habit of explicitly recognizing this — it matters more than you think. -- If process improvement work keeps getting deprioritized in favor of firefighting, that is a signal to address at the [[procedure-quarterly-team-retro]]. -- Keep a running doc of topics between sessions so nothing slips through the cracks during the two-week gap. -- When tooling discussions get technical, resist the urge to prescribe solutions. Ask questions, let Paco own the recommendation. -- Time-box the meeting at 30 minutes. If Paco needs more time on a specific topic, schedule a dedicated follow-up rather than letting the 1:1 balloon. diff --git a/demo-vault-v2/procedure-biweekly-1on1-sara.md b/demo-vault-v2/procedure-biweekly-1on1-sara.md deleted file mode 100644 index e781f697..00000000 --- a/demo-vault-v2/procedure-biweekly-1on1-sara.md +++ /dev/null @@ -1,30 +0,0 @@ ---- -aliases: ["1:1 with Sara"] -Is A: Procedure -Belongs to: "[[responsibility-team-management]]" -Cadence: Bi-weekly -Owner: "[[person-luca-rossi]]" ---- -# 1:1 with Sara - -The bi-weekly 1:1 with [[person-sara-ricci]] is where content quality and editorial direction get the attention they deserve. Sara's work directly shapes how readers experience the newsletter and podcast, so this meeting needs to balance tactical review of current output with strategic conversation about craft, standards, and growth. A good 1:1 rhythm here directly impacts [[measure-essay-quality-score]] and overall content reputation. - -## Steps - -- [ ] Review Sara's recent editing work and any pending drafts before the meeting -- [ ] Open with a workload and energy check — editorial work requires sustained focus, and burnout shows up as declining quality before declining output -- [ ] Discuss the current editorial pipeline: what is in draft, what is in review, what is scheduled -- [ ] Review any content quality concerns — inconsistencies in tone, recurring structural issues, or reader feedback worth addressing -- [ ] Align on the [[responsibility-content-production]] priorities for the next two weeks -- [ ] Discuss one professional development topic — writing craft, editorial process, or content strategy skills Sara wants to deepen -- [ ] Share specific feedback on recent work, citing concrete examples of what landed well or what could be tightened -- [ ] Ask for upward feedback: "Is there anything about how I write or hand off drafts that makes your job harder?" -- [ ] Agree on 2-3 action items with clear owners - -## Notes - -- Sara's editorial judgment is an asset. When you disagree on a suggestion, explain your reasoning rather than just overriding — this builds trust and sharpens both of your instincts. -- Track recurring editorial feedback themes over time. If the same note keeps coming up, it likely points to a systemic writing habit worth addressing at the source. -- Use this meeting to discuss [[measure-articles-per-week]] targets only if they are at risk — do not let throughput metrics crowd out the quality conversation. -- If Sara flags that workload is unsustainable, take it seriously. Content quality degrades before deadlines slip, and by then the damage to reader trust is already done. -- Keep a shared list of "editorial standards" decisions made in these meetings so they become institutional knowledge, not tribal knowledge. diff --git a/demo-vault-v2/procedure-content-calendar-review.md b/demo-vault-v2/procedure-content-calendar-review.md deleted file mode 100644 index e889aee4..00000000 --- a/demo-vault-v2/procedure-content-calendar-review.md +++ /dev/null @@ -1,29 +0,0 @@ ---- -aliases: ["Content Calendar Review"] -Is A: Procedure -Belongs to: "[[responsibility-content-production]]" -Cadence: Weekly -Owner: "[[person-luca-rossi]]" ---- -# Content Calendar Review - -A consistent content operation requires looking ahead, not just reacting to what is due this week. The weekly content calendar review ensures there is always a 4-week runway of planned topics, prevents last-minute scrambles, and keeps the editorial pipeline aligned with [[topic-content-strategy]] goals. Without this discipline, content production becomes reactive, quality drops, and the team feels perpetually behind. - -## Steps - -- [ ] Open the content calendar and review the current week's scheduled pieces — confirm everything is on track for publication -- [ ] Check the next 3 weeks for gaps: are there enough topics slotted in to maintain [[measure-articles-per-week]] targets? -- [ ] Review the backlog of topic ideas and move the strongest candidates into open slots, balancing across content pillars -- [ ] Cross-reference with the [[procedure-monthly-pillar-planning]] output to ensure monthly themes are represented -- [ ] Flag any dependencies — pieces that need guest input, data pulls, or coordination with [[person-sara-ricci]] for heavy editing -- [ ] Identify one "evergreen" piece and one "timely" piece for the coming week to maintain a healthy content mix -- [ ] Update topic statuses: move drafts forward, mark completed pieces, archive abandoned ideas with a brief note on why -- [ ] Share the updated calendar with the team so [[person-sara-ricci]] and [[person-paco-furiani]] can plan their work accordingly - -## Notes - -- The 4-week runway is a minimum. If it drops below 3 weeks, treat it as an urgent problem and block time to brainstorm and slot new topics. -- Do not over-plan beyond 6 weeks — topics planned too far out tend to feel stale by the time they come up, and you waste time replanning. -- Keep a "spark file" of raw topic ideas that are not yet developed enough for the calendar. Review it during this session for anything that has matured. -- Seasonal and event-driven content (product launches, holidays, industry events) should be placed on the calendar at least 4 weeks ahead to allow proper development time. -- This review pairs well with the [[procedure-newsletter-metrics-weekly]] — let performance data inform which content types and topics deserve more calendar space. diff --git a/demo-vault-v2/procedure-editorial-review.md b/demo-vault-v2/procedure-editorial-review.md deleted file mode 100644 index 44acd780..00000000 --- a/demo-vault-v2/procedure-editorial-review.md +++ /dev/null @@ -1,30 +0,0 @@ ---- -aliases: ["Editorial Review"] -Is A: Procedure -Belongs to: "[[responsibility-content-production]]" -Cadence: Weekly -Owner: "[[person-luca-rossi]]" ---- -# Editorial Review - -The weekly editorial review is where drafts become publishable pieces. [[person-sara-ricci]] provides editing suggestions throughout the week, and this procedure ensures those suggestions are reviewed thoughtfully, feedback flows in both directions, and final drafts are approved with confidence. Skipping or rushing this step is the fastest way to erode content quality and undermine the trust readers place in the newsletter. - -## Steps - -- [ ] Collect all drafts that [[person-sara-ricci]] has marked as "ready for review" since the last session -- [ ] Read each draft end-to-end before looking at Sara's inline suggestions — form your own impression of the piece first -- [ ] Review Sara's editing suggestions one by one: accept, modify, or discuss each with a brief rationale -- [ ] Check that the piece aligns with the [[topic-content-strategy]] and the current week's theme from the content calendar -- [ ] Verify structural quality: clear thesis, logical flow, strong opening, actionable takeaways -- [ ] Assess the piece against [[measure-essay-quality-score]] criteria — does it meet the bar for publication? -- [ ] Add any final polish: tighten the intro, sharpen the headline, ensure the CTA is clear -- [ ] Approve the final draft and mark it as ready for scheduling, or send it back with specific revision notes -- [ ] Provide Sara with 1-2 pieces of direct feedback on her editing — what was particularly sharp, what could be pushed further - -## Notes - -- Resist the urge to rewrite Sara's suggestions in your own voice. The goal is editorial consistency, not stylistic uniformity. Her perspective strengthens the work. -- If you find yourself rejecting more than 30% of suggestions consistently, schedule a calibration conversation — the issue is likely a misaligned mental model, not bad editing. -- Time-box the review to 60-90 minutes. If it regularly takes longer, the drafts may need to be tighter before they reach the editing stage. -- Keep a log of the most impactful editorial changes over time. This becomes a style guide by example, referenced in [[on-consistency-in-creative-work]]. -- Never approve a draft you have not read completely. Scanning headings and spot-checking paragraphs is not a review. diff --git a/demo-vault-v2/procedure-evergreen-content-audit.md b/demo-vault-v2/procedure-evergreen-content-audit.md deleted file mode 100644 index b29e3bd4..00000000 --- a/demo-vault-v2/procedure-evergreen-content-audit.md +++ /dev/null @@ -1,31 +0,0 @@ ---- -aliases: ["Evergreen Content Audit"] -Is A: Procedure -Belongs to: "[[responsibility-content-production]]" -Cadence: Quarterly -Owner: "[[person-luca-rossi]]" ---- -# Evergreen Content Audit - -Evergreen content is only valuable if it stays accurate and relevant. This quarterly audit systematically reviews published evergreen articles for outdated information, broken links, missed improvement opportunities, and alignment with current [[topic-content-strategy]] priorities. A well-maintained evergreen library compounds in value over time; a neglected one quietly erodes credibility. - -## Steps - -- [ ] Pull a list of all published evergreen articles, sorted by traffic and last-updated date -- [ ] Identify articles that have not been updated in the past 6 months — these are the highest priority for review -- [ ] For each article under review, check factual accuracy: are statistics, tool recommendations, and examples still current? -- [ ] Test all outbound links and internal wiki-links — fix or remove any that are broken -- [ ] Evaluate whether the article's structure and depth still meet the [[measure-essay-quality-score]] bar you hold today -- [ ] Identify 2-3 articles that could be significantly improved with new insights, updated examples, or expanded sections -- [ ] Flag any articles that are no longer relevant and should be deprecated or merged into other pieces -- [ ] Update the "last reviewed" date on each audited article -- [ ] Create tasks for [[person-sara-ricci]] to help with rewrites or edits on flagged articles -- [ ] Track the number of articles audited and improved as input to [[measure-evergreen-notes-created]] - -## Notes - -- Prioritize high-traffic articles first. A small improvement to a piece that gets 1,000 views per month is worth more than a major rewrite of one that gets 50. -- Do not try to audit the entire library in one sitting. Batch it into 10-15 articles per session across the quarter. -- When an article needs more than minor edits, add it to the content calendar as a scheduled rewrite rather than trying to fix it during the audit. -- Use reader feedback and comments as a signal for what needs updating — if people are asking clarifying questions, the content may have gaps. -- This audit often surfaces ideas for new content. Capture those in the topic backlog during the review rather than derailing the audit to write them. diff --git a/demo-vault-v2/procedure-evergreen-note-writing.md b/demo-vault-v2/procedure-evergreen-note-writing.md deleted file mode 100644 index f02276c6..00000000 --- a/demo-vault-v2/procedure-evergreen-note-writing.md +++ /dev/null @@ -1,28 +0,0 @@ ---- -aliases: ["Evergreen Note Writing"] -Is A: Procedure -Belongs to: "[[responsibility-learning]]" -Cadence: Weekly -Owner: "[[person-luca-rossi]]" ---- -# Evergreen Note Writing - -Evergreen notes are the building blocks of original thinking. Writing 1-2 per week forces you to process what you are reading, hearing, and observing into durable ideas that compound over time. This procedure supports [[responsibility-learning]] by turning passive consumption into active knowledge creation, and feeds directly into the content pipeline when notes mature into publishable essays. See [[on-consistency-in-creative-work]] for why this rhythm matters. - -## Steps - -- [ ] Review highlights and annotations from the past week's reading sessions (see [[procedure-weekly-reading-session]]) -- [ ] Identify 1-2 ideas that feel genuinely interesting, surprising, or in tension with something you previously believed -- [ ] For each idea, write a clear, standalone note: one core claim supported by reasoning, evidence, or examples -- [ ] Connect the note to existing evergreen notes using wiki-links — look for patterns, contradictions, and extensions -- [ ] Add relevant tags and metadata so the note is discoverable in future searches -- [ ] Pressure-test the note: would this idea make sense to someone encountering it without context? If not, add the missing framing -- [ ] Track output against [[measure-evergreen-notes-created]] to maintain accountability - -## Notes - -- Quality over quantity. One well-developed note with clear thinking is worth more than three shallow observations. If you only write one note in a week, that is fine — as long as it is good. -- The best evergreen notes often come from the collision of two unrelated ideas. Pay attention to moments where a podcast conversation echoes something from a book, or where a business observation maps onto a fitness principle. -- Do not wait for ideas to feel "big enough." Many of the best notes start as a single sentence and grow through revisiting. Write the seed now; refine later. -- Revisit notes from 2-4 weeks ago during this session. Fresh distance often reveals whether an idea has legs or was just a passing enthusiasm. -- This practice directly feeds [[responsibility-content-production]] — the best newsletter essays start as evergreen notes that have been refined through connection and reflection. See [[newsletter-subject-lines]] and [[the-real-job-of-a-newsletter]] for how these notes eventually shape published work. diff --git a/demo-vault-v2/procedure-gym-routine.md b/demo-vault-v2/procedure-gym-routine.md deleted file mode 100644 index 519586c2..00000000 --- a/demo-vault-v2/procedure-gym-routine.md +++ /dev/null @@ -1,29 +0,0 @@ ---- -aliases: ["Gym Strength Routine"] -Is A: Procedure -Belongs to: "[[responsibility-health-fitness]]" -Cadence: Weekly -Owner: "[[person-luca-rossi]]" ---- -# Gym Strength Routine - -Strength training twice per week (Monday and Wednesday) provides the structural foundation that supports cycling performance, injury prevention, and general longevity. This routine focuses on compound lifts and core work — movements that build functional strength without excessive fatigue that would interfere with [[procedure-weekly-cycling-block]] sessions. Consistency here directly supports [[measure-resting-hr]] improvements and the broader goals tracked in [[responsibility-health-fitness]]. - -## Steps - -- [ ] Arrive at the gym with a clear plan — review the session's target lifts and weights before starting -- [ ] Warm up for 10 minutes: dynamic stretching, foam rolling on tight areas, and 5 minutes of light rowing or cycling -- [ ] Perform the primary compound lift for the session (Monday: squat or deadlift; Wednesday: bench press or overhead press) — 4 sets of 5-6 reps at working weight -- [ ] Complete 2-3 accessory lifts targeting supporting muscle groups (rows, lunges, pull-ups, Romanian deadlifts) — 3 sets of 8-10 reps each -- [ ] Finish with a 10-minute core circuit: planks, pallof press, dead bugs, and hanging leg raises -- [ ] Log all lifts, sets, reps, and weights in the training tracker immediately after the session -- [ ] Cool down with 5 minutes of static stretching, focusing on hip flexors and thoracic spine -- [ ] Note any pain, unusual fatigue, or form breakdowns — these inform adjustments at the [[procedure-monthly-health-review]] - -## Notes - -- Progressive overload is the goal, but never at the expense of form. Add weight only when the current load feels controlled through the full range of motion. -- If a cycling race or hard training block is coming up, reduce gym volume by 30-40% in the preceding week rather than skipping sessions entirely. Consistency beats intensity. -- Monday sessions should prioritize lower body (squat, deadlift) since Wednesday is further from weekend rides. Wednesday can emphasize upper body and core. -- Keep gym sessions under 60 minutes. If they regularly run longer, the rest periods are too generous or the accessory list has crept up — trim it. -- Track trends monthly as part of [[procedure-monthly-health-review]]. Strength plateaus lasting more than 4 weeks may signal a need for programming changes or recovery attention. diff --git a/demo-vault-v2/procedure-invoice-processing.md b/demo-vault-v2/procedure-invoice-processing.md deleted file mode 100644 index 2e2b15cc..00000000 --- a/demo-vault-v2/procedure-invoice-processing.md +++ /dev/null @@ -1,30 +0,0 @@ ---- -aliases: ["Invoice Processing"] -Is A: Procedure -Belongs to: "[[responsibility-sponsorships]]" -Cadence: Monthly -Owner: "[[person-luca-rossi]]" ---- -# Invoice Processing - -Timely and professional invoicing is essential to maintaining healthy sponsor relationships and predictable cash flow. This monthly procedure ensures every active sponsor receives an accurate invoice, outstanding payments are followed up on, and the financial picture feeding into [[measure-sponsorship-mrr]] stays current. Sloppy invoicing creates friction with sponsors and makes financial planning unreliable — both of which are avoidable with a consistent process. - -## Steps - -- [ ] Pull the list of active sponsorship deals from the CRM, noting each sponsor's billing cycle and agreed rate -- [ ] For each sponsor due an invoice this month, generate the invoice using the standard template — include campaign dates, placement details, and the agreed amount -- [ ] Double-check all invoice details: correct company name, billing address, PO number (if required), and payment terms -- [ ] Send invoices via email with a clear subject line and the invoice attached as PDF -- [ ] Log each sent invoice in the financial tracker with the send date and expected payment date -- [ ] Review the outstanding invoices list — identify any payments that are 15+ days overdue -- [ ] Send a polite follow-up email for overdue invoices, CC'ing [[person-matteo-cellini]] for visibility on the sponsor relationship -- [ ] Update [[measure-sponsorship-mrr]] with confirmed payments received this month -- [ ] Reconcile the month's invoicing against bank deposits to ensure nothing was missed - -## Notes - -- Send invoices within the first 3 business days of the month. Delays on your end invite delays on theirs. -- Maintain a template library so invoice generation takes minutes, not an hour. Standardization reduces errors. -- When following up on overdue payments, keep the tone friendly and professional. Most late payments are due to internal approval processes, not bad intent. -- If a sponsor consistently pays late (3+ months in a row), raise this with [[person-matteo-cellini]] to address it proactively in the relationship — it may warrant adjusted payment terms. -- Keep a separate record of all invoicing activity for [[procedure-quarterly-financial-planning]] — the data is essential for revenue forecasting. diff --git a/demo-vault-v2/procedure-monthly-health-review.md b/demo-vault-v2/procedure-monthly-health-review.md deleted file mode 100644 index 0d737d59..00000000 --- a/demo-vault-v2/procedure-monthly-health-review.md +++ /dev/null @@ -1,30 +0,0 @@ ---- -aliases: ["Monthly Health Review"] -Is A: Procedure -Belongs to: "[[responsibility-health-fitness]]" -Cadence: Monthly -Owner: "[[person-luca-rossi]]" ---- -# Monthly Health Review - -Training without reviewing is just exercise; training with review is a system that improves. This monthly review aggregates health and fitness data — resting heart rate, weight, HRV, sleep quality, and training load — to identify trends, catch warning signs early, and make informed adjustments to the training plan. The insights here feed directly into decisions about [[procedure-weekly-cycling-block]] intensity and [[procedure-gym-routine]] volume. - -## Steps - -- [ ] Export or review the past month's data from the fitness tracker: resting HR, HRV, sleep duration, and sleep quality scores -- [ ] Plot [[measure-resting-hr]] trend over the month — look for sustained increases that may signal overtraining or illness -- [ ] Review body weight trend: is it stable, trending toward the target, or drifting in an unintended direction? -- [ ] Aggregate cycling volume from [[measure-cycling-km-per-month]] and compare against the planned training load -- [ ] Review gym performance logs: are lifts progressing, plateauing, or regressing? -- [ ] Assess subjective energy and motivation levels over the past month — note any patterns tied to training load, sleep, or life stress -- [ ] Based on the data, decide: maintain current training plan, increase volume/intensity, or pull back for recovery -- [ ] Document the review findings and any plan adjustments in this month's health review note -- [ ] Set 1-2 specific health targets for the coming month (e.g., "average 7.5 hours sleep," "hit 3 zone 2 rides per week") - -## Notes - -- Do not overreact to single data points. A bad night of sleep or a high resting HR reading is noise. Look for trends over 7-14 day windows. -- HRV is the most useful leading indicator of recovery status. A sustained downward trend (5+ days) warrants reducing training load before symptoms appear. -- If you skipped gym or cycling sessions this month, note why. Patterns of skipping reveal whether the issue is scheduling, motivation, or recovery. -- This review is also a good time to check whether nutrition is supporting training goals. If performance is stalling despite consistent training, diet is often the missing variable. -- Keep these reviews brief — 20-30 minutes. The goal is pattern recognition and decision-making, not exhaustive analysis. diff --git a/demo-vault-v2/procedure-monthly-pillar-planning.md b/demo-vault-v2/procedure-monthly-pillar-planning.md deleted file mode 100644 index ab8324ff..00000000 --- a/demo-vault-v2/procedure-monthly-pillar-planning.md +++ /dev/null @@ -1,30 +0,0 @@ ---- -aliases: ["Monthly Content Planning"] -Is A: Procedure -Belongs to: "[[responsibility-content-production]]" -Cadence: Monthly -Owner: "[[person-luca-rossi]]" ---- -# Monthly Content Planning - -Monthly pillar planning is where content strategy meets execution. This procedure translates high-level [[topic-content-strategy]] goals into a concrete month of newsletter topics, essays, and pillar articles. Without this step, weekly content production drifts toward whatever feels easiest rather than what serves the audience and business best. The output directly feeds into the [[procedure-content-calendar-review]] and sets the direction for [[person-sara-ricci]]'s editorial work. - -## Steps - -- [ ] Review last month's content performance: which topics, formats, and angles resonated most? Pull data from [[procedure-newsletter-metrics-weekly]] and [[procedure-monthly-subscriber-metrics]] -- [ ] Revisit the quarterly content themes and assess progress — are you on track, or do certain pillars need more attention this month? -- [ ] Brainstorm 8-12 topic candidates for the month, drawing from the idea backlog, reader questions, and recent [[procedure-evergreen-note-writing]] output -- [ ] Select 4-5 primary topics and assign each to a week, balancing across content pillars (technical, personal, strategic) -- [ ] Identify 1 pillar article (long-form, high-effort) to develop over the month alongside regular newsletter issues -- [ ] For each selected topic, write a 2-3 sentence brief: the core argument, the target reader, and the key takeaway -- [ ] Assign any research, data gathering, or guest coordination tasks to [[person-sara-ricci]] or [[person-paco-furiani]] as needed -- [ ] Update the content calendar with the month's plan and share it with the team -- [ ] Block writing time on the calendar for the pillar article — this will not happen unless it is protected - -## Notes - -- Resist the temptation to plan only "safe" topics you know will perform. Reserve at least one slot per month for an experimental piece that pushes into new territory. -- The best months have a mix: one deeply technical piece, one personal/reflective piece, one strategy piece, and one that connects to a trending conversation. -- Reader feedback and replies are an underused input. Scan recent newsletter replies for recurring questions or themes — these are almost guaranteed to resonate as topics. -- The pillar article is the highest-leverage content you produce. Protect it from being deprioritized by weekly urgency. See [[the-real-job-of-a-newsletter]] for why long-form investment matters. -- Align this planning session with [[measure-articles-per-week]] targets so the month's output commitments are realistic given available time and energy. diff --git a/demo-vault-v2/procedure-monthly-portfolio-review.md b/demo-vault-v2/procedure-monthly-portfolio-review.md deleted file mode 100644 index 3e50ea49..00000000 --- a/demo-vault-v2/procedure-monthly-portfolio-review.md +++ /dev/null @@ -1,30 +0,0 @@ ---- -aliases: ["Monthly Portfolio Review"] -Is A: Procedure -Belongs to: "[[responsibility-personal-finance]]" -Cadence: Monthly -Owner: "[[person-luca-rossi]]" ---- -# Monthly Portfolio Review - -The monthly portfolio review keeps [[responsibility-personal-finance]] on track by providing a disciplined checkpoint for investment performance, asset allocation drift, and savings rate. Left unmonitored, portfolios drift out of alignment with long-term targets, and small spending creep erodes savings without being noticed. This procedure ensures decisions are data-driven and emotions stay out of investment management. - -## Steps - -- [ ] Log into all investment and brokerage accounts and record current balances -- [ ] Calculate the portfolio's total value and compare against last month — note the absolute and percentage change -- [ ] Check asset allocation against the target allocation — identify any asset class that has drifted more than 5% from its target weight -- [ ] If drift exceeds 5%, determine the rebalancing trades needed and execute them (or schedule them for the next trading day) -- [ ] Calculate this month's [[measure-savings-rate]]: (income - expenses) / income — compare against the target rate -- [ ] Review [[measure-net-worth]] trend: update the tracking spreadsheet with this month's data point -- [ ] Note any significant market events or personal financial changes that affected the portfolio this month -- [ ] Review recurring expenses for any new subscriptions or cost increases that should be addressed -- [ ] Set any action items for the coming month: contributions to fund, bills to review, or financial goals to adjust - -## Notes - -- Rebalancing is mechanical, not emotional. If the allocation says sell, sell. If it says buy, buy. The whole point of having a target allocation is to remove in-the-moment decision-making. -- Do not check portfolio performance more than once per month outside of this review. Frequent checking leads to anxiety-driven decisions that hurt long-term returns. -- The savings rate is often more impactful than investment returns for wealth building in the early years. Focus energy there before obsessing over fund selection. -- Keep this review under 30 minutes. If it takes longer, the tracking system needs simplification — consider consolidating accounts or automating data pulls. -- This monthly data feeds into the [[procedure-quarterly-financial-planning]] for longer-term strategic decisions. Keep the records clean and consistent. diff --git a/demo-vault-v2/procedure-monthly-sponsor-report.md b/demo-vault-v2/procedure-monthly-sponsor-report.md deleted file mode 100644 index e0e769c2..00000000 --- a/demo-vault-v2/procedure-monthly-sponsor-report.md +++ /dev/null @@ -1,30 +0,0 @@ ---- -aliases: ["Monthly Sponsor Report"] -Is A: Procedure -Belongs to: "[[responsibility-sponsorships]]" -Cadence: Monthly -Owner: "[[person-luca-rossi]]" ---- -# Monthly Sponsor Report - -Monthly sponsor reports are the single most important touchpoint for retention and upsells. Sponsors who receive clear, professional performance data feel confident their investment is working — and confident sponsors renew. This procedure ensures every active sponsor receives a well-structured report that includes the metrics they care about, delivered on time, and positions the relationship for long-term growth. The output directly supports [[measure-sponsorship-mrr]] stability and [[measure-close-rate]] on renewals. - -## Steps - -- [ ] Pull performance data for all active sponsorship placements: impressions, clicks, click-through rate, and unique opens -- [ ] For each sponsor, compile the data into the standard report template — include month-over-month comparisons where possible -- [ ] Add context to the numbers: highlight what performed well, explain any anomalies, and note relevant audience growth from [[measure-subscribers]] -- [ ] Include a brief qualitative section: reader feedback mentioning the sponsor, notable engagement patterns, or content synergies -- [ ] Review the report draft for accuracy — double-check every number against the source data before sending -- [ ] Send each report to the sponsor's primary contact with a personalized note from [[person-matteo-cellini]] or yourself -- [ ] Log the report delivery date and any sponsor responses or questions in the CRM -- [ ] Flag any underperforming placements for internal discussion — proactively address these before the sponsor raises concerns -- [ ] Identify 1-2 upsell or renewal opportunities based on strong performance data and note them for [[person-matteo-cellini]] to follow up - -## Notes - -- Send reports within the first 5 business days of the month. Late reports signal disorganization and erode sponsor trust. -- Honesty builds more trust than spin. If a placement underperformed, acknowledge it and explain what you will adjust — sponsors respect transparency far more than excuses. -- Include [[measure-open-rate]] and audience growth data even when it is not strictly "their" metric. Sponsors like to see that the platform they are investing in is growing. -- Keep the report concise — one page is ideal. Sponsors are busy; they want signal, not a data dump. -- The best sponsor reports end with a forward-looking statement: "Here is what we are planning next month and how it benefits your placement." This primes renewal conversations naturally. diff --git a/demo-vault-v2/procedure-monthly-subscriber-metrics.md b/demo-vault-v2/procedure-monthly-subscriber-metrics.md deleted file mode 100644 index b5de6564..00000000 --- a/demo-vault-v2/procedure-monthly-subscriber-metrics.md +++ /dev/null @@ -1,30 +0,0 @@ ---- -aliases: ["Monthly Subscriber Metrics Review"] -Is A: Procedure -Belongs to: "[[responsibility-grow-newsletter]]" -Cadence: Monthly -Owner: "[[person-luca-rossi]]" ---- -# Monthly Subscriber Metrics Review - -Growing a newsletter sustainably requires understanding not just how many subscribers you are adding, but where they come from, why they stay, and why they leave. This monthly review aggregates the key metrics that drive [[responsibility-grow-newsletter]] decisions: subscriber growth, churn, open rates, and click rates. The data collected here informs content strategy adjustments, growth experiments, and the overall health assessment of the newsletter as a business asset. - -## Steps - -- [ ] Export subscriber data from the email platform: total subscribers, new subscribers, unsubscribes, and net growth for the month -- [ ] Update the [[measure-subscribers]] tracking spreadsheet with this month's data point -- [ ] Calculate and record the churn rate: unsubscribes / total subscribers at the start of the month -- [ ] Review [[measure-open-rate]] trend: compare this month's average against the 3-month rolling average -- [ ] Analyze click rate performance and identify which content types or topics drove the highest engagement -- [ ] Break down new subscriber sources: organic search, referrals, social media, cross-promotions, paid acquisition -- [ ] Identify the top 3 growth drivers and the top 3 churn signals from this month's data -- [ ] Compare actual growth against the monthly target — if off-track, diagnose the gap and propose corrective actions -- [ ] Document findings and share a summary with [[person-sara-ricci]] and [[person-matteo-cellini]] so content and sponsorship decisions are data-informed - -## Notes - -- Churn rate is just as important as growth rate. A "leaky bucket" problem (high growth but high churn) is a content quality or audience-fit signal, not a growth problem. See [[topic-newsletter-growth]] for more on this distinction. -- Open rate trends matter more than absolute open rates, especially given the unreliability of open tracking after Apple Mail Privacy Protection. Focus on the direction, not the number. -- Segment the data by subscriber cohort when possible. Subscribers who joined 6+ months ago behave differently from those who joined last week — conflating them hides important patterns. -- If a particular growth channel delivered a spike of subscribers, check their 30-day retention before doubling down. Some channels bring high volume but low-quality subscribers who churn quickly. -- This review feeds directly into [[procedure-quarterly-sponsor-outreach]] — sponsors want to see healthy, growing audience metrics before committing. diff --git a/demo-vault-v2/procedure-newsletter-ab-testing.md b/demo-vault-v2/procedure-newsletter-ab-testing.md deleted file mode 100644 index 591b89e9..00000000 --- a/demo-vault-v2/procedure-newsletter-ab-testing.md +++ /dev/null @@ -1,30 +0,0 @@ ---- -aliases: ["Newsletter A/B Testing"] -Is A: Procedure -Belongs to: "[[responsibility-content-production]]" -Cadence: Bi-weekly -Owner: "[[person-luca-rossi]]" ---- -# Newsletter A/B Testing - -A/B testing turns newsletter optimization from guesswork into evidence. By systematically testing subject lines, content formats, and structural choices, this procedure builds a growing body of knowledge about what resonates with the audience. Each test is small and low-risk, but the compounding effect of dozens of data points over time significantly improves [[measure-open-rate]] and overall engagement. See [[newsletter-subject-lines]] for accumulated insights from past tests. - -## Steps - -- [ ] Define the hypothesis for this test cycle: what specific question are you trying to answer? (e.g., "Do question-format subject lines outperform statement-format?") -- [ ] Choose the variable to test — only one variable per test to ensure clean results (subject line, preview text, CTA placement, content length, etc.) -- [ ] Create the two variants (A and B) with a single, clear difference between them -- [ ] Configure the A/B test in the email platform: set the audience split (typically 50/50 for subject lines, 20/20/60 for content tests with auto-send) -- [ ] Set the success metric before sending: open rate for subject line tests, click rate for content tests -- [ ] Send the test and wait for the full measurement window (minimum 24 hours for subject lines, 48 hours for content engagement) -- [ ] Record the results: variant, sample size, metric values, statistical significance, and winner -- [ ] Document the learning in the A/B testing log and update [[newsletter-subject-lines]] if the finding is about subject lines -- [ ] Apply the winning insight to the next newsletter issue as the new default - -## Notes - -- Statistical significance matters. A test with 200 opens per variant is too small to draw conclusions from a 2% difference. Aim for at least 500 per variant before declaring a winner. -- Test one thing at a time. Testing a new subject line format AND a new CTA simultaneously makes it impossible to attribute the result. -- Keep a running log of all tests and results. After 20+ tests, patterns emerge that are far more valuable than any single result. This feeds into [[topic-newsletter-growth]] strategy. -- Not every test will have a clear winner, and that is useful information too. "No significant difference" means the variable does not matter much — stop agonizing over it and focus elsewhere. -- Share interesting test results with [[person-sara-ricci]] — they inform her editorial instincts and help align the whole content operation around what actually works. diff --git a/demo-vault-v2/procedure-newsletter-metrics-weekly.md b/demo-vault-v2/procedure-newsletter-metrics-weekly.md deleted file mode 100644 index 1ea3100d..00000000 --- a/demo-vault-v2/procedure-newsletter-metrics-weekly.md +++ /dev/null @@ -1,29 +0,0 @@ ---- -aliases: ["Weekly Newsletter Metrics"] -Is A: Procedure -Belongs to: "[[responsibility-content-production]]" -Cadence: Weekly -Owner: "[[person-luca-rossi]]" ---- -# Weekly Newsletter Metrics - -Reviewing newsletter metrics weekly creates a tight feedback loop between content decisions and audience response. Rather than waiting for the monthly deep dive in [[procedure-monthly-subscriber-metrics]], this lighter weekly check catches performance shifts early and keeps content production decisions grounded in data. It takes 15 minutes and prevents the slow drift of publishing into a void without knowing what is landing. - -## Steps - -- [ ] Pull the latest newsletter edition's performance data from the email platform (wait at least 48 hours after send for stable numbers) -- [ ] Record [[measure-open-rate]] and compare against the 4-week rolling average — flag any significant deviation (more than 5% in either direction) -- [ ] Record click rate and identify which links or sections drove the most clicks -- [ ] Check unsubscribe count for this edition — a spike may indicate a content or frequency mismatch -- [ ] Review any reply emails from readers — note themes, questions, and feedback worth acting on -- [ ] Compare this edition's performance against the same content type from previous months (e.g., technical deep-dive vs. personal essay) -- [ ] Log all data in the weekly metrics tracker for trend analysis -- [ ] Share a brief summary with [[person-sara-ricci]] highlighting what worked and what to learn from - -## Notes - -- Open rate is a directional indicator, not a precise measurement. Apple Mail Privacy Protection inflates it, so focus on trends and relative comparisons between editions rather than absolute numbers. -- Click rate is the most reliable signal of content engagement. If open rate is stable but click rate drops, the content may be less compelling even though the subject line worked. -- Reader replies are qualitative gold. A single thoughtful reply often reveals more about what resonated than any metric dashboard. Do not skip reading them. -- Resist the urge to over-optimize based on a single week. One low-performing edition does not mean the topic is bad — it might mean the subject line missed, or external factors (holidays, competing news) suppressed engagement. -- This weekly data feeds into the [[procedure-content-calendar-review]] — use it to adjust upcoming topic selection based on what the audience is responding to. diff --git a/demo-vault-v2/procedure-podcast-analytics.md b/demo-vault-v2/procedure-podcast-analytics.md deleted file mode 100644 index 0dec6598..00000000 --- a/demo-vault-v2/procedure-podcast-analytics.md +++ /dev/null @@ -1,30 +0,0 @@ ---- -aliases: ["Podcast Analytics Review"] -Is A: Procedure -Belongs to: "[[responsibility-podcast]]" -Cadence: Monthly -Owner: "[[person-luca-rossi]]" ---- -# Podcast Analytics Review - -The monthly podcast analytics review turns download numbers into editorial decisions. By examining which episodes perform, where listeners drop off, and which topics sustain engagement, this procedure ensures the podcast evolves based on evidence rather than assumptions. The data collected here directly informs guest selection, topic planning, and format experiments, all of which drive [[measure-podcast-downloads]] growth over time. - -## Steps - -- [ ] Pull download data for all episodes published in the past month from the podcast hosting platform -- [ ] Record [[measure-podcast-downloads]] for each episode and the monthly aggregate — compare against the prior month and 3-month average -- [ ] Analyze listener retention curves for each episode: where do listeners drop off? Are there patterns tied to episode length, segment type, or topic? -- [ ] Rank episodes by performance and identify what the top-performing episodes have in common (guest profile, topic type, title format) -- [ ] Review listener geography and platform distribution for any notable shifts -- [ ] Check podcast review sites for new ratings and reviews — note themes in listener feedback -- [ ] Compare [[measure-podcast-episodes-per-month]] against the target cadence — were all planned episodes published? -- [ ] Identify 2-3 actionable insights (e.g., "episodes under 45 minutes retain 20% more listeners" or "solo episodes outperform interviews this quarter") -- [ ] Share findings with [[person-paco-furiani]] to inform editing and production decisions - -## Notes - -- Download numbers for new episodes stabilize after about 7 days. Do not draw conclusions from the first 24-48 hours — early downloads reflect audience habits, not content quality. -- Listener retention is the most underused metric in podcasting. A high-download episode with 40% retention at the midpoint is less healthy than a moderate-download episode with 75% retention. -- Compare performance across guest episodes vs. solo episodes. If one format consistently outperforms, adjust the mix accordingly rather than forcing a 50/50 split. -- External factors (being featured in a podcast directory, a guest sharing with their audience) can cause download spikes that are not repeatable. Separate one-time spikes from sustainable growth in your analysis. -- This review feeds into [[procedure-podcast-guest-outreach]] — let the data guide what kind of guests and topics to prioritize in the pipeline. diff --git a/demo-vault-v2/procedure-podcast-editing.md b/demo-vault-v2/procedure-podcast-editing.md deleted file mode 100644 index 52f0f479..00000000 --- a/demo-vault-v2/procedure-podcast-editing.md +++ /dev/null @@ -1,30 +0,0 @@ ---- -aliases: ["Podcast Editing Review"] -Is A: Procedure -Belongs to: "[[responsibility-podcast]]" -Cadence: Bi-weekly -Owner: "[[person-luca-rossi]]" ---- -# Podcast Editing Review - -The editing review is the quality gate between recording and publishing. [[person-paco-furiani]] handles the initial edit — cutting filler, balancing audio levels, adding intro/outro — and this procedure ensures the final product meets the show's quality standard before it goes live. A consistent editing review prevents the gradual erosion of production quality that listeners notice before you do. - -## Steps - -- [ ] Download or stream Paco's edited version of the latest episode -- [ ] Listen to the full episode with fresh ears — do not skim or skip sections -- [ ] Check audio quality: are levels balanced between host and guest? Is background noise minimal? Are transitions smooth? -- [ ] Evaluate content edits: were the right sections cut? Did any important context get lost in the editing? -- [ ] Note any awkward jumps, abrupt cuts, or pacing issues that need smoothing -- [ ] Verify that intro, outro, and sponsor reads are correctly placed and sound natural -- [ ] Provide [[person-paco-furiani]] with specific, timestamped feedback: what to fix, what to keep, and what was done particularly well -- [ ] Approve the episode for publishing or request a revision with a clear deadline -- [ ] Once approved, confirm the episode is queued for the scheduled publish date - -## Notes - -- Listen on the same device and environment your audience uses most — headphones on a commute or earbuds at a desk. What sounds fine on studio monitors may have issues through consumer audio. -- Be specific in feedback. "The transition at 23:15 is abrupt" is actionable; "the middle section feels off" is not. Paco does better work when the notes are precise. -- If you find yourself requesting the same type of revision repeatedly, address it as a process improvement in the next [[procedure-biweekly-1on1-paco]] rather than continuing to catch it in review. -- Resist the temptation to over-edit. Some imperfection is what makes podcasts feel human and conversational. Only cut what genuinely detracts from the listener experience. -- Keep a running quality checklist that evolves over time. As production standards improve, the checklist should tighten — this prevents regression and documents what "good" sounds like for the show. diff --git a/demo-vault-v2/procedure-podcast-guest-outreach.md b/demo-vault-v2/procedure-podcast-guest-outreach.md deleted file mode 100644 index a7b384a1..00000000 --- a/demo-vault-v2/procedure-podcast-guest-outreach.md +++ /dev/null @@ -1,30 +0,0 @@ ---- -aliases: ["Podcast Guest Outreach"] -Is A: Procedure -Belongs to: "[[responsibility-podcast]]" -Cadence: Monthly -Owner: "[[person-luca-rossi]]" ---- -# Podcast Guest Outreach - -A podcast is only as good as its guest pipeline. This monthly outreach procedure ensures there is always a 3-month booking horizon of confirmed guests, preventing the scramble of last-minute scheduling that leads to weaker episodes. Systematic outreach also allows for intentional curation — building a guest roster that serves the audience rather than just filling slots. See [[what-makes-a-good-podcast-guest]] for the selection criteria that guide this process. - -## Steps - -- [ ] Review the current guest pipeline: how many confirmed bookings exist for the next 3 months? Identify gaps. -- [ ] Brainstorm 8-10 potential guests based on current content themes, audience interests, and topics that performed well in [[procedure-podcast-analytics]] -- [ ] Vet each candidate against the criteria in [[what-makes-a-good-podcast-guest]]: expertise, storytelling ability, audience relevance, and willingness to promote -- [ ] Select the top 5 candidates and research each one: read their recent work, listen to their other podcast appearances, identify unique angles -- [ ] Draft personalized outreach emails for each candidate — reference specific work of theirs and explain why the conversation would be valuable for both audiences -- [ ] Send outreach emails and log each contact in the guest tracking spreadsheet with date sent and status -- [ ] Follow up on any outstanding outreach from the previous month that has not received a response (one follow-up, then move on) -- [ ] For confirmed guests, send a scheduling link and the pre-recording brief within 48 hours of confirmation -- [ ] Update the 3-month booking calendar and share it with [[person-paco-furiani]] for production planning - -## Notes - -- Quality over quantity. Five well-researched, personalized outreach emails outperform twenty generic ones. Guests can tell when you have done your homework, and it sets the tone for the entire relationship. -- Maintain a "dream guest" list of 10-15 people you would love to have on the show. Even if they are out of reach today, revisit the list as the show grows — audience size and reputation compound. -- The best guest leads often come from existing guests. At the end of every recording, ask: "Who else should I talk to about this topic?" This warm introduction path has a much higher conversion rate than cold outreach. -- Balance the guest roster across expertise areas and demographics. A podcast that only features one type of guest gets predictable fast. -- Track outreach response rate over time. If it drops below 30%, revisit the outreach template, the show's positioning, or whether the target guests are too far above the show's current reach. diff --git a/demo-vault-v2/procedure-podcast-recording.md b/demo-vault-v2/procedure-podcast-recording.md deleted file mode 100644 index 1649670b..00000000 --- a/demo-vault-v2/procedure-podcast-recording.md +++ /dev/null @@ -1,31 +0,0 @@ ---- -aliases: ["Podcast Recording"] -Is A: Procedure -Belongs to: "[[responsibility-podcast]]" -Cadence: Bi-weekly -Owner: "[[person-luca-rossi]]" ---- -# Podcast Recording - -The bi-weekly recording session is where the podcast actually gets made. Everything else — outreach, editing, analytics — exists to support this moment. A well-prepared recording session produces a better conversation, reduces editing time for [[person-paco-furiani]], and results in episodes that listeners remember and share. This procedure covers the full arc from pre-call preparation through the recording itself to the handoff for editing. - -## Steps - -- [ ] Review the guest's background 24 hours before recording: re-read their recent work, review the pre-recording brief they completed, and note 2-3 unique angles -- [ ] Prepare 8-10 discussion questions, ordered from warm-up to deep-dive — but hold them loosely, the best conversations wander productively -- [ ] Test all equipment 30 minutes before the call: microphone, headphones, recording software, backup recording, internet connection -- [ ] Join the call 5 minutes early for a brief pre-recording chat with the guest: build rapport, align on the episode's direction, and address any concerns -- [ ] Hit record and begin with a natural opening — introduce the guest conversationally, not with a scripted bio reading -- [ ] During the conversation, listen actively and follow interesting threads even if they deviate from the prepared questions -- [ ] Keep an eye on time: aim for 60-90 minutes of raw recording, knowing 10-15 minutes will be cut in editing -- [ ] Close with the standard outro questions and thank the guest genuinely -- [ ] Immediately after the call, send the raw recording files to [[person-paco-furiani]] with timestamped notes on any sections to highlight or cut -- [ ] Send the guest a thank-you message within 24 hours, including the estimated publish date and a request to share the episode when it goes live - -## Notes - -- The prep call is not optional. Even 5 minutes of casual conversation before hitting record dramatically improves the energy and flow of the actual interview. -- Record a local backup in addition to the cloud recording. Audio disasters happen, and there is no recovery from a lost recording with a busy guest. -- Resist the urge to fill every silence. Pauses give the guest space to think and often lead to the most insightful moments of the conversation. See [[what-makes-a-good-podcast-guest]] for more on facilitating great dialogue. -- If the conversation is not working (guest is distracted, topic is not landing), do not force it. Acknowledge it, pivot to a different angle, or wrap up gracefully. A short good episode is better than a long mediocre one. -- Track which episodes required the least editing — those conversations reveal what "in the zone" sounds like for this show, and that pattern should inform future guest and topic selection. diff --git a/demo-vault-v2/procedure-podcast-show-notes.md b/demo-vault-v2/procedure-podcast-show-notes.md deleted file mode 100644 index ac645717..00000000 --- a/demo-vault-v2/procedure-podcast-show-notes.md +++ /dev/null @@ -1,30 +0,0 @@ ---- -aliases: ["Podcast Show Notes"] -Is A: Procedure -Belongs to: "[[responsibility-podcast]]" -Cadence: Bi-weekly -Owner: "[[person-luca-rossi]]" ---- -# Podcast Show Notes - -Show notes are the podcast's written footprint — they drive discoverability through search, provide value to listeners who want to reference key points, and serve as promotional content for the newsletter and social media. Well-crafted show notes turn a single recording into multiple content touchpoints, extending the episode's reach well beyond the initial listen. This procedure ensures every episode gets the written support it deserves. - -## Steps - -- [ ] Listen to the final edited episode (or review detailed timestamps from the recording session) and note the key topics, insights, and quotable moments -- [ ] Write a compelling episode summary (3-5 sentences) that communicates the core value proposition — why should someone press play? -- [ ] Create a structured outline of the episode's major segments with timestamps so listeners can navigate directly to topics that interest them -- [ ] Pull 2-3 key quotes from the guest that capture the most impactful or surprising moments of the conversation -- [ ] Compile a list of all resources mentioned in the episode: books, tools, articles, people, and links -- [ ] Write a brief guest bio (2-3 sentences) with links to their website and social profiles -- [ ] Format the show notes for the podcast website and submit for publishing -- [ ] Adapt the show notes into a newsletter teaser for the next edition — highlight 1-2 insights to drive listens from [[measure-subscribers]] -- [ ] Share the show notes and promotional assets with [[person-sara-ricci]] for cross-promotion in the newsletter - -## Notes - -- The episode summary is the most important element of show notes. Most potential listeners decide whether to press play based on the summary alone — write it like a headline, not an abstract. -- Timestamps are a small effort with outsized value. They improve the listener experience and boost SEO by adding keyword-rich text to the show notes page. -- Do not just transcribe the episode. Show notes should complement the audio, not duplicate it. Provide structure, links, and highlights that add value beyond what someone gets by listening. -- Cross-promote episodes in the newsletter by connecting episode themes to recent written content. This creates a flywheel between [[responsibility-podcast]] and [[responsibility-content-production]]. -- Publish show notes on the same day the episode goes live, or ideally a few hours before. Delayed show notes mean missed traffic from the initial launch push. diff --git a/demo-vault-v2/procedure-quarterly-financial-planning.md b/demo-vault-v2/procedure-quarterly-financial-planning.md deleted file mode 100644 index c1aae8ce..00000000 --- a/demo-vault-v2/procedure-quarterly-financial-planning.md +++ /dev/null @@ -1,31 +0,0 @@ ---- -aliases: ["Quarterly Financial Planning"] -Is A: Procedure -Belongs to: "[[responsibility-personal-finance]]" -Cadence: Quarterly -Owner: "[[person-luca-rossi]]" ---- -# Quarterly Financial Planning - -The quarterly financial planning session zooms out from the monthly portfolio checks to examine the full financial picture: income trends, expense patterns, savings rate trajectory, and progress toward long-term net worth targets. Running an indie business means revenue can be lumpy and expenses unpredictable — this quarterly discipline ensures financial decisions are intentional rather than reactive, and that the business remains financially sustainable on a longer time horizon. - -## Steps - -- [ ] Aggregate the past quarter's income by source: sponsorships, consulting, digital products, and any other revenue streams -- [ ] Compare quarterly income against the prior quarter and the same quarter last year to identify trends and seasonality -- [ ] Review total expenses for the quarter, categorized by business operations, tools/subscriptions, team compensation, and personal -- [ ] Calculate the quarterly [[measure-savings-rate]] and compare against the annual target — if behind, identify the top 3 expense categories to address -- [ ] Update the [[measure-net-worth]] tracker with the quarter-end snapshot and plot the trend line -- [ ] Assess whether the current net worth trajectory is on track to meet the annual target — if not, model what needs to change (higher income, lower expenses, or both) -- [ ] Review [[measure-sponsorship-mrr]] trend over the quarter and project next quarter's expected revenue based on the pipeline -- [ ] Identify any large planned expenses or investments for the coming quarter and factor them into the cash flow plan -- [ ] Set 2-3 specific financial goals for the next quarter with measurable targets -- [ ] Document the quarterly financial summary and any strategic decisions made - -## Notes - -- This is the session where you make big-picture financial decisions: whether to invest in a new tool, hire help, or adjust pricing. Monthly reviews are too reactive for these choices; quarterly gives the right perspective. -- Revenue concentration risk is real. If more than 40% of income comes from a single source (e.g., one large sponsor), flag it and actively diversify in the coming quarter. -- Compare [[measure-savings-rate]] across quarters to see if lifestyle creep is eroding savings. A slowly declining savings rate is easy to miss month-to-month but becomes obvious quarterly. -- Keep the planning session under 90 minutes. If it takes longer, the financial tracking system needs simplification — automate data collection so the session focuses on analysis and decisions. -- The output of this session should inform [[procedure-quarterly-sponsor-outreach]] targets — revenue goals and sponsorship pipeline need to be aligned. diff --git a/demo-vault-v2/procedure-quarterly-sponsor-outreach.md b/demo-vault-v2/procedure-quarterly-sponsor-outreach.md index af74f545..7d612e8d 100644 --- a/demo-vault-v2/procedure-quarterly-sponsor-outreach.md +++ b/demo-vault-v2/procedure-quarterly-sponsor-outreach.md @@ -1,31 +1,16 @@ --- -aliases: ["Quarterly Sponsor Outreach"] -Is A: Procedure -Belongs to: "[[responsibility-sponsorships]]" -Cadence: Quarterly -Owner: "[[person-luca-rossi]]" +type: Procedure +aliases: + - "[[Quarterly Sponsor Outreach]]" +belongs_to: "[[responsibility-sponsorships]]" +owner: "[[person-matteo-cellini]]" +cadence: Quarterly --- + # Quarterly Sponsor Outreach -Sponsorship revenue does not grow passively — it requires systematic pipeline development. This quarterly outreach procedure ensures the business maintains a healthy flow of potential sponsors by identifying, researching, and contacting at least 20 qualified prospects each quarter. Managed through Airtable for pipeline tracking, this process keeps [[measure-sponsorship-mrr]] growing and reduces the risk of revenue gaps when existing sponsors churn. [[person-matteo-cellini]] plays a key role in executing and following up on outreach. +Review the pipeline, choose the next target companies, and send a fresh outreach batch each quarter. -## Steps +- Start from last quarter's warm leads. +- Share the shortlist with [[person-matteo-cellini]] before sending outreach. -- [ ] Review the current sponsor pipeline in Airtable: how many prospects are in each stage (identified, contacted, in conversation, proposal sent, closed)? -- [ ] Analyze which sponsor categories and company sizes have converted best historically — use this to focus outreach efforts -- [ ] Research and build a target list of 25-30 potential sponsors using industry directories, competitor analysis, and newsletter audience demographics -- [ ] Qualify each prospect: does their product/service align with the audience? Do they have an active content marketing or sponsorship budget? -- [ ] Narrow the list to the top 20+ prospects and assign each to a tier (high-priority, standard) based on fit and estimated deal size -- [ ] Draft personalized outreach emails for high-priority prospects — reference specific audience overlap, recent content, and what makes this placement unique -- [ ] Brief [[person-matteo-cellini]] on the outreach plan and delegate standard-tier outreach for him to personalize and send -- [ ] Send all outreach emails and log them in Airtable with dates, status, and follow-up reminders -- [ ] Review the quarter's [[measure-close-rate]] and adjust the outreach volume target if the conversion rate has changed -- [ ] Set the revenue target for next quarter based on pipeline health and share it with the team - -## Notes - -- Personalization is non-negotiable for high-priority prospects. Generic outreach gets ignored. Reference the prospect's product, a recent campaign of theirs, or a specific data point about audience fit. -- The 20+ outreach target assumes a 15-20% response rate and a 25-30% close rate on responses. If your actual rates differ, adjust the volume accordingly — the math must work backwards from the revenue goal. -- Do not neglect warm leads. Past sponsors who did not renew, prospects who said "not now" 6 months ago, and inbound inquiries that went cold are often easier to convert than cold outreach. -- Use [[procedure-monthly-subscriber-metrics]] data in outreach materials — sponsors want to see audience growth, engagement rates, and demographic alignment. -- Coordinate outreach timing with the content calendar. If a major pillar article or high-profile podcast guest is coming up, use it as a hook in outreach emails to demonstrate content quality and momentum. diff --git a/demo-vault-v2/procedure-quarterly-team-retro.md b/demo-vault-v2/procedure-quarterly-team-retro.md deleted file mode 100644 index ba1d7d32..00000000 --- a/demo-vault-v2/procedure-quarterly-team-retro.md +++ /dev/null @@ -1,31 +0,0 @@ ---- -aliases: ["Quarterly Team Retrospective"] -Is A: Procedure -Belongs to: "[[responsibility-team-management]]" -Cadence: Quarterly -Owner: "[[person-luca-rossi]]" ---- -# Quarterly Team Retrospective - -The quarterly retrospective is the team's dedicated space to reflect honestly on what is working, what is not, and what should change. In a small team, it is easy to skip formal reflection because "we talk all the time" — but informal conversations rarely surface systemic issues or lead to concrete process improvements. This procedure ensures that [[person-matteo-cellini]], [[person-paco-furiani]], and [[person-sara-ricci]] all have an equal voice in shaping how the team operates, and that insights translate into action. - -## Steps - -- [ ] Schedule a 90-minute session at least one week in advance — send each team member a pre-work prompt: "List 2-3 things that went well, 2-3 things that did not, and 1 change you would make" -- [ ] Open the session by reviewing action items from last quarter's retro — which were completed, which were dropped, and why? -- [ ] Collect and discuss "what went well" contributions from each team member — celebrate wins and identify patterns worth reinforcing -- [ ] Collect and discuss "what did not go well" contributions — focus on systemic issues, not individual blame -- [ ] Facilitate a discussion on root causes for the most impactful problems raised -- [ ] Brainstorm potential process changes or experiments to address the top 2-3 issues -- [ ] Vote on which changes to implement this quarter — limit to 2-3 actionable commitments to avoid overloading -- [ ] Assign an owner to each action item with a clear deadline and definition of done -- [ ] Review [[measure-team-nps]] results if available and discuss any trends -- [ ] Close by asking each person for one word that describes how they feel about the coming quarter - -## Notes - -- Psychological safety is the prerequisite for a useful retro. If people do not feel safe raising problems, the session becomes a performance of agreement. Model vulnerability by going first with your own "what did not go well." -- Limit action items to 2-3 per quarter. Teams that commit to 8 improvements execute none. Focus on the changes with the highest leverage. -- The pre-work prompt is essential. Without it, the session gets dominated by whoever thinks fastest on their feet, and quieter team members (often with the best observations) stay silent. -- Rotate the facilitation role if possible. When the team lead always facilitates, the dynamic skews toward top-down rather than collaborative. -- Keep a running retro log across quarters. Patterns that appear in multiple retros deserve deeper investigation — they signal structural issues, not one-off problems. diff --git a/demo-vault-v2/procedure-race-preparation.md b/demo-vault-v2/procedure-race-preparation.md deleted file mode 100644 index 2c88d8fc..00000000 --- a/demo-vault-v2/procedure-race-preparation.md +++ /dev/null @@ -1,30 +0,0 @@ ---- -aliases: ["Race Preparation"] -Is A: Procedure -Belongs to: "[[responsibility-health-fitness]]" -Cadence: "As needed" -Owner: "[[person-luca-rossi]]" ---- -# Race Preparation - -The week before a gran fondo or cycling event is not the time for heroic training — it is the time for disciplined tapering. This procedure covers the 7-day preparation window: reducing training volume while maintaining enough intensity to stay sharp, dialing in nutrition and hydration, optimizing sleep, and handling the logistics that make race day smooth. Proper preparation turns months of [[procedure-weekly-cycling-block]] training into actual race-day performance rather than leaving fitness on the table through fatigue, poor nutrition, or logistical stress. - -## Steps - -- [ ] Seven days out: reduce cycling volume by 40-50% from the normal training week while keeping 1-2 short intensity efforts (intervals or tempo) to maintain leg speed -- [ ] Review the race route profile: note key climbs, descents, feed zones, and any technical sections that require attention -- [ ] Plan race-day nutrition: calculate calorie and hydration needs based on expected duration and conditions, and prepare or purchase the required gels, bars, and electrolytes -- [ ] Practice the race nutrition plan during one of the taper rides to confirm stomach tolerance and timing -- [ ] Three days out: shift to very easy spinning only — 30-45 minutes at recovery pace, no hard efforts -- [ ] Prepare all equipment: check bike mechanically (tires, brakes, shifting, chain), lay out race kit, charge devices, and pack spares (tubes, CO2, multi-tool) -- [ ] Prioritize sleep: aim for 8+ hours per night in the final 3 days, especially two nights before the race (the night before is often restless regardless) -- [ ] Night before: prepare transition bags, pin race number, set alarms, and review the logistics plan (travel time, parking, registration) -- [ ] Race morning: eat the planned pre-race meal 3 hours before start, arrive at the venue with at least 60 minutes to spare, warm up for 15-20 minutes - -## Notes - -- The taper feels wrong. You will feel sluggish, restless, and convinced you are losing fitness. This is normal — trust the process. The body needs time to absorb the training load, and race day will prove the taper worked. -- Do not try anything new on race day: no new nutrition, no new kit, no last-minute bike adjustments. Race day is for executing the plan, not experimenting. -- Sleep two nights before the race matters more than the night before. Pre-race nerves often disrupt sleep the final night, and that is fine as long as the previous nights were solid. -- Review [[measure-cycling-km-per-month]] and recent training logs to calibrate pacing expectations. Your race pace should reflect your actual training, not your aspirational fitness level. -- After the race, schedule a recovery week (50% volume, easy intensity) before returning to normal training. Racing depletes the body more than training does, and skipping recovery invites injury or illness. diff --git a/demo-vault-v2/procedure-referral-program.md b/demo-vault-v2/procedure-referral-program.md deleted file mode 100644 index 705a54a4..00000000 --- a/demo-vault-v2/procedure-referral-program.md +++ /dev/null @@ -1,29 +0,0 @@ ---- -aliases: ["Referral Program Management"] -Is A: Procedure -Belongs to: "[[responsibility-grow-newsletter]]" -Cadence: Weekly -Owner: "[[person-luca-rossi]]" ---- -# Referral Program Management - -The referral program turns engaged readers into a growth engine. When subscribers actively recommend the newsletter to others, those referrals convert at a higher rate and retain longer than subscribers from almost any other channel. This weekly procedure ensures the program runs smoothly — rewards are delivered, performance is monitored, and the referral copy is continuously improved to maximize [[measure-subscribers]] growth through word of mouth. - -## Steps - -- [ ] Check the referral dashboard for the past week: how many referrals were made, by how many unique referrers? -- [ ] Identify top referrers who have crossed a reward threshold and trigger the reward fulfillment (digital reward, shoutout, premium content access, or physical merchandise) -- [ ] Send a personalized thank-you message to the top 3 referrers this week — genuine appreciation drives continued advocacy -- [ ] Review the referral conversion rate: of people who clicked a referral link, how many actually subscribed? If this rate is dropping, investigate landing page or copy issues -- [ ] Check if any A/B test on referral copy is running — review results if the test window has closed and implement the winning variant -- [ ] If no test is running, set up a new A/B test on one element: the referral prompt copy, the reward description, or the referral landing page headline -- [ ] Monitor for abuse: look for suspicious referral patterns (bulk self-referrals, bot signups) and clean them from the data -- [ ] Log weekly referral metrics in the growth tracker for trend analysis alongside [[measure-subscribers]] data - -## Notes - -- The referral prompt placement matters as much as the copy. Test positioning it at different points in the newsletter — after the most valuable section often outperforms the footer placement. -- Reward tiers work better than a single reward. Multiple levels (3 referrals, 10 referrals, 25 referrals) create ongoing motivation rather than a one-and-done dynamic. -- The best referral copy explains the *why*, not just the *what*. "Share this with a friend who is building something" resonates more than "Refer 3 friends for a free sticker." See [[topic-newsletter-growth]] for more on this. -- Track the lifetime value of referred subscribers vs. other acquisition channels. If referral subscribers have significantly higher retention, that justifies investing more in the program. -- Do not let the referral program run on autopilot for more than a month without reviewing performance. Stale rewards and copy lose effectiveness over time. diff --git a/demo-vault-v2/procedure-seo-content-optimization.md b/demo-vault-v2/procedure-seo-content-optimization.md deleted file mode 100644 index d574b02d..00000000 --- a/demo-vault-v2/procedure-seo-content-optimization.md +++ /dev/null @@ -1,30 +0,0 @@ ---- -aliases: ["SEO Content Optimization"] -Is A: Procedure -Belongs to: "[[responsibility-grow-newsletter]]" -Cadence: Monthly -Owner: "[[person-luca-rossi]]" ---- -# SEO Content Optimization - -Search traffic is the most sustainable growth channel for a content business because it compounds — an article optimized today continues to bring readers for months or years. This monthly procedure systematically improves existing articles with updated keywords, better internal linking, and structural improvements that help search engines and readers alike find and engage with the content. The effort here directly supports [[measure-subscribers]] growth by expanding the top of the funnel. - -## Steps - -- [ ] Pull the search performance report from Google Search Console: identify the top 20 articles by impressions and click-through rate -- [ ] Identify "almost there" articles — pieces ranking on page 2 (positions 11-20) that could reach page 1 with targeted improvements -- [ ] For each priority article, research current keyword opportunities: are there related terms or questions people search for that the article does not address? -- [ ] Update article titles and meta descriptions to better match high-volume search queries while maintaining natural readability -- [ ] Improve internal linking: add 3-5 relevant internal links from the target article to other content, and add links from high-authority pages back to the target article -- [ ] Review and improve the article's structure: add or refine headers (H2/H3), break up long paragraphs, and ensure the content answers the searcher's intent clearly -- [ ] Update any outdated information, statistics, or examples that could hurt credibility or engagement -- [ ] Submit updated URLs for re-indexing in Google Search Console -- [ ] Track the changes made and the article's ranking position for comparison in next month's review - -## Notes - -- Focus on improving existing content before creating new SEO-targeted pieces. Updating a page-2 article to page 1 is almost always higher ROI than writing a new article from scratch. -- Do not stuff keywords. Write for readers first, search engines second. Google's algorithms are sophisticated enough that naturally written, comprehensive content ranks better than keyword-optimized thin content. -- Internal linking is the most underutilized SEO lever for independent publishers. Each internal link passes authority and helps search engines understand content relationships — treat it as seriously as external link building. -- Changes take 2-6 weeks to reflect in search rankings. Do not judge the impact of this month's work until the following month's review. Patience is essential. -- Coordinate with [[person-sara-ricci]] when updates require significant content revisions — SEO optimization should improve quality, not degrade it. The [[procedure-editorial-review]] process applies to updated content too. diff --git a/demo-vault-v2/procedure-social-media-scheduling.md b/demo-vault-v2/procedure-social-media-scheduling.md deleted file mode 100644 index 4053935c..00000000 --- a/demo-vault-v2/procedure-social-media-scheduling.md +++ /dev/null @@ -1,29 +0,0 @@ ---- -aliases: ["Social Media Scheduling"] -Is A: Procedure -Belongs to: "[[responsibility-content-production]]" -Cadence: Weekly -Owner: "[[person-luca-rossi]]" ---- -# Social Media Scheduling - -Social media extends the reach of newsletter content to audiences who have not yet subscribed, and reinforces key ideas with those who have. This weekly procedure repurposes the latest newsletter content into LinkedIn and Twitter posts, scheduled in advance so that social media presence stays consistent without requiring daily attention. The goal is not to create new content for social — it is to extract maximum value from content that already exists. This directly supports [[responsibility-grow-newsletter]] by driving traffic and building awareness. - -## Steps - -- [ ] Review the latest newsletter edition and identify 3-5 key insights, quotes, or frameworks that stand alone as social media posts -- [ ] Adapt each insight into the native format for each platform: LinkedIn (longer, narrative, professional) and Twitter (concise, punchy, thread-friendly) -- [ ] Write 2-3 LinkedIn posts for the week: one insight post, one personal reflection or behind-the-scenes post, and one engagement prompt or question -- [ ] Write 4-5 tweets for the week: a mix of standalone insights, newsletter highlights with a subscribe CTA, and replies or engagements with relevant conversations -- [ ] Add relevant visuals or formatting (line breaks, bullet points, emojis where appropriate for the platform) to maximize readability -- [ ] Schedule all posts using the scheduling tool, spacing them throughout the week for consistent visibility -- [ ] Include a link to the newsletter or podcast in at least 2 posts per platform per week to drive traffic back to owned channels -- [ ] Review last week's post performance: identify which topics and formats drove the most engagement and factor that into this week's scheduling - -## Notes - -- Social media is a distribution channel, not a content creation burden. If it starts to feel like a separate content operation, you are doing too much. Repurpose ruthlessly. -- LinkedIn posts that tell a short story or share a specific lesson consistently outperform generic advice posts. Lead with a concrete experience, not an abstract principle. -- Do not post and forget. Spend 10-15 minutes after each post goes live responding to comments and engaging with others' content. The algorithm rewards conversation, not broadcasting. -- Track which social posts drive the most newsletter signups, not just likes or impressions. Vanity metrics are noise; subscriber conversion is the signal that matters for [[measure-subscribers]]. -- Batch the scheduling into a single 30-45 minute session. Context-switching between social media and deep work throughout the week is the most expensive way to handle this. diff --git a/demo-vault-v2/procedure-sponsor-onboarding.md b/demo-vault-v2/procedure-sponsor-onboarding.md index 11ae1765..2fa9f783 100644 --- a/demo-vault-v2/procedure-sponsor-onboarding.md +++ b/demo-vault-v2/procedure-sponsor-onboarding.md @@ -1,30 +1,17 @@ --- -aliases: ["Sponsor Onboarding"] -Is A: Procedure -Belongs to: "[[responsibility-sponsorships]]" -Cadence: "As needed" -Owner: "[[person-luca-rossi]]" +type: Procedure +aliases: + - "[[Sponsor Onboarding]]" +belongs_to: "[[responsibility-sponsorships]]" +owner: "[[person-luca-rossi]]" +cadence: "As needed" --- + # Sponsor Onboarding -First impressions set the tone for the entire sponsor relationship. A smooth onboarding process — from signed deal to first placement — signals professionalism, reduces friction, and increases the likelihood of long-term partnerships and renewals. This procedure ensures that every new sponsor receives a consistent experience: a clear brief, creative review, scheduled placement, and timely invoicing. [[person-matteo-cellini]] coordinates much of this process, but the quality bar is set here. +Turn a signed sponsor into a smooth first placement with minimal back-and-forth. -## Steps +- Confirm the publication date. +- Review copy and assets. +- Hand off recurring communication to [[person-matteo-cellini]]. -- [ ] Once the deal is signed, send the sponsor a welcome email with a clear timeline for their first placement and what they need to provide -- [ ] Share the sponsor brief template: ad copy guidelines, character limits, image specs, link requirements, and the newsletter's tone and audience profile -- [ ] Schedule a 15-minute kick-off call (or async exchange) to align on messaging goals, key selling points, and any audience segments the sponsor wants to emphasize -- [ ] Receive the sponsor's creative assets and review them against the brief: does the copy fit the newsletter's tone? Are the claims accurate and non-hyperbolic? -- [ ] If creative revisions are needed, provide specific, constructive feedback with examples of what works well in the newsletter's format -- [ ] Once creative is approved, schedule the placement in the content calendar and confirm the publication date with the sponsor -- [ ] Generate and send the first invoice per the agreed payment terms (see [[procedure-invoice-processing]]) -- [ ] Add the sponsor to the CRM with all relevant details: contact info, contract terms, placement schedule, and notes from the kick-off conversation -- [ ] Brief [[person-matteo-cellini]] on the relationship so he can manage ongoing communications and the [[procedure-monthly-sponsor-report]] - -## Notes - -- The onboarding experience is a preview of the entire relationship. If it is chaotic or slow, the sponsor will expect the same going forward. Make it crisp. -- Creative review is a service, not an obstacle. The best sponsor placements feel native to the newsletter, and that requires editorial guidance. Frame feedback as "this will perform better for you" rather than "this does not meet our standards." -- Send the sponsor a sample of a previous sponsor placement so they can see what the final product looks like. This dramatically reduces revision cycles. -- Track the time from signed deal to first published placement. If it consistently exceeds 2 weeks, there is a bottleneck in the process worth diagnosing. -- A well-onboarded sponsor is more likely to renew. Every hour invested in onboarding saves time in the [[procedure-sponsor-renewal]] process later. diff --git a/demo-vault-v2/procedure-sponsor-renewal.md b/demo-vault-v2/procedure-sponsor-renewal.md deleted file mode 100644 index 96c48c08..00000000 --- a/demo-vault-v2/procedure-sponsor-renewal.md +++ /dev/null @@ -1,31 +0,0 @@ ---- -aliases: ["Sponsor Renewal Process"] -Is A: Procedure -Belongs to: "[[responsibility-sponsorships]]" -Cadence: Quarterly -Owner: "[[person-luca-rossi]]" ---- -# Sponsor Renewal Process - -Renewing existing sponsors is significantly more efficient than acquiring new ones — the relationship trust is already established, the creative workflow is proven, and the cost of sale is a fraction of cold outreach. This quarterly procedure ensures that no contract expiration goes unnoticed, renewal conversations begin early enough to avoid gaps, and existing sponsors feel valued and informed when making their decision. This is a key lever for [[measure-sponsorship-mrr]] stability. - -## Steps - -- [ ] Pull a list of all sponsor contracts expiring in the next 90 days from the CRM -- [ ] For each expiring contract, review the sponsor's performance data: clicks, CTR, audience feedback, and any qualitative wins from [[procedure-monthly-sponsor-report]] -- [ ] Prepare a renewal brief for each sponsor: summarize their results, highlight audience growth since they started, and outline placement options for the next term -- [ ] Initiate renewal conversations 45-60 days before contract expiration — this gives enough time for negotiation without creating urgency pressure -- [ ] Schedule a call or send a detailed renewal proposal to each sponsor, tailored to their goals and past performance -- [ ] For high-performing sponsors, propose expanded placements or upgraded packages — use data to justify the upsell -- [ ] For underperforming sponsors, proactively address the results: explain what happened, what you would change, and why the next term will be different -- [ ] Negotiate terms and close renewals, updating the CRM with new contract details -- [ ] Brief [[person-matteo-cellini]] on all renewed contracts and any changes to placement schedules or creative requirements -- [ ] Track the renewal rate and feed it into [[measure-close-rate]] for trend analysis - -## Notes - -- The renewal conversation should never be the first time a sponsor hears about their performance. If [[procedure-monthly-sponsor-report]] is running well, the renewal is a natural next step, not a surprise ask. -- Start renewal conversations earlier for large-deal sponsors. Enterprise-level sponsors often need internal budget approval cycles, and starting late means missing their planning window. -- If a sponsor declines to renew, ask for candid feedback on why. This data is invaluable for improving the product and informs [[procedure-quarterly-sponsor-outreach]] targeting. -- Offering a small incentive for multi-quarter commitments (e.g., 10% discount for 4-quarter deal) improves revenue predictability and reduces the overhead of quarterly renewal cycles. -- Keep a "winback" list of sponsors who did not renew. Revisit them in 6 months with updated audience metrics and a fresh pitch — circumstances change, and a well-timed follow-up can reopen the relationship. diff --git a/demo-vault-v2/procedure-weekly-cycling-block.md b/demo-vault-v2/procedure-weekly-cycling-block.md deleted file mode 100644 index bf5183da..00000000 --- a/demo-vault-v2/procedure-weekly-cycling-block.md +++ /dev/null @@ -1,30 +0,0 @@ ---- -aliases: ["Weekly Cycling Training Block"] -Is A: Procedure -Belongs to: "[[responsibility-health-fitness]]" -Cadence: Weekly -Owner: "[[person-luca-rossi]]" ---- -# Weekly Cycling Training Block - -Structured cycling training three times per week builds the aerobic base and intensity needed for gran fondo events and long-term fitness. The weekly block follows a polarized training approach: one high-intensity session (intervals), one moderate endurance ride, and one long ride on the weekend. This structure ensures progressive overload without overtraining, and the data feeds into [[measure-cycling-km-per-month]] and the broader [[responsibility-health-fitness]] tracking. - -## Steps - -- [ ] Monday evening: review the week's planned rides — confirm the route, duration, and intensity targets for each session based on the current training phase -- [ ] Tuesday (Intervals): warm up for 15 minutes, then complete the prescribed interval set (e.g., 5x5 minutes at threshold, or 8x3 minutes at VO2max) with recovery between efforts, followed by a 10-minute cooldown -- [ ] After the Tuesday session, log the workout: duration, distance, average power/HR, interval compliance, and perceived effort -- [ ] Thursday (Endurance): ride 60-90 minutes at a steady zone 2 pace — keep heart rate in the aerobic zone and resist the urge to push harder -- [ ] After the Thursday session, log the workout and note how the endurance effort felt relative to previous weeks — improving comfort at the same effort level is a sign of fitness gains -- [ ] Saturday (Long Ride): complete the week's longest ride, 2-4 hours depending on the training phase, mixing terrain and including some race-pace efforts in the final third -- [ ] After the Saturday ride, log the full session including nutrition intake, hydration, and any mechanical or physical issues -- [ ] Sunday: review the week's three sessions together — assess total volume against [[measure-cycling-km-per-month]] targets and training plan progression -- [ ] Adjust next week's plan if needed based on how the body responded: fatigue signals, soreness, or signs of underrecovery - -## Notes - -- The Tuesday interval session is the most important ride of the week for fitness development. If you have to skip a session, skip Thursday — never skip Tuesday. -- Zone 2 endurance work on Thursday should genuinely feel easy. If you cannot hold a conversation, you are going too hard. Easy riding builds the aerobic engine that supports everything else. -- The Saturday long ride is where race-specific fitness is built. Simulate race conditions: practice nutrition, pace the climbs, and ride at intensity in the final hour when fatigue is real. -- Track [[measure-cycling-km-per-month]] but do not chase volume for its own sake. Consistent quality sessions beat junk miles every time. -- Pair this block with the [[procedure-gym-routine]] (Monday and Wednesday) and ensure adequate recovery between sessions. If gym soreness is affecting Tuesday intervals, adjust gym timing or volume. The [[procedure-monthly-health-review]] is where these interactions get assessed systematically. diff --git a/demo-vault-v2/procedure-weekly-newsletter.md b/demo-vault-v2/procedure-weekly-newsletter.md deleted file mode 100644 index df914c8b..00000000 --- a/demo-vault-v2/procedure-weekly-newsletter.md +++ /dev/null @@ -1,31 +0,0 @@ ---- -aliases: ["Weekly Newsletter"] -Is A: Procedure -Belongs to: "[[responsibility-content-production]]" -Cadence: Weekly -Owner: "[[person-luca-rossi]]" ---- -# Weekly Newsletter - -The weekly Refactoring newsletter is the core content product — the piece that drives subscriber growth, sponsor revenue, and audience trust. This procedure covers the full production cycle: from drafting the essay and curating links through editing and sponsor block integration to final publication. Every step matters because the newsletter is a direct conversation with the audience, and consistency in quality and cadence is what builds a lasting content business. See [[the-real-job-of-a-newsletter]] for the philosophy behind this work. - -## Steps - -- [ ] Monday-Tuesday: Draft the main essay based on the topic from the [[procedure-content-calendar-review]] — aim for a complete rough draft by end of day Tuesday -- [ ] Wednesday morning: Self-edit the draft — tighten the opening, strengthen the argument, cut anything that does not serve the core idea -- [ ] Wednesday afternoon: Send the draft to [[person-sara-ricci]] for editorial review (see [[procedure-editorial-review]]) -- [ ] Thursday: Review Sara's editing suggestions, incorporate feedback, and finalize the essay -- [ ] Thursday: Curate 3-5 links for the "links" section — select articles, tools, or resources that are genuinely valuable to the audience, not filler -- [ ] Thursday-Friday: Integrate the sponsor block — review the sponsor's creative, ensure it fits naturally within the newsletter's flow, and confirm with [[person-matteo-cellini]] if any questions arise -- [ ] Friday morning: Final proof of the complete newsletter — read it end-to-end as a subscriber would, checking formatting, links, images, and sponsor placement -- [ ] Friday: Write the subject line last (see [[newsletter-subject-lines]] for best practices) — test 2-3 options and select the strongest -- [ ] Friday afternoon: Schedule the newsletter for the planned send time and confirm delivery in the email platform -- [ ] After send: Monitor initial performance metrics and capture any immediate reader replies for the [[procedure-newsletter-metrics-weekly]] review - -## Notes - -- The essay is the product. Everything else — links, sponsor block, formatting — supports the essay. If the essay is not strong, no amount of polish elsewhere will save the edition. Protect writing time fiercely. -- Write the subject line after the essay is finished, not before. The best subject lines emerge from the content itself, and writing them first constrains the essay. See [[newsletter-subject-lines]] for the accumulated A/B testing insights. -- The curated links section is a trust signal. Only include resources you have actually read or used. Readers notice when the links feel like an afterthought, and it erodes the newsletter's credibility. -- Sponsor integration should feel seamless. If the sponsor copy jars against the newsletter's tone, work with [[person-matteo-cellini]] to adjust it — a poorly integrated sponsor hurts both the reader experience and the sponsor's results. -- Maintain a "not this week" file for ideas and sections you cut during editing. They often become seeds for future essays or evergreen notes. See [[on-consistency-in-creative-work]] for why protecting the creative process matters. diff --git a/demo-vault-v2/procedure-weekly-reading-session.md b/demo-vault-v2/procedure-weekly-reading-session.md deleted file mode 100644 index 478cc8da..00000000 --- a/demo-vault-v2/procedure-weekly-reading-session.md +++ /dev/null @@ -1,29 +0,0 @@ ---- -aliases: ["Weekly Reading Session"] -Is A: Procedure -Belongs to: "[[responsibility-learning]]" -Cadence: Weekly -Owner: "[[person-luca-rossi]]" ---- -# Weekly Reading Session - -Sunday morning reading is the anchor habit for [[responsibility-learning]]. Two to three hours of focused, uninterrupted reading creates the raw material that feeds evergreen notes, newsletter essays, and original thinking. Without dedicated reading time, the content pipeline slowly starves — you end up recycling old ideas instead of generating new ones. This is not leisure reading; it is a professional investment in the quality of everything you write and think. The output directly supports [[measure-books-per-month]] and fuels the [[procedure-evergreen-note-writing]] practice. - -## Steps - -- [ ] Saturday evening: select the book or long-form material for tomorrow's session — have a backup ready in case you finish or lose interest -- [ ] Sunday morning: set up the reading environment — no phone (or phone in another room), coffee prepared, comfortable seating, notebook or highlighter within reach -- [ ] Read for 2-3 hours with full attention — no multitasking, no "quick checks" of email or messages -- [ ] While reading, highlight or mark passages that provoke a reaction: surprise, disagreement, connection to another idea, or a new framing of something familiar -- [ ] After the reading session, spend 15-20 minutes reviewing highlights and writing brief margin notes or annotations that capture your reaction (not just the author's words) -- [ ] Identify 1-2 ideas from the session that are candidates for [[procedure-evergreen-note-writing]] this week -- [ ] Update the reading log: book title, pages/chapters completed, and the session's date — this feeds into [[measure-books-per-month]] tracking -- [ ] If you finished a book, write a brief (3-5 sentence) personal take: what was the core insight, what did you disagree with, and who should read it - -## Notes - -- Protect this time ruthlessly. The moment reading sessions become "optional" or "if I have time," they stop happening. Block it on the calendar like any other non-negotiable commitment. -- Read broadly, not just in your domain. The most valuable newsletter insights come from connecting ideas across fields — a cycling training concept applied to business, or a financial principle applied to content strategy. -- Alternate between challenging books and enjoyable ones. A steady diet of only difficult material leads to avoidance, while only reading easy material limits growth. The rhythm matters. -- Physical books and e-ink readers work better than tablets for focused reading. Backlit screens invite distraction and fatigue faster. -- Do not pressure yourself to finish every book. If a book is not delivering value after 50-75 pages, abandon it without guilt and move to the next one. Life is too short for bad books, and the sunk cost fallacy applies to reading too. diff --git a/demo-vault-v2/procedure-weekly-team-sync.md b/demo-vault-v2/procedure-weekly-team-sync.md deleted file mode 100644 index 00036ac9..00000000 --- a/demo-vault-v2/procedure-weekly-team-sync.md +++ /dev/null @@ -1,30 +0,0 @@ ---- -aliases: ["Weekly Team Sync"] -Is A: Procedure -Belongs to: "[[responsibility-team-management]]" -Cadence: Weekly -Owner: "[[person-luca-rossi]]" ---- -# Weekly Team Sync - -The Monday morning team sync is the operating rhythm of the business. In 30 minutes, [[person-matteo-cellini]], [[person-paco-furiani]], and [[person-sara-ricci]] align on the week's priorities, surface blockers before they become problems, and coordinate across workstreams. Without this weekly touchpoint, a small remote team drifts into silos where everyone is busy but not necessarily aligned. The sync is not for deep discussion — it is for coordination and clarity. - -## Steps - -- [ ] Before the meeting: review the team task board and note any items that are blocked, overdue, or newly urgent -- [ ] Open the sync by briefly recapping last week's key outcomes — what shipped, what slipped, and any wins worth celebrating -- [ ] Go around the team: each person shares their top 2-3 priorities for the week and any blockers they need help with -- [ ] Identify cross-team dependencies: does Sara need a draft from Luca? Does Paco need creative assets from Matteo? Surface these and set deadlines -- [ ] Address the top 1-2 blockers as a group — if resolution requires more than 5 minutes of discussion, schedule a separate follow-up -- [ ] Review [[measure-task-completion-rate]] trends briefly — are we maintaining velocity, or is the team taking on more than it can deliver? -- [ ] Confirm the week's key deadlines: newsletter publish date, podcast episode, sponsor deliverables, and any external commitments -- [ ] Close with any announcements or updates that affect the whole team -- [ ] Post a written summary of priorities and action items in the shared channel within 30 minutes of the meeting - -## Notes - -- Keep the sync to 30 minutes maximum. If it regularly runs over, the agenda is too broad or blockers are not being resolved between meetings. Tighten the format. -- This meeting is for coordination, not brainstorming. If a topic needs creative discussion (e.g., a new content strategy), schedule a separate session rather than derailing the sync. -- The written summary is non-negotiable. Without it, half the team will remember different priorities, and alignment degrades within 24 hours. -- If someone is blocked on something from the previous week, escalate it immediately — a blocker that persists for two weeks is a process failure, not a people failure. -- Rotate the note-taking responsibility weekly. This distributes the administrative load and ensures everyone is engaged in capturing decisions, not just listening passively. diff --git a/demo-vault-v2/procedure-welcome-email-sequence.md b/demo-vault-v2/procedure-welcome-email-sequence.md deleted file mode 100644 index 497a768f..00000000 --- a/demo-vault-v2/procedure-welcome-email-sequence.md +++ /dev/null @@ -1,30 +0,0 @@ ---- -aliases: ["Welcome Email Sequence Review"] -Is A: Procedure -Belongs to: "[[responsibility-grow-newsletter]]" -Cadence: Monthly -Owner: "[[person-luca-rossi]]" ---- -# Welcome Email Sequence Review - -The welcome email sequence is the first sustained interaction a new subscriber has with the newsletter, and it disproportionately determines whether they become a long-term reader or quietly disengage. This monthly review ensures the onboarding sequence stays effective, current, and aligned with what the newsletter has become — because the content evolves faster than the automation, and stale welcome emails silently erode first impressions and [[measure-open-rate]] for new cohorts. - -## Steps - -- [ ] Review the current welcome email sequence end-to-end: read each email as if you were a brand new subscriber encountering it for the first time -- [ ] Check that the content in each email is still accurate: are the "best of" article links still relevant? Are the descriptions of what the newsletter covers still true? -- [ ] Review performance metrics for each email in the sequence: open rate, click rate, and unsubscribe rate at each step -- [ ] Identify the drop-off points: where in the sequence do new subscribers stop opening? This is the weakest email and the highest priority for improvement -- [ ] Update or rewrite any emails that are underperforming or contain outdated content -- [ ] Test subject lines for the weakest-performing email — set up an A/B test for the coming month -- [ ] Verify that the sequence timing is appropriate: are emails spaced well (typically 1-3 days apart), or is the sequence too compressed or too spread out? -- [ ] Ensure the sequence transitions smoothly into regular newsletter delivery — the last welcome email should set expectations for what comes next -- [ ] Check that the sequence includes a clear value proposition early (email 1-2) and a soft referral or engagement ask later (email 4-5) - -## Notes - -- The first welcome email is the highest-opened email you will ever send. Treat it like the most important piece of content you write, because for many readers, it is the one that decides whether they stay. See [[the-real-job-of-a-newsletter]] for why this matters. -- Do not over-automate. A 12-email welcome sequence is almost certainly too long. 4-6 emails over 2 weeks is the sweet spot for most newsletters — enough to build the relationship without overwhelming the inbox. -- Personalization matters but does not need to be complex. Even using the subscriber's first name and referencing how they found the newsletter (if tracked) significantly improves engagement. -- Review unsubscribe reasons for new subscribers specifically. If people are leaving during the welcome sequence, the problem is expectation mismatch — what they signed up for is not what they are receiving. -- This review should be coordinated with [[person-sara-ricci]] since the welcome emails set the editorial tone. Any changes to the sequence should be consistent with the newsletter's evolving voice and the insights from [[procedure-newsletter-ab-testing]]. diff --git a/demo-vault-v2/procedure.md b/demo-vault-v2/procedure.md deleted file mode 100644 index a361ac69..00000000 --- a/demo-vault-v2/procedure.md +++ /dev/null @@ -1,7 +0,0 @@ ---- -Is A: Type ---- - -# Procedure - -A Procedure is a recurring process tied to an Area or Responsibility. Procedures have a cadence and describe how to do something step by step. diff --git a/demo-vault-v2/project.md b/demo-vault-v2/project.md deleted file mode 100644 index 732ce119..00000000 --- a/demo-vault-v2/project.md +++ /dev/null @@ -1,7 +0,0 @@ ---- -Is A: Type ---- - -# Project - -A Project is a time-bounded effort with a clear goal, defined outcome, and eventual completion. Projects belong to Areas and advance Goals. diff --git a/demo-vault-v2/quarter.md b/demo-vault-v2/quarter.md deleted file mode 100644 index 1ed72b92..00000000 --- a/demo-vault-v2/quarter.md +++ /dev/null @@ -1,7 +0,0 @@ ---- -Is A: Type ---- - -# Quarter - -A Quarter note captures the focus, OKRs, and reflections for a three-month period. It is the primary planning horizon for goals and projects. diff --git a/demo-vault-v2/reading-more-by-reading-better.md b/demo-vault-v2/reading-more-by-reading-better.md deleted file mode 100644 index 41500b97..00000000 --- a/demo-vault-v2/reading-more-by-reading-better.md +++ /dev/null @@ -1,33 +0,0 @@ ---- -aliases: ["Read More by Reading Better"] -Is A: Evergreen -Topics: ["[[topic-reading-books]]"] -Status: Published ---- -# Read More by Reading Better -The bottleneck in most people's reading isn't speed — it's selection and retention. They read too many books they don't finish and retain too little of what they do. - -Three things have improved my reading dramatically: - -1. **Permission to stop.** If a book hasn't earned its next chapter by page 50, I stop. Life is too short for dutiful reading. - -2. **Writing after reading.** I write a brief note — what was the core claim? Do I believe it? What does it connect to? This takes 20 minutes and dramatically improves retention. - -3. **Re-reading deliberately.** I re-read a handful of books every year that have proven worth re-reading. Each time I find something new. - -The writing-after-reading habit is the one that has made the biggest difference, and it connects directly to how I think about knowledge management. Before I adopted this practice, I would finish a book, feel like I understood it, and then six months later struggle to recall anything beyond a vague impression. Now, the act of writing a note forces me to distill the book's central argument into my own words, identify which parts I agree with and which I dispute, and connect it to ideas I already hold. This process regularly reveals that I understood less than I thought — and that is exactly the point. The note becomes the proof of understanding, not the feeling of understanding. - -Selection deserves as much attention as the reading itself. Most reading advice focuses on speed or volume, but the highest-leverage intervention is choosing better books. I maintain a running list that is heavily filtered by recommendations from people I trust — not bestseller lists, not algorithm recommendations, but specific books recommended by specific people whose judgment I respect in specific domains. When [[person-matteo-cellini]] recommends a book about systems thinking, I take it seriously because I know his track record of recommendations in that space. This social filtering dramatically improves the hit rate compared to browsing a bookstore or scrolling through Goodreads. - -Re-reading is the most counterintuitive of the three practices because it feels wasteful — why read a book you have already read when there are thousands you have not? The answer is that you are not the same reader the second time. A book like Essentialism or Deep Work means something different after you have spent a year trying to implement its ideas. The second reading is not a review — it is a dialogue between the book and your experience. I typically re-read 3-4 books per year and get more from those re-readings than from most new books. The insight density of a great book on its second pass is remarkably high because you know which parts are relevant to your life. - -## Key insight -Reading productivity is determined by the product of three factors: selection quality, comprehension depth, and retention rate. Most people try to improve reading by increasing speed, which affects none of these factors. The highest-impact interventions are ruthless selection (stop reading bad books immediately), active processing (write notes after reading), and strategic re-reading (revisit the best books as your experience grows). Together, these practices mean reading fewer books but extracting dramatically more value from each one. - -## Related -- [[knowledge-management-is-not-filing]] — Writing after reading is knowledge integration, not filing -- [[the-compound-effect-in-knowledge-work]] — Reading compounds when each book connects to previous reading -- [[note-deep-work]] — One of the books worth re-reading annually -- [[note-essentialism]] — Another re-reading candidate that improves with experience -- [[note-atomic-habits]] — The habit architecture for building a consistent reading practice -- [[topic-reading-books]] — Broader thinking on reading as a practice diff --git a/demo-vault-v2/recovery-week-in-training.md b/demo-vault-v2/recovery-week-in-training.md deleted file mode 100644 index bea4a92c..00000000 --- a/demo-vault-v2/recovery-week-in-training.md +++ /dev/null @@ -1,28 +0,0 @@ ---- -aliases: ["The Importance of Recovery Weeks"] -Is A: Evergreen -Topics: ["[[topic-cycling-training]]", "[[topic-sleep-recovery]]"] -Status: Published ---- -# The Importance of Recovery Weeks -Every serious cycling training plan includes a recovery week every 3-4 weeks: significantly reduced volume, same intensity. This isn't optional. - -Without recovery weeks, training stress accumulates until the athlete either gets sick, injured, or simply stops improving. The body adapts during recovery, not during training. Training is just the stimulus. - -I've made the mistake of skipping recovery weeks when training was going well — 'why back off if I feel strong?' Invariably, the 5th or 6th week of consecutive load is when something breaks. Respect the cycle. - -The physiological explanation is straightforward: training creates microscopic damage to muscle fibers, depletes glycogen stores, and accumulates systemic fatigue. Adaptation — the process of rebuilding stronger — requires time and reduced load. Without it, the damage compounds faster than the repair. This is why overtraining syndrome exists: it is not a failure of willpower but a failure of recovery. The athletes who train the most are not always the ones who improve the most. The ones who improve the most are the ones who train hard and recover hard with equal discipline. - -What makes this relevant beyond cycling is how precisely it maps to knowledge work. I have experimented with implementing recovery weeks in my work schedule: every fourth week, I reduce my output by 40-50%. I write shorter newsletters, decline discretionary meetings, and spend more time reading, walking, and thinking without producing. The first few times I tried this, it felt irresponsible — like I was falling behind. But the pattern that emerged was unmistakable. The week after a recovery week consistently produces my best work. Ideas that were stuck come unstuck. Writing that felt forced flows naturally. The creative well refills. - -The cultural resistance to recovery — in both athletics and knowledge work — comes from a linear model of progress: more input equals more output. This model is correct for machines and incorrect for biological systems. Biological systems are adaptive, and adaptation requires cycles of stress and recovery. The founder who works 60-hour weeks for 18 months straight is not being more productive than the one who works 45-hour weeks with regular recovery periods. They are burning through their adaptive capacity and accumulating a recovery debt that will eventually come due, usually in the form of burnout, illness, or simply declining quality of output. - -## Key insight -Recovery is not the absence of training — it is the phase where training produces results. This is true for athletic performance and for cognitive performance. The most productive knowledge workers structure their time in cycles: focused output followed by deliberate recovery. Skipping recovery does not create more output; it creates diminishing returns from the same effort and eventually produces negative returns when the system breaks down. The discipline to rest when you feel strong is harder and more valuable than the discipline to work when you feel tired. - -## Related -- [[training-load-and-knowledge-work]] — The theoretical framework connecting athletic training load to cognitive work -- [[cycling-teaches-patience]] — Patience and pacing as the strategic foundation that makes recovery weeks possible -- [[sleeping-more-is-a-superpower]] — Sleep as the most fundamental unit of recovery -- [[on-founder-energy-management]] — Recovery weeks as a structural element of founder energy management -- [[the-two-types-of-hard]] — Knowing when difficulty signals a need for recovery versus a need for persistence diff --git a/demo-vault-v2/refactoring-ideas.md b/demo-vault-v2/refactoring-ideas.md deleted file mode 100644 index 10e8492b..00000000 --- a/demo-vault-v2/refactoring-ideas.md +++ /dev/null @@ -1,6 +0,0 @@ ---- -Is A: Note ---- -# Refactoring Ideas - -Collection of ideas for refactoring the codebase to improve maintainability and performance. diff --git a/demo-vault-v2/refactoring-key-ideas.md b/demo-vault-v2/refactoring-key-ideas.md deleted file mode 100644 index 48925948..00000000 --- a/demo-vault-v2/refactoring-key-ideas.md +++ /dev/null @@ -1,6 +0,0 @@ ---- -Is A: Note ---- -# Refactoring Key Ideas - -Key takeaways from Martin Fowler's Refactoring book and other refactoring resources. diff --git a/demo-vault-v2/refactoring-patterns.md b/demo-vault-v2/refactoring-patterns.md deleted file mode 100644 index 5841c9ab..00000000 --- a/demo-vault-v2/refactoring-patterns.md +++ /dev/null @@ -1,6 +0,0 @@ ---- -Is A: Note ---- -# Refactoring Patterns - -Common refactoring patterns including Extract Method, Rename Variable, and Replace Conditional with Polymorphism. diff --git a/demo-vault-v2/refactoring.md b/demo-vault-v2/refactoring.md deleted file mode 100644 index e6a8f65f..00000000 --- a/demo-vault-v2/refactoring.md +++ /dev/null @@ -1,7 +0,0 @@ ---- -Is A: Area -Status: Active ---- -# Refactoring - -Area note covering refactoring practices, principles, and techniques for improving code quality without changing external behavior. diff --git a/demo-vault-v2/renamed-title-xyz.md b/demo-vault-v2/renamed-title-xyz.md deleted file mode 100644 index a69dde29..00000000 --- a/demo-vault-v2/renamed-title-xyz.md +++ /dev/null @@ -1,4 +0,0 @@ ---- -type: Note -status: Active ---- diff --git a/demo-vault-v2/responsibility-content-production.md b/demo-vault-v2/responsibility-content-production.md deleted file mode 100644 index 19a3c99b..00000000 --- a/demo-vault-v2/responsibility-content-production.md +++ /dev/null @@ -1,42 +0,0 @@ ---- -aliases: ["Content Production"] -Is A: Responsibility -Belongs to: "[[area-building]]" -Has Measures: ["[[measure-articles-per-week]]", "[[measure-essay-quality-score]]"] -Has Procedures: ["[[procedure-weekly-newsletter]]", "[[procedure-monthly-pillar-planning]]", "[[procedure-social-media-scheduling]]", "[[procedure-newsletter-ab-testing]]", "[[procedure-content-calendar-review]]", "[[procedure-editorial-review]]", "[[procedure-evergreen-content-audit]]", "[[procedure-newsletter-metrics-weekly]]"] -Status: Open ---- -# Content Production - -Content production is the engine behind Refactoring. Every week, the newsletter and supporting essays need to ship on time, at a quality bar that keeps readers coming back. This responsibility covers the full lifecycle of written content — from ideation and outlining through drafting, editing, and publishing — and it is the single most important operational commitment in the business. - -## Scope - -- Writing and publishing the weekly Refactoring newsletter edition -- Producing standalone essays and deep-dive articles on engineering leadership topics -- Maintaining and executing the monthly content calendar and pillar plan -- Running A/B tests on subject lines, formats, and send times to optimize engagement -- Coordinating with [[person-sara-ricci]] on editorial review and copy quality -- Auditing and refreshing evergreen content to keep the archive valuable over time - -## Current state - -The production cadence is stable: one newsletter edition plus at least one standalone essay ships every week. Reader feedback consistently lands above 4.5 out of 5 on quality, and the editorial pipeline with Sara has reduced last-minute scrambles significantly. The main challenge right now is balancing depth with consistency — some weeks the essay ideas demand more research time than the schedule allows, which can push social distribution to the back burner. - -Pillar planning has helped front-load topic selection, but there is room to improve the feedback loop between [[measure-essay-quality-score]] data and future topic choices. The evergreen content audit is running quarterly but could benefit from being more systematic. - -## Key procedures - -- [[procedure-weekly-newsletter]] -- [[procedure-monthly-pillar-planning]] -- [[procedure-content-calendar-review]] -- [[procedure-editorial-review]] -- [[procedure-newsletter-ab-testing]] -- [[procedure-social-media-scheduling]] -- [[procedure-evergreen-content-audit]] -- [[procedure-newsletter-metrics-weekly]] - -## Key measures - -- [[measure-articles-per-week]] -- [[measure-essay-quality-score]] diff --git a/demo-vault-v2/responsibility-grow-newsletter.md b/demo-vault-v2/responsibility-grow-newsletter.md deleted file mode 100644 index 374cfbab..00000000 --- a/demo-vault-v2/responsibility-grow-newsletter.md +++ /dev/null @@ -1,37 +0,0 @@ ---- -aliases: ["Grow Newsletter"] -Is A: Responsibility -Belongs to: "[[area-building]]" -Has Measures: ["[[measure-subscribers]]", "[[measure-open-rate]]"] -Has Procedures: ["[[procedure-monthly-subscriber-metrics]]", "[[procedure-referral-program]]", "[[procedure-welcome-email-sequence]]", "[[procedure-seo-content-optimization]]"] -Status: Open ---- -# Grow Newsletter - -Growing the Refactoring subscriber base is the highest-leverage activity in the business. Subscriber count directly drives sponsorship revenue, audience trust, and long-term brand equity. This responsibility covers every channel and tactic used to attract new subscribers and retain existing ones — organic search, referral loops, welcome sequences, and strategic cross-promotions. - -## Scope - -- Tracking and analyzing subscriber growth trends on a monthly basis -- Running and iterating on the referral program to turn readers into advocates -- Optimizing the welcome email sequence to convert new signups into engaged readers -- SEO optimization of published essays and newsletter archive pages -- Experimenting with cross-promotions and partnerships with complementary newsletters -- Monitoring open rate and engagement metrics as leading indicators of list health - -## Current state - -The newsletter is on a strong growth trajectory, with organic and referral channels accounting for the majority of new subscribers. Open rates remain well above industry average at over 45%, which signals a healthy, engaged list. The referral program is functional but underutilized — most readers do not actively share, and the incentive structure could be more compelling. - -SEO is an area with significant untapped potential. Several essays rank well for competitive long-tail keywords, but the back-catalog has not been systematically optimized. The welcome sequence converts well, though it has not been updated in several months and could benefit from fresh content that reflects the newsletter's current positioning. - -## Key procedures - -- [[procedure-referral-program]] -- [[procedure-welcome-email-sequence]] -- [[procedure-seo-content-optimization]] - -## Key measures - -- [[measure-subscribers]] -- [[measure-open-rate]] diff --git a/demo-vault-v2/responsibility-health-fitness.md b/demo-vault-v2/responsibility-health-fitness.md deleted file mode 100644 index 405405ae..00000000 --- a/demo-vault-v2/responsibility-health-fitness.md +++ /dev/null @@ -1,38 +0,0 @@ ---- -aliases: ["Health & Fitness"] -Is A: Responsibility -Belongs to: "[[area-health]]" -Has Measures: ["[[measure-resting-hr]]", "[[measure-cycling-km-per-month]]"] -Has Procedures: ["[[procedure-weekly-cycling-block]]", "[[procedure-gym-routine]]", "[[procedure-monthly-health-review]]", "[[procedure-race-preparation]]"] -Status: Open ---- -# Health & Fitness - -Health and fitness underpin everything else. Without consistent physical training and good recovery habits, writing quality drops, decision-making suffers, and energy for the business fades. This responsibility covers structured cycling training, gym work, nutrition awareness, and preparing for endurance events like gran fondos — treating the body as infrastructure, not an afterthought. - -## Scope - -- Following a structured weekly cycling training plan with volume and intensity targets -- Maintaining a consistent gym routine focused on functional strength and injury prevention -- Tracking resting heart rate and other biomarkers as proxies for overall fitness -- Preparing for specific endurance events and races throughout the season -- Conducting monthly health reviews to assess trends and adjust training load -- Balancing training volume with work demands, especially during high-output content weeks - -## Current state - -The cycling season is in full swing, and monthly volume is tracking at or above 300 km per month. Resting heart rate is holding in a good range, which suggests the aerobic base is solid. Gym sessions have been more inconsistent — they tend to get squeezed when the content calendar is packed, which is a pattern worth addressing. - -Race preparation for upcoming gran fondos is on track, but the transition between base-building and race-specific intensity blocks needs more deliberate planning. The monthly health review has been useful for catching overtraining signals early, though adherence to the review cadence has slipped a few times this year. - -## Key procedures - -- [[procedure-weekly-cycling-block]] -- [[procedure-gym-routine]] -- [[procedure-monthly-health-review]] -- [[procedure-race-preparation]] - -## Key measures - -- [[measure-resting-hr]] -- [[measure-cycling-km-per-month]] diff --git a/demo-vault-v2/responsibility-learning.md b/demo-vault-v2/responsibility-learning.md deleted file mode 100644 index f3777af7..00000000 --- a/demo-vault-v2/responsibility-learning.md +++ /dev/null @@ -1,36 +0,0 @@ ---- -aliases: ["Learning"] -Is A: Responsibility -Belongs to: "[[area-learning]]" -Has Measures: ["[[measure-books-per-month]]", "[[measure-evergreen-notes-created]]"] -Has Procedures: ["[[procedure-weekly-reading-session]]", "[[procedure-evergreen-note-writing]]"] -Status: Open ---- -# Learning - -Learning is the raw material supply chain for everything Refactoring produces. Reading widely, studying deeply, and synthesizing ideas into evergreen notes ensures that the newsletter and podcast draw from a genuine well of insight rather than recycled surface-level takes. This responsibility covers deliberate reading habits, note-taking systems, and the ongoing effort to turn consumption into durable knowledge. - -## Scope - -- Maintaining a consistent weekly reading practice across books, articles, and research papers -- Focusing reading on non-fiction domains: business strategy, technology, behavioral science, and self-improvement -- Writing evergreen notes that distill key ideas into reusable, linkable knowledge assets -- Curating a reading pipeline that balances current interests with deliberate exploration of new fields -- Connecting reading insights to content production — feeding ideas into newsletter essays and podcast topics -- Reviewing and refining the personal knowledge management workflow periodically - -## Current state - -The reading habit is consistent, averaging two or more books per month, with a good mix of business, technology, and science titles. Evergreen note output is meeting the target of three or more per month, though the quality and depth of notes varies — some are thorough syntheses, others are closer to quick highlights that need revisiting. - -The main gap is in the connection between reading and production. Many good ideas from books end up buried in notes without surfacing in newsletter content or podcast conversations. Building a better bridge between [[procedure-evergreen-note-writing]] and [[procedure-monthly-pillar-planning]] would help close this loop and make the learning investment pay off more directly. - -## Key procedures - -- [[procedure-weekly-reading-session]] -- [[procedure-evergreen-note-writing]] - -## Key measures - -- [[measure-books-per-month]] -- [[measure-evergreen-notes-created]] diff --git a/demo-vault-v2/responsibility-personal-finance.md b/demo-vault-v2/responsibility-personal-finance.md deleted file mode 100644 index 4eb7b1a6..00000000 --- a/demo-vault-v2/responsibility-personal-finance.md +++ /dev/null @@ -1,37 +0,0 @@ ---- -aliases: ["Personal Finance"] -Is A: Responsibility -Belongs to: "[[area-finance]]" -Has Measures: ["[[measure-net-worth]]", "[[measure-savings-rate]]"] -Has Procedures: ["[[procedure-monthly-portfolio-review]]", "[[procedure-quarterly-financial-planning]]", "[[procedure-invoice-processing]]"] -Status: Open ---- -# Personal Finance - -Personal finance is about building long-term financial resilience so that creative and business decisions are never driven by short-term cash pressure. This responsibility covers investment management, savings discipline, financial planning, and the operational side of invoicing and cash flow — all with a philosophy rooted in simplicity, index fund investing, and a high savings rate. - -## Scope - -- Tracking net worth on a monthly basis to maintain visibility into long-term trajectory -- Maintaining a savings rate above 30% of income through disciplined spending -- Managing an investment portfolio primarily built on low-cost index funds -- Running quarterly financial planning sessions to review goals, allocation, and risk -- Processing invoices and managing cash flow for Refactoring's sponsorship revenue -- Keeping financial systems simple and automated wherever possible - -## Current state - -The savings rate target is consistently met, and the portfolio is performing in line with broad market indices. Monthly net worth tracking has become a reliable habit, and the quarterly planning sessions provide a good checkpoint for rebalancing and revisiting assumptions. Invoice processing runs smoothly thanks to a standardized workflow, though there is occasional lag when sponsor renewals overlap. - -The main area for improvement is tax optimization. As Refactoring's revenue grows, the Italian tax situation becomes more complex, and there may be opportunities to structure things more efficiently. This is worth a dedicated review in the next quarterly planning session. The overall philosophy remains unchanged: keep it boring, keep it diversified, and let compounding do the work. - -## Key procedures - -- [[procedure-monthly-portfolio-review]] -- [[procedure-quarterly-financial-planning]] -- [[procedure-invoice-processing]] - -## Key measures - -- [[measure-net-worth]] -- [[measure-savings-rate]] diff --git a/demo-vault-v2/responsibility-podcast.md b/demo-vault-v2/responsibility-podcast.md deleted file mode 100644 index a19b1e4d..00000000 --- a/demo-vault-v2/responsibility-podcast.md +++ /dev/null @@ -1,39 +0,0 @@ ---- -aliases: ["Podcast"] -Is A: Responsibility -Belongs to: "[[area-building]]" -Has Measures: ["[[measure-podcast-downloads]]", "[[measure-podcast-episodes-per-month]]"] -Has Procedures: ["[[procedure-podcast-recording]]", "[[procedure-podcast-guest-outreach]]", "[[procedure-podcast-editing]]", "[[procedure-podcast-show-notes]]", "[[procedure-podcast-analytics]]"] -Status: Open ---- -# Podcast - -The Refactoring podcast is the second major content channel alongside the newsletter. Bi-weekly episodes featuring conversations with tech leaders, engineering managers, and founders create a different kind of depth and relationship than written content alone. This responsibility covers the full production pipeline — guest sourcing, recording, editing, publishing, and performance analysis — and plays a critical role in audience growth and brand positioning. - -## Scope - -- Sourcing and scheduling guests who bring genuine insight on engineering culture, leadership, and building -- Preparing for and conducting interviews that are conversational, substantive, and worth re-listening to -- Managing the post-production pipeline: editing, show notes, and publishing on schedule -- Tracking downloads and engagement metrics to understand what resonates with the audience -- Maintaining a guest pipeline that is at least 4-6 weeks ahead of the publishing calendar -- Cross-promoting episodes through the newsletter and social channels to maximize reach - -## Current state - -The podcast is shipping consistently at two episodes per month, and download numbers are trending upward. Guest quality has been strong, with several recent episodes generating above-average engagement and social sharing. The production pipeline with [[person-paco-furiani]] handling operations has reduced the turnaround time from recording to publication significantly. - -The main challenge is guest pipeline management. Outreach tends to happen in bursts rather than steadily, which occasionally creates scheduling pressure. There is also an opportunity to be more strategic about guest selection — aligning episode topics with upcoming newsletter themes to create a more cohesive content ecosystem. Analytics review happens but is not yet systematic enough to drive data-informed decisions about format and topic selection. - -## Key procedures - -- [[procedure-podcast-recording]] -- [[procedure-podcast-guest-outreach]] -- [[procedure-podcast-editing]] -- [[procedure-podcast-show-notes]] -- [[procedure-podcast-analytics]] - -## Key measures - -- [[measure-podcast-downloads]] -- [[measure-podcast-episodes-per-month]] diff --git a/demo-vault-v2/responsibility-sponsorships.md b/demo-vault-v2/responsibility-sponsorships.md index 221eae0b..e112127e 100644 --- a/demo-vault-v2/responsibility-sponsorships.md +++ b/demo-vault-v2/responsibility-sponsorships.md @@ -1,39 +1,21 @@ --- -aliases: ["Sponsorships"] -Is A: Responsibility -Belongs to: "[[area-building]]" -Has Measures: ["[[measure-sponsorship-mrr]]", "[[measure-close-rate]]"] -Has Procedures: ["[[procedure-monthly-sponsor-report]]", "[[procedure-quarterly-sponsor-outreach]]", "[[procedure-sponsor-onboarding]]", "[[procedure-invoice-processing]]", "[[procedure-sponsor-renewal]]"] -Status: Open +type: Responsibility +aliases: + - "[[Sponsorships]]" +belongs_to: "[[area-building]]" +has_measures: + - "[[measure-sponsorship-mrr]]" + - "[[measure-close-rate]]" +has_procedures: + - "[[procedure-quarterly-sponsor-outreach]]" + - "[[procedure-sponsor-onboarding]]" +status: Open --- + # Sponsorships -Sponsorships are the primary revenue engine for Refactoring. Selling and managing sponsorship deals with B2B tech companies funds the entire operation — from team salaries to tools to the time and space needed for quality content production. This responsibility covers the full sponsorship lifecycle: outreach, closing, onboarding, delivery, reporting, and renewal. The goal is to build long-term partnerships, not one-off ad placements. +The compact responsibility used to verify that wikilink-valued fields render as relationships instead of plain text properties. -## Scope +- `status` stays a normal property. +- `has_measures` and `has_procedures` should render in the relationships area. -- Running quarterly outreach campaigns to fill the sponsorship pipeline with qualified prospects -- Closing sponsorship deals with a focus on long-term, recurring partnerships over one-off placements -- Onboarding new sponsors with clear expectations on deliverables, timelines, and audience data -- Delivering monthly sponsor reports that demonstrate value and ROI transparently -- Managing renewals proactively, using performance data and relationship quality to retain sponsors -- Coordinating with [[person-matteo-cellini]] on partnership strategy and outreach execution - -## Current state - -Sponsorship revenue is growing steadily, with MRR on a clear upward trajectory from its current base toward the target. Close rate remains healthy at above 30%, and the renewal pipeline is strong — most sponsors who run a first campaign choose to continue. The relationship-first approach, grounded in the philosophy captured in [[the-sponsorship-relationship]], is paying off. - -The biggest bottleneck is outreach volume. Quarterly outreach cycles sometimes lose momentum in execution, and there is an opportunity to systematize the pipeline further with [[person-matteo-cellini]] owning more of the top-of-funnel work. Sponsor reporting has improved significantly but could be more automated. The invoice processing workflow is reliable but still involves some manual steps that are worth streamlining. - -## Key procedures - -- [[procedure-quarterly-sponsor-outreach]] -- [[procedure-sponsor-onboarding]] -- [[procedure-sponsor-renewal]] -- [[procedure-monthly-sponsor-report]] -- [[procedure-invoice-processing]] - -## Key measures - -- [[measure-sponsorship-mrr]] -- [[measure-close-rate]] diff --git a/demo-vault-v2/responsibility-team-management.md b/demo-vault-v2/responsibility-team-management.md deleted file mode 100644 index e99b9b14..00000000 --- a/demo-vault-v2/responsibility-team-management.md +++ /dev/null @@ -1,39 +0,0 @@ ---- -aliases: ["Team Management"] -Is A: Responsibility -Belongs to: "[[area-building]]" -Has Measures: ["[[measure-team-nps]]", "[[measure-task-completion-rate]]"] -Has Procedures: ["[[procedure-weekly-team-sync]]", "[[procedure-biweekly-1on1-matteo]]", "[[procedure-biweekly-1on1-paco]]", "[[procedure-biweekly-1on1-sara]]", "[[procedure-quarterly-team-retro]]"] -Status: Open ---- -# Team Management - -Team management is about getting the most out of a small, high-trust team without introducing the overhead and bureaucracy that kills small operations. With [[person-matteo-cellini]] on partnerships, [[person-paco-furiani]] on operations, and [[person-sara-ricci]] on editorial, the team is compact but covers the critical functions of the business. This responsibility encompasses hiring decisions, task coordination, performance feedback, and building a culture where people do their best work with minimal friction. - -## Scope - -- Running weekly team syncs to align priorities, surface blockers, and maintain shared context -- Conducting biweekly 1:1s with each team member to provide feedback, coaching, and support -- Tracking task completion rates to ensure operational commitments are met consistently -- Running quarterly retrospectives to reflect on what is working and what needs to change -- Making decisions about team structure, roles, and potential new hires as the business grows -- Maintaining team morale and engagement, measured through internal NPS and qualitative signals - -## Current state - -The team is functioning well. Weekly syncs keep everyone aligned, and the biweekly 1:1 cadence provides enough touchpoints to catch issues early. Task completion rate is above target, and the overall vibe is positive — people feel ownership over their domains and have the autonomy to make decisions within them. - -The main area to watch is scaling. As Refactoring grows, the current team structure will come under pressure. Matteo is increasingly stretched across partnerships and sponsor outreach, and there may be a case for additional support there. The quarterly retro has been valuable for surfacing these kinds of structural questions before they become urgent. The philosophy outlined in [[small-teams-scale-through-systems]] guides how the team thinks about growth — systems and processes first, headcount second. - -## Key procedures - -- [[procedure-weekly-team-sync]] -- [[procedure-biweekly-1on1-matteo]] -- [[procedure-biweekly-1on1-paco]] -- [[procedure-biweekly-1on1-sara]] -- [[procedure-quarterly-team-retro]] - -## Key measures - -- [[measure-team-nps]] -- [[measure-task-completion-rate]] diff --git a/demo-vault-v2/responsibility.md b/demo-vault-v2/responsibility.md deleted file mode 100644 index ef43db1e..00000000 --- a/demo-vault-v2/responsibility.md +++ /dev/null @@ -1,7 +0,0 @@ ---- -Is A: Type ---- - -# Responsibility - -A Responsibility is an ongoing area of ownership — something you are accountable for indefinitely. Responsibilities have procedures, projects, and measures attached. diff --git a/demo-vault-v2/responsive-rename-test-renamed.md b/demo-vault-v2/responsive-rename-test-renamed.md deleted file mode 100644 index a7e1922c..00000000 --- a/demo-vault-v2/responsive-rename-test-renamed.md +++ /dev/null @@ -1,7 +0,0 @@ ---- -type: Note -status: Active ---- - - -Appended by raw editor test \ No newline at end of file diff --git a/demo-vault-v2/save-no-rename-test.md b/demo-vault-v2/save-no-rename-test.md deleted file mode 100644 index dce2c691..00000000 --- a/demo-vault-v2/save-no-rename-test.md +++ /dev/null @@ -1,6 +0,0 @@ ---- -title: Save No Rename Test -type: Note -status: Active ---- -# Save No Rename Test diff --git a/demo-vault-v2/should-be-r-renamed.md b/demo-vault-v2/should-be-r-renamed.md deleted file mode 100644 index 88d59f5a..00000000 --- a/demo-vault-v2/should-be-r-renamed.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Should Be R -type: Note -status: Active ---- -# Should Be R Renamed - -Snippet test content 1773606307602everted diff --git a/demo-vault-v2/sleeping-more-is-a-superpower.md b/demo-vault-v2/sleeping-more-is-a-superpower.md deleted file mode 100644 index 9a82a6d4..00000000 --- a/demo-vault-v2/sleeping-more-is-a-superpower.md +++ /dev/null @@ -1,28 +0,0 @@ ---- -aliases: ["Sleeping More Is a Competitive Advantage"] -Is A: Evergreen -Topics: ["[[topic-sleep-recovery]]", "[[topic-mental-health]]"] -Status: Published ---- -# Sleeping More Is a Competitive Advantage -The tech industry glorifies sleep deprivation. 'Sleep when you're dead.' '80-hour weeks.' These are cultural artifacts from an era when we didn't understand what sleep deprivation does to cognitive performance. - -Sleep-deprived people are bad at judging their own impairment. They think they're functioning at 80% when they're actually at 50%. They make more errors, have worse judgment, and are less creative — and they don't know it. - -Consistently sleeping 7-8 hours doesn't make you less productive. It makes you more productive per hour, with better judgment and lower error rates. The math nearly always works out. - -The evidence on this is overwhelming and I find it remarkable how widely it is still ignored. Matthew Walker's research at Berkeley demonstrates that after 17-19 hours of wakefulness, cognitive performance degrades to the equivalent of a blood alcohol level of 0.05%. Most professionals would never attend a meeting drunk, but they routinely make important decisions on 5-6 hours of sleep, which produces comparable impairment. The self-assessment paradox — sleep-deprived people consistently overestimate their own functioning — means that the people most affected by this are the least likely to recognize it. - -My own experience confirms the research. I track my sleep with an Oura ring and my writing output with simple metrics: words per hour, editing time per piece, and reader engagement on published pieces. The correlation between sleep quality and every single one of these metrics is strong enough that I no longer treat sleep as a personal preference. I treat it as a business input, like software or office space. When I sleep 7.5+ hours, my first-draft quality is noticeably higher, I require fewer editing passes, and the resulting pieces generate more reader engagement. When I sleep under 6.5 hours for more than two consecutive nights, my writing degrades in specific, predictable ways: I default to cliches, my arguments become less structured, and I miss logical gaps that I would normally catch. - -The competitive advantage of sleep becomes even more pronounced in domains that require creativity and judgment rather than rote execution. A factory worker on 6 hours of sleep can still operate a machine at 90% efficiency. A founder on 6 hours of sleep makes hiring decisions, strategic bets, and product calls with dramatically impaired judgment — and the consequences of those impaired decisions compound over months and years. The worst part is that the high-stakes decisions where judgment matters most are often the ones made at the end of long, sleep-deprived days. The structure of founder life systematically concentrates the most important decisions in the periods of worst cognitive performance. - -## Key insight -Sleep is the highest-leverage performance intervention available to knowledge workers, and it is free. Every hour of sleep between 6 and 8 hours produces more than an hour of effective work the following day through improved focus, creativity, and judgment. The math is unintuitive but consistent: sleeping 7.5 hours and working 9 focused hours produces more and better output than sleeping 6 hours and working 11 foggy hours. The founders and creators who internalize this do not see sleep as a constraint on their productivity. They see it as the foundation of their productivity. - -## Related -- [[on-founder-energy-management]] — Sleep as the first tier of the energy management framework -- [[recovery-week-in-training]] — Sleep is to daily recovery what recovery weeks are to training periodization -- [[training-load-and-knowledge-work]] — The adaptation model requires sleep as the primary recovery mechanism -- [[cycling-teaches-patience]] — The discipline to sleep enough is the same discipline that prevents going out too hard on a ride -- [[topic-sleep-recovery]] — Broader thinking on sleep and recovery diff --git a/demo-vault-v2/small-teams-scale-through-systems.md b/demo-vault-v2/small-teams-scale-through-systems.md deleted file mode 100644 index 90d1709f..00000000 --- a/demo-vault-v2/small-teams-scale-through-systems.md +++ /dev/null @@ -1,28 +0,0 @@ ---- -aliases: ["Small Teams Scale Through Systems, Not Headcount"] -Is A: Evergreen -Topics: ["[[topic-team-leadership]]", "[[topic-saas-business]]"] -Status: Published ---- -# Small Teams Scale Through Systems, Not Headcount -The instinct when workload grows is to hire. But hiring is slow, expensive, and introduces coordination overhead. The better first move is almost always to systematize. - -A team of 3 with good systems — documented processes, clear ownership, async-first communication — can often outperform a team of 10 without them. The difference is decision latency and context overhead. - -This is especially true in content businesses, where the core work is creative and can't easily be parallelized. Better to double the quality of what 3 people produce than to dilute quality by hiring 3 more. - -The systems I have found most valuable in running Refactoring with a very small team fall into three categories. The first is process documentation: not extensive manuals, but clear checklists for recurring tasks. The weekly newsletter has a documented workflow from ideation to publication that anyone on the team can follow. This eliminates the bottleneck of having one person who holds all the context. The second is asynchronous communication defaults: we write things down instead of scheduling meetings, which means decisions and context are preserved in a searchable format rather than lost in a Zoom call. The third is ownership clarity: every deliverable has exactly one owner, and that owner has the authority to make decisions without consensus. - -The counterintuitive insight about systems is that they create freedom rather than constraining it. When the newsletter production workflow is systematized, I do not spend cognitive energy on logistics — I spend it on the creative work that actually differentiates the product. The system handles the how, freeing me to focus on the what. This is why the best creators I know are also the most systematized. They do not see systems and creativity as opposing forces. They see systems as the infrastructure that protects creative energy from being consumed by operational friction. - -The scaling question for small teams is rarely "do we need more people?" It is "have we exhausted the leverage available from better systems?" In my experience, teams reach for headcount far too early. Every new hire adds communication overhead (the number of communication channels grows quadratically with team size), onboarding cost, and cultural dilution risk. A new system — a better workflow, a clearer decision framework, an automation — adds leverage with none of these costs. The right time to hire is when the systems are good and the constraint is genuinely human capacity, not when the systems are poor and the constraint is operational chaos that more people would only amplify. - -## Key insight -Systems are a small team's competitive advantage over larger competitors. While big teams struggle with coordination overhead and diffused ownership, a well-systematized small team can make decisions faster, iterate quicker, and maintain quality consistency. The path to scaling is not headcount-first but systems-first: document, automate, and clarify until every team member is operating at maximum leverage. Only then does adding a person multiply output rather than dividing attention. - -## Related -- [[the-compound-effect-in-knowledge-work]] — Good systems compound: each process improvement makes the next one easier to implement -- [[on-founder-energy-management]] — Systems reduce the energy drain of operational decisions, preserving energy for creative work -- [[the-saas-metric-that-matters]] — NRR in SaaS is often driven by the quality of systems supporting the customer, not team size -- [[procedure-weekly-newsletter]] — A concrete example of a production system for a small content team -- [[topic-team-leadership]] — Broader thinking on leading and scaling teams diff --git a/demo-vault-v2/target-books-24q1.md b/demo-vault-v2/target-books-24q1.md deleted file mode 100644 index 4e7139ff..00000000 --- a/demo-vault-v2/target-books-24q1.md +++ /dev/null @@ -1,25 +0,0 @@ ---- -aliases: ["Books Q1 2024"] -Is A: Target -Belongs to: "[[24q1]]" -Measure: "[[measure-books-per-month]]" -Goal value: 6 -Actual value: 6 -Status: Done ---- -# Books Target Q1 2024 -Target: 6 books in the quarter (2/month). - -The reading target is a personal development commitment that [[person-luca-rossi]] treats as seriously as the business metrics. The goal of two books per month balances depth with breadth -- enough to explore a range of topics across engineering leadership, business strategy, and personal growth without rushing through material. Q1 is typically the easiest quarter for reading, with fewer social commitments and long winter evenings. - -## Progress - -- January: completed 2 books -- "The Manager's Path" by Camille Fournier (re-read for a newsletter deep dive) and "Working in Public" by Nadia Eghbal. -- February: completed 2 books -- "Thinking in Bets" by Annie Duke and "The Almanack of Naval Ravikant" by Eric Jorgenson. -- March: completed 2 books -- "Staff Engineer" by Will Larson and "Atomic Habits" by James Clear. -- Hit the target exactly with 6 books for the quarter. - -## Notes - -- Re-reading "The Manager's Path" proved valuable -- it directly informed two newsletter editions and generated strong reader engagement. Re-reads of canonical books should be a regular practice. -- The mix of technical leadership and general non-fiction felt right. Pure business books tend to be less actionable than books that bridge engineering and leadership. diff --git a/demo-vault-v2/target-books-24q2.md b/demo-vault-v2/target-books-24q2.md deleted file mode 100644 index d793a840..00000000 --- a/demo-vault-v2/target-books-24q2.md +++ /dev/null @@ -1,25 +0,0 @@ ---- -aliases: ["Books Q2 2024"] -Is A: Target -Belongs to: "[[24q2]]" -Measure: "[[measure-books-per-month]]" -Goal value: 6 -Actual value: 4 -Status: Done ---- -# Books Target Q2 2024 -Target: 6 books in the quarter (2/month). - -Q2 was expected to be more challenging for reading time due to the [[24q2-hire-editor]] project consuming significant bandwidth. The 6-book target was maintained regardless, as [[person-luca-rossi]] views the reading habit as non-negotiable infrastructure for content quality. - -## Progress - -- April: completed 2 books -- "An Elegant Puzzle" by Will Larson and "Show Your Work" by Austin Kleon. -- May: completed 1 book -- "The Hard Thing About Hard Things" by Ben Horowitz. The editor hiring process ate into evening reading time significantly. -- June: completed 1 book -- "Continuous Discovery Habits" by Teresa Torres. Started a second book but did not finish before quarter end. -- Finished with 4 books -- the weakest quarter of the year, missing the target by 2. - -## Notes - -- The miss was directly attributable to the editor hiring process, which involved reviewing writing samples and conducting interviews over evenings and weekends. This was a worthwhile trade-off. -- Quality over quantity: the 4 books read this quarter were all highly relevant and each generated at least one newsletter idea. Better to read fewer books well than rush through more. diff --git a/demo-vault-v2/target-books-24q3.md b/demo-vault-v2/target-books-24q3.md deleted file mode 100644 index 5c6e732a..00000000 --- a/demo-vault-v2/target-books-24q3.md +++ /dev/null @@ -1,25 +0,0 @@ ---- -aliases: ["Books Q3 2024"] -Is A: Target -Belongs to: "[[24q3]]" -Measure: "[[measure-books-per-month]]" -Goal value: 6 -Actual value: 7 -Status: Done ---- -# Books Target Q3 2024 -Target: 6 books in the quarter (2/month). - -With the editor onboarded and the newsletter operations running more smoothly, Q3 was an opportunity to recover the reading pace. Summer travel also provided unexpected reading time -- long flights and beach days turned out to be productive for focused reading. - -## Progress - -- July: completed 3 books -- "Build" by Tony Fadell, "Obviously Awesome" by April Dunford, and "The Design of Everyday Things" by Don Norman. The Fadell book was consumed almost entirely during a 9-hour flight. -- August: completed 2 books -- "Inspired" by Marty Cagan and "Refactoring UI" by Adam Wathan & Steve Schoger. The latter directly influenced thinking about Laputa's design system. -- September: completed 2 books -- "Engineering Management for the Rest of Us" by Sarah Drasner and "Creativity, Inc." by Ed Catmull. -- Exceeded the target with 7 books -- the best reading quarter in the tracking period. - -## Notes - -- Travel is underrated as reading time. Three of the seven books were read primarily during trips. Worth factoring this into scheduling. -- "Refactoring UI" was a standout -- it changed how [[person-luca-rossi]] thinks about the Laputa UI and led to several design decisions captured in the project spec. diff --git a/demo-vault-v2/target-books-24q4.md b/demo-vault-v2/target-books-24q4.md deleted file mode 100644 index 7cfee05d..00000000 --- a/demo-vault-v2/target-books-24q4.md +++ /dev/null @@ -1,25 +0,0 @@ ---- -aliases: ["Books Q4 2024"] -Is A: Target -Belongs to: "[[24q4]]" -Measure: "[[measure-books-per-month]]" -Goal value: 6 -Actual value: 5 -Status: Done ---- -# Books Target Q4 2024 -Target: 6 books in the quarter (2/month). - -Q4 is always a demanding quarter with year-end business reviews, holiday content planning, and personal commitments. The 6-book target was maintained but [[person-luca-rossi]] expected it to be tight. The reading list leaned more heavily toward business and strategy books to inform 2025 planning. - -## Progress - -- October: completed 2 books -- "Company of One" by Paul Jarvis and "The Mom Test" by Rob Fitzpatrick. Both influenced thinking about keeping the business intentionally small. -- November: completed 2 books -- "Extreme Ownership" by Jocko Willink and "Range" by David Epstein. -- December: completed 1 book -- "Deep Work" by Cal Newport. Holiday social obligations and year-end planning reduced reading time significantly. -- Finished with 5 books -- one short of target. - -## Notes - -- "Company of One" was particularly resonant and reinforced the decision to keep the newsletter business lean rather than hiring a full team. This philosophy carries into 2025 planning. -- Annual total: 22 books (6 + 4 + 7 + 5), averaging 5.5 per quarter. The 2/month target is aspirational but the actual pace of roughly 1.5/month is sustainable and productive. diff --git a/demo-vault-v2/target-books-25q1.md b/demo-vault-v2/target-books-25q1.md deleted file mode 100644 index d798bb08..00000000 --- a/demo-vault-v2/target-books-25q1.md +++ /dev/null @@ -1,25 +0,0 @@ ---- -aliases: ["Books Q1 2025"] -Is A: Target -Belongs to: "[[25q1]]" -Measure: "[[measure-books-per-month]]" -Goal value: 6 -Actual value: 4 -Status: Done ---- -# Books Target Q1 2025 -Target: 6 books in the quarter (2/month). - -Q1 2025 was heavily impacted by the launch push for [[25q1-laputa-v1]], which consumed most of [[person-luca-rossi]]'s evenings and weekends. The reading target was maintained at 6 books knowing it would be a stretch. The reading list was deliberately curated toward product development and systems design to support the Laputa work. - -## Progress - -- January: completed 2 books -- "Designing Data-Intensive Applications" by Martin Kleppmann (a technical deep-dive relevant to Laputa's architecture) and "Sprint" by Jake Knapp. -- February: completed 1 book -- "Shape Up" by Ryan Singer. Laputa development consumed nearly all available time outside of newsletter production. -- March: completed 1 book -- "Badass: Making Users Awesome" by Kathy Sierra. Started "Thinking, Fast and Slow" but only reached the halfway point. -- Finished with 4 books -- missing by 2, the same shortfall as Q2 2024. - -## Notes - -- The pattern is clear: quarters with major project launches (editor hiring in Q2 2024, Laputa v1 in Q1 2025) consistently produce 4-book quarters. This is acceptable as long as the reading maintains quality. -- "Shape Up" directly influenced the project management approach for Laputa. The 6-week cycle concept was adapted for the quarterly milestone structure. diff --git a/demo-vault-v2/target-books-25q2.md b/demo-vault-v2/target-books-25q2.md deleted file mode 100644 index 5058a42e..00000000 --- a/demo-vault-v2/target-books-25q2.md +++ /dev/null @@ -1,25 +0,0 @@ ---- -aliases: ["Books Q2 2025"] -Is A: Target -Belongs to: "[[25q2]]" -Measure: "[[measure-books-per-month]]" -Goal value: 6 -Actual value: 7 -Status: Done ---- -# Books Target Q2 2025 -Target: 6 books in the quarter (2/month). - -With Laputa v1 shipped and the business running more smoothly, Q2 was expected to be a recovery quarter for reading. [[person-luca-rossi]] also started an informal book club with [[person-sara-ricci]] and [[person-matteo-cellini]], which provided external accountability and made it easier to stay on pace. - -## Progress - -- April: completed 2 books -- "Thinking, Fast and Slow" by Daniel Kahneman (finished from Q1) and "The Psychology of Money" by Morgan Housel. -- May: completed 3 books -- "Influence" by Robert Cialdini, "Writing Down the Bones" by Natalie Goldberg, and "The Art of Doing Science and Engineering" by Richard Hamming. A long weekend trip provided extended uninterrupted reading time. -- June: completed 2 books -- "Measure What Matters" by John Doerr and "The Courage to Be Disliked" by Ichiro Kishimi. -- Exceeded target with 7 books -- matching Q3 2024 as the best quarter. - -## Notes - -- The informal book club works well as an accountability mechanism. Having a discussion partner makes it easier to commit to finishing books rather than abandoning them midway. -- "Measure What Matters" directly informed a rethink of how targets and goals are structured in the personal knowledge system -- the very system that Laputa is designed to manage. diff --git a/demo-vault-v2/target-books-25q3.md b/demo-vault-v2/target-books-25q3.md deleted file mode 100644 index 38674e7e..00000000 --- a/demo-vault-v2/target-books-25q3.md +++ /dev/null @@ -1,25 +0,0 @@ ---- -aliases: ["Books Q3 2025"] -Is A: Target -Belongs to: "[[25q3]]" -Measure: "[[measure-books-per-month]]" -Goal value: 6 -Actual value: "None" -Status: Open ---- -# Books Target Q3 2025 -Target: 6 books in the quarter (2/month). - -Q3 2025 should be favorable for reading, with summer travel planned and the Laputa development entering a more sustainable cadence. The reading list includes a mix of engineering culture books (for newsletter content), design books (for Laputa), and one or two fiction titles to broaden perspective. The book club with [[person-sara-ricci]] and [[person-matteo-cellini]] continues. - -## Progress - -- Quarter is in progress. July reading list includes "Empowered" by Marty Cagan and "Building a Second Brain" by Tiago Forte. -- Two international trips are planned, which historically correlate with higher reading output. -- The book club has selected "The Innovator's Dilemma" by Clayton Christensen as the group read for August. -- On track for 6 books based on current pace. - -## Notes - -- "Building a Second Brain" is particularly relevant as research for Laputa's feature set. The personal knowledge management space is heating up and understanding competing philosophies is important. -- Considering adding audiobooks to the tracking. Several "books" in previous quarters were actually consumed as audiobooks during runs, and this format enables more reading volume without additional sitting time. diff --git a/demo-vault-v2/target-books-25q4.md b/demo-vault-v2/target-books-25q4.md deleted file mode 100644 index f1c79b95..00000000 --- a/demo-vault-v2/target-books-25q4.md +++ /dev/null @@ -1,25 +0,0 @@ ---- -aliases: ["Books Q4 2025"] -Is A: Target -Belongs to: "[[25q4]]" -Measure: "[[measure-books-per-month]]" -Goal value: 6 -Actual value: "None" -Status: Open ---- -# Books Target Q4 2025 -Target: 6 books in the quarter (2/month). - -Q4 will be the final reading quarter of the two-year tracking period. The goal is to close the year strong with at least 6 books, bringing the 2025 annual total to a projected 21-23 books. The reading list will focus on year-end reflection themes -- strategy, decision-making, and personal growth -- to inform 2026 goal-setting. - -## Progress - -- Quarter has not started yet. Preliminary reading list is being assembled. -- Planned reads include "Good Strategy Bad Strategy" by Richard Rumelt, "Antifragile" by Nassim Taleb, and at least one title recommended by the book club. -- The historical pattern suggests Q4 will land at 5 books due to holiday commitments, but aiming for 6 with the buffer of audiobooks. -- Two-year running total (if Q3 and Q4 hit targets): approximately 46 books across 8 quarters. - -## Notes - -- At this point, the reading habit is well-established and self-sustaining. The formal tracking has been valuable for maintaining accountability but may not need to continue as a formal target in 2026. -- The most impactful books over the two-year period have consistently been the ones that bridge technical and human domains. This should guide future reading list curation. diff --git a/demo-vault-v2/target-resting-hr-24q1.md b/demo-vault-v2/target-resting-hr-24q1.md deleted file mode 100644 index 5864179a..00000000 --- a/demo-vault-v2/target-resting-hr-24q1.md +++ /dev/null @@ -1,25 +0,0 @@ ---- -aliases: ["Resting HR Q1 2024"] -Is A: Target -Belongs to: "[[24q1]]" -Measure: "[[measure-resting-hr]]" -Goal value: 54 -Actual value: 57 -Status: Behind ---- -# Resting HR Target Q1 2024 -Target: resting HR < 54 bpm. - -Resting heart rate is the primary health metric that [[person-luca-rossi]] tracks as a proxy for overall cardiovascular fitness. The Q1 2024 target of 54 bpm was set based on a late-2023 average of around 58 bpm, with the assumption that a consistent running habit (3-4 times per week) would bring it down steadily. Lower resting HR correlates strongly with better sleep quality and sustained energy throughout the workday. - -## Progress - -- January: averaged 58 bpm. Holiday indulgence and a two-week break from running over the new year period meant starting the quarter at baseline. -- February: improved to 56 bpm average as running frequency resumed to 3x/week. Added one zone 2 long run per week. -- March: ended at 57 bpm average. A mild cold in mid-March disrupted training for 10 days and caused a temporary spike to 60 bpm. -- Quarter average of 57 bpm -- missed the 54 bpm target by 3 bpm. - -## Notes - -- The 54 bpm target was likely too aggressive for Q1 given the holiday starting point. A more realistic target would have been 56 bpm, with 54 as a stretch goal. -- Illness-related setbacks are hard to plan for but have an outsized impact on HR trends. Building in recovery weeks after illness rather than trying to immediately resume full training would be beneficial. diff --git a/demo-vault-v2/target-resting-hr-24q2.md b/demo-vault-v2/target-resting-hr-24q2.md deleted file mode 100644 index 6c786ac1..00000000 --- a/demo-vault-v2/target-resting-hr-24q2.md +++ /dev/null @@ -1,25 +0,0 @@ ---- -aliases: ["Resting HR Q2 2024"] -Is A: Target -Belongs to: "[[24q2]]" -Measure: "[[measure-resting-hr]]" -Goal value: 54 -Actual value: 53 -Status: Done ---- -# Resting HR Target Q2 2024 -Target: resting HR < 54 bpm. - -The 54 bpm target was carried over from Q1 after missing it by 3 bpm. Spring weather made outdoor running more enjoyable and consistent, and [[person-luca-rossi]] added structured interval training to the routine based on advice from [[person-sara-ricci]], who has a background in sports science. The combination of zone 2 base building and weekly intervals was expected to drive meaningful HR improvement. - -## Progress - -- April: averaged 55 bpm as the consistent spring running routine took hold. Running 4x/week for the first time, including one interval session. -- May: dropped to 53 bpm average. The interval training appeared to have a significant impact -- two weeks of measurable improvement after introducing tempo runs. -- June: held at 53 bpm average through the month. Added a weekly cycling session as cross-training without disrupting the running schedule. -- Quarter average of 53 bpm -- hit the target with 1 bpm to spare. - -## Notes - -- This was the first health target achieved. The structured interval training was clearly the differentiator compared to Q1's pure easy-running approach. -- [[person-sara-ricci]]'s advice on the 80/20 rule (80% easy, 20% hard) for endurance training proved correct. The temptation to run hard every day is counterproductive. diff --git a/demo-vault-v2/target-resting-hr-24q3.md b/demo-vault-v2/target-resting-hr-24q3.md deleted file mode 100644 index 4d38eac4..00000000 --- a/demo-vault-v2/target-resting-hr-24q3.md +++ /dev/null @@ -1,25 +0,0 @@ ---- -aliases: ["Resting HR Q3 2024"] -Is A: Target -Belongs to: "[[24q3]]" -Measure: "[[measure-resting-hr]]" -Goal value: 53 -Actual value: 55 -Status: Behind ---- -# Resting HR Target Q3 2024 -Target: resting HR < 53 bpm. - -After hitting the Q2 target, the bar was raised slightly to 53 bpm. Summer presented a mixed bag for training: longer days and better weather supported outdoor activity, but travel disruptions and heat made consistent training harder. The [[24q3-podcast-season-2]] launch also added time pressure, compressing the windows available for exercise. - -## Progress - -- July: averaged 54 bpm. Summer heat forced several runs to be cut short or replaced with indoor cycling, which is less effective for HR improvement. -- August: spiked to 56 bpm average during a two-week vacation where running was inconsistent and diet was less controlled. Also coincided with the Hacker News traffic spike, which caused stress-related sleep disruption. -- September: recovered to 55 bpm as routine normalized, but could not close the gap to 53 in one month. -- Quarter average of 55 bpm -- missed the 53 bpm target by 2 bpm. - -## Notes - -- Summer travel and heat are a recurring challenge. Pre-planning hotel gym access and having a travel-friendly bodyweight routine could mitigate the vacation disruption. -- The correlation between stress (Hacker News traffic week) and elevated resting HR was striking -- roughly +3 bpm during that period. Managing stress responses is as important as the physical training. diff --git a/demo-vault-v2/target-resting-hr-24q4.md b/demo-vault-v2/target-resting-hr-24q4.md deleted file mode 100644 index 6b3c292d..00000000 --- a/demo-vault-v2/target-resting-hr-24q4.md +++ /dev/null @@ -1,25 +0,0 @@ ---- -aliases: ["Resting HR Q4 2024"] -Is A: Target -Belongs to: "[[24q4]]" -Measure: "[[measure-resting-hr]]" -Goal value: 53 -Actual value: 51 -Status: Done ---- -# Resting HR Target Q4 2024 -Target: resting HR < 53 bpm. - -The 53 bpm target was maintained after Q3's miss. Autumn is historically the best season for running -- cool temperatures, stable weather, and a return to routine after summer. [[person-luca-rossi]] committed to a structured 12-week training plan for the first time, targeting a half-marathon in December as a forcing function for consistent training volume. - -## Progress - -- October: averaged 53 bpm as the structured training plan began. Running 4x/week with clear purpose (easy run, tempo, intervals, long run) made the routine feel more sustainable. -- November: dropped to 51 bpm -- the lowest monthly average recorded. Peak training volume for the half-marathon preparation correlated with the best HR results. -- December: held at 51 bpm through the half-marathon (completed in 1:42) and maintained through a disciplined holiday period with only a short 5-day break. -- Quarter average of 51 bpm -- comfortably exceeded the 53 bpm target. - -## Notes - -- The half-marathon goal was a breakthrough strategy. Having a specific event to train for provided structure and motivation that abstract HR targets alone could not match. -- Closing the year at 51 bpm (down from 57-58 at the start) represents significant cardiovascular improvement. This validates the investment in consistent training over quick fixes. diff --git a/demo-vault-v2/target-resting-hr-25q1.md b/demo-vault-v2/target-resting-hr-25q1.md deleted file mode 100644 index b460b787..00000000 --- a/demo-vault-v2/target-resting-hr-25q1.md +++ /dev/null @@ -1,25 +0,0 @@ ---- -aliases: ["Resting HR Q1 2025"] -Is A: Target -Belongs to: "[[25q1]]" -Measure: "[[measure-resting-hr]]" -Goal value: 52 -Actual value: 54 -Status: Behind ---- -# Resting HR Target Q1 2025 -Target: resting HR < 52 bpm. - -The Q1 2025 target of 52 bpm was set as a modest step from Q4 2024's strong finish at 51 bpm. However, the [[25q1-laputa-v1]] launch consumed enormous amounts of time and mental energy, and [[person-luca-rossi]] anticipated that maintaining the Q4 training volume would be difficult. The target reflected a desire to at least not regress significantly. - -## Progress - -- January: averaged 53 bpm. Post-half-marathon recovery period plus Laputa crunch mode reduced running from 4x to 2x/week. The reduced volume was immediately visible in the HR data. -- February: worsened to 55 bpm. Laputa v1 launch stress, combined with several late-night coding sessions, disrupted sleep patterns and elevated resting HR noticeably. -- March: recovered slightly to 54 bpm as the launch settled and running frequency returned to 3x/week. Added meditation as a stress management tool. -- Quarter average of 54 bpm -- missed the 52 bpm target by 2 bpm. - -## Notes - -- This quarter confirmed that product launch periods are incompatible with fitness targets. Future planning should explicitly set lower HR targets during expected launch quarters rather than pretending normal training is possible. -- The meditation habit started in March is promising. Even 10 minutes daily seemed to help with sleep quality and stress-related HR elevation. Worth continuing as a permanent habit. diff --git a/demo-vault-v2/target-resting-hr-25q2.md b/demo-vault-v2/target-resting-hr-25q2.md deleted file mode 100644 index a950d47e..00000000 --- a/demo-vault-v2/target-resting-hr-25q2.md +++ /dev/null @@ -1,25 +0,0 @@ ---- -aliases: ["Resting HR Q2 2025"] -Is A: Target -Belongs to: "[[25q2]]" -Measure: "[[measure-resting-hr]]" -Goal value: 52 -Actual value: 55 -Status: Behind ---- -# Resting HR Target Q2 2025 -Target: resting HR < 52 bpm. - -The 52 bpm target was maintained from Q1, representing a second attempt at this level. Despite the ongoing [[25q2-laputa-v2]] development work, the plan was to protect training time more aggressively by blocking morning hours for exercise before starting work. [[person-sara-ricci]] also suggested adding strength training to the routine to support overall metabolic health. - -## Progress - -- April: averaged 54 bpm. The morning exercise block worked well initially, with 4 runs per week for the first two weeks. A knee niggle in the third week forced a reduction to 2x/week plus cycling. -- May: plateaued at 55 bpm. The knee issue persisted, limiting running to easy efforts only. Strength training sessions were added (2x/week) but their HR impact takes longer to materialize. -- June: held at 55 bpm. The knee improved by mid-June and running volume gradually increased, but not enough time remained to see HR improvement within the quarter. -- Quarter average of 55 bpm -- missed the 52 bpm target by 3 bpm. - -## Notes - -- The knee issue was a reminder that injury prevention (stretching, strength work, proper warm-ups) needs to be part of the routine, not an afterthought. Running volume ramp-ups should be gradual. -- Two consecutive misses on the HR target suggest 52 bpm may not be achievable alongside the current work intensity. Re-evaluating whether 53 bpm is a more honest target for 2025. diff --git a/demo-vault-v2/target-resting-hr-25q3.md b/demo-vault-v2/target-resting-hr-25q3.md deleted file mode 100644 index e4546919..00000000 --- a/demo-vault-v2/target-resting-hr-25q3.md +++ /dev/null @@ -1,25 +0,0 @@ ---- -aliases: ["Resting HR Q3 2025"] -Is A: Target -Belongs to: "[[25q3]]" -Measure: "[[measure-resting-hr]]" -Goal value: 51 -Actual value: "None" -Status: Open ---- -# Resting HR Target Q3 2025 -Target: resting HR < 51 bpm. - -The 51 bpm target is aggressive given the Q2 miss, but [[person-luca-rossi]] is motivated by the knowledge that this level was achieved in Q4 2024. The strategy is to replicate the conditions that worked then: a structured training plan with a specific race goal (a 10K in September), the 80/20 training split, and daily meditation for stress management. The knee is fully recovered and strength training has become a regular part of the routine. - -## Progress - -- Quarter is in progress. July started with a 12-week structured training plan targeting the September 10K. -- Running frequency is back to 4x/week with no knee issues. Strength training continues 2x/week. -- Morning exercise blocks are protected on the calendar as non-negotiable meetings. -- Early July resting HR readings are trending around 53-54 bpm, suggesting the Q2 fitness base was not entirely lost. - -## Notes - -- The race goal strategy from Q4 2024 is being deliberately replicated. Having a concrete event to train for provides better adherence than abstract metric targets. -- [[person-sara-ricci]] recommended adding a sleep hygiene protocol (no screens after 10pm, consistent bedtime) which could be an additional lever for HR improvement beyond exercise alone. diff --git a/demo-vault-v2/target-resting-hr-25q4.md b/demo-vault-v2/target-resting-hr-25q4.md deleted file mode 100644 index 151b80d0..00000000 --- a/demo-vault-v2/target-resting-hr-25q4.md +++ /dev/null @@ -1,25 +0,0 @@ ---- -aliases: ["Resting HR Q4 2025"] -Is A: Target -Belongs to: "[[25q4]]" -Measure: "[[measure-resting-hr]]" -Goal value: 51 -Actual value: "None" -Status: Open ---- -# Resting HR Target Q4 2025 -Target: resting HR < 51 bpm. - -The 51 bpm target is maintained for Q4, which historically has been the best quarter for fitness results (cool weather, routine stability, post-summer motivation). If Q3 delivers the expected improvement, Q4 should be about maintaining and consolidating rather than making dramatic gains. The plan includes signing up for another half-marathon in November to provide a training anchor. - -## Progress - -- Quarter has not started yet. Planning is underway. -- The second half-marathon is being researched -- ideally a late-November event to keep the training plan aligned with the quarter timeline. -- If Q3 finishes at 52-53 bpm, the path to 51 by end of Q4 is straightforward with consistent training. -- If Q3 misses significantly, the target may be revised to 52 bpm to remain realistic. - -## Notes - -- Over the two-year tracking period, resting HR has ranged from 51 bpm (Q4 2024 best) to 57 bpm (Q1 2024 start). The overall trend is positive despite periodic setbacks from illness, injury, and launch stress. -- The key insight from two years of data: consistency matters more than intensity. Quarters with 3-4 moderate sessions per week always outperform quarters with sporadic intense training. diff --git a/demo-vault-v2/target-revenue-24q1.md b/demo-vault-v2/target-revenue-24q1.md deleted file mode 100644 index 33b056cb..00000000 --- a/demo-vault-v2/target-revenue-24q1.md +++ /dev/null @@ -1,25 +0,0 @@ ---- -aliases: ["Revenue Q1 2024"] -Is A: Target -Belongs to: "[[24q1]]" -Measure: "[[measure-sponsorship-mrr]]" -Goal value: 8000 -Actual value: 7251 -Status: Behind ---- -# Revenue Target Q1 2024 -Target: €8,000/month MRR by end of quarter. - -This was the inaugural quarter with formal sponsorship MRR targets, aligned with the [[2024-double-revenue]] annual goal. The €8k target assumed successful completion of the [[24q1-launch-sponsorship-packages]] project, which would introduce tiered pricing and multi-month commitments to replace the ad-hoc sponsorship deals that had characterized 2023. - -## Progress - -- January carried over two legacy sponsors at roughly €2,800/month combined while the new packages were being finalized. -- The new tiered sponsorship packages launched in mid-February, generating two new sign-ups at the mid-tier (€1,200/month each) by month end. -- March brought one additional sponsor at the premium tier (€2,000/month), but a legacy sponsor churned, netting only +€800 for the month. -- Closed at €7,251 MRR -- about €750 short of the €8k target. - -## Notes - -- The new packaging structure is clearly an improvement over ad-hoc deals, but the sales cycle is longer than expected. Most sponsors need 3-4 weeks of back-and-forth before committing. -- [[person-luca-rossi]] noted that sponsors care more about audience quality (open rates, click-through) than raw subscriber count. This insight should inform how growth is messaged to potential sponsors. diff --git a/demo-vault-v2/target-revenue-24q2.md b/demo-vault-v2/target-revenue-24q2.md deleted file mode 100644 index 0e6a552b..00000000 --- a/demo-vault-v2/target-revenue-24q2.md +++ /dev/null @@ -1,25 +0,0 @@ ---- -aliases: ["Revenue Q2 2024"] -Is A: Target -Belongs to: "[[24q2]]" -Measure: "[[measure-sponsorship-mrr]]" -Goal value: 10000 -Actual value: 9914 -Status: Behind ---- -# Revenue Target Q2 2024 -Target: €10,000/month MRR by end of quarter. - -The €10k MRR target represented the first five-figure month, a psychological milestone for the business. The plan was to build on the new sponsorship packages launched in Q1 and begin outbound sales efforts. [[person-paco-furiani]] started helping with sponsor outreach on a part-time basis this quarter, which was expected to accelerate the pipeline. - -## Progress - -- April saw two new mid-tier sponsors close, pushing MRR to €8,900. The outbound approach was working -- both came from cold outreach by [[person-paco-furiani]]. -- May added one premium sponsor (€2,000/month) but lost a mid-tier sponsor who cited budget cuts, netting +€800 for the month. -- June was flat with minor upsells to existing sponsors adding roughly €200, bringing the total to €9,914. -- Missed the target by just €86 -- the closest near-miss of the year. - -## Notes - -- Churn is the silent killer. Gross new sales were actually ahead of plan, but losing one mid-tier sponsor in May erased most of the gains. Need to invest in sponsor retention and relationship management. -- [[person-paco-furiani]]'s outbound efforts are proving valuable. The ROI on his part-time involvement is clearly positive. diff --git a/demo-vault-v2/target-revenue-24q3.md b/demo-vault-v2/target-revenue-24q3.md deleted file mode 100644 index d5240290..00000000 --- a/demo-vault-v2/target-revenue-24q3.md +++ /dev/null @@ -1,25 +0,0 @@ ---- -aliases: ["Revenue Q3 2024"] -Is A: Target -Belongs to: "[[24q3]]" -Measure: "[[measure-sponsorship-mrr]]" -Goal value: 12000 -Actual value: 11156 -Status: Behind ---- -# Revenue Target Q3 2024 -Target: €12,000/month MRR by end of quarter. - -The €12k target required roughly €2k in net new MRR, which seemed achievable given the Q2 pipeline. However, this quarter coincided with summer seasonality, which historically affects B2B advertising budgets. The podcast revenue from [[24q3-podcast-season-2]] was expected to provide a secondary revenue stream, though podcast sponsorships were priced lower than newsletter placements. - -## Progress - -- July was soft as expected -- two sponsors paused for the summer, dropping MRR to €8,700 temporarily. One new annual deal partially offset the dip. -- August improved as paused sponsors resumed and a new premium sponsor signed a 6-month commitment, pushing MRR to €10,400. -- September brought podcast sponsorship revenue online for the first time (€800/month), but newsletter sponsor acquisition slowed as Q4 budget planning consumed potential buyers' attention. -- Closed at €11,156 MRR -- about €850 short of the €12k target. - -## Notes - -- Summer seasonality hit harder than anticipated. Future planning should assume a 10-15% MRR dip in July and price targets accordingly. -- Podcast sponsorships are a meaningful but modest revenue stream. At €800/month they contribute to diversification but will not be a primary growth driver. diff --git a/demo-vault-v2/target-revenue-24q4.md b/demo-vault-v2/target-revenue-24q4.md deleted file mode 100644 index 62c5d07b..00000000 --- a/demo-vault-v2/target-revenue-24q4.md +++ /dev/null @@ -1,25 +0,0 @@ ---- -aliases: ["Revenue Q4 2024"] -Is A: Target -Belongs to: "[[24q4]]" -Measure: "[[measure-sponsorship-mrr]]" -Goal value: 14000 -Actual value: 12722 -Status: Behind ---- -# Revenue Target Q4 2024 -Target: €14,000/month MRR by end of quarter. - -The €14k target was the final push toward the [[2024-double-revenue]] annual goal. Hitting it would have required roughly €2,800 in net new MRR -- a significant jump. The plan relied on Q4 being the strongest quarter for B2B ad spend (year-end budget flushes) and closing several deals that had been in the pipeline since September. - -## Progress - -- October was the best sales month of the year: three new sponsors closed (two mid-tier, one premium), adding €3,400 in gross MRR. However, one legacy sponsor at €1,200/month churned. -- November held steady with minor upsells and one new mid-tier sponsor, pushing MRR to €12,500. -- December saw the expected year-end slowdown in new deal closings, but no churn. A small price increase on renewals added €222 to the monthly total. -- Closed at €12,722 MRR -- well short of €14k but still roughly 75% higher than the year's starting point. - -## Notes - -- The [[2024-double-revenue]] goal was not achieved (ended at ~€12.7k vs. the implied ~€14k doubling target), but the growth trajectory was strong. The revenue engine is real and repeatable. -- Churn remains the biggest headwind. Gross revenue added in 2024 was actually sufficient to hit the target, but losses from churned sponsors ate into the gains. A formal retention process is needed for 2025. diff --git a/demo-vault-v2/target-revenue-25q1.md b/demo-vault-v2/target-revenue-25q1.md deleted file mode 100644 index 8501795b..00000000 --- a/demo-vault-v2/target-revenue-25q1.md +++ /dev/null @@ -1,25 +0,0 @@ ---- -aliases: ["Revenue Q1 2025"] -Is A: Target -Belongs to: "[[25q1]]" -Measure: "[[measure-sponsorship-mrr]]" -Goal value: 15000 -Actual value: 15569 -Status: Done ---- -# Revenue Target Q1 2025 -Target: €15,000/month MRR by end of quarter. - -The €15k target kicked off the [[2025-reach-22k-mrr]] annual goal with an ambitious but measured first step. Key changes this quarter included introducing a formal sponsor retention program (quarterly check-ins and performance reports), raising prices by 10-15% on new deals, and adding a new "data sponsorship" tier that gave sponsors access to anonymized audience survey data. - -## Progress - -- January started strong with zero churn for the first time -- the new retention program and proactive check-ins made an immediate difference. Two new mid-tier sponsors signed up. -- February saw the data sponsorship tier close its first two deals at premium pricing (€2,500/month each), significantly accelerating MRR growth. -- March brought one more premium deal and continued zero churn, pushing MRR comfortably past the target. -- Closed at €15,569 MRR -- exceeding the target by €569. - -## Notes - -- This was the first revenue target hit since the formalization of MRR tracking. The retention program is clearly working -- zero churn in a quarter is unprecedented. -- The data sponsorship tier is a significant innovation. Sponsors are willing to pay a meaningful premium for audience insights, and it differentiates the offering from commodity newsletter ads. diff --git a/demo-vault-v2/target-revenue-25q2.md b/demo-vault-v2/target-revenue-25q2.md deleted file mode 100644 index b071d3a4..00000000 --- a/demo-vault-v2/target-revenue-25q2.md +++ /dev/null @@ -1,25 +0,0 @@ ---- -aliases: ["Revenue Q2 2025"] -Is A: Target -Belongs to: "[[25q2]]" -Measure: "[[measure-sponsorship-mrr]]" -Goal value: 17000 -Actual value: 16928 -Status: Behind ---- -# Revenue Target Q2 2025 -Target: €17,000/month MRR by end of quarter. - -The €17k target continued the steady ramp toward [[2025-reach-22k-mrr]]. With the strong Q1 result and zero churn, there was optimism that the momentum would carry. However, this quarter also saw [[person-luca-rossi]] devoting significant time to [[25q2-laputa-v2]], which reduced capacity for direct sponsor sales. [[person-paco-furiani]] took on more of the outbound sales role to compensate. - -## Progress - -- April added two new mid-tier sponsors but lost one legacy sponsor who shifted their budget to podcast-only advertising, resulting in net +€800. -- May was slower than expected with only one new deal closing, but an existing sponsor upgraded from mid-tier to the data sponsorship tier, adding €1,000/month net. -- June closed one new premium deal but the MRR gain was partially offset by a seasonal pause from a sponsor who only runs campaigns during product launch periods. -- Ended at €16,928 -- just €72 short of target. - -## Notes - -- The pattern of near-misses continues, but the revenue trajectory remains healthy. The business is consistently adding €1,500-2,000 in net MRR per quarter. -- [[person-paco-furiani]]'s expanded role in sales is working well. He closed 60% of new deals this quarter, freeing [[person-luca-rossi]] to focus on product development. diff --git a/demo-vault-v2/target-revenue-25q3.md b/demo-vault-v2/target-revenue-25q3.md deleted file mode 100644 index 03786d19..00000000 --- a/demo-vault-v2/target-revenue-25q3.md +++ /dev/null @@ -1,25 +0,0 @@ ---- -aliases: ["Revenue Q3 2025"] -Is A: Target -Belongs to: "[[25q3]]" -Measure: "[[measure-sponsorship-mrr]]" -Goal value: 19000 -Actual value: "None" -Status: Open ---- -# Revenue Target Q3 2025 -Target: €19,000/month MRR by end of quarter. - -The €19k target requires approximately €2,100 in net new MRR, which is achievable but depends on keeping churn near zero. Summer seasonality remains a risk based on past experience. The plan includes launching a self-serve sponsorship booking tool to reduce sales friction and expanding the podcast sponsorship portfolio to capture more of the audio advertising budget that sponsors are increasingly allocating. - -## Progress - -- Quarter is currently in planning. The self-serve booking tool MVP is expected to go live in early July. -- Pipeline has three warm leads in the premium tier and two in the data sponsorship tier, representing roughly €4,000/month in potential gross MRR. -- [[person-paco-furiani]] is focused on converting pipeline deals before the August slowdown historically associated with summer. -- Contingency: if summer churn repeats the 2024 pattern, the team will offer 3-month commitment discounts to at-risk sponsors proactively. - -## Notes - -- The self-serve booking tool is a bet on reducing the sales cycle from weeks to days for smaller sponsors. If it works, it could meaningfully change the growth curve. -- Reaching €19k would put the business on track for the [[2025-reach-22k-mrr]] annual goal, with only €3k of growth needed in Q4. diff --git a/demo-vault-v2/target-revenue-25q4.md b/demo-vault-v2/target-revenue-25q4.md deleted file mode 100644 index e04cd532..00000000 --- a/demo-vault-v2/target-revenue-25q4.md +++ /dev/null @@ -1,25 +0,0 @@ ---- -aliases: ["Revenue Q4 2025"] -Is A: Target -Belongs to: "[[25q4]]" -Measure: "[[measure-sponsorship-mrr]]" -Goal value: 22000 -Actual value: "None" -Status: Open ---- -# Revenue Target Q4 2025 -Target: €22,000/month MRR by end of quarter. - -The €22k target is the culmination of the [[2025-reach-22k-mrr]] annual goal and would represent a roughly 73% increase from the ~€12.7k MRR at the start of 2025. Q4 is historically the strongest quarter for B2B advertising budgets, so this is strategically placed. The target also assumes the self-serve booking tool is fully operational and generating incremental small-sponsor revenue. - -## Progress - -- Quarter has not started yet. Strategy planning is in progress. -- Key assumptions: Q3 delivers at least €18k MRR (allowing a €4k gap to close in Q4), the self-serve tool generates at least €1,000/month from small sponsors, and Q4 budget flush behavior delivers 2-3 new premium deals. -- [[person-paco-furiani]] is building a target list of 20 potential premium sponsors to approach in September for Q4 commitments. -- If the Laputa app launches publicly, there may be an opportunity to bundle app sponsorship with newsletter sponsorship as a premium offering. - -## Notes - -- €22k MRR would make the newsletter business comfortably profitable as a standalone operation, even after accounting for [[person-paco-furiani]]'s compensation and other operational costs. -- This target is ambitious but not unreasonable given the trajectory. The biggest risk is a repeat of 2024's churn problem, which the retention program should mitigate. diff --git a/demo-vault-v2/target-subscribers-24q1.md b/demo-vault-v2/target-subscribers-24q1.md deleted file mode 100644 index 91c0fc2f..00000000 --- a/demo-vault-v2/target-subscribers-24q1.md +++ /dev/null @@ -1,25 +0,0 @@ ---- -aliases: ["Subscribers Q1 2024"] -Is A: Target -Belongs to: "[[24q1]]" -Measure: "[[measure-subscribers]]" -Goal value: 38000 -Actual value: 37428 -Status: Behind ---- -# Subscribers Target Q1 2024 -Target: 38,000 subscribers by end of quarter. - -This was the first quarter with a formalized subscriber growth target. After closing 2023 at roughly 34,000 subscribers, the 38k goal represented steady organic growth driven primarily by the weekly newsletter cadence and cross-promotion from the [[24q1-launch-sponsorship-packages]] work. The number was set conservatively to establish a baseline for the [[2024-reach-50k-subscribers]] annual goal. - -## Progress - -- January started slow with 34,800 subs; holiday period dampened new sign-ups and open rates dipped below 40%. -- A viral LinkedIn post in February brought roughly 1,200 new subscribers in a single week, temporarily putting the quarter ahead of pace. -- March saw higher-than-usual unsubscribes after a content pivot toward more technical deep-dives, netting only +400 for the month. -- Closed the quarter at 37,428 -- about 570 short of the 38k target. - -## Notes - -- The unsubscribe spike in March suggests the audience has a ceiling for purely technical content. Mixing in career and business angles likely retains broader appeal. -- Despite missing the number, the growth rate was still roughly 10% quarter-over-quarter, which [[person-luca-rossi]] considered acceptable for a first formal target. diff --git a/demo-vault-v2/target-subscribers-24q2.md b/demo-vault-v2/target-subscribers-24q2.md deleted file mode 100644 index f1d9562c..00000000 --- a/demo-vault-v2/target-subscribers-24q2.md +++ /dev/null @@ -1,25 +0,0 @@ ---- -aliases: ["Subscribers Q2 2024"] -Is A: Target -Belongs to: "[[24q2]]" -Measure: "[[measure-subscribers]]" -Goal value: 42000 -Actual value: 41701 -Status: Behind ---- -# Subscribers Target Q2 2024 -Target: 42,000 subscribers by end of quarter. - -Building on the Q1 miss, the 42k target assumed a rebound from the technical-content unsubscribe wave and factored in planned cross-promotions with two other indie newsletters. This quarter also coincided with the [[24q2-hire-editor]] project, which was expected to free up time for more promotional efforts and collaborations. - -## Progress - -- April saw strong growth of +1,400, partly driven by a guest post on a popular Substack that linked back to the sign-up page. -- May plateaued with only +800 net adds; the editor onboarding consumed more bandwidth than expected, reducing promotional activity. -- June recovered somewhat with +1,100 new subscribers thanks to a well-received deep dive on engineering manager compensation data. -- Final count landed at 41,701 -- just 299 short of target. - -## Notes - -- The near-miss was frustrating but showed that the growth engine is fundamentally sound. Consistency in publishing cadence matters more than any single viral hit. -- Cross-promotions yielded measurable but modest results (roughly 300-400 subs each). Worth continuing but not a primary lever. diff --git a/demo-vault-v2/target-subscribers-24q3.md b/demo-vault-v2/target-subscribers-24q3.md deleted file mode 100644 index 3b1fe232..00000000 --- a/demo-vault-v2/target-subscribers-24q3.md +++ /dev/null @@ -1,25 +0,0 @@ ---- -aliases: ["Subscribers Q3 2024"] -Is A: Target -Belongs to: "[[24q3]]" -Measure: "[[measure-subscribers]]" -Goal value: 47000 -Actual value: 47316 -Status: Done ---- -# Subscribers Target Q3 2024 -Target: 47,000 subscribers by end of quarter. - -The 47k target was the most ambitious quarterly jump yet, requiring roughly 5,300 net new subscribers. This coincided with [[24q3-podcast-season-2]] launching, which was expected to create a secondary acquisition channel. The broader [[2024-reach-50k-subscribers]] goal made this quarter critical -- missing it would put the annual target out of reach. - -## Progress - -- July kicked off strong with the podcast season 2 premiere driving 600 new subscribers in its first week alone from show-notes CTAs. -- August was the breakout month: a newsletter edition on "Why Senior Engineers Should Write" was shared widely on Hacker News, bringing in 2,100 new subscribers over 10 days. -- September maintained steady momentum with +1,500, supported by consistent podcast episodes and improved SEO on the archive pages. -- Closed at 47,316 -- exceeding the target by 316. - -## Notes - -- This was the first quarter the target was actually hit. The podcast proved to be a meaningful subscriber acquisition channel, validating the investment in [[24q1-podcast-season-1]]. -- The Hacker News spike showed that long-form, opinionated content outperforms how-to guides for viral growth. Worth leaning into this style more deliberately. diff --git a/demo-vault-v2/target-subscribers-24q4.md b/demo-vault-v2/target-subscribers-24q4.md deleted file mode 100644 index 2802de54..00000000 --- a/demo-vault-v2/target-subscribers-24q4.md +++ /dev/null @@ -1,25 +0,0 @@ ---- -aliases: ["Subscribers Q4 2024"] -Is A: Target -Belongs to: "[[24q4]]" -Measure: "[[measure-subscribers]]" -Goal value: 53000 -Actual value: 52265 -Status: Behind ---- -# Subscribers Target Q4 2024 -Target: 53,000 subscribers by end of quarter. - -The 53k target was set to push past the 50k milestone that underpinned the [[2024-reach-50k-subscribers]] annual goal. While aggressive, the momentum from Q3's strong finish and the ongoing podcast made it feel achievable. [[person-luca-rossi]] also planned a year-end "best of" series to drive re-shares. - -## Progress - -- October performed well with +1,800, carried by podcast momentum and a collaboration with a well-known engineering leader. -- November slowed to +1,200 as the pre-holiday period brought lower engagement across the board. Open rates dropped to 38%. -- December was the weakest month at +900 net adds. The "best of" series performed adequately but did not drive the viral sharing that was hoped for. -- Final count: 52,265 -- missed the 53k target by 735, but did clear the symbolic 50k mark in late November. - -## Notes - -- Passing 50,000 subscribers was a significant milestone even though the quarterly target was missed. It validated the annual goal trajectory set at the start of 2024. -- Q4 seasonality is real for B2B newsletter audiences. Future planning should bake in lower growth expectations for October-December. diff --git a/demo-vault-v2/target-subscribers-25q1.md b/demo-vault-v2/target-subscribers-25q1.md deleted file mode 100644 index b3c69677..00000000 --- a/demo-vault-v2/target-subscribers-25q1.md +++ /dev/null @@ -1,25 +0,0 @@ ---- -aliases: ["Subscribers Q1 2025"] -Is A: Target -Belongs to: "[[25q1]]" -Measure: "[[measure-subscribers]]" -Goal value: 59000 -Actual value: 58676 -Status: Behind ---- -# Subscribers Target Q1 2025 -Target: 59,000 subscribers by end of quarter. - -With the newsletter past 52k at the start of the year, the 59k target reflected the ambitious [[2025-reach-85k-subscribers]] annual goal. This required roughly 6,700 net new subscribers in one quarter -- a step up from previous quarters. The plan leaned heavily on improved onboarding sequences to reduce early churn and new content formats to broaden the audience. - -## Progress - -- January started strong with +2,400, driven by "new year" energy and a well-timed piece on 2025 engineering hiring trends. -- February maintained pace at +1,900 but churn crept up slightly as the new onboarding sequence was still being A/B tested. -- March delivered +1,600, falling slightly short of the monthly target needed to close the gap. A planned collaboration fell through at the last moment. -- Ended at 58,676 -- 324 short of the 59k goal. - -## Notes - -- The onboarding sequence improvements showed early promise: 7-day retention improved from 72% to 79%. The full impact should compound over subsequent quarters. -- Missing by such a narrow margin again is a pattern. [[person-luca-rossi]] decided to set targets with a small buffer going forward to account for late-quarter slowdowns. diff --git a/demo-vault-v2/target-subscribers-25q2.md b/demo-vault-v2/target-subscribers-25q2.md deleted file mode 100644 index feee1acc..00000000 --- a/demo-vault-v2/target-subscribers-25q2.md +++ /dev/null @@ -1,25 +0,0 @@ ---- -aliases: ["Subscribers Q2 2025"] -Is A: Target -Belongs to: "[[25q2]]" -Measure: "[[measure-subscribers]]" -Goal value: 66000 -Actual value: 66349 -Status: Done ---- -# Subscribers Target Q2 2025 -Target: 66,000 subscribers by end of quarter. - -The 66k target represented the steepest quarterly climb yet, requiring over 7,300 net adds. This coincided with the [[25q2-laputa-v2]] development phase, which meant less time for promotional content. To compensate, [[person-luca-rossi]] invested in a referral program and doubled down on SEO-optimized archive pages that had started generating meaningful organic traffic. - -## Progress - -- April was the strongest month in the newsletter's history: +3,100 subscribers, powered by a referral program launch that offered exclusive content for successful referrals. -- May maintained solid growth at +2,200 despite reduced publishing cadence (biweekly instead of weekly) due to Laputa development demands. -- June closed with +2,400 as the referral program reached steady state and several archive articles started ranking on the first page of Google for competitive search terms. -- Hit 66,349 -- exceeding the target by 349. - -## Notes - -- The referral program proved to be the single most effective growth lever introduced since the podcast. Roughly 30% of new subscribers in Q2 came through referrals. -- SEO is becoming a compounding asset. The archive pages now drive roughly 800 organic subscribers per month with zero ongoing effort. diff --git a/demo-vault-v2/target-subscribers-25q3.md b/demo-vault-v2/target-subscribers-25q3.md deleted file mode 100644 index 1f1f5168..00000000 --- a/demo-vault-v2/target-subscribers-25q3.md +++ /dev/null @@ -1,25 +0,0 @@ ---- -aliases: ["Subscribers Q3 2025"] -Is A: Target -Belongs to: "[[25q3]]" -Measure: "[[measure-subscribers]]" -Goal value: 75000 -Actual value: "None" -Status: Open ---- -# Subscribers Target Q3 2025 -Target: 75,000 subscribers by end of quarter. - -The 75k target is the most aggressive quarterly goal to date, requiring approximately 8,700 net new subscribers. The plan relies on the compounding effects of the referral program and SEO, supplemented by a planned podcast relaunch and a series of guest appearances on larger shows. This is the penultimate quarter for the [[2025-reach-85k-subscribers]] goal, so strong performance here is essential to keep the annual target within reach. - -## Progress - -- Quarter is currently in progress. Early indicators from July show the referral program continuing to perform well. -- Podcast relaunch is scheduled for mid-July with a new format that emphasizes shorter, more frequent episodes. -- Two guest appearances on top-50 tech podcasts are confirmed for August, which should provide significant exposure. -- SEO traffic continues to grow organically; projecting roughly 1,000 organic subscribers per month by end of quarter. - -## Notes - -- This quarter's outcome will largely determine whether the 85k annual goal is achievable. A miss here would require extraordinary Q4 performance to compensate. -- [[person-matteo-cellini]] is supporting promotional efforts this quarter, allowing [[person-luca-rossi]] to focus more on Laputa development without sacrificing growth. diff --git a/demo-vault-v2/target-subscribers-25q4.md b/demo-vault-v2/target-subscribers-25q4.md deleted file mode 100644 index d752adff..00000000 --- a/demo-vault-v2/target-subscribers-25q4.md +++ /dev/null @@ -1,25 +0,0 @@ ---- -aliases: ["Subscribers Q4 2025"] -Is A: Target -Belongs to: "[[25q4]]" -Measure: "[[measure-subscribers]]" -Goal value: 85000 -Actual value: "None" -Status: Open ---- -# Subscribers Target Q4 2025 -Target: 85,000 subscribers by end of quarter. - -The 85k target is the capstone of the [[2025-reach-85k-subscribers]] annual goal. Hitting this number would represent roughly a 63% year-over-year increase from the ~52k starting point at the beginning of 2025. The target assumes continued compounding from the referral program, SEO, and podcast channels, plus a potential boost from the public launch of [[25q1-laputa-v1]] driving brand awareness. - -## Progress - -- Quarter has not started yet. Planning is underway. -- The growth model projects needing approximately 10,000 net adds, which would be the highest single-quarter gain ever. -- Key initiatives being considered include a paid acquisition experiment (first time), a major content partnership, and leveraging the Laputa app launch for cross-promotion. -- Contingency planning includes adjusting the target downward to 80k if Q3 underperforms significantly. - -## Notes - -- This target may need revision depending on Q3 results. [[person-luca-rossi]] has committed to a mid-year review in August to assess whether 85k remains realistic. -- Even if the exact number is missed, reaching 80k+ would still represent exceptional growth and position the newsletter for a strong 2026. diff --git a/demo-vault-v2/target.md b/demo-vault-v2/target.md deleted file mode 100644 index 9ee518d9..00000000 --- a/demo-vault-v2/target.md +++ /dev/null @@ -1,7 +0,0 @@ ---- -Is A: Type ---- - -# Target - -A Target is a specific numeric goal within a Measure — the number you are aiming for by a given date. Targets make accountability concrete. diff --git a/demo-vault-v2/task-24q1-01.md b/demo-vault-v2/task-24q1-01.md deleted file mode 100644 index da2f2cf0..00000000 --- a/demo-vault-v2/task-24q1-01.md +++ /dev/null @@ -1,26 +0,0 @@ ---- -aliases: ["Write Q24Q1 retrospective"] -Is A: Task -Belongs to: "[[24q1]]" -Status: Done -Owner: "[[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 - -- [x] Pull final metrics for all four tracked measures and record actual values -- [x] Write narrative summary for each goal area (subscribers, revenue, books, health) -- [x] Identify top 3 learnings and top 3 action items for Q2 -- [x] Share condensed summary with [[person-paco-furiani]] and [[person-sara-ricci]] -- [x] 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. diff --git a/demo-vault-v2/task-24q1-02.md b/demo-vault-v2/task-24q1-02.md deleted file mode 100644 index c225a9af..00000000 --- a/demo-vault-v2/task-24q1-02.md +++ /dev/null @@ -1,26 +0,0 @@ ---- -aliases: ["Update website About page"] -Is A: Task -Belongs to: "[[24q1]]" -Status: Done -Owner: "[[person-luca-rossi]]" ---- -# Update website About page - -The newsletter website's About page had not been updated since mid-2023 and still reflected an earlier positioning focused purely on engineering management. With the content expanding to cover indie hacking, content business, and broader engineering leadership, the About page needed a rewrite to accurately represent what subscribers would get. - -This task also involved updating the headshot photo, refreshing the social proof section with current subscriber count and notable sponsor logos, and ensuring the page loads quickly on mobile. The updated page is a key part of the conversion funnel -- many new visitors land on the About page before deciding to subscribe. - -## Acceptance criteria - -- [x] Rewrite the bio section to reflect current content scope (engineering leadership + indie hacking) -- [x] Update subscriber count and social proof logos -- [x] Replace headshot with current photo -- [x] Test page load speed on mobile (target < 2s) -- [x] Get feedback from [[person-sara-ricci]] on the new copy before publishing - -## Notes - -- The updated About page improved the subscribe conversion rate from roughly 8% to 11% based on the following month's analytics. A meaningful lift. -- [[person-sara-ricci]] suggested adding a "What readers say" section with testimonial quotes, which was added as a follow-up task in [[24q2]]. -- Related to the broader [[24q1-launch-sponsorship-packages]] project, since sponsors also reference the About page during evaluation. diff --git a/demo-vault-v2/task-24q1-03.md b/demo-vault-v2/task-24q1-03.md deleted file mode 100644 index 6c410c8f..00000000 --- a/demo-vault-v2/task-24q1-03.md +++ /dev/null @@ -1,26 +0,0 @@ ---- -aliases: ["Fix broken links in newsletter archive"] -Is A: Task -Belongs to: "[[24q1]]" -Status: Done -Owner: "[[person-luca-rossi]]" ---- -# Fix broken links in newsletter archive - -An audit of the newsletter archive revealed 47 broken links across roughly 120 published editions. Most were caused by external sites changing their URL structure, a few were internal links to pages that had been reorganized. Broken links hurt SEO, degrade the reader experience for anyone browsing older editions, and reflect poorly on the brand when sponsors evaluate the archive. - -The task involved running a link-checking tool across the entire archive, categorizing the broken links (external vs. internal, fixable vs. permanently dead), and either updating the links or adding appropriate redirects. For permanently dead external links, the approach was to link to the Wayback Machine archive or replace with an equivalent current resource. - -## Acceptance criteria - -- [x] Run link checker across all 120+ archive pages -- [x] Categorize broken links by type (external dead, external moved, internal broken) -- [x] Fix or replace all 47 identified broken links -- [x] Set up a monthly automated link check using a scheduled script -- [x] Verify no new broken links introduced by the fixes - -## Notes - -- The automated monthly link check was set up using a cron job and a simple Python script. It sends a Slack notification when new broken links are detected. See [[procedure-link-audit]] for details. -- Several broken links pointed to Medium articles that had been paywalled. These were replaced with direct links to the authors' personal sites where available. -- This was more tedious than expected but necessary. Archive SEO value depends on link health. diff --git a/demo-vault-v2/task-24q2-04.md b/demo-vault-v2/task-24q2-04.md deleted file mode 100644 index ade6bf22..00000000 --- a/demo-vault-v2/task-24q2-04.md +++ /dev/null @@ -1,26 +0,0 @@ ---- -aliases: ["Set up new analytics dashboard"] -Is A: Task -Belongs to: "[[24q2]]" -Status: Done -Owner: "[[person-luca-rossi]]" ---- -# Set up new analytics dashboard - -The existing analytics setup was fragmented across multiple tools -- Substack's built-in analytics for email metrics, Google Analytics for the website, and manual spreadsheets for sponsor tracking. This task consolidated everything into a single dashboard that provides a unified view of the key metrics: [[measure-subscribers]], [[measure-sponsorship-mrr]], [[measure-podcast-downloads]], and engagement metrics (open rate, click-through rate). - -The dashboard was built using a combination of Google Sheets (for data aggregation) and a simple Retool dashboard for visualization. The goal was a single URL that [[person-luca-rossi]] and [[person-paco-furiani]] could check daily without needing to log into multiple tools. - -## Acceptance criteria - -- [x] Consolidate subscriber, revenue, and engagement data into a single data source -- [x] Build dashboard with daily/weekly/monthly views for all key metrics -- [x] Set up automated data pulls from Substack API and Google Analytics -- [x] Add sponsor pipeline tracking (leads, proposals sent, contracts signed) -- [x] Share dashboard access with [[person-paco-furiani]] - -## Notes - -- The Retool dashboard took longer to set up than expected (about 3 days instead of the planned 1 day), but the ongoing time savings are substantial. Checking metrics went from a 20-minute multi-tool process to a 2-minute glance. -- Discovered that Substack's API has rate limits that required batching data pulls overnight. The sync runs at 3am CET. -- This dashboard became the source of truth for all quarterly target tracking going forward. diff --git a/demo-vault-v2/task-24q2-05.md b/demo-vault-v2/task-24q2-05.md deleted file mode 100644 index b18f4258..00000000 --- a/demo-vault-v2/task-24q2-05.md +++ /dev/null @@ -1,26 +0,0 @@ ---- -aliases: ["Create sponsor media kit PDF"] -Is A: Task -Belongs to: "[[24q2]]" -Status: Done -Owner: "[[person-luca-rossi]]" ---- -# Create sponsor media kit PDF - -Sponsor prospects consistently asked for a one-pager that summarized audience demographics, engagement metrics, pricing tiers, and past sponsor results. Previously, this information was sent piecemeal via email, which was slow and inconsistent. This task created a professionally designed media kit PDF that could be sent as the standard first touchpoint in the sponsor sales process. - -The media kit needed to feel premium but not overly corporate -- matching the newsletter's brand voice of "senior engineer who knows what they are talking about." [[person-paco-furiani]] provided input on what sponsor prospects most frequently asked about during sales conversations, which shaped the content priorities. - -## Acceptance criteria - -- [x] Design a 4-page media kit covering audience profile, engagement stats, pricing, and case studies -- [x] Include current subscriber count, open rate, click-through rate, and audience demographics -- [x] Add testimonial quotes from 2-3 existing sponsors -- [x] Create editable template (Figma) so it can be updated quarterly with fresh stats -- [x] Get approval from [[person-paco-furiani]] before distributing to prospects - -## Notes - -- The media kit increased sponsor conversion rate on cold outreach from roughly 5% to 12%, making it the single most impactful sales tool created in 2024. -- The Figma template approach was key -- [[person-paco-furiani]] can update the numbers each quarter without needing design help. -- Related to [[24q1-launch-sponsorship-packages]] as part of the broader professionalization of the sponsor sales process. diff --git a/demo-vault-v2/task-24q2-06.md b/demo-vault-v2/task-24q2-06.md deleted file mode 100644 index 186e0477..00000000 --- a/demo-vault-v2/task-24q2-06.md +++ /dev/null @@ -1,26 +0,0 @@ ---- -aliases: ["Update editorial guidelines for Sara"] -Is A: Task -Belongs to: "[[24q2]]" -Status: Done -Owner: "[[person-luca-rossi]]" ---- -# Update editorial guidelines for Sara - -With [[person-sara-ricci]] joining as editor through the [[24q2-hire-editor]] project, the existing informal editorial guidelines needed to be formalized into a comprehensive document. Sara needed clear guidance on tone, style, content structure, and the editorial review process so she could edit independently without constant back-and-forth with [[person-luca-rossi]]. - -The guidelines cover everything from headline formatting conventions and paragraph length preferences to the handling of code snippets, the voice for different content types (deep dives vs. opinion pieces vs. interviews), and the approval workflow. The document also includes a "red lines" section covering topics and framings to avoid. - -## Acceptance criteria - -- [x] Document the newsletter's voice and tone with concrete examples -- [x] Define the editorial workflow (draft -> edit -> review -> publish) -- [x] Create a style guide covering formatting, code blocks, image usage, and link conventions -- [x] Include a section on content types and their distinct editorial requirements -- [x] Review the guidelines with [[person-sara-ricci]] and incorporate her feedback - -## Notes - -- Sara's feedback significantly improved the guidelines. She flagged several areas where the implicit rules in Luca's head were inconsistent or contradictory, which helped clarify the actual editorial standards. -- The guidelines document is maintained in the vault as [[procedure-editorial-guidelines]] and is updated whenever a new editorial decision sets a precedent. -- This investment paid off immediately -- Sara's first independent edit required only minor revisions, compared to the extensive back-and-forth expected without guidelines. diff --git a/demo-vault-v2/task-24q2-07.md b/demo-vault-v2/task-24q2-07.md deleted file mode 100644 index 0cdc9ab5..00000000 --- a/demo-vault-v2/task-24q2-07.md +++ /dev/null @@ -1,26 +0,0 @@ ---- -aliases: ["Research gran fondo training plans"] -Is A: Task -Belongs to: "[[24q2]]" -Status: Done -Owner: "[[person-luca-rossi]]" ---- -# Research gran fondo training plans - -With the cycling cross-training habit established in Q1 and the [[measure-resting-hr]] targets motivating more structured fitness, [[person-luca-rossi]] considered signing up for a gran fondo (long-distance cycling event) as a fitness goal for late 2024. This task involved researching available events in Italy, evaluating different training plan structures, and deciding whether to commit. - -The research covered 12-week and 16-week training plans from various coaching methodologies, equipment requirements (the current road bike is adequate for events up to 120km), and the time commitment involved. The key constraint was that training could not significantly interfere with newsletter production or the business workload. - -## Acceptance criteria - -- [x] Identify 3-5 gran fondo events in Italy between September and November 2024 -- [x] Compare at least 3 training plan methodologies (time-based, power-based, heart rate-based) -- [x] Assess weekly time commitment for each plan and flag conflicts with work schedule -- [x] Make go/no-go decision and document reasoning -- [x] If go, select the event and training plan - -## Notes - -- Decision: deferred to 2025. The time commitment for a proper gran fondo training plan (8-12 hours/week at peak) was incompatible with the Q3/Q4 business priorities. Opted to continue casual cycling as cross-training instead. -- The research was not wasted -- the heart rate-based training approach informed the running plan that led to hitting the Q4 2024 resting HR target. -- [[person-sara-ricci]] recommended a specific coach who specializes in time-constrained athletes. Filed for future reference. diff --git a/demo-vault-v2/task-24q3-08.md b/demo-vault-v2/task-24q3-08.md deleted file mode 100644 index 3bdd465f..00000000 --- a/demo-vault-v2/task-24q3-08.md +++ /dev/null @@ -1,26 +0,0 @@ ---- -aliases: ["Write podcast pitch template"] -Is A: Task -Belongs to: "[[24q3]]" -Status: Done -Owner: "[[person-luca-rossi]]" ---- -# Write podcast pitch template - -With [[24q3-podcast-season-2]] underway, the guest booking process needed to scale. Previously, each guest invitation was a bespoke email written from scratch, which was time-consuming and inconsistent. This task created a modular pitch template that could be customized for different guest types (engineering leaders, indie founders, authors) while maintaining the podcast's professional tone. - -The template needed to clearly communicate the podcast's value proposition to potential guests: audience size, listener demographics, episode format, and what the guest could expect in terms of preparation and time commitment. It also needed to address common objections (time, promotional value) and include social proof from previous guests. - -## Acceptance criteria - -- [x] Create a base pitch template with customizable sections for guest type -- [x] Include podcast stats (downloads per episode, audience demographics, notable past guests) -- [x] Write 3 variants: one for engineering VPs, one for indie founders, one for authors -- [x] Add a follow-up sequence template (initial pitch, nudge after 5 days, final follow-up) -- [x] Test with 5 outreach emails and measure response rate - -## Notes - -- The template achieved a 40% response rate in the first batch of 5 outreach emails (2 accepted, 0 declined, 3 no response). This was significantly better than the previous ad-hoc approach (~20% response rate). -- The indie founder variant performed best -- founders are generally more responsive to podcast invitations than executives at larger companies. -- Template is stored as [[procedure-podcast-guest-pitch]] for ongoing use. diff --git a/demo-vault-v2/task-24q3-09.md b/demo-vault-v2/task-24q3-09.md deleted file mode 100644 index 97994c76..00000000 --- a/demo-vault-v2/task-24q3-09.md +++ /dev/null @@ -1,26 +0,0 @@ ---- -aliases: ["Review and update pricing page"] -Is A: Task -Belongs to: "[[24q3]]" -Status: Done -Owner: "[[person-luca-rossi]]" ---- -# Review and update pricing page - -The sponsorship pricing page had been static since the [[24q1-launch-sponsorship-packages]] project. With six months of data on sponsor engagement and conversion rates, it was time to update the pricing to reflect the newsletter's increased value (higher subscriber count, better open rates, proven sponsor ROI). This task also involved restructuring the page to better highlight the data sponsorship tier that was being piloted. - -The pricing update needed to balance maximizing revenue per sponsor with maintaining competitive positioning against other engineering newsletters in the market. [[person-paco-furiani]] conducted informal competitive research, reaching out to contacts at similar newsletters to benchmark pricing ranges. - -## Acceptance criteria - -- [x] Audit current pricing against competitive benchmarks from 5+ comparable newsletters -- [x] Propose updated pricing tiers with rationale for each change -- [x] Redesign the pricing page layout to feature the data sponsorship tier more prominently -- [x] Add an ROI calculator or "what you get" section to justify pricing -- [x] Update the media kit PDF to reflect new pricing - -## Notes - -- Prices were increased by roughly 15% across all tiers. No existing sponsors complained during renewal conversations, suggesting the previous pricing may have been too low. -- The ROI calculator section proved effective -- prospects who engaged with it converted at nearly 2x the rate of those who did not. -- [[person-paco-furiani]] found that the newsletter's pricing was in the lower quartile compared to peers with similar audience sizes. Room for further increases in 2025. diff --git a/demo-vault-v2/task-24q3-10.md b/demo-vault-v2/task-24q3-10.md deleted file mode 100644 index 5e6651cd..00000000 --- a/demo-vault-v2/task-24q3-10.md +++ /dev/null @@ -1,26 +0,0 @@ ---- -aliases: ["Archive Q2 sponsor contracts"] -Is A: Task -Belongs to: "[[24q3]]" -Status: Done -Owner: "[[person-luca-rossi]]" ---- -# Archive Q2 sponsor contracts - -End-of-quarter housekeeping task to properly archive all sponsor contracts from [[24q2]], ensuring financial records are complete and accessible for year-end accounting. This includes both active contracts that renewed into Q3 and expired contracts that were not renewed. All contracts need to be filed in the standard folder structure with consistent naming. - -This task also involves reconciling the actual payments received against the contracted amounts, flagging any discrepancies for follow-up. [[person-paco-furiani]] handles the initial organization while [[person-luca-rossi]] does the final review and reconciliation. - -## Acceptance criteria - -- [x] Collect all Q2 sponsor contracts (new, renewed, and expired) into the archive folder -- [x] Apply standard naming convention: `YYYY-QN-SponsorName-Tier.pdf` -- [x] Reconcile contracted amounts against actual payments received -- [x] Flag and resolve any payment discrepancies -- [x] Update the sponsor tracking spreadsheet with final Q2 figures - -## Notes - -- Found one discrepancy: a mid-tier sponsor had been invoiced at the old rate rather than the new rate after their contract renewal. The difference was only €200 but was corrected going forward. -- This process took about 2 hours. Established [[procedure-sponsor-archive]] to make it faster in future quarters. -- All Q2 contracts are now archived and linked to [[24q2]] for reference. diff --git a/demo-vault-v2/task-24q3-11.md b/demo-vault-v2/task-24q3-11.md deleted file mode 100644 index e449b636..00000000 --- a/demo-vault-v2/task-24q3-11.md +++ /dev/null @@ -1,26 +0,0 @@ ---- -aliases: ["Create onboarding checklist for new subscribers"] -Is A: Task -Belongs to: "[[24q3]]" -Status: Done -Owner: "[[person-luca-rossi]]" ---- -# Create onboarding checklist for new subscribers - -New subscriber retention was identified as a key lever during the [[24q3]] planning. Data showed that subscribers who engaged with at least 3 emails in their first 2 weeks had a 90% chance of remaining subscribed after 90 days, while those who opened fewer than 2 had a 45% churn rate within the same period. This task created an onboarding sequence designed to maximize early engagement. - -The onboarding checklist defines the sequence of touchpoints a new subscriber receives: welcome email, curated "best of" digest, community invitation, and a personal note from [[person-luca-rossi]]. Each touchpoint was designed to deliver immediate value and build the habit of opening the newsletter. - -## Acceptance criteria - -- [x] Map the ideal first-14-days subscriber journey with specific touchpoints -- [x] Write copy for each onboarding email (welcome, best-of digest, community invite, personal note) -- [x] Set up automated triggers in the email platform for each touchpoint -- [x] Define success metrics (14-day open rate, 30-day retention rate) -- [x] A/B test the sequence against the previous single welcome email - -## Notes - -- The A/B test results were striking: the new onboarding sequence improved 30-day retention from 68% to 79%. This is one of the highest-ROI projects of the year. -- The personal note from [[person-luca-rossi]] was the most-opened email in the sequence (62% open rate), suggesting that personal connection matters more than curated content for early engagement. -- The onboarding flow is documented in [[procedure-subscriber-onboarding]] and was refined further in [[25q1]]. diff --git a/demo-vault-v2/task-24q4-12.md b/demo-vault-v2/task-24q4-12.md deleted file mode 100644 index d9a5ac52..00000000 --- a/demo-vault-v2/task-24q4-12.md +++ /dev/null @@ -1,26 +0,0 @@ ---- -aliases: ["Set up automated welcome sequence"] -Is A: Task -Belongs to: "[[24q4]]" -Status: Done -Owner: "[[person-luca-rossi]]" ---- -# Set up automated welcome sequence - -Building on the onboarding checklist created in [[24q3]], this task implemented the full automated welcome sequence in the email platform. The previous version required manual triggering for some steps; this task made the entire 14-day sequence fully automated, including conditional logic (e.g., skip the "best of" digest if the subscriber already opened 3+ regular editions). - -The automation also included tagging logic to segment new subscribers by acquisition source (organic, referral, podcast, cross-promotion) so that future analysis could identify which channels produce the most engaged subscribers. - -## Acceptance criteria - -- [x] Implement the full 14-day welcome sequence as automated workflows -- [x] Add conditional branching based on subscriber engagement signals -- [x] Set up source-based tagging for all new subscriber acquisition channels -- [x] Test the complete flow with test accounts for each branch -- [x] Monitor the first 500 subscribers through the automated sequence and verify no errors - -## Notes - -- The conditional branching reduced email fatigue -- subscribers who were already highly engaged did not receive redundant touchpoints, keeping the experience feeling personal rather than automated. -- Source-based tagging revealed that podcast-sourced subscribers had the highest 90-day retention (88%) followed by organic (82%) and referral (78%). This data informed channel investment decisions for [[25q1]]. -- Related to [[procedure-subscriber-onboarding]] which was updated to reflect the automated workflow. diff --git a/demo-vault-v2/task-24q4-13.md b/demo-vault-v2/task-24q4-13.md deleted file mode 100644 index 6b543aa1..00000000 --- a/demo-vault-v2/task-24q4-13.md +++ /dev/null @@ -1,26 +0,0 @@ ---- -aliases: ["Prepare Q4 sponsor renewal emails"] -Is A: Task -Belongs to: "[[24q4]]" -Status: Done -Owner: "[[person-luca-rossi]]" ---- -# Prepare Q4 sponsor renewal emails - -Q4 is renewal season for most annual sponsor contracts. This task prepared personalized renewal emails for each sponsor whose contract was expiring at year-end, including their individual performance data (impressions, clicks, conversions where trackable) and a proposed renewal package. The goal was to retain at least 80% of expiring sponsors and upsell where possible. - -[[person-paco-furiani]] drafted the initial emails while [[person-luca-rossi]] reviewed and personalized each one. The renewal emails needed to go out by mid-November to give sponsors time to process through their internal budget approval cycles before the December budget freeze. - -## Acceptance criteria - -- [x] Pull individual performance reports for each expiring sponsor -- [x] Draft personalized renewal emails with performance data and proposed package -- [x] Include upsell options (data tier, podcast bundle) where appropriate -- [x] Send all renewal emails by November 15 -- [x] Track responses and follow up within 5 business days of no response - -## Notes - -- Retention result: 7 out of 9 expiring sponsors renewed (78%), just under the 80% target. The two that churned cited internal budget cuts rather than dissatisfaction. -- Three sponsors accepted upsell offers, adding approximately €1,800/month in net MRR. The personalized performance data was cited as a key factor in their decision. -- [[person-paco-furiani]] handled the follow-up sequence effectively. The process is now documented in [[procedure-sponsor-renewal]]. diff --git a/demo-vault-v2/task-24q4-14.md b/demo-vault-v2/task-24q4-14.md deleted file mode 100644 index 48e9c03a..00000000 --- a/demo-vault-v2/task-24q4-14.md +++ /dev/null @@ -1,26 +0,0 @@ ---- -aliases: ["Write 2024 annual review post"] -Is A: Task -Belongs to: "[[24q4]]" -Status: Done -Owner: "[[person-luca-rossi]]" ---- -# Write 2024 annual review post - -The annual review post is one of the newsletter's highest-performing content pieces, combining transparent business metrics with personal reflections on the year. This tradition started informally in 2023 and was formalized for 2024 as a comprehensive piece covering growth metrics, revenue progression, key decisions, failures, and plans for 2025. - -The post serves multiple purposes: it builds trust with the audience through transparency, attracts new subscribers who discover it via social sharing, provides accountability for the business goals, and serves as a reference document for future planning. It typically takes 2-3 full days to write, edit, and design. - -## Acceptance criteria - -- [x] Compile final 2024 metrics across all tracked dimensions -- [x] Write narrative covering key decisions, wins, and failures of the year -- [x] Include specific revenue and subscriber numbers (full transparency) -- [x] Add forward-looking section outlining 2025 goals ([[2025-reach-22k-mrr]], [[2025-reach-85k-subscribers]], [[2025-ship-laputa]]) -- [x] Have [[person-sara-ricci]] edit the draft before publication - -## Notes - -- The 2024 annual review was the most-shared newsletter edition of the year, generating roughly 1,400 new subscribers in the week following publication. Transparency content consistently outperforms everything else. -- Reader feedback was overwhelmingly positive, with many citing the revenue transparency as refreshing and rare in the tech newsletter space. -- The post is archived and linked to both [[24q4]] and the [[2024-double-revenue]] goal retrospective. diff --git a/demo-vault-v2/task-24q4-15.md b/demo-vault-v2/task-24q4-15.md deleted file mode 100644 index 04549891..00000000 --- a/demo-vault-v2/task-24q4-15.md +++ /dev/null @@ -1,26 +0,0 @@ ---- -aliases: ["Update team role descriptions"] -Is A: Task -Belongs to: "[[24q4]]" -Status: Done -Owner: "[[person-luca-rossi]]" ---- -# Update team role descriptions - -As the team expanded from a solo operation to include [[person-sara-ricci]] (editor), [[person-paco-furiani]] (sponsor sales), and occasional contributions from [[person-matteo-cellini]] (technical consulting), the informal role definitions needed to be documented. This task created clear role descriptions for each team member, including responsibilities, decision-making authority, and communication expectations. - -The role descriptions serve as the basis for compensation reviews, goal-setting, and conflict resolution. They also help when onboarding any future team members by establishing the organizational structure clearly. - -## Acceptance criteria - -- [x] Write role descriptions for all current team members (Luca, Sara, Paco, Matteo) -- [x] Define responsibilities, decision-making authority, and reporting lines for each role -- [x] Specify communication norms (async by default, weekly sync, response time expectations) -- [x] Review role descriptions with each team member and incorporate feedback -- [x] Store in the vault as a referenceable document - -## Notes - -- The most valuable outcome was clarifying decision-making authority. Previously, [[person-paco-furiani]] and [[person-sara-ricci]] would defer to [[person-luca-rossi]] on decisions they were fully empowered to make independently, creating unnecessary bottlenecks. -- [[person-matteo-cellini]]'s role was formalized as a quarterly advisory engagement (4 hours/month) focused on technical architecture decisions for Laputa. -- Role descriptions are stored in [[procedure-team-roles]] and will be reviewed annually. diff --git a/demo-vault-v2/task-24q4-16.md b/demo-vault-v2/task-24q4-16.md deleted file mode 100644 index 4d41bb9e..00000000 --- a/demo-vault-v2/task-24q4-16.md +++ /dev/null @@ -1,26 +0,0 @@ ---- -aliases: ["Create content library for repurposing"] -Is A: Task -Belongs to: "[[24q4]]" -Status: Done -Owner: "[[person-luca-rossi]]" ---- -# Create content library for repurposing - -After publishing over 100 newsletter editions, there was a substantial backlog of content that could be repurposed across channels: podcast show notes, social media posts, LinkedIn articles, and eventually an e-book. This task created an organized content library tagging each edition by topic, performance metrics, and repurposing potential. - -The library enables [[person-sara-ricci]] to independently identify high-performing past content and adapt it for other channels without needing [[person-luca-rossi]] to remember which editions worked well. It also supports the long-term goal of compiling the best content into an e-book on engineering leadership. - -## Acceptance criteria - -- [x] Catalog all 100+ newsletter editions with topic tags, publication date, and performance metrics -- [x] Rate each edition's repurposing potential (high/medium/low) based on evergreen relevance -- [x] Create a "repurposing pipeline" board showing what has been repurposed and what is queued -- [x] Identify top 20 editions suitable for e-book compilation -- [x] Train [[person-sara-ricci]] on how to use the content library for social media content - -## Notes - -- The content library identified 23 editions rated as "high repurposing potential." Of these, 8 were already being referenced in podcast episodes but 15 had never been repurposed in any form -- a significant untapped opportunity. -- [[person-sara-ricci]] immediately started using the library to create a 3x/week LinkedIn posting schedule from repurposed content, saving roughly 5 hours/week of original writing. -- The top-20 e-book list became the foundation for the [[25q2]] e-book outline task. diff --git a/demo-vault-v2/task-25q1-17.md b/demo-vault-v2/task-25q1-17.md deleted file mode 100644 index dbd00508..00000000 --- a/demo-vault-v2/task-25q1-17.md +++ /dev/null @@ -1,26 +0,0 @@ ---- -aliases: ["Set up new Airtable base for 2025 sponsors"] -Is A: Task -Belongs to: "[[25q1]]" -Status: Done -Owner: "[[person-luca-rossi]]" ---- -# Set up new Airtable base for 2025 sponsors - -The 2024 sponsor tracking lived in a combination of Google Sheets and email threads, which became increasingly unwieldy as the sponsor roster grew past 10 active accounts. For 2025, the decision was made to migrate sponsor relationship management to Airtable, which provides better views, filtering, and automation capabilities without the overhead of a full CRM. - -The Airtable base needed to track the full sponsor lifecycle: lead, outreach, proposal, negotiation, contract, active, renewal, and churned. [[person-paco-furiani]] would be the primary user, so his workflow needs shaped the design. The base also needed to integrate with the analytics dashboard created in [[24q2]] to pull in sponsor performance data automatically. - -## Acceptance criteria - -- [x] Design the Airtable base schema with tables for sponsors, contracts, payments, and communications -- [x] Migrate all active 2025 sponsor data from the existing Google Sheets -- [x] Set up views for [[person-paco-furiani]]: pipeline board, renewal calendar, payment tracker -- [x] Create automations for contract expiry reminders (30 days and 7 days before) -- [x] Train [[person-paco-furiani]] on the new system - -## Notes - -- The migration took about a full day, but [[person-paco-furiani]] reported immediately that the pipeline board view alone saved him 30 minutes per day compared to the spreadsheet. -- The automated expiry reminders prevented a near-miss in March where a renewal conversation would have started too late without the 30-day alert. -- Connected to the broader [[2025-reach-22k-mrr]] goal by improving the operational efficiency of sponsor management. diff --git a/demo-vault-v2/task-25q1-18.md b/demo-vault-v2/task-25q1-18.md deleted file mode 100644 index 0ed45dd3..00000000 --- a/demo-vault-v2/task-25q1-18.md +++ /dev/null @@ -1,26 +0,0 @@ ---- -aliases: ["Review and update newsletter footer"] -Is A: Task -Belongs to: "[[25q1]]" -Status: Done -Owner: "[[person-luca-rossi]]" ---- -# Review and update newsletter footer - -The newsletter footer is seen by every subscriber on every edition but had not been updated in over a year. It still referenced outdated social links, a subscriber count from mid-2023, and lacked a referral program CTA. Given that the referral program was launching in [[25q2]], the footer needed to be updated to include a referral link, refreshed social links, and updated branding. - -This small task had outsized impact potential because the footer is the most consistently viewed element across all newsletter editions. Even a modest improvement in click-through on the referral link could compound significantly over thousands of subscribers. - -## Acceptance criteria - -- [x] Update social media links (add LinkedIn, remove inactive Twitter/X account) -- [x] Add a referral program teaser with placeholder link (to be activated when program launches) -- [x] Refresh the subscriber count and "about" blurb -- [x] Ensure the footer renders correctly across email clients (Gmail, Apple Mail, Outlook) -- [x] A/B test the new footer against the old one for 2 weeks - -## Notes - -- The A/B test showed the new footer generated 3x more clicks on the social links and a notable increase in profile visits on LinkedIn. The old footer was essentially invisible to readers. -- The referral program placeholder generated curiosity -- several subscribers replied to ask what was coming, which provided a natural launch announcement audience. -- Cross-client rendering required fixing a padding issue in Outlook that collapsed the footer layout. Documented the fix in [[procedure-newsletter-template]]. diff --git a/demo-vault-v2/task-25q1-19.md b/demo-vault-v2/task-25q1-19.md deleted file mode 100644 index 12cb5bb1..00000000 --- a/demo-vault-v2/task-25q1-19.md +++ /dev/null @@ -1,26 +0,0 @@ ---- -aliases: ["Write referral program landing page copy"] -Is A: Task -Belongs to: "[[25q1]]" -Status: Done -Owner: "[[person-luca-rossi]]" ---- -# Write referral program landing page copy - -The referral program, planned for full launch in [[25q2]], needed a dedicated landing page that explained the program mechanics, showcased the rewards, and made it effortless for subscribers to share. This task focused on writing the copy and designing the page structure. The actual technical implementation (unique referral links, reward tracking) was handled separately. - -The copy needed to motivate sharing without feeling pushy. The tone should match the newsletter's voice: straightforward, genuine, and focused on the value the subscriber would be providing to their colleagues by sharing. Rewards were structured as tiered: 3 referrals for exclusive content, 10 for a private Q&A session, 25 for a featured mention in the newsletter. - -## Acceptance criteria - -- [x] Write hero section copy explaining the program in one clear paragraph -- [x] Design the reward tier structure and write descriptions for each tier -- [x] Create FAQ section addressing common questions (how tracking works, when rewards are delivered) -- [x] Write email announcement copy for the program launch -- [x] Get feedback from [[person-sara-ricci]] on tone and clarity - -## Notes - -- [[person-sara-ricci]]'s main feedback was to simplify the reward tiers from 5 to 3. The original structure was too complex and the middle tiers were not differentiated enough to motivate incremental sharing. -- The "share value with colleagues" framing tested better in informal feedback than the "earn rewards" framing. People prefer to feel generous rather than transactional. -- The landing page copy was finalized and ready for the [[25q2]] launch. Connected to [[2025-reach-85k-subscribers]] as the referral program's primary growth contribution. diff --git a/demo-vault-v2/task-25q1-20.md b/demo-vault-v2/task-25q1-20.md deleted file mode 100644 index 29e08257..00000000 --- a/demo-vault-v2/task-25q1-20.md +++ /dev/null @@ -1,26 +0,0 @@ ---- -aliases: ["Research new podcast guest categories"] -Is A: Task -Belongs to: "[[25q1]]" -Status: Done -Owner: "[[person-luca-rossi]]" ---- -# Research new podcast guest categories - -After two seasons of the podcast, the guest roster had been predominantly engineering managers and VPs of Engineering at mid-to-large tech companies. While this audience resonated well, the content was starting to feel repetitive. This research task explored new guest categories that could bring fresh perspectives while still appealing to the newsletter's core audience of senior engineers and engineering leaders. - -The research involved analyzing listener feedback from the podcast survey (sent in Q4 2024), reviewing competitor podcast guest lineups, and identifying emerging topics in the engineering leadership space that could benefit from non-traditional guests. - -## Acceptance criteria - -- [x] Analyze podcast listener survey for guest preference data -- [x] Identify 5 new guest categories with rationale for each -- [x] Create a shortlist of 10 potential guests across the new categories -- [x] Validate the shortlist with [[person-matteo-cellini]] for technical relevance -- [x] Update the podcast pitch templates to accommodate new guest types - -## Notes - -- The five new categories identified: (1) indie hackers building developer tools, (2) technical writers and documentation leads, (3) engineering-adjacent roles (design engineers, DevRel), (4) founders who transitioned from engineering leadership, and (5) researchers in software engineering productivity. -- [[person-matteo-cellini]] flagged the software engineering productivity researchers as the most differentiated category -- very few podcasts interview these guests despite high listener interest. -- The expanded guest categories directly supported the podcast relaunch planned for [[25q3]]. diff --git a/demo-vault-v2/task-25q1-21.md b/demo-vault-v2/task-25q1-21.md deleted file mode 100644 index 2fd0b33b..00000000 --- a/demo-vault-v2/task-25q1-21.md +++ /dev/null @@ -1,26 +0,0 @@ ---- -aliases: ["Update cycling training plan for spring"] -Is A: Task -Belongs to: "[[25q1]]" -Status: Done -Owner: "[[person-luca-rossi]]" ---- -# Update cycling training plan for spring - -With spring approaching and the [[measure-resting-hr]] targets requiring consistent cardiovascular training, this task updated the cycling component of [[person-luca-rossi]]'s fitness routine for the warmer months. The Q1 2025 resting HR miss (54 vs. target of 52) made it clear that cross-training needed to complement running more effectively, not replace it during busy periods. - -The updated plan balanced cycling with running so that cycling served as active recovery and zone 2 aerobic work on non-running days. The research from the [[24q2]] gran fondo investigation informed the heart rate zone structure. - -## Acceptance criteria - -- [x] Design a weekly schedule that integrates cycling with the existing running plan -- [x] Define heart rate zones for cycling sessions (recovery, zone 2, tempo) -- [x] Identify 3-4 local cycling routes of varying length (30min, 60min, 90min) -- [x] Set up cycling sessions on the training calendar with specific targets -- [x] Order any needed equipment (new tires, cycling computer mount) - -## Notes - -- The integrated plan works out to 5 sessions per week total: 3 runs (easy, intervals, long) and 2 rides (recovery spin, zone 2 endurance). This is sustainable alongside the work schedule if morning sessions are protected. -- Ordered a heart rate monitor strap for cycling (the wrist-based watch is less accurate during riding due to vibration). The strap data is significantly cleaner. -- [[person-sara-ricci]] recommended joining a local cycling group for the Saturday long rides, which adds a social accountability element. diff --git a/demo-vault-v2/task-25q1-22.md b/demo-vault-v2/task-25q1-22.md deleted file mode 100644 index f30b0cfa..00000000 --- a/demo-vault-v2/task-25q1-22.md +++ /dev/null @@ -1,26 +0,0 @@ ---- -aliases: ["Create Q2 sponsor pitch deck"] -Is A: Task -Belongs to: "[[25q1]]" -Status: Done -Owner: "[[person-luca-rossi]]" ---- -# Create Q2 sponsor pitch deck - -Separate from the standard media kit PDF, this task created a more detailed pitch deck for high-value sponsor prospects that [[person-paco-furiani]] could present in live video calls. The deck needed to tell a compelling story about the newsletter's audience, demonstrate proven ROI for sponsors, and introduce the new data sponsorship tier with concrete examples of the insights sponsors would receive. - -The pitch deck was designed for 15-minute presentations followed by Q&A, which is the standard format for sponsor sales calls. It needed to be visually polished, data-driven, and leave room for customization based on the specific prospect's industry and goals. - -## Acceptance criteria - -- [x] Create a 12-15 slide pitch deck covering audience, engagement, pricing, and ROI -- [x] Include 2-3 sponsor case studies with specific metrics (impressions, clicks, conversions) -- [x] Design a dedicated section for the data sponsorship tier with sample insights -- [x] Build the deck in Google Slides for easy customization by [[person-paco-furiani]] -- [x] Rehearse the presentation flow with [[person-paco-furiani]] and refine - -## Notes - -- [[person-paco-furiani]] used the deck in 8 sales calls during Q2 and reported it significantly improved the quality of conversations. Prospects asked more specific questions and moved to proposal stage faster. -- The case study slides were the most impactful section -- prospects consistently asked for "more like this" during calls. -- The deck is stored in Google Drive and linked to [[procedure-sponsor-sales]] for ongoing updates. diff --git a/demo-vault-v2/task-25q1-23.md b/demo-vault-v2/task-25q1-23.md deleted file mode 100644 index bce56c79..00000000 --- a/demo-vault-v2/task-25q1-23.md +++ /dev/null @@ -1,26 +0,0 @@ ---- -aliases: ["Archive 2024 financial records"] -Is A: Task -Belongs to: "[[25q1]]" -Status: Done -Owner: "[[person-luca-rossi]]" ---- -# Archive 2024 financial records - -Annual financial housekeeping task to close out the 2024 books and prepare records for tax filing. This involves reconciling all revenue streams (newsletter sponsorships, podcast sponsorships, one-off consulting), verifying expense records, and organizing everything into the format required by the accountant. The task also includes a financial review to assess the business's profitability and inform 2025 budgeting. - -This is a compliance-critical task -- the Italian tax filing deadline drives the timeline, and incomplete records would create significant headaches with the accountant. - -## Acceptance criteria - -- [x] Reconcile all 2024 revenue against bank statements and invoices -- [x] Categorize and verify all business expenses (tools, contractors, travel, equipment) -- [x] Prepare the year-end P&L summary -- [x] Package records in the accountant's required format and deliver by February 15 -- [x] Archive all 2024 financial documents in the standard folder structure - -## Notes - -- Total 2024 revenue came in at approximately €148k, with expenses around €42k (primarily contractor compensation for [[person-sara-ricci]] and [[person-paco-furiani]], plus tools and travel). Net profit margin of roughly 72%. -- The accountant flagged that some tool subscriptions were being paid from a personal card rather than the business account. This was corrected for 2025 to simplify future reconciliation. -- Financial records are archived and linked to [[24q4]]. The P&L summary feeds into the [[2025-reach-22k-mrr]] goal planning. diff --git a/demo-vault-v2/task-25q2-24.md b/demo-vault-v2/task-25q2-24.md deleted file mode 100644 index f0c4f6d9..00000000 --- a/demo-vault-v2/task-25q2-24.md +++ /dev/null @@ -1,26 +0,0 @@ ---- -aliases: ["Migrate newsletter archive to new template"] -Is A: Task -Belongs to: "[[25q2]]" -Status: Done -Owner: "[[person-luca-rossi]]" ---- -# Migrate newsletter archive to new template - -The newsletter archive on the website was using a template designed in early 2023 that no longer matched the current brand identity. The archive is a significant traffic driver (roughly 40% of organic search traffic lands on archive pages), so the template needed to be updated for both aesthetic and functional reasons. The new template introduced better typography, a table of contents for long articles, improved code block rendering, and prominent CTAs for subscribing. - -The migration involved updating the template, testing it across all 120+ archive pages, and ensuring no SEO regressions from URL changes or broken structured data. [[person-sara-ricci]] reviewed the visual design while [[person-luca-rossi]] handled the technical implementation. - -## Acceptance criteria - -- [x] Design and implement new archive page template matching current brand guidelines -- [x] Migrate all 120+ archive pages to the new template -- [x] Add table of contents, improved code blocks, and subscribe CTAs to the template -- [x] Verify no broken links, missing images, or SEO regressions after migration -- [x] Monitor search traffic for 2 weeks post-migration to confirm no negative impact - -## Notes - -- The migration went smoothly with no SEO regressions. Organic traffic actually increased by roughly 8% in the two weeks post-migration, likely due to improved page load times and better mobile rendering. -- The subscribe CTA in the new template generates approximately 200 new subscribers per month from archive traffic -- previously there was no CTA on archive pages at all. -- [[person-sara-ricci]] caught several formatting issues during the review that would have gone unnoticed, reinforcing the value of having a dedicated editorial eye on technical changes. diff --git a/demo-vault-v2/task-25q2-25.md b/demo-vault-v2/task-25q2-25.md deleted file mode 100644 index 90dec6fe..00000000 --- a/demo-vault-v2/task-25q2-25.md +++ /dev/null @@ -1,26 +0,0 @@ ---- -aliases: ["Write e-book outline"] -Is A: Task -Belongs to: "[[25q2]]" -Status: Done -Owner: "[[person-luca-rossi]]" ---- -# Write e-book outline - -Building on the content library created in [[24q4]], this task produced a detailed outline for an e-book on engineering leadership. The book would compile and expand on the newsletter's highest-performing content, organized into a coherent narrative arc. The target audience is senior individual contributors transitioning into engineering management -- the same core audience as the newsletter. - -The outline needed to work both as a standalone book and as a lead magnet for the newsletter. The plan was to offer the e-book for free in exchange for an email address (for new subscribers) or as a reward for referral program participants. [[person-matteo-cellini]] provided input on the technical depth and accuracy of the proposed chapter structure. - -## Acceptance criteria - -- [x] Define the book's thesis, target audience, and unique angle -- [x] Create a chapter-by-chapter outline (target: 12-15 chapters) -- [x] Map existing newsletter content to each chapter (what can be reused vs. written fresh) -- [x] Estimate writing effort per chapter and create a production timeline -- [x] Get feedback from [[person-matteo-cellini]] on technical accuracy and from [[person-sara-ricci]] on narrative flow - -## Notes - -- The final outline has 14 chapters organized into 4 parts: "The Transition" (IC to manager), "The Craft" (day-to-day management), "The System" (organizational design), and "The Growth" (career trajectory). Roughly 60% of the content can be adapted from existing newsletter editions. -- [[person-matteo-cellini]] suggested adding more concrete examples from real companies (anonymized). This is the section that will require the most original writing. -- Production timeline: first draft of chapters 1-5 in [[25q3]], full draft by end of [[25q4]], editing and launch in early 2026. diff --git a/demo-vault-v2/task-25q2-26.md b/demo-vault-v2/task-25q2-26.md deleted file mode 100644 index c479064f..00000000 --- a/demo-vault-v2/task-25q2-26.md +++ /dev/null @@ -1,26 +0,0 @@ ---- -aliases: ["Set up community Discord structure"] -Is A: Task -Belongs to: "[[25q2]]" -Status: Done -Owner: "[[person-luca-rossi]]" ---- -# Set up community Discord structure - -The newsletter audience had been requesting a community space for over a year. After evaluating options (Slack, Circle, Discord, custom forum), Discord was chosen for its familiarity with the developer audience, free tier capabilities, and strong bot ecosystem. This task set up the Discord server structure, moderation rules, and initial content to seed the community before a soft launch to engaged subscribers. - -The community strategy was deliberately conservative: start with a small, invite-only group of the most engaged subscribers, establish healthy norms, and then gradually open access. The goal was quality of conversations over quantity of members. - -## Acceptance criteria - -- [x] Create the Discord server with appropriate channel structure (introductions, general, ask-anything, content-feedback, off-topic) -- [x] Write community guidelines and pin them in the welcome channel -- [x] Set up moderation bots and assign moderation roles -- [x] Create a "beta invite" list of the top 200 most engaged subscribers -- [x] Draft the launch announcement email for the beta invite group - -## Notes - -- The beta launch went well -- 87 of 200 invited subscribers joined (43.5% acceptance rate), and initial conversations were high-quality. The invite-only framing created a sense of exclusivity that motivated engagement. -- The "content-feedback" channel has been particularly valuable. Subscribers provide early input on newsletter drafts, essentially serving as a focus group. This directly improved several editions. -- [[person-sara-ricci]] volunteered to moderate the community alongside her editing role, which has worked well given the manageable size. diff --git a/demo-vault-v2/task-25q2-27.md b/demo-vault-v2/task-25q2-27.md deleted file mode 100644 index a784991c..00000000 --- a/demo-vault-v2/task-25q2-27.md +++ /dev/null @@ -1,26 +0,0 @@ ---- -aliases: ["Research LeadDev London conference"] -Is A: Task -Belongs to: "[[25q2]]" -Status: Done -Owner: "[[person-luca-rossi]]" ---- -# Research LeadDev London conference - -LeadDev London is one of the premier conferences for engineering leaders and a natural fit for the newsletter's audience. This research task evaluated whether attending (and potentially speaking at) the conference would be worthwhile for brand awareness, subscriber growth, and networking with potential sponsors and collaborators. The conference is held in Q3, so the research needed to happen in Q2 to meet speaker proposal deadlines. - -The evaluation considered cost (travel, accommodation, ticket), expected ROI (new subscribers, sponsor leads, content opportunities), and time commitment (3 days out of the office, plus preparation time for a talk if accepted). - -## Acceptance criteria - -- [x] Research LeadDev London dates, location, ticket pricing, and speaker proposal process -- [x] Estimate total cost (travel from Italy, 3 nights accommodation, ticket, meals) -- [x] Assess potential ROI: expected subscriber growth from conference exposure, sponsor networking opportunities -- [x] Submit a speaker proposal if the ROI analysis is positive -- [x] Make a go/no-go decision and book travel if proceeding - -## Notes - -- Decision: go. The estimated total cost of approximately €2,500 was justified by the networking potential alone. Three current sponsors would be attending, providing face-time opportunities that are hard to replicate remotely. -- The speaker proposal was submitted on the topic "Building a Content Business as a Side Project." Acceptance notification expected in July. -- [[person-matteo-cellini]] offered to co-present if a more technical angle would strengthen the proposal, but the solo personal narrative was deemed more aligned with the audience. diff --git a/demo-vault-v2/task-25q2-28.md b/demo-vault-v2/task-25q2-28.md deleted file mode 100644 index aa9b7aa4..00000000 --- a/demo-vault-v2/task-25q2-28.md +++ /dev/null @@ -1,26 +0,0 @@ ---- -aliases: ["Update podcast description and tags"] -Is A: Task -Belongs to: "[[25q2]]" -Status: Done -Owner: "[[person-luca-rossi]]" ---- -# Update podcast description and tags - -The podcast was approaching its relaunch in [[25q3]] with a new shorter-episode format, and the existing description and metadata on Apple Podcasts, Spotify, and other platforms had not been updated since the Season 1 launch in [[24q1-podcast-season-1]]. This task refreshed all podcast metadata to reflect the evolved content focus, improved subscriber count, and upcoming format changes. - -Podcast discoverability depends heavily on metadata quality -- the right keywords, an accurate description, and current artwork can significantly impact organic discovery on podcast platforms. This was especially important ahead of the planned relaunch. - -## Acceptance criteria - -- [x] Rewrite the podcast description for Apple Podcasts and Spotify (max 4000 chars) -- [x] Update category tags and keywords based on competitive analysis of top engineering podcasts -- [x] Refresh the podcast artwork to match current newsletter brand identity -- [x] Update the "About" section on the podcast website -- [x] Verify all changes are live across Apple Podcasts, Spotify, Google Podcasts, and Overcast - -## Notes - -- The keyword analysis revealed the podcast was missing several high-traffic tags ("tech leadership," "staff engineer," "engineering career") that competitors were ranking for. Adding these improved discoverability in platform search results within two weeks. -- The new artwork was designed to visually connect the podcast and newsletter brands more tightly. [[person-sara-ricci]] handled the design using the newsletter's existing visual system. -- Related to [[measure-podcast-downloads]] -- the metadata update is expected to contribute to improved organic discovery ahead of the Season 3 relaunch. diff --git a/demo-vault-v2/task-25q2-29.md b/demo-vault-v2/task-25q2-29.md deleted file mode 100644 index 97877f4e..00000000 --- a/demo-vault-v2/task-25q2-29.md +++ /dev/null @@ -1,26 +0,0 @@ ---- -aliases: ["Review team compensation packages"] -Is A: Task -Belongs to: "[[25q2]]" -Status: Done -Owner: "[[person-luca-rossi]]" ---- -# Review team compensation packages - -With the business growing steadily and approaching €17k MRR, it was time to review compensation for [[person-sara-ricci]] and [[person-paco-furiani]] to ensure it remained fair and competitive. Both had taken on expanded responsibilities since their initial agreements, and the business could afford modest increases without impacting profitability targets. - -The review also considered whether to introduce performance-based bonuses tied to specific business metrics, which could align incentives more directly with the [[2025-reach-22k-mrr]] and [[2025-reach-85k-subscribers]] goals. - -## Acceptance criteria - -- [x] Benchmark current compensation against market rates for similar roles in the indie content business space -- [x] Propose updated compensation packages for [[person-sara-ricci]] and [[person-paco-furiani]] -- [x] Design a performance bonus structure tied to quarterly business metrics -- [x] Discuss proposals individually with each team member and finalize -- [x] Update employment/contractor agreements with new terms - -## Notes - -- Both Sara and Paco received a 12% base increase, reflecting expanded roles and strong business performance. The increases were within budget and still leave healthy margins. -- The performance bonus structure: Paco receives a 5% commission on new sponsor revenue he directly closes; Sara receives a quarterly bonus tied to subscriber retention metrics (her editing quality directly impacts engagement and retention). -- Both team members expressed appreciation for the structured review process. Previously, compensation discussions happened reactively. Annual reviews are now scheduled as a recurring task -- see [[procedure-compensation-review]]. diff --git a/demo-vault-v2/task-25q3-30.md b/demo-vault-v2/task-25q3-30.md deleted file mode 100644 index 85794ec1..00000000 --- a/demo-vault-v2/task-25q3-30.md +++ /dev/null @@ -1,26 +0,0 @@ ---- -aliases: ["Create sponsor case studies"] -Is A: Task -Belongs to: "[[25q3]]" -Status: Done -Owner: "[[person-luca-rossi]]" ---- -# Create sponsor case studies - -Sponsor case studies are the most effective sales tool for converting premium-tier prospects. This task created 3 detailed case studies from willing sponsors, documenting their goals, the campaign setup, results achieved, and return on investment. Each case study was designed to serve double duty: as a standalone PDF for sales conversations and as content for the website's "Advertise With Us" page. - -[[person-paco-furiani]] identified the 3 sponsors most likely to participate (based on strong results and good relationships) and coordinated the interviews. [[person-luca-rossi]] wrote the case studies, and [[person-sara-ricci]] edited and designed them. - -## Acceptance criteria - -- [x] Identify and secure participation from 3 sponsors with strong campaign results -- [x] Conduct 30-minute interviews with each sponsor to capture their perspective -- [x] Write case studies following a standard format: challenge, solution, results, testimonial -- [x] Design case studies as both web pages and downloadable PDFs -- [x] Integrate case studies into the sales pitch deck and media kit - -## Notes - -- All 3 sponsors agreed to participate, which speaks to the strength of the relationships [[person-paco-furiani]] has built. Each sponsor also provided a pull quote for the media kit. -- The results data was compelling: one sponsor reported a 340% ROI on their newsletter campaign, which became the headline stat in the updated pitch deck. -- Case studies are now the first thing [[person-paco-furiani]] sends to warm leads after the initial introduction, and they have noticeably shortened the sales cycle. diff --git a/demo-vault-v2/task-25q3-31.md b/demo-vault-v2/task-25q3-31.md deleted file mode 100644 index f4f9b3eb..00000000 --- a/demo-vault-v2/task-25q3-31.md +++ /dev/null @@ -1,26 +0,0 @@ ---- -aliases: ["Write e-book first draft (ch 1-5)"] -Is A: Task -Belongs to: "[[25q3]]" -Status: Done -Owner: "[[person-luca-rossi]]" ---- -# Write e-book first draft (ch 1-5) - -Following the outline completed in [[25q2]], this task produced the first draft of the e-book's first five chapters, covering Part 1 ("The Transition") and the beginning of Part 2 ("The Craft"). These chapters address the most universal experiences of the IC-to-manager transition: the identity shift, first 1-on-1s, giving feedback, hiring your first report, and managing former peers. - -The writing approach was to start with the corresponding newsletter editions from the content library, expand them with additional depth and examples, and weave them into a cohesive narrative rather than a collection of articles. This required significant rewriting -- roughly 40% of the final text was new material. - -## Acceptance criteria - -- [x] Complete first drafts of chapters 1 through 5 (target: 25,000-30,000 words total) -- [x] Ensure each chapter stands alone while contributing to the overall narrative arc -- [x] Include at least 2 real-world examples per chapter (anonymized from newsletter reader stories) -- [x] Send chapters 1-3 to [[person-sara-ricci]] for initial editorial feedback -- [x] Maintain a writing schedule of 1,500 words/day on designated writing days - -## Notes - -- The first draft came in at 27,400 words across 5 chapters. The writing pace averaged about 1,200 words per writing day -- slightly below the 1,500 target, but the quality was higher than expected. -- [[person-sara-ricci]]'s feedback on the first 3 chapters was encouraging: the narrative voice is strong, but the transitions between "newsletter-adapted" sections and new material are sometimes jarring. This will be addressed in the second draft. -- Chapter 3 ("Giving Feedback as a New Manager") is the strongest chapter so far and may work as a standalone excerpt for marketing purposes. diff --git a/demo-vault-v2/task-25q3-32.md b/demo-vault-v2/task-25q3-32.md deleted file mode 100644 index 6865252b..00000000 --- a/demo-vault-v2/task-25q3-32.md +++ /dev/null @@ -1,26 +0,0 @@ ---- -aliases: ["Plan London trip logistics"] -Is A: Task -Belongs to: "[[25q3]]" -Status: Done -Owner: "[[person-luca-rossi]]" ---- -# Plan London trip logistics - -Following the positive research and go-decision from the [[25q2]] LeadDev London evaluation, this task handled all the logistics for the trip: flights, accommodation, conference registration, scheduling meetings with sponsors and potential collaborators who would also be attending, and preparing the talk (if the speaker proposal was accepted). - -The trip needed to be planned to maximize the business value of every day while keeping costs reasonable. [[person-paco-furiani]] coordinated with sponsor contacts to schedule in-person meetings, and [[person-luca-rossi]] reached out to several newsletter peers for informal meetups. - -## Acceptance criteria - -- [x] Book flights (Milan to London, flexible dates around conference) -- [x] Book accommodation within walking distance of the conference venue -- [x] Register for the conference (speaker registration if talk accepted, attendee otherwise) -- [x] Schedule 4-5 in-person meetings with sponsors and potential sponsors attending the conference -- [x] Create a day-by-day itinerary covering conference sessions, meetings, and social events - -## Notes - -- The speaker proposal was accepted for a 20-minute talk. Conference registration is complimentary for speakers, saving the €600 ticket cost. -- [[person-paco-furiani]] secured meetings with 5 sponsor contacts, including 2 prospective sponsors who had been in the pipeline for months. The face-to-face meetings were expected to accelerate deal closure. -- Total estimated trip cost: €1,800 (flights €350, accommodation €1,050 for 3 nights, meals and transport €400). Under the €2,500 budget allocated during the research phase. diff --git a/demo-vault-v2/task-25q3-33.md b/demo-vault-v2/task-25q3-33.md deleted file mode 100644 index bd276488..00000000 --- a/demo-vault-v2/task-25q3-33.md +++ /dev/null @@ -1,26 +0,0 @@ ---- -aliases: ["Update website with new subscriber milestone"] -Is A: Task -Belongs to: "[[25q3]]" -Status: Done -Owner: "[[person-luca-rossi]]" ---- -# Update website with new subscriber milestone - -With the newsletter crossing 66,000 subscribers at the end of [[25q2]] and trending toward 75,000 during [[25q3]], the website needed to be updated to reflect the latest social proof numbers. Subscriber milestones are a critical part of the credibility narrative for both new subscribers and potential sponsors. The update also coincided with a broader website refresh planned for Q3. - -Beyond just updating the number, this task included adding a "growth story" section to the About page that shows the subscriber trajectory over time, reinforcing the momentum narrative. - -## Acceptance criteria - -- [x] Update subscriber count across all website pages (homepage, About, Advertise) -- [x] Add a subscriber growth chart to the About page showing the 2-year trajectory -- [x] Update the media kit PDF with the latest subscriber count -- [x] Refresh sponsor logos on the homepage with current sponsors (remove churned, add new) -- [x] Verify all updates render correctly on mobile and desktop - -## Notes - -- The growth chart proved to be a compelling visual. Several new subscribers mentioned it in their welcome survey as a factor in their decision to subscribe ("I could see the community is growing, which made me want to be part of it"). -- The sponsor logo refresh required approval from each sponsor for logo usage. All approved, but the process took a week longer than expected. In the future, logo usage rights should be included in the standard sponsor contract. -- Related to [[measure-subscribers]] and [[2025-reach-85k-subscribers]] as part of the public-facing social proof strategy. diff --git a/demo-vault-v2/task-25q3-34.md b/demo-vault-v2/task-25q3-34.md deleted file mode 100644 index 10cc7cfa..00000000 --- a/demo-vault-v2/task-25q3-34.md +++ /dev/null @@ -1,26 +0,0 @@ ---- -aliases: ["Prepare Q4 content calendar"] -Is A: Task -Belongs to: "[[25q3]]" -Status: Done -Owner: "[[person-luca-rossi]]" ---- -# Prepare Q4 content calendar - -Q4 is the most important quarter for content strategy due to year-end retrospective content, "best of" lists, and 2026 predictions -- all of which tend to perform well with the audience. This task created a detailed content calendar for [[25q4]], mapping every newsletter edition, podcast episode, and social media campaign to specific themes and publication dates. - -The calendar needed to balance planned content with flexibility for timely topics. [[person-sara-ricci]] co-developed the calendar to ensure realistic editorial timelines and identify editions where she could take a larger role in drafting to free up [[person-luca-rossi]] for Laputa development. - -## Acceptance criteria - -- [x] Map all Q4 newsletter editions (12-13 weekly editions) with topic, angle, and draft deadline -- [x] Plan podcast episodes aligned with newsletter themes where possible -- [x] Schedule the annual review post for the last edition before the holiday break -- [x] Identify 3-4 editions where [[person-sara-ricci]] can take lead on drafting -- [x] Build in 2 "flex spots" for timely/reactive content - -## Notes - -- The calendar includes 13 editions, with [[person-sara-ricci]] leading on 4 of them (topics she has particular expertise in: editorial processes, content strategy, and two interview-based editions). This is the first time she will publish under her own byline alongside Luca's. -- The annual review post is scheduled for December 18 with a draft deadline of December 10, giving [[person-sara-ricci]] a full week for editing. -- The flex spots are intentionally placed in October and November, when industry news cycles (conference season, product launches) tend to generate reactive content opportunities. diff --git a/demo-vault-v2/task-25q3-35.md b/demo-vault-v2/task-25q3-35.md deleted file mode 100644 index 7c7e54c5..00000000 --- a/demo-vault-v2/task-25q3-35.md +++ /dev/null @@ -1,26 +0,0 @@ ---- -aliases: ["Review portfolio allocation Q3"] -Is A: Task -Belongs to: "[[25q3]]" -Status: Done -Owner: "[[person-luca-rossi]]" ---- -# Review portfolio allocation Q3 - -Quarterly personal finance review to ensure investment portfolio allocation remains aligned with the target strategy. With the newsletter business generating consistent and growing income, the investment strategy has shifted from conservative capital preservation toward a more balanced growth approach. This review checks actual allocation against targets and identifies any rebalancing needed. - -The portfolio covers both long-term retirement savings and a medium-term "business runway" fund that provides 6 months of living expenses as a safety net for the indie business. [[person-luca-rossi]] manages the portfolio directly using a passive index fund strategy. - -## Acceptance criteria - -- [x] Pull current portfolio allocation across all accounts -- [x] Compare actual allocation against target allocation (70% equities, 20% bonds, 10% cash/runway) -- [x] Identify any positions that have drifted more than 5% from target -- [x] Execute rebalancing trades if needed -- [x] Update the financial tracking spreadsheet with Q3 figures - -## Notes - -- The portfolio had drifted slightly equity-heavy (74% vs. 70% target) due to strong market performance in H1 2025. Rebalanced by redirecting September investment contributions to bonds rather than selling equities to avoid tax implications. -- The business runway fund is fully funded at 6 months of expenses. Considering increasing it to 9 months given the growing team obligations to [[person-sara-ricci]] and [[person-paco-furiani]]. -- This quarterly review takes about 1 hour. Low effort, high peace of mind. Documented in [[procedure-quarterly-finance-review]]. diff --git a/demo-vault-v2/task-25q4-36.md b/demo-vault-v2/task-25q4-36.md deleted file mode 100644 index a99e3c76..00000000 --- a/demo-vault-v2/task-25q4-36.md +++ /dev/null @@ -1,26 +0,0 @@ ---- -aliases: ["Write 2026 sponsorship prospectus"] -Is A: Task -Belongs to: "[[25q4]]" -Status: Open -Owner: "[[person-luca-rossi]]" ---- -# Write 2026 sponsorship prospectus - -The 2026 sponsorship prospectus is the annual document that defines the sponsor offerings, pricing, and terms for the coming year. It serves as the foundation for all sponsor sales conversations in Q1 2026 and beyond. The prospectus needs to reflect the newsletter's growth (projected 80k+ subscribers by year-end), the expanded product portfolio (newsletter + podcast + community + data insights), and the pricing adjustments warranted by increased audience size and engagement. - -This is a strategic document that [[person-paco-furiani]] will use as his primary sales tool. It should position the newsletter as a premium advertising channel in the engineering leadership space, distinct from commodity newsletter ad networks. [[person-luca-rossi]] will draft the content and positioning while [[person-paco-furiani]] provides input on prospect objections and competitive positioning. - -## Acceptance criteria - -- [ ] Define 2026 sponsorship tiers and pricing (incorporating 10-15% price increase) -- [ ] Write the prospectus document including audience profile, engagement metrics, and case studies -- [ ] Include new product offerings (community sponsorship, e-book sponsorship) if applicable -- [ ] Design the prospectus as a professional PDF using the updated brand guidelines -- [ ] Review with [[person-paco-furiani]] and finalize before December 1 - -## Notes - -- Should incorporate the case studies created in [[25q3]] as social proof within the prospectus. -- Consider bundling options (newsletter + podcast + community) as premium packages, which would differentiate from competitors who only offer single-channel placements. -- The December 1 deadline is important because [[person-paco-furiani]] needs the prospectus to begin Q1 2026 outreach during the December-January period when budget planning happens. diff --git a/demo-vault-v2/task-25q4-37.md b/demo-vault-v2/task-25q4-37.md deleted file mode 100644 index d941af76..00000000 --- a/demo-vault-v2/task-25q4-37.md +++ /dev/null @@ -1,26 +0,0 @@ ---- -aliases: ["Plan 2026 editorial calendar"] -Is A: Task -Belongs to: "[[25q4]]" -Status: Open -Owner: "[[person-luca-rossi]]" ---- -# Plan 2026 editorial calendar - -Building on the quarterly content calendar process established throughout 2024-2025, this task creates the high-level editorial calendar for all of 2026. The annual calendar does not specify individual edition topics but rather defines the thematic arcs for each quarter, major content events (annual review, mid-year retrospective), and the publishing cadence for each channel (newsletter, podcast, social media, e-book launch). - -The 2026 calendar also needs to account for the e-book launch (projected Q1 2026), any changes to the podcast format based on the relaunch learnings, and the potential introduction of a paid tier or premium content offering that has been under discussion. - -## Acceptance criteria - -- [ ] Define quarterly thematic arcs for 2026 (Q1: launch + new year, Q2: growth, Q3: depth, Q4: reflection) -- [ ] Set the publishing cadence for each channel (newsletter frequency, podcast episodes/month) -- [ ] Map major content events and their production timelines -- [ ] Identify guest contributor opportunities to reduce load on [[person-luca-rossi]] -- [ ] Review with [[person-sara-ricci]] and align on her editorial capacity - -## Notes - -- A key decision for 2026 is whether to introduce a paid subscriber tier. The editorial calendar should plan for this possibility even if the final decision has not been made yet. -- [[person-sara-ricci]]'s growing capability as a writer (she published 4 editions under her own byline in Q4 2025) opens the possibility of increasing publishing frequency without increasing Luca's writing load. -- The calendar should also account for [[person-luca-rossi]]'s Laputa development time, which is expected to remain at roughly 40% of total work hours in 2026. diff --git a/demo-vault-v2/task-25q4-38.md b/demo-vault-v2/task-25q4-38.md deleted file mode 100644 index bb148e7a..00000000 --- a/demo-vault-v2/task-25q4-38.md +++ /dev/null @@ -1,26 +0,0 @@ ---- -aliases: ["Update team handbook"] -Is A: Task -Belongs to: "[[25q4]]" -Status: Open -Owner: "[[person-luca-rossi]]" ---- -# Update team handbook - -The team handbook, last updated in [[24q4]] when role descriptions were created, needs a comprehensive refresh to reflect the operational changes of 2025. The team has grown more autonomous, new tools and processes have been adopted (Airtable, Discord, referral program), and several ad-hoc decisions about communication norms and decision-making authority need to be codified. - -The handbook serves as the single reference document for how the team operates. It should be clear enough that a new team member (hypothetical at this point) could read it and understand the business structure, tools, processes, and cultural norms without extensive onboarding conversations. - -## Acceptance criteria - -- [ ] Review and update all role descriptions for [[person-luca-rossi]], [[person-sara-ricci]], [[person-paco-furiani]], and [[person-matteo-cellini]] -- [ ] Document all tools and their purposes (Airtable, Retool, Discord, email platform, etc.) -- [ ] Update communication norms (async-first, response time expectations, escalation paths) -- [ ] Add a section on operational procedures with links to all [[procedure-quarterly-retro]], [[procedure-sponsor-renewal]], etc. -- [ ] Review the handbook with the full team and incorporate feedback - -## Notes - -- The handbook should be stored in the vault as a living document, not a static PDF. This ensures it stays current as processes evolve. -- Consider adding a "decision log" section that captures important operational decisions and their rationale, so the team can reference why things are done a certain way. -- This is a good candidate for [[person-sara-ricci]] to co-own, given her editorial skills and growing understanding of the business operations. diff --git a/demo-vault-v2/task-25q4-39.md b/demo-vault-v2/task-25q4-39.md deleted file mode 100644 index 32a5a7d5..00000000 --- a/demo-vault-v2/task-25q4-39.md +++ /dev/null @@ -1,26 +0,0 @@ ---- -aliases: ["Book travel for January conferences"] -Is A: Task -Belongs to: "[[25q4]]" -Status: Open -Owner: "[[person-luca-rossi]]" ---- -# Book travel for January conferences - -Following the positive experience at LeadDev London during [[25q3]], [[person-luca-rossi]] is planning to attend 1-2 conferences in January 2026 to kick off the new year with networking and content inspiration. This task covers researching available conferences, evaluating the cost-benefit of each, and booking all travel logistics before the holiday price surge. - -The priority conferences are those with strong engineering leadership audiences where [[person-luca-rossi]] could potentially speak, meet sponsors, and generate content (live-tweeting, post-conference newsletter editions). The LeadDev London experience showed that in-person events generate outsized networking value relative to their cost. - -## Acceptance criteria - -- [ ] Research January 2026 engineering/tech leadership conferences (target: 3-5 candidates) -- [ ] Evaluate each conference on: audience fit, speaker opportunity, sponsor networking potential, cost -- [ ] Submit speaker proposals to the top 2 conferences by their deadlines -- [ ] Book flights and accommodation for selected conferences (targeting early-bird rates) -- [ ] Create a networking prep document listing target contacts at each conference - -## Notes - -- Likely candidates include: a US-based conference (e.g., QCon San Francisco if January timing works), a European event, and possibly a niche indie hacker gathering. -- Budget: approximately €4,000-5,000 for 2 conferences including transatlantic travel. This is justified by the ROI demonstrated at LeadDev London (2 new sponsor deals closed from conference contacts). -- [[person-paco-furiani]] should attend at least one conference in 2026 as well, to build his own network with sponsor contacts. This could be a separate task for Q1 2026. diff --git a/demo-vault-v2/task-25q4-40.md b/demo-vault-v2/task-25q4-40.md deleted file mode 100644 index edb9c44f..00000000 --- a/demo-vault-v2/task-25q4-40.md +++ /dev/null @@ -1,26 +0,0 @@ ---- -aliases: ["Write end-of-year letter to subscribers"] -Is A: Task -Belongs to: "[[25q4]]" -Status: Open -Owner: "[[person-luca-rossi]]" ---- -# Write end-of-year letter to subscribers - -The end-of-year letter is a personal, non-promotional message from [[person-luca-rossi]] to the entire subscriber base, separate from the annual review post. While the annual review is data-driven and business-focused, the end-of-year letter is reflective and personal -- a thank-you to the community, a look back at the year's highlights, and a personal note about what the journey has meant. - -This tradition started in 2023 and has consistently been one of the most-replied-to editions of the year. Subscribers appreciate the vulnerability and personal touch, and the reply volume provides valuable qualitative feedback that numbers alone cannot capture. - -## Acceptance criteria - -- [ ] Write a personal, reflective letter (target: 1,000-1,500 words) covering the year's highlights and personal growth -- [ ] Include specific thank-yous to the community for milestones achieved (subscriber growth, community engagement) -- [ ] Share one honest reflection on a failure or mistake from the year -- [ ] End with a forward-looking note about what excites you about 2026 -- [ ] Schedule for publication on December 23 (last working day before holiday break) - -## Notes - -- The 2024 end-of-year letter received 340 replies, making it the most-engaged edition of the year by that metric. The key to the letter is genuine vulnerability, not performative transparency. -- Consider including a subtle referral CTA ("if you know someone who would enjoy this community, forward this email") since holiday sharing tends to convert well. -- [[person-sara-ricci]] should do a light edit for clarity but this letter should retain [[person-luca-rossi]]'s unfiltered voice. Over-editing dilutes the personal tone. diff --git a/demo-vault-v2/task-25q4-41.md b/demo-vault-v2/task-25q4-41.md deleted file mode 100644 index 84a2d440..00000000 --- a/demo-vault-v2/task-25q4-41.md +++ /dev/null @@ -1,26 +0,0 @@ ---- -aliases: ["Review and renew tool subscriptions"] -Is A: Task -Belongs to: "[[25q4]]" -Status: Open -Owner: "[[person-luca-rossi]]" ---- -# Review and renew tool subscriptions - -Annual review of all SaaS tools and subscriptions used by the business. The tool stack has grown organically over two years and some subscriptions may no longer be necessary, while others might benefit from an annual plan switch (typically 20-30% cheaper than monthly billing). This review also evaluates whether any tools should be replaced with better alternatives. - -The current tool stack includes: email platform, website hosting, analytics, Airtable, Retool, podcast hosting, design tools, scheduling tools, and various smaller utilities. Total tool spend is a significant line item in the business expenses. - -## Acceptance criteria - -- [ ] Audit all active subscriptions with monthly cost, annual cost, and usage frequency -- [ ] Identify subscriptions that can be cancelled (unused or redundant) -- [ ] Identify subscriptions that should switch from monthly to annual billing for savings -- [ ] Evaluate 2-3 tools where better/cheaper alternatives exist -- [ ] Execute renewals, cancellations, and switches before year-end - -## Notes - -- Last year's audit (in the [[25q1]] financial archiving task) identified €200/month in wasted subscriptions. Expecting a smaller number this year since that cleanup was relatively recent, but worth checking. -- The biggest tool expense is the email platform. Evaluate whether the current platform still offers the best value given the subscriber count has grown significantly (pricing tiers scale with list size). -- Consider consolidating some tools: Airtable might be able to replace one of the analytics tools, and Retool dashboards could replace some standalone reporting subscriptions. diff --git a/demo-vault-v2/task-25q4-42.md b/demo-vault-v2/task-25q4-42.md deleted file mode 100644 index dee27494..00000000 --- a/demo-vault-v2/task-25q4-42.md +++ /dev/null @@ -1,26 +0,0 @@ ---- -aliases: ["Archive 2025 sponsor contracts"] -Is A: Task -Belongs to: "[[25q4]]" -Status: Open -Owner: "[[person-luca-rossi]]" ---- -# Archive 2025 sponsor contracts - -Year-end archival of all 2025 sponsor contracts, following the [[procedure-sponsor-archive]] process established in [[24q3]]. This task is more straightforward than the 2024 version because the process and naming conventions are already in place. The main work is collecting all contracts, reconciling payments, and ensuring the Airtable base is aligned with the financial records. - -This is a compliance-critical task that feeds into the annual financial records archival and tax filing process. [[person-paco-furiani]] handles the initial collection and organization while [[person-luca-rossi]] does the final reconciliation. - -## Acceptance criteria - -- [ ] Collect all 2025 sponsor contracts (new, renewed, expired, and churned) from the Airtable base -- [ ] Apply standard naming convention and file in the archive folder structure -- [ ] Reconcile contracted amounts against actual payments received for each sponsor -- [ ] Flag and resolve any payment discrepancies before year-end -- [ ] Update the Airtable base with final 2025 status for each sponsor record - -## Notes - -- The Airtable base should make this process significantly faster than the 2024 version, which relied on Google Sheets and email threads. Expecting 1-2 hours instead of the 4+ hours it took last year. -- [[person-paco-furiani]] should start collecting contracts in early December to avoid the year-end rush. -- Any outstanding payments need to be invoiced before December 15 to ensure they are received before the fiscal year closes. diff --git a/demo-vault-v2/task-25q4-43.md b/demo-vault-v2/task-25q4-43.md deleted file mode 100644 index ad2bee30..00000000 --- a/demo-vault-v2/task-25q4-43.md +++ /dev/null @@ -1,26 +0,0 @@ ---- -aliases: ["Set up 2026 tracking spreadsheets"] -Is A: Task -Belongs to: "[[25q4]]" -Status: Open -Owner: "[[person-luca-rossi]]" ---- -# Set up 2026 tracking spreadsheets - -Annual setup task to create fresh tracking spreadsheets for 2026 metrics. While the Retool dashboard handles real-time monitoring, the underlying data still needs structured tracking sheets for targets, actuals, and variance analysis. This task creates the 2026 versions of the tracking sheets for [[measure-subscribers]], [[measure-sponsorship-mrr]], [[measure-podcast-downloads]], [[measure-books-per-month]], and [[measure-resting-hr]]. - -The task also involves setting the 2026 targets, which requires reviewing the 2025 outcomes and projecting realistic growth. The target-setting process should involve input from [[person-paco-furiani]] (for revenue targets) and incorporate the lessons from two years of target-setting experience. - -## Acceptance criteria - -- [ ] Create 2026 tracking spreadsheets for all five measures with monthly and quarterly views -- [ ] Set proposed 2026 targets for each measure based on 2025 actuals and growth projections -- [ ] Configure the Retool dashboard to read from the new 2026 data sources -- [ ] Review proposed targets with [[person-paco-furiani]] and finalize -- [ ] Archive the 2025 tracking spreadsheets in the completed records folder - -## Notes - -- Key question for 2026 targets: should the growth rate be maintained (roughly 60-70% year-over-year for subscribers and revenue) or moderated to a more sustainable pace? Two years of aggressive growth has been productive but also stressful. -- Consider adding new measures for 2026, such as community engagement metrics (Discord activity, referral program participation) and e-book sales once it launches. -- The target-setting conversation with [[person-paco-furiani]] should happen in the first week of December to give him time to build his Q1 2026 outreach plan around the revenue targets. diff --git a/demo-vault-v2/task-25q4-44.md b/demo-vault-v2/task-25q4-44.md deleted file mode 100644 index 8034f792..00000000 --- a/demo-vault-v2/task-25q4-44.md +++ /dev/null @@ -1,26 +0,0 @@ ---- -aliases: ["Update podcast listing on all platforms"] -Is A: Task -Belongs to: "[[25q4]]" -Status: Open -Owner: "[[person-luca-rossi]]" ---- -# Update podcast listing on all platforms - -End-of-year update to the podcast listings across all distribution platforms. This follows the same approach as the Q2 update (task in [[25q2]]) but reflects the full year of podcast evolution: the Season 3 relaunch, the shorter episode format, updated download numbers, and any new platforms that should be added to the distribution list. - -The podcast has grown significantly in 2025 and the listings should reflect the current state rather than the earlier positioning. This also presents an opportunity to experiment with platform-specific descriptions that are optimized for each platform's search algorithm. - -## Acceptance criteria - -- [ ] Update podcast description and metadata on all platforms (Apple Podcasts, Spotify, Google Podcasts, Overcast, Pocket Casts) -- [ ] Refresh episode artwork for the most recent season -- [ ] Add the podcast to any new platforms that have gained relevance in 2025 -- [ ] Optimize keywords based on updated competitive analysis -- [ ] Verify all changes are live and appearing correctly across platforms - -## Notes - -- Check whether YouTube Podcasts should be added as a distribution channel. Several engineering podcasts have seen significant growth on YouTube in 2025, and the video format could open a new audience. -- The shorter episode format from the Season 3 relaunch should be highlighted in the description, as it differentiates from the longer-form competitor podcasts. -- [[person-sara-ricci]] can handle the artwork refresh since she created the current version during the [[25q2]] update. diff --git a/demo-vault-v2/task-25q4-45.md b/demo-vault-v2/task-25q4-45.md deleted file mode 100644 index ed533b13..00000000 --- a/demo-vault-v2/task-25q4-45.md +++ /dev/null @@ -1,26 +0,0 @@ ---- -aliases: ["Write Q4 retrospective"] -Is A: Task -Belongs to: "[[25q4]]" -Status: Open -Owner: "[[person-luca-rossi]]" ---- -# Write Q4 retrospective - -The Q4 2025 retrospective is both a quarterly review and the year-end capstone for the 2025 goal cycle. This retro covers Q4 performance across all tracked measures, but more importantly, it provides a comprehensive assessment of the annual goals: [[2025-reach-22k-mrr]], [[2025-reach-85k-subscribers]], and [[2025-ship-laputa]]. The retro feeds directly into 2026 goal-setting and strategic planning. - -Following the template established in the Q1 2024 retrospective (the first task in this vault), this retro should cover metrics, narrative, learnings, and action items. However, because it is also an annual retro, it should include an additional section reflecting on the two-year arc of the business from early 2024 through end of 2025. - -## Acceptance criteria - -- [ ] Pull final Q4 and full-year 2025 metrics for all tracked measures -- [ ] Write quarterly narrative for Q4 (metrics, wins, misses) -- [ ] Write annual narrative for 2025 including assessment against each annual goal -- [ ] Identify top 5 learnings from 2025 and top 5 priorities for 2026 -- [ ] Share the retro with [[person-paco-furiani]], [[person-sara-ricci]], and [[person-matteo-cellini]] for input - -## Notes - -- This retro will be significantly more substantial than the quarterly retros, likely 3,000-4,000 words. Allocate a full day for writing and reflection. -- The retro should be honest about goal misses (several targets across two years were narrowly missed) and what this pattern reveals about target-setting methodology. -- Consider publishing a condensed version of the annual retro as a newsletter edition, similar to the [[24q4]] annual review post. The 2024 version was the most-shared edition of the year, so a 2025 version could perform similarly for [[2025-reach-85k-subscribers]]. diff --git a/demo-vault-v2/task.md b/demo-vault-v2/task.md deleted file mode 100644 index 990fb2cd..00000000 --- a/demo-vault-v2/task.md +++ /dev/null @@ -1,7 +0,0 @@ ---- -Is A: Type ---- - -# Task - -A Task is a discrete, actionable to-do that can be completed. Tasks are the smallest unit of work, linked to Projects or Procedures. diff --git a/demo-vault-v2/test-note-a.md b/demo-vault-v2/test-note-a.md deleted file mode 100644 index fec7d509..00000000 --- a/demo-vault-v2/test-note-a.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Test Note A -type: Note -status: Active ---- -# Test Note A - -[[MaBC diff --git a/demo-vault-v2/test-note-abc.md b/demo-vault-v2/test-note-abc.md deleted file mode 100644 index a69dde29..00000000 --- a/demo-vault-v2/test-note-abc.md +++ /dev/null @@ -1,4 +0,0 @@ ---- -type: Note -status: Active ---- diff --git a/demo-vault-v2/the-compound-effect-in-knowledge-work.md b/demo-vault-v2/the-compound-effect-in-knowledge-work.md deleted file mode 100644 index c08cbf19..00000000 --- a/demo-vault-v2/the-compound-effect-in-knowledge-work.md +++ /dev/null @@ -1,28 +0,0 @@ ---- -aliases: ["The Compound Effect in Knowledge Work"] -Is A: Evergreen -Topics: ["[[topic-productivity-systems]]", "[[topic-writing]]"] -Status: Published ---- -# The Compound Effect in Knowledge Work -Small, consistent intellectual investments compound dramatically over time. A newsletter writer who publishes 50 essays a year builds an insurmountable lead over one who publishes 10 — not just in volume, but in clarity of thought, audience trust, and SEO authority. - -The key insight is that the compounding happens in the *system*, not in any single piece. Each essay trains your thinking, attracts new readers, and creates internal links for future pieces. After 200 essays, you're not writing 200 times better — but you are writing with the advantage of 200 previous attempts behind you. - -This is why consistency beats intensity. A newsletter sent every Monday for 3 years is more valuable than 50 brilliant newsletters sent sporadically. - -The compounding operates on multiple layers simultaneously, which is what makes it so powerful and so hard to replicate. The first layer is skill: every piece you write makes you slightly better at articulating complex ideas. Over 200 pieces, this adds up to a dramatic improvement in writing speed and clarity. The second layer is audience: each piece attracts some new readers who stay for subsequent pieces, creating a growing base of attention. The third layer is content: your archive becomes a resource that new readers explore, older pieces get cited and linked, and the total body of work develops a gravitational pull that individual pieces cannot. The fourth layer — and the most underappreciated — is network: each piece creates potential connections to people, opportunities, and ideas that compound into an expanding web of relationships and possibilities. - -I see this concretely in Refactoring's trajectory. In year one, each newsletter issue stood alone — it either resonated or it did not, and its impact was limited to the week it was sent. By year three, new issues referenced and built on previous ones, readers arrived through the archive as much as through the current issue, and sponsors were attracted by the accumulated authority of the entire body of work. The revenue from a single issue in year three was several multiples of a single issue in year one, not because any individual issue was that much better, but because it sat on top of an accumulated foundation of trust, authority, and reader habit. - -The implication for anyone starting a knowledge work practice — a newsletter, a blog, a research agenda, a consulting practice — is to optimize for longevity over peak performance. The newsletter that publishes consistently for 5 years will almost certainly outperform the one that publishes brilliantly for 18 months and then burns out. The compounding curve is back-loaded: the payoff is disproportionately concentrated in years 3-5 and beyond. This makes the early period feel unrewarding, which is exactly why most people quit before the compounding kicks in. - -## Key insight -Knowledge work compounds through at least four reinforcing loops: skill improvement, audience accumulation, content gravity, and network expansion. Each loop amplifies the others, creating a flywheel that accelerates over time. The practical consequence is that the most important decision in knowledge work is not what to write or how to write it — it is whether to keep going. The people who benefit most from compounding are the ones who stay consistent long enough for the back-loaded returns to materialize. Quitting in year two is like selling a compounding investment right before the hockey stick. - -## Related -- [[on-consistency-in-creative-work]] — Consistency is the mechanism that makes compounding possible -- [[knowledge-management-is-not-filing]] — Connected knowledge compounds in ways that filed knowledge does not -- [[newsletter-growth-is-about-trust]] — Trust is the audience-layer compound that drives sustainable growth -- [[investing-in-yourself-vs-markets]] — Compounding returns on self-investment often exceed market returns -- [[note-atomic-habits]] — The habit framework for maintaining the consistency that enables compounding diff --git a/demo-vault-v2/the-real-job-of-a-newsletter.md b/demo-vault-v2/the-real-job-of-a-newsletter.md deleted file mode 100644 index 0c22bec2..00000000 --- a/demo-vault-v2/the-real-job-of-a-newsletter.md +++ /dev/null @@ -1,28 +0,0 @@ ---- -aliases: ["The Real Job of a Newsletter"] -Is A: Evergreen -Topics: ["[[topic-content-strategy]]", "[[topic-newsletter-growth]]"] -Status: Published ---- -# The Real Job of a Newsletter -People subscribe to newsletters for different reasons: to learn, to stay informed, to feel part of a community, to be entertained, to have a trusted filter. But they stay subscribed for one reason: the newsletter reliably delivers on the implicit promise it made when they subscribed. - -The biggest growth lever for any newsletter isn't content, distribution, or growth hacks — it's understanding the real job the reader is hiring the newsletter to do, and doing that job consistently well. - -For Refactoring, the job is: 'help me think more clearly about engineering, leadership, and building software at scale, without taking too much of my time.' - -The jobs-to-be-done framework, originally developed for product management, maps perfectly to newsletters because a newsletter is a product. Readers have alternatives — other newsletters, blogs, podcasts, books, conversations with peers — and they allocate their limited attention based on which option does the job best. Understanding the specific job your newsletter is hired to do, in the reader's own language, is the single most important strategic insight you can have. It determines content scope, tone, length, frequency, and format. Every decision flows from it. - -I arrived at Refactoring's job statement through reader interviews, not assumption. Early on, I assumed readers wanted tactical advice — specific frameworks, templates, and how-tos. The interviews revealed something different. Readers wanted to feel less alone in the challenges of engineering leadership. They wanted someone who understood their specific problems to help them think through those problems, not hand them a pre-packaged solution. The difference is subtle but enormous in its implications for content strategy. Tactical content competes with documentation and Stack Overflow. Thinking-partner content competes with trusted mentors, and there is far less supply of that. - -The job statement also serves as a powerful editorial filter. When I am choosing between two potential newsletter topics, the question "which of these better helps engineering leaders think more clearly about building software at scale?" immediately resolves the decision. It eliminates topics that are interesting but off-job — a piece about personal productivity habits, for example, might be interesting coming from me but does not serve the core job readers hired Refactoring to do. This discipline to stay on-job is what builds the reliability that drives retention. Readers learn that every issue will be relevant to their core challenge, and that predictability is worth more than occasional brilliance in an unrelated domain. - -## Key insight -A newsletter's job is not what the author thinks it is — it is what the reader experiences it as. The gap between these two perspectives is where most newsletter strategies fail. Authors optimize for what they want to write. Successful newsletters optimize for the job readers are hiring them to do. Discovering that job requires talking to readers and listening carefully to the language they use, not making assumptions based on content strategy theory. Once you know the job, every editorial decision becomes clearer, and the newsletter builds the kind of reliable value that drives long-term retention and growth. - -## Related -- [[newsletter-growth-is-about-trust]] — Consistently doing the job well is how trust is built -- [[why-b2b-newsletters-work]] — The B2B context creates specific jobs-to-be-done that newsletters are uniquely suited to fill -- [[newsletter-subject-lines]] — Subject lines should communicate the job each issue will do for the reader -- [[b2b-content-is-trust-not-traffic]] — Understanding the reader's job is how content becomes trust-building rather than traffic-chasing -- [[note-good-strategy-bad-strategy]] — Strategy as understanding the core challenge, which parallels understanding the core job diff --git a/demo-vault-v2/the-saas-metric-that-matters.md b/demo-vault-v2/the-saas-metric-that-matters.md deleted file mode 100644 index d3432715..00000000 --- a/demo-vault-v2/the-saas-metric-that-matters.md +++ /dev/null @@ -1,28 +0,0 @@ ---- -aliases: ["The SaaS Metric That Actually Matters"] -Is A: Evergreen -Topics: ["[[topic-saas-business]]"] -Status: Published ---- -# The SaaS Metric That Actually Matters -Everyone talks about MRR, ARR, and churn rate. These are important. But the metric that actually tells you whether your business is healthy is net revenue retention (NRR) — the percentage of revenue from last year's customers you're retaining this year, including expansions. - -NRR > 100% means your existing customers are spending more than they were. This is the signature of product-market fit: customers who stay and spend more because the product keeps improving and becoming more embedded in their workflows. - -A business with 80% NRR is structurally fragile. A business with 120% NRR is almost impossible to kill. - -The power of NRR as a diagnostic metric is that it captures multiple dimensions of business health in a single number. High NRR means low churn (customers are not leaving), strong product-market fit (customers are expanding usage), and effective pricing (the pricing model captures value as usage grows). Low NRR can mean any combination of these factors is failing, and decomposing NRR into its components — gross retention, contraction, and expansion — tells you exactly where the problem lies. I have seen founders obsess over MRR growth while ignoring an NRR of 85%, which means they are filling a leaky bucket. No amount of new customer acquisition fixes a retention problem. - -The NRR benchmark varies meaningfully by market segment. Enterprise SaaS products typically target 120-130% NRR because large accounts have natural expansion opportunities — more seats, more teams, higher tiers. SMB products often settle for 90-100% because small businesses churn at higher rates and have limited expansion potential. Understanding which benchmark applies to your market is critical for not either panicking about a number that is actually healthy or celebrating a number that is actually mediocre for your segment. - -What makes NRR particularly interesting from a content business perspective is that the concept translates directly to newsletter economics. A newsletter's "NRR" is whether last year's sponsors are spending more this year. If your returning sponsors are increasing their commitment — longer contracts, bigger packages, additional placements — that is the clearest possible signal that your content is generating real value. In Refactoring's case, tracking sponsor NRR was what gave me confidence that the business model was sound well before revenue was large in absolute terms. Sponsors who renewed at 120%+ of their initial spend were telling me, with their budget decisions, that the newsletter was working for them. - -## Key insight -Net revenue retention is the single metric that separates structurally healthy businesses from structurally fragile ones. A high NRR means your product is becoming more valuable to existing customers over time, which creates a compounding revenue base that grows even without new customer acquisition. The most important question for any SaaS founder is not "how do I acquire more customers?" but "how do I make existing customers want to spend more?" The answer to the second question makes the first question easier and less urgent. - -## Related -- [[the-sponsorship-relationship]] — Sponsor retention as the newsletter equivalent of NRR -- [[small-teams-scale-through-systems]] — Systems that improve customer experience drive NRR -- [[open-source-as-marketing]] — NRR is the critical conversion metric for open-source to paid transitions -- [[b2b-content-is-trust-not-traffic]] — Trust-driven content creates the kind of engagement that drives sponsor NRR -- [[note-the-lean-startup]] — The build-measure-learn cycle applied to improving retention diff --git a/demo-vault-v2/the-sponsorship-relationship.md b/demo-vault-v2/the-sponsorship-relationship.md deleted file mode 100644 index 4067cead..00000000 --- a/demo-vault-v2/the-sponsorship-relationship.md +++ /dev/null @@ -1,28 +0,0 @@ ---- -aliases: ["The Sponsor Relationship Is a Long Game"] -Is A: Evergreen -Topics: ["[[topic-saas-business]]", "[[topic-b2b-marketing]]"] -Status: Published ---- -# The Sponsor Relationship Is a Long Game -Most newsletters treat sponsors transactionally: one slot, one check, move on. The newsletters that build lasting sponsor revenue think differently. - -A sponsor who tries your audience once and gets good results will come back. A sponsor who tries once and gets mediocre results will not — regardless of whether the ROI was there. The relationship matters as much as the numbers. - -This means investing in sponsor success even beyond what's contractually required. Proactive reporting, creative suggestions, introductions to relevant readers. The goal is for the sponsor to feel like a partner, not a customer. - -The economics of sponsor retention versus sponsor acquisition make this obvious once you do the math. Finding a new sponsor requires outreach, negotiation, creative briefing, and trust-building — a process that takes 4-8 weeks minimum and has a low conversion rate. Renewing an existing sponsor requires a conversation and an invoice. The cost of acquisition is at least 5x the cost of retention, which means that a sponsor who renews three times is worth roughly 15x a one-time sponsor in terms of net margin. Despite this, most newsletter operators spend the majority of their sales energy on acquisition rather than retention, because acquisition feels active and important while retention feels passive. - -The retention playbook I have developed for Refactoring is built around three principles. First, proactive communication: I send sponsors performance data mid-campaign, not just at the end, along with honest context about what is working and what is not. Second, creative partnership: I suggest ad copy angles, positioning adjustments, and timing recommendations based on what I know about the audience. This takes time but transforms the relationship from vendor-buyer to collaborator. Third, honest feedback: if I do not think a sponsor is a good fit for the audience, I tell them before they sign, even if it means losing the deal. This has saved me from bad campaigns that would have soured the relationship and the audience's trust simultaneously. - -The long-game approach to sponsorship also creates a powerful flywheel with content quality. When sponsors succeed, they renew. Renewals provide revenue stability, which reduces the pressure to accept poorly-fitting sponsors. Fewer poorly-fitting sponsors means better audience experience, which means higher engagement, which means sponsors succeed more consistently. The opposite flywheel — accepting any sponsor to meet short-term revenue targets — degrades audience trust, reduces engagement, makes sponsors less successful, and makes renewals less likely. Understanding which flywheel you are in, and which one your decisions are accelerating, is critical. - -## Key insight -Newsletter sponsorship is a relationship business disguised as a media business. The newsletters that build sustainable sponsor revenue are the ones that treat each sponsor relationship as an asset to be cultivated over years, not a transaction to be completed. This requires investing in sponsor success beyond contractual obligations, being honest about fit, and optimizing for renewal rate over deal volume. The compounding value of long-term sponsor relationships — in revenue stability, reduced sales effort, and improved audience experience — is the most underrated economic advantage in the newsletter business. - -## Related -- [[the-saas-metric-that-matters]] — Sponsor NRR is the newsletter equivalent of SaaS net revenue retention -- [[podcasting-is-relationship-building]] — Podcasts create relationships that often convert to sponsorships -- [[why-b2b-newsletters-work]] — The opt-in dynamic that makes newsletter sponsorship valuable in the first place -- [[b2b-content-is-trust-not-traffic]] — Trust with the audience is what makes sponsorship effective for the sponsor -- [[newsletter-growth-is-about-trust]] — Audience trust is the asset that sponsors are ultimately buying access to diff --git a/demo-vault-v2/the-two-types-of-hard.md b/demo-vault-v2/the-two-types-of-hard.md deleted file mode 100644 index 36857027..00000000 --- a/demo-vault-v2/the-two-types-of-hard.md +++ /dev/null @@ -1,28 +0,0 @@ ---- -aliases: ["The Two Types of Hard"] -Is A: Evergreen -Topics: ["[[topic-productivity-systems]]", "[[topic-mental-health]]"] -Status: Published ---- -# The Two Types of Hard -There are two kinds of difficulty in creative work. The first is the hard of skill — you literally don't know how to do the thing yet. The second is the hard of resistance — you know how, but starting feels uncomfortable. - -Mistaking one for the other is dangerous. If you think resistance is skill gap, you'll spend time learning when you should be shipping. If you think skill gap is resistance, you'll force output when you actually need to learn. - -The tell: skill-gap hard gets easier with study and practice. Resistance hard gets easier with starting. Both are real; neither should be romanticized. - -I encounter both types regularly in running Refactoring, and I have learned to diagnose them through different sensations. Skill-gap hard feels like confusion — I literally do not know what the right approach is, and more effort does not resolve the uncertainty. When I first started negotiating sponsorship contracts, the difficulty was genuine skill gap. No amount of willpower would have helped because I did not understand market rates, deal structures, or negotiation norms. The solution was learning: reading about media sales, talking to other newsletter operators, and making enough mistakes to build a mental model. - -Resistance hard feels different. It feels like avoidance — I know exactly what to do but cannot make myself begin. Writing the opening paragraph of a newsletter issue is almost always resistance hard. I know how to write. I have written hundreds of openings. But the blank page triggers a predictable cycle of checking email, getting coffee, reorganizing my desktop, and generally doing anything other than the one thing I need to do. The solution is not more learning; it is starting, however badly. I have trained myself to write the worst possible opening paragraph as fast as I can, knowing that the act of starting will break the resistance and the paragraph will be rewritten anyway. - -The danger zone is the overlap — tasks that involve both skill gap and resistance simultaneously. Launching a new product, entering an unfamiliar market, or giving a public talk for the first time involve genuine skill gaps wrapped in emotional resistance. The temptation is to address only one: to study endlessly (addressing skill gap while avoiding the resistance of actually doing it) or to force yourself through it without preparation (addressing resistance while ignoring the skill gap). The productive approach is to sequence them: learn enough to have a basic plan, then start despite the discomfort, then learn more from the experience of doing. The cycle of learning-doing-learning is more effective than either pure learning or pure doing. - -## Key insight -The ability to correctly diagnose whether difficulty is skill-based or resistance-based is a meta-skill that determines how effectively you spend your time. Most procrastination in experienced knowledge workers is resistance, not skill gap — and the cure for resistance is always starting, not preparing. Most frustration in new domains is skill gap, not resistance — and the cure for skill gap is learning, not pushing harder. Developing the self-awareness to tell the difference is one of the highest-leverage investments a creative professional can make, because it prevents the two most common failure modes: perpetual preparation and brute-force mediocrity. - -## Related -- [[on-consistency-in-creative-work]] — Consistency is the framework that handles resistance by removing the decision to start -- [[on-founder-energy-management]] — Depleted energy amplifies resistance, making it harder to distinguish from skill gap -- [[cycling-teaches-patience]] — Knowing when to push and when to hold back maps directly to the two types of hard -- [[recovery-week-in-training]] — Sometimes what feels like resistance is actually depletion signaling the need for recovery -- [[note-deep-work]] — Deep work practices as a structure for overcoming resistance diff --git a/demo-vault-v2/theme/dark.md b/demo-vault-v2/theme/dark.md deleted file mode 100644 index 7baed442..00000000 --- a/demo-vault-v2/theme/dark.md +++ /dev/null @@ -1,54 +0,0 @@ ---- -Is A: Theme -Description: Dark variant with deep navy tones -background: "#0f0f1a" -foreground: "#e0e0e0" -card: "#16162a" -popover: "#1e1e3a" -primary: "#155DFF" -primary-foreground: "#FFFFFF" -secondary: "#2a2a4a" -secondary-foreground: "#e0e0e0" -muted: "#1e1e3a" -muted-foreground: "#888888" -accent: "#2a2a4a" -accent-foreground: "#e0e0e0" -destructive: "#f44336" -border: "#2a2a4a" -input: "#2a2a4a" -ring: "#155DFF" -sidebar: "#1a1a2e" -sidebar-foreground: "#e0e0e0" -sidebar-border: "#2a2a4a" -sidebar-accent: "#2a2a4a" -text-primary: "#e0e0e0" -text-secondary: "#888888" -text-muted: "#666666" -text-heading: "#e0e0e0" -bg-primary: "#0f0f1a" -bg-sidebar: "#1a1a2e" -bg-hover: "#2a2a4a" -bg-hover-subtle: "#1e1e3a" -bg-selected: "#155DFF22" -border-primary: "#2a2a4a" -accent-blue: "#155DFF" -accent-green: "#00B38B" -accent-orange: "#D9730D" -accent-red: "#f44336" -accent-purple: "#A932FF" -accent-yellow: "#F0B100" -accent-blue-light: "#155DFF33" -accent-green-light: "#00B38B33" -accent-purple-light: "#A932FF33" -accent-red-light: "#f4433633" -accent-yellow-light: "#F0B10033" -font-family: "'Inter', -apple-system, BlinkMacSystemFont, sans-serif" -font-size-base: 14px -editor-font-size: 16 -editor-line-height: 1.5 -editor-max-width: 720 ---- - -# Dark - -A dark theme with deep navy tones for comfortable night-time reading. diff --git a/demo-vault-v2/theme/default-theme.md b/demo-vault-v2/theme/default-theme.md deleted file mode 100644 index c63d6754..00000000 --- a/demo-vault-v2/theme/default-theme.md +++ /dev/null @@ -1,20 +0,0 @@ ---- -type: Theme -title: Default -primary: "#155DFF" -background: "#1a1a2e" -foreground: "#37352F" -sidebar: "#2a2a3e" -border: "#E9E9E7" -muted: "#F0F0EF" -muted-foreground: "#9B9A97" -accent: "#F0F7FF" -accent-foreground: "#0A3B8F" -font-family: "'Inter', -apple-system, BlinkMacSystemFont, sans-serif" -font-size-base: 14 -line-height-base: 1.6 ---- - -# Default Theme - -Light theme with warm, paper-like tones. \ No newline at end of file diff --git a/demo-vault-v2/theme/default.md b/demo-vault-v2/theme/default.md deleted file mode 100644 index 1066763d..00000000 --- a/demo-vault-v2/theme/default.md +++ /dev/null @@ -1,54 +0,0 @@ ---- -Is A: Theme -Description: Light theme with warm, paper-like tones -background: "#FFFFFF" -foreground: "#37352F" -card: "#FFFFFF" -popover: "#FFFFFF" -primary: "#155DFF" -primary-foreground: "#FFFFFF" -secondary: "#EBEBEA" -secondary-foreground: "#37352F" -muted: "#F0F0EF" -muted-foreground: "#787774" -accent: "#EBEBEA" -accent-foreground: "#37352F" -destructive: "#E03E3E" -border: "#E9E9E7" -input: "#E9E9E7" -ring: "#155DFF" -sidebar: "#F7F6F3" -sidebar-foreground: "#37352F" -sidebar-border: "#E9E9E7" -sidebar-accent: "#EBEBEA" -text-primary: "#37352F" -text-secondary: "#787774" -text-muted: "#B4B4B4" -text-heading: "#37352F" -bg-primary: "#FFFFFF" -bg-sidebar: "#F7F6F3" -bg-hover: "#EBEBEA" -bg-hover-subtle: "#F0F0EF" -bg-selected: "#E8F4FE" -border-primary: "#E9E9E7" -accent-blue: "#155DFF" -accent-green: "#00B38B" -accent-orange: "#D9730D" -accent-red: "#E03E3E" -accent-purple: "#A932FF" -accent-yellow: "#F0B100" -accent-blue-light: "#155DFF14" -accent-green-light: "#00B38B14" -accent-purple-light: "#A932FF14" -accent-red-light: "#E03E3E14" -accent-yellow-light: "#F0B10014" -font-family: "'Inter', -apple-system, BlinkMacSystemFont, sans-serif" -font-size-base: 14px -editor-font-size: 16 -editor-line-height: 1.5 -editor-max-width: 720 ---- - -# Default - -The default light theme for Laputa. Clean and warm, inspired by Notion. diff --git a/demo-vault-v2/theme/minimal.md b/demo-vault-v2/theme/minimal.md deleted file mode 100644 index 4e3ce8a0..00000000 --- a/demo-vault-v2/theme/minimal.md +++ /dev/null @@ -1,53 +0,0 @@ ---- -Is A: Theme -Description: High contrast, minimal chrome -background: "#FAFAFA" -foreground: "#111111" -card: "#FFFFFF" -popover: "#FFFFFF" -primary: "#000000" -primary-foreground: "#FFFFFF" -secondary: "#F0F0F0" -secondary-foreground: "#111111" -muted: "#F5F5F5" -muted-foreground: "#666666" -accent: "#F0F0F0" -accent-foreground: destructive: "#CC0000" -border: "#E0E0E0" -input: "#E0E0E0" -ring: "#000000" -sidebar: "#F5F5F5" -sidebar-foreground: "#111111" -sidebar-border: "#E0E0E0" -sidebar-accent: "#E8E8E8" -text-primary: "#111111" -text-secondary: "#666666" -text-muted: "#999999" -text-heading: "#111111" -bg-primary: "#FAFAFA" -bg-sidebar: "#F5F5F5" -bg-hover: "#EBEBEB" -bg-hover-subtle: "#F5F5F5" -bg-selected: "#00000014" -border-primary: "#E0E0E0" -accent-blue: "#000000" -accent-green: "#006600" -accent-orange: "#996600" -accent-red: "#CC0000" -accent-purple: "#660099" -accent-yellow: "#996600" -accent-blue-light: "#00000014" -accent-green-light: "#00660014" -accent-purple-light: "#66009914" -accent-red-light: "#CC000014" -accent-yellow-light: "#99660014" -font-family: "'SF Mono', 'Menlo', monospace" -font-size-base: 13px -editor-font-size: 15 -editor-line-height: 1.6 -editor-max-width: 680 -title: Minimal ---- -# Minimal - -High contrast, minimal chrome. Monospace typography throughout. diff --git a/demo-vault-v2/topic-ai-ml.md b/demo-vault-v2/topic-ai-ml.md deleted file mode 100644 index cfd745eb..00000000 --- a/demo-vault-v2/topic-ai-ml.md +++ /dev/null @@ -1,27 +0,0 @@ ---- -aliases: ["AI & Machine Learning"] -Is A: Topic ---- -# AI & Machine Learning - -AI and machine learning are reshaping how software is built, how content is created, and how businesses operate. This topic covers the practical side of AI — from LLMs and their applications in content workflows to the broader implications for engineering teams, developer tools, and the future of knowledge work. - -## Why this matters - -As someone writing for engineering leaders, understanding AI is not optional — it is the single most important technology trend affecting the audience. Every newsletter edition touches AI in some form, whether directly or through its second-order effects on team structure, hiring, and product strategy. Staying sharp here means the writing stays relevant and ahead of the curve, rather than parroting surface-level takes. The note [[ai-wont-replace-thinking]] captures a core belief: AI augments judgment, it does not substitute it. - -## Key resources - -- [[note-thinking-fast-and-slow]] — foundational mental models for reasoning about how AI interacts with human cognition -- Simon Willison's blog — consistently the best source for practical LLM insights and experiments -- Andrej Karpathy's talks and posts — deep technical intuition made accessible -- The Gradient podcast — long-form AI research conversations -- [[ai-wont-replace-thinking]] — a personal evergreen note on where AI fits in creative and analytical work - -## Notes - -- The most interesting AI applications for a content business are in research assistance and draft generation, not in replacing the writer -- Engineering teams are adopting AI coding tools faster than leadership realizes, creating a gap between how work is actually done and how it is managed -- LLMs are surprisingly good at structured summarization but consistently bad at nuanced editorial judgment — which is exactly where human writers earn their keep -- The hype cycle around AI means there is a massive opportunity for thoughtful, skeptical-but-informed writing on the topic -- Most B2B companies are still figuring out how to talk about AI to their customers, which creates sponsorship opportunities for newsletters that do it well diff --git a/demo-vault-v2/topic-b2b-marketing.md b/demo-vault-v2/topic-b2b-marketing.md deleted file mode 100644 index aa4d802c..00000000 --- a/demo-vault-v2/topic-b2b-marketing.md +++ /dev/null @@ -1,27 +0,0 @@ ---- -aliases: ["B2B Marketing"] -Is A: Topic ---- -# B2B Marketing - -B2B marketing is the discipline of reaching and persuading business buyers — in this context, specifically developers, engineering leaders, and technical decision-makers. It covers positioning, demand generation, content marketing, and the unique dynamics of selling to people who distrust traditional marketing. - -## Why this matters - -Refactoring's entire business model sits at the intersection of content and B2B marketing. The newsletter is itself a B2B marketing channel for sponsors, and understanding what makes B2B marketing effective (or ineffective) directly informs both the content strategy and the sponsorship pitch. Writing about engineering leadership with credibility is, at its core, a B2B marketing act — one grounded in trust rather than persuasion. The evergreen note [[b2b-content-is-trust-not-traffic]] captures this precisely, and [[why-b2b-newsletters-work]] explains the structural advantage. - -## Key resources - -- [[b2b-content-is-trust-not-traffic]] — the foundational principle behind Refactoring's approach -- [[why-b2b-newsletters-work]] — why email newsletters outperform most B2B channels -- [[note-good-strategy-bad-strategy]] — strategy frameworks that apply directly to B2B positioning -- April Dunford's "Obviously Awesome" — the best book on positioning for technical products -- Lenny Rachitsky's newsletter — a reference point for how B2B content businesses can scale - -## Notes - -- The best B2B marketing does not feel like marketing at all — it feels like useful content from a trusted peer -- Most developer marketing fails because it leads with features instead of problems, and with hype instead of honesty -- Sponsorship-funded newsletters work because they align incentives: the reader gets free content, the sponsor gets trusted distribution, the creator gets independence -- The line between editorial and advertising is critical to maintain — once readers sense compromise, trust erodes and open rates follow -- B2B content marketing is a long game; the compounding effects described in [[the-compound-effect-in-knowledge-work]] apply here directly diff --git a/demo-vault-v2/topic-content-strategy.md b/demo-vault-v2/topic-content-strategy.md deleted file mode 100644 index baeaa490..00000000 --- a/demo-vault-v2/topic-content-strategy.md +++ /dev/null @@ -1,27 +0,0 @@ ---- -aliases: ["Content Strategy"] -Is A: Topic ---- -# Content Strategy - -Content strategy is the practice of planning, creating, and distributing content that serves both the audience and the business. For a newsletter-first operation like Refactoring, it means deciding what to write about, in what format, at what cadence, and through which channels — all in service of building trust, growing the audience, and sustaining revenue. - -## Why this matters - -Content strategy is not a side concern for Refactoring — it is the business. Every decision about what to publish, how to frame it, and where to distribute it directly affects subscriber growth, reader engagement, and sponsorship value. Getting strategy right means the weekly writing effort compounds over time instead of feeling like a treadmill. The evergreen note [[the-real-job-of-a-newsletter]] grounds the strategy in a clear purpose, and [[on-consistency-in-creative-work]] is a reminder that showing up reliably matters more than occasional brilliance. - -## Key resources - -- [[the-real-job-of-a-newsletter]] — defining what the newsletter is actually for, beyond "content" -- [[on-consistency-in-creative-work]] — why cadence and reliability trump sporadic quality -- [[note-essentialism]] — a framework for saying no to content ideas that dilute focus -- [[note-show-your-work]] — Austin Kleon's case for sharing the process, not just the output -- Stacking the Bricks by Amy Hoy — practical thinking on building an audience through useful content - -## Notes - -- The best content strategy for a solo creator is simple: pick a niche, publish consistently, and let compounding do the work -- Pillar content (deep, reusable essays) should drive the calendar, with timely takes layered on top — not the other way around -- Repurposing is underrated: a single essay can become a newsletter edition, a LinkedIn post, a podcast episode prompt, and a thread -- The temptation to chase trending topics is real but usually counterproductive — the audience subscribed for a specific point of view, not for news -- Distribution matters as much as creation, but it is the part most writers neglect because it feels less creative diff --git a/demo-vault-v2/topic-cooking.md b/demo-vault-v2/topic-cooking.md deleted file mode 100644 index 011880ec..00000000 --- a/demo-vault-v2/topic-cooking.md +++ /dev/null @@ -1,27 +0,0 @@ ---- -aliases: ["Cooking"] -Is A: Topic ---- -# Cooking - -Cooking covers Italian home cooking, meal preparation, and the ongoing experiment of making good food efficiently. It spans traditional recipes, weeknight shortcuts, and the occasional ambitious weekend project — always with an emphasis on fresh ingredients, simplicity, and the quiet satisfaction of feeding yourself and others well. - -## Why this matters - -Cooking is one of the few activities that is genuinely restorative after a day of knowledge work. It engages the hands and senses in a way that writing and coding do not, and it forces presence — you cannot think about newsletter metrics while searing a steak. It also connects directly to [[topic-nutrition]], since controlling what goes into meals is the most reliable lever for eating well as an endurance athlete. Beyond the personal benefits, the discipline of following a recipe precisely or improvising with constraints is a surprisingly good analogy for creative work. - -## Key resources - -- Marcella Hazan's "Essentials of Classic Italian Cooking" — the definitive reference for Italian home cooking -- Salt Fat Acid Heat by Samin Nosrat — foundational principles that make improvisation possible -- Serious Eats (J. Kenji Lopez-Alt) — the best resource for technique-driven home cooking -- Italia Squisita (YouTube) — Italian chefs explaining traditional recipes with precision -- [[topic-nutrition]] — the complementary topic on how food choices affect training and cognitive performance - -## Notes - -- The best weeknight meals have five or fewer ingredients and take under 30 minutes — complexity is not the same as quality -- Meal prep on Sunday saves decision energy during the week, but it works only when the recipes are things you actually want to eat on Thursday -- Italian cooking at its best is an exercise in restraint: good ingredients, minimal interference, and respect for the technique -- Cooking for others is an underrated form of generosity and connection — it builds relationships in a way that a dinner reservation does not -- The overlap between cooking and engineering is real: both involve managing heat, timing, and dependencies in sequence diff --git a/demo-vault-v2/topic-cycling-training.md b/demo-vault-v2/topic-cycling-training.md deleted file mode 100644 index fb9df6fe..00000000 --- a/demo-vault-v2/topic-cycling-training.md +++ /dev/null @@ -1,27 +0,0 @@ ---- -aliases: ["Cycling Training"] -Is A: Topic ---- -# Cycling Training - -Cycling training covers the structured pursuit of road cycling performance — training plans, periodization, nutrition on the bike, gear decisions, and race preparation for gran fondos and long-distance rides. It is the primary physical discipline and a significant part of life outside work. - -## Why this matters - -Cycling is more than fitness — it is a forcing function for discipline, patience, and long-term thinking. The parallels with building a business are surprisingly direct: you cannot rush base fitness any more than you can rush audience growth, and the athletes who recover well outperform those who simply train more. The evergreen note [[cycling-teaches-patience]] captures this. Training also provides the physical foundation described in [[responsibility-health-fitness]], and the interplay between training load and knowledge work explored in [[training-load-and-knowledge-work]] is a constant balancing act. - -## Key resources - -- [[cycling-teaches-patience]] — the mental model that links cycling discipline to creative work -- [[training-load-and-knowledge-work]] — how physical training volume affects cognitive output -- [[recovery-week-in-training]] — why periodic deloads are non-negotiable for sustained progress -- [[note-born-to-run]] — book notes on endurance, though focused on running, the principles transfer -- TrainerRoad and TrainingPeaks — the tools used for structured training plans and performance tracking - -## Notes - -- Structured training with clear intensity zones produces better results than riding hard every day — polarized training works -- Gran fondo preparation requires at least 12 weeks of dedicated build, and skipping the base phase always shows up on race day -- Nutrition on the bike is the most overlooked performance lever for amateur cyclists — fueling properly transforms long rides -- Indoor training on the smart trainer is efficient but mentally taxing; mixing it with outdoor rides keeps motivation high -- The best cycling season starts with a proper off-season: rest, strength work, and zero guilt about lower volume diff --git a/demo-vault-v2/topic-data-engineering.md b/demo-vault-v2/topic-data-engineering.md deleted file mode 100644 index b13eaefb..00000000 --- a/demo-vault-v2/topic-data-engineering.md +++ /dev/null @@ -1,27 +0,0 @@ ---- -aliases: ["Data Engineering"] -Is A: Topic ---- -# Data Engineering - -Data engineering covers the infrastructure and practices behind moving, transforming, and serving data at scale — data pipelines, the modern data stack, analytics engineering, and the organizational challenges of making data useful. It remains a core area of technical knowledge from earlier career experience and a frequent topic in Refactoring content. - -## Why this matters - -Data engineering was a formative part of the professional journey before Refactoring, and the audience for the newsletter includes a large contingent of data and platform engineers. Writing credibly about engineering leadership requires staying current on how data teams work, what tools they use, and what problems they face. It also informs the broader perspective on [[topic-developer-tools]] and [[topic-saas-business]], since much of the modern data stack is built by venture-backed SaaS companies with interesting business dynamics. - -## Key resources - -- "Fundamentals of Data Engineering" by Joe Reis and Matt Housley — the best modern textbook on the field -- The Data Engineering Podcast — consistent coverage of tools, practices, and industry trends -- dbt (data build tool) documentation and community — the most influential tool in modern analytics engineering -- [[topic-developer-tools]] — the overlapping topic on how tools for engineers are built and sold -- Maxime Beauchemin's blog posts — foundational writing on data pipeline architecture from the creator of Airflow - -## Notes - -- The modern data stack hype cycle has peaked, and the industry is consolidating around fewer, more integrated tools — this is healthy -- Data engineering is one of the few engineering disciplines where the organizational problem (who owns the data, who defines metrics) is harder than the technical problem -- The best data teams treat data pipelines as software engineering problems, not as ETL scripts — testing, version control, and CI/CD apply -- Analytics engineering as a discipline (bridging data engineering and analytics) has been one of the most important organizational innovations in tech in recent years -- Many Refactoring readers work at the intersection of data and platform engineering, making this a consistently high-engagement topic diff --git a/demo-vault-v2/topic-developer-tools.md b/demo-vault-v2/topic-developer-tools.md deleted file mode 100644 index 3f5a5998..00000000 --- a/demo-vault-v2/topic-developer-tools.md +++ /dev/null @@ -1,27 +0,0 @@ ---- -aliases: ["Developer Tools"] -Is A: Topic ---- -# Developer Tools - -Developer tools covers the landscape of products built for software engineers — IDEs, CI/CD platforms, observability tools, code review systems, and the emerging category of AI-assisted development. It also encompasses developer experience (DevEx) as a discipline and the unique business dynamics of selling to engineers. - -## Why this matters - -Developer tools are both a frequent editorial topic for Refactoring and a major category for newsletter sponsors. Understanding what makes a great developer tool — and what makes engineers adopt or reject one — is essential for writing credibly about engineering productivity and for positioning sponsorship offerings to DevTool companies. The overlap with [[topic-ai-ml]] is growing rapidly as AI-powered coding assistants reshape the category. The open-source angle explored in [[open-source-as-marketing]] is particularly relevant here, since many DevTool companies use open source as their primary go-to-market strategy. - -## Key resources - -- [[open-source-as-marketing]] — how open source functions as a distribution strategy for developer tools -- [[topic-ai-ml]] — the intersection of AI and developer tooling is the fastest-moving area -- [[note-zero-to-one]] — Thiel's frameworks on competition and differentiation apply directly to crowded DevTool markets -- The Pragmatic Engineer newsletter by Gergely Orosz — a peer publication that covers DevTools and engineering practices extensively -- Developer experience research from DX (Abi Noda's team) — the most rigorous work on measuring developer productivity - -## Notes - -- The best developer tools win by reducing friction in a workflow engineers already have, not by inventing a new workflow from scratch -- Selling to developers requires a bottoms-up adoption motion — top-down enterprise sales alone will not work for tools that live in the daily coding workflow -- DevEx as a discipline is still maturing; most companies conflate "developer productivity" with "more features shipped faster," which misses the point -- AI coding assistants are the biggest disruption to the DevTool category since Git — the incumbents that integrate AI well will survive, the rest will be displaced -- Sponsorship demand from DevTool companies is strong because they have clear, measurable acquisition metrics and a well-defined ICP (individual contributor engineers) diff --git a/demo-vault-v2/topic-italian-startups.md b/demo-vault-v2/topic-italian-startups.md deleted file mode 100644 index efb653fe..00000000 --- a/demo-vault-v2/topic-italian-startups.md +++ /dev/null @@ -1,27 +0,0 @@ ---- -aliases: ["Italian Startup Ecosystem"] -Is A: Topic ---- -# Italian Startup Ecosystem - -The Italian startup ecosystem covers the state of technology entrepreneurship in Italy — venture funding, talent availability, cultural attitudes toward risk, regulatory environment, and the growing but still underweight presence of Italian startups on the European and global stage. It includes observations from both inside and outside the ecosystem. - -## Why this matters - -Being based in Italy and running a tech media business gives a unique vantage point on the Italian startup scene. The ecosystem is small enough that personal connections matter enormously, and large enough that interesting things are genuinely happening. Writing about Italian startups for an international audience helps bridge a gap — most English-language tech media ignores Southern Europe entirely. The evergreen note [[italian-startup-ecosystem-observations]] captures the key structural observations, and several podcast guests have come from the Italian tech community. - -## Key resources - -- [[italian-startup-ecosystem-observations]] — distilled observations on what makes the Italian ecosystem distinct -- Italian Tech Alliance — the main industry body tracking funding data and policy -- Startup Italia and Italian Tech (La Stampa) — the primary Italian-language media covering the scene -- [[topic-saas-business]] — many Italian startups are building B2B SaaS, and the business model dynamics apply -- Events: Italian Tech Week (Turin), Web Summit (for the European context) - -## Notes - -- The Italian ecosystem suffers more from a lack of ambition than a lack of talent — the engineering skill is there, but the default career path still favors corporate roles over startups -- Venture funding in Italy has grown significantly but remains a fraction of France, Germany, or the UK — the gap is primarily at Series A and beyond -- Remote work has been a net positive for Italian tech talent, allowing engineers to work for international companies while staying in Italy and occasionally contributing to local startups -- The best Italian startups tend to have at least one founder with significant international experience, which provides the network and mindset that the domestic ecosystem alone does not yet supply -- There is a real opportunity for a content-native media brand focused on Italian tech — the space is underserved in both Italian and English diff --git a/demo-vault-v2/topic-mental-health.md b/demo-vault-v2/topic-mental-health.md deleted file mode 100644 index 3f982ad4..00000000 --- a/demo-vault-v2/topic-mental-health.md +++ /dev/null @@ -1,27 +0,0 @@ ---- -aliases: ["Mental Health"] -Is A: Topic ---- -# Mental Health - -Mental health covers stress management, emotional wellbeing, work-life boundaries, and the psychological challenges that come with running a business as an indie founder. It encompasses both the practical tactics for staying grounded and the broader conversation about vulnerability, burnout, and sustainable ambition. - -## Why this matters - -The founder journey is psychologically demanding in ways that are rarely discussed honestly. Running Refactoring means shouldering revenue targets, creative output pressure, and team responsibility simultaneously — with no corporate safety net. Understanding mental health is not a luxury but a prerequisite for longevity in this work. The evergreen notes [[on-founder-energy-management]] and [[the-two-types-of-hard]] directly address the emotional texture of this life. Sleep and recovery, covered in [[topic-sleep-recovery]], are the physical foundations, but the psychological layer — managing anxiety, maintaining perspective, knowing when to push and when to rest — is equally critical. - -## Key resources - -- [[on-founder-energy-management]] — managing the finite resource of founder energy across competing demands -- [[the-two-types-of-hard]] — distinguishing between productive struggle and destructive stress -- [[sleeping-more-is-a-superpower]] — the connection between rest and mental resilience -- [[note-deep-work]] — Cal Newport's framework for protecting attention, which is as much about mental health as productivity -- The Huberman Lab podcast — evidence-based protocols for stress, anxiety, and emotional regulation - -## Notes - -- The biggest mental health risk for indie founders is not dramatic burnout but chronic low-grade depletion — it accumulates quietly until output quality noticeably drops -- Regular physical exercise (especially cycling) is the single most effective intervention for maintaining emotional equilibrium, ahead of any app or technique -- Having a small team helps enormously — the loneliness of solo founding is real, and even a team of three creates enough social structure to stay grounded -- The newsletter audience responds strongly to honest writing about the hard parts of building — it creates trust and signals that the content is written by a real person, not a brand -- Setting hard boundaries on work hours is not about discipline but about creating the conditions for sustainable output over years, not months diff --git a/demo-vault-v2/topic-music-guitar.md b/demo-vault-v2/topic-music-guitar.md deleted file mode 100644 index 986c0730..00000000 --- a/demo-vault-v2/topic-music-guitar.md +++ /dev/null @@ -1,27 +0,0 @@ ---- -aliases: ["Music & Guitar"] -Is A: Topic ---- -# Music & Guitar - -Music and guitar covers the practice of playing guitar, learning music theory, discovering new music, and the deep satisfaction of making sounds with your hands. It is a purely personal pursuit — no content angle, no monetization — which is precisely what makes it valuable. - -## Why this matters - -Guitar is the counterweight to a life spent in front of screens. It engages a completely different set of cognitive and motor skills, and the feedback loop is immediate: you hear the result of your effort in real time, with no analytics dashboard or subscriber count in between. Playing music also exercises a kind of patient, incremental skill-building that mirrors the philosophy described in [[on-consistency-in-creative-work]] — you do not get better at guitar by reading about guitar, you get better by practicing every day. Having a creative outlet with zero professional stakes is essential for long-term mental health and prevents the kind of identity collapse where everything in life becomes about the business. - -## Key resources - -- Justin Guitar (justinguitar.com) — the gold standard for free online guitar instruction -- Rick Beato's YouTube channel — music theory, ear training, and analysis for curious players -- "The Music Lesson" by Victor Wooten — a philosophically rich book about musicianship beyond technique -- Ultimate Guitar (tabs and community) — the practical resource for learning songs -- [[topic-mental-health]] — the broader context of why non-work hobbies matter for founder wellbeing - -## Notes - -- Learning guitar as an adult requires accepting that progress is slow and non-linear — which is humbling and healthy in equal measure -- Playing even 15 minutes a day produces meaningful improvement over months; the habit matters far more than the session length -- Music theory is optional but transformative — understanding why a chord progression works changes how you hear everything -- The best practice sessions alternate between learning new material and playing things you already know well, to balance challenge with enjoyment -- There is an interesting parallel between improvising on guitar and writing: both require internalizing structure so deeply that you can riff on it without thinking diff --git a/demo-vault-v2/topic-newsletter-growth.md b/demo-vault-v2/topic-newsletter-growth.md deleted file mode 100644 index 82178145..00000000 --- a/demo-vault-v2/topic-newsletter-growth.md +++ /dev/null @@ -1,27 +0,0 @@ ---- -aliases: ["Newsletter Growth"] -Is A: Topic ---- -# Newsletter Growth - -Newsletter growth covers the strategies, experiments, and hard-won learnings about building an email newsletter audience from zero to scale. It spans organic growth, referral mechanics, paid acquisition, cross-promotions, SEO, and the ongoing work of turning casual readers into loyal subscribers who open every edition. - -## Why this matters - -Growing the Refactoring subscriber base is the single most important business lever. Subscriber count directly determines sponsorship pricing power, and a healthy, engaged list creates compounding returns across every dimension — content reach, brand credibility, and revenue. This topic is also one of the most-requested by the newsletter audience itself, since many readers are building their own newsletters or content businesses. The evergreen note [[newsletter-growth-is-about-trust]] captures the core thesis, and the operational side lives in [[responsibility-grow-newsletter]]. - -## Key resources - -- [[newsletter-growth-is-about-trust]] — the foundational principle that genuine trust drives sustainable growth -- [[newsletter-subject-lines]] — specific observations on what drives opens, the most immediate growth lever -- [[the-real-job-of-a-newsletter]] — understanding what the newsletter actually does clarifies how to grow it -- Newsletter Operator by Matt McGarry — the best tactical resource on newsletter growth strategies -- SparkLoop and Beehiiv communities — practical benchmarks and referral program mechanics - -## Notes - -- Organic growth through consistently excellent content is slower but produces a higher-quality list than any paid channel -- Referral programs work, but only when the incentives are compelling and the ask is easy — most referral programs are set-and-forget and underperform as a result -- Subject lines are the most underrated growth lever because they directly affect open rate, which in turn affects deliverability, which in turn affects whether new subscribers ever see the content -- Cross-promotions with complementary newsletters (non-competing, overlapping audience) are the highest-ROI paid growth channel for B2B newsletters -- The biggest mistake in newsletter growth is optimizing for subscriber count instead of engagement — a smaller, engaged list outperforms a large, disengaged one on every metric that matters diff --git a/demo-vault-v2/topic-nutrition.md b/demo-vault-v2/topic-nutrition.md deleted file mode 100644 index 19aa33da..00000000 --- a/demo-vault-v2/topic-nutrition.md +++ /dev/null @@ -1,27 +0,0 @@ ---- -aliases: ["Nutrition"] -Is A: Topic ---- -# Nutrition - -Nutrition covers the intersection of eating well as an endurance athlete and as a knowledge worker — meal preparation, macronutrient balance, fueling for training, and the daily habits that support both physical performance and cognitive sharpness. It is practical and habit-oriented rather than dogmatic about any specific diet. - -## Why this matters - -What you eat directly affects both cycling performance and writing quality. Under-fueling before a ride leads to poor sessions and missed training adaptations. Eating poorly during the work week leads to afternoon energy crashes that kill the deep focus needed for writing. Getting nutrition right is a force multiplier across both [[responsibility-health-fitness]] and [[responsibility-content-production]], and the connection between physical and cognitive performance is one of the themes explored in [[training-load-and-knowledge-work]]. - -## Key resources - -- [[training-load-and-knowledge-work]] — how physical demands and nutrition interact with cognitive output -- [[topic-cycling-training]] — the athletic context that drives specific nutritional needs -- [[note-atomic-habits]] — the habit-formation framework that makes good nutrition sustainable -- "Racing Weight" by Matt Fitzgerald — the best evidence-based book on nutrition for endurance athletes -- Examine.com — the most trustworthy, non-commercial source for nutrition science summaries - -## Notes - -- The simplest effective nutrition strategy is: enough protein, enough carbs around training, plenty of vegetables, and not overthinking the rest -- Meal prep is the single most reliable way to eat well during the work week — the decision is made once on Sunday, not five times per day -- Hydration is consistently underrated as a performance and cognition lever — even mild dehydration measurably impairs both -- Cutting weight for cycling season requires a careful, gradual approach to avoid losing power and wrecking training quality -- The nutrition industry is 90% marketing and 10% science — the best strategy is to ignore most of it and focus on consistent basics diff --git a/demo-vault-v2/topic-open-source.md b/demo-vault-v2/topic-open-source.md deleted file mode 100644 index f1fde1a6..00000000 --- a/demo-vault-v2/topic-open-source.md +++ /dev/null @@ -1,27 +0,0 @@ ---- -aliases: ["Open Source"] -Is A: Topic ---- -# Open Source - -Open source covers the culture, economics, and practice of building and contributing to open-source software. It spans community dynamics, licensing models, sustainability challenges, and the increasingly important role of open source as a go-to-market strategy for developer-facing companies. - -## Why this matters - -Open source sits at the intersection of several threads that matter for Refactoring: engineering culture, developer tools, and B2B business models. Many of the companies that sponsor the newsletter are open-source-first, and understanding how open source functions as both a product strategy and a community-building tool makes the editorial and sponsorship work more informed. The evergreen note [[open-source-as-marketing]] captures the key insight — open source is often the most effective distribution channel for developer tools. For the newsletter audience, open source is a deeply held value, and writing about it with nuance (not just cheerleading) builds credibility. - -## Key resources - -- [[open-source-as-marketing]] — how open source functions as distribution and trust-building for companies -- [[topic-developer-tools]] — the DevTool category where open source is most prevalent as a strategy -- "Working in Public" by Nadia Eghbal — the definitive book on open-source community dynamics and maintainer burnout -- The Changelog podcast — long-running, thoughtful coverage of the open-source world -- [[note-show-your-work]] — the philosophy of building in public, which shares DNA with open source - -## Notes - -- The open-source sustainability problem is real but often misframed — the issue is not that people will not pay, but that the value capture mechanisms for maintainers are poorly designed -- Open-source licenses matter more than most developers realize, especially when VC-backed companies change licenses after building a community (the "bait and switch" pattern) -- Contributing to open source is one of the best career investments a developer can make — it builds skills, reputation, and network simultaneously -- The tension between open-source idealism and commercial reality is a rich topic for newsletter content, and the audience has strong opinions on it -- Most successful open-source business models follow the "open core" pattern: the core is free, and the enterprise features (SSO, audit logs, compliance) are paid diff --git a/demo-vault-v2/topic-personal-finance.md b/demo-vault-v2/topic-personal-finance.md deleted file mode 100644 index eb40c861..00000000 --- a/demo-vault-v2/topic-personal-finance.md +++ /dev/null @@ -1,27 +0,0 @@ ---- -aliases: ["Personal Finance & Investing"] -Is A: Topic ---- -# Personal Finance & Investing - -Personal finance and investing covers the principles and practices of managing money for long-term wealth building — index fund investing, portfolio allocation, savings discipline, tax optimization, and the philosophical underpinnings of financial independence. The approach is rooted in simplicity, low costs, and patience. - -## Why this matters - -Financial independence is what makes it possible to run Refactoring without taking VC money or making desperate compromises for revenue. A high savings rate and a boring investment portfolio create the runway and psychological safety to make long-term decisions in the business. The evergreen notes [[index-funds-and-intellectual-humility]] and [[investing-in-yourself-vs-markets]] capture two complementary ideas: most people should stick to index funds, and the best investment for an indie founder is often putting money back into the business. This topic also connects directly to [[responsibility-personal-finance]], where the operational side lives. - -## Key resources - -- [[index-funds-and-intellectual-humility]] — why passive investing is both financially and intellectually sound -- [[investing-in-yourself-vs-markets]] — the case for self-investment as the highest-returning asset class -- [[note-thinking-fast-and-slow]] — Kahneman's work on cognitive biases is essential reading for any investor -- "The Simple Path to Wealth" by JL Collins — the most practical guide to index fund investing -- Ben Felix's YouTube channel and podcast — evidence-based investing advice, no hype - -## Notes - -- The single most important financial decision for an indie founder is keeping a high savings rate — it buys time, options, and peace of mind -- Index fund investing works precisely because it requires no skill, no market timing, and no emotional decision-making — which is exactly what makes it psychologically difficult -- The Italian tax system adds complexity to investment decisions, especially around capital gains and the differences between ETFs domiciled in various jurisdictions -- Financial independence is not about retiring early — it is about reaching the point where work is a choice rather than a necessity, which changes every decision for the better -- Writing about personal finance for the newsletter audience is tricky because income levels vary enormously, but the principles (save more, invest simply, be patient) are universal diff --git a/demo-vault-v2/topic-podcasting.md b/demo-vault-v2/topic-podcasting.md deleted file mode 100644 index 8a1568fd..00000000 --- a/demo-vault-v2/topic-podcasting.md +++ /dev/null @@ -1,27 +0,0 @@ ---- -aliases: ["Podcasting"] -Is A: Topic ---- -# Podcasting - -Podcasting covers the craft and business of producing a tech-focused interview podcast — from guest selection and interview technique to production workflow, promotion strategies, and monetization. It encompasses both the creative side (what makes a great conversation) and the operational side (how to ship episodes consistently). - -## Why this matters - -The Refactoring podcast is a core part of the content ecosystem, and understanding podcasting as a craft directly affects the quality and impact of every episode. A good podcast builds relationships with guests that extend well beyond the recording, creates content that reaches people who prefer audio over text, and strengthens the brand in ways the newsletter alone cannot. The evergreen notes [[podcasting-is-relationship-building]] and [[what-makes-a-good-podcast-guest]] capture the key editorial principles, and the operational side lives in [[responsibility-podcast]]. - -## Key resources - -- [[podcasting-is-relationship-building]] — the insight that podcast value extends far beyond download numbers -- [[what-makes-a-good-podcast-guest]] — the selection criteria that lead to great conversations -- [[responsibility-podcast]] — the operational responsibility covering the full production pipeline -- "Out on the Wire" by Jessica Abel — a narrative exploration of storytelling in audio -- The Tim Ferriss Show and Lenny's Podcast — reference points for long-form tech interview formats that work - -## Notes - -- The most important decision in podcasting is guest selection — a mediocre host with a great guest produces better content than a great host with a mediocre guest -- Audio quality matters more than most indie podcasters think, but less than audio engineers think — invest in a good microphone and quiet room, skip the professional studio -- Podcast growth is slow and almost entirely driven by word of mouth and cross-promotion — there is no SEO equivalent for audio, which makes the newsletter cross-promotion channel invaluable -- The best interview technique is genuine curiosity combined with preparation — knowing enough to ask sharp follow-ups, but not so much that the conversation feels rehearsed -- Monetizing a niche podcast is more about sponsorship fit than download volume — a small, highly targeted audience is worth more to the right sponsor than a large, generic one diff --git a/demo-vault-v2/topic-product-management.md b/demo-vault-v2/topic-product-management.md deleted file mode 100644 index 7b2b10e6..00000000 --- a/demo-vault-v2/topic-product-management.md +++ /dev/null @@ -1,27 +0,0 @@ ---- -aliases: ["Product Management"] -Is A: Topic ---- -# Product Management - -Product management covers the discipline of deciding what to build, why, and in what order — prioritization frameworks, user research, product strategy, and the organizational dynamics between product, engineering, and design. It is a topic of ongoing interest both as a former practitioner and as a newsletter writer covering engineering leadership. - -## Why this matters - -A large portion of the Refactoring audience works closely with product managers or holds PM-adjacent roles, and the interface between engineering and product is one of the most fertile areas for newsletter content. Understanding product thinking also makes Refactoring itself better — treating the newsletter as a product with users, retention metrics, and a roadmap is a perspective that sharpens decision-making. The frameworks from [[note-essentialism]] and [[note-good-strategy-bad-strategy]] apply directly to product prioritization, and the PM-engineering relationship is a recurring theme in podcast conversations. - -## Key resources - -- [[note-good-strategy-bad-strategy]] — the most useful strategy framework for product decisions -- [[note-essentialism]] — the discipline of doing less, better — directly applicable to product scope -- [[note-the-lean-startup]] — foundational thinking on validated learning and iterative product development -- "Inspired" by Marty Cagan — the standard reference on how to run a product organization -- Lenny's Newsletter — the go-to publication covering product management in depth - -## Notes - -- The best product managers are not feature factories — they spend more time defining the problem than designing the solution -- Most product prioritization frameworks (RICE, ICE, etc.) are useful as structured thinking exercises, not as objective decision-making tools — the numbers are always estimates -- The tension between engineering-led and product-led organizations is a false binary; the best teams have strong voices on both sides with a shared understanding of goals -- Roadmaps are communication tools, not commitments — the most important thing about a roadmap is that it reflects current thinking and gets updated regularly -- Writing about product management for an engineering audience requires respecting the engineering perspective — engineers are skeptical of PM frameworks for good reasons, and the best writing acknowledges that diff --git a/demo-vault-v2/topic-productivity-systems.md b/demo-vault-v2/topic-productivity-systems.md deleted file mode 100644 index 08c90be3..00000000 --- a/demo-vault-v2/topic-productivity-systems.md +++ /dev/null @@ -1,27 +0,0 @@ ---- -aliases: ["Productivity Systems"] -Is A: Topic ---- -# Productivity Systems - -Productivity systems covers personal knowledge management, task management, note-taking workflows, deep work practices, and the tools and habits that help a knowledge worker produce meaningful output consistently. It is as much about the philosophy of attention and intention as it is about specific tools or methods. - -## Why this matters - -Running a content business solo (with a small team) demands an unusually high level of personal organization. There is no manager setting priorities, no sprint planning meeting — just the daily decision of what to work on and the discipline to follow through. A good productivity system is the scaffolding that makes this possible. The evergreen note [[knowledge-management-is-not-filing]] captures a key insight: the point of a knowledge system is not to organize information but to surface it when it matters. The Laputa app itself is an expression of this philosophy — building the exact tool needed to manage a vault of thousands of notes and ideas. - -## Key resources - -- [[knowledge-management-is-not-filing]] — the core principle behind a useful PKM system -- [[the-compound-effect-in-knowledge-work]] — how small, consistent efforts in note-taking and organization compound over time -- [[note-deep-work]] — Cal Newport's framework for protecting focused attention -- [[note-atomic-habits]] — the habit-formation system that makes productivity sustainable -- "Building a Second Brain" by Tiago Forte — the PARA method and the concept of intermediate packets - -## Notes - -- The best productivity system is the one you actually use consistently — sophistication means nothing if the system is abandoned after two weeks -- Deep work is the highest-value activity in a content business, and protecting blocks of uninterrupted time is worth more than any tool or framework -- Most people over-invest in capture and under-invest in retrieval — the value of a note is realized when you find it again at the right moment, not when you write it -- Task management and knowledge management serve different purposes and should not be forced into the same tool — tasks are ephemeral, knowledge is durable -- The meta-trap of productivity systems is spending more time optimizing the system than doing the work it is supposed to enable — a trap worth guarding against actively diff --git a/demo-vault-v2/topic-public-speaking.md b/demo-vault-v2/topic-public-speaking.md deleted file mode 100644 index 2352a324..00000000 --- a/demo-vault-v2/topic-public-speaking.md +++ /dev/null @@ -1,27 +0,0 @@ ---- -aliases: ["Public Speaking"] -Is A: Topic ---- -# Public Speaking - -Public speaking covers the craft of preparing and delivering talks at conferences, meetups, and company events — from structuring a narrative and designing slides to managing stage nerves and engaging an audience. It is a skill developed through practice rather than natural talent, and one that compounds in value over time. - -## Why this matters - -Public speaking is one of the highest-leverage activities for building a personal brand and expanding the Refactoring audience. A single well-delivered conference talk can generate hundreds of newsletter signups, open doors to podcast guests, and establish credibility with sponsors. It also forces a level of clarity in thinking that writing alone does not — when you have to explain an idea on stage with no backspace key, you discover quickly whether you truly understand it. The themes explored in [[writing-for-clarity-vs-writing-for-credit]] apply equally to speaking: the goal is to be understood, not to impress. - -## Key resources - -- [[writing-for-clarity-vs-writing-for-credit]] — the principle of communicating for understanding, applicable to both writing and speaking -- [[note-show-your-work]] — the philosophy of sharing openly, which translates naturally to the stage -- [[note-on-writing-well]] — Zinsser's principles of clarity and simplicity apply to spoken communication equally -- "Talk Like TED" by Carmine Gallo — practical techniques for structuring and delivering memorable presentations -- Speaking.io by Zach Holman — the best free resource on the logistics and craft of conference speaking - -## Notes - -- The biggest mistake in conference talks is trying to cover too much — one clear idea, well-developed, is worth more than five ideas rushed through -- Nerves never fully go away, but they become manageable with repetition — the 10th talk is dramatically less stressful than the 1st -- Storytelling is the most effective structure for a technical talk, more effective than a list of tips or a tour of a tool — stories create emotional engagement that bullet points cannot -- Slides should support the speaker, not replace them — if the slides make sense without narration, the talk is probably a blog post in disguise -- The Q&A after a talk is often more valuable than the talk itself for building relationships and understanding what the audience actually cares about diff --git a/demo-vault-v2/topic-reading-books.md b/demo-vault-v2/topic-reading-books.md deleted file mode 100644 index a09630b8..00000000 --- a/demo-vault-v2/topic-reading-books.md +++ /dev/null @@ -1,27 +0,0 @@ ---- -aliases: ["Reading & Books"] -Is A: Topic ---- -# Reading & Books - -Reading and books covers the practice of reading deliberately, choosing what to read wisely, retaining and applying what is read, and the broader role of books as a source of ideas for writing and thinking. It encompasses reading habits, book selection strategies, note-taking from books, and the intersection of reading and content creation. - -## Why this matters - -Reading is the primary input channel for Refactoring's content. Almost every newsletter essay and podcast conversation trace back to an idea encountered in a book, an article, or a research paper. Reading more — and reading better — directly improves the quality and originality of the output. The evergreen note [[reading-more-by-reading-better]] captures the core insight that reading speed matters less than reading strategy. This topic connects tightly to [[responsibility-learning]], which covers the operational side of maintaining a reading habit, and to [[procedure-evergreen-note-writing]], which turns reading into reusable knowledge. - -## Key resources - -- [[reading-more-by-reading-better]] — the principle that strategic reading outperforms speed reading -- [[the-compound-effect-in-knowledge-work]] — why consistent reading compounds into expertise over time -- [[note-range]] — David Epstein's case for reading broadly rather than narrowly, which informs book selection -- [[note-on-writing-well]] — a book that changed how both reading and writing are approached -- Ryan Holiday's reading list newsletter — consistently excellent non-fiction recommendations - -## Notes - -- The most important reading skill is not speed but selection — choosing the right book matters more than finishing every book you start -- Taking notes while reading is non-negotiable for retention; without notes, the half-life of a book's ideas is measured in weeks -- Rereading great books is underrated — the best non-fiction books reveal different things on second and third readings because the reader has changed -- Audiobooks count as reading and are particularly useful for narrative non-fiction; dense analytical books work better in print where you can annotate -- The biggest trap in reading for content creation is the temptation to summarize rather than synthesize — the value is not in retelling what the book says but in connecting it to original thinking diff --git a/demo-vault-v2/topic-running.md b/demo-vault-v2/topic-running.md deleted file mode 100644 index 5088be73..00000000 --- a/demo-vault-v2/topic-running.md +++ /dev/null @@ -1,27 +0,0 @@ ---- -aliases: ["Running"] -Is A: Topic ---- -# Running - -Running covers casual road running, trail running, and the role of running as cross-training for cycling. It is not a primary sport but a complementary one — used for variety, mental clarity, and maintaining aerobic fitness when the bike is not an option. - -## Why this matters - -Running is the most accessible form of exercise when traveling, during bad weather, or when a cycling session is not practical. It provides a different kind of physical stimulus that complements cycling well, especially for general aerobic capacity and mental resilience. The meditative quality of a solo run — no power meter, no route planning, just movement — has a restorative effect that is distinct from structured cycling training. The ideas in [[note-born-to-run]] about human endurance capacity are inspiring, and the parallels between running and knowledge work (steady pace, long effort, the importance of not starting too fast) connect to themes in [[the-two-types-of-hard]]. - -## Key resources - -- [[note-born-to-run]] — Christopher McDougall's exploration of human endurance and the joy of running -- [[topic-cycling-training]] — the primary sport that running complements -- [[recovery-week-in-training]] — the principle of periodic rest that applies across all endurance disciplines -- [[topic-sleep-recovery]] — the recovery side that makes training adaptations possible -- Strava and basic GPS watch — the minimal tooling needed for casual running - -## Notes - -- Running is the best cross-training for cycling because it maintains aerobic fitness while using different muscle groups, reducing overuse injury risk -- Trail running is more engaging than road running and easier on the joints — the varied terrain demands attention that makes the time pass faster -- The risk of running too much as a cyclist is that it can create fatigue that interferes with key cycling sessions — keeping it to 1-2 easy runs per week avoids this -- Running is uniquely good for thinking through problems — the rhythm and lack of required attention (unlike cycling in traffic) free up mental processing in a way few other activities do -- Starting a run is always the hardest part; the mood boost that comes by kilometer two is remarkably reliable diff --git a/demo-vault-v2/topic-saas-business.md b/demo-vault-v2/topic-saas-business.md deleted file mode 100644 index 780d6e23..00000000 --- a/demo-vault-v2/topic-saas-business.md +++ /dev/null @@ -1,27 +0,0 @@ ---- -aliases: ["SaaS Business Models"] -Is A: Topic ---- -# SaaS Business Models - -SaaS business models covers the economics, strategies, and operational patterns of software-as-a-service companies — recurring revenue mechanics, churn dynamics, pricing strategies, customer acquisition, and the metrics that separate healthy SaaS businesses from struggling ones. It is a frequent editorial topic and a core knowledge area for understanding the newsletter's sponsor base. - -## Why this matters - -Most of Refactoring's sponsors are B2B SaaS companies, and understanding how their businesses work makes the sponsorship relationship more productive and the editorial content more credible. Writing about engineering leadership without understanding the business context in which engineering teams operate would be incomplete — and SaaS is the dominant business model for the companies where Refactoring readers work. The evergreen note [[the-saas-metric-that-matters]] cuts through the vanity metrics to focus on what actually indicates business health, and [[topic-b2b-marketing]] covers the marketing side of how these companies reach customers. - -## Key resources - -- [[the-saas-metric-that-matters]] — identifying the single metric that best indicates SaaS business health -- [[note-zero-to-one]] — Thiel's frameworks on monopoly and competition, directly applicable to SaaS strategy -- [[note-the-lean-startup]] — the foundational methodology that most SaaS companies claim to follow -- SaaStr (Jason Lemkin) — the most comprehensive resource on SaaS metrics, sales, and scaling -- Christoph Janz's "Five Ways to Build a $100M Business" — the classic framework for understanding SaaS market sizing - -## Notes - -- Net revenue retention is the single most important metric for a SaaS business — it tells you whether the product gets more valuable to existing customers over time -- Most SaaS companies die not from building the wrong product but from failing to find a scalable, repeatable customer acquisition channel -- Pricing is the most underleveraged growth lever in SaaS — most companies underprice because they are afraid of churn, but the best companies charge more and invest in delivering more value -- The PLG (product-led growth) vs. sales-led debate is largely a false dichotomy — most successful SaaS companies use both, with the mix depending on deal size and buyer persona -- Understanding SaaS economics well enough to discuss them in editorial content makes sponsorship conversations significantly easier, because sponsors see that the newsletter understands their world diff --git a/demo-vault-v2/topic-sleep-recovery.md b/demo-vault-v2/topic-sleep-recovery.md deleted file mode 100644 index d76a05c4..00000000 --- a/demo-vault-v2/topic-sleep-recovery.md +++ /dev/null @@ -1,27 +0,0 @@ ---- -aliases: ["Sleep & Recovery"] -Is A: Topic ---- -# Sleep & Recovery - -Sleep and recovery covers the science and practice of rest — sleep hygiene, recovery protocols for endurance training, and the growing body of evidence showing that rest is not the absence of productivity but a prerequisite for it. It spans both the physical recovery needed for athletic performance and the cognitive recovery needed for sustained creative output. - -## Why this matters - -Sleep is the single highest-leverage intervention available, affecting everything from writing quality to training adaptation to emotional regulation. Running a content business while training for endurance events creates a dual demand on recovery capacity, and cutting sleep to "get more done" is the fastest way to degrade performance on both fronts. The evergreen note [[sleeping-more-is-a-superpower]] captures this directly, and [[recovery-week-in-training]] extends the principle to deliberate deload periods. This topic connects to both [[responsibility-health-fitness]] and [[topic-mental-health]], because inadequate rest undermines both physical and psychological resilience. - -## Key resources - -- [[sleeping-more-is-a-superpower]] — the case for prioritizing sleep above almost everything else -- [[recovery-week-in-training]] — the principle of planned rest applied to training periodization -- [[training-load-and-knowledge-work]] — how recovery mediates the interaction between physical and cognitive demands -- "Why We Sleep" by Matthew Walker — the most comprehensive popular science book on sleep -- The Huberman Lab episodes on sleep — actionable protocols for sleep optimization - -## Notes - -- Eight hours of sleep is not a luxury but a biological requirement — the evidence is overwhelming that performance on less than seven hours is measurably impaired, even when it does not feel that way -- Sleep quality matters as much as quantity; consistency in sleep and wake times is the single most impactful sleep hygiene practice -- Recovery weeks (planned deloads in training) are psychologically difficult because they feel like losing momentum, but they are when the actual adaptation happens -- Naps of 20-30 minutes are a legitimate performance tool during the afternoon, not a sign of laziness — treating them as part of the schedule rather than a guilty indulgence changes the relationship with rest -- The culture of hustle and sleep deprivation in startups is one of the most counterproductive norms in tech — writing honestly about the value of rest resonates strongly with the newsletter audience diff --git a/demo-vault-v2/topic-team-leadership.md b/demo-vault-v2/topic-team-leadership.md deleted file mode 100644 index 8a1161bb..00000000 --- a/demo-vault-v2/topic-team-leadership.md +++ /dev/null @@ -1,27 +0,0 @@ ---- -aliases: ["Team Leadership"] -Is A: Topic ---- -# Team Leadership - -Team leadership covers the art and practice of managing small teams — running effective 1:1s, giving and receiving feedback, building culture in remote and async environments, and making decisions about structure and process that help people do their best work. It is both a daily practice in managing the Refactoring team and a core editorial topic for the newsletter. - -## Why this matters - -Team leadership is arguably the single most important topic for the Refactoring audience. Engineering managers, tech leads, and VPs of engineering are all navigating the same fundamental challenge: how to get the best out of a group of talented, autonomous people without creating bureaucracy. The experience of managing [[person-matteo-cellini]], [[person-paco-furiani]], and [[person-sara-ricci]] provides firsthand material for writing on this topic, and the evergreen note [[small-teams-scale-through-systems]] captures the core philosophy. This topic connects directly to [[responsibility-team-management]] on the operational side. - -## Key resources - -- [[small-teams-scale-through-systems]] — the principle that systems and processes enable small teams to punch above their weight -- [[note-good-strategy-bad-strategy]] — strategic clarity at the team level prevents wasted effort -- [[note-deep-work]] — protecting the team's focus time is a leadership responsibility, not just a personal one -- "The Manager's Path" by Camille Fournier — the definitive guide for engineering management at every level -- "An Elegant Puzzle" by Will Larson — systems thinking applied to engineering organization design - -## Notes - -- The most impactful thing a leader of a small team can do is remove ambiguity — when everyone knows what matters this week and why, execution follows naturally -- 1:1s are the highest-ROI meeting a manager has, and the most common mistake is using them for status updates instead of coaching and relationship building -- Remote teams need more intentional communication rituals, not more meetings — async defaults with periodic sync touchpoints work better than constant video calls -- Feedback is a muscle that atrophies if not exercised regularly; the best teams normalize feedback as a routine part of collaboration, not a high-stakes annual event -- Scaling a team from 3 to 10 people is a qualitatively different challenge than starting with 3 — the communication overhead grows non-linearly, and the leader's role shifts from doing to enabling diff --git a/demo-vault-v2/topic-travel.md b/demo-vault-v2/topic-travel.md deleted file mode 100644 index dfa00dac..00000000 --- a/demo-vault-v2/topic-travel.md +++ /dev/null @@ -1,27 +0,0 @@ ---- -aliases: ["Travel"] -Is A: Topic ---- -# Travel - -Travel covers trips for conferences, cycling events, and personal exploration — discovering new cities, experiencing different cultures, and the logistical art of working remotely from unfamiliar places. It includes both the practical side of travel planning and the broader value of leaving the home routine periodically. - -## Why this matters - -Travel serves multiple purposes in this life. Conference travel builds the professional network and provides material for content — meeting podcast guests, understanding different tech ecosystems, and staying connected to the broader engineering community. Personal travel provides perspective and reset, which is essential for creative work. The Italian context matters here: being based in Italy means European destinations are easily accessible, but meaningful engagement with the US and global tech scene requires deliberate travel planning. Travel also intersects with [[topic-cycling-training]], since some of the best cycling routes are discovered on the road, and with [[topic-cooking]], since food is a central part of how new places are experienced. - -## Key resources - -- [[topic-italian-startups]] — the domestic ecosystem that connects to conference and networking travel in Italy -- [[topic-public-speaking]] — many trips are driven by speaking engagements at conferences -- [[on-founder-energy-management]] — travel is energizing but also draining, and managing it well is part of founder energy management -- Seat61.com — the best resource for European train travel, which is the preferred mode for sustainability and comfort -- Nomad List — useful for evaluating cities for extended stays and co-working options - -## Notes - -- The best conference trips are the ones where the hallway conversations and dinners are more valuable than the scheduled talks -- Working from a different city for a week or two is a form of productive disruption — the change of environment breaks routine patterns and often sparks new ideas -- Cycling trips that double as training camps are the ideal combination of fitness and exploration — loading the bike on a train and riding in a new region is deeply satisfying -- Travel fatigue is cumulative and often underestimated; spacing trips at least two weeks apart preserves both the enjoyment and the ability to produce content consistently -- Italy's geographic position makes it ideal for short European trips, but the timezone gap with US-based contacts and sponsors requires deliberate scheduling when traveling east or west diff --git a/demo-vault-v2/topic-writing.md b/demo-vault-v2/topic-writing.md index 9b0f2766..35013c95 100644 --- a/demo-vault-v2/topic-writing.md +++ b/demo-vault-v2/topic-writing.md @@ -1,27 +1,13 @@ --- -aliases: ["Writing"] -Is A: Topic +type: Topic +aliases: + - "[[Writing]]" --- + # Writing -Writing covers the craft of putting ideas into words clearly, consistently, and for a specific audience. It spans the mechanics of good prose, the habits that sustain a weekly publishing cadence, the editorial mindset needed to serve a technical readership, and the deeper question of what makes writing worth reading in the first place. +The exact-match Quick Open target for search ranking QA. -## Why this matters - -Writing is the core skill of the entire Refactoring operation. Every newsletter edition, every essay, every podcast show note, every sponsor report — all of it depends on the ability to write clearly and persuasively. Improving as a writer is the single highest-leverage investment in the business. The evergreen notes [[writing-for-clarity-vs-writing-for-credit]] and [[on-consistency-in-creative-work]] capture two foundational principles: write to be understood (not to sound smart), and show up reliably (not brilliantly once in a while). This topic connects to [[responsibility-content-production]] on the operational side and to [[topic-reading-books]] on the input side, since the best writers are always avid readers. - -## Key resources - -- [[writing-for-clarity-vs-writing-for-credit]] — the guiding principle for all Refactoring content -- [[on-consistency-in-creative-work]] — why regular publishing matters more than occasional masterpieces -- [[note-on-writing-well]] — William Zinsser's classic, reread annually, on simplicity and humanity in nonfiction prose -- [[note-show-your-work]] — Austin Kleon's manifesto for sharing the creative process openly -- "Draft No. 4" by John McPhee — the best book on the structural craft of nonfiction writing - -## Notes - -- The most common writing mistake in technical content is assuming the reader has the same context as the writer — good technical writing is an exercise in empathy -- Editing is where writing quality actually happens; the first draft is just raw material, and the willingness to cut and restructure separates good writers from average ones -- Writing for a weekly cadence requires accepting that not every piece will be exceptional — the consistent output matters more than individual brilliance, and the average quality rises over time through sheer practice -- Voice is the competitive moat in newsletter writing; tactics and insights can be copied, but a distinctive voice cannot be replicated -- The best way to improve as a writer is to read good writing carefully and to write frequently — there are no shortcuts, and that is both discouraging and liberating +- [[writing-for-clarity-vs-writing-for-credit]] +- [[writing-weekly-rhythm]] +- [[note-on-clear-prose]] diff --git a/demo-vault-v2/topic.md b/demo-vault-v2/topic.md deleted file mode 100644 index 412863ee..00000000 --- a/demo-vault-v2/topic.md +++ /dev/null @@ -1,7 +0,0 @@ ---- -Is A: Type ---- - -# Topic - -A Topic is a subject area for categorization and linking. Topics group related notes, projects, and resources by theme. diff --git a/demo-vault-v2/training-load-and-knowledge-work.md b/demo-vault-v2/training-load-and-knowledge-work.md deleted file mode 100644 index df344f51..00000000 --- a/demo-vault-v2/training-load-and-knowledge-work.md +++ /dev/null @@ -1,30 +0,0 @@ ---- -aliases: ["Training Load and Knowledge Work"] -Is A: Evergreen -Topics: ["[[topic-cycling-training]]", "[[topic-productivity-systems]]"] -Status: Published ---- -# Training Load and Knowledge Work -Endurance athletes understand that adaptation happens during recovery, not during training. You get stronger by stressing the system, then allowing it to rebuild stronger. Skip recovery and you get injured or overtrained. - -Knowledge work follows the same principle. Deep focus creates cognitive load — stress on your attention system. Without recovery (sleep, walks, boredom), you don't consolidate learning, and creativity degrades. - -The best writers, programmers, and thinkers I know are obsessive about protecting recovery. Not because they're lazy, but because they understand the adaptation model. - -In cycling, training load is quantified precisely using metrics like Training Stress Score (TSS), which combines duration and intensity into a single number. Over time, you track Chronic Training Load (fitness), Acute Training Load (fatigue), and the balance between them (form). This framework makes it possible to push hard enough to improve without pushing so hard that you break down. The numbers do not lie. When your fatigue exceeds your fitness by a certain margin, performance degrades regardless of how motivated you feel. - -Knowledge work lacks equivalent metrics, which is both a measurement problem and a management problem. We have no TSS for cognitive work. A day of deep writing, a day of back-to-back meetings, and a day of debugging a complex system all deplete different cognitive resources, but we treat them as interchangeable "work" and manage them by the same crude metric: hours. The result is that most knowledge workers have no idea whether they are in a productive training zone or accumulating a fatigue debt that will surface as burnout in three months. They only discover it after the breakdown, which is like an athlete only discovering overtraining after the injury. - -My attempt to apply training load principles to knowledge work has been imperfect but useful. I track three types of cognitive work — creative (writing, strategy), administrative (email, operations), and social (meetings, calls) — and try to manage the weekly balance between them. A week with 20+ hours of creative work requires less social and administrative load to stay sustainable. A week heavy with meetings requires lighter creative expectations. I also apply the 3:1 principle from cycling: three weeks of progressive load followed by one lighter week. This is not precise science, but it is dramatically better than the default approach of "work as hard as possible until something breaks." - -The deeper principle connecting athletic training and knowledge work is that both are biological processes governed by the stress-adaptation cycle. Your brain, like your muscles, needs progressive overload to grow and recovery to consolidate those gains. The knowledge workers who produce the most over a career are not the ones who work the hardest in any given month. They are the ones who sustain a productive training load across years without burning out. This requires the same periodization discipline that athletes use: structured cycles of intensity and recovery, not a flat line of maximum effort. - -## Key insight -The stress-adaptation model from endurance training is the best available framework for managing knowledge work sustainably. The key principles translate directly: progressive overload (gradually increasing the complexity of the work you take on), periodization (cycling between intense and recovery periods), and respecting recovery as the phase where actual improvement occurs. The main barrier to applying this framework is the absence of quantitative metrics for cognitive load, which means knowledge workers must rely on self-awareness and qualitative tracking rather than the precise numbers athletes use. Imperfect tracking is vastly better than no tracking. - -## Related -- [[cycling-teaches-patience]] — Patience and pacing as the practical application of training load management -- [[recovery-week-in-training]] — Recovery weeks as the structural implementation of periodization in knowledge work -- [[sleeping-more-is-a-superpower]] — Sleep as the primary recovery mechanism for cognitive load -- [[on-founder-energy-management]] — Energy management as the founder-specific application of training load principles -- [[the-two-types-of-hard]] — Training load context helps distinguish genuine fatigue from resistance diff --git a/demo-vault-v2/type/area.md b/demo-vault-v2/type/area.md index 5409f903..a58b4365 100644 --- a/demo-vault-v2/type/area.md +++ b/demo-vault-v2/type/area.md @@ -1,7 +1,11 @@ --- -Is A: Type +type: Type +icon: folders +color: amber +sidebar label: Areas --- # Area -An Area is an ongoing sphere of responsibility in your life or work — something you maintain indefinitely. Areas have standards to uphold, not completion dates. +Areas are ongoing domains of responsibility with no fixed end date. + diff --git a/demo-vault-v2/type/event.md b/demo-vault-v2/type/event.md index 8b6d8274..901a5c35 100644 --- a/demo-vault-v2/type/event.md +++ b/demo-vault-v2/type/event.md @@ -1,7 +1,11 @@ --- -Is A: Type +type: Type +icon: calendar +color: orange +sidebar label: Events --- # Event -An Event is a point-in-time occurrence — a meeting, a milestone, a trip, or anything that happened on a specific date. Events are linked to the entities they relate to. +Events are time-bound occurrences tied to projects, people, or periods. + diff --git a/demo-vault-v2/type/evergreen.md b/demo-vault-v2/type/evergreen.md deleted file mode 100644 index e5532e0c..00000000 --- a/demo-vault-v2/type/evergreen.md +++ /dev/null @@ -1,7 +0,0 @@ ---- -Is A: Type ---- - -# Evergreen - -An Evergreen note captures a durable idea or insight that remains relevant over time. Unlike fleeting notes, evergreens are refined, stand-alone thoughts worth revisiting. diff --git a/demo-vault-v2/type/experiment.md b/demo-vault-v2/type/experiment.md deleted file mode 100644 index 2e5f3d88..00000000 --- a/demo-vault-v2/type/experiment.md +++ /dev/null @@ -1,7 +0,0 @@ ---- -Is A: Type ---- - -# Experiment - -An Experiment is a hypothesis-driven investigation with a clear test and measurable outcome. Experiments are time-bound and have explicit success criteria. diff --git a/demo-vault-v2/type/goal.md b/demo-vault-v2/type/goal.md deleted file mode 100644 index 87e8b940..00000000 --- a/demo-vault-v2/type/goal.md +++ /dev/null @@ -1,7 +0,0 @@ ---- -Is A: Type ---- - -# Goal - -A Goal is a specific, measurable outcome you want to achieve within a defined timeframe. Goals belong to Areas and are tracked with Key Results or Measures. diff --git a/demo-vault-v2/type/measure.md b/demo-vault-v2/type/measure.md index 2a3ab919..3e3e8a99 100644 --- a/demo-vault-v2/type/measure.md +++ b/demo-vault-v2/type/measure.md @@ -1,7 +1,11 @@ --- -Is A: Type +type: Type +icon: chart-line-up +color: cyan +sidebar label: Measures --- # Measure -A Measure tracks a metric that matters — revenue, subscribers, conversion rate. Measures are linked to Goals or Areas and updated regularly. +Measures track the numbers that matter for a responsibility or project. + diff --git a/demo-vault-v2/type/month.md b/demo-vault-v2/type/month.md deleted file mode 100644 index d7962549..00000000 --- a/demo-vault-v2/type/month.md +++ /dev/null @@ -1,7 +0,0 @@ ---- -Is A: Type ---- - -# Month - -A Month note captures the focus, highlights, and reflections for a calendar month. It provides a mid-level time horizon between weeks and quarters. diff --git a/demo-vault-v2/type/note.md b/demo-vault-v2/type/note.md index 0a81fe74..347b4d01 100644 --- a/demo-vault-v2/type/note.md +++ b/demo-vault-v2/type/note.md @@ -1,7 +1,11 @@ --- -Is A: Type +type: Type +icon: note +color: slate +sidebar label: Notes --- # Note -A Note is a general-purpose document — research notes, meeting notes, strategy docs, or anything that doesn't fit a more specific type. +Notes capture references, ideas, or QA artifacts that do not need a more specific type. + diff --git a/demo-vault-v2/type/person.md b/demo-vault-v2/type/person.md index d6d0ec03..0bf537fb 100644 --- a/demo-vault-v2/type/person.md +++ b/demo-vault-v2/type/person.md @@ -1,7 +1,11 @@ --- -Is A: Type +type: Type +icon: user +color: rose +sidebar label: People --- # Person -A Person is someone you interact with — colleagues, collaborators, mentors, friends. People can own projects, be linked to events, and appear in relationships. +People notes represent collaborators, owners, or recurring contacts. + diff --git a/demo-vault-v2/type/procedure.md b/demo-vault-v2/type/procedure.md index a361ac69..9560c7a4 100644 --- a/demo-vault-v2/type/procedure.md +++ b/demo-vault-v2/type/procedure.md @@ -1,7 +1,11 @@ --- -Is A: Type +type: Type +icon: checklist +color: violet +sidebar label: Procedures --- # Procedure -A Procedure is a recurring process tied to an Area or Responsibility. Procedures have a cadence and describe how to do something step by step. +Procedures describe repeatable workflows that support a responsibility. + diff --git a/demo-vault-v2/type/project.md b/demo-vault-v2/type/project.md index 732ce119..0ea5ad44 100644 --- a/demo-vault-v2/type/project.md +++ b/demo-vault-v2/type/project.md @@ -1,7 +1,11 @@ --- -Is A: Type +type: Type +icon: rocket +color: blue +sidebar label: Projects --- # Project -A Project is a time-bounded effort with a clear goal, defined outcome, and eventual completion. Projects belong to Areas and advance Goals. +Projects are time-bound efforts with an owner, a status, and a clear outcome. + diff --git a/demo-vault-v2/type/quarter.md b/demo-vault-v2/type/quarter.md index 1ed72b92..d51d59db 100644 --- a/demo-vault-v2/type/quarter.md +++ b/demo-vault-v2/type/quarter.md @@ -1,7 +1,11 @@ --- -Is A: Type +type: Type +icon: clock-countdown +color: emerald +sidebar label: Quarters --- # Quarter -A Quarter note captures the focus, OKRs, and reflections for a three-month period. It is the primary planning horizon for goals and projects. +Quarter notes group the initiatives and outcomes for a planning window. + diff --git a/demo-vault-v2/type/responsibility.md b/demo-vault-v2/type/responsibility.md index ef43db1e..70f179f6 100644 --- a/demo-vault-v2/type/responsibility.md +++ b/demo-vault-v2/type/responsibility.md @@ -1,7 +1,11 @@ --- -Is A: Type +type: Type +icon: briefcase +color: green +sidebar label: Responsibilities --- # Responsibility -A Responsibility is an ongoing area of ownership — something you are accountable for indefinitely. Responsibilities have procedures, projects, and measures attached. +Responsibilities are long-lived ownership areas with linked procedures and measures. + diff --git a/demo-vault-v2/type/target.md b/demo-vault-v2/type/target.md deleted file mode 100644 index 9ee518d9..00000000 --- a/demo-vault-v2/type/target.md +++ /dev/null @@ -1,7 +0,0 @@ ---- -Is A: Type ---- - -# Target - -A Target is a specific numeric goal within a Measure — the number you are aiming for by a given date. Targets make accountability concrete. diff --git a/demo-vault-v2/type/task.md b/demo-vault-v2/type/task.md deleted file mode 100644 index 990fb2cd..00000000 --- a/demo-vault-v2/type/task.md +++ /dev/null @@ -1,7 +0,0 @@ ---- -Is A: Type ---- - -# Task - -A Task is a discrete, actionable to-do that can be completed. Tasks are the smallest unit of work, linked to Projects or Procedures. diff --git a/demo-vault-v2/type/topic.md b/demo-vault-v2/type/topic.md index 412863ee..fcabf9a6 100644 --- a/demo-vault-v2/type/topic.md +++ b/demo-vault-v2/type/topic.md @@ -1,7 +1,11 @@ --- -Is A: Type +type: Type +icon: books +color: indigo +sidebar label: Topics --- # Topic -A Topic is a subject area for categorization and linking. Topics group related notes, projects, and resources by theme. +Topics collect related notes and make search/navigation scenarios easy to inspect. + diff --git a/demo-vault-v2/type/year.md b/demo-vault-v2/type/year.md deleted file mode 100644 index 532d84dc..00000000 --- a/demo-vault-v2/type/year.md +++ /dev/null @@ -1,7 +0,0 @@ ---- -Is A: Type ---- - -# Year - -A Year note captures the themes, goals, and reflections for a calendar year. It provides the highest-level time horizon in the life OS. diff --git a/demo-vault-v2/untitled-area-10.md b/demo-vault-v2/untitled-area-10.md deleted file mode 100644 index 1f8b017c..00000000 --- a/demo-vault-v2/untitled-area-10.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled area 10 -type: Area -status: Active ---- - -# Untitled area 10 - diff --git a/demo-vault-v2/untitled-area-11.md b/demo-vault-v2/untitled-area-11.md deleted file mode 100644 index 75f3f99b..00000000 --- a/demo-vault-v2/untitled-area-11.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled area 11 -type: Area -status: Active ---- - -# Untitled area 11 - diff --git a/demo-vault-v2/untitled-area-12.md b/demo-vault-v2/untitled-area-12.md deleted file mode 100644 index cc706a35..00000000 --- a/demo-vault-v2/untitled-area-12.md +++ /dev/null @@ -1,10 +0,0 @@ ---- -title: Untitled area 12 -type: Area -status: Active ---- -# Untitled area 12 - -[[2024-03|March 2024]] - -[[2024-03|March 2024]] diff --git a/demo-vault-v2/untitled-area-13.md b/demo-vault-v2/untitled-area-13.md deleted file mode 100644 index 42129e08..00000000 --- a/demo-vault-v2/untitled-area-13.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled area 13 -type: Area -status: Active ---- - -# Untitled area 13 - diff --git a/demo-vault-v2/untitled-area-14.md b/demo-vault-v2/untitled-area-14.md deleted file mode 100644 index e2c6e57d..00000000 --- a/demo-vault-v2/untitled-area-14.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled area 14 -type: Area -status: Active ---- - -# Untitled area 14 - diff --git a/demo-vault-v2/untitled-area-15.md b/demo-vault-v2/untitled-area-15.md deleted file mode 100644 index 3a13c659..00000000 --- a/demo-vault-v2/untitled-area-15.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled area 15 -type: Area -status: Active ---- - -# Untitled area 15 - diff --git a/demo-vault-v2/untitled-area-16.md b/demo-vault-v2/untitled-area-16.md deleted file mode 100644 index 59028079..00000000 --- a/demo-vault-v2/untitled-area-16.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled area 16 -type: Area -status: Active ---- - -# Untitled area 16 - diff --git a/demo-vault-v2/untitled-area-17.md b/demo-vault-v2/untitled-area-17.md deleted file mode 100644 index 551e52ff..00000000 --- a/demo-vault-v2/untitled-area-17.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled area 17 -type: Area -status: Active ---- - -# Untitled area 17 - diff --git a/demo-vault-v2/untitled-area-18.md b/demo-vault-v2/untitled-area-18.md deleted file mode 100644 index 9fbdf969..00000000 --- a/demo-vault-v2/untitled-area-18.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled area 18 -type: Area -status: Active ---- - -# Untitled area 18 - diff --git a/demo-vault-v2/untitled-area-2.md b/demo-vault-v2/untitled-area-2.md deleted file mode 100644 index 87a128ee..00000000 --- a/demo-vault-v2/untitled-area-2.md +++ /dev/null @@ -1,6 +0,0 @@ ---- -title: Untitled area 2 -type: Area -status: Active ---- -# Untitled area 2 diff --git a/demo-vault-v2/untitled-area-3.md b/demo-vault-v2/untitled-area-3.md deleted file mode 100644 index 6428949c..00000000 --- a/demo-vault-v2/untitled-area-3.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled area 3 -type: Area -status: Active ---- - -# Untitled area 3 - diff --git a/demo-vault-v2/untitled-area-4.md b/demo-vault-v2/untitled-area-4.md deleted file mode 100644 index 5f9b0e6d..00000000 --- a/demo-vault-v2/untitled-area-4.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled area 4 -type: Area -status: Active ---- - -# Untitled area 4 - diff --git a/demo-vault-v2/untitled-area-5.md b/demo-vault-v2/untitled-area-5.md deleted file mode 100644 index f78c6676..00000000 --- a/demo-vault-v2/untitled-area-5.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled area 5 -type: Area -status: Active ---- - -# Untitled area 5 - diff --git a/demo-vault-v2/untitled-area-6.md b/demo-vault-v2/untitled-area-6.md deleted file mode 100644 index b326e27e..00000000 --- a/demo-vault-v2/untitled-area-6.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled area 6 -type: Area -status: Active ---- - -# Untitled area 6 - diff --git a/demo-vault-v2/untitled-area-7.md b/demo-vault-v2/untitled-area-7.md deleted file mode 100644 index a061ebde..00000000 --- a/demo-vault-v2/untitled-area-7.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled area 7 -type: Area -status: Active ---- - -# Untitled area 7 - diff --git a/demo-vault-v2/untitled-area-8.md b/demo-vault-v2/untitled-area-8.md deleted file mode 100644 index c3cec877..00000000 --- a/demo-vault-v2/untitled-area-8.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled area 8 -type: Area -status: Active ---- - -# Untitled area 8 - diff --git a/demo-vault-v2/untitled-area-9.md b/demo-vault-v2/untitled-area-9.md deleted file mode 100644 index a8795fbe..00000000 --- a/demo-vault-v2/untitled-area-9.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled area 9 -type: Area -status: Active ---- - -# Untitled area 9 - diff --git a/demo-vault-v2/untitled-area.md b/demo-vault-v2/untitled-area.md deleted file mode 100644 index 4b924680..00000000 --- a/demo-vault-v2/untitled-area.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled area -type: Area -status: Active ---- - -# Untitled area - diff --git a/demo-vault-v2/untitled-career-tracks-depend-on-company-shape-2.md b/demo-vault-v2/untitled-career-tracks-depend-on-company-shape-2.md deleted file mode 100644 index 9cf4de94..00000000 --- a/demo-vault-v2/untitled-career-tracks-depend-on-company-shape-2.md +++ /dev/null @@ -1,6 +0,0 @@ ---- -title: Untitled Career Tracks Depend on Company Shape 2 -type: Note -status: Active ---- -# Untitled Career Tracks Depend on Company Shape 2 diff --git a/demo-vault-v2/untitled-experiment-2.md b/demo-vault-v2/untitled-experiment-2.md deleted file mode 100644 index 3f1c5d27..00000000 --- a/demo-vault-v2/untitled-experiment-2.md +++ /dev/null @@ -1,14 +0,0 @@ ---- -title: Untitled experiment 3 -type: Experiment -status: Active ---- -# Untitled experiment 2 - -## Hypothesis - -## Method - -## Results - -## Conclusion diff --git a/demo-vault-v2/untitled-experiment.md b/demo-vault-v2/untitled-experiment.md deleted file mode 100644 index 2b84774b..00000000 --- a/demo-vault-v2/untitled-experiment.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -title: Untitled experiment -type: Experiment -status: Active ---- -# Untitled experiment - -## Hypothesis - -## Method - -[[Ma - -## Results - -## Conclusion diff --git a/demo-vault-v2/untitled-not.md b/demo-vault-v2/untitled-not.md deleted file mode 100644 index c3012d8f..00000000 --- a/demo-vault-v2/untitled-not.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled not -type: Note -status: Active ---- -# Untitled not - -[[Mae diff --git a/demo-vault-v2/untitled-note-10.md b/demo-vault-v2/untitled-note-10.md deleted file mode 100644 index 5df6b537..00000000 --- a/demo-vault-v2/untitled-note-10.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled note 10 -type: Note -status: Active ---- - -# Untitled note 10 - diff --git a/demo-vault-v2/untitled-note-100-md-renamed.md b/demo-vault-v2/untitled-note-100-md-renamed.md deleted file mode 100644 index 689cc94d..00000000 --- a/demo-vault-v2/untitled-note-100-md-renamed.md +++ /dev/null @@ -1,11 +0,0 @@ ---- -title: Untitled note 100 -type: Project -status: Active ---- - -# untitled-note-100.md Renamed - - - -Appended by raw editor test \ No newline at end of file diff --git a/demo-vault-v2/untitled-note-101.md b/demo-vault-v2/untitled-note-101.md deleted file mode 100644 index 6c463242..00000000 --- a/demo-vault-v2/untitled-note-101.md +++ /dev/null @@ -1,10 +0,0 @@ ---- -title: Untitled note 101 -type: Note -status: Active ---- -# Untitled note 101 - -[[2024-03|March 2024]] - -[[2024-03|March 2024]] diff --git a/demo-vault-v2/untitled-note-102.md b/demo-vault-v2/untitled-note-102.md deleted file mode 100644 index 3a6eef51..00000000 --- a/demo-vault-v2/untitled-note-102.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled note 102 -type: Note -status: Active ---- - -# Untitled note 102 - diff --git a/demo-vault-v2/untitled-note-103.md b/demo-vault-v2/untitled-note-103.md deleted file mode 100644 index dd0100e3..00000000 --- a/demo-vault-v2/untitled-note-103.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled note 103 -type: Note -status: Active ---- - -# Untitled note 103 - diff --git a/demo-vault-v2/untitled-note-104.md b/demo-vault-v2/untitled-note-104.md deleted file mode 100644 index ea244eee..00000000 --- a/demo-vault-v2/untitled-note-104.md +++ /dev/null @@ -1,6 +0,0 @@ ---- -title: Untitled note 104 -type: Note -status: Active ---- -# Untitled note 104My Custom H1 Heading diff --git a/demo-vault-v2/untitled-note-105-md-renamed.md b/demo-vault-v2/untitled-note-105-md-renamed.md deleted file mode 100644 index 90ace4fb..00000000 --- a/demo-vault-v2/untitled-note-105-md-renamed.md +++ /dev/null @@ -1,11 +0,0 @@ ---- -title: Untitled note 105 -type: Project -status: Active ---- - -# untitled-note-105.md Renamed - - - -Appended by raw editor test \ No newline at end of file diff --git a/demo-vault-v2/untitled-note-106.md b/demo-vault-v2/untitled-note-106.md deleted file mode 100644 index 06cff741..00000000 --- a/demo-vault-v2/untitled-note-106.md +++ /dev/null @@ -1,10 +0,0 @@ ---- -title: Untitled note 106 -type: Note -status: Active ---- -# Untitled note 106 - -[[2024-03|March 2024]] - -[[2024-03|March 2024]] diff --git a/demo-vault-v2/untitled-note-107.md b/demo-vault-v2/untitled-note-107.md deleted file mode 100644 index 9afbf7d1..00000000 --- a/demo-vault-v2/untitled-note-107.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled note 107 -type: Note -status: Active ---- - -# Untitled note 107 - diff --git a/demo-vault-v2/untitled-note-108.md b/demo-vault-v2/untitled-note-108.md deleted file mode 100644 index 2133de3b..00000000 --- a/demo-vault-v2/untitled-note-108.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled note 108 -type: Note -status: Active ---- - -# Untitled note 108 - diff --git a/demo-vault-v2/untitled-note-109.md b/demo-vault-v2/untitled-note-109.md deleted file mode 100644 index 9ffd691a..00000000 --- a/demo-vault-v2/untitled-note-109.md +++ /dev/null @@ -1,6 +0,0 @@ ---- -title: Untitled note 109 -type: Note -status: Active ---- -# Untitled note 109My Custom H1 Heading diff --git a/demo-vault-v2/untitled-note-11.md b/demo-vault-v2/untitled-note-11.md deleted file mode 100644 index 00fb5b6c..00000000 --- a/demo-vault-v2/untitled-note-11.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled note 11 -type: Note -status: Active ---- - -# Untitled note 11 - diff --git a/demo-vault-v2/untitled-note-110-md-renamed.md b/demo-vault-v2/untitled-note-110-md-renamed.md deleted file mode 100644 index 7f04a214..00000000 --- a/demo-vault-v2/untitled-note-110-md-renamed.md +++ /dev/null @@ -1,11 +0,0 @@ ---- -title: Untitled note 110 -type: Project -status: Active ---- - -# untitled-note-110.md Renamed - - - -Appended by raw editor test \ No newline at end of file diff --git a/demo-vault-v2/untitled-note-111.md b/demo-vault-v2/untitled-note-111.md deleted file mode 100644 index 2d6f3d1c..00000000 --- a/demo-vault-v2/untitled-note-111.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled note 111 -type: Note -status: Active ---- -[[2024-03|March 2024]] - -[[2024-03|March 2024]] diff --git a/demo-vault-v2/untitled-note-112.md b/demo-vault-v2/untitled-note-112.md deleted file mode 100644 index 05666178..00000000 --- a/demo-vault-v2/untitled-note-112.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled note 112 -type: Note -status: Active ---- - -# Untitled note 112 - diff --git a/demo-vault-v2/untitled-note-113.md b/demo-vault-v2/untitled-note-113.md deleted file mode 100644 index 3a337742..00000000 --- a/demo-vault-v2/untitled-note-113.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled note 113 -type: Note -status: Active ---- - -# Untitled note 113 - diff --git a/demo-vault-v2/untitled-note-114.md b/demo-vault-v2/untitled-note-114.md deleted file mode 100644 index 6e8f3581..00000000 --- a/demo-vault-v2/untitled-note-114.md +++ /dev/null @@ -1,6 +0,0 @@ ---- -title: Untitled note 114 -type: Note -status: Active ---- -My Custom H1 Heading diff --git a/demo-vault-v2/untitled-note-115-md-renamed.md b/demo-vault-v2/untitled-note-115-md-renamed.md deleted file mode 100644 index be29031c..00000000 --- a/demo-vault-v2/untitled-note-115-md-renamed.md +++ /dev/null @@ -1,11 +0,0 @@ ---- -title: Untitled note 115 -type: Project -status: Active ---- - -# untitled-note-115.md Renamed - - - -Appended by raw editor test \ No newline at end of file diff --git a/demo-vault-v2/untitled-note-116.md b/demo-vault-v2/untitled-note-116.md deleted file mode 100644 index 62b14d1e..00000000 --- a/demo-vault-v2/untitled-note-116.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled note 116 -type: Note -status: Active ---- -[[2024-03|March 2024]] - -[[2024-03|March 2024]] diff --git a/demo-vault-v2/untitled-note-117.md b/demo-vault-v2/untitled-note-117.md deleted file mode 100644 index 4c05f31a..00000000 --- a/demo-vault-v2/untitled-note-117.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -title: Untitled note 117 -type: Note -status: Active ---- diff --git a/demo-vault-v2/untitled-note-118.md b/demo-vault-v2/untitled-note-118.md deleted file mode 100644 index 43ccf68d..00000000 --- a/demo-vault-v2/untitled-note-118.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -title: Untitled note 118 -type: Note -status: Active ---- diff --git a/demo-vault-v2/untitled-note-119.md b/demo-vault-v2/untitled-note-119.md deleted file mode 100644 index afd36614..00000000 --- a/demo-vault-v2/untitled-note-119.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -title: Untitled note 119 -type: Note -status: Active ---- diff --git a/demo-vault-v2/untitled-note-12.md b/demo-vault-v2/untitled-note-12.md deleted file mode 100644 index 137fc023..00000000 --- a/demo-vault-v2/untitled-note-12.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled note 12 -type: Note -status: Active ---- - -# Untitled note 12 - diff --git a/demo-vault-v2/untitled-note-120.md b/demo-vault-v2/untitled-note-120.md deleted file mode 100644 index 2acd1775..00000000 --- a/demo-vault-v2/untitled-note-120.md +++ /dev/null @@ -1,6 +0,0 @@ ---- -title: Untitled note 120 -type: Note -status: Active ---- -My Custom H1 Heading diff --git a/demo-vault-v2/untitled-note-121-md-renamed.md b/demo-vault-v2/untitled-note-121-md-renamed.md deleted file mode 100644 index 67c6d118..00000000 --- a/demo-vault-v2/untitled-note-121-md-renamed.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled note 121 -type: Project -status: Active ---- - - -Appended by raw editor test \ No newline at end of file diff --git a/demo-vault-v2/untitled-note-122.md b/demo-vault-v2/untitled-note-122.md deleted file mode 100644 index b487d64c..00000000 --- a/demo-vault-v2/untitled-note-122.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled note 122 -type: Note -status: Active ---- -[[2024-03|March 2024]] - -[[2024-03|March 2024]] diff --git a/demo-vault-v2/untitled-note-123.md b/demo-vault-v2/untitled-note-123.md deleted file mode 100644 index d5069df3..00000000 --- a/demo-vault-v2/untitled-note-123.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -title: Untitled note 123 -type: Note -status: Active ---- diff --git a/demo-vault-v2/untitled-note-124.md b/demo-vault-v2/untitled-note-124.md deleted file mode 100644 index d09f85ea..00000000 --- a/demo-vault-v2/untitled-note-124.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -title: Untitled note 124 -type: Note -status: Active ---- diff --git a/demo-vault-v2/untitled-note-125.md b/demo-vault-v2/untitled-note-125.md deleted file mode 100644 index 5c1640a8..00000000 --- a/demo-vault-v2/untitled-note-125.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -title: Untitled note 125 -type: Note -status: Active ---- diff --git a/demo-vault-v2/untitled-note-126.md b/demo-vault-v2/untitled-note-126.md deleted file mode 100644 index ebc37afe..00000000 --- a/demo-vault-v2/untitled-note-126.md +++ /dev/null @@ -1,6 +0,0 @@ ---- -title: Untitled note 126 -type: Note -status: Active ---- -My Custom H1 Heading diff --git a/demo-vault-v2/untitled-note-127-md-renamed.md b/demo-vault-v2/untitled-note-127-md-renamed.md deleted file mode 100644 index 35c49643..00000000 --- a/demo-vault-v2/untitled-note-127-md-renamed.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled note 127 -type: Project -status: Active ---- - - -Appended by raw editor test \ No newline at end of file diff --git a/demo-vault-v2/untitled-note-128.md b/demo-vault-v2/untitled-note-128.md deleted file mode 100644 index acbc1b5d..00000000 --- a/demo-vault-v2/untitled-note-128.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled note 128 -type: Note -status: Active ---- -[[2024-03|March 2024]] - -[[2024-03|March 2024]] diff --git a/demo-vault-v2/untitled-note-129.md b/demo-vault-v2/untitled-note-129.md deleted file mode 100644 index 262e29f5..00000000 --- a/demo-vault-v2/untitled-note-129.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -title: Untitled note 129 -type: Note -status: Active ---- diff --git a/demo-vault-v2/untitled-note-13.md b/demo-vault-v2/untitled-note-13.md deleted file mode 100644 index 99d4e4fd..00000000 --- a/demo-vault-v2/untitled-note-13.md +++ /dev/null @@ -1,6 +0,0 @@ ---- -title: Untitled note 13 -type: Note -status: Active ---- -# Untitled note 13My Custom H1 Heading diff --git a/demo-vault-v2/untitled-note-130.md b/demo-vault-v2/untitled-note-130.md deleted file mode 100644 index 45630011..00000000 --- a/demo-vault-v2/untitled-note-130.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -title: Untitled note 130 -type: Note -status: Active ---- diff --git a/demo-vault-v2/untitled-note-131.md b/demo-vault-v2/untitled-note-131.md deleted file mode 100644 index 6b300be5..00000000 --- a/demo-vault-v2/untitled-note-131.md +++ /dev/null @@ -1,6 +0,0 @@ ---- -title: Untitled note 131 -type: Note -status: Active ---- -My Custom H1 Heading diff --git a/demo-vault-v2/untitled-note-132-md-renamed.md b/demo-vault-v2/untitled-note-132-md-renamed.md deleted file mode 100644 index 0b56b57f..00000000 --- a/demo-vault-v2/untitled-note-132-md-renamed.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled note 132 -type: Project -status: Active ---- - - -Appended by raw editor test \ No newline at end of file diff --git a/demo-vault-v2/untitled-note-133.md b/demo-vault-v2/untitled-note-133.md deleted file mode 100644 index f9b77590..00000000 --- a/demo-vault-v2/untitled-note-133.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled note 133 -type: Note -status: Active ---- -[[2024-03|March 2024]] - -[[2024-03|March 2024]] diff --git a/demo-vault-v2/untitled-note-134.md b/demo-vault-v2/untitled-note-134.md deleted file mode 100644 index 3b8fa619..00000000 --- a/demo-vault-v2/untitled-note-134.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -title: Untitled note 134 -type: Note -status: Active ---- diff --git a/demo-vault-v2/untitled-note-135.md b/demo-vault-v2/untitled-note-135.md deleted file mode 100644 index 98b69960..00000000 --- a/demo-vault-v2/untitled-note-135.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -title: Untitled note 135 -type: Note -status: Active ---- diff --git a/demo-vault-v2/untitled-note-136.md b/demo-vault-v2/untitled-note-136.md deleted file mode 100644 index e4586c56..00000000 --- a/demo-vault-v2/untitled-note-136.md +++ /dev/null @@ -1,6 +0,0 @@ ---- -title: Untitled note 136 -type: Note -status: Active ---- -My Custom H1 Heading diff --git a/demo-vault-v2/untitled-note-137-md-renamed.md b/demo-vault-v2/untitled-note-137-md-renamed.md deleted file mode 100644 index a8344640..00000000 --- a/demo-vault-v2/untitled-note-137-md-renamed.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled note 137 -type: Project -status: Active ---- - - -Appended by raw editor test \ No newline at end of file diff --git a/demo-vault-v2/untitled-note-138.md b/demo-vault-v2/untitled-note-138.md deleted file mode 100644 index 813c2f8e..00000000 --- a/demo-vault-v2/untitled-note-138.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled note 138 -type: Note -status: Active ---- -[[2024-03|March 2024]] - -[[2024-03|March 2024]] diff --git a/demo-vault-v2/untitled-note-139.md b/demo-vault-v2/untitled-note-139.md deleted file mode 100644 index a6488d6f..00000000 --- a/demo-vault-v2/untitled-note-139.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -title: Untitled note 139 -type: Note -status: Active ---- diff --git a/demo-vault-v2/untitled-note-14.md b/demo-vault-v2/untitled-note-14.md deleted file mode 100644 index d0c23f4c..00000000 --- a/demo-vault-v2/untitled-note-14.md +++ /dev/null @@ -1,6 +0,0 @@ ---- -title: Untitled note 14 -type: Note -status: Active ---- -# Untitled note 14My Custom H1 Heading diff --git a/demo-vault-v2/untitled-note-140.md b/demo-vault-v2/untitled-note-140.md deleted file mode 100644 index 2357c75a..00000000 --- a/demo-vault-v2/untitled-note-140.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -title: Untitled note 140 -type: Note -status: Active ---- diff --git a/demo-vault-v2/untitled-note-141.md b/demo-vault-v2/untitled-note-141.md deleted file mode 100644 index e6ad64f2..00000000 --- a/demo-vault-v2/untitled-note-141.md +++ /dev/null @@ -1,6 +0,0 @@ ---- -title: Untitled note 141 -type: Note -status: Active ---- -My Custom H1 Heading diff --git a/demo-vault-v2/untitled-note-142-md-renamed.md b/demo-vault-v2/untitled-note-142-md-renamed.md deleted file mode 100644 index 9644324b..00000000 --- a/demo-vault-v2/untitled-note-142-md-renamed.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled note 142 -type: Project -status: Active ---- - - -Appended by raw editor test \ No newline at end of file diff --git a/demo-vault-v2/untitled-note-143.md b/demo-vault-v2/untitled-note-143.md deleted file mode 100644 index 6ef0e1d8..00000000 --- a/demo-vault-v2/untitled-note-143.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled note 143 -type: Note -status: Active ---- -[[2024-03|March 2024]] - -[[2024-03|March 2024]] diff --git a/demo-vault-v2/untitled-note-144.md b/demo-vault-v2/untitled-note-144.md deleted file mode 100644 index cd03b66f..00000000 --- a/demo-vault-v2/untitled-note-144.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -title: Untitled note 144 -type: Note -status: Active ---- diff --git a/demo-vault-v2/untitled-note-145.md b/demo-vault-v2/untitled-note-145.md deleted file mode 100644 index 4418aa61..00000000 --- a/demo-vault-v2/untitled-note-145.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -title: Untitled note 145 -type: Note -status: Active ---- diff --git a/demo-vault-v2/untitled-note-146.md b/demo-vault-v2/untitled-note-146.md deleted file mode 100644 index 08a915ad..00000000 --- a/demo-vault-v2/untitled-note-146.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -title: Untitled note 146 -type: Note -status: Active ---- diff --git a/demo-vault-v2/untitled-note-147.md b/demo-vault-v2/untitled-note-147.md deleted file mode 100644 index 964a94d0..00000000 --- a/demo-vault-v2/untitled-note-147.md +++ /dev/null @@ -1,6 +0,0 @@ ---- -title: Untitled note 147 -type: Note -status: Active ---- -My Custom H1 Heading diff --git a/demo-vault-v2/untitled-note-148-md-renamed.md b/demo-vault-v2/untitled-note-148-md-renamed.md deleted file mode 100644 index 65544703..00000000 --- a/demo-vault-v2/untitled-note-148-md-renamed.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled note 148 -type: Project -status: Active ---- - - -Appended by raw editor test \ No newline at end of file diff --git a/demo-vault-v2/untitled-note-149.md b/demo-vault-v2/untitled-note-149.md deleted file mode 100644 index 621d2d0f..00000000 --- a/demo-vault-v2/untitled-note-149.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled note 149 -type: Note -status: Active ---- -[[2024-03|March 2024]] - -[[2024-03|March 2024]] diff --git a/demo-vault-v2/untitled-note-15-md-renamed.md b/demo-vault-v2/untitled-note-15-md-renamed.md deleted file mode 100644 index 71eb7f4b..00000000 --- a/demo-vault-v2/untitled-note-15-md-renamed.md +++ /dev/null @@ -1,11 +0,0 @@ ---- -title: Untitled note 15 -type: Project -status: Active ---- - -# untitled-note-15.md Renamed - - - -Appended by raw editor test \ No newline at end of file diff --git a/demo-vault-v2/untitled-note-150.md b/demo-vault-v2/untitled-note-150.md deleted file mode 100644 index 86bb845a..00000000 --- a/demo-vault-v2/untitled-note-150.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -title: Untitled note 150 -type: Note -status: Active ---- diff --git a/demo-vault-v2/untitled-note-151.md b/demo-vault-v2/untitled-note-151.md deleted file mode 100644 index aef4c349..00000000 --- a/demo-vault-v2/untitled-note-151.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -title: Untitled note 151 -type: Note -status: Active ---- diff --git a/demo-vault-v2/untitled-note-152.md b/demo-vault-v2/untitled-note-152.md deleted file mode 100644 index 9e249299..00000000 --- a/demo-vault-v2/untitled-note-152.md +++ /dev/null @@ -1,6 +0,0 @@ ---- -title: Untitled note 152 -type: Note -status: Active ---- -My Custom H1 Heading diff --git a/demo-vault-v2/untitled-note-153-md-renamed.md b/demo-vault-v2/untitled-note-153-md-renamed.md deleted file mode 100644 index 7b44d972..00000000 --- a/demo-vault-v2/untitled-note-153-md-renamed.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled note 153 -type: Project -status: Active ---- - - -Appended by raw editor test \ No newline at end of file diff --git a/demo-vault-v2/untitled-note-154.md b/demo-vault-v2/untitled-note-154.md deleted file mode 100644 index d3ed4577..00000000 --- a/demo-vault-v2/untitled-note-154.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled note 154 -type: Note -status: Active ---- -[[2024-03|March 2024]] - -[[2024-03|March 2024]] diff --git a/demo-vault-v2/untitled-note-155.md b/demo-vault-v2/untitled-note-155.md deleted file mode 100644 index 7fa2675f..00000000 --- a/demo-vault-v2/untitled-note-155.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -title: Untitled note 155 -type: Note -status: Active ---- diff --git a/demo-vault-v2/untitled-note-156.md b/demo-vault-v2/untitled-note-156.md deleted file mode 100644 index db05f21a..00000000 --- a/demo-vault-v2/untitled-note-156.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -title: Untitled note 156 -type: Note -status: Active ---- diff --git a/demo-vault-v2/untitled-note-157.md b/demo-vault-v2/untitled-note-157.md deleted file mode 100644 index 3949bb9e..00000000 --- a/demo-vault-v2/untitled-note-157.md +++ /dev/null @@ -1,6 +0,0 @@ ---- -title: Untitled note 157 -type: Note -status: Active ---- -My Custom H1 Heading diff --git a/demo-vault-v2/untitled-note-158-md-renamed.md b/demo-vault-v2/untitled-note-158-md-renamed.md deleted file mode 100644 index a59b01a6..00000000 --- a/demo-vault-v2/untitled-note-158-md-renamed.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled note 158 -type: Project -status: Active ---- - - -Appended by raw editor test \ No newline at end of file diff --git a/demo-vault-v2/untitled-note-159.md b/demo-vault-v2/untitled-note-159.md deleted file mode 100644 index 1cd23173..00000000 --- a/demo-vault-v2/untitled-note-159.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled note 159 -type: Note -status: Active ---- -[[2024-03|March 2024]] - -[[2024-03|March 2024]] diff --git a/demo-vault-v2/untitled-note-16.md b/demo-vault-v2/untitled-note-16.md deleted file mode 100644 index f47cf11e..00000000 --- a/demo-vault-v2/untitled-note-16.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled note 16 -type: Note -status: Active ---- - -# Untitled note 16 - diff --git a/demo-vault-v2/untitled-note-160.md b/demo-vault-v2/untitled-note-160.md deleted file mode 100644 index 80f9f04a..00000000 --- a/demo-vault-v2/untitled-note-160.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -title: Untitled note 160 -type: Note -status: Active ---- diff --git a/demo-vault-v2/untitled-note-161.md b/demo-vault-v2/untitled-note-161.md deleted file mode 100644 index 5be49449..00000000 --- a/demo-vault-v2/untitled-note-161.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -title: Untitled note 161 -type: Note -status: Active ---- diff --git a/demo-vault-v2/untitled-note-162.md b/demo-vault-v2/untitled-note-162.md deleted file mode 100644 index c2431d50..00000000 --- a/demo-vault-v2/untitled-note-162.md +++ /dev/null @@ -1,6 +0,0 @@ ---- -title: Untitled note 162 -type: Note -status: Active ---- -My Custom H1 Heading diff --git a/demo-vault-v2/untitled-note-163-md-renamed.md b/demo-vault-v2/untitled-note-163-md-renamed.md deleted file mode 100644 index ff0ed2a3..00000000 --- a/demo-vault-v2/untitled-note-163-md-renamed.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled note 163 -type: Project -status: Active ---- - - -Appended by raw editor test \ No newline at end of file diff --git a/demo-vault-v2/untitled-note-164.md b/demo-vault-v2/untitled-note-164.md deleted file mode 100644 index 8abfb830..00000000 --- a/demo-vault-v2/untitled-note-164.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled note 164 -type: Note -status: Active ---- -[[2024-03|March 2024]] - -[[2024-03|March 2024]] diff --git a/demo-vault-v2/untitled-note-165.md b/demo-vault-v2/untitled-note-165.md deleted file mode 100644 index 5b19d698..00000000 --- a/demo-vault-v2/untitled-note-165.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -title: Untitled note 165 -type: Note -status: Active ---- diff --git a/demo-vault-v2/untitled-note-166.md b/demo-vault-v2/untitled-note-166.md deleted file mode 100644 index 69bdfe51..00000000 --- a/demo-vault-v2/untitled-note-166.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -title: Untitled note 166 -type: Note -status: Active ---- diff --git a/demo-vault-v2/untitled-note-167.md b/demo-vault-v2/untitled-note-167.md deleted file mode 100644 index 49c68ac7..00000000 --- a/demo-vault-v2/untitled-note-167.md +++ /dev/null @@ -1,6 +0,0 @@ ---- -title: Untitled note 167 -type: Note -status: Active ---- -My Custom H1 Heading diff --git a/demo-vault-v2/untitled-note-168-md-renamed.md b/demo-vault-v2/untitled-note-168-md-renamed.md deleted file mode 100644 index cf131c9f..00000000 --- a/demo-vault-v2/untitled-note-168-md-renamed.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled note 168 -type: Note -status: Active ---- - - -Appended by raw editor test \ No newline at end of file diff --git a/demo-vault-v2/untitled-note-169.md b/demo-vault-v2/untitled-note-169.md deleted file mode 100644 index f7ddcb63..00000000 --- a/demo-vault-v2/untitled-note-169.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled note 169 -type: Note -status: Active ---- -[[2024-03|March 2024]] - -[[2024-03|March 2024]] diff --git a/demo-vault-v2/untitled-note-17.md b/demo-vault-v2/untitled-note-17.md deleted file mode 100644 index 2f719053..00000000 --- a/demo-vault-v2/untitled-note-17.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled note 17 -type: Note -status: Active ---- - -# Untitled note 17 - diff --git a/demo-vault-v2/untitled-note-170.md b/demo-vault-v2/untitled-note-170.md deleted file mode 100644 index 9e4b710a..00000000 --- a/demo-vault-v2/untitled-note-170.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -title: Untitled note 170 -type: Note -status: Active ---- diff --git a/demo-vault-v2/untitled-note-171.md b/demo-vault-v2/untitled-note-171.md deleted file mode 100644 index 64ec4301..00000000 --- a/demo-vault-v2/untitled-note-171.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -title: Untitled note 171 -type: Note -status: Active ---- diff --git a/demo-vault-v2/untitled-note-172.md b/demo-vault-v2/untitled-note-172.md deleted file mode 100644 index d91ecb42..00000000 --- a/demo-vault-v2/untitled-note-172.md +++ /dev/null @@ -1,6 +0,0 @@ ---- -title: Untitled note 172 -type: Note -status: Active ---- -My Custom H1 Heading diff --git a/demo-vault-v2/untitled-note-173-md-renamed.md b/demo-vault-v2/untitled-note-173-md-renamed.md deleted file mode 100644 index a2933fde..00000000 --- a/demo-vault-v2/untitled-note-173-md-renamed.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled note 173 -type: Project -status: Active ---- - - -Appended by raw editor test \ No newline at end of file diff --git a/demo-vault-v2/untitled-note-174.md b/demo-vault-v2/untitled-note-174.md deleted file mode 100644 index ce24a513..00000000 --- a/demo-vault-v2/untitled-note-174.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled note 174 -type: Note -status: Active ---- -[[2024-03|March 2024]] - -[[2024-03|March 2024]] diff --git a/demo-vault-v2/untitled-note-175.md b/demo-vault-v2/untitled-note-175.md deleted file mode 100644 index 4525a98a..00000000 --- a/demo-vault-v2/untitled-note-175.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -title: Untitled note 175 -type: Note -status: Active ---- diff --git a/demo-vault-v2/untitled-note-176.md b/demo-vault-v2/untitled-note-176.md deleted file mode 100644 index 7d4dee70..00000000 --- a/demo-vault-v2/untitled-note-176.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -title: Untitled note 176 -type: Note -status: Active ---- diff --git a/demo-vault-v2/untitled-note-177.md b/demo-vault-v2/untitled-note-177.md deleted file mode 100644 index 942d1ca9..00000000 --- a/demo-vault-v2/untitled-note-177.md +++ /dev/null @@ -1,6 +0,0 @@ ---- -title: Untitled note 177 -type: Note -status: Active ---- -My Custom H1 Heading diff --git a/demo-vault-v2/untitled-note-1775473305.md b/demo-vault-v2/untitled-note-1775473305.md deleted file mode 100644 index a69dde29..00000000 --- a/demo-vault-v2/untitled-note-1775473305.md +++ /dev/null @@ -1,4 +0,0 @@ ---- -type: Note -status: Active ---- diff --git a/demo-vault-v2/untitled-note-1775473680.md b/demo-vault-v2/untitled-note-1775473680.md deleted file mode 100644 index ce9b23cb..00000000 --- a/demo-vault-v2/untitled-note-1775473680.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -type: Note -status: Active ---- -My Custom H1 Heading diff --git a/demo-vault-v2/untitled-note-1775473969.md b/demo-vault-v2/untitled-note-1775473969.md deleted file mode 100644 index 6ffd9a23..00000000 --- a/demo-vault-v2/untitled-note-1775473969.md +++ /dev/null @@ -1,7 +0,0 @@ ---- -type: Note -status: Active ---- -[[2024-03|March 2024]] - -[[2024-03|March 2024]] diff --git a/demo-vault-v2/untitled-note-1775496473.md b/demo-vault-v2/untitled-note-1775496473.md deleted file mode 100644 index a69dde29..00000000 --- a/demo-vault-v2/untitled-note-1775496473.md +++ /dev/null @@ -1,4 +0,0 @@ ---- -type: Note -status: Active ---- diff --git a/demo-vault-v2/untitled-note-1775496825.md b/demo-vault-v2/untitled-note-1775496825.md deleted file mode 100644 index ce9b23cb..00000000 --- a/demo-vault-v2/untitled-note-1775496825.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -type: Note -status: Active ---- -My Custom H1 Heading diff --git a/demo-vault-v2/untitled-note-1775497099.md b/demo-vault-v2/untitled-note-1775497099.md deleted file mode 100644 index 6ffd9a23..00000000 --- a/demo-vault-v2/untitled-note-1775497099.md +++ /dev/null @@ -1,7 +0,0 @@ ---- -type: Note -status: Active ---- -[[2024-03|March 2024]] - -[[2024-03|March 2024]] diff --git a/demo-vault-v2/untitled-note-1775541952.md b/demo-vault-v2/untitled-note-1775541952.md deleted file mode 100644 index a69dde29..00000000 --- a/demo-vault-v2/untitled-note-1775541952.md +++ /dev/null @@ -1,4 +0,0 @@ ---- -type: Note -status: Active ---- diff --git a/demo-vault-v2/untitled-note-1775542285.md b/demo-vault-v2/untitled-note-1775542285.md deleted file mode 100644 index a69dde29..00000000 --- a/demo-vault-v2/untitled-note-1775542285.md +++ /dev/null @@ -1,4 +0,0 @@ ---- -type: Note -status: Active ---- diff --git a/demo-vault-v2/untitled-note-1775542291.md b/demo-vault-v2/untitled-note-1775542291.md deleted file mode 100644 index a69dde29..00000000 --- a/demo-vault-v2/untitled-note-1775542291.md +++ /dev/null @@ -1,4 +0,0 @@ ---- -type: Note -status: Active ---- diff --git a/demo-vault-v2/untitled-note-1775542296.md b/demo-vault-v2/untitled-note-1775542296.md deleted file mode 100644 index a69dde29..00000000 --- a/demo-vault-v2/untitled-note-1775542296.md +++ /dev/null @@ -1,4 +0,0 @@ ---- -type: Note -status: Active ---- diff --git a/demo-vault-v2/untitled-note-1775542431.md b/demo-vault-v2/untitled-note-1775542431.md deleted file mode 100644 index a69dde29..00000000 --- a/demo-vault-v2/untitled-note-1775542431.md +++ /dev/null @@ -1,4 +0,0 @@ ---- -type: Note -status: Active ---- diff --git a/demo-vault-v2/untitled-note-1775542439.md b/demo-vault-v2/untitled-note-1775542439.md deleted file mode 100644 index a69dde29..00000000 --- a/demo-vault-v2/untitled-note-1775542439.md +++ /dev/null @@ -1,4 +0,0 @@ ---- -type: Note -status: Active ---- diff --git a/demo-vault-v2/untitled-note-1775542446.md b/demo-vault-v2/untitled-note-1775542446.md deleted file mode 100644 index a69dde29..00000000 --- a/demo-vault-v2/untitled-note-1775542446.md +++ /dev/null @@ -1,4 +0,0 @@ ---- -type: Note -status: Active ---- diff --git a/demo-vault-v2/untitled-note-1775542459.md b/demo-vault-v2/untitled-note-1775542459.md deleted file mode 100644 index a69dde29..00000000 --- a/demo-vault-v2/untitled-note-1775542459.md +++ /dev/null @@ -1,4 +0,0 @@ ---- -type: Note -status: Active ---- diff --git a/demo-vault-v2/untitled-note-1775542467.md b/demo-vault-v2/untitled-note-1775542467.md deleted file mode 100644 index a69dde29..00000000 --- a/demo-vault-v2/untitled-note-1775542467.md +++ /dev/null @@ -1,4 +0,0 @@ ---- -type: Note -status: Active ---- diff --git a/demo-vault-v2/untitled-note-1775542474.md b/demo-vault-v2/untitled-note-1775542474.md deleted file mode 100644 index a69dde29..00000000 --- a/demo-vault-v2/untitled-note-1775542474.md +++ /dev/null @@ -1,4 +0,0 @@ ---- -type: Note -status: Active ---- diff --git a/demo-vault-v2/untitled-note-1775542676.md b/demo-vault-v2/untitled-note-1775542676.md deleted file mode 100644 index a69dde29..00000000 --- a/demo-vault-v2/untitled-note-1775542676.md +++ /dev/null @@ -1,4 +0,0 @@ ---- -type: Note -status: Active ---- diff --git a/demo-vault-v2/untitled-note-1775542684.md b/demo-vault-v2/untitled-note-1775542684.md deleted file mode 100644 index a69dde29..00000000 --- a/demo-vault-v2/untitled-note-1775542684.md +++ /dev/null @@ -1,4 +0,0 @@ ---- -type: Note -status: Active ---- diff --git a/demo-vault-v2/untitled-note-1775542692.md b/demo-vault-v2/untitled-note-1775542692.md deleted file mode 100644 index a69dde29..00000000 --- a/demo-vault-v2/untitled-note-1775542692.md +++ /dev/null @@ -1,4 +0,0 @@ ---- -type: Note -status: Active ---- diff --git a/demo-vault-v2/untitled-note-1775542700.md b/demo-vault-v2/untitled-note-1775542700.md deleted file mode 100644 index a69dde29..00000000 --- a/demo-vault-v2/untitled-note-1775542700.md +++ /dev/null @@ -1,4 +0,0 @@ ---- -type: Note -status: Active ---- diff --git a/demo-vault-v2/untitled-note-1775542708.md b/demo-vault-v2/untitled-note-1775542708.md deleted file mode 100644 index a69dde29..00000000 --- a/demo-vault-v2/untitled-note-1775542708.md +++ /dev/null @@ -1,4 +0,0 @@ ---- -type: Note -status: Active ---- diff --git a/demo-vault-v2/untitled-note-1775542716-renamed.md b/demo-vault-v2/untitled-note-1775542716-renamed.md deleted file mode 100644 index b59b95b1..00000000 --- a/demo-vault-v2/untitled-note-1775542716-renamed.md +++ /dev/null @@ -1,7 +0,0 @@ ---- -type: Project -status: Active ---- - - -Appended by raw editor test \ No newline at end of file diff --git a/demo-vault-v2/untitled-note-1775542923.md b/demo-vault-v2/untitled-note-1775542923.md deleted file mode 100644 index a69dde29..00000000 --- a/demo-vault-v2/untitled-note-1775542923.md +++ /dev/null @@ -1,4 +0,0 @@ ---- -type: Note -status: Active ---- diff --git a/demo-vault-v2/untitled-note-1775542931.md b/demo-vault-v2/untitled-note-1775542931.md deleted file mode 100644 index a69dde29..00000000 --- a/demo-vault-v2/untitled-note-1775542931.md +++ /dev/null @@ -1,4 +0,0 @@ ---- -type: Note -status: Active ---- diff --git a/demo-vault-v2/untitled-note-1775542938.md b/demo-vault-v2/untitled-note-1775542938.md deleted file mode 100644 index a69dde29..00000000 --- a/demo-vault-v2/untitled-note-1775542938.md +++ /dev/null @@ -1,4 +0,0 @@ ---- -type: Note -status: Active ---- diff --git a/demo-vault-v2/untitled-note-1775542951.md b/demo-vault-v2/untitled-note-1775542951.md deleted file mode 100644 index a69dde29..00000000 --- a/demo-vault-v2/untitled-note-1775542951.md +++ /dev/null @@ -1,4 +0,0 @@ ---- -type: Note -status: Active ---- diff --git a/demo-vault-v2/untitled-note-1775542959.md b/demo-vault-v2/untitled-note-1775542959.md deleted file mode 100644 index a69dde29..00000000 --- a/demo-vault-v2/untitled-note-1775542959.md +++ /dev/null @@ -1,4 +0,0 @@ ---- -type: Note -status: Active ---- diff --git a/demo-vault-v2/untitled-note-1775542967.md b/demo-vault-v2/untitled-note-1775542967.md deleted file mode 100644 index a69dde29..00000000 --- a/demo-vault-v2/untitled-note-1775542967.md +++ /dev/null @@ -1,4 +0,0 @@ ---- -type: Note -status: Active ---- diff --git a/demo-vault-v2/untitled-note-1775542981.md b/demo-vault-v2/untitled-note-1775542981.md deleted file mode 100644 index 6ffd9a23..00000000 --- a/demo-vault-v2/untitled-note-1775542981.md +++ /dev/null @@ -1,7 +0,0 @@ ---- -type: Note -status: Active ---- -[[2024-03|March 2024]] - -[[2024-03|March 2024]] diff --git a/demo-vault-v2/untitled-note-178-md-renamed.md b/demo-vault-v2/untitled-note-178-md-renamed.md deleted file mode 100644 index e1a251e8..00000000 --- a/demo-vault-v2/untitled-note-178-md-renamed.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled note 178 -type: Note -status: Active ---- - - -Appended by raw editor test \ No newline at end of file diff --git a/demo-vault-v2/untitled-note-179.md b/demo-vault-v2/untitled-note-179.md deleted file mode 100644 index a0386244..00000000 --- a/demo-vault-v2/untitled-note-179.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled note 179 -type: Note -status: Active ---- -[[2024-03|March 2024]] - -[[2024-03|March 2024]] diff --git a/demo-vault-v2/untitled-note-18.md b/demo-vault-v2/untitled-note-18.md deleted file mode 100644 index 45b12ae7..00000000 --- a/demo-vault-v2/untitled-note-18.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled note 18 -type: Note -status: Active ---- - -# Untitled note 18 - diff --git a/demo-vault-v2/untitled-note-180.md b/demo-vault-v2/untitled-note-180.md deleted file mode 100644 index 4b407ce4..00000000 --- a/demo-vault-v2/untitled-note-180.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -title: Untitled note 180 -type: Note -status: Active ---- diff --git a/demo-vault-v2/untitled-note-181.md b/demo-vault-v2/untitled-note-181.md deleted file mode 100644 index 01827bc6..00000000 --- a/demo-vault-v2/untitled-note-181.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -title: Untitled note 181 -type: Note -status: Active ---- diff --git a/demo-vault-v2/untitled-note-182.md b/demo-vault-v2/untitled-note-182.md deleted file mode 100644 index d82b919b..00000000 --- a/demo-vault-v2/untitled-note-182.md +++ /dev/null @@ -1,6 +0,0 @@ ---- -title: Untitled note 182 -type: Note -status: Active ---- -My Custom H1 Heading diff --git a/demo-vault-v2/untitled-note-183-md-renamed.md b/demo-vault-v2/untitled-note-183-md-renamed.md deleted file mode 100644 index e99b0b73..00000000 --- a/demo-vault-v2/untitled-note-183-md-renamed.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled note 183 -type: Project -status: Active ---- - - -Appended by raw editor test \ No newline at end of file diff --git a/demo-vault-v2/untitled-note-184.md b/demo-vault-v2/untitled-note-184.md deleted file mode 100644 index 35e9cf33..00000000 --- a/demo-vault-v2/untitled-note-184.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled note 184 -type: Note -status: Active ---- -[[2024-03|March 2024]] - -[[2024-03|March 2024]] diff --git a/demo-vault-v2/untitled-note-185.md b/demo-vault-v2/untitled-note-185.md deleted file mode 100644 index a446e759..00000000 --- a/demo-vault-v2/untitled-note-185.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -title: Untitled note 185 -type: Note -status: Active ---- diff --git a/demo-vault-v2/untitled-note-186.md b/demo-vault-v2/untitled-note-186.md deleted file mode 100644 index f8777cf5..00000000 --- a/demo-vault-v2/untitled-note-186.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -title: Untitled note 186 -type: Note -status: Active ---- diff --git a/demo-vault-v2/untitled-note-187.md b/demo-vault-v2/untitled-note-187.md deleted file mode 100644 index 14c9058c..00000000 --- a/demo-vault-v2/untitled-note-187.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -title: Untitled note 187 -type: Note -status: Active ---- diff --git a/demo-vault-v2/untitled-note-188.md b/demo-vault-v2/untitled-note-188.md deleted file mode 100644 index a723d699..00000000 --- a/demo-vault-v2/untitled-note-188.md +++ /dev/null @@ -1,6 +0,0 @@ ---- -title: Untitled note 188 -type: Note -status: Active ---- -My Custom H1 Heading diff --git a/demo-vault-v2/untitled-note-189-md-renamed.md b/demo-vault-v2/untitled-note-189-md-renamed.md deleted file mode 100644 index 8662a40d..00000000 --- a/demo-vault-v2/untitled-note-189-md-renamed.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled note 189 -type: Project -status: Active ---- - - -Appended by raw editor test \ No newline at end of file diff --git a/demo-vault-v2/untitled-note-19.md b/demo-vault-v2/untitled-note-19.md deleted file mode 100644 index 5bb39bd0..00000000 --- a/demo-vault-v2/untitled-note-19.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled note 19 -type: Note -status: Active ---- - -# Untitled note 19 - diff --git a/demo-vault-v2/untitled-note-190.md b/demo-vault-v2/untitled-note-190.md deleted file mode 100644 index 4b342e88..00000000 --- a/demo-vault-v2/untitled-note-190.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled note 190 -type: Note -status: Active ---- -[[2024-03|March 2024]] - -[[2024-03|March 2024]] diff --git a/demo-vault-v2/untitled-note-191.md b/demo-vault-v2/untitled-note-191.md deleted file mode 100644 index c441dd4a..00000000 --- a/demo-vault-v2/untitled-note-191.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -title: Untitled note 191 -type: Note -status: Active ---- diff --git a/demo-vault-v2/untitled-note-192.md b/demo-vault-v2/untitled-note-192.md deleted file mode 100644 index e09febd7..00000000 --- a/demo-vault-v2/untitled-note-192.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -title: Untitled note 192 -type: Note -status: Active ---- diff --git a/demo-vault-v2/untitled-note-193.md b/demo-vault-v2/untitled-note-193.md deleted file mode 100644 index 56784e61..00000000 --- a/demo-vault-v2/untitled-note-193.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -title: Untitled note 193 -type: Note -status: Active ---- diff --git a/demo-vault-v2/untitled-note-194.md b/demo-vault-v2/untitled-note-194.md deleted file mode 100644 index 18c1b03a..00000000 --- a/demo-vault-v2/untitled-note-194.md +++ /dev/null @@ -1,6 +0,0 @@ ---- -title: Untitled note 194 -type: Note -status: Active ---- -My Custom H1 Heading diff --git a/demo-vault-v2/untitled-note-195untitled-note-195-md-renamed.md b/demo-vault-v2/untitled-note-195untitled-note-195-md-renamed.md deleted file mode 100644 index cec9742d..00000000 --- a/demo-vault-v2/untitled-note-195untitled-note-195-md-renamed.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled note 195 -type: Project -status: Active ---- - - -Appended by raw editor test \ No newline at end of file diff --git a/demo-vault-v2/untitled-note-196.md b/demo-vault-v2/untitled-note-196.md deleted file mode 100644 index 64945bd5..00000000 --- a/demo-vault-v2/untitled-note-196.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled note 196 -type: Note -status: Active ---- -[[2024-03|March 2024]] - -[[2024-03|March 2024]] diff --git a/demo-vault-v2/untitled-note-197.md b/demo-vault-v2/untitled-note-197.md deleted file mode 100644 index 1bab1862..00000000 --- a/demo-vault-v2/untitled-note-197.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -title: Untitled note 197 -type: Note -status: Active ---- diff --git a/demo-vault-v2/untitled-note-198.md b/demo-vault-v2/untitled-note-198.md deleted file mode 100644 index 494faef4..00000000 --- a/demo-vault-v2/untitled-note-198.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -title: Untitled note 198 -type: Note -status: Active ---- diff --git a/demo-vault-v2/untitled-note-199.md b/demo-vault-v2/untitled-note-199.md deleted file mode 100644 index 74fb8c49..00000000 --- a/demo-vault-v2/untitled-note-199.md +++ /dev/null @@ -1,6 +0,0 @@ ---- -title: Untitled note 199 -type: Note -status: Active ---- -My Custom H1 Heading diff --git a/demo-vault-v2/untitled-note-2.md b/demo-vault-v2/untitled-note-2.md deleted file mode 100644 index 5153bf71..00000000 --- a/demo-vault-v2/untitled-note-2.md +++ /dev/null @@ -1,10 +0,0 @@ ---- -title: Untitled note 2 -type: Note -status: Active ---- -# Untitled note 2 - -[[March 2024]] - -[[March 2024]] diff --git a/demo-vault-v2/untitled-note-20.md b/demo-vault-v2/untitled-note-20.md deleted file mode 100644 index 6db1899c..00000000 --- a/demo-vault-v2/untitled-note-20.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled note 20 -type: Note -status: Active ---- - -# Untitled note 20 - diff --git a/demo-vault-v2/untitled-note-200untitled-note-200-md-renamed.md b/demo-vault-v2/untitled-note-200untitled-note-200-md-renamed.md deleted file mode 100644 index fbb45604..00000000 --- a/demo-vault-v2/untitled-note-200untitled-note-200-md-renamed.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled note 200 -type: Note -status: Active ---- - - -Appended by raw editor test \ No newline at end of file diff --git a/demo-vault-v2/untitled-note-201.md b/demo-vault-v2/untitled-note-201.md deleted file mode 100644 index 702ba871..00000000 --- a/demo-vault-v2/untitled-note-201.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled note 201 -type: Note -status: Active ---- -[[2024-03|March 2024]] - -[[2024-03|March 2024]] diff --git a/demo-vault-v2/untitled-note-202.md b/demo-vault-v2/untitled-note-202.md deleted file mode 100644 index 5d6c8eea..00000000 --- a/demo-vault-v2/untitled-note-202.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -title: Untitled note 202 -type: Note -status: Active ---- diff --git a/demo-vault-v2/untitled-note-203.md b/demo-vault-v2/untitled-note-203.md deleted file mode 100644 index a7fc436b..00000000 --- a/demo-vault-v2/untitled-note-203.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -title: Untitled note 203 -type: Note -status: Active ---- diff --git a/demo-vault-v2/untitled-note-204.md b/demo-vault-v2/untitled-note-204.md deleted file mode 100644 index 6be90fd1..00000000 --- a/demo-vault-v2/untitled-note-204.md +++ /dev/null @@ -1,6 +0,0 @@ ---- -title: Untitled note 204 -type: Note -status: Active ---- -My Custom H1 Heading diff --git a/demo-vault-v2/untitled-note-205untitled-note-205-md-renamed.md b/demo-vault-v2/untitled-note-205untitled-note-205-md-renamed.md deleted file mode 100644 index 5da31fdd..00000000 --- a/demo-vault-v2/untitled-note-205untitled-note-205-md-renamed.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled note 205 -type: Note -status: Active ---- - - -Appended by raw editor test \ No newline at end of file diff --git a/demo-vault-v2/untitled-note-206.md b/demo-vault-v2/untitled-note-206.md deleted file mode 100644 index ceac9c5a..00000000 --- a/demo-vault-v2/untitled-note-206.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled note 206 -type: Note -status: Active ---- -[[2024-03|March 2024]] - -[[2024-03|March 2024]] diff --git a/demo-vault-v2/untitled-note-207.md b/demo-vault-v2/untitled-note-207.md deleted file mode 100644 index ef39779d..00000000 --- a/demo-vault-v2/untitled-note-207.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -title: Untitled note 207 -type: Note -status: Active ---- diff --git a/demo-vault-v2/untitled-note-208.md b/demo-vault-v2/untitled-note-208.md deleted file mode 100644 index f664eb68..00000000 --- a/demo-vault-v2/untitled-note-208.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -title: Untitled note 208 -type: Note -status: Active ---- diff --git a/demo-vault-v2/untitled-note-209.md b/demo-vault-v2/untitled-note-209.md deleted file mode 100644 index 1265a88a..00000000 --- a/demo-vault-v2/untitled-note-209.md +++ /dev/null @@ -1,6 +0,0 @@ ---- -title: Untitled note 209 -type: Note -status: Active ---- -My Custom H1 Heading diff --git a/demo-vault-v2/untitled-note-21.md b/demo-vault-v2/untitled-note-21.md deleted file mode 100644 index 41ae1a5a..00000000 --- a/demo-vault-v2/untitled-note-21.md +++ /dev/null @@ -1,6 +0,0 @@ ---- -title: Untitled note 21 -type: Note -status: Active ---- -# Untitled note 21My Custom H1 Heading diff --git a/demo-vault-v2/untitled-note-210untitled-note-210-md-renamed.md b/demo-vault-v2/untitled-note-210untitled-note-210-md-renamed.md deleted file mode 100644 index 6d3ba059..00000000 --- a/demo-vault-v2/untitled-note-210untitled-note-210-md-renamed.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled note 210 -type: Note -status: Active ---- - - -Appended by raw editor test \ No newline at end of file diff --git a/demo-vault-v2/untitled-note-211.md b/demo-vault-v2/untitled-note-211.md deleted file mode 100644 index 309ba2ff..00000000 --- a/demo-vault-v2/untitled-note-211.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled note 211 -type: Note -status: Active ---- -[[2024-03|March 2024]] - -[[2024-03|March 2024]] diff --git a/demo-vault-v2/untitled-note-212.md b/demo-vault-v2/untitled-note-212.md deleted file mode 100644 index 2dd7e7b8..00000000 --- a/demo-vault-v2/untitled-note-212.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -title: Untitled note 212 -type: Note -status: Active ---- diff --git a/demo-vault-v2/untitled-note-213.md b/demo-vault-v2/untitled-note-213.md deleted file mode 100644 index 6334f955..00000000 --- a/demo-vault-v2/untitled-note-213.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -title: Untitled note 213 -type: Note -status: Active ---- diff --git a/demo-vault-v2/untitled-note-214.md b/demo-vault-v2/untitled-note-214.md deleted file mode 100644 index cbe8dc49..00000000 --- a/demo-vault-v2/untitled-note-214.md +++ /dev/null @@ -1,6 +0,0 @@ ---- -title: Untitled note 214 -type: Note -status: Active ---- -My Custom H1 Heading diff --git a/demo-vault-v2/untitled-note-215-renamed.md b/demo-vault-v2/untitled-note-215-renamed.md deleted file mode 100644 index 255713e3..00000000 --- a/demo-vault-v2/untitled-note-215-renamed.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled note 215 -type: Note -status: Active ---- - - -Appended by raw editor test \ No newline at end of file diff --git a/demo-vault-v2/untitled-note-216.md b/demo-vault-v2/untitled-note-216.md deleted file mode 100644 index ef8ab901..00000000 --- a/demo-vault-v2/untitled-note-216.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled note 216 -type: Note -status: Active ---- -[[2024-03|March 2024]] - -[[2024-03|March 2024]] diff --git a/demo-vault-v2/untitled-note-217.md b/demo-vault-v2/untitled-note-217.md deleted file mode 100644 index 291e330c..00000000 --- a/demo-vault-v2/untitled-note-217.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -title: Untitled note 217 -type: Note -status: Active ---- diff --git a/demo-vault-v2/untitled-note-218.md b/demo-vault-v2/untitled-note-218.md deleted file mode 100644 index ee68957f..00000000 --- a/demo-vault-v2/untitled-note-218.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -title: Untitled note 218 -type: Note -status: Active ---- diff --git a/demo-vault-v2/untitled-note-219.md b/demo-vault-v2/untitled-note-219.md deleted file mode 100644 index 11ccc99c..00000000 --- a/demo-vault-v2/untitled-note-219.md +++ /dev/null @@ -1,6 +0,0 @@ ---- -title: Untitled note 219 -type: Note -status: Active ---- -My Custom H1 Heading diff --git a/demo-vault-v2/untitled-note-22-md-renamed.md b/demo-vault-v2/untitled-note-22-md-renamed.md deleted file mode 100644 index b612bbdd..00000000 --- a/demo-vault-v2/untitled-note-22-md-renamed.md +++ /dev/null @@ -1,11 +0,0 @@ ---- -title: Untitled note 22 -type: Note -status: Active ---- - -# untitled-note-22.md Renamed - - - -Appended by raw editor test \ No newline at end of file diff --git a/demo-vault-v2/untitled-note-220-renamed.md b/demo-vault-v2/untitled-note-220-renamed.md deleted file mode 100644 index a295128a..00000000 --- a/demo-vault-v2/untitled-note-220-renamed.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled note 220 -type: Project -status: Active ---- - - -Appended by raw editor test \ No newline at end of file diff --git a/demo-vault-v2/untitled-note-221.md b/demo-vault-v2/untitled-note-221.md deleted file mode 100644 index 2c9952a2..00000000 --- a/demo-vault-v2/untitled-note-221.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled note 221 -type: Note -status: Active ---- -[[2024-03|March 2024]] - -[[2024-03|March 2024]] diff --git a/demo-vault-v2/untitled-note-222.md b/demo-vault-v2/untitled-note-222.md deleted file mode 100644 index b1f50ca9..00000000 --- a/demo-vault-v2/untitled-note-222.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -title: Untitled note 222 -type: Note -status: Active ---- diff --git a/demo-vault-v2/untitled-note-223.md b/demo-vault-v2/untitled-note-223.md deleted file mode 100644 index 838354f1..00000000 --- a/demo-vault-v2/untitled-note-223.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -title: Untitled note 223 -type: Note -status: Active ---- diff --git a/demo-vault-v2/untitled-note-224.md b/demo-vault-v2/untitled-note-224.md deleted file mode 100644 index d36aa848..00000000 --- a/demo-vault-v2/untitled-note-224.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -title: Untitled note 224 -type: Note -status: Active ---- diff --git a/demo-vault-v2/untitled-note-225.md b/demo-vault-v2/untitled-note-225.md deleted file mode 100644 index 57285870..00000000 --- a/demo-vault-v2/untitled-note-225.md +++ /dev/null @@ -1,6 +0,0 @@ ---- -title: Untitled note 225 -type: Note -status: Active ---- -My Custom H1 Heading diff --git a/demo-vault-v2/untitled-note-226-renamed.md b/demo-vault-v2/untitled-note-226-renamed.md deleted file mode 100644 index 8fa89d71..00000000 --- a/demo-vault-v2/untitled-note-226-renamed.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled note 226 -type: Note -status: Active ---- - - -Appended by raw editor test \ No newline at end of file diff --git a/demo-vault-v2/untitled-note-227.md b/demo-vault-v2/untitled-note-227.md deleted file mode 100644 index 7f7c7263..00000000 --- a/demo-vault-v2/untitled-note-227.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled note 227 -type: Note -status: Active ---- -[[2024-03|March 2024]] - -[[2024-03|March 2024]] diff --git a/demo-vault-v2/untitled-note-228.md b/demo-vault-v2/untitled-note-228.md deleted file mode 100644 index a785258e..00000000 --- a/demo-vault-v2/untitled-note-228.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -title: Untitled note 228 -type: Note -status: Active ---- diff --git a/demo-vault-v2/untitled-note-229.md b/demo-vault-v2/untitled-note-229.md deleted file mode 100644 index 11d2b846..00000000 --- a/demo-vault-v2/untitled-note-229.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -title: Untitled note 229 -type: Note -status: Active ---- diff --git a/demo-vault-v2/untitled-note-23.md b/demo-vault-v2/untitled-note-23.md deleted file mode 100644 index 0cc0c9a1..00000000 --- a/demo-vault-v2/untitled-note-23.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled note 23 -type: Note -status: Active ---- - -# Untitled note 23 - diff --git a/demo-vault-v2/untitled-note-230.md b/demo-vault-v2/untitled-note-230.md deleted file mode 100644 index 1e53c56e..00000000 --- a/demo-vault-v2/untitled-note-230.md +++ /dev/null @@ -1,6 +0,0 @@ ---- -title: Untitled note 230 -type: Note -status: Active ---- -My Custom H1 Heading diff --git a/demo-vault-v2/untitled-note-231-renamed.md b/demo-vault-v2/untitled-note-231-renamed.md deleted file mode 100644 index 289cfdf3..00000000 --- a/demo-vault-v2/untitled-note-231-renamed.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled note 231 -type: Project -status: Active ---- - - -Appended by raw editor test \ No newline at end of file diff --git a/demo-vault-v2/untitled-note-232.md b/demo-vault-v2/untitled-note-232.md deleted file mode 100644 index c542c4b6..00000000 --- a/demo-vault-v2/untitled-note-232.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled note 232 -type: Note -status: Active ---- -[[2024-03|March 2024]] - -[[2024-03|March 2024]] diff --git a/demo-vault-v2/untitled-note-233.md b/demo-vault-v2/untitled-note-233.md deleted file mode 100644 index 6a955bbb..00000000 --- a/demo-vault-v2/untitled-note-233.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -title: Untitled note 233 -type: Note -status: Active ---- diff --git a/demo-vault-v2/untitled-note-234.md b/demo-vault-v2/untitled-note-234.md deleted file mode 100644 index f945d7ac..00000000 --- a/demo-vault-v2/untitled-note-234.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -title: Untitled note 234 -type: Note -status: Active ---- diff --git a/demo-vault-v2/untitled-note-235.md b/demo-vault-v2/untitled-note-235.md deleted file mode 100644 index 5abdb88d..00000000 --- a/demo-vault-v2/untitled-note-235.md +++ /dev/null @@ -1,6 +0,0 @@ ---- -title: Untitled note 235 -type: Note -status: Active ---- -My Custom H1 Heading diff --git a/demo-vault-v2/untitled-note-236-renamed.md b/demo-vault-v2/untitled-note-236-renamed.md deleted file mode 100644 index 83b58cd4..00000000 --- a/demo-vault-v2/untitled-note-236-renamed.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled note 236 -type: Note -status: Active ---- - - -Appended by raw editor test \ No newline at end of file diff --git a/demo-vault-v2/untitled-note-237.md b/demo-vault-v2/untitled-note-237.md deleted file mode 100644 index cf79b05c..00000000 --- a/demo-vault-v2/untitled-note-237.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled note 237 -type: Note -status: Active ---- -[[2024-03|March 2024]] - -[[2024-03|March 2024]] diff --git a/demo-vault-v2/untitled-note-238.md b/demo-vault-v2/untitled-note-238.md deleted file mode 100644 index ffcd1878..00000000 --- a/demo-vault-v2/untitled-note-238.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -title: Untitled note 238 -type: Note -status: Active ---- diff --git a/demo-vault-v2/untitled-note-239.md b/demo-vault-v2/untitled-note-239.md deleted file mode 100644 index 33f9a92b..00000000 --- a/demo-vault-v2/untitled-note-239.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -title: Untitled note 239 -type: Note -status: Active ---- diff --git a/demo-vault-v2/untitled-note-24.md b/demo-vault-v2/untitled-note-24.md deleted file mode 100644 index 3c4296c4..00000000 --- a/demo-vault-v2/untitled-note-24.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled note 24 -type: Note -status: Active ---- - -# Untitled note 24 - diff --git a/demo-vault-v2/untitled-note-240.md b/demo-vault-v2/untitled-note-240.md deleted file mode 100644 index 92d9eeda..00000000 --- a/demo-vault-v2/untitled-note-240.md +++ /dev/null @@ -1,6 +0,0 @@ ---- -title: Untitled note 240 -type: Note -status: Active ---- -My Custom H1 Heading diff --git a/demo-vault-v2/untitled-note-241-renamed.md b/demo-vault-v2/untitled-note-241-renamed.md deleted file mode 100644 index 9ebd9c96..00000000 --- a/demo-vault-v2/untitled-note-241-renamed.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled note 241 -type: Project -status: Active ---- - - -Appended by raw editor test \ No newline at end of file diff --git a/demo-vault-v2/untitled-note-242.md b/demo-vault-v2/untitled-note-242.md deleted file mode 100644 index 213813f1..00000000 --- a/demo-vault-v2/untitled-note-242.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled note 242 -type: Note -status: Active ---- -[[2024-03|March 2024]] - -[[2024-03|March 2024]] diff --git a/demo-vault-v2/untitled-note-243.md b/demo-vault-v2/untitled-note-243.md deleted file mode 100644 index 6b68b78f..00000000 --- a/demo-vault-v2/untitled-note-243.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -title: Untitled note 243 -type: Note -status: Active ---- diff --git a/demo-vault-v2/untitled-note-244.md b/demo-vault-v2/untitled-note-244.md deleted file mode 100644 index 5ffd1e2e..00000000 --- a/demo-vault-v2/untitled-note-244.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -title: Untitled note 244 -type: Note -status: Active ---- diff --git a/demo-vault-v2/untitled-note-245.md b/demo-vault-v2/untitled-note-245.md deleted file mode 100644 index 8ac1a81a..00000000 --- a/demo-vault-v2/untitled-note-245.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -title: Untitled note 245 -type: Note -status: Active ---- diff --git a/demo-vault-v2/untitled-note-246-renamed.md b/demo-vault-v2/untitled-note-246-renamed.md deleted file mode 100644 index bd830905..00000000 --- a/demo-vault-v2/untitled-note-246-renamed.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled note 246 -type: Note -status: Active ---- - - -Appended by raw editor test \ No newline at end of file diff --git a/demo-vault-v2/untitled-note-247.md b/demo-vault-v2/untitled-note-247.md deleted file mode 100644 index 56ce8bf0..00000000 --- a/demo-vault-v2/untitled-note-247.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled note 247 -type: Note -status: Active ---- -[[2024-03|March 2024]] - -[[2024-03|March 2024]] diff --git a/demo-vault-v2/untitled-note-248.md b/demo-vault-v2/untitled-note-248.md deleted file mode 100644 index 219407fb..00000000 --- a/demo-vault-v2/untitled-note-248.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -title: Untitled note 248 -type: Note -status: Active ---- diff --git a/demo-vault-v2/untitled-note-249.md b/demo-vault-v2/untitled-note-249.md deleted file mode 100644 index 97558a9d..00000000 --- a/demo-vault-v2/untitled-note-249.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -title: Untitled note 249 -type: Note -status: Active ---- diff --git a/demo-vault-v2/untitled-note-25.md b/demo-vault-v2/untitled-note-25.md deleted file mode 100644 index 802ee585..00000000 --- a/demo-vault-v2/untitled-note-25.md +++ /dev/null @@ -1,6 +0,0 @@ ---- -title: Untitled note 25 -type: Note -status: Active ---- -# Untitled note 25My Custom H1 Heading diff --git a/demo-vault-v2/untitled-note-250.md b/demo-vault-v2/untitled-note-250.md deleted file mode 100644 index e7bf5415..00000000 --- a/demo-vault-v2/untitled-note-250.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -title: Untitled note 250 -type: Note -status: Active ---- diff --git a/demo-vault-v2/untitled-note-251.md b/demo-vault-v2/untitled-note-251.md deleted file mode 100644 index 3f440faf..00000000 --- a/demo-vault-v2/untitled-note-251.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -title: Untitled note 251 -type: Note -status: Active ---- diff --git a/demo-vault-v2/untitled-note-252.md b/demo-vault-v2/untitled-note-252.md deleted file mode 100644 index 1c730462..00000000 --- a/demo-vault-v2/untitled-note-252.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -title: Untitled note 252 -type: Note -status: Active ---- diff --git a/demo-vault-v2/untitled-note-253.md b/demo-vault-v2/untitled-note-253.md deleted file mode 100644 index 5b9b3df7..00000000 --- a/demo-vault-v2/untitled-note-253.md +++ /dev/null @@ -1,6 +0,0 @@ ---- -title: Untitled note 253 -type: Note -status: Active ---- -My Custom H1 Heading diff --git a/demo-vault-v2/untitled-note-254-renamed.md b/demo-vault-v2/untitled-note-254-renamed.md deleted file mode 100644 index b0f8ccff..00000000 --- a/demo-vault-v2/untitled-note-254-renamed.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled note 254 -type: Note -status: Active ---- - - -Appended by raw editor test \ No newline at end of file diff --git a/demo-vault-v2/untitled-note-255.md b/demo-vault-v2/untitled-note-255.md deleted file mode 100644 index 6dcce8d2..00000000 --- a/demo-vault-v2/untitled-note-255.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -title: Untitled note 255 -type: Note -status: Active ---- diff --git a/demo-vault-v2/untitled-note-256.md b/demo-vault-v2/untitled-note-256.md deleted file mode 100644 index 97a79fc6..00000000 --- a/demo-vault-v2/untitled-note-256.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -title: Untitled note 256 -type: Note -status: Active ---- diff --git a/demo-vault-v2/untitled-note-257.md b/demo-vault-v2/untitled-note-257.md deleted file mode 100644 index 3b848eb0..00000000 --- a/demo-vault-v2/untitled-note-257.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -title: Untitled note 257 -type: Note -status: Active ---- diff --git a/demo-vault-v2/untitled-note-258.md b/demo-vault-v2/untitled-note-258.md deleted file mode 100644 index 14b8da43..00000000 --- a/demo-vault-v2/untitled-note-258.md +++ /dev/null @@ -1,6 +0,0 @@ ---- -title: Untitled note 258 -type: Note -status: Active ---- -My Custom H1 Heading diff --git a/demo-vault-v2/untitled-note-259.md b/demo-vault-v2/untitled-note-259.md deleted file mode 100644 index 3dcd562c..00000000 --- a/demo-vault-v2/untitled-note-259.md +++ /dev/null @@ -1,6 +0,0 @@ ---- -title: Untitled note 259 -type: Note -status: Active ---- -My Custom H1 Heading diff --git a/demo-vault-v2/untitled-note-26-md-renamed.md b/demo-vault-v2/untitled-note-26-md-renamed.md deleted file mode 100644 index 799351fe..00000000 --- a/demo-vault-v2/untitled-note-26-md-renamed.md +++ /dev/null @@ -1,11 +0,0 @@ ---- -title: Untitled note 26 -type: Project -status: Active ---- - -# untitled-note-26.md Renamed - - - -Appended by raw editor test \ No newline at end of file diff --git a/demo-vault-v2/untitled-note-260-renamed.md b/demo-vault-v2/untitled-note-260-renamed.md deleted file mode 100644 index e6263816..00000000 --- a/demo-vault-v2/untitled-note-260-renamed.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled note 260 -type: Project -status: Active ---- - - -Appended by raw editor test \ No newline at end of file diff --git a/demo-vault-v2/untitled-note-261.md b/demo-vault-v2/untitled-note-261.md deleted file mode 100644 index 3aba27c3..00000000 --- a/demo-vault-v2/untitled-note-261.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled note 261 -type: Note -status: Active ---- -[[2024-03|March 2024]] - -[[2024-03|March 2024]] diff --git a/demo-vault-v2/untitled-note-262.md b/demo-vault-v2/untitled-note-262.md deleted file mode 100644 index 13a58c3e..00000000 --- a/demo-vault-v2/untitled-note-262.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -title: Untitled note 262 -type: Note -status: Active ---- diff --git a/demo-vault-v2/untitled-note-263.md b/demo-vault-v2/untitled-note-263.md deleted file mode 100644 index 001ec8e3..00000000 --- a/demo-vault-v2/untitled-note-263.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -title: Untitled note 263 -type: Note -status: Active ---- diff --git a/demo-vault-v2/untitled-note-264.md b/demo-vault-v2/untitled-note-264.md deleted file mode 100644 index ea97bf07..00000000 --- a/demo-vault-v2/untitled-note-264.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -title: Untitled note 264 -type: Note -status: Active ---- diff --git a/demo-vault-v2/untitled-note-265.md b/demo-vault-v2/untitled-note-265.md deleted file mode 100644 index 76fc1fe3..00000000 --- a/demo-vault-v2/untitled-note-265.md +++ /dev/null @@ -1,6 +0,0 @@ ---- -title: Untitled note 265 -type: Note -status: Active ---- -My Custom H1 Heading diff --git a/demo-vault-v2/untitled-note-266-renamed.md b/demo-vault-v2/untitled-note-266-renamed.md deleted file mode 100644 index 28aa3ac7..00000000 --- a/demo-vault-v2/untitled-note-266-renamed.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled note 266 -type: Project -status: Active ---- - - -Appended by raw editor test \ No newline at end of file diff --git a/demo-vault-v2/untitled-note-267.md b/demo-vault-v2/untitled-note-267.md deleted file mode 100644 index a637139f..00000000 --- a/demo-vault-v2/untitled-note-267.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled note 267 -type: Note -status: Active ---- -[[2024-03|March 2024]] - -[[2024-03|March 2024]] diff --git a/demo-vault-v2/untitled-note-268.md b/demo-vault-v2/untitled-note-268.md deleted file mode 100644 index 1fa52e27..00000000 --- a/demo-vault-v2/untitled-note-268.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -title: Untitled note 268 -type: Note -status: Active ---- diff --git a/demo-vault-v2/untitled-note-269.md b/demo-vault-v2/untitled-note-269.md deleted file mode 100644 index 8558d4e1..00000000 --- a/demo-vault-v2/untitled-note-269.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -title: Untitled note 269 -type: Note -status: Active ---- diff --git a/demo-vault-v2/untitled-note-27.md b/demo-vault-v2/untitled-note-27.md deleted file mode 100644 index 3239064c..00000000 --- a/demo-vault-v2/untitled-note-27.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled note 27 -type: Note -status: Active ---- - -# Untitled note 27 - diff --git a/demo-vault-v2/untitled-note-270.md b/demo-vault-v2/untitled-note-270.md deleted file mode 100644 index 174e9b54..00000000 --- a/demo-vault-v2/untitled-note-270.md +++ /dev/null @@ -1,6 +0,0 @@ ---- -title: Untitled note 270 -type: Note -status: Active ---- -My Custom H1 Heading diff --git a/demo-vault-v2/untitled-note-271-renamed.md b/demo-vault-v2/untitled-note-271-renamed.md deleted file mode 100644 index ef2a3934..00000000 --- a/demo-vault-v2/untitled-note-271-renamed.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled note 271 -type: Project -status: Active ---- - - -Appended by raw editor test \ No newline at end of file diff --git a/demo-vault-v2/untitled-note-272.md b/demo-vault-v2/untitled-note-272.md deleted file mode 100644 index 81b066ab..00000000 --- a/demo-vault-v2/untitled-note-272.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled note 272 -type: Note -status: Active ---- -[[2024-03|March 2024]] - -[[2024-03|March 2024]] diff --git a/demo-vault-v2/untitled-note-273.md b/demo-vault-v2/untitled-note-273.md deleted file mode 100644 index 0a623551..00000000 --- a/demo-vault-v2/untitled-note-273.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -title: Untitled note 273 -type: Note -status: Active ---- diff --git a/demo-vault-v2/untitled-note-274.md b/demo-vault-v2/untitled-note-274.md deleted file mode 100644 index 0402971d..00000000 --- a/demo-vault-v2/untitled-note-274.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -title: Untitled note 274 -type: Note -status: Active ---- diff --git a/demo-vault-v2/untitled-note-275.md b/demo-vault-v2/untitled-note-275.md deleted file mode 100644 index ed6a505b..00000000 --- a/demo-vault-v2/untitled-note-275.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -title: Untitled note 275 -type: Note -status: Active ---- diff --git a/demo-vault-v2/untitled-note-276.md b/demo-vault-v2/untitled-note-276.md deleted file mode 100644 index 08c65885..00000000 --- a/demo-vault-v2/untitled-note-276.md +++ /dev/null @@ -1,6 +0,0 @@ ---- -title: Untitled note 276 -type: Note -status: Active ---- -My Custom H1 Heading diff --git a/demo-vault-v2/untitled-note-277.md b/demo-vault-v2/untitled-note-277.md deleted file mode 100644 index e5d74196..00000000 --- a/demo-vault-v2/untitled-note-277.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled note 277 -type: Note -status: Active ---- -[[2024-03|March 2024]] - -[[2024-03|March 2024]] diff --git a/demo-vault-v2/untitled-note-278.md b/demo-vault-v2/untitled-note-278.md deleted file mode 100644 index 37f4f97e..00000000 --- a/demo-vault-v2/untitled-note-278.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -title: Untitled note 278 -type: Note -status: Active ---- diff --git a/demo-vault-v2/untitled-note-279.md b/demo-vault-v2/untitled-note-279.md deleted file mode 100644 index 4683016e..00000000 --- a/demo-vault-v2/untitled-note-279.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -title: Untitled note 279 -type: Note -status: Active ---- diff --git a/demo-vault-v2/untitled-note-28.md b/demo-vault-v2/untitled-note-28.md deleted file mode 100644 index 6aa84f82..00000000 --- a/demo-vault-v2/untitled-note-28.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled note 28 -type: Note -status: Active ---- - -# Untitled note 28 - diff --git a/demo-vault-v2/untitled-note-280.md b/demo-vault-v2/untitled-note-280.md deleted file mode 100644 index 28ed833f..00000000 --- a/demo-vault-v2/untitled-note-280.md +++ /dev/null @@ -1,6 +0,0 @@ ---- -title: Untitled note 280 -type: Note -status: Active ---- -My Custom H1 Heading diff --git a/demo-vault-v2/untitled-note-281-renamed.md b/demo-vault-v2/untitled-note-281-renamed.md deleted file mode 100644 index 1b932658..00000000 --- a/demo-vault-v2/untitled-note-281-renamed.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled note 281 -type: Project -status: Active ---- - - -Appended by raw editor test \ No newline at end of file diff --git a/demo-vault-v2/untitled-note-282.md b/demo-vault-v2/untitled-note-282.md deleted file mode 100644 index ab2ec769..00000000 --- a/demo-vault-v2/untitled-note-282.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -title: Untitled note 282 -type: Note -status: Active ---- diff --git a/demo-vault-v2/untitled-note-283.md b/demo-vault-v2/untitled-note-283.md deleted file mode 100644 index 08668ea3..00000000 --- a/demo-vault-v2/untitled-note-283.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -title: Untitled note 283 -type: Note -status: Active ---- diff --git a/demo-vault-v2/untitled-note-284.md b/demo-vault-v2/untitled-note-284.md deleted file mode 100644 index 2eff4fde..00000000 --- a/demo-vault-v2/untitled-note-284.md +++ /dev/null @@ -1,6 +0,0 @@ ---- -title: Untitled note 284 -type: Note -status: Active ---- -My Custom H1 Heading diff --git a/demo-vault-v2/untitled-note-285-renamed.md b/demo-vault-v2/untitled-note-285-renamed.md deleted file mode 100644 index 884b1d32..00000000 --- a/demo-vault-v2/untitled-note-285-renamed.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled note 285 -type: Project -status: Active ---- - - -Appended by raw editor test \ No newline at end of file diff --git a/demo-vault-v2/untitled-note-286.md b/demo-vault-v2/untitled-note-286.md deleted file mode 100644 index 8473378e..00000000 --- a/demo-vault-v2/untitled-note-286.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled note 286 -type: Note -status: Active ---- -[[2024-03|March 2024]] - -[[2024-03|March 2024]] diff --git a/demo-vault-v2/untitled-note-287.md b/demo-vault-v2/untitled-note-287.md deleted file mode 100644 index 195ce96c..00000000 --- a/demo-vault-v2/untitled-note-287.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -title: Untitled note 287 -type: Note -status: Active ---- diff --git a/demo-vault-v2/untitled-note-288.md b/demo-vault-v2/untitled-note-288.md deleted file mode 100644 index 4fef9a31..00000000 --- a/demo-vault-v2/untitled-note-288.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -title: Untitled note 288 -type: Note -status: Active ---- diff --git a/demo-vault-v2/untitled-note-289.md b/demo-vault-v2/untitled-note-289.md deleted file mode 100644 index bf60279c..00000000 --- a/demo-vault-v2/untitled-note-289.md +++ /dev/null @@ -1,6 +0,0 @@ ---- -title: Untitled note 289 -type: Note -status: Active ---- -My Custom H1 Heading diff --git a/demo-vault-v2/untitled-note-29.md b/demo-vault-v2/untitled-note-29.md deleted file mode 100644 index 0ad4bb62..00000000 --- a/demo-vault-v2/untitled-note-29.md +++ /dev/null @@ -1,6 +0,0 @@ ---- -title: Untitled note 29 -type: Note -status: Active ---- -# Untitled note 29My Custom H1 Heading diff --git a/demo-vault-v2/untitled-note-290-renamed.md b/demo-vault-v2/untitled-note-290-renamed.md deleted file mode 100644 index 66600d29..00000000 --- a/demo-vault-v2/untitled-note-290-renamed.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled note 290 -type: Project -status: Active ---- - - -Appended by raw editor test \ No newline at end of file diff --git a/demo-vault-v2/untitled-note-291.md b/demo-vault-v2/untitled-note-291.md deleted file mode 100644 index 3b9031e9..00000000 --- a/demo-vault-v2/untitled-note-291.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled note 291 -type: Note -status: Active ---- -[[2024-03|March 2024]] - -[[2024-03|March 2024]] diff --git a/demo-vault-v2/untitled-note-292.md b/demo-vault-v2/untitled-note-292.md deleted file mode 100644 index 9644c1fc..00000000 --- a/demo-vault-v2/untitled-note-292.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -title: Untitled note 292 -type: Note -status: Active ---- diff --git a/demo-vault-v2/untitled-note-293.md b/demo-vault-v2/untitled-note-293.md deleted file mode 100644 index d074a21b..00000000 --- a/demo-vault-v2/untitled-note-293.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -title: Untitled note 293 -type: Note -status: Active ---- diff --git a/demo-vault-v2/untitled-note-294.md b/demo-vault-v2/untitled-note-294.md deleted file mode 100644 index 87c0aad3..00000000 --- a/demo-vault-v2/untitled-note-294.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -title: Untitled note 294 -type: Note -status: Active ---- diff --git a/demo-vault-v2/untitled-note-295.md b/demo-vault-v2/untitled-note-295.md deleted file mode 100644 index de1592b8..00000000 --- a/demo-vault-v2/untitled-note-295.md +++ /dev/null @@ -1,6 +0,0 @@ ---- -title: Untitled note 295 -type: Note -status: Active ---- -My Custom H1 Heading diff --git a/demo-vault-v2/untitled-note-296-renamed.md b/demo-vault-v2/untitled-note-296-renamed.md deleted file mode 100644 index b6e96cdf..00000000 --- a/demo-vault-v2/untitled-note-296-renamed.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled note 296 -type: Project -status: Active ---- - - -Appended by raw editor test \ No newline at end of file diff --git a/demo-vault-v2/untitled-note-297.md b/demo-vault-v2/untitled-note-297.md deleted file mode 100644 index 392faa79..00000000 --- a/demo-vault-v2/untitled-note-297.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled note 297 -type: Note -status: Active ---- -[[2024-03|March 2024]] - -[[2024-03|March 2024]] diff --git a/demo-vault-v2/untitled-note-298.md b/demo-vault-v2/untitled-note-298.md deleted file mode 100644 index 6c9c45ab..00000000 --- a/demo-vault-v2/untitled-note-298.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -title: Untitled note 298 -type: Note -status: Active ---- diff --git a/demo-vault-v2/untitled-note-299.md b/demo-vault-v2/untitled-note-299.md deleted file mode 100644 index 20906c22..00000000 --- a/demo-vault-v2/untitled-note-299.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -title: Untitled note 299 -type: Note -status: Active ---- diff --git a/demo-vault-v2/untitled-note-3.md b/demo-vault-v2/untitled-note-3.md deleted file mode 100644 index c5cdd3c1..00000000 --- a/demo-vault-v2/untitled-note-3.md +++ /dev/null @@ -1,10 +0,0 @@ ---- -title: Untitled note 3 -type: Note -status: Active ---- -# Cycle Two Title - -[[March 2024]] Appended by raw editor test - -[[March 2024]] diff --git a/demo-vault-v2/untitled-note-30-md-renamed.md b/demo-vault-v2/untitled-note-30-md-renamed.md deleted file mode 100644 index f8d29f4e..00000000 --- a/demo-vault-v2/untitled-note-30-md-renamed.md +++ /dev/null @@ -1,11 +0,0 @@ ---- -title: Untitled note 30 -type: Project -status: Active ---- - -# untitled-note-30.md Renamed - - - -Appended by raw editor test \ No newline at end of file diff --git a/demo-vault-v2/untitled-note-300.md b/demo-vault-v2/untitled-note-300.md deleted file mode 100644 index 9ef8b6a1..00000000 --- a/demo-vault-v2/untitled-note-300.md +++ /dev/null @@ -1,6 +0,0 @@ ---- -title: Untitled note 300 -type: Note -status: Active ---- -My Custom H1 Heading diff --git a/demo-vault-v2/untitled-note-301-renamed.md b/demo-vault-v2/untitled-note-301-renamed.md deleted file mode 100644 index 869eb0bd..00000000 --- a/demo-vault-v2/untitled-note-301-renamed.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled note 301 -type: Project -status: Active ---- - - -Appended by raw editor test \ No newline at end of file diff --git a/demo-vault-v2/untitled-note-302.md b/demo-vault-v2/untitled-note-302.md deleted file mode 100644 index 291e2b30..00000000 --- a/demo-vault-v2/untitled-note-302.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled note 302 -type: Note -status: Active ---- -[[2024-03|March 2024]] - -[[2024-03|March 2024]] diff --git a/demo-vault-v2/untitled-note-303.md b/demo-vault-v2/untitled-note-303.md deleted file mode 100644 index 62e6f3c9..00000000 --- a/demo-vault-v2/untitled-note-303.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -title: Untitled note 303 -type: Note -status: Active ---- diff --git a/demo-vault-v2/untitled-note-304.md b/demo-vault-v2/untitled-note-304.md deleted file mode 100644 index 9cabcd4e..00000000 --- a/demo-vault-v2/untitled-note-304.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -title: Untitled note 304 -type: Note -status: Active ---- diff --git a/demo-vault-v2/untitled-note-305.md b/demo-vault-v2/untitled-note-305.md deleted file mode 100644 index 254aed21..00000000 --- a/demo-vault-v2/untitled-note-305.md +++ /dev/null @@ -1,6 +0,0 @@ ---- -title: Untitled note 305 -type: Note -status: Active ---- -My Custom H1 Heading diff --git a/demo-vault-v2/untitled-note-306-renamed.md b/demo-vault-v2/untitled-note-306-renamed.md deleted file mode 100644 index 022bfc95..00000000 --- a/demo-vault-v2/untitled-note-306-renamed.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled note 306 -type: Project -status: Active ---- - - -Appended by raw editor test \ No newline at end of file diff --git a/demo-vault-v2/untitled-note-307.md b/demo-vault-v2/untitled-note-307.md deleted file mode 100644 index fc64c17d..00000000 --- a/demo-vault-v2/untitled-note-307.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled note 307 -type: Note -status: Active ---- -[[2024-03|March 2024]] - -[[2024-03|March 2024]] diff --git a/demo-vault-v2/untitled-note-308.md b/demo-vault-v2/untitled-note-308.md deleted file mode 100644 index 0bb3a01c..00000000 --- a/demo-vault-v2/untitled-note-308.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -title: Untitled note 308 -type: Note -status: Active ---- diff --git a/demo-vault-v2/untitled-note-309.md b/demo-vault-v2/untitled-note-309.md deleted file mode 100644 index 17841177..00000000 --- a/demo-vault-v2/untitled-note-309.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -title: Untitled note 309 -type: Note -status: Active ---- diff --git a/demo-vault-v2/untitled-note-31.md b/demo-vault-v2/untitled-note-31.md deleted file mode 100644 index 6cc09aed..00000000 --- a/demo-vault-v2/untitled-note-31.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled note 31 -type: Note -status: Active ---- - -# Untitled note 31 - diff --git a/demo-vault-v2/untitled-note-310.md b/demo-vault-v2/untitled-note-310.md deleted file mode 100644 index a763b75f..00000000 --- a/demo-vault-v2/untitled-note-310.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -title: Untitled note 310 -type: Note -status: Active ---- diff --git a/demo-vault-v2/untitled-note-311-renamed.md b/demo-vault-v2/untitled-note-311-renamed.md deleted file mode 100644 index 82eb9783..00000000 --- a/demo-vault-v2/untitled-note-311-renamed.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled note 311 -type: Project -status: Active ---- - - -Appended by raw editor test \ No newline at end of file diff --git a/demo-vault-v2/untitled-note-312.md b/demo-vault-v2/untitled-note-312.md deleted file mode 100644 index 5fd503d0..00000000 --- a/demo-vault-v2/untitled-note-312.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled note 312 -type: Note -status: Active ---- -[[2024-03|March 2024]] - -[[2024-03|March 2024]] diff --git a/demo-vault-v2/untitled-note-313.md b/demo-vault-v2/untitled-note-313.md deleted file mode 100644 index 756fce11..00000000 --- a/demo-vault-v2/untitled-note-313.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -title: Untitled note 313 -type: Note -status: Active ---- diff --git a/demo-vault-v2/untitled-note-314.md b/demo-vault-v2/untitled-note-314.md deleted file mode 100644 index 1f357e6e..00000000 --- a/demo-vault-v2/untitled-note-314.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -title: Untitled note 314 -type: Note -status: Active ---- diff --git a/demo-vault-v2/untitled-note-315.md b/demo-vault-v2/untitled-note-315.md deleted file mode 100644 index 4d3934e7..00000000 --- a/demo-vault-v2/untitled-note-315.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -title: Untitled note 315 -type: Note -status: Active ---- diff --git a/demo-vault-v2/untitled-note-316.md b/demo-vault-v2/untitled-note-316.md deleted file mode 100644 index 200971ca..00000000 --- a/demo-vault-v2/untitled-note-316.md +++ /dev/null @@ -1,6 +0,0 @@ ---- -title: Untitled note 316 -type: Note -status: Active ---- -My Custom H1 Heading diff --git a/demo-vault-v2/untitled-note-317.md b/demo-vault-v2/untitled-note-317.md deleted file mode 100644 index 99a0a9f1..00000000 --- a/demo-vault-v2/untitled-note-317.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -title: Untitled note 317 -type: Note -status: Active ---- diff --git a/demo-vault-v2/untitled-note-318.md b/demo-vault-v2/untitled-note-318.md deleted file mode 100644 index 78445c4b..00000000 --- a/demo-vault-v2/untitled-note-318.md +++ /dev/null @@ -1,6 +0,0 @@ ---- -title: Untitled note 318 -type: Note -status: Active ---- -My Custom H1 Heading diff --git a/demo-vault-v2/untitled-note-319-renamed.md b/demo-vault-v2/untitled-note-319-renamed.md deleted file mode 100644 index 5b9f9aa1..00000000 --- a/demo-vault-v2/untitled-note-319-renamed.md +++ /dev/null @@ -1,6 +0,0 @@ ---- -title: Untitled note 319 -type: Project -status: Active ---- -Appended by raw editor test diff --git a/demo-vault-v2/untitled-note-32.md b/demo-vault-v2/untitled-note-32.md deleted file mode 100644 index eccc4bef..00000000 --- a/demo-vault-v2/untitled-note-32.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled note 32 -type: Note -status: Active ---- - -# Untitled note 32 - diff --git a/demo-vault-v2/untitled-note-320.md b/demo-vault-v2/untitled-note-320.md deleted file mode 100644 index 607d5856..00000000 --- a/demo-vault-v2/untitled-note-320.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -title: Untitled note 320 -type: Note -status: Active ---- diff --git a/demo-vault-v2/untitled-note-321.md b/demo-vault-v2/untitled-note-321.md deleted file mode 100644 index 828d479e..00000000 --- a/demo-vault-v2/untitled-note-321.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -title: Untitled note 321 -type: Note -status: Active ---- diff --git a/demo-vault-v2/untitled-note-322.md b/demo-vault-v2/untitled-note-322.md deleted file mode 100644 index 21a0671f..00000000 --- a/demo-vault-v2/untitled-note-322.md +++ /dev/null @@ -1,6 +0,0 @@ ---- -title: Untitled note 322 -type: Note -status: Active ---- -My Custom H1 Heading diff --git a/demo-vault-v2/untitled-note-323-renamed.md b/demo-vault-v2/untitled-note-323-renamed.md deleted file mode 100644 index 7ffd1ad3..00000000 --- a/demo-vault-v2/untitled-note-323-renamed.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled note 323 -type: Project -status: Active ---- - - -Appended by raw editor test \ No newline at end of file diff --git a/demo-vault-v2/untitled-note-324.md b/demo-vault-v2/untitled-note-324.md deleted file mode 100644 index 91d757ad..00000000 --- a/demo-vault-v2/untitled-note-324.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled note 324 -type: Note -status: Active ---- -[[2024-03|March 2024]] - -[[2024-03|March 2024]] diff --git a/demo-vault-v2/untitled-note-325.md b/demo-vault-v2/untitled-note-325.md deleted file mode 100644 index 50d577c9..00000000 --- a/demo-vault-v2/untitled-note-325.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -title: Untitled note 325 -type: Note -status: Active ---- diff --git a/demo-vault-v2/untitled-note-326.md b/demo-vault-v2/untitled-note-326.md deleted file mode 100644 index 4e8457b0..00000000 --- a/demo-vault-v2/untitled-note-326.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -title: Untitled note 326 -type: Note -status: Active ---- diff --git a/demo-vault-v2/untitled-note-327.md b/demo-vault-v2/untitled-note-327.md deleted file mode 100644 index 178abda9..00000000 --- a/demo-vault-v2/untitled-note-327.md +++ /dev/null @@ -1,6 +0,0 @@ ---- -title: Untitled note 327 -type: Note -status: Active ---- -My Custom H1 Heading diff --git a/demo-vault-v2/untitled-note-328-renamed.md b/demo-vault-v2/untitled-note-328-renamed.md deleted file mode 100644 index d0b2866c..00000000 --- a/demo-vault-v2/untitled-note-328-renamed.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled note 328 -type: Project -status: Active ---- - - -Appended by raw editor test \ No newline at end of file diff --git a/demo-vault-v2/untitled-note-329.md b/demo-vault-v2/untitled-note-329.md deleted file mode 100644 index 84f16eb0..00000000 --- a/demo-vault-v2/untitled-note-329.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -title: Untitled note 329 -type: Note -status: Active ---- diff --git a/demo-vault-v2/untitled-note-33.md b/demo-vault-v2/untitled-note-33.md deleted file mode 100644 index 58bdc41b..00000000 --- a/demo-vault-v2/untitled-note-33.md +++ /dev/null @@ -1,6 +0,0 @@ ---- -title: Untitled note 33 -type: Note -status: Active ---- -# Untitled note 33My Custom H1 Heading diff --git a/demo-vault-v2/untitled-note-330.md b/demo-vault-v2/untitled-note-330.md deleted file mode 100644 index ee7e278d..00000000 --- a/demo-vault-v2/untitled-note-330.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -title: Untitled note 330 -type: Note -status: Active ---- diff --git a/demo-vault-v2/untitled-note-331.md b/demo-vault-v2/untitled-note-331.md deleted file mode 100644 index 4222b13e..00000000 --- a/demo-vault-v2/untitled-note-331.md +++ /dev/null @@ -1,6 +0,0 @@ ---- -title: Untitled note 331 -type: Note -status: Active ---- -My Custom H1 Heading diff --git a/demo-vault-v2/untitled-note-332.md b/demo-vault-v2/untitled-note-332.md deleted file mode 100644 index efd30334..00000000 --- a/demo-vault-v2/untitled-note-332.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -title: Untitled note 332 -type: Note -status: Active ---- diff --git a/demo-vault-v2/untitled-note-333-renamed.md b/demo-vault-v2/untitled-note-333-renamed.md deleted file mode 100644 index ddc39c78..00000000 --- a/demo-vault-v2/untitled-note-333-renamed.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled note 333 -type: Project -status: Active ---- - - -Appended by raw editor test \ No newline at end of file diff --git a/demo-vault-v2/untitled-note-334-renamed.md b/demo-vault-v2/untitled-note-334-renamed.md deleted file mode 100644 index 999094ac..00000000 --- a/demo-vault-v2/untitled-note-334-renamed.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled note 334 -type: Project -status: Active ---- - - -Appended by raw editor test \ No newline at end of file diff --git a/demo-vault-v2/untitled-note-335.md b/demo-vault-v2/untitled-note-335.md deleted file mode 100644 index 82e72285..00000000 --- a/demo-vault-v2/untitled-note-335.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -title: Untitled note 335 -type: Note -status: Active ---- diff --git a/demo-vault-v2/untitled-note-336.md b/demo-vault-v2/untitled-note-336.md deleted file mode 100644 index 8f6233f9..00000000 --- a/demo-vault-v2/untitled-note-336.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -title: Untitled note 336 -type: Note -status: Active ---- diff --git a/demo-vault-v2/untitled-note-337.md b/demo-vault-v2/untitled-note-337.md deleted file mode 100644 index 24ca7ecd..00000000 --- a/demo-vault-v2/untitled-note-337.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -title: Untitled note 337 -type: Note -status: Active ---- diff --git a/demo-vault-v2/untitled-note-338-renamed.md b/demo-vault-v2/untitled-note-338-renamed.md deleted file mode 100644 index 10b614db..00000000 --- a/demo-vault-v2/untitled-note-338-renamed.md +++ /dev/null @@ -1,6 +0,0 @@ ---- -title: Untitled note 338 -type: Project -status: Active ---- -Appended by raw editor test diff --git a/demo-vault-v2/untitled-note-339.md b/demo-vault-v2/untitled-note-339.md deleted file mode 100644 index 65731c04..00000000 --- a/demo-vault-v2/untitled-note-339.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -title: Untitled note 339 -type: Note -status: Active ---- diff --git a/demo-vault-v2/untitled-note-34-md-renamed.md b/demo-vault-v2/untitled-note-34-md-renamed.md deleted file mode 100644 index e699702c..00000000 --- a/demo-vault-v2/untitled-note-34-md-renamed.md +++ /dev/null @@ -1,11 +0,0 @@ ---- -title: Untitled note 34 -type: Project -status: Active ---- - -# untitled-note-34.md Renamed - - - -Appended by raw editor test \ No newline at end of file diff --git a/demo-vault-v2/untitled-note-340.md b/demo-vault-v2/untitled-note-340.md deleted file mode 100644 index fb889c74..00000000 --- a/demo-vault-v2/untitled-note-340.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -title: Untitled note 340 -type: Note -status: Active ---- diff --git a/demo-vault-v2/untitled-note-341.md b/demo-vault-v2/untitled-note-341.md deleted file mode 100644 index 86d79be1..00000000 --- a/demo-vault-v2/untitled-note-341.md +++ /dev/null @@ -1,6 +0,0 @@ ---- -title: Untitled note 341 -type: Note -status: Active ---- -My Custom H1 Heading diff --git a/demo-vault-v2/untitled-note-342.md b/demo-vault-v2/untitled-note-342.md deleted file mode 100644 index b1d3210b..00000000 --- a/demo-vault-v2/untitled-note-342.md +++ /dev/null @@ -1,6 +0,0 @@ ---- -title: Untitled note 342 -type: Note -status: Active ---- -My Custom H1 Heading diff --git a/demo-vault-v2/untitled-note-343.md b/demo-vault-v2/untitled-note-343.md deleted file mode 100644 index 86940027..00000000 --- a/demo-vault-v2/untitled-note-343.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled note 343 -type: Note -status: Active ---- -[[2024-03|March 2024]] - -[[2024-03|March 2024]] diff --git a/demo-vault-v2/untitled-note-344-renamed.md b/demo-vault-v2/untitled-note-344-renamed.md deleted file mode 100644 index f6e3591d..00000000 --- a/demo-vault-v2/untitled-note-344-renamed.md +++ /dev/null @@ -1,6 +0,0 @@ ---- -title: Untitled note 344 -type: Note -status: Active ---- -My Custom H1 Heading diff --git a/demo-vault-v2/untitled-note-346.md b/demo-vault-v2/untitled-note-346.md deleted file mode 100644 index 0aa864b6..00000000 --- a/demo-vault-v2/untitled-note-346.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -title: Untitled note 346 -type: Note -status: Active ---- diff --git a/demo-vault-v2/untitled-note-347.md b/demo-vault-v2/untitled-note-347.md deleted file mode 100644 index 00a3f030..00000000 --- a/demo-vault-v2/untitled-note-347.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -title: Untitled note 347 -type: Note -status: Active ---- diff --git a/demo-vault-v2/untitled-note-348.md b/demo-vault-v2/untitled-note-348.md deleted file mode 100644 index 3369b558..00000000 --- a/demo-vault-v2/untitled-note-348.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -title: Untitled note 348 -type: Note -status: Active ---- diff --git a/demo-vault-v2/untitled-note-349.md b/demo-vault-v2/untitled-note-349.md deleted file mode 100644 index 40a4b968..00000000 --- a/demo-vault-v2/untitled-note-349.md +++ /dev/null @@ -1,6 +0,0 @@ ---- -title: Untitled note 349 -type: Note -status: Active ---- -My Custom H1 Heading diff --git a/demo-vault-v2/untitled-note-35.md b/demo-vault-v2/untitled-note-35.md deleted file mode 100644 index 0420b503..00000000 --- a/demo-vault-v2/untitled-note-35.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled note 35 -type: Note -status: Active ---- - -# Untitled note 35 - diff --git a/demo-vault-v2/untitled-note-350.md b/demo-vault-v2/untitled-note-350.md deleted file mode 100644 index e570736d..00000000 --- a/demo-vault-v2/untitled-note-350.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -title: Untitled note 350 -type: Note -status: Active ---- diff --git a/demo-vault-v2/untitled-note-351.md b/demo-vault-v2/untitled-note-351.md deleted file mode 100644 index b98824d6..00000000 --- a/demo-vault-v2/untitled-note-351.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -title: Untitled note 351 -type: Note -status: Active ---- diff --git a/demo-vault-v2/untitled-note-352.md b/demo-vault-v2/untitled-note-352.md deleted file mode 100644 index cab8ada0..00000000 --- a/demo-vault-v2/untitled-note-352.md +++ /dev/null @@ -1,6 +0,0 @@ ---- -title: Untitled note 352 -type: Note -status: Active ---- -My Custom H1 Heading diff --git a/demo-vault-v2/untitled-note-353-renamed.md b/demo-vault-v2/untitled-note-353-renamed.md deleted file mode 100644 index d5d02519..00000000 --- a/demo-vault-v2/untitled-note-353-renamed.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled note 353 -type: Project -status: Active ---- - - -Appended by raw editor test \ No newline at end of file diff --git a/demo-vault-v2/untitled-note-354.md b/demo-vault-v2/untitled-note-354.md deleted file mode 100644 index e41b182f..00000000 --- a/demo-vault-v2/untitled-note-354.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled note 354 -type: Note -status: Active ---- -[[2024-03|March 2024]] - -[[2024-03|March 2024]] diff --git a/demo-vault-v2/untitled-note-355.md b/demo-vault-v2/untitled-note-355.md deleted file mode 100644 index 9839c4ca..00000000 --- a/demo-vault-v2/untitled-note-355.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -title: Untitled note 355 -type: Note -status: Active ---- diff --git a/demo-vault-v2/untitled-note-356.md b/demo-vault-v2/untitled-note-356.md deleted file mode 100644 index 1fb43eac..00000000 --- a/demo-vault-v2/untitled-note-356.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -title: Untitled note 356 -type: Note -status: Active ---- diff --git a/demo-vault-v2/untitled-note-357.md b/demo-vault-v2/untitled-note-357.md deleted file mode 100644 index d3ca810b..00000000 --- a/demo-vault-v2/untitled-note-357.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -title: Untitled note 357 -type: Note -status: Active ---- diff --git a/demo-vault-v2/untitled-note-359-renamed.md b/demo-vault-v2/untitled-note-359-renamed.md deleted file mode 100644 index 3c260e2f..00000000 --- a/demo-vault-v2/untitled-note-359-renamed.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled note 359 -type: Project -status: Active ---- - - -Appended by raw editor test \ No newline at end of file diff --git a/demo-vault-v2/untitled-note-36.md b/demo-vault-v2/untitled-note-36.md deleted file mode 100644 index e087e6f8..00000000 --- a/demo-vault-v2/untitled-note-36.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled note 36 -type: Note -status: Active ---- - -# Untitled note 36 - diff --git a/demo-vault-v2/untitled-note-361.md b/demo-vault-v2/untitled-note-361.md deleted file mode 100644 index caacbfc8..00000000 --- a/demo-vault-v2/untitled-note-361.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -title: Untitled note 361 -type: Note -status: Active ---- diff --git a/demo-vault-v2/untitled-note-37.md b/demo-vault-v2/untitled-note-37.md deleted file mode 100644 index 92f4b33a..00000000 --- a/demo-vault-v2/untitled-note-37.md +++ /dev/null @@ -1,6 +0,0 @@ ---- -title: Untitled note 37 -type: Note -status: Active ---- -# Untitled note 37My Custom H1 Heading diff --git a/demo-vault-v2/untitled-note-38-md-renamed.md b/demo-vault-v2/untitled-note-38-md-renamed.md deleted file mode 100644 index d6c90ace..00000000 --- a/demo-vault-v2/untitled-note-38-md-renamed.md +++ /dev/null @@ -1,11 +0,0 @@ ---- -title: Untitled note 38 -type: Project -status: Active ---- - -# untitled-note-38.md Renamed - - - -Appended by raw editor test \ No newline at end of file diff --git a/demo-vault-v2/untitled-note-39.md b/demo-vault-v2/untitled-note-39.md deleted file mode 100644 index 886499e4..00000000 --- a/demo-vault-v2/untitled-note-39.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled note 39 -type: Note -status: Active ---- - -# Untitled note 39 - diff --git a/demo-vault-v2/untitled-note-40.md b/demo-vault-v2/untitled-note-40.md deleted file mode 100644 index 05f56cff..00000000 --- a/demo-vault-v2/untitled-note-40.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled note 40 -type: Note -status: Active ---- - -# Untitled note 40 - diff --git a/demo-vault-v2/untitled-note-41.md b/demo-vault-v2/untitled-note-41.md deleted file mode 100644 index b7452c9b..00000000 --- a/demo-vault-v2/untitled-note-41.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled note 41 -type: Note -status: Active ---- - -# Untitled note 41 - diff --git a/demo-vault-v2/untitled-note-42.md b/demo-vault-v2/untitled-note-42.md deleted file mode 100644 index de457b3b..00000000 --- a/demo-vault-v2/untitled-note-42.md +++ /dev/null @@ -1,6 +0,0 @@ ---- -title: Untitled note 42 -type: Note -status: Active ---- -# Untitled note 42My Custom H1 Heading diff --git a/demo-vault-v2/untitled-note-43-md-renamed.md b/demo-vault-v2/untitled-note-43-md-renamed.md deleted file mode 100644 index 11d53670..00000000 --- a/demo-vault-v2/untitled-note-43-md-renamed.md +++ /dev/null @@ -1,11 +0,0 @@ ---- -title: Untitled note 43 -type: Note -status: Active ---- - -# untitled-note-43.md Renamed - - - -Appended by raw editor test \ No newline at end of file diff --git a/demo-vault-v2/untitled-note-44.md b/demo-vault-v2/untitled-note-44.md deleted file mode 100644 index f3778c01..00000000 --- a/demo-vault-v2/untitled-note-44.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled note 44 -type: Note -status: Active ---- - -# Untitled note 44 - diff --git a/demo-vault-v2/untitled-note-45.md b/demo-vault-v2/untitled-note-45.md deleted file mode 100644 index 7514eb36..00000000 --- a/demo-vault-v2/untitled-note-45.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled note 45 -type: Note -status: Active ---- - -# Untitled note 45 - diff --git a/demo-vault-v2/untitled-note-46.md b/demo-vault-v2/untitled-note-46.md deleted file mode 100644 index 3d48d325..00000000 --- a/demo-vault-v2/untitled-note-46.md +++ /dev/null @@ -1,6 +0,0 @@ ---- -title: Untitled note 46 -type: Note -status: Active ---- -# Untitled note 46My Custom H1 Heading diff --git a/demo-vault-v2/untitled-note-47-md-renamed.md b/demo-vault-v2/untitled-note-47-md-renamed.md deleted file mode 100644 index 5b027e0c..00000000 --- a/demo-vault-v2/untitled-note-47-md-renamed.md +++ /dev/null @@ -1,11 +0,0 @@ ---- -title: Untitled note 47 -type: Project -status: Active ---- - -# untitled-note-47.md Renamed - - - -Appended by raw editor test \ No newline at end of file diff --git a/demo-vault-v2/untitled-note-48.md b/demo-vault-v2/untitled-note-48.md deleted file mode 100644 index 38fd1564..00000000 --- a/demo-vault-v2/untitled-note-48.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled note 48 -type: Note -status: Active ---- - -# Untitled note 48 - diff --git a/demo-vault-v2/untitled-note-49.md b/demo-vault-v2/untitled-note-49.md deleted file mode 100644 index 8c2258b5..00000000 --- a/demo-vault-v2/untitled-note-49.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled note 49 -type: Note -status: Active ---- - -# Untitled note 49 - diff --git a/demo-vault-v2/untitled-note-5.md b/demo-vault-v2/untitled-note-5.md deleted file mode 100644 index 06bd2691..00000000 --- a/demo-vault-v2/untitled-note-5.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled note 5 -type: Note -status: Active ---- - -# Untitled note 5 - diff --git a/demo-vault-v2/untitled-note-50.md b/demo-vault-v2/untitled-note-50.md deleted file mode 100644 index e0407a1a..00000000 --- a/demo-vault-v2/untitled-note-50.md +++ /dev/null @@ -1,6 +0,0 @@ ---- -title: Untitled note 50 -type: Note -status: Active ---- -# Untitled note 50My Custom H1 Heading diff --git a/demo-vault-v2/untitled-note-51-md-renamed.md b/demo-vault-v2/untitled-note-51-md-renamed.md deleted file mode 100644 index b01e2a24..00000000 --- a/demo-vault-v2/untitled-note-51-md-renamed.md +++ /dev/null @@ -1,11 +0,0 @@ ---- -title: Untitled note 51 -type: Project -status: Active ---- - -# untitled-note-51.md Renamed - - - -Appended by raw editor test \ No newline at end of file diff --git a/demo-vault-v2/untitled-note-52.md b/demo-vault-v2/untitled-note-52.md deleted file mode 100644 index a7d26130..00000000 --- a/demo-vault-v2/untitled-note-52.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled note 52 -type: Note -status: Active ---- - -# Untitled note 52 - diff --git a/demo-vault-v2/untitled-note-53.md b/demo-vault-v2/untitled-note-53.md deleted file mode 100644 index 285d0fce..00000000 --- a/demo-vault-v2/untitled-note-53.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled note 53 -type: Note -status: Active ---- - -# Untitled note 53 - diff --git a/demo-vault-v2/untitled-note-54.md b/demo-vault-v2/untitled-note-54.md deleted file mode 100644 index 3427e93d..00000000 --- a/demo-vault-v2/untitled-note-54.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled note 54 -type: Note -status: Active ---- - -# Untitled note 54 - diff --git a/demo-vault-v2/untitled-note-55.md b/demo-vault-v2/untitled-note-55.md deleted file mode 100644 index 4a685018..00000000 --- a/demo-vault-v2/untitled-note-55.md +++ /dev/null @@ -1,6 +0,0 @@ ---- -title: Untitled note 55 -type: Note -status: Active ---- -# Untitled note 55My Custom H1 Heading diff --git a/demo-vault-v2/untitled-note-56-md-renamed.md b/demo-vault-v2/untitled-note-56-md-renamed.md deleted file mode 100644 index 725eae09..00000000 --- a/demo-vault-v2/untitled-note-56-md-renamed.md +++ /dev/null @@ -1,11 +0,0 @@ ---- -title: Untitled note 56 -type: Project -status: Active ---- - -# untitled-note-56.md Renamed - - - -Appended by raw editor test \ No newline at end of file diff --git a/demo-vault-v2/untitled-note-57.md b/demo-vault-v2/untitled-note-57.md deleted file mode 100644 index 541a8685..00000000 --- a/demo-vault-v2/untitled-note-57.md +++ /dev/null @@ -1,10 +0,0 @@ ---- -title: Untitled note 57 -type: Note -status: Active ---- -# Untitled note 57 - -[[2024-03|March 2024]] - -[[2024-03|March 2024]] diff --git a/demo-vault-v2/untitled-note-58.md b/demo-vault-v2/untitled-note-58.md deleted file mode 100644 index 61db6a72..00000000 --- a/demo-vault-v2/untitled-note-58.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled note 58 -type: Note -status: Active ---- - -# Untitled note 58 - diff --git a/demo-vault-v2/untitled-note-59.md b/demo-vault-v2/untitled-note-59.md deleted file mode 100644 index 3ea7d4aa..00000000 --- a/demo-vault-v2/untitled-note-59.md +++ /dev/null @@ -1,6 +0,0 @@ ---- -title: Untitled note 59 -type: Note -status: Active ---- -# Untitled note 59My Custom H1 Heading diff --git a/demo-vault-v2/untitled-note-6.md b/demo-vault-v2/untitled-note-6.md deleted file mode 100644 index 1c4e853d..00000000 --- a/demo-vault-v2/untitled-note-6.md +++ /dev/null @@ -1,10 +0,0 @@ ---- -title: Untitled note 6 -type: Note -status: Active ---- -# Cycle Two Title - -[[2024-03|March 2024]] Appended by raw editor test - -[[2024-03|March 2024]] diff --git a/demo-vault-v2/untitled-note-60-md-renamed.md b/demo-vault-v2/untitled-note-60-md-renamed.md deleted file mode 100644 index f00db4df..00000000 --- a/demo-vault-v2/untitled-note-60-md-renamed.md +++ /dev/null @@ -1,11 +0,0 @@ ---- -title: Untitled note 60 -type: Project -status: Active ---- - -# untitled-note-60.md Renamed - - - -Appended by raw editor test \ No newline at end of file diff --git a/demo-vault-v2/untitled-note-61.md b/demo-vault-v2/untitled-note-61.md deleted file mode 100644 index 30a989b6..00000000 --- a/demo-vault-v2/untitled-note-61.md +++ /dev/null @@ -1,10 +0,0 @@ ---- -title: Untitled note 61 -type: Note -status: Active ---- -# Untitled note 61 - -[[2024-03|March 2024]] - -[[2024-03|March 2024]] diff --git a/demo-vault-v2/untitled-note-62.md b/demo-vault-v2/untitled-note-62.md deleted file mode 100644 index e2d7b9bc..00000000 --- a/demo-vault-v2/untitled-note-62.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled note 62 -type: Note -status: Active ---- - -# Untitled note 62 - diff --git a/demo-vault-v2/untitled-note-63.md b/demo-vault-v2/untitled-note-63.md deleted file mode 100644 index 9f21b70f..00000000 --- a/demo-vault-v2/untitled-note-63.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled note 63 -type: Note -status: Active ---- - -# Untitled note 63 - diff --git a/demo-vault-v2/untitled-note-64.md b/demo-vault-v2/untitled-note-64.md deleted file mode 100644 index 9c62bd74..00000000 --- a/demo-vault-v2/untitled-note-64.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled note 64 -type: Note -status: Active ---- - -# Untitled note 64 - diff --git a/demo-vault-v2/untitled-note-65.md b/demo-vault-v2/untitled-note-65.md deleted file mode 100644 index b58a20fb..00000000 --- a/demo-vault-v2/untitled-note-65.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled note 65 -type: Note -status: Active ---- - -# Untitled note 65 - diff --git a/demo-vault-v2/untitled-note-66.md b/demo-vault-v2/untitled-note-66.md deleted file mode 100644 index 7f498b4d..00000000 --- a/demo-vault-v2/untitled-note-66.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled note 66 -type: Note -status: Active ---- - -# Untitled note 66 - diff --git a/demo-vault-v2/untitled-note-67.md b/demo-vault-v2/untitled-note-67.md deleted file mode 100644 index 61867f08..00000000 --- a/demo-vault-v2/untitled-note-67.md +++ /dev/null @@ -1,6 +0,0 @@ ---- -title: Untitled note 67 -type: Note -status: Active ---- -# Untitled note 67My Custom H1 Heading diff --git a/demo-vault-v2/untitled-note-68-md-renamed.md b/demo-vault-v2/untitled-note-68-md-renamed.md deleted file mode 100644 index 087cbb08..00000000 --- a/demo-vault-v2/untitled-note-68-md-renamed.md +++ /dev/null @@ -1,11 +0,0 @@ ---- -title: Untitled note 68 -type: Project -status: Active ---- - -# untitled-note-68.md Renamed - - - -Appended by raw editor test \ No newline at end of file diff --git a/demo-vault-v2/untitled-note-69.md b/demo-vault-v2/untitled-note-69.md deleted file mode 100644 index 28acdbd3..00000000 --- a/demo-vault-v2/untitled-note-69.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled note 69 -type: Note -status: Active ---- -[[2024-03|March 2024]] - -[[2024-03|March 2024]] diff --git a/demo-vault-v2/untitled-note-7.md b/demo-vault-v2/untitled-note-7.md deleted file mode 100644 index 8a5b937f..00000000 --- a/demo-vault-v2/untitled-note-7.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled note 7 -type: Note -status: Active ---- - -# Untitled note 7 - diff --git a/demo-vault-v2/untitled-note-70.md b/demo-vault-v2/untitled-note-70.md deleted file mode 100644 index 85485703..00000000 --- a/demo-vault-v2/untitled-note-70.md +++ /dev/null @@ -1,6 +0,0 @@ ---- -title: Untitled note 70 -type: Note -status: Active ---- -# Untitled note 70 diff --git a/demo-vault-v2/untitled-note-71.md b/demo-vault-v2/untitled-note-71.md deleted file mode 100644 index bd0f36cb..00000000 --- a/demo-vault-v2/untitled-note-71.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled note 71 -type: Note -status: Active ---- - -# Untitled note 71 - diff --git a/demo-vault-v2/untitled-note-72.md b/demo-vault-v2/untitled-note-72.md deleted file mode 100644 index 4b39a999..00000000 --- a/demo-vault-v2/untitled-note-72.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled note 72 -type: Note -status: Active ---- - -# Untitled note 72 - diff --git a/demo-vault-v2/untitled-note-73.md b/demo-vault-v2/untitled-note-73.md deleted file mode 100644 index 129c1c8e..00000000 --- a/demo-vault-v2/untitled-note-73.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled note 73 -type: Note -status: Active ---- - -# Untitled note 73 - diff --git a/demo-vault-v2/untitled-note-74-md-renamed.md b/demo-vault-v2/untitled-note-74-md-renamed.md deleted file mode 100644 index 9fb0a119..00000000 --- a/demo-vault-v2/untitled-note-74-md-renamed.md +++ /dev/null @@ -1,11 +0,0 @@ ---- -title: Untitled note 74 -type: Project -status: Active ---- - -# untitled-note-74.md Renamed - - - -Appended by raw editor test \ No newline at end of file diff --git a/demo-vault-v2/untitled-note-75.md b/demo-vault-v2/untitled-note-75.md deleted file mode 100644 index 47bc7f8a..00000000 --- a/demo-vault-v2/untitled-note-75.md +++ /dev/null @@ -1,10 +0,0 @@ ---- -title: Untitled note 75 -type: Note -status: Active ---- -# Untitled note 75 - -[[2024-03|March 2024]] - -[[2024-03|March 2024]] diff --git a/demo-vault-v2/untitled-note-76.md b/demo-vault-v2/untitled-note-76.md deleted file mode 100644 index 57b5acca..00000000 --- a/demo-vault-v2/untitled-note-76.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled note 76 -type: Note -status: Active ---- - -# Untitled note 76 - diff --git a/demo-vault-v2/untitled-note-77.md b/demo-vault-v2/untitled-note-77.md deleted file mode 100644 index 38a58234..00000000 --- a/demo-vault-v2/untitled-note-77.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled note 77 -type: Note -status: Active ---- - -# Untitled note 77 - diff --git a/demo-vault-v2/untitled-note-78.md b/demo-vault-v2/untitled-note-78.md deleted file mode 100644 index 37df9866..00000000 --- a/demo-vault-v2/untitled-note-78.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled note 78 -type: Note -status: Active ---- - -# Untitled note 78 - diff --git a/demo-vault-v2/untitled-note-79.md b/demo-vault-v2/untitled-note-79.md deleted file mode 100644 index bd2d71ab..00000000 --- a/demo-vault-v2/untitled-note-79.md +++ /dev/null @@ -1,6 +0,0 @@ ---- -title: Untitled note 79 -type: Note -status: Active ---- -# Untitled note 79My Custom H1 Heading diff --git a/demo-vault-v2/untitled-note-8.md b/demo-vault-v2/untitled-note-8.md deleted file mode 100644 index fdaf166b..00000000 --- a/demo-vault-v2/untitled-note-8.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled note 8 -type: Note -status: Active ---- - -# Untitled note 8 - diff --git a/demo-vault-v2/untitled-note-80.md b/demo-vault-v2/untitled-note-80.md deleted file mode 100644 index 6f69997f..00000000 --- a/demo-vault-v2/untitled-note-80.md +++ /dev/null @@ -1,6 +0,0 @@ ---- -title: Untitled note 80 -type: Note -status: Active ---- -# Untitled note 80My Custom H1 Heading diff --git a/demo-vault-v2/untitled-note-81.md b/demo-vault-v2/untitled-note-81.md deleted file mode 100644 index 4ea75273..00000000 --- a/demo-vault-v2/untitled-note-81.md +++ /dev/null @@ -1,10 +0,0 @@ ---- -title: Untitled note 81 -type: Note -status: Active ---- -# Untitled note 81 - -[[2024-03|March 2024]] - -[[2024-03|March 2024]] diff --git a/demo-vault-v2/untitled-note-82.md b/demo-vault-v2/untitled-note-82.md deleted file mode 100644 index a8a6ae6c..00000000 --- a/demo-vault-v2/untitled-note-82.md +++ /dev/null @@ -1,6 +0,0 @@ ---- -title: Untitled note 82 -type: Note -status: Active ---- -# Updated By Raw Editor diff --git a/demo-vault-v2/untitled-note-83-md-renamed.md b/demo-vault-v2/untitled-note-83-md-renamed.md deleted file mode 100644 index def29697..00000000 --- a/demo-vault-v2/untitled-note-83-md-renamed.md +++ /dev/null @@ -1,13 +0,0 @@ ---- -title: Untitled note 83 -type: Note -status: Active ---- - -# untitled-note-83.md Renamed - - - -Appended by raw editor test - -Appended by raw editor test \ No newline at end of file diff --git a/demo-vault-v2/untitled-note-84.md b/demo-vault-v2/untitled-note-84.md deleted file mode 100644 index 5f47bde2..00000000 --- a/demo-vault-v2/untitled-note-84.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled note 84 -type: Note -status: Active ---- - -# Untitled note 84 - diff --git a/demo-vault-v2/untitled-note-85.md b/demo-vault-v2/untitled-note-85.md deleted file mode 100644 index 9a87c055..00000000 --- a/demo-vault-v2/untitled-note-85.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled note 85 -type: Note -status: Active ---- - -# Untitled note 85 - diff --git a/demo-vault-v2/untitled-note-86.md b/demo-vault-v2/untitled-note-86.md deleted file mode 100644 index 6ac09574..00000000 --- a/demo-vault-v2/untitled-note-86.md +++ /dev/null @@ -1,6 +0,0 @@ ---- -title: Untitled note 86 -type: Note -status: Active ---- -# Untitled note 86My Custom H1 Heading diff --git a/demo-vault-v2/untitled-note-87-md-renamed.md b/demo-vault-v2/untitled-note-87-md-renamed.md deleted file mode 100644 index 235da060..00000000 --- a/demo-vault-v2/untitled-note-87-md-renamed.md +++ /dev/null @@ -1,11 +0,0 @@ ---- -title: Untitled note 87 -type: Project -status: Active ---- - -# untitled-note-87.md Renamed - - - -Appended by raw editor test \ No newline at end of file diff --git a/demo-vault-v2/untitled-note-88.md b/demo-vault-v2/untitled-note-88.md deleted file mode 100644 index 55f3b460..00000000 --- a/demo-vault-v2/untitled-note-88.md +++ /dev/null @@ -1,10 +0,0 @@ ---- -title: Untitled note 88 -type: Note -status: Active ---- -# Untitled note 88 - -[[2024-03|March 2024]] - -[[2024-03|March 2024]] diff --git a/demo-vault-v2/untitled-note-89.md b/demo-vault-v2/untitled-note-89.md deleted file mode 100644 index 616a8738..00000000 --- a/demo-vault-v2/untitled-note-89.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled note 89 -type: Note -status: Active ---- - -# Untitled note 89 - diff --git a/demo-vault-v2/untitled-note-9.md b/demo-vault-v2/untitled-note-9.md deleted file mode 100644 index dcbe5bd4..00000000 --- a/demo-vault-v2/untitled-note-9.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled note 9 -type: Note -status: Active ---- - -# Untitled note 9 - diff --git a/demo-vault-v2/untitled-note-90.md b/demo-vault-v2/untitled-note-90.md deleted file mode 100644 index 38af0e4a..00000000 --- a/demo-vault-v2/untitled-note-90.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled note 90 -type: Note -status: Active ---- - -# Untitled note 90 - diff --git a/demo-vault-v2/untitled-note-91.md b/demo-vault-v2/untitled-note-91.md deleted file mode 100644 index cfa46a53..00000000 --- a/demo-vault-v2/untitled-note-91.md +++ /dev/null @@ -1,6 +0,0 @@ ---- -title: Untitled note 91 -type: Note -status: Active ---- -# Untitled note 91My Custom H1 Heading diff --git a/demo-vault-v2/untitled-note-92-md-renamed.md b/demo-vault-v2/untitled-note-92-md-renamed.md deleted file mode 100644 index bdef4b02..00000000 --- a/demo-vault-v2/untitled-note-92-md-renamed.md +++ /dev/null @@ -1,11 +0,0 @@ ---- -title: Untitled note 92 -type: Project -status: Active ---- - -# untitled-note-92.md Renamed - - - -Appended by raw editor test \ No newline at end of file diff --git a/demo-vault-v2/untitled-note-93.md b/demo-vault-v2/untitled-note-93.md deleted file mode 100644 index 46867069..00000000 --- a/demo-vault-v2/untitled-note-93.md +++ /dev/null @@ -1,10 +0,0 @@ ---- -title: Untitled note 93 -type: Note -status: Active ---- -# Untitled note 93 - -[[2024-03|March 2024]] - -[[2024-03|March 2024]] diff --git a/demo-vault-v2/untitled-note-94.md b/demo-vault-v2/untitled-note-94.md deleted file mode 100644 index b8338fe7..00000000 --- a/demo-vault-v2/untitled-note-94.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled note 94 -type: Note -status: Active ---- - -# Untitled note 94 - diff --git a/demo-vault-v2/untitled-note-95.md b/demo-vault-v2/untitled-note-95.md deleted file mode 100644 index 9f052358..00000000 --- a/demo-vault-v2/untitled-note-95.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled note 95 -type: Note -status: Active ---- - -# Untitled note 95 - diff --git a/demo-vault-v2/untitled-note-96.md b/demo-vault-v2/untitled-note-96.md deleted file mode 100644 index abff69c5..00000000 --- a/demo-vault-v2/untitled-note-96.md +++ /dev/null @@ -1,6 +0,0 @@ ---- -title: Untitled note 96 -type: Note -status: Active ---- -# Untitled note 96My Custom H1 Heading diff --git a/demo-vault-v2/untitled-note-97.md b/demo-vault-v2/untitled-note-97.md deleted file mode 100644 index 5190e674..00000000 --- a/demo-vault-v2/untitled-note-97.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled note 97 -type: Note -status: Active ---- - -# Untitled note 97 - diff --git a/demo-vault-v2/untitled-note-98.md b/demo-vault-v2/untitled-note-98.md deleted file mode 100644 index 3a23503b..00000000 --- a/demo-vault-v2/untitled-note-98.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Untitled note 98 -type: Note -status: Active ---- - -# Untitled note 98 - diff --git a/demo-vault-v2/untitled-note-99.md b/demo-vault-v2/untitled-note-99.md deleted file mode 100644 index fa0f1aea..00000000 --- a/demo-vault-v2/untitled-note-99.md +++ /dev/null @@ -1,6 +0,0 @@ ---- -title: Untitled note 99 -type: Note -status: Active ---- -# Untitled note 99My Custom H1 Heading diff --git a/demo-vault-v2/untitled-note.md b/demo-vault-v2/untitled-note.md deleted file mode 100644 index f56021ac..00000000 --- a/demo-vault-v2/untitled-note.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -title: Untitled note -type: Note -status: Active ---- diff --git a/demo-vault-v2/untitled-project-10.md b/demo-vault-v2/untitled-project-10.md deleted file mode 100644 index 9634d9c5..00000000 --- a/demo-vault-v2/untitled-project-10.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -title: Untitled project 10 -type: Project -status: Active ---- - -# Untitled project 10 - -## Objective - - - -## Key Results - - - -## Notes - diff --git a/demo-vault-v2/untitled-project-11.md b/demo-vault-v2/untitled-project-11.md deleted file mode 100644 index e8b899d9..00000000 --- a/demo-vault-v2/untitled-project-11.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -title: Untitled project 11 -type: Project -status: Active ---- - -# Untitled project 11 - -## Objective - - - -## Key Results - - - -## Notes - diff --git a/demo-vault-v2/untitled-project-12.md b/demo-vault-v2/untitled-project-12.md deleted file mode 100644 index 2cd4b655..00000000 --- a/demo-vault-v2/untitled-project-12.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -title: Untitled project 12 -type: Project -status: Active ---- - -# Untitled project 12 - -## Objective - - - -## Key Results - - - -## Notes - diff --git a/demo-vault-v2/untitled-project-13.md b/demo-vault-v2/untitled-project-13.md deleted file mode 100644 index 896afd4a..00000000 --- a/demo-vault-v2/untitled-project-13.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -title: Untitled project 13 -type: Project -status: Active ---- - -# Untitled project 13 - -## Objective - - - -## Key Results - - - -## Notes - diff --git a/demo-vault-v2/untitled-project-14.md b/demo-vault-v2/untitled-project-14.md deleted file mode 100644 index c65af50a..00000000 --- a/demo-vault-v2/untitled-project-14.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -title: Untitled project 14 -type: Project -status: Active ---- - -# Untitled project 14 - -## Objective - - - -## Key Results - - - -## Notes - diff --git a/demo-vault-v2/untitled-project-15.md b/demo-vault-v2/untitled-project-15.md deleted file mode 100644 index d8a62059..00000000 --- a/demo-vault-v2/untitled-project-15.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -title: Untitled project 15 -type: Project -status: Active ---- - -# Untitled project 15 - -## Objective - - - -## Key Results - - - -## Notes - diff --git a/demo-vault-v2/untitled-project-16.md b/demo-vault-v2/untitled-project-16.md deleted file mode 100644 index 1c208959..00000000 --- a/demo-vault-v2/untitled-project-16.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -title: Untitled project 16 -type: Project -status: Active ---- - -# Untitled project 16 - -## Objective - - - -## Key Results - - - -## Notes - diff --git a/demo-vault-v2/untitled-project-17.md b/demo-vault-v2/untitled-project-17.md deleted file mode 100644 index 0fa3dc74..00000000 --- a/demo-vault-v2/untitled-project-17.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -title: Untitled project 17 -type: Project -status: Active ---- - -# Untitled project 17 - -## Objective - - - -## Key Results - - - -## Notes - diff --git a/demo-vault-v2/untitled-project-1775473964.md b/demo-vault-v2/untitled-project-1775473964.md deleted file mode 100644 index 8f781418..00000000 --- a/demo-vault-v2/untitled-project-1775473964.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -type: Project -status: Active ---- - -## Objective - - - -## Key Results - - - -## Notes - diff --git a/demo-vault-v2/untitled-project-1775497094.md b/demo-vault-v2/untitled-project-1775497094.md deleted file mode 100644 index 8f781418..00000000 --- a/demo-vault-v2/untitled-project-1775497094.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -type: Project -status: Active ---- - -## Objective - - - -## Key Results - - - -## Notes - diff --git a/demo-vault-v2/untitled-project-1775542975.md b/demo-vault-v2/untitled-project-1775542975.md deleted file mode 100644 index 8f781418..00000000 --- a/demo-vault-v2/untitled-project-1775542975.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -type: Project -status: Active ---- - -## Objective - - - -## Key Results - - - -## Notes - diff --git a/demo-vault-v2/untitled-project-18.md b/demo-vault-v2/untitled-project-18.md deleted file mode 100644 index e8e4af9c..00000000 --- a/demo-vault-v2/untitled-project-18.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -title: Untitled project 18 -type: Project -status: Active ---- - -# Untitled project 18 - -## Objective - - - -## Key Results - - - -## Notes - diff --git a/demo-vault-v2/untitled-project-19.md b/demo-vault-v2/untitled-project-19.md deleted file mode 100644 index 5135d69e..00000000 --- a/demo-vault-v2/untitled-project-19.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -title: Untitled project 19 -type: Project -status: Active ---- - -## Objective - - - -## Key Results - - - -## Notes - diff --git a/demo-vault-v2/untitled-project-2.md b/demo-vault-v2/untitled-project-2.md deleted file mode 100644 index 17772bf5..00000000 --- a/demo-vault-v2/untitled-project-2.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -title: Untitled project 2 -type: Project -status: Active ---- - -# Untitled project 2 - -## Objective - - - -## Key Results - - - -## Notes - diff --git a/demo-vault-v2/untitled-project-20.md b/demo-vault-v2/untitled-project-20.md deleted file mode 100644 index 8069c350..00000000 --- a/demo-vault-v2/untitled-project-20.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -title: Untitled project 20 -type: Project -status: Active ---- - -## Objective - - - -## Key Results - - - -## Notes - diff --git a/demo-vault-v2/untitled-project-21.md b/demo-vault-v2/untitled-project-21.md deleted file mode 100644 index 436cde9e..00000000 --- a/demo-vault-v2/untitled-project-21.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -title: Untitled project 21 -type: Project -status: Active ---- - -## Objective - - - -## Key Results - - - -## Notes - diff --git a/demo-vault-v2/untitled-project-22.md b/demo-vault-v2/untitled-project-22.md deleted file mode 100644 index 93c26b0a..00000000 --- a/demo-vault-v2/untitled-project-22.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -title: Untitled project 22 -type: Project -status: Active ---- - -## Objective - - - -## Key Results - - - -## Notes - diff --git a/demo-vault-v2/untitled-project-23.md b/demo-vault-v2/untitled-project-23.md deleted file mode 100644 index 74e5b785..00000000 --- a/demo-vault-v2/untitled-project-23.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -title: Untitled project 23 -type: Project -status: Active ---- - -## Objective - - - -## Key Results - - - -## Notes - diff --git a/demo-vault-v2/untitled-project-24.md b/demo-vault-v2/untitled-project-24.md deleted file mode 100644 index e72e38cd..00000000 --- a/demo-vault-v2/untitled-project-24.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -title: Untitled project 24 -type: Project -status: Active ---- - -## Objective - - - -## Key Results - - - -## Notes - diff --git a/demo-vault-v2/untitled-project-25.md b/demo-vault-v2/untitled-project-25.md deleted file mode 100644 index a43e48b4..00000000 --- a/demo-vault-v2/untitled-project-25.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -title: Untitled project 25 -type: Project -status: Active ---- - -## Objective - - - -## Key Results - - - -## Notes - diff --git a/demo-vault-v2/untitled-project-26.md b/demo-vault-v2/untitled-project-26.md deleted file mode 100644 index 8cbd29dc..00000000 --- a/demo-vault-v2/untitled-project-26.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -title: Untitled project 26 -type: Project -status: Active ---- - -## Objective - - - -## Key Results - - - -## Notes - diff --git a/demo-vault-v2/untitled-project-27.md b/demo-vault-v2/untitled-project-27.md deleted file mode 100644 index 8219e5bf..00000000 --- a/demo-vault-v2/untitled-project-27.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -title: Untitled project 27 -type: Project -status: Active ---- - -## Objective - - - -## Key Results - - - -## Notes - diff --git a/demo-vault-v2/untitled-project-28.md b/demo-vault-v2/untitled-project-28.md deleted file mode 100644 index 26b4b377..00000000 --- a/demo-vault-v2/untitled-project-28.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -title: Untitled project 28 -type: Project -status: Active ---- - -## Objective - - - -## Key Results - - - -## Notes - diff --git a/demo-vault-v2/untitled-project-29.md b/demo-vault-v2/untitled-project-29.md deleted file mode 100644 index 6b761be6..00000000 --- a/demo-vault-v2/untitled-project-29.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -title: Untitled project 29 -type: Project -status: Active ---- - -## Objective - - - -## Key Results - - - -## Notes - diff --git a/demo-vault-v2/untitled-project-3.md b/demo-vault-v2/untitled-project-3.md deleted file mode 100644 index f77f82ee..00000000 --- a/demo-vault-v2/untitled-project-3.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -title: Untitled project 3 -type: Project -status: Active ---- - -# Untitled project 3 - -## Objective - - - -## Key Results - - - -## Notes - diff --git a/demo-vault-v2/untitled-project-30.md b/demo-vault-v2/untitled-project-30.md deleted file mode 100644 index 3a685c50..00000000 --- a/demo-vault-v2/untitled-project-30.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -title: Untitled project 30 -type: Project -status: Active ---- - -## Objective - - - -## Key Results - - - -## Notes - diff --git a/demo-vault-v2/untitled-project-31.md b/demo-vault-v2/untitled-project-31.md deleted file mode 100644 index 0bf900a7..00000000 --- a/demo-vault-v2/untitled-project-31.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -title: Untitled project 31 -type: Project -status: Active ---- - -## Objective - - - -## Key Results - - - -## Notes - diff --git a/demo-vault-v2/untitled-project-32.md b/demo-vault-v2/untitled-project-32.md deleted file mode 100644 index 18f35890..00000000 --- a/demo-vault-v2/untitled-project-32.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -title: Untitled project 32 -type: Project -status: Active ---- - -## Objective - - - -## Key Results - - - -## Notes - diff --git a/demo-vault-v2/untitled-project-33.md b/demo-vault-v2/untitled-project-33.md deleted file mode 100644 index 5f124f30..00000000 --- a/demo-vault-v2/untitled-project-33.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -title: Untitled project 33 -type: Project -status: Active ---- - -## Objective - - - -## Key Results - - - -## Notes - diff --git a/demo-vault-v2/untitled-project-34.md b/demo-vault-v2/untitled-project-34.md deleted file mode 100644 index bc3b12ad..00000000 --- a/demo-vault-v2/untitled-project-34.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -title: Untitled project 34 -type: Project -status: Active ---- - -## Objective - - - -## Key Results - - - -## Notes - diff --git a/demo-vault-v2/untitled-project-35.md b/demo-vault-v2/untitled-project-35.md deleted file mode 100644 index b37755c0..00000000 --- a/demo-vault-v2/untitled-project-35.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -title: Untitled project 35 -type: Project -status: Active ---- - -## Objective - - - -## Key Results - - - -## Notes - diff --git a/demo-vault-v2/untitled-project-36.md b/demo-vault-v2/untitled-project-36.md deleted file mode 100644 index 48958517..00000000 --- a/demo-vault-v2/untitled-project-36.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -title: Untitled project 36 -type: Project -status: Active ---- - -## Objective - - - -## Key Results - - - -## Notes - diff --git a/demo-vault-v2/untitled-project-37.md b/demo-vault-v2/untitled-project-37.md deleted file mode 100644 index 8a340c61..00000000 --- a/demo-vault-v2/untitled-project-37.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -title: Untitled project 37 -type: Project -status: Active ---- - -## Objective - - - -## Key Results - - - -## Notes - diff --git a/demo-vault-v2/untitled-project-38.md b/demo-vault-v2/untitled-project-38.md deleted file mode 100644 index 1fa6a905..00000000 --- a/demo-vault-v2/untitled-project-38.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -title: Untitled project 38 -type: Project -status: Active ---- - -## Objective - - - -## Key Results - - - -## Notes - diff --git a/demo-vault-v2/untitled-project-39.md b/demo-vault-v2/untitled-project-39.md deleted file mode 100644 index ff6cc407..00000000 --- a/demo-vault-v2/untitled-project-39.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -title: Untitled project 39 -type: Project -status: Active ---- - -## Objective - - - -## Key Results - - - -## Notes - diff --git a/demo-vault-v2/untitled-project-4.md b/demo-vault-v2/untitled-project-4.md deleted file mode 100644 index c90cb319..00000000 --- a/demo-vault-v2/untitled-project-4.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -title: Untitled project 4 -type: Project -status: Active ---- - -# Untitled project 4 - -## Objective - - - -## Key Results - - - -## Notes - diff --git a/demo-vault-v2/untitled-project-40.md b/demo-vault-v2/untitled-project-40.md deleted file mode 100644 index 70d4ba18..00000000 --- a/demo-vault-v2/untitled-project-40.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -title: Untitled project 40 -type: Project -status: Active ---- - -## Objective - - - -## Key Results - - - -## Notes - diff --git a/demo-vault-v2/untitled-project-41.md b/demo-vault-v2/untitled-project-41.md deleted file mode 100644 index 272507d0..00000000 --- a/demo-vault-v2/untitled-project-41.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -title: Untitled project 41 -type: Project -status: Active ---- - -## Objective - - - -## Key Results - - - -## Notes - diff --git a/demo-vault-v2/untitled-project-42.md b/demo-vault-v2/untitled-project-42.md deleted file mode 100644 index 4e83a278..00000000 --- a/demo-vault-v2/untitled-project-42.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -title: Untitled project 42 -type: Project -status: Active ---- - -## Objective - - - -## Key Results - - - -## Notes - diff --git a/demo-vault-v2/untitled-project-43.md b/demo-vault-v2/untitled-project-43.md deleted file mode 100644 index 30766520..00000000 --- a/demo-vault-v2/untitled-project-43.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -title: Untitled project 43 -type: Project -status: Active ---- - -## Objective - - - -## Key Results - - - -## Notes - diff --git a/demo-vault-v2/untitled-project-44.md b/demo-vault-v2/untitled-project-44.md deleted file mode 100644 index f692f621..00000000 --- a/demo-vault-v2/untitled-project-44.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -title: Untitled project 44 -type: Project -status: Active ---- - -## Objective - - - -## Key Results - - - -## Notes - diff --git a/demo-vault-v2/untitled-project-45.md b/demo-vault-v2/untitled-project-45.md deleted file mode 100644 index 0ac20046..00000000 --- a/demo-vault-v2/untitled-project-45.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -title: Untitled project 45 -type: Project -status: Active ---- - -## Objective - - - -## Key Results - - - -## Notes - diff --git a/demo-vault-v2/untitled-project-46.md b/demo-vault-v2/untitled-project-46.md deleted file mode 100644 index 6c27b5df..00000000 --- a/demo-vault-v2/untitled-project-46.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -title: Untitled project 46 -type: Project -status: Active ---- - -## Objective - - - -## Key Results - - - -## Notes - diff --git a/demo-vault-v2/untitled-project-47.md b/demo-vault-v2/untitled-project-47.md deleted file mode 100644 index fc9d1092..00000000 --- a/demo-vault-v2/untitled-project-47.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -title: Untitled project 47 -type: Project -status: Active ---- - -## Objective - - - -## Key Results - - - -## Notes - diff --git a/demo-vault-v2/untitled-project-48.md b/demo-vault-v2/untitled-project-48.md deleted file mode 100644 index 9b45d733..00000000 --- a/demo-vault-v2/untitled-project-48.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -title: Untitled project 48 -type: Project -status: Active ---- - -## Objective - - - -## Key Results - - - -## Notes - diff --git a/demo-vault-v2/untitled-project-49.md b/demo-vault-v2/untitled-project-49.md deleted file mode 100644 index 87e06667..00000000 --- a/demo-vault-v2/untitled-project-49.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -title: Untitled project 49 -type: Project -status: Active ---- - -## Objective - - - -## Key Results - - - -## Notes - diff --git a/demo-vault-v2/untitled-project-5.md b/demo-vault-v2/untitled-project-5.md deleted file mode 100644 index 2d076fc4..00000000 --- a/demo-vault-v2/untitled-project-5.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -title: Untitled project 5 -type: Project -status: Active ---- - -# Untitled project 5 - -## Objective - - - -## Key Results - - - -## Notes - diff --git a/demo-vault-v2/untitled-project-50.md b/demo-vault-v2/untitled-project-50.md deleted file mode 100644 index 6ff7ee7d..00000000 --- a/demo-vault-v2/untitled-project-50.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -title: Untitled project 50 -type: Project -status: Active ---- - -## Objective - - - -## Key Results - - - -## Notes - diff --git a/demo-vault-v2/untitled-project-51.md b/demo-vault-v2/untitled-project-51.md deleted file mode 100644 index 7f315ba3..00000000 --- a/demo-vault-v2/untitled-project-51.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -title: Untitled project 51 -type: Project -status: Active ---- - -## Objective - - - -## Key Results - - - -## Notes - diff --git a/demo-vault-v2/untitled-project-52.md b/demo-vault-v2/untitled-project-52.md deleted file mode 100644 index c7ec56c3..00000000 --- a/demo-vault-v2/untitled-project-52.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -title: Untitled project 52 -type: Project -status: Active ---- - -## Objective - - - -## Key Results - - - -## Notes - diff --git a/demo-vault-v2/untitled-project-53.md b/demo-vault-v2/untitled-project-53.md deleted file mode 100644 index 99cf3309..00000000 --- a/demo-vault-v2/untitled-project-53.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -title: Untitled project 53 -type: Project -status: Active ---- - -## Objective - - - -## Key Results - - - -## Notes - diff --git a/demo-vault-v2/untitled-project-54.md b/demo-vault-v2/untitled-project-54.md deleted file mode 100644 index d61ddf20..00000000 --- a/demo-vault-v2/untitled-project-54.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -title: Untitled project 54 -type: Project -status: Active ---- - -## Objective - - - -## Key Results - - - -## Notes - diff --git a/demo-vault-v2/untitled-project-55.md b/demo-vault-v2/untitled-project-55.md deleted file mode 100644 index a6c97247..00000000 --- a/demo-vault-v2/untitled-project-55.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -title: Untitled project 55 -type: Project -status: Active ---- - -## Objective - - - -## Key Results - - - -## Notes - diff --git a/demo-vault-v2/untitled-project-56.md b/demo-vault-v2/untitled-project-56.md deleted file mode 100644 index 4996d18a..00000000 --- a/demo-vault-v2/untitled-project-56.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -title: Untitled project 56 -type: Project -status: Active ---- - -## Objective - - - -## Key Results - - - -## Notes - diff --git a/demo-vault-v2/untitled-project-57.md b/demo-vault-v2/untitled-project-57.md deleted file mode 100644 index 7493a1a4..00000000 --- a/demo-vault-v2/untitled-project-57.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -title: Untitled project 57 -type: Project -status: Active ---- - -## Objective - - - -## Key Results - - - -## Notes - diff --git a/demo-vault-v2/untitled-project-58.md b/demo-vault-v2/untitled-project-58.md deleted file mode 100644 index 23b9a18f..00000000 --- a/demo-vault-v2/untitled-project-58.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -title: Untitled project 58 -type: Project -status: Active ---- - -## Objective - - - -## Key Results - - - -## Notes - diff --git a/demo-vault-v2/untitled-project-6.md b/demo-vault-v2/untitled-project-6.md deleted file mode 100644 index 7013a6e4..00000000 --- a/demo-vault-v2/untitled-project-6.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -title: Untitled project 6 -type: Project -status: Active ---- - -# Untitled project 6 - -## Objective - - - -## Key Results - - - -## Notes - diff --git a/demo-vault-v2/untitled-project-7.md b/demo-vault-v2/untitled-project-7.md deleted file mode 100644 index 4e1e8822..00000000 --- a/demo-vault-v2/untitled-project-7.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -title: Untitled project 7 -type: Project -status: Active ---- - -# Untitled project 7 - -## Objective - - - -## Key Results - - - -## Notes - diff --git a/demo-vault-v2/untitled-project-8.md b/demo-vault-v2/untitled-project-8.md deleted file mode 100644 index 39f8f94d..00000000 --- a/demo-vault-v2/untitled-project-8.md +++ /dev/null @@ -1,12 +0,0 @@ ---- -title: Untitled project 8 -type: Project -status: Active ---- -# Untitled project 8 - -## Objective - -## Key Results - -## Notes diff --git a/demo-vault-v2/untitled-project-9.md b/demo-vault-v2/untitled-project-9.md deleted file mode 100644 index 46bc47c3..00000000 --- a/demo-vault-v2/untitled-project-9.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -title: Untitled project 9 -type: Project -status: Active ---- - -# Untitled project 9 - -## Objective - - - -## Key Results - - - -## Notes - diff --git a/demo-vault-v2/untitled-project.md b/demo-vault-v2/untitled-project.md deleted file mode 100644 index ba424cff..00000000 --- a/demo-vault-v2/untitled-project.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -title: Untitled project -type: Project -status: Active ---- - -# Untitled project - -## Objective - - - -## Key Results - - - -## Notes - diff --git a/demo-vault-v2/untitled-save-no-rename-test.md b/demo-vault-v2/untitled-save-no-rename-test.md deleted file mode 100644 index 48f3ee39..00000000 --- a/demo-vault-v2/untitled-save-no-rename-test.md +++ /dev/null @@ -1,6 +0,0 @@ ---- -title: Untitled Save No Rename Test -type: Note -status: Active ---- -# Untitled Save No Rename Test diff --git a/demo-vault-v2/untitled-test-note-abc-2-renamed.md b/demo-vault-v2/untitled-test-note-abc-2-renamed.md deleted file mode 100644 index 953806ce..00000000 --- a/demo-vault-v2/untitled-test-note-abc-2-renamed.md +++ /dev/null @@ -1,6 +0,0 @@ ---- -title: Untitled Test Note ABC 2 -type: Note -status: Active ---- -# Untitled Test Note ABC 2 Renamed diff --git a/demo-vault-v2/untitled-test-note-abc-2.md b/demo-vault-v2/untitled-test-note-abc-2.md deleted file mode 100644 index 76b75530..00000000 --- a/demo-vault-v2/untitled-test-note-abc-2.md +++ /dev/null @@ -1,6 +0,0 @@ ---- -title: Untitled Test Note ABC 2 -type: Note -status: Active ---- -# Untitled Test Note ABC 2 diff --git a/demo-vault-v2/untitled-test-note-abc.md b/demo-vault-v2/untitled-test-note-abc.md deleted file mode 100644 index e75faccc..00000000 --- a/demo-vault-v2/untitled-test-note-abc.md +++ /dev/null @@ -1,6 +0,0 @@ ---- -title: Untitled Test Note ABC -type: Note -status: Active ---- -# Untitled Test Note ABC diff --git a/demo-vault-v2/what-makes-a-good-podcast-guest.md b/demo-vault-v2/what-makes-a-good-podcast-guest.md deleted file mode 100644 index a9866a18..00000000 --- a/demo-vault-v2/what-makes-a-good-podcast-guest.md +++ /dev/null @@ -1,28 +0,0 @@ ---- -aliases: ["What Makes a Good Podcast Guest"] -Is A: Evergreen -Topics: ["[[topic-podcasting]]"] -Status: Published ---- -# What Makes a Good Podcast Guest -The best podcast guests are not the most famous or the most accomplished. They're the most specific. - -A guest who can speak from direct experience about one particular problem — how they restructured their engineering team after a disastrous product launch, exactly what they changed in their hiring process after a bad hire — is far more valuable than a guest who can speak generally about leadership at scale. - -This has changed how I approach guest outreach. Instead of starting with 'who is impressive?', I start with 'what specific thing happened to this person that would be genuinely useful to our listeners?' - -After recording over a hundred podcast episodes, I have identified three qualities that separate memorable guests from forgettable ones, and none of them are fame or follower count. The first is specificity: the guest can describe a concrete situation with enough detail that the listener can picture themselves in it. "We reorganized our team" is vague. "We split a 12-person backend team into three 4-person squads, each owning a specific domain, and two of the three squad leads had never managed before" is specific enough to be useful. The second quality is honesty about failure: guests who can describe what went wrong, what they would do differently, and what it felt like to be in the middle of a mess produce episodes that resonate far more than guests who present a polished success narrative. The third is genuine curiosity: guests who ask me questions, push back on my framing, and use the conversation as genuine thinking time rather than a rehearsed performance create the kind of dialogue that listeners can actually learn from. - -The selection process I use now is deliberately biased toward practitioners over thought leaders. A VP Engineering who just navigated a painful migration from monolith to microservices is a better guest than a consultant who has advised fifty companies on the same topic, because the VP has the emotional texture and the specific details that make a story believable and actionable. Thought leaders tend to speak in frameworks; practitioners tend to speak in stories. Listeners remember stories. - -This has also shaped how I prepare for recordings. Instead of sending a list of questions in advance, I identify the specific experience I want the guest to share and frame the conversation around that experience. The prep call is about finding the story, not about planning the structure. Once you have the right story, the conversation structures itself. The worst episodes I have recorded were the ones where I had a detailed question list and the guest had prepared polished answers. The best episodes were the ones where we found an unexpected thread and followed it. - -## Key insight -The quality of a podcast is determined primarily by guest selection and preparation, not by production value or interview technique. The most impactful selection criterion is specificity of experience: choosing guests who can share a detailed, honest account of a specific professional challenge. This requires shifting the selection question from "who is important?" to "who has a story our listeners need to hear?" The resulting episodes are more useful, more memorable, and generate more listener engagement than episodes with higher-profile guests who speak in generalities. - -## Related -- [[podcasting-is-relationship-building]] — Guest selection should also consider relationship value, not just content value -- [[writing-for-clarity-vs-writing-for-credit]] — Specificity and honesty in podcasting mirror the clarity-over-credit principle in writing -- [[on-consistency-in-creative-work]] — A consistent podcast schedule forces you to develop a reliable guest pipeline -- [[procedure-podcast-recording]] — The practical procedure for finding, preparing, and recording with guests -- [[topic-podcasting]] — Broader thinking on podcasting as a medium and business diff --git a/demo-vault-v2/why-b2b-newsletters-work.md b/demo-vault-v2/why-b2b-newsletters-work.md deleted file mode 100644 index 5ad09d22..00000000 --- a/demo-vault-v2/why-b2b-newsletters-work.md +++ /dev/null @@ -1,28 +0,0 @@ ---- -aliases: ["Why B2B Newsletters Work"] -Is A: Evergreen -Topics: ["[[topic-newsletter-growth]]", "[[topic-b2b-marketing]]"] -Status: Published ---- -# Why B2B Newsletters Work -B2B newsletters occupy a unique position in the attention economy: they're invited into the inbox, not pushed. The reader actively chose to receive them. This opt-in dynamic is unlike almost every other marketing channel. - -The implication: the conversion funnel is inverted compared to advertising. You don't need to interrupt; you need to deserve the slot. Readers who find a B2B newsletter worth reading self-select as high-intent. They're not casual browsers; they're professionals investing time in staying current. - -This is why the economics of a B2B newsletter sponsor can be so attractive. You're not renting attention; you're being introduced to a curated audience that has already demonstrated professional intent. - -The opt-in dynamic creates a quality floor that other channels lack. In programmatic advertising, you are paying to interrupt people who did not ask to be interrupted, and the economics reflect it — low engagement, low trust, high waste. In a B2B newsletter, the reader invited you into their most protected digital space: their inbox. This creates an implicit social contract: you promise relevance, and they promise attention. When both sides honor this contract, the resulting engagement quality is an order of magnitude higher than any interruptive channel. - -The business model implications extend beyond simple advertising economics. A B2B newsletter with a highly engaged professional audience is one of the few media properties where the audience's professional context is the product. A newsletter about engineering leadership with 30,000 subscribers who are actual engineering leaders is more valuable than a general tech publication with 3 million visitors, because the advertiser knows exactly who they are reaching and in what professional mindset they are being reached. The specificity of the audience and the quality of the attention make the CPM math work at rates that seem absurd by traditional media standards but are entirely rational given the conversion rates. - -There is also a timing advantage that B2B newsletters exploit naturally. Email is consumed during work hours, often as part of a professional routine. A VP Engineering reading Refactoring over Monday morning coffee is in a professional frame of mind — thinking about their team, their challenges, their tooling decisions. A sponsor message encountered in this context lands differently than the same message encountered during a casual social media scroll. The professional context primes the reader for professional decision-making, which is exactly what B2B sponsors need. This timing alignment is not something newsletters engineer; it is inherent to the medium, and it is one of the reasons B2B newsletters consistently outperform expectations on sponsor ROI. - -## Key insight -B2B newsletters work because they align three factors that no other channel combines: opt-in attention (the reader chose to be here), professional context (they are reading during work, in a professional mindset), and audience specificity (the publisher knows exactly who subscribes and why). This triple alignment creates a marketing channel where the audience is pre-qualified, the attention is genuine, and the context is optimal for B2B purchasing decisions. The result is a medium that punches far above its weight in terms of influence per reader, which is why newsletter sponsorship CPMs can be 10-50x higher than programmatic display and still deliver positive sponsor ROI. - -## Related -- [[b2b-content-is-trust-not-traffic]] — The trust mechanism that makes B2B newsletter content effective -- [[the-real-job-of-a-newsletter]] — Understanding the professional job readers hire a B2B newsletter to do -- [[the-sponsorship-relationship]] — How to structure sponsor relationships to maximize the B2B newsletter advantage -- [[newsletter-growth-is-about-trust]] — Trust as the currency that sustains the opt-in dynamic -- [[newsletter-subject-lines]] — Subject lines as the mechanism for honoring the opt-in contract diff --git a/demo-vault-v2/wikilinks-qa-test.md b/demo-vault-v2/wikilinks-qa-test.md deleted file mode 100644 index d64bda0b..00000000 --- a/demo-vault-v2/wikilinks-qa-test.md +++ /dev/null @@ -1,5 +0,0 @@ -# Wikilinks QA Test - -See [[ProjectX]] and [[Team Goals|Goals]] for details on the project timeline. - -This is a test note for QA purposes. diff --git a/demo-vault-v2/writing-for-clarity-vs-writing-for-credit.md b/demo-vault-v2/writing-for-clarity-vs-writing-for-credit.md index f762f294..8e7bee4c 100644 --- a/demo-vault-v2/writing-for-clarity-vs-writing-for-credit.md +++ b/demo-vault-v2/writing-for-clarity-vs-writing-for-credit.md @@ -1,30 +1,11 @@ --- -aliases: ["Writing for Clarity vs. Writing for Credit"] -Is A: Evergreen -Topics: ["[[topic-writing]]"] -Status: Published +type: Note +topics: + - "[[topic-writing]]" +status: Published --- + # Writing for Clarity vs. Writing for Credit -There are two failure modes in technical writing. The first is jargon-as-camouflage: using complexity to signal expertise, so the reader can't tell if you actually know what you're talking about. The second is oversimplification-as-humility: stripping out necessary nuance to seem accessible. -Clarity is harder than either. It requires understanding a topic well enough to choose exactly which complexity to preserve and which to discard — and being honest about which parts you don't fully understand yourself. +Write to be understood before you write to impress. This note exists so `Writing` has a strong prefix match underneath the exact title result. -The best technical writers I've read are ruthlessly honest about the limits of their knowledge. This is what earns trust. - -The distinction between writing for clarity and writing for credit maps directly to audience relationship. Writing for credit is author-centered: the goal is for the reader to think "this person is smart." Writing for clarity is reader-centered: the goal is for the reader to think "now I understand this." These goals occasionally align, but they diverge more often than most writers realize. A paragraph that makes the author look knowledgeable — dense with jargon, referencing obscure research, structured as an academic argument — often fails to actually transfer understanding to the reader. The writer walks away feeling validated; the reader walks away confused but blaming themselves for not being smart enough. - -I catch myself writing for credit more often than I would like to admit, and the tell is always the same: I am reaching for complexity rather than arriving at it. When I genuinely understand something, the explanation flows toward simplicity because I can see which details matter and which are decorative. When I am on shaky ground, I unconsciously pile on complexity to obscure the gaps in my understanding. The cure is embarrassingly simple: I ask myself, "Could I explain this to a smart friend who has no context on this topic?" If the answer is no, I do not understand it well enough to write about it, and I need to go learn more before I write. - -This principle has shaped Refactoring's editorial voice. I aim for what I think of as "earned simplicity" — explanations that are simple not because they skip complexity but because they have digested complexity and extracted the essential insight. This is dramatically harder than either academic-style complexity or shallow hot-takes, but it is the voice that readers trust and return to. When a reader emails to say "you made me understand something I have been confused about for years," that is the signal that the writing is serving clarity rather than credit. Those emails are worth more to me than any engagement metric. - -The AI writing revolution makes this distinction even more consequential. AI can produce writing that sounds knowledgeable — it generates the surface patterns of expertise effortlessly. But it struggles with earned simplicity because that requires genuine understanding of which details to keep and which to discard, which is a judgment that depends on having actually grappled with the material. As AI-generated content floods every niche, the ability to write with genuine clarity — to actually transfer understanding rather than to perform understanding — becomes the primary differentiator for human writers. - -## Key insight -The fundamental question to ask about any piece of technical writing is: "Who is this serving — the author's reputation or the reader's understanding?" Writing for clarity requires the humility to be simple where simplicity serves the reader, even when complexity would make the author look smarter. It also requires the honesty to say "I don't fully understand this part" rather than obscuring gaps with jargon. In an era of AI-generated content that effortlessly mimics expertise, genuine clarity — earned through deep understanding and presented with intellectual honesty — is the most valuable and rarest form of technical writing. - -## Related -- [[ai-wont-replace-thinking]] — AI can mimic the surface of expertise but cannot produce earned clarity -- [[on-consistency-in-creative-work]] — Regular writing practice develops the clarity muscle through repetition -- [[newsletter-subject-lines]] — Clarity over cleverness in subject lines mirrors the broader writing principle -- [[the-real-job-of-a-newsletter]] — Clarity serves the reader's job-to-be-done; credit-seeking undermines it -- [[note-on-writing-well]] — Zinsser's principles of clear, honest writing as a foundational reference diff --git a/demo-vault-v2/writing-weekly-rhythm.md b/demo-vault-v2/writing-weekly-rhythm.md new file mode 100644 index 00000000..298d58f4 --- /dev/null +++ b/demo-vault-v2/writing-weekly-rhythm.md @@ -0,0 +1,11 @@ +--- +type: Note +topics: + - "[[topic-writing]]" +status: Active +--- + +# Writing Weekly Rhythm + +A short operational note about keeping a weekly publishing cadence without overproducing drafts. + diff --git a/demo-vault-v2/year.md b/demo-vault-v2/year.md deleted file mode 100644 index 532d84dc..00000000 --- a/demo-vault-v2/year.md +++ /dev/null @@ -1,7 +0,0 @@ ---- -Is A: Type ---- - -# Year - -A Year note captures the themes, goals, and reflections for a calendar year. It provides the highest-level time horizon in the life OS. diff --git a/docs/ABSTRACTIONS.md b/docs/ABSTRACTIONS.md index dc8114cd..7ef22655 100644 --- a/docs/ABSTRACTIONS.md +++ b/docs/ABSTRACTIONS.md @@ -564,7 +564,7 @@ No indexing step required — search runs directly against the filesystem. - Persists vault list to `~/.config/com.tolaria.app/vaults.json` (reads legacy `com.laputa.app` on upgrade) - Switching closes all tabs and resets sidebar - Supports adding, removing, hiding/restoring vaults -- Default vault: Getting Started demo vault +- Default vault: public Getting Started starter vault cloned on demand ### Vault Config diff --git a/docs/ARCHITECTURE.md b/docs/ARCHITECTURE.md index 7c1d7fe1..85f6edb3 100644 --- a/docs/ARCHITECTURE.md +++ b/docs/ARCHITECTURE.md @@ -583,7 +583,7 @@ The vault backend (`src-tauri/src/vault/`) is split into focused submodules: | `image.rs` | `save_image` — saves base64-encoded attachments with sanitized filenames | | `migration.rs` | `flatten_vault`, `vault_health_check`, `migrate_is_a_to_type` | | `config_seed.rs` | Maintains vault AI guidance (`AGENTS.md` + `CLAUDE.md` shim), migrates legacy `config/agents.md`, and repairs missing root type scaffolding such as `type.md` and `note.md` | -| `getting_started.rs` | Creates the Getting Started demo vault | +| `getting_started.rs` | Clones and normalizes the public Getting Started starter vault | ## Rust Backend Modules diff --git a/docs/GETTING-STARTED.md b/docs/GETTING-STARTED.md index 961690b6..e05e6b1d 100644 --- a/docs/GETTING-STARTED.md +++ b/docs/GETTING-STARTED.md @@ -183,7 +183,7 @@ tolaria/ ├── e2e/ # Playwright E2E tests (~26 specs) ├── tests/smoke/ # Playwright specs (full regression + @smoke subset) ├── design/ # Per-task design files -├── demo-vault-v2/ # Getting Started demo vault +├── demo-vault-v2/ # Curated local QA fixture for native/dev flows ├── scripts/ # Build/utility scripts │ ├── package.json # Frontend dependencies + scripts @@ -199,6 +199,12 @@ tolaria/ ## Key Files to Know +### Fixtures + +- `demo-vault-v2/` is the small checked-in QA fixture used for native/manual Tolaria flows. It is intentionally curated around a handful of search, relationship, project-navigation, and attachment scenarios. +- `tests/fixtures/test-vault/` is the deterministic Playwright fixture copied into temp directories for isolated integration and smoke tests. +- `python3 scripts/generate_demo_vault.py` generates the larger synthetic vault on demand at `generated-fixtures/demo-vault-large/` for scale/performance experiments. That output is gitignored and should not bloat the normal QA fixture. + ### Start here | File | Why it matters | diff --git a/scripts/generate_demo_vault.py b/scripts/generate_demo_vault.py index 5ba86137..08954af4 100644 --- a/scripts/generate_demo_vault.py +++ b/scripts/generate_demo_vault.py @@ -1,12 +1,19 @@ #!/usr/bin/env python3 -"""Generate ~1,080 synthetic markdown files for the Laputa demo vault. +"""Generate a large synthetic vault for scale and performance checks. -Creates a realistic 2-year knowledge vault (Q1 2024 – Q4 2025) for a +Creates a realistic 2-year knowledge vault (Q1 2024 - Q4 2025) for a fictional persona based on Luca Rossi, founder of Refactoring. -Usage: python scripts/generate_demo_vault.py +The curated `demo-vault-v2/` fixture is intentionally small and lives in git. +This script generates the larger corpus on demand outside that checked-in QA +fixture. + +Usage: + python3 scripts/generate_demo_vault.py + python3 scripts/generate_demo_vault.py --output /tmp/demo-vault-large """ +import argparse import random import shutil from datetime import date, timedelta @@ -14,7 +21,8 @@ from pathlib import Path random.seed(42) -VAULT = Path(__file__).resolve().parent.parent / "demo-vault-v2" +DEFAULT_VAULT = Path(__file__).resolve().parent.parent / "generated-fixtures" / "demo-vault-large" +VAULT = DEFAULT_VAULT SUBDIRS = [ "area", "responsibility", "measure", "target", "goal", "year", "quarter", "month", "project", "experiment", "procedure", "task", @@ -541,155 +549,182 @@ NOTES = [ ] -def generate_all(): - random.seed(42) - # Setup dirs +def reset_vault(): + COUNTS.clear() if VAULT.exists(): shutil.rmtree(VAULT) for sub in SUBDIRS: (VAULT / sub).mkdir(parents=True, exist_ok=True) - # ── YEARS ───────────────────────────────────────────────────── + +def generate_years(): for year in ["2024", "2025"]: - qs = [q for q in QUARTER_SLUGS if q.startswith(year[2:])] + quarters = [q for q in QUARTER_SLUGS if q.startswith(year[2:])] write_md("year", year, { - "aliases": [year], "Is A": "Year", + "aliases": [year], + "Is A": "Year", "Created at": f"{year}-01-01", - "Has": [wl(q) for q in qs], + "Has": [wl(q) for q in quarters], }, f"# {year}\nAnother year of building Refactoring, shipping content, and growing the audience. Review written in December.") - # ── QUARTERS ────────────────────────────────────────────────── + +def generate_quarters(): for q in QUARTER_SLUGS: projects_in_q = [p[0] for p in PROJECTS if p[2] == q] write_md("quarter", q, { - "aliases": [Q_LABEL[q]], "Is A": "Quarter", + "aliases": [Q_LABEL[q]], + "Is A": "Quarter", "Created at": Q_START[q], "Belongs to": wl(Q_YEAR[q]), "Has": [wl(p) for p in projects_in_q], "Status": "Done" if q < "25q4" else "Open", }, f"# {Q_LABEL[q]}\nQuarterly review for {Q_LABEL[q]}. See projects and targets below.") - # ── MONTHS ──────────────────────────────────────────────────── - rating_cycle = ["😄","🤩","😄","😄","😐","🤩","😄","🤩","😄","😐","😄","😄"] + +def generate_months(): + rating_cycle = ["😄", "🤩", "😄", "😄", "😐", "🤩", "😄", "🤩", "😄", "😐", "😄", "😄"] + month_tones = ["difficult", "solid", "great", "mixed"] month_idx = 0 + for q in QUARTER_SLUGS: - for ms in Q_MONTHS[q]: - y, m = ms.split("-") - mname = MONTH_NAMES[int(m)] + for month_slug in Q_MONTHS[q]: + year, month = month_slug.split("-") + month_name = MONTH_NAMES[int(month)] rating = rating_cycle[month_idx % len(rating_cycle)] - write_md("month", ms, { - "aliases": [f"{mname} {y}"], "Is A": "Month", - "Created at": f"{ms}-28", + tone = month_tones[month_idx % len(month_tones)] + write_md("month", month_slug, { + "aliases": [f"{month_name} {year}"], + "Is A": "Month", + "Created at": f"{month_slug}-28", "Belongs to": wl(q), "Rating": rating, - }, f"# {mname} {y}\nMonthly review. A {['difficult','solid','great','mixed'][month_idx % 4]} month overall.") + }, f"# {month_name} {year}\nMonthly review. A {tone} month overall.") month_idx += 1 - # ── AREAS ───────────────────────────────────────────────────── - for slug, name, resp_slugs in AREAS: + +def generate_areas(): + for slug, name, responsibility_slugs in AREAS: write_md("area", slug, { - "aliases": [name], "Is A": "Area", - "Has": [wl(r) for r in resp_slugs], + "aliases": [name], + "Is A": "Area", + "Has": [wl(resp) for resp in responsibility_slugs], }, f"# {name}\nOne of the core life/work areas.") - # ── RESPONSIBILITIES ────────────────────────────────────────── - for slug, name, area, measures, procs, body in RESPONSIBILITIES: + +def generate_responsibilities(): + for slug, name, area, measures, procedures, body in RESPONSIBILITIES: write_md("responsibility", slug, { - "aliases": [name], "Is A": "Responsibility", + "aliases": [name], + "Is A": "Responsibility", "Belongs to": wl(area), - "Has Measures": [wl(m) for m in measures], - "Has Procedures": [wl(p) for p in procs], + "Has Measures": [wl(measure) for measure in measures], + "Has Procedures": [wl(proc) for proc in procedures], "Status": "Open", }, f"# {name}\n{body}") - # ── MEASURES ────────────────────────────────────────────────── - for slug, name, resp, unit in MEASURES: + +def generate_measures(): + for slug, name, responsibility, unit in MEASURES: write_md("measure", slug, { - "aliases": [name], "Is A": "Measure", - "Belongs to": wl(resp), + "aliases": [name], + "Is A": "Measure", + "Belongs to": wl(responsibility), "Unit": unit, }, f"# {name}\nTracked monthly via spreadsheet. Unit: {unit}.") - # ── TARGETS ─────────────────────────────────────────────────── - open_qs = {"25q3", "25q4"} - for q in QUARTER_SLUGS: - subs_start, subs_end = SUB_TRAJ[q] - rev = REV_TRAJ[q] - status_q = "Open" if q in open_qs else "Done" - # subscribers target - actual_s = random.randint(subs_end - 800, subs_end + 500) - t_status = "Done" if actual_s >= subs_end else "Behind" - write_md("target", f"target-subscribers-{q}", { - "aliases": [f"Subscribers {Q_LABEL[q]}"], "Is A": "Target", - "Belongs to": wl(q), + +def generate_targets(): + open_quarters = {"25q3", "25q4"} + + for quarter in QUARTER_SLUGS: + _, subscribers_goal = SUB_TRAJ[quarter] + revenue_goal = REV_TRAJ[quarter] + quarter_status = "Open" if quarter in open_quarters else "Done" + + actual_subscribers = random.randint(subscribers_goal - 800, subscribers_goal + 500) + subscribers_status = "Done" if actual_subscribers >= subscribers_goal else "Behind" + write_md("target", f"target-subscribers-{quarter}", { + "aliases": [f"Subscribers {Q_LABEL[quarter]}"], + "Is A": "Target", + "Belongs to": wl(quarter), "Measure": wl("measure-subscribers"), - "Goal value": subs_end, - "Actual value": actual_s if q not in open_qs else None, - "Status": status_q if q in open_qs else t_status, - }, f"# Subscribers Target {Q_LABEL[q]}\nTarget: {subs_end:,} subscribers by end of quarter.") - # revenue target - rev_actual = random.randint(int(rev * 0.9), int(rev * 1.15)) - write_md("target", f"target-revenue-{q}", { - "aliases": [f"Revenue {Q_LABEL[q]}"], "Is A": "Target", - "Belongs to": wl(q), + "Goal value": subscribers_goal, + "Actual value": actual_subscribers if quarter not in open_quarters else None, + "Status": quarter_status if quarter in open_quarters else subscribers_status, + }, f"# Subscribers Target {Q_LABEL[quarter]}\nTarget: {subscribers_goal:,} subscribers by end of quarter.") + + actual_revenue = random.randint(int(revenue_goal * 0.9), int(revenue_goal * 1.15)) + revenue_status = "Done" if actual_revenue >= revenue_goal else "Behind" + write_md("target", f"target-revenue-{quarter}", { + "aliases": [f"Revenue {Q_LABEL[quarter]}"], + "Is A": "Target", + "Belongs to": wl(quarter), "Measure": wl("measure-sponsorship-mrr"), - "Goal value": rev, - "Actual value": rev_actual if q not in open_qs else None, - "Status": status_q if q in open_qs else ("Done" if rev_actual >= rev else "Behind"), - }, f"# Revenue Target {Q_LABEL[q]}\nTarget: €{rev:,}/month MRR by end of quarter.") - # resting HR target - hr_goal = 54 - QUARTER_SLUGS.index(q) // 2 - hr_actual = random.randint(hr_goal - 2, hr_goal + 3) - write_md("target", f"target-resting-hr-{q}", { - "aliases": [f"Resting HR {Q_LABEL[q]}"], "Is A": "Target", - "Belongs to": wl(q), + "Goal value": revenue_goal, + "Actual value": actual_revenue if quarter not in open_quarters else None, + "Status": quarter_status if quarter in open_quarters else revenue_status, + }, f"# Revenue Target {Q_LABEL[quarter]}\nTarget: €{revenue_goal:,}/month MRR by end of quarter.") + + hr_goal = 54 - QUARTER_SLUGS.index(quarter) // 2 + actual_hr = random.randint(hr_goal - 2, hr_goal + 3) + hr_status = "Done" if actual_hr <= hr_goal else "Behind" + write_md("target", f"target-resting-hr-{quarter}", { + "aliases": [f"Resting HR {Q_LABEL[quarter]}"], + "Is A": "Target", + "Belongs to": wl(quarter), "Measure": wl("measure-resting-hr"), "Goal value": hr_goal, - "Actual value": hr_actual if q not in open_qs else None, - "Status": status_q if q in open_qs else ("Done" if hr_actual <= hr_goal else "Behind"), - }, f"# Resting HR Target {Q_LABEL[q]}\nTarget: resting HR < {hr_goal} bpm.") - # books target - write_md("target", f"target-books-{q}", { - "aliases": [f"Books {Q_LABEL[q]}"], "Is A": "Target", - "Belongs to": wl(q), + "Actual value": actual_hr if quarter not in open_quarters else None, + "Status": quarter_status if quarter in open_quarters else hr_status, + }, f"# Resting HR Target {Q_LABEL[quarter]}\nTarget: resting HR < {hr_goal} bpm.") + + actual_books = random.randint(4, 7) if quarter not in open_quarters else None + write_md("target", f"target-books-{quarter}", { + "aliases": [f"Books {Q_LABEL[quarter]}"], + "Is A": "Target", + "Belongs to": wl(quarter), "Measure": wl("measure-books-per-month"), "Goal value": 6, - "Actual value": random.randint(4, 7) if q not in open_qs else None, - "Status": status_q, - }, f"# Books Target {Q_LABEL[q]}\nTarget: 6 books in the quarter (2/month).") + "Actual value": actual_books, + "Status": quarter_status, + }, f"# Books Target {Q_LABEL[quarter]}\nTarget: 6 books in the quarter (2/month).") - # ── GOALS ───────────────────────────────────────────────────── + +def generate_goals(): for slug, name, year, status, body in GOALS: write_md("goal", slug, { - "aliases": [name], "Is A": "Goal", + "aliases": [name], + "Is A": "Goal", "Belongs to": wl(year), "Status": status, }, f"# {name}\n{body}") - # ── PROJECTS ────────────────────────────────────────────────── - for slug, title, q, resp, status, body in PROJECTS: + +def generate_projects(): + for slug, title, quarter, responsibility, status, body in PROJECTS: write_md("project", slug, { - "aliases": [title], "Is A": "Project", - "Belongs to": wl(q), - "Advances": wl(resp), + "aliases": [title], + "Is A": "Project", + "Belongs to": wl(quarter), + "Advances": wl(responsibility), "Status": status, "Owner": wl("person-luca-rossi"), }, f"# {title}\n{body}") - # ── EXPERIMENTS ─────────────────────────────────────────────── - for slug, title, q, status, body in EXPERIMENTS: + +def generate_experiments(): + for slug, title, quarter, status, body in EXPERIMENTS: write_md("experiment", slug, { - "aliases": [title], "Is A": "Experiment", - "Belongs to": wl(q), + "aliases": [title], + "Is A": "Experiment", + "Belongs to": wl(quarter), "Status": status, "Owner": wl("person-luca-rossi"), }, f"# {title}\n{body}") - # ── PROCEDURES ──────────────────────────────────────────────── - all_procs = [] - for _, _, _, _, procs, _ in RESPONSIBILITIES: - all_procs.extend(procs) - proc_map = { + +def build_procedure_map(): + return { "procedure-weekly-newsletter": ("Weekly Newsletter", "responsibility-content-production", "Weekly", "Draft, edit, and publish the weekly Refactoring newsletter. Includes essay writing, curated links, and sponsor block."), "procedure-monthly-subscriber-metrics": ("Monthly Subscriber Metrics Review", "responsibility-grow-newsletter", "Monthly", "Review subscriber growth, churn, open rates, and click rates. Update the tracking spreadsheet."), "procedure-referral-program": ("Referral Program Management", "responsibility-grow-newsletter", "Weekly", "Check referral program performance. Reward top referrers. A/B test referral copy."), @@ -726,16 +761,21 @@ def generate_all(): "procedure-weekly-reading-session": ("Weekly Reading Session", "responsibility-learning", "Weekly", "Sunday morning: 2-3 hours of focused reading. No phone, coffee, and a good book."), "procedure-evergreen-note-writing": ("Evergreen Note Writing", "responsibility-learning", "Weekly", "Write 1-2 evergreen notes per week from recent reading, conversations, or observations."), } - for proc_slug, (proc_name, resp, cadence, body) in proc_map.items(): + + +def generate_procedures(): + for proc_slug, (proc_name, responsibility, cadence, body) in build_procedure_map().items(): write_md("procedure", proc_slug, { - "aliases": [proc_name], "Is A": "Procedure", - "Belongs to": wl(resp), + "aliases": [proc_name], + "Is A": "Procedure", + "Belongs to": wl(responsibility), "Cadence": cadence, "Owner": wl("person-luca-rossi"), }, f"# {proc_name}\n{body}") - # ── TASKS ───────────────────────────────────────────────────── - task_templates = [ + +def build_task_templates(): + return [ ("Write Q{q} retrospective", "24q1", "Done"), ("Update website About page", "24q1", "Done"), ("Fix broken links in newsletter archive", "24q1", "Done"), @@ -782,206 +822,300 @@ def generate_all(): ("Update podcast listing on all platforms", "25q4", "Open"), ("Write Q4 retrospective", "25q4", "Open"), ] - for i, (title, q, status) in enumerate(task_templates): - write_md("task", f"task-{q}-{i+1:02d}", { - "aliases": [title.replace("{q}", q.upper())], "Is A": "Task", - "Belongs to": wl(q), + + +def generate_tasks(): + for index, (title, quarter, status) in enumerate(build_task_templates(), start=1): + rendered_title = title.replace("{q}", quarter.upper()) + write_md("task", f"task-{quarter}-{index:02d}", { + "aliases": [rendered_title], + "Is A": "Task", + "Belongs to": wl(quarter), "Status": status, "Owner": wl("person-luca-rossi"), - }, f"# {title.replace('{q}', q.upper())}\n") + }, f"# {rendered_title}\n") - # ── PERSONS ─────────────────────────────────────────────────── + +def generate_people(): for slug, name, tier, tags, bio in PERSONS: write_md("person", slug, { - "aliases": [name], "Is A": "Person", + "aliases": [name], + "Is A": "Person", "Tier": tier, "Tags": tags, }, f"# {name}\n{bio}") - # ── TOPICS ──────────────────────────────────────────────────── - for slug, name, desc in TOPICS: - write_md("topic", slug, { - "aliases": [name], "Is A": "Topic", - }, f"# {name}\n{desc}") - # ── EVENTS ──────────────────────────────────────────────────── +def generate_topics(): + for slug, name, description in TOPICS: + write_md("topic", slug, { + "aliases": [name], + "Is A": "Topic", + }, f"# {name}\n{description}") + + +def quarter_label_for_date(current_date: date) -> str: + if current_date.month < 4: + return "1" + if current_date.month < 7: + return "2" + if current_date.month < 10: + return "3" + return "4" + + +def generate_events(): current_date = date(2024, 1, 1) end_date = date(2025, 12, 31) - event_num = 0 + event_count = 0 sara_joined = date(2024, 4, 1) - while current_date <= end_date and event_num < 650: - dow = current_date.weekday() # 0=Mon, 6=Sun - ds = current_date.isoformat() - # month slug - ms = current_date.strftime("%Y-%m") + while current_date <= end_date and event_count < 650: + weekday = current_date.weekday() + day_slug = current_date.isoformat() + month_slug = current_date.strftime("%Y-%m") - # Monday: team sync - if dow == 0: + if weekday == 0: team = [wl("person-matteo-cellini"), wl("person-paco-furiani")] if current_date >= sara_joined: team.append(wl("person-sara-ricci")) - write_md("event", f"event-team-sync-{ds}", { - "aliases": [f"Team sync — {ds}"], "Is A": "Event", - "Date": ds, "Belongs to": wl(ms), - "Related to": team, "Tags": ["Work"], - }, f"# Team sync — {ds}\nWeekly Monday team alignment. Covered priorities, blockers, and sponsor updates.") - event_num += 1 + write_md("event", f"event-team-sync-{day_slug}", { + "aliases": [f"Team sync — {day_slug}"], + "Is A": "Event", + "Date": day_slug, + "Belongs to": wl(month_slug), + "Related to": team, + "Tags": ["Work"], + }, f"# Team sync — {day_slug}\nWeekly Monday team alignment. Covered priorities, blockers, and sponsor updates.") + event_count += 1 - # Tuesday: cycling intervals - if dow == 1: - write_md("event", f"event-cycling-{ds}", { - "aliases": [f"Cycling intervals — {ds}"], "Is A": "Event", - "Date": ds, "Belongs to": wl(ms), - "Related to": [wl("person-luca-rossi")], "Tags": ["Health", "Sport"], - }, f"# Cycling intervals — {ds}\n60-min interval session. 4x8min at threshold power.") - event_num += 1 - - # Wednesday: gym or 1:1 - if dow == 2: - # Alternate gym and 1:1 with Matteo - if (current_date - date(2024, 1, 3)).days % 14 < 7: - write_md("event", f"event-gym-{ds}", { - "aliases": [f"Gym — {ds}"], "Is A": "Event", - "Date": ds, "Belongs to": wl(ms), - "Tags": ["Health"], - }, f"# Gym — {ds}\nStrength training. Squat, deadlift, pull-ups. 75 minutes.") - event_num += 1 - else: - write_md("event", f"event-1on1-matteo-{ds}", { - "aliases": [f"1:1 Matteo — {ds}"], "Is A": "Event", - "Date": ds, "Belongs to": wl(ms), - "Related to": [wl("person-matteo-cellini")], "Tags": ["Work"], - }, f"# 1:1 Matteo — {ds}\nBi-weekly 1:1. Covered sponsor pipeline and Q{'1' if current_date.month < 4 else '2' if current_date.month < 7 else '3' if current_date.month < 10 else '4'} priorities.") - event_num += 1 - - # Thursday: cycling endurance - if dow == 3: - write_md("event", f"event-cycling-endurance-{ds}", { - "aliases": [f"Cycling endurance — {ds}"], "Is A": "Event", - "Date": ds, "Belongs to": wl(ms), + if weekday == 1: + write_md("event", f"event-cycling-{day_slug}", { + "aliases": [f"Cycling intervals — {day_slug}"], + "Is A": "Event", + "Date": day_slug, + "Belongs to": wl(month_slug), + "Related to": [wl("person-luca-rossi")], "Tags": ["Health", "Sport"], - }, f"# Cycling endurance — {ds}\n90-min endurance ride at zone 2. Avg HR 135.") - event_num += 1 + }, f"# Cycling intervals — {day_slug}\n60-min interval session. 4x8min at threshold power.") + event_count += 1 - # Friday: sponsor call or gym (alternating) - if dow == 4: + if weekday == 2: + if (current_date - date(2024, 1, 3)).days % 14 < 7: + write_md("event", f"event-gym-{day_slug}", { + "aliases": [f"Gym — {day_slug}"], + "Is A": "Event", + "Date": day_slug, + "Belongs to": wl(month_slug), + "Tags": ["Health"], + }, f"# Gym — {day_slug}\nStrength training. Squat, deadlift, pull-ups. 75 minutes.") + else: + quarter_label = quarter_label_for_date(current_date) + write_md("event", f"event-1on1-matteo-{day_slug}", { + "aliases": [f"1:1 Matteo — {day_slug}"], + "Is A": "Event", + "Date": day_slug, + "Belongs to": wl(month_slug), + "Related to": [wl("person-matteo-cellini")], + "Tags": ["Work"], + }, f"# 1:1 Matteo — {day_slug}\nBi-weekly 1:1. Covered sponsor pipeline and Q{quarter_label} priorities.") + event_count += 1 + + if weekday == 3: + write_md("event", f"event-cycling-endurance-{day_slug}", { + "aliases": [f"Cycling endurance — {day_slug}"], + "Is A": "Event", + "Date": day_slug, + "Belongs to": wl(month_slug), + "Tags": ["Health", "Sport"], + }, f"# Cycling endurance — {day_slug}\n90-min endurance ride at zone 2. Avg HR 135.") + event_count += 1 + + if weekday == 4: if (current_date - date(2024, 1, 5)).days % 14 < 7: sponsor = random.choice(SPONSOR_PERSONS) - write_md("event", f"event-sponsor-call-{ds}", { - "aliases": [f"Sponsor call — {ds}"], "Is A": "Event", - "Date": ds, "Belongs to": wl(ms), - "Related to": [wl(sponsor)], "Tags": ["Work"], - }, f"# Sponsor call — {ds}\nSponsor discovery/renewal call. Discussed placement and campaign goals.") - event_num += 1 + write_md("event", f"event-sponsor-call-{day_slug}", { + "aliases": [f"Sponsor call — {day_slug}"], + "Is A": "Event", + "Date": day_slug, + "Belongs to": wl(month_slug), + "Related to": [wl(sponsor)], + "Tags": ["Work"], + }, f"# Sponsor call — {day_slug}\nSponsor discovery/renewal call. Discussed placement and campaign goals.") else: - write_md("event", f"event-gym-fri-{ds}", { - "aliases": [f"Gym — {ds}"], "Is A": "Event", - "Date": ds, "Belongs to": wl(ms), + write_md("event", f"event-gym-fri-{day_slug}", { + "aliases": [f"Gym — {day_slug}"], + "Is A": "Event", + "Date": day_slug, + "Belongs to": wl(month_slug), "Tags": ["Health"], - }, f"# Gym — {ds}\nStrength session. Bench press, rows, overhead press. Core work.") - event_num += 1 + }, f"# Gym — {day_slug}\nStrength session. Bench press, rows, overhead press. Core work.") + event_count += 1 - # Saturday: long ride - if dow == 5: - with_alessand = random.random() < 0.4 - rel = [wl("person-luca-rossi")] - note = "Solo long ride." - if with_alessand: - rel = [wl("person-luca-rossi"), wl("person-alessandro-ferrari")] - note = "Long ride with Alessandro." - write_md("event", f"event-long-ride-{ds}", { - "aliases": [f"Long ride — {ds}"], "Is A": "Event", - "Date": ds, "Belongs to": wl(ms), - "Related to": rel, "Tags": ["Health", "Sport"], - }, f"# Long ride — {ds}\n{note} {random.randint(80,130)}km, {random.randint(800,2000)}m elevation.") - event_num += 1 + if weekday == 5: + relations = [wl("person-luca-rossi")] + ride_note = "Solo long ride." + if random.random() < 0.4: + relations = [wl("person-luca-rossi"), wl("person-alessandro-ferrari")] + ride_note = "Long ride with Alessandro." + write_md("event", f"event-long-ride-{day_slug}", { + "aliases": [f"Long ride — {day_slug}"], + "Is A": "Event", + "Date": day_slug, + "Belongs to": wl(month_slug), + "Related to": relations, + "Tags": ["Health", "Sport"], + }, f"# Long ride — {day_slug}\n{ride_note} {random.randint(80, 130)}km, {random.randint(800, 2000)}m elevation.") + event_count += 1 - # Sunday: reading session (bi-weekly) or family call - if dow == 6: + if weekday == 6: if (current_date - date(2024, 1, 7)).days % 14 < 7: - write_md("event", f"event-reading-{ds}", { - "aliases": [f"Reading session — {ds}"], "Is A": "Event", - "Date": ds, "Belongs to": wl(ms), + write_md("event", f"event-reading-{day_slug}", { + "aliases": [f"Reading session — {day_slug}"], + "Is A": "Event", + "Date": day_slug, + "Belongs to": wl(month_slug), "Tags": ["Learning"], - }, f"# Reading session — {ds}\nSunday morning reading block. 2 hours with coffee.") - event_num += 1 + }, f"# Reading session — {day_slug}\nSunday morning reading block. 2 hours with coffee.") else: - write_md("event", f"event-family-call-{ds}", { - "aliases": [f"Family call — {ds}"], "Is A": "Event", - "Date": ds, "Belongs to": wl(ms), + write_md("event", f"event-family-call-{day_slug}", { + "aliases": [f"Family call — {day_slug}"], + "Is A": "Event", + "Date": day_slug, + "Belongs to": wl(month_slug), "Related to": [wl("person-elena-rossi"), wl("person-roberto-rossi")], "Tags": ["Personal", "Family"], - }, f"# Family call — {ds}\nSunday family call with Elena and parents.") - event_num += 1 + }, f"# Family call — {day_slug}\nSunday family call with Elena and parents.") + event_count += 1 - # Monthly: 1:1 Paco (first Thursday of month) - if dow == 3 and current_date.day <= 7: - write_md("event", f"event-1on1-paco-{ds}", { - "aliases": [f"1:1 Paco — {ds}"], "Is A": "Event", - "Date": ds, "Belongs to": wl(ms), - "Related to": [wl("person-paco-furiani")], "Tags": ["Work"], - }, f"# 1:1 Paco — {ds}\nMonthly 1:1. Operations review, tooling updates, and process improvements.") - event_num += 1 + if weekday == 3 and current_date.day <= 7: + write_md("event", f"event-1on1-paco-{day_slug}", { + "aliases": [f"1:1 Paco — {day_slug}"], + "Is A": "Event", + "Date": day_slug, + "Belongs to": wl(month_slug), + "Related to": [wl("person-paco-furiani")], + "Tags": ["Work"], + }, f"# 1:1 Paco — {day_slug}\nMonthly 1:1. Operations review, tooling updates, and process improvements.") + event_count += 1 - # Monthly: nonna visit (last Sunday of month) - if dow == 6 and current_date.day >= 24: - write_md("event", f"event-nonna-visit-{ds}", { - "aliases": [f"Visita dalla Nonna — {ds}"], "Is A": "Event", - "Date": ds, "Belongs to": wl(ms), - "Related to": [wl("person-nonna-lucia")], "Tags": ["Personal", "Family"], - }, f"# Visita dalla Nonna — {ds}\nVisita mensile alla nonna a Lecco. Pranzo con risotto.") - event_num += 1 + if weekday == 6 and current_date.day >= 24: + write_md("event", f"event-nonna-visit-{day_slug}", { + "aliases": [f"Visita dalla Nonna — {day_slug}"], + "Is A": "Event", + "Date": day_slug, + "Belongs to": wl(month_slug), + "Related to": [wl("person-nonna-lucia")], + "Tags": ["Personal", "Family"], + }, f"# Visita dalla Nonna — {day_slug}\nVisita mensile alla nonna a Lecco. Pranzo con risotto.") + event_count += 1 - # Podcast recording: bi-weekly Thursday (from Feb 2024) - if dow == 3 and current_date >= date(2024, 2, 1) and (current_date - date(2024, 2, 1)).days % 14 < 7: + if weekday == 3 and current_date >= date(2024, 2, 1) and (current_date - date(2024, 2, 1)).days % 14 < 7: guest = random.choice(PODCAST_GUESTS) - write_md("event", f"event-podcast-rec-{ds}", { - "aliases": [f"Podcast recording — {ds}"], "Is A": "Event", - "Date": ds, "Belongs to": wl(ms), - "Related to": [wl(guest)], "Tags": ["Work", "Podcast"], - }, f"# Podcast recording — {ds}\nRecorded episode with {next((p[1] for p in PERSONS if p[0] == guest), guest)}. Great conversation.") - event_num += 1 + guest_name = next((person[1] for person in PERSONS if person[0] == guest), guest) + write_md("event", f"event-podcast-rec-{day_slug}", { + "aliases": [f"Podcast recording — {day_slug}"], + "Is A": "Event", + "Date": day_slug, + "Belongs to": wl(month_slug), + "Related to": [wl(guest)], + "Tags": ["Work", "Podcast"], + }, f"# Podcast recording — {day_slug}\nRecorded episode with {guest_name}. Great conversation.") + event_count += 1 - # Weekly dinner (Friday evening) - if dow == 4 and random.random() < 0.5: + if weekday == 4 and random.random() < 0.5: friend = random.choice(FRIEND_SLUGS + ["person-giulia-marchetti"]) - write_md("event", f"event-dinner-{ds}", { - "aliases": [f"Dinner — {ds}"], "Is A": "Event", - "Date": ds, "Belongs to": wl(ms), - "Related to": [wl(friend)], "Tags": ["Personal"], - }, f"# Dinner — {ds}\nEvening dinner with {next((p[1] for p in PERSONS if p[0] == friend), friend)}.") - event_num += 1 + friend_name = next((person[1] for person in PERSONS if person[0] == friend), friend) + write_md("event", f"event-dinner-{day_slug}", { + "aliases": [f"Dinner — {day_slug}"], + "Is A": "Event", + "Date": day_slug, + "Belongs to": wl(month_slug), + "Related to": [wl(friend)], + "Tags": ["Personal"], + }, f"# Dinner — {day_slug}\nEvening dinner with {friend_name}.") + event_count += 1 current_date += timedelta(days=1) - # ── EVERGREENS ──────────────────────────────────────────────── + +def generate_evergreens(): for slug, title, topics, body in EVERGREENS: write_md("evergreen", slug, { - "aliases": [title], "Is A": "Evergreen", - "Topics": [wl(t) for t in topics], + "aliases": [title], + "Is A": "Evergreen", + "Topics": [wl(topic) for topic in topics], "Status": "Published", }, f"# {title}\n{body}") - # ── NOTES ───────────────────────────────────────────────────── + +def generate_notes(): for slug, title, author, topic, url, body in NOTES: write_md("note", slug, { - "aliases": [title], "Is A": "Note", + "aliases": [title], + "Is A": "Note", "Author": author, "Topics": [wl(topic)], "URL": url, }, f"# {title}\n*{author}*\n\n{body}") - # ── SUMMARY ─────────────────────────────────────────────────── + +def print_summary(): total = sum(COUNTS.values()) - print(f"\n✅ Demo vault generated at: {VAULT}\n") + print(f"\n✅ Large fixture generated at: {VAULT}\n") print(f"{'Type':<25} {'Count':>6}") print("-" * 33) - for t, c in sorted(COUNTS.items()): - print(f"{t:<25} {c:>6}") + for note_type, count in sorted(COUNTS.items()): + print(f"{note_type:<25} {count:>6}") print("-" * 33) print(f"{'TOTAL':<25} {total:>6}") +def generate_all(output_path: Path | None = None): + global VAULT + + if output_path is not None: + VAULT = output_path + + random.seed(42) + reset_vault() + + steps = [ + generate_years, + generate_quarters, + generate_months, + generate_areas, + generate_responsibilities, + generate_measures, + generate_targets, + generate_goals, + generate_projects, + generate_experiments, + generate_procedures, + generate_tasks, + generate_people, + generate_topics, + generate_events, + generate_evergreens, + generate_notes, + ] + for step in steps: + step() + + print_summary() + + +def parse_args(): + parser = argparse.ArgumentParser(description="Generate the large synthetic Tolaria fixture.") + parser.add_argument( + "--output", + type=Path, + default=DEFAULT_VAULT, + help=f"Output directory for the generated vault (default: {DEFAULT_VAULT})", + ) + return parser.parse_args() + + if __name__ == "__main__": - generate_all() + args = parse_args() + generate_all(args.output.resolve())