@ericrisco/rsc 2.0.19 → 2.1.0

package/skills/init/evals/cases.yaml

@@ -1,14 +1,14 @@
 skill: init
 
 # Cases for the rsc-skills "init" front door / bootstrapper.
-# init profiles the user (technical level + accompaniment dial), discovers what
+# init profiles the user (one question: technical terms or analogies), discovers what
 # they want to BUILD or GOVERN (code OR a non-code harness), recommends rsc
 # skills, and hands off to the harness skill. It is NOT the scaffolder and NOT
 # a specific stack skill.
 
 should_trigger:
   - prompt: "Quiero montar un proyecto nuevo pero no sé por dónde empezar."
-    why: "Canonical greenfield entry with explicit uncertainty ('no sé por dónde empezar') — init's job is to gauge level, discover, and recommend before anything is built."
+    why: "Canonical greenfield entry with explicit uncertainty ('no sé por dónde empezar') — init's job is to ask the register, discover, and recommend before anything is built."
 
   - prompt: "I have an existing repo and I want to set up the harness on it. Where do I start?"
     why: "Brownfield bootstrapping: pointing the rsc harness at an existing project is exactly init's front-door role (detect greenfield vs brownfield, profile, recommend skills)."
@@ -17,7 +17,7 @@ should_trigger:
     why: "First-contact phrasing without naming any tool — init is the literal first thing you run; it should claim 'what do I do first' onboarding moments."
 
   - prompt: "Tengo una idea para una app pero soy de negocio, no técnico. Ayúdame a arrancar esto desde cero."
-    why: "Greenfield + explicitly non-technical user — init leads with the technical-level question and the accompaniment dial, the core reason it exists, before any stack choice."
+    why: "Greenfield + explicitly non-technical user — init leads with the one register question (technical or analogies), the core reason it exists, before any stack choice."
 
   - prompt: "I want to use this to run my company's operations, not to write code. Can I bootstrap that here?"
     why: "Non-code harness (company/ops) bootstrap — init is domain-agnostic and explicitly governs non-code harnesses the same way; this is a deliberately non-obvious trigger."
@@ -38,7 +38,7 @@ should_not_trigger:
     why: "init explicitly hands off scaffolding to the harness skill. The moment the user asks to actually BUILD 01-TOOLS/02-DOCS, it is harness's job, not init's (init writes only the profile + link)."
 
   - prompt: "Set up a FastAPI backend with a Postgres database for my new service."
-    why: "User already knows the stack and wants a specific backend built — this is the fastapi/backend stack skill, not the level-gauging front door. init recommends skills; it does not implement stacks."
+    why: "User already knows the stack and wants a specific backend built — this is the fastapi/backend stack skill, not the profiling front door. init recommends skills; it does not implement stacks."
     route_to: "fastapi"
 
   - prompt: "Help me pick and configure a deploy target — Hetzner vs Vercel vs Fly.io — and ship it."
@@ -56,8 +56,8 @@ should_not_trigger:
 capability:
   - scenario: "A non-technical founder says: 'I want to build an app to connect dog owners but I don't know where to start.' Show how init opens the engagement."
     must_include:
-      - "Asks the technical-level question FIRST, before any discovery or recommendation (e.g. 'are you comfortable with code or prefer plain language?'), and records technical_level"
-      - "Presents the accompaniment dial L0–L3 and, given a silent non-technical user, defaults to L3 (full accompaniment)"
+      - "Asks ONE first-contact question FIRST, before any discovery or recommendation ('¿Te hablo en lenguaje técnico o con analogías?'), and records technical_level as technical or non-technical"
+      - "Asks no second calibration question (no accompaniment/verbosity level); given a silent or unclear answer, records non-technical and speaks with plain words and analogies"
       - "Persists the profile to 02-DOCS/wiki/harness/user-profile.md and an append-only 02-DOCS/wiki/harness/decisions.md, and links both from a ## Knowledge map section in root CLAUDE.md (creating CLAUDE.md if absent, additive only)"
       - "Detects greenfield vs brownfield rather than assuming, and runs DISCOVER (goals, audience, constraints, surfaces) before recommending"
       - "Recommends specific rsc skills matched to discovery (at minimum harness; nextjs/flutter + design if app surfaces justify it) and PRINTS the exact install commands (npx @ericrisco/rsc add <skill> ...)"
