[lab · T1] Corpus & Chunking — 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: L01, L02 · Lifecycle stage: Discovery · the method

What this track is about

The retrievable unit is a decision, not a default. Both labs here are about consequences that arrive later: an id scheme decides whether re-ingest is incremental or a rebuild, and a heading path decides whether a chunk can be cited at all.

Where people get stuck

The most common stuck point is L01's hidden check on insertions. Scheme C is stable against edits, not insertions — inserting a paragraph at the top shifts every ordinal below it. That is a real limitation, the check exists to make you meet it, and naming it before an interviewer asks is the whole point.

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

Discovery produces the artefact the following stage needs. If you finish L01, L02 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.