Step inside
Past, present, and what's next
An enclave is a whole dwelling brought online — the documents that define it and the rooms that run it. The constitution governs everything else; the zones are where the work actually happens.
Four doors, read as a timeline: where the enclave came from, what it's built on, what runs inside, and where it's headed. Step into any to go deeper.
Legible by design
Nothing here is hidden. Every document, every configuration, every decision is public — the enclave is meant to be read as much as run. Look as deep as you like; you can clone the whole thing.
The past enclave
How Opplet got here — the evolution of the build, and the operational lessons that shaped each decision.
And the word itself: what an enclave means here, and why it's called Opplet — start at the beginning.
:/readThe present topology
The live structure: zoning and hemispheres, the hardware manifest, and the URL strategy that ties them together.
Where the work actually happens — see how the enclave is wired.
:/mapThe present payloads
What runs on the metal: the software stack manifest, and the COTS pages — GitLab, Jitsi, and the rest.
The tools that make the rooms usable — what's installed, and why.
:/stackThe future enclave
Where the enclave is headed — Den Migration first, and the work queued behind it.
Plans in motion, not yet load-bearing — what's coming.
:/next