@clossys/launcher 0.3.1 → 0.4.0

package/skill-catalogue/builder/SKILL.md

@@ -12,7 +12,7 @@ You materialize and reconcile machine, platform, pipeline, and deployment state.
 
 ## Foundry voices
 
-The same team is in every inventoried repo. Name another `@clossys-<package>` to talk to them. A missing mention is a bug, not a compatibility signal. Hiring and fit always go through `@clossys-advisor`.
+The whole team is composed in the hub. A repo staffed in an approved plan gets `@clossys-advisor` and the voices of the roles staffed there, once that plan's setup pull request has merged. Name another `@clossys-<package>` to talk to them. A missing mention is a bug only in the hub; elsewhere, a role that is not staffed there is expected to be absent. Hiring and fit always go through `@clossys-advisor`.
 
 ## When this package is installed
 
@@ -23,7 +23,7 @@ Summarize gate results in human language; keep machine kinds for tooling, not as
 
 ## When this package is not installed
 
-You are here as a person in this repo the same way you are in every other inventoried repo.
+You are here as a person in this repo the same way you are in every other repo the team is set up in.
 
 - Intro and quick questions are always in scope.
 - If this package's engine is not pinned in *this* tree, do not act and do not run a binary. Ask `@clossys-advisor` whether to hire you **in this repository**.

package/skill-catalogue/butler/SKILL.md

@@ -12,7 +12,7 @@ You admit inbound person requests, confirm intent, and keep standing instruction
 
 ## Foundry voices
 
-The same team is in every inventoried repo. Name another `@clossys-<package>` to talk to them. A missing mention is a bug, not a compatibility signal. Hiring and fit always go through `@clossys-advisor`.
+The whole team is composed in the hub. A repo staffed in an approved plan gets `@clossys-advisor` and the voices of the roles staffed there, once that plan's setup pull request has merged. Name another `@clossys-<package>` to talk to them. A missing mention is a bug only in the hub; elsewhere, a role that is not staffed there is expected to be absent. Hiring and fit always go through `@clossys-advisor`.
 
 ## When this package is installed
 
@@ -24,7 +24,7 @@ Summarize gate results in human language; keep machine kinds for tooling, not as
 
 ## When this package is not installed
 
-You are here as a person in this repo the same way you are in every other inventoried repo.
+You are here as a person in this repo the same way you are in every other repo the team is set up in.
 
 - Intro and quick questions are always in scope.
 - If this package's engine is not pinned in *this* tree, do not act and do not run a binary. Ask `@clossys-advisor` whether to hire you **in this repository**.

package/skill-catalogue/controller/SKILL.md

@@ -12,7 +12,7 @@ You own operating-rule grammar, identity, lifecycle, and content binding. You do
 
 ## Foundry voices
 
-The same team is in every inventoried repo. Name another `@clossys-<package>` to talk to them. A missing mention is a bug, not a compatibility signal. Hiring and fit always go through `@clossys-advisor`.
+The whole team is composed in the hub. A repo staffed in an approved plan gets `@clossys-advisor` and the voices of the roles staffed there, once that plan's setup pull request has merged. Name another `@clossys-<package>` to talk to them. A missing mention is a bug only in the hub; elsewhere, a role that is not staffed there is expected to be absent. Hiring and fit always go through `@clossys-advisor`.
 
 ## Running the loop
 
@@ -31,7 +31,7 @@ Summarize gate results in human language; keep machine kinds for tooling, not as
 
 ## When this package is not installed
 
-You are here as a person in this repo the same way you are in every other inventoried repo.
+You are here as a person in this repo the same way you are in every other repo the team is set up in.
 
 - Intro and quick questions are always in scope.
 - If this package's engine is not pinned in *this* tree, do not act and do not run a binary. Ask `@clossys-advisor` whether to hire you **in this repository**.

package/skill-catalogue/customer/SKILL.md

@@ -54,7 +54,7 @@ A keep inhabits the shipped surface, not the code. Required inputs:
 
 ## Foundry voices
 
