@design-intelligence/ghost 0.20.0

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

@@ -0,0 +1,377 @@
+---
+name: capture
+description: Author repo-local Ghost brand fingerprints 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?
+---
+
+# Recipe: Author Ghost Fingerprint
+
+**Goal:** record durable brand truths 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.
+
+```text
+.ghost/
+  manifest.yml          # schema + id
+  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
+  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`.
+
+## Lead with an annotated exemplar over a complete artifact
+
+The strongest steering artifact is not a summary; it is a complete on-brand
+artifact with annotation. Capture the whole thing, then name what the agent
+should preserve and what is incidental.
+
+`exemplar.status-card.md`:
+
+````markdown
+---
+description: Complete status card exemplar — normative for density, evidence placement, and action language.
+materials:
+  - src/components/status-card.tsx
+---
+
+Normative for the opening fact, square edge, evidence placement, and accountable
+action. The exact invoice count and dates are incidental.
+
+```tsx
+<section className="border-l border-[#D8DED8] bg-[#F7F5EF] p-6 text-[#17201B]">
+  <p className="text-xs uppercase tracking-[0.14em] text-[#2F6F4F]">Bank sync</p>
+  <h1 className="mt-3 text-2xl font-semibold">3 deposits need matching</h1>
+  <p className="mt-2 max-w-prose text-sm">
+    They total $8,410 and arrived between Jul 12 and Jul 15.
+  </p>
+  <button className="mt-6 border border-[#17201B] px-4 py-2 text-sm">
+    Match deposits — about 4 minutes
+  </button>
+</section>
+```
+
+What makes it ours: the surface opens with an accountable fact, keeps evidence
+next to the claim, uses square structure instead of floating cards, and prices
+the user's next action in time. Do not copy the exact amounts, dates, or class
+names unless the implementation path confirms them.
+````
+
+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.
+
+Protect exact voice artifacts the same way. A real on-brand error message
+out-steers a paragraph about error-message voice:
+
+`exemplar.error-voice.md`:
+
+```markdown
+---
+description: A verbatim on-brand error message — the voice at failure moments.
+---
+
+Normative for rhythm and stance at failure moments; match its form, not its words.
+
+> We couldn't save your changes. Your work is still here — try again, and if it
+> keeps failing, we'll hold onto everything while you sort it out.
+
+What makes it ours: leads with what happened, not with apology. States what is
+safe before what to do. One calm next step. No "Oops," no exclamation points,
+no blame on the user or the network.
+```
+
+## Add Skeletons when the opening structure matters
+
+A `## Skeleton` section contains the literal opening structure the agent should
+start from. Use it on a pattern node when the first tokens determine whether the
+surface lands in the right shape.
+
+Rules:
+
+- Put exactly one fenced block in each `## Skeleton` section. `ghost validate`
+  warns when there are zero or multiple fences.
+- Make the block complete enough to begin from, but not so complete that it
+  invents task-specific facts.
+- Keep explanation above the `## Skeleton`; `ghost pull` extracts skeleton
+  fences and emits them dead last under the banner to begin from this structure.
+- If a pulled skeleton matches the requested surface, write it first verbatim,
+  then fill it with the task's facts and materials.
+
+## Write rules only after concrete artifacts
+
+Rules are useful when they name the decision that survives across examples.
+Keep them short, specific, and attached to concrete objects whenever possible:
+
+- exact values when the agent keeps inventing values;
+- never/always invariants when a hard line is crossed;
+- conditions in prose when guidance applies only in a situation;
+- decision traces when two plausible choices keep competing.
+
+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
+
+A guard is ordinary node prose whose kind declares `posture: guard` in
+`glossary.md`:
+
+```yaml
+kinds:
+  - name: anti-goal
+    posture: guard
+```
+
+A good guard states **not X; instead Y; recognize the switch by Z**. The
+replacement matters because negation alone raises the salience of the rejected
+thing.
+
+`anti-goal.generic-ui.md`:
+
+```markdown
+---
+description: Review-critical replacement for the generic AI dashboard default.
+---
+
+Not: rounded-xl cards on gray-50, indigo primary buttons, gradient hero text,
+emoji headings, and "You're crushing it" optimism.
+
+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.
+```
+
+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.
+
+## The node shape
+
+A node at `principle.trust.md` (id `principle.trust`, kind `principle`):
+
+```markdown
+---
+description: Trust at the payment moment.  # the retrieval payload
+# optional: materials, audience, stage, or other free-form keys
+---
+
+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.
+- **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`).
+- **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 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
+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
+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
+  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.
+
+## Node prose stances
+
+Node prose is steering payload. A generic sentence in a 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.
+- **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.
+
+Everywhere else:
+
+- **No aspirational abstractions.** "We value clarity and trust" steers
+  nothing. Name the decision the truth 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
+  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
+  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
+  curated for altitude; ask the human which it is.
+
+## Score drafts before curation
+
+Before handing drafts to the human (step 5), rate each node 1 to 5 per
+dimension:
+
+| Dimension | Question |
+| --- | --- |
+| 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? |
+| Altitude | Is it universal on purpose, or given its condition? |
+| Residue | Is it free of starter-demo prose and brand-deck filler? |
+
+Below 20 of 25, the node goes back to the interview, not into the package. The
+score is a drafting gate for the agent; the human's keep/soften/reject verdict
+in curation still decides what becomes canonical.
+
+## Author through steering jobs
+
+The steering jobs are questions, not mandatory fields. Encode the truth in the
+strongest form that fixes the observed failure.
+
+| If the agent keeps... | Author... |
+| --- | --- |
+| missing the truth | sharper `description` / `index` mention |
+| inventing values | `asset.*` node with materials and exact names |
+| producing generic output | `anti-goal.*` guard 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.*` |
+
+Ask while authoring:
+
+- What complete artifact shows the brand at its best?
+- What should be copied from this exemplar, and what is incidental?
+- What generic output would an agent probably produce?
+- What does this brand refuse, and what replaces it?
+- What real material should the agent inspect?
+- What opening structure should be preserved?
+- What hard line would you block in review?
+- When would this guidance reverse?
+
+## Steps
+
+### 1. Classify the authoring scenario
+
+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
+shows — words, images, links, exemplars — is the evidence; agent synthesis is
+draft work until a human curates it and Git review accepts it.
+
+Monorepos and product suites run **one contract per package**.
+
+### 2. Initialize
+
+```bash
+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.
+
+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.
+
+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
+materials that should survive export or refactors under `materials/`; point at
+living app code where the implementation itself should stay in place. Optional
+review checks live under `.ghost/checks/` (`ghost checks init`) and are
+feed-back only; they are never gathered.
+
+### 3. Shape the glossary
+
+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.
+
+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
+`voice.<slug>.md` nodes; declaring a kind with zero or one users is good
+hygiene, not over-structure.
+
+### 4. Orient
+
+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.
+
+### 5. Write sparse nodes
+
+Add the smallest useful set of nodes, each a purpose-coherent prose truth
+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
+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.
+
+### 6. Validate
+
+```bash
+ghost validate .ghost
+```
+
+`validate` checks artifact shape, per-node validity, glossary kind prefixes,
+material locators, check references, and Skeleton fence counts.
+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
+  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 ship a blacklist-only anti-goal; state the replacement and enforce the
+  hard line in review.

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

