Capability showcase

The site/ directory is a dependency-free GitHub Pages experience for engineers evaluating Poise. Its Invariant Orrery translates real verification layers into an inspectable symbolic system:

• closed orbits represent generated property laws;
• fractured forms represent mutations the suite must catch;
• braided paths represent Loom scheduler exploration;
• tiered planes represent the Rust compiler floor;
• dots traveling through the system represent ordinary behavioral examples.

The capability glyphs are independent of those proof states. Selection uses a directional hexagon, affinity an anchor, topology nested planes, health an aperture, discovery radiating snapshots, observability an eye, and runtime integration a bridge. Combining the two axes lets the replay show which kind of proof is exercising which kind of primitive.

Data contract

site/data/latest.json is schema version 1. The checked-in record is explicitly labeled recorded; it preserves the dated full-campaign baseline documented in mutation-testing.md. A GitHub Actions publication replaces it with a ci record generated by scripts/write-showcase-data.mjs.

The generator counts authored Rust test entry points, property laws, Loom model boundaries, and the four cargo-mutants outcome files. Pass, fail, and unavailable states come from the corresponding Actions steps. It never infers success from a missing file and never turns a partial mutation run into the recorded full baseline.

The Pages workflow uses continue-on-error only long enough to export and upload the evidence. Its final verification step still fails the job if ordinary, property, Loom, MSRV, or mutation verification failed. The deployment job runs even then so the broken proof remains visible in the orrery instead of leaving a stale green page.

The same Pages artifact includes this mdBook at site/book/. The Orrery and book share the palette and typography in site/styles/tokens.css; the book adds only its document-specific theme. A single revision therefore owns the visual explanation, the verification record, and the engineering guidance.

To inspect a generated record without replacing the checked-in baseline:

POISE_SHOWCASE_OUTPUT=/tmp/poise-verification.json \
  node scripts/write-showcase-data.mjs

Resource and accessibility contract

The visitor’s browser never runs Rust tests, fuzzers, mutation testing, or model checking. It only replays the bounded JSON record.

• Desktop rendering is capped at 420 particles and 1.5 device-pixel ratio.
• Tablet rendering is capped at 210 particles; small screens use 130.
• Reduced-motion rendering is static and uses at most 140 particles.
• Rendering pauses while the document is hidden or the orrery is offscreen.
• Resizing rebuilds a fixed-size particle array instead of growing it.
• Every canvas interaction has an HTML button and keyboard equivalent.
• Without canvas or JavaScript, the complete semantic atlas and proof ledger remain readable.

Run the site locally from the repository root with any static file server whose document root is site/. For example:

python3 -m http.server 4173 --directory site