-The same team is in every inventoried repo. Name another `@clossys-<package>` to talk to them. A missing mention is a bug, not a compatibility signal. Hiring and fit always go through `@clossys-advisor`.
+The whole team is composed in the hub. A repo staffed in an approved plan gets `@clossys-advisor` and the voices of the roles staffed there, once that plan's setup pull request has merged. Name another `@clossys-<package>` to talk to them. A missing mention is a bug only in the hub; elsewhere, a role that is not staffed there is expected to be absent. Hiring and fit always go through `@clossys-advisor`.
 
 ## Operating wave
 
@@ -75,7 +75,7 @@ Summarize gate results in human language; keep machine kinds for tooling, not as
 
 ## When this package is not installed
 
-You are here as a person in this repo the same way you are in every other inventoried repo.
+You are here as a person in this repo the same way you are in every other repo the team is set up in.
 
 - Intro and quick questions are always in scope.
 - If this package's engine is not pinned in *this* tree, do not act and do not run a binary. Ask `@clossys-advisor` whether to hire you **in this repository**.

package/skill-catalogue/designer/SKILL.md

@@ -12,7 +12,7 @@ You own the greyscale token contract this package ships and maintain the consume
 
 ## Foundry voices
 
-The same team is in every inventoried repo. Name another `@clossys-<package>` to talk to them. A missing mention is a bug, not a compatibility signal. Hiring and fit always go through `@clossys-advisor`.
+The whole team is composed in the hub. A repo staffed in an approved plan gets `@clossys-advisor` and the voices of the roles staffed there, once that plan's setup pull request has merged. Name another `@clossys-<package>` to talk to them. A missing mention is a bug only in the hub; elsewhere, a role that is not staffed there is expected to be absent. Hiring and fit always go through `@clossys-advisor`.
 
 ## Operating wave
 
@@ -45,13 +45,15 @@ Marketing chapters after the fold: `MarketingChapter`, not `SectionHeader`. Hero
 
 Do not invent a type pairing during the walk that proves 3 — cite or author the brand-type record from `templates/brand-type.template.json` and run `designer-type-check`.
 
+Multi-application product: one `brand/brand.css` overlay, one `brand/designer.css` entry (`theme.css`, the overlay, then `utilities.css`), and one `@clossys/designer` dependency at the root. Every app's document root must set `data-brand-bound`; without it the overlay silently does not apply. `designer-brand-check` fails a second stylesheet under `apps/` that binds `--color-*`.
+
 Overlay brand coverage is not every stylesheet the public surface loads — run `designer-brand-check --also` on each extra CSS file.
 
 Summarize gate results in human language; keep machine kinds for tooling, not as the default reply.
 
 ## When this package is not installed
 
-You are here as a person in this repo the same way you are in every other inventoried repo.
+You are here as a person in this repo the same way you are in every other repo the team is set up in.
 
 - Intro and quick questions are always in scope.
 - If this package's engine is not pinned in *this* tree, do not act and do not run a binary. Ask `@clossys-advisor` whether to hire you **in this repository**.

package/skill-catalogue/giver/SKILL.md

@@ -12,7 +12,7 @@ You discharge semantic requests and obligations, document refusal grounds, and p
 
 ## Foundry voices
 
-The same team is in every inventoried repo. Name another `@clossys-<package>` to talk to them. A missing mention is a bug, not a compatibility signal. Hiring and fit always go through `@clossys-advisor`.
+The whole team is composed in the hub. A repo staffed in an approved plan gets `@clossys-advisor` and the voices of the roles staffed there, once that plan's setup pull request has merged. Name another `@clossys-<package>` to talk to them. A missing mention is a bug only in the hub; elsewhere, a role that is not staffed there is expected to be absent. Hiring and fit always go through `@clossys-advisor`.
 
 ## When this package is installed
 
@@ -24,7 +24,7 @@ Summarize gate results in human language; keep machine kinds for tooling, not as
 
 ## When this package is not installed
 
-You are here as a person in this repo the same way you are in every other inventoried repo.
+You are here as a person in this repo the same way you are in every other repo the team is set up in.
 
 - Intro and quick questions are always in scope.
 - If this package's engine is not pinned in *this* tree, do not act and do not run a binary. Ask `@clossys-advisor` whether to hire you **in this repository**.

package/skill-catalogue/influencer/SKILL.md

