✓Explain mechanistically why a model produces a confident, wrong citation1 attempt
◇ a cold, no-notes verbal explanation that locates the flat/near-uniform distribution over content tokens, states nothing wires that uncertainty to a hedge, cites the post-training penalty on 'I don't know', and concludes confidence != correctness
Hallucination is structuralLogits → softmax → samplingPretraining
et1 marginal pass. Cold first pass (6.5): had form-vs-content (peaked vs flat) and no-truth-only-probabilities, but dropped the frozen-weights/corpus-gone root and gave the shallow 'incentivized to be confident' for the confidence crux. On one redirect, produced the missing-wire decoupling himself cleanly (flat distribution not connected to the hedge decision; 'no process expresses that the token was picked from a flat distribution') AND added an unprompted insight: a guessed token gets appended and baked in as truth, conditioning the rest of the answer. Substance is all there; the supplied piece (frozen weights) he's independently nailed cold earlier this session. Pass = test-time completeness lesson, not a knowledge gap.
✓Given two prompts, predict which costs more and why1 attempt
◇ a correct cold prediction with the mechanism — quadratic attention cost in token count (one 1000^2 vs ten 100^2), input-vs-output token pricing, and context/window growth
Tokenization (BPE)Self-attention (intuition)Context window / KV cache
passed et2 (cost prediction): B, ~200x tokens; reconciled linear per-token bill vs super-linear attention compute (latency/GPU), plus the sharp insight that per-token pricing is a deliberate linear abstraction over quadratic compute. came out in pieces under prompting - worth a cold re-confirm later; underlying n^2 mechanism already solid from M2
○Explain why the same prompt at temp=0 returned two different answers
◇ a cold explanation that temp=0 is greedy, not deterministic — float non-associativity under batching/parallelism (and MoE routing) flips the argmax between near-tied logits
Logits → softmax → samplingWhy temp=0 isn't reproducible
2 concepts to go○Explain why last week's fact isn't in the model but works once pasted into context
◇ a cold explanation that the fact isn't in the frozen pretrained weights (knowledge cutoff) but works once pasted because attention over the in-context tokens conditions the answer (in-context learning), with no weight change
PretrainingContext window / KV cacheIn-context learning
3 concepts to go○B1 (build): turn messy dev artifacts (logs, stack traces, API docs) into validated JSON at ~100%, no fine-tuning
◇ a CLI/service that turns messy dev artifacts (logs, stack traces, API docs) into schema-validated JSON, with a small eval showing ~100% validity on a held-out set and no fine-tuning — committed repo + eval output
Structured outputContext engineeringObject model & reference semanticsExceptions & control flowPydantic & validation at the edges
5 concepts to go○B2 (build): docs/code RAG over a real repo with a retrieval eval harness that proves a measured improvement
◇ a docs/code RAG over a real repo plus a retrieval-eval harness (recall@k on a labeled set) that proves a measured before/after improvement from one change — committed repo + eval numbers
RAG failure modesRetrieval evaluationAdvanced retrieval patternsThe eval mindset
4 concepts to go○B3 (build): a dev-tools agent (PR review / log triage) with human approval gates that recovers from tool failure
◇ a dev-tools agent (PR review / log triage) with human approval gates before actions and recovery from an injected tool failure — committed repo + a trace showing the gate firing and a recovered run
Agent failure modesTool use / function callingHuman-in-the-loop & approvalsPrompt injection & jailbreaks (defense)
4 concepts to go○B4 CAPSTONE: ship a cloud service from B2/B3 - model routing, caching, full tracing, a 30+ case eval gating CI, and a documented before/after metric
◇ a deployed cloud service (model routing + caching + full tracing) with a 30+ case eval gating CI and a documented before/after metric — live endpoint + CI config + the metric writeup
Build an eval harnessModel selection & routingDeployment & CI/CD for AIObservability / tracingOnline eval & monitoring
5 concepts to go
depth-as-procrastinationdormant
treats 'I could go deeper here' as a reason to stay on an already-mastered concept; optimization bias operating on the syllabus instead of the next real gap
completion-seekingdormant
wants full coverage of everything before moving on; control preference. Redirect to the exit test / deliverable, not coverage
premature-convergence×2
closes options / commits to one explanation before testing alternatives; efficiency over exploration