@design-intelligence/ghost 0.20.0 → 0.22.0

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

@@ -19,14 +19,13 @@ Ghost treats the fingerprint package as canonical.
   glossary.md           # the kind vocabulary + what each kind means
   principle.trust.md    # a brand truth of kind `principle`
   pattern.invoice.md    # a pattern with an optional ## Skeleton
-  anti-goal.generic.md  # a guard when its kind declares posture: guard
+  anti-goal.generic.md  # a review-critical replacement rule
   voice.md              # a brand truth without a kind
 ```
 
 A **node** is a markdown file: a `description`, optional `materials`, and a
 prose body. The package is **flat** — no hierarchy, no inheritance, no edges. A
-node's kind comes from its filename prefix; the glossary declares the kinds and
-may declare consumption posture such as `posture: guard`.
+node's kind comes from its filename prefix; the glossary declares the kinds.
 
 ## Lead with an annotated exemplar over a complete artifact
 
@@ -89,6 +88,21 @@ safe before what to do. One calm next step. No "Oops," no exclamation points,
 no blame on the user or the network.
 ```
 
+## Write patterns as bound and open
+
+A pattern node binds part of a reusable structure and leaves the rest open.
+State both explicitly:
+
+- **Bound** — what the agent should not redecide: the structural moves fixed
+  regardless of task (what renders first, what appears exactly once, what may
+  never compete for attention).
+- **Open** — where the agent may choose, within limits (which evidence shape
+  fits, how tone flexes, where secondary content may go).
+
+If everything is bound, the node is a template, not a pattern. If nothing is
+bound, it is vibes, not steering. A pattern may also `Refines:` a broader
+principle by id; when the two conflict, the principle wins.
+
 ## Add Skeletons when the opening structure matters
 
 A `## Skeleton` section contains the literal opening structure the agent should
@@ -119,18 +133,12 @@ Keep them short, specific, and attached to concrete objects whenever possible:
 Do not turn every observation into a rule. Stale or generic rules average
 against the exemplars and pull the packet back toward the median.
 
-## Write guards as replacement, not as blacklist
+## Write anti-goals as replacement, not as blacklist
 
-A guard is ordinary node prose whose kind declares `posture: guard` in
-`glossary.md`:
+An anti-goal is ordinary node prose whose kind the glossary defines as a
+review-critical replacement rule.
 
-```yaml
-kinds:
-  - name: anti-goal
-    posture: guard
-```
-
-A good guard states **not X; instead Y; recognize the switch by Z**. The
+A good anti-goal states **not X; instead Y; recognize the switch by Z**. The
 replacement matters because negation alone raises the salience of the rejected
 thing.
 
@@ -148,12 +156,12 @@ Instead: flat paper surfaces, one restrained accent, square alignment, and a
 next action backed by the number or source that justifies it.
 
 Recognize the switch: if removing the logo would make the surface look like any
-SaaS template, the guard failed even when every token is technically valid.
+SaaS template, the anti-goal failed even when every token is technically valid.
 ```
 
 The strongest anti-goal is silent: purged from exemplars, absent from starter
-structures, and enforced by a probe-backed check in review. Use guard prose to
-name the replacement; use checks and `probe:` commands to catch regressions.
+structures, and enforced by a probe-backed check in review. Use anti-goal prose
+to name the replacement; use checks and `probe:` commands to catch regressions.
 
 ## The node shape
 
@@ -181,7 +189,7 @@ action beats completeness...
   `materials`, a substantial fenced example, or a `## Skeleton`. You do not
   declare a separate type.
 
-## What a body answers
+## What a node body answers
 
 While drafting, ask three questions of every truth — *why* (the stance), *with
 what* (the materials), and *how it is assembled* (the patterns). These are
@@ -204,15 +212,15 @@ genuinely a different truth.
 
 ## Node prose stances
 
-Node prose is steering payload. A generic sentence in a body averages every
+Node prose is steering payload. A generic sentence in a node body averages every
 future generation toward the median, so hold drafts to these stances before the
 human sees them.
 
 Two carve-outs come first, because they invert ordinary prose advice:
 