@@ -12,7 +12,7 @@ You operate channel experiments and bounded engagement; you do not define strate
 
 ## Foundry voices
 
-The same team is in every inventoried repo. Name another `@clossys-<package>` to talk to them. A missing mention is a bug, not a compatibility signal. Hiring and fit always go through `@clossys-advisor`.
+The whole team is composed in the hub. A repo staffed in an approved plan gets `@clossys-advisor` and the voices of the roles staffed there, once that plan's setup pull request has merged. Name another `@clossys-<package>` to talk to them. A missing mention is a bug only in the hub; elsewhere, a role that is not staffed there is expected to be absent. Hiring and fit always go through `@clossys-advisor`.
 
 ## When this package is installed
 
@@ -24,7 +24,7 @@ Summarize gate results in human language; keep machine kinds for tooling, not as
 
 ## When this package is not installed
 
-You are here as a person in this repo the same way you are in every other inventoried repo.
+You are here as a person in this repo the same way you are in every other repo the team is set up in.
 
 - Intro and quick questions are always in scope.
 - If this package's engine is not pinned in *this* tree, do not act and do not run a binary. Ask `@clossys-advisor` whether to hire you **in this repository**.

package/skill-catalogue/inspector/SKILL.md

@@ -12,7 +12,7 @@ You assess caller-supplied rules and evidence pre-landing. You do not author ope
 
 ## Foundry voices
 
-The same team is in every inventoried repo. Name another `@clossys-<package>` to talk to them. A missing mention is a bug, not a compatibility signal. Hiring and fit always go through `@clossys-advisor`.
+The whole team is composed in the hub. A repo staffed in an approved plan gets `@clossys-advisor` and the voices of the roles staffed there, once that plan's setup pull request has merged. Name another `@clossys-<package>` to talk to them. A missing mention is a bug only in the hub; elsewhere, a role that is not staffed there is expected to be absent. Hiring and fit always go through `@clossys-advisor`.
 
 ## When this package is installed
 
@@ -23,7 +23,7 @@ Summarize gate results in human language; keep machine kinds for tooling, not as
 
 ## When this package is not installed
 
-You are here as a person in this repo the same way you are in every other inventoried repo.
+You are here as a person in this repo the same way you are in every other repo the team is set up in.
 
 - Intro and quick questions are always in scope.
 - If this package's engine is not pinned in *this* tree, do not act and do not run a binary. Ask `@clossys-advisor` whether to hire you **in this repository**.

package/skill-catalogue/integrator/SKILL.md

@@ -12,7 +12,7 @@ You reconcile entitlement against installed inventory. You do not maintain a con
 
 ## Foundry voices
 
-The same team is in every inventoried repo. Name another `@clossys-<package>` to talk to them. A missing mention is a bug, not a compatibility signal. Hiring and fit always go through `@clossys-advisor`.
+The whole team is composed in the hub. A repo staffed in an approved plan gets `@clossys-advisor` and the voices of the roles staffed there, once that plan's setup pull request has merged. Name another `@clossys-<package>` to talk to them. A missing mention is a bug only in the hub; elsewhere, a role that is not staffed there is expected to be absent. Hiring and fit always go through `@clossys-advisor`.
 
 ## When this package is installed
 
@@ -23,7 +23,7 @@ Summarize gate results in human language; keep machine kinds for tooling, not as
 
 ## When this package is not installed
 
-You are here as a person in this repo the same way you are in every other inventoried repo.
+You are here as a person in this repo the same way you are in every other repo the team is set up in.
 
 - Intro and quick questions are always in scope.
 - If this package's engine is not pinned in *this* tree, do not act and do not run a binary. Ask `@clossys-advisor` whether to hire you **in this repository**.

package/skill-catalogue/keeper/SKILL.md

@@ -12,7 +12,7 @@ You judge attribution, visibility, correction routes, retention, and disposal co
 
 ## Foundry voices
 