@@ -66,7 +66,7 @@ capability:
 
   - scenario: "A user with an existing multi-package repo says: 'Point the harness at my project and get me started.' Show the brownfield front-door flow."
     must_include:
-      - "Still asks the technical-level question and sets the accompaniment dial first — profile before anything, even on brownfield"
+      - "Still asks the one register question first — profile before anything, even on brownfield"
       - "Detects brownfield via manifests (package.json / pyproject.toml / pubspec.yaml / go.mod / Cargo.toml), source files, legacy XX-* folders, or existing 01-TOOLS/02-DOCS, with a read-only scan that ignores node_modules/.venv/.next/.git/dist/build"
       - "Summarizes the detected stack and current state and CONFIRMS with the user instead of assuming"
       - "Writes profile + decisions log under 02-DOCS/wiki/harness/ and adds the Knowledge-map link to CLAUDE.md without deleting existing content"

package/skills/init/references/accompaniment-and-profile.md

@@ -1,62 +1,45 @@
-# Accompaniment & Profile — the non-technical-first script, the dial, and how it persists
+# Register & Profile — the first-contact question and how it persists
 
-This file holds the runtime detail behind the SKILL.md section "Non-technical-first + the accompaniment dial". It defines: the first-contact script, the dial, the exact `02-DOCS` file formats, and the rules every downstream skill follows to adapt.
+This file holds the runtime detail behind the SKILL.md section "First contact". It defines: the first-contact question, the register it sets, the exact `02-DOCS` file formats, and the rule every downstream skill follows. (The filename is historical: the accompaniment dial it once described is retired.)
 
 ## Why this matters
 
-The single biggest failure mode of a developer-built harness is talking like a developer to someone who is not one. This system inverts the default: it assumes non-technical, asks before assuming otherwise, and lets the user turn explanation up or down at will. The profile is the contract; every skill honors it.
+The single biggest failure mode of a developer-built harness is talking like a developer to someone who is not one. This system inverts the default: it assumes analogies, asks once before assuming otherwise, and keeps one voice for everyone. The profile is the contract; every skill honors it.
 
-## The first-contact script
+## The first-contact question
 
-Ask exactly two things, in order, before anything else. Do not bundle them with discovery questions.
-
-### Question 1 — technical level (the literal first message)
+Ask exactly one thing before anything else. Do not bundle it with discovery questions.
 
 Spanish:
 
-> "Antes de nada, para hablarte como te resulte más cómodo: ¿te manejas con código y términos técnicos, o prefieres que te lo explique todo en cristiano? No hay respuesta mala — solo me ayuda a no aburrirte ni perderte."
+> "¿Te hablo en lenguaje técnico o con analogías?"
 
 English:
 
-> "First, so I talk to you the right way: are you comfortable with code and technical terms, or would you rather I explain everything in plain language? There's no wrong answer — it just helps me not bore you or lose you."
+> "Should I talk to you in technical terms or with analogies?"
 
 Map the answer to one of:
 
-- `non-technical` — plain language, analogies, no jargon, no code shown unless asked.
-- `mixed` — comfortable with concepts, not necessarily syntax; define terms once.
-- `technical` — full jargon OK, can read code and configs.
-
-If the user does not answer clearly, assume `non-technical`. Never guess "technical" from the fact that they opened a terminal — many non-technical people are handed one.
-
-### Question 2 — the accompaniment dial
-
-Present all four levels with their plain descriptions (do not show only labels):
+- `technical` — technical terms used directly; can read code and configs.
+- `non-technical` — plain words and everyday analogies; no undefined jargon; no code shown unless asked.
+- `mixed` — still valid in older profiles; treat it like `non-technical`.
 
-- **L0 — "Modo cavernícola"**: mínimas palabras. Hago las cosas y ya, casi sin explicar.
-- **L1 — "Breve"**: una línea de *por qué* en cada paso.
-- **L2 — "Explica decisiones"**: justifico cada decisión relevante a medida que avanzo.
-- **L3 — "Acompañamiento total"**: te lo explico TODO, te hago muchas preguntas para entender tu contexto, y razono cada decisión. Ideal para no-técnicos.
+`non-technical` and `mixed` (and no profile at all) also arm the danger guard, which blocks irreversible commands; `technical` never does. Say so when you record the answer.
 
