Project Charter

The Project Charter is the governing authority for Opplet — but it is not a single founding document. It is a living suite of documents that together define, develop, and maintain the enclave and its interrelated parts. We call it a project charter, not merely a charter, because it governs an enterprise still being built: alongside what Opplet is, it carries what Opplet is becoming — current states, desired outcomes, and development plans. A plain charter fixes a founding moment; this one evolves with the work, and holds authority precisely because it stays current rather than frozen.

At its center is the Constitution — the keystone. With the documents beneath it, the Constitution forms the Charter: four domain triads, each a Doctrine (the methodology), an SOP (the mechanics), and a Moodle course (the learning material).

A domain is the unit of governance, a team is who runs it, a zone is where it runs — three distinct things kept apart.

Beneath the keystone sit the four Doctrines and their SOPs, the Software and Hardware Manifests, and the URL and website nomenclature. Because these documents form an interconnected system, they must stay coherent — shared models agreeing, terminology aligned, cross-references resolving. The Custodian keeps the whole coherent and certifies it by cutting Charter Releases: frozen snapshots of every document’s version at a moment they were known to agree. See the live status report for current drift and coherence.