Reference

Resources & further reading

Everything this course teaches is anchored to published work, and this page is that anchor map: the strongest source behind each lesson, with an honest mark of how far the evidence actually reaches. The field is young — much of what follows is preprint, single-study, or drawn from general rather than legal settings, and a few techniques the course demonstrates have no supporting literature yet at all. Those gaps are listed plainly below, because for a legal reader they are part of the evidence, not an embarrassment to it. Read the verdict on each item before you rely on it.

How to read the verdicts

Strongly evidenced — peer-reviewed and replicated or multiply corroborated; teach as established.  Emerging — plausible and often rigorous, but single-study, preprint, or narrow-domain; a finding to watch.  Contested — good sources disagree; learn the disagreement, not a winner.  Vendor-claimed — asserted by a product source, not independent evidence.

L0 · Foundations — tokenisation

L1 · Getting documents in — long context

L2 · Finding what matters — retrieval / RAG

L3 · Summarising reliably — grounding & hallucination

L4 · Working at scale — agents & connectors

L5 · Reasoning across — multi-agent evaluation

L6 · Improving the loop — reliability through iteration

Adjacent — speech & document capture

Not taught as public lessons (they need real models, kept for the internal build), but on the same spine and useful if you digitise audio or scans:

Broader landscape

The honest gaps

For a sceptical reader these disclosures are the credibility. Where the course shows a technique the literature does not yet fully support, it says so — here and in the lessons themselves.

How this course runs

Every cell you ran executed in your own browser — Python compiled to WebAssembly (Pyodide), with the real tiktoken tokeniser and its vocabulary served from this site, never a third-party server. There is no backend, no login, and nothing about you is stored or sent anywhere: your progress lives only in this browser's local storage, which is why the toolkit has Save and Load buttons rather than an account. Where a lesson needed a live model or a connector, the output was pre-baked and the connector mocked — by design, so the page stays static, private, and safe to leave running in a law school. The agentic skills themselves are Claude Code practice; this course is the gentle, backend-free on-ramp to it.

Going further — take-home experiments that reproduce each finding in a live Claude or Gemini.  ·  ← Back to the course