-Defaults when the user gives no preference: `non-technical → L3`, `mixed → L2`, `technical → L1`. The user can change the dial any time by saying so ("ponlo en breve", "explícamelo todo"); update `user-profile.md` when they do.
+If the user does not answer clearly, record `non-technical`. Never guess "technical" from the fact that they opened a terminal — many non-technical people are handed one. The user can change it any time ("háblame técnico", "con analogías"); update `user-profile.md` when they do.
 
 ## How every skill adapts
 
-Both values combine. `accompaniment_level` controls **how much** is said and **how many questions** are asked; `technical_level` controls **the vocabulary**. A profile written by an older `onboard` may carry `accompaniment:` instead — it is the same dial; read it, and write `accompaniment_level` the next time you touch the profile.
+There is no per-user depth setting. Every skill speaks in the one voice the `orient` skill owns (`skills/orient/references/orientation-contract.md`): short sentences, one idea per sentence, simple words, active voice, the instruction before the reason, and every answer understandable on its own. `technical_level` only picks the register:
 
-| Level | Output verbosity | Questions before acting | On a decision |
-| --- | --- | --- | --- |
-| L0 | Result line only | None beyond hard blockers | Pick the recommended option, log it, mention it in one line |
-| L1 | One *why* line per step | Only on genuine ambiguity | Present the 3 options tersely, recommend, proceed on confirm |
-| L2 | Justify each relevant decision | Ask before each significant decision | Full 3-option pattern with trade-offs |
-| L3 | Narrate reasoning throughout | Many — contextualize every choice | Full 3-option pattern + explain each option in plain language and check understanding |
+- `technical` — use the term directly; skip the 101 explanations.
+- `non-technical` / `mixed` — translate every term ("a database is where the app remembers things"), prefer analogies, never paste raw config without explaining it.
 
-Vocabulary modifier:
+If the person still does not understand, `orient` climbs its explanation ladder (text → diagram → one HTML page → a video, only offered).
 
-- `non-technical` — translate every term ("a database is where the app remembers things"), prefer analogies, never paste raw config without explaining it.
-- `mixed` — use the term, define it inline the first time.
-- `technical` — use the term directly; skip the 101 explanations even at L3.
+**Legacy keys.** A profile written by an older `init` or `onboard` may carry `accompaniment_level:` or the even older `accompaniment:`. Both are retired: ignore their value, and drop the line the next time you touch the profile.
 
-**Rule:** read `user-profile.md` at the start of every session. If it is missing, you are likely being run before `init` — run the first-contact script before doing the requested work, or at minimum default to `non-technical` + `L3` and note that the profile is unset.
+**Rule:** read `user-profile.md` at the start of every session. If it is missing, you are likely being run before `init` — ask the first-contact question before doing the requested work, or at minimum speak with analogies and note that the profile is unset.
 
 ## Persistence format
 
@@ -64,16 +47,15 @@ Both files live under `02-DOCS/wiki/harness/`. `init` creates this directory eve
 
 ### `02-DOCS/wiki/harness/user-profile.md`
 
-A living document — updated whenever the user reveals new goals, context, constraints, or changes the dial. It is the single source of truth other skills read.
+A living document — updated whenever the user reveals new goals, context, constraints, or changes the register. It is the single source of truth other skills read.
 
 ```markdown
 # User Profile
 
 > Source of truth for how every rsc skill talks to this user. Updated continuously.
 
-## Levels
-- technical_level: non-technical            <!-- non-technical | mixed | technical -->
-- accompaniment_level: L3                    <!-- L0 | L1 | L2 | L3 -->
+## Register
+- technical_level: non-technical            <!-- technical | non-technical (mixed: legacy, reads as non-technical) -->
 - language: es                               <!-- the user's working language -->
 - last_updated: 2026-06-01
 
@@ -133,7 +115,7 @@ Add (or update) a `## Knowledge map` section that links BOTH files. Create `CLAU
 ```markdown
 ## Knowledge map
 
-- [User profile](02-DOCS/wiki/harness/user-profile.md) — technical level, accompaniment dial, goals, context, constraints. **Every skill reads this first and adapts its verbosity and questions.**
+- [User profile](02-DOCS/wiki/harness/user-profile.md) — register (technical or analogies), goals, context, constraints. **Every skill reads this first and speaks in that register.**
 - [Decisions log](02-DOCS/wiki/harness/decisions.md) — append-only record of every significant decision and why.
 ```
 

