Stewardship & Governance
How MIR is operated, governed, and structurally constrained.
Registry Steward
MIR is operated and maintained by phpMyDEV, LLC, the founding steward of the MIR protocol and registry.
The steward is responsible for
- Maintaining registry availability and uptime
- Reviewing and approving partner applications
- Enforcing event submission standards
- Managing protocol updates and versioning
- Upholding constraints defined in the Constitution
The steward does not
- Score, rank, or judge users
- Sell or monetize participation data
- Edit or remove submitted events
- Decide what participation means
MIR records participation. It does not interpret it.
Founding Steward
MIR was designed as neutral infrastructure for recording participation history. The system architecture separates:
Partners submit events. Users own their history. MIR stores the record.
The steward operates the registry but does not control what partners submit or what users do with their history.
Governance Structure
MIR operates under the MIR Constitution, which defines:
- What MIR is — and what it will never do
- Neutrality by design, privacy first
- History without judgment — participation, not people
- An explicit boundary on growth and authority
The Constitution exists to protect the protocol — including from its own steward.
Future Participation
MIR is structured to support additional stewards, contributors, and advisory participation over time.
The protocol is designed for continuity beyond any single operator.
MIR is infrastructure, not authority.
It exists to make participation history visible, not to assign meaning.