Skip to content
STATUS DRAFT · LCS v1.0.0 · built in the open, contributors wanted open a PR →
// Governance

Governance

LLMConsent is community-owned and developed in the open, modeled on the IETF, W3C, and the BIP/EIP improvement-proposal processes. Decisions are made by rough consensus, not by a company.

Principles

The protocol is governed so that no single entity can control how AI systems interact with human data.

  • No single owner. The protocol is community-owned. No admin keys, no ability to freeze or seize.
  • Transparent process. All decisions are made in public, with open participation.
  • Rough consensus. Standards advance by general agreement and working code, not by vote.
  • Protocol, not platform. We define standards and encourage many independent implementations.

The proposal process (LCP)

All standards begin life as LLMConsent Proposals (LCPs) and move through a staged lifecycle. Accepted standards are immutable; changes require a new proposal that supersedes the old one.

  1. Draft. A complete proposal, championed by its author and open for feedback.
  2. Review. Formal community review of at least 30 days, with a maintainer sponsor.
  3. Last Call. A final 14-day window for objections once rough consensus is reached.
  4. Final. An accepted standard with a reference implementation.

LCPs come in three types: Core (changes to LCS-001 through LCS-004), Extension (new functionality on top of core), and Informational (best practices and guidelines).

Roles

  • Contributors submit proposals, give feedback, and report issues.
  • Maintainers review proposals, facilitate discussion, and merge accepted standards.
  • Implementers build reference implementations and SDKs and report back.

Inspiration

This model draws directly on the processes that built the open internet: the IETF RFC process, the W3C Process Document, and the BIP/EIP improvement-proposal traditions.

The full Governance Charter and Standards Process are maintained in the standards repository.