@design-intelligence/ghost 0.28.0 → 0.29.0

package/dist/skill-bundle/references/concrete.md

@@ -0,0 +1,131 @@
+---
+name: concrete
+description: Bind ghost guidance to concrete material in formats agents can use directly.
+---
+
+# Recipe: Bind Guidance To Concrete Material
+
+**Goal:** make the intended continuation cheaper than the generic one without
+turning the package into a second implementation or a fixed template library.
+
+Concrete material commonly does three jobs:
+
+| Form | What it constrains | What it buys |
+| --- | --- | --- |
+| Tokens | values and role names | stops plausible near-miss colors, sizes, and durations |
+| Skeletons | opening structure | commits layout before a generic structure wins the first tokens |
+| Components | reusable decisions | compresses variants, states, spacing, and behavior into names |
+
+## Scope is not delivery
+
+Scope says how much a material constrains. Delivery says whether the agent actually
+receives it. Skeletons live in node bodies and `ghost pull` emits them last.
+Files behind `materials` arrive only when pulled or inspected. Material the
+agent never reads contributes nothing.
+
+Anything that must never be missed belongs in prose or a Skeleton. Anything
+behind `materials` must repay the inspection turn: explicit, skimmable, and
+contract-first.
+
+## Ship the syntax the agent emits
+
+Every transform between what the agent reads and writes is an error
+opportunity. If it reads `color.background.default: "#fafafa"` in nested JSON
+but must write `var(--background)`, the model must reconstruct the mapping under
+attention pressure. Near-miss names are priors filling that gap.
+
+When a build pipeline owns the source of truth, point `materials` at the output
+the agent writes against, not an upstream representation. Name each file;
+glob patterns are invalid because a live repo can make them capture unintended
+content.
+
+## Choose only what helps
+
+**Tokens are the visual floor.** Use one flat, contract-first file in the
+emission syntax. For CSS, lead with a comment such as `/* style only with these
+custom properties; never hardcode colors or timing. */`, then group flat
+`--name: value` pairs by role. In a utility codebase, name the emitted classes
+in prose and point to the built stylesheet. Avoid markdown token tables and
+nested source JSON when the output uses neither.
+
+**Skeletons are earned by composition-critical openings.** Put exactly one
+fenced block under `## Skeleton`, in the target medium, with real token or class
+names and `{placeholders}` for task facts. Include only enough structure to
+commit the shape. A Skeleton in a materials file forfeits guaranteed delivery.
+
+**Components are earned by repeated, diverse surfaces.** The source is the API
+reference. Point to each component file explicitly and keep prose to usage
+grammar: purpose, reach-when, neighboring alternative, and never. Do not copy
+props into markdown. For a class vocabulary, lead each class block with a
+one-line contract comment so a skimming agent can recover the grammar.
+
+Examples are ordinary materials. When a complete runnable surface helps, point
+to it and follow the example guidance in [nodes.md](nodes.md). Name the file for
+the shape it shows, such as `composition.form.html`, not for arbitrary content.
+
+Absence can be the correct stance. A package that asks agents to compose fresh
+from tokens may reject a component kit. A package that values variation may use
+few Skeletons. The reason for absence must be explicit.
+
+## Bind a component library
+
+An OSS component library should ship its own `.ghost/` packet beside the code,
+then let adopters copy and own both. The packet is a taste floor, not the
+consumer's brand.
+
+1. Vendor or install the components and packet together.
+2. Repoint every `materials` locator to the receiving repo's exact files.
+3. State in the cover that local brand guidance overrides the vendored floor.
+4. Give prose only to components whose purpose or divergence is not generic.
+5. Put token and theming invariants in contract nodes.
+6. Add checks only for countable, review-critical invariants.
+7. Run `ghost validate`; dead-locator warnings identify paths that moved.
+
+For a familiar library, the model may already know the API. Guidance still
+matters for restraint and choice: which variant when, what not to combine, and
+which neighboring component fits instead. For a novel library, the component
+source supplies missing API knowledge; prose supplies the usage decision.
+
+Do not add a component schema, registry mirror, or prop manifest to ghost. Those
+copies drift. `materials` locates implementation; the node body explains why
+and when.
+
+## Bundle or reference
+
+Put brand-owned artifacts that must travel through export or survive refactors
+under `.ghost/materials/`: token output, logos, type files, motion data, and
+portable examples. Reference living components, stories, tests, and styles at
+their repository paths. Guidance stays in prose in both cases.
+
+Use external locators when the authoritative material remains external. Add a
+short `note` only when the locator itself does not tell the agent what it will
+find.
+
+## Drift bill
+
+Concrete material repeats decisions from the prose. After changing guidance,
+tokens, or component contracts, sweep Skeletons, components, examples, and
+checks for stranded names or literals. Delete any copy whose maintenance cost
+exceeds its steering value.
+
+`ghost pull` inlines each distinct local material once per pull. Later nodes
+keep a pointer to the first copy, so sharing a material across nodes is safe and
+does not inflate its salience.
+
+## Concrete self-check
+
+1. Where does the emitted value vocabulary live?
+2. What commits the most composition-critical opening?
+3. Which reusable decisions are compressed into source-backed names?
+4. What material shows decisions working together when prose is not enough?
+5. Will the agent actually receive or inspect each material?
+6. Is each material in the syntax the agent will emit?
+7. Which copy goes stale when the underlying decision changes?
+
+Any answer may be "absent, because." An unexplained absence is the gap.
+
+## Never
+
+- Never point materials at globs, directories, or generated junk.
+- Never duplicate component APIs or pipeline source formats in prose.
+- Never add concrete material only because a design-system convention says to.

