@ericrisco/rsc 2.0.19 → 2.1.0

package/skills/code-review/SKILL.md

@@ -103,7 +103,7 @@ End every review with exactly one, plainly — no mushy middle:
 
 ## Effort dial
 
-Mirror the slash command's effort level: **low/medium** → fewer, high-confidence findings (raise the confidence floor, focus on passes 1–4). **high/max** → broader coverage; uncertain findings are allowed but must be labelled `[question]`, never inflated into blockers. This is *coverage vs precision*, not the harness accompaniment dial — it changes what you look at, not how much you narrate.
+Mirror the slash command's effort level: **low/medium** → fewer, high-confidence findings (raise the confidence floor, focus on passes 1–4). **high/max** → broader coverage; uncertain findings are allowed but must be labelled `[question]`, never inflated into blockers. This is *coverage vs precision*, not the user's register — it changes what you look at, not how you word it.
 
 ## Emitting comments and applying fixes
 

package/skills/constitution/SKILL.md

@@ -17,18 +17,15 @@ Not this phase: *what to build* → `../specify/SKILL.md`; the technical approac
 
 ## Model tier — `heavy` (opt-in routing)
 
-This phase's default model tier is **`heavy`** — it sets the project's non-negotiables, the highest-leverage decisions in the repo. Routing is **off** unless `models.enabled: true` in `02-DOCS/wiki/sdd/config.yaml`. When on: resolve this phase's tier (`models.overrides` wins over `models.phases`), map it to a model via `models.tiers`, and apply per `../sdd/references/model-routing.md` — announce the switch per the accompaniment dial when it differs from the session model, and dispatch any `Task`/`parallel` subagents on that model. Routing off or no profile → honor the session model silently. Never fake a switch a tool can't make; skip routing on a one-line change.
+This phase's default model tier is **`heavy`** — it sets the project's non-negotiables, the highest-leverage decisions in the repo. Routing is **off** unless `models.enabled: true` in `02-DOCS/wiki/sdd/config.yaml`. When on: resolve this phase's tier (`models.overrides` wins over `models.phases`), map it to a model via `models.tiers`, and apply per `../sdd/references/model-routing.md` — announce the switch in one line when it differs from the session model, and dispatch any `Task`/`parallel` subagents on that model. Routing off or no profile → honor the session model silently. Never fake a switch a tool can't make; skip routing on a one-line change.
 
-## Honor the accompaniment dial first
+## Honor the register first
 
-Before asking anything, read `02-DOCS/wiki/harness/user-profile.md` and match its `technical_level` and `accompaniment_level`. No profile yet → default to non-technical and ask the two gauging questions, or point the user at `init`; never assume fluency. The constitution interview adapts:
+Before asking anything, read `02-DOCS/wiki/harness/user-profile.md` and use its `technical_level`: technical terms, or plain words with analogies. No profile yet → use analogies and ask once "technical or with analogies?", or point the user at `init`; never assume fluency. The interview is the same for every reader:
 
-| Level | How this skill behaves |
-|-------|------------------------|
-| L0 — cavernícola | Infer almost everything from the codebase and stack wiki. Ask only the 1-2 questions that genuinely change a principle. Draft, show, ratify. |
-| L1 — breve | One line of *why* per principle proposed. Ask 3-4 questions max. |
-| L2 — explica decisiones | Justify each principle as you propose it; surface trade-offs where a rule constrains the team. |
-| L3 — acompañamiento total | Explain what a constitution is and why each section matters, one kind question at a time, before writing anything. Non-technical framing. |
+- Infer almost everything from the codebase and stack wiki. Ask only the few questions that genuinely change a principle.
+- Give one line of *why* per principle proposed, and the trade-off where a rule constrains the team — in the `orient` voice.
+- For a `non-technical` reader, say in one sentence what a constitution is (the house rules every later step obeys) before drafting.
 
 ## Reconcile before you write (do not duplicate the stack wiki)
 
@@ -58,7 +55,7 @@ Strong — "4. No secret is ever committed; secrets load from 01-TOOLS/<provider
 
 ## The interview (requirements-first, batched)
 
-Gather what you cannot infer, then draft. Ask in batches sized to the accompaniment level (L0: the 1-2 that matter; L3: one at a time, explained). Cover these dimensions — skip any the stack wiki already answers, and confirm rather than re-ask:
+Gather what you cannot infer, then draft. Ask in one short batch — only the questions that matter. Cover these dimensions — skip any the stack wiki already answers, and confirm rather than re-ask:
 
 1. **Stack canon** — languages, frameworks, runtime/versions, package manager. What is fixed vs. open?
 2. **Quality bar** — formatter/linter (must pass clean?), type checking (strict?), test discipline (TDD? coverage floor? what kind of tests gate a merge?).
@@ -95,7 +92,7 @@ The constitution is versioned so `analyze` and `review` can cite "constitution v
 
 - **Semantic-ish versioning.** MAJOR when a principle is removed or reversed (breaks existing work); MINOR when a principle is added or materially tightened; PATCH for wording/clarity with no behavior change.
 - **Amendments are append-only in the log.** Never silently edit a ratified principle — strike it (mark superseded) and add the new one, bump the version, and record date + why in the amendment log.
-- **Ratification.** A new or amended constitution is shown to the user and ratified explicitly before it takes effect. At L0, "ratify" is a quick yes; at L3, walk each change.
+- **Ratification.** A new or amended constitution is shown to the user and ratified explicitly before it takes effect. "Ratify" is an explicit yes on the shown draft; walk each change only if the user asks.
 - **Downstream notice.** When a principle changes mid-project, flag that existing specs/plans may now be inconsistent — `analyze` will catch the drift on the next run.
 
 ## Anti-patterns
