@oneli8/tokens 1.0.0-beta.8 → 1.0.0-beta.9

package/README.md

@@ -22,10 +22,16 @@ import '@oneli8/tokens/css';             // every token as a :root custom proper
 import { tokens } from '@oneli8/tokens'; // flat { 'color-text-primary': '#151817', ... }
 ```
 
-Names are not derived from a rule. Every variable carries an explicit code
-syntax in Figma, recorded verbatim in `src/figma-code-syntax.txt`, so the name a
-component reads is the name the designer set. Where Figma spells two sibling
-tokens differently, this package reproduces both rather than tidying one.
+The names follow a grammar, and the grammar is borrowed from Sanskrit rather
+than from a CSS convention. A compound that names one thing is written as one
+word, and a qualifier stays separate from what it qualifies. That is the whole
+rule, and the Naming section below works through it.
+
+Figma is the authority on the result. Every variable there carries an explicit
+code syntax, recorded verbatim in `src/figma-code-syntax.txt`, so a component
+reads the spelling the designer set rather than one re-derived from the grammar.
+Where the file spells two siblings differently, this package reproduces both
+rather than tidying one. The grammar is the rule; the record is the spelling.
 
 The vocabulary is authored across `src/primitive.json`, `src/semantic.json`,
 `src/component.json` and `src/themes.json`, each value carrying its own

package/ai-context.json

@@ -1,13 +1,16 @@
 {
   "$comment": "GENERATED by packages/sync/src/build-package-context.mjs — do not edit.",
   "system": "OneLi8",
-  "version": "1.0.0-beta.8",
+  "version": "1.0.0-beta.9",
   "meaning": "OneLi8 means One Light.",
   "foundations": {
     "package": "@oneli8/tokens",
     "css": "@oneli8/tokens/css",
     "tokenPrefix": "--ol8-",
-    "namingAuthority": "Figma. Every variable carries an explicit codeSyntax, recorded verbatim in packages/tokens/src/figma-code-syntax.txt. Names are never derived from a rule.",
+    "naming": {
+      "grammar": "Sanskrit grammar, not a CSS convention. Two rules follow from it and together they explain every name in the system. First, a compound that names ONE thing is written as one word: actionprimary is a single role rather than action plus primary, and cutedge is one feature of the Gem material, so action-primary would suggest two things where there is one. Second, a qualifier stays SEPARATE from what it qualifies: in --ol8-material-control-gem--primary-hover-start, hover is a state applied to start, two grammatical roles, so they stay apart. That is why disabledcontent is joined while hover-start is not. Hyphens separate levels of the hierarchy, never words inside a level. Words stay readable: no abbreviations, no truncation, no btn where button will do.",
+      "authority": "Figma is the authority on the result. Every variable there carries an explicit codeSyntax, copied verbatim into packages/tokens/src/figma-code-syntax.txt. Read a name from that record rather than re-deriving it from the grammar, because the file is not perfectly regular between siblings and guessing is how code and design drifted apart before. The grammar is the rule; the record is the spelling."
+    },
     "rules": [
       "Components consume SEMANTIC roles only. Primitives (color-<family>-<step>) are hidden from pickers in Figma and must not appear in component code.",
       "color-primary-* is an alias ramp onto color-blue-* — identical values, distinct names. Prefer the semantic role over either.",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@oneli8/tokens",
-  "version": "1.0.0-beta.8",
+  "version": "1.0.0-beta.9",
   "description": "OneLi8 Design System \u2014 design tokens compiled from Figma. CSS custom properties and a flat JS object.",
   "keywords": [
     "design-tokens",