parhelion-procedures is the operator runbook repo for the Parhelion flight software. It treats operational discipline as a core system component: what operators verify has to match the tag on the flight computer.
Engineering the operation
Operators cannot start from an unknown state. The repo turns Markdown checklists into versioned PDFs.
The checklist asks for facts before software runs: image versions, git tags, daemon health, disk headroom, and active screen sessions. It also records field limits, including tooling memory-leak warnings on the flight computer.
Release discipline for documents
A Makefile and CI build the PDFs and inject version data from git. CI publishes a bundle tied to a software release tag. Operators download that bundle instead of ad hoc notes.
The point is match, not ceremony: the operational envelope should match the code on the hardware.
Leadership context
Procedures encode release integration discipline for the team flight application. CI publishes PDF bundles tied to software tags so integration review has a verifiable operator envelope: image versions, git tags, daemon health, disk headroom, GO/NO-GO gates. OS identity checks send operators to the image lane in Parhelion Yocto.
OS and application release boundaries
Operator checklists cover software tags, daemon health, and GO/NO-GO gates for the team flight application. OS image changes are a separate, rare event: eMMC reflash from staged WIC artifacts, with identity checked against /etc/parhelion-os-release. Day-to-day application updates use parhelion-update <tag> without rebaking the image.
The OS build, flash workflow, and bench evidence live in Parhelion Yocto. The program hub is Parhelion. This repo stays on operator runbooks tied to application release tags.