package/dist/skill-bundle/references/making.md

@@ -38,7 +38,7 @@ selects, inspects, makes, renders, judges, and repairs in the same session.
    - read inlined text materials;
    - open referenced source, token, or component files;
    - view image inspect-pointers instead of relying on filenames;
-   - inspect rendered exemplars, not just their contexts;
+   - inspect rendered examples, not just their contexts;
    - use an available host connection for an external locator only when inspecting
      it could materially affect the task;
    - let the host run its normal authentication and permission flow;
@@ -51,10 +51,9 @@ selects, inspects, makes, renders, judges, and repairs in the same session.
    - never modify an external resource unless the user explicitly asks;
    - record remote, oversized, missing, or unreadable materials;
    - never claim material grounding for something you did not inspect.
-6. **Separate exemplar intent from incidentals.** When a pulled exemplar applies,
-   identify what is load-bearing, what should change with task facts, and the
-   conditions where the exemplar stops applying. Do not turn one exemplar into a
-   universal visual target.
+6. **Follow the example instructions.** Keep what the node says to preserve,
+   change what belongs to the task, and use the example only in the situation it
+   covers. Do not turn one example into a universal target.
 7. **Brief the work.** Follow [brief.md](brief.md). The brief is a steering step,
    not a report. Keep the five-section shape, cap non-negotiables at five, and
    keep ghost-backed claims separate from provisional local reasoning.

package/dist/skill-bundle/references/nodes.md

