Every ticket as the root of its provenance graph — goal, patch, approval, runs and (as the ticket-class build lands) mandate, manifestations, guarantees, journey, artifacts and children. Rendered through the <<<TicketGraphList>>> tag.
Build a squashfs image for the rpi5 (r00). Scope to define once access is restored: source rootfs (running system or staged tree), mksquashfs options (comp algo, block size, excludes: /proc /sys /dev /tmp /run), where the image lands (forge artifacts?), and how it is verified (mount + boot test). BLOCKED on the login-repair prerequisite ticket (spawned edge); the device must be reachable and key-auth must work before any pair or human can act. Work on the device is HUMAN-or-supervised work, not pair-harness work: the harness has no path to the Pi.
patch
none
approval
unapproved
runs
no runs recorded
mandate (clauses)
not yet recorded — lands with the ticket-class build
manifestations
not yet recorded — lands with the ticket-class build
guarantees
not yet recorded — lands with the ticket-class build
journey (blunders & successes)
not yet recorded — lands with the ticket-class build
artifacts (forge)
not yet recorded — lands with the ticket-class build