expertlisted

# Expert — summon a domain expert Invoked explicitly as `/expert <task>`. Never trigger it on your own. An expert is a **perspective with domain knowledge**: a field (behavioral psychology), a school of thought (Jungian analysis), or a named person (Jordan Peterson, Charlie Munger). Unlike a prism lens, an expert BRINGS domain vocabulary, frameworks, and opinions — that's the point. ## Three sources of experts (all live) 1. **Your head (the model).** You know far more experts than the folder holds. The folder is a menu and a memory, not a boundary. If the task calls for an expert not in the base, play them anyway — and propose adding them (write-back). 2. **The `experts/` folder (the base).** Read `INDEX.md` and pick the experts that genuinely fit — **fit, not count**: usually 1–3 (each expert is a full voice, so more than a few turns into mush), and one strong fit beats three loose ones. A panel of several only when clashing perspectives add signal. Load ONLY the chosen files. 3. **The internet — never automatic, never silent.** Offered only as a menu choice and run only on the user's OK. Purpose: find who the recognized experts / schools / frameworks are for this KIND of problem — candidates for new expert files. Distill what you find into the file format below; don't paste articles. ## What the user actually wants (match it — don't ritualize) Summoning an expert loads its apparatus into YOUR reasoning; it is not a cue to perform that apparatus at the user. Read which o