Concepts
The Concepts section explains the model the runtime is built on. The chapters are self-contained but assume basic familiarity with ATProto records and panproto's lens vocabulary. What you need first states the assumed background.
| Chapter | What it explains |
|---|---|
| Why idiolect exists | The founding problem, developed through one worked example; no formalism. |
| What you need first | The assumed background: ATProto's record model, plus one concept from panproto (the lens). |
| Idiolect, dialect, language | The frame the project is named after; what each layer is responsible for. |
| The dev.idiolect.* lexicon family | The shipped lexicons, what each one covers, and how they compose. |
| Records as content-addressed signed data | Why ATProto's record model is the substrate; what the runtime gets for free. |
| Lens semantics and laws | The get / put / complement model, GetPut, PutGet, optic classification. |
| Open enums and vocabularies | Why every enum field is open; how *Vocab siblings extend slugs. |
| The vocabulary knowledge graph | The typed multi-relation graph, OWL Lite, SKOS Core, registry queries. |
| Deliberation | The deliberation lexicons, how they relate to belief / recommendation. |
| Observer protocol | Why aggregate state lives in records, not in a central endpoint. |
| Lexicon evolution policy | Every lexicon revision ships with a derived, classified, verified, published lens. |