@design-intelligence/ghost 0.23.0 → 0.24.0

package/dist/skill-bundle/references/authoring-scenarios.md

@@ -1,19 +1,19 @@
 ---
 name: authoring-scenarios
-description: Choose the right human-agent workflow for authoring Ghost brand fingerprints.
+description: Choose the right human-agent workflow for authoring ghost packages.
 handoffs:
-  - label: Validate the fingerprint
+  - label: Validate the package
     command: ghost validate --format json
-    prompt: Classify this fingerprint's authoring scenario and confirm the package validates.
+    prompt: Classify this package's authoring scenario and confirm the package validates.
 ---
 
-# Recipe: Collaborative Fingerprint Authoring
+# Recipe: Collaborative Package Authoring
 
-**Goal:** help a human and agent co-author durable brand truths through
+**Goal:** help a human and agent co-author durable brand guidance through
 conversation — without laundering what a codebase happens to do into what the
 brand means.
 
-The fingerprint is medium-agnostic and is not derived from a repo. Its raw
+The ghost package is medium-agnostic and is not derived from a repo. Its raw
 material is **elicitation**: what the human says, shows, and points at — words,
 screenshots, links, exemplar products, marketing copy, a competitor they define
 themselves against. Agent synthesis is draft work until the human curates it
@@ -22,15 +22,15 @@ and ordinary Git review accepts it.
 Repo-bound reality — components, tokens, paths, building blocks — can be
 recorded as `materials` on the node whose prose explains their purpose. When a
 conversation surfaces "we have a component for that," treat it as material to
-locate and interpret, not as brand truth by itself.
+locate and interpret, not as brand guidance on its own.
 
 ## 1. Start With One Repeated Decision
 
-Do not try to fingerprint the whole brand at once. Ask the human for the one
+Do not try to capture the whole brand at once. Ask the human for the one
 decision whose feedback keeps repeating — the checkout always flagged for
 trust, the voice always re-toned, the empty state always rewritten — and
-capture that one truth as a node first. One high-confidence truth beats an
-empty catalog; the fingerprint grows as the next repeated decision shows up.
+capture that one decision as a node first. One well-grounded node beats an
+empty catalog; the package grows as the next repeated decision shows up.
 
 The scenario below tunes the authoring *posture* for that first node; it is not
 a gate to clear before writing anything.
@@ -38,19 +38,22 @@ a gate to clear before writing anything.
 | Scenario | Default authoring posture |
 | --- | --- |
 | Net new brand | Stance-first. Elicit feel, audience, and early anti-goals before anything else exists to point at. |
-| Established brand, first fingerprint | Artifact-rich interview. The human can show a lot — shipped surfaces, brand docs, campaigns. Elicit which of it is *intentional*. |
+| Established brand, first ghost package | Artifact-rich interview. The human can show a lot — shipped surfaces, brand docs, campaigns. Elicit which of it is *intentional*. |
 | Strong opinions, weak articulation | Example-led. The human knows it when they see it: work from exemplars and counter-exemplars ("this feels like us, this never would") toward the stance underneath. |
-| Brand doc or design-language deck exists | Distillation. The document is testimony, not truth: pull the claims that actually steer decisions, drop the aspirational filler, and have the human ratify each survivor. |
+| Brand doc or design-language deck exists | Distillation. Treat the document as evidence: pull the claims that actually steer decisions, drop the aspirational filler, and have the human ratify each survivor. |
 | Rebrand, redesign, migration | Transition-led. Capture current, target, and what must not be lost in between. |
-| Fork, white label, tenant variant | Shared base + local divergence. Keep common truths broad; scope divergence with conditions. |
+| Fork, white label, tenant variant | Shared base + local divergence. Keep shared guidance broad; scope divergence with conditions. |
 | Monorepo or product suite | One contract per package. |
 
+When supplied artifacts are the starting point or must be reconciled with an
+existing package, follow [distill.md](distill.md).
+
 If more than one applies, start with the broad scenario, then narrow.
 
 ## 2. Interview The Human
 
 The interview is the engine. Ask only high-leverage questions that change the
