Project Charter

The Opplet Project Charter is the complex of documents by which this enclave is defined, developed, and maintained — its whole governing body, not any single file. The Constitution is its keystone, the boundary law everything else answers to; the SOP (operations), the Participant Doctrine (methodology), the infrastructure manifests, the Orientation Syllabus, and the Official Website document are its other members. The Charter is the whole; the Constitution is one document within it. It is defined in Constitution §13, which this page reports on but does not override.

Because the Charter is many documents that reference one another, they have to stay coherent — cross-references resolving, shared models agreeing, shared terms used the same way throughout. A Charter Release records that coherence: a frozen, certified snapshot of the version every member held the last time the set was reconciled and found to cohere. Releases are immutable — a new one is cut, never edited.

This page is generated; it always reflects live state, and nothing on it is maintained by hand. It compares each member’s current doc_version against the version pinned in the active Charter Release. Between releases a member may move ahead of its pin; that drift is expected, and is exactly what the summary below flags for the next reconcile.

Needs review before the next release

Full compatibility matrix

Cutting a release

Cutting a Charter Release is the Custodian’s responsibility (Constitution §17); the step-by-step procedure lives in the SOP §11.