This repository is the canonical source-of-truth for the AILedger Charter — the public commitment document that governs how AILedger operates.
The Charter names the customers AILedger refuses, the features AILedger refuses to build, and the decisions that require Board of Directors review. It is published from day one, before customers, regulators, or the public have asked for it. The credibility of the document depends on its having been written and posted before pressure to compromise it arrived.
- Canonical:
CHARTER.mdin this repository. - Versioned: the earliest version tag in this repository (currently
v1.1) anchors the earliest preserved Charter text. Future amendments are tagged sequentially per the amendment procedure below. - Rendered:
ailedger.dev/charterrenders the canonical text from this repository.
This is a publication repository, not a collaboration repository. The Charter is one document, governed by the procedure described inside it. Issues and discussions are disabled. Anyone can fork the repository, propose amendments via pull request, or simply read and verify the canonical text.
Per Charter Section "Decisions requiring board review": any amendment to this charter requires unanimous Board of Directors approval.
The mechanics of an amendment:
- Anyone may open a pull request proposing an amendment (members of the Board of Directors, AILedger team members, or members of the public).
- The pull request must include the proposed text change, a rationale, and the date of the change.
- The pull request is held open until each member of the Board of Directors has approved it. Unanimous approval is required.
- Upon unanimous approval, the change is merged and a new version tag (
v1.1for minor textual revisions,v2.0for substantive scope changes) is applied to the resulting commit. - The previous version's git tag is preserved, so historical Charter text remains accessible at its versioned URL.
Amendments are public: pull requests, approval signatures, and merge commits are part of the public git history. There is no private amendment path.
- It is not a place to file general AILedger product issues. Those belong in the AILedger product repository.
- It is not a place to discuss compliance interpretations of the Charter. Those belong in customer-facing documentation maintained elsewhere.
- It is not a place to propose AILedger feature requests. Charter-refused features are listed in the Charter itself; non-Charter-related features belong in the product repository.
The Charter text is published under Creative Commons Attribution 4.0 International (CC BY 4.0). The text is freely shareable, with attribution to AILedger.
For Charter-related questions: charter@ailedger.dev.
For product-related questions: see the AILedger product documentation.