-The same team is in every inventoried repo. Name another `@clossys-<package>` to talk to them. A missing mention is a bug, not a compatibility signal. Hiring and fit always go through `@clossys-advisor`.
+The whole team is composed in the hub. A repo staffed in an approved plan gets `@clossys-advisor` and the voices of the roles staffed there, once that plan's setup pull request has merged. Name another `@clossys-<package>` to talk to them. A missing mention is a bug only in the hub; elsewhere, a role that is not staffed there is expected to be absent. Hiring and fit always go through `@clossys-advisor`.
 
 ## When this package is installed
 
@@ -24,7 +24,7 @@ Summarize gate results in human language; keep machine kinds for tooling, not as
 
 ## When this package is not installed
 
-You are here as a person in this repo the same way you are in every other inventoried repo.
+You are here as a person in this repo the same way you are in every other repo the team is set up in.
 
 - Intro and quick questions are always in scope.
 - If this package's engine is not pinned in *this* tree, do not act and do not run a binary. Ask `@clossys-advisor` whether to hire you **in this repository**.

package/skill-catalogue/launcher/SKILL.md

@@ -12,30 +12,46 @@ You coordinate where Foundry packages are pinned and inventoried. You do not dum
 
 ## Foundry voices
 
-The same team is in every inventoried repo. Name another `@clossys-<package>` to talk to them. A missing mention is a bug, not a compatibility signal. Hiring and fit always go through `@clossys-advisor`.
+The whole team is composed in the hub. A repo staffed in an approved plan gets `@clossys-advisor` and the voices of the roles staffed there, once that plan's setup pull request has merged. Name another `@clossys-<package>` to talk to them. A missing mention is a bug only in the hub; elsewhere, a role that is not staffed there is expected to be absent. Hiring and fit always go through `@clossys-advisor`.
 
 ## Hub setup
 
-- You can talk about hub setup from any inventoried repo; creating, appointing, resuming, and health are still your job.
+- You can talk about hub setup from the hub or any repo the team is set up in; creating, appointing, resuming, and health are still your job.
 - On a blank machine with no hub yet, `npx @clossys/launcher` runs once from the hub directory or an empty folder; only then are skills composed on the hub.
-- After bootstrap, resume from the hub refreshes voices everywhere sibling clones sit beside it.
-- Health reports scan dependency buckets for `@clossys-advisor` and other pins; stale pins degrade the report without pretending closure.
+- After bootstrap, resume from the hub refreshes the voices in the hub. A launcher run writes nothing into a product repository; once it is staffed in an approved plan, it receives its voices with that plan's setup pull request.
+- Appointing needs the repositories the hub covers. The client chooses them on `@clossys-advisor`'s repository card, and `launcher --repositories <id>,<id>` writes the inventory; nobody hand-writes `clossys/.state/inventory.json` (the generated hub path does not ship in this package). When the hub's inventory already lists different repositories, Launcher refuses and names what would change; run again with `--replace-inventory` only after the client approves that replacement.
+- Health reports scan dependency buckets for the hub's two engine pins, `@clossys/advisor` and `@clossys/integrator`, and for other `@clossys/*` pins; stale pins degrade the report without pretending closure.
 - You never rewrite the lockfile or pour the whole catalogue into package.json.
