@naswerks/engineering-loop 0.5.1 → 0.7.0

package/.claude-plugin/marketplace.json

@@ -10,7 +10,7 @@
     {
       "name": "naswerks",
       "description": "The engineering loop: docs-* knowledge loop, spec-* execution loop, and init for a fresh repository.",
-      "version": "0.5.1",
+      "version": "0.7.0",
       "source": "./"
     }
   ]

package/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "naswerks",
-  "version": "0.5.1",
+  "version": "0.7.0",
   "description": "The engineering loop: a knowledge loop (docs-*) and an execution loop (spec-*) for repositories driven by hosted agent sessions, plus init to make a repository ready for both.",
   "author": { "name": "naswerks" },
   "license": "MIT",

package/CHANGELOG.md

@@ -5,6 +5,93 @@ version is the one in `package.json` and `.claude-plugin/plugin.json`, which mus
 
 ## [Unreleased]
 
+## [0.7.0] - 2026-10-01
+
+### Changed
+
+- **The hosted plane runs the hand-cranked ceremony: one file, two voices, a poke each way.** A seat writes
+  its `plan.md` and `tldr.md` with its own tools and posts each by `path` the first time — the control plane
+  reads the file from the seat's runner (periscope 1.4.0's `workspace_read`) — then with nothing. The
+  coordinator appends its ruling to the seat's `tldr.md` under its coordinator-voice heading and calls
+  `accept_plan`, `accept` or `callout` with a one-line summary; the control plane mirrors the file before it
+  records the act, and the seat is pointed at the section added. The act still decides. A runner older than
+  periscope 1.4.0 keeps the old form: the seat posts `content`, and the verb carries the coordinator's words.
+  `spec-seat`, `spec-coordinator` and `engineering-loop.md` § The blackboard say so.
+- `spec-coordinator`: `seat_acts` is the coordinator's census (its mint carries `acts:read`, and
+  `spec-retro` says so too); `read_blackboard` returns a window of a file or only the sections new since a
+  revision; `accept` carries the commit call, and an acceptance written into the seat's file binds to that
+  revision.
+- `spec-seat`: a search is data only as a quoted literal given to a read-only search tool, with no `$`, no
+  backtick, no interpreter and no `xargs` in the pipeline. On a periscope 1.4.0 runner the native reads
+  reach outside the workspace, credential material excepted; on an older one a file outside it is read with
+  a shell command.
+
+### Added
+
+- **`## [seat·…] ABOUT TO PARK`, the seat's third anchor:** the next call waits on a human, and here it is —
+  the verbatim command and what it waits on, posted before the call runs. Non-staling, like `HOLDING`.
+- Both skills: a control-plane verb that fails with a transport error (`ECONNRESET`) is called once more,
+  then disclosed; a refusal has a name and a dropped connection does not.
+
+### Upgrading from 0.6
+
+1. Take the release: `claude plugin marketplace update engineering-loop`, then
+   `claude plugin update naswerks@engineering-loop --scope <scope>`, and a new session.
+2. Re-copy the loop text of `references/engineering-loop.md` into `docs/_meta/engineering-loop.md` — § The
+   blackboard changed — keeping your repository-owned sections. Then `init refresh` restamps both copies; it
+   never touches loop text.
+3. A control plane that reads the seat anchors treats `## [seat·…] ABOUT TO PARK` as it treats
+   `## [seat·…] HOLDING` — a post-acceptance append that does not stale the acceptance. Until it does, the
+   append stales one.
+
+## [0.6.0] - 2026-09-29
+
+### Changed
+
+- **Two skills are named for the seat kinds that run them.** `spec-parent` is now `spec-coordinator`, and
+  `spec-child` is now `spec-build`. A spec seat's skill is `spec-{kind}` for every kind; `fixit` rides
+  `spec-build`, and `docs-process` is its own skill. Invoke them as `/naswerks:spec-coordinator` and
+  `/naswerks:spec-build`. A control plane that seeds skills by name seeds the new names, with this version
+  as its pack floor.
+- **The coordinator's voice is spelled `COORDINATOR`.** The anchors are `## COORDINATOR RULING`,
+  `## COORDINATOR NOTE` and `## COORDINATOR ACCEPT` (beside `## OPERATOR RULING`), the ruling templates open
+  `COORDINATOR RESPONSE`, and a seat's own anchors are `## [seat·…] CLOSE-OUT RECEIPT` and
+  `## [seat·…] HOLDING`. A board written before this version spells them `## PARENT …` and `[child·…]`:
+  every grep the skills run reads both spellings, a parser that reads the anchors should too, and no seat
+  rewrites a heading already on its board.
+- The coordinator's close-out audit is filed as `sessions/coordinator-retrospective.md`; a reader takes
+  `sessions/parent-retrospective.md` in an effort begun before this version.
+- `spec-coordinator` no longer names a `parallel` spawn argument: a shared worktree holds one live seat at a
+  time, and parallel seats need separate worktrees, decided when the pipeline is created.
+- The retired-vocabulary census retires `parent` beside `chain` and `child`.
+- `docs-workflow.md` says the ignition brief is written whole at authoring and verified at ignition. The
+  sentence sits in § Templates, which a copy owns: see Upgrading, step 3.
+
+### Added
+
+- `pins/names.test.mjs`: every skill name the pack writes is a skill it carries, and every seat kind runs a
+  skill named for it. The kinds, their skills and the words shaped like a skill name that name none are one
+  list in `skills/init/scripts/owned.mjs`, which the doctor reads too.
+- `init doctor` degrades a brief whose `## The kick` names a skill this pack does not carry, and names the
+  coordinator's skill.
+
+### Upgrading from 0.5
+
+1. Take the release (`claude plugin marketplace update engineering-loop`, then
+   `claude plugin update naswerks@engineering-loop`) between efforts: a session that invokes `spec-parent`
+   or `spec-child` after the update finds no such skill.
+2. Re-copy the loop text of both references into `docs/_meta/`, keeping your repository-owned sections;
+   `init refresh` restamps and never touches loop text.
+3. Three places are yours, so neither `init refresh` nor a re-copy reaches them. Change each one that still
+   carries the old text:
+   - § The archive convention (repository-owned): `parent-retrospective.md` is `coordinator-retrospective.md`.
+   - § Templates (repository-owned): the ignition brief is "the coordinator seat's standing orders for the
+     run — written whole at authoring, verified at ignition" (it read "the parent seat's standing orders
+     for the run — two sections completed at ignition").
+   - `docs/_meta/doc-index.md`: the build-seat paragraph `init` wrote from its template names `spec-build`
+     (it read `spec-child`).
+4. Run `init doctor`. A brief whose kick still names a retired skill shows a DEGRADE row; change the kick.
+
 ## [0.5.1] - 2026-09-24
 
 ### Fixed

