-
Notifications
You must be signed in to change notification settings - Fork 0
Office Hours Log
Newest first. One entry per session, with the questions that came up and where they were answered.
The point of writing these down is that the same three questions come up every cohort, and a searchable log turns the fourth asking into a link.
Thread: #87
Agenda: the two-metrics-disagree case; building an eval set with no labels; open floor.
What came up:
| Question | Where it landed |
|---|---|
| A change clears the band on evidence recall and not on full-chain. Ship it? | #29 — one effect, two levels of statistical power |
| My eval set is 96 questions, not 207. Does the ~380 figure scale? | It scales, and something else breaks: below ~100 the bootstrap's coverage is off, not just wide |
| How do I build an eval set when the client has no labels? | Notebook 02; EX-04. The part people skip is null questions |
The thing worth repeating: "inside the noise band" is a statement about your instrument, not about your change. The usual correct next move is to grow the eval set, not to abandon the change.
Copy this shape. Date descending, keep it short, link rather than restate.
## YYYY-MM-DD · One-line topic
**Thread:** #NNN
**Agenda:** two or three items.
**What came up:**
| Question | Where it landed |
|---|---|
| ... | ... |
**The thing worth repeating:** one sentence.If a question came up that has no good answer yet, say so and link the open issue. A log that only records successes is a log nobody trusts.
Wiki, not docs. Anything that should be reviewed, versioned with the code, or published to the
docs site belongs in docs/ instead —
see Wiki Conventions. · Report a problem
When it breaks
Reference
The cohort
Meta
In the repo