Officer Handoffs in 📝MythOS are an upcoming succession feature for 📝Communities that turn the transfer of power between elected officers into a structured, mutually attested checklist. They exist because succession is where real cooperatives break: an outgoing treasurer forgets a bank login, an incoming president never gets the admin keys, and the organization quietly loses continuity nobody notices until it matters. This is for communities running 📝Collective Governance with term-bound roles, where every election implies a transfer and every transfer deserves a record.
Key Capabilities
- Handoff checklists — MythOS provides a standard template; each community edits it to match its real assets
- Mutual attestation — outgoing and incoming officers each confirm what was transferred and how it went
- Incomplete-handoff reporting — a successor can flag what was never received and request intervention
- Escalation path — unresolved handoffs route to the community's dispute-resolution process
- Beyond the platform — checklists can cover real-world items like bank credentials and account access
Getting Started
Coming soon. Officer Handoffs ship alongside the first release of Collective Governance elections.
FAQ
- What if the outgoing officer doesn't complete the handoff? The incoming officer reports the specific incomplete items, and the case escalates to the community's dispute-resolution process.
- Who writes the checklist? The community — MythOS ships a common default, and communities adapt it to their actual roles and assets.
- Does this only cover MythOS permissions? No; the checklist is community-authored, so it can include anything a role actually holds, from platform permissions to bank accounts.
Related
- 📝Collective Governance — the elections and term system that trigger handoffs
- 📝Community-Owned Memos — where handoff templates and records live