Resources · RCC ClusterDocs

Maintaining RCC Expedition releases

Current release:

RCC-Expedition-USB-v1.0.1.zip
SHA-256 0cc1b6ad446db85d276dd7634f1fddca1c6029c3838191d404870a9912278780

Publication policy

RCC Expedition may be published after static validation and content review.

A native Windows 11 smoke test is recommended during rollout but is not a publication blocker. Do not wire that test into the MkDocs build or site deployment gate.

If a native Windows test identifies a defect, publish a corrected versioned course asset and update docs/rcc-expedition.md.

Ownership boundary

RCC Expedition owns workstation-security onboarding and the local challenge-first learning experience.

ClusterDocs owns mutable RCC technical facts. Prefer links from the course to ClusterDocs over copying changing RCC configuration into the download.

All embedded ClusterDocs links must use the current production origin https://ikim-essen.github.io/ClusterDocs/ and, where a matching NG lesson exists, link to that future page rather than a retired legacy route or only the home page. A possible later docs.ikim.uk-essen.de CNAME is not active release input. Rebuild and validate the release with:

python tools/rebuild_expedition_release.py
python tools/validate_expedition_release.py

Commit the resulting ZIP, outer checksum, and the checksum printed on the public Expedition page together. The repository validator checks the outer digest, every inner digest, archive path safety, and embedded documentation origins.

expedition-overlays/ contains the newcomer-facing START HERE.html and READ ME FIRST.txt. The deterministic rebuild replaces those two files before recomputing every inner checksum, so the public archive cannot drift from the reviewable source overlays.

The original v1.0.0 ZIP and checksum remain in the download directory so an existing versioned link continues to resolve. Never replace an already published versioned archive; publish usability or content changes under a new version.