Governance
Nokto is an open protocol for receiving accounts. Nokto Platform maintains it, and builds a commercial product on it — on the same terms as anyone else.
What that means in practice
Nokto Platform is the steward. It holds commit rights, reviews and merges pull requests, decides proposals, and is accountable for releases. It also builds a commercial product on this protocol, and that product resolves @nokto-protocol/* from the public npm registry at pinned versions, exactly as any integrator does — a commitment while nothing is published, and verifiable by anyone once it is. SCOPE.md explains why that constraint is the one that matters.
This is steward-maintained software. It is not consensus governance: there is no vote, no council, and no neutral foundation. Saying so plainly is more useful than implying a structure that does not exist — you can then judge the protocol on whether its interfaces are honest and its decisions are reasoned, which are things you can actually check.
The consensus surface
Almost everything is an ordinary pull request. Bug fixes, documentation, tests, issuer adapters, verifier plugins, examples, performance work, and SDK ergonomics that do not change the wire — open one and we will review it.
Six things are different, because an integrator pins against them and a change breaks code we cannot see:
- The signed income-claim message layout
- The predicate registry — adding a predicate, or changing an existing one's arguments
- Assurance tier or binding scheme semantics
- Any of the ten invariants
- Contract ledger state layout
@nokto-protocol/schemaconformance vectors