Governance
Last updated: June 11, 2026
In plain English: Amitte is currently run by its maintainer — a BDFL-style setup, stated plainly rather than dressed up as a committee. Policies live in the public repo and change through versioned commits with notice in the changelog. Publishers carry one of three trust tiers (unverified, verified, official), revocations are published in a public feed, and moderation actions are counted in a live transparency report.
How decisions are made
Amitte is governed by the project maintainers — at this stage, a single person. That's BDFL-style governance, and we'd rather state it plainly than pretend otherwise. As the project grows, governance will broaden; until then:
- Maintainer(s) — final call on roadmap, releases, policy, and takedowns. Significant decisions are recorded as ADRs in the repo's
decisions/directory. - Contributors — anyone who ships accepted PRs.
- Community reviewers — a planned reputation-based role that will triage submissions and flag reports.
Decision process by weight:
- Routine (bugfix, dependency bump, new seed skill): maintainer merges.
- Feature-shape or spec change: an RFC in
docs/rfcs/with a 7-day comment window; maintainer decides. - Policy change: see below.
How policies change
All policies — this document, the Terms of Service, Privacy Policy, Content Policy, and Takedown Policy — are versioned markdown in the public repository. Anyone can read the history, diff a change, or open an issue against a proposed one.
Material policy changes get:
- A versioned commit with the change visible in the repo history.
- An entry in the Changelog.
- A 14-day notice and comment window before taking effect (except urgent safety or legal changes, which take effect immediately and are flagged as such in the changelog).
- An updated "Last updated" date on the policy page.
Trust tiers
Every publisher carries one of three tiers, shown on their profile and on each entry:
| Tier | Meaning | How it's earned |
|---|---|---|
| unverified | Default. A GitHub account signed in and published. No identity claims beyond the GitHub handle. | Automatic on sign-up |
| verified | The publisher proved control of a domain via a DNS challenge (a token we generate, placed in a TXT record and checked). The domain is shown on their profile. | DNS domain proof |
| official | First-party — the publisher is the Amitte project itself or a party we've directly confirmed. Granted manually by maintainers only; never automatic. | Maintainer grant |
Tiers are advisory trust signals, not endorsements. A verified badge means "this publisher controls that domain" — nothing more. Evaluate content on its merits regardless of tier. Tier changes (manual and reputation-driven) are counted in the transparency report.
Revocation feed
When a version is revoked — by us under the Takedown Policy or by the publisher — it is added to the public revocation feed at /v1/revocations.json. SDKs and caching consumers should poll this feed and drop revoked versions. The feed is append-only: once revoked, a version stays listed so that consumers who fetched it earlier can find out.
Transparency
Moderation and admin actions — tier changes, takedowns, flag triage — are counted in the live transparency report: aggregate totals and a redacted recent-action feed, no publisher identifiers.
Conflict of interest
Maintainers who publish content go through the same review pipeline as everyone else. Flagged submissions from conflicted parties are reviewed by a second maintainer when one is available, and postponed until one is otherwise.
Funding
The project currently takes no payments. If that changes, a separate finance policy will be published covering who signs, where funds are held, and how conflicts of interest are disclosed.
Exit plan
If the maintainer(s) can no longer run the project, a 60-day notice will be posted. The repository and published seed skills remain under their licenses, and registry-hosted data will be exported to a public archive where possible.
Contact
Governance questions: policy@amitte.com, or open an issue at github.com/amitte-ai/amitte/issues tagged governance.