@stratixlabs/core 1.7.1 → 1.7.2

package/README.md

@@ -1,16 +1,16 @@
-# Substrata
+# Stratix
 
-Substrata is a framework-agnostic **design infrastructure** for tokens, schemas, and automation that transforms design decisions into **semantic contracts**. It serves as a stable foundation for semantic design governance, enabling automation, consistency, and long-term resilience across any platform or tech stack.
+Stratix is a framework-agnostic **design infrastructure** for tokens, schemas, and automation that transforms design decisions into **semantic contracts**. It serves as a stable foundation for semantic design governance, enabling automation, consistency, and long-term resilience across any platform or tech stack.
 
-Unlike a UI library that couples design to components, Substrata provides the low-level *definitions* (design tokens and their canonical graph) that drive the UI, ensuring design intent is preserved from design tools to production code—even as frameworks change.
+Unlike a UI library that couples design to components, Stratix provides the low-level *definitions* (design tokens and their canonical graph) that drive the UI, ensuring design intent is preserved from design tools to production code—even as frameworks change.
 
-**[Documentation](https://mikaelcarrara.github.io/substrata)**
+**[Documentation](https://github.com/mikaelcarrara/stratix)**
 
 ---
 
 ## Philosophy
 
-Substrata is guided by a core set of architectural principles: tokens are the atomic foundation of design; infrastructure must outlive frameworks; and a single source of truth prevents divergence. We design for durability and longevity, achieving consistency through architecture, not discipline. Our focus is on defining the foundation, not the final UI surfaces.
+Stratix is guided by a core set of architectural principles: tokens are the atomic foundation of design; infrastructure must outlive frameworks; and a single source of truth prevents divergence. We design for durability and longevity, achieving consistency through architecture, not discipline. Our focus is on defining the foundation, not the final UI surfaces.
 
 See our policies on [**Governance**](./GOVERNANCE.md) and [**Contributing**](./CONTRIBUTING.md).
 
@@ -18,7 +18,7 @@ See our policies on [**Governance**](./GOVERNANCE.md) and [**Contributing**](./C
 
 ## Architecture
 
-Substrata is architected as a system of independent layers. Each layer encapsulates a distinct responsibility and can evolve independently, enabling long-term scalability, resilience, and architectural clarity.
+Stratix is architected as a system of independent layers. Each layer encapsulates a distinct responsibility and can evolve independently, enabling long-term scalability, resilience, and architectural clarity.
 
 1.  **Tokens**: Define design decisions as CSS Variables—colors, spacing, typography, and core primitives. They are semantic, stable, versionable, and platform-agnostic.
 2.  **Base Styles**: Apply tokens to native HTML elements, establishing predictable defaults and consistent rendering without adding abstractions or components.
@@ -30,11 +30,11 @@ This layered approach ensures that the core design system remains decoupled from
 
 ## W3C Alignment
 
-Substrata implements the "Source of Truth" layer in the W3C reference architecture:
+Stratix implements the "Source of Truth" layer in the W3C reference architecture:
 
 1.  **Definition**: Design intent defined in design tools (e.g., Figma).
 2.  **Transformation**: Raw data processed into usable artifacts.
-3.  **Source of Truth (Substrata)**: The detailed, versioned, and semantic definition of all tokens (CSS variables, JSON).
+3.  **Source of Truth (Stratix)**: The detailed, versioned, and semantic definition of all tokens (CSS variables, JSON).
 4.  **Consumption**: Applications (React, Vue, iOS, Android) consuming these tokens.
 
 Read more in [W3C Alignment](./docs/w3c-alignment.html).
@@ -43,35 +43,35 @@ Read more in [W3C Alignment](./docs/w3c-alignment.html).
 
 ## Choose Your Path
 
-Substrata is designed to be used in three distinct ways depending on your goal.
+Stratix is designed to be used in three distinct ways depending on your goal.
 
 | Path | Goal | Installation | Tool |
 | :--- | :--- | :--- | :--- |
-| **1. Consumer** | Use default tokens in your app | `npm install @stratixlabs/core` | NPM |
-| **2. Author** | Manage your own design system | `npx @stratixlabs/core init` | CLI (NPX) |
-| **3. Contributor** | Modify Substrata core/docs | `git clone ...` | Git |
+| **1. Consumer** | Use default tokens in your app | `npm install @stratixlabs/core` | NPM |
+| **2. Author** | Manage your own design system | `npx @stratixlabs/core init` | CLI (NPX) |
+| **3. Contributor** | Modify Stratix core/docs | `git clone ...` | Git |
 
 ---
 
 ### Path 1: Consumer (Recommended)
-Best for developers who want to use the official Substrata tokens (colors, spacing, etc.) in their project.
+Best for developers who want to use the official Stratix tokens (colors, spacing, etc.) in their project.
 
 ```bash
-npm install @stratixlabs/core
+npm install @stratixlabs/core
 ```
-*See [Getting Started](https://mikaelcarrara.github.io/substrata/getting-started) for importing CSS/JSON.*
+*See Getting Started for importing CSS/JSON.*
 
 ### Path 2: Author & Automation
-Best for architects building a custom design system using Substrata as the engine.
+Best for architects building a custom design system using Stratix as the engine.
 
 `init` scaffolds a **complete, production-ready** system:
 
 **📦 Generated Structure:**
-- `substrata.config.js` - Configuration file
+- `stratix.config.js` - Configuration file
 - `src/tokens/` - **9 token files** (colors, spacing, typography, radius-and-borders, elevation, motion, opacity, breakpoints, semantic-aliases)
 - `src/consumption/` - **3 framework examples** (Tailwind, styled-components, plain CSS)
 - `scripts/` - Automation scripts (generate, validate, lint, breaking-change detection, token-aware code lint)
-- `src/substrata.css` - Main entry point (imports all tokens)
+- `src/stratix.css` - Main entry point (imports all tokens)
 - `src/base.css` - Typography reset and base styles
 
 **📜 NPM Scripts Added:**
@@ -83,7 +83,7 @@ Best for architects building a custom design system using Substrata as the engin
 
 ```bash
 # Set up complete design system infrastructure
-npx @stratixlabs/core init
+npx stratix init
 
 # Generate tokens.json
 npm run build:tokens
@@ -92,16 +92,16 @@ npm run build:tokens
 npm run test:tokens
 ```
 
-Then import `src/substrata.css` in your app. Check `src/consumption/` for framework-specific integration examples.
+Then import `src/stratix.css` in your app. Check `src/consumption/` for framework-specific integration examples.
 
-*See [Authoring & Automation](https://mikaelcarrara.github.io/substrata/automation) for detailed guide.*
+*See Authoring & Automation for detailed guide.*
 
 ### Path 3: Contributor
-Best for those who want to improve Substrata itself or host their own fork.
+Best for those who want to improve Stratix itself or host their own fork.
 
 ```bash
-git clone https://github.com/mikaelcarrara/substrata.git
-cd substrata
+git clone https://github.com/mikaelcarrara/stratix.git
+cd stratix
 npm install
 npm run build:tokens
 ```
@@ -111,39 +111,39 @@ npm run build:tokens
 Clone or download from GitHub:
 
 ```bash
-git clone https://github.com/mikaelcarrara/substrata.git
+git clone https://github.com/mikaelcarrara/stratix.git
 ```
 
 Or download directly and include in your project.
 
 ## Usage
 
-Substrata is designed to be consumed, not imposed. You can use it in multiple ways:
+Stratix is designed to be consumed, not imposed. You can use it in multiple ways:
 
 ### 1. Plain CSS
 Import the full system or valid subsets from the package:
 ```css
 /* Import everything */
-@import "@stratixlabs/core/substrata.css";
+@import "@stratixlabs/core/stratix.css";
 
 /* Or just tokens */
-@import "@stratixlabs/core/src/tokens/colors.css";
+@import "@stratixlabs/core/src/tokens/colors.css";
 ```
 
 ### 2. Tailwind CSS
-Substrata feeds Tailwind. It does not replace it.
+Stratix feeds Tailwind. It does not replace it.
 ```css
-@import "@stratixlabs/core/substrata.css";
+@import "@stratixlabs/core/stratix.css";
 @tailwind base;
 @tailwind components;
 @tailwind utilities;
 ```
-*See the [Next.js + Tailwind Quickstart](https://mikaelcarrara.github.io/substrata/getting-started#quickstart-next-tailwind) for a full app example, and [Consumption Strategies](./docs/consumption.html) for `tailwind.config.js` mapping.*
+*See the Next.js + Tailwind Quickstart for a full app example, and [Consumption Strategies](./docs/consumption.html) for `tailwind.config.js` mapping.*
 
 ### 3. JavaScript / TypeScript
 Import tokens as a JSON object:
 ```js
-import tokens from '@stratixlabs/core';
+import tokens from '@stratixlabs/core';
 
 const Button = styled.button`
   padding: ${tokens.space[3].value} ${tokens.space[4].value};
@@ -156,7 +156,7 @@ const Button = styled.button`
 
 ## Documentation
 
-Full documentation is available online. Key sections include [**Getting Started**](https://mikaelcarrara.github.io/substrata/getting-started), the [**Tokens Reference**](https://mikaelcarrara.github.io/substrata/tokens), [**Consumption Strategies**](https://mikaelcarrara.github.io/substrata/consumption), and guides on [**Automation**](https://mikaelcarrara.github.io/substrata/automation).
+Full documentation is available online. Key sections include [**Getting Started**](https://mikaelcarrara.github.io/Stratix/getting-started), the [**Tokens Reference**](https://mikaelcarrara.github.io/Stratix/tokens), [**Consumption Strategies**](https://mikaelcarrara.github.io/Stratix/consumption), and guides on [**Automation**](https://mikaelcarrara.github.io/Stratix/automation).
 
 ---
 
@@ -181,11 +181,11 @@ These aliases help preserve intent across frameworks and refactors.
 
 ## Core Artifacts
 
-Substrata's architecture is defined by a few key artifacts that enable its semantic power:
+Stratix's architecture is defined by a few key artifacts that enable its semantic power:
 
 - **`tokens.json`**: The canonical source of truth, containing all design tokens in a structured, machine-readable format.
 - **JSON Schema**: A strict schema for `tokens.json` that enables validation, IDE autocompletion, and automated CI checks.
-- **`substrata.d.ts`**: TypeScript declarations for type-safe token consumption in modern development workflows.
+- **`stratix.d.ts`**: TypeScript declarations for type-safe token consumption in modern development workflows.
 
 See the [**ROADMAP.md**](./ROADMAP.md) and [**ARCHITECTURE.md**](./ARCHITECTURE.md) for more details on our architectural evolution.
 
@@ -193,35 +193,35 @@ See the [**ROADMAP.md**](./ROADMAP.md) and [**ARCHITECTURE.md**](./ARCHITECTURE.
 
 ## Tooling & Scripts
 
-- [detect-breaking-changes.js](file:///c:/Users/Usuario/Desktop/substrata/scripts/detect-breaking-changes.js)
+- [detect-breaking-changes.js](file:///c:/Users/Usuario/Desktop/Stratix/scripts/detect-breaking-changes.js)
   - What it does: Detects when tokens are removed or renamed
   - Foundation: Basic validation, table stakes
 
-- [figma-sync.js](file:///c:/Users/Usuario/Desktop/substrata/scripts/figma-sync.js)
+- [figma-sync.js](file:///c:/Users/Usuario/Desktop/Stratix/scripts/figma-sync.js)
   - What it does: Pull/push tokens to/from Figma
   - Foundation: The design ↔ code bridge you want standard
 
-- [generate-dts-from-tokens.js](file:///c:/Users/Usuario/Desktop/substrata/scripts/generate-dts-from-tokens.js)
+- [generate-dts-from-tokens.js](file:///c:/Users/Usuario/Desktop/Stratix/scripts/generate-dts-from-tokens.js)
   - What it does: Generates TypeScript definitions
   - Why core: Basic DX expected in modern libraries
 
-- [generate-tokens.js](file:///c:/Users/Usuario/Desktop/substrata/scripts/generate-tokens.js)
+- [generate-tokens.js](file:///c:/Users/Usuario/Desktop/Stratix/scripts/generate-tokens.js)
   - What it does: CSS → tokens.json
   - Foundation: Fundamental build pipeline
 
-- [lint-code.js](file:///c:/Users/Usuario/Desktop/substrata/scripts/lint-code.js)
+- [lint-code.js](file:///c:/Users/Usuario/Desktop/Stratix/scripts/lint-code.js)
   - What it does: Detects hardcoded values in code
   - Foundation: Basic linting is expected
 
-- [lint-hardcoded.js](file:///c:/Users/Usuario/Desktop/substrata/scripts/lint-hardcoded.js)
+- [lint-hardcoded.js](file:///c:/Users/Usuario/Desktop/Stratix/scripts/lint-hardcoded.js)
   - What it does: Similar, detects hardcoded values
   - Foundation: Basic quality tooling
 
-- [tokens-to-css.js](file:///c:/Users/Usuario/Desktop/substrata/scripts/tokens-to-css.js)
+- [tokens-to-css.js](file:///c:/Users/Usuario/Desktop/Stratix/scripts/tokens-to-css.js)
   - What it does: tokens.json → CSS variables
   - Foundation: The bidirectional loop you promised
 
-- [validate-tokens.js](file:///c:/Users/Usuario/Desktop/substrata/scripts/validate-tokens.js)
+- [validate-tokens.js](file:///c:/Users/Usuario/Desktop/Stratix/scripts/validate-tokens.js)
   - What it does: Validates tokens.json against schema
   - Foundation: Validation is fundamental
 
@@ -233,7 +233,7 @@ See the [**ROADMAP.md**](./ROADMAP.md) and [**ARCHITECTURE.md**](./ARCHITECTURE.
 npm run detect:breaking
 npm run sync:figma
 FIGMA_SYNC_DIRECTION=push npm run sync:figma
-FIGMA_TOKEN=... FIGMA_FILE_KEY=... npx @stratixlabs/core figma apply-preview
+FIGMA_TOKEN=... FIGMA_FILE_KEY=... npx stratix figma apply-preview
 npm run build:types
 npm run build:tokens
 npm run lint:code
@@ -247,3 +247,4 @@ npm run test:tokens
 ## License
 
 MIT © 2026 Mikael Carrara
+

package/bin/{substrata.js → stratix.js}

@@ -7,19 +7,19 @@ const args = process.argv.slice(2);
 const command = args[0];
 
 if (!command || (command !== 'init' && command !== 'generate' && command !== 'figma')) {
-    console.log('Usage: @stratixlabs/core <command>');
+    console.log('Usage: stratix <command>');
     console.log('Commands:');
-    console.log('  init      Initialize a complete Substrata project with tokens, scripts, and examples');
+    console.log('  init      Initialize a complete Stratix project with tokens, scripts, and examples');
     console.log('  generate  Generate tokens.json from source');
     console.log('  figma     Figma-related automation (sync, apply-preview)');
     process.exit(1);
 }
 
 if (command === 'init') {
-    console.log('🚀 Initializing Substrata...\n');
+    console.log('🚀 Initializing Stratix...\n');
 
     const cwd = process.cwd();
-    const configPath = path.join(cwd, 'substrata.config.js');
+    const configPath = path.join(cwd, 'stratix.config.js');
     const tokensDir = path.join(cwd, 'src/tokens');
     const consumptionDir = path.join(cwd, 'src/consumption');
     const scriptsDir = path.join(cwd, 'scripts');
@@ -27,7 +27,7 @@ if (command === 'init') {
 
     // 1. Create config file
     if (fs.existsSync(configPath)) {
-        console.log('⚠️  substrata.config.js already exists.');
+        console.log('⚠️  stratix.config.js already exists.');
     } else {
         const defaultConfig = `module.exports = {
   tokens: './src/tokens',
@@ -35,7 +35,7 @@ if (command === 'init') {
 };
 `;
         fs.writeFileSync(configPath, defaultConfig);
-        console.log('✅ Created substrata.config.js');
+        console.log('✅ Created stratix.config.js');
     }
 
     // 2. Create directory structure
@@ -217,9 +217,9 @@ if (command === 'init') {
         }
     }
 
-    // 4. Create substrata.css (imports all tokens)
-    const substrataCssPath = path.join(srcDir, 'substrata.css');
-    const substrataCss = `@import "tokens/typography.css";
+    // 4. Create stratix.css (imports all tokens)
+    const stratixCssPath = path.join(srcDir, 'stratix.css');
+    const stratixCss = `@import "tokens/typography.css";
 @import "tokens/spacing.css";
 @import "tokens/colors.css";
 @import "tokens/radius-and-borders.css";
@@ -231,10 +231,10 @@ if (command === 'init') {
 
 @import "./base.css";
 `;
-    if (!fs.existsSync(substrataCssPath)) {
+    if (!fs.existsSync(stratixCssPath)) {
         if (!fs.existsSync(srcDir)) fs.mkdirSync(srcDir, { recursive: true });
-        fs.writeFileSync(substrataCssPath, substrataCss);
-        console.log('\n✅ Created src/substrata.css');
+        fs.writeFileSync(stratixCssPath, stratixCss);
+        console.log('\n✅ Created src/stratix.css');
     }
 
     // 5. Create base.css
@@ -289,10 +289,10 @@ h4 {
     const consumptionExamples = {
         'plain.css': `/* 
   Plain CSS Consumption Example
-  Import Substrata tokens and use them directly in your styles.
+  Import Stratix tokens and use them directly in your styles.
 */
 
-@import "@stratixlabs/core/substrata.css";
+@import "@stratixlabs/core/stratix.css";
 
 .card {
   background: var(--color-surface);
@@ -317,7 +317,7 @@ h4 {
 `,
         'styled-components.js': `/* 
   CSS-in-JS Consumption Example (styled-components / emotion)
-  Use Substrata tokens in template literals via CSS variables.
+  Use Stratix tokens in template literals via CSS variables.
 */
 
 import styled from 'styled-components';
@@ -347,7 +347,7 @@ export const Button = styled.button\`
 `,
         'tailwind.config.js': `/* 
   Tailwind CSS Consumption Example
-  Map Substrata tokens to Tailwind's theme configuration.
+  Map Stratix tokens to Tailwind's theme configuration.
 */
 
 /** @type {import('tailwindcss').Config} */
@@ -461,17 +461,17 @@ module.exports = {
         }
     }
 
-    console.log('\n✨ Substrata is ready!\n');
+    console.log('\n✨ Stratix is ready!\n');
     console.log('📂 Generated structure:');
-    console.log('   ├── substrata.config.js');
+    console.log('   ├── stratix.config.js');
     console.log('   ├── src/');
     console.log('   │   ├── tokens/          (9 token files)');
     console.log('   │   ├── consumption/     (3 framework examples)');
-    console.log('   │   ├── substrata.css    (main entry point)');
+    console.log('   │   ├── stratix.css      (main entry point)');
     console.log('   │   └── base.css');
     console.log('   └── scripts/            (3 automation scripts)\n');
     console.log('▶️  Next steps:');
-    console.log('   1. Import src/substrata.css in your app');
+    console.log('   1. Import src/stratix.css in your app');
     console.log('   2. Run: npm run build:tokens');
     console.log('   3. Check src/consumption/ for framework integration examples\n');
 }
@@ -497,7 +497,7 @@ if (command === 'figma') {
     const subcommand = args[1];
 
     if (!subcommand || subcommand !== 'apply-preview') {
-        console.log('Usage: @stratixlabs/core figma <subcommand>');
+        console.log('Usage: stratix figma <subcommand>');
         console.log('Subcommands:');
         console.log('  apply-preview  Apply figma-push-preview.json to Figma via Variables REST API');
         process.exit(1);

package/package.json

@@ -1,9 +1,9 @@
 {
   "name": "@stratixlabs/core",
-  "version": "1.7.1",
+  "version": "1.7.2",
   "description": "...",
   "bin": {
-    "substrata": "bin/substrata.js"
+    "stratix": "bin/stratix.js"
   },
   "main": "index.js",
   "scripts": {
@@ -39,9 +39,9 @@
     "src",
     "index.js",
     "tokens.json",
-    "substrata.d.ts",
+    "stratix.d.ts",
     "README.md",
-    "substrata.config.js"
+    "stratix.config.js"
   ],
   "devDependencies": {
     "ajv": "^8.12.0"