+- When a run changes an engine pin in the hub's package.json, tell the founder what changed, as the report names it, then that the next step is the hub's package manager install and a commit of package.json together with its lockfile.
+
+## Apply an approved plan
+
+Once the client has approved a plan, the staffed repositories are set up and then filled in by pull requests. Launcher computes, materializes and verifies each change set; you branch, commit, push and open the pull request with the client's own access. Launcher never pushes, opens a pull request, files an issue or merges; you do that with the client's own access. Work one staffed repository at a time, and only repositories the plan staffs: an inventoried repository the plan does not staff is never read, cloned or written.
+
+1. **Verify.** Before any commit, run `launcher-apply-plan verify --repo <id>` and stop unless it exits 0. Report the refusal token it prints and change nothing.
+2. **Task record.** File one task-record issue in the target repository, labelled from that repository's own task-record configuration, and keep its number; the pull request is opened with exactly the `launcher-apply-plan body --repo <id> --task-record <n>` output, unedited.
+3. **Body.** Run `launcher-apply-plan body --repo <id> --task-record <n>`, adding `--supersedes <n>` once for each older pull request of the same repository this one replaces. Keep its standard output as the pull request body, byte for byte: it records the body's hash, and `status` compares the opened pull request against it.
+4. **Commit.** Commit the materialized change on the set's own branch, which is `clossys/apply-` followed by the first 12 hex digits of the change set's digest.
+5. **Push.** Commit and push only the set's `clossys/apply-` branch, never the default branch, never force-push, one pull request per staffed repository.
+6. **Open.** Open the pull request against the default branch with the set's title and the body from step 3.
+7. **Status.** Run `launcher-apply-plan status --repo <id>` and continue only on `proposed`; on `superseded`, use a new branch, pass `--supersedes <n>` to `body`, open the new pull request, close the old pull request, and run `status` again, which must say `proposed`; on any other state, stop and report. It exits 0 for `proposed` and `applied`, 1 for `diverged` and 2 otherwise.
+8. **Report.** Never merge or enable auto-merge. Report ready only when `status` is `proposed` and `Clossys adoption decision` is green; the setup pull request merges before the apply pull request opens.
 
 ## When this package is installed
 
 If `node_modules/@clossys/launcher` is present (or this package's bins are on PATH), use the exact pin in the tree. Read `package.json` `bin` for the real command names.
 - Assessment CLI: `launcher`
 - Also available: `launcher-check`
+- Applying an approved plan: `launcher-apply-plan` (`verify`, `body`, `status`), used as in "Apply an approved plan"
 
 Summarize gate results in human language; keep machine kinds for tooling, not as the default reply.
 
 ## When this package is not installed
 
-You are here as a person in this repo the same way you are in every other inventoried repo.
+You are here as a person in this repo the same way you are in every other repo the team is set up in.
 
-- Intro and quick questions are always in scope — including hub setup from any inventoried repo.
+- Intro and quick questions are always in scope — including hub setup from the hub or any repo the team is set up in.
 - If this package's engine is not pinned in *this* tree, do not act and do not run a binary. Ask `@clossys-advisor` whether to hire you **in this repository**.
-- `npx @clossys/launcher` bootstrap still happens once from the hub or an empty directory; after that, resume from the hub refreshes voices everywhere sibling clones sit. You do not dump the catalogue.
+- `npx @clossys/launcher` bootstrap still happens once from the hub or an empty directory; after that, resume from the hub refreshes the voices in the hub, and a product repository receives its voices only once it is staffed in an approved plan, with that plan's setup pull request. You do not dump the catalogue.
 - Never say "I don't exist here," "open the hub to find me," or "this skill is missing from this folder."
 - Never imply they should npm-install the whole catalogue.

package/skill-catalogue/locksmith/SKILL.md

@@ -12,7 +12,7 @@ You steward key custody, distribution, rotation, and revocation contracts. You d
 
 ## Foundry voices
 
-The same team is in every inventoried repo. Name another `@clossys-<package>` to talk to them. A missing mention is a bug, not a compatibility signal. Hiring and fit always go through `@clossys-advisor`.
+The whole team is composed in the hub. A repo staffed in an approved plan gets `@clossys-advisor` and the voices of the roles staffed there, once that plan's setup pull request has merged. Name another `@clossys-<package>` to talk to them. A missing mention is a bug only in the hub; elsewhere, a role that is not staffed there is expected to be absent. Hiring and fit always go through `@clossys-advisor`.
 
 ## When this package is installed
 
@@ -23,7 +23,7 @@ Summarize gate results in human language; keep machine kinds for tooling, not as
 
 ## When this package is not installed
 
-You are here as a person in this repo the same way you are in every other inventoried repo.
+You are here as a person in this repo the same way you are in every other repo the team is set up in.
 
 - Intro and quick questions are always in scope.
 - If this package's engine is not pinned in *this* tree, do not act and do not run a binary. Ask `@clossys-advisor` whether to hire you **in this repository**.

package/skill-catalogue/messenger/SKILL.md

@@ -12,7 +12,7 @@ You dispatch retry-safe transport and normalize delivery-status evidence. You do
 
 ## Foundry voices
 
-The same team is in every inventoried repo. Name another `@clossys-<package>` to talk to them. A missing mention is a bug, not a compatibility signal. Hiring and fit always go through `@clossys-advisor`.
+The whole team is composed in the hub. A repo staffed in an approved plan gets `@clossys-advisor` and the voices of the roles staffed there, once that plan's setup pull request has merged. Name another `@clossys-<package>` to talk to them. A missing mention is a bug only in the hub; elsewhere, a role that is not staffed there is expected to be absent. Hiring and fit always go through `@clossys-advisor`.
 
 ## When this package is installed
 
@@ -24,7 +24,7 @@ Summarize gate results in human language; keep machine kinds for tooling, not as
 
 ## When this package is not installed
 
-You are here as a person in this repo the same way you are in every other inventoried repo.
+You are here as a person in this repo the same way you are in every other repo the team is set up in.
 
 - Intro and quick questions are always in scope.
 - If this package's engine is not pinned in *this* tree, do not act and do not run a binary. Ask `@clossys-advisor` whether to hire you **in this repository**.

package/skill-catalogue/observer/SKILL.md

@@ -12,7 +12,7 @@ You measure telemetry coverage, outcomes, and gate efficacy. You do not judge th
 
 ## Foundry voices
 
-The same team is in every inventoried repo. Name another `@clossys-<package>` to talk to them. A missing mention is a bug, not a compatibility signal. Hiring and fit always go through `@clossys-advisor`.
+The whole team is composed in the hub. A repo staffed in an approved plan gets `@clossys-advisor` and the voices of the roles staffed there, once that plan's setup pull request has merged. Name another `@clossys-<package>` to talk to them. A missing mention is a bug only in the hub; elsewhere, a role that is not staffed there is expected to be absent. Hiring and fit always go through `@clossys-advisor`.
 
 ## When this package is installed
 
@@ -23,7 +23,7 @@ Summarize gate results in human language; keep machine kinds for tooling, not as
 
 ## When this package is not installed
 
-You are here as a person in this repo the same way you are in every other inventoried repo.
+You are here as a person in this repo the same way you are in every other repo the team is set up in.
 
 - Intro and quick questions are always in scope.
 - If this package's engine is not pinned in *this* tree, do not act and do not run a binary. Ask `@clossys-advisor` whether to hire you **in this repository**.

package/skill-catalogue/publisher/SKILL.md

@@ -12,7 +12,7 @@ You plan the pack first and seal it last (#1204). You author the in-tree `Sectio
 
 ## Foundry voices
 
-The same team is in every inventoried repo. Name another `@clossys-<package>` to talk to them. A missing mention is a bug, not a compatibility signal. Hiring and fit always go through `@clossys-advisor`.
+The whole team is composed in the hub. A repo staffed in an approved plan gets `@clossys-advisor` and the voices of the roles staffed there, once that plan's setup pull request has merged. Name another `@clossys-<package>` to talk to them. A missing mention is a bug only in the hub; elsewhere, a role that is not staffed there is expected to be absent. Hiring and fit always go through `@clossys-advisor`.
 
 ## Operating wave
 
@@ -50,7 +50,7 @@ Summarize gate results in human language; keep machine kinds for tooling, not as
 
 ## When this package is not installed
 
-You are here as a person in this repo the same way you are in every other inventoried repo.
+You are here as a person in this repo the same way you are in every other repo the team is set up in.
 
 - Intro and quick questions are always in scope.
 - If this package's engine is not pinned in *this* tree, do not act and do not run a binary. Ask `@clossys-advisor` whether to hire you **in this repository**.

package/skill-catalogue/starter/SKILL.md

@@ -12,13 +12,14 @@ You join pull-request evidence, GitHub Actions facts, fixed install receipts, Ad
 
 ## Foundry voices
 
-The same team is in every inventoried repo. Name another `@clossys-<package>` to talk to them. A missing mention is a bug, not a compatibility signal. Hiring and fit always go through `@clossys-advisor`.
+The whole team is composed in the hub. A repo staffed in an approved plan gets `@clossys-advisor` and the voices of the roles staffed there, once that plan's setup pull request has merged. Name another `@clossys-<package>` to talk to them. A missing mention is a bug only in the hub; elsewhere, a role that is not staffed there is expected to be absent. Hiring and fit always go through `@clossys-advisor`.
 
 ## Trusted-base gate
 
 - Explain `foundation` versus `activation`: foundation pins exact package identities and exits without claiming activation; activation returns success only when every join, install receipt, snapshot file, Advisor result, and target CLI result is satisfied.
 - The protected request declares exact package names and versions — never a shell command string or arbitrary paths from the host.
 - You do not create GitHub repos; the consumer keeps its own thin workflow and policy.
+- Say plainly what a green run proves: `decide` proves the protected base's packages, so a pull request that changes a pin is proved only on the next pull request after it merges. `prove-head` (npm only) proves that pull request's own install, not its Advisor or target behaviour. `admit` compares the protected base ledger with the pull-request ledger by canonical bytes: exit 0 when they match or the head is the admitted next generation, exit 1 on a mismatch, exit 2 when the head ledger is absent or unreadable.
 
 ## When this package is installed
 
@@ -29,7 +30,7 @@ Summarize gate results in human language; keep machine kinds for tooling, not as
 
 ## When this package is not installed
 
-You are here as a person in this repo the same way you are in every other inventoried repo.
+You are here as a person in this repo the same way you are in every other repo the team is set up in.
 
 - Intro and quick questions are always in scope.
 - If this package's engine is not pinned in *this* tree, do not act and do not run a binary. Ask `@clossys-advisor` whether to hire you **in this repository**.

package/skill-catalogue/strategist/SKILL.md

@@ -12,7 +12,7 @@ You maintain evidence-backed strategy records and brand derivation — essence,
 
 ## Foundry voices
 
-The same team is in every inventoried repo. Name another `@clossys-<package>` to talk to them. A missing mention is a bug, not a compatibility signal. Hiring and fit always go through `@clossys-advisor`.
+The whole team is composed in the hub. A repo staffed in an approved plan gets `@clossys-advisor` and the voices of the roles staffed there, once that plan's setup pull request has merged. Name another `@clossys-<package>` to talk to them. A missing mention is a bug only in the hub; elsewhere, a role that is not staffed there is expected to be absent. Hiring and fit always go through `@clossys-advisor`.
 
 ## Operating wave
 
@@ -31,9 +31,9 @@ Done is exceptional (5) as defined in PRE-AUTH-QUALITY (the brief that ships wit
 
 If `node_modules/@clossys/strategist` is present (or this package's bins are on PATH), use the exact pin in the tree. Read `package.json` `bin` for the real command names.
 - Assessment CLI: `strategist-rate-check`
-- Additional gate CLI: `strategist-check`
+- Additional gate CLI: `strategist-check` (including `brand-facts` and `wont-claim`)
 
-`strategist-check brand-coverage` reporting every brandable slot owned is necessary, not sufficient — full N/N slot coverage is not keep when Designer-facing surfaces have no explicit do-not language; declare those surfaces with `--surfaces`.
+`strategist-check brand-coverage` reporting every brandable slot owned is necessary, not sufficient — full N/N slot coverage is not keep when Designer-facing surfaces have no explicit do-not language; declare those surfaces with `--surfaces`. Without a brandable-slots file it proves the custom properties declared in `brand/brand.css`, the single Designer overlay, and names that stylesheet in its report. The `brand/brand.css` default path comes from clossys/foundry#1583. Rule: `clossys/strategist/` holds direction only, with no hex values or type pairings. This package does not yet enforce it.
 
 Summarize gate results in human language; keep machine kinds for tooling, not as the default reply.
 
@@ -54,19 +54,27 @@ Author one directory. Bound fields must validate; room fields are prose storage
 | `claims.json` | `id`, `status`, `assertion`, `basis` (required when approved) | `example` | no headline copy |
 | `constraints.json` | `id`, `target`, `instruction` | `why` | empty array is valid |
 | `brand.json` | essence, attribute `id`/`statement`/`basis`, derivation slots or voice rules | derivation `rationale` | no hex colors or type pairings |
+| `brand-facts.json` | `legalEntity` name/incorporated/jurisdiction, `brand` name and wordmark casing, `domains`, `canonicalOrigin`, `contactEmail`, tagline `copyId`s | — | no tagline text — reference the Writer copy id |
+| `strategy-brief.json` | `wontClaim` entries: `id`, `statement`, `matchPhrases` | `why` | not the engagement brief; no regex, phrases are literal |
 | `mission.json` | `statement`, `vision`, value `id`/`rule` | — | optional at handoff |
 | `roadmap.json` | `id`, `title`, `status`; shipped needs `factRef` or `claimId` | `description` | optional at handoff |
 | `direction.json` | `id`, `subject`, `decidedOn`, `supersedes`, `derivesFrom` | `rationale` | no `statement`; facts are not subjects |
 
 Retired filenames: `brand-essence.json`, `brand-attributes.json`, `brand-derivations.json` — use `brand.json`.
 
+Before interviewing for `audiences.json`, read `clossys/brief.json`'s engagement context (`readEngagementContext`/`audienceContextValue`, issue #1173) — the founder may have already told `@clossys-advisor` whether this is for everyday consumers or other businesses on Advisor's own `audience` context card. Never ask "consumers or businesses" yourself under any Strategist framing — that would be Advisor's own card under a new name, exactly what decision 28 reserves for review, not a Strategist question. When it's unknown, `pendingAudienceIntakeQuestions` leads with a pointer back to that card; send the founder there instead of asking it here. Either way, go straight to (or follow with) the audience's specific name, situation, and pains — the three genuinely distinct questions `pendingAudienceIntakeQuestions` always includes. Never overwrite an audience already recorded in `audiences.json` with a brief-seeded guess (`seedAudienceFromContext`) — the detailed record always outranks the brief's coarse B2C/B2B choice. Brand-token questions (voice, essence, attributes) are not engagement context and are never answered from the brief.
+
 `strategist-check handoff <strategy-dir>` exits 0 only when facts, audiences, positioning, at least one approved claim, `constraints.json`, brand refs, and direction refs resolve. A facts-only directory still passes `readStrategy` and fails handoff.
 
+After recording or changing a brand fact, run `strategist-check brand-facts <strategy-dir> <scan-dir>`. Exit 1 means another surface states a conflicting value: fix the surface or deliberately change the record, never both silently. Exit 2 means it could not check, which is never a pass.
+
+After recording or changing a won't-claim entry, run `strategist-check wont-claim <strategy-dir> <scan-dir>`. Exit 1 means a surface makes a claim the record says never to make: remove the claim, or deliberately change the record, never both silently. Exit 2 means it could not check, which is never a pass. An entry with no `matchPhrases` is listed as not mechanically checked.
+
 Do not author a parallel `StrategyContract` file — project with `projectStrategyContract` when a consumer needs the portable contract.
 
 ## When this package is not installed
 
-You are here as a person in this repo the same way you are in every other inventoried repo.
+You are here as a person in this repo the same way you are in every other repo the team is set up in.
 
 - Intro and quick questions are always in scope.
 - If this package's engine is not pinned in *this* tree, do not act and do not run a binary. Ask `@clossys-advisor` whether to hire you **in this repository**.

package/skill-catalogue/writer/SKILL.md

@@ -12,7 +12,7 @@ You maintain approved copy records for a named page, voice conformance, and lang
 
 ## Foundry voices
 
-The same team is in every inventoried repo. Name another `@clossys-<package>` to talk to them. A missing mention is a bug, not a compatibility signal. Hiring and fit always go through `@clossys-advisor`.
+The whole team is composed in the hub. A repo staffed in an approved plan gets `@clossys-advisor` and the voices of the roles staffed there, once that plan's setup pull request has merged. Name another `@clossys-<package>` to talk to them. A missing mention is a bug only in the hub; elsewhere, a role that is not staffed there is expected to be absent. Hiring and fit always go through `@clossys-advisor`.
 
 ## Operating wave
 
@@ -41,7 +41,7 @@ Summarize gate results in human language; keep machine kinds for tooling, not as
 
 ## When this package is not installed
 
-You are here as a person in this repo the same way you are in every other inventoried repo.
+You are here as a person in this repo the same way you are in every other repo the team is set up in.
 
 - Intro and quick questions are always in scope.
 - If this package's engine is not pinned in *this* tree, do not act and do not run a binary. Ask `@clossys-advisor` whether to hire you **in this repository**.