mythik 0.0.1 → 0.1.0

package/docs/wiki/compiled/concept-storage-postgres-jsonb.md

@@ -0,0 +1,53 @@
+---
+id: concept-storage-postgres-jsonb
+title: Storage — Postgres `jsonb` requirement
+kind: concept
+sources: [docs/consumer/ai-context.md#postgres--supabase-jsonb-for-spec-and-patches]
+---
+
+# Postgres / Supabase: `jsonb` for `spec` and `patches`
+
+On Postgres-flavored backends (Supabase, plain Postgres), the JSON columns
+**MUST be `jsonb`, not `text`**.
+
+## Affected columns
+
+- `screens.spec`
+- `screen_versions.spec`
+- `screen_versions.patches`
+
+## Why
+
+Supabase code path returns rows directly from PostgREST without defensive
+parse:
+
+- `screens.spec` — `supabase.ts:41` returns `rows[0].spec` directly. A
+  `text` column would return a string and downstream consumers
+  (`MythikInstance.getSpec`, `MythikRenderer`) would receive a stringified
+  spec instead of an object.
+- `screen_versions.spec` and `.patches` — Supabase versioned path consumes
+  these as already-parsed objects from PostgREST. A `text` column would
+  cause `applyPatches` / `structuredClone` to receive a string instead of
+  an object — **silent corruption**.
+
+## SQL Server is defensive
+
+SQL Server stores parse `NVARCHAR(MAX)` defensively
+(`typeof === 'string' ? JSON.parse(...) : raw` at `sqlserver.ts:58` and
+`sqlserver-versioned.ts:133-135` and `:153`) and tolerate either form.
+Postgres-flavored stores have **no such defense**.
+
+## Verification
+
+Verify the column type via INFORMATION_SCHEMA — see
+[[@concept-storage-verification]].
+
+## Related concepts
+
+- [[@concept-storage-overview]]
+- [[@concept-storage-postgres-triggers]]
+- [[@concept-storage-verification]]
+
+## Sources (raw)
+
+- `docs/consumer/ai-context.md § Postgres / Supabase: jsonb for spec and patches`

package/docs/wiki/compiled/concept-storage-postgres-triggers.md

@@ -0,0 +1,60 @@
+---
+id: concept-storage-postgres-triggers
+title: Storage — Postgres triggers for `screens`
+kind: concept
+sources: [docs/consumer/ai-context.md#postgres--supabase-triggers-for-screensupdated_at-and-screensversion]
+---
+
+# Postgres / Supabase: triggers for `screens.updated_at` and `screens.version`
+
+On Postgres-flavored backends, these two columns MUST be maintained by
+**`BEFORE UPDATE` triggers** because the Supabase save path sends only
+the `spec` field — it does NOT update `updated_at` or `version` itself.
+
+## Why SQL Server doesn't need this
+
+SQL Server stores set both columns app-level inside the MERGE
+(`sqlserver.ts:74`: `UPDATE SET spec = @spec, updated_at = GETUTCDATE(),
+version = version + 1`).
+
+## Recommended trigger pair on Postgres
+
+```sql
+CREATE OR REPLACE FUNCTION screens_update_updated_at()
+RETURNS TRIGGER AS $$ BEGIN NEW.updated_at = NOW(); RETURN NEW; END; $$ LANGUAGE plpgsql;
+
+CREATE OR REPLACE FUNCTION screens_increment_version()
+RETURNS TRIGGER AS $$ BEGIN NEW.version = OLD.version + 1; RETURN NEW; END; $$ LANGUAGE plpgsql;
+
+CREATE TRIGGER screens_updated_at_trigger
+  BEFORE UPDATE ON screens
+  FOR EACH ROW EXECUTE FUNCTION screens_update_updated_at();
+
+CREATE TRIGGER screens_version_trigger
+  BEFORE UPDATE ON screens
+  FOR EACH ROW EXECUTE FUNCTION screens_increment_version();
+```
+
+Trigger function names are arbitrary (use any unique name); the framework
+does not introspect them.
+
+## Other tables don't need triggers
+
+`screen_versions` and `screen_environments` are append-only / upsert-on-PK
+and the framework writes all columns explicitly on each INSERT/UPSERT.
+
+## Verification
+
+Verify the triggers exist via `information_schema.triggers WHERE
+event_object_table = 'screens'`. Without them, `updated_at` and `version`
+will silently stop advancing on save.
+
+## Related concepts
+
+- [[@concept-storage-overview]]
+- [[@concept-storage-postgres-jsonb]]
+- [[@concept-storage-verification]]
+
+## Sources (raw)
+
+- `docs/consumer/ai-context.md § Postgres / Supabase: triggers for screens.updated_at and screens.version`

package/docs/wiki/compiled/concept-storage-table-environments.md

@@ -0,0 +1,40 @@
+---
+id: concept-storage-table-environments
+title: Storage — Table 2 `screen_environments`
+kind: concept
+sources: [docs/consumer/ai-context.md#storage-setup]
+---
+
+# Table 2 — `screen_environments` (opt-in)
+
+Environment promotions. Required only when using `*EnvironmentStore`.
+
+## Columns
+
+| Column | Semantic type | Nullable | Default | Notes |
+|---|---|---|---|---|
+| `screen_id` | short string (≤255) | NOT NULL | — | PK part 1 |
+| `environment` | short string (≤100) | NOT NULL | — | PK part 2 (`dev`, `staging`, `prod`, etc.) |
+| `version` | integer | NOT NULL | — | Promoted spec version (logical reference to `screen_versions.version`; not enforced as FK in v0.1.0) |
+| `promoted_at` | UTC timestamp | NOT NULL | NOW UTC | Set by DB on insert; UPDATE on re-promotion |
+| `promoted_by` | short string (≤255) | NOT NULL | `'system'` | Author who promoted |
+
+## Constraints
+
+- `PRIMARY KEY (screen_id, environment)` — one promotion record per
+  `(spec, env)` pair; re-promote upserts via MERGE/UPSERT
+
+## No triggers needed
+
+This table is append-only / upsert-on-PK; the framework writes all columns
+explicitly on each INSERT/UPSERT.
+
+## Related concepts
+
+- [[@concept-storage-overview]]
+- [[@concept-environment-store]]
+- [[@concept-promote-gate]]
+
+## Sources (raw)
+
+- `docs/consumer/ai-context.md § Storage Setup → Table 2 — screen_environments`

package/docs/wiki/compiled/concept-storage-table-screens.md

@@ -0,0 +1,44 @@
+---
+id: concept-storage-table-screens
+title: Storage — Table 0 `screens`
+kind: concept
+sources: [docs/consumer/ai-context.md#storage-setup]
+---
+
+# Table 0 — `screens` (REQUIRED)
+
+Current spec per `id`. Used by every adapter.
+
+## Columns
+
+| Column | Semantic type | Nullable | Default | Notes |
+|---|---|---|---|---|
+| `id` | short string (≤255) | NOT NULL | — | Spec identifier; PK |
+| `name` | short string (≤255) | NULL | — | Display name. Framework's INSERT populates with `id` value |
+| `spec` | long string (≥1MB capacity) | NOT NULL | — | JSON-encoded current spec. SQL Server: `NVARCHAR(MAX)` text. **Postgres / Supabase MUST be `jsonb`** — see [[@concept-storage-postgres-jsonb]] |
+| `version` | integer | NOT NULL | `1` | Incremented on every UPDATE. SQL Server: app-level. Postgres: via TRIGGER (see [[@concept-storage-postgres-triggers]]) |
+| `is_active` | boolean | NOT NULL | `true` | Framework's INSERT sets `1`/`true`; UPDATE never touches it |
+| `created_at` | UTC timestamp | — | — | OPTIONAL — framework does not read or write. If added, make `NOT NULL` with NOW UTC default |
+| `updated_at` | UTC timestamp | NOT NULL | NOW UTC | Required. Updated on every UPDATE. SQL Server: app-level. Postgres: via TRIGGER |
+
+## Constraints
+
+- `PRIMARY KEY (id)` — required (every framework query filters by `id`)
+
+## Indexes (RECOMMENDED, none required)
+
+- `(is_active, id)` — useful for consumer queries filtering active
+  screens. Framework's `list()` uses only `ORDER BY id`, so this is
+  consumer-hygiene only.
+
+## Related concepts
+
+- [[@concept-storage-overview]]
+- [[@concept-storage-postgres-jsonb]]
+- [[@concept-storage-postgres-triggers]]
+- [[@concept-spec-store-interface]]
+- [[@concept-spec-stores-catalog]]
+
+## Sources (raw)
+
+- `docs/consumer/ai-context.md § Storage Setup → Table 0 — screens`

package/docs/wiki/compiled/concept-storage-table-versions.md

@@ -0,0 +1,50 @@
+---
+id: concept-storage-table-versions
+title: Storage — Table 1 `screen_versions`
+kind: concept
+sources: [docs/consumer/ai-context.md#storage-setup]
+---
+
+# Table 1 — `screen_versions` (opt-in)
+
+Version history. Required only when using `*VersionedSpecStore`.
+
+## Columns
+
+| Column | Semantic type | Nullable | Default | Notes |
+|---|---|---|---|---|
+| `id` | auto-increment integer, PK | NOT NULL | DB-managed | Surrogate PK; framework never writes |
+| `screen_id` | short string (≤255) | NOT NULL | — | Spec doc identifier |
+| `version` | integer | NOT NULL | — | Sequential per-`screen_id`; framework computes via `MAX(version) + 1` |
+| `is_snapshot` | boolean | NOT NULL | `false` | `true` for full-spec rows, `false` for patch rows |
+| `spec` | long string (≥1MB capacity) | NULL | — | JSON-encoded full spec; populated only when `is_snapshot = true` |
+| `patches` | long string (≥1MB capacity) | NULL | — | JSON-encoded patch array; populated only when `is_snapshot = false` |
+| `author` | short string (≤255) | NOT NULL | `'system'` | Provided via `--author` flag; bootstrapped to `'system'` for lazy v1 backfill |
+| `source_type` | short string (≤50) | NOT NULL | `'push'` | Source channel (`push`, `patch`, etc.) |
+| `description` | medium string (≤1000) | NULL | — | Optional description from `--description` flag |
+| `created_at` | UTC timestamp | NOT NULL | NOW UTC | Set by DB on insert |
+
+## Constraints
+
+- `PRIMARY KEY (id)` — surrogate key on auto-increment
+- `UNIQUE (screen_id, version)` — framework relies on per-screen
+  uniqueness to compute next version
+
+## Indexes (required for query performance)
+
+- `(screen_id, version)` — supports `WHERE screen_id = ? ORDER BY version DESC`
+- `(screen_id, version) WHERE is_snapshot = true` (partial index) —
+  accelerates `loadVersion`'s nearest-snapshot lookup. Omit if target
+  DB doesn't support partial indexes (correctness preserved, performance
+  degrades on long histories).
+
+## Related concepts
+
+- [[@concept-storage-overview]]
+- [[@concept-versioned-store]]
+- [[@concept-versioning-snapshots-patches]]
+- [[@cli-versioning-author]]
+
+## Sources (raw)
+
+- `docs/consumer/ai-context.md § Storage Setup → Table 1 — screen_versions`

package/docs/wiki/compiled/concept-storage-verification.md

@@ -0,0 +1,57 @@
+---
+id: concept-storage-verification
+title: Storage — post-apply verification
+kind: concept
+sources: [docs/consumer/ai-context.md#verification-post-apply]
+---
+
+# Storage verification (post-apply)
+
+After applying the DDL, verify the relevant tables exist with correct
+columns by querying the target's information schema.
+
+## Standard ANSI query
+
+```sql
+SELECT TABLE_NAME, COLUMN_NAME, DATA_TYPE, IS_NULLABLE
+FROM INFORMATION_SCHEMA.COLUMNS
+WHERE TABLE_NAME IN ('screens', 'screen_versions', 'screen_environments')
+ORDER BY TABLE_NAME, ORDINAL_POSITION;
+```
+
+(Consumers using only the base store can drop `screen_versions` +
+`screen_environments` from the `IN (...)` list.)
+
+## Confirm column counts
+
+- 7 columns for `screens` (`id`, `name`, `spec`, `version`, `is_active`,
+  `created_at`, `updated_at`)
+- 10 columns for `screen_versions`
+- 5 columns for `screen_environments`
+
+## Postgres-only — verify triggers
+
+```sql
+SELECT trigger_name, event_object_table
+FROM information_schema.triggers
+WHERE event_object_table = 'screens';
+```
+
+Without the two triggers, `updated_at` and `version` will silently stop
+advancing on save.
+
+## If verification fails
+
+If any column is missing or has a wrong NULL/NOT NULL flag, abort and
+report — the framework's INSERT/SELECT/UPDATE will fail at runtime.
+
+## Related concepts
+
+- [[@concept-storage-overview]]
+- [[@concept-storage-postgres-triggers]]
+- [[@concept-storage-postgres-jsonb]]
+- [[@concept-storage-idempotency]]
+
+## Sources (raw)
+
+- `docs/consumer/ai-context.md § Verification (post-apply)`

package/docs/wiki/compiled/concept-template-children-marker.md

@@ -0,0 +1,56 @@
+---
+id: concept-template-children-marker
+title: `"$children"` — template children slot
+kind: concept
+sources: [docs/consumer/ai-context.md#templates, docs/consumer/reference-doc.md#element-templates-templates]
+---
+
+# `"$children"` — template children slot
+
+Authors mark where consumer-supplied children should be inserted by writing
+the **string literal** `"$children"` as an item in the template's `children`
+array (NOT an expression object — see anti-patterns).
+
+## Shape / Signature
+
+```json
+{
+  "templates": {
+    "card": {
+      "type": "box",
+      "defaults": { "padding": 16 },
+      "style": { "padding": { "$prop": "padding" }, "borderRadius": 12, "backgroundColor": { "$token": "colors.surface" } },
+      "children": ["$children"]
+    }
+  },
+  "elements": {
+    "my-card": { "type": "card", "children": ["title", "body"] }
+  }
+}
+```
+
+`"$children"` is replaced with the consuming element's actual children
+(`["title", "body"]`) at expansion time.
+
+## Multiple slots
+
+Multiple `"$children"` markers each splice the full consumer children
+list — the same children render in each slot position.
+
+## Constraints / Anti-patterns
+
+- **`"$children"` is a string literal** — write the bare string in the
+  array, NOT `{ "$children": true }`. The expression-object form is
+  silently ignored.
+- Same slot semantics apply to custom-element render trees — see
+  [[@concept-element-children-slot]].
+
+## Related concepts
+
+- [[@concept-templates]]
+- [[@concept-element-children-slot]] — Layer 3 equivalent
+
+## Sources (raw)
+
+- `docs/consumer/ai-context.md § Templates`
+- `docs/consumer/reference-doc.md § Element Templates → Templates with children`

package/docs/wiki/compiled/concept-template-interpolation.md

@@ -0,0 +1,60 @@
+---
+id: concept-template-interpolation
+title: `$template` interpolation contract
+kind: concept
+sources: [docs/consumer/ai-context-runtime-semantics.md#15-template-interpolation]
+---
+
+# `$template` interpolation contract
+
+`$template` is resolved at the **consumption site**. The same template object
+resolves at different times depending on where it lives in the spec.
+
+## Site contract
+
+| Site | Timing | Context |
+|---|---|---|
+| Element prop | At render | Render context (eager) |
+| Action param | At dispatch | Dispatch-time state (lazy) |
+
+Nested expressions (`$state`, `$auth`, `$math`) inside the template resolve
+with the template's execution context.
+
+## Examples
+
+In a prop — resolves at render with the current `/auth/user/id`:
+```json
+{ "props": { "src": { "$template": "/avatars/${ /auth/user/id }.png" } } }
+```
+
+In an action param — resolves at dispatch with the current `/ui/selectedId`:
+```json
+{ "action": "fetch", "params": { "url": { "$template": "/api/items/${ /ui/selectedId }" } } }
+```
+
+## Reference forms inside `$template`
+
+| Form | Resolves to |
+|---|---|
+| `${/state/path}` | Read from state |
+| `${name}` | Read from a `$let` binding |
+
+## Constraints / Anti-patterns
+
+- **`$item` does NOT resolve directly inside `$template`.** Capture in
+  `$let` first.
+- **`$template` does NOT resolve in transaction phases.** Capture row data
+  via `setState` first.
+- In `DataSourceConfig.url`, plain strings containing `${...}` are LITERAL
+  — wrap in `$template` to enable templating. Validator catches this and
+  points to the fix.
+
+## Related concepts
+
+- [[@expression-template]] — basic syntax
+- [[@expression-let-ref]] — capturing for `$template`
+- [[@concept-expression-timing]] — full timing matrix
+
+## Sources (raw)
+
+- `docs/consumer/ai-context-runtime-semantics.md § 1.5`

package/docs/wiki/compiled/concept-templates-vs-variants.md

@@ -0,0 +1,80 @@
+---
+id: concept-templates-vs-variants
+title: Templates vs Variants — decision table
+kind: concept
+sources: [docs/consumer/ai-context-patterns.md#reusable-components--templates--variants]
+---
+
+# Templates vs Variants — when to pick which
+
+Two underused reuse mechanisms. **Use them before duplicating style blocks.**
+
+## Decision table
+
+| Situation | Pick |
+|---|---|
+| Same primitive type, different style set | `tokens.components.{type}.{variant}` |
+| Composite (custom type wrapping primitive + children slot) | `appSpec.templates` |
+| Style varies by state (hover/active/focus) | Variants (built-in state slots) |
+| Parametrized via props + children | Templates (with `$prop` + `$children`) |
+
+## Trade-off
+
+- **Variants are lightweight** and integrate natively with primitive
+  rendering. Prefer when you only vary style.
+- **Templates are more flexible** but more verbose. Use when you compose
+  structure (different children, parametrized props beyond style).
+
+## Example — variant (style-only)
+
+```json
+"tokens": {
+  "components": {
+    "button": {
+      "ctaPulse": {
+        "style": { "background": { "$token": "colors.primary" } },
+        "animations": {
+          "ambient": { "recipe": "pulse-primary" },
+          "hover": { "recipe": "lift" }
+        }
+      }
+    }
+  }
+}
+```
+
+Use: `{ "type": "button", "props": { "variant": "ctaPulse", "label": "..." } }`.
+
+## Example — template (composite)
+
+```json
+"templates": {
+  "button-pulse-cta": {
+    "type": "button",
+    "defaults": { "variant": "primary" },
+    "props": { "label": { "$prop": "label" } },
+    "style": { "background": "linear-gradient(135deg, #6366f1, #8b5cf6)", "padding": { "$prop": "padding" } },
+    "animations": { "ambient": { "recipe": "pulse-primary" } },
+    "children": ["$children"]
+  }
+}
+```
+
+Use: `{ "type": "button-pulse-cta", "props": { "label": "Sign Up", "padding": "10px 20px" } }`.
+
+## Animations cascade across both
+
+`animations` declared at any of these levels merges via the cascade —
+identity → variant → elementDef → template → element. See
+[[@concept-animation-cascade]].
+
+## Related concepts
+
+- [[@concept-templates]]
+- [[@concept-component-variants]]
+- [[@concept-animation-cascade]]
+- [[@antipattern-style-block-duplication]]
+
+## Sources (raw)
+
+- `docs/consumer/ai-context-patterns.md § Reusable Components — Templates + Variants`

package/docs/wiki/compiled/concept-templates.md

@@ -0,0 +1,93 @@
+---
+id: concept-templates
+title: `templates` — reusable element definitions
+kind: concept
+sources: [docs/consumer/ai-context.md#templates, docs/consumer/reference-doc.md#element-templates-templates]
+---
+
+# `templates` — reusable element definitions
+
+Define reusable element shapes once, reference by custom type name in any
+screen. Reduces repetition for monetary columns, stat cards, button
+variants with content slots, etc.
+
+## Shape / Signature
+
+```json
+{
+  "templates": {
+    "monetary-col": {
+      "type": "text",
+      "defaults": { "color": "#0F172A", "currency": "HNL" },
+      "props": {
+        "content": { "$format": "currency", "value": { "$prop": "value" }, "currency": { "$prop": "currency" }, "locale": "es-HN" }
+      },
+      "style": {
+        "textAlign": "right", "fontFamily": "monospace",
+        "color": { "$prop": "color" }
+      }
+    }
+  },
+  "elements": {
+    "col-amount": { "type": "monetary-col", "props": { "value": { "$item": "amount" } } },
+    "col-total": { "type": "monetary-col", "props": { "value": { "$item": "total" }, "color": "#D97706" } }
+  }
+}
+```
+
+## Template properties
+
+| Property | Type | Description |
+|---|---|---|
+| `type` | string | Primitive type the template wraps |
+| `defaults` | object | Default prop values |
+| `props` | object | Props using `$prop` for parameterization |
+| `style` | object | Style using `$prop` |
+| `children` | string[] | Child element IDs. Use `"$children"` marker to insert consumer's children |
+
+Templates support all Element fields: `visible`, `hover`, `active`, `motion`,
+`animations`, etc.
+
+## Sharing
+
+- AppSpec-level templates available to all screens.
+- Screen-level templates override app-level with same name.
+
+## Composite templates with `$let`
+
+When `$prop` needs to flow into `$template`, bridge via `$let`:
+
+```json
+"stat-card": {
+  "type": "text",
+  "defaults": { "label": "Count", "value": 0 },
+  "props": {
+    "content": {
+      "$let": { "l": { "$prop": "label" }, "v": { "$prop": "value" } },
+      "$in": { "$template": "${l}: ${v}" }
+    }
+  }
+}
+```
+
+## Constraints / Anti-patterns
+
+- Templates are **single elements** — one `type` with props/style/defaults.
+  For multi-element compositions, the consuming element defines children
+  alongside the template type.
+- **Don't duplicate style blocks across specs** — extract to a template or
+  variant. See [[@antipattern-style-block-duplication]] +
+  [[@concept-templates-vs-variants]].
+
+## Related concepts
+
+- [[@expression-prop]]
+- [[@expression-let-ref]]
+- [[@concept-template-children-marker]]
+- [[@concept-templates-vs-variants]]
+- [[@concept-component-variants]]
+
+## Sources (raw)
+
+- `docs/consumer/ai-context.md § Templates`
+- `docs/consumer/reference-doc.md § Element Templates (templates)`

package/docs/wiki/compiled/concept-token-categories.md

@@ -0,0 +1,58 @@
+---
+id: concept-token-categories
+title: Token categories — `$token` paths
+kind: concept
+sources: [docs/consumer/ai-context.md#deep-design-token-system, docs/consumer/reference-doc.md#token-categories--token-paths]
+---
+
+# Token categories
+
+All primitives consume tokens via `useDesignTokens` internally. Specs
+reference them via `$token` with dot notation.
+
+## Categories
+
+| Category | Paths | Example |
+|---|---|---|
+| Colors | `colors.primary`, `colors.surface`, `colors.text`, `colors.error`, `colors.accent`, etc. (13 semantic colors) | `{ "$token": "colors.primary" }` |
+| Shape | `shape.radius.none/sm/md/lg/xl/full` | `{ "$token": "shape.radius.lg" }` |
+| Typography | `typography.fontFamily.base/heading/mono`, `typography.scale.xs/sm/md/lg/xl/2xl` (each has `.fontSize`, `.lineHeight`), `typography.weight.normal/medium/semibold/bold`, `typography.letterSpacing`, `typography.headingLetterSpacing` | `{ "$token": "typography.scale.xl.fontSize" }` |
+| Spacing | `spacing.unit`, `spacing.scale.xs/sm/md/lg/xl/2xl` | `{ "$token": "spacing.scale.md" }` |
+| Elevation | `elevation.none/sm/md/lg/xl` — auto-converts to CSS `boxShadow` string in `$token` | `{ "$token": "elevation.lg" }` |
+| Motion | `motion.duration.fast/normal/slow`, `motion.easing.default/enter/exit`, `motion.spring.damping/stiffness/mass`, `motion.stagger` | `{ "$token": "motion.duration.fast" }` |
+| Opacity | `opacity.disabled/pressed/backdrop/muted` | `{ "$token": "opacity.backdrop" }` |
+
+## Identity-derived
+
+| Category | Paths | Notes |
+|---|---|---|
+| Scheme colors | `schemeColors.text`, `schemeColors.surface`, etc. | For preview/themed content (rule 131) |
+| Color weight | `colorWeight.navBg`, `colorWeight.navText`, `colorWeight.sectionBg`, `colorWeight.heroBg`, `colorWeight.heroGradient` | Layout tokens — see [[@concept-identity-color-weight]] |
+
+## Auto elevation conversion
+
+`{ "$token": "elevation.md" }` returns a CSS `boxShadow` string on web
+(e.g., `"0px 4px 12px rgba(0,0,0,0.15)"`). On RN, primitives handle
+elevation internally via native shadow props. No manual conversion needed
+(rule 100).
+
+## `multiply`
+
+```json
+{ "$token": "spacing.unit", "multiply": 3 }
+```
+
+Scales a numeric token (e.g., `spacing.unit` × 3).
+
+## Related concepts
+
+- [[@concept-token-system]]
+- [[@concept-dna-seeds]]
+- [[@expression-token]]
+- [[@concept-identity-color-weight]]
+- [[@concept-identity-color-scheme]]
+
+## Sources (raw)
+
+- `docs/consumer/ai-context.md § Deep Design Token System → Token categories`
+- `docs/consumer/reference-doc.md § Token Categories & $token Paths`