Glossary In Plain Words
Every core term defined in short sentences with pointers to the page that teaches it.
How to use this page
Read a term, then follow it to the page that shows it in action. Terms stay short on purpose so students and builders share one vocabulary.
When a discussion drifts, return here and reset on the plain meaning before continuing.
Core loop terms
A trace is the saved record of one attempt. A score is the test plus judge result. A lesson names the failure pattern and the repair idea. A patch is one small change plus one matching test. A verdict accepts or rejects with a reason. Memory keeps wins and lessons across cycles.
Grounding is the outside check that keeps the loop honest. A frozen path is judge, gate, or entry code that the loop may never edit. A transfer check is a hidden case the generator never sees during search.
Terms with home pages
| Term | Plain meaning | Learn it in |
|---|---|---|
| Trace | Saved steps, outputs, costs, timings | Core loop |
| Score | Comparable test plus judge result | Evaluation |
| Lesson | Pattern, cause, repair, risk | Core loop |
| Patch | One change plus one test | Build |
| Verdict | Accept or reject with reason | Core loop |
| Grounding | Outside check that proves gain | Evaluation |
| Frozen path | Judge and gate code, never edited by loop | Safety |
| Transfer check | Hidden case for generality proof | Benchmarks |
| Archive | Rejected tries with reasons kept | Code review |
| Drift | Goals shifting without review | Failure drills |