WEBSITE ALPHA · AI-assisted, source-reviewed documentation · Full-stack docs reconciled 2026-08-26
64x64base

downloads

A place to start

Start with the canonical source and its green CI artifacts. Versioned beta ZIPs, checksums, release notes, and known limitations appear on GitHub Releases when a release gate passes.

Current public source

The public main branch is authoritative for source, CI, licensing, and releases. Feature branches and local maintainer trees are not public runtime truth.

GitHub Releases

Public authority model

Outside contributors need one source of truth: the public main branch. Local implementation, staging, website, and generated-manual trees are maintainer workflow details until promoted through a reviewed public change.

What is authoritative

  • Source: public main
  • Build proof: green CI for the referenced commit
  • Distribution: tagged GitHub release with checksum
  • Limitations: release notes and Current State page

Promotion convention

Source flow:
feature branch -> review + CI -> public main

Website flow:
main evidence -> reviewed site source -> verified deployment

Website prose explains evidence; it does not create implementation truth.

Accepted documentation snapshot

The current Markdown manual and 183-page command reference were reviewed and promoted from public source commit be935053. The manual carries the manual-reviewed proof label and contains 4,118 lines and 237 headings.

Latest staged assembled-manual snapshot

These permanent links currently resolve to the assembled candidate generated on 2026-07-23: 26 parts, 191 bound command pages, and 14,542 lines. A stable address is not an automatic freshness claim. A newer local documentation candidate remains review-needed and does not replace these files until its acceptance and staging gates pass. The accepted snapshot above remains the reviewed baseline; see the build manifest for the exact source commit, counts, and checksums.

Current staged downloads

These files are staged from the current implementation tree as reviewed or operator-useful artifacts. They are public derivatives or direct maintainer aids, not replacements for runtime/source proof.

As release packaging matures, this page can grow into a manifest for reviewed binaries, source archives, generated manuals, diagrams, checksums, and proof bundles. Until then, it stays deliberately simple: start with the source, build notes, and evidence pages.