-fingerprint:
+guidance:
 
 - What should this brand feel like, and what should it never become? (The
   "never become" answers are anti-goal nodes — capture them with the same care
@@ -63,7 +66,7 @@ fingerprint:
 - What keeps getting flagged in review, re-toned, or rewritten?
 - Where do trust, density, pacing, accessibility, recovery, or disclosure
   matter most?
-- Which truths are universal, and which only hold under a specific situation?
+- Which guidance is universal, and which guidance holds only under a specific situation?
 
 Capture human-authored or human-approved answers as nodes. Do not treat
 unapproved notes as canonical.
@@ -73,7 +76,7 @@ unapproved notes as canonical.
 Ask for artifacts and read them closely: screenshots, links, exemplar products,
 brand docs, marketing copy, past campaigns, a rejected design and why it was
 rejected. Treat every artifact as *testimony* — evidence of a stance the human
-holds — never as truth by itself. A pattern that appears everywhere may be
+holds — never as guidance by itself. A pattern that appears everywhere may be
 legacy; a pattern that appears once may be the brand at its best. The human
 says which.
 
@@ -85,15 +88,15 @@ and enforced in review, not repeated as the model's main example.
 
 ## 4. Draft The Nodes
 
-Write the smallest useful set of nodes, each a purpose-coherent prose truth with
+Write the smallest useful set of nodes, each carrying purpose-coherent prose guidance with
 a one-line `description`, named `<kind>.<slug>.md` (or a bare slug when no kind is present). Ask three questions of each node body: why (the stance), with what
 (the materials), and how it is assembled (the patterns). These are drafting
 prompts, not fields.
 
-Draft only what the human said or showed. State universal truths plainly; give
-narrower truths a **condition** in the prose — the situation they apply in,
+Draft only what the human said or showed. State universal guidance plainly; give
+narrower guidance a **condition** in the prose — the situation they apply in,
 never a destination. Label uncertain reasoning as provisional. Prefer a few
-high-confidence truths over a broad catalog. Hold draft prose to the node prose
+focused guidance over a broad catalog. Hold draft prose to the node prose
 stances in [capture.md](capture.md) and score each node against its drafting
 gate before presenting drafts for curation.
 
@@ -103,7 +106,7 @@ Before treating draft content as durable, ask the human to classify important
 claims:
 
 - keep as canonical
-- soften into guidance
+- soften the guidance
 - reject as accidental or legacy
 - move to scratch notes
 - restate at a broader or narrower altitude (add or drop a condition)
@@ -115,10 +118,10 @@ Two authoring decisions replace any notion of hierarchy:
 - **Kind** — declare the kind vocabulary in `glossary.md` and name each node
   `<kind>.<slug>.md` so its normative weight is clear. The glossary defines what
   each kind means and how strongly it binds. Kinds are your choice;
-  Ghost ships no fixed vocabulary.
-- **Altitude** — state a truth at the level it is actually true. Universal → state
+  ghost ships no fixed vocabulary.
+- **Altitude** — state guidance at the level where it applies. Universal → state
   it plainly. Narrower → name the situation that activates it, in the prose. Never
-  file a truth by destination (`for-emails.md`); the model reads the condition and
+  file a node by destination (`for-emails.md`); the model reads the condition and
   decides when it applies.
 
 ## 7. Validate And Ratify
@@ -137,7 +140,7 @@ edits are drafts; checked-in nodes are canonical.
 The shapes below teach what steering prose looks like when it works. The
 examples use **Morrow Ledger**, a fictional bookkeeping product — teaching
 fiction for this recipe only, never content for a real corpus. Each shape is a
-pattern to imitate with the human's real truths.
+pattern to imitate with the human's real guidance.
 
 - **Stance as forced choices.** Not adjectives — decisions under pressure:
   "Clarity beats momentum: write '3 invoices are 14+ days late', not 'Cash
@@ -160,25 +163,25 @@ pattern to imitate with the human's real truths.
   teaches its accidents as brand.
 - **Material inventory.** `materials` locates; prose explains meaning:
   "`src/styles/tokens.css` should define the ink, ledger, amber, and paper
-  colors." Never duplicate API docs unless the API itself is the brand truth.
+  colors." Never duplicate API docs unless the API itself is the brand guidance.
 - **Decision trace.** A worked tradeoff with the reversal condition: "We chose
   visible evidence over shorter surfaces… Reverses when the evidence would
   expose sensitive third-party details — then show the count only." Models
   imitate reasoning as well as outputs.
 
 State the silence posture on the manifest-declared cover, which `gather`
-inlines for every task: when the fingerprint is silent, proceed provisionally
+inlines for every task: when the package is silent, proceed provisionally
 from local conventions only when safe, and ask before brand-defining,
 irreversible, legal, privacy-sensitive, or high-risk choices.
 
 ## Never
 
-- Never derive brand truth from repo code alone; what the codebase repeats may
+- Never derive brand guidance from repo code alone; what the codebase repeats may
   be legacy, not stance. Use repo paths as `materials` only after the prose
-  truth has been curated.
+  guidance has been curated.
 - Never draft a node the human neither said nor showed; that is invention
   wearing the brand's clothes.
 - Never treat a brand doc, an artifact, or repetition frequency as brand
   authority; the human ratifies what is intentional.
 - Never invent a hierarchy, inheritance, or edges — the package is flat.
-- Never file a truth by destination; state its condition in the prose.
+- Never file a node by destination; state its condition in the prose.

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

@@ -1,21 +1,21 @@
 ---
 name: blocks
-description: Author block and material nodes so an agent can match a fingerprint's stance to concrete building blocks.
+description: Author block and material nodes so an agent can match a ghost package's stance to concrete building blocks.
 handoffs:
   - label: List the node menu
     command: ghost gather
-    prompt: What materials does this fingerprint document, and what is absent?
+    prompt: What materials does this package document, and what is absent?
 ---
 
 # Recipe: Author Block And Material Nodes
 
 **Goal:** when you are documenting the **materials** a brand draws from — its
 building blocks, assets, and reusable pieces — write that prose so an agent can
-translate the fingerprint's stance into concrete building blocks without the
-fingerprint ever naming a component.
+translate the package's stance into concrete building blocks without the
+guidance ever naming a component.
 
 This is opinionated method, not new schema. **"Block node" is shorthand in this
-recipe, not a Ghost concept**: it means any node whose truth is a reusable
+recipe, not a ghost concept**: it means any node whose guidance is a reusable
 building block, whatever kind the author's glossary declares for it (`block`,
 `asset`, `pattern`, …). A block node is a node like any other: a markdown file
 with a `description` and a prose body, named `<kind>.<slug>.md` (or a bare
@@ -25,12 +25,11 @@ whatever keeps each node purpose-coherent.
 
 ## Where it sits
 
-A fingerprint declares stance. Block and material nodes ground that stance in
-concrete materials — they are what makes a node **concrete** in gather, pull
-ordering, and review matching. A realizing agent **reads** them and matches
-against them. Strip every block node and the fingerprint is still valid — it
-just gives the agent less to draw on, and prose-only steering is weak steering.
-The agent does the matching.
+A ghost package declares stance. Block and material nodes ground that stance in
+concrete material: materials, substantial fenced examples, or Skeletons. A
+realizing agent **reads** them and matches against them. Strip every block node
+and the package is still valid — it just gives the agent less to draw on,
+and prose-only steering is weak steering. The agent does the matching.
 
 ## Concreteness is the grounding dial
 
@@ -51,7 +50,7 @@ Neither is correct. A concrete block node is a deliberate trade, not a leak.
   the absence of a body is the signal that training priors are acceptable here.
   When a primitive is itself brand-distinctive (a button whose shape, weight, or
   focus treatment is a recognizable brand move), its *divergence from the
-  generic form* is a truth worth a body: state what differs and why, not the
+  generic form* is a decision worth a node: state what differs and why, not the
   full API.
 - **Anything that encodes a user moment** (confirmation, plan, task, tool,
   reasoning, sources…) earns **one short prose body**. This is what the method is
@@ -85,15 +84,15 @@ when (use X instead) / never*:
 
 Keep props, markup, and API reference out; the body documents purpose, and the
 implementation beneath it is swappable. Explicit values are the exception when
-the value itself is the brand truth — an exact color, a specific corner radius —
+the value itself is the brand guidance — an exact color, a specific corner radius —
 not a swappable implementation detail.
 
 ## How a match runs
 
-The agent reads the fingerprint's stance, `gather`s the menu, ranks candidate
-block nodes by description, separates near-neighbors on *not when* and
-*never*, and assembles. The realizing surface authors the chosen blocks in its
-medium. The fingerprint never named a component; the agent bridged via documented
+The agent reads the package's stance, `gather`s the menu, pulls block nodes
+whose descriptions apply, separates near-neighbors on *not when* and *never*,
+and assembles. The realizing surface authors the chosen blocks in its medium.
+The guidance never named a component; the agent bridged via documented
 purpose.
 
 ## Curation rule
@@ -156,7 +155,7 @@ divergence from the generic form would earn a short body.)
 ## Materials: bundle brand-owned materials, reference implementations
 
 Use the rule of thumb literally. Bundle brand-owned materials: brand-owned artifacts that
