Repository navigation
v0.3.0 — complete the chain: claims and the probe
Completeness: explanations must not omit the connections a learner needs.
- Claims in
model.yaml:why,guarantee,mechanism,definition,limit,misconception, each with required fields (awhyneeds the simplest alternative and its failure; aguaranteeneeds an example and a counterexample). Renderings mark where they cover each claim (<!-- claim: id -->,data-claim,self.claim()), andexplainer checkfails on incomplete or uncovered claims. - Function rule: a function named in
model.md(exp, log, sqrt, sigmoid, …) with nowhyclaim fails the check, unlessaccept_unjustifiedgives a reason. explainer probe: a prompt for a fresh agent that reads onlymodel.mdand lists omissions before rendering. On the existing examples it found "why exp" and the Dijkstra negative-edge counterexample.- Model template: new sections Why this form, Concrete cases, Terms, Scope. Principle 10, "Complete the chain".
- Blind test: claims with
askbecome quiz questions; the rubric expects their cases. - Examples:
softmax-temperaturenow explains why exp (with the divide-by-sum and squares counterexamples, live on the page and in the video), why divide by T, shift versus scale, and a worked T = 2 step.dijkstraadds why the smallest estimate, finality with this run's numbers, path reconstruction, and a negative-edge chapter.git-bisectadds the halving trace and a case where bisect names the wrong commit. - Checks: scientific notation is one number (6.0 × 10⁻⁶); hash fragments like
4e10stay identifiers;renderreports repeated narration lines. - Docs: authoring guide, model reference, web toolkit reference, docs index, contributing guide.
Full history: CHANGELOG.md