package/skills/init/references/discovery.md

@@ -1,6 +1,6 @@
 # Discovery — greenfield & brownfield questionnaires (software AND non-code harnesses)
 
-Phase 2 detail. Establish two things: **the state of the ground** (greenfield vs brownfield) and **what the user wants to build or govern**. Record everything to `02-DOCS/wiki/harness/user-profile.md` as you learn it. Ask in batches sized to `accompaniment_level` — never dump every question at once.
+Phase 2 detail. Establish two things: **the state of the ground** (greenfield vs brownfield) and **what the user wants to build or govern**. Record everything to `02-DOCS/wiki/harness/user-profile.md` as you learn it. Ask in short batches — never dump every question at once.
 
 ## First: greenfield vs brownfield (detect, then confirm)
 
@@ -31,7 +31,7 @@ Record `domain: software | non-code-harness`. Both are first-class. A non-code h
 
 ### Greenfield software
 
-Ask in batches. Adapt depth to the dial.
+Ask in short batches, only what changes the plan.
 
 1. **The idea in one sentence.** What does it do, for whom?
 2. **Surfaces.** Which of these does it need? (This drives the skill recommendation.)

package/skills/init/references/recommend-skills.md

@@ -7,7 +7,7 @@ and prints commands the user runs.
 
 ## The skill map
 