@@ -107,13 +104,13 @@ The constitution is versioned so `analyze` and `review` can cite "constitution v
 | "Two stack articles disagree — I'll just pick the stricter one." | Contradictions are findings. Surface them; the user resolves. |
 | "The principle is 'write good code' — everyone knows what that means." | Not checkable, not a principle. Make it testable or drop it. |
 | "I'll rewrite the existing constitution to match what they said today." | Amend, don't overwrite. Strike + add + bump version + log the why. |
-| "No profile yet, I'll assume they're technical and skip the dial." | Default non-technical; ask the two gauging questions or send them to `init`. |
+| "No profile yet, I'll assume they're technical." | Use analogies; ask once "technical or with analogies?" or send them to `init`. |
 | "I'll add a Co-Authored-By so the commit credits the assist." | No. Git authorship is the human's — it's a fixed principle, enforced at `ship`. |
 | "I'll ratify it myself since it's obvious." | The user ratifies. Show the draft, get the explicit yes, then it takes effect. |
 
 ## Checklist before handing off
 
-- [ ] `02-DOCS/wiki/harness/user-profile.md` read; verbosity matched to the dial (or gauging questions asked).
+- [ ] `02-DOCS/wiki/harness/user-profile.md` read; register matched to `technical_level` (or the register question asked).
 - [ ] Reconciliation pass done against every `02-DOCS/wiki/stack/*` article; contradictions surfaced, not auto-resolved.
 - [ ] Every principle is numbered, imperative, testable, and links its enforcer where one exists.
 - [ ] The Definition-of-Done checklist is present (what `verify` runs against).

package/skills/constitution/evals/cases.yaml

@@ -41,7 +41,7 @@ should_not_trigger:
 
   - prompt: "I'm starting from scratch and don't know where to begin — help me bootstrap the project."
     route_to: "init"
-    why: "Front-door bootstrapping (gauge the user, set the accompaniment dial, recommend bundles) is init; the constitution runs after the harness exists and the profile is set."
+    why: "Front-door bootstrapping (ask the register question, write the profile, recommend bundles) is init; the constitution runs after the harness exists and the profile is set."
 
   - prompt: "Show me how to actually configure Ruff and pytest with an 80% coverage gate in our FastAPI service."
     route_to: "fastapi"
@@ -61,9 +61,9 @@ should_not_trigger:
 # the file, and ratifies with the user — an ungrounded answer writes a vague,
 # unversioned wall of aspirations.
 capability:
-  - scenario: "Stand up the constitution for a new project that has a Next.js frontend and a FastAPI backend. The harness already wrote 02-DOCS/wiki/stack/nextjs.md and fastapi.md with some conventions. There is a user-profile at L1 (brief)."
+  - scenario: "Stand up the constitution for a new project that has a Next.js frontend and a FastAPI backend. The harness already wrote 02-DOCS/wiki/stack/nextjs.md and fastapi.md with some conventions. There is a user-profile with technical_level: technical."
     must_include:
-      - "Reads 02-DOCS/wiki/harness/user-profile.md and matches L1 verbosity (one line of why per principle, few questions) rather than a long interview."
+      - "Reads 02-DOCS/wiki/harness/user-profile.md and speaks in technical terms, briefly (one line of why per principle, few questions) rather than a long interview."
       - "Runs the reconciliation pass: reads the existing wiki/stack/nextjs.md and fastapi.md, lifts only project-wide non-negotiables, and LINKS those articles instead of pasting their config; surfaces any contradiction for the user to resolve rather than auto-picking."
       - "Every principle is numbered, imperative, and testable (a number, command, or named artifact), not an aspiration like 'write clean code'."
       - "Includes the two fixed principles: git authorship is the human's (no Co-Authored-By AI / generated-with footer, enforced at ship) and significant decisions are logged."

package/skills/continuous-learning/SKILL.md

@@ -12,7 +12,7 @@ This is the engine that makes the system get better every time it is wrong. When
 
 One premise is load-bearing: **a lesson that lives only in chat is gone at the next compaction.** Verbal reflection only changes future behaviour when it is persisted to memory the agent actually reads next time (this is the Reflexion mechanism — self-reflection written to durable memory, not held in the conversation). In this harness, "memory" is a concrete set of surfaces: a `SKILL.md` body, `02-DOCS/wiki/harness/decisions.md`, `02-DOCS/wiki/harness/user-profile.md`, a root `CLAUDE.md` rule, or a `verify.sh` check. **Chat is not memory.** A lesson is "captured" only when it has landed in one of those.
 
-Read `02-DOCS/wiki/harness/user-profile.md` for the accompaniment dial before you narrate. It governs narration only — the capture loop runs identically at every level.
+Read `technical_level` in `02-DOCS/wiki/harness/user-profile.md` before you narrate, and speak in the `orient` voice in that register. It governs the words only — the capture loop runs identically for every reader.
 
 ## Boundaries
 

package/skills/continuous-learning/evals/cases.yaml

@@ -29,7 +29,7 @@ should_not_trigger:
 capability:
   - scenario: "A user says: 'You've now twice deleted my .env when scaffolding a tool. I'm tired of catching it. Make sure this never happens again.' Show how continuous-learning captures it."
     must_include:
-      - "Reads 02-DOCS/wiki/harness/user-profile.md for the accompaniment dial and adapts narration to L0–L3."
+      - "Reads technical_level from 02-DOCS/wiki/harness/user-profile.md and narrates briefly in that register (technical terms or analogies)."
       - "States the root cause blamelessly as a system gap (a missing guardrail), not 'I was careless'."
       - "Applies the 2+-recurrences rule: this is the 2nd time, so a structural fix is required — not another apology or note."
       - "Routes to the right durable home via the table: a root CLAUDE.md rule and/or a verify.sh check on the scaffolding skill, naming the exact path."