@@ -0,0 +1,138 @@
+---
+name: nodes
+description: Write durable ghost guidance with discriminating context, purposeful prose, conditions, replacements, and useful examples.
+---
+
+# Recipe: Write Guidance Nodes
+
+**Goal:** write the smallest node that forces a real brand decision. Package
+shape belongs in [schema.md](schema.md); this recipe owns the guidance itself.
+
+## One node, one purpose
+
+A node is one coherent decision with one applicability. Split only when a body
+contains another decision that should be gathered in a different situation.
+Do not split by destination or component name.
+
+Use `context` as retrieval payload, not summary. State the observable situation
+in which the node applies. Read it alone: if it fits every brand or almost every
+task, it will not help selection. Put what to do and why in the body.
+
+Altitude lives in prose:
+
+- State universal guidance plainly.
+- Give narrower guidance a condition that names when it holds.
+- Name the reversal condition when a decision can legitimately flip.
+- Do not encode scope through folders, hierarchy, inheritance, or edges.
+
+While drafting, ask three questions. They are prompts, not fields:
+
+1. **Why:** what stance or tradeoff forces the choice?
+2. **With what:** which concrete materials let the agent act on it?
+3. **How assembled:** which relationships or opening structure must hold?
+
+A node may answer one or all three. Put locators in `materials`; keep
+interpretation in prose.
+
+## Write decisions, not brand-deck language
+
+A useful sentence rejects a plausible alternative. "We value clarity and
+trust" does not steer. "State what remains safe before asking the person to try
+again" does.
+
+Keep real absolutes. `Never` and `always` are correct for human-ratified hard
+lines. Elsewhere, remove filler and unchosen hedges: "elevate," "delight,"
+"seamless," "best-in-class," "generally," "where possible," and "consider."
+If the human has not picked a side, return to authoring rather than laundering
+uncertainty into prose.
+
+## Patterns bind and open
+
+A pattern fixes part of a reusable structure and leaves the rest available:
+
+- **Bound:** what must not be redecided, such as what appears first, exactly
+  once, or never competes for attention.
+- **Open:** where the agent may choose within limits, such as evidence form,
+  secondary content, or tone within a range.
+
+Everything bound is a template. Nothing bound is vibes. Use a Skeleton only
+when the opening structure itself must arrive verbatim; see
+[concrete.md](concrete.md).
+
+## Anti-goals replace
+
+A strong anti-goal says **not X; instead Y; recognize the switch by Z**.
+Negation alone makes the rejected default more salient without committing the
+replacement.
+
+```markdown
+---
+context: Building or reviewing a performance dashboard.
+---
+
+Not rounded cards, celebratory gradients, and a wall of equal metrics.
+Instead use one accountable fact, its evidence, and one priced next action on a
+flat surface. Recognize the switch: removing the logo should not leave a generic
+SaaS dashboard behind.
+```
+
+Purge the rejected pattern from examples and starter structures. Use checks to
+catch the hard regression; do not make anti-goal prose carry review alone.
+
+## Explain examples
+
+If a node includes or points to an example, say what the agent should keep and
+what should change with the task. Name the situation it fits when needed. If
+you cannot give those instructions, leave the example out.
+
+## Reusable blocks earn prose by purpose
+
+Generic primitives need no node merely because they exist. A primitive earns
+prose only for its brand-specific divergence. A reusable block earns a node when
+it encodes a distinguishable user moment or arrangement.
+
+For a reusable block, write a short body in this rhythm:
+
+- **For:** the user need, not the widget.
+- **Reach when:** the user's first question.
+- **Not when:** the neighboring purpose to choose instead.
+- **Never:** the misuse that stretches it beyond its job.
+
+Two blocks that answer the same first question are one purpose, not two nodes.
+Keep props and API reference out of the body. The implementation is swappable;
+the purpose is durable.
+
+## Drafting gate
+
+Before curation, ask:
+
+| Dimension | Question |
+| --- | --- |
+| Testimony | Can you name the human words or evidence behind this? |
+| Discrimination | Does the context select a real situation rather than a topic? |
+| Force | Does the body decide something and reject a plausible alternative? |
+| Altitude | Is it universal on purpose, or conditioned? |
+| Residue | Is it free of starter prose, API mirroring, and brand-deck filler? |
+
+A weak answer returns to the human or evidence. Scores do not make guidance
+canonical; human curation does.
+
+## Match the form to the failure
+
+| If the agent keeps... | Author... |
+| --- | --- |
+| missing guidance | sharper `context`; universal guidance may belong on the cover |
+| inventing values | a material-backed node with exact vocabulary |
+| producing generic output | replacement anti-goal plus a well-explained example |
+| choosing the wrong structure | bound/open pattern and, when needed, a Skeleton |
+| crossing a hard line | invariant prose plus a review check |
+| applying guidance too broadly | a condition or reversal condition |
+| making the wrong tradeoff | a decision trace with the losing alternative |
+
+## Never
+
+- Never write a node the human neither said, showed, nor accepted.
+- Never make a node a container for observations or implementation inventory.
+- Never duplicate API documentation unless the API itself is the guidance.
+- Never use a broad context to compensate for unrelated decisions in one body.
+- Never ship a blacklist-only anti-goal.