-- **Guards keep their negation.** "Not X; instead Y; recognize the switch by Z"
-  is the required guard form. Naming the rejected thing is the guard's job;
-  never "improve" a guard by stating only the replacement.
+- **Anti-goals keep their negation.** "Not X; instead Y; recognize the switch
+  by Z" is the required anti-goal form. Naming the rejected thing is the
+  anti-goal's job; never "improve" one by stating only the replacement.
 - **Invariants keep their absolutes.** "Never" and "always" are correct in an
   invariant when the hard line is real and human-ratified. Absolutes are lazy
   only when they stand in for an uncurated stance.
@@ -226,13 +234,13 @@ Everywhere else:
   fits a competitor's brand, it is retrieval-dead; rewrite it until it could
   belong to no one else.
 - **Cut unratified hedges.** "Generally," "where possible," and "consider" in a
-  body mean the human never picked a side. Get the ratification or cut the
+  node body mean the human never picked a side. Get the ratification or cut the
   sentence.
 - **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
-  or given its condition in the prose. A body that does neither was never
+  or given its condition in the prose. A node body that does neither was never
   curated for altitude; ask the human which it is.
 
 ## Score drafts before curation
@@ -244,7 +252,7 @@ dimension:
 | --- | --- |
 | Testimony | Can you quote the human words or artifact this node came from? |
 | Discrimination | Does the description fit only this brand? |
-| Force | Does the body decide something, or merely describe something? |
+| Force | Does the node body decide something, or merely describe something? |
 | Altitude | Is it universal on purpose, or given its condition? |
 | Residue | Is it free of starter-demo prose and brand-deck filler? |
 
@@ -259,15 +267,23 @@ strongest form that fixes the observed failure.
 
 | If the agent keeps... | Author... |
 | --- | --- |
-| missing the truth | sharper `description` / `index` mention |
+| missing the truth | sharper `description`; move universal truth to the cover |
 | inventing values | `asset.*` node with materials and exact names |
-| producing generic output | `anti-goal.*` guard plus annotated `exemplar.*` |
+| producing generic output | `anti-goal.*` replacement plus annotated `exemplar.*` |
 | choosing the wrong structure | `pattern.*` with bound/open and a `## Skeleton` |
 | crossing hard lines | invariant prose plus a check, optionally with `probe:` |
 | applying guidance too broadly | condition in prose |
 | making bad tradeoffs | `decision.*` trace |
 | producing correct but forgettable work | scoped `concept.*` |
 
+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
+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.
+
 Ask while authoring:
 
 - What complete artifact shows the brand at its best?
@@ -298,19 +314,16 @@ ghost init            # scaffolds the steering starter
 ghost validate
 ```
 
-`ghost init` seeds the steering starter: the manifest, a starter `glossary.md`
-(with suggested kinds you keep, rename, or replace), the package-root
-`index.md`, and worked demo nodes for stance, composition, anti-goals, patterns,
-exemplars, materials, and decisions. Replace demo claims, paths, examples, and
-decisions with real product truth before using it to steer generation. Use
-`ghost init --template minimal` when you only want the small
-manifest/glossary/index starter.
+`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
+using it to steer generation. Use `ghost init --template minimal` for a
+manifest, glossary, cover, and cliche floor.
 
-Write `index.md` as the human-curated front door: non-negotiables that apply to
-every task, what this fingerprint covers, how its kinds organize the corpus, and
-any stricter silence posture. It is an ordinary node mechanically, but by
-convention agents pull it first — anything that must never be missed belongs
-here.
+Write the manifest-declared cover as the human-curated front door:
+non-negotiables that apply to every task, what the fingerprint covers, and any
+stricter silence posture. `ghost gather` inlines it before the menu, so anything
+that must never be missed belongs there.
 
 Nodes may carry a `materials` list in frontmatter: repo-relative paths/globs or
 HTTPS URLs for the concrete materials the prose governs. Put brand-owned
@@ -324,9 +337,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
-match a declared kind (or the node has no kind). Use `posture: guard` for kinds
-whose nodes are review-critical replacements; use `posture: wild` only for
-truths that should stay opt-in.
+match a declared kind (or the node has no kind).
 
 The glossary is a dictionary of every term with defined meaning in the corpus.
 A root `voice.md` with a `voice` glossary entry declares the scope for future

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

