iusethis/iusethis · governance-as-files · ballot 1 open

The iusethis Charter

A DAO in spirit, run entirely on GitHub controls: proposals are pull requests, votes are reviews, titles are files, and the whole record is git log. Full founder control today — with the handoff written on day one.

1.Three phases, handoff by design

Most founder-led projects never write a succession plan and improvise one in a crisis. This one is in the first commit.

Phase 0 — Stewardship (now)

The Steward holds all titles and final say, including veto. Every veto must be written into the proposal it vetoes — logged power is transferable power.

Phase 1 — Council

Triggers automatically when five independent people hold titles. The veto becomes a tie-break; formal votes decide.

Phase 2 — Handoff

The Steward title itself transfers by vote. Everything already lives in an org-owned repo, so handoff is a merge commit, not a migration.

2.GitHub controls as the voting machine

Governance actGitHub mechanism
ProposePR adding docs/proposals/NNN-title.md
VotePR review — Approve = +1, Request changes = −1
Who bindsTitle-holders (docs/TITLES.md) bind; everyone else votes advisory — always logged, always read
EnforceBranch protection + CODEOWNERS on governance paths; GitHub teams mirror titles
BacklogOne project board, two queues: write-ups and governance proposals

Defaults: 72-hour lazy consensus for anything reversible; a 7-day formal vote for charter changes, titles, money, licensing, and content removal.

3.Titles — held, and delegated

A title is a named area of authority. One person may hold many and may delegate any of them — the delegate acts with full authority, the delegation is revocable, both names are in the registry. Titles lapse after six quiet months, without shame.

TitleOwns
StewardCharter, domain, org account, Phase 0 final say
RegistrarThe register of records
EditorWrite-ups and the ledger format
HeraldCarnival, announcements, syndication
KeeperSite, build, DNS, design tokens
ModeratorConduct process — never content taste
ArchivistDecision log and archive integrity
BursarMoney (dormant until money exists)

4.Joining — the onboarding SOP

  1. Apply — the Join governance issue template: title sought, the object you profess, links to merged work.
  2. Sponsorship — any title-holder comments sponsoring with one specific sentence about your work. Sponsorship is itself recognition.
  3. Acceptance — 72h lazy consensus among holders of the sought title (+ Steward assent in Phase 0). Objections cite work, never vibes.
  4. Seating — a PR adds you to the registry and the GitHub team. The merge commit is the appointment.
  5. First act — you pick your own first task. Nobody assigns it.

5.Positive-reinforcement governance

6.Ballot 1 — open now, closes 2026-09-07

Proposal 002 · formal

Adopt the governance charter

Makes GOVERNANCE.md, TITLES.md and ONBOARDING.md the law of the repo.

Proposal 003 · formal

Ratify the editorial identity

Ratifies Proposal 001 in full — the entry-as-love-story definition, the ledger format, the Vault color system, the marks.

Proposal 004 · formal

Seat the founding titles

Seats the founder in all titles — visibly, accountably, temporarily — with delegation open from day one.

Bootstrap note: at opening there is exactly one binding voter, so Ballot 1 is founder-ratified by construction. It is held as a vote anyway: the procedure runs once for real, advisory votes are gathered, and the record shows governance began by the same mechanism that will one day hand it off.