Week 9 · Sunday — consolidate and defend
Retrieval project: label audit, contamination check, adaptation ADR
- 90 minsession length
- 4timed blocks
- 5tasks
- —status
Session plan90 min
Before you start
Before the session: Saturday's corpus/ and eval/ files, the baseline run file, and the scoring script that
re-computes recall@5 and MRR@10 from a query file and a run file. No new installation or data. An ADR template
with headings (context, decision, options, evidence, consequences, revisit trigger) in notes/adr/.
Blocks4
Block 1: Spaced recall
20 minClosed notes, then correct:
- Day 41: what TF-IDF up-weights and down-weights, and one query type where it beats an embedding model.
- Day 42: why a fluent answer is not evidence; what temperature and top-p change.
- Day 43: the missing-capability question behind prompting vs retrieval vs fine-tuning, and why the evaluation set is built before adaptation.
- Day 44: trainable parameters for a rank-8 LoRA update on a 4096 x 4096 weight matrix, compared with the full matrix.
- Day 45: two ways a model-based judge can be biased, and what benchmark contamination means.
- From Week 8: what your neural comparison did and did not prove.
Tag each miss for review.
Block 2: Evaluation-set audit and baseline limits
40 min- Label audit (15 min). Without looking at your labels, re-label a random sample of 10 answerable queries
from the chunk file. Compare with the original labels: count agreements, list disagreements, and resolve each
with a written reason. Save corrections as
eval/queries_v1.1.jsonlwith a change log; never edit v1 in place. - Contamination check (10 min). For each query, compute the longest shared word sequence (or word n-gram overlap) with its labelled chunks. Flag queries that copy the source wording, and flag any query written after you saw retrieval output. Decide per flagged query: keep as a look-up item, rewrite as a new item, or exclude, and record the decision.
- Freeze the split (5 min). Split the audited set into a development part (about two thirds, used for all tuning in Weeks 10-11) and a held-out part (used once in Week 11 for the final comparison), stratified by query type. Record the hash of each file.
- What the baseline cannot answer (10 min). Re-score the baseline on v1.1 (development part only) and list the query types it handles badly, with query ids. Separate what retrieval cannot fix (the corpus lacks the answer) from what a better retriever might fix.
- Label audit (15 min). Without looking at your labels, re-label a random sample of 10 answerable queries
from the chunk file. Compare with the original labels: count agreements, list disagreements, and resolve each
with a written reason. Save corrections as
Block 3: Teach-back and decision defense
20 minWrite the adaptation ADR (architecture decision record, 150-250 words) for a hypothetical academy study assistant built on this corpus: context, the missing capability, options considered (prompting only, retrieval, LoRA or full fine-tuning), decision, evidence used (your baseline results and audit), consequences, and the evidence that would make you revisit the decision. Then defend it aloud in two minutes against this challenge: "Just fine-tune a model on all the lessons; retrieval is unnecessary."
Block 4: Weekly review and planning
10 minUpdate the weekly log with corrected recall misses, the label-agreement result, contamination decisions and the dataset versions now frozen. Week 10 priority: the context flow and one controlled retrieval improvement chosen from today's failure list, evaluated on the development part only.
Tasks5
Task 1
recallAnswer the Days 41-45 recall set plus one Week 8 item and correct misses; include the LoRA parameter arithmetic.
Task 2
reviewBlind re-label 10 random answerable queries, compare with the original labels, resolve disagreements in writing, and publish a new version with a change log.
Task 3
analysisFlag queries that copy source wording or were written after seeing retrieval output, decide what to do with each, and freeze a stratified development / held-out split.
Task 4
analysisRe-score the baseline on the development part of v1.1 and separate failures a retriever could fix from questions the corpus cannot answer.
Task 5
defenseWrite and defend the adaptation ADR choosing among prompting, retrieval and fine-tuning for a study assistant on this corpus.
Rubric4 criteria
| Criterion | Meets | Exceeds |
|---|---|---|
| Label reliability | A blind re-label sample is compared, disagreements are resolved in writing, and corrections go into a new version. | Identifies a systematic labelling pattern (for example, partly relevant chunks graded as fully relevant) and fixes the guideline, not only the items. |
| Contamination and split discipline | Copied-wording and post-hoc queries are flagged with a stated measure and handled; the split is stratified and hashed. | Explains how contamination would inflate the Week 10-11 comparison and how the held-out part protects it. |
| Adaptation decision | The ADR names the missing capability, compares at least three options, and cites the learner's own evidence. | States quantitatively what evidence would justify fine-tuning instead, and the cost of collecting it. |
| Recall and review | Recall misses are corrected and tagged; dataset versions and the Week 10 priority are logged. | Links a recall miss (for example, judge bias) to a concrete risk in the learner's own evaluation plan. |
Required output
Versioned corpus/evaluation set, baseline results, and adaptation ADR: the audited evaluation set v1.1 with change log and frozen development / held-out split, contamination decisions, baseline limits by query type, corrected recall mistakes, the ADR, and the Week 10 priority.
Studios are tracked separately from the 60 core lessons; completing one never completes a lesson.