package/dist/skill-bundle/references/schema.md

@@ -1,12 +1,10 @@
 ---
 name: schema
-description: The ghost package shape: flat nodes, derived concreteness, Skeletons, and checks.
+description: The deterministic ghost package contract: layout, manifest, nodes, materials, Skeletons, checks, and command behavior.
 ---
 
 # ghost Package Reference
 
-Canonical package:
-
 ```text
 .ghost/
   manifest.yml        ghost.package/v1: schema + id + optional cover
@@ -18,28 +16,31 @@ Canonical package:
 ```
 
 Reserved at the root: `manifest.yml`, `glossary.md`, `materials/`, and
-`checks/`. Every other `*.md` is a node.
+`checks/`. Every other `*.md` is a node. The corpus is flat: no hierarchy,
+inheritance, or edges.
 
 ## Manifest
 
 `manifest.yml` declares `schema`, `id`, and optionally `cover`. `cover` is a
 node id. When present and resolved, `ghost gather` inlines that node above the
-menu on every invocation. Use it for what selection cannot reliably retrieve:
-essence, temperature, and brand-only refusals.
+menu on every invocation.
 
-`ghost validate` enforces the cover contract: a missing referenced cover is an
-error, an undeclared cover is a warning, and a cover body past the one-screen
-budget (1500 bytes) is a warning.
+`ghost validate` reports a missing referenced cover as an error, an undeclared
+cover as a warning, and a cover body over 1500 bytes as a warning.
 
-## Nodes
+## Glossary and identity
+
+`glossary.md` declares the package's kind vocabulary and defines each kind. A
+node's id is its filename minus `.md`; its kind is the first dotted filename
+segment. A bare filename has no kind. Undeclared kind prefixes warn.
 
-A node is markdown with frontmatter and a prose body:
+## Nodes
 
 ```markdown
 ---
 context: Placing, sizing, or choosing a logo lockup or glyph.
 materials:
-  - brand/logo*.svg
+  - brand/logo-primary.svg
   - https://figma.com/file/example?node-id=logo-lockups
   - locator: mcp://brand-assets/logo-lockups
     note: Source lockups and glyph exports
@@ -48,36 +49,26 @@ materials:
 Use the full lockup when recognition matters.
 ```
 
-- Identity is the filename minus `.md`.
-- Kind is the first dotted segment of the filename.
-- `context` is the retrieval payload shown by `ghost gather`. Its only job is
-  to tell the agent when to gather the node. Name the observable applicability
-  condition directly; put guidance and contribution in the body. Say “gather
-  when” only when an explicit routing instruction is necessary. Avoid broad
-  universal wording unless universal retrieval is intended. `description`
-  remains a deprecated read alias for one release; `ghost validate` warns until
-  it is renamed.
-- `materials` accepts repo-relative file paths plus supported external locators
-  using `https:`, `mcp:`, `figma:`, or `github:`. Name each file explicitly:
-  glob patterns are not supported and fail validation, because in a live
-  repo a glob can capture unintended files into pulls. Items may be bare
-  locator strings or `{ locator, note }` objects. Use a short `note` only when
-  an opaque locator needs retrieval context. The external locator tells the
-  host how to connect; ghost does not fetch or authenticate. The list locates
-  material, while guidance stays in the node body.
-
-ghost derives whether a node carries concrete material from structure:
-non-empty `materials`, a fenced code block of at least 3 lines, or a
-`## Skeleton` section. `gather` reports these payload labels for clarity; they
-are not ranking signals.
-
-## Skeleton convention
-
-A `## Skeleton` section contains the literal opening structure for a surface.
-It should contain exactly one fenced block; `ghost validate` warns, never fails,
-when a Skeleton section has zero or multiple fences.
+- `context` is the retrieval payload shown by `ghost gather`.
+- `description` remains a deprecated read alias for one release; validation
+  warns until it is renamed.
+- `materials` accepts explicit repo-relative file paths and external locators
+  using `https:`, `mcp:`, `figma:`, or `github:`.
+- Glob patterns are invalid. Each local file must be named explicitly.
+- A material may be a bare locator or `{ locator, note }`.
+- External locators describe access; ghost does not fetch or authenticate.
+- Frontmatter may contain additional descriptive keys. Guidance stays in prose.
 