-should travel with the fingerprint and survive export or refactors — tokens.css,
+should travel with the package and survive export or refactors — tokens.css,
 motion.json, logo.svg, type materials. Reference implementations: living app
 code, components, stories, or tests whose home is still the product repo. The
 `materials` list locates both; the prose says what the material proves.
@@ -174,7 +173,7 @@ prop APIs re-imports implementation opinion and creates a mirror to maintain.
   of a body is the signal. A brand-distinctive primitive earns a body for its
   divergence, never for its API.
 - Never put props, markup, or API reference in a block body; explicit
-  values belong only when the value itself is the brand truth.
-- Never let the fingerprint reference the realizing surface; blocks are read,
+  values belong only when the value itself is the brand guidance.
+- Never let the package reference the realizing surface; blocks are read,
   not addressed.
 - Never split two blocks that answer the same first question; that is one node.

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

@@ -1,20 +1,22 @@
 ---
 name: brief
-description: Build a compact pre-generation packet from pulled Ghost truths.
+description: Build a compact pre-generation packet from pulled ghost guidance.
 ---
 
-# Recipe: Brief Work From Ghost Fingerprint
+# Recipe: Brief Work From ghost Package
 
 A brief is an ephemeral steering packet for the generating pass. It is not a new
 schema and is never written back into `.ghost/`.
 
 1. Run `ghost gather <ask> --format json` and select against descriptions.
