@design-intelligence/ghost 0.30.0 → 0.31.0

package/dist/init-payloads/skeleton/glossary.md

@@ -1,39 +1,51 @@
 ---
 kinds:
+  - name: standard
   - name: foundation
   - name: context
-  - name: cliche
 ---
 
+# standard
+
+Shared guidance that is not specific to this brand. Every rule carries one of
+two authority labels. An **Obligation** is a requirement brand preference
+cannot waive — accessibility, safety, honesty, functional integrity; the
+brand controls how it is expressed, not whether it holds. A **Default** is a
+recommended starting position that protects unsteered work from generic model
+behavior; explicit brand guidance in the cover, a foundation, or a matching
+context may deliberately replace it. When a default with a paired check is
+overridden, adapt or remove the check flag in the same change.
+
 # foundation
 
-The core elements — color, type, controls, layout, motion, voice — plus
-composition, the rules for assembling them into a view. Each foundation
-node is a chapter: usage rules that hold no matter what the brand values
-turn out to be, the brand's open questions (unanswered in this starter,
-marked as decisions only a human can make), and the chapter's misuse list.
-Follow the usage rules as written. Never fill in an open value and present
-it as the brand's.
+The brand's load-bearing decisions — color, type, controls, layout, motion,
+voice, and composition, the rules for assembling them into a view. Each
+foundation node is a chapter: usage law that holds no matter what the brand
+values turn out to be, the brand's open questions (unanswered in this
+starter, marked as decisions only a human can make), and the chapter's
+rejected moves. Follow the rules as written. Never fill in an open value and
+present it as the brand's. A brand carries only the foundations its evidence
+supports; these chapters are subjects, not mandatory slots.
 
 # context
 
 Where the defaults bend: a context names a situation — an AI conversation
 thread, a data-dense console, a transactional email — and states only what
-inverts there. Read a context only when its situation matches the task.
-Rules from the wrong context are contamination, not guidance.
-
-# cliche
-
-The defaults a generative model falls back on when no brand is steering it.
-These are nobody's brand. Each entry pairs the tired move with the honest
-replacement. Gather before styling anything greenfield; enforced by paired
-checks at review.
+inverts there. A situation may combine surface, channel, modality, audience,
+or moment. Read a context only when its situation matches the task. Rules
+from the wrong context are contamination, not guidance.
 
 ---
 
+Node bodies in this package follow one shape: `## Usage` carries the
+worldview and decision logic; `## Rules` carries observable requirements a
+reviewer can assess in the finished artifact; `## Never` pairs each rejected
+move with its replacement; an optional `## Skeleton` (always last) carries
+literal opening structure. A node includes only the sections it needs.
+
 The cover node (`brand.md`, declared in the manifest) is the one page always
 in context: what the brand is, its temperature, and the refusals only it
-makes. The ghost skill's `authoring` recipe explains how to grow this skeleton
-into a real ghost package: write the cover, answer each
-chapter's open question, prune the cliches your chapters absorb, then add
-materials and examples.
+makes. The ghost skill's `authoring` recipe explains how to grow this starter
+into a real ghost package: write the cover, answer each chapter's open
+question, prune the shared defaults your chapters absorb, then add materials
+and examples.

package/dist/init-payloads/vessel-light/checks/conversation-grammar.md

@@ -3,8 +3,8 @@ name: Conversation grammar
 description: Flags conversation UI that breaks plain assistant text, prompt-input structure, primary-action discipline, or collapsed tool output.
 severity: high
 references:
-  - grammar.conversation
-  - grammar.surfaces
+  - context.conversation
+  - foundation.surfaces
 ---
 
 Apply this check to diffs that touch AI threads, agent consoles, prompt composers, chat messages, or tool-call rendering.

package/dist/init-payloads/vessel-light/checks/median-tells.md

@@ -3,60 +3,60 @@ name: Median tells
 description: Flags the measured defaults of unsteered generation and current model-signature tells — hover-lift, default accents, unprompted dark theme, gradient text, frequency tells, and per-model signatures.
 severity: high
 references:
