Project Charter
The Opplet Project Charter is a dynamic suite of documents used to actively define, develop, and maintain this enclave as a whole and its major interrelated components. Because Opplet continuously evolves, this collective framework — encompassing current states, desired outcomes, and development plans — functions as the governing authority, rather than any single, static file.
The summary below is auto-generated to reflect the live state. It compares each component’s current doc_version against the version pinned in the active Charter Release. Because individual documents update between releases, expected drift occurs. This summary flags that drift to inform the next reconciliation.
Needs review before the next release
Full compatibility matrix
| Document | Current | Pinned in Charter Release 2026.3 | Status |
|---|---|---|---|
| Tier 0 — Keystone | |||
| Opplet Constitution | v12.8 | v12.8 | As released |
| Tier 1 — Doctrine & Architecture | |||
| Enclave Doctrine | v1.2 | v1.2 | As released |
| Commons Doctrine | v2.2 | v2.2 | As released |
| WiseNxt Doctrine | v4.4 | v4.4 | As released |
| Workplace Doctrine | v1.2 | v1.2 | As released |
| Tier 2 — Operations & Learning | |||
| Enclave SOP | v2.2 | v2.2 | As released |
| Enclave Bootcamp | v2.0 | v2.0 | As released |
| Commons SOP | v2.2 | v2.2 | As released |
| Commons Welcome | v2.1 | v2.1 | As released |
| WiseNxt SOP | v1.4 | v1.4 | As released |
| WiseNxt Orientation | v2.0 | v2.0 | As released |
| Workplace SOP | v1.2 | v1.2 | As released |
| Tier 3 — Manifests & Reports | |||
| Software Stack | v1.6 | v1.6 | As released |
| Hardware Manifest | v1.2 | v1.2 | As released |
| URL Nomenclature | v6.0 | v6.0 | As released |
| Opplet.Com Website | v2.5 | v2.5 | As released |
| Tier 4 — Zone Projects | |||
| Den Migration | v1.0 | v1.0 | As released |
Charter releases
As an interconnected system, these documents must maintain strict coherence, ensuring shared models agree, terminology aligns, and cross-references resolve. A Charter Release captures this coherence, providing a frozen, certified snapshot of every component’s exact version at the time of reconciliation.
Releases are strictly immutable; past releases are never edited, only superseded. Cutting a new Charter Release is the Custodian’s responsibility (Constitution §17), following the procedures detailed in SOP §11.