-2. The cover is already in context. Pull a small set from the menu: **3–5 nodes
-   is normal; 10 is a bad selection** unless the task is unusually broad.
-3. Prefer concrete nodes: `materials`, substantial fenced examples, or a
-   `## Skeleton`. If there is **no concrete material for this surface**, the
-   readiness ceiling is **Yellow**.
-4. Keep provisional reasoning visibly separate from Ghost-backed claims.
+2. The cover is already in context and outside selection. Pull every applicable
+   node with `ghost pull <id> [<id>…]`; skip nodes whose stated situation does
+   not apply. Topic overlap alone is not applicability.
+3. Note gather payload labels where present: `materials`, substantial fenced
+   examples, or a `## Skeleton`. If there is no concrete material for this
+   surface, the readiness ceiling is **Yellow**.
+4. If no node applies, name the package's silence, follow the cover silence
+   posture, and keep provisional reasoning separate from ghost-backed claims.
 
 ## The packet: five sections only
 
@@ -34,14 +36,14 @@ Return this shape:
 - matching pulled Skeleton, or "none pulled"
 
 ## Silent / provisional
-- what Ghost does not cover and what local evidence carries
+- what ghost does not cover and what local evidence carries
 ```
 
 Rules:
 
 - Do not add sections for every kind. Sections dilute instruction weight.
-- Treat `ghost pull` ordering as signal: stance first, concrete material next,
-  prose rules, Skeletons dead last.
+- Treat `ghost pull` ordering as packet structure: stance first, concrete-material
+  nodes next, prose rules, Skeletons dead last.
 - If a pulled Skeleton matches the surface, begin the artifact from it verbatim
   before filling.
 - Anti-goals are review-critical: state the positive replacement, not just the

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

@@ -1,26 +1,26 @@
 ---
 name: capture
-description: Author repo-local Ghost brand fingerprints as a flat set of prose nodes.
+description: Author repo-local ghost packages as a flat set of prose nodes.
 handoffs:
   - label: Inspect the package
     command: ghost validate
-    prompt: Does this fingerprint package validate, and what is absent?
+    prompt: Does this ghost package validate, and what is absent?
 ---
 
-# Recipe: Author Ghost Fingerprint
+# Recipe: Author ghost Package
 
-**Goal:** record durable brand truths in `.ghost/` as a flat set of prose
+**Goal:** record durable brand guidance in `.ghost/` as a flat set of prose
 **nodes**. If a change is uncommitted, it is draft work. If it is checked in,
-Ghost treats the fingerprint package as canonical.
+ghost treats the `.ghost/` package as canonical.
 
 ```text
 .ghost/
   manifest.yml          # schema + id
   glossary.md           # the kind vocabulary + what each kind means