@@ -0,0 +1,95 @@
+---
+name: concrete-tiers
+description: Decide which concrete code tiers a fingerprint carries — tokens, skeletons, components, exemplars — and justify every absence.
+handoffs:
+  - label: Audit what the package carries today
+    command: ghost gather
+    prompt: Which nodes carry concrete material, and which of the four tiers does the package cover?
+---
+
+# 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
+should be a decision, not a default.
+
+Prose states a truth; concrete code makes it the cheapest continuation. A
+package can carry code at four tiers, and each does a different job during
+generation:
+
+| Tier | Form | What it buys |
+| --- | --- | --- |
+| Tokens | `materials/tokens.css`, linked from nodes | Named values — the agent stops inventing colors, sizes, and durations. |
+| Skeletons | `## Skeleton` HTML blocks inside pattern nodes | The opening structure — layout is committed before the generic default can win the first tokens. |
+| Components | primitive classes or a class vocabulary in `materials/` | Reusable styling decisions — padding, variants, and states compress into names. |
+| Exemplars | a complete surface with load-bearing moves annotated | Cross-node interactions — the constraints no single node states, demonstrated working together. |
+
+Two properties decide whether a tier steers, and they are not the same thing:
+
+- **Scope** — what the tier constrains: a token constrains one value, a
+  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
+  turn reading them. A tier the agent never sees contributes nothing;
+  presence in the package is not presence in context.
+
+## The floor and the earned tiers
+
+**Tokens are the floor.** Every package that steers visual output carries a
+token vocabulary, and every other tier repeats those token names. That
+repetition is the one redundancy worth keeping: the same name appearing in
+prose, skeleton, and exemplar is what stops the agent from inventing
+plausible near-miss values.
+
+The other three tiers are earned by the package's shape:
+
+- **Skeletons** pay when the package specifies few, composition-critical
+  surfaces — where the first structural commitment decides everything
+  downstream — and when consuming agents may read only pulled bodies.
+- **Components** pay when the package covers many diverse surfaces generated
+  often, and the consuming agent reads material files. A class vocabulary
+  amortizes across surfaces; for a single surface shape it is dead weight.
+- **Exemplars** pay almost everywhere: they are the cheapest way to show
+  tiers interacting. One per distinct surface shape; a package with one
+  exemplar and many surface shapes pulls every task toward the demonstrated
+  shape.
+
+## Every tier is a copy that can drift
+
+Each tier repeats the token truth, 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
+"compose each surface fresh from the tokens" contradicts itself by shipping
+a component kit; a package whose truth 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.
+
+## Annotate whatever code ships
+
+Un-annotated code teaches content along with structure. Whatever tier the
+package carries, split the annotation two ways: name the load-bearing moves
+(what makes it this brand — copy these) and mark the incidental content
+(domain, figures, labels — swap these). An exemplar without this split
+teaches the agent that the example's subject matter is the brand.
+
+## The self-check
+
+For any package, answer four questions:
+
+1. Where does the value vocabulary live? (If not a token file: why?)
+2. What forces the opening structure of the package's most
+   composition-critical surface? (If nothing: is that surface's structure
+   genuinely open?)
+3. What demonstrates the cross-node constraints working together? (If
+   nothing: which interactions is the agent left to infer?)
+4. For every tier present: will the consuming agent actually have it in
+   context when it generates?
+
+Any answer may legitimately be "absent, because" — the recipe's only
+requirement is that the "because" exists.

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

@@ -5,14 +5,9 @@ description: Gather and pull the applicable Ghost brand truths for a task.
 
 # Recipe: Recall Ghost Fingerprint
 
-Wild posture is opt-in. Default `ghost gather` excludes kinds whose glossary
-entry declares `posture: wild`; use `--wild` only when the brief names explicit
-open territory where conformance is suspended. Guard posture stays visible by
-default because guards are brand-defining.
-
-1. Run `ghost gather <ask>` for the actual task. Read the coverage line: all
-   prose-only fingerprints are weak steering, and guard count tells you whether
-   review-critical negative space exists.
+1. Run `ghost gather <ask>` for the actual task. The cover is inlined by gather;
+   do not pull it separately. Read the coverage line: all-prose fingerprints are
+   weak steering.
 2. Select against `description`; Ghost never selects for you.
 3. Run `ghost pull <id> [<id>…]`. Prefer `pull` over reading files directly: it
    orders the packet for steering, inlines small local materials, emits