-```markdown
+A node is concrete when it has non-empty `materials`, a fenced code block of at
+least three lines, or a `## Skeleton` section. `gather` reports those payload
+labels; they are not ranking signals.
+
+## Skeletons
+
+A `## Skeleton` section contains literal opening structure. It must contain
+exactly one fenced block; zero or multiple fences warn.
+
+````markdown
 ## Skeleton
 
 ```tsx
@@ -86,10 +77,10 @@ when a Skeleton section has zero or multiple fences.
   <button>{nextStep}</button>
 </section>
 ```
-```
+````
 
-`ghost pull` extracts Skeleton fences and emits them dead last under a banner
-instructing the agent to begin from that structure verbatim.
+`ghost pull` removes Skeleton sections from node bodies and emits their fences
+last under the begin-from-this-structure banner.
 
 ## Checks
 
@@ -107,16 +98,18 @@ references:
 Grade whether the change preserves the logo guidance in `asset.logo`.
 ```
 
-`references` are node ids with optional heading anchors. Check bodies contain
-review instructions for the host agent; they are not run by ghost and are never
-part of generation context.
-
-## Gather / Pull / Review
-
-- `ghost gather` emits the cover above Available guidance, then coverage counts.
-  The guidance list is complete, unfiltered, and unranked. Checks are invisible.
-- `ghost pull` emits selected nodes in steering order and inlines small local
-  materials. Binary local materials become inspect-pointers. External materials
-  remain locators for the host agent to access only when the task requires them.
-- `ghost review` matches diff files to local node materials, offers relevant
-  checks, and emits a packet for the host agent to judge.
+`references` contains node ids with optional heading anchors. Check bodies are
+review instructions for the host agent. ghost validates and transports checks;
+it does not grade them.
+
+## Command behavior
+
+- `ghost gather` emits the cover, coverage counts, then a complete, unfiltered,
+  unranked node menu. Checks are absent.
+- `ghost pull` emits selected nodes in steering order, inlines eligible local
+  text materials once, leaves later duplicate pointers, turns binary materials
+  into inspect-pointers, and leaves external materials as locators.
+- `ghost review` matches touched files to exact local material paths, offers
+  relevant checks, and emits an advisory packet for the host agent.
+- `ghost export` bundles the package and audits which locators travel.
+- `ghost pulse` summarizes local gather and pull events.

package/dist/skill-bundle/references/self-check.md

@@ -35,7 +35,6 @@ Before generating, can you cite:
 - the governing principle, stance, or tradeoff?
 - the concrete materials, if exactness matters?
 - the applicable pattern, if structure matters?
-- the relevant exemplar and what it is normative for?
 - the anti-goal that blocks the generic version?
 - the hard invariants?
 - the conditions that apply or do not apply?

package/dist/skill-bundle/references/steering-audit.md

@@ -37,24 +37,15 @@ Report first:
 | Row | Status | Evidence | Next move |
 | --- | --- | --- | --- |
 | Retrieval | strong / weak | contexts, ids, cover | sharpen contexts or move universal guidance to the cover |
-| Concreteness | strong / thin | materials, fenced examples, Skeletons | add concrete locators, exemplars, or opening structures |
+| Concreteness | strong / thin | materials, fenced examples, Skeletons | add concrete locators, examples, or opening structures |
 | Anti-goals | present / missing / vague | `anti-goal.*`, review packet | write not-X-instead-Y replacements and material locators |