@@ -0,0 +1,38 @@
+---
+name: recall
+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.
+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
+   inspect-pointers for binary materials, extracts Skeletons last, and logs the
+   pull to `.ghost/.events`.
+
+## Read order = pull emission order
+
+`ghost pull` emits selected nodes in steering order:
+
+1. `index` / stance first: non-negotiables and silence posture.
+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
+   structure verbatim.
+
+Return the selected truths with node ids, how each applies, and where the
+fingerprint is silent. If silence is safe, proceed provisionally and label it;
+if it is brand-defining or high-risk, ask or author a node first.

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

@@ -0,0 +1,119 @@
+---
+name: schema
+description: The Ghost fingerprint package shape: flat nodes, derived concreteness, Skeletons, guards, probes, and checks.
+---
+
+# Ghost Fingerprint Package Reference
+
+Canonical package:
+
+```text
+.ghost/
+  manifest.yml        ghost.fingerprint-package/v1: schema + id
+  glossary.md         kind vocabulary + meanings + optional posture
+  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
+  checks/             optional review assertions; never a node source
+```
+
+Reserved at the root: `manifest.yml`, `glossary.md`, `materials/`, and
+`checks/`. Every other `*.md` is a node.
+
+## Glossary posture
+
+A kind may declare posture. Omitted posture defaults to `steady`.
+
+```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.
+
+## Nodes
+
+A node is markdown with frontmatter and a prose body:
+
+```markdown
+---
+description: Logo lockups, clearspace, and when the glyph can stand alone.
+materials:
+  - brand/logo*.svg
+  - https://figma.com/file/example?node-id=logo-lockups
+---
+
+Use the full lockup when recognition matters.
+```
+
+- Identity is the filename minus `.md`.
+- Kind is the first dotted segment of the filename.
+- `description` is the retrieval payload shown by `ghost gather`.
+- `materials` accepts repo-relative paths/globs plus absolute HTTPS URLs. It is
+  a locator list, not guidance.
+
+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.
+This is reported in gather/pulse and used for pull ordering.
+
+## 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.
+
+```markdown
+## Skeleton
+
+```tsx
+<section>
+  <h1>{status}</h1>
+  <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.
+
+## Checks
+
+Checks live under `.ghost/checks/*.md` and are never gathered or pulled:
+
+```markdown
+---
+name: logo-clearspace-holds
+description: Logo usage preserves clearspace and lockup integrity.
+severity: medium
+references:
+  - asset.logo
+probe: pnpm test:logo-clearspace
+---
+
+Grade whether the change preserves the logo guidance in `asset.logo`.
+```
+
+`references` are node ids with optional heading anchors. `probe` is optional: a
+repo-root shell command that `ghost review` runs for offered checks by default
+(timeout 30s; stdout/stderr truncated). Probe output is evidence only, never a
+Ghost pass/fail verdict. Use `ghost review --no-probes` to skip. Trust model:
+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 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.

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

@@ -0,0 +1,65 @@
+---
+name: self-check
+description: A pre-generation probe that reveals whether you have actually gathered and reasoned about the brand fingerprint, before you build.
+---
+
+# Recipe: Self-Check Before Generating
+
+Before writing UI, copy, email, or any output, check whether you are grounded in
+the fingerprint or about to fall back on generic instincts. These questions test
+your **grounding and provenance**, not the fingerprint's contents, so they hold
+for any fingerprint, however sparse, whatever the medium, whoever authored it.
+
+Ask yourself:
+
+1. **What did you gather?** Which Ghost nodes did you pull for this task (from
+   `ghost gather`), and can you cite them by id? If you have not gathered, you
+   are not grounded. Gather first.
+2. **What is Ghost-backed vs. provisional?** For each claim you are about to
+   encode, is it backed by a gathered node (cite the id), or is it your own
+   provisional local reasoning? You must be able to label every claim as one or
+   the other.
+3. **Do the conditions apply?** For each conditional truth you pulled, does its
+   stated situation actually hold for this task? For each kind with conditional
+   or scoped meaning **per the glossary**, apply it only when its stated
+   situation holds; do not apply it where it does not, and do not ignore it
+   where it does.
+4. **Where is the fingerprint silent?** What does the fingerprint not cover for
+   your task, and what will carry the reasoning in those gaps? Naming the silence
+   is part of being grounded; pretending coverage you do not have is not.
+
+## Steering readiness
+
+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?
+- any decision trace for ambiguous tradeoffs?
+- where the fingerprint is silent?
+
+Classify readiness:
+
+- **Green:** enough Ghost-backed guidance and concrete material for this surface
+  to generate.
+- **Yellow:** generation is safe, but some reasoning must be labeled
+  provisional; if there is no concrete material for this surface, readiness is
+  at most Yellow.
+- **Red:** missing brand-defining, high-risk, or irreversible guidance; ask a
+  human or author a node first.
+
+When you cannot answer the grounding questions:
+
+1. Run `ghost gather <ask>` to emit the menu for the actual task, then match the
+   work to nodes by their descriptions.
+2. Read the selected nodes' bodies and re-ask the questions, citing node ids.
+
+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
+high-risk or brand-defining choices.

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

@@ -0,0 +1,61 @@
+---
+name: steering-audit
+description: Audit a Ghost fingerprint for concrete steering coverage and guard routing.
+---
+
+# Recipe: Audit Steering Coverage
+
+A steering audit asks whether a fingerprint can move generation away from the
+generic median. It is not a validation pass; `ghost validate` handles package
+shape.
+
+Start with:
+
+```bash
+ghost validate
+ghost gather --format json
+ghost pulse --format json
+```
+
+If checks are installed and a diff exists, run `ghost review` too.
+
+## Headline the audit with concreteness + guards
+
+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.
+
+## Corpus-level table
+
+| Row | Status | Evidence | Next move |
+| --- | --- | --- | --- |
+| Retrieval | strong / weak | descriptions, ids, `index` | sharpen descriptions or mention cold nodes in `index` |
+| 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 |
+| 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 |
+
+## Task-level readiness
+
+For a task, gather, pull, and report:
+
+- **Green:** enough Ghost-backed concrete guidance to generate.
+- **Yellow:** safe to generate, but some reasoning is provisional. If there is
+  no concrete material for this surface, readiness is at most Yellow.
+- **Red:** missing brand-defining, high-risk, irreversible, legal, privacy, or
+  security guidance; ask or author first.
+
+Never present steering coverage as deterministic pass/fail.