@naswerks/engineering-loop 0.5.0 → 0.6.0

package/skills/{spec-parent → spec-coordinator}/SKILL.md

@@ -1,12 +1,12 @@
 ---
-name: spec-parent
-description: Assume the COORDINATOR seat for a spec-pipeline effort — quarterback the build seats (one per spec) via prompts, TLDR reviews, verification, and commit calls. Use immediately after spec-pipeline in the same session (the author is already context-loaded), or in a fresh session with the topic name to resume/take a prepped effort. Run spec-parent {topic}.
+name: spec-coordinator
+description: Assume the COORDINATOR seat for a spec-pipeline effort — quarterback the build seats (one per spec) via prompts, TLDR reviews, verification, and commit calls. Use immediately after spec-pipeline in the same session (the author is already context-loaded), or in a fresh session with the topic name to resume/take a prepped effort. Run spec-coordinator {topic}.
 ---
 
-# spec-parent
+# spec-coordinator
 
 Turn this session into the **coordinator** for a `docs/research/{topic}/` spec pipeline. This is
-phase 3 of the backlog model (`docs-backlog`, `spec-pipeline`, **`spec-parent`**, seats build,
+phase 3 of the backlog model (`docs-backlog`, `spec-pipeline`, **`spec-coordinator`**, seats build,
 `docs-process`).
 
 **Find the format first.** This repository writes its formats (the doc header and status words, where an effort is filed, its rails) in the sections `rg -n '^#+ .*\(repository-owned\)' docs/_meta/` lists; read the one a step names before that step writes. This skill names the section, never the format.
@@ -117,7 +117,7 @@ read the board and answer on first receipt rather than spending a round-trip.
    corrected.
 
    **Pick the docs:** the floor and the loop's standard docs are settled (`spec-seat`'s Step 0 +
-   `spec-child`'s role table). **This repository's own docs are yours to seed, by path, every time:** copy
+   `spec-build`'s role table). **This repository's own docs are yours to seed, by path, every time:** copy
    the seat's role rows from `docs/_meta/doc-index.md` § Role reading lists into the prompt's `EXTRA DOCS`
    line — a seat follows a path in its prompt and does not reliably follow an index. Then add the extras
    the task itself warrants. When in doubt, seed the doc: a seat reading one extra doc is cheaper than a
@@ -420,10 +420,12 @@ so read them as run-time obligations, not close-out ones:
   wait or to reshape the command — not to complete a run or curl past the fence. **And a park that sails
   through anyway is DATA:** record it immediately as an incident, because a fence that failed silently once
   will fail silently again, and your record is the only trace.
-- **`parallel:true` is for specs that share no files — that is its whole purpose.** A refused spawn means
-  the previous seat is still holding the shared effort worktree and needs reaping; the answer is to reap
-  it, or to wait if it has not closed out yet. Reaching for `parallel` there is a category error rather
-  than a shortcut: it does not free the worktree, it just puts two seats in it.
+- **A shared worktree holds one live seat at a time, and nothing but you enforces it.** `seat_spawn`
+  refuses a terminal seat, a seat that already has a live session and a runner it cannot reach — it does
+  NOT refuse a second seat while another is still live in the shared tree, so spawning early puts two
+  seats in one worktree. Reap the previous seat first, or wait if it has not closed out yet. Parallel
+  seats need separate worktrees, which is the pipeline's shape, decided at create — and only for specs
+  that share no files.
 
 ## The steering channel — shape your callouts by SOLICITATION
 
@@ -442,10 +444,10 @@ send context attached to a ruling instead.
 
 ## The seat prompt template
 
-The ceremony rides the **`spec-child` skill** — the prompt is an IGNITER, not a ceremony restatement.
+The ceremony rides the **`spec-build` skill** — the prompt is an IGNITER, not a ceremony restatement.
 
 ```
-You are a BUILD SEAT in a coordinator-run effort: invoke the spec-child skill with
+You are a BUILD SEAT in a coordinator-run effort: invoke the spec-build skill with
 role={backend | frontend | mixed} before anything else, and ALWAYS after `spec-seat`: the seat header
 names `spec-seat` first, the job skill second.
 
@@ -473,7 +475,7 @@ THE TASK: {compressed spec restatement with the load-bearing specifics inline.}
 
 For investigation-first work, add **STEP 0 — INVESTIGATE, REPORT, STOP** before the task, or use
 `role={...} fixit` for no-spec defect sessions (the skill carries the fix-it ceremony). Fallback: if the
-seat can't invoke skills, paste the ceremony from the `spec-child` skill inline.
+seat can't invoke skills, paste the ceremony from the `spec-build` skill inline.
 
 ### The bookend rows (R and P) get a MANIFEST instead of prior shapes
 
@@ -514,7 +516,7 @@ P it is the difference between archiving this effort and sweeping somebody else'
 ## Ruling template (plan review / question answers)
 
 ```
-PARENT RESPONSE — PLAN TLDR {ACCEPTED / ACCEPTED WITH RIDERS / BLOCKING-PRECONDITION}.
+COORDINATOR RESPONSE — PLAN TLDR {ACCEPTED / ACCEPTED WITH RIDERS / BLOCKING-PRECONDITION}.
 {Verdict vocabulary: accept · accept-with-riders (numbered rulings anchored to the SEAT'S OWN item
 numbers — it folds them in and GOES, no re-approval round-trip; the dominant verdict) ·
 blocking-precondition ("accept, but step 0 first") · read-full-plan (not a verdict you send — you
@@ -543,14 +545,17 @@ asking for a paste (`read-full-plan` = read `plan.md`, a pull, never force-fed).
 verbs ARE the appends and the machinery writes them for you.
 
 **Anchor grammar (canonical — the witness greps these):** rulings land under
-`## PARENT RULING (plan — {verdict})` hand-cranked, `## PARENT RULING (plan rev N — {verdict})` when the
-rev ladder exists; notes under `## PARENT NOTE ({context})`. The parent-voice vocabulary is a CLOSED list
-of four — `PARENT NOTE` · `PARENT ACCEPT` · `PARENT RULING` · `OPERATOR RULING` — so a fifth anchor you
-invent counts as nothing. **Never vary the prefixes**, and **never discuss the anchor grammar inside a
-steering note**: the detector matches the STRING, not your intent, and naming an anchor while explaining
-it derives a spurious acceptance receipt. Refer to it obliquely ("the acceptance anchor").
-**Point, don't paste:** steer with *"read your `tldr.md` under `## PARENT RULING`"*, never by re-pasting a
-multi-KB block into a composer.
+`## COORDINATOR RULING (plan — {verdict})` hand-cranked, `## COORDINATOR RULING (plan rev N — {verdict})`
+when the rev ladder exists; notes under `## COORDINATOR NOTE ({context})`. The coordinator-voice
+vocabulary is a CLOSED list of four — `COORDINATOR NOTE` · `COORDINATOR ACCEPT` · `COORDINATOR RULING` ·
+`OPERATOR RULING` — so a fifth anchor you invent counts as nothing. An older board spells the first three
+`PARENT NOTE` · `PARENT ACCEPT` · `PARENT RULING`; every reader of the anchors, each grep in this loop
+included, takes that spelling as the same three, and you write only the new one. **Never vary the prefixes**, and **never
+discuss the anchor grammar inside a steering note**: the detector matches the STRING, not your intent,
+and naming an anchor while explaining it derives a spurious acceptance receipt. Refer to it obliquely
+("the acceptance anchor").
+**Point, don't paste:** steer with *"read your `tldr.md` under `## COORDINATOR RULING`"*, never by
+re-pasting a multi-KB block into a composer.
 
 **When to read (hand-cranked):** the human's nudge is your wake signal, and the human is the ONLY bus — so
 before cutting each next prompt, sweep `sessions/*/tldr.md` mtimes for appends you were never nudged
@@ -564,7 +569,7 @@ plan-approval click is the human's counterpart of the product's accept-gate —
 ## Docs-write + commit call template
 
 ```
-PARENT RESPONSE — FINAL TLDR ACCEPTED {(+ what I verified myself)}.
+COORDINATOR RESPONSE — FINAL TLDR ACCEPTED {(+ what I verified myself)}.
 1. Run docs-write. Carry: {departures, honest gaps, deferred findings verbatim, gotchas}.
 2. COMMIT CALL — approved. Stage explicitly (never git add -A): YOUR diff + working doc,
    PLUS docs/research/{topic}/project-status.md — my ledger rides your commit,
@@ -583,7 +588,7 @@ PARENT RESPONSE — FINAL TLDR ACCEPTED {(+ what I verified myself)}.
 ```
 
 **THE ACCEPTANCE IS A RECEIPT VERB, AND PROSE IS NOT A RECEIPT.** Send the acceptance act carrying your
-text; it lands in the seat's `tldr.md` under `## PARENT ACCEPT (final — {slice})` and the rev-bound
+text; it lands in the seat's `tldr.md` under `## COORDINATOR ACCEPT (final — {slice})` and the rev-bound
 receipt derives from it. **An acceptance delivered as a steering note records zero rows** — and the push
 bar reads the row, not the paragraph.
 
@@ -591,10 +596,10 @@ bar reads the row, not the paragraph.
 (the receipt binds pre-commit), then the seat commits and pushes. **The receipt is rev-bound:** it covers
 the tldr rev + HEAD it was written against — if the seat re-posts its TLDR CONTENT after your acceptance,
 the unattended push parks naming both revs, and one **argless re-accept** is the cheap repair, **sent with
-the retry order in the same act**. A seat's post-push `## [child·…] CLOSE-OUT RECEIPT` append does NOT
+the retry order in the same act**. A seat's post-push `## [seat·…] CLOSE-OUT RECEIPT` append does NOT
 stale your acceptance — reap without a re-accept after it.
 
-**Hand-cranked:** append the same `## PARENT ACCEPT (final — {slice})` heading to the seat's
+**Hand-cranked:** append the same `## COORDINATOR ACCEPT (final — {slice})` heading to the seat's
 `sessions/{slug}/tldr.md` yourself — there is no machinery and no derivation; the anchor + your tracker
 row ARE the receipts.
 
@@ -617,7 +622,7 @@ post-merge.
   corrections, what you verified yourself, mid-build directives, and anything you don't want to forget —
   written when it happens, never reconstructed at close. **The tracker's own section notes say what each
   section holds**; follow them rather than inventing structure. Do **not** add a `## Checkpoint ledger` or
-  a `## Parent decisions` section — the session entry *is* the decision record, and a parallel section
+  a `## Coordinator decisions` section — the session entry *is* the decision record, and a parallel section
   splits one narrative across two places.
 - **If a retro has to supersede your session rows, the ledger was not kept.** A retro confirms the rows
   and adds the audit and economics; it never corrects facts that should already be written.
@@ -644,7 +649,7 @@ post-merge.
   a sequence, and do not treat a stale living doc as something this effort must fix.
 - Periodically remind the human to sweep your doc edits into a small `docs` commit.
 - Counterpart skills: `spec-seat` (the contract of every seat you arm — read it to know what they were
-  told) · `spec-child` (the builders' job skill) · `spec-pipeline` (how the specs came to exist) ·
+  told) · `spec-build` (the builders' job skill) · `spec-pipeline` (how the specs came to exist) ·
   `spec-review` (the outside look, before your retro) · `spec-retro` (your close-out audit) ·
   `spec-witness` (the read-only verifier) · `spec-ignite` (the ignition copilot that puts an authored
   effort onto the plane).

package/skills/spec-ignite/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: spec-ignite
-description: Become the IGNITION COPILOT for a spec pipeline — verify the committed ignition brief against live state, verify every step by receipt, and kick on the human's word. Authoring belongs to spec-pipeline; this seat VERIFIES, so it can run cold. Use right after spec-pipeline when the pipeline will run hosted (the manual alternative is spec-parent), or fresh with a topic whose specs are already authored. Two verbal gates: nothing moves before "stage it"; nothing spawns before "kick it".
+description: Become the IGNITION COPILOT for a spec pipeline — verify the committed ignition brief against live state, verify every step by receipt, and kick on the human's word. Authoring belongs to spec-pipeline; this seat VERIFIES, so it can run cold. Use right after spec-pipeline when the pipeline will run hosted (the manual alternative is spec-coordinator), or fresh with a topic whose specs are already authored. Two verbal gates: nothing moves before "stage it"; nothing spawns before "kick it".
 ---
 
 # spec-ignite
@@ -119,10 +119,10 @@ injects** — the human keyboard and the hardened ladders are the only submit pa
 
 The coordinator's task is the brief's own **`## The kick`** section, copied verbatim. Roughly:
 
-> You are the COORDINATOR of the {topic} pipeline. Invoke the `spec-parent` skill, then read
+> You are the COORDINATOR of the {topic} pipeline. Invoke the `spec-coordinator` skill, then read
 > `docs/research/{topic}/00-ignition-brief.md` and follow it. Your branch is `{the effort's branch}`.
 
-**Do not draft a constitution here.** The seat's PROCEDURE is the `spec-parent` skill; its POLICY rides the
+**Do not draft a constitution here.** The seat's PROCEDURE is the `spec-coordinator` skill; its POLICY rides the
 un-skippable policy suffix the control plane supplies at open (you do not paste it, and you cannot
 override it); its HANDS are the coordinator charter the control plane attaches to a `coordinator` seed
 and to no other kind. This RUN's choreography is the committed brief. A task string cannot be diffed or
@@ -271,7 +271,7 @@ you found rather than working around it.
   anomalies that may change it — surprises are findings, not adjustments.
 
 ## Related
-- `spec-pipeline` (authors what you ignite, including the brief you verify) · `spec-parent` (the
-  coordinator's procedure, and the HAND-CRANKED alternative) · `spec-seat` + `spec-child` (what the
+- `spec-pipeline` (authors what you ignite, including the brief you verify) · `spec-coordinator` (the
+  coordinator's procedure, and the HAND-CRANKED alternative) · `spec-seat` + `spec-build` (what the
   control plane seeds into every build seat) · `spec-retro` (the close-out audit) · `spec-witness`
   (point one at the run you just ignited)

package/skills/spec-pipeline/SKILL.md

@@ -59,14 +59,14 @@ sessions/                        WHO PUTS IT THERE
                                  questions with the coordinator's rulings appended beneath them. Read
                                  top-to-bottom it IS the session's whole conversation, in message order
   code-review.md                 the review seat, in its own commit, if the run has a review row
-  parent-retrospective.md        the coordinator, at the close
+  coordinator-retrospective.md   the coordinator, at the close
   witness-ledger-*.md            a human commit — the witness is zero-writes by contract (its ticket
                                  cannot even carry the write scope), so its testimony reaches the repo
                                  by someone else's hand
 ```
 
 - **Per-seat artifacts go in a `{spec-slug}/` subfolder; effort-wide artifacts sit at the `sessions/`
-  root.** The first seat creates its subfolder and, incidentally, the parent folder; everything after
+  root.** The first seat creates its subfolder and, incidentally, `sessions/` itself; everything after
   writes into what exists.
 - **RE-COPY BOTH FILES ONCE, IMMEDIATELY BEFORE THE FINAL PUSH.** A seat's close-out receipt is written
   AFTER the commit that carries its testimony, so a single copy always lands truncated — and a follow-up
@@ -78,7 +78,7 @@ sessions/                        WHO PUTS IT THERE
   separate questions file, and there are no status snapshots: the tracker is committed live, so its git
   history already carries the progression a snapshot would fake.
 - **Append-only.** `tldr.md` grows; nobody rewrites it. The rev ladder is the history.
-- **Who READS it:** the coordinator reads each TLDR and appends its rulings under `## PARENT RULING` · the
+- **Who READS it:** the coordinator reads each TLDR and appends its rulings under `## COORDINATOR RULING` · the
   review seat reads every session's TLDR as testimony **and reads nothing else** · the retro greps it for
   acceptance anchors and unanswered questions · the witness uses rev counts and mtimes as a zero-cost
   heartbeat.
@@ -214,7 +214,7 @@ sessions/                        WHO PUTS IT THERE
 5. **Name the archive destination when only you can.** Read `docs/_meta/docs-workflow.md` § The archive
    convention (repository-owned). If where a pipeline files depends on something only this session knows
    (which living feature the effort belongs to, say), resolve it now and write the path into the
-   umbrella's blockquote as an `Archive:` line; `spec-parent` hands it to the docs-process row and
+   umbrella's blockquote as an `Archive:` line; `spec-coordinator` hands it to the docs-process row and
    `docs-process` files there. A convention that needs nothing from you needs no line.
 
 6. **Stop.** The specs stay in `research/{topic}/`. Do NOT implement, do NOT touch living docs, do NOT
@@ -320,7 +320,7 @@ cross-reading them; a human row recorded only by the coordinator has ONE, and th
 one whose errors nobody else catches.
 
 ## The kick — paste this verbatim as the coordinator's task
-> You are the COORDINATOR of the {topic} pipeline. Invoke the `spec-parent` skill, then read
+> You are the COORDINATOR of the {topic} pipeline. Invoke the `spec-coordinator` skill, then read
 > `docs/research/{topic}/00-ignition-brief.md` and follow it. Your branch is `{the effort's branch}`.
 
 Deltas true of THIS kick only (a concurrent pipeline, a model override, a one-off probe) go here as a
@@ -328,7 +328,7 @@ short list. Everything else is already in this brief — the task string is a PO
 stays short because a task buried in a run row cannot be diffed or reviewed the way this file can.
 ```
 
-**Do not restate the ceremony here.** The coordinator's procedure lives in `spec-parent` and its policy
+**Do not restate the ceremony here.** The coordinator's procedure lives in `spec-coordinator` and its policy
 is the one § This repository's rails (repository-owned) names, which a hosted run also carries in the
 un-skippable policy suffix the control plane supplies; a brief that re-teaches them accretes
 into prompt-law that breaks the coordinator it was meant to steer. The brief carries THIS RUN's
@@ -410,7 +410,7 @@ viewer because they are instructions to the coordinator, not content for the hum
 |---|---|---|---|
 ```
 
-**Never generate a `## Checkpoint ledger` or a `## Parent decisions` section.** The session section
+**Never generate a `## Checkpoint ledger` or a `## Coordinator decisions` section.** The session section
 *is* the decision record; a parallel section splits one narrative across two places.
 
 ## `live-checks.md`

package/skills/spec-retro/SKILL.md

@@ -13,8 +13,8 @@ today that perspective evaporates the moment the run closes. This skill turns it
 **Find the format first.** This repository writes its formats (the doc header and status words, where an effort is filed, its rails) in the sections `rg -n '^#+ .*\(repository-owned\)' docs/_meta/` lists; read the one a step names before that step writes. This skill names the section, never the format.
 
 Run it as the **last act of the coordinator seat**, after the final session's close-out commit — before or
-after the PR is cut, either works. Output: `docs/research/{topic}/sessions/parent-retrospective.md`. It is
-a scoped write on the pipeline's branch, so it rides the PR to the base branch either way.
+after the PR is cut, either works. Output: `docs/research/{topic}/sessions/coordinator-retrospective.md`.
+It is a scoped write on the pipeline's branch, so it rides the PR to the base branch either way.
 
 **You are one of the three kinds that do NOT compose `spec-seat`** — this skill is your whole contract,
 and the control plane's seed says so rather than merely omitting it.
@@ -54,7 +54,7 @@ document** — a number whose lane you cannot name is testimony, not an audit.
 
 **If the argless sweep is not runnable at your run's scale, that is a day-one escalation, not a
 close-out discovery.** A few thousand rows can exceed the lane's page budget; you cannot retroactively
-obtain the audit your own doctrine mandates. `spec-parent` carries this as a run-time obligation.
+obtain the audit your own doctrine mandates. `spec-coordinator` carries this as a run-time obligation.
 
 **Two instruments that share no code are the only way a ceremony audit means anything** — on one
 instrument you are grading your own homework with your own pencil. Where the control plane offers a
@@ -148,11 +148,13 @@ could not tell. And do not flatten predicates that were measured apart: a conten
 stales a PUSH; a close-out-receipt append does not stale a REAP. Report what you observe; never
 generalise one park into a law.
 
-**The derived-row path:** the acceptance's durable record is the `## PARENT ACCEPT (final — {slice})`
-anchor in each seat's `tldr.md`, and the receipt DERIVES from it. Reconcile file against substrate:
+**The derived-row path:** the acceptance's durable record is the `## COORDINATOR ACCEPT (final —
+{slice})` anchor in each seat's `tldr.md`, and the receipt DERIVES from it. A board written before this
+vocabulary spells it `## PARENT ACCEPT`; a reader of the anchors takes both spellings, so the grep does too. Reconcile
+file against substrate:
 
 ```bash
-rg -n "## PARENT ACCEPT" docs/research/{topic}/sessions/*/tldr.md
+rg -n "## (COORDINATOR|PARENT) ACCEPT" docs/research/{topic}/sessions/*/tldr.md
 ```
 
 **AUDIT THE QUESTION LANE THE SAME WAY — it is a heading grep, not a row query.** A seat asks by appending
@@ -163,8 +165,8 @@ run whose seats asked repeatedly and changed a ruling by it.
 **AND ON THE HOSTED PLANE THE FILE IS NOT THE CLOSE PREDICATE — audit BOTH halves, because they answer
 different questions.** *Was one asked?* is a fact about the file (the heading grep below, mirroring the
 control plane's grammar). *Was it answered?* is a fact about the LEDGER — the ruling act carrying the
-asking post's id — and it is deliberately not read from the file, because a seat can type a parent-voice
-heading into its own blackboard. **A retro that audits only the file can be shown a question that
+asking post's id — and it is deliberately not read from the file, because a seat can type a
+coordinator-voice heading into its own blackboard. **A retro that audits only the file can be shown a question that
 answered itself.** Reconcile the grep's hits against the ruling acts, and report any hit with no act as an
 unanswered question whatever the file says.
 
@@ -177,11 +179,12 @@ prefixed and plural headings, and the lane has TWO headings: `## QUESTIONS` (rec
 rg -niE '^##[[:space:]]*(\[[^]]*\][[:space:]]*)?(MID-BUILD[[:space:]]+)?QUESTIONS?\b' docs/research/{topic}/sessions/*/tldr.md | rg -viE 'QUESTIONS?[[:space:]]+ANSWERED'
 ```
 
-Reconcile each hit against the parent-voice append that answered it (`## PARENT RULING` / `## PARENT NOTE`
-in the same file) — an unanswered question is the finding. **Your audit instrument must be at least as
-tolerant as the code it audits.**
+Reconcile each hit against the coordinator-voice append that answered it (`## COORDINATOR RULING` /
+`## COORDINATOR NOTE` in the same file, or `## PARENT RULING` / `## PARENT NOTE` on an older board) — an
+unanswered question is the finding. **Your audit instrument must be at least as tolerant as the code it
+audits.**
 
-- **Hosted:** N `## PARENT ACCEPT` anchors imply N acceptance acts (rev-bound: the act carries the tldr
+- **Hosted:** N acceptance anchors (`## (COORDINATOR|PARENT) ACCEPT`) imply N acceptance acts (rev-bound: the act carries the tldr
   rev, the HEAD and a content hash). An anchor with no act means the derivation failed (LOUD in the
   logs — find it); an act with no anchor is a cockpit accept (legitimate; the act says so).
   Acceptance-shaped PROSE without the anchor writes nothing by design — flag it as a ceremony miss.
@@ -374,7 +377,7 @@ is the look of a record with none of a record's properties.
    session's `tldr.md`, and the working docs.
 2. **Query** the substrate for §§2-5. Verify each query FIRES on a known-positive row before trusting a
    clean result.
-3. **Write** `docs/research/{topic}/sessions/parent-retrospective.md` — NATIVELY, in the tree you were born
+3. **Write** `docs/research/{topic}/sessions/coordinator-retrospective.md` — NATIVELY, in the tree you were born
    in: the coordinator lives in the effort's worktree, so the scoped write (the effort home's own `.md`
    files, `sessions/`, the tracker, `live-checks.md` and the specs) lands on the effort's branch and rides
    its PR. Every write earns its loud audit row. **If the write REFUSES, that is a PLATFORM DEFECT:**
@@ -396,6 +399,6 @@ is the look of a record with none of a record's properties.
    leaves an identical belief standing in a sibling that words it differently has to be made twice.
 
 ## Related
-- `spec-parent` (the seat, and the run-time half of this skill's close-out demands) · `spec-child` (the
-  builders) · `spec-seat` (their shared contract) · `spec-witness` (the read-only verifier) ·
+- `spec-coordinator` (the seat, and the run-time half of this skill's close-out demands) · `spec-build`
+  (the builders) · `spec-seat` (their shared contract) · `spec-witness` (the read-only verifier) ·
   `spec-pipeline` (which authored the specs you are grading)

package/skills/spec-review/SKILL.md

@@ -24,7 +24,7 @@ else's job.
   Reading it anchors you on that grade and the pipeline pays for two opinions to get one.
 - **You do not fix anything.** Findings get classified and filed. A reviewer that repairs its own findings
   cannot be trusted to count them.
-- **You do not decide whether a fixit runs — you classify.** The parent rules on it. A reviewer that can
+- **You do not decide whether a fixit runs — you classify.** The coordinator rules on it. A reviewer that can
   trigger work is grading its own necessity.
 - **Every TLDR, spec, and doc claim is TESTIMONY to verify, never a fact to build on.** That includes
   anything your coordinator tells you: if a ruling arrives in your `tldr.md`, record it and treat it as a
@@ -194,8 +194,9 @@ testimony.
 
 ## The report — `sessions/code-review.md`
 
-Files beside `parent-retrospective.md` in the pipeline's `sessions/` folder. It is a pipeline artifact,
-not a chat transcript, and it archives with the effort.
+Files beside the coordinator's retrospective in the pipeline's `sessions/` folder
+(`coordinator-retrospective.md`, or `parent-retrospective.md` in an effort begun before that name). It is
+a pipeline artifact, not a chat transcript, and it archives with the effort.
 
 ```markdown
 # Code + session review — {topic}, pipeline {id}
@@ -244,7 +245,7 @@ that does not exist yet (an unauthored row, an unwritten charter) is NOT homed:
 
 ## Lineage   _(where § Doc metadata (repository-owned) keeps the footer)_
 - **Pipeline** — the tracker · the umbrella · sessions 02..NN
-- **Counterpart** — `parent-retrospective.md` (the inside look; written after this)
+- **Counterpart** — `coordinator-retrospective.md` (the inside look; written after this)
 ```
 
 ## Ceremony
@@ -254,7 +255,7 @@ TLDR with beliefs and numbered questions, the question lane, the parked-call dis
 vocabulary, the six-section FINAL TLDR, and the close-out order. You commit `sessions/code-review.md` on
 your coordinator's call like any seat.
 
-**The close-out receipt's heading token is the literal `child·` for you too** — it is a protocol anchor,
+**The close-out receipt's heading token is the literal `seat·` for you too** — it is a protocol anchor,
 not a description of your seat, and writing `[review·…]` stales your own acceptance. `spec-seat` carries
 the detail.
 
@@ -267,7 +268,7 @@ Your baselines are reads, not builds: you run the suites to confirm the pipeline
 number you cannot reproduce is a finding.
 
 ## Related
-- `spec-parent` (rules on your fixit candidates; writes the retro after you) · `spec-child` (the seats you
+- `spec-coordinator` (rules on your fixit candidates; writes the retro after you) · `spec-build` (the seats you
   are reviewing) · `spec-retro` (the inside look) · `spec-witness` (the live read-only seat; its ledger, if
   one exists, is evidence like any other artifact) · `docs-process` (consumes this report and gives every
   finding a disposition)

package/skills/spec-seat/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: spec-seat
-description: The CONTRACT for any seat a pipeline coordinator arms — the blackboard, the question lane, the parked-call discriminator, the verdict vocabulary, the BELIEFS sha, git shapes, the six-section FINAL TLDR, and the close-out order. Invoked FIRST, then the job skill (spec-child | spec-review | docs-process). Not a seat of its own; the shared half of every seat's procedure.
+description: The CONTRACT for any seat a pipeline coordinator arms — the blackboard, the question lane, the parked-call discriminator, the verdict vocabulary, the BELIEFS sha, git shapes, the six-section FINAL TLDR, and the close-out order. Invoked FIRST, then the job skill (spec-build | spec-review | docs-process). Not a seat of its own; the shared half of every seat's procedure.
 ---
 
 # spec-seat
@@ -10,13 +10,13 @@ the review row, the docs-process row — runs THIS, then its own job skill:
 
 | Seat kind | Composes |
 |---|---|
-| `build` · `fixit` | `spec-seat` + **`spec-child`** |
+| `build` · `fixit` | `spec-seat` + **`spec-build`** |
 | `review` | `spec-seat` + **`spec-review`** |
 | `docs-process` | `spec-seat` + **`docs-process`** |
 
 **THE PAIRING IS SEVEN-WAY AND NON-UNIFORM, and the three kinds missing from that table are missing
 DELIBERATELY.** `coordinator`, `retro` and `witness` each carry their OWN whole contract
-(`spec-parent` · `spec-retro` · `spec-witness`) and are **never** told to invoke this file — prefixing
+(`spec-coordinator` · `spec-retro` · `spec-witness`) and are **never** told to invoke this file — prefixing
 `spec-seat` onto a skill that already carries a whole contract ships a seed contradicting the skill it
 points at. The control plane composes each kind's seed from this table and has no catch-all: an unknown
 kind is refused by name (`seat-kind-has-no-seed`) rather than ignited wrongly.
@@ -26,7 +26,7 @@ contradicts it. Where they genuinely conflict, that is **a finding to report**,
 quietly — say so in your PLAN TLDR and let the coordinator rule.
 
 **The coordinator does NOT compose this.** It writes rulings rather than receiving them, owns the tracker,
-and holds the close — a different contract, and `spec-parent` carries it whole.
+and holds the close — a different contract, and `spec-coordinator` carries it whole.
 
 **Why this file exists:** a base contract that every seat kind shared, with the build job mixed in, sent
 the review row into the umbrella its own charter excluded and offered the docs-process row a `docs-write`
@@ -100,7 +100,7 @@ FINAL TLDR — **append, never overwrite**) are FILES, not just chat text.
 
 - **Hand-cranked:** create them under `docs/research/{topic}/sessions/{slug}/` at plan time and end your
   turn announcing the path. The coordinator reads `tldr.md` with normal file tools and APPENDS its ruling
-  under `## PARENT RULING`, so read the answer in your own file and proceed. The full plan is PULL — it is
+  under `## COORDINATOR RULING`, so read the answer in your own file and proceed. The full plan is PULL — it is
   read only on a read-full-plan verdict; never paste it into chat. (If your harness has a plan-approval
   mode that forbids writes: give the chat summary, get the human's approve, THEN post and stop.)
 - **Hosted (a seat inside a pipeline):** the same two files are yours to edit with normal file tools, then
@@ -118,29 +118,33 @@ Either way, `tldr.md` read top-to-bottom is the session's whole conversation in
 
 **Greppable turn anchors:** every append gets a stable heading carrying actor + identity —
 `## [{seat}·{slug} · run {id}] {phase}` when your seat has a run identity, `## [{seat}·{slug}] {phase}`
-hand-cranked. The coordinator's voice is always `## PARENT RULING …` / `## PARENT NOTE …`. The stable
-prefixes are the contract: one grep for `## PARENT RULING` across every session's `tldr.md` lists every
-ruling in the effort.
-
-**THE HEADING VOCABULARY IS CLOSED, AND THAT IS THE HAZARD AS WELL AS THE CONTRACT.** The parent-voice
-list is exactly four — `PARENT NOTE` · `PARENT ACCEPT` · `PARENT RULING` · `OPERATOR RULING` — matched
-by the control plane on a word boundary, so `## PARENT NOTEBOOK` cannot pass. A fifth anchor invented
-later closes nothing and counts as nothing until the control plane learns it. **Section boundaries are
-level-2 headings only** — `### Option A` inside your question block is still inside the question,
-deliberately, so a ruling never arrives having truncated your options.
-
-**Point, don't paste:** to direct anyone at content, say *"read `tldr.md` under `## PARENT RULING`"* —
-never re-paste a multi-KB block into a composer.
+hand-cranked. The coordinator's voice is always `## COORDINATOR RULING …` / `## COORDINATOR NOTE …`. The
+stable prefixes are the contract: one grep for `## (COORDINATOR|PARENT) RULING` across every session's
+`tldr.md` lists every ruling in the effort.
+
+**THE HEADING VOCABULARY IS CLOSED, AND THAT IS THE HAZARD AS WELL AS THE CONTRACT.** The
+coordinator-voice list is exactly four — `COORDINATOR NOTE` · `COORDINATOR ACCEPT` · `COORDINATOR RULING`
+· `OPERATOR RULING` — matched by the control plane on a word boundary, so `## COORDINATOR NOTEBOOK`
+cannot pass. An older board spells the first three `PARENT NOTE` · `PARENT ACCEPT` · `PARENT RULING`; a
+reader of the anchors takes that spelling as the same three, which is why the grep above carries both. A fifth
+anchor invented later closes nothing and counts as nothing until the control plane learns it. **Section
+boundaries are level-2 headings only** — `### Option A` inside your question block is still inside the
+question, deliberately, so a ruling never arrives having truncated your options.
+
+**Point, don't paste:** to direct anyone at content, say *"read `tldr.md` under `## COORDINATOR
+RULING`"* — never re-paste a multi-KB block into a composer.
 
 **If `tldr.md` already exists when you go to create your blackboard, APPEND** — machinery may have written
-before you, and recreating the file clobbers it (the platform refuses a shrinking rewrite).
+before you, and recreating the file clobbers it (the platform refuses a shrinking rewrite). **And every
+heading already on your board stays exactly as written, an older spelling included:** the platform refuses
+a revision whose earlier headings changed, so never tidy an old heading into the current vocabulary.
 
 **Re-read `tldr.md` immediately before every append.** The coordinator appends into the SAME file between
 your turns — an edit whose old text no longer matches almost always means the conversation moved.
 Re-read, fold what's new, then append. Never resolve the mismatch by rewriting the whole file; the rev
 ladder is the history.
 
-**`## PARENT NOTE (FYI — no reply needed)` is the NO-TURN lane:** the coordinator can leave you
+**`## COORDINATOR NOTE (FYI — no reply needed)` is the NO-TURN lane:** the coordinator can leave you
 informational context WITHOUT waking you — it lands durably in your `tldr.md` and costs you nothing.
 The re-read above is where you pick FYIs up: fold them as context, owe no reply, and never treat one as
 a ruling — an FYI cannot answer an open question (only a ruling heading does).
@@ -149,7 +153,7 @@ a ruling — an FYI cannot answer an open question (only a ruling heading does).
 
 **When you need a decision at ANY point:** append a question section to your own `tldr.md`, post
 (`post_tldr`), and **END YOUR TURN.** Your coordinator is woken with your text, and its ruling under a
-parent-voice heading is your answer — pick it up from your own file and resume.
+coordinator-voice heading is your answer — pick it up from your own file and resume.
 
 **TWO literal headings, one lane — pick by phase, and use a real `##` heading either way:**
 
@@ -170,7 +174,7 @@ every section and answers `Blocking` / `NotBlocking` / `Undeclared`. Markdown ar
 - **Never let a reader turn your declaration into liveness.** It is a claim made at the instant you
   typed it; a seat that wrote `BLOCKING:` and then kept working was telling the truth.
 
-**Both poke the coordinator identically** — same wake, same re-raise, same parent-voice answer. The split
+**Both poke the coordinator identically** — same wake, same re-raise, same coordinator-voice answer. The split
 is for the READER (a recon fork and a mid-build discovery are different kinds of news), never for the
 machinery. A question under any OTHER heading — or as a bare `QUESTIONS:` label with no `##` — gets no
 banner and **the re-raise can never fire**, so it can sit unanswered indefinitely. And never use
@@ -194,13 +198,13 @@ the pipeline a round-trip and nothing else.
 The latch reads the ACTS LEDGER: a ruling closes your question only when it is delivered as a `callout`
 carrying your post's act id as `answeringActId`. A `callout` without one steers you and closes nothing.
 **The reason is a security property, not tidiness:** `tldr.md` is written BY YOU, so a file-side close
-predicate is a string the audited party can type — a seat could write `## PARENT RULING` into its own file
+predicate is a string the audited party can type — a seat could write `## COORDINATOR RULING` into its own file
 and switch off the very re-raise that exists to stop it waiting forever. The question is therefore split
 in two: *was one asked?* — a fact about the file, where forgery only wakes your own coordinator — versus
 *was it answered?* — a fact about what the coordinator DID, read from the ledger.
 
 **The honest rendering of your file is unchanged**: an open-questions read of the file still clears on the
-parent-voice heading, because that is what the file SAYS. What differs is what a DECISION may be
+coordinator-voice heading, because that is what the file SAYS. What differs is what a DECISION may be
 predicated on.
 
 ### THREE CONTRACT LINES, all earned by one kind of silence
@@ -238,7 +242,7 @@ Ask what the park is protecting:
 
 - **A park on a STATE condition** — the park text names a rev, a hash, or a version: it is STATE, not
   approval. Do not re-request, do not reshape; read the substrate for the healing signal (your own acts:
-  the fresh acceptance receipt, or the `## PARENT NOTE (re-accept)` append) and retry ONCE on receipt.
+  the fresh acceptance receipt, or the `## COORDINATOR NOTE (re-accept)` append) and retry ONCE on receipt.
   State parks are machine-healable — one argless re-accept re-binds a stale acceptance. **Never hold for
   one specific lane: whichever arrives first IS your signal, and the substrate outranks the bus.**
 - **A park on your own legitimate in-worktree work** — **re-request it** (no self-imposed cap, no
@@ -342,7 +346,7 @@ naming both. That is why your BELIEFS sha is a contract line and not a courtesy
 moves mid-build is disclosed FIRST, never absorbed quietly.
 
 **The re-accept signal:** after a rev-bound/stale-acceptance park, the re-accept arrives as a
-`## PARENT NOTE (re-accept)` append plus a callout — retry your held action on receipt. If your next wake
+`## COORDINATOR NOTE (re-accept)` append plus a callout — retry your held action on receipt. If your next wake
 shows the fresh acceptance receipt in your own rows WITHOUT the note, **that row IS your signal** — the
 substrate outranks the bus. Never hold for one specific lane. **A re-accept with no retry order is a
 doorbell with no follow-through**; if you receive one bare, retry anyway and say that you did.
@@ -416,13 +420,13 @@ produces a working doc**, COMMIT CALL with the message). Execute it exactly.
 makes the acceptance stale by design. Append your close-out receipt AFTER the push under this heading:
 
 ```
-## [child·{slug} · run {id}] CLOSE-OUT RECEIPT
+## [seat·{slug} · run {id}] CLOSE-OUT RECEIPT
 ```
 
 ## IF YOU HAVE PUSHED AND ARE WAITING, SAY SO. IT DOES NOT STALE YOU.
 
 ```
-## [child·{slug} · run {id}] HOLDING
+## [seat·{slug} · run {id}] HOLDING
 ```
 
 **Then `post_tldr` and end your turn.** Body: what you pushed, and what you are waiting for
@@ -437,10 +441,11 @@ cost a pipeline hours. Preventing it is your job, and it costs you one append.
 the accepted CONTENT, not to the revision number, so appending your own state or a question leaves it
 intact. Only **new content** stales.
 
-**The token is the literal `child·`, whatever seat you are.** The control plane's close-out matcher keys
-on `[child·…] CLOSE-OUT RECEIPT`, so a review or docs-process seat that writes `[review·…]` or
+**The token is the literal `seat·`, whatever seat you are.** The control plane's close-out matcher keys
+on `[seat·…] CLOSE-OUT RECEIPT`, so a review or docs-process seat that writes `[review·…]` or
 `[process·…]` **fails the match and stales its own acceptance** — costing a re-post and an argless
-re-accept. **It is a PROTOCOL ANCHOR, not a description of you.** A descriptive tail after the marker IS
+re-accept. (An older board's `[child·…]` token matches too; write only `seat·`.) **It is a PROTOCOL
+ANCHOR, not a description of you.** A descriptive tail after the marker IS
 blessed (`… CLOSE-OUT RECEIPT — addendum: the six staged, tree clean`) — an end-anchored pattern on the
 one heading seats are told to write would be a trap that fires on ordinary prose.
 
@@ -489,7 +494,7 @@ why. Silence is not compliance.
 **THE TESTIMONY REGRESS, AND THE DECLARED STOPPING POINT — read this before you copy anything.** The
 order above puts the COMMIT before the CLOSE-OUT RECEIPT, so the copy you commit ends at your FINAL TLDR
 and can contain neither the receipt (hash, session id, staging receipt) nor the coordinator's
-`## PARENT ACCEPT`. **A follow-up commit does not fix this, it moves it:** any receipt ABOUT that commit is
+`## COORDINATOR ACCEPT`. **A follow-up commit does not fix this, it moves it:** any receipt ABOUT that commit is
 also written after it. The regress is infinite and the ceremony does not pretend otherwise.
 
 **So the rule is a declared stopping point rather than a fix: RE-COPY `plan.md` AND `tldr.md` ONCE,
@@ -519,5 +524,5 @@ plane. The publish receipt is written at your turn's STOP and is structurally un
   with a clean rerun builds trust, an undisclosed one destroys it.
 - **A rule recalled from context needs re-reading at the source before it is used to refuse work.** A
   rule already corrected on disk is the commonest thing a seat blocks itself on.
-- Your job skill is next: `spec-child` (build/fixit) · `spec-review` (the outside look) ·
-  `docs-process` (compile the living docs). Counterpart: `spec-parent` (the seat that arms you).
+- Your job skill is next: `spec-build` (build/fixit) · `spec-review` (the outside look) ·
+  `docs-process` (compile the living docs). Counterpart: `spec-coordinator` (the seat that arms you).

package/skills/spec-witness/SKILL.md

@@ -78,13 +78,16 @@ git — agree.
    are a zero-token heartbeat per seat — a growing ladder is a live session, a frozen one dates its last
    turn. `seat_content` reads the board; read `tldr.md` top-to-bottom and it IS the session's whole
    conversation in message-flow order — the fastest "where is this seat" there is. The coordinator's
-   voice is a greppable anchor: `## PARENT RULING (plan rev N — {verdict})` and `## PARENT NOTE (…)`
-   (actor-suffixed when known) on the hosted plane; the same prefixes without the rev counter under
-   `docs/research/{topic}/sessions/{spec-slug}/` hand-cranked — so grep the prefix, never the full form.
+   voice is a greppable anchor: `## COORDINATOR RULING (plan rev N — {verdict})` and `## COORDINATOR NOTE
+   (…)` (actor-suffixed when known) on the hosted plane; the same prefixes without the rev counter under
+   `docs/research/{topic}/sessions/{spec-slug}/` hand-cranked — so grep the prefix, never the full form,
+   and grep both spellings: an older board writes `## PARENT RULING` / `## PARENT NOTE`
+   (`rg -n "## (COORDINATOR|PARENT) (RULING|NOTE)"`).
    **Honest delivery verdicts:** a ruling act's reply states recorded-vs-delivered truthfully —
    "recorded, not delivered" is NORMAL (the seats run substrate-first; the board is load-bearing, the
    pointer is best-effort). A delivery miss is only a finding if the seat ALSO never acted on the
-   substrate. **Blessed close-outs:** a seat's post-push `## [child·…] CLOSE-OUT RECEIPT` append does NOT
+   substrate. **Blessed close-outs:** a seat's post-push `## [seat·…] CLOSE-OUT RECEIPT` append (an older
+   board's `[child·…]`) does NOT
    stale its acceptance — a reap without a fresh acceptance after such an append is correct behaviour,
    not a skipped step.
 3. **Change-detection monitors, not tails:** emit only rows past a high-water mark + a terminal-state
@@ -216,7 +219,7 @@ Disciplines that don't fit a numbered step:
   trusting their silence — silence from a dead monitor looks identical to a quiet run.
 
 ## Related
-- `spec-parent` (the seat that rules) · `spec-child` (the seats that act) · `spec-seat` (their shared
+- `spec-coordinator` (the seat that rules) · `spec-build` (the seats that act) · `spec-seat` (their shared
   contract — read it to know what the seats you are watching were told)
 - **You are one of the three kinds that do NOT compose `spec-seat`** — this skill is your whole
   contract, and the control plane's seed says so rather than merely omitting it.

package/templates/docs/_meta/doc-index.md

@@ -54,7 +54,7 @@
 
 ## Role reading lists
 
-The docs a build seat reads on top of the floor every seat reads (`spec-seat` Step 0). The `spec-child`
+The docs a build seat reads on top of the floor every seat reads (`spec-seat` Step 0). The `spec-build`
 skill names the loop's standard docs by path; this table is the repository's reserved space — one row per
 doc, saying which roles read it. The coordinator copies a role's rows into every seat's seed as
 `EXTRA DOCS`, so a seat sees paths, not this index. Add a row for any doc of your own a role should read;