package/README.md

@@ -69,9 +69,9 @@ and never touches the rest of the text.
 | `docs-process` | docs | patch living docs from working docs, verified against code, then archive |
 | `docs-audit-feature` · `docs-audit-full` | docs | audit living docs against code |
 | `spec-pipeline` | spec | explode an approved plan into numbered specs |
-| `spec-parent` | spec | the coordinator seat |
+| `spec-coordinator` | spec | the coordinator seat |
 | `spec-seat` | spec | the contract every armed seat follows |
-| `spec-child` | spec | the build job for one spec |
+| `spec-build` | spec | the build job for one spec |
 | `spec-review` | spec | the outside look before the retrospective |
 | `spec-retro` | spec | the coordinator's close-out audit |
 | `spec-witness` | spec | a read-only verifier |

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@naswerks/engineering-loop",
-  "version": "0.5.1",
+  "version": "0.7.0",
   "description": "The engineering loop as a Claude Code plugin: a knowledge loop (docs-*), an execution loop (spec-*), and init for a fresh repository. The package root is the plugin root.",
   "license": "MIT",
   "type": "module",

package/references/docs-workflow.md

@@ -1,4 +1,4 @@
-<!-- naswerks-loop: version=0.5.1 -->
+<!-- naswerks-loop: version=0.7.0 -->
 # Docs Workflow
 
 > How knowledge flows through `docs/`: the loop, the folder rules, the templates, and the `docs-*` skills.
@@ -204,9 +204,9 @@ one** (via `spec-pipeline`). The trigger for the layout is simply *"does this ef
                                    (TWO files — questions ride the PLAN TLDR, and there are no
                                     status snapshots, because the tracker is committed live and
                                     its git history carries every revision)