-  principle.trust.md    # a brand truth of kind `principle`
+  principle.trust.md    # guidance of kind `principle`
   pattern.invoice.md    # a pattern with an optional ## Skeleton
   anti-goal.generic.md  # a review-critical replacement rule
-  voice.md              # a brand truth without a kind
+  voice.md              # guidance without a kind
 ```
 
 A **node** is a markdown file: a `description`, optional `materials`, and a
@@ -68,6 +68,30 @@ The annotation is load-bearing. A bare sample teaches form; the annotation
 teaches which features of the form are intentional, which stops an agent from
 copying incidental details.
 
+An exemplar should identify eight things in prose:
+
+1. the rendered artifact the agent should inspect;
+2. the implementation, fixture, or source that produced it;
+3. what is intentional and load-bearing;
+4. what is incidental and should change with task facts;
+5. the observable conditions where it applies;
+6. the content, viewport, or state conditions that challenge or break it;
+7. the current materials it demonstrates;
+8. provenance, owner, review date, or compatibility signal when freshness
+   matters.
+
+Put locators in `materials`: render, implementation, assets, source, or external
+reference. Put interpretation in the body. Ownership and freshness also live in
+prose, the exemplar artifact, or a repo-owned system; they are not structured
+`materials` metadata.
+
+A rendered exemplar proves one solution under stated conditions. It is not a
+universal visual target. Provide one exemplar for each distinct,
+composition-critical surface shape that earns one, and say which details may be
+reused. If unrelated tasks start converging on the same composition, section
+order, or decoration, tighten applicability, add a shape-appropriate exemplar,
+or remove the exemplar.
+
 Protect exact voice artifacts the same way. A real on-brand error message
 out-steers a paragraph about error-message voice:
 
@@ -177,21 +201,25 @@ Near the moment of payment, reduce felt risk. Proximity of reassurance to the
 action beats completeness...
 ```
 
-- **`description`** is how an agent finds the node: a one-line "what this is and
-  when to gather it." `ghost gather` emits the menu of id, kind, description,
-  concrete coverage, and material count; the agent matches the ask against it.
+- **`description`** is how an agent finds the node: a compact retrieval payload
+  naming what the node governs, the observable condition under which it applies,
+  and what it contributes when useful. `ghost gather` emits id, kind,
+  description, concrete coverage, payload labels, and material count; the agent matches the ask
+  against applicability.
 - **Kind is the filename prefix** and must be a kind the glossary declares. A
   bare name (`voice.md`) has no kind.
-- **Altitude lives in the prose.** State a universal truth plainly; give a
-  narrower truth its **condition** — the situation it applies in — in the prose.
-  Never file a truth by destination (`for-emails.md`).
+- **Altitude lives in the prose.** State universal guidance plainly; give a
+  narrower guidance a **condition** — the situation it applies in — in the prose
+  and usually in the description. Do not use broad universal imperatives unless
+  universal retrieval is intended. Never file a node by destination
+  (`for-emails.md`).
 - **Concreteness is derived.** A node carries concrete material when it has
   `materials`, a substantial fenced example, or a `## Skeleton`. You do not
   declare a separate type.
 
 ## What a node body answers
 
-While drafting, ask three questions of every truth — *why* (the stance), *with
+While drafting, ask three questions of every node — *why* (the stance), *with
 what* (the materials), and *how it is assembled* (the patterns). These are
 drafting prompts, never frontmatter keys, node types, or required sections, and
 a node may answer only one. Each answer lands as a steering dimension the
@@ -200,15 +228,15 @@ machinery already scores:
 - **why** lands as stance prose — read first in `ghost pull`, weakest at
   moving output form on its own; it is the yardstick every later selection is
   measured against.
-- **with what** lands as `materials` and concreteness — drives pull ordering
-  and `ghost review` matching. See [blocks.md](blocks.md) for authoring
+- **with what** lands as `materials` and concreteness — affects pull packet
+  order and `ghost review` matching. See [blocks.md](blocks.md) for authoring
   material-backed nodes.
 - **how it is assembled** lands as patterns and `## Skeleton` sections — the
   strongest steering; Skeleton fences are extracted and emitted dead last so
   generation starts from them.
 
-Keep a node **purpose-coherent**: one truth, any length. Split only when it is
-genuinely a different truth.
+Keep a node **purpose-coherent**: one coherent decision, any length. Split only when it
+contains a separate decision with different applicability.
 
 ## Node prose stances
 
