Governance

How Kronk-the-project is governed

Kronk uses a Seed / Kommons pattern.

Seeds — plant an idea

Anyone can plant a Seed. A Seed is a lightweight coordination surface: here's an idea, here's what it might look like, here's what's needed to build it. No approval required — the point of a Seed is to gather the people who want to work on something.

Kommons — structural moves

Anything that touches the platform's spine — visibility scopes, storage discipline, reserved vocabulary, the manifest schema, the feed contract — is a Kommons proposal. Kommons proposals require support to enact.

Sub-layers are places; ideas are things to build. Don't route a Seed through Kommons; don't try to plant a scope change as a Seed.

Stewards and maintainers

The people credited on /kronk/contributors are the ones who built and maintain each korner's code. Steward is recognition, not power: being named a steward doesn't grant runtime moderation authority beyond what any account has.

Runtime moderation, when it's needed, escalates to the instance admins through the standard Mastodon report flow. Structural moderation (deprecating a korner, resetting a shared scope) routes through Kommons.