Official Website

Purpose and Scope

This document describes opplet.com — the enclave’s public static site — as a governed system. It is also the canonical source of the site’s version: the doc_version above is the site version shown in the footer, replacing the value that was formerly hardcoded in site configuration.

1. Nature

opplet.com is a Hugo static site. It is generated from source into plain HTML, CSS, and JavaScript and served as static files — there is no server-side application behind it. That sets it apart from the dynamic services running in the enclave’s zones (GitLab, HumHub, BookStack, ERPNext, and the rest): those are live applications; this is a published artifact.

2. What It Publishes

The site is the public edition of the enclave’s governance. It carries:

the public editions of the governed documents — the Constitution, the Participant Doctrine, the SOP, the Orientation Syllabus, and the manifests;
the Charter Release page, which reports document coherence (see §4);
the enclave’s public pages — the zone descriptions (Basement, Den, Office, Kitchen, Lounge, Range) and the sibling and partner projects.

The working source — drafts, change discussion, and member resources — does not live here; it lives in the community library. The site publishes the ratified, public face; the library holds the workshop.

3. Source and Build

The site’s source is held in GitLab and built with Hugo. Each governed page declares its identity in front matter (doc_id, doc_version, tier), and those fields drive both the per-document meta band and the document’s row in the compatibility matrix. The current Charter Release is named once, in the charterRelease site parameter, and every template that needs it reads from there rather than repeating the value.

4. Charter Release Coherence

The site tracks whether its governed documents still cohere with the last certified release:

a lockfile under data/releases/ pins the version of every governed document at the last point the set was certified to cohere;
the drift report lists documents whose live version has moved ahead of the pin;
the compatibility matrix shows the full pinned-versus-current state.

Cutting a new release re-pins the set; the procedure is recorded in RELEASE.md.

5. The Site as a Governed Document

Because the site publishes the governance, its own public copy must not drift from the documents it carries — a landing page that still reads “Sovereign” after the Constitution adopts “Custodian” is an incoherence worth catching. Bringing the site under the Charter as a governed document makes that visible: this page is pinned in the release like any other, and its doc_version is the site version. When the site’s public face changes materially, this version moves, the matrix flags it, and it is reconciled into the next release.

Changelog

v2.4.1 (2026-06-10)

The static site was brought under Charter governance: assigned the doc_id official-website, pinned in Charter Release 2026.2, and made the single source of the site version. The footer now reads this document’s doc_version and links here, replacing the hardcoded version site parameter.
Site versions prior to this entry predate governed tracking.

END OF DOCUMENT