package/skills/debug/SKILL.md

@@ -26,21 +26,17 @@ delegation table below.
 
 ## Model tier — `heavy` (opt-in routing)
 
-This phase's default model tier is **`heavy`** — root-cause diagnosis is deep reasoning. Routing is **off** unless `models.enabled: true` in `02-DOCS/wiki/sdd/config.yaml`. When on: resolve this phase's tier (`models.overrides` wins over `models.phases`), map it to a model via `models.tiers`, and apply per `../sdd/references/model-routing.md` — announce the switch per the accompaniment dial when it differs from the session model, and dispatch any `Task`/`parallel` subagents on that model. Routing off or no profile → honor the session model silently. Never fake a switch a tool can't make; skip routing on a one-line change.
+This phase's default model tier is **`heavy`** — root-cause diagnosis is deep reasoning. Routing is **off** unless `models.enabled: true` in `02-DOCS/wiki/sdd/config.yaml`. When on: resolve this phase's tier (`models.overrides` wins over `models.phases`), map it to a model via `models.tiers`, and apply per `../sdd/references/model-routing.md` — announce the switch in one line when it differs from the session model, and dispatch any `Task`/`parallel` subagents on that model. Routing off or no profile → honor the session model silently. Never fake a switch a tool can't make; skip routing on a one-line change.
 
-## Read the room first (accompaniment dial)
+## Read the room first (register)
 
-Before diagnosing, read `02-DOCS/wiki/harness/user-profile.md` for the technical + accompaniment
-level and match it; with no profile yet, assume non-technical — narrate the reasoning plainly and
-never apply a behavior-changing fix without a quick confirm. The *method* never changes with the
-dial — the volume does.
+Before diagnosing, read `technical_level` in `02-DOCS/wiki/harness/user-profile.md`; it picks
+technical terms or plain words with analogies. With no profile yet, use analogies. The *method*
+never changes with the register — only the words do.
 
-| Level | While diagnosing you show… | Questions you ask |
-| --- | --- | --- |
-| **L0** terse | the confirmed cause and the one-line fix, once found | none unless you need a missing repro detail |
-| **L1** brief | the cause + one line of *why* it produced this symptom | only what you can't observe yourself (e.g. exact error text) |
-| **L2** decisions | each step's finding (repro, the half that isolated it, the cause) | confirm before a fix that changes behavior beyond the bug |
-| **L3** full | narrate the whole loop, teach the binary-search reasoning aloud | ask to contextualize the environment, recent changes, expectations |
+In the `orient` voice, show: the confirmed cause, one line of *why* it produced this symptom, and
+the fix. Ask only what you can't observe yourself (e.g. exact error text). Confirm before a fix that
+changes behavior beyond the bug.
 
 ## The loop — five steps, never skipped, never reordered
 

package/skills/debug/evals/cases.yaml

@@ -62,7 +62,7 @@ should_not_trigger:
 capability:
   - scenario: "Mid-implement, a FastAPI integration test for the orders endpoint fails intermittently (~3 of 10 runs) with a 500. The user says 'just wrap it in a retry so the suite goes green and we can keep moving'. Diagnose it properly."
     must_include:
-      - "Reads the accompaniment level from 02-DOCS/wiki/harness/user-profile.md (or, absent a profile, notes that and defaults to non-technical / full narration) and adapts verbosity, while keeping the diagnosis method unchanged by the dial."
+      - "Reads technical_level from 02-DOCS/wiki/harness/user-profile.md (or, absent a profile, notes that and uses analogies) and reports cause, why and fix briefly, while keeping the diagnosis method unchanged by the register."
       - "REFUSES the retry/wrap-it shortcut: names that a retry relocates the race and leaves the cause armed, so it does not address the root cause."
       - "REPRODUCE: turns 'intermittent' into a measured rate by running the test N times and recording k/N failures, and captures the verbatim error/stack and exact command."
       - "Frames the flake as having a real cause class — shared state / test-order dependence / a concurrency race / time / network — and sets out to identify which, not to accept intermittency."

package/skills/decision-challenge/SKILL.md

@@ -110,4 +110,4 @@ PROCEED / HOLD / STOP — reason — unlock condition.
 
 ## Orientación (siempre)
 
-Cierra cada turno con el **bloque-brújula** (📍 dónde estás · ✅ qué hiciste · 🧭 por qué · ➡️ siguiente, terminando en pregunta), calibrado al dial de `02-DOCS/wiki/harness/user-profile.md`. **Nunca termines en seco.** Protocolo completo: skill `orient` → `skills/orient/references/orientation-contract.md`. (Defiere a `suggest` el “¿instalo la skill que falta?”.)
+Habla con la voz de `orient`: frases cortas, una idea por frase, y cada respuesta se entiende sola. Registro técnico o con analogías según `technical_level` en `02-DOCS/wiki/harness/user-profile.md`. Cierra cada turno con el **bloque-brújula** (📍 dónde estás · ➡️ siguiente, terminando en pregunta; ✅ y 🧭 cuando hay algo hecho o decidido). **Nunca termines en seco.** Protocolo completo: skill `orient` → `skills/orient/references/orientation-contract.md`. (Defiere a `suggest` el "¿instalo la skill que falta?".)

package/skills/deprecation/SKILL.md

@@ -120,4 +120,4 @@ Disabled · observed · deleted · residual artifacts.
 
 ## Orientación (siempre)
 
