[lab · T8] Shipping — track thread

[akash-coded]

L.A.B. track thread. One per track. Ask here rather than opening a new thread — the
answers accumulate where the next person will look.

Labs: L12 · Lifecycle stage: Release · the method

What this track is about

The capstone. Everything from T4 to T7 feeds one function whose output is a decision record somebody who was not in the room can audit.

Where people get stuck

Two things the gate must get right and real gates get wrong: each slice needs its own noise band (a slice of 24 has a far wider interval than the full set, and gating it fails constantly on noise), and inside the band is not a regression — it means not measurable at this n. A gate that conflates them blocks correct changes, gets disabled, and then still looks like a control.

How to ask here

Paste the check that failed and its message. The messages are written to be actionable — if
one is not, that is a bug in the lab and saying so is a useful contribution.

python scripts/lab.py run <id>            # public checks
python scripts/lab.py run <id> --hidden   # everything

Submitting

Fork, fill in starter.py, open a pull request. The
Labs workflow posts your results as a comment and
edits it in place on each push. It will not fail the build on red checks — the comment says
what failed.

What this track hands to the next one

Release produces the artefact the following stage needs. If you finish L12 and cannot say what
that artefact is for your own corpus, the track is not done — that is the point of the lifecycle
running underneath the pathway rather than beside it.