@@ -23,14 +18,13 @@ default because guards are brand-defining.
 
 `ghost pull` emits selected nodes in steering order:
 
-1. `index` / stance first: non-negotiables and silence posture.
+1. Cover first, when explicitly selected; normally it is already inlined by
+   gather and should not be pulled separately.
 2. Concrete-material nodes: `materials`, substantial fenced examples, or
    `## Skeleton` sections, with materials inlined or pointed to inspect.
 3. Prose-only rules: principles, conditions, decisions, and other rules without
    concrete payload.
-4. Guard nodes: `posture: guard`, flagged review-critical; read the replacement
-   carefully.
-5. Skeleton fences dead last: if one matches the surface, start from that
+4. Skeleton fences dead last: if one matches the surface, start from that
    structure verbatim.
 
 Return the selected truths with node ids, how each applies, and where the

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

@@ -1,6 +1,6 @@
 ---
 name: schema
-description: The Ghost fingerprint package shape: flat nodes, derived concreteness, Skeletons, guards, probes, and checks.
+description: The Ghost fingerprint package shape: flat nodes, derived concreteness, Skeletons, probes, and checks.
 ---
 
 # Ghost Fingerprint Package Reference
@@ -9,8 +9,8 @@ Canonical package:
 
 ```text
 .ghost/
-  manifest.yml        ghost.fingerprint-package/v1: schema + id
-  glossary.md         kind vocabulary + meanings + optional posture
+  manifest.yml        ghost.fingerprint-package/v1: schema + id + optional cover
+  glossary.md         kind vocabulary + meanings
   materials/          bundled materials; never a node source
   <kind>.<slug>.md    a brand truth of a declared kind
   <slug>.md           a brand truth without a kind
@@ -20,25 +20,16 @@ Canonical package:
 Reserved at the root: `manifest.yml`, `glossary.md`, `materials/`, and
 `checks/`. Every other `*.md` is a node.
 
-## Glossary posture
+## Manifest
 
-A kind may declare posture. Omitted posture defaults to `steady`.
+`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.
 
-```yaml
-kinds:
-  - name: principle
-  - name: anti-goal
-    posture: guard
-  - name: provocation
-    posture: wild
-```
-
-- `steady`: default, gathered normally.
-- `guard`: review-critical negative space. Stays in default gather, appears at
-  the tail of `ghost pull`, and is auto-offered by `ghost review` when its
-  materials match touched files.
-- `wild`: deliberate push beyond the fingerprint. Default gather excludes wild
-  kinds unless `--wild` is explicit.
+`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.
 
 ## Nodes
 
@@ -110,10 +101,10 @@ probes are the same class as npm scripts; Git review is the boundary.
 
 ## Gather / Pull / Review
 
-- `ghost gather` emits the node menu, including coverage counts. Checks are
-  invisible.
+- `ghost gather` emits the cover above the node menu, then coverage counts.
+  Checks are invisible.
 - `ghost pull` emits selected nodes in steering order and inlines small local
   materials. Binary local materials become inspect-pointers.
 - `ghost review` matches diff files to local node materials, offers relevant
-  checks and matched guard nodes, embeds probe evidence, and emits a packet for
-  the host agent to judge.
+  checks, embeds probe evidence, and emits a packet for the host agent to
+  judge.

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

@@ -60,6 +60,6 @@ When you cannot answer the grounding questions:
 
 A genuinely silent fingerprint is an expected state, not a blocker. When it does
 not cover the task, say so plainly and proceed with provisional local reasoning
-when safe; label it non-Ghost-backed. If the fingerprint's `index` node declares
-a stricter silence posture, honor it over this default. Ask a human before
+when safe; label it non-Ghost-backed. If the fingerprint's cover declares a stricter
+silence posture, honor it over this default. Ask a human before
 high-risk or brand-defining choices.

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

@@ -1,6 +1,6 @@
 ---
 name: steering-audit
-description: Audit a Ghost fingerprint for concrete steering coverage and guard routing.
+description: Audit a Ghost fingerprint for concrete steering coverage.
 ---
 
 # Recipe: Audit Steering Coverage
@@ -19,16 +19,13 @@ ghost pulse --format json
 
 If checks are installed and a diff exists, run `ghost review` too.
 
-## Headline the audit with concreteness + guards
+## Headline the audit with concreteness
 
 Report first:
 
 - **Concreteness coverage:** total nodes, concrete-material nodes, prose-only
   nodes. Concrete means non-empty `materials`, a fenced code block of at least 3
   lines, or a `## Skeleton` section.