-                                 code-review.md            the review seat's outside look, if
-                                                           the pipeline had a review row
-                                 parent-retrospective.md   the parent's inside look
+                                 code-review.md                the review seat's outside look, if
+                                                               the pipeline had a review row
+                                 coordinator-retrospective.md  the coordinator's inside look
                                These are TESTIMONY: an archive pass repairs links elsewhere and
                                leaves sessions/** byte-untouched. Older archived sessions may
                                still hold questions.md / status-after-*.md; that is historical
@@ -430,8 +430,8 @@ once the code is fixed. Keep entries one line, dated, and pointing at a `file:li
 ### Spec doc (a numbered pipeline — `spec-pipeline`)
 
 When a research idea graduates into a real plan, `spec-pipeline` explodes it into a numbered pipeline in
-`docs/research/{topic}/`: `00-ignition-brief.md` (the parent seat's standing orders for the run — two
-sections completed at ignition) · `01-{topic}.md` (the umbrella) · `02..NN-{slice}.md` (**one
+`docs/research/{topic}/`: `00-ignition-brief.md` (the coordinator seat's standing orders for the run —
+written whole at authoring, verified at ignition) · `01-{topic}.md` (the umbrella) · `02..NN-{slice}.md` (**one
 self-contained spec per planned session**) · `project-status.md` (the tracker, which carries its own
 section notes) · `live-checks.md` (the human's verification rows).
 Each per-session spec uses this template (carries `Builds on`/`Source:` so the chain stays navigable):
@@ -472,13 +472,13 @@ come from this copy, so a repository changes them once, here.
 |-------|------|-------------|
 | `docs-backlog` | Have an idea | Capture it as a research doc in `research/` |
 | `spec-pipeline` | A research idea is graduating into a real plan | Explode the plan into a numbered spec pipeline (umbrella + one self-contained spec per session + `project-status`) in `research/{topic}/`; the plan becomes ephemeral |
-| `spec-parent` | Right after `spec-pipeline` (same session, context-loaded) or to resume an effort fresh | Assume the coordinator seat: cut seat prompts (one per spec), review/verify TLDRs, give commit calls, own `project-status.md` — the same loop hand-cranked or hosted |
+| `spec-coordinator` | Right after `spec-pipeline` (same session, context-loaded) or to resume an effort fresh | Assume the coordinator seat: cut seat prompts (one per spec), review/verify TLDRs, give commit calls, own `project-status.md` — the same loop hand-cranked or hosted |
 | `spec-seat` | **Every** seat a coordinator arms — invoked FIRST, before the job skill | The CONTRACT, not a seat: the shared half of every seat's procedure — beliefs, plain-text PLAN TLDR, numbered questions w/ recommendations, six-section FINAL TLDR, commit only on the relayed call |
-| `spec-child` | Igniting a build or fixit seat — manually or platform-spawned, after `spec-seat` | The BUILD JOB only: one spec, the role's reading list, the pin taxonomy, the suite protocol; `fixit` variant for no-spec defect sessions. Its ceremony comes from `spec-seat` |
+| `spec-build` | Igniting a build or fixit seat — manually or platform-spawned, after `spec-seat` | The BUILD JOB only: one spec, the role's reading list, the pin taxonomy, the suite protocol; `fixit` variant for no-spec defect sessions. Its ceremony comes from `spec-seat` |
 | `spec-witness` | A pipeline looks wedged, actors' claims conflict, or you want a substrate-verified state report | The read-only fourth seat: the control plane's read lanes, transcripts, git; zero writes, zero rulings — the seats act, the human judges, the witness testifies |
-| `spec-ignite` | Right after `spec-pipeline` when the pipeline runs HOSTED (vs `spec-parent` for hand-cranked) | The ignition copilot: verify the committed brief, derive the stage card (the human clicks Create), "kick it", a hosted coordinator runs the pipeline; two verbal gates, everything announced, every UI gap a named finding |
+| `spec-ignite` | Right after `spec-pipeline` when the pipeline runs HOSTED (vs `spec-coordinator` for hand-cranked) | The ignition copilot: verify the committed brief, derive the stage card (the human clicks Create), "kick it", a hosted coordinator runs the pipeline; two verbal gates, everything announced, every UI gap a named finding |
 | `spec-review` | A pipeline's builds are done and it has a review row | The outside look, before the retro and before the PR: code + patterns + composition across session seams + the loop's own comms, in two independent passes. Files `sessions/code-review.md` and classifies which findings earn a fixit. **Its value is having none of the pipeline's context** |
-| `spec-retro` | The parent's LAST act, after any review and any fixit | The inside look: a substrate-verified grade, the ceremony audit (did the acts the seat believes it performed actually write rows?), the ledger reconciliation, the true economics, the blindnesses, and the ranked fixit backlog |
+| `spec-retro` | The coordinator's LAST act, after any review and any fixit | The inside look: a substrate-verified grade, the ceremony audit (did the acts the seat believes it performed actually write rows?), the ledger reconciliation, the true economics, the blindnesses, and the ranked fixit backlog |
 | `docs-status` | Session start | Report what's recently archived, what's in `working/`, what's in `research/`; sweep the meta-comments for the condensed status table |
 | `docs-write` | End of a session | Finalize the working doc; it stays in `working/` (records its `## Archive` target) |
 | `docs-process` | Start of a session, `working/` has docs | Patch living docs from the working doc's checklist (verified vs code), then file the doc into `archive/` |

package/references/engineering-loop.md

@@ -1,11 +1,11 @@
-<!-- naswerks-loop: version=0.5.1 -->
+<!-- naswerks-loop: version=0.7.0 -->
 # The Engineering Loop — flow, seats, skills, and the ceremony
 
 > The quick intro to how work gets built with this loop: the two loops (`docs-*` knowledge, `spec-*`
 > execution), the seats (Human / Coordinator / Seat, plus the read-only Witness), the ceremony per
 > session, and a bare-bones exchange showing the back-and-forth. Point newcomers at this plus
 > [doc-index](doc-index.md) + [docs-workflow](docs-workflow.md). Operational templates live in the
-> `spec-parent` skill; the seat contract in `spec-seat`.
+> `spec-coordinator` skill; the seat contract in `spec-seat`.
 <!-- meta: type=guide; status=current; verified={date}; lineage=1 -->
 
 ---
@@ -38,7 +38,7 @@ Plan graduates          -> spec-pipeline         -> docs/research/{topic}/: umbr
                                                     per session + project-status.md (the plan is
                                                     now throwaway — the specs carry every crumb)
 Same session — CHOOSE THE SEAT:
-  hand-cranked          -> spec-parent           -> this session becomes the COORDINATOR and cuts
+  hand-cranked          -> spec-coordinator      -> this session becomes the COORDINATOR and cuts
                                                     Prompt #1 (you relay every message)
   hosted                -> spec-ignite           -> this session becomes the IGNITION COPILOT:
                                                     verify the brief, derive the stage card, YOU
@@ -108,13 +108,13 @@ What a commit and a PR pass here, beyond the loop. These add to the Hard rules b
   just *plan, build, `docs-write`, `docs-process`* — no pipeline, no coordinator, a flat working
   doc. This is the default and it never requires a control plane.
 - **`spec-*` is the execution loop** for work that is more than one session: `spec-pipeline`
-  graduates the plan, `spec-parent` takes the seat, build seats build one spec each. **Each spec is sized
+  graduates the plan, `spec-coordinator` takes the seat, build seats build one spec each. **Each spec is sized
   for ONE session** — recon, plan, build, suite and FINAL TLDR before the session's context compacts —
   and the spec count falls out of that: a pipeline of two specs is a pipeline, and so is one of ten. It
   hands off to the knowledge loop at both ends (research docs in, working docs out).
 - **Either loop runs by hand or hosted.** The manual version is this document's ceremony with the human
   relaying; the hosted version is the control plane running the same ceremony, machine-relayed. When they
-  drift, this doc + the `spec-parent` skill are the requirements; the control plane follows.
+  drift, this doc + the `spec-coordinator` skill are the requirements; the control plane follows.
 
 ## The seats
 
@@ -126,7 +126,7 @@ What a commit and a PR pass here, beyond the loop. These add to the Hard rules b
 | **Witness** *(optional, `spec-witness`)* | a read-only session with substrate access | testifies from rows/transcripts/git when claims conflict or a pipeline looks wedged; answers "whose turn is it" | writes anything; injects anything; rules on anything |
 
 The seat, not the chat, is the product: `project-status.md` must stay current enough that a
-fresh session can resume as coordinator losslessly (`spec-parent {topic}`).
+fresh session can resume as coordinator losslessly (`spec-coordinator {topic}`).
 
 ## The skills
 
@@ -138,10 +138,10 @@ fresh session can resume as coordinator losslessly (`spec-parent {topic}`).
 | `docs-process` | docs | effort done, fresh session | patch living docs (verified vs code), archive |
 | `docs-audit-feature` / `docs-audit-full` | docs | doc suspected stale / monthly | deep-audit docs against code |
 | `spec-pipeline` | spec | a plan came through and you're committing to it | explode the plan into a numbered spec pipeline — *spare no crumb* |
-| `spec-parent` | spec | right after `spec-pipeline` (same session) or fresh with the topic | assume the coordinator seat |
-| `spec-seat` | spec | **every** seat the coordinator arms, invoked FIRST | **the CONTRACT, not a seat** — the shared half of every seat's procedure. `spec-parent` does NOT compose it: the coordinator writes rulings rather than receiving them |
-| `spec-child` | spec | igniting a build or fixit seat — manual (`spec-child {role} {spec}`) or hosted | **the BUILD JOB only** — one spec, the role's adds, the pin taxonomy, the suite protocol, the fixit variant. Its ceremony comes from `spec-seat` |
-| `spec-ignite` | spec | when an authored pipeline runs HOSTED (the `spec-parent` alternative) | the ignition copilot, and it can run COLD: gates, re-verify the brief's baselines + platform state against live HEAD, derive the stage card (human clicks Create), "kick it" with the brief's own kick text as the task; every UI gap a named finding |
+| `spec-coordinator` | spec | right after `spec-pipeline` (same session) or fresh with the topic | assume the coordinator seat |
+| `spec-seat` | spec | **every** seat the coordinator arms, invoked FIRST | **the CONTRACT, not a seat** — the shared half of every seat's procedure. `spec-coordinator` does NOT compose it: the coordinator writes rulings rather than receiving them |
+| `spec-build` | spec | igniting a build or fixit seat — manual (`spec-build {role} {spec}`) or hosted | **the BUILD JOB only** — one spec, the role's adds, the pin taxonomy, the suite protocol, the fixit variant. Its ceremony comes from `spec-seat` |
+| `spec-ignite` | spec | when an authored pipeline runs HOSTED (the `spec-coordinator` alternative) | the ignition copilot, and it can run COLD: gates, re-verify the brief's baselines + platform state against live HEAD, derive the stage card (human clicks Create), "kick it" with the brief's own kick text as the task; every UI gap a named finding |
 | `spec-review` | spec | a pipeline's builds are done, if it has a review row | the OUTSIDE look, before the retro and before the PR: correctness/security/**composition across session seams** · the patterns, with every departure identified · the loop's own comms. Two independent passes, consolidated. Classifies which findings earn a fixit; **its value is having none of the pipeline's context** |
 | `spec-retro` | spec | the coordinator's LAST act, after any review and any fixit | the INSIDE look: a substrate-verified grade, the ceremony audit (did the acts write rows?), the ledger reconciliation, the true economics, the blindnesses, the ranked fixit backlog — *a retrospective that cannot indict its own author is marketing* |
 | `spec-witness` | spec | a pipeline looks wedged, or actors' claims conflict | the read-only fourth seat: substrate access, zero writes, zero rulings |
@@ -155,7 +155,7 @@ The thing that keeps prompts and skills from drifting apart:
 |---|---|---|
 | **POLICY** | the policy document § This repository's rails names — and, hosted, the un-skippable system-prompt suffix the control plane supplies at open | cannot be skipped, present on every turn |
 | **PROCEDURE — shared** | `spec-seat` | the contract for ANY seat the coordinator arms: blackboard, question lane, parked-call discriminator, verdicts, BELIEFS sha, git shapes, six-section FINAL TLDR, close-out order |
-| **PROCEDURE — per job** | `spec-child` · `spec-review` · `docs-process` | what THIS seat does. The job skill **refines** the seat contract and never contradicts it; a genuine conflict is a finding, not a fork |
+| **PROCEDURE — per job** | `spec-build` · `spec-review` · `docs-process` | what THIS seat does. The job skill **refines** the seat contract and never contradicts it; a genuine conflict is a finding, not a fork |
 | **TASK** | the seed prompt + the pipeline's `00-ignition-brief.md` | per-run; dies with the run |
 
 A seed's first act is therefore to **invoke its skills** — `spec-seat`, then the job — not to restate them.
@@ -174,7 +174,7 @@ diff.
 ## The ceremony (one build session)
 
 1. **Coordinator cuts the seat prompt** from the PREVIOUS session's actual shipped shapes — never
-   from the spec's guesses alone. (Template: `spec-parent` skill.)
+   from the spec's guesses alone. (Template: `spec-coordinator` skill.)
 2. **Seat recons, states its beliefs** (HEAD sha, dirty files, versions, baselines), then a
    **PLAN TLDR as plain text** — before any plan-approval presentation — with **questions as
    numbered options + an embedded recommendation, then STOP**. Never an interactive question tool.
@@ -208,7 +208,7 @@ COORDINATOR -> Prompt #N: docs preamble, ##PROMPT##, ONE spec + context docs + p
                + CEREMONY block
 SEAT        -> PLAN TLDR (BELIEFS: head/dirty/versions/baselines · the plan, 5-10 lines ·
                QUESTIONS 1..n, options + recommendation), STOP
-COORDINATOR -> PARENT RESPONSE — PLAN {ACCEPTED / ACCEPTED-WITH-RIDERS / …} · rulings 1..n
+COORDINATOR -> COORDINATOR RESPONSE — PLAN {ACCEPTED / ACCEPTED-WITH-RIDERS / …} · rulings 1..n
                (DECISION — why) · riders · "Go build."
 SEAT        -> (builds free; mid-run question: numbered text, STOP; COORDINATOR ruling; resume)
 SEAT        -> FINAL TLDR — (a) SHIPPED+VERIFICATION (b) VERBATIM RUNNER SUMMARIES (c) HONEST GAPS
@@ -225,7 +225,7 @@ The exchange above is not just chat — it is a pair of FILES per build session:
 
 - **`tldr.md` — the chat.** Append-only, two voices: the seat's PLAN TLDR + numbered
   questions, the coordinator's ruling appended beneath them, optional mid-build updates +
-  `## PARENT NOTE`s, then the FINAL TLDR. Read top-to-bottom it IS the session's whole
+  `## COORDINATOR NOTE`s, then the FINAL TLDR. Read top-to-bottom it IS the session's whole
   conversation, greppable by anchor.
 - **`plan.md` — the document.** The full plan, posted once, corrected on pushback. PULL-only:
   the coordinator reads it on a `read-full-plan` verdict; it is never force-fed into a wake or chat.
@@ -237,11 +237,11 @@ with the effort:
 
 ```
 docs/research/{topic}/sessions/         <- per-session work in {spec-slug}/, effort-wide at the root
-  {spec-slug}/plan.md        each seat   the full plan, posted once, corrected on pushback (PULL-only)
-  {spec-slug}/tldr.md        each seat   the two-voice chat — seat turns AND coordinator rulings interleaved
-  code-review.md             the review  the outside look, if the pipeline had a review row
-  parent-retrospective.md    the coord.  the close-out audit (the inside look)
-  witness-ledger-*.md        a human     the witness is zero-writes, so its ledger arrives by hand
+  {spec-slug}/plan.md           each seat   the full plan, posted once, corrected on pushback (PULL-only)
+  {spec-slug}/tldr.md           each seat   the two-voice chat — seat turns AND coordinator rulings interleaved
+  code-review.md                the review  the outside look, if the pipeline had a review row
+  coordinator-retrospective.md  the coord.  the close-out audit (the inside look)
+  witness-ledger-*.md           a human     the witness is zero-writes, so its ledger arrives by hand
 ```
 
 Two files per build session; questions ride the TLDR, and there are no status snapshots because the
@@ -253,51 +253,59 @@ repo files, staged at close-out; the coordinator appends rulings with its own fi
 human's relay is a one-line nudge each way).
 
 <!-- control-plane-specific -->
-**Hosted — there is no folder tree the controller can read.** A seat **carries its bytes** to
-`post_plan` / `post_tldr` (verbs under `acts:write`, so a witness ticket structurally cannot post), and
-everything identifying is **server-derived** — pipeline and seat from the verified ticket, and **the rev**
-(newest + 1). *A rev nobody can misstate cannot regress by accident.* The append-only guard is what
-survives the transport: the ladder only climbs, a shorter file is refused, and the same rev with
-different bytes is refused — so the mirror **cannot be clobbered or rewound by a caller that lies, even
-though it can be fed.**
-
-**The coordinator's voice is NOT in the seat's file on the hosted plane.** A coordinator answers with
-`callout` (its sixth drive verb, machine-written, the only downward path), which persists on its own
-artifact lane and closes the question in the **acts ledger**. So **the file says whether a question was
-ASKED; the ledger says whether it was ANSWERED**, and a seat typing a parent-voice heading into its own
-TLDR closes nothing. `callout` **refuses when the charge has no live session** — a coordinator must
+**Hosted — the same files, read by the controller.** A seat edits its two files with its own tools and
+**pokes**: `post_plan` / `post_tldr` with the file's `path` inside its workspace the first time, then with
+nothing — the control plane reads the file from the seat's runner and mirrors it (verbs under `acts:write`,
+so a witness ticket structurally cannot post). A runner older than periscope 1.4.0 cannot be read; there the
+seat carries its bytes as `content`. Everything identifying is **server-derived** — pipeline and seat from
+the verified ticket, and **the rev** (newest + 1). *A rev nobody can misstate cannot regress by accident.*
+The append-only guard is what survives the transport: the ladder only climbs, a revision that drops a section
+is refused, and the same rev with different bytes is refused — so the mirror **cannot be clobbered or rewound
+by a caller that lies, even though it can be fed.**
+
+**The coordinator's voice is in the seat's file in both modes.** The coordinator appends its ruling to the
+seat's `tldr.md` under its coordinator-voice heading, then calls its verb (`accept_plan` · `accept` ·
+`callout`) with a one-line summary: the control plane mirrors the file as a revision in the coordinator's
+voice BEFORE it records the act, and the seat is pointed at the section added. **The file says what was
+said; the ledger says what was decided** — a question closes only on the coordinator's act, so a seat typing
+a coordinator-voice heading into its own TLDR closes nothing, and a revision in the coordinator's voice never
+counts as the seat asking. `callout` **refuses when the charge has no live session** — a coordinator must
 `seat_spawn` before it can rule — and reports **"RULING RECORDED, NOT DELIVERED"** in those words if the
-transport drops it.
+transport drops it. Where the coordinator cannot write the seat's file (a runner older than 1.4.0, a seat in
+its own workspace), the verb carries the words, as before.
 
-The parent-voice block (machinery-written hosted; the hand-cranked coordinator writes it — hand-cranked
-there is no rev counter, so the heading is `## PARENT RULING (plan — {verdict})`; the stable grep prefix
-`## PARENT RULING` is the contract in both modes):
+The coordinator-voice block (the coordinator writes it in both modes; hand-cranked there is no rev counter,
+so the heading is `## COORDINATOR RULING (plan — {verdict})`; the stable grep prefix
+`## COORDINATOR RULING` is the contract in both modes, and an older board's `## PARENT RULING` is read as
+the same heading):
 
 ```
-## PARENT RULING (plan rev N — {accept | accept-with-riders | blocking-precondition})
+## COORDINATOR RULING (plan rev N — {accept | accept-with-riders | blocking-precondition})
 
-PARENT RESPONSE — PLAN TLDR {VERDICT}. {one sentence naming the best thing in the plan}
+COORDINATOR RESPONSE — PLAN TLDR {VERDICT}. {one sentence naming the best thing in the plan}
 Answers:
 1. {RULING IN CAPS} — {decision first, then the why}.
 ...
 Go build. Fold the riders in — no re-approval round-trip.
 ```
 
-Callouts and nudges append as `## PARENT NOTE` (actor-suffixed when known, e.g. `(operator)`).
+Callouts and nudges append as `## COORDINATOR NOTE` (actor-suffixed when known, e.g. `(operator)`).
 
-**The seat's own two anchors:**
+**The seat's own three anchors:**
 
 ```
-## [child·{slug} · run {id}] CLOSE-OUT RECEIPT     <- after the push
-## [child·{slug} · run {id}] HOLDING              <- "I have pushed and I am waiting"
+## [seat·{slug} · run {id}] CLOSE-OUT RECEIPT     <- after the push
+## [seat·{slug} · run {id}] HOLDING              <- "I have pushed and I am waiting"
+## [seat·{slug} · run {id}] ABOUT TO PARK        <- "the next call waits on a human, and here it is"
 ```
 
-**A question heading, a HOLDING and a close-out receipt are ALL non-staling** — the gates bind an
-acceptance to the accepted CONTENT, not to the revision number, so appending your own *state* leaves it
-intact. Only **new content** stales. A seat that has pushed and is waiting is otherwise indistinguishable
+**A question heading, a HOLDING, an ABOUT TO PARK and a close-out receipt are ALL non-staling** — the gates
+bind an acceptance to the accepted CONTENT, not to the revision number, so appending your own *state* leaves
+it intact. Only **new content** stales. A seat that has pushed and is waiting is otherwise indistinguishable
 from a seat that has done nothing, and a coordinator reading a wake led by its own acceptance concludes
-there is nothing to rule — the HOLDING anchor is what prevents that. The token is the literal `child·`
-whatever seat you are — it is a protocol anchor, not a description of you.
+there is nothing to rule — the HOLDING anchor is what prevents that, and ABOUT TO PARK does the same for a
+seat the gate is holding. The token is the literal `seat·` whatever seat you are — it is a protocol anchor,
+not a description of you.
 
 ### Questions ride the same blackboard
 
@@ -321,4 +329,4 @@ the credential: **a receipt the audited party can mint is not a receipt** — wh
 door takes the human's own token and never a seat's job ticket.
 
 ## Lineage
-- **Related** — [docs-workflow](docs-workflow.md) · [doc-index](doc-index.md) · the `spec-parent` and `spec-seat` skills (the operational templates and the seat contract)
+- **Related** — [docs-workflow](docs-workflow.md) · [doc-index](doc-index.md) · the `spec-coordinator` and `spec-seat` skills (the operational templates and the seat contract)

package/skills/docs-process/SKILL.md

@@ -45,7 +45,8 @@ branch, which is the truth for that PR, and you say so at close.
    the seat that does it.
 
    **If the effort was a spec pipeline, you have a SECOND input: `sessions/code-review.md`** — the review
-   seat's outside look, filed beside `parent-retrospective.md`. Read both. **Every review finding gets a
+   seat's outside look, filed beside the coordinator's retrospective (`coordinator-retrospective.md`, or
+   `parent-retrospective.md` in an effort begun before that name). Read both. **Every review finding gets a
    disposition, and the disposition is TOTAL:** a living-doc patch here · an existing fixit seat · a
    chartered follow-up · a new spec pipeline · or killed on record with the reason. **A finding with no named
    home is dropped, not deferred** — and the review's own classification (fixit candidate / deferred /

package/skills/init/SKILL.md

@@ -250,5 +250,5 @@ write, offer — and ask before doing either — to fill each new absent-line fr
 - The floor four are always drafted, even in a repository with no frontend — the reading floor must
   RESOLVE for every seat kind, and "No frontend detected — fill this in" is an honest doc. The standard
   seven are drafted only on evidence; their absence is recorded, never papered over.
-- Counterpart skills: `spec-seat` (reads the floor), `spec-child` (reads the role rows), `spec-pipeline`
+- Counterpart skills: `spec-seat` (reads the floor), `spec-build` (reads the role rows), `spec-pipeline`
   (writes the brief `doctor` checks), `docs-write` / `docs-process` (the queue `doctor` reads).

package/skills/init/scripts/doctor.mjs

@@ -5,7 +5,7 @@ import { existsSync, readFileSync, readdirSync, statSync } from 'node:fs';
 import { join, resolve, dirname } from 'node:path';
 import { fileURLToPath } from 'node:url';
 import { execFileSync } from 'node:child_process';
-import { OWNED, compareVersions, compareMinor, frontmatterListCount, linesOf, bare, h2Index, findSection, railsItems } from './owned.mjs';
+import { OWNED, KINDS, KIND_SKILLS, NOT_SKILLS, skillTokens, compareVersions, compareMinor, frontmatterListCount, linesOf, bare, h2Index, findSection, railsItems } from './owned.mjs';
 
 const repo = resolve(process.argv[2] || process.cwd());
 const packRoot = resolve(dirname(fileURLToPath(import.meta.url)), '..', '..', '..');
@@ -194,7 +194,9 @@ for (const name of ['CLAUDE.md', 'AGENTS.md']) {
 }
 
 // ── 7. every ignition brief, checked the way the control plane checks it ────────────────────────
-const KINDS = new Set(['coordinator', 'build', 'fixit', 'review', 'retro', 'witness', 'docs-process']);
+// The kick is sent verbatim as the coordinator's task, so a skill it names that this pack does not carry
+// (a renamed one, most often) tells the coordinator to invoke nothing.
+const packSkills = new Set(existsSync(join(packRoot, 'skills')) ? readdirSync(join(packRoot, 'skills')) : []);
 const researchDir = join(repo, 'docs', 'research');
 if (existsSync(researchDir)) {
   for (const topic of readdirSync(researchDir)) {
@@ -205,6 +207,7 @@ if (existsSync(researchDir)) {
     const kick = sectionOf(text, '## The kick');
     if (kick === null) problems.push('the brief has no `## The kick` section, so the task text could not be read');
     else if (!kick.split('\n').some((l) => l.trimStart().startsWith('>'))) problems.push('the `## The kick` section carries no blockquote; its whole text stands in for the task');
+    const unknown = kick === null || packSkills.size === 0 ? [] : [...new Set(skillTokens(kick))].filter((t) => !packSkills.has(t) && !NOT_SKILLS.includes(t));
     const seq = sectionOf(text, '## The sequence');
     if (seq === null) problems.push('the brief has no `## The sequence` section, so no seats could be read');
     else {
@@ -213,13 +216,14 @@ if (existsSync(researchDir)) {
       for (const line of tableRows.slice(1)) {
         const cells = line.trim().replace(/^\|/, '').replace(/\|$/, '').split('|').map((c) => c.trim().replace(/^`|`$/g, '').trim());
         if (cells.every((c) => /^[-: ]*$/.test(c))) continue;
-        if (!cells.some((c) => KINDS.has(c))) { problems.push(`a sequence row names no seat kind and composes nothing: \`${line.trim()}\``); continue; }
+        if (!cells.some((c) => KINDS.includes(c))) { problems.push(`a sequence row names no seat kind and composes nothing: \`${line.trim()}\``); continue; }
         const spec = cells.map((c) => /\b(\d{2}-[A-Za-z0-9._-]*?\.md)\b/.exec(c)).find(Boolean);
         if (spec && !existsSync(join(researchDir, topic, spec[1]))) problems.push(`the sequence names \`${spec[1]}\` and it is missing from disk`);
       }
     }
-    if (problems.length) for (const pr of problems) row('FAIL', `docs/research/${topic}/00-ignition-brief.md`, pr);
-    else row('ok', `docs/research/${topic}/00-ignition-brief.md`, 'the kick and the sequence read clean');
+    for (const pr of problems) row('FAIL', `docs/research/${topic}/00-ignition-brief.md`, pr);
+    for (const t of unknown) row('DEGRADE', `docs/research/${topic}/00-ignition-brief.md`, `the kick names \`${t}\`, a skill this pack does not carry; the coordinator's skill is \`${KIND_SKILLS.coordinator}\``);
+    if (!problems.length && !unknown.length) row('ok', `docs/research/${topic}/00-ignition-brief.md`, 'the kick and the sequence read clean');
   }
 }
 

package/skills/init/scripts/owned.mjs

@@ -21,6 +21,32 @@ export const OWNED = [
 
 export const STAMP = /^(<!-- naswerks-loop: version=)([0-9]+\.[0-9]+\.[0-9]+[^ ]*)( -->)/;
 
+// The seat kinds a pipeline row may name, checked the way the control plane checks a brief's sequence.
+export const KINDS = ['coordinator', 'build', 'fixit', 'review', 'retro', 'witness', 'docs-process'];
+
+// The skill each kind runs as its job. A spec seat's skill is named for its kind, so a skill's name says
+// which seat runs it: `fixit` is the build job's no-spec variant, and `docs-process` is the knowledge
+// loop's own skill, seated by a pipeline as its last row.
+export const KIND_SKILLS = {
+  coordinator: 'spec-coordinator',
+  build: 'spec-build',
+  fixit: 'spec-build',
+  review: 'spec-review',
+  retro: 'spec-retro',
+  witness: 'spec-witness',
+  'docs-process': 'docs-process',
+};
+
+// Words shaped like a skill name that name no skill: the method doc, the placeholders, and the compounds
+// the prose uses. Every other spec-* or docs-* word the pack writes is a skill it carries.
+export const NOT_SKILLS = ['docs-workflow', 'spec-slug', 'spec-path', 'spec-doc', 'spec-driven', 'docs-only'];
+
+// Every skill-shaped word in a text. A word followed by `*` or `-*` names a family (docs-*, docs-audit-*),
+// never one skill.
+export function skillTokens(text) {
+  return [...text.matchAll(/\b(?:spec|docs)-[a-z]+(?:-[a-z]+)*\b(?![-*])/g)].map((m) => m[0]);
+}
+
 export function compareVersions(a, b) {
   const pa = a.split(/[.-]/).map((x) => parseInt(x, 10) || 0), pb = b.split(/[.-]/).map((x) => parseInt(x, 10) || 0);
   for (let i = 0; i < 3; i++) { if ((pa[i] || 0) !== (pb[i] || 0)) return (pa[i] || 0) - (pb[i] || 0); }

package/skills/{spec-child → spec-build}/SKILL.md

@@ -1,9 +1,9 @@
 ---
-name: spec-child
-description: The BUILD JOB for a pipeline seat — one spec, the role's reading list, the pin taxonomy, the suite protocol, and the fixit variant. Composed AFTER spec-seat, which carries the seat contract (blackboard, question lane, verdicts, FINAL TLDR, close-out). Use when a prompt says you are a build or fixit session, or run spec-child {role} {spec-path}. Roles: backend | frontend | mixed.
+name: spec-build
+description: The BUILD JOB for a pipeline seat — one spec, the role's reading list, the pin taxonomy, the suite protocol, and the fixit variant. Composed AFTER spec-seat, which carries the seat contract (blackboard, question lane, verdicts, FINAL TLDR, close-out). Use when a prompt says you are a build or fixit session, or run spec-build {role} {spec-path}. Roles: backend | frontend | mixed.
 ---
 
-# spec-child
+# spec-build
 
 **Your seat contract is `spec-seat` — invoke it first if you have not.** It carries the blackboard, the
 question lane, the parked-call discriminator, the verdict vocabulary, the BELIEFS sha, git shapes, the
@@ -14,7 +14,7 @@ You build exactly one spec. The coordinator judges and rules; you recon, plan, b
 Hand-cranked, a human relays messages; hosted inside a pipeline, your coordinator drives you itself and
 the relay is machine-carried — **your contract is identical either way.**
 
-Invoked as `spec-child {role} {spec-path}`, or told "you are a build session" with the spec path.
+Invoked as `spec-build {role} {spec-path}`, or told "you are a build session" with the spec path.
 
 ## Step 1 — with your role and spec in hand
 
@@ -130,7 +130,7 @@ build over a tree they had not touched, and they got a **passing receipt that pr
 false-green genus, embedded in the manual instead of in a test. Name the app you edited and run its
 commands from its root.
 
-## Fix-it variant (`spec-child fixit`)
+## Fix-it variant (`spec-build fixit`)
 
 No spec — your contract is the prompt + the coordinator's ledger (READ-ONLY). **STEP 0 — INVESTIGATE,
 REPORT, STOP:** (1) reproduce/characterize cheaply, (2) find the cheapest reliable RECEIPT for the fixed
@@ -152,6 +152,6 @@ what a truthful partial looks like per named item, **ask for it** before you sta
 - **The spec's anchors are hypotheses; HEAD is the truth.** The biggest catches — stale trees, false
   greens, dropped rulings — are all belief-vs-ledger mismatches. Your beliefs block exists so the
   coordinator can catch them cheaply.
-- Counterpart skills: `spec-seat` (your contract) · `spec-parent` (the seat that arms you) ·
+- Counterpart skills: `spec-seat` (your contract) · `spec-coordinator` (the seat that arms you) ·
   `spec-pipeline` (how your spec came to exist). The hosted version of you runs THIS same pair — the
   control plane's seed names both skills, in this order.