-| Consistency | clean / conflicting | concrete bodies vs rules | update stale examples; examples average with rules |
+| Consistency | clean / conflicting | guidance vs concrete material | update or remove stale material |
 | Stance | present / missing | cover, `principle.*` | write forced-choice principles |
 | Materials | present / missing | `materials`, inspect-pointers | point at real assets/components/tokens |
-| Exemplars | annotated / unannotated / converging / missing | fenced samples, screenshots, repeated runs | say what to copy and what is incidental; tighten applicability when unrelated tasks converge |
 | Patterns | bound-open / loose / missing | `pattern.*`, Skeletons | state applies / bound / open and add a Skeleton when opening structure matters |
 | Checks | covered / partial / missing | checks/, review packet | add checks for high-risk invariants |
 | Silence posture | defined / missing | cover | say when to proceed provisionally or ask |
 
-## Exemplar convergence
-
-When auditing repeated runs, compare unrelated asks that pulled the same
-exemplar. If they reproduce the same composition, section order, or decorative
-treatment without the exemplar's stated condition requiring it, the exemplar is
-steering beyond its intent. The next move is to tighten applicability, add a
-shape-appropriate exemplar, or remove the exemplar.
-
 ## Task-level readiness
 
 For a task, gather, pull, and report:

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@design-intelligence/ghost",
-  "version": "0.28.0",
+  "version": "0.29.0",
   "description": "ghost CLI for portable .ghost/ packages of brand guidance your agent reads before it builds, with advisory review after",
   "license": "Apache-2.0",
   "author": "Block, Inc.",

package/dist/skill-bundle/references/adapting-a-starter.md