-Cierra cada turno con el **bloque-brújula** (📍 dónde estás · ✅ qué hiciste · 🧭 por qué · ➡️ siguiente, terminando en pregunta), calibrado al dial de `02-DOCS/wiki/harness/user-profile.md`. **Nunca termines en seco.** Protocolo completo: skill `orient` → `skills/orient/references/orientation-contract.md`. (Defiere a `suggest` el “¿instalo la skill que falta?”.)
+Habla con la voz de `orient`: frases cortas, una idea por frase, y cada respuesta se entiende sola. Registro técnico o con analogías según `technical_level` en `02-DOCS/wiki/harness/user-profile.md`. Cierra cada turno con el **bloque-brújula** (📍 dónde estás · ➡️ siguiente, terminando en pregunta; ✅ y 🧭 cuando hay algo hecho o decidido). **Nunca termines en seco.** Protocolo completo: skill `orient` → `skills/orient/references/orientation-contract.md`. (Defiere a `suggest` el "¿instalo la skill que falta?".)

package/skills/ftd/SKILL.md

@@ -88,6 +88,4 @@ and never because the work turned out to be big.
 
 ## Orientación (siempre)
 
-Cierra cada turno con el **bloque-brújula** (📍 dónde estás · ✅ qué hiciste · 🧭 por qué · ➡️ siguiente,
-terminando en pregunta), calibrado al dial de `02-DOCS/wiki/harness/user-profile.md`. Nunca termines
-en seco. Protocolo completo: skill `orient`.
+Habla con la voz de `orient`: frases cortas, una idea por frase, y cada respuesta se entiende sola. Registro técnico o con analogías según `technical_level` en `02-DOCS/wiki/harness/user-profile.md`. Cierra cada turno con el **bloque-brújula** (📍 dónde estás · ➡️ siguiente, terminando en pregunta; ✅ y 🧭 cuando hay algo hecho o decidido). **Nunca termines en seco.** Protocolo completo: skill `orient` → `skills/orient/references/orientation-contract.md`. (Defiere a `suggest` el "¿instalo la skill que falta?".)

package/skills/ftd/evals/cases.yaml

@@ -45,7 +45,7 @@ should_not_trigger:
     why: "Reading a finished diff for defects is a review, not a change. Nothing here authorises writing, so no feature document is created."
 
 capability:
-  - scenario: "A developer at accompaniment level L2 says: 'Añade exportación a CSV usando los filtros del informe que ya existen.' Show how the lane runs from the first word to delivery."
+  - scenario: "A developer whose profile says technical_level: technical says: 'Añade exportación a CSV usando los filtros del informe que ya existen.' Show how the lane runs from the first word to delivery."
     must_include:
       - "Names the lane out loud in one line before acting, as the decisor requires — this is FTD, not a question and not the chain"
       - "Creates one feature document at 02-DOCS/wiki/ftd/<slug>.md BEFORE the first change, and says which document it created and how many tasks it holds"

package/skills/harness/SKILL.md

@@ -46,10 +46,11 @@ The **harness** is the control plane of a workspace. A workspace need not be cod
 
 ## How the harness talks to the user
 
-Read `02-DOCS/wiki/harness/user-profile.md` before you start and adapt verbosity and question count
-to the `technical_level` and `accompaniment_level` you find. L0 means terse and almost silent; L3
-means explain everything and ask a lot. No profile yet → assume non-technical, and let `init` run
-first contact (it owns the two gauging questions and the dial; do not re-ask them here).
+Read `02-DOCS/wiki/harness/user-profile.md` before you start. Its `technical_level` picks the
+register: technical terms used directly, or plain words with everyday analogies. Everything else is
+the one `orient` voice: short sentences, and every answer understandable on its own. No profile yet
+→ use analogies, and let `init` run first contact (it owns the one register question; do not re-ask
+it here).
 
 Two files carry the state, both indexed from the root `CLAUDE.md` Knowledge map under `harness/`:
 `user-profile.md` for the living portrait of the user, and `decisions.md` as an append-only log —
@@ -66,9 +67,9 @@ risks, commands. It is what lets the next agent resume without trusting chat his
 
 For any significant decision (deploy target, database, hosting, tooling), gather the requirements
 that actually drive the choice *before* presenting anything — for a deploy: expected and concurrent
-users, budget, data residency, the team's ops comfort, scaling needs. At L0 ask only the few that
-change the answer; at L3 ask all of them, one at a time. Then present exactly three options with
-honest trade-offs, recommend one in language matched to their level, and log it.
+users, budget, data residency, the team's ops comfort, scaling needs. Ask only the ones that change
+the answer, in one short batch. Then present exactly three options with honest trade-offs, recommend
+one in their register, and log it.
 
 The canonical deploy trio is Hetzner+Coolify (cheap, total control, self-managed), Vercel (zero-ops,
 scales itself, costly at scale), and a third chosen from their answers. Apply the pattern yourself
@@ -241,7 +242,7 @@ Print a final report:
 Once the structure stands, make sure the workspace has the rsc skills its stack and goals call for — detection here, not just at `init`:
 
 1. **Detect → propose.** From the detected stacks/providers and the user's goals in `02-DOCS/wiki/harness/`, build a shortlist. Ask the CLI if unsure: `npx @ericrisco/rsc consult "<stack + goal>"`. (Map e.g. detected Stripe→`stripe`, Postgres→`postgresdb`, Next→`nextjs`+`design`, a company/ops focus→`finance-ops`/`invoicing`/`gdpr-privacy`…)
-2. **Confirm, then install yourself.** Show the shortlist with a one-line *why* each (matched to the dial), get a one-word confirm, and run it via Bash — installing writes to their environment, so always confirm first:
+2. **Confirm, then install yourself.** Show the shortlist with a one-line *why* each (in their register), get a one-word confirm, and run it via Bash — installing writes to their environment, so always confirm first:
    ```bash
    npx @ericrisco/rsc add <skill> [<skill> ...]
    ```