-  - anti-goal.median > Hover-lift
-  - anti-goal.median > Indigo accent
-  - anti-goal.median > Dark theme
-  - anti-goal.median > Gradients
-  - anti-goal.median > Glassmorphism
-  - anti-goal.median > Side-stripe
-  - anti-goal.median > Cream surface
-  - anti-goal.median > Chat bubbles
-  - anti-goal.median > Stock copy
-  - anti-goal.median > Celebration
-  - anti-goal.median > Hero metric
-  - anti-goal.median > Eyebrow kicker
+  - standard.model-defaults > Hover-lift
+  - standard.model-defaults > Indigo accent
+  - standard.model-defaults > Dark theme
+  - standard.model-defaults > Gradients
+  - standard.model-defaults > Glassmorphism
+  - standard.model-defaults > Side-stripe
+  - standard.model-defaults > Cream surface
+  - standard.model-defaults > Chat bubbles
+  - standard.model-defaults > Stock copy
+  - standard.model-defaults > Celebration
+  - standard.model-defaults > Hero metric
+  - standard.model-defaults > Eyebrow kicker
 ---
 
 This is Vessel's adaptation of the shared median check; the fidelity carve-outs
 below are the body's own. These flags target the measured convergence patterns
 of unsteered model generation, plus tells specific to individual models. Each
-is mechanically detectable in a diff. Pruning a rule from `anti-goal.median`
+is mechanically detectable in a diff. Pruning a rule from `standard.model-defaults`
 orphans its paired reference here — `ghost validate` warns; delete the flag and
 its reference together.
 
 Flag `transform` with `translateY` inside a `:hover` rule on cards, buttons,
 or list items, especially paired with a shadow increase. Hover confirmation
 in Vessel is color and background change, not lift.
-(`anti-goal.median > Hover-lift`)
+(`standard.model-defaults > Hover-lift`)
 
 Flag accent values in the indigo/blue/purple default family (`#4f46e5`,
 `#6366f1`, `#2563eb`, `#3b82f6`, `#8b5cf6`, and close neighbors) unless the
 diff shows the user asked for them. They are model defaults, not palette
-members. (`anti-goal.median > Indigo accent`)
+members. (`standard.model-defaults > Indigo accent`)
 
 Flag whole-page dark backgrounds when the ask did not request dark mode.
 Dark surfaces in Vessel are the editorial dark band or an explicit `.dark`
-theme, never an unprompted default. (`anti-goal.median > Dark theme`)
+theme, never an unprompted default. (`standard.model-defaults > Dark theme`)
 
 Flag `linear-gradient` or `radial-gradient` as page or section backgrounds,
-and gradient-filled buttons. (`anti-goal.median > Gradients`)
+and gradient-filled buttons. (`standard.model-defaults > Gradients`)
 
 Flag `backdrop-filter: blur` used for glassmorphism cards.
-(`anti-goal.median > Glassmorphism`)
+(`standard.model-defaults > Glassmorphism`)
 
 Flag `background-clip: text` (with or without the `-webkit-` prefix) paired
 with a gradient. Emphasis comes from weight or size in a single solid color.
 
 Flag a thick colored border on one side of an element (`border-left` or a
 `border-l-*` utility at 2px or more in a non-neutral color) while the other
-sides stay thin. (`anti-goal.median > Side-stripe`)
+sides stay thin. (`standard.model-defaults > Side-stripe`)
 
 Flag warm off-white page backgrounds in the cream/sand/beige band, and token
 names like `--cream`, `--sand`, `--parchment`, `--linen` introduced by the
-diff. (`anti-goal.median > Cream surface`)
+diff. (`standard.model-defaults > Cream surface`)
 
 Flag assistant messages rendered as bubbles with initials-circle avatars.
-(`anti-goal.median > Chat bubbles`)
+(`standard.model-defaults > Chat bubbles`)
 
 Flag emoji used as icons or imagery in interface chrome. Text labels carry
 meaning.
@@ -64,22 +64,22 @@ meaning.
 Flag stock template copy in headings: "Simple, transparent pricing",
 "Welcome back", and interchangeable-with-a-competitor phrasing. Recommend
 copy that states what this product specifically does.
-(`anti-goal.median > Stock copy`)
+(`standard.model-defaults > Stock copy`)
 
 Flag exclamation-marked success copy, confetti language, and celebratory UI
 ("You did it!", "Awesome!"). Confirmation is quiet and factual.
-(`anti-goal.median > Celebration`)
+(`standard.model-defaults > Celebration`)
 
 Flag the hero-metric template — a big number, small label, and supporting
 stats as default proof — unless the metric shows real user data. Recommend
 evidence specific to the product, or nothing.
-(`anti-goal.median > Hero metric`)
+(`standard.model-defaults > Hero metric`)
 
 Frequency tells — the crime is repetition, not the move (advisory):
 
 Flag three or more uppercase, tracked eyebrow kickers above section headings
 in one page. One named kicker is voice; a kicker on every section is model
-grammar. (`anti-goal.median > Eyebrow kicker`)
+grammar. (`standard.model-defaults > Eyebrow kicker`)
 
 Flag five or more em-dashes in body copy in one view.
 

package/dist/init-payloads/vessel-light/checks/motion-restraint.md

@@ -3,8 +3,8 @@ name: Motion restraint
 description: Flags non-token motion, looping decoration, and keyframes that do not explain state change.
 severity: medium
 references:
-  - grammar.motion
-  - signature.temperature
+  - foundation.motion
+  - foundation.temperature
 ---
 
 Review changed transitions and animations for vocabulary first.

package/dist/init-payloads/vessel-light/checks/relationships.md

@@ -3,10 +3,10 @@ name: Relationship discipline
 description: Flags structural violations of the grammar — emphasis-ladder breaks, sibling margins, decorative borders, nested cards. These rules survive any adaptation.
 severity: high
 references:
-  - grammar.hierarchy
-  - grammar.rhythm
-  - grammar.surfaces
-  - anti-goal.median > Nested cards
+  - foundation.hierarchy
+  - foundation.rhythm
+  - foundation.surfaces
+  - standard.model-defaults > Nested cards
 ---
 
 These assertions test relationships between token roles, not the values behind

package/dist/init-payloads/vessel-light/checks/shape-matches-job.md

@@ -3,9 +3,9 @@ name: Shape matches the job
 description: Flags views composed for the wrong reader job — a form styled as a table, an announcement headline over a reviewable artifact, a live state presented as settled fact, a second primary, or a skeleton loader standing in for content.
 severity: high
 references:
-  - grammar.job
-  - grammar.deletion
-  - grammar.hierarchy
+  - foundation.job
+  - foundation.deletion
+  - foundation.hierarchy
 ---
 
 Apply this check to diffs that add or restructure a view. Classify the
@@ -17,27 +17,27 @@ not fit.
 Flag a view whose job routes to one example but whose composition imitates
 another — a submit-and-done task laid out as a dashboard of cards, a
 records-scanning task rendered as prose sections, a stop-and-decide moment
-inlined into the page instead of interrupting it. (`grammar.job`)
+inlined into the page instead of interrupting it. (`foundation.job`)
 
 Flag an announcement headline in display or headline type above an artifact
 the reader will review — "Here's your draft", "Your plan is ready", "All
 set". The artifact opens the view; status lives in quiet metadata or
-nowhere. (`grammar.job`)
+nowhere. (`foundation.job`)
 
 Flag a live or ongoing value presented without its freshness — no timestamp
 or "updated" line in muted metadata near the figure. A moving value styled
-as a settled fact misleads. (`grammar.job`)
+as a settled fact misleads. (`foundation.job`)
 
 Flag recommendation or verdict framing where the decision belongs to the
 reader and the system cannot honestly rank the options. Present the
-material; withhold the verdict. (`grammar.job`)
+material; withhold the verdict. (`foundation.job`)
 
 Flag a second primary-variant action in a view, and flag a promoted primary
 on a view that honestly earns none — a steady status view, an open
 comparison. Zero is a valid spend of `--primary-budget`.
-(`grammar.hierarchy`)
+(`foundation.hierarchy`)
 
 Flag skeleton loaders, placeholder shimmer, or staged construction where
 content will land — and any element that cannot name what breaks if it is
 removed. The fix is demotion or deletion, never more emphasis.
-(`grammar.deletion`)
+(`foundation.deletion`)

package/dist/init-payloads/vessel-light/checks/values.md

@@ -3,12 +3,12 @@ name: Value discipline
 description: Flags off-signature values — non-pill controls, off-palette hues, raw color literals, expression over budget. Adapting the dials rewrites this check alongside the signature nodes.
 severity: high
 references:
-  - signature.shape
-  - signature.palette
-  - grammar.color-roles
-  - register.data-density
-  - register.editorial
-  - register.email
+  - foundation.shape
+  - foundation.palette
+  - foundation.color-roles
+  - context.data-density
+  - context.editorial
+  - context.email
 ---
 
 These assertions test Vessel's current answers to the signature dials. A

package/dist/init-payloads/vessel-light/context.conversation.md

@@ -0,0 +1,53 @@
+---
+for: Any AI thread, agent console, review assistant, or prompt composer.
+materials:
+  - materials/examples/composition.conversation.html
+---
+
+## Usage
+
+Conversation UI is not chat cosplay. The assistant speaks on the page surface
+as plain text: no bubble, no border, no fill.
+
+Assistant hierarchy comes from prose, spacing, and type. Wrapping assistant
+messages in cards makes the system look defensive and wastes density.
+
+Tool calls are operational evidence. The prompt input is one bordered
+surface; the textarea region stays empty of controls so writing remains the
+focus.
+
+Use the conversation reference when building any AI thread, agent console,
+review assistant, or prompt composer. It carries the grammar that agents most
+often get wrong.
+
+## Rules
+
+- The assistant speaks on the page surface as plain text: no bubble, no
+  border, no fill.
+- User turns are compact muted surfaces aligned right. They mark authorship
+  without turning the thread into alternating balloons.
+- Tool calls collapse to a labeled one-line summary with status. Expand only
+  when the user asks for detail, then show mono content inside the disclosed
+  area.
+- The prompt input is one bordered surface, with the textarea region empty
+  of controls. Attachments, model choices, secondary tools, and send live in
+  a single row below it.
+- There is one primary send action. Stop and send are mutually exclusive
+  states of the same action area.
+
+## Never
+
+- Never wrap assistant messages in cards — it makes the system look
+  defensive and wastes density; instead draw assistant hierarchy from prose,
+  spacing, and type.
+- Never turn the thread into alternating balloons — instead mark authorship
+  with compact muted user surfaces aligned right and plain-text assistant
+  turns.
+- Never expand tool calls by default — instead collapse them to a labeled
+  one-line summary with status, expanding only when the user asks for
+  detail.
+- Never put controls inside the textarea region — instead keep writing the
+  focus and place attachments, model choices, secondary tools, and send in a
+  single row below it.
+- Never show stop and send as two competing primary buttons — instead treat
+  them as mutually exclusive states of the same action area.

package/dist/init-payloads/vessel-light/context.data-density.md

@@ -0,0 +1,51 @@
+---
+for: Tables, dashboards, logs, monitoring, or other data-dense consoles.
+materials:
+  - materials/examples/composition.table.html
+  - materials/primitives.css
+---
+
+Condition: this node applies to data-dense surfaces — tables, dashboards,
+transaction logs, and admin consoles.
+
+## Usage
+
+Data density inverts the settings-page rhythm. Operators need scan speed
+before they need breathing room.
+
+Tight adjacency is meaning when rows compare against rows. A ragged amount
+column is a broken instrument. Hierarchy is muted-first: data is the default
+plane, labels are muted, and emphasis is rare enough to stay useful.
+
+Generous whitespace is drift here. Wasted density makes operators scroll.
+
+## Rules
+
+- Use the two smallest gap steps (`--gap-xs`, `--gap-sm`) where forms use
+  the medium step.
+- Numerals are mono so columns align.
+- Data is the default plane, labels are muted, and emphasis is rare enough
+  to stay useful.
+- Data surfaces take the small radius.
+- Status is a text label with at most one functional color family per view.
+- Charts inside a console follow the product carve-out from the palette
+  signature: expression hues live inside the plot area only. Outside the
+  plot, the one-status-hue cap holds.
+- Hairline borders carry rows.
+- Hover confirmation uses the fast duration. It should acknowledge
+  targeting, not animate the table.
+
+## Never
+
+- Never give a table cell the surface radius — a surface-radius table cell
+  is costume; the signature radius (see foundation.shape) belongs on cards,
+  not cells — instead data surfaces take the small radius.
+- Never let chart color leak into rows, badges, or headers — more status
+  color turns monitoring into confetti; instead keep expression hues inside
+  the plot area and hold the one-status-hue cap outside it.
+- Never zebra stripe — instead let hairline borders carry rows with less
+  noise and more trust.
+- Never animate the table on hover — instead acknowledge targeting with the
+  fast duration.
+- Never spend generous whitespace here — it is drift, and wasted density
+  makes operators scroll; instead use the two smallest gap steps.

package/dist/init-payloads/vessel-light/context.editorial.md

@@ -0,0 +1,53 @@
+---
+for: Heroes, marketing pages, pull quotes, or full-bleed dark moments.
+materials:
+  - materials/examples/composition.editorial.html
+  - materials/tokens.css
+---
+
+Condition: this node applies to marketing, landing, and editorial surfaces —
+never to product UI.
+
+## Usage
+
+Editorial surfaces invert the product type rules. Display scale is not an
+indulgence here; it is the job.
+
+Pull quotes are visual punctuation for longform. They interrupt reading with
+verdicts, not decoration. The tracked uppercase label is the kicker grammar.
+It gives the page a hard editorial edge before the headline lands.
+
+Monochrome remains the spine, but editorial is the loud end of the expression
+ladder (see foundation.palette). Commit to few colors at scale; variety is
+where expression collapses into decoration.
+
+A hero built at product scale reads as timid. Timidity is drift here, exactly
+as spectacle is drift in product UI.
+
+## Rules
+
+- Use the `--heading-display-*` tokens — size, line height, and weight —
+  when the words are the composition. The display tier belongs to this
+  context (see foundation.type for the scale's character).
+- Section rhythm uses `--section-padding-vertical`.
+- The sanctioned dramatic moment is the full-bleed dark section. Use the
+  `--surface-dark-*` family and let contrast carry the scene.
+- Up to two expression hues per page as atmosphere — a tinted dark section,
+  a colored pull-quote accent, a duotone image moment.
+- There is one primary action per page, and it keeps the control radius from
+  foundation.shape.
+
+## Never
+
+- Never stretch a product stack until it looks important — instead use
+  `--section-padding-vertical` for section rhythm.
+- Never use pull quotes as decoration — instead let them interrupt reading
+  with a verdict; they are visual punctuation for longform.
+- Never let variety carry the expression — that is where expression
+  collapses into decoration; instead commit to few colors at scale, up to
+  two hues per page.
+- Never allow competing calls to action — editorial confidence does not
+  excuse them; instead keep one primary action per page.
+- Never build a hero at product scale — it reads as timid, and timidity is
+  drift here exactly as spectacle is drift in product UI; instead let the
+  display scale do its job.

package/dist/init-payloads/vessel-light/context.email.md

@@ -0,0 +1,53 @@
+---
+for: Transactional email only.
+materials:
+  - materials/examples/email.html
+---
+
+Condition: this node applies only to email. In any other medium, everything
+below is a violation.
+
+## Usage
+
+Email clients do not honor the web contract. Custom properties, external
+stylesheets, flex layout, and webfonts are unreliable materials here.
+
+Email inverts the material contract deliberately. Transcribe token values by
+hand instead of referencing tokens — every hex below is a transcription of
+`materials/tokens.css`, which stays the single source; if a token changes,
+re-transcribe. Hardcoding hex here is fidelity, not drift. The check
+exemption is the condition itself.
+
+Email fidelity is made from boring structure. The soul survives the body
+swap: monochrome spine, quiet factual copy, one primary action, no
+celebration. A receipt is allowed one degree of warmth; it is not allowed a
+palette.
+
+## Rules
+
+- Use `#1a1a1a` (`--color-gray-900`, foreground) for text, `#999999`
+  (`--color-gray-500`, muted) for muted text, and `#e8e8e8`
+  (`--color-gray-200`, border) for borders when the email needs the Vessel
+  palette.
+- Keep the surface radius on cards and the control radius on buttons (see
+  foundation.shape). The values survive even when the token names cannot
+  travel.
+- Build with table layout, a 600px wrapper, predictable cells, and
+  bulletproof buttons.
+- HK Grotesk falls back to the system stack. The voice must survive without
+  the font file.
+- Email gets exactly one expressive moment: a header band or the figure that
+  matters, in one expression hue, transcribed by hand like every value
+  here — amber is `#f6b44a` (`--expression-1`). One moment, one hue.
+
+## Never
+
+- Never reference tokens directly in email — custom properties are
+  unreliable materials here; instead transcribe token values by hand from
+  `materials/tokens.css`, and re-transcribe if a token changes.
+- Never add further color to compensate for email constraints — constraint
+  is not permission to perform; instead hold to the one expressive moment in
+  one hue.
+- Never apply anything in this node outside email — in any other medium it
+  is a violation; instead use the token-referencing contract the other
+  contexts require.

package/dist/init-payloads/vessel-light/foundation.color-roles.md

@@ -0,0 +1,41 @@
+---
+for: Choosing or applying color.
+materials:
+  - materials/tokens.css
+---
+
+## Usage
+
+The token file is the source of truth. An agent may combine tokens, but it
+may not author around them. Raw color values are implementation detail, never
+product language.
+
+If a container needs a color, it first needs a role. The status roles —
+destructive, success, warning, info — exist only when meaning demands them.
+None of them are brand accents.
+
+One view should not perform a color palette. If a status color is present,
+let the rest of the view stay on the base roles. Richness beyond this is
+context-gated: a closed expression set (`--expression-*`) exists, but its
+size, members, and volume ladder are a brand answer — see the palette
+foundation — and each context caps how loud they may be.
+
+## Rules
+
+- Author with semantic roles: `background`, `foreground`, `card`, `popover`,
+  `primary`, `secondary`, `muted`, `border`, `input`, `ring`, and the status
+  roles.
+- Destructive means destructive or error. Success means success. Warning
+  means warning. Info means information.
+- The constant that holds across every context: expression never touches
+  what you click. Buttons, inputs, and links stay on the base roles
+  everywhere.
+
+## Never
+
+- Never let a status role moonlight as atmosphere, in any context — status
+  colors keep their meanings everywhere; use the expression set at the
+  context's sanctioned volume instead.
+- Never author around the tokens with raw color values — combine tokens.
+- Never put a color on a colored control — a colored control is a different
+  design system; controls stay on the base roles.

package/dist/init-payloads/vessel-light/foundation.deletion.md

@@ -0,0 +1,53 @@
+---
+for: The final pass over any composition, or whenever a view feels crowded, busy, or dressed up.
+---
+
+## Usage
+
+Restraint is not a mood; it is a test every element has to pass. Before a
+view ships, run the pass: each label, divider, icon, caption, and helper
+line must name what breaks if it is removed. If nothing breaks, delete it.
+Convention is not a reason — "forms usually have this" keeps nothing.
+
+The test has a direction. When a view is crowded, or two elements compete
+for attention, the fix is always demotion or deletion — never adding
+emphasis to the loser. Raising the volume of one element to beat another
+starts an arms race the composition always loses; removing the weaker claim
+ends it.
+
+Do: a settings page whose every row survives the what-breaks question, with
+one primary action and gaps doing the dividing.
+
+After everything deletable is gone, whatever remains is unmistakably the
+point.
+
+## Rules
+
+- Every label, divider, icon, caption, and helper line must name what breaks
+  if it is removed; if nothing breaks, delete it.
+- A view arrives settled: when content lands, it lands in its final
+  position — no reflow, no staggered construction, no element arriving late
+  to shift its neighbors.
+- While work is genuinely pending, show the smallest true statement (a quiet
+  loading state, per the motion doctrine's loop exception) and nothing else.
+
+## Never
+
+- Never fix a crowded view or an attention contest by adding emphasis to the
+  loser — instead demote or delete the weaker claim.
+- Never add a decorative divider where a gap step states the relationship —
+  instead let the gap do the dividing.
+- Never add an icon that restates its adjacent label — instead delete the
+  icon.
+- Never add a tooltip explaining an obvious control — instead delete the
+  tooltip.
+- Never add onboarding chrome to routine views — instead delete it.
+- Never dress a view in credibility costume — instead use a small factual
+  source or timestamp line; it beats a dashboard of gauges.
+- Never ship skeleton loaders or placeholder shimmer promising content that
+  is not there — a fake page is hedging rendered as UI; instead show the
+  smallest true statement while work is pending.
+- Never ship the settings page with icon-per-row decoration, a divider under
+  every group, a progress shimmer on load, and a bolded second CTA competing
+  for the eye — instead run the deletion pass until every row survives the
+  what-breaks question.