diff --git a/content/docs/concepts/enterprise-framework.cn.mdx b/content/docs/concepts/enterprise-framework.cn.mdx
new file mode 100644
index 0000000..814904e
--- /dev/null
+++ b/content/docs/concepts/enterprise-framework.cn.mdx
@@ -0,0 +1,315 @@
+---
+title: 企业框架
+description: "第一阶段：代码驱动的元数据引擎 - 定义即应用"
+---
+
+# ObjectStack 企业框架
+
+**"定义即应用"**
+
+## 概述
+
+ObjectStack 企业框架代表了企业应用开发的新方法——**"面向专业开发者的元数据引擎"**。在第一阶段，我们专注于赋能开发者通过基于代码的元数据定义构建企业级应用，消除了对可视化配置界面的需求，同时保持 ObjectStack 协议生态系统的强大功能和灵活性。
+
+### 核心理念
+
+在第一阶段，我们将 ObjectStack 定义为**"面向专业开发者的企业级应用元框架"**。
+
+* **没有黑盒**: 所有的业务定义都在本地代码中，基于 TypeScript，清晰透明。
+* **Git 为中心**: 使用 Git 仓库作为唯一真理来源 (Single Source of Truth)。
+* **自带基建**: 开发者只负责写"业务描述"，框架负责"数据库迁移、API 生成、界面渲染"。
+
+---
+
+## 架构全景图
+
+企业框架围绕三个不同的层次构建，这些层次共同将基于代码的定义转换为运行中的应用程序。
+
+```mermaid
+graph TB
+    subgraph "A. 创造层：ObjectStack SDK"
+        CLI[ObjectStack CLI]
+        SDK[TypeScript SDK]
+        MetaCode[代码化元数据]
+    end
+    
+    subgraph "B. 治理层：CI/CD 流水线"
+        Extract[提取元数据]
+        Compile[编译逻辑]
+        Bundle[打包制品]
+        Version[版本控制]
+    end
+    
+    subgraph "C. 执行层：ObjectStack 内核"
+        ObjectQL[ObjectQL - 自动迁移]
+        ObjectOS[ObjectOS - 逻辑沙箱]
+        ObjectUI[ObjectUI - 渲染器 API]
+    end
+    
+    CLI --> MetaCode
+    SDK --> MetaCode
+    MetaCode --> Extract
+    Extract --> Compile
+    Compile --> Bundle
+    Bundle --> Version
+    Version --> ObjectQL
+    Version --> ObjectOS
+    Version --> ObjectUI
+```
+
+### A. 创造层：ObjectStack SDK
+
+**"在 IDE 中定义世界"**
+
+开发者不再需要登录网页后台配置，而是直接在 VS Code 或他们喜欢的 IDE 中工作。
+
+#### ObjectStack CLI
+
+命令行工具，用于快速生成代码模板和项目脚手架：
+
+* `ostack init`: 初始化标准项目结构
+* `ostack g resource contract`: 生成"合同"模块的标准目录
+* `ostack build`: 编译元数据和业务逻辑
+* `ostack dev`: 启动本地开发服务器，支持热重载
+
+#### 基于代码的元数据
+
+我们利用 **TypeScript** 的静态类型能力来定义元数据：
+
+* **Schema**: 使用类似 Zod 或 TypeORM 的语法定义数据结构
+* **Logic**: 直接编写 TS 函数作为 Trigger
+* **UI**: 使用 JSON 或 TS 对象描述界面布局（通过我们提供的类型提示）
+
+**代码示例：**
+
+```typescript
+// src/objects/contract.ts
+import { defineObject, Field } from '@objectstack/sdk';
+
+export const Contract = defineObject({
+  name: 'contract',
+  label: '销售合同',
+  fields: {
+    title: Field.String({ 
+      label: '标题', 
+      required: true,
+      maxLength: 200
+    }),
+    amount: Field.Currency({ 
+      label: '金额',
+      precision: 18,
+      scale: 2
+    }),
+    status: Field.Select({ 
+      options: ['draft', 'signed', 'cancelled'],
+      defaultValue: 'draft'
+    }),
+    signedAt: Field.DateTime({
+      label: '签署日期',
+      nullable: true
+    })
+  },
+  
+  // 触发器逻辑直接写在这里
+  triggers: {
+    beforeInsert: async ({ doc }) => {
+      if (doc.amount < 0) {
+        throw new Error("金额不能为负");
+      }
+    },
+    
+    afterUpdate: async ({ doc, oldDoc }) => {
+      if (doc.status === 'signed' && oldDoc.status !== 'signed') {
+        doc.signedAt = new Date();
+      }
+    }
+  },
+  
+  // 访问控制
+  permissions: {
+    create: ['sales', 'admin'],
+    read: ['sales', 'admin', 'viewer'],
+    update: ['sales', 'admin'],
+    delete: ['admin']
+  }
+});
+```
+
+### B. 治理层：CI/CD 流水线
+
+**"Git 仓库即控制台"**
+
+没有 Hub，**Git Repository** 就是 Hub。
+
+#### 构建时编排
+
+当代码提交时，ObjectStack 的构建工具（基于 Vite 或 Rollup）会扫描所有 `.ts` 文件：
+
+1. **Extract**: 提取其中的元数据定义（Schema/UI）
+2. **Compile**: 将后端逻辑编译为优化的 JS 包
+3. **Bundle**: 将这些打包成一个不可变的 **Artifact（制品）**
+
+```mermaid
+sequenceDiagram
+    participant Dev as 开发者
+    participant Git as Git 仓库
+    participant CI as CI 服务器
+    participant Build as 构建工具
+    participant Artifact as Docker 镜像
+    
+    Dev->>Git: git push origin main
+    Git->>CI: 触发构建
+    CI->>Build: 运行 'ostack build'
+    Build->>Build: 提取元数据
+    Build->>Build: 编译 TypeScript
+    Build->>Build: 生成迁移脚本
+    Build->>Artifact: 创建 Docker 镜像
+    Artifact->>Artifact: 打标签版本 (v1.0.0)
+```
+
+#### 版本管理
+
+* 利用 **Git Tag** 管理版本（v1.0, v1.1）
+* 利用 **Pull Request** 进行变更审批
+* 利用 **Git Branches** 进行功能开发和热修复
+
+### C. 执行层：ObjectStack 内核
+
+**"自带动力的单体引擎"**
+
+这是交付给客户的核心——一个标准的 **Docker 镜像** 或 **NPM 包**，客户将其部署在自己的服务器上。
+
+这个 Kernel 包含了统一的"三位一体"引擎：
+
+#### 1. ObjectQL（自动迁移）
+
+应用启动时，Kernel 读取打包好的 Metadata：
+
+* **自动同步 DB**: 发现 `Contract` 对象多了 `amount` 字段 → 自动对 Postgres 执行 `ALTER TABLE`
+* **自动生成 API**: 自动挂载 GraphQL/REST 端点 `/api/data/contract`
+
+#### 2. ObjectOS（逻辑沙箱）
+
+* 负责加载并执行开发者编写的 `triggers` 函数
+* 管理身份验证和授权（RBAC/ACL）
+* 处理工作流状态机
+* 编排本地优先同步
+
+#### 3. ObjectUI（渲染器 API）
+
+* 向前端（React/Vue 客户端）提供 `schema.json`
+* **Amis 集成**: 如果使用 Amis，这里直接输出 Amis 标准的 JSON 配置，前端直接渲染
+* 支持复杂 UI 的自定义 React 组件
+
+---
+
+## 落地工作流
+
+这是客户采用该方案时的标准作业流程（SOP）：
+
+| 步骤 | 角色 | 动作 | 产物 |
+|------|------|------|------|
+| **1. 初始化** | 架构师 | `npm create objectstack-app my-erp` | 包含核心依赖的 Git 仓库 |
+| **2. 开发** | 开发者 | 编写 `.ts` 文件定义对象、逻辑和界面 | 源代码 (Source Code) |
+| **3. 提交** | 开发者 | `git push origin main` | 触发 CI 构建 |
+| **4. 构建** | CI Server | 运行 `ostack build` | **Docker Image** (包含 Kernel + 业务代码) |
+| **5. 部署** | 运维 | `docker run -d my-erp:latest` | 运行中的企业应用 |
+| **6. 迭代** | 全员 | 修改代码 → Push → 自动热更新 | 持续交付 |
+
+### 详细工作流示例
+
+```mermaid
+stateDiagram-v2
+    [*] --> 初始化
+    初始化 --> 开发: ostack init
+    开发 --> 本地测试: ostack dev
+    本地测试 --> 开发: 修复问题
+    本地测试 --> 提交: 测试通过
+    提交 --> CI: git push
+    CI --> 构建: 运行流水线
+    构建 --> 部署: 创建镜像
+    部署 --> 运行中: docker run
+    运行中 --> 迭代: 新需求
+    迭代 --> 开发: 代码变更
+    运行中 --> [*]: 关闭
+```
+
+---
+
+## 商业模式与交付物
+
+在 Phase 1，你交付给客户的是一套 **"开发底座"**。
+
+### 核心交付物清单
+
+1. **`@objectstack/cli`**: 命令行工具 (NPM)
+2. **`@objectstack/core`**: 核心运行时依赖 (包含 ObjectQL/OS/UI 的逻辑)
+3. **Standard Template**: 标准的企业级项目脚手架
+4. **Documentation**: 详细的 API 文档和最佳实践指南
+
+### 卖点话术
+
+* **"不被厂商绑定"**: 代码在你们自己手里，Git 仓库在你们自己服务器上
+* **"零技术债务"**: 你们只写业务逻辑，底层脏活累活（数据库连接、API 封装、权限校验）全部由框架处理
+* **"类型安全"**: 全链路 TypeScript 支持，重构不再火葬场
+
+---
+
+## 项目结构
+
+典型的 ObjectStack 企业应用遵循以下结构：
+
+```
+my-erp/
+├── src/
+│   ├── objects/              # 业务对象定义
+│   │   ├── contract.ts
+│   │   ├── customer.ts
+│   │   └── order.ts
+│   ├── workflows/            # 状态机和流程
+│   │   └── order-approval.ts
+│   ├── permissions/          # 访问控制定义
+│   │   └── roles.ts
+│   ├── ui/                   # UI 布局和组件
+│   │   └── contract-form.json
+│   └── triggers/             # 业务逻辑钩子
+│       └── calculate-tax.ts
+├── migrations/               # 生成的数据库迁移
+├── tests/                    # 单元和集成测试
+├── objectstack.config.ts     # 框架配置
+├── package.json
+└── tsconfig.json
+```
+
+---
+
+## 与现有 ObjectStack 概念的集成
+
+企业框架建立在核心 ObjectStack 理念之上：
+
+* **协议驱动**: TypeScript 代码编译为标准 ObjectStack JSON 协议
+* **本地优先**: 生成的应用默认支持本地优先架构
+* **数据库无关**: ObjectQL 编译目标支持多种数据库后端
+
+但是，它增加了关键的开发者体验层：
+
+* **代码优先的 DX**: 开发者在熟悉的 IDE 中工作，拥有完整的 IntelliSense
+* **类型安全**: 在编译时捕获错误，而不是运行时
+* **Git 工作流**: 利用现有的基于 Git 的开发实践
+
+---
+
+## 下一步
+
+* **[SDK 参考](../specifications/sdk)**: `@objectstack/sdk` 的详细 API 文档
+* **[CLI 指南](../specifications/cli)**: 命令参考和使用示例
+* **[部署模式](../specifications/deployment)**: Docker、Kubernetes 和云部署策略
+
+:::tip 企业级准备
+ObjectStack 企业框架专为重视代码质量、版本控制和可维护性的团队而设计。它将低代码的力量带入专业开发工作流程。
+:::
+
+---
+
+**ObjectStack Enterprise Framework**  
+*Code it locally. Run it globally.*
diff --git a/content/docs/concepts/enterprise-framework.mdx b/content/docs/concepts/enterprise-framework.mdx
new file mode 100644
index 0000000..36a20e1
--- /dev/null
+++ b/content/docs/concepts/enterprise-framework.mdx
@@ -0,0 +1,316 @@
+---
+title: Enterprise Framework
+description: "Phase 1: The Code-Driven Metadata Engine - Definition is Application (定义即应用)"
+---
+
+# ObjectStack Enterprise Framework
+
+**"Definition is Application" (定义即应用)**
+
+## Overview
+
+ObjectStack Enterprise Framework represents a new approach to enterprise application development—**"A Metadata Engine for Professional Developers"**. In Phase 1, we focus on empowering developers to build enterprise-grade applications through code-based metadata definitions, eliminating the need for visual configuration interfaces while maintaining the power and flexibility of the ObjectStack protocol ecosystem.
+
+### Core Philosophy
+
+In this first phase, ObjectStack is defined as an **"Enterprise Application Meta-Framework for Professional Developers"**.
+
+* **No Black Boxes**: All business definitions exist in local code, based on TypeScript, clear and transparent.
+* **Git as the Center**: Use Git repositories as the Single Source of Truth.
+* **Built-in Infrastructure**: Developers only write "business descriptions"; the framework handles "database migrations, API generation, and UI rendering".
+
+---
+
+## The Architecture Landscape
+
+The Enterprise Framework is structured around three distinct layers that work together to transform code-based definitions into running applications.
+
+```mermaid
+graph TB
+    subgraph "A. Creator Layer: ObjectStack SDK"
+        CLI[ObjectStack CLI]
+        SDK[TypeScript SDK]
+        MetaCode[Metadata as Code]
+    end
+    
+    subgraph "B. Governance Layer: CI/CD Pipeline"
+        Extract[Extract Metadata]
+        Compile[Compile Logic]
+        Bundle[Bundle Artifact]
+        Version[Version Control]
+    end
+    
+    subgraph "C. Execution Layer: ObjectStack Kernel"
+        ObjectQL[ObjectQL - Auto-Migration]
+        ObjectOS[ObjectOS - Logic Sandbox]
+        ObjectUI[ObjectUI - Renderer API]
+    end
+    
+    CLI --> MetaCode
+    SDK --> MetaCode
+    MetaCode --> Extract
+    Extract --> Compile
+    Compile --> Bundle
+    Bundle --> Version
+    Version --> ObjectQL
+    Version --> ObjectOS
+    Version --> ObjectUI
+```
+
+### A. Creator Layer: ObjectStack SDK
+
+**"Define the World in Your IDE"**
+
+Developers no longer need to log into web-based admin consoles for configuration. Instead, they work directly in VS Code or their preferred IDE.
+
+#### ObjectStack CLI
+
+The command-line tool for rapid code generation and project scaffolding:
+
+* `ostack init`: Initialize a standard project structure
+* `ostack g resource contract`: Generate a "Contract" module with standard directory layout
+* `ostack build`: Compile metadata and business logic
+* `ostack dev`: Start local development server with hot reload
+
+#### Metadata as Code
+
+We leverage **TypeScript's** static typing capabilities to define metadata:
+
+* **Schema**: Define data structures using Zod-like or TypeORM-like syntax
+* **Logic**: Write TS functions directly as Triggers
+* **UI**: Describe interface layouts using JSON or TS objects (with full type hints)
+
+**Code Example:**
+
+```typescript
+// src/objects/contract.ts
+import { defineObject, Field } from '@objectstack/sdk';
+
+export const Contract = defineObject({
+  name: 'contract',
+  label: 'Sales Contract',
+  fields: {
+    title: Field.String({ 
+      label: 'Title', 
+      required: true,
+      maxLength: 200
+    }),
+    amount: Field.Currency({ 
+      label: 'Amount',
+      required: false,
+      precision: 18,
+      scale: 2
+    }),
+    status: Field.Select({ 
+      options: ['draft', 'signed', 'cancelled'],
+      defaultValue: 'draft'
+    }),
+    signedAt: Field.DateTime({
+      label: 'Signed Date',
+      nullable: true
+    })
+  },
+  
+  // Trigger logic written directly here
+  triggers: {
+    beforeInsert: async ({ doc }) => {
+      if (doc.amount < 0) {
+        throw new Error("Amount cannot be negative");
+      }
+    },
+    
+    afterUpdate: async ({ doc, oldDoc }) => {
+      if (doc.status === 'signed' && oldDoc.status !== 'signed') {
+        doc.signedAt = new Date();
+      }
+    }
+  },
+  
+  // Access control
+  permissions: {
+    create: ['sales', 'admin'],
+    read: ['sales', 'admin', 'viewer'],
+    update: ['sales', 'admin'],
+    delete: ['admin']
+  }
+});
+```
+
+### B. Governance Layer: CI/CD Pipeline
+
+**"Git Repository as Console"**
+
+There is no separate "Hub"—**Your Git Repository IS the Hub**.
+
+#### Build-Time Composition
+
+When code is committed, ObjectStack's build tooling (based on Vite or Rollup) scans all `.ts` files:
+
+1. **Extract**: Pull out metadata definitions (Schema/UI)
+2. **Compile**: Compile backend logic into optimized JS bundles
+3. **Bundle**: Package everything into an immutable **Artifact**
+
+```mermaid
+sequenceDiagram
+    participant Dev as Developer
+    participant Git as Git Repository
+    participant CI as CI Server
+    participant Build as Build Tool
+    participant Artifact as Docker Image
+    
+    Dev->>Git: git push origin main
+    Git->>CI: Trigger Build
+    CI->>Build: Run 'ostack build'
+    Build->>Build: Extract Metadata
+    Build->>Build: Compile TypeScript
+    Build->>Build: Generate Migrations
+    Build->>Artifact: Create Docker Image
+    Artifact->>Artifact: Tag Version (v1.0.0)
+```
+
+#### Version Management
+
+* Use **Git Tags** to manage versions (v1.0, v1.1)
+* Use **Pull Requests** for change approval and review
+* Leverage **Git Branches** for feature development and hotfixes
+
+### C. Execution Layer: ObjectStack Kernel
+
+**"Self-Powered Monolithic Engine"**
+
+This is the core delivered to customers—a standard **Docker Image** or **NPM Package** that they deploy on their own infrastructure.
+
+The Kernel contains the unified "Trinity" engine:
+
+#### 1. ObjectQL (Auto-Migration)
+
+When the application starts, the Kernel reads the packaged metadata:
+
+* **Auto-Sync Database**: Discovers the `Contract` object has a new `amount` field → Automatically executes `ALTER TABLE` on PostgreSQL
+* **Auto-Generate API**: Automatically mounts GraphQL/REST endpoints at `/api/data/contract`
+
+#### 2. ObjectOS (Logic Sandbox)
+
+* Loads and executes developer-written `triggers` functions
+* Manages authentication and authorization (RBAC/ACL)
+* Handles workflow state machines
+* Orchestrates local-first synchronization
+
+#### 3. ObjectUI (Renderer API)
+
+* Provides `schema.json` to the frontend (React/Vue client)
+* **Amis Integration**: If using Amis, directly outputs Amis-standard JSON configuration for immediate rendering
+* Supports custom React components for complex UIs
+
+---
+
+## Implementation Workflow
+
+This is the Standard Operating Procedure (SOP) for customers adopting this solution:
+
+| Step | Role | Action | Output |
+|------|------|--------|--------|
+| **1. Initialize** | Architect | `npm create objectstack-app my-erp` | Git repository with core dependencies |
+| **2. Develop** | Developer | Write `.ts` files defining objects, logic, and UI | Source Code |
+| **3. Commit** | Developer | `git push origin main` | Trigger CI build |
+| **4. Build** | CI Server | Run `ostack build` | **Docker Image** (Kernel + Business Code) |
+| **5. Deploy** | DevOps | `docker run -d my-erp:latest` | Running enterprise application |
+| **6. Iterate** | Team | Modify code → Push → Auto hot-reload | Continuous Delivery |
+
+### Detailed Workflow Example
+
+```mermaid
+stateDiagram-v2
+    [*] --> Initialize
+    Initialize --> Develop: ostack init
+    Develop --> LocalTest: ostack dev
+    LocalTest --> Develop: Fix issues
+    LocalTest --> Commit: Tests pass
+    Commit --> CI: git push
+    CI --> Build: Run pipeline
+    Build --> Deploy: Create image
+    Deploy --> Running: docker run
+    Running --> Iterate: New requirements
+    Iterate --> Develop: Code changes
+    Running --> [*]: Shutdown
+```
+
+---
+
+## Commercial Model & Deliverables
+
+In Phase 1, you deliver a **"Development Foundation"** to customers.
+
+### Core Deliverables
+
+1. **`@objectstack/cli`**: Command-line tooling (NPM package)
+2. **`@objectstack/core`**: Core runtime dependencies (includes ObjectQL/OS/UI logic)
+3. **Standard Template**: Enterprise-grade project scaffolding
+4. **Documentation**: Comprehensive API docs and best practices guide
+
+### Value Propositions
+
+* **"No Vendor Lock-in"**: Code lives in your repository, Git lives on your servers
+* **"Zero Technical Debt"**: You write business logic; the framework handles infrastructure (database connections, API wrappers, permission checks)
+* **"Type Safety"**: Full-stack TypeScript support; refactoring becomes safe and predictable
+
+---
+
+## Project Structure
+
+A typical ObjectStack Enterprise application follows this structure:
+
+```
+my-erp/
+├── src/
+│   ├── objects/              # Business object definitions
+│   │   ├── contract.ts
+│   │   ├── customer.ts
+│   │   └── order.ts
+│   ├── workflows/            # State machines and processes
+│   │   └── order-approval.ts
+│   ├── permissions/          # Access control definitions
+│   │   └── roles.ts
+│   ├── ui/                   # UI layouts and components
+│   │   └── contract-form.json
+│   └── triggers/             # Business logic hooks
+│       └── calculate-tax.ts
+├── migrations/               # Generated database migrations
+├── tests/                    # Unit and integration tests
+├── objectstack.config.ts     # Framework configuration
+├── package.json
+└── tsconfig.json
+```
+
+---
+
+## Integration with Existing ObjectStack Concepts
+
+The Enterprise Framework builds upon the core ObjectStack philosophy:
+
+* **Protocol-Driven**: The TypeScript code compiles down to standard ObjectStack JSON protocols
+* **Local-First**: The generated applications support local-first architecture by default
+* **Database-Agnostic**: ObjectQL compilation targets multiple database backends
+
+However, it adds a critical developer experience layer:
+
+* **Code-First DX**: Developers work in their familiar IDE with full IntelliSense
+* **Type Safety**: Catch errors at compile-time, not runtime
+* **Git Workflow**: Leverage existing Git-based development practices
+
+---
+
+## Next Steps
+
+* **[SDK Reference](../specifications/sdk)**: Detailed API documentation for `@objectstack/sdk`
+* **[CLI Guide](../specifications/cli)**: Command reference and usage examples
+* **[Deployment Patterns](../specifications/deployment)**: Docker, Kubernetes, and cloud deployment strategies
+
+:::tip Enterprise-Ready
+The ObjectStack Enterprise Framework is designed for teams that value code quality, version control, and maintainability. It brings the power of low-code to professional development workflows.
+:::
+
+---
+
+**ObjectStack Enterprise Framework**  
+*Code it locally. Run it globally.*
diff --git a/content/docs/concepts/meta.json b/content/docs/concepts/meta.json
index 2cccfac..4d41761 100644
--- a/content/docs/concepts/meta.json
+++ b/content/docs/concepts/meta.json
@@ -1,4 +1,4 @@
 {
   "title": "Concepts",
-  "pages": ["core-values", "architecture", "enterprise-patterns", "terminology"]
+  "pages": ["core-values", "architecture", "enterprise-framework", "enterprise-patterns", "terminology"]
 }
