{"path":"GOVERNANCE.md","size":1726,"locked":false,"binary":false,"truncated":false,"content":"# Governance\n\nMappers Protocol is currently maintained by a single maintainer ([@iamPhatom_](https://twitter.com/iamPhatom_)). This document describes how decisions are made today and how that will change as the project grows.\n\n## Current Model — Benevolent Maintainer\n\nAll merge decisions, roadmap direction, and release timing are currently made by the project maintainer. This is a deliberate, temporary state for an early-stage protocol, not a long-term governance structure.\n\n## Decision Process\n\n- **Smart contract changes** (`programs/`) require the highest scrutiny. Any change affecting fund custody, PDA derivation, or authority checks must include a written rationale and, where possible, updated test coverage before merge.\n- **Non-critical changes** (docs, dashboard UI, tooling) may be merged with lighter review.\n- Disagreements are resolved by the maintainer with public rationale given in the relevant issue or PR — not silently.\n\n## Path to Multi-Maintainer Governance\n\nAs the protocol approaches Mainnet-Beta, governance will transition in this order:\n1. Add trusted co-maintainers with merge rights, scoped by directory (see `CODEOWNERS`).\n2. Move oracle authority from a single keypair to a multisig/threshold scheme (tracked in the whitepaper's Security Model section).\n3. Establish a public RFC process for protocol-level changes (fee model, consensus thresholds, PDA schema changes).\n\n## Reporting Concerns About Governance\n\nIf you believe a decision was made improperly or not transparently, open a GitHub Discussion or contact the maintainer directly. This is separate from the [Code of Conduct](CODE_OF_CONDUCT.md) enforcement process, which covers interpersonal conduct, not project decisions.\n"}