@@ -228,7 +256,7 @@ Two carve-outs come first, because they invert ordinary prose advice:
 Everywhere else:
 
 - **No aspirational abstractions.** "We value clarity and trust" steers
-  nothing. Name the decision the truth forces: what gets picked when two goods
+  nothing. Name the decision the guidance forces: what gets picked when two goods
   compete, and what gets given up.
 - **Descriptions must discriminate.** Read the description alone. If it also
   fits a competitor's brand, it is retrieval-dead; rewrite it until it could
@@ -239,7 +267,7 @@ Everywhere else:
 - **Ban brand-deck filler.** "Elevate," "delight," "seamless," "best-in-class,"
   "empower." When a brand doc supplies these words, they are testimony to
   distill, never prose to keep.
-- **Settle the altitude on purpose.** Every truth is either claimed universal
+- **Settle the altitude on purpose.** Every node is either claimed universal
   or given its condition in the prose. A node body that does neither was never
   curated for altitude; ask the human which it is.
 
@@ -262,12 +290,12 @@ in curation still decides what becomes canonical.
 
 ## Author through steering jobs
 
-The steering jobs are questions, not mandatory fields. Encode the truth in the
+The steering jobs are questions, not mandatory fields. Encode the guidance in the
 strongest form that fixes the observed failure.
 
 | If the agent keeps... | Author... |
 | --- | --- |
-| missing the truth | sharper `description`; move universal truth to the cover |
+| missing the guidance | sharper `description`; move universal guidance to the cover |
 | inventing values | `asset.*` node with materials and exact names |
 | producing generic output | `anti-goal.*` replacement plus annotated `exemplar.*` |
 | choosing the wrong structure | `pattern.*` with bound/open and a `## Skeleton` |
@@ -278,11 +306,11 @@ strongest form that fixes the observed failure.
 
 A `concept.*` node holds a one-time creative move — a launch hook, a
 campaign idea, a specific non-median leap the corpus would not have produced
-by recombining its other truths. Scope it explicitly to the task or surface
+by recombining its other guidance. Scope it explicitly to the task or surface
 it was written for, keep it distinct from invariants, and do not generalize
 it into permanent brand law. If it proves reusable later, promote it into an
 exemplar or pattern deliberately; do not let a one-off default into durable
-truth by accumulation.
+guidance through accumulation.
 
 Ask while authoring:
 
@@ -301,7 +329,7 @@ Ask while authoring:
 
 Decide which posture fits before scaffolding. Follow
 [authoring-scenarios.md](authoring-scenarios.md) when setting up or substantially
-revising a fingerprint. Human intent anchors the truths; what the human says and
+revising a ghost package. Human intent anchors the guidance; what the human says and
 shows — words, images, links, exemplars — is the evidence; agent synthesis is
 draft work until a human curates it and Git review accepts it.
 
@@ -316,12 +344,12 @@ ghost validate
 
 `ghost init` seeds the skeleton starter: the manifest, a starter
 `glossary.md`, a `brand.md` cover, foundation chapters with open questions, and
-the model cliche floor. Replace open questions with real product truth before
+the model cliche floor. Replace open questions with real product guidance before
 using it to steer generation. Use `ghost init --template minimal` for a
 manifest, glossary, cover, and cliche floor.
 
 Write the manifest-declared cover as the human-curated front door:
-non-negotiables that apply to every task, what the fingerprint covers, and any
+non-negotiables that apply to every task, what the package covers, and any
 stricter silence posture. `ghost gather` inlines it before the menu, so anything
 that must never be missed belongs there.
 
@@ -336,7 +364,7 @@ feed-back only; they are never gathered.
 
 Declare the kinds you will use in `glossary.md` — the frontmatter `kinds` list
 plus a `#` section per kind explaining its meaning and normative weight. Kinds
-are your choice; Ghost ships no fixed vocabulary. A node's filename prefix must
+are your choice; ghost ships no fixed vocabulary. A node's filename prefix must
 match a declared kind (or the node has no kind).
 
 The glossary is a dictionary of every term with defined meaning in the corpus.
@@ -349,17 +377,17 @@ hygiene, not over-structure.
 Elicit the brand from the human, not from a codebase. Interview for stance,
 audience, anti-goals, and exemplars; ask for the material they can show —
 screenshots, links, exemplar products, brand docs, copy they love or hate. Treat
