Build with, not about: what community governance really requires.

“Community input” is too often a meeting held after the important decisions have already been made. Real governance is something else entirely — and you can tell the difference by how much power actually changes hands.

What governance really requires

• A seat with authority. Not a comment box — a role that can shape, slow, or stop the work.
• Data they can take home. Communities can export and keep their own data, under their own governance. It’s a feature, not a favor.
• Rules enforced in code. Consent, retention, and suppression that the system itself enforces — not promises in a document no one can audit.
• The right to say no. Including the right to decline a use of the data, or to end the engagement, without losing what’s theirs.

The strongest protection you can give people is a system that was never built to harm them — and rules that make sure it stays that way.

Building with a community is slower than building about one. It is also the only version that earns trust, because the trust is structural — written into who holds the keys.