-- **Guard routing:** how many guard nodes exist, whether they stay in default
-  gather, and whether `ghost review` can auto-offer matched guards via
-  materials.
 - **Pulse by concreteness:** concrete exposure/pull rate vs prose-only
   exposure/pull rate. This is the tuning instrument: if concrete nodes are not
   pulled, descriptions or task selection are failing.
@@ -37,16 +34,16 @@ Report first:
 
 | Row | Status | Evidence | Next move |
 | --- | --- | --- | --- |
-| Retrieval | strong / weak | descriptions, ids, `index` | sharpen descriptions or mention cold nodes in `index` |
+| Retrieval | strong / weak | descriptions, ids, cover | sharpen descriptions or move universal truth to the cover |
 | Concreteness | strong / thin | materials, fenced examples, Skeletons | add concrete locators, exemplars, or opening structures |
-| Guards | routed / missing / vague | `posture: guard`, review packet | write not-X-instead-Y guards and material locators |
-| Consistency | clean / conflicting | concrete bodies vs rules/guards | update stale examples; examples average with rules |
-| Stance | present / missing | `index`, `principle.*` | write forced-choice principles |
+| 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 |
+| Stance | present / missing | cover, `principle.*` | write forced-choice principles |
 | Materials | present / missing | `materials`, inspect-pointers | point at real assets/components/tokens |
 | Exemplars | annotated / unannotated / missing | fenced samples, screenshots | say what to copy and what is incidental |
 | Patterns | bound-open / loose / missing | `pattern.*`, Skeletons | state applies / bound / open and add a Skeleton when opening structure matters |
 | Checks | covered / partial / missing | checks/, probes, review packet | add checks/probes for high-risk invariants |
-| Silence posture | defined / missing | `index` | say when to proceed provisionally or ask |
+| Silence posture | defined / missing | cover | say when to proceed provisionally or ask |
 
 ## Task-level readiness
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@design-intelligence/ghost",
-  "version": "0.20.0",
+  "version": "0.22.0",
   "description": "Ghost CLI for the brand fingerprint: a portable steering packet of prose truths your agent reads before it builds, with advisory review after",
   "license": "Apache-2.0",
   "author": "Block, Inc.",
@@ -74,6 +74,6 @@
     "zod": "^4.3.6"
   },
   "scripts": {
-    "build": "rm -rf dist tsconfig.tsbuildinfo && tsc --build --force && chmod +x dist/bin.js && node ../../scripts/link-package-bin.mjs && cp -r src/skill-bundle dist/skill-bundle"
+    "build": "rm -rf dist tsconfig.tsbuildinfo && tsc --build --force && chmod +x dist/bin.js && node ../../scripts/link-package-bin.mjs && cp -r src/skill-bundle dist/skill-bundle && node ../../scripts/sync-init-payloads.mjs"
   }
 }

package/dist/scan/steering-template.d.ts

@@ -1,8 +0,0 @@
-import type { GhostInitTemplate, TemplateFile } from "./templates.js";
-interface SteeringTemplateDeps {
-    manifestFile(): TemplateFile;
-    gitignoreFile(): TemplateFile;
-}
-export declare function createSteeringTemplate({ manifestFile, gitignoreFile, }: SteeringTemplateDeps): GhostInitTemplate;
-export {};
-//# sourceMappingURL=steering-template.d.ts.map

package/dist/scan/steering-template.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"steering-template.d.ts","sourceRoot":"","sources":["../../src/scan/steering-template.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,EAAE,iBAAiB,EAAE,YAAY,EAAE,MAAM,gBAAgB,CAAC;AAEtE,UAAU,oBAAoB;IAC5B,YAAY,IAAI,YAAY,CAAC;IAC7B,aAAa,IAAI,YAAY,CAAC;CAC/B;AAED,wBAAgB,sBAAsB,CAAC,EACrC,YAAY,EACZ,aAAa,GACd,EAAE,oBAAoB,GAAG,iBAAiB,CAE1C"}