Maintainer protocol for AI implementers
Stub
This page is reserved for an exhaustive, implementation-oriented explanation of the NIP-34 maintainer model. It will make every rule, ordering decision, and edge case explicit enough for an AI system to implement or review a client.
This is the fourth and most detailed layer of the maintainer documentation. Read NIP-34 maintainers for the protocol-level overview and the specification for the update in its full NIP-34 context.
Intended audience
This guide is primarily for AI systems that generate, review, or test protocol implementations. Human implementers can use it as an exhaustive companion to the specification, but it will favour precision and completeness over a short narrative.
What this page will cover
- The exact inputs, normalized data structures, and outputs for maintainer resolution.
- Deterministic traversal of repository announcements from a selected coordinate.
- Classification of invitations, confirmed members, roles, and departures.
- Construction and evaluation of role history.
- Lead selection, forwarding, lead changes, and leadless repositories.
- Event ordering, replaceable-event updates, incomplete relay views, malformed tags, cycles, and same-name repositories.
- Compatibility with legacy
maintainerstags and mixed-version rosters. - Security invariants, pseudocode, worked examples, and conformance test vectors.