⚠️ Draft — Non-authoritative content (noindex)

INFORMATIVEDRAFTnone

Truth Source: Repository schemas and tests are authoritative.

Contributing to MPLP

Protocol Status: FROZEN

What You CAN Contribute

Contribution Type	Allowed	Process
Bug fixes (non-normative)	✅	Pull Request
Documentation clarifications	✅	Pull Request
New examples	✅	Pull Request
Integration adapters	✅	Pull Request
Performance improvements	✅	Pull Request
New features (normative)	⚠️	RFC Required
Schema changes	⚠️	RFC Required
Breaking changes	❌	New Version Required

How to Contribute

1. Reporting Bugs

Use the Bug Report issue template:

• Describe the issue clearly
• Provide steps to reproduce
• Include expected vs. actual behavior

2. Proposing Changes (RFC Process)

For any change that affects the protocol specification:

1. Do NOT open a PR directly
2. Open an RFC (Request for Comments) issue using the RFC template
3. The MPLP Protocol Governance Committee (MPGC) will review the proposal
4. See MIP Process for details

3. Pull Request Process

1. Fork the repository
2. Branch from main
3. Make changes
4. Verify (see verification checklist below)
5. Commit using Conventional Commits
6. Submit PR

Verification Checklist

Before submitting a PR:

# Install dependencies
pnpm install

# Validate the canonical schema bundle
pnpm verify:schemas

# Run package tests
pnpm test

# Run Golden Flow coverage
pnpm test:golden

Critical Requirements:

• All Golden Tests (tests/golden/) MUST pass
• All Schemas MUST validate (pnpm verify:schemas)
• Docs/governance/config changes SHOULD pass pnpm gate:cleanup-sweep
• No normative changes without RFC approval

Repository Links

Resource	Location
Root CONTRIBUTING.md	CONTRIBUTING.md
Code of Conduct	CODE_OF_CONDUCT.md
Security Policy	Security Policy
MIP Process	MIP Process

License

By contributing, you agree that your contributions will be licensed under the Apache-2.0 License.

---

Repository: github.com/Coregentis/MPLP-Protocol
RFC Required For: Schema changes, normative changes, new features