-| Discovery signal | Skills | One-line *why* (adapt to level) |
+| Discovery signal | Skills | One-line *why* (in the user's register) |
 | --- | --- | --- |
 | Always (every project) | `harness` | The control plane — scaffolds and governs the whole workspace (`suggest` installs with it as the floor). |
 | Backend / API / database | `fastapi` or `go`, `postgresdb` | The server, the API, the database that remembers things. |
@@ -28,7 +28,7 @@ usually does NOT want `fastapi`/`nextjs` unless they're also building software.
 ## What to print
 
 One `npx @ericrisco/rsc add` line per recommendation (or batch them on one line), each with
-its *why* in the user's language and level.
+its *why* in the user's language and register.
 
 ```text
 npx @ericrisco/rsc add <skill> [<skill> ...]
@@ -81,7 +81,7 @@ For any significant decision — deploy target, database, framework, hosting, wh
 
 ### 1. Gather the driving requirements first
 
-Ask the questions that actually change the answer. Match question count/depth to `accompaniment_level` (L0: only hard blockers; L3: ask all, explaining why each matters). Checklists per decision type:
+Ask only the questions that actually change the answer, in one short batch. Checklists per decision type:
 
 - **Deploy target:** expected number of users; concurrent users; budget; data region / residency rules; the team's comfort operating servers; scaling needs (steady vs spiky); existing org/cloud constraints.
 - **Database:** data shape (relational vs documents vs key-value); expected size and growth; query patterns; consistency vs scale needs; managed vs self-hosted preference; budget.
@@ -92,9 +92,9 @@ Ask the questions that actually change the answer. Match question count/depth to
 
 Three, with honest trade-offs — what each is good at, what it costs, what it demands. Not two (false binary), not ten (paralysis). If a fourth is genuinely worth knowing, mention it in one line under the third — but the choice is between three.
 
-### 3. Recommend one, matched to their answers AND their level
+### 3. Recommend one, matched to their answers
 
-State your recommendation and why, in language they understand. At L3 / non-technical, explain each option in plain terms and check they followed before they pick.
+State your recommendation and why, in their register. For a `non-technical` user, explain each option with an everyday analogy and check they followed before they pick.
 
 ### 4. Log the decision
 

package/skills/init/scripts/verify.sh

@@ -4,8 +4,9 @@
 #
 # WHAT IT DOES (read-only; never edits or creates a file)
 #   Static checks that Phase 1 (PROFILE) actually landed in the workspace:
-#     1. 02-DOCS/wiki/harness/user-profile.md exists and carries technical_level
-#        and accompaniment_level lines.
+#     1. 02-DOCS/wiki/harness/user-profile.md exists and carries a technical_level
+#        line — the one dial (technical, or with analogies). The accompaniment dial
+#        is retired: an old profile that still carries it is not flagged.
 #     2. 02-DOCS/wiki/harness/decisions.md exists (append-only decisions log).
 #     3. Root CLAUDE.md exists and its "## Knowledge map" section links the profile.
 #   Everything is detect-or-skip: a missing workspace piece is a WARNING, never a
@@ -79,11 +80,6 @@ else
   else
     warn "profile is missing a technical_level line"
   fi
-  if has "$PROFILE" 'accompaniment_level'; then
-    ok "profile records accompaniment_level"
-  else
-    warn "profile is missing an accompaniment_level line"
-  fi
 fi
 
 # --- 2. decisions log -------------------------------------------------------

package/skills/knowledge-ops/SKILL.md

@@ -13,7 +13,7 @@ origin: risco
 ## Before you touch anything
 
 1. **Confirm `02-DOCS/wiki/` exists.** If there is no wiki, stop and say: "Run `harness` to build the `02-DOCS/` wiki first, then come back to garden it." Why: this skill operates an existing engine; it never creates one. See `../harness/SKILL.md`.
-2. **Read `wiki/harness/user-profile.md`** to set your verbosity (the harness accompaniment dial, L0–L3). Why: a non-technical owner wants decisions narrated; an expert wants terse diffs.
+2. **Read `wiki/harness/user-profile.md`** for `technical_level`, which sets your register (technical terms, or plain words with analogies). Why: a non-technical owner needs each decision explained with an analogy; a technical one reads the term directly. Either way, speak in the `orient` voice: short, and every answer understandable on its own.
 3. **Read `wiki/index.md` and `wiki/scores.json` before any edit.** Why: you garden from the map and the score signal, never blind. `scores.json` tells you what is bloated, orphaned, or stale.
 
 If `wiki/log.md` shows a Maintenance Pass ran in the last few minutes, let it finish — do not race the automation.

package/skills/orient/SKILL.md

@@ -1,65 +1,76 @@
 ---
 name: orient
-description: "Always-on. The brújula: close every turn by situating the person — where they are, what just happened, why it mattered, and the next step as a question, never a dead end. Reads the accompaniment and technical dials from 02-DOCS and calibrates how much it explains, rewriting the dial when the user asks for more or less. NOT the missing-skill installer (that is `suggest`)."
-tags: [orient, guide, compass, dial, meta, always-on]
+description: "Always-on. How the harness talks to the person: STE-style short sentences, every answer understandable on its own, technical or with analogies by the profile, and a ladder (text → diagram → HTML page → video on request) when the person does not follow. Closes every turn with the brújula. Fires on 'no entiendo', 'explícamelo', 'enséñame', 'dibújamelo', 'explain it from zero', '¿dónde estamos?'. NOT the missing-skill installer (that is `suggest`), NOT a text the user sends to others (that is `unslop`)."
+tags: [orient, voice, ste, explain, diagram, eli5, show-me, compass, always-on]
 recommends: []
 profiles: [minimal, core, full]
 origin: risco
 ---
 
-# orient — the brújula that never leaves the user lost
+# orient — talk so the person understands, then show them where they are
 
-You are always loaded. Your one job: **after anything happens, keep the human oriented.** A tool
-executes and falls silent; a mentor walks alongside. You are what makes the harness a mentor.
+You own how the harness speaks to the person. Three rules, a register, a ladder, and the brújula.
 
-`suggest` keeps the *session* equipped ("you're missing a skill, install it?"). You keep the *person*
-equipped ("you are here, you did this, for this reason, next is X — which?"). The install prompt is
-its job, never yours.
+## The three rules
 
-## The one rule
+1. **Speak STE.** STE is the controlled writing style of aircraft manuals (ASD-STE100). Short
+   sentences. One idea per sentence. Simple words. Active voice. The instruction before the reason.
+2. **Every answer stands alone.** The reader has not seen your reasoning, and may not remember earlier
+   messages. Never point at something they did not see ("the second commit", "that fix", "as above").
+   Name it, in one sentence.
+3. **Short.** Say what the reader needs, then stop. No walls of paragraphs. Rules 2 and 3 meet in one
+   place: give the **minimum** context, never the whole story.
 
-**No turn ends in seco.** Any turn that finishes an action, reaches a fork, or could leave the user
-unsure closes with the brújula block. One block, at the end — never interrupt mid-work to orient.
+Full rules and examples → `references/orientation-contract.md`.
 
-## The brújula block
+## The register
 
-Four intents. The wording adapts to the person; the intents do not.
+Read `technical_level` in `02-DOCS/wiki/harness/user-profile.md`.
 
-```text
-📍 Dónde estás — the project phase/state (the map)
-✅ Qué acabas de hacer — one line, in the user's language
-🧭 Por qué — the technical why, scaled to the dial
-➡️ Siguiente — 1-3 concrete options, ending in a question
-```
+| technical_level | Register |
+|---|---|
+| `technical` | Technical terms, used directly. No 101s. |
+| `non-technical`, `mixed` | Plain words. One everyday analogy for each new idea. |
+| no profile | Analogies. Ask once: "¿Te hablo en lenguaje técnico o con analogías?" and save the answer. |
+
+The person can change it by saying so ("háblame más técnico", "con analogías"). Update
+`technical_level` (`technical` or `non-technical`), confirm in one line, apply it from this turn.
+Old profiles may carry `accompaniment_level:` or `accompaniment:` (the retired L0–L3 dial): ignore both.
 
-Situate them from what is **actually** built. If you are unsure of the project state, read the
-Knowledge map or the repo before writing 📍 — an invented state is worse than a shorter block.
+## The ladder — when the person does not follow
 
-## Calibrate to the dial
+Climb **one** step per sign. Signs: they repeat the question, say "no entiendo" / "¿qué?" /
+"explícamelo", answer short and annoyed, or ask about a term you just used. Weak signs are not signs:
+guessing their mood reads as condescending.
 
-Read `02-DOCS/wiki/harness/user-profile.md` before writing the block. Two fields combine:
-`accompaniment_level` sets the depth, `technical_level` sets the vocabulary. A profile written by an older `onboard` may carry `accompaniment:` instead — it is the same dial; read it, and write `accompaniment_level` the next time you touch the profile.
+| Step | What | Detail |
+|---|---|---|
+| 1 | Text, in the three rules | always |
+| 2 | One diagram in the chat | the smallest form that carries the point |
+| 3 | One self-contained HTML page | big pictures, few words; open it |
+| 4 | Animated video | only offered, never made unasked |
 
-| accompaniment_level | How the block behaves |
-|---------------------|-----------------------|
-| L0 — cavernícola | Only `✅` + `➡️`. One next option, a yes/no question. |
-| L1 — breve | The four lines; `🧭` is one line of why. |
-| L2 — explica decisiones | The four lines; `🧭` justifies the relevant decision; offer real forks. |
-| L3 — acompañamiento total | The four lines, full why, each option explained in plain language. |
+The person can also ask for any step directly ("dibújamelo", "hazme una página", "explícamelo desde
+cero"). Forms, the from-zero page and the video step → `references/explain-ladder.md`.
 
-`technical_level` is orthogonal: a non-technical user gets plain language and analogies even at L0;
-a technical user skips the 101 explanations even at L3. No profile yet → assume non-technical + L3
-(the non-technical-first default) and offer to set the dial.
+## The brújula — close every turn
 
-The dial is spoken, not configured: when the user says "explícame más / menos", "no me expliques
-tanto" or "enséñame", update `accompaniment_level` in the profile, confirm in one line, and apply
-the new depth from this turn on.
+No turn ends in seco. One block, at the end, never mid-work.
+
+```text
+📍 Dónde estás — the state, in one sentence that stands alone
+✅ Qué has hecho — only when something was done
+🧭 Por qué — only when a decision was made; one sentence
+➡️ Siguiente — 1-3 concrete options, ending in a question
+```
 
-At a real fork, ask. Deciding alone is faster and wrong — the fork is the moment the person's
+📍 and ➡️ always. ✅ and 🧭 only when they carry something. Situate from what is **actually** built;
+an invented state is worse than a shorter block. At a real fork, ask: the fork is where the person's
 judgment is worth more than yours.
 
-## See Also
+## Where this ends
 
-- `references/orientation-contract.md` — the full brújula contract: block anatomy, what each of the
-  four beats must contain, and how the dial changes their depth. Read it when a turn ends ambiguously
-  or when calibrating a new dial level.
+- "Install the missing skill?" belongs to `suggest`.
+- A text the person sends to others (email, post, README) belongs to `unslop`.
+- Visual identity is `design`; a deck someone presents from is `presentations`; a course with
+  exercises is `course-builder`.

package/skills/orient/evals/README.md

@@ -1,16 +1,18 @@
 # Evals — orient
 
-The always-on brújula. These cases check that it keeps the user oriented at the end of a
-turn (map + what happened + why-at-level + next step as a question) and that it defers
-install prompts to `suggest` and never interrupts trivial mid-flow edits.
+How the harness talks to the person. These cases check the voice (STE-style, short, every answer
+stands alone), the register from `technical_level`, the explain ladder (text → diagram → HTML →
+video on request), and the brújula at the end of a turn. Install prompts stay with `suggest`; text
+for others stays with `unslop`.
 
 | Prompt | Expected |
 |---|---|
-| "ya está instalado, ¿y ahora qué?" | situate + next step as a question |
-| "no sé por dónde seguir" | render the map + 1-3 next options |
-| "explícame menos" | lower the dial, confirm, apply reduced depth |
+| "ya está instalado, ¿y ahora qué?" | short stand-alone state + next step as a question |
+| "no entiendo nada" | one step up the ladder: a small diagram |
+| "explícame Docker desde cero" | from-zero explanation with analogies |
+| "háblame más técnico" | set technical_level, confirm, apply |
 | "renombra esta variable" | no full brújula block (trivial mid-flow) |
-| "necesito una base de datos" | defer to `suggest` (no duplicate install prompt) |
+| "haz que este correo suene humano" | defer to `unslop` |
 
-A pass = orient closes the turn without leaving the user in seco, scales the why to the
-dial, and never duplicates `suggest`'s install prompt.
+A pass = short sentences, nothing that needs earlier context, the right register, one ladder step
+per sign, and no turn ending in seco.

package/skills/orient/evals/cases.yaml

@@ -1,57 +1,67 @@
 skill: orient
 
-# The always-on brújula. It fires at the END of a turn to keep the user oriented:
-# map + what happened + why (scaled to the dial) + a next step phrased as a question.
-# It defers "install a missing skill?" to suggest and does not interrupt mid-work.
+# How the harness talks to the person: STE-style short sentences, every answer stands alone,
+# register (technical or with analogies) from technical_level, a ladder (text → diagram → HTML →
+# video on request) when the person does not follow, and the brújula at the end of a turn.
+# It defers "install a missing skill?" to suggest and text for others to unslop.
 
 should_trigger:
   - prompt: "Ya está instalado el postgresdb. ¿Y ahora qué?"
-    why: "An action just finished and the user is explicitly unsure what to do next — orient must situate them and propose the next step."
-
-  - prompt: "Vale, hemos creado la landing. ¿Qué hago con esto?"
-    why: "A step finished and the user asks for direction — orient closes with the map + next options as a question."
+    why: "An action just finished and the user is unsure what to do next — orient situates them and proposes the next step."
 
   - prompt: "No sé por dónde seguir con mi proyecto."
     why: "The user is lost — the core trigger: situate on the map and propose 1-3 next steps."
 
-  - prompt: "Explícame menos, que me agobio con tanto detalle."
-    why: "A spoken dial request — orient lowers accompaniment_level, confirms it, and applies the new depth."
+  - prompt: "No entiendo nada de lo que me has dicho."
+    why: "A clear sign the person does not follow — orient climbs one step of the ladder (a diagram)."
 
-  - prompt: "¿En qué punto del proyecto vamos?"
-    why: "A 'where am I?' question — orient renders the map (what's built, what's missing, what phase)."
+  - prompt: "Dibújame cómo funciona el flujo de login."
+    why: "A direct request for step 2 of the ladder — the smallest diagram that carries the point."
 
-  - prompt: "Acabo de terminar el spec. Listo."
-    why: "A turn ends after finishing work — orient must not end in seco; it proposes the next phase as a question."
+  - prompt: "Explícame qué es Docker desde cero, que no sé nada."
+    why: "Zero background — a from-zero explanation with everyday analogies (the old eli5 job, now step 3 of the ladder)."
+
+  - prompt: "Háblame más técnico, que esto ya lo controlo."
+    why: "A spoken register change — orient sets technical_level to technical, confirms in one line, applies it."
+
+  - prompt: "¿En qué punto del proyecto vamos?"
+    why: "A 'where am I?' question — orient renders the state in sentences that stand alone."
 
 should_not_trigger:
   - prompt: "Renombra esta variable a `userCount`."
     route_to: "none"
-    why: "A trivial mechanical edit mid-flow — orient does not interrupt with a full brújula block over a one-line change."
+    why: "A trivial mechanical edit mid-flow — no full brújula block over a one-line change."
 
   - prompt: "Necesito una base de datos para guardar pedidos."
     route_to: "suggest"
-    why: "This is an install gap — suggest owns it. orient must not duplicate the 'install it?' prompt."
+    why: "An install gap — suggest owns it. orient must not duplicate the 'install it?' prompt."
 
-  - prompt: "Optimiza esta query de Postgres que va lenta."
-    route_to: "postgresdb"
-    why: "A concrete task owned by another skill; orient adds the closing block but does not drive the work."
+  - prompt: "Haz que este correo al cliente suene más humano."
+    route_to: "unslop"
+    why: "A text the user sends to others — unslop owns the human-register rewrite."
 
   - prompt: "Arregla el test que falla."
     route_to: "debug"
-    why: "Root-cause work owned by debug; orient does not take over the task itself."
+    why: "Root-cause work owned by debug; orient only closes the turn."
 
 capability:
-  - scenario: "The user just ran `npx @ericrisco/rsc add postgresdb` and says 'ya está, ¿y ahora qué?'. The profile shows accompaniment_level L0. Show how orient closes the turn."
+  - scenario: "The user just ran `npx @ericrisco/rsc add postgresdb` and says 'ya está, ¿y ahora qué?'. The profile shows technical_level non-technical. Show how orient closes the turn."
     must_include:
-      - "Situates the user on the map ('📍 dónde estás' / what is built vs missing)"
-      - "States what just happened in one plain-language line ('✅ instalaste la base de datos')"
-      - "Proposes a concrete next step ending in a question, never leaving the turn in seco"
-      - "At L0, keeps it to ✅ + ➡️ with a single yes/no option and zero jargon"
+      - "Short sentences, one idea each; no paragraph walls"
+      - "Every line understandable without earlier messages (names the database, does not say 'eso' or 'lo de antes')"
+      - "Plain words with an everyday analogy for any new idea (non-technical register)"
+      - "Closes with 📍 and ➡️, the next step ending in a question"
       - "Does NOT re-prompt to install a skill (defers that to suggest)"
 
-  - scenario: "Mid-project, the user says 'explícame menos'. The profile shows accompaniment_level L2. Show how orient responds."
+  - scenario: "Orient explained a caching bug in text. The user replies: '¿qué? no entiendo'. The profile shows technical_level technical. Show the next answer."
+    must_include:
+      - "Climbs exactly one step: a single small diagram (pseudocode, call tree or flow), not an HTML page or a video"
+      - "Uses real names from the code, not placeholders"
+      - "Keeps the technical register (no 101s)"
+      - "At most two lines of prose beside the diagram"
+
+  - scenario: "The profile carries `technical_level: mixed` and an old `accompaniment_level: L0`. The user asks what a migration is. Show how orient answers."
     must_include:
-      - "Updates accompaniment_level in 02-DOCS/wiki/harness/user-profile.md to a lower level"
-      - "Confirms the change in one line"
-      - "Re-renders guidance at the reduced depth from this turn on"
-      - "Still closes with a next-step question (no seco)"
+      - "Ignores accompaniment_level (retired)"
+      - "Uses the analogies register (mixed → analogies)"
+      - "Short, stand-alone answer that ends with the brújula"