b3126044e8
- Simplify flatten_vault API to return usize instead of MigrationResult struct - Add KEEP_FOLDERS: attachments/ and _themes/ alongside type/, config/, theme/ - Use HashSet for collision tracking in unique_filename - Update wikilinks from path-based [[folder/slug]] to title-based [[slug]] - Clean up empty directories after flattening - Flatten demo-vault-v2: move all notes from type-based subfolders to root - Update smoke tests for flat vault structure - Remove migrate_to_flat_vault from repair_vault (one-time migration only) Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
1.8 KiB
1.8 KiB
aliases, Is A, Belongs to, Status, Owner
| aliases | Is A | Belongs to | Status | Owner | |
|---|---|---|---|---|---|
|
Task | 25q4 | Open | 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.