@@ -1,110 +0,0 @@
----
-name: adapting-a-starter
-description: Transplant a starter ghost package — a body like vessel-light or the naked skeleton — into your own brand, one procedure from manifest id to regenerated refs.
-handoffs:
-  - label: Validate the adapted package
-    command: ghost validate --format json
-    prompt: Does the adapted package validate, and did any pruned rule orphan a check reference?
----
-
-# Recipe: Adapt A Starter Package
-
-**Goal:** turn an installed starter — a full body (`ghost init --body
-vessel-light`) or the naked skeleton (`ghost init`) — into *your* brand's
-brand guidance without shipping a self-contradicting package.
-
-The naked skeleton is factored by what must happen during adaptation:
-
-| Stratum | Files | On adaptation |
-| --- | --- | --- |
-| Cover | `brand.md` | Write it — essence in one paragraph, temperature, and brand-only refusals. Apply the admission test to every line: a violation visible in one element belongs in that element's chapter; visible in one view, in the composition chapter; visible only across the whole body of work, here. Keep a one-screen budget and delete every scaffolding sentence when real. |
-| Foundation | `foundation.*` | Answer each chapter's open section (`Palette`, `Typeface`, `Radius`, `Character`, `Warmth`), restate it as the brand's current answer, and edit misuse lists to the brand's real failure modes. |
-| Context | `context.*` | Add or re-tune after the open questions are answered; context nodes state only what inverts in a matching situation. |
-| Cliche floor | `cliche.*` | Prune — delete entries a foundation misuse list absorbs, delete the paired check flag with it, and replace generic entries with refusals only this brand makes. If a refusal passes the cover admission test, graduate it to `brand.md`. |
-| Materials and refs | `materials/*`, referenced implementations, refs | Add or regenerate so the prose has concrete material to inspect. |
-| Checks | `checks/*` | Keep paired with the nodes they enforce; delete or rewrite flags when their source rule changes. |
-
-Do the steps **in order and in one sitting** where possible. A half-adapted
-package is worse than an unadapted one: stale refs steer harder than any prose
-you rewrote, so stopping before refs and checks are current ships a package
-that contradicts itself.
-
-## The procedure
-
-1. **Change the manifest id.** Edit `id:` in `manifest.yml` to your brand's
-   name. This is deliberately first: it is the explicit act that marks the
-   adaptation as begun. Until it changes, the package honestly claims to be the
-   starter, and every consuming agent cites it as a starter default.
-2. **Write the cover.** Replace `brand.md` with the brand's essence in one
-   paragraph, the shared temperature of words and motion, and the refusals only
-   this brand makes. Test every line: a violation visible in one element moves
-   to that element's chapter; visible in one view, to the composition chapter;
-   only what shows solely across the whole body of work stays. Keep the cover
-   to one screen and delete every scaffolding sentence when it is real.
-3. **Answer the foundation chapters.** Walk each `foundation.*` node. Keep the
-   usage rules that describe the closed vocabulary; answer the open section as
-   the brand's current answer. Ask the human for undecided values; never
-   freehand a value and present it as brand-backed. Edit each misuse list to the
-   failures this brand actually needs to avoid.
-4. **Add or edit materials.** Record literal values where the implementation or
-   asset materials live, then add `materials` locators to the nodes that explain
-   them. Name each file explicitly; do not reach for glob patterns, which in a
-   live repo can capture unintended files into pulls. Role names can stay
-   stable while values change. The point is that a realizing agent can inspect
-   the same concrete source the prose governs. Starter and vendored packages
-   ship locators written against the source repo's layout, so after vendoring,
-   verify every locator resolves against this repo's actual paths, repoint the
-   ones that moved, and run `ghost validate` — `material-locator-dead` warnings
-   name the stale ones.
-5. **Re-tune contexts.** Revisit each `context.*` node after the foundation
-   answers exist. Keep only inversions that apply in that situation; delete
-   generic foundation rules repeated there, and add new contexts only when a
-   task situation truly bends the defaults.
-6. **Prune `cliche.median`.** Each rule is a `###` heading section; delete the
-   whole section for every rule a foundation misuse list now absorbs or your
-   brand legitimately violates. Do not rewrite surviving measured defaults into
-   taste. Then run `ghost validate`: every check reference orphaned by a pruned
-   heading surfaces as its own warning — delete the paired flag and its
-   reference from the check.
-7. **Regenerate refs.** Exemplars dominate prose: a prose rule contradicted by a
-   stale ref loses. Rebuild each ref against the new values and chapter answers,
-   keep any annotation headers current, and make each ref demonstrate its closed
-   sets completely. If the starter shipped no refs, generate them now — a
-   package with no exemplars steers at half strength.
-8. **Rewrite checks and near-miss nodes.** For each answered foundation chapter,
-   name the failure mode one step away from the answer and its replacement. Put
-   pre-generation guidance in nodes and review assertions in `checks/`; never
-   leave a check that asserts an obligation no node states.
-9. **Re-run the checks, including against refs.** `ghost validate` for package
-   shape, then review the regenerated refs against the median and value checks
-   (stage the ref changes and run `ghost review`). The floor only holds if the
-   refs hold it too: a ref that trips a median flag will teach every future
-   generation the violation.
-
-## Consuming an unadapted starter
-
-Work does not block on adaptation. Before the procedure runs (or midway through
-it), cite starter content honestly:
-
-- Cover scaffolding and unanswered foundation sections: **provisional** — never
-  plain brand guidance.
-- Foundation usage rules: **ghost-backed starter structure** until the human
-  answers the open sections and edits the misuse lists.
-- Surviving median rules: **owner-backed after init** — ghost stamps this
-  measured model behavior into every initialized package; you own the pruning and
-  any adaptation thereafter.
-- Context nodes: **conditional** — read only when their situation matches, and
-  revisit them after the foundation answers change.
-- The manifest id tells you which state you are in: a starter id means
-  unadapted.
-
-## Never
-
-- Never leave cover scaffolding in a real ghost package.
-- Never present your provisional value as the brand's answer.
-- Never leave stale refs alongside new values — regenerate or delete; a stale
-  exemplar outweighs rewritten prose.
-- Never prune a median rule without deleting its paired check flag, or keep a
-  check that asserts an obligation no node states.
-- Never pre-write the manifest id change into automation — it is the human's
-  act of ownership, the one step an agent should not take alone.