-every artifact as testimony to curate, never truth to copy verbatim. Repo-bound
-reality can be recorded as `materials` on the node whose prose explains its
-purpose.
+every artifact as evidence to curate, never guidance to copy verbatim. When
+supplied artifacts are the starting point or must be reconciled with existing
+guidance, follow [distill.md](distill.md). Repo-bound reality can be recorded as
+`materials` on the node whose prose explains its purpose.
 
 ### 5. Write sparse nodes
 
-Add the smallest useful set of nodes, each a purpose-coherent prose truth
+Add the smallest useful set of nodes, each carrying purpose-coherent prose guidance
 answering why, with what, or how it is assembled, named `<kind>.<slug>.md` or a
 bare slug. Draft only what the
-human said or showed. State conditions as situations in the prose. Prefer a few
-high-confidence truths over a noisy catalog. Hold each draft to the node prose
+human said or showed. State conditions as situations in the prose. Prefer a small amount of focused, well-grounded guidance over a noisy catalog. Hold each draft to the node prose
 stances and score it before curation; a node below the gate returns to the
 interview. Ask the human to keep, soften,
 reject, or re-title important claims before treating draft nodes as durable.
@@ -377,12 +405,12 @@ Undeclared kind prefixes and malformed Skeleton sections are warnings.
 ## Never
 
 - Never describe any file outside `.ghost/` as canonical package input.
-- Never derive a brand truth from repo code alone; what a codebase repeats may
-  be legacy, not stance. Use repo paths as `materials` only when the prose truth
+- Never derive brand guidance from repo code alone; what a codebase repeats may
+  be legacy, not stance. Use repo paths as `materials` only when the prose guidance
   has been curated.
 - Never draft a node the human neither said nor showed.
 - Never invent a hierarchy, inheritance, or cross-node edges — the package is
   flat.
-- Never file a truth by destination; state its condition in the prose.
+- Never file a node by destination; state its condition in the prose.
 - Never ship a blacklist-only anti-goal; state the replacement and enforce the
   hard line in review.

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

@@ -1,6 +1,6 @@
 ---
 name: concrete-tiers
-description: Decide which concrete code tiers a fingerprint carries — tokens, skeletons, components, exemplars — and justify every absence.
+description: Decide which concrete code tiers a ghost package carries — tokens, skeletons, components, exemplars — and justify every absence.
 handoffs:
   - label: Audit what the package carries today
     command: ghost gather
@@ -10,10 +10,10 @@ handoffs:
 # Recipe: Choose The Concrete Code Tiers
 
 **Goal:** decide, deliberately, which tiers of concrete code material a
-fingerprint carries — and be able to say why any tier is absent. Absence
+package carries — and be able to say why any tier is absent. Absence
 should be a decision, not a default.
 
-Prose states a truth; concrete code makes it the cheapest continuation. A
+Prose states guidance; concrete code makes it the cheapest continuation. A
 package can carry code at four tiers, and each does a different job during
 generation:
 
@@ -30,7 +30,7 @@ Two properties decide whether a tier steers, and they are not the same thing:
   skeleton one block, an exemplar one whole surface.
 - **Delivery** — whether the material is guaranteed to reach the agent.
   Skeleton blocks live in node bodies, so `ghost pull` delivers them with the
-  truth. Files behind `materials:` locators reach only agents that spend a
+  guidance. Files behind `materials:` locators reach only agents that spend a
   turn reading them. A tier the agent never sees contributes nothing;
   presence in the package is not presence in context.
 
@@ -57,15 +57,15 @@ The other three tiers are earned by the package's shape:
 
 ## Every tier is a copy that can drift
 
-Each tier repeats the token truth, and a stale copy steers harder than the
+Each tier repeats the token decision, and a stale copy steers harder than the
 prose that corrects it. A hardcoded value in an exemplar where a token
 exists is a lie waiting for a rename. Before adding a tier, accept its
 maintenance bill; after any token change, sweep every tier for stranded
 literals.
 
-A tier can also fight the package's stance. A package whose truth is
+A tier can also fight the package's stance. A package whose guidance is
 "compose each surface fresh from the tokens" contradicts itself by shipping
-a component kit; a package whose truth is "compose from the grammar, the
+a component kit; a package whose guidance is "compose from the grammar, the
 refs are examples not a framework" hardens toward template convergence if
 every pattern carries a mandatory skeleton. When a tier and the stance
 conflict, the stance wins — that absence is the package expressing itself.