MWIP Incubation Governance

Decision process

Incubation changes are proposed as issues or pull requests with a problem statement, security/compatibility assessment, fixture impact and migration note. Core schema changes require two maintainer approvals and a minimum seven-day review window after the repository becomes public.

Roles

The initial technical group has three required perspectives: a MiteClaw reference implementation maintainer, an independent implementation representative and a security/policy reviewer. No single vendor may unilaterally approve a breaking Core change after open governance begins.

RFC lifecycle

IDEA → DRAFT → REVIEW → ACCEPTED/REJECTED → IMPLEMENTED. A draft may not create an authority grant. An accepted specification still requires conformance fixtures and implementation-specific security review before effect-capable use.

Claim policy

During private incubation, the project is described as an incubating profile. It must not claim industry-standard status until public governance, independent implementation and interoperability gates in the charter are met.