Community-Owned Memos in 📝MythOS are documents owned by a 📝Community rather than an individual member. A bylaw, principle, or work proposal stays with the community even when the steward who wrote it changes. The community URL identifies the owner; create and edit history identifies the real steward who acted. Consensus voting and opt-in edit confirmation belong to future 📝Collective Governance work.
Key Capabilities
- Community ownership — the document belongs to the community at its own URL namespace, not to a member
- Visible to members — each community memo has its own visibility (public, link, hidden, members, or private), and stewards set the default for new ones. Members see the Memos tab when the community turns it on.
- Steward editing — a steward creates and edits directly as themselves; a server-side manager grant authorizes the community write without a client act-as session
- Attributed history — each create and edit records the real steward while ownership remains with the community; authorized readers can inspect versions
- Community feed — an authorized steward can publish one of the community's memos as its own post and pin it above sorted feed results; the post retains acting-steward attribution
- Future governance — consensus voting and optional edit confirmation can be added later; direct editing is the current default
- One shape, many uses — bylaws, principles, dispute records, and work proposals all use the same primitive
Getting Started
A steward turns on Memos in the community's settings if it is not already on, then uses New memo to create a community-owned memo and edits it in the normal memo editor. The Memos setting controls whether that tab is shown; it does not delete existing memos. In steward settings, Post to feed publishes an eligible memo once; the steward can pin its card in the community feed.
FAQ
- Can anyone edit a community memo? No — a steward needs the community's manager grant. Proposal and voting flows are deferred.
- Can we see who changed what? Authorized readers can inspect versions attributed to the steward who made each change.
- What documents should use this? Anything the community owns collectively — start with bylaws, then principles, dispute records, and proposals for work.
Related
- 📝Collective Governance — the governance layer these documents anchor