These words carry precise meanings in this repo. Use them, don't paraphrase them; a term restated is a term forked.
- spiky profile — the intra-individual shape of abilities across
DOMAINS.md: pronounced peaks beside pronounced troughs. Neurotypical profiles are flatter. The reader's profile is spiky, not broken. - cognitive profile — that shape itself, independent of any label. What a skill actually targets.
- neurodivergent — umbrella term for brain types that deviate from the statistical norm (ADHD, autism, dyslexia, dyspraxia, Tourette's, …). Names who, never what someone can't do.
- neurotypical — the statistical-norm brain type. Flat-profile tendency; a claim about averages, not a compliment.
- normal — statistical: what most people's pattern looks like. In this repo, normal never implies correct.
- expected — normative: what a given age or role anticipates. The skills close normal ≠ expected gaps by changing the output's demands, never by "fixing" the reader.
- domain — one row of
DOMAINS.md(working memory, processing speed, attention, …). The unit rules are grouped by; the thing that composes. - condition bundle — a family skill: a named condition (ADHD, dyslexia, …) whose rules are curated from domains. Conditions don't compose; domains do. Two conditions sharing a trough share the rule vocabulary.
- trough — a domain where the profile runs low; the thing a rule exists for. peak — where it runs high; the thing rules must never fight (don't simplify reasoning because decoding is slow).
- synthesis — the honest label for a rule with no published basis: the fork's own judgment, citable to the authors, never dressed as a source it doesn't have.
- mode — the per-skill session state. Each skill turns on by invocation and off only by
"stop <condition> mode"or"normal mode"(core Persistence section). - domain skill —
metadata.type: domain: a pure trough, invocable without any condition label (ADR 0006). Stacks; conditions don't. - stack — the active mode set: at most one condition skill plus any number of domain skills.
"normal mode"clears the whole stack; each stop phrase clears only its own skill. - stricter wins — the merge rule when two active rules conflict: the tighter constraint on output overrides the looser ("one instruction per message" beats "number the steps").