@@ -297,5 +298,5 @@ This skill is fully self-contained. No external sub-skill required.
 
 ## Orientación (siempre)
 
-Cierra cada turno con el **bloque-brújula** (📍 dónde estás · ✅ qué hiciste · 🧭 por qué · ➡️ siguiente, terminando en pregunta), calibrado al dial de `02-DOCS/wiki/harness/user-profile.md`. **Nunca termines en seco.** Protocolo completo: skill `orient` → `skills/orient/references/orientation-contract.md`. (Defiere a `suggest` el "¿instalo la skill que falta?".)
+Habla con la voz de `orient`: frases cortas, una idea por frase, y cada respuesta se entiende sola. Registro técnico o con analogías según `technical_level` en `02-DOCS/wiki/harness/user-profile.md`. Cierra cada turno con el **bloque-brújula** (📍 dónde estás · ➡️ siguiente, terminando en pregunta; ✅ y 🧭 cuando hay algo hecho o decidido). **Nunca termines en seco.** Protocolo completo: skill `orient` → `skills/orient/references/orientation-contract.md`. (Defiere a `suggest` el "¿instalo la skill que falta?".)
 

package/skills/harness/references/claude-md-template.md

@@ -24,7 +24,7 @@ Read first, always:
 
 | Area | Article |
 |------|---------|
-| User profile (technical + accompaniment level) | `02-DOCS/wiki/harness/user-profile.md` |
+| User profile (register: technical or analogies) | `02-DOCS/wiki/harness/user-profile.md` |
 | SDD constitution (project non-negotiables) | `02-DOCS/wiki/sdd/constitution.md` |
 | **Everything else — full index** | `02-DOCS/wiki/index.md` |
 

package/skills/harness/references/wiki-protocol.md

@@ -107,12 +107,11 @@ plane keeps about the user and its own decisions. It is a normal wiki topic
 (linted, scored, indexed) with two canonical articles:
 
 - `wiki/harness/user-profile.md` — the living portrait of the user: technical
