[lab · T7] Agents & Traces — 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: L11 · Lifecycle stage: Operations · the method

What this track is about

A trace that records the answer is a log. A trace that records the decisions is evidence.

Where people get stuck

The field people omit is the config fingerprint. Without it you cannot distinguish the system is broken from the system changed, and three weeks after a user report those need completely different responses.

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

Operations produces the artefact the following stage needs. If you finish L11 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.