olwiki — Our Living Wiki

olwiki is a living document development system. It presents version-controlled documents as coordinated, multi-layer systems — where frameworks, vehicles, theses, and references evolve together and stay accountable through measurable, reviewable change.

Mission

To make complex, living documents readable, reviewable, and improvable by turning every document into a layered, version-controlled, and human-verifiable system — grounded in Codeberg as the single source of truth.

The document format: .phlee

Every document is a .phlee file — a self-contained, layered binary that is the source of truth on disk and in the repository.

• Layers. A document can carry multiple layers (framework, vehicle, thesis, commentary, data). Each layer is a distinct, reviewable slice of content.
• Sections. Layers are marked up into named, indexed sections, so readers can navigate to a specific claim and anchor a contribution to it.
• Metadata. Title, tier, status, and structure travel with the document — no separate metadata sidecar is required.
• Portable. One file holds everything; the site, editors, and tooling all read the same bytes.

How the site works today (static design-test state)

The current demo is a fully static build — no application server. It exists to test the design, the .phlee format, and the reading/contribution flow.

• Static rendering. demo-olwiki reads the .phlee files and renders each layer through a Markdown pipeline into real HTML at build time.
• Client-side fluidity. Layered toggles, the HUD table of contents, reading progress, and anchored comments all run in the browser over the rendered DOM — the pages are interactive without a server.
• Topcoat UI. Pages are styled through the Topcoat design system (the same stack used by the full olwiki server).
• Hosting. Cloudflare Pages serves the static output, with Pages Functions providing serverless endpoints for gated access.

Contribution & collaboration — current and future

Now (static limits): Contribution is email-based. You can anchor a note to a sentence or section, and the site assembles a structured, plain-text contribution email. There is no write-back, no accounts, and no live submission — the static build cannot mutate the Codeberg source itself.

Future direction: olwiki is designed for a more direct collaboration workflow — signed-in participants submitting contributions that are written back to the version-controlled document, tracked, reviewed, and merged. The .phlee format already carries collaboration state (profiles, contributions, annotations, votes) so this utility can be unlocked without a format change. That capability is an active design goal, not yet live in the static demo.

Technical stack

Access

This document is public — no sign-in required. Some documents are restricted: they require an access code and are served behind it until they are ready to be published.

[!note] Get in touch Questions or feedback: olwiki@p-h.email