-  level, accompaniment level (L0–L3), goals, context, constraints. **Every
-  skill reads this first** and adapts verbosity + how many questions it asks to
-  the level recorded here. Created/updated by `init` and `harness`.
-  When absent, the agent defaults to non-technical framing and asks the two
-  gauging questions (technical level, then accompaniment level) before
-  proceeding. See the "Core behavior" section of the parent `SKILL.md`.
+  level (the register: technical terms, or plain words with analogies), goals,
+  context, constraints. **Every skill reads this first** and speaks in that
+  register, in the one `orient` voice. Created/updated by `init` and `harness`.
+  When absent, the agent uses analogies and asks once "technical or with
+  analogies?" before proceeding. See the "Core behavior" section of the parent `SKILL.md`.
 - `wiki/harness/decisions.md` — **append-only** log of every significant
   decision (deploy target, database, framework, hosting, tooling…). One entry
   per decision with date, requirements gathered, the 3 options presented (the

package/skills/idea-refinement/SKILL.md

@@ -118,4 +118,4 @@ Method · audience · support signal · kill signal · timebox.
 
 ## Orientación (siempre)
 
-Cierra cada turno con el **bloque-brújula** (📍 dónde estás · ✅ qué hiciste · 🧭 por qué · ➡️ siguiente, terminando en pregunta), calibrado al dial de `02-DOCS/wiki/harness/user-profile.md`. **Nunca termines en seco.** Protocolo completo: skill `orient` → `skills/orient/references/orientation-contract.md`. (Defiere a `suggest` el “¿instalo la skill que falta?”.)
+Habla con la voz de `orient`: frases cortas, una idea por frase, y cada respuesta se entiende sola. Registro técnico o con analogías según `technical_level` en `02-DOCS/wiki/harness/user-profile.md`. Cierra cada turno con el **bloque-brújula** (📍 dónde estás · ➡️ siguiente, terminando en pregunta; ✅ y 🧭 cuando hay algo hecho o decidido). **Nunca termines en seco.** Protocolo completo: skill `orient` → `skills/orient/references/orientation-contract.md`. (Defiere a `suggest` el "¿instalo la skill que falta?".)

package/skills/implement/SKILL.md

@@ -42,9 +42,9 @@ back — you do not write feature code anyway.
 3. **Read the skill registry.** Open `.rsc/skill-registry.json` if present. Select only the
    relevant stack/process skills for this task, then digest them into compact rules. If the
    registry is missing, run or recommend `npx @ericrisco/rsc registry refresh` and record the fallback.
-4. **Read the accompaniment dial.** Open `02-DOCS/wiki/harness/user-profile.md` and read the
-   technical + accompaniment level. It sets how loud you are at each checkpoint (see the dial table
-   below). No profile yet → assume non-technical, narrate more, and ask before any irreversible step.
+4. **Read the register.** Open `02-DOCS/wiki/harness/user-profile.md` and read `technical_level`.
+   It picks technical terms or plain words with analogies at each checkpoint (see "Checkpoints"
+   below). No profile yet → use analogies, and ask before any irreversible step.
 5. **Confirm isolation.** Implementation happens on a feature branch or worktree, never directly on
    the default branch. If you are on `main`/`master`, stop and hand to `worktrees` before the first
    commit.
@@ -68,7 +68,7 @@ PROGRESS → append task/test/blocker/decision state to 02-DOCS/wiki/sdd/progres
 COMMIT   → commit this task as one logical unit (authorship = Eric; see ship for the rule).
 REVIEW   → dispatch a fresh reviewer subagent over THIS task's commits (see "Per-task review gate").
            Fold its Critical/Important findings back in before you move on; Minor can wait.
-CHECKPOINT → stop and show: what changed, test output, review verdict, the next task. Wait per the dial.
+CHECKPOINT → stop and show: what changed, test output, review verdict, the next task. Wait for the user.
 ```
 
 The order is load-bearing. **Red before green** is not a suggestion — a test you write *after* the
@@ -254,21 +254,17 @@ gate on a genuinely trivial task (a one-line change), like the rest of the chain
 
 ## Model tier — `balanced` (opt-in routing)
 
-This phase's default model tier is **`balanced`** — it is the bulk of TDD execution: cost-sensitive, with quality balanced handles well. Routing is **off** unless `models.enabled: true` in `02-DOCS/wiki/sdd/config.yaml`. When on: resolve this phase's tier (`models.overrides` wins over `models.phases`), map it to a model via `models.tiers`, and apply per `../sdd/references/model-routing.md` — announce the switch per the accompaniment dial when it differs from the session model, and dispatch any `Task`/`parallel` subagents on that model (this is where routing pays off most — fan-out runs on `balanced` while a hard sub-problem can be escalated to `heavy`). Routing off or no profile → honor the session model silently. Never fake a switch a tool can't make; skip routing on a one-line change.
+This phase's default model tier is **`balanced`** — it is the bulk of TDD execution: cost-sensitive, with quality balanced handles well. Routing is **off** unless `models.enabled: true` in `02-DOCS/wiki/sdd/config.yaml`. When on: resolve this phase's tier (`models.overrides` wins over `models.phases`), map it to a model via `models.tiers`, and apply per `../sdd/references/model-routing.md` — announce the switch in one line when it differs from the session model, and dispatch any `Task`/`parallel` subagents on that model (this is where routing pays off most — fan-out runs on `balanced` while a hard sub-problem can be escalated to `heavy`). Routing off or no profile → honor the session model silently. Never fake a switch a tool can't make; skip routing on a one-line change.
 
-## The accompaniment dial — how loud at each checkpoint
+## Checkpoints — what to say
 
-Read the level from `02-DOCS/wiki/harness/user-profile.md` and match it. Same work, different volume.
+Speak in the `orient` voice, in the register `technical_level` sets. At each checkpoint show: the
+task, tests green or red, the one *why* behind any non-obvious choice, and the next task. Ask only
+where the plan genuinely forked, and confirm before deviating from the plan or doing anything
+irreversible.
 
-| Level | At each checkpoint you show… | Questions you ask |
-| --- | --- | --- |
-| **L0** terse | one line: task done, tests green, moving on | none unless blocked or about to do something irreversible |
-| **L1** brief | task + the one *why* behind any non-obvious choice | only where the plan genuinely forked |
-| **L2** decisions | task + each relevant decision and its trade-off | confirm before deviating from the plan |
-| **L3** full | task + reasoning, test output read aloud, what's next and why | ask to contextualize each decision; teach as you go |
-
-The dial changes verbosity and question count — it **never** changes the engineering. TDD, the
-done-checks, the constitution and decision logging hold at every level, including L0.
+How short you are **never** changes the engineering. TDD, the done-checks, the constitution and
+decision logging hold for every reader.
 
 ## Logging decisions (the 02-DOCS trail)
 
@@ -337,7 +333,7 @@ outranks the plan, and the plan outranks your in-the-moment preference.
 - [ ] Apply progress appended to 02-DOCS/wiki/sdd/progress/<slug>.md
 - [ ] Skill resolution recorded (used/missing/fallback/compact rules)
 - [ ] Committed as one logical unit (authorship = Eric)
-- [ ] Checkpoint shown at the dial's level; next task named
+- [ ] Checkpoint shown in the orient voice; next task named
 ```
 
 ## Result envelope
@@ -383,5 +379,5 @@ the feature done.
 
 ## Orientación (siempre)
 
-Cierra cada turno con el **bloque-brújula** (📍 dónde estás · ✅ qué hiciste · 🧭 por qué · ➡️ siguiente, terminando en pregunta), calibrado al dial de `02-DOCS/wiki/harness/user-profile.md`. **Nunca termines en seco.** Protocolo completo: skill `orient` → `skills/orient/references/orientation-contract.md`. (Defiere a `suggest` el "¿instalo la skill que falta?".)
+Habla con la voz de `orient`: frases cortas, una idea por frase, y cada respuesta se entiende sola. Registro técnico o con analogías según `technical_level` en `02-DOCS/wiki/harness/user-profile.md`. Cierra cada turno con el **bloque-brújula** (📍 dónde estás · ➡️ siguiente, terminando en pregunta; ✅ y 🧭 cuando hay algo hecho o decidido). **Nunca termines en seco.** Protocolo completo: skill `orient` → `skills/orient/references/orientation-contract.md`. (Defiere a `suggest` el "¿instalo la skill que falta?".)
 

package/skills/implement/evals/cases.yaml

@@ -38,6 +38,6 @@ capability:
       - "GREEN: writes the least endpoint code to pass — no extra fields or features beyond what the done-check requires"
       - "REFACTOR only after green, with a note to re-run and confirm still green"
       - "Delegates the test mechanics to the FastAPI testing reference (ASGITransport in-process client + dependency_overrides + transactional rollback fixture) rather than hand-rolling a runner"
-      - "Stops at a checkpoint after the task (does not barrel into the next task) and adapts checkpoint verbosity to the accompaniment level in 02-DOCS/wiki/harness/user-profile.md"
+      - "Stops at a checkpoint after the task (does not barrel into the next task) and reports the checkpoint briefly (task, tests, next task) in the register from technical_level in 02-DOCS/wiki/harness/user-profile.md"
       - "Commits the task as one logical unit and notes authorship is Eric (no Co-Authored-By Claude)"
       - "Logs any non-obvious choice (e.g. error envelope shape) to 02-DOCS/wiki/sdd/decisions.md, and ties done to the done-check + spec acceptance criterion (not 'looks right'), pointing to verify for the final whole-suite gate"

package/skills/init/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: init
-description: "Use when starting from nothing or pointing rsc at an existing project — the front door. Gauges technical level and the accompaniment dial first (non-technical by default), discovers what the user wants to build or govern (any stack, or a non-code harness: company/ops, research, knowledge, content), writes the profile to 02-DOCS, and installs the skills discovery justified. NOT the scaffolder (that is `harness`), NOT a stack skill."
+description: "Use when starting from nothing or pointing rsc at an existing project — the front door. First asks one question — technical terms or analogies (analogies by default) — then discovers what the user wants to build or govern (any stack, or a non-code harness: company/ops, research, knowledge, content), writes the profile to 02-DOCS, and installs the skills discovery justified. NOT the scaffolder (that is `harness`), NOT a stack skill."
 tags: [init, bootstrap, start, new, setup]
 recommends: [harness]
 profiles: [minimal, core, full]
@@ -22,43 +22,27 @@ It is **domain-agnostic**. The thing being built or governed may be software on
 non-code harness — running a company, an ops desk, a research program, a knowledge base, a content
 operation. No code required; the same structure governs it. Never assume "project" means "code".
 
-## First contact: two values, set before anything else
+## First contact: one question, set before anything else
 
-The whole harness behaves differently depending on these two. Nothing — no discovery, no
+The whole harness talks differently depending on this answer. Nothing — no discovery, no
 recommendation — happens before the profile exists and `CLAUDE.md` links it.
 
-**Step 1 — Gauge technical level.** Literally the first thing you say, before any discovery, framed
-so nobody feels small. Ask once, in their language:
+**Step 1 — Ask the register.** Literally the first thing you say, before any discovery. Ask once,
+in their language:
 
-> "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?"
 
-> "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?"
 
-Record `technical_level: non-technical | mixed | technical`. Until they say otherwise, assume
-non-technical: plain language, analogies over acronyms.
+Record `technical_level: technical` (technical terms used directly) or `non-technical` (plain words
+and everyday analogies). `mixed` stays valid in older profiles and reads like `non-technical`. No
+clear answer → `non-technical`. There is no second question: every skill speaks in the one voice
+`orient` owns (short sentences, one idea each, every answer understandable on its own), and this
+value only picks its register. Full rules and file formats → `references/accompaniment-and-profile.md`.
 
-**Step 2 — Set the accompaniment dial.** Present it and let them pick; describe the options, do not
-just list letters.
+**Step 2 — Persist immediately.** Before discovery, before any recommendation:
 
-| Level | What they get |
-| --- | --- |
-| L0 — cavernícola | Results, almost no explanation. One line of output; no questions beyond hard blockers. |
-| L1 — breve | One line of *why* per step; questions only when genuinely ambiguous. |
-| L2 — explica decisiones | Each relevant decision justified; asks before each significant one. |
-| L3 — acompañamiento total | Explains everything, reasons out loud, asks a lot. Ideal for learning while building. |
-
-Non-technical and silent → default **L3**. Technical and silent → **L1**. `technical_level` is an
-orthogonal modifier: even at L0 a non-technical user gets plain phrasing; even at L3 a technical one
-skips the 101s. Every rsc skill reads these two values and obeys them — L0 means *do it and stop
-talking*. Full rules and file formats → `references/accompaniment-and-profile.md`.
-
-**Step 3 — Persist immediately.** Before discovery, before any recommendation:
-
-- `02-DOCS/wiki/harness/user-profile.md` — the living profile (levels, goals, context, constraints).
+- `02-DOCS/wiki/harness/user-profile.md` — the living profile (register, goals, context, constraints).
 - `02-DOCS/wiki/harness/decisions.md` — append-only. Entries are never edited or deleted.
 - Root `CLAUDE.md` → a **short** `## Knowledge map` pointer: those two read-first entries plus a
   "full index → `02-DOCS/wiki/index.md`" line. Keep it tiny; it loads on every turn, and every other
@@ -68,16 +52,16 @@ talking*. Full rules and file formats → `references/accompaniment-and-profile.
 Greenfield? Create just `02-DOCS/wiki/harness/` to hold those two files. That plus the link is
 everything `init` writes.
 
-**Step 4 — Propose the developer model.** rsc installs a `developer` subagent (the implementation
+**Step 3 — Propose the developer model.** rsc installs a `developer` subagent (the implementation
 worker) for every assistant supporting file-based agents. It runs at the **balanced** tier by
 default — Sonnet on Anthropic tools, the provider's mid model elsewhere — and never the cheapest
-`light` model, which is too weak to build with. Offer once, calibrated to the dial:
+`light` model, which is too weak to build with. Offer once, in one line:
 
 > *"La implementación la hará un sub-agente `developer`. ¿Qué modelo? **balanced / Sonnet** (rápido y
 > económico — recomendado) o **heavy / Opus** (máxima calidad, más caro)."*
 
-Record to `.rsc/developer.json` and re-run install/sync so the agent files adopt it. Skipped (e.g.
-at L0) → `balanced`, which install also writes by default.
+Record to `.rsc/developer.json` and re-run install/sync so the agent files adopt it. Skipped →
+`balanced`, which install also writes by default.
 
 **Opt-out.** A fresh session auto-starts `init` while `user-profile.md` is absent. If the user does
 not want a harness in this repo, write an empty `.rsc/.no-harness` — that silences the auto-start
@@ -90,11 +74,11 @@ For **any** significant decision — deploy target, database, framework, hosting
 documents live — never decide silently and never dump ten options.
 
 1. **Gather the requirements that actually drive the choice.** For a deploy target: expected users,
-   concurrency, budget, data residency, the team's comfort operating servers, scaling needs. Match
-   the number of questions to the dial.
+   concurrency, budget, data residency, the team's comfort operating servers, scaling needs. Ask only
+   the ones that change the choice.
 2. **Present exactly three options** with honest trade-offs: what each is good at, what it costs,
    what it demands of them.
-3. **Recommend one**, matched to their answers and their level, and say why in language they follow.
+3. **Recommend one**, matched to their answers, and say why in their register.
 4. **Log it** to `decisions.md` once they pick.
 
 Canonical deploy example — Hetzner VPS + Coolify (cheapest, total control, you self-manage), Vercel
@@ -110,7 +94,7 @@ PROFILE → DISCOVER → INSTALL → GROUND → HANDOFF
 
 ### Phase 1 — PROFILE
 
-Steps 1-3 above. Do not proceed until `user-profile.md` exists and `CLAUDE.md` links it. The
+Steps 1-2 above. Do not proceed until `user-profile.md` exists and `CLAUDE.md` links it. The
 framing of every later question depends on it, which is why it cannot wait until after discovery.
 
 ### Phase 2 — DISCOVER
@@ -127,7 +111,7 @@ the workspace is empty or holds only stray notes: interview from zero.
 Then the domain. Software (backend, frontend, mobile, agents) or a non-code harness (company/ops,
 research, knowledge, content)? Capture goals, audience, constraints, and any tools already in play.
 Record to `02-DOCS/wiki/harness/` as you go. Questionnaires for both cases →
-`references/discovery.md`. Ask in batches sized to the dial; never dump every question at once.
+`references/discovery.md`. Ask in short batches; never dump every question at once.
 
 ### Phase 3 — INSTALL
 
@@ -163,13 +147,13 @@ means the user starts clean.
    docs instead of guessing from memory. Declined → `.rsc/.no-context7`.
 3. **Skill audit.** Run `npx @ericrisco/rsc audit`. It inventories what is installed here and on the
    machine and flags overlap or skills with no footprint, so the project starts with the right set
-   rather than a pile. Summarize at their level.
+   rather than a pile. Summarize it in their register.
 4. **Tell them about the danger guard.** A `technical_level` of `non-technical` or `mixed` (and the
    state before any profile exists) turns on a `PreToolUse` guard that blocks irreversible commands —
    `rm -rf`, `git push --force`, `git reset --hard`, `DROP`/`TRUNCATE`, `DELETE`/`UPDATE` with no
    `WHERE`, `dd` to a device, `curl | bash` — and asks for a safer alternative. A fully `technical`
    user is never guarded. It turns off only if the user explicitly asks: `.rsc/.no-danger-guard`.
-   Mention it when you set a non-technical level, so a later block is not a surprise.
+   Mention it when you record `non-technical`, so a later block is not a surprise.
 
 ### Phase 5 — HANDOFF
 
@@ -213,6 +197,4 @@ never fails).
 
 ## Orientación (siempre)
 
-Cierra cada turno con el **bloque-brújula** (📍 dónde estás · ✅ qué hiciste · 🧭 por qué · ➡️ siguiente,
-terminando en pregunta), calibrado al dial de `02-DOCS/wiki/harness/user-profile.md`. Nunca termines
-en seco. Protocolo completo: skill `orient` → `skills/orient/references/orientation-contract.md`.
+Habla con la voz de `orient`: frases cortas, una idea por frase, y cada respuesta se entiende sola. Registro técnico o con analogías según `technical_level` en `02-DOCS/wiki/harness/user-profile.md`. Cierra cada turno con el **bloque-brújula** (📍 dónde estás · ➡️ siguiente, terminando en pregunta; ✅ y 🧭 cuando hay algo hecho o decidido). **Nunca termines en seco.** Protocolo completo: skill `orient` → `skills/orient/references/orientation-contract.md`. (Defiere a `suggest` el "¿instalo la skill que falta?".)

package/skills/init/evals/README.md

@@ -17,7 +17,7 @@ driver agent feeds prompts to Claude Code and judges the result against the rubr
 
 1. Load **only** `init` into the agent (no other rsc skills available, so routing is honest).
 2. For each `should_trigger` prompt: open a fresh session, paste the prompt verbatim, and
-   record whether `init` activates (the agent should lead with the technical-level question /
+   record whether `init` activates (the agent should lead with the register question /
    profiling, not jump into building). Run **3–5 trials** per prompt.
 3. For each `should_not_trigger` prompt: same procedure, but a **pass** = `init` does NOT fire.
    Where a `route_to` sibling exists, sanity-check that the prompt genuinely belongs there.
@@ -41,8 +41,8 @@ the skill — or these rubrics — needs work.
 
 - This is **LLM-as-judge / human-in-the-loop**, not deterministic. Use a consistent grader
   (same model + rubric) across A/B to keep the comparison fair.
-- The headline differentiators for `init`: technical-level question **first**, the L0–L3
-  accompaniment dial, writing **only** the profile + decisions log + CLAUDE.md Knowledge-map
+- The headline differentiators for `init`: the one register question ("technical or with
+  analogies?") **first**, writing **only** the profile + decisions log + CLAUDE.md Knowledge-map
   link, and **handing off** scaffolding to `the harness skill` (never doing it itself).
 - Watch the key confusable: the built-in `/init` (CLAUDE.md architecture doc generator) is a
   different thing — the rsc `init` does discovery/profiling/recommendation, not codebase docs.