@design-intelligence/ghost 0.30.0 → 0.31.1

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

@@ -0,0 +1,73 @@
+---
+for: Any view containing text or actions.
+materials:
+  - materials/primitives.css
+  - materials/examples/composition.form.html
+---
+
+## Usage
+
+Hierarchy is a closed vocabulary, not a size slider. Every piece of text and
+every control picks from a named set; anything outside the set is a broken
+primitive, not a variant.
+
+Variant names are jobs, not decoration. Display leads a rare editorial
+moment. Headline names a section. Title anchors a card, dialog, or compact
+region. Body carries reading. Label names structure — category tags, field
+labels, bylines, metadata, compact status. Mono carries code and machine
+detail.
+
+Tone is part of the message. Default is the main reading plane. Muted carries
+secondary information. Inverse is for dark or primary surfaces. Hierarchy
+starts with tone and weight before size — a secondary note usually wants
+muted body or label, not a smaller custom font. If the prose needs emphasis,
+improve the sentence before adding a style.
+
+Primary is for the action the screen exists to complete — if two buttons
+both look primary, the hierarchy failed. And some views honestly earn none: a
+steady status view or an open comparison has no action the screen exists to
+complete, and promoting one anyway puts the system's thumb on the scale.
+Zero is a valid spend.
+
+Destructive is a meaning, not a rung: it is rare, and it names the
+destructive act directly.
+
+The focus ring is guidance, not decoration. Proportional figures in a data
+column wobble, and a wobbling column reads as sloppy arithmetic. Mono already
+carries tabular alignment for machine detail; the rule extends to any numeric
+data in product UI.
+
+The form reference shows the intended decision order: stacked labels and
+fields, compact helper text, one submit, secondary escape. Copy the decision
+order before adjusting surface detail.
+
+## Rules
+
+- The text variants are exactly six: display, headline, title, body, label,
+  mono.
+- The tones are exactly seven: default, muted, inverse, success, warning,
+  info, destructive.
+- The four status tones appear only when the words have that state meaning.
+- The control emphasis ladder is exactly five rungs: primary, secondary,
+  outline, ghost, link.
+- At most one primary action per view (`--primary-budget: 1`); everything
+  else steps down the ladder.
+- Fields are quiet until they are active: hairline border, muted
+  placeholder, clear label, and a focused ring when the user engages.
+- Errors state facts next to the field that caused them.
+- Figures that will be compared or scanned — amounts, counts, dates in
+  columns, any metric — set in tabular numerals (`--numeric-tabular`), with
+  the unit tight to the number.
+- Balanced text is for headings and compact statements.
+
+## Never
+
+- Never fake hierarchy with arbitrary font sizes — instead choose the tier
+  that matches the job, then use tone, weight, and spacing for the rest.
+- Never borrow destructive for urgency, emphasis, or brand heat — instead
+  reserve it for the destructive act it names.
+- Never hide field errors in modals, toasts, or generic banners when the
+  user needs to fix one input — instead state the facts next to the field
+  that caused them.
+- Never balance long body copy into jagged reading — instead reserve
+  balanced text for headings and compact statements.

package/dist/init-payloads/vessel-light/{grammar.job.md → foundation.job.md}

@@ -9,6 +9,8 @@ materials:
   - materials/examples/email.html
 ---
 
+## Usage
+
 Before any structure exists, name what the reader does next with the view.
 The topic never picks the shape; the reader's job does. A billing question
 is not "a billing page" — it is a form to fill, a table to scan, a decision
@@ -16,39 +18,48 @@ to confirm, or a thread to continue, and each of those is a different
 composition. A view built for the wrong job does not merely look off; it
 misleads.
 
-The jobs and where they route:
-
-- **Fill something in** — settings, signup, any submit-and-done task → the
-  form example. Stacked labels and fields, one submit, secondary escape.
-- **Scan and compare records** — lists, audits, anything with rows and
-  figures → the table example, in the data-density register.
-- **Read a narrative** — a landing page, an announcement, a story → the
-  editorial example, in the editorial register.
-- **Stop and decide** — a confirmation, a destructive act, a choice that
-  interrupts the task → the overlay example. The decision is the view.
-- **Converse with the system** — an AI thread, an agent console, a prompt
-  composer → the conversation example.
-- **Be notified elsewhere** — receipts, alerts, anything that lands in an
-  inbox → the email example, in the email register.
-
 Read the request's verbs, not its nouns: "edit / set up / submit" routes to
 form; "compare / list / review the records" to table; "announce / tell the
 story" to editorial; "confirm / are you sure" to overlay; "ask / draft with
 me" to conversation. When two jobs fold into one request, build for the job
 the reader performs on this view, now — the other job is the next view. When
-a job fits none of these, compose from the grammar and say so; do not force
-the nearest example.
+a job fits none of these, compose from the grammar and say so.
 
-Three shapes lie about the job, and we refuse them everywhere:
+Three shapes lie about the job, and we refuse them everywhere; they are
+listed under Never.
 
-- A view whose content is an artifact the reader will review — a draft, a
-  filled form, a generated plan — leads with the artifact, never with an
-  announcement headline. "Here's your draft" in display type demotes the
-  actual deliverable; the artifact sitting there with its actions is the
-  statement that it is ready.
+## Rules
+
+- **Fill something in** — settings, signup, any submit-and-done task —
+  routes to the form example: stacked labels and fields, one submit,
+  secondary escape.
+- **Scan and compare records** — lists, audits, anything with rows and
+  figures — routes to the table example, in the data-density context.
+- **Read a narrative** — a landing page, an announcement, a story — routes
+  to the editorial example, in the editorial context.
+- **Stop and decide** — a confirmation, a destructive act, a choice that
+  interrupts the task — routes to the overlay example. The decision is the
+  view.
+- **Converse with the system** — an AI thread, an agent console, a prompt
+  composer — routes to the conversation example.
+- **Be notified elsewhere** — receipts, alerts, anything that lands in an
+  inbox — routes to the email example, in the email context.
 - A view reporting a live or ongoing state carries its freshness — "updated
-  2 min ago" — in quiet metadata. Presenting a moving value as a settled
-  fact is a small lie the reader eventually catches.
-- A view where the decision belongs to the reader presents the material and
-  withholds the verdict. Recommendation framing on a choice the system
-  cannot honestly make is manufactured confidence, and it reads that way.
+  2 min ago" — in quiet metadata.
+
+## Never
+
+- Never force the nearest example when a job fits none of these — instead
+  compose from the grammar and say so.
+- Never lead with an announcement headline when the view's content is an
+  artifact the reader will review — a draft, a filled form, a generated
+  plan. "Here's your draft" in display type demotes the actual deliverable —
+  instead lead with the artifact; the artifact sitting there with its
+  actions is the statement that it is ready.
+- Never present a moving value as a settled fact — it is a small lie the
+  reader eventually catches; instead carry the view's freshness — "updated
+  2 min ago" — in quiet metadata.
+- Never put recommendation framing on a choice the system cannot honestly
+  make — it is manufactured confidence, and it reads that way; instead
+  present the material and withhold the verdict when the decision belongs to
+  the reader.

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

@@ -0,0 +1,46 @@
+---
+for: Any transition, animation, or hover treatment.
+materials:
+  - materials/tokens.css
+---
+
+## Usage
+
+Motion is evidence of a state change. It confirms hover, press, reveal,
+collapse, entrance, exit, and spatial movement. It does not entertain.
+
+The entire vocabulary is three duration roles and one ease. The ease's
+character is a brand answer — see the temperature signature.
+
+Prefer opacity and small transform changes. If removing an animation does not
+reduce comprehension, the animation was decoration.
+
+Condition: marketing and editorial surfaces may stage entrances — scroll
+reveals and section transitions are part of editorial rhythm, still built
+from the three durations and the one ease. In product UI the same staging is
+decoration.
+
+## Rules
+
+- The vocabulary is exactly three duration roles and one ease.
+- Fast is for hover and press.
+- Normal is for reveals, fades, and small state changes.
+- Slow is reserved for spatial transitions where the user needs to
+  understand movement.
+- Nothing loops except explicit loading states. A spinner may continue
+  because work continues.
+
+## Never
+
+- Never introduce novelty easings because a surface feels static — instead
+  stay on the one ease; its character is a brand answer (see the temperature
+  signature).
+- Never ship decorative pulsing, floating, glowing, or attention-seeking
+  keyframes — they are off-language; instead loop nothing except explicit
+  loading states.
+- Never keep an animation whose removal does not reduce comprehension — it
+  was decoration; instead delete it and prefer opacity and small transform
+  changes where motion earns its place.
+- Never stage entrances in product UI — that staging is decoration there;
+  instead reserve scroll reveals and section transitions for marketing and
+  editorial surfaces.

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

@@ -0,0 +1,57 @@
+---
+for: Color beyond the base roles, in any register.
+materials:
+  - materials/tokens.css
+---
+
+## Usage
+
+This is Vessel's answer to palette — it stands until you replace it.
+
+The relationship is fixed: one brand at different volumes. A monochrome spine
+is the default atmosphere in every medium — calm, legible, and resistant to
+novelty — and a closed expression set supplies the atmosphere, with volume
+set by context, never by taste.
+
+Expressive color outside the closed set is not expression; it is another
+brand. An invented hue is not a bolder Vessel; it is a different brand.
+
+Loudness comes from commitment to few colors at scale, not variety.
+
+To adapt: edit the `--expression-*` values (and the gray ramp, if the spine
+changes) in `materials/tokens.css` and restate this node's current answer.
+The ladder — a quiet spine, a closed hue set, context-gated volume — is the
+part worth keeping.
+
+## Rules
+
+- The base palette is monochrome gray.
+- The expression palette is five named hues and only these — amber
+  (`--expression-1`), periwinkle (`--expression-2`), clay
+  (`--expression-3`), orchid (`--expression-4`), sage (`--expression-5`).
+- Product UI: expression lives only in data visualization. A chart may use
+  the hues; the interface around it stays monochrome.
+- Data-dense consoles: one hue family may mark status. Nothing atmospheric.
+  Charts inside a console keep the product carve-out — hues stay inside the
+  plot area and never leak into rows, badges, or headers.
+- Email: exactly one expressive moment per message — a header band or the
+  figure that matters. One hue, quiet everywhere else.
+- Editorial: expression is sanctioned atmosphere — a tinted dark section, a
+  colored pull-quote accent, a duotone moment. Never more than two hues per
+  page.
+- Two constants that outrank the ladder: expression never touches what you
+  click — buttons, inputs, and links stay monochrome in every context — and
+  the status roles are not expression; they keep their meanings everywhere.
+
+## Never
+
+- Never use expressive color outside the five named hues — an invented hue
+  is not a bolder Vessel; it is a different brand; instead stay inside the
+  `--expression-*` set at the context's sanctioned volume.
+- Never put expression on what you click — instead keep buttons, inputs, and
+  links monochrome in every context.
+- Never let the status roles moonlight as atmosphere — they are not
+  expression; instead keep their meanings everywhere and draw atmosphere
+  from the expression set.
+- Never set expression volume by taste — instead set it by context, per the
+  ladder above.

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

@@ -0,0 +1,39 @@
+---
+for: Laying out any view.
+materials:
+  - materials/primitives.css
+---
+
+## Usage
+
+All layout is stacks. Rhythm comes from relationships between siblings, not
+from isolated margins pasted onto whichever element was last touched.
+
+Choose the gap that states the relationship. Ad-hoc margins between siblings
+are forbidden because they hide the rhythm. When spacing feels wrong, change
+the stack gap or split the stack.
+
+Columns are for almost everything: forms, cards, message lists, modal bodies,
+settings, empty states, and page sections. A column lets the user scan.
+
+Rows are conditional. Use them for controls, metadata lines, compact status,
+and paired label/value moments. If a row starts wrapping awkwardly, it
+probably wanted to be a column.
+
+## Rules
+
+- The gap steps are exactly five: `--gap-xs`, `--gap-sm`, `--gap-md`,
+  `--gap-lg`, `--gap-xl`.
+- The default is column, medium gap, stretch alignment, start justification.
+  That is the ordinary reading rhythm.
+- Rows are for controls, metadata lines, compact status, and paired
+  label/value moments.
+
+## Never
+
+- Never place ad-hoc margins between siblings — they hide the rhythm;
+  instead change the stack gap or split the stack.
+- Never tune by single pixels to make a screenshot pass — instead choose the
+  gap step that states the relationship.
+- Never keep a row that starts wrapping awkwardly — it probably wanted to be
+  a column; instead convert it.

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

@@ -0,0 +1,39 @@
+---
+for: Choosing or implementing any radius or corner treatment.
+materials:
+  - materials/tokens.css
+  - materials/primitives.css
+---
+
+## Usage
+
+This is Vessel's answer to shape — it stands until you replace it.
+
+The relationship is fixed: controls and surfaces carry different radius
+roles, and the two never swap. The pill is Vessel's most visible control
+signature; a rectangular button is not a variant, it is a different design
+system.
+
+20px is a considered position: rounder than default shadcn, but not bubbly.
+Use the radius system as restraint, not as decoration.
+
+To adapt: edit the `--radius-control` and `--radius-surface` values in
+`materials/tokens.css` and restate this node's current answer. The
+role split — one radius for what you click, one for what contains — is the
+part worth keeping.
+
+## Rules
+
+- Buttons and text inputs use `--radius-control`; cards and other surfaces
+  use `--radius-surface`.
+- Controls are pills (`--radius-control: 999px`).
+- Surfaces take the 20px signature radius (`--radius-surface: 20px`).
+
+## Never
+
+- Never give a button the surface radius — a rectangular button is the
+  fastest tell that the output is not Vessel; instead controls take
+  `--radius-control`, the pill.
+- Never swap the two radius roles — instead keep `--radius-control` on what
+  you click and `--radius-surface` on what contains.
+- Never use the radius system as decoration — instead use it as restraint.

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

@@ -0,0 +1,45 @@
+---
+for: Any card, popover, modal, dialog, scrim, or bordered container.
+materials:
+  - materials/primitives.css
+  - materials/examples/composition.overlay.html
+---
+
+## Usage
+
+Surface is the only way an element gets a background, border, radius, or
+shadow. If a container needs visual treatment, it first needs a surface role.
+
+The vocabulary is closed: role, padding, radius, border, and elevation. These
+axes create enough range for page flow, cards, popovers, muted blocks,
+accents, and dark moments without inventing one-off boxes.
+
+Elevation implies hierarchy — a card sits in the document flow, a popover
+floats above the flow, a modal interrupts the task. Pick the tier that
+matches the interaction.
+
+Borders are structural, especially for inputs and overlays. They are not
+decorative frames around ordinary text.
+
+The overlay reference shows the interrupting end of the system: background
+scrim, modal radius, modal shadow, compact header, clear footer. Copy its
+hierarchy when a user must stop and decide.
+
+## Rules
+
+- The default surface is flat: no border, no shadow. We do not outline
+  everything to prove layout exists.
+- The elevation tiers are exactly three: card, popover, modal.
+- Component shadows belong to the primitives that own them.
+- Borders are structural, especially for inputs and overlays.
+
+## Never
+
+- Never write a custom shadow because the composition feels flat — instead
+  pick the elevation tier that matches the interaction.
+- Never pair a low tier with an interrupting role or give a routine card
+  modal gravity — instead match the tier to the interaction's hierarchy.
+- Never borrow component shadows for layout — they belong to the primitives
+  that own them; instead take layout elevation from the three tiers.
+- Never use borders as decoration, especially around assistant text —
+  instead use space, tone, and type hierarchy.

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

@@ -0,0 +1,39 @@
+---
+for: Any work applying this brand's signature.
+---
+
+## Usage
+
+These are the near-misses of Vessel's own signature: outputs that got close
+enough to cite the brand and still missed it. Each reject names its
+replacement. When a tell fires, the fix direction is always toward the
+token, the role, or deletion — never toward adding a compensating style on
+top of the miss.
+
+Fidelity note: pills and fluid clamp display headings are medians Vessel
+deliberately shares — their presence is fidelity, not drift. Convergence is
+not the crime; surrendering the choice is.
+
+## Never
+
+- Never ship rectangular buttons. A rectangular button is not a variant; it
+  is a different design system — instead controls take `--radius-control`,
+  the pill.
+- Never swap radius roles: the surface radius on a control, the pill on a
+  surface, or 20px cells in a data table — instead `--radius-control` on
+  what you click, `--radius-surface` on what contains, small radius on data
+  cells.
+- Never put expression hues on interactive controls, invent a sixth hue, or
+  pass off a tinted gray as monochrome — instead use the five named
+  expression hues at the context's sanctioned volume, and a true gray spine.
+  An invented hue is not a bolder Vessel; it is a different brand.
+- Never write custom shadows that sit near a tier — instead use the exact
+  tier — card, popover, or modal — chosen by interaction importance.
+- Never borrow `--shadow-btn` for layout — component shadows belong to the
+  primitives that own them; instead take layout elevation from the three
+  tiers.
+- Never use editorial display type in product UI, or product type timidity
+  in editorial — instead each context keeps its own vocabulary; a modal
+  title is not a poster, and a hero at product scale reads as timid.
+- Never put borders around assistant text — instead the assistant speaks as
+  plain text on the page surface; use space, tone, and type hierarchy.

package/dist/init-payloads/vessel-light/{signature.temperature.md → foundation.temperature.md}

@@ -4,19 +4,15 @@ materials:
   - materials/tokens.css
 ---
 
+## Usage
+
 This is Vessel's answer to temperature — it stands until you replace it.
 
 The relationship is fixed: voice and motion carry the same temperature. Copy
 states what happened, what is possible, or what the user must decide — it
 does not perform personality — and motion confirms rather than entertains.
 
-Vessel's current answer in words: product UI is the default register —
-factual, quiet, sentence case, and free of applause. No exclamation marks;
-celebration is not reassurance. Confirmations are quiet: "Changes saved",
-never "Awesome!" The system should sound reliable, not excited by basic
-competence. Errors name the problem and the fix in the place where the user
-can act; a vague failure banner is evasion. Buttons name the act — "Delete
-account", "Save changes", "Invite member", not "Do it" or "Let's go".
+The system should sound reliable, not excited by basic competence.
 Destructive copy is direct because the risk is direct; softening the verb
 makes the interface less honest. Vessel never celebrates at the user. Trust
 comes from precision, restraint, and naming the truth plainly.
@@ -28,12 +24,7 @@ card expired". "You might want to consider updating your billing info" →
 "Update your billing info". Strip the apology, the applause, and the hedge;
 keep the fact and the fix.
 
-Vessel's current answer in motion: three durations — `--duration-fast`,
-`--duration-normal`, `--duration-slow` — and one ease, `--ease-spring`, which
-should feel resolved without feeling elastic. Hover confirms with color and
-background shifts at the fast duration, not levitation.
-
-Condition: editorial surfaces switch register. Short declarative confident
+Condition: editorial surfaces switch context. Short declarative confident
 fragments are correct in heroes and section headings. That same editorial
 confidence is wrong in a settings form — product copy serves the task before
 it serves the voice. Email copy uses the product voice: factual, not
@@ -42,3 +33,30 @@ campaign-like.
 To adapt: rewrite this node's current answers in your brand's voice and edit
 the duration and ease values in `materials/tokens.css`. The coupling — words
 and motion sharing one temperature — is the part worth keeping.
+
+## Rules
+
+- Product UI is the default context — factual, quiet, sentence case, and
+  free of applause.
+- No exclamation marks; celebration is not reassurance.
+- Confirmations are quiet: "Changes saved", never "Awesome!"
+- Errors name the problem and the fix in the place where the user can act.
+- Buttons name the act — "Delete account", "Save changes", "Invite member",
+  not "Do it" or "Let's go".
+- Motion carries three durations — `--duration-fast`, `--duration-normal`,
+  `--duration-slow` — and one ease, `--ease-spring`, which should feel
+  resolved without feeling elastic.
+- Hover confirms with color and background shifts at the fast duration.
+
+## Never
+
+- Never ship a vague failure banner — it is evasion; instead name the
+  problem and the fix in the place where the user can act.
+- Never soften the verb on destructive copy — it makes the interface less
+  honest; instead name the destructive act directly.
+- Never celebrate at the user — instead let trust come from precision,
+  restraint, and naming the truth plainly.
+- Never confirm hover with levitation — instead confirm with color and
+  background shifts at the fast duration.
+- Never carry editorial confidence into a settings form — instead let
+  product copy serve the task before it serves the voice.

package/dist/init-payloads/vessel-light/{signature.type.md → foundation.type.md}

@@ -11,6 +11,8 @@ materials:
   - materials/fonts/HKGrotesk-SemiBold.woff2
 ---
 
+## Usage
+
 This is Vessel's answer to type — it stands until you replace it.
 
 The relationship is fixed: one typeface is the voice of the interface,
@@ -19,19 +21,9 @@ output. The heading scale is editorial — its tokens exist for pages composed
 outside the text variants — and product UI never mixes the two vocabularies
 in one view.
 
-Vessel's current answer: HK Grotesk. vessel-light ships it as its embedded
-voice — here, `tokens.css` is canonical.
-
-The heading scale is editorial: display, section, and sub each carry their
-own rhythm (`--heading-display-*`, `--heading-section-*`, `--heading-sub-*`).
 Display sizes use tight tracking and sub-1 line heights because the words
-behave like composition, not paragraph text. Card-level headings inside
-editorial features use the product `title` variant — the scale does not reach
-below sub.
-
-Labels are small, semibold, and tracked wide. They should feel precise, never
-loud. Body text keeps the established reading sizes with relaxed line height;
-do not shrink important prose until it becomes legal copy.
+behave like composition, not paragraph text. Labels should feel precise,
+never loud.
 
 Condition: display and section scale are for editorial or hero moments.
 Product UI lives in headline, title, body, label, and mono. A modal title is
@@ -41,3 +33,26 @@ To adapt: swap the font files, edit `--font-sans`, `--font-mono`, and the
 heading tokens in `materials/tokens.css`, and restate this node's current
 answer. The one-voice rule and the editorial/product vocabulary split are the
 parts worth keeping.
+
+## Rules
+
+- The typeface is HK Grotesk. vessel-light ships it as its embedded voice —
+  here, `tokens.css` is canonical.
+- The heading scale is editorial: display, section, and sub each carry their
+  own rhythm (`--heading-display-*`, `--heading-section-*`,
+  `--heading-sub-*`).
+- Card-level headings inside editorial features use the product `title`
+  variant — the scale does not reach below sub.
+- Labels are small, semibold, and tracked wide.
+- Body text keeps the established reading sizes with relaxed line height.
+- Product UI lives in headline, title, body, label, and mono.
+
+## Never
+
+- Never mix the editorial heading scale and the product text variants in one
+  view — instead keep each vocabulary in its own context; a modal title is
+  not a poster.
+- Never shrink important prose until it becomes legal copy — instead keep
+  body text at the established reading sizes with relaxed line height.
+- Never make labels loud — instead keep them small, semibold, and tracked
+  wide so they feel precise.

package/dist/init-payloads/vessel-light/glossary.md

@@ -1,44 +1,41 @@
 ---
 kinds:
-  - name: grammar
-  - name: signature
-  - name: register
-  - name: anti-goal
+  - name: standard
+  - name: foundation
+  - name: context
 ---
 
-# grammar
+# standard
 
-The brand's decision logic: closed sets, role vocabularies, and assembly
-rules, stated in token roles and never in literal values. Grammar survives an
-adaptation unchanged — adapt the package, swap every value, and these nodes still
-hold. Gather grammar before inventing structure.
+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. A **Default** is a starting position that protects unsteered
+work from generic model behavior; explicit brand guidance may deliberately
+replace it. When a default with a paired check is overridden, adapt or remove
+the check flag in the same change.
 
-# signature
+# foundation
 
-The dials: the choices that make this brand this brand, each stated as a
-current answer that stands until you replace it. Signature nodes name real
-values because they are the values — on adaptation, edit the token roles in
-`materials/tokens.css` and restate the node. Gather signature before setting
-any value a dial governs.
+Vessel's load-bearing decisions: the closed sets, role vocabularies, and
+assembly rules, plus the answered identity dials — shape, palette, type,
+temperature — each stating Vessel's current answer, which stands until you
+replace it. The role logic survives an adaptation unchanged; the answered
+values do not — on adaptation, edit the token roles in `materials/tokens.css`
+and restate each answer. Gather foundations before inventing structure or
+setting any value a dial governs.
 
-# register
+# context
 
-A condition-scoped contract: a situation — data-dense consoles, editorial
-pages, transactional email — where parts of the default rules invert. Each
-register names its condition first. Truths from the wrong register are
-poison, not context; gather a register only when its condition matches the
+A named situation — data-dense consoles, editorial pages, transactional
+email, conversation UI — where parts of the default rules bend or invert.
+Each context names its condition first. Truths from the wrong context are
+poison, not guidance; read a context only when its condition matches the
 task.
 
-# anti-goal
-
-What this package refuses, each reject paired with its replacement.
-`anti-goal.median` is the model's floor, not the brand's taste;
-`anti-goal.tells` is the near-miss map of this brand's own signature. Gather
-anti-goals before styling anything greenfield.
-
 ---
 
 To adapt this package to another brand, follow the starter section of the
-`authoring` recipe in the ghost skill bundle. In short: new manifest id, prune the
-median rules your brand legitimately violates, answer each signature node,
-edit `materials/tokens.css`, regenerate the examples, rewrite the tells.
+`authoring` recipe in the ghost skill bundle. In short: new manifest id, prune
+the shared model-defaults rules your brand legitimately violates, restate each
+answered foundation dial, edit `materials/tokens.css`, regenerate the
+examples, rewrite the tells.