{% extends "base.html" %} {% block body_class %}{% endblock %} {% block title %}Governance — MoonBite decision records (ADRs){% endblock %} {% block meta_description %}Every rule change to MoonBite is written down as an Architecture Decision Record. Read them all.{% endblock %} {% block head_extra %} {% endblock %} {% block content %} {# d01 mark: one closed path; d02 glyph bars at y=-40.5 and 11.5. #} {% set MARK = "M 13.99 -99.02 A 100 100 0 1 0 99.02 -13.99 A 62 62 0 0 1 13.99 -99.02 Z" %} {% set newest = adrs[-1] if adrs else none %}
Governance
Every change to how MoonBite works is written down first, in the open, as an Architecture Decision Record. No silent rule changes. Read the reasoning behind the chain.
Decision log
Each record explains what was decided and why. Open one to read its full text, including its status and date.
{{ adrs|length }} records
Process
The record comes first. The code follows it, and anyone can check the running parameters against both.
A change starts as an Architecture Decision Record: what is decided, why, and which earlier records it relates to or replaces. Its status (accepted, proposed or draft) is stated at the top.
The full text of every record is public and listed in the decision log above.
Changes to the rules land in the source code, which anyone can read and build.
The monetary parameters are published as JSON at /api/consensus. Compare them with the records that set them.
In force
Read from the consensus parameters, not typed into this page.
Full parameter set: /api/consensus
The records explain the reasoning. The source code and the consensus parameters are what the network runs.