diff --git a/content/docs/specifications/cli/index.mdx b/content/docs/specifications/cli/index.mdx
new file mode 100644
index 0000000..fd5b032
--- /dev/null
+++ b/content/docs/specifications/cli/index.mdx
@@ -0,0 +1,698 @@
+---
+title: ObjectStack CLI
+description: Command-line interface for ObjectStack Enterprise Framework development
+---
+
+# ObjectStack CLI Specification
+
+The ObjectStack CLI (`@objectstack/cli`) is a command-line tool that streamlines enterprise application development using the ObjectStack framework. It provides scaffolding, build, development server, and deployment utilities.
+
+## Installation
+
+### Global Installation
+
+```bash
+npm install -g @objectstack/cli
+# or
+pnpm add -g @objectstack/cli
+```
+
+### Project Scaffolding
+
+Create a new ObjectStack application:
+
+```bash
+npm create objectstack-app my-erp
+# or
+pnpm create objectstack-app my-erp
+```
+
+---
+
+## Command Reference
+
+### ostack init
+
+Initialize a new ObjectStack project in the current directory.
+
+#### Usage
+
+```bash
+ostack init [options]
+```
+
+#### Options
+
+| Option | Description | Default |
+|--------|-------------|---------|
+| `--name <name>` | Project name | Current directory name |
+| `--template <template>` | Project template | `standard` |
+| `--database <db>` | Database adapter | `postgresql` |
+| `--ui <framework>` | UI framework | `react` |
+| `--git` | Initialize Git repository | `true` |
+
+#### Templates
+
+* `standard` - Full-featured enterprise template
+* `minimal` - Minimal setup with basic structure
+* `crm` - Pre-configured CRM template
+* `erp` - Pre-configured ERP template
+
+#### Example
+
+```bash
+ostack init --name my-company-erp --template erp --database postgresql
+```
+
+#### Generated Structure
+
+```
+my-company-erp/
+├── src/
+│   ├── objects/
+│   │   └── .gitkeep
+│   ├── workflows/
+│   │   └── .gitkeep
+│   ├── permissions/
+│   │   └── .gitkeep
+│   └── ui/
+│       └── .gitkeep
+├── tests/
+│   └── .gitkeep
+├── objectstack.config.ts
+├── package.json
+├── tsconfig.json
+├── .gitignore
+└── README.md
+```
+
+---
+
+### ostack generate (g)
+
+Generate boilerplate code for objects, workflows, and other components.
+
+#### Usage
+
+```bash
+ostack generate <type> <name> [options]
+# Alias
+ostack g <type> <name> [options]
+```
+
+#### Types
+
+##### Object
+
+Generate a new business object:
+
+```bash
+ostack g object contract
+# or
+ostack g resource contract
+```
+
+**Generated Files:**
+
+```
+src/
+└── objects/
+    ├── contract.ts
+    └── contract.test.ts
+```
+
+**Options:**
+
+| Option | Description |
+|--------|-------------|
+| `--fields <fields>` | Comma-separated field definitions |
+| `--with-triggers` | Include trigger template |
+| `--with-permissions` | Include permission template |
+
+**Example:**
+
+```bash
+ostack g object invoice --fields "number:String,amount:Currency,date:DateTime" --with-triggers
+```
+
+##### Workflow
+
+Generate a workflow state machine:
+
+```bash
+ostack g workflow order-approval
+```
+
+**Generated Files:**
+
+```
+src/
+└── workflows/
+    ├── order-approval.ts
+    └── order-approval.test.ts
+```
+
+##### Permission
+
+Generate a permission role definition:
+
+```bash
+ostack g permission sales-manager
+```
+
+##### UI Layout
+
+Generate a UI layout definition:
+
+```bash
+ostack g layout contract-form
+```
+
+**Generated Files:**
+
+```
+src/
+└── ui/
+    └── contract-form.json
+```
+
+##### Migration
+
+Generate a database migration file:
+
+```bash
+ostack g migration add-tax-field-to-invoice
+```
+
+**Generated Files:**
+
+```
+migrations/
+└── 20260122_add_tax_field_to_invoice.ts
+```
+
+---
+
+### ostack dev
+
+Start the development server with hot reload.
+
+#### Usage
+
+```bash
+ostack dev [options]
+```
+
+#### Options
+
+| Option | Description | Default |
+|--------|-------------|---------|
+| `--port <port>` | Server port | `3000` |
+| `--host <host>` | Server host | `localhost` |
+| `--open` | Open browser automatically | `false` |
+| `--database <url>` | Database connection URL | From config |
+| `--watch` | Watch for file changes | `true` |
+
+#### Example
+
+```bash
+ostack dev --port 8080 --open
+```
+
+#### Features
+
+* **Hot Module Replacement (HMR)**: Code changes reflect immediately
+* **Auto-Rebuild**: Recompiles metadata on file save
+* **Live Database Sync**: Schema changes auto-migrate during development
+* **Error Overlay**: Displays compilation errors in the UI
+
+---
+
+### ostack build
+
+Build the application for production deployment.
+
+#### Usage
+
+```bash
+ostack build [options]
+```
+
+#### Options
+
+| Option | Description | Default |
+|--------|-------------|---------|
+| `--output <dir>` | Output directory | `build/` |
+| `--target <target>` | Build target | `docker` |
+| `--minify` | Minify output | `true` |
+| `--sourcemap` | Generate source maps | `false` |
+
+#### Targets
+
+* `docker` - Docker image with embedded runtime
+* `npm` - NPM package for Node.js deployment
+* `static` - Static files for serverless deployment
+
+#### Example
+
+```bash
+ostack build --target docker --output ./dist
+```
+
+#### Build Process
+
+```mermaid
+graph LR
+    A[TypeScript Files] --> B[Extract Metadata]
+    B --> C[Validate Schemas]
+    C --> D[Compile Triggers]
+    D --> E[Generate Migrations]
+    E --> F[Bundle Assets]
+    F --> G[Create Artifact]
+```
+
+#### Output Structure
+
+```
+build/
+├── metadata/
+│   ├── objects/
+│   │   ├── contract.json
+│   │   └── customer.json
+│   └── workflows/
+│       └── order-approval.json
+├── triggers/
+│   ├── contract.js
+│   └── customer.js
+├── migrations/
+│   └── 001_initial_schema.sql
+├── kernel/
+│   └── objectstack-runtime.js
+├── Dockerfile
+└── manifest.json
+```
+
+---
+
+### ostack migrate
+
+Run database migrations.
+
+#### Usage
+
+```bash
+ostack migrate [command] [options]
+```
+
+#### Commands
+
+##### up
+
+Apply pending migrations:
+
+```bash
+ostack migrate up
+```
+
+**Options:**
+
+| Option | Description |
+|--------|-------------|
+| `--steps <n>` | Apply only N migrations |
+| `--to <version>` | Migrate to specific version |
+
+##### down
+
+Rollback migrations:
+
+```bash
+ostack migrate down [--steps 1]
+```
+
+##### status
+
+Check migration status:
+
+```bash
+ostack migrate status
+```
+
+**Output:**
+
+```
+┌─────────────────────────────────┬──────────┐
+│ Migration                       │ Status   │
+├─────────────────────────────────┼──────────┤
+│ 001_initial_schema              │ Applied  │
+│ 002_add_customer_fields         │ Applied  │
+│ 003_create_order_table          │ Pending  │
+└─────────────────────────────────┴──────────┘
+```
+
+##### create
+
+Create a new migration:
+
+```bash
+ostack migrate create add_tax_calculation
+```
+
+---
+
+### ostack test
+
+Run unit and integration tests.
+
+#### Usage
+
+```bash
+ostack test [pattern] [options]
+```
+
+#### Options
+
+| Option | Description | Default |
+|--------|-------------|---------|
+| `--watch` | Watch mode | `false` |
+| `--coverage` | Generate coverage report | `false` |
+| `--verbose` | Verbose output | `false` |
+
+#### Example
+
+```bash
+ostack test src/objects/contract.test.ts --coverage
+```
+
+---
+
+### ostack lint
+
+Lint TypeScript code and metadata definitions.
+
+#### Usage
+
+```bash
+ostack lint [options]
+```
+
+#### Options
+
+| Option | Description | Default |
+|--------|-------------|---------|
+| `--fix` | Auto-fix issues | `false` |
+| `--strict` | Strict mode | `false` |
+
+#### Checks
+
+* TypeScript compilation errors
+* ESLint violations
+* Metadata schema validation
+* Naming convention compliance
+* Security vulnerabilities in triggers
+
+---
+
+### ostack deploy
+
+Deploy the application to various targets.
+
+#### Usage
+
+```bash
+ostack deploy [target] [options]
+```
+
+#### Targets
+
+##### Docker
+
+```bash
+ostack deploy docker --registry ghcr.io/myorg/my-erp --tag v1.0.0
+```
+
+**Options:**
+
+| Option | Description |
+|--------|-------------|
+| `--registry <url>` | Container registry URL |
+| `--tag <tag>` | Image tag |
+| `--push` | Push to registry |
+
+##### Kubernetes
+
+```bash
+ostack deploy k8s --namespace production --replicas 3
+```
+
+**Options:**
+
+| Option | Description |
+|--------|-------------|
+| `--namespace <ns>` | Kubernetes namespace |
+| `--replicas <n>` | Number of replicas |
+| `--config <file>` | Kubernetes config file |
+
+##### Cloud
+
+```bash
+ostack deploy cloud --provider aws --region us-east-1
+```
+
+**Providers:**
+
+* `aws` - AWS ECS/Fargate
+* `gcp` - Google Cloud Run
+* `azure` - Azure Container Instances
+
+---
+
+### ostack db
+
+Database management utilities.
+
+#### Usage
+
+```bash
+ostack db <command> [options]
+```
+
+#### Commands
+
+##### seed
+
+Seed the database with sample data:
+
+```bash
+ostack db seed [--file seeds/demo-data.json]
+```
+
+##### reset
+
+Reset the database (drop all tables):
+
+```bash
+ostack db reset [--force]
+```
+
+##### export
+
+Export database schema and data:
+
+```bash
+ostack db export --output backup.sql
+```
+
+##### import
+
+Import database from file:
+
+```bash
+ostack db import --file backup.sql
+```
+
+---
+
+### ostack doctor
+
+Diagnose common issues and verify setup.
+
+#### Usage
+
+```bash
+ostack doctor
+```
+
+#### Checks
+
+* Node.js version compatibility
+* Database connectivity
+* Required dependencies installed
+* TypeScript configuration
+* File permissions
+* Port availability
+
+#### Example Output
+
+```
+ObjectStack Doctor v1.0.0
+
+✓ Node.js version (20.10.0)
+✓ TypeScript installed (5.3.3)
+✓ Database connection (postgresql://localhost:5432/mydb)
+✓ Port 3000 available
+✗ Missing dependency: @objectstack/core
+  Run: npm install @objectstack/core
+
+1 issue found. Run suggested commands to fix.
+```
+
+---
+
+## Configuration File
+
+### objectstack.config.ts
+
+```typescript
+import { defineConfig } from '@objectstack/cli';
+
+export default defineConfig({
+  // Project metadata
+  name: 'my-erp',
+  version: '1.0.0',
+  
+  // Database configuration
+  database: {
+    adapter: 'postgresql',
+    url: process.env.DATABASE_URL || 'postgresql://localhost:5432/mydb',
+    pool: {
+      min: 2,
+      max: 10
+    },
+    migrations: {
+      directory: './migrations',
+      tableName: '_migrations'
+    }
+  },
+  
+  // Build configuration
+  build: {
+    outDir: './build',
+    sourcemap: true,
+    minify: true,
+    target: 'docker'
+  },
+  
+  // Development server
+  dev: {
+    port: 3000,
+    host: 'localhost',
+    open: false,
+    hotReload: true
+  },
+  
+  // Runtime configuration
+  runtime: {
+    logLevel: 'info',
+    maxUploadSize: '10mb',
+    cors: {
+      enabled: true,
+      origins: ['http://localhost:3000']
+    }
+  },
+  
+  // Plugin system
+  plugins: [
+    // Add custom plugins
+  ]
+});
+```
+
+---
+
+## Environment Variables
+
+| Variable | Description | Default |
+|----------|-------------|---------|
+| `DATABASE_URL` | Database connection string | - |
+| `NODE_ENV` | Environment (development/production) | `development` |
+| `PORT` | Server port | `3000` |
+| `LOG_LEVEL` | Logging level | `info` |
+| `SECRET_KEY` | Encryption key for secrets | - |
+
+---
+
+## CI/CD Integration
+
+### GitHub Actions
+
+```yaml
+name: Build and Deploy
+
+on:
+  push:
+    branches: [main]
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v3
+      
+      - name: Setup Node.js
+        uses: actions/setup-node@v3
+        with:
+          node-version: 20
+      
+      - name: Install dependencies
+        run: npm ci
+      
+      - name: Run tests
+        run: ostack test --coverage
+      
+      - name: Build
+        run: ostack build --target docker
+      
+      - name: Deploy
+        run: ostack deploy docker --push
+        env:
+          DOCKER_REGISTRY: ${{ secrets.DOCKER_REGISTRY }}
+```
+
+### GitLab CI
+
+```yaml
+stages:
+  - build
+  - test
+  - deploy
+
+build:
+  stage: build
+  script:
+    - npm ci
+    - ostack build
+
+test:
+  stage: test
+  script:
+    - ostack test --coverage
+
+deploy:
+  stage: deploy
+  script:
+    - ostack deploy docker --push
+  only:
+    - main
+```
+
+---
+
+## Next Steps
+
+* **[SDK Reference](../sdk)**: Learn the ObjectStack SDK API
+* **[Deployment Guide](../deployment)**: Deploy to production
+* **[Best Practices](../../guides/best-practices)**: Development guidelines
+
+:::tip Pro Tip
+Use `ostack doctor` regularly to catch configuration issues early. Add it to your pre-commit hooks for automated checks.
+:::
diff --git a/content/docs/specifications/cli/meta.json b/content/docs/specifications/cli/meta.json
new file mode 100644
index 0000000..977fb58
--- /dev/null
+++ b/content/docs/specifications/cli/meta.json
@@ -0,0 +1,6 @@
+{
+  "title": "CLI",
+  "pages": [
+    "index"
+  ]
+}
diff --git a/content/docs/specifications/deployment/index.mdx b/content/docs/specifications/deployment/index.mdx
new file mode 100644
index 0000000..5234b6c
--- /dev/null
+++ b/content/docs/specifications/deployment/index.mdx
@@ -0,0 +1,660 @@
+---
+title: Deployment Guide
+description: Deploy ObjectStack Enterprise Framework applications to production environments
+---
+
+# Deployment Guide
+
+This guide covers deploying ObjectStack Enterprise Framework applications to various production environments, including Docker, Kubernetes, and cloud platforms.
+
+## Overview
+
+ObjectStack applications compile to a self-contained artifact that includes:
+
+* **Runtime Kernel**: ObjectQL + ObjectOS + ObjectUI engines
+* **Business Logic**: Compiled TypeScript triggers and workflows
+* **Metadata**: Object schemas, permissions, and UI definitions
+* **Migrations**: Database schema update scripts
+
+---
+
+## Deployment Targets
+
+### Docker Deployment
+
+The most common deployment method uses Docker containers.
+
+#### Building the Docker Image
+
+```bash
+ostack build --target docker
+```
+
+**Generated Dockerfile:**
+
+```dockerfile
+FROM node:20-alpine AS base
+
+WORKDIR /app
+
+# Copy built artifacts
+COPY build/ ./
+
+# Install production dependencies
+RUN npm ci --omit=dev
+
+EXPOSE 3000
+
+# Health check
+HEALTHCHECK --interval=30s --timeout=3s --start-period=5s --retries=3 \
+  CMD node healthcheck.js
+
+# Run the application
+CMD ["node", "kernel/objectstack-runtime.js"]
+```
+
+#### Building and Running
+
+```bash
+# Build the image
+docker build -t my-erp:latest .
+
+# Run locally
+docker run -d \
+  --name my-erp \
+  -p 3000:3000 \
+  -e DATABASE_URL=postgresql://user:pass@db:5432/mydb \
+  -e SECRET_KEY=your-secret-key \
+  my-erp:latest
+
+# Check logs
+docker logs -f my-erp
+
+# Stop
+docker stop my-erp
+```
+
+---
+
+### Docker Compose
+
+For multi-service deployments:
+
+**docker-compose.yml:**
+
+```yaml
+version: '3.8'
+
+services:
+  app:
+    build: .
+    ports:
+      - "3000:3000"
+    environment:
+      - DATABASE_URL=postgresql://postgres:password@db:5432/mydb
+      - REDIS_URL=redis://redis:6379
+      - NODE_ENV=production
+    depends_on:
+      - db
+      - redis
+    restart: unless-stopped
+  
+  db:
+    image: postgres:16-alpine
+    environment:
+      - POSTGRES_DB=mydb
+      - POSTGRES_USER=postgres
+      - POSTGRES_PASSWORD=password
+    volumes:
+      - postgres_data:/var/lib/postgresql/data
+    restart: unless-stopped
+  
+  redis:
+    image: redis:7-alpine
+    restart: unless-stopped
+
+volumes:
+  postgres_data:
+```
+
+**Usage:**
+
+```bash
+# Start all services
+docker-compose up -d
+
+# View logs
+docker-compose logs -f app
+
+# Scale the application
+docker-compose up -d --scale app=3
+
+# Stop all services
+docker-compose down
+```
+
+---
+
+### Kubernetes Deployment
+
+For production-grade orchestration with high availability.
+
+#### Kubernetes Manifests
+
+**deployment.yaml:**
+
+```yaml
+apiVersion: apps/v1
+kind: Deployment
+metadata:
+  name: objectstack-app
+  namespace: production
+spec:
+  replicas: 3
+  selector:
+    matchLabels:
+      app: objectstack-app
+  template:
+    metadata:
+      labels:
+        app: objectstack-app
+    spec:
+      containers:
+      - name: app
+        image: my-registry/my-erp:v1.0.0
+        ports:
+        - containerPort: 3000
+        env:
+        - name: DATABASE_URL
+          valueFrom:
+            secretKeyRef:
+              name: app-secrets
+              key: database-url
+        - name: SECRET_KEY
+          valueFrom:
+            secretKeyRef:
+              name: app-secrets
+              key: secret-key
+        - name: NODE_ENV
+          value: "production"
+        resources:
+          requests:
+            memory: "256Mi"
+            cpu: "250m"
+          limits:
+            memory: "1Gi"
+            cpu: "1000m"
+        livenessProbe:
+          httpGet:
+            path: /health
+            port: 3000
+          initialDelaySeconds: 30
+          periodSeconds: 10
+        readinessProbe:
+          httpGet:
+            path: /ready
+            port: 3000
+          initialDelaySeconds: 5
+          periodSeconds: 5
+---
+apiVersion: v1
+kind: Service
+metadata:
+  name: objectstack-app
+  namespace: production
+spec:
+  selector:
+    app: objectstack-app
+  ports:
+  - protocol: TCP
+    port: 80
+    targetPort: 3000
+  type: LoadBalancer
+---
+apiVersion: v1
+kind: Secret
+metadata:
+  name: app-secrets
+  namespace: production
+type: Opaque
+stringData:
+  database-url: "postgresql://user:pass@postgres:5432/mydb"
+  secret-key: "your-secret-key-here"
+```
+
+#### Deploy to Kubernetes
+
+```bash
+# Create namespace
+kubectl create namespace production
+
+# Apply manifests
+kubectl apply -f deployment.yaml
+
+# Check deployment status
+kubectl get deployments -n production
+kubectl get pods -n production
+
+# View logs
+kubectl logs -f -l app=objectstack-app -n production
+
+# Scale deployment
+kubectl scale deployment/objectstack-app --replicas=5 -n production
+```
+
+---
+
+### Cloud Platforms
+
+#### AWS Elastic Container Service (ECS)
+
+**Using the CLI:**
+
+```bash
+ostack deploy cloud --provider aws --region us-east-1
+```
+
+**Manual Deployment:**
+
+1. **Build and push image to ECR:**
+
+```bash
+# Authenticate to ECR
+aws ecr get-login-password --region us-east-1 | \
+  docker login --username AWS --password-stdin 123456789.dkr.ecr.us-east-1.amazonaws.com
+
+# Tag and push
+docker tag my-erp:latest 123456789.dkr.ecr.us-east-1.amazonaws.com/my-erp:latest
+docker push 123456789.dkr.ecr.us-east-1.amazonaws.com/my-erp:latest
+```
+
+2. **Create ECS Task Definition:**
+
+```json
+{
+  "family": "my-erp-task",
+  "networkMode": "awsvpc",
+  "requiresCompatibilities": ["FARGATE"],
+  "executionRoleArn": "arn:aws:iam::123456789:role/ecsTaskExecutionRole",
+  "cpu": "512",
+  "memory": "1024",
+  "containerDefinitions": [
+    {
+      "name": "app",
+      "image": "123456789.dkr.ecr.us-east-1.amazonaws.com/my-erp:latest",
+      "portMappings": [
+        {
+          "containerPort": 3000,
+          "protocol": "tcp"
+        }
+      ],
+      "environment": [
+        {"name": "NODE_ENV", "value": "production"}
+      ],
+      "secrets": [
+        {
+          "name": "DATABASE_URL",
+          "valueFrom": "arn:aws:secretsmanager:us-east-1:123456789:secret:db-url"
+        }
+      ],
+      "logConfiguration": {
+        "logDriver": "awslogs",
+        "options": {
+          "awslogs-group": "/ecs/my-erp",
+          "awslogs-region": "us-east-1",
+          "awslogs-stream-prefix": "ecs"
+        }
+      }
+    }
+  ]
+}
+```
+
+3. **Create ECS Service:**
+
+```bash
+aws ecs create-service \
+  --cluster my-cluster \
+  --service-name my-erp-service \
+  --task-definition my-erp-task \
+  --desired-count 3 \
+  --launch-type FARGATE \
+  --network-configuration "awsvpcConfiguration={subnets=[subnet-12345],securityGroups=[sg-12345]}"
+```
+
+#### Google Cloud Run
+
+```bash
+# Build and deploy in one command
+gcloud run deploy my-erp \
+  --source . \
+  --region us-central1 \
+  --platform managed \
+  --allow-unauthenticated \
+  --set-env-vars NODE_ENV=production \
+  --set-secrets DATABASE_URL=db-url:latest
+```
+
+#### Azure Container Instances
+
+```bash
+# Create resource group
+az group create --name my-erp-rg --location eastus
+
+# Deploy container
+az container create \
+  --resource-group my-erp-rg \
+  --name my-erp \
+  --image myregistry.azurecr.io/my-erp:latest \
+  --cpu 1 \
+  --memory 1 \
+  --ports 3000 \
+  --environment-variables NODE_ENV=production \
+  --secure-environment-variables DATABASE_URL=$DATABASE_URL
+```
+
+---
+
+## Database Migrations
+
+### Pre-Deployment Migration
+
+Run migrations before deploying the new version:
+
+```bash
+# Using kubectl for Kubernetes
+kubectl run migration-job \
+  --image=my-erp:v1.0.0 \
+  --restart=Never \
+  --command -- ostack migrate up
+
+# Using Docker
+docker run --rm \
+  -e DATABASE_URL=$DATABASE_URL \
+  my-erp:latest \
+  ostack migrate up
+```
+
+### Zero-Downtime Deployment
+
+Use a two-phase deployment:
+
+**Phase 1: Deploy backward-compatible schema**
+
+```bash
+# Deploy version with additive changes only
+kubectl set image deployment/objectstack-app app=my-erp:v1.1.0
+```
+
+**Phase 2: Remove deprecated fields**
+
+```bash
+# After all pods updated, run cleanup migration
+kubectl run cleanup-job --image=my-erp:v1.1.0 --command -- ostack migrate cleanup
+```
+
+---
+
+## Environment Configuration
+
+### Production Environment Variables
+
+```bash
+# Application
+NODE_ENV=production
+PORT=3000
+LOG_LEVEL=warn
+
+# Database
+DATABASE_URL=postgresql://user:password@host:5432/dbname
+DATABASE_POOL_MIN=5
+DATABASE_POOL_MAX=20
+
+# Security
+SECRET_KEY=your-strong-secret-key
+SESSION_SECRET=your-session-secret
+CORS_ORIGINS=https://app.example.com,https://admin.example.com
+
+# Features
+ENABLE_API_DOCS=false
+ENABLE_DEBUGGING=false
+MAX_UPLOAD_SIZE=10mb
+
+# Monitoring
+SENTRY_DSN=https://...
+NEWRELIC_LICENSE_KEY=...
+```
+
+### Secrets Management
+
+#### Kubernetes Secrets
+
+```bash
+# Create secret from file
+kubectl create secret generic app-secrets \
+  --from-env-file=.env.production \
+  -n production
+
+# Create from literal values
+kubectl create secret generic app-secrets \
+  --from-literal=database-url='postgresql://...' \
+  --from-literal=secret-key='...' \
+  -n production
+```
+
+#### Docker Secrets
+
+```bash
+# Create secret
+echo "postgresql://..." | docker secret create db_url -
+
+# Use in service
+docker service create \
+  --name my-erp \
+  --secret db_url \
+  my-erp:latest
+```
+
+#### Cloud Provider Secret Managers
+
+**AWS Secrets Manager:**
+
+```bash
+# Store secret
+aws secretsmanager create-secret \
+  --name my-erp/database-url \
+  --secret-string "postgresql://..."
+
+# Reference in ECS task definition
+"secrets": [
+  {
+    "name": "DATABASE_URL",
+    "valueFrom": "arn:aws:secretsmanager:region:account:secret:my-erp/database-url"
+  }
+]
+```
+
+---
+
+## Monitoring and Observability
+
+### Health Checks
+
+ObjectStack provides built-in health endpoints:
+
+* `GET /health` - Liveness probe (is the app running?)
+* `GET /ready` - Readiness probe (can the app serve traffic?)
+* `GET /metrics` - Prometheus metrics
+
+### Logging
+
+Configure structured JSON logging for production:
+
+```typescript
+// objectstack.config.ts
+export default defineConfig({
+  runtime: {
+    logLevel: 'info',
+    logFormat: 'json',
+    logDestination: 'stdout'
+  }
+});
+```
+
+### Application Performance Monitoring
+
+**Sentry Integration:**
+
+```typescript
+// objectstack.config.ts
+import * as Sentry from '@sentry/node';
+
+export default defineConfig({
+  plugins: [
+    {
+      name: 'sentry',
+      setup: () => {
+        Sentry.init({
+          dsn: process.env.SENTRY_DSN,
+          environment: process.env.NODE_ENV
+        });
+      }
+    }
+  ]
+});
+```
+
+---
+
+## CI/CD Best Practices
+
+### Deployment Checklist
+
+- [ ] Run tests in CI (`ostack test`)
+- [ ] Lint code (`ostack lint`)
+- [ ] Build Docker image
+- [ ] Push to registry with version tag
+- [ ] Run database migrations
+- [ ] Deploy to staging environment
+- [ ] Run smoke tests
+- [ ] Deploy to production (blue-green or canary)
+- [ ] Monitor metrics and logs
+- [ ] Rollback if issues detected
+
+### Blue-Green Deployment
+
+```bash
+# Deploy green environment
+kubectl apply -f deployment-green.yaml
+
+# Test green environment
+curl https://green.example.com/health
+
+# Switch traffic
+kubectl patch service my-app -p '{"spec":{"selector":{"version":"green"}}}'
+
+# Monitor for 10 minutes
+# If successful, scale down blue
+
+# If issues, rollback
+kubectl patch service my-app -p '{"spec":{"selector":{"version":"blue"}}}'
+```
+
+---
+
+## Scaling Strategies
+
+### Horizontal Scaling
+
+**Kubernetes Horizontal Pod Autoscaler:**
+
+```yaml
+apiVersion: autoscaling/v2
+kind: HorizontalPodAutoscaler
+metadata:
+  name: objectstack-app-hpa
+spec:
+  scaleTargetRef:
+    apiVersion: apps/v1
+    kind: Deployment
+    name: objectstack-app
+  minReplicas: 3
+  maxReplicas: 10
+  metrics:
+  - type: Resource
+    resource:
+      name: cpu
+      target:
+        type: Utilization
+        averageUtilization: 70
+```
+
+### Vertical Scaling
+
+Adjust resource limits based on monitoring:
+
+```yaml
+resources:
+  requests:
+    memory: "512Mi"
+    cpu: "500m"
+  limits:
+    memory: "2Gi"
+    cpu: "2000m"
+```
+
+---
+
+## Troubleshooting
+
+### Common Issues
+
+**Pod CrashLoopBackOff:**
+
+```bash
+# Check logs
+kubectl logs -f pod-name
+
+# Common causes:
+# - Missing environment variables
+# - Database connection failure
+# - Failed migrations
+```
+
+**High Memory Usage:**
+
+```bash
+# Check memory usage
+kubectl top pods
+
+# Adjust memory limits or investigate memory leaks
+```
+
+**Database Connection Pool Exhausted:**
+
+```typescript
+// Increase pool size in config
+database: {
+  pool: {
+    min: 10,
+    max: 50
+  }
+}
+```
+
+---
+
+## Next Steps
+
+* **[Security Guide](../../guides/security)**: Secure your deployment
+* **[Monitoring Guide](../../guides/monitoring)**: Set up comprehensive monitoring
+* **[Backup & Recovery](../../guides/backup)**: Data protection strategies
+
+:::warning Production Checklist
+Before going to production, ensure you have:
+- Database backups configured
+- Monitoring and alerting set up
+- SSL/TLS certificates installed
+- Secrets properly managed
+- Disaster recovery plan documented
+:::
diff --git a/content/docs/specifications/deployment/meta.json b/content/docs/specifications/deployment/meta.json
new file mode 100644
index 0000000..d89926d
--- /dev/null
+++ b/content/docs/specifications/deployment/meta.json
@@ -0,0 +1,6 @@
+{
+  "title": "Deployment",
+  "pages": [
+    "index"
+  ]
+}
diff --git a/content/docs/specifications/meta.json b/content/docs/specifications/meta.json
index 6dba7d2..d20bbca 100644
--- a/content/docs/specifications/meta.json
+++ b/content/docs/specifications/meta.json
@@ -1,6 +1,9 @@
 {
   "title": "Specifications",
   "pages": [
+    "sdk",
+    "cli",
+    "deployment",
     "objectql",
     "objectui",
     "objectos"
diff --git a/content/docs/specifications/sdk/index.mdx b/content/docs/specifications/sdk/index.mdx
new file mode 100644
index 0000000..8965795
--- /dev/null
+++ b/content/docs/specifications/sdk/index.mdx
@@ -0,0 +1,609 @@
+---
+title: ObjectStack SDK
+description: TypeScript SDK for defining business objects, logic, and metadata as code
+---
+
+# ObjectStack SDK Specification
+
+The ObjectStack SDK (`@objectstack/sdk`) is a TypeScript library that enables developers to define enterprise application metadata through code. It provides a type-safe, IntelliSense-enabled API for defining data schemas, business logic, permissions, and UI layouts.
+
+## Philosophy
+
+The SDK embodies the principle of **"Metadata as Code"**:
+
+* **Type Safety**: Leverage TypeScript's type system to catch errors at compile time
+* **Developer Experience**: Full IntelliSense support in modern IDEs
+* **Version Control**: All metadata is stored as code in Git repositories
+* **Composability**: Build complex applications from simple, reusable definitions
+
+---
+
+## Installation
+
+```bash
+npm install @objectstack/sdk
+# or
+pnpm add @objectstack/sdk
+# or
+yarn add @objectstack/sdk
+```
+
+---
+
+## Core API
+
+### defineObject
+
+The primary API for defining business objects (entities).
+
+#### TypeScript Interface
+
+```typescript
+interface ObjectDefinition {
+  name: string;                    // Unique identifier (snake_case)
+  label: string;                   // Human-readable display name
+  pluralLabel?: string;            // Plural form for UI
+  description?: string;            // Documentation
+  fields: Record<string, FieldDefinition>;
+  triggers?: TriggerDefinitions;
+  permissions?: PermissionDefinitions;
+  indexes?: IndexDefinition[];
+  validations?: ValidationRule[];
+}
+
+function defineObject(definition: ObjectDefinition): ObjectMetadata;
+```
+
+#### Example
+
+```typescript
+import { defineObject, Field } from '@objectstack/sdk';
+
+export const Customer = defineObject({
+  name: 'customer',
+  label: 'Customer',
+  pluralLabel: 'Customers',
+  description: 'Enterprise customer records',
+  
+  fields: {
+    name: Field.String({ 
+      label: 'Company Name',
+      required: true,
+      maxLength: 200,
+      searchable: true
+    }),
+    
+    email: Field.Email({
+      label: 'Primary Email',
+      required: true,
+      unique: true
+    }),
+    
+    industry: Field.Select({
+      label: 'Industry',
+      options: ['Technology', 'Finance', 'Healthcare', 'Retail'],
+      nullable: true
+    }),
+    
+    revenue: Field.Currency({
+      label: 'Annual Revenue',
+      precision: 18,
+      scale: 2,
+      nullable: true
+    }),
+    
+    isActive: Field.Boolean({
+      label: 'Active',
+      defaultValue: true
+    }),
+    
+    createdAt: Field.DateTime({
+      label: 'Created Date',
+      autoCreateTime: true
+    })
+  }
+});
+```
+
+---
+
+## Field Types
+
+The SDK provides a comprehensive set of field type constructors.
+
+### Primitive Types
+
+#### String
+
+```typescript
+Field.String(options: {
+  label: string;
+  required?: boolean;
+  minLength?: number;
+  maxLength?: number;
+  pattern?: RegExp | string;
+  defaultValue?: string;
+  searchable?: boolean;      // Enable full-text search
+  encrypted?: boolean;        // Store encrypted in DB
+})
+```
+
+#### Number
+
+```typescript
+Field.Number(options: {
+  label: string;
+  required?: boolean;
+  min?: number;
+  max?: number;
+  precision?: number;         // Total digits
+  scale?: number;             // Decimal places
+  defaultValue?: number;
+})
+```
+
+#### Boolean
+
+```typescript
+Field.Boolean(options: {
+  label: string;
+  required?: boolean;
+  defaultValue?: boolean;
+})
+```
+
+### Semantic Types
+
+#### Email
+
+```typescript
+Field.Email(options: {
+  label: string;
+  required?: boolean;
+  unique?: boolean;
+  verificationRequired?: boolean;
+})
+```
+
+#### Currency
+
+```typescript
+Field.Currency(options: {
+  label: string;
+  required?: boolean;
+  precision?: number;         // Default: 18
+  scale?: number;             // Default: 2
+  currency?: string;          // ISO code (USD, EUR, etc.)
+})
+```
+
+#### DateTime
+
+```typescript
+Field.DateTime(options: {
+  label: string;
+  required?: boolean;
+  nullable?: boolean;
+  defaultValue?: Date | 'now';
+  autoCreateTime?: boolean;   // Set on insert
+  autoUpdateTime?: boolean;   // Set on update
+  timezone?: 'UTC' | 'local';
+})
+```
+
+### Relational Types
+
+#### Reference (Foreign Key)
+
+```typescript
+Field.Reference(options: {
+  label: string;
+  referenceTo: string;        // Target object name
+  required?: boolean;
+  onDelete?: 'cascade' | 'set_null' | 'restrict';
+  displayField?: string;      // Which field to show in UI
+})
+```
+
+**Example:**
+
+```typescript
+fields: {
+  account: Field.Reference({
+    label: 'Account',
+    referenceTo: 'account',
+    required: true,
+    onDelete: 'restrict'
+  })
+}
+```
+
+#### MasterDetail (Parent-Child)
+
+```typescript
+Field.MasterDetail(options: {
+  label: string;
+  referenceTo: string;
+  required?: boolean;
+  cascade?: boolean;          // Delete children when parent deleted
+})
+```
+
+### Compound Types
+
+#### Select (Picklist)
+
+```typescript
+Field.Select(options: {
+  label: string;
+  options: string[] | { label: string; value: string }[];
+  required?: boolean;
+  defaultValue?: string;
+  nullable?: boolean;
+})
+```
+
+#### MultiSelect
+
+```typescript
+Field.MultiSelect(options: {
+  label: string;
+  options: string[] | { label: string; value: string }[];
+  maxSelections?: number;
+})
+```
+
+#### JSON
+
+```typescript
+Field.JSON(options: {
+  label: string;
+  schema?: JSONSchema;        // Optional JSON Schema for validation
+  encrypted?: boolean;
+})
+```
+
+---
+
+## Triggers (Business Logic Hooks)
+
+Triggers define business logic that executes automatically during data lifecycle events.
+
+### Trigger Types
+
+```typescript
+interface TriggerDefinitions {
+  beforeInsert?: TriggerFunction;
+  afterInsert?: TriggerFunction;
+  beforeUpdate?: TriggerFunction;
+  afterUpdate?: TriggerFunction;
+  beforeDelete?: TriggerFunction;
+  afterDelete?: TriggerFunction;
+}
+
+type TriggerFunction = (context: TriggerContext) => Promise<void> | void;
+
+interface TriggerContext {
+  doc: Record<string, any>;        // Current document
+  oldDoc?: Record<string, any>;    // Previous state (update/delete only)
+  user: UserContext;               // Current user
+  transaction: Transaction;        // DB transaction for atomic operations
+  objectQL: ObjectQLClient;        // Query other objects
+}
+```
+
+### Example
+
+```typescript
+export const Order = defineObject({
+  name: 'order',
+  label: 'Order',
+  
+  fields: {
+    totalAmount: Field.Currency({ label: 'Total' }),
+    status: Field.Select({ 
+      options: ['draft', 'submitted', 'approved', 'cancelled'] 
+    }),
+    approvedAt: Field.DateTime({ nullable: true }),
+    approvedBy: Field.Reference({ 
+      referenceTo: 'user', 
+      nullable: true 
+    })
+  },
+  
+  triggers: {
+    beforeInsert: async ({ doc }) => {
+      // Validate business rules
+      if (doc.totalAmount < 0) {
+        throw new Error('Total amount cannot be negative');
+      }
+      
+      // Auto-set defaults
+      if (!doc.status) {
+        doc.status = 'draft';
+      }
+    },
+    
+    afterUpdate: async ({ doc, oldDoc, user, transaction }) => {
+      // Track approval
+      if (doc.status === 'approved' && oldDoc.status !== 'approved') {
+        doc.approvedAt = new Date();
+        doc.approvedBy = user.id;
+        
+        // Create audit log
+        await transaction.insert('audit_log', {
+          objectType: 'order',
+          recordId: doc.id,
+          action: 'approved',
+          userId: user.id,
+          timestamp: new Date()
+        });
+      }
+    },
+    
+    beforeDelete: async ({ doc }) => {
+      // Prevent deletion of approved orders
+      if (doc.status === 'approved') {
+        throw new Error('Cannot delete approved orders');
+      }
+    }
+  }
+});
+```
+
+---
+
+## Permissions
+
+Define role-based access control (RBAC) at the object and field level.
+
+### Permission Structure
+
+```typescript
+interface PermissionDefinitions {
+  create?: string[] | PermissionRule;
+  read?: string[] | PermissionRule;
+  update?: string[] | PermissionRule;
+  delete?: string[] | PermissionRule;
+  fieldPermissions?: Record<string, FieldPermission>;
+}
+
+interface PermissionRule {
+  roles?: string[];
+  condition?: string;           // Expression evaluated at runtime
+}
+
+interface FieldPermission {
+  read?: string[] | PermissionRule;
+  edit?: string[] | PermissionRule;
+}
+```
+
+### Example
+
+```typescript
+export const Employee = defineObject({
+  name: 'employee',
+  label: 'Employee',
+  
+  fields: {
+    name: Field.String({ label: 'Name' }),
+    email: Field.Email({ label: 'Email' }),
+    salary: Field.Currency({ label: 'Salary' }),
+    department: Field.String({ label: 'Department' })
+  },
+  
+  permissions: {
+    create: ['hr_manager', 'admin'],
+    read: ['employee', 'hr_manager', 'admin'],
+    update: ['hr_manager', 'admin'],
+    delete: ['admin'],
+    
+    fieldPermissions: {
+      salary: {
+        read: ['hr_manager', 'admin'],
+        edit: ['hr_manager', 'admin']
+      }
+    }
+  }
+});
+```
+
+---
+
+## Indexes
+
+Define database indexes for query optimization.
+
+```typescript
+interface IndexDefinition {
+  name?: string;
+  fields: string[];
+  unique?: boolean;
+  type?: 'btree' | 'hash' | 'gin' | 'gist';
+}
+```
+
+### Example
+
+```typescript
+export const Product = defineObject({
+  name: 'product',
+  label: 'Product',
+  
+  fields: {
+    sku: Field.String({ label: 'SKU' }),
+    name: Field.String({ label: 'Name' }),
+    category: Field.String({ label: 'Category' }),
+    price: Field.Currency({ label: 'Price' })
+  },
+  
+  indexes: [
+    {
+      name: 'idx_product_sku',
+      fields: ['sku'],
+      unique: true
+    },
+    {
+      name: 'idx_product_category',
+      fields: ['category', 'price']
+    }
+  ]
+});
+```
+
+---
+
+## Validation Rules
+
+Define cross-field validation rules that run before saving data.
+
+```typescript
+interface ValidationRule {
+  name: string;
+  condition: string | ValidationFunction;
+  message: string;
+  level?: 'error' | 'warning';
+}
+
+type ValidationFunction = (doc: Record<string, any>) => boolean;
+```
+
+### Example
+
+```typescript
+export const Invoice = defineObject({
+  name: 'invoice',
+  label: 'Invoice',
+  
+  fields: {
+    startDate: Field.DateTime({ label: 'Start Date' }),
+    endDate: Field.DateTime({ label: 'End Date' }),
+    amount: Field.Currency({ label: 'Amount' }),
+    discount: Field.Currency({ label: 'Discount' })
+  },
+  
+  validations: [
+    {
+      name: 'date_range',
+      condition: (doc) => doc.endDate > doc.startDate,
+      message: 'End date must be after start date',
+      level: 'error'
+    },
+    {
+      name: 'discount_limit',
+      condition: (doc) => doc.discount <= doc.amount * 0.3,
+      message: 'Discount cannot exceed 30% of amount',
+      level: 'error'
+    }
+  ]
+});
+```
+
+---
+
+## Compilation & Runtime
+
+### Build Process
+
+When you run `ostack build`, the SDK:
+
+1. **Scans** all TypeScript files in `src/objects/`
+2. **Extracts** metadata from `defineObject()` calls
+3. **Validates** the definitions against the schema
+4. **Generates** ObjectQL protocol JSON files
+5. **Compiles** TypeScript trigger functions to JavaScript
+6. **Bundles** everything into a deployable artifact
+
+### Generated Output
+
+```
+build/
+├── metadata/
+│   ├── customer.json       # ObjectQL schema
+│   ├── order.json
+│   └── product.json
+├── triggers/
+│   ├── customer.js         # Compiled trigger functions
+│   ├── order.js
+│   └── product.js
+└── manifest.json           # Complete application manifest
+```
+
+---
+
+## Type Safety
+
+The SDK provides full TypeScript type inference:
+
+```typescript
+// The SDK knows the shape of your object
+const customer = Customer.create({
+  name: 'Acme Corp',          // ✓ Type-safe
+  email: 'contact@acme.com',  // ✓ Type-safe
+  revenue: 1000000,           // ✓ Type-safe
+  // age: 25                  // ✗ Error: Property doesn't exist
+});
+
+// IntelliSense for field names
+Customer.fields.name          // ✓ Autocomplete works
+Customer.fields.email         // ✓ Autocomplete works
+// Customer.fields.age        // ✗ Error: Property doesn't exist
+```
+
+---
+
+## Advanced Patterns
+
+### Composition
+
+```typescript
+// Base definition
+const AuditFields = {
+  createdAt: Field.DateTime({ autoCreateTime: true }),
+  createdBy: Field.Reference({ referenceTo: 'user' }),
+  updatedAt: Field.DateTime({ autoUpdateTime: true }),
+  updatedBy: Field.Reference({ referenceTo: 'user' })
+};
+
+// Reuse in multiple objects
+export const Contract = defineObject({
+  name: 'contract',
+  fields: {
+    title: Field.String({ label: 'Title' }),
+    ...AuditFields
+  }
+});
+```
+
+### Inheritance (Planned)
+
+```typescript
+const BaseObject = defineObject({
+  name: 'base',
+  fields: {
+    id: Field.UUID({ primary: true }),
+    ...AuditFields
+  }
+});
+
+export const CustomObject = defineObject({
+  extends: BaseObject,
+  name: 'custom',
+  fields: {
+    customField: Field.String({ label: 'Custom' })
+  }
+});
+```
+
+---
+
+## Next Steps
+
+* **[CLI Reference](./cli)**: Learn how to use the ObjectStack CLI
+* **[Deployment Guide](./deployment)**: Deploy your application
+* **[Migration Guide](./migrations)**: Handle database schema changes
+
+:::tip Best Practice
+Keep your object definitions small and focused. Create separate files for each business object and organize them by domain (e.g., `src/objects/sales/`, `src/objects/inventory/`).
+:::
diff --git a/content/docs/specifications/sdk/meta.json b/content/docs/specifications/sdk/meta.json
new file mode 100644
index 0000000..e5b509f
--- /dev/null
+++ b/content/docs/specifications/sdk/meta.json
@@ -0,0 +1,6 @@
+{
+  "title": "SDK",
+  "pages": [
+    "index"
+  ]
+}