From 4633c9e90ff017ccbeaabef02d1c15cf5074b93a Mon Sep 17 00:00:00 2001
From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com>
Date: Thu, 15 Jan 2026 02:55:05 +0000
Subject: [PATCH 1/7] Initial plan


From 3ed856d11bf2a72abe00f2e2e90dcf217eab28b9 Mon Sep 17 00:00:00 2001
From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com>
Date: Thu, 15 Jan 2026 03:21:30 +0000
Subject: [PATCH 2/7] Remove UI-related packages, commands, and documentation

Co-authored-by: hotlong <50353452+hotlong@users.noreply.github.com>
---
 docs/guide/architecture/overview.md           |   34 -
 docs/guide/architecture/why-objectql.md       |   54 -
 docs/guide/cli.md                             |  258 ----
 docs/guide/configuration.md                   |   44 -
 docs/guide/data-modeling.md                   |  154 ---
 docs/guide/drivers/extensibility.md           |  178 ---
 .../drivers/implementing-custom-driver.md     |  552 ---------
 docs/guide/drivers/index.md                   |   62 -
 docs/guide/drivers/mongo.md                   |  154 ---
 docs/guide/drivers/sql.md                     |  127 --
 docs/guide/formulas-and-rules-quick-ref.md    |  275 -----
 docs/guide/formulas-and-rules.md              |  690 -----------
 docs/guide/getting-started.md                 |  158 ---
 docs/guide/ide-setup.md                       |   24 -
 docs/guide/index.md                           |   69 --
 docs/guide/license.md                         |   64 -
 docs/guide/logic-actions.md                   |  199 ----
 docs/guide/logic-hooks.md                     |  184 ---
 docs/guide/metadata-organization.md           |  365 ------
 docs/guide/microservices.md                   |   61 -
 docs/guide/migration-id-field.md              |  294 -----
 docs/guide/page-metadata.md                   |  671 -----------
 docs/guide/plugins.md                         |  249 ----
 docs/guide/querying.md                        |  195 ---
 docs/guide/server-integration.md              |  114 --
 docs/spec/form.md                             | 1046 -----------------
 docs/spec/menu.md                             |  771 ------------
 docs/spec/page.md                             |  467 --------
 docs/spec/report.md                           |  789 -------------
 docs/spec/view.md                             |  416 -------
 examples/browser/README.md                    |  154 ---
 examples/browser/example-node.ts              |   86 --
 examples/browser/index.html                   |  519 --------
 package.json                                  |    1 -
 packages/foundation/core/src/ai-agent.ts      |   46 +-
 packages/runtime/server/src/index.ts          |    1 -
 packages/runtime/server/src/studio.ts         |  164 ---
 packages/tools/cli/package.json               |    1 -
 packages/tools/cli/src/commands/ai.ts         |    7 +-
 packages/tools/cli/src/commands/new.ts        |   52 -
 packages/tools/cli/src/commands/studio.ts     |  354 ------
 packages/tools/cli/src/index.ts               |   17 -
 packages/tools/studio/CHANGELOG.md            |   89 --
 packages/tools/studio/README.md               |   47 -
 packages/tools/studio/index.html              |   12 -
 packages/tools/studio/package.json            |   47 -
 packages/tools/studio/postcss.config.cjs      |    6 -
 packages/tools/studio/src/App.css             |  308 -----
 packages/tools/studio/src/App.tsx             |   36 -
 .../tools/studio/src/components/DataGrid.tsx  |  227 ----
 .../studio/src/components/FileEditor.tsx      |   95 --
 .../studio/src/components/ObjectList.tsx      |  137 ---
 .../studio/src/components/RecordDetail.tsx    |  229 ----
 .../studio/src/components/SchemaInspector.tsx |  207 ----
 .../tools/studio/src/components/Sidebar.tsx   |  128 --
 .../tools/studio/src/components/ui/button.tsx |   60 -
 .../tools/studio/src/components/ui/card.tsx   |   76 --
 .../tools/studio/src/hooks/use-metadata.ts    |   39 -
 packages/tools/studio/src/index.css           |   59 -
 packages/tools/studio/src/lib/utils.ts        |    6 -
 packages/tools/studio/src/main.tsx            |   10 -
 packages/tools/studio/src/pages/Dashboard.tsx |   36 -
 .../studio/src/pages/MetadataBrowser.tsx      |  214 ----
 .../tools/studio/src/pages/ObjectView.tsx     |  264 -----
 .../tools/studio/src/pages/SchemaEditor.tsx   |   85 --
 packages/tools/studio/tailwind.config.cjs     |   77 --
 packages/tools/studio/tsconfig.json           |   25 -
 packages/tools/studio/vite.config.ts          |   26 -
 68 files changed, 13 insertions(+), 12652 deletions(-)
 delete mode 100644 docs/guide/architecture/overview.md
 delete mode 100644 docs/guide/architecture/why-objectql.md
 delete mode 100644 docs/guide/cli.md
 delete mode 100644 docs/guide/configuration.md
 delete mode 100644 docs/guide/data-modeling.md
 delete mode 100644 docs/guide/drivers/extensibility.md
 delete mode 100644 docs/guide/drivers/implementing-custom-driver.md
 delete mode 100644 docs/guide/drivers/index.md
 delete mode 100644 docs/guide/drivers/mongo.md
 delete mode 100644 docs/guide/drivers/sql.md
 delete mode 100644 docs/guide/formulas-and-rules-quick-ref.md
 delete mode 100644 docs/guide/formulas-and-rules.md
 delete mode 100644 docs/guide/getting-started.md
 delete mode 100644 docs/guide/ide-setup.md
 delete mode 100644 docs/guide/index.md
 delete mode 100644 docs/guide/license.md
 delete mode 100644 docs/guide/logic-actions.md
 delete mode 100644 docs/guide/logic-hooks.md
 delete mode 100644 docs/guide/metadata-organization.md
 delete mode 100644 docs/guide/microservices.md
 delete mode 100644 docs/guide/migration-id-field.md
 delete mode 100644 docs/guide/page-metadata.md
 delete mode 100644 docs/guide/plugins.md
 delete mode 100644 docs/guide/querying.md
 delete mode 100644 docs/guide/server-integration.md
 delete mode 100644 docs/spec/form.md
 delete mode 100644 docs/spec/menu.md
 delete mode 100644 docs/spec/page.md
 delete mode 100644 docs/spec/report.md
 delete mode 100644 docs/spec/view.md
 delete mode 100644 examples/browser/README.md
 delete mode 100644 examples/browser/example-node.ts
 delete mode 100644 examples/browser/index.html
 delete mode 100644 packages/runtime/server/src/studio.ts
 delete mode 100644 packages/tools/cli/src/commands/studio.ts
 delete mode 100644 packages/tools/studio/CHANGELOG.md
 delete mode 100644 packages/tools/studio/README.md
 delete mode 100644 packages/tools/studio/index.html
 delete mode 100644 packages/tools/studio/package.json
 delete mode 100644 packages/tools/studio/postcss.config.cjs
 delete mode 100644 packages/tools/studio/src/App.css
 delete mode 100644 packages/tools/studio/src/App.tsx
 delete mode 100644 packages/tools/studio/src/components/DataGrid.tsx
 delete mode 100644 packages/tools/studio/src/components/FileEditor.tsx
 delete mode 100644 packages/tools/studio/src/components/ObjectList.tsx
 delete mode 100644 packages/tools/studio/src/components/RecordDetail.tsx
 delete mode 100644 packages/tools/studio/src/components/SchemaInspector.tsx
 delete mode 100644 packages/tools/studio/src/components/Sidebar.tsx
 delete mode 100644 packages/tools/studio/src/components/ui/button.tsx
 delete mode 100644 packages/tools/studio/src/components/ui/card.tsx
 delete mode 100644 packages/tools/studio/src/hooks/use-metadata.ts
 delete mode 100644 packages/tools/studio/src/index.css
 delete mode 100644 packages/tools/studio/src/lib/utils.ts
 delete mode 100644 packages/tools/studio/src/main.tsx
 delete mode 100644 packages/tools/studio/src/pages/Dashboard.tsx
 delete mode 100644 packages/tools/studio/src/pages/MetadataBrowser.tsx
 delete mode 100644 packages/tools/studio/src/pages/ObjectView.tsx
 delete mode 100644 packages/tools/studio/src/pages/SchemaEditor.tsx
 delete mode 100644 packages/tools/studio/tailwind.config.cjs
 delete mode 100644 packages/tools/studio/tsconfig.json
 delete mode 100644 packages/tools/studio/vite.config.ts

diff --git a/docs/guide/architecture/overview.md b/docs/guide/architecture/overview.md
deleted file mode 100644
index c6d750a8..00000000
--- a/docs/guide/architecture/overview.md
+++ /dev/null
@@ -1,34 +0,0 @@
-# Architecture & Concepts
-
-ObjectQL is built with a modular architecture that separates the data definition (Metadata) from the execution engine (Driver). This design allows applications to run on different database stacks (SQL vs NoSQL) without changing the business logic.
-
-## High-Level Overview
-
-An ObjectQL application consists of three main layers:
-
-1.  **Metadata Layer**: JSON/YAML files that define the shape of your data (`.object.yml`) and operations.
-2.  **Core Engine**: The `ObjectQL` class that loads metadata, validates requests, and orchestrates execution.
-3.  **Driver Layer**: Adapters that translate ObjectQL requests into database-specific queries (SQL, Mongo Protocol, etc.).
-
-## Dependency Graph
-
-The project is structured as a monorepo with strict dependency rules to ensure scalability and maintainability.
-
-*   **`@objectql/types`**: The shared contract. Contains all interfaces (`ObjectConfig`, `ObjectQLDriver`). Has **zero dependencies**.
-*   **`@objectql/core`**: The main runtime. It depends on `types`.
-*   **`@objectql/driver-*`**: Database adapters. They implement interfaces from `types` but do **not** depend on `core` (avoiding circular dependencies).
-
-## Core Concepts
-
-### 1. Metadata-First
-In traditional ORMs (like TypeORM or Prisma), you define classes/schema in code. In ObjectQL, the schema is data itself. This allows:
-*   Dynamic schema generation at runtime.
-*   Building "No-Code" table designers.
-*   Hot-reloading of data structure without recompiling.
-
-### 2. Universal Protocol
-ObjectQL uses a unified JSON-based query language (AST). This allows frontends, AI agents, or external systems to send complex queries (`filters`, `expand`, `aggregates`) in a safe, serializable format.
-
-### 3. Logic: Actions & Hooks
-*   **Hooks**: Intercept standard CRUD operations (e.g., "Before Create", "After Update") to enforce business rules.
-*   **Actions**: Define custom RPC methods (e.g., "Approve Invoice") exposed via the API.
diff --git a/docs/guide/architecture/why-objectql.md b/docs/guide/architecture/why-objectql.md
deleted file mode 100644
index d6af4b7a..00000000
--- a/docs/guide/architecture/why-objectql.md
+++ /dev/null
@@ -1,54 +0,0 @@
-# Why ObjectQL?
-
-In the era of AI automation, the requirements for backend infrastructure have shifted. We are no longer just building for human users on web forms; we are building systems that **AI Agents** need to read, understand, and manipulate.
-
-## The Problem with Traditional ORMs
-
-Tools like TypeORM, Prisma, or Sequelize are fantastic for human developers. They rely heavily on:
-1.  **Complex TypeScript Types**: Great for IDE autocomplete, but invisible to an LLM running in a production execution environment.
-2.  **Chained Method Calls**: `db.users.where(...).include(...)`. This requires the AI to synthesize valid executable code, which is prone to syntax errors and hallucinations.
-3.  **Code-First Schema**: The schema is buried in class definitions, making it hard to extract a simple "map" of the data for the AI context window.
-
-## The ObjectQL Solution: Protocol-First
-
-ObjectQL treats **Logic as Data**.
-
-### 1. Schema is JSON (The Context)
-Instead of parsing TypeScript files, an AI Agent can simply read a JSON definition. This is the native tongue of LLMs.
-
-```json
-{
-  "name": "contact",
-  "fields": { "email": { "type": "text", "required": true } }
-}
-```
-
-This compact format fits perfectly in RAG (Retrieval-Augmented Generation) contexts.
-
-### 2. Queries are ASTs (The Action)
-To fetch data, the AI doesn't need to write SQL or function code. It generates a JSON object (Abstract Syntax Tree).
-
-```json
-{
-  "op": "find",
-  "from": "contact",
-  "filters": [["email", "contains", "@gmail.com"]]
-}
-```
-*   **Safe**: No SQL Injection possible. The Driver handles escaping.
-*   **Deterministic**: It either parses or it fails. No subtle logic bugs from misplaced parentheses in code.
-*   **Portability**: The same JSON runs on Mongo, Postgres, or a REST API.
-
-## Comparison
-
-| Feature | Traditional ORM | ObjectQL |
-| :--- | :--- | :--- |
-| **Schema Definition** | TypeScript Classes / Migration Files | JSON / YAML Metadata |
-| **Query Language** | Fluent API / Raw SQL | JSON AST |
-| **Runtime** | Node.js / Python Runtime | Universal Protocol (Any Language) |
-| **AI Friendliness** | Low (Requires Code Gen) | High (Requires JSON Gen) |
-| **Dynamic Fields** | Hard (Migration required) | Native (Metadata-driven) |
-
-## Conclusion
-
-If you are building a Copilot, an Autonomous Agent, or a Low-Code platform, ObjectQL provides the structured, safe, and descriptive layer that connects your LLM to your database.
diff --git a/docs/guide/cli.md b/docs/guide/cli.md
deleted file mode 100644
index b5f13237..00000000
--- a/docs/guide/cli.md
+++ /dev/null
@@ -1,258 +0,0 @@
-# CLI Guide
-
-The ObjectQL CLI (`@objectql/cli`) is an essential tool for development, automating tasks like type generation and database migrations.
-
-## 1. Installation
-
-The CLI is typically installed as a dev dependency in your project.
-
-```bash
-npm install -D @objectql/cli
-```
-
-You can then run it via `npx objectql` or add scripts to your `package.json`.
-
-## 2. Core Commands
-
-### 2.1 `init` (Create Project)
-
-Create a new ObjectQL project from a starter template.
-
-```bash
-npx objectql init [options]
-```
-
-**Options:**
-
-| Option | Alias | Default | Description |
-| :--- | :--- | :--- | :--- |
-| `--template <template>` | `-t` | `basic` | Template to use (`basic`, `express-api`, `enterprise`). |
-| `--name <name>` | `-n` | - | Project name. |
-| `--dir <path>` | `-d` | - | Target directory. |
-| `--skip-install` | | `false` | Skip dependency installation. |
-| `--skip-git` | | `false` | Skip git initialization. |
-
-**Example:**
-
-```bash
-npx objectql init -t express-api -n my-app
-```
-
-### 2.2 `generate` (Type Generation)
-
-Scans your `*.object.yml` files and generates TypeScript interfaces. This is crucial for maintaining type safety in your Hooks and Actions.
-**Alias**: `g`
-
-```bash
-npx objectql generate [options]
-```
-
-**Options:**
-
-| Option | Alias | Default | Description |
-| :--- | :--- | :--- | :--- |
-| `--source <path>` | `-s` | `.` | Root directory to search for object files. |
-| `--output <path>` | `-o` | `./src/generated` | Directory where `.ts` files will be generated. |
-
-**Example:**
-
-```bash
-# Generate types from /src/objects to /src/types
-npx objectql generate --source ./src/objects --output ./src/types
-```
-
-### 2.3 `new` (Scaffold Metadata)
-
-Generate a new metadata file (Object, View, Form, etc.) in the project.
-
-```bash
-npx objectql new <type> <name> [options]
-```
-
-**Arguments:**
-*   `<type>`: The type of metadata to generate (e.g., `object`, `view`, `page`).
-*   `<name>`: The name of the file/entity.
-
-**Options:**
-
-| Option | Alias | Default | Description |
-| :--- | :--- | :--- | :--- |
-| `--dir <path>` | `-d` | `.` | Output directory. |
-
-**Example:**
-```bash
-npx objectql new object customer
-```
-
-## 3. Development Tools
-
-### 3.1 `serve` (Dev Server)
-
-Start a standalone development server.
-**Alias**: `s`
-
-```bash
-npx objectql serve [options]
-```
-
-**Options:**
-
-| Option | Alias | Default | Description |
-| :--- | :--- | :--- | :--- |
-| `--port <number>` | `-p` | `3000` | Port to listen on. |
-| `--dir <path>` | `-d` | `.` | Directory containing schema. |
-
-### 3.2 `studio` (Admin UI)
-
-Starts the web-based admin studio to browse data and view schema.
-**Alias**: `ui`
-
-```bash
-npx objectql studio [options]
-```
-
-**Options:**
-
-| Option | Alias | Default | Description |
-| :--- | :--- | :--- | :--- |
-| `--port <number>` | `-p` | `3000` | Port to listen on. |
-| `--dir <path>` | `-d` | `.` | Directory containing schema. |
-| `--no-open` | | `false` | Do not open the browser automatically. |
-
-### 3.3 `repl` (Interactive Shell)
-
-Starts an interactive terminal similar to the MongoDB shell, allowing you to directly query your database using the ObjectQL API.
-**Alias**: `r`
-
-```bash
-npx objectql repl [options]
-```
-
-**Options:**
-
-| Option | Alias | Default | Description |
-| :--- | :--- | :--- | :--- |
-| `--config <path>` | `-c` | - | Path to `objectql.config.ts/js`. |
-
-**Example Session:**
-
-```javascript
-objectql> await tasks.find({ status: 'todo' })
-[ { id: 1, title: 'Fix bug', status: 'todo' } ]
-```
-
-## 4. Internationalization (i18n)
-
-Tools for managing translations.
-
-### 4.1 `i18n extract`
-
-Extract translatable strings from metadata files into JSON.
-
-```bash
-npx objectql i18n extract [options]
-```
-
-**Options:**
-
-| Option | Alias | Default | Description |
-| :--- | :--- | :--- | :--- |
-| `--source <path>` | `-s` | `.` | Source directory to scan. |
-| `--output <path>` | `-o` | `./src/i18n` | Output directory for translation files. |
-| `--lang <lang>` | `-l` | `en` | Language code. |
-
-### 4.2 `i18n init`
-
-Initialize i18n structure for a new language.
-
-```bash
-npx objectql i18n init <lang> [options]
-```
-
-**Options:**
-
-| Option | Alias | Default | Description |
-| :--- | :--- | :--- | :--- |
-| `--base-dir <path>` | `-b` | `./src/i18n` | Base i18n directory. |
-
-### 4.3 `i18n validate`
-
-Validate translation completeness against a base language.
-
-```bash
-npx objectql i18n validate <lang> [options]
-```
-
-**Options:**
-
-| Option | Alias | Default | Description |
-| :--- | :--- | :--- | :--- |
-| `--base-dir <path>` | `-b` | `./src/i18n` | Base i18n directory. |
-| `--base-lang <lang>` | | `en` | Base language to compare against. |
-
-## 5. Database Migration
-
-Manage database schema changes.
-
-### 5.1 `migrate`
-
-Run pending database migrations.
-
-```bash
-npx objectql migrate [options]
-```
-
-**Options:**
-
-| Option | Alias | Default | Description |
-| :--- | :--- | :--- | :--- |
-| `--config <path>` | `-c` | - | Path to `objectql.config.ts/js`. |
-| `--dir <path>` | `-d` | `./migrations` | Migrations directory. |
-
-### 5.2 `migrate create`
-
-Create a new migration file.
-
-```bash
-npx objectql migrate create <name> [options]
-```
-
-**Options:**
-
-| Option | Alias | Default | Description |
-| :--- | :--- | :--- | :--- |
-| `--dir <path>` | `-d` | `./migrations` | Migrations directory. |
-
-### 5.3 `migrate status`
-
-Show the status of migrations (applied/pending).
-
-```bash
-npx objectql migrate status [options]
-```
-
-**Options:**
-
-| Option | Alias | Default | Description |
-| :--- | :--- | :--- | :--- |
-| `--config <path>` | `-c` | - | Path to `objectql.config.ts/js`. |
-| `--dir <path>` | `-d` | `./migrations` | Migrations directory. |
-
-## 6. Integration with Workflow
-
-We recommend adding the CLI commands to your lifecycle scripts.
-
-**package.json:**
-
-```json
-{
-  "scripts": {
-    "codegen": "objectql generate -s ./src -o ./src/generated",
-    "build": "npm run codegen && tsc",
-    "dev": "npm run codegen && ts-node src/index.ts",
-    "studio": "objectql studio"
-  }
-}
-```
-
-This ensures that whenever you build or start your app, your TypeScript types are perfectly synced with your YAML definitions.
diff --git a/docs/guide/configuration.md b/docs/guide/configuration.md
deleted file mode 100644
index 68d26ecb..00000000
--- a/docs/guide/configuration.md
+++ /dev/null
@@ -1,44 +0,0 @@
-# Configuration
-
-ObjectQL is configured by passing an `ObjectQLConfig` object to the constructor.
-
-## Basic Layout
-
-```typescript
-// objectql.config.ts
-import { ObjectQL } from '@objectql/core';
-
-export const db = new ObjectQL({
-    connection: 'sqlite://data.db', // 1. Infrastructure
-    presets: ['@objectql/preset-auth'], // 2. Base Capabilities
-    source: ['src'], // 3. Application Logic
-    plugins: [] // 4. Extensions
-});
-```
-
-## Reference
-
-### `connection` (string)
-The Connection String URI defining the database connection.
-*   `sqlite://path/to/db`
-*   `postgres://user:pass@host:5432/db`
-*   `mongodb://host:27017/db`
-
-The engine will automatically load the appropriate driver (`@objectql/driver-sql` or `@objectql/driver-mongo`).
-
-### `source` (string | string[])
-One or more directory paths (relative or absolute) containing your schema files (`*.object.yml`).
-The loader scans these directories recursively.
-
-### `presets` (string[])
-A list of NPM packages to load as presets.
-ObjectQL will try to resolve the package and load schema files from its directory.
-Useful for sharing common business objects (User, Role, File, etc.).
-
-### `plugins` ((ObjectQLPlugin | string)[])
-A list of plugin instances OR package names to extend the core functionality.
-See [Plugin System](./plugins.html) for details.
-
-### `objects` (Record<string, ObjectConfig>)
-(Advanced) In-memory definition of objects. Useful for dynamic runtime schema generation.
-Objects defined here take highest priority.
diff --git a/docs/guide/data-modeling.md b/docs/guide/data-modeling.md
deleted file mode 100644
index 39b36186..00000000
--- a/docs/guide/data-modeling.md
+++ /dev/null
@@ -1,154 +0,0 @@
-# Data Modeling Guide
-
-Data modeling in ObjectQL is **Metadata-First**. You define your application's schema using `*.object.yml` files (or JSON), and ObjectQL handles validation, database mapping, and type generation.
-
-## 1. The Object Definition
-
-**ObjectQL uses filename-based identification.** The object name is automatically inferred from the filename (without the `.object.yml` extension), eliminating redundancy.
-
-**File naming:** `<object_name>.object.yml`
-
-```yaml
-# File: product.object.yml
-# Object name "product" is automatically inferred from filename!
-
-label: Product
-description: "Catalog items for sale"
-icon: standard:product
-
-fields:
-  name:
-    type: text
-    required: true
-    label: Product Name
-  
-  price:
-    type: currency
-    scale: 2
-    label: Price
-    
-  category:
-    type: select
-    options:
-      - electronics
-      - furniture
-      - clothing
-```
-
-**Note:** The redundant `name: product` property is no longer needed - it's automatically inferred from the filename!
-
-## 2. Fields & Relationships
-
-ObjectQL supports rich field types that automate UI rendering and validation.
-
-### Core Types
-*   **Text**: `text`, `textarea`, `markdown`, `html`
-*   **Numbers**: `number`, `currency`, `percent`
-*   **Flags**: `boolean`
-*   **Media**: `image`, `file`, `avatar`
-
-### Relationships
-*   **Lookup**: A loose foreign key. Can be optional.
-    ```yaml
-    created_by: { type: lookup, reference_to: user }
-    ```
-*   **Master-Detail**: A strong parent-child bond. Deleting the parent cascades to the child.
-    ```yaml
-    order_id: { type: master_detail, reference_to: order }
-    ```
-
-### Specialized Types
-*   **Vector**: Stores embeddings (arrays of floats) for AI search.
-    ```yaml
-    embedding: { type: vector, dimension: 1536, index: true }
-    ```
-
-## 3. Indexes & Constraints
-
-Optimize query performance and ensure data integrity.
-
-### Field-Level Shortcuts
-Use these for simple, single-column definitions.
-
-```yaml
-fields:
-  sku:
-    type: text
-    unique: true  # Enforce uniqueness
-  
-  status:
-    type: select
-    index: true   # Speed up filters
-```
-
-### Composite Indexes
-Define these at the root of your object file for multi-column optimizations (e.g., sorting by Date within a Category).
-
-```yaml
-indexes:
-  category_date_idx:
-    fields: [category, created_at]
-  
-  unique_product_variant:
-    fields: [product_id, color, size]
-    unique: true
-```
-
-## 4. Internationalization (i18n)
-
-ObjectQL adopts a "clean schema, external translation" philosophy.
-
-*   **Schema**: Keep `*.object.yml` clean and technical (usually English keys/labels).
-*   **Metadata Translations**: Store UI labels in `i18n/[lang]/[object].json`.
-*   **Data Translations**: If you need to translate record content (like a Product Name), we recommend modeling it explicitly (e.g., a `ProductTranslation` table) rather than complicating the core column types.
-
-## 5. Extending Objects
-
-ObjectQL supports a powerful **Schema Merging** capability. This allows you to extend or modify objects defined in external packages (like plugins or standard libraries) without touching their source code.
-
-This mechanism works by defining a new `.object.yml` file with the **same object name**.
-
-### How it works
-
-When ObjectQL loads schemas, if it encounters multiple definitions for the same object (e.g., `user`), it merges them together. The priority depends on the loading order (usually Application layer overrides Package/Plugin layer).
-
-### Example: Extending the User Object
-
-Suppose a plugin defines a basic `user` object. You want to add a `phone` field and enforce that `email` is required.
-
-**Original Definition (in Plugin):**
-```yaml
-# node_modules/@objectql/plugin-auth/user.object.yml
-name: user
-fields:
-  name: { type: text }
-  email: { type: text }
-```
-
-**Your Extension (in App):**
-```yaml
-# src/objects/user-extension.object.yml
-name: user                 # Must match exactly
-label: System User (Ext)   # Overrides the label
-
-fields:
-  # 1. Modify existing field
-  email:
-    required: true
-
-  # 2. Add new field
-  phone:
-    type: text
-    label: Mobile Phone
-    unique: true
-```
-
-### Merge Rules
-
-| Component | Behavior |
-| :--- | :--- |
-| **Top-level Props** | **Override**. (`label`, `icon`, `description` in your file replace the original). |
-| **Fields** | **Deep Merge**. Existing fields are updated (properties merged), new fields are added. |
-| **Actions** | **Merge**. You can add new actions or override existing ones. |
-| **Indexes** | **Merge**. New indexes are added. |
-
diff --git a/docs/guide/drivers/extensibility.md b/docs/guide/drivers/extensibility.md
deleted file mode 100644
index 0be72d14..00000000
--- a/docs/guide/drivers/extensibility.md
+++ /dev/null
@@ -1,178 +0,0 @@
-# Driver Extensibility Guide
-
-ObjectQL is designed to support multiple database backends through its **Driver** abstraction layer. This guide explains how to extend ObjectQL with additional database types.
-
-## Current Official Drivers
-
-ObjectQL currently provides official support for:
-
-| Driver | Package | Databases Supported | Status |
-|--------|---------|---------------------|--------|
-| **SQL Driver** | `@objectql/driver-sql` | PostgreSQL, MySQL, SQLite, SQL Server | ✅ Production Ready |
-| **MongoDB Driver** | `@objectql/driver-mongo` | MongoDB 4.0+ | ✅ Production Ready |
-| **SDK/Remote Driver** | `@objectql/sdk` | HTTP-based ObjectQL servers | ✅ Production Ready |
-
-## Potential Database Types for Extension
-
-ObjectQL's Driver interface can theoretically support any database system. Here are common database types that could be implemented:
-
-### Key-Value Stores
-
-| Database | Use Case | Implementation Complexity |
-|----------|----------|--------------------------|
-| **Redis** | Caching, real-time data, pub/sub | 🟢 Low - Simple key-value operations |
-| **Memcached** | Distributed caching | 🟢 Low - Basic get/set operations |
-| **etcd** | Configuration management, service discovery | 🟡 Medium - Hierarchical keys |
-
-### Document Databases
-
-| Database | Use Case | Implementation Complexity |
-|----------|----------|--------------------------|
-| **CouchDB** | Multi-master replication, offline-first | 🟡 Medium - Similar to MongoDB |
-| **Firebase/Firestore** | Real-time sync, mobile apps | 🟡 Medium - Cloud-native features |
-| **RavenDB** | .NET integration, ACID transactions | 🟡 Medium - Advanced indexing |
-
-### Wide Column Stores
-
-| Database | Use Case | Implementation Complexity |
-|----------|----------|--------------------------|
-| **Cassandra** | High availability, time-series data | 🔴 High - Distributed architecture |
-| **HBase** | Hadoop ecosystem, big data | 🔴 High - Complex data model |
-| **DynamoDB** | AWS-native, serverless | 🟡 Medium - Single-table design patterns |
-
-### Search Engines
-
-| Database | Use Case | Implementation Complexity |
-|----------|----------|--------------------------|
-| **Elasticsearch** | Full-text search, analytics | 🟡 Medium - Query DSL mapping |
-| **OpenSearch** | Fork of Elasticsearch, AWS managed | 🟡 Medium - Similar to Elasticsearch |
-| **Algolia** | Hosted search, real-time indexing | 🟢 Low - REST API based |
-| **Meilisearch** | Typo-tolerant search | 🟢 Low - Simple REST API |
-
-### Graph Databases
-
-| Database | Use Case | Implementation Complexity |
-|----------|----------|--------------------------|
-| **Neo4j** | Social networks, recommendation engines | 🔴 High - Cypher query language |
-| **ArangoDB** | Multi-model (graph + document) | 🟡 Medium - AQL query language |
-| **OrientDB** | Multi-model graph database | 🟡 Medium - SQL-like syntax |
-
-### Time-Series Databases
-
-| Database | Use Case | Implementation Complexity |
-|----------|----------|--------------------------|
-| **InfluxDB** | Metrics, IoT, monitoring | 🟡 Medium - Time-based queries |
-| **TimescaleDB** | PostgreSQL extension for time-series | 🟢 Low - SQL compatible |
-| **Prometheus** | Monitoring and alerting | 🟡 Medium - PromQL query language |
-
-### NewSQL Databases
-
-| Database | Use Case | Implementation Complexity |
-|----------|----------|--------------------------|
-| **CockroachDB** | Distributed SQL, PostgreSQL compatible | 🟢 Low - PostgreSQL protocol |
-| **TiDB** | MySQL compatible, horizontal scaling | 🟢 Low - MySQL protocol |
-| **YugabyteDB** | PostgreSQL compatible, cloud-native | 🟢 Low - PostgreSQL protocol |
-
-### Cloud-Native Databases
-
-| Database | Use Case | Implementation Complexity |
-|----------|----------|--------------------------|
-| **AWS DynamoDB** | Serverless, auto-scaling | 🟡 Medium - NoSQL patterns |
-| **Google Cloud Firestore** | Real-time sync, mobile | 🟡 Medium - Document-based |
-| **Azure Cosmos DB** | Multi-model, global distribution | 🟡 Medium - Multiple APIs |
-| **Supabase** | PostgreSQL-as-a-service | 🟢 Low - PostgreSQL protocol |
-| **PlanetScale** | MySQL-compatible, serverless | 🟢 Low - MySQL protocol |
-
-### Columnar Databases
-
-| Database | Use Case | Implementation Complexity |
-|----------|----------|--------------------------|
-| **ClickHouse** | OLAP, analytics, data warehousing | 🔴 High - Column-oriented queries |
-| **Apache Druid** | Real-time analytics | 🔴 High - Complex aggregations |
-
-### Embedded Databases
-
-| Database | Use Case | Implementation Complexity |
-|----------|----------|--------------------------|
-| **LevelDB** | Embedded key-value store | 🟢 Low - Simple operations |
-| **RocksDB** | High-performance embedded DB | 🟢 Low - LevelDB-compatible |
-| **LMDB** | Memory-mapped key-value store | 🟢 Low - Fast read operations |
-
-## Implementation Complexity Guide
-
-- 🟢 **Low Complexity** (1-2 weeks): Database has SQL compatibility or simple REST API, straightforward query mapping
-- 🟡 **Medium Complexity** (3-6 weeks): Custom query language, moderate feature mapping required
-- 🔴 **High Complexity** (2-3 months): Distributed systems, complex data models, significant architectural differences
-
-## Choosing a Database to Implement
-
-When deciding which database to add support for, consider:
-
-### 1. **Use Case Alignment**
-- Does the database solve a specific problem for ObjectQL users?
-- Does it complement existing drivers?
-
-### 2. **Community Demand**
-- Is there active interest in this database?
-- Are there existing GitHub issues requesting it?
-
-### 3. **Technical Feasibility**
-- How well does the database's data model map to ObjectQL's abstraction?
-- Does it support required operations (CRUD, filters, sorting)?
-
-### 4. **Maintenance Burden**
-- Is the database actively maintained?
-- Does it have a stable API?
-- Is there good documentation?
-
-### 5. **Ecosystem Maturity**
-- Are there quality Node.js/TypeScript clients?
-- Is the client library actively maintained?
-
-## Recommended First Extensions
-
-Based on community needs and implementation complexity, we recommend prioritizing:
-
-1. **Redis Driver** - High demand, simple implementation, excellent for caching
-2. **Elasticsearch Driver** - Popular for search features, clear use case
-3. **DynamoDB Driver** - AWS ecosystem, serverless applications
-4. **ClickHouse Driver** - Analytics and reporting use cases
-
-## Getting Started
-
-To implement a custom driver:
-
-1. Review the [Driver Implementation Guide](./implementing-custom-driver.md)
-2. Study existing driver implementations:
-   - [`@objectql/driver-sql`](../../../packages/drivers/sql/src/index.ts) - SQL databases
-   - [`@objectql/driver-mongo`](../../../packages/drivers/mongo/src/index.ts) - MongoDB
-3. Review the [Driver Interface](../../../packages/foundation/types/src/driver.ts)
-4. Follow the [Driver Testing Guide](./testing-drivers.md) (coming soon)
-
-## Community Drivers
-
-We encourage the community to create and maintain third-party drivers for additional databases. If you've implemented a driver, please:
-
-1. Follow the ObjectQL driver conventions
-2. Include comprehensive tests
-3. Document configuration and usage
-4. Submit a PR to add your driver to this list
-
-### Publishing Community Drivers
-
-Name your package following the convention: `@your-org/objectql-driver-<database>`
-
-Example: `@acme/objectql-driver-redis`
-
-## Need Help?
-
-- 📖 Read the [Driver Implementation Guide](./implementing-custom-driver.md)
-- 💬 Join the [ObjectQL Discord](https://discord.gg/objectql) (if available)
-- 🐛 [Open a GitHub Issue](https://github.com/objectstack-ai/objectql/issues)
-- 📧 Contact the maintainers
-
-## Related Documentation
-
-- [SQL Driver Documentation](./sql.md)
-- [MongoDB Driver Documentation](./mongo.md)
-- [Driver Interface Reference](../../../packages/foundation/types/src/driver.ts)
diff --git a/docs/guide/drivers/implementing-custom-driver.md b/docs/guide/drivers/implementing-custom-driver.md
deleted file mode 100644
index 212d0135..00000000
--- a/docs/guide/drivers/implementing-custom-driver.md
+++ /dev/null
@@ -1,552 +0,0 @@
-# Implementing a Custom Driver
-
-This guide walks you through implementing a custom database driver for ObjectQL. By the end, you'll understand how to create a driver that seamlessly integrates with ObjectQL's universal data protocol.
-
-## Table of Contents
-
-1. [Understanding the Driver Interface](#understanding-the-driver-interface)
-2. [Implementation Steps](#implementation-steps)
-3. [Best Practices](#best-practices)
-4. [Testing Your Driver](#testing-your-driver)
-5. [Example: Redis Driver](#example-redis-driver)
-
-## Understanding the Driver Interface
-
-All ObjectQL drivers implement the `Driver` interface defined in `@objectql/types/src/driver.ts`:
-
-```typescript
-export interface Driver {
-    // Basic CRUD Operations
-    find(objectName: string, query: any, options?: any): Promise<any[]>;
-    findOne(objectName: string, id: string | number, query?: any, options?: any): Promise<any>;
-    create(objectName: string, data: any, options?: any): Promise<any>;
-    update(objectName: string, id: string | number, data: any, options?: any): Promise<any>;
-    delete(objectName: string, id: string | number, options?: any): Promise<any>;
-    count(objectName: string, filters: any, options?: any): Promise<number>;
-    
-    // Schema / Lifecycle (Optional)
-    init?(objects: any[]): Promise<void>;
-    introspectSchema?(): Promise<IntrospectedSchema>;
-    
-    // Advanced Operations (Optional)
-    aggregate?(objectName: string, query: any, options?: any): Promise<any>;
-    distinct?(objectName: string, field: string, filters?: any, options?: any): Promise<any[]>;
-    
-    // Bulk / Atomic Operations (Optional)
-    createMany?(objectName: string, data: any[], options?: any): Promise<any>;
-    updateMany?(objectName: string, filters: any, data: any, options?: any): Promise<any>;
-    deleteMany?(objectName: string, filters: any, options?: any): Promise<any>;
-    findOneAndUpdate?(objectName: string, filters: any, update: any, options?: any): Promise<any>;
-    
-    // Transaction Support (Optional)
-    beginTransaction?(): Promise<any>;
-    commitTransaction?(trx: any): Promise<void>;
-    rollbackTransaction?(trx: any): Promise<void>;
-    
-    // Connection Management (Optional)
-    disconnect?(): Promise<void>;
-}
-```
-
-### Required Methods
-
-These methods **must** be implemented:
-
-- `find()` - Query multiple records
-- `findOne()` - Get a single record by ID
-- `create()` - Create a new record
-- `update()` - Update an existing record
-- `delete()` - Delete a record
-- `count()` - Count records matching filters
-
-### Optional Methods
-
-These methods enhance functionality but are not required:
-
-- `init()` - Initialize database schema
-- `introspectSchema()` - Read existing database schema
-- `aggregate()` - Perform aggregation operations
-- `distinct()` - Get distinct values
-- `createMany()`, `updateMany()`, `deleteMany()` - Bulk operations
-- `beginTransaction()`, `commitTransaction()`, `rollbackTransaction()` - Transaction support
-- `disconnect()` - Clean up resources
-
-## Implementation Steps
-
-### Step 1: Set Up the Package
-
-Create a new package in `packages/drivers/<driver-name>/`:
-
-```bash
-mkdir -p packages/drivers/redis
-cd packages/drivers/redis
-```
-
-Create `package.json`:
-
-```json
-{
-  "name": "@objectql/driver-redis",
-  "version": "1.0.0",
-  "description": "Redis driver for ObjectQL",
-  "main": "dist/index.js",
-  "types": "dist/index.d.ts",
-  "scripts": {
-    "build": "tsc",
-    "test": "jest"
-  },
-  "dependencies": {
-    "@objectql/types": "workspace:*",
-    "redis": "^4.6.0"
-  },
-  "devDependencies": {
-    "typescript": "^5.0.0",
-    "jest": "^29.0.0",
-    "@types/jest": "^29.0.0"
-  }
-}
-```
-
-Create `tsconfig.json`:
-
-```json
-{
-  "extends": "../../../tsconfig.base.json",
-  "compilerOptions": {
-    "outDir": "./dist",
-    "rootDir": "./src"
-  },
-  "include": ["src/**/*"]
-}
-```
-
-### Step 2: Create the Driver Class
-
-Create `src/index.ts`:
-
-```typescript
-import { Driver } from '@objectql/types';
-import { createClient, RedisClientType } from 'redis';
-
-export class RedisDriver implements Driver {
-    private client: RedisClientType;
-    private config: any;
-    private connected: Promise<void>;
-
-    constructor(config: { url: string }) {
-        this.config = config;
-        this.client = createClient({ url: config.url });
-        this.connected = this.connect();
-    }
-
-    private async connect(): Promise<void> {
-        await this.client.connect();
-    }
-
-    // Implement required methods...
-}
-```
-
-### Step 3: Implement Core CRUD Methods
-
-#### `find()`
-
-The `find()` method must handle:
-- **Filters**: Array of filter conditions
-- **Sorting**: Sort order specifications
-- **Pagination**: `skip` and `limit`
-- **Field Projection**: `fields` array
-
-```typescript
-async find(objectName: string, query: any, options?: any): Promise<any[]> {
-    await this.connected;
-    
-    // Get all keys for this object type
-    const pattern = `${objectName}:*`;
-    const keys = await this.client.keys(pattern);
-    
-    // Retrieve all documents
-    let results: any[] = [];
-    for (const key of keys) {
-        const data = await this.client.get(key);
-        if (data) {
-            const doc = JSON.parse(data);
-            results.push(doc);
-        }
-    }
-    
-    // Apply filters
-    if (query.filters) {
-        results = this.applyFilters(results, query.filters);
-    }
-    
-    // Apply sorting
-    if (query.sort) {
-        results = this.applySort(results, query.sort);
-    }
-    
-    // Apply pagination
-    if (query.skip) {
-        results = results.slice(query.skip);
-    }
-    if (query.limit) {
-        results = results.slice(0, query.limit);
-    }
-    
-    // Apply field projection
-    if (query.fields) {
-        results = results.map(doc => this.projectFields(doc, query.fields));
-    }
-    
-    return results;
-}
-```
-
-#### `findOne()`
-
-```typescript
-async findOne(objectName: string, id: string | number, query?: any, options?: any): Promise<any> {
-    await this.connected;
-    
-    const key = `${objectName}:${id}`;
-    const data = await this.client.get(key);
-    
-    if (!data) {
-        return null;
-    }
-    
-    return JSON.parse(data);
-}
-```
-
-#### `create()`
-
-```typescript
-async create(objectName: string, data: any, options?: any): Promise<any> {
-    await this.connected;
-    
-    // Generate ID if not provided
-    const id = data.id || this.generateId();
-    const doc = {
-        ...data,
-        id,
-        created_at: new Date().toISOString(),
-        updated_at: new Date().toISOString()
-    };
-    
-    const key = `${objectName}:${id}`;
-    await this.client.set(key, JSON.stringify(doc));
-    
-    return doc;
-}
-```
-
-#### `update()`
-
-```typescript
-async update(objectName: string, id: string | number, data: any, options?: any): Promise<any> {
-    await this.connected;
-    
-    const key = `${objectName}:${id}`;
-    const existing = await this.client.get(key);
-    
-    if (!existing) {
-        throw new Error(`Record not found: ${objectName}:${id}`);
-    }
-    
-    const doc = {
-        ...JSON.parse(existing),
-        ...data,
-        id,
-        updated_at: new Date().toISOString()
-    };
-    
-    await this.client.set(key, JSON.stringify(doc));
-    
-    return doc;
-}
-```
-
-#### `delete()`
-
-```typescript
-async delete(objectName: string, id: string | number, options?: any): Promise<any> {
-    await this.connected;
-    
-    const key = `${objectName}:${id}`;
-    const result = await this.client.del(key);
-    
-    return result > 0;
-}
-```
-
-#### `count()`
-
-```typescript
-async count(objectName: string, filters: any, options?: any): Promise<number> {
-    await this.connected;
-    
-    const pattern = `${objectName}:*`;
-    const keys = await this.client.keys(pattern);
-    
-    if (!filters) {
-        return keys.length;
-    }
-    
-    // Count only records matching filters
-    let count = 0;
-    for (const key of keys) {
-        const data = await this.client.get(key);
-        if (data) {
-            const doc = JSON.parse(data);
-            if (this.matchesFilters(doc, filters)) {
-                count++;
-            }
-        }
-    }
-    
-    return count;
-}
-```
-
-### Step 4: Implement Filter Logic
-
-ObjectQL uses a universal filter format:
-
-```typescript
-// Example filters:
-[
-  ['name', '=', 'John'],           // Simple equality
-  'or',                            // Logical operator
-  ['age', '>', 25],                // Comparison
-  'and',
-  ['status', 'in', ['active', 'pending']]  // IN operator
-]
-```
-
-Implement filter matching:
-
-```typescript
-private applyFilters(records: any[], filters: any[]): any[] {
-    return records.filter(record => this.matchesFilters(record, filters));
-}
-
-private matchesFilters(record: any, filters: any[]): boolean {
-    if (!filters || filters.length === 0) {
-        return true;
-    }
-    
-    let result = true;
-    let nextJoin = 'and';
-    
-    for (const item of filters) {
-        if (typeof item === 'string') {
-            // Logical operator
-            nextJoin = item.toLowerCase();
-            continue;
-        }
-        
-        if (Array.isArray(item)) {
-            const [field, operator, value] = item;
-            const matches = this.evaluateCondition(record[field], operator, value);
-            
-            if (nextJoin === 'and') {
-                result = result && matches;
-            } else {
-                result = result || matches;
-            }
-            
-            nextJoin = 'and'; // Reset to default
-        }
-    }
-    
-    return result;
-}
-
-private evaluateCondition(fieldValue: any, operator: string, compareValue: any): boolean {
-    switch (operator) {
-        case '=':
-            return fieldValue === compareValue;
-        case '!=':
-            return fieldValue !== compareValue;
-        case '>':
-            return fieldValue > compareValue;
-        case '>=':
-            return fieldValue >= compareValue;
-        case '<':
-            return fieldValue < compareValue;
-        case '<=':
-            return fieldValue <= compareValue;
-        case 'in':
-            return Array.isArray(compareValue) && compareValue.includes(fieldValue);
-        case 'nin':
-            return Array.isArray(compareValue) && !compareValue.includes(fieldValue);
-        case 'contains':
-            return String(fieldValue).includes(String(compareValue));
-        default:
-            return false;
-    }
-}
-```
-
-### Step 5: Implement Sorting
-
-```typescript
-private applySort(records: any[], sort: any[]): any[] {
-    const sorted = [...records];
-    
-    // Apply sorts in reverse order for correct precedence
-    for (let i = sort.length - 1; i >= 0; i--) {
-        const [field, direction] = Array.isArray(sort[i]) 
-            ? sort[i] 
-            : [sort[i].field, sort[i].order || 'asc'];
-        
-        sorted.sort((a, b) => {
-            const aVal = a[field];
-            const bVal = b[field];
-            
-            if (aVal < bVal) return direction === 'asc' ? -1 : 1;
-            if (aVal > bVal) return direction === 'asc' ? 1 : -1;
-            return 0;
-        });
-    }
-    
-    return sorted;
-}
-```
-
-### Step 6: Add Cleanup
-
-```typescript
-async disconnect(): Promise<void> {
-    await this.client.quit();
-}
-```
-
-### Step 7: Add Helper Methods
-
-```typescript
-private generateId(): string {
-    // Simple UUID v4 generation
-    return 'xxxxxxxx-xxxx-4xxx-yxxx-xxxxxxxxxxxx'.replace(/[xy]/g, (c) => {
-        const r = Math.random() * 16 | 0;
-        const v = c === 'x' ? r : (r & 0x3 | 0x8);
-        return v.toString(16);
-    });
-}
-
-private projectFields(doc: any, fields: string[]): any {
-    const result: any = {};
-    for (const field of fields) {
-        if (doc[field] !== undefined) {
-            result[field] = doc[field];
-        }
-    }
-    return result;
-}
-```
-
-## Best Practices
-
-### 1. **Consistent ID Handling**
-
-- Use `id` as the primary key field name (not `_id`)
-- Support both string and number IDs
-- Auto-generate IDs when not provided
-
-### 2. **Error Handling**
-
-```typescript
-import { ObjectQLError } from '@objectql/types';
-
-async create(objectName: string, data: any): Promise<any> {
-    try {
-        // Implementation
-    } catch (error) {
-        throw new ObjectQLError({
-            code: 'CREATE_FAILED',
-            message: `Failed to create ${objectName}: ${error.message}`,
-            details: { objectName, error }
-        });
-    }
-}
-```
-
-### 3. **TypeScript Strict Mode**
-
-- Enable `strict: true` in `tsconfig.json`
-- Avoid using `any` where possible
-- Define proper types for configuration
-
-### 4. **Async/Await Consistency**
-
-- All driver methods should be `async`
-- Always await database operations
-- Handle connection pooling properly
-
-### 5. **Performance Optimization**
-
-- Use connection pooling
-- Batch operations when possible
-- Implement proper indexing strategies
-
-### 6. **Testing**
-
-Create comprehensive tests in `test/index.test.ts`:
-
-```typescript
-import { RedisDriver } from '../src';
-
-describe('RedisDriver', () => {
-    let driver: RedisDriver;
-    
-    beforeAll(async () => {
-        driver = new RedisDriver({ url: 'redis://localhost:6379' });
-    });
-    
-    afterAll(async () => {
-        await driver.disconnect();
-    });
-    
-    describe('CRUD Operations', () => {
-        it('should create a record', async () => {
-            const result = await driver.create('users', {
-                name: 'Alice',
-                email: 'alice@example.com'
-            });
-            
-            expect(result).toHaveProperty('id');
-            expect(result.name).toBe('Alice');
-        });
-        
-        // Add more tests...
-    });
-});
-```
-
-## Example: Redis Driver
-
-See the complete Redis driver implementation in [`packages/drivers/redis/`](../../../packages/drivers/redis/) (if available).
-
-## Publishing Your Driver
-
-1. **Test Thoroughly**: Ensure all required methods work correctly
-2. **Document**: Create clear README with usage examples
-3. **Version**: Follow semantic versioning (SemVer)
-4. **Publish**: Publish to npm with appropriate tags
-
-```bash
-npm publish --access public
-```
-
-## Getting Help
-
-- Review existing drivers: [SQL](../../../packages/drivers/sql/), [MongoDB](../../../packages/drivers/mongo/)
-- Check the [Driver Interface](../../../packages/foundation/types/src/driver.ts)
-- Open an issue on [GitHub](https://github.com/objectstack-ai/objectql/issues)
-
-## Next Steps
-
-- Read the [Driver Extensibility Guide](./extensibility.md)
-- Study the [SQL Driver Implementation](../../../packages/drivers/sql/src/index.ts)
-- Join the ObjectQL community for support
diff --git a/docs/guide/drivers/index.md b/docs/guide/drivers/index.md
deleted file mode 100644
index 3c0c430a..00000000
--- a/docs/guide/drivers/index.md
+++ /dev/null
@@ -1,62 +0,0 @@
-# Database Drivers
-
-ObjectQL relies on **Drivers** to communicate with the underlying database. A driver is responsible for translating the ObjectQL specific query format (AST) into the native query language of the database (SQL, MongoDB Query, etc.).
-
-You can configure multiple drivers for different parts of your application, or use a single driver for everything.
-
-## Available Drivers
-
-We currently support the following official drivers:
-
-*   **[SQL Driver](./sql)**: Supports PostgreSQL, MySQL, SQLite, MSSQL, etc.
-*   **[MongoDB Driver](./mongo)**: Supports MongoDB.
-
-## Extensibility
-
-ObjectQL is designed to support additional database types through custom drivers. 
-
-*   **[Driver Extensibility Guide](./extensibility)**: Learn about potential database types that can be supported and how to choose the right one for your needs.
-*   **[Implementing a Custom Driver](./implementing-custom-driver)**: Step-by-step guide to building your own database driver for ObjectQL.
-
-## Unified ID Field
-
-ObjectQL provides a **consistent API** across all database drivers by standardizing on the `id` field name for primary keys:
-
-- **MongoDB Driver**: Automatically maps `id` (API) ↔ `_id` (database)
-- **SQL Driver**: Uses `id` natively in the database schema
-
-This means you can write database-agnostic code:
-
-```typescript
-// Same code works with MongoDB OR SQL drivers!
-const user = await app.create('users', {
-  id: 'user-123',     // Works with both drivers
-  name: 'Alice'
-});
-
-const query = {
-  filters: [['id', '=', 'user-123']]  // Consistent across drivers
-};
-const results = await app.find('users', query);
-```
-
-**No more switching between `_id` and `id` depending on your database!**
-
-See the individual driver documentation for implementation details.
-
-## Configuring a Driver
-
-Drivers are instantiated and passed to the `ObjectQL` constructor under the `driver` property (or `datasources` map for multi-db setup).
-
-```typescript
-import { ObjectQL } from '@objectql/core';
-import { SqlDriver } from '@objectql/driver-sql';
-
-const myDriver = new SqlDriver({ /* options */ });
-
-const app = new ObjectQL({
-  driver: myDriver
-});
-```
-
-See the specific pages for configuration options for each driver.
diff --git a/docs/guide/drivers/mongo.md b/docs/guide/drivers/mongo.md
deleted file mode 100644
index 6e087137..00000000
--- a/docs/guide/drivers/mongo.md
+++ /dev/null
@@ -1,154 +0,0 @@
-# MongoDB Driver
-
-The MongoDB driver allows ObjectQL to store data in a MongoDB database (version 4.0+). It takes advantage of MongoDB's document model to store JSON fields natively and flexible schemas.
-
-## Installation
-
-```bash
-npm install @objectql/driver-mongo mongodb
-```
-
-## Configuration
-
-The `MongoDriver` accepts connection parameters directly.
-
-```typescript
-import { MongoDriver } from '@objectql/driver-mongo';
-
-const driver = new MongoDriver({
-  url: 'mongodb://localhost:27017', // Connection string
-  dbName: 'my_app_db',              // Database name
-  options: {
-    // Optional MongoDB client options
-    maxPoolSize: 10
-  }
-});
-```
-
-## Unified ID Field
-
-ObjectQL provides a **unified `id` field** across all database drivers for a consistent API experience.
-
-### How It Works
-
-- **API Level**: You always use `id` in your application code (queries, filters, documents)
-- **Database Level**: MongoDB internally uses `_id` as required by MongoDB conventions
-- **Automatic Mapping**: The driver transparently converts between `id` and `_id`
-
-### Examples
-
-**Querying by ID:**
-```typescript
-// ✅ Use 'id' in queries - works consistently across all drivers
-const query = {
-  filters: [['id', '=', '507f1f77bcf86cd799439011']]
-};
-const users = await app.find('users', query);
-```
-
-**Creating Documents:**
-```typescript
-// ✅ Use 'id' when creating - the driver maps it to '_id' internally
-const newUser = await app.create('users', {
-  id: '507f1f77bcf86cd799439011',  // Optional: specify custom ID
-  name: 'Alice',
-  email: 'alice@example.com'
-});
-
-// Result returned with 'id' field (not '_id')
-console.log(newUser.id); // '507f1f77bcf86cd799439011'
-```
-
-**Finding by ID:**
-```typescript
-// ✅ Use 'id' parameter
-const user = await app.findOne('users', '507f1f77bcf86cd799439011');
-console.log(user.id); // Always 'id', never '_id'
-```
-
-**Sorting by ID:**
-```typescript
-const query = {
-  sort: [['id', 'desc']]  // ✅ Use 'id' for sorting
-};
-const users = await app.find('users', query);
-```
-
-**Field Projection:**
-```typescript
-const query = {
-  fields: ['id', 'name', 'email']  // ✅ Use 'id' to select the ID field
-};
-const users = await app.find('users', query);
-// Results contain 'id', not '_id'
-```
-
-### Migration from Legacy Code
-
-If you have existing code using `_id`, you have two options:
-
-1. **Recommended: Migrate to `id`** for consistency across drivers:
-
-**Before (Legacy):**
-```typescript
-// ❌ Old way - inconsistent with SQL drivers
-const query = {
-  filters: [['_id', '=', '507f1f77bcf86cd799439011']],
-  sort: [['_id', 'desc']],
-  fields: ['_id', 'name']
-};
-```
-
-**After (Recommended):**
-```typescript
-// ✅ New way - consistent across all drivers
-const query = {
-  filters: [['id', '=', '507f1f77bcf86cd799439011']],
-  sort: [['id', 'desc']],
-  fields: ['id', 'name']
-};
-```
-
-2. **Backward Compatible Mode:** Continue using `_id` in queries (results still return `id`)
-
-The MongoDB driver **fully supports `_id` in filters, sorting, and field projections** for backward compatibility:
-
-```typescript
-// ✅ This works - backward compatible
-const query = {
-  filters: [['_id', '=', '507f1f77bcf86cd799439011']],
-  sort: [['_id', 'desc']],
-  fields: ['_id', 'name']
-};
-const users = await app.find('users', query);
-
-// Results ALWAYS use 'id' regardless of query field name
-console.log(users[0].id); // '507f1f77bcf86cd799439011'
-console.log(users[0]._id); // undefined
-```
-
-**Key Points:**
-- Queries accept both `id` and `_id` (automatically mapped to MongoDB's `_id`)
-- Results always return `id` field (never `_id`)
-- Using `id` is recommended for database portability
-
-## ID Generation
-
-When creating documents without specifying an `id`, the driver automatically generates a string ID:
-
-```typescript
-const newUser = await app.create('users', {
-  name: 'Bob',
-  // No id specified
-});
-
-// Driver generates a unique string ID (not ObjectId)
-console.log(newUser.id); // e.g., '507f1f77bcf86cd799439011'
-```
-
-The generated IDs are hexadecimal strings (24 characters) that maintain MongoDB's uniqueness guarantees without using ObjectId objects.
-
-## Limitations
-
-*   **Joins**: While MongoDB supports `$lookup` (which this driver uses for joins), complex relationships across many collections can be slower than SQL.
-*   **Transactions**: Transactions are supported but require a MongoDB Replica Set deployment.
diff --git a/docs/guide/drivers/sql.md b/docs/guide/drivers/sql.md
deleted file mode 100644
index 21d4260f..00000000
--- a/docs/guide/drivers/sql.md
+++ /dev/null
@@ -1,127 +0,0 @@
-# SQL Driver (Knex)
-
-The SQL driver implementation is based on [Knex.js](https://knexjs.org/), a powerful SQL query builder. It supports all major SQL databases including PostgreSQL, MySQL, SQLite3, and SQL Server.
-
-## Installation
-
-```bash
-npm install @objectql/driver-sql knex pg
-# Replace 'pg' with 'mysql', 'sqlite3', or 'mssql' depending on your database.
-```
-
-## Configuration
-
-The `SqlDriver` constructor accepts the standard [Knex configuration object](https://knexjs.org/guide/#configuration-options).
-
-```typescript
-import { SqlDriver } from '@objectql/driver-sql';
-
-const driver = new SqlDriver({
-  client: 'pg', // 'mysql', 'sqlite3', etc.
-  connection: {
-    host: '127.0.0.1',
-    port: 5432,
-    user: 'your_user',
-    password: 'your_password',
-    database: 'your_app_db'
-  },
-  // Optional: Connection pool settings
-  pool: { min: 2, max: 10 }
-});
-```
-
-### SQLite Example
-
-For local development or testing with SQLite:
-
-```typescript
-const driver = new SqlDriver({
-  client: 'sqlite3',
-  connection: {
-    filename: './local.db'
-  },
-  useNullAsDefault: true // Required for SQLite support
-});
-```
-
-## Unified ID Field
-
-ObjectQL uses **`id`** as the primary key field name across all SQL databases for consistency with the MongoDB driver.
-
-### How It Works
-
-- **Database Column**: SQL tables use `id` as the primary key column (VARCHAR/TEXT type)
-- **API Level**: You use `id` in your queries, filters, and documents
-- **Consistency**: Same API as MongoDB driver - no need to remember `_id` vs `id`
-
-### Examples
-
-**Table Schema:**
-```sql
-CREATE TABLE users (
-  id VARCHAR(255) PRIMARY KEY,  -- Primary key is 'id'
-  name VARCHAR(255),
-  email VARCHAR(255),
-  created_at TIMESTAMP,
-  updated_at TIMESTAMP
-);
-```
-
-**Creating Documents:**
-```typescript
-// Create with auto-generated ID
-const user = await app.create('users', {
-  name: 'Alice',
-  email: 'alice@example.com'
-});
-console.log(user.id); // Auto-generated UUID or custom ID
-
-// Create with custom ID
-const user = await app.create('users', {
-  id: 'custom-user-123',
-  name: 'Bob'
-});
-```
-
-**Querying by ID:**
-```typescript
-const query = {
-  filters: [['id', '=', 'custom-user-123']]
-};
-const users = await app.find('users', query);
-```
-
-**Finding by ID:**
-```typescript
-const user = await app.findOne('users', 'custom-user-123');
-```
-
-### Legacy `_id` Support
-
-For backward compatibility, if you provide `_id` in a create operation, the driver will automatically map it to `id`:
-
-```typescript
-// Legacy code - automatically mapped
-const user = await app.create('users', {
-  _id: 'user-123',  // Mapped to 'id' internally
-  name: 'Charlie'
-});
-
-console.log(user.id); // 'user-123'
-```
-
-This ensures smooth migration for projects that previously used MongoDB-style `_id` fields.
-
-## Schema Mapping
-
-The driver automatically maps ObjectQL types to SQL column types:
-
-| ObjectQL Type | SQL Type | Notes |
-| :--- | :--- | :--- |
-| `text` | `VARCHAR(255)` | |
-| `textarea` | `TEXT` | |
-| `boolean` | `BOOLEAN` | or `TINYINT` in MySQL |
-| `number` | `FLOAT` / `DECIMAL` | |
-| `date` | `DATE` | |
-| `datetime` | `TIMESTAMP` | |
-| `json` | `JSON` | or `TEXT` if not supported |
diff --git a/docs/guide/formulas-and-rules-quick-ref.md b/docs/guide/formulas-and-rules-quick-ref.md
deleted file mode 100644
index bd152a95..00000000
--- a/docs/guide/formulas-and-rules-quick-ref.md
+++ /dev/null
@@ -1,275 +0,0 @@
-# Formulas & Rules Quick Reference
-
-**Quick syntax reference for ObjectQL formulas and validation rules.**
-
-For complete documentation, see:
-- 📖 [English Guide](./formulas-and-rules.md)
-
-## Formula Syntax Quick Reference
-
-### Basic Formula
-
-```yaml
-calculated_field:
-  type: formula
-  expression: "field1 + field2"
-  data_type: number
-```
-
-### Common Patterns
-
-```yaml
-# Arithmetic
-profit:
-  type: formula
-  expression: "revenue - cost"
-  data_type: currency
-
-# String concatenation
-full_name:
-  type: formula
-  expression: "first_name + ' ' + last_name"
-  data_type: text
-
-# Conditional
-status_label:
-  type: formula
-  expression: "score > 80 ? 'High' : 'Low'"
-  data_type: text
-
-# Date math
-days_old:
-  type: formula
-  expression: "$today - created_date"
-  data_type: number
-
-# Lookup reference
-owner_email:
-  type: formula
-  expression: "project.owner.email"
-  data_type: text
-```
-
-### Special Variables
-
-| Variable | Example |
-|----------|---------|
-| `$today` | Current date |
-| `$now` | Current timestamp |
-| `$current_user.id` | Current user ID |
-| `$current_user.name` | Current user name |
-
-## Validation Rules Quick Reference
-
-### Field Validation
-
-```yaml
-# In object.yml
-fields:
-  email:
-    type: email
-    required: true
-    validation:
-      format: email
-      message: "Please enter a valid email"
-  
-  age:
-    type: number
-    validation:
-      min: 0
-      max: 150
-```
-
-### Cross-Field Validation
-
-```yaml
-# In project.validation.yml
-rules:
-  - name: valid_date_range
-    type: cross_field
-    rule:
-      field: end_date
-      operator: ">="
-      compare_to: start_date
-    message: "End date must be after start date"
-```
-
-### Conditional Validation
-
-```yaml
-rules:
-  - name: description_required_for_high_budget
-    type: conditional
-    condition:
-      field: budget
-      operator: ">"
-      value: 10000
-    rule:
-      field: description
-      operator: "not_empty"
-    message: "Description required for budgets over $10,000"
-```
-
-### State Machine
-
-```yaml
-rules:
-  - name: status_transition
-    type: state_machine
-    field: status
-    transitions:
-      draft:
-        allowed_next: [submitted, cancelled]
-      submitted:
-        allowed_next: [approved, rejected]
-      approved:
-        allowed_next: []
-        is_terminal: true
-```
-
-## Operators Quick Reference
-
-### Comparison
-
-| Operator | Example |
-|----------|---------|
-| `=` | `field: status, operator: "=", value: "active"` |
-| `!=` | `field: status, operator: "!=", value: null` |
-| `>` | `field: amount, operator: ">", value: 1000` |
-| `>=` | `field: end_date, operator: ">=", compare_to: start_date` |
-| `<` | `field: age, operator: "<", value: 18` |
-| `<=` | `field: discount, operator: "<=", value: 1` |
-| `in` | `field: status, operator: "in", value: ["active", "pending"]` |
-| `not_in` | `field: status, operator: "not_in", value: ["deleted"]` |
-| `contains` | `field: tags, operator: "contains", value: "urgent"` |
-| `not_empty` | `field: description, operator: "not_empty"` |
-
-### Logical
-
-```yaml
-# AND - all must be true
-condition:
-  all_of:
-    - field: status
-      operator: "="
-      value: active
-    - field: amount
-      operator: ">"
-      value: 1000
-
-# OR - any must be true
-condition:
-  any_of:
-    - field: priority
-      operator: "="
-      value: high
-    - field: amount
-      operator: ">"
-      value: 10000
-
-# NOT - must be false
-condition:
-  none_of:
-    - field: status
-      operator: "="
-      value: deleted
-```
-
-## Permission Rules Quick Reference
-
-```yaml
-# In project.permission.yml
-rules:
-  - name: owner_full_access
-    condition:
-      field: owner_id
-      operator: "="
-      value: $current_user.id
-    permissions:
-      read: true
-      create: true
-      update: true
-      delete: true
-```
-
-## Common Use Cases
-
-### Budget Validation
-
-```yaml
-rules:
-  - name: budget_approval_required
-    type: conditional
-    condition:
-      field: budget
-      operator: ">"
-      value: 50000
-    rule:
-      field: approved_by
-      operator: "not_empty"
-    message: "Budget over $50K requires approval"
-```
-
-### Date Range Validation
-
-```yaml
-rules:
-  - name: valid_date_range
-    type: cross_field
-    rule:
-      field: end_date
-      operator: ">="
-      compare_to: start_date
-    message: "End date must be after start date"
-```
-
-### Status Workflow
-
-```yaml
-rules:
-  - name: order_workflow
-    type: state_machine
-    field: status
-    transitions:
-      draft:
-        allowed_next: [submitted, cancelled]
-      submitted:
-        allowed_next: [approved, rejected]
-      approved:
-        allowed_next: [processing, cancelled]
-      processing:
-        allowed_next: [shipped, cancelled]
-      shipped:
-        allowed_next: [delivered]
-      delivered:
-        allowed_next: []  # terminal
-```
-
-### Calculated Metrics
-
-```yaml
-# Profit margin
-profit_margin:
-  type: formula
-  expression: "(revenue - cost) / revenue * 100"
-  data_type: percent
-
-# Days since creation
-age_days:
-  type: formula
-  expression: "$today - created_date"
-  data_type: number
-
-# Full address
-full_address:
-  type: formula
-  expression: "street + ', ' + city + ', ' + state + ' ' + zip"
-  data_type: text
-```
-
-## Related Docs
-
-- 📖 [Complete Formulas & Rules Guide](./formulas-and-rules.md)
-- 📖 [Object Definitions](../spec/object.md)
-- 📖 [Validation Spec](../spec/validation.md)
-- 📖 [Permission Spec](../spec/permission.md)
diff --git a/docs/guide/formulas-and-rules.md b/docs/guide/formulas-and-rules.md
deleted file mode 100644
index f5da18dd..00000000
--- a/docs/guide/formulas-and-rules.md
+++ /dev/null
@@ -1,690 +0,0 @@
-# Formulas and Rules Syntax Guide
-
-This guide covers the complete syntax for formulas and validation rules in ObjectQL. Understanding these patterns will help you create powerful calculated fields and enforce business rules.
-
-## Table of Contents
-
-1. [Formula Syntax](#formula-syntax)
-2. [Validation Rule Syntax](#validation-rule-syntax)
-3. [Permission Rule Syntax](#permission-rule-syntax)
-4. [Expression Evaluation](#expression-evaluation)
-5. [Common Operators](#common-operators)
-6. [Best Practices](#best-practices)
-
-## Formula Syntax
-
-Formulas are used to create calculated fields that derive their values from other fields or expressions. They are read-only and automatically computed.
-
-### Basic Formula Structure
-
-```yaml
-fields:
-  field_name:
-    type: formula
-    expression: "field1 + field2"
-    data_type: number  # Result type: number, text, date, boolean
-```
-
-### Expression Syntax
-
-ObjectQL formulas use **JavaScript-style expressions** with field references:
-
-#### Field References
-
-```yaml
-# Simple field reference - use field name directly
-calc_total:
-  type: formula
-  expression: "price * quantity"
-  data_type: number
-
-# With curly braces (alternative syntax)
-calc_total_alt:
-  type: formula
-  expression: "{price} * {quantity}"
-  data_type: number
-```
-
-#### Arithmetic Operations
-
-```yaml
-# Addition
-profit:
-  type: formula
-  expression: "revenue - cost"
-  data_type: currency
-
-# Multiplication
-area:
-  type: formula
-  expression: "width * height"
-  data_type: number
-
-# Division
-average_score:
-  type: formula
-  expression: "total_score / num_attempts"
-  data_type: number
-
-# Percentage
-profit_margin:
-  type: formula
-  expression: "(revenue - cost) / revenue * 100"
-  data_type: percent
-```
-
-#### String Operations
-
-```yaml
-# Concatenation
-full_name:
-  type: formula
-  expression: "first_name + ' ' + last_name"
-  data_type: text
-
-# String methods
-uppercase_name:
-  type: formula
-  expression: "name.toUpperCase()"
-  data_type: text
-```
-
-#### Date Calculations
-
-```yaml
-# Date difference
-days_open:
-  type: formula
-  expression: "$today - created_date"
-  data_type: number
-
-# Date comparison
-is_overdue:
-  type: formula
-  expression: "due_date < $today && status != 'completed'"
-  data_type: boolean
-```
-
-#### Conditional Formulas
-
-```yaml
-# Simple if/else
-priority_label:
-  type: formula
-  expression: "score > 80 ? 'High' : 'Low'"
-  data_type: text
-
-# Multi-condition
-status_category:
-  type: formula
-  expression: |
-    if (amount > 10000) {
-      return 'High Value';
-    } else if (amount > 1000) {
-      return 'Medium Value';
-    } else {
-      return 'Low Value';
-    }
-  data_type: text
-```
-
-#### Lookup Field References
-
-```yaml
-# Access related object fields using dot notation
-account_owner_name:
-  type: formula
-  expression: "customer.account.owner.name"
-  data_type: text
-
-# Nested lookups
-region_manager:
-  type: formula
-  expression: "account.region.manager.email"
-  data_type: text
-```
-
-### Special Variables
-
-| Variable | Description | Example |
-|----------|-------------|---------|
-| `$today` | Current date (YYYY-MM-DD) | `$today - created_date` |
-| `$now` | Current timestamp | `$now` |
-| `$current_user.id` | Current user ID | `owner_id == $current_user.id` |
-| `$current_user.name` | Current user name | `$current_user.name` |
-
-### Formula Examples
-
-#### Revenue Calculations
-
-```yaml
-# Simple profit
-profit:
-  type: formula
-  expression: "revenue - cost"
-  data_type: currency
-
-# Profit margin percentage
-profit_margin:
-  type: formula
-  expression: "(revenue - cost) / revenue * 100"
-  data_type: percent
-
-# Discounted price
-final_price:
-  type: formula
-  expression: "list_price * (1 - discount_rate)"
-  data_type: currency
-```
-
-#### Date & Time
-
-```yaml
-# Age calculation
-days_since_created:
-  type: formula
-  expression: "$today - created_date"
-  data_type: number
-
-# Is expired
-is_expired:
-  type: formula
-  expression: "expiration_date < $today"
-  data_type: boolean
-
-# Duration
-project_duration_days:
-  type: formula
-  expression: "end_date - start_date"
-  data_type: number
-```
-
-#### Status & Categorization
-
-```yaml
-# Risk level based on multiple factors
-risk_level:
-  type: formula
-  expression: |
-    if (amount > 100000 && customer.credit_score < 600) {
-      return 'High Risk';
-    } else if (amount > 50000 || customer.credit_score < 700) {
-      return 'Medium Risk';
-    } else {
-      return 'Low Risk';
-    }
-  data_type: text
-
-# Priority score
-priority_score:
-  type: formula
-  expression: |
-    (urgency_level * 0.4) + 
-    (impact_level * 0.4) + 
-    (customer_tier * 0.2)
-  data_type: number
-```
-
-## Validation Rule Syntax
-
-Validation rules enforce data quality and business logic. They can be simple field checks or complex cross-field validations.
-
-### Rule Types
-
-ObjectQL supports several types of validation rules:
-
-1. **Field Validation** - Single field constraints
-2. **Cross-Field Validation** - Compare multiple fields
-3. **Conditional Validation** - Apply rules based on conditions
-4. **State Machine** - Enforce state transitions
-5. **Business Rule** - Complex business logic
-6. **Custom Validation** - JavaScript functions
-
-### Field Validation
-
-Defined directly in field configuration:
-
-```yaml
-# In object.yml
-fields:
-  email:
-    type: email
-    required: true
-    validation:
-      format: email
-      message: "Please enter a valid email address"
-  
-  age:
-    type: number
-    validation:
-      min: 0
-      max: 150
-      message: "Age must be between 0 and 150"
-  
-  username:
-    type: text
-    required: true
-    validation:
-      min_length: 3
-      max_length: 20
-      pattern: "^[a-zA-Z0-9_]+$"
-      message: "Username must be 3-20 alphanumeric characters"
-```
-
-### Cross-Field Validation
-
-Compare values between multiple fields:
-
-```yaml
-# In project.validation.yml
-rules:
-  - name: valid_date_range
-    type: cross_field
-    rule:
-      field: end_date
-      operator: ">="
-      compare_to: start_date
-    message: "End date must be on or after start date"
-    error_code: "INVALID_DATE_RANGE"
-```
-
-#### Supported Operators
-
-| Operator | Description | Example |
-|----------|-------------|---------|
-| `=` | Equals | `field: status, operator: "=", value: "active"` |
-| `!=` | Not equals | `field: status, operator: "!=", value: null` |
-| `>` | Greater than | `field: end_date, operator: ">", compare_to: start_date` |
-| `>=` | Greater than or equal | `field: budget, operator: ">=", value: 0` |
-| `<` | Less than | `field: age, operator: "<", value: 18` |
-| `<=` | Less than or equal | `field: discount, operator: "<=", value: 1` |
-| `in` | In array | `field: status, operator: "in", value: ["active", "pending"]` |
-| `not_in` | Not in array | `field: status, operator: "not_in", value: ["deleted"]` |
-| `contains` | String/array contains | `field: tags, operator: "contains", value: "urgent"` |
-| `not_empty` | Field is not empty | `field: description, operator: "not_empty"` |
-
-### Conditional Validation
-
-Apply validation only when certain conditions are met:
-
-```yaml
-rules:
-  - name: description_required_for_high_budget
-    type: conditional
-    description: "Description is required for high budget projects"
-    condition:
-      field: budget
-      operator: ">"
-      value: 10000
-    rule:
-      field: description
-      operator: "not_empty"
-    message: "Description is required for projects over $10,000"
-```
-
-### State Machine Validation
-
-Enforce valid state transitions:
-
-```yaml
-rules:
-  - name: status_transition
-    type: state_machine
-    field: status
-    transitions:
-      planning:
-        allowed_next: [active, cancelled]
-      active:
-        allowed_next: [on_hold, completed, cancelled]
-      on_hold:
-        allowed_next: [active, cancelled]
-      completed:
-        allowed_next: []
-        is_terminal: true
-      cancelled:
-        allowed_next: []
-        is_terminal: true
-    message: "Invalid status transition from {{old_status}} to {{new_status}}"
-    error_code: "INVALID_STATE_TRANSITION"
-```
-
-### Business Rule Validation
-
-Complex business logic with multiple conditions:
-
-```yaml
-rules:
-  - name: budget_within_limits
-    type: business_rule
-    constraint:
-      expression: "budget <= department.budget_limit OR executive_approval = true"
-      relationships:
-        department:
-          via: department_id
-          fields: [budget_limit]
-    message: "Budget exceeds department limit. Executive approval required."
-    error_code: "BUDGET_LIMIT_EXCEEDED"
-    trigger: [create, update]
-    fields: [budget, department_id, executive_approval]
-```
-
-### Custom Validation
-
-JavaScript validation functions for complex logic:
-
-```yaml
-rules:
-  - name: credit_check
-    type: custom
-    message: "Customer credit limit exceeded"
-    error_code: "CREDIT_LIMIT_EXCEEDED"
-    trigger: [create, update]
-    fields: [amount, customer_id]
-    validator: |
-      async function validate(record, context) {
-        const customer = await context.api.findOne('customers', record.customer_id);
-        const totalOrders = await context.api.sum('orders', 'amount', [
-          ['customer_id', '=', record.customer_id],
-          ['status', 'in', ['pending', 'processing']]
-        ]);
-        
-        return (totalOrders + record.amount) <= customer.credit_limit;
-      }
-```
-
-## Permission Rule Syntax
-
-Permission rules control data access based on user roles and record conditions.
-
-### Basic Permission Rules
-
-```yaml
-# In project.permission.yml
-rules:
-  - name: owner_full_access
-    description: "Record owner has full access"
-    priority: 10
-    condition:
-      field: owner_id
-      operator: "="
-      value: $current_user.id
-    permissions:
-      read: true
-      create: true
-      update: true
-      delete: true
-```
-
-### Complex Conditions
-
-```yaml
-rules:
-  - name: public_approved_read_only
-    description: "Public approved records are read-only"
-    condition:
-      all_of:
-        - field: status
-          operator: "="
-          value: approved
-        - field: is_public
-          operator: "="
-          value: true
-    permissions:
-      read: true
-      update: false
-      delete: false
-```
-
-### Conditional Operators
-
-| Operator | Description |
-|----------|-------------|
-| `all_of` | All conditions must be true (AND) |
-| `any_of` | Any condition must be true (OR) |
-| `none_of` | No conditions can be true (NOT) |
-
-## Expression Evaluation
-
-### Expression Context
-
-When expressions are evaluated, they have access to:
-
-1. **Record Fields** - Current record data
-2. **Related Records** - Via lookup/master-detail relationships
-3. **System Variables** - `$today`, `$now`, `$current_user`
-4. **Previous Values** - For update operations (in validation)
-
-### Evaluation Order
-
-1. Field-level validations (required, format, range)
-2. Cross-field validations
-3. Business rule validations
-4. Custom validations
-5. State machine validations
-
-### Error Handling
-
-```yaml
-rules:
-  - name: safe_division
-    type: custom
-    validator: |
-      function validate(record) {
-        if (record.denominator === 0) {
-          return false;
-        }
-        return (record.numerator / record.denominator) < 100;
-      }
-    message: "Result must be less than 100 (division by zero not allowed)"
-```
-
-## Common Operators
-
-### Comparison Operators
-
-```javascript
-// Equality
-field = value
-field != value
-
-// Numerical comparison
-field > value
-field >= value
-field < value
-field <= value
-
-// Set membership
-field in [value1, value2, value3]
-field not_in [value1, value2]
-
-// String operations
-field contains "substring"
-field starts_with "prefix"
-field ends_with "suffix"
-
-// Existence
-field is_null
-field is_not_null
-field not_empty
-```
-
-### Logical Operators
-
-```yaml
-# AND - All conditions must be true
-condition:
-  all_of:
-    - field: status
-      operator: "="
-      value: active
-    - field: budget
-      operator: ">"
-      value: 1000
-
-# OR - At least one condition must be true
-condition:
-  any_of:
-    - field: priority
-      operator: "="
-      value: high
-    - field: amount
-      operator: ">"
-      value: 10000
-
-# NOT - Condition must be false
-condition:
-  none_of:
-    - field: status
-      operator: "="
-      value: deleted
-```
-
-### Array Filters
-
-Used in query language for filtering records:
-
-```javascript
-// Basic filter - [field, operator, value]
-["status", "=", "active"]
-
-// Multiple filters with AND
-[
-  ["status", "=", "active"],
-  "and",
-  ["amount", ">", 1000]
-]
-
-// Multiple filters with OR
-[
-  ["priority", "=", "high"],
-  "or",
-  ["amount", ">", 50000]
-]
-
-// Complex nested conditions
-[
-  ["status", "=", "active"],
-  "and",
-  [
-    ["priority", "=", "high"],
-    "or",
-    ["amount", ">", 10000]
-  ]
-]
-```
-
-## Best Practices
-
-### Formula Best Practices
-
-1. **Keep formulas simple** - Complex logic should be in hooks or actions
-2. **Use appropriate data types** - Specify correct `data_type` for the result
-3. **Handle null values** - Use conditional checks for optional fields
-4. **Document complex formulas** - Add comments explaining business logic
-5. **Test edge cases** - Verify division by zero, null values, etc.
-
-```yaml
-# Good - Simple and clear
-discount_amount:
-  type: formula
-  expression: "list_price * discount_rate"
-  data_type: currency
-
-# Good - Handles null
-full_name:
-  type: formula
-  expression: "(first_name || '') + ' ' + (last_name || '')"
-  data_type: text
-
-# Avoid - Too complex for a formula
-complex_score:
-  type: formula
-  expression: |
-    var base = weight * coefficient;
-    for (var i = 0; i < iterations; i++) {
-      base = base * (1 + rate);
-    }
-    return base;
-  data_type: number
-  # Better: Move to a hook or action
-```
-
-### Validation Rule Best Practices
-
-1. **Use declarative rules when possible** - Prefer `cross_field` over `custom`
-2. **Provide clear error messages** - Help users understand what's wrong
-3. **Set appropriate severity** - Use `error`, `warning`, or `info`
-4. **Order rules by likelihood of failure** - Fast-fail optimization
-5. **Use AI context** - Help AI tools understand business intent
-
-```yaml
-# Good - Clear message and intent
-rules:
-  - name: valid_date_range
-    type: cross_field
-    ai_context:
-      intent: "Ensure timeline is logical"
-      business_rule: "Projects cannot end before they start"
-    rule:
-      field: end_date
-      operator: ">="
-      compare_to: start_date
-    message: "End date must be on or after start date"
-    severity: error
-
-# Good - Conditional validation
-  - name: approval_required_for_high_value
-    type: conditional
-    condition:
-      field: amount
-      operator: ">"
-      value: 50000
-    rule:
-      field: approved_by
-      operator: "not_empty"
-    message: "Approval required for transactions over $50,000"
-    severity: error
-```
-
-### Performance Optimization
-
-1. **Minimize async validations** - They slow down operations
-2. **Use indexes** - For fields used in validation lookups
-3. **Cache validation results** - When appropriate
-4. **Batch validation** - For bulk operations
-
-```yaml
-rules:
-  - name: inventory_check
-    type: custom
-    batch_enabled: true
-    batch_size: 100
-    validator: |
-      async function validateBatch(records, context) {
-        const skus = records.map(r => r.sku);
-        const inventory = await context.api.find('inventory', {
-          filters: [['sku', 'in', skus]]
-        });
-        
-        return records.map(record => {
-          const inv = inventory.find(i => i.sku === record.sku);
-          return inv && inv.available_quantity >= record.quantity;
-        });
-      }
-```
-
-## Related Documentation
-
-- [Object Definition](../spec/object.md) - Complete object metadata reference
-- [Validation Rules](../spec/validation.md) - Detailed validation specification
-- [Permission Rules](../spec/permission.md) - Access control documentation
-- [Query Language](../spec/query-language.md) - Query syntax and filters
-- [Hooks & Actions](./logic-hooks.md) - Custom business logic
-
-## Examples
-
-For working examples, see:
-
-- `/packages/starters/basic/src/modules/projects/` - Project validation examples
-- `/packages/starters/enterprise/src/modules/crm/` - CRM business rules
-- `/examples/tutorials/` - Tutorial projects with formulas and rules
diff --git a/docs/guide/getting-started.md b/docs/guide/getting-started.md
deleted file mode 100644
index 29e2204b..00000000
--- a/docs/guide/getting-started.md
+++ /dev/null
@@ -1,158 +0,0 @@
-# Getting Started with ObjectQL
-
-**ObjectQL** is a universal, metadata-driven ORM designed for building dynamic business applications. Unlike traditional ORMs where you define schema in class files (like TypeORM entities), ObjectQL uses a **Metadata-First** approach.
-
-## Why ObjectQL?
-
-1.  **Metadata-Driven**: Define your data models in JSON or YAML. Perfect for low-code platforms where schema changes at runtime.
-2.  **Universal Protocol**: The query language is a JSON AST, making it easy for frontends or AI agents to generate queries.
-3.  **Action & Hook System**: Built-in support for "Button Actions" (RPC) and "Triggers" (Hooks), allowing you to model **Behavior** alongside **Data**.
-
-## Quick Start: The "Hello World"
-
-You can experience ObjectQL with a single file. No YAML, no complex config.
-
-### 1. Minimal Setup
-
-Install the core and SQLite driver (for zero-config database).
-
-```bash
-npm install @objectql/core @objectql/driver-sql sqlite3
-# or
-pnpm add @objectql/core @objectql/driver-sql sqlite3
-```
-
-### 2. The Universal Script
-
-Create `index.ts`. This script defines the schema, boots the engine, and runs queries in one go.
-
-```typescript
-import { ObjectQL } from '@objectql/core';
-import { SqlDriver } from '@objectql/driver-sql';
-
-async function main() {
-  // 1. Initialize Driver (In-Memory SQLite)
-  const driver = new SqlDriver({
-    client: 'sqlite3',
-    connection: { filename: ':memory:' }, 
-    useNullAsDefault: true
-  });
-
-  // 2. Initialize Engine
-  const app = new ObjectQL({
-    datasources: { default: driver }
-  });
-
-  // 3. Define Metadata Inline (Code as Configuration)
-  app.registerObject({
-    name: 'todo',
-    fields: {
-      title: { type: 'text', required: true },
-      completed: { type: 'boolean', defaultValue: false }
-    }
-  });
-
-  await app.init();
-
-  // 4. Run Business Logic
-  // We use a system context here for simplicity
-  const ctx = app.createContext({ isSystem: true });
-  const repo = ctx.object('todo');
-
-  await repo.create({ title: 'Build the Future' });
-  
-  const results = await repo.find();
-  console.log('Todos:', results);
-}
-
-main();
-```
-
-## Scaling Up: The Metadata Approach
-
-Once you are comfortable with the core, you should move your definitions to YAML files.
-
-```typescript
-import { ObjectQL } from '@objectql/core';
-import * as path from 'path';
-
-async function main() {
-    const db = new ObjectQL({
-        // 1. Connection String (Protocol://Path)
-        // Detects 'sqlite', 'postgres', 'mongodb' automatically
-        connection: 'sqlite://data.db', 
-        
-        // 2. Schema Source
-        // Where your *.object.yml files are located
-        source: ['src/objects'],
-
-        // 3. Load Presets (Optional)
-        // Load standard objects from npm packages
-        presets: ['@objectql/preset-auth']
-    });
-
-    await db.init();
-    
-    // ...
-    
-    // 3. Create Data (CRUD)
-    // Create a context (representing a user request)
-    const ctx = db.createContext({}); 
-    const todoRepo = ctx.object('todo');
-
-    const newTask = await todoRepo.create({
-        title: 'Learn ObjectQL',
-        completed: false
-    });
-    console.log('Created:', newTask);
-
-    // 4. Query Data
-    const tasks = await todoRepo.find({
-        filters: [['completed', '=', false]]
-    });
-    console.log('Pending Tasks:', tasks);
-}
-
-main();
-```
-
-## Adding Business Logic
-
-ObjectQL shines when you need to add logic.
-
-### Adding a Hook
-
-Triggers logic automatically when data changes.
-
-```typescript
-app.on('beforeCreate', 'todo', async (ctx) => {
-    if (ctx.doc.title === 'Sleep') {
-        throw new Error("Cannot sleep yet!");
-    }
-    // Auto-tagging
-    ctx.doc.title = `[Task] ${ctx.doc.title}`;
-});
-```
-
-### Adding an Action
-
-Defines a custom operation (RPC) that frontends can call.
-
-```typescript
-// Define protocol
-app.registerAction('todo', 'mark_done', async (ctx) => {
-    const { id } = ctx;
-    await ctx.object('todo').update(id, { completed: true });
-    return { message: 'Good job!' };
-});
-
-// Invocation
-await ctx.object('todo').execute('mark_done', 'id_123', {});
-```
-
-## Next Steps
-
-*   **[Database Drivers](./drivers/index.md)**: Connect to PostgreSQL, MongoDB, etc.
-*   **[Data Modeling](./data-modeling.md)**: Learn about all field types (Select, Lookup, Date, etc.)
-*   **[SDK Reference](./sdk-reference.md)**: Explore the full API.
-*   **[Hooks](./logic-hooks.md)**: Deep dive into the event system.
diff --git a/docs/guide/ide-setup.md b/docs/guide/ide-setup.md
deleted file mode 100644
index 29ff0edb..00000000
--- a/docs/guide/ide-setup.md
+++ /dev/null
@@ -1,24 +0,0 @@
-# IDE Setup
-
-To get the best experience developing with ObjectQL, we recommend Visual Studio Code with the following configuration.
-
-## Visual Studio Code
-
-We recommend using [VS Code](https://code.visualstudio.com/) as your primary editor.
-
-### Recommended Extensions
-
-**1. YAML (Red Hat)**  
-Essential for editing `*.object.yml` files. It provides syntax highlighting and validation.  
-[Install Extension](https://marketplace.visualstudio.com/items?itemName=redhat.vscode-yaml)
-
-**2. JSON (Official)**  
-For editing configuration files.
-
-## AI Assistant Configuration
-
-ObjectQL is designed to be "AI-Native". The most efficient way to write schema and hooks is by pairing with an LLM.
-
-We strongly recommend configuring your AI Coding Assistant (GitHub Copilot, Cursor, Windsurf) with our specialized System Prompts. These prompts teach the AI about ObjectQL's metadata protocol.
-
-[👉 Go to AI Coding Assistant Guide](/ai/coding-assistant)
diff --git a/docs/guide/index.md b/docs/guide/index.md
deleted file mode 100644
index 351f39d0..00000000
--- a/docs/guide/index.md
+++ /dev/null
@@ -1,69 +0,0 @@
-# Introduction
-
-**ObjectQL** is a protocol-first application engine. It rethinks backend development by treating everything—Data Models, Queries, and Logic—as **structured data** rather than code strings.
-
-## The Core Philosophy
-
-### 1. The JSON Protocol
-In traditional development, you write SQL strings (`SELECT * FROM users`) or use fluent builders (`db.select('users')`).
-In ObjectQL, the query **IS** the data structure.
-
-```json
-// Find users where age > 18
-{
-  "op": "find",
-  "object": "user",
-  "args": {
-    "filters": [["age", ">", 18]]
-  }
-}
-```
-
-This makes the protocol:
-*   **Universal**: Can be generated by any client (JS, Python, Swift, or LLMs).
-*   **Serialization-ready**: Pass it over HTTP, WebSocket, or save it to a file.
-*   **Secure**: Zero SQL injection risk by design.
-
-### 2. Metadata as Source of Truth
-Instead of defining TypeScript classes or SQL DDL, you define your business domain in declarative YAML.
-
-```yaml
-# user.object.yml
-name: user
-fields:
-  email: { type: email, unique: true }
-  role: { type: select, options: [admin, user] }
-```
-
-This metadata is loaded at runtime to:
-*   Auto-generate database schemas (tables/collections).
-*   Auto-generate TypeScript types.
-*   Auto-validate incoming requests.
-
-### 3. Logic as Graph
-Your application logic isn't hidden inside controller functions. It's attached to the Graph as **Hooks** and **Actions**.
-
-*   **Hook**: "When `user` is created, send email."
-*   **Action**: "Expose RPC `resetPassword` on `user`."
-
-## Why use ObjectQL?
-
-*   **For AI**: It demands structured input/output, which fits AI Agent capabilities perfectly.
-*   **For Low-Code**: The rigorous structure makes it easy to build UI visual editors on top of it.
-*   **For Microservices**: The federation protocol allows you to stitch multiple services into one graph instantly.
-
-## 📡 API Access
-
-ObjectQL exposes your data through multiple API styles:
-
-*   **[Complete API Reference](../api/README.md)** - Comprehensive guide to all endpoints
-*   **[JSON-RPC API](../api/README.md#json-rpc-style-api)** - Universal protocol for all operations
-*   **[REST API](../api/README.md#rest-style-api)** - Traditional REST endpoints
-*   **[Metadata API](../api/README.md#metadata-api)** - Runtime schema discovery
-*   **[Authentication Guide](../api/authentication.md)** - Securing your APIs
-
-## Next Steps
-
-*   [**Getting Started**](./getting-started.md): Build your first ObjectQL app
-*   [**CLI Tool**](./cli.md): Using the command line interface for codegen
-*   [**API Reference**](../api/README.md): Complete API documentation
diff --git a/docs/guide/license.md b/docs/guide/license.md
deleted file mode 100644
index de394337..00000000
--- a/docs/guide/license.md
+++ /dev/null
@@ -1,64 +0,0 @@
-# License
-
-ObjectQL is released under the **MIT License**.
-
-## About This License
-
-The MIT License is one of the most permissive and widely-used open source licenses. It:
-
-- ✅ **Allows** you to use, modify, and distribute the software freely
-- ✅ **Permits** commercial use without restrictions
-- ✅ **Enables** you to sublicense and use in proprietary software
-- ✅ **Requires** only that you include the copyright notice and license text
-- ✅ **Provides** no warranty (software is provided "as is")
-
-This license maximizes freedom while protecting the copyright holders from liability.
-
-## Full License Text
-
-The complete license text is available in the [LICENSE](https://github.com/objectql/objectql/blob/main/LICENSE) file in the repository.
-
-You can also view the official MIT License at:
-[https://opensource.org/licenses/MIT](https://opensource.org/licenses/MIT)
-
-## Key Points
-
-### What You Can Do
-
-- **Use** ObjectQL in your applications and projects (personal or commercial)
-- **Modify** the source code to fit your needs
-- **Distribute** copies of ObjectQL (with proper attribution)
-- **Sublicense** and incorporate into proprietary software
-- **Sell** products built with or based on ObjectQL
-- **Use** ObjectQL in competitive products
-
-### What You Must Do
-
-- **Include** the original copyright notice and license text when distributing the software
-- **Provide** attribution to ObjectQL Contributors
-
-### What the License Does Not Provide
-
-- **No warranty**: The software is provided "as is" without warranty of any kind
-- **No liability**: Authors are not liable for any claims or damages arising from use of the software
-
-### Important Notes
-
-1. **Attribution Required**: You must include the copyright notice and license text in all copies or substantial portions of the software
-2. **No Patent Grant**: Unlike some other licenses (e.g., Apache 2.0), the MIT License does not explicitly grant patent rights
-3. **Simple and Permissive**: One of the shortest and most permissive licenses available
-
-## Questions?
-
-If you have questions about the license or how it applies to your use case, please:
-
-- Open a [GitHub Discussion](https://github.com/objectql/objectql/discussions)
-- Review the official [Open Source Initiative documentation](https://opensource.org/licenses/MIT)
-
-## Copyright Notice
-
-```
-MIT License
-
-Copyright (c) 2026 ObjectQL Contributors (https://github.com/objectql)
-```
diff --git a/docs/guide/logic-actions.md b/docs/guide/logic-actions.md
deleted file mode 100644
index 9ed768be..00000000
--- a/docs/guide/logic-actions.md
+++ /dev/null
@@ -1,199 +0,0 @@
-# Logic: Actions (RPC)
-
-Actions (Remote Procedure Calls) allow you to define custom backend functions that go beyond simple CRUD. They are integrated into the metadata, meaning the Frontend knows exactly how to render them (buttons, confirmation dialogs, forms) and the Backend knows how to validate them.
-
-## 1. What is an Action?
-
-Unlike a Hook (which reacts to CRUD events), an **Action** is explicitly invoked by a user or a system.
-
-| Feature | Action | Hook |
-| :--- | :--- | :--- |
-| **Trigger** | Explicit (Button, API Call) | Implicit (Database Event) |
-| **Input** | Custom Arguments (`params`) | Database Record |
-| **Output** | Custom Result (JSON) | None (Void) |
-| **Use Case** | "Approve Invoice", "Sync LDAP" | "Validation", "Audit Log" |
-
-## 2. Defining Actions
-
-Actions require two parts:
-1.  **Declaration**: in `*.object.yml` (Defines the "Interface" & "UI").
-2.  **Implementation**: in `*.action.ts` (Defines the "Logic").
-
-### Step 1: Declare in YAML
-
-Define the action's signature in the Object file.
-
-```yaml
-# invoice.object.yml
-actions:
-  mark_paid:
-    type: record           # 'record' = acts on a specific row (needs ID)
-    label: Mark as Paid
-    icon: standard:money
-    confirm_text: "Are you sure? This will trigger a receipt email."
-    params:                # Input arguments (Schema)
-      note:
-        type: textarea
-        label: Payment Note
-        required: false
-      method:
-        type: select
-        options: [cash, card, transfer]
-        default: transfer
-
-  import_csv:
-    type: global           # 'global' = acts on the collection
-    label: Import Invoices
-    params:
-      file_url:
-        type: text
-```
-
-### Step 2: Implement in TypeScript
-
-Create a corresponding `.action.ts` file in the same directory.
-Use the `ActionDefinition` type for full type safety.
-
-```typescript
-// invoice.action.ts
-import { ActionDefinition } from '@objectql/types';
-// import { Invoice } from './types'; // generated types
-
-interface PayInput {
-    note?: string;
-    method: 'cash' | 'card' | 'transfer';
-}
-
-export const mark_paid: ActionDefinition<any, PayInput> = {
-    handler: async ({ id, input, api, user, objectName }) => {
-        // 1. Fetch current state
-        const invoice = await api.findOne(objectName, id);
-        if (!invoice) throw new Error("Invoice not found");
-        
-        if (invoice.status === 'Paid') {
-            throw new Error("Invoice is already paid.");
-        }
-
-        // 2. Perform updates
-        await api.update(objectName, id, {
-            status: 'Paid',
-            payment_method: input.method,
-            payment_note: input.note,
-            paid_by: user?.id,
-            paid_at: new Date()
-        });
-
-        // 3. Return result to UI
-        return { 
-            success: true, 
-            message: `Invoice #${invoice.code} marked as paid.` 
-        };
-    }
-};
-
-interface ImportInput {
-    file_url: string;
-}
-
-export const import_csv: ActionDefinition<any, ImportInput> = {
-    handler: async ({ input, api }) => {
-        // Logic to download CSV and parse it...
-        return { count: 100 };
-    }
-};
-```
-
-## 3. Action Context (`ctx`)
-
-The `handler` function receives a single context object with the following properties:
-
-| Property | Type | Description |
-| :--- | :--- | :--- |
-| `objectName` | `string` | The API name of the object (e.g., `invoice`). |
-| `actionName` | `string` | The API name of the action (e.g., `mark_paid`). |
-| `id` | `string \| number` | **(Record Actions only)** The ID of the target record. |
-| `input` | `T` | The validated arguments passed by the caller. |
-| `api` | `HookAPI` | Database API (`find`, `create`, `update`, `delete`, `count`). |
-| `user` | `object` | The current session user (contains `id`, `name`, etc.). |
-
-## 4. Parameter Types
-
-The `params` section in YAML supports the same types as Object Fields. This allows the Frontend to auto-generate beautiful forms.
-
-*   `text`, `textarea`, `number`, `boolean`, `date`, `datetime`
-*   `select` (Dropdown)
-*   `lookup` (Reference to another object)
-*   `file` (Attachment)
-
-**Example: Lookup Parameter**
-```yaml
-params:
-  assign_to:
-    type: lookup
-    reference: user
-    label: Assign To Staff
-```
-
-## 5. Invoking Actions
-
-### A. Via Server-Side Code (`app.executeAction`)
-
-You can call actions from other parts of your backend (e.g., Cron jobs, Webhooks).
-
-```typescript
-// Cron Job
-await app.executeAction('invoice', 'mark_paid', {
-    id: 'inv_123',
-    input: {
-        method: 'card', 
-        note: 'Auto-processed'
-    },
-    user: { id: 'system' } // Simulate a user
-});
-```
-
-### B. Via HTTP API (RPC)
-
-ObjectQL Server uses a unified RPC endpoint (typically mounted at `/api/objectql`).
-
-```http
-POST /api/objectql
-Content-Type: application/json
-
-{
-    "op": "action",
-    "object": "invoice",
-    "args": {
-        "action": "mark_paid",
-        "id": "inv_123",
-        "input": {
-            "method": "cash",
-            "note": "Paid at counter"
-        }
-    }
-}
-```
-
-> **Note on Versioning:** It is recommended to mount the ObjectQL handler under a versioned prefix like `/api/v1/objectql` in your Express/Node app to manage future breaking changes.
-
-### C. Via Frontend SDK
-
-```javascript
-// React / Client Code
-await objectql.action('invoice', 'mark_paid').call({
-    id: recordId,
-    input: { method: 'cash' }
-});
-```
-
-## 6. Transaction Safety
-
-By default, Actions are **NOT** automatically wrapped in a database transaction. If you need atomicity (all-or-nothing), you should manage it manually, or if using a driver that supports it, rely on the `api` methods which might share a transaction context if configured (though `HookAPI` is currently stateless).
-
-*Future versions of ObjectQL may introduce transactional decorators.*
-
-## 7. Best Practices
-
-1.  **Thin Controllers**: Keep your `.action.ts` handlers relatively thin. If the logic is complex, move it to a dedicated Service class.
-2.  **Input Validation**: Although ObjectQL checks types defined in YAML, always validate business rules (e.g., "Amount must be positive") inside the handler.
-3.  **Return JSON**: Always return a JSON serializable object. Do not return database cursors or complex class instances.
diff --git a/docs/guide/logic-hooks.md b/docs/guide/logic-hooks.md
deleted file mode 100644
index c9108029..00000000
--- a/docs/guide/logic-hooks.md
+++ /dev/null
@@ -1,184 +0,0 @@
-# Logic Hooks
-
-Hooks (often called "Triggers" in SQL databases) allow you to intercept database operations to inject custom logic. They are transaction-aware and fully typed.
-
-## 1. Registration Methods
-
-You can define hooks in two ways: **File-based** (Static) or **Programmatic** (Dynamic).
-
-### A. File-based (Recommended)
-Place a `*.hook.ts` file next to your object definition. The loader automatically discovers it.
-
-**File:** `src/objects/project.hook.ts`
-
-```typescript
-import { ObjectHookDefinition } from '@objectql/types';
-
-const hooks: ObjectHookDefinition = {
-    beforeCreate: async (ctx) => {
-        // ...
-    },
-    afterUpdate: async (ctx) => {
-        // ...
-    }
-};
-
-export default hooks;
-```
-
-### B. Programmatic (Dynamic)
-Use the `app.on()` API, typically inside a [Plugin](./plugins.md).
-
-```typescript
-app.on('before:create', 'project', async (ctx) => {
-    // ...
-});
-
-// Wildcard listener
-app.on('after:delete', '*', async (ctx) => {
-    console.log(`Object ${ctx.objectName} deleted record ${ctx.id}`);
-});
-```
-
-## 2. Event Lifecycle
-
-| Event Name | Description | Common Use Case |
-| :--- | :--- | :--- |
-| `before:create` | Before inserting a new record. | Validation, Default Values, ID generation. |
-| `after:create` | After insertion is committed. | Notifications, downstream sync. |
-| `before:update` | Before modifying an existing record. | Permission checks, Immutable field protection. |
-| `after:update` | After modification is committed. | Audit logging, history tracking. |
-| `before:delete` | Before removing a record. | Referential integrity checks. |
-| `after:delete` | After removal is committed. | Clean up related resources (e.g. S3 files). |
-| `before:find` | Before executing a query. | **Row-Level Security (RLS)**, Force filters. |
-| `after:find` | After fetching results. | Decryption, Sensitive data masking. |
-
-## 3. The Hook Context
-
-The context object (`ctx`) changes based on the event type.
-
-### Common Properties (Available Everywhere)
-
-| Property | Type | Description |
-| :--- | :--- | :--- |
-| `objectName` | `string` | The name of the object being operated on. |
-| `user` | `ObjectQLUser` | Current user session/context. |
-| `broker` | `IStation` | (If Microservices enabled) Station broker instance. |
-
-### Mutation Context (Create/Update/Delete)
-
-| Property | Type | Available In | Description |
-| :--- | :--- | :--- | :--- |
-| `data` | `Any` | Create/Update | The data payload being written. **Mutable**. |
-| `id` | `string` | Update/Delete | The ID of the record being acted upon. |
-| `previousData` | `Any` | Update/Delete | The existing record fetched from DB before operation. |
-| `result` | `Any` | After * | The final result returned from the driver. |
-
-### Query Context (Find)
-
-| Property | Type | Description |
-| :--- | :--- | :--- |
-| `query` | `steedos-filters` | The query AST (filters, fields, sort). **Mutable**. |
-| `result` | `Any[]` | (After Find) The array of records found. **Mutable**. |
-
-## 4. Common Patterns & Examples
-
-### A. Validation & Default Values
-Throwing an error inside a `before` hook aborts the transaction.
-
-```typescript
-beforeCreate: async ({ data, user }) => {
-    if (data.amount < 0) {
-        throw new Error("Amount cannot be negative");
-    }
-    // Set default owner if not provided
-    if (!data.owner) {
-        data.owner = user.userId;
-    }
-}
-```
-
-### B. Immutable Fields Protection
-Prevent users from changing critical fields during update.
-
-```typescript
-beforeUpdate: async ({ data, previousData }) => {
-    if (data.code !== undefined && data.code !== previousData.code) {
-        throw new Error("Cannot change project code once created.");
-    }
-}
-```
-
-### C. Row-Level Security (RLS)
-The most secure place to enforce permissions is `before:find`. This injects filters into *every* query (API, GraphQL, or internal).
-
-```typescript
-beforeFind: async ({ query, user }) => {
-    if (!user.is_admin) {
-        // Enforce: owners can only see their own records
-        // Merging into existing filters
-        query.filters = [
-            (query.filters || []), 
-            ['owner', '=', user.userId]
-        ];
-    }
-}
-```
-
-### D. Side Effects (Notifications)
-Use `after` hooks for logic that strictly relies on success.
-
-```typescript
-afterCreate: async ({ data, objectName }) => {
-    await NotificationService.send({
-        to: data.owner,
-        message: `New ${objectName} created.`
-    });
-}
-```
-
-### E. Result Masking
-Hide sensitive fields based on rules.
-
-```typescript
-afterFind: async ({ result, user }) => {
-    if (!user.has_permission('view_salary')) {
-        result.forEach(record => {
-            delete record.salary;
-            delete record.bonus;
-        });
-    }
-}
-```
-
-### F. Auto-Numbering / ID Generation
-Generate complex business keys.
-
-```typescript
-beforeCreate: async ({ data }) => {
-    if (!data.code) {
-        data.code = await SequenceService.next('PROJECT_CODE');
-    }
-}
-```
-
-### G. Conditional Deletion
-Use `previousData` in delete hooks to prevent deleting records based on their state.
-
-```typescript
-beforeDelete: async ({ previousData, user }) => {
-    // Prevent deletion if project is active
-    if (previousData.status === 'active') {
-         throw new Error("Cannot delete an active project. Archive it first.");
-    }
-}
-```
-
-## 5. Transaction Safety
-
-Hooks participate in the database transaction.
-*   If a `before` hook throws -> The DB operation is never executed.
-*   If the DB operation fails -> `after` hooks are never executed.
-*   If an `after` hook throws -> **The entire transaction rolls back** (including the DB write).
-
-> **Tip:** If you want a "Fire and Forget" action that shouldn't rollback the transaction (e.g. sending an email), wrap your logic in a `try/catch` or execute it without `await`.
diff --git a/docs/guide/metadata-organization.md b/docs/guide/metadata-organization.md
deleted file mode 100644
index 299bd2e4..00000000
--- a/docs/guide/metadata-organization.md
+++ /dev/null
@@ -1,365 +0,0 @@
-# Organizing Metadata for Large Projects
-
-When building enterprise-scale applications with ObjectQL, proper metadata organization becomes critical. This guide demonstrates best practices for structuring your object definitions, actions, hooks, and translations in a maintainable way.
-
-## The Challenge
-
-As your application grows beyond 30-50 objects, a flat file structure becomes problematic:
-
-**Problems with Flat Structure:**
-```
-src/objects/
-├── user.object.yml
-├── organization.object.yml
-├── account.object.yml
-├── contact.object.yml
-├── opportunity.object.yml
-├── employee.object.yml
-├── department.object.yml
-├── invoice.object.yml
-├── payment.object.yml
-├── project.object.yml
-├── task.object.yml
-... (100+ files)
-```
-
-- ❌ Hard to find related objects
-- ❌ Merge conflicts when multiple teams work simultaneously
-- ❌ Unclear ownership boundaries
-- ❌ Can't deploy modules independently
-- ❌ Difficult to understand relationships
-
-## Recommended Structure: Domain-Driven Modules
-
-For applications with **30+ objects** and **multiple teams**, organize by business domain:
-
-```
-src/
-├── core/                    # Foundation objects (user, org, etc.)
-│   ├── objects/
-│   ├── i18n/
-│   └── index.ts
-│
-├── modules/                 # Business domain modules
-│   ├── crm/                # Customer management
-│   │   ├── objects/
-│   │   ├── actions/
-│   │   ├── hooks/
-│   │   ├── i18n/
-│   │   ├── README.md
-│   │   └── index.ts
-│   │
-│   ├── hr/                 # Human resources
-│   ├── finance/            # Finance & accounting
-│   └── project/            # Project management
-│
-├── extensions/             # Custom overrides
-├── shared/                 # Shared utilities
-└── index.ts               # Application entry
-```
-
-## Real-World Example
-
-See the complete working example at:
-```
-packages/starters/enterprise/
-```
-
-This demonstrates:
-- ✅ 20+ objects organized across 5 modules
-- ✅ Domain-driven structure (CRM, HR, Finance, Project)
-- ✅ Cross-module relationships
-- ✅ Extension pattern for customization
-- ✅ Comprehensive indexing strategy
-- ✅ Multi-language support (en, zh-CN)
-- ✅ Module documentation
-
-## Module Anatomy
-
-Each module follows a consistent pattern:
-
-```
-modules/[domain]/
-├── objects/              # Object definitions
-│   ├── [object1].object.yml
-│   └── [object2].object.yml
-├── actions/              # Custom actions
-│   └── [object1].action.ts
-├── hooks/                # Lifecycle hooks
-│   └── [object1].hooks.ts
-├── i18n/                 # Translations
-│   ├── en/
-│   └── zh-CN/
-├── README.md             # Module documentation
-└── index.ts              # Module exports
-```
-
-### Module Documentation Template
-
-Each module should have a README explaining:
-
-1. **Overview** - What business domain it covers
-2. **Objects** - List of objects with descriptions
-3. **Relationships** - How objects relate to each other
-4. **Team Ownership** - Who maintains this module
-5. **Dependencies** - What other modules/objects it depends on
-6. **Usage Examples** - Common query patterns
-
-## Object Naming Conventions
-
-### File-Based Naming
-
-**ObjectQL uses filename-based identification.** The object name is automatically inferred from the filename (without the `.object.yml` extension), eliminating redundancy.
-
-**Examples:**
-- `crm_account.object.yml` → Object name: `crm_account`
-- `finance_invoice.object.yml` → Object name: `finance_invoice`
-- `project_task.object.yml` → Object name: `project_task`
-
-Inside the file, you **no longer need** to specify `name: crm_account` - it's inferred from the filename!
-
-```yaml
-# File: crm_account.object.yml
-# Object name "crm_account" is automatically inferred!
-
-label: CRM Account
-fields:
-  company_name:
-    type: text
-    required: true
-```
-
-### Prefixing Strategy
-
-For large projects with multiple modules, use prefixes in your **filenames** to avoid name collisions:
-
-```
-# ✅ Good: Clear module ownership via filenames
-crm/objects/crm_account.object.yml       → Object: crm_account
-finance/objects/finance_invoice.object.yml → Object: finance_invoice
-project/objects/project_task.object.yml   → Object: project_task
-
-# ❌ Avoid: Risk of collision
-crm/objects/account.object.yml           → Object: account (ambiguous)
-finance/objects/account.object.yml       → Object: account (collision!)
-```
-
-**When to prefix:**
-- ✅ Multi-module applications (30+ objects)
-- ✅ Plugin architectures
-- ✅ When similar concepts exist across domains
-
-**When NOT to prefix:**
-- ❌ Core shared objects (`user.object.yml`, `organization.object.yml`)
-- ❌ Small applications (< 30 objects)
-- ❌ When it reduces clarity
-
-## Dependency Management
-
-### Dependency Layers
-
-```
-┌─────────────────────────────────┐
-│   Application Layer             │
-│   (modules/*)                   │
-│   - Can depend on Core          │
-│   - Can depend on other modules │
-└─────────────────────────────────┘
-           ↓
-┌─────────────────────────────────┐
-│   Foundation Layer              │
-│   (core/*)                      │
-│   - No dependencies             │
-│   - Used by everyone            │
-└─────────────────────────────────┘
-```
-
-### Cross-Module References
-
-When modules need to reference each other's objects:
-
-```yaml
-# In modules/finance/objects/invoice.object.yml
-fields:
-  account:
-    type: lookup
-    reference_to: crm_account  # Reference to CRM module
-```
-
-**Best Practices:**
-1. Document cross-module dependencies in module README
-2. Avoid circular dependencies
-3. Use core objects to break dependency cycles
-4. Consider extracting shared concepts to core layer
-
-## Index Strategy by Module
-
-Different modules have different performance requirements:
-
-### High-Traffic Modules (CRM, Sales)
-```yaml
-# Aggressive indexing
-fields:
-  status: { type: select, index: true }
-  owner: { type: lookup, index: true }
-  created_at: { type: datetime, index: true }
-
-indexes:
-  owner_status_idx: { fields: [owner, status] }
-  status_created_idx: { fields: [status, created_at] }
-```
-
-### Low-Traffic Modules (Admin, Config)
-```yaml
-# Minimal indexing
-fields:
-  name: { type: text, index: true }
-  status: { type: select, index: true }
-# Add more indexes only when needed
-```
-
-## Extension Pattern
-
-Use extensions to customize objects without modifying source files.
-
-**Original** (`core/objects/user.object.yml`):
-```yaml
-# File: user.object.yml
-# Object name "user" is inferred from filename
-
-fields:
-  name: { type: text }
-  email: { type: text }
-```
-
-**Extension** (`extensions/user.extension.object.yml`):
-```yaml
-# File: user.extension.object.yml
-# Extends the "user" object (matches by filename base)
-
-fields:
-  employee_id: { type: text }
-  email: { required: true, unique: true }
-```
-
-**Result:** ObjectQL merges both definitions, adding `employee_id` and making `email` required.
-
-## Internationalization at Scale
-
-### Three-Layer i18n Strategy
-
-```
-1. Core Layer (core/i18n/)
-   → Shared objects (user, organization)
-   
-2. Module Layer (modules/[domain]/i18n/)
-   → Domain-specific objects
-   
-3. Extension Layer (extensions/i18n/)
-   → Customer/regional customizations
-```
-
-### Directory Structure
-```
-core/i18n/
-  en/core.json
-  zh-CN/core.json
-
-modules/crm/i18n/
-  en/crm.json
-  zh-CN/crm.json
-```
-
-## Migration Path
-
-### From Flat to Modular
-
-**Step 1: Analyze**
-Group existing objects by business domain.
-
-**Step 2: Plan**
-Create module structure, decide on prefixes.
-
-**Step 3: Migrate Gradually**
-```
-src/
-├── objects/          # Legacy (keep temporarily)
-├── modules/          # New structure
-│   └── crm/          # Start with one module
-└── index.ts          # Loads from both
-```
-
-**Step 4: Update References**
-Update imports and references to use new module structure.
-
-**Step 5: Clean Up**
-Remove legacy flat structure once migration is complete.
-
-## Project Size Guidelines
-
-| Size | Objects | Teams | Recommended Structure |
-|------|---------|-------|----------------------|
-| **Small** | 1-30 | 1 | Flat `objects/` directory |
-| **Medium** | 30-100 | 2-3 | Domain modules |
-| **Large** | 100-500 | 5-10 | Modules + plugins |
-| **Enterprise** | 500+ | 10+ | Monorepo with packages |
-
-## Testing Strategy
-
-### Module Tests
-```typescript
-// modules/crm/__tests__/integration.test.ts
-describe('CRM Module', () => {
-  it('should handle lead conversion', async () => {
-    const lead = await createLead();
-    await convertLead(lead.id);
-    // Verify account, contact, opportunity created
-  });
-});
-```
-
-### Object Schema Tests
-```typescript
-// modules/crm/objects/__tests__/account.test.ts
-describe('Account Object', () => {
-  it('should have required fields', () => {
-    const schema = loadObjectSchema('crm_account');
-    expect(schema.fields.name.required).toBe(true);
-  });
-});
-```
-
-## Complete Working Example
-
-Explore the full example with 20+ objects:
-```bash
-cd packages/starters/enterprise
-pnpm install
-pnpm build
-```
-
-The example includes:
-- Core module (user, organization, attachment)
-- CRM module (account, contact, opportunity, lead)
-- HR module (employee, department, position, timesheet)
-- Finance module (invoice, payment, expense, budget)
-- Project module (project, task, milestone, timesheet entry)
-- Extensions pattern
-- Multi-language support
-- Comprehensive documentation
-
-## Key Takeaways
-
-1. **Start simple** - Don't over-engineer for small projects
-2. **Think in domains** - Organize by business capability, not technical layers
-3. **Document boundaries** - Make module ownership and dependencies explicit
-4. **Plan for scale** - Use prefixes and modules when you hit 30-50 objects
-5. **Test modules** - Each module should be testable independently
-6. **Version control** - Use module-level versioning for independent deployments
-
-## See Also
-
-- [Data Modeling Guide](./data-modeling.md)
-- [Plugin Development](./plugins.md)
-- [Logic Hooks](./logic-hooks.md)
-- [Complete Example](../../packages/starters/enterprise/)
diff --git a/docs/guide/microservices.md b/docs/guide/microservices.md
deleted file mode 100644
index a4a8f112..00000000
--- a/docs/guide/microservices.md
+++ /dev/null
@@ -1,61 +0,0 @@
-# Microservices & Federation
-
-ObjectQL provides a built-in mechanism to aggregate data from multiple services into a single unified graph. This is similar to **GraphQL Federation** or Salesforce's **External Objects**, but strictly for the ObjectQL protocol.
-
-## Concept: Remote Remotes
-
-You can configure an ObjectQL instance to act as a **Gateway**. It connects to other ObjectQL instances, downloads their metadata (Schema), and automatically creates proxy drivers for them.
-
-*   **Source of Truth**: The microservice defines the object (`user.object.yml`).
-*   **Proxy**: The gateway sees a virtual object (`user`) and forwards all queries (Find, Update, Actions) to the microservice.
-
-## Configuration
-
-### The Subgraph (Service A)
-
-This is a standard ObjectQL service running standard drivers (SQL/Mongo).
-It must expose the metadata API (default in `@objectql/server`).
-
-```typescript
-// user-service/index.ts
-const app = new ObjectQL({
-    source: './src/objects', // Defines 'user', 'role'
-    datasources: { ... }
-});
-// Exposes http://user-service:3000/api/metadata/objects
-```
-
-### The Gateway
-
-The gateway aggregates multiple services.
-
-```typescript
-// gateway/index.ts
-const app = new ObjectQL({
-    // No local source needed, just remotes
-    remotes: [
-        'http://user-service:3000',
-        'http://order-service:3000'
-    ]
-});
-
-await app.init();
-```
-
-### Usage
-
-Once initialized, the Gateway behaves exactly like a monolith.
-
-```typescript
-// Code running on Gateway
-// Transparently forwards request to User Service via HTTP
-const users = await app.object('user').find({
-    filters: [['status', '=', 'active']]
-});
-```
-
-## Benefits
-
-1.  **Decoupling**: Services manage their own schema migrations and domain logic.
-2.  **Unity**: Frontend or upper layers see a single API surface.
-3.  **Hybrid**: A Gateway can *also* have local objects. You can mix "local cache tables" with "remote live tables" in the same application.
diff --git a/docs/guide/migration-id-field.md b/docs/guide/migration-id-field.md
deleted file mode 100644
index a0b58785..00000000
--- a/docs/guide/migration-id-field.md
+++ /dev/null
@@ -1,294 +0,0 @@
-# Migration Guide: Unified ID Field
-
-This guide helps you migrate from the legacy `_id` field to the unified `id` field API.
-
-## What Changed?
-
-ObjectQL now provides a **unified `id` field** across all database drivers:
-
-- **Before**: MongoDB used `_id`, SQL used `id` - inconsistent API
-- **After**: Both drivers use `id` at the API level - consistent API
-
-The MongoDB driver now automatically maps between `id` (API) and `_id` (database) internally.
-
-## Benefits
-
-✅ **Consistent API**: Write database-agnostic code  
-✅ **Easier Migration**: Switch between MongoDB and SQL without code changes  
-✅ **Better Developer Experience**: No need to remember which driver uses which field  
-✅ **Backward Compatible**: Legacy `_id` usage still works (MongoDB only)
-
-## Migration Steps
-
-### 1. Update Filters
-
-**Before:**
-```typescript
-// MongoDB-specific code
-const query = {
-  filters: [['_id', '=', 'user-123']]
-};
-```
-
-**After:**
-```typescript
-// Works with both MongoDB and SQL
-const query = {
-  filters: [['id', '=', 'user-123']]
-};
-```
-
-### 2. Update Document Creation
-
-**Before:**
-```typescript
-// MongoDB-specific code
-const user = await app.create('users', {
-  _id: 'user-123',
-  name: 'Alice'
-});
-```
-
-**After:**
-```typescript
-// Works with both MongoDB and SQL
-const user = await app.create('users', {
-  id: 'user-123',
-  name: 'Alice'
-});
-```
-
-### 3. Update Field Access in Results
-
-**Before:**
-```typescript
-const users = await app.find('users', {});
-console.log(users[0]._id); // MongoDB
-console.log(users[0].id);  // SQL
-```
-
-**After:**
-```typescript
-const users = await app.find('users', {});
-console.log(users[0].id);  // Works for both MongoDB and SQL
-```
-
-### 4. Update Sorting
-
-**Before:**
-```typescript
-const query = {
-  sort: [['_id', 'desc']]  // MongoDB-specific
-};
-```
-
-**After:**
-```typescript
-const query = {
-  sort: [['id', 'desc']]  // Works for both
-};
-```
-
-### 5. Update Field Projection
-
-**Before:**
-```typescript
-const query = {
-  fields: ['_id', 'name', 'email']  // MongoDB-specific
-};
-```
-
-**After:**
-```typescript
-const query = {
-  fields: ['id', 'name', 'email']  // Works for both
-};
-```
-
-## Automated Migration
-
-You can use a find-and-replace tool to migrate your codebase:
-
-### Search Patterns
-
-1. **In Filters**: `['_id',` → `['id',`
-2. **In Objects**: `_id:` → `id:`
-3. **In Access**: `.\_id` → `.id`
-4. **In Fields**: `'_id'` → `'id'`
-
-### Example Script
-
-```bash
-# Search for _id usage in your codebase
-grep -r "_id" src/
-
-# Use your editor's find-and-replace with caution
-# Or use a tool like:
-find src/ -type f -name "*.ts" -exec sed -i "s/\['_id'/\['id'/g" {} +
-```
-
-**⚠️ Warning**: Always review changes manually and test thoroughly after automated replacement.
-
-## Backward Compatibility
-
-### MongoDB Driver
-
-The MongoDB driver maintains **full backward compatibility** for `_id` usage:
-
-- `_id` in **filters** is automatically mapped to MongoDB's `_id`
-- `_id` in **sorting** is automatically mapped to MongoDB's `_id`
-- `_id` in **field projections** is automatically mapped to MongoDB's `_id`
-- `_id` in **create operations** is mapped to `id`
-- Results **always** return `id` (not `_id`)
-
-**Example:**
-```typescript
-// Legacy code - fully supported for backward compatibility
-const query = {
-  filters: [['_id', '=', 'user-123']],
-  sort: [['_id', 'desc']],
-  fields: ['_id', 'name', 'email']
-};
-const users = await app.find('users', query);
-
-// Results use 'id' (not '_id')
-console.log(users[0].id); // 'user-123'
-console.log(users[0]._id); // undefined
-```
-
-**No Breaking Changes:** Your existing queries using `_id` will continue to work without modification. However, migrating to `id` is recommended for:
-- Consistency with SQL drivers
-- Database portability
-- Future-proofing your code
-
-### SQL Driver
-
-The SQL driver has always used `id`, so no migration needed for SQL-only codebases.
-
-For codebases using MongoDB-style `_id` with SQL:
-```typescript
-// Legacy code with _id
-const user = await app.create('users', {
-  _id: 'user-123',  // Automatically mapped to 'id'
-  name: 'Alice'
-});
-
-// Result uses 'id'
-console.log(user.id); // 'user-123'
-```
-
-## Testing Your Migration
-
-After migrating, verify the following:
-
-### 1. Create Operations
-```typescript
-const user = await app.create('users', {
-  id: 'test-123',
-  name: 'Test User'
-});
-assert(user.id === 'test-123');
-assert(user._id === undefined); // Should not have _id
-```
-
-### 2. Find Operations
-```typescript
-const users = await app.find('users', {
-  filters: [['id', '=', 'test-123']]
-});
-assert(users[0].id === 'test-123');
-```
-
-### 3. Update Operations
-```typescript
-await app.update('users', 'test-123', {
-  name: 'Updated Name'
-});
-const updated = await app.findOne('users', 'test-123');
-assert(updated.name === 'Updated Name');
-```
-
-### 4. Sort and Projection
-```typescript
-const users = await app.find('users', {
-  fields: ['id', 'name'],
-  sort: [['id', 'asc']]
-});
-assert(users[0].id !== undefined);
-assert(users[0]._id === undefined);
-```
-
-## Database Migration
-
-### MongoDB Collections
-
-No database migration needed! The MongoDB driver:
-- Continues to use `_id` in the database (MongoDB requirement)
-- Automatically maps `id` ↔ `_id` at the driver level
-- Existing data works without changes
-
-### SQL Tables
-
-If you have legacy SQL tables using `_id` as the primary key:
-
-```sql
--- The driver will detect and automatically recreate tables
--- But you can also migrate manually:
-
--- Option 1: Rename column (PostgreSQL)
-ALTER TABLE users RENAME COLUMN _id TO id;
-
--- Option 2: Create new table and migrate data
-CREATE TABLE users_new (
-  id VARCHAR(255) PRIMARY KEY,
-  name VARCHAR(255),
-  -- ... other columns
-);
-
-INSERT INTO users_new (id, name, ...)
-SELECT _id, name, ... FROM users;
-
-DROP TABLE users;
-ALTER TABLE users_new RENAME TO users;
-```
-
-## Common Issues
-
-### Issue: `undefined` for `id` field
-
-**Cause**: Using old code that accesses `_id` on results
-
-**Solution**: Change `result._id` to `result.id`
-
-### Issue: Filters not working
-
-**Cause**: Still using `_id` in filter arrays
-
-**Solution**: Change `['_id', '=', value]` to `['id', '=', value]`
-
-### Issue: Custom ID not working in MongoDB
-
-**Cause**: Passing `_id` instead of `id` in create
-
-**Solution**: Change `{ _id: 'custom' }` to `{ id: 'custom' }`
-
-## Need Help?
-
-If you encounter issues during migration:
-
-1. Check the [Driver Documentation](./drivers/index.md)
-2. Review the [API Reference](../api/README.md)
-3. Open an issue on [GitHub](https://github.com/objectql/objectql/issues)
-
-## Summary
-
-| Aspect | Before (Legacy) | After (Unified) |
-|--------|----------------|-----------------|
-| MongoDB Filter | `['_id', '=', '123']` | `['id', '=', '123']` |
-| SQL Filter | `['id', '=', '123']` | `['id', '=', '123']` |
-| MongoDB Create | `{ _id: '123', ... }` | `{ id: '123', ... }` |
-| SQL Create | `{ id: '123', ... }` | `{ id: '123', ... }` |
-| MongoDB Result | `result._id` | `result.id` |
-| SQL Result | `result.id` | `result.id` |
-
-**Recommendation**: Migrate all code to use `id` for maximum consistency and portability.
diff --git a/docs/guide/page-metadata.md b/docs/guide/page-metadata.md
deleted file mode 100644
index 02fa23be..00000000
--- a/docs/guide/page-metadata.md
+++ /dev/null
@@ -1,671 +0,0 @@
-# Page Metadata Guide
-
-Page metadata in ObjectQL allows you to define custom UI pages declaratively using YAML files. This approach is inspired by low-code platforms like Airtable, Retool, and Appsmith, making it easy to create rich, data-driven interfaces without writing custom frontend code.
-
-## Overview
-
-Pages are the visual interface layer in ObjectQL applications. They define how data is displayed, how users interact with it, and how components are arranged on the screen.
-
-### Key Features
-
-- **Declarative Configuration**: Define pages using simple YAML files
-- **Multiple Layout Types**: Support for various layouts (dashboard, forms, wizards, etc.)
-- **Component-Based**: Compose pages from reusable components
-- **Data Binding**: Connect components to ObjectQL data sources
-- **Responsive Design**: Built-in responsive configuration
-- **Access Control**: Fine-grained permission management
-- **AI-Ready**: AI context for intelligent page generation
-
-## Quick Start
-
-Create a new page by adding a `*.page.yml` file to your project:
-
-```yaml
-# src/dashboard.page.yml
-name: dashboard
-label: Project Dashboard
-description: Overview of projects and tasks
-icon: dashboard
-layout: dashboard
-
-components:
-  - id: total_projects
-    type: metric
-    label: Total Projects
-    data_source:
-      object: projects
-      query:
-        op: count
-    grid:
-      x: 0
-      y: 0
-      w: 3
-      h: 2
-  
-  - id: recent_tasks
-    type: data_grid
-    label: Recent Tasks
-    data_source:
-      object: tasks
-      fields: ['name', 'status', 'due_date']
-      sort: [['created_at', 'desc']]
-      limit: 10
-    grid:
-      x: 0
-      y: 2
-      w: 12
-      h: 6
-```
-
-## Page Configuration
-
-### Basic Structure
-
-Every page must have these core properties:
-
-```yaml
-name: page_identifier        # Unique identifier
-label: Display Name          # Human-readable name
-layout: single_column        # Layout type
-```
-
-### Layout Types
-
-ObjectQL supports multiple layout types for different use cases:
-
-#### 1. Single Column Layout
-```yaml
-layout: single_column
-components:
-  - id: header
-    type: text
-    label: Welcome
-  - id: data_table
-    type: data_grid
-    data_source:
-      object: tasks
-```
-
-Best for: Simple forms, lists, detail views
-
-#### 2. Two Column Layout
-```yaml
-layout: two_column
-sections:
-  - id: main_content
-    type: content
-    style:
-      width: 70%
-    components:
-      - id: edit_form
-        type: form
-        # ...
-  
-  - id: sidebar
-    type: sidebar
-    style:
-      width: 30%
-    components:
-      - id: stats
-        type: metric
-        # ...
-```
-
-Best for: Detail pages with sidebar, master-detail views
-
-#### 3. Dashboard Layout
-```yaml
-layout: dashboard
-components:
-  - id: metric_1
-    type: metric
-    grid:
-      x: 0    # Grid column (0-11)
-      y: 0    # Grid row
-      w: 3    # Width (grid units)
-      h: 2    # Height (grid units)
-  
-  - id: chart_1
-    type: chart
-    grid:
-      x: 3
-      y: 0
-      w: 6
-      h: 4
-```
-
-Best for: Dashboards, KPI displays, analytics pages
-
-#### 4. Wizard Layout
-```yaml
-layout: wizard
-components:
-  - id: step_1
-    type: container
-    label: Basic Info
-    config:
-      step: 1
-    components:
-      - id: form_1
-        type: form
-        # ...
-  
-  - id: step_2
-    type: container
-    label: Details
-    config:
-      step: 2
-    components:
-      - id: form_2
-        type: form
-        # ...
-```
-
-Best for: Multi-step processes, onboarding, complex forms
-
-#### 5. Canvas Layout
-```yaml
-layout: canvas
-components:
-  - id: hero
-    type: container
-    style:
-      position: absolute
-      top: 0
-      left: 0
-      width: 100%
-      height: 400px
-    # ...
-```
-
-Best for: Landing pages, custom layouts
-
-#### 6. Tabs Layout
-```yaml
-layout: tabs
-components:
-  - id: tab_1
-    type: container
-    label: Overview
-    components:
-      # Tab content
-  
-  - id: tab_2
-    type: container
-    label: Details
-    components:
-      # Tab content
-```
-
-Best for: Organizing related content
-
-## Components
-
-### Component Types
-
-ObjectQL provides a rich set of built-in component types:
-
-#### Data Display Components
-
-**Data Grid**
-```yaml
-- id: tasks_grid
-  type: data_grid
-  label: Tasks
-  data_source:
-    object: tasks
-    fields: ['name', 'status', 'priority', 'due_date']
-    sort: [['created_at', 'desc']]
-  config:
-    columns:
-      - field: name
-        label: Task Name
-        width: 300
-      - field: status
-        label: Status
-        badge: true
-    row_actions:
-      - label: Edit
-        action: edit_task
-    enable_search: true
-    enable_filters: true
-```
-
-**Detail View**
-```yaml
-- id: project_detail
-  type: detail_view
-  label: Project Details
-  data_source:
-    object: projects
-    query:
-      op: findOne
-      filter: [['_id', '=', '{{route.params.id}}']]
-  config:
-    mode: readonly
-    sections:
-      - label: Basic Info
-        fields: ['name', 'description', 'status']
-      - label: Timeline
-        fields: ['start_date', 'end_date']
-```
-
-**Metric/KPI**
-```yaml
-- id: total_count
-  type: metric
-  label: Total Projects
-  data_source:
-    object: projects
-    query:
-      op: count
-  config:
-    format: number
-    icon: folder
-    color: blue
-```
-
-**Chart**
-```yaml
-- id: status_chart
-  type: chart
-  label: Projects by Status
-  data_source:
-    object: projects
-    fields: ['status']
-    query:
-      op: group_by
-      field: status
-      aggregate: count
-  config:
-    chart_type: pie
-    colors: ['#10b981', '#3b82f6', '#f59e0b']
-```
-
-#### Data Input Components
-
-**Form**
-```yaml
-- id: edit_form
-  type: form
-  label: Edit Project
-  data_source:
-    object: projects
-  config:
-    mode: edit  # create, edit, or view
-    layout: vertical
-    fields:
-      - name: name
-        label: Project Name
-        type: text
-        required: true
-      - name: description
-        label: Description
-        type: textarea
-      - name: status
-        label: Status
-        type: select
-    field_layout:
-      - row: [name]
-      - row: [description]
-      - row: [status]
-  actions:
-    on_submit:
-      type: run_action
-      object: projects
-      action: update
-      success_message: Project updated
-```
-
-**Button**
-```yaml
-- id: submit_btn
-  type: button
-  label: Submit
-  config:
-    variant: primary
-    icon: check
-  actions:
-    on_click:
-      type: submit_form
-      success_message: Submitted successfully
-```
-
-#### Layout Components
-
-**Container**
-```yaml
-- id: section_1
-  type: container
-  label: Section Title
-  components:
-    - id: child_1
-      type: text
-      # ...
-```
-
-**Tabs**
-```yaml
-- id: tabs_container
-  type: tabs
-  components:
-    - id: tab_1
-      type: container
-      label: Tab 1
-      components: [...]
-    - id: tab_2
-      type: container
-      label: Tab 2
-      components: [...]
-```
-
-#### Content Components
-
-**Text**
-```yaml
-- id: welcome_text
-  type: text
-  config:
-    content: |
-      # Welcome to ObjectQL
-      This is a markdown-formatted text component.
-    format: markdown
-  style:
-    padding: 20px
-```
-
-**Image**
-```yaml
-- id: logo
-  type: image
-  config:
-    src: /assets/logo.png
-    alt: Company Logo
-  style:
-    width: 200px
-```
-
-**Divider**
-```yaml
-- id: separator
-  type: divider
-  style:
-    margin: 20px 0
-```
-
-## Data Sources
-
-Components can connect to ObjectQL data sources:
-
-### Basic Query
-```yaml
-data_source:
-  object: projects
-  fields: ['name', 'status', 'owner']
-  sort: [['created_at', 'desc']]
-  limit: 10
-```
-
-### Filtered Query
-```yaml
-data_source:
-  object: tasks
-  fields: ['name', 'due_date']
-  filters:
-    - ['status', '=', 'active']
-    - 'and'
-    - ['assigned_to', '=', '{{current_user.id}}']
-```
-
-### With Relationships
-```yaml
-data_source:
-  object: tasks
-  fields: ['name', 'status']
-  expand:
-    project:
-      fields: ['name']
-    assigned_to:
-      fields: ['name', 'email']
-```
-
-### Aggregations
-```yaml
-data_source:
-  object: projects
-  query:
-    op: count
-```
-
-```yaml
-data_source:
-  object: tasks
-  query:
-    op: group_by
-    field: status
-    aggregate: count
-```
-
-## Actions
-
-Components can trigger actions in response to user interactions:
-
-### Navigation
-```yaml
-actions:
-  on_click:
-    type: navigate
-    path: /projects/{{id}}
-```
-
-### Modal
-```yaml
-actions:
-  on_click:
-    type: open_modal
-    modal: edit_project_modal
-```
-
-### Execute Action
-```yaml
-actions:
-  on_click:
-    type: run_action
-    object: projects
-    action: archive
-    confirm: Archive this project?
-    success_message: Project archived
-```
-
-### Form Submission
-```yaml
-actions:
-  on_submit:
-    type: submit_form
-    success_message: Form submitted
-    on_error: show_toast
-```
-
-### Refresh Data
-```yaml
-actions:
-  on_load:
-    type: refresh
-```
-
-### Custom Handler
-```yaml
-actions:
-  on_click:
-    type: custom
-    handler: myCustomHandler
-```
-
-## Styling
-
-Components support flexible styling:
-
-```yaml
-style:
-  width: 100%
-  height: 400px
-  background: '#f7fafc'
-  padding: 20px
-  margin: 10px 0
-  border_radius: 8px
-  class_name: custom-class
-  custom_css:
-    box-shadow: 0 2px 4px rgba(0,0,0,0.1)
-```
-
-## Responsive Design
-
-Configure responsive behavior for different screen sizes:
-
-### Page-Level
-```yaml
-responsive:
-  mobile:
-    columns: 1
-  tablet:
-    columns: 2
-  desktop:
-    columns: 3
-```
-
-### Component-Level
-```yaml
-components:
-  - id: responsive_grid
-    type: data_grid
-    responsive:
-      mobile:
-        visible: true
-        columns: 1
-      tablet:
-        visible: true
-        columns: 2
-      desktop:
-        visible: true
-        columns: 3
-```
-
-## Access Control
-
-Define permissions for pages and components:
-
-### Page Permissions
-```yaml
-permissions:
-  view: ['admin', 'manager', 'user']
-  edit: ['admin', 'manager']
-```
-
-### Component Visibility
-```yaml
-components:
-  - id: admin_only
-    type: button
-    label: Delete
-    permissions: ['admin']
-    visible_when:
-      role: admin
-```
-
-## State Management
-
-Pages can maintain state:
-
-```yaml
-state:
-  initial:
-    current_tab: 0
-    selected_items: []
-    filter_value: ''
-  persist: true
-  storage_key: my_page_state
-```
-
-## AI Context
-
-Provide context for AI-powered features:
-
-```yaml
-ai_context:
-  intent: Manage project tasks and track progress
-  persona: Project managers and team members
-  tasks:
-    - View all tasks
-    - Create new tasks
-    - Update task status
-    - Assign tasks to team members
-```
-
-## Real-time Updates
-
-Enable real-time data updates:
-
-```yaml
-realtime: true
-refresh_interval: 30  # seconds
-```
-
-## SEO & Metadata
-
-Configure SEO metadata:
-
-```yaml
-meta:
-  title: Project Dashboard - My App
-  description: Manage your projects and tasks
-  keywords: ['projects', 'tasks', 'dashboard']
-```
-
-## Examples
-
-### Complete Dashboard Example
-
-See `packages/starters/basic/src/dashboard.page.yml` for a full dashboard implementation.
-
-### Form Page Example
-
-See `packages/starters/basic/src/project_detail.page.yml` for a two-column detail page with forms.
-
-### Wizard Example
-
-See `packages/starters/basic/src/create_project_wizard.page.yml` for a multi-step wizard.
-
-### Canvas Layout Example
-
-See `packages/starters/basic/src/landing.page.yml` for a custom landing page.
-
-## Integration with Navigation
-
-Pages can be referenced in application navigation:
-
-```yaml
-# app.yml
-navigation:
-  - type: page
-    name: dashboard
-    label: Dashboard
-    icon: dashboard
-    path: /dashboard
-```
-
-## Best Practices
-
-1. **Keep It Simple**: Start with simple layouts and add complexity as needed
-2. **Reuse Components**: Use containers to create reusable component groups
-3. **Data Binding**: Use `{{}}` syntax to bind dynamic values
-4. **Responsive First**: Always consider mobile layouts
-5. **Test Permissions**: Verify access control for sensitive pages
-6. **AI Context**: Provide clear AI context for better code generation
-7. **Naming Convention**: Use descriptive component IDs (e.g., `tasks_grid` not `grid1`)
-
-## Next Steps
-
-- Learn about [Application Configuration](./application.md)
-- Explore [Data Modeling](./data-modeling.md)
-- Read about [Actions](./logic-actions.md)
-- Check [Validation Rules](./validation.md)
diff --git a/docs/guide/plugins.md b/docs/guide/plugins.md
deleted file mode 100644
index b6d331ff..00000000
--- a/docs/guide/plugins.md
+++ /dev/null
@@ -1,249 +0,0 @@
-# Plugin System
-
-Plugins are the primary way to extend ObjectQL. They allow you to bundle behavior, schema modifications, and logic (hooks/actions) into reusable units.
-
-## 1. Anatomy of a Plugin
-
-A plugin is simply an object that implements the `ObjectQLPlugin` interface.
-
-```typescript
-import { IObjectQL } from '@objectql/types';
-
-export interface ObjectQLPlugin {
-    /**
-     * The unique name of the plugin
-     */
-    name: string;
-    
-    /**
-     * Called during initialization, before drivers connect.
-     * @param app The ObjectQL instance
-     */
-    setup(app: IObjectQL): void | Promise<void>;
-}
-```
-
-## 2. Execution Lifecycle
-
-Understanding valid execution timing is critical.
-
-1.  **Phase 1: Construction (`new ObjectQL`)**
-    *   Load Metadata from `packages`.
-    *   Load Metadata from `source` directories (`*.object.yml`).
-    *   Load Metadata from `config.objects`.
-    *   **Result:** `app.metadata` holds all static definitions.
-
-2.  **Phase 2: Initialization (`await app.init()`)**
-    *   **Step A: Remotes:** Fetch metadata from remote services.
-    *   **Step B: Plugins (`plugin.setup`)**:  <-- **YOU ARE HERE**
-        *   This is the last chance to modify metadata before it touches the DB.
-        *   You can access all objects loaded in Phase 1 & Step A.
-    *   **Step C: Drivers:** Drivers connect and synchronize schema (create tables, etc.).
-
-## 3. Creating Plugins
-
-You can define plugins in two styles: **Object** or **Class**.
-
-### Option A: Object Style (Simpler)
-Useful for stateless, simple logic or one-off modifications.
-
-```typescript
-const MySimplePlugin = {
-    name: 'my-simple-plugin',
-    setup(app) {
-        app.on('before:create', 'user', async (ctx) => {
-            console.log('Creating user...');
-        });
-    }
-};
-```
-
-### Option B: Class Style (Recommended)
-Useful when your plugin needs to maintain internal state, configuration, or complex initialization logic.
-
-```typescript
-class MyComplexPlugin implements ObjectQLPlugin {
-    name = 'my-complex-plugin';
-    private config;
-
-    constructor(config = {}) {
-        this.config = config;
-    }
-
-    async setup(app: IObjectQL) {
-        // Access config here
-        if (this.config.enableLogging) {
-            app.on('before:*', '*', async (ctx) => {
-                console.log(`[${ctx.event}] ${ctx.objectName}`);
-            });
-        }
-    }
-}
-```
-
-## 3. Loading Plugins
-
-Plugins are passed to the `ObjectQL` constructor via the `plugins` array. The loader is very flexible.
-
-### Method 1: Inline Instance
-Pass the plugin object or class instance directly.
-
-```typescript
-const db = new ObjectQL({
-    plugins: [
-        MySimplePlugin,          // Object
-        new MyComplexPlugin({})  // Class Instance
-    ]
-});
-```
-
-### Method 2: NPM Package (String)
-You can specify the package name as a string. ObjectQL uses `require()` (Node.js) to resolve it.
-
-```typescript
-const db = new ObjectQL({
-    plugins: [
-        '@objectql/plugin-audit', // Searches node_modules
-        './local-plugins/my-plugin' // Relative path
-    ]
-});
-```
-
-#### Package Resolution Rules
-When loading from a string, ObjectQL tries to find the plugin in the exported module in this order:
-
-1.  **Class Constructor**: If the module exports a Class (default or module.exports), it tries to instantiation it (`new Plugin()`).
-2.  **Plugin Object**: If the module exports an object with a `setup` function, it uses it directly.
-3.  **Default Export**: If the module has a `default` export, it checks that recursively.
-
-**Example Package (`node_modules/my-plugin/index.js`):**
-```javascript
-// This works
-module.exports = class MyPlugin { ... }
-
-// This also works
-module.exports = { name: '..', setup: () => {} }
-
-// This also works (ESM/TS)
-export default class MyPlugin { ... }
-```
-
-## 4. What can Plugins do?
-
-The `setup(app)` method gives you full access to the `ObjectQL` instance.
-
-### A. Manipulate Metadata (Schema)
-Plugins have full control over the schema. You can modify existing objects or register new ones.
-
-**Example 1: Injecting a global field**
-```typescript
-setup(app) {
-    const allObjects = app.metadata.list('object');
-    for (const obj of allObjects) {
-        // Add 'createdAt' to every object if missing
-        if (!obj.fields.createdAt) {
-            obj.fields.createdAt = { type: 'datetime' };
-        }
-    }
-}
-```
-
-**Example 2: Registering a new Object**
-Plugins can bundle their own data models (e.g. an audit log table).
-
-```typescript
-setup(app) {
-    app.registerObject({
-        name: 'audit_log',
-        fields: {
-            action: { type: 'string' },
-            userId: { type: 'string' },
-            timestamp: { type: 'datetime' }
-        }
-    });
-}
-```
-
-**Example 3: Scanning a Directory**
-Plugins can also scan a directory to load metadata files, just like the main application. This is useful for bundling a set of objects.
-
-```typescript
-import * as path from 'path';
-
-setup(app) {
-    // Scan the 'objects' folder inside the plugin directory
-    const objectsDir = path.join(__dirname, 'objects');
-    app.loadFromDirectory(objectsDir);
-}
-```
-
-### B. Register Global Hooks
-Listen to lifecycle events on specific objects or `*` (wildcard).
-
-```typescript
-setup(app) {
-    app.on('before:delete', '*', async (ctx) => {
-        if (ctx.objectName === 'system_log') {
-            throw new Error("Logs cannot be deleted");
-        }
-    });
-}
-```
-
-### C. Register Custom Actions
-Add new capabilities to objects.
-
-```typescript
-setup(app) {
-    // Usage: objectql.executeAction('user', 'sendEmail', { ... })
-    app.registerAction('user', 'sendEmail', async (ctx) => {
-        await emailService.send(ctx.args.to, ctx.args.body);
-    });
-}
-```
-
-### D. Custom Metadata Loaders
-Plugins can register new loaders to scan for custom file types (e.g. `*.workflow.yml`). This allows ObjectQL to act as a unified metadata engine.
-
-```typescript
-import * as yaml from 'js-yaml';
-
-setup(app) {
-    app.addLoader({
-        name: 'workflow-loader',
-        glob: ['**/*.workflow.yml'],
-        handler: (ctx) => {
-            const doc = yaml.load(ctx.content);
-            const workflowName = doc.name;
-            
-            // Register into MetadataRegistry with a custom type
-            ctx.registry.register('workflow', {
-                type: 'workflow',
-                id: workflowName,
-                path: ctx.file,
-                content: doc
-            });
-        }
-    });
-}
-```
-
-### E. Manage Packages (Presets)
-Plugins can dynamically load or unload other packages. This is useful for plugins that act as "features" which bring in a set of dependencies.
-
-```typescript
-setup(app) {
-    // Dynamically load another package
-    app.addPackage('@objectos/standard-objects');
-
-    // Or remove a package if it conflicts with this plugin
-    app.removePackage('@objectos/legacy-objects');
-}
-```
-
-## 5. Scope Isolation
-
-
-When a plugin is loaded via **Package Name** (Method 2), ObjectQL automatically marks the hooks and actions registered by that plugin with its package name.
-
-This allows `app.removePackage('@objectql/plugin-auth')` to cleanly remove all hooks and actions associated with that plugin, without affecting others.
diff --git a/docs/guide/querying.md b/docs/guide/querying.md
deleted file mode 100644
index e43ed500..00000000
--- a/docs/guide/querying.md
+++ /dev/null
@@ -1,195 +0,0 @@
-# Querying Data
-
-ObjectQL uses a **JSON-based Protocol** for all data operations. Unlike SQL (strings) or Query Builders (chained methods), ObjectQL queries are **Data Structures**.
-
-This design makes it strictly typed, easy to serialise/transport over HTTP, and safe from injection—perfect for both human developers and AI Agents.
-
-## The `find()` Operation
-
-The `find` method recovers a list of records matching specific criteria.
-
-```typescript
-const products = await app.object('product').find({
-    filters: [
-        ['category', '=', 'electronics'],
-        ['price', '>', 500]
-    ],
-    fields: ['name', 'price', 'category'],
-    sort: ['-price'], // Descending
-    skip: 0,
-    limit: 10
-});
-```
-
-### Filters
-
-Filters are defined as a 2D array: `[[ field, operator, value ]]`.
-
-**Implicit AND**:
-```typescript
-filters: [
-    ['status', '=', 'active'],
-    ['stock', '>', 0]
-]
-// SQL: WHERE status = 'active' AND stock > 0
-```
-
-**Explicit OR**:
-Use the `_or` special operator in complex filters (see advanced docs).
-
-### Sorting
-
-*   `field`: Ascending.
-*   `-field`: Descending.
-
-## CRUD Operations
-
-### Create (Insert)
-
-```typescript
-const id = await app.object('user').insert({
-    name: "Alice",
-    email: "alice@example.com",
-    role: "admin"
-});
-```
-
-### Update
-
-Updates are always bulk operations targeted by `filters`. To update a single record, filter by ID.
-
-```typescript
-// Update specific record
-await app.object('user').update(
-    { filters: [['_id', '=', '123']] }, // Target
-    { doc: { status: 'active' } }       // Change
-);
-
-// Bulk update
-await app.object('product').update(
-    { filters: [['stock', '=', 0]] },
-    { doc: { status: 'out_of_stock' } }
-);
-```
-
-### Delete
-
-```typescript
-// Delete specific record
-await app.object('user').delete({
-    filters: [['_id', '=', '123']]
-});
-```
-
-## Relationships (Joins & Expand)
-
-ObjectQL handles relationships distinctively. Instead of SQL `JOIN` keywords, we use the `expand` property to hydrate related records. This ensures compatibility across SQL and NoSQL drivers (where joins might be separate queries).
-
-### 1. The `expand` Syntax
-
-To get related data, define the relationship in `expand`.
-
-```typescript
-// Fetch tasks and include project details
-const tasks = await app.object('task').find({
-    fields: ['name', 'status', 'project'], // 'project' key returns the ID
-    expand: {
-        project: {
-            fields: ['name', 'start_date', 'owner']
-        }
-    }
-});
-/* Result:
-{
-    name: "Fix Bug",
-    project: {
-        name: "Q1 Web App",
-        owner: "Alice"
-    }
-}
-*/
-```
-
-### 2. Nested Expansion
-
-You can nest expansions arbitrarily deep.
-
-```typescript
-expand: {
-    project: {
-        fields: ['name'],
-        expand: {
-            // Expand the 'manager' field on the 'project' object
-            manager: {
-                fields: ['name', 'email']
-            }
-        }
-    }
-}
-```
-
-### 3. Filtering on Related Records
-
-There are two ways to filter based on relationships:
-
-**A. Filter the Root (Dot Notation)**
-Find tasks where the *project's status* is active.
-*(Note: Requires a driver that supports SQL Joins)*
-```typescript
-filters: [
-    ['project.status', '=', 'active']
-]
-```
-
-**B. Filter the Expanded List**
-Find projects, but only include *completed* tasks in the expansion.
-```typescript
-app.object('project').find({
-    expand: {
-        tasks: {
-            filters: [['status', '=', 'completed']]
-        }
-    }
-})
-```
-
-## Aggregation
-
-ObjectQL supports SQL-like aggregation via the `aggregate()` method on the repository.
-
-```typescript
-const stats = await app.object('order').aggregate({
-    // 1. Filter first
-    filters: [['status', '=', 'paid']],
-    
-    // 2. Group by specific fields
-    groupBy: ['customer_id'],
-    
-    // 3. Define aggregate functions
-    aggregate: [
-        { func: 'sum', field: 'total', alias: 'total_revenue' },
-        { func: 'count', field: 'id', alias: 'order_count' },
-        { func: 'max', field: 'created_at', alias: 'last_order_date' }
-    ]
-});
-
-/* Result:
-[
-    { customer_id: "101", total_revenue: 5000, order_count: 3, last_order_date: "2023-12-01..." },
-    { customer_id: "102", total_revenue: 1200, order_count: 1, last_order_date: "2023-11-15..." }
-]
-*/
-```
-
-### Supported Functions
-*   `count`
-*   `sum`
-*   `avg`
-*   `min`
-*   `max`
-
-## Why JSON?
-
-1.  **Transportable**: The query IS the HTTP request body. No translation needed.
-2.  **Secure**: Impossible to inject SQL syntax.
-3.  **Generatable**: LLMs produce perfect JSON structures naturally.
diff --git a/docs/guide/server-integration.md b/docs/guide/server-integration.md
deleted file mode 100644
index e5b8d55a..00000000
--- a/docs/guide/server-integration.md
+++ /dev/null
@@ -1,114 +0,0 @@
-# Server Integration
-
-ObjectQL is designed to be framework-agnostic. While it can be used directly as a library, we provide a standard `@objectql/server` package to expose your application via HTTP.
-
-## The `@objectql/server` Package
-
-This package provides a standardized way to handle HTTP requests, similar to libraries like `better-auth`. It receives a standard JSON request body and routes it to the correct internal ObjectQL operation (`find`, `create`, `action`, etc.).
-
-### Installation
-
-```bash
-pnpm add @objectql/server
-```
-
-## Supported Frameworks
-
-### 1. Node.js (Raw HTTP)
-
-You can mount the handler directly on a native Node.js `http.Server`.
-
-```typescript
-import { createNodeHandler } from '@objectql/server';
-import { app } from './my-objectql-app'; // Your ObjectQL instance
-import { createServer } from 'http';
-
-const server = createServer(createNodeHandler(app));
-server.listen(3000);
-```
-
-### 2. Express
-
-Mount ObjectQL on any route path.
-
-```typescript
-import express from 'express';
-import { createNodeHandler } from '@objectql/server';
-import { app } from './my-objectql-app';
-
-const server = express();
-// ObjectQL server adapter handles body parsing automatically,
-// but works fine if you already used express.json()
-server.all('/api/objectql', createNodeHandler(app));
-
-server.listen(3000);
-```
-
-### 3. Next.js (Pages Router)
-
-```typescript
-// pages/api/objectql.ts
-import { createNodeHandler } from '@objectql/server';
-import { app } from '../../lib/store';
-
-export const config = {
-  api: {
-    bodyParser: false, // Let ObjectQL handle it, or true if you prefer
-  },
-};
-
-export default createNodeHandler(app);
-```
-
-## The Protocol
-
-The server exposes a single endpoint that accepts POST requests with a JSON body defined by `ObjectQLRequest`:
-
-```typescript
-interface ObjectQLRequest {
-    op: 'find' | 'findOne' | 'create' | 'update' | 'delete' | 'count' | 'action';
-    object: string;
-    args: any;
-    user?: any; // For passing authentication context
-}
-```
-
-## 📖 OpenAPI / Swagger Support
-
-`@objectql/server` automatically generates an OpenAPI 3.0 specification from your registered schema.
-
-You can access the spec by appending `/openapi.json` to your handler's mount path.
-
-**Example URLs:**
-*   **CLI Serve:** `http://localhost:3000/openapi.json`
-*   **Express (mounted at /api/objectql):** `http://localhost:3000/api/objectql/openapi.json`
-*   **Next.js (pages/api/objectql.ts):** `http://localhost:3000/api/objectql/openapi.json`
-
-This JSON file describes your data objects as "Virtual REST" endpoints (`GET /user`, `POST /user`, etc.), allowing you to easily import them into **Swagger UI**, **Postman**, or other API tools for visualization and testing.
-
-## Example Usage
-
-**Example (cURL):**
-
-```bash
-curl -X POST http://localhost:3000/api/objectql \
-  -H "Content-Type: application/json" \
-  -d '{
-    "op": "create",
-    "object": "User",
-    "args": {
-      "data": { "name": "Alice", "email": "alice@example.com" }
-    }
-  }'
-```
-
-## Dev Server
-
-For rapid prototyping, `@objectql/cli` provides a built-in dev server.
-
-```bash
-# Serves the current directory schema on port 3000
-objectql serve
-```
-
-See [CLI Documentation](../package/cli) for more details.
diff --git a/docs/spec/form.md b/docs/spec/form.md
deleted file mode 100644
index 106d346a..00000000
--- a/docs/spec/form.md
+++ /dev/null
@@ -1,1046 +0,0 @@
-# Form Metadata
-
-Form metadata defines the structure, layout, and behavior of data entry forms. Forms are the primary interface for creating and editing records. They are designed to be both functional and AI-understandable for automated form generation.
-
-## 1. Overview
-
-Form metadata provides:
-
-- **Layout definition**: Multi-column layouts, sections, tabs, wizards
-- **Field configuration**: Labels, help text, default values, placeholders
-- **Conditional logic**: Show/hide fields based on conditions
-- **Validation**: Real-time field validation with clear messages
-- **Workflow integration**: Multi-step forms, wizards
-- **Responsive design**: Mobile-optimized layouts
-- **AI assistance**: Smart defaults, auto-complete, validation helpers
-
-**File Naming Convention:** `<form_name>.form.yml`
-
-The filename (without the `.form.yml` extension) automatically becomes the form's identifier. This eliminates the need for a redundant `name` property.
-
-**Examples:**
-- `project_form.form.yml` → Form name: `project_form`
-- `quick_task.form.yml` → Form name: `quick_task`
-- `customer_edit.form.yml` → Form name: `customer_edit`
-
-## 2. Root Structure with AI Context
-
-```yaml
-# File: project_form.form.yml
-# Form name is inferred from filename!
-
-label: Project Information
-type: edit  # create, edit, view
-object: projects
-description: Form for creating and editing projects
-
-# AI-friendly context
-ai_context:
-  intent: "Capture essential project information for planning and tracking"
-  user_persona: "Project manager or team lead"
-  typical_completion_time: "3-5 minutes"
-  
-  # Help AI understand form flow
-  user_journey: |
-    1. Enter basic project details (name, description)
-    2. Set timeline and budget
-    3. Assign team members
-    4. Review and submit
-  
-  # Common issues to prevent
-  common_errors:
-    - "Forgetting to set realistic deadlines"
-    - "Not assigning budget upfront"
-    - "Missing team member assignments"
-  
-  # Quality checks
-  quality_guidance: |
-    - Name should be descriptive and unique
-    - Description should explain problem being solved
-    - Budget should align with project scope
-
-# Layout Configuration
-layout:
-  columns: 2
-  sections:
-    - name: basic_info
-      label: Basic Information
-      columns: 2
-      
-      ai_context:
-        intent: "Capture core identifying information"
-        user_guidance: "Start with a clear, descriptive project name"
-        completion_order: 1
-      
-      fields:
-        - name
-        - status
-        - priority
-        - category
-    
-    - name: details
-      label: Project Details
-      columns: 1
-      
-      ai_context:
-        intent: "Document project purpose and scope"
-        user_guidance: "Be specific about what problems this project solves"
-        completion_order: 2
-      
-      fields:
-        - description
-        - objectives
-        - deliverables
-    
-    - name: timeline
-      label: Timeline & Budget
-      columns: 2
-      
-      ai_context:
-        intent: "Set realistic expectations for duration and cost"
-        validation_focus: "Ensure dates are logical and budget is within limits"
-        completion_order: 3
-      
-      fields:
-        - start_date
-        - end_date
-        - budget
-        - estimated_hours
-    
-    - name: assignment
-      label: Team Assignment
-      columns: 2
-      
-      ai_context:
-        intent: "Assign ownership and build project team"
-        user_guidance: "Owner is accountable for project success"
-        completion_order: 4
-      
-      fields:
-        - owner
-        - team
-        - department
-
-# Field Overrides with AI Enhancement
-field_config:
-  name:
-    placeholder: "e.g., 'Q2 Website Redesign'"
-    help_text: "Choose a name that clearly identifies the project"
-    
-    ai_context:
-      intent: "Unique project identifier for tracking and reporting"
-      
-      # Smart suggestions
-      suggestions_based_on:
-        - "Department name"
-        - "Current quarter"
-        - "Primary deliverable"
-      
-      quality_check: "Should be descriptive, not generic like 'Project 1'"
-      
-      examples:
-        good: ["Website Redesign 2026", "Q1 Marketing Campaign"]
-        bad: ["Project", "Untitled", "New Project"]
-  
-  description:
-    rows: 5
-    placeholder: "What is this project about? What problem does it solve?"
-    help_text: "Provide comprehensive project overview"
-    
-    ai_context:
-      intent: "Clear problem statement and expected outcomes"
-      quality_check: "Should answer: What, Why, and Expected Outcome"
-      min_quality_length: 50  # Characters for meaningful description
-      
-      ai_assist:
-        enabled: true
-        feature: "auto_expand"
-        prompt: "Expand this brief description into a full project overview"
-  
-  status:
-    default_value: planning
-    help_text: "Current project stage"
-    
-    ai_context:
-      intent: "Track project through lifecycle"
-      default_rationale: "New projects start in planning phase"
-  
-  budget:
-    prefix: $
-    format: currency
-    help_text: "Total approved project budget"
-    
-    ai_context:
-      intent: "Financial planning and tracking"
-      
-      # Smart defaults based on project type
-      smart_defaults:
-        small_project: 25000
-        medium_project: 100000
-        large_project: 500000
-      
-      # Warning thresholds (severity: info, warning, error)
-      warning_thresholds:
-        - amount: 50000
-          message: "Projects over $50K require manager approval"
-          severity: warning
-        
-        - amount: 200000
-          message: "Projects over $200K require director approval"
-          severity: error
-  
-  start_date:
-    default: "$today"
-    
-    ai_context:
-      intent: "When project work begins"
-      smart_default_rationale: "Most projects start immediately or within days"
-  
-  end_date:
-    ai_context:
-      intent: "Target completion date"
-      
-      # AI can suggest realistic timelines
-      suggestions:
-        - value: "start_date + 30 days"
-          label: "1 month project"
-        - value: "start_date + 90 days"
-          label: "1 quarter project"
-        - value: "start_date + 180 days"
-          label: "6 month project"
-  
-  owner:
-    default: "$current_user"
-    
-    ai_context:
-      intent: "Person responsible for project success"
-      default_rationale: "Usually the person creating the project"
-      
-      # Smart suggestions
-      suggestions_based_on:
-        - "Current user's manager"
-        - "Department head"
-        - "Previous project owners in same category"
-
-# Conditional Display with Business Logic
-conditional_logic:
-  - name: show_completion_fields
-    
-    ai_context:
-      intent: "Show completion tracking when project is done"
-      business_rule: "Completed projects need actual dates and costs"
-    
-    condition:
-      field: status
-      operator: "="
-      value: completed
-    
-    actions:
-      - show_fields: [completion_date, actual_cost, completion_notes]
-      - mark_required: [completion_date, completion_notes]
-      - hide_fields: [estimated_hours]
-  
-  - name: require_approval_info
-    
-    ai_context:
-      intent: "High-value projects need approval tracking"
-      business_rule: "Company policy requires approval for projects > $50K"
-    
-    condition:
-      field: budget
-      operator: ">"
-      value: 50000
-    
-    actions:
-      - show_fields: [approval_required, approver, approval_justification]
-      - mark_required: [approver, approval_justification]
-      - show_message:
-          type: info
-          text: "This project requires management approval due to budget amount"
-  
-  - name: suggest_risk_assessment
-    
-    ai_context:
-      intent: "Large or complex projects should assess risks"
-      business_rule: "Projects over 6 months or $200K should document risks"
-    
-    condition:
-      any_of:
-        - field: budget
-          operator: ">"
-          value: 200000
-        - field: estimated_hours
-          operator: ">"
-          value: 1000
-    
-    actions:
-      - show_section: risk_assessment
-      - show_message:
-          type: warning
-          text: "Consider documenting project risks and mitigation strategies"
-
-# AI-Powered Form Features
-ai_features:
-  # Auto-complete from context
-  auto_complete:
-    enabled: true
-    fields: [description, objectives]
-    
-    ai_context:
-      intent: "Help users write better project descriptions"
-      feature: "Expand brief notes into full descriptions"
-  
-  # Smart validation
-  validation_assistant:
-    enabled: true
-    
-    ai_context:
-      intent: "Real-time suggestions for improving data quality"
-      checks:
-        - "Description is too vague"
-        - "Budget seems unrealistic for project scope"
-        - "Timeline conflicts with resource availability"
-  
-  # Similar projects
-  similar_projects:
-    enabled: true
-    match_on: [category, department, budget_range]
-    
-    ai_context:
-      intent: "Show similar past projects to help with estimation"
-      use: "User can copy timeline and budget estimates from successful projects"
-
-# Actions
-actions:
-  primary:
-    - label: Save
-      action: save
-      icon: save
-    - label: Save & New
-      action: save_and_new
-      icon: add
-  
-  secondary:
-    - label: Cancel
-      action: cancel
-      icon: close
-
-# Validation
-validation:
-  on_change: true
-  on_submit: true
-  show_errors_inline: true
-```
-
-## 3. Form Types
-
-| Type | Description | Use Case |
-|:---|:---|:---|
-| `create` | New record creation | Creating new entities |
-| `edit` | Record editing | Updating existing records |
-| `view` | Read-only display | Viewing record details |
-| `wizard` | Multi-step form | Complex data entry workflows |
-| `inline` | Inline editing | Quick edits in lists/grids |
-| `quick_create` | Minimal quick form | Fast record creation |
-
-## 4. Layout Sections
-
-Organize fields into logical groups:
-
-```yaml
-layout:
-  # Global layout settings
-  columns: 2
-  spacing: medium
-  
-  sections:
-    # Basic Section
-    - name: personal_info
-      label: Personal Information
-      description: Employee basic details
-      columns: 2
-      collapsible: true
-      collapsed: false
-      fields:
-        - first_name
-        - last_name
-        - email
-        - phone
-    
-    # Full-width Section
-    - name: address
-      label: Address
-      columns: 1
-      fields:
-        - street
-        - city
-        - state
-        - zip_code
-    
-    # Nested Sections
-    - name: employment
-      label: Employment Details
-      sections:
-        - name: position
-          label: Position
-          fields:
-            - title
-            - department
-            - manager
-        
-        - name: compensation
-          label: Compensation
-          fields:
-            - salary
-            - bonus
-            - stock_options
-```
-
-## 5. Field Configuration
-
-Override object-level field definitions:
-
-```yaml
-field_config:
-  # Text Field
-  email:
-    label: Email Address
-    placeholder: user@example.com
-    help_text: Primary contact email
-    required: true
-    autocomplete: email
-    validation:
-      format: email
-  
-  # Number Field
-  budget:
-    label: Project Budget
-    prefix: $
-    suffix: USD
-    format: currency
-    decimal_places: 2
-    min: 0
-    max: 1000000
-    step: 1000
-    help_text: Total allocated budget
-  
-  # Select Field
-  status:
-    label: Status
-    help_text: Current project status
-    default_value: draft
-    style: dropdown  # dropdown, radio, buttons
-  
-  # Lookup Field
-  owner:
-    label: Project Owner
-    help_text: Responsible person
-    search_fields: [name, email]
-    display_format: "{name} ({email})"
-    create_new: true  # Allow creating new record
-  
-  # Date Field
-  start_date:
-    label: Start Date
-    help_text: Project kickoff date
-    min_date: today
-    max_date: +1 year
-    default_value: today
-    format: MM/DD/YYYY
-  
-  # Textarea
-  description:
-    label: Description
-    placeholder: Enter detailed description
-    rows: 5
-    max_length: 5000
-    show_character_count: true
-    rich_text: false
-  
-  # Checkbox
-  is_public:
-    label: Public Project
-    help_text: Visible to all users
-    default_value: false
-  
-  # File Upload
-  attachments:
-    label: Attachments
-    help_text: Upload relevant documents
-    multiple: true
-    accept: [.pdf, .doc, .docx, .xls, .xlsx]
-    max_size: 10MB
-    max_files: 5
-```
-
-## 6. Conditional Logic
-
-Show/hide fields and control behavior based on conditions:
-
-```yaml
-conditional_logic:
-  # Show/Hide Fields
-  - name: show_international_fields
-    condition:
-      field: country
-      operator: "!="
-      value: US
-    actions:
-      - show_fields: [passport_number, visa_status]
-      - hide_fields: [ssn]
-  
-  # Make Fields Required
-  - name: require_reason_for_delay
-    condition:
-      field: status
-      operator: "="
-      value: delayed
-    actions:
-      - mark_required: [delay_reason, estimated_recovery_date]
-  
-  # Change Field Properties
-  - name: readonly_after_approval
-    condition:
-      field: approval_status
-      operator: "="
-      value: approved
-    actions:
-      - readonly_fields: [budget, scope, timeline]
-  
-  # Multiple Conditions (AND)
-  - name: high_value_approval
-    condition:
-      type: and
-      conditions:
-        - field: amount
-          operator: ">"
-          value: 10000
-        - field: department
-          operator: "="
-          value: finance
-    actions:
-      - show_fields: [cfo_approval]
-      - mark_required: [cfo_approval]
-  
-  # Multiple Conditions (OR)
-  - name: special_handling
-    condition:
-      type: or
-      conditions:
-        - field: priority
-          operator: "="
-          value: urgent
-        - field: vip_customer
-          operator: "="
-          value: true
-    actions:
-      - show_section: special_instructions
-      - set_field_value:
-          field: requires_review
-          value: true
-```
-
-## 7. Tabs Layout
-
-Organize complex forms into tabs:
-
-```yaml
-layout:
-  type: tabs
-  tabs:
-    # Tab 1: Basic Info
-    - name: basic
-      label: Basic Information
-      icon: info
-      sections:
-        - name: details
-          fields:
-            - name
-            - description
-            - status
-    
-    # Tab 2: Advanced
-    - name: advanced
-      label: Advanced Settings
-      icon: settings
-      sections:
-        - name: configuration
-          fields:
-            - priority
-            - tags
-            - custom_fields
-    
-    # Tab 3: Related Records
-    - name: related
-      label: Related Items
-      icon: link
-      sections:
-        - name: tasks
-          type: related_list
-          object: tasks
-          relation: project_id
-          
-        - name: documents
-          type: related_list
-          object: documents
-          relation: project_id
-```
-
-## 8. Wizard Forms
-
-Multi-step forms for complex workflows:
-
-```yaml
-name: project_wizard
-type: wizard
-object: projects
-
-steps:
-  # Step 1: Basic Info
-  - name: basic
-    label: Basic Information
-    description: Enter project fundamentals
-    fields:
-      - name
-      - description
-      - category
-    validation:
-      required: [name, category]
-    
-    # Show only if validation passes
-    allow_next: true
-  
-  # Step 2: Team
-  - name: team
-    label: Team Assignment
-    description: Assign team members
-    fields:
-      - owner
-      - team_members
-      - department
-    
-    # Skip if single-person project
-    skip_if:
-      field: project_type
-      operator: "="
-      value: individual
-  
-  # Step 3: Timeline
-  - name: timeline
-    label: Timeline & Budget
-    description: Set schedule and budget
-    fields:
-      - start_date
-      - end_date
-      - budget
-      - milestones
-  
-  # Step 4: Review
-  - name: review
-    label: Review & Submit
-    description: Review all information
-    type: summary
-    
-    # Show summary of all fields
-    summary_sections:
-      - label: Basic Information
-        fields: [name, description, category]
-      - label: Team
-        fields: [owner, team_members]
-      - label: Timeline
-        fields: [start_date, end_date, budget]
-
-# Wizard Navigation
-wizard_config:
-  allow_back: true
-  allow_skip: false
-  show_progress: true
-  save_draft: true
-  
-  buttons:
-    back: Previous
-    next: Next
-    finish: Create Project
-```
-
-## 9. Field Groups
-
-Group related fields visually:
-
-```yaml
-layout:
-  sections:
-    - name: contact
-      label: Contact Information
-      
-      # Field Groups within Section
-      field_groups:
-        # Primary Contact
-        - label: Primary Contact
-          columns: 2
-          fields:
-            - primary_email
-            - primary_phone
-        
-        # Secondary Contact
-        - label: Secondary Contact
-          columns: 2
-          collapsible: true
-          collapsed: true
-          fields:
-            - secondary_email
-            - secondary_phone
-```
-
-## 10. Inline Editing
-
-Quick edit configuration:
-
-```yaml
-name: task_inline_edit
-type: inline
-object: tasks
-
-# Fields available for inline edit
-editable_fields:
-  - status
-  - priority
-  - assignee
-  - due_date
-
-# Quick action buttons
-quick_actions:
-  - label: Complete
-    action: update
-    values:
-      status: completed
-      completed_date: $current_date
-  
-  - label: Reassign
-    action: show_field
-    field: assignee
-```
-
-## 11. Quick Create Form
-
-Minimal form for fast data entry:
-
-```yaml
-name: task_quick_create
-type: quick_create
-object: tasks
-label: Quick Add Task
-
-# Minimal required fields
-fields:
-  - name
-  - assignee
-  - due_date
-
-# Auto-fill fields
-defaults:
-  status: open
-  priority: medium
-  created_by: $current_user
-
-# After creation
-after_create:
-  action: close  # or 'stay', 'redirect'
-  message: Task created successfully
-```
-
-## 12. Dynamic Fields
-
-Add/remove field groups dynamically:
-
-```yaml
-layout:
-  sections:
-    - name: contacts
-      label: Contact Persons
-      type: repeatable
-      
-      # Field group that can be repeated
-      field_group:
-        - name
-        - email
-        - phone
-        - role
-      
-      # Configuration
-      min_items: 1
-      max_items: 10
-      add_button_label: Add Contact
-      remove_button_label: Remove
-```
-
-## 13. Form Actions
-
-Define available actions on the form:
-
-```yaml
-actions:
-  # Primary Actions (prominent buttons)
-  primary:
-    - label: Save
-      action: save
-      icon: save
-      hotkey: Ctrl+S
-      
-    - label: Save & Close
-      action: save_and_close
-      icon: save_close
-  
-  # Secondary Actions (less prominent)
-  secondary:
-    - label: Save as Draft
-      action: save
-      values:
-        status: draft
-      icon: draft
-    
-    - label: Cancel
-      action: cancel
-      icon: close
-      confirm: Discard changes?
-  
-  # Custom Actions
-  custom:
-    - label: Send for Approval
-      action: custom
-      handler: send_for_approval
-      icon: send
-      
-      # Only show when ready
-      visible_when:
-        field: status
-        operator: "="
-        value: ready_for_approval
-```
-
-## 14. Form Validation
-
-```yaml
-validation:
-  # When to validate
-  on_change: true        # Validate as user types
-  on_blur: true          # Validate when field loses focus
-  on_submit: true        # Validate before submit
-  
-  # How to show errors
-  show_errors_inline: true
-  show_error_summary: true
-  error_summary_position: top
-  
-  # Validation rules
-  rules:
-    - fields: [start_date, end_date]
-      validator: |
-        function validate(values) {
-          return values.end_date > values.start_date;
-        }
-      message: End date must be after start date
-```
-
-## 15. Responsive Design
-
-Mobile-optimized layouts:
-
-```yaml
-layout:
-  # Desktop layout
-  desktop:
-    columns: 2
-    sections: [...]
-  
-  # Tablet layout
-  tablet:
-    columns: 1
-    compact_sections: true
-  
-  # Mobile layout
-  mobile:
-    columns: 1
-    stack_fields: true
-    hide_labels: false
-    
-    # Show only essential fields
-    visible_fields:
-      - name
-      - status
-      - priority
-      - due_date
-```
-
-## 16. Field Dependencies
-
-Load field options based on other field values:
-
-```yaml
-field_config:
-  state:
-    type: select
-    label: State
-  
-  city:
-    type: select
-    label: City
-    depends_on: state
-    
-    # Load cities based on selected state
-    options_query:
-      object: cities
-      filters:
-        - field: state
-          operator: "="
-          value: $state
-      fields: [name]
-      sort:
-        - field: name
-          direction: asc
-```
-
-## 17. Auto-save
-
-Automatically save form progress:
-
-```yaml
-auto_save:
-  enabled: true
-  interval: 30000  # 30 seconds
-  mode: draft      # Save as draft
-  
-  # Show indicator
-  show_indicator: true
-  indicator_position: top-right
-  
-  # Recovery
-  enable_recovery: true
-  recovery_prompt: You have unsaved changes. Restore?
-```
-
-## 18. Form Events & Hooks
-
-Execute logic on form events:
-
-```yaml
-events:
-  # Before form loads
-  on_load: |
-    async function onLoad(context) {
-      // Pre-populate fields
-      if (context.user.department) {
-        context.setFieldValue('department', context.user.department);
-      }
-    }
-  
-  # When field changes
-  on_field_change:
-    budget:
-      handler: |
-        function onChange(value, context) {
-          // Auto-calculate tax
-          const tax = value * 0.1;
-          context.setFieldValue('estimated_tax', tax);
-        }
-  
-  # Before submit
-  on_before_submit: |
-    async function beforeSubmit(values, context) {
-      // Final validation
-      if (values.amount > 10000 && !values.approval) {
-        context.showError('High-value orders require approval');
-        return false;
-      }
-      return true;
-    }
-  
-  # After successful submit
-  on_success: |
-    function onSuccess(result, context) {
-      context.showMessage('Record saved successfully');
-      context.redirect(`/projects/${result.id}`);
-    }
-  
-  # On error
-  on_error: |
-    function onError(error, context) {
-      context.showError(`Failed to save: ${error.message}`);
-    }
-```
-
-## 19. Form Modes
-
-Different modes for different contexts:
-
-```yaml
-modes:
-  # Create mode
-  create:
-    title: New Project
-    show_fields: [name, description, owner, start_date]
-    defaults:
-      status: draft
-      created_by: $current_user
-  
-  # Edit mode
-  edit:
-    title: Edit Project
-    show_fields: [name, description, status, owner, start_date, end_date]
-    readonly_fields: [created_by, created_at]
-  
-  # Clone mode
-  clone:
-    title: Clone Project
-    show_fields: [name, description, owner]
-    exclude_fields: [id, created_at, created_by]
-    field_overrides:
-      name:
-        default_value: "Copy of {original_name}"
-```
-
-## 20. Implementation Example
-
-```typescript
-// src/forms/project.form.yml
-import { FormDefinition } from '@objectql/types';
-
-export const project_form: FormDefinition = {
-  name: 'project_form',
-  type: 'edit',
-  object: 'projects',
-  layout: {
-    columns: 2,
-    sections: [
-      {
-        name: 'basic',
-        label: 'Basic Information',
-        fields: ['name', 'description', 'status']
-      }
-    ]
-  },
-  field_config: {
-    status: {
-      default_value: 'draft'
-    }
-  }
-};
-```
-
-## 21. Best Practices
-
-1. **User Experience**: Group related fields logically
-2. **Progressive Disclosure**: Show advanced fields only when needed
-3. **Clear Labels**: Use descriptive labels and help text
-4. **Validation**: Validate early and provide clear error messages
-5. **Performance**: Lazy-load heavy components
-6. **Accessibility**: Support keyboard navigation and screen readers
-7. **Mobile**: Design for mobile-first
-8. **Defaults**: Set sensible default values
-
-## 22. Related Specifications
-
-- [Objects & Fields](./object.md) - Data model
-- [Views](./view.md) - Display layouts
-- [Validation](./validation.md) - Validation rules
-- [Actions](./action.md) - Form actions
diff --git a/docs/spec/menu.md b/docs/spec/menu.md
deleted file mode 100644
index 6c88a1c5..00000000
--- a/docs/spec/menu.md
+++ /dev/null
@@ -1,771 +0,0 @@
-# Menu & Navigation Metadata
-
-Menu and navigation metadata defines the application structure, navigation hierarchy, and user interface organization.
-
-## 1. Overview
-
-Navigation features include:
-
-- **Menu Structures**: Top nav, side nav, context menus
-- **Hierarchical Organization**: Nested menu items and folders
-- **Dynamic Menus**: Role-based, permission-aware navigation
-- **Quick Actions**: Global actions and shortcuts
-- **Breadcrumbs**: Automatic navigation trails
-- **Search Integration**: Global search within navigation
-
-**File Naming Convention:** `<menu_name>.menu.yml`
-
-The filename (without the `.menu.yml` extension) automatically becomes the menu's identifier.
-
-**Examples:**
-- `main_navigation.menu.yml` → Menu name: `main_navigation`
-- `admin_menu.menu.yml` → Menu name: `admin_menu`
-
-**Note:** Menu metadata is often embedded within Application metadata (`.app.yml` files) as the `navigation` property. See [Application Metadata](./application.md) for the recommended approach.
-
-## 2. Root Structure
-
-```yaml
-# File: main_navigation.menu.yml
-# Menu name is inferred from filename!
-
-label: Main Menu
-type: sidebar  # sidebar, topnav, context, mobile
-app: sales     # Optional: Link to a specific application
-
-# Menu Items
-items:
-  # Dashboard
-  - name: home
-    label: Home
-    icon: home
-    path: /
-    type: page
-  
-  # Sales Section
-  - name: sales
-    label: Sales
-    icon: currency
-    type: section
-    items:
-      - name: leads
-        label: Leads
-        icon: users
-        path: /sales/leads
-        object: leads
-        view: list
-      
-      - name: opportunities
-        label: Opportunities
-        icon: funnel
-        path: /sales/opportunities
-        object: opportunities
-        view: kanban
-      
-      - name: quotes
-        label: Quotes
-        icon: document
-        path: /sales/quotes
-        object: quotes
-  
-  # Service Section
-  - name: service
-    label: Service
-    icon: support
-    type: section
-    items:
-      - name: cases
-        label: Cases
-        path: /service/cases
-        object: cases
-        badge:
-          query:
-            object: cases
-            filters: [['status', '=', 'open']]
-            function: count
-          color: red
-      
-      - name: knowledge
-        label: Knowledge Base
-        path: /service/knowledge
-        object: articles
-  
-  # Reports
-  - name: reports
-    label: Reports
-    icon: chart
-    type: section
-    items:
-      - name: sales_reports
-        label: Sales Reports
-        type: folder
-        items:
-          - name: revenue_report
-            label: Revenue Report
-            path: /reports/revenue
-            icon: report
-          
-          - name: pipeline_report
-            label: Pipeline Report
-            path: /reports/pipeline
-            icon: report
-      
-      - name: dashboards
-        label: Dashboards
-        type: folder
-        items:
-          - name: sales_dashboard
-            label: Sales Dashboard
-            path: /dashboards/sales
-            icon: dashboard
-
-  # Divider
-  - type: divider
-  
-  # Settings
-  - name: settings
-    label: Settings
-    icon: settings
-    path: /settings
-    permissions:
-      - admin
-
-# Quick Actions (Global)
-quick_actions:
-  - name: new_lead
-    label: New Lead
-    icon: add
-    action: create_record
-    object: leads
-    hotkey: Ctrl+Shift+L
-  
-  - name: new_case
-    label: New Case
-    icon: add
-    action: create_record
-    object: cases
-    hotkey: Ctrl+Shift+C
-  
-  - name: search
-    label: Global Search
-    icon: search
-    action: open_search
-    hotkey: Ctrl+K
-```
-
-## 3. Menu Types
-
-| Type | Description | Use Case |
-|:---|:---|:---|
-| `sidebar` | Vertical side navigation | Main app navigation |
-| `topnav` | Horizontal top bar | Secondary navigation |
-| `context` | Context-sensitive menu | Right-click, actions menu |
-| `mobile` | Mobile hamburger menu | Mobile navigation |
-| `breadcrumb` | Navigation trail | Page hierarchy |
-
-## 4. Menu Item Types
-
-### 4.1 Page Links
-
-```yaml
-items:
-  - name: dashboard
-    label: Dashboard
-    type: page
-    path: /dashboard
-    icon: home
-    
-    # Open behavior
-    target: _self  # _self, _blank, modal
-    
-    # Highlight when active
-    active_match: /dashboard*
-```
-
-### 4.2 Object Views
-
-Direct links to object list views:
-
-```yaml
-items:
-  - name: accounts
-    label: Accounts
-    type: object
-    object: accounts
-    view: list  # Uses default or specified view
-    icon: company
-    path: /accounts
-    
-    # Quick filters
-    default_filters:
-      - field: status
-        operator: "="
-        value: active
-```
-
-### 4.3 Sections/Folders
-
-Group related items:
-
-```yaml
-items:
-  - name: sales_section
-    label: Sales
-    type: section  # or 'folder'
-    icon: currency
-    
-    # Collapsible
-    collapsible: true
-    collapsed: false
-    
-    # Nested items
-    items:
-      - name: leads
-        label: Leads
-        path: /leads
-      
-      - name: accounts
-        label: Accounts
-        path: /accounts
-```
-
-### 4.4 Actions
-
-Execute actions from menu:
-
-```yaml
-items:
-  - name: export_data
-    label: Export Data
-    type: action
-    icon: download
-    action: export_records
-    
-    # Confirmation
-    confirm: Export all data?
-    
-    # Params
-    params:
-      format: csv
-```
-
-### 4.5 External Links
-
-Link to external resources:
-
-```yaml
-items:
-  - name: help_center
-    label: Help Center
-    type: external
-    url: https://help.example.com
-    icon: help
-    target: _blank
-```
-
-### 4.6 Dividers
-
-Visual separators:
-
-```yaml
-items:
-  - type: divider
-  
-  # Or with label
-  - type: divider
-    label: Admin Tools
-```
-
-## 5. Dynamic Menu Items
-
-Menu items that adapt based on context:
-
-```yaml
-items:
-  # Show only if user has permission
-  - name: admin_panel
-    label: Admin Panel
-    path: /admin
-    icon: shield
-    
-    permissions:
-      - admin
-  
-  # Show based on feature flag
-  - name: beta_feature
-    label: Beta Feature
-    path: /beta
-    
-    visible_when:
-      feature_flag: beta_features_enabled
-  
-  # Show based on condition
-  - name: pending_approvals
-    label: Pending Approvals
-    path: /approvals
-    
-    visible_when:
-      query:
-        object: approvals
-        filters: [['status', '=', 'pending']]
-        function: count
-        operator: ">"
-        value: 0
-```
-
-## 6. Badges & Indicators
-
-Show counts or status on menu items:
-
-```yaml
-items:
-  - name: notifications
-    label: Notifications
-    path: /notifications
-    icon: bell
-    
-    # Badge configuration
-    badge:
-      # Dynamic count
-      query:
-        object: notifications
-        filters:
-          - field: read
-            operator: "="
-            value: false
-          - field: user_id
-            operator: "="
-            value: $current_user.id
-        function: count
-      
-      # Styling
-      color: red  # red, blue, green, yellow, gray
-      max_value: 99  # Show "99+" if exceeds
-      show_zero: false
-```
-
-## 7. Favorites & Pinned Items
-
-User-customizable favorites:
-
-```yaml
-favorites:
-  enabled: true
-  
-  # Default favorites
-  default_items:
-    - dashboard
-    - my_tasks
-    - my_calendar
-  
-  # Max favorites
-  max_favorites: 10
-  
-  # Position
-  position: top  # top, bottom, section
-  
-  # Label
-  section_label: Favorites
-```
-
-## 8. Recent Items
-
-Track recently accessed items:
-
-```yaml
-recent_items:
-  enabled: true
-  
-  # Number to track
-  max_items: 10
-  
-  # Include types
-  include_types:
-    - page
-    - object
-    - report
-  
-  # Position in menu
-  position: top
-  section_label: Recent
-```
-
-## 9. Search Integration
-
-Global search in navigation:
-
-```yaml
-search:
-  enabled: true
-  
-  # Position
-  position: top
-  
-  # Hotkey
-  hotkey: Ctrl+K
-  
-  # Search scope
-  scope:
-    - objects
-    - reports
-    - dashboards
-    - help_articles
-  
-  # Quick actions in search
-  quick_actions:
-    - label: New Lead
-      action: create_record
-      object: leads
-    
-    - label: New Task
-      action: create_record
-      object: tasks
-```
-
-## 10. Breadcrumbs
-
-Automatic navigation trail:
-
-```yaml
-breadcrumbs:
-  enabled: true
-  
-  # Show on pages
-  show_on:
-    - object_detail
-    - object_edit
-    - reports
-  
-  # Format
-  separator: "/"
-  
-  # Home link
-  include_home: true
-  home_label: Home
-  
-  # Truncation
-  max_items: 5
-  truncate_middle: true
-```
-
-## 11. Multi-Level Navigation
-
-Complex nested structures:
-
-```yaml
-items:
-  - name: sales
-    label: Sales
-    type: section
-    icon: currency
-    
-    items:
-      # Level 2
-      - name: pipeline
-        label: Pipeline Management
-        type: folder
-        
-        items:
-          # Level 3
-          - name: leads
-            label: Leads
-            path: /sales/pipeline/leads
-          
-          - name: opportunities
-            label: Opportunities
-            path: /sales/pipeline/opportunities
-      
-      # Level 2
-      - name: accounts
-        label: Account Management
-        type: folder
-        
-        items:
-          # Level 3
-          - name: all_accounts
-            label: All Accounts
-            path: /sales/accounts
-          
-          - name: my_accounts
-            label: My Accounts
-            path: /sales/accounts/mine
-```
-
-## 12. Responsive Navigation
-
-Mobile-optimized menus:
-
-```yaml
-responsive:
-  # Mobile behavior
-  mobile:
-    type: drawer  # drawer, tabs, bottom_nav
-    
-    # Collapsed by default
-    collapsed: true
-    
-    # Show icons only
-    compact: true
-    
-    # Bottom navigation
-    bottom_nav:
-      enabled: true
-      max_items: 5
-      items:
-        - home
-        - tasks
-        - notifications
-        - profile
-  
-  # Tablet
-  tablet:
-    type: sidebar
-    collapsible: true
-    width: 240
-```
-
-## 13. Context Menus
-
-Right-click and action menus:
-
-```yaml
-# File: record_context_menu.menu.yml
-# Menu name is inferred from filename!
-
-type: context
-object: tasks
-
-items:
-  - name: edit
-    label: Edit
-    icon: edit
-    action: edit_record
-  
-  - name: delete
-    label: Delete
-    icon: delete
-    action: delete_record
-    confirm: Delete this task?
-    destructive: true
-  
-  - type: divider
-  
-  - name: duplicate
-    label: Duplicate
-    icon: copy
-    action: duplicate_record
-  
-  - name: share
-    label: Share
-    icon: share
-    action: share_record
-  
-  - type: divider
-  
-  - name: change_status
-    label: Change Status
-    icon: status
-    type: submenu
-    items:
-      - label: Mark Complete
-        action: update_field
-        field: status
-        value: completed
-      
-      - label: Mark In Progress
-        action: update_field
-        field: status
-        value: in_progress
-```
-
-## 14. Theme & Styling
-
-Customize menu appearance:
-
-```yaml
-theme:
-  # Width
-  width: 280
-  collapsed_width: 64
-  
-  # Colors
-  background: "#1a1a1a"
-  text_color: "#ffffff"
-  active_background: "#2d2d2d"
-  active_text_color: "#4CAF50"
-  
-  # Icons
-  icon_size: 20
-  show_icons: true
-  
-  # Typography
-  font_size: 14
-  font_weight: 400
-  
-  # Spacing
-  item_padding: 12
-  section_padding: 20
-  
-  # Animation
-  animation_duration: 200
-  hover_effect: true
-```
-
-## 15. Keyboard Navigation
-
-Keyboard shortcuts and accessibility:
-
-```yaml
-keyboard_navigation:
-  enabled: true
-  
-  # Shortcuts
-  shortcuts:
-    toggle_menu: Alt+M
-    search: Ctrl+K
-    next_item: ArrowDown
-    prev_item: ArrowUp
-    expand_section: ArrowRight
-    collapse_section: ArrowLeft
-    select: Enter
-  
-  # Accessibility
-  aria_labels: true
-  focus_visible: true
-  skip_navigation: true
-```
-
-## 16. User Customization
-
-Allow users to customize navigation:
-
-```yaml
-user_customization:
-  # Reorder items
-  allow_reorder: true
-  
-  # Show/hide items
-  allow_toggle_visibility: true
-  
-  # Custom folders
-  allow_custom_folders: true
-  
-  # Themes
-  allow_theme_selection: true
-  
-  # Save preferences
-  save_preferences: true
-  per_user: true
-```
-
-## 17. Analytics & Tracking
-
-Track navigation usage:
-
-```yaml
-analytics:
-  enabled: true
-  
-  # Track events
-  track:
-    - menu_item_click
-    - search_usage
-    - quick_action_usage
-  
-  # Metrics
-  metrics:
-    - popular_items
-    - user_navigation_paths
-    - search_queries
-```
-
-## 18. Implementation Example
-
-Complete menu definition:
-
-```yaml
-# File: main_navigation.menu.yml
-# Menu name is inferred from filename!
-
-label: Main Navigation
-type: sidebar
-
-items:
-  - name: home
-    label: Home
-    icon: home
-    path: /
-  
-  - name: sales
-    label: Sales
-    icon: currency
-    type: section
-    items:
-      - name: leads
-        label: Leads
-        path: /leads
-        object: leads
-      
-      - name: accounts
-        label: Accounts
-        path: /accounts
-        object: accounts
-```
-
-**TypeScript Implementation:**
-
-```typescript
-// File: main_navigation.menu.ts
-import { MenuDefinition } from '@objectql/types';
-
-export const main_menu: MenuDefinition = {
-  type: 'sidebar',
-  items: [
-    {
-      name: 'home',
-      label: 'Home',
-      icon: 'home',
-      path: '/'
-    },
-    {
-      name: 'sales',
-      label: 'Sales',
-      icon: 'currency',
-      type: 'section',
-      items: [
-        {
-          name: 'leads',
-          label: 'Leads',
-          path: '/leads',
-          object: 'leads'
-        },
-        {
-          name: 'accounts',
-          label: 'Accounts',
-          path: '/accounts',
-          object: 'accounts'
-        }
-      ]
-    }
-  ]
-};
-```
-
-## 19. Best Practices
-
-1. **Hierarchy**: Keep menu depth to 2-3 levels maximum
-2. **Icons**: Use consistent, meaningful icons
-3. **Labels**: Clear, concise menu labels
-4. **Grouping**: Logically group related items
-5. **Performance**: Lazy-load large menus
-6. **Mobile**: Optimize for touch interfaces
-7. **Accessibility**: Support keyboard navigation and screen readers
-8. **Permissions**: Filter menu items by user permissions
-9. **Testing**: Test navigation with different user roles
-
-## 20. Related Specifications
-
-- [Permissions](./permission.md) - Access control
-- [Views](./view.md) - Page layouts
-- [Objects](./object.md) - Data models
-- [Actions](./action.md) - Menu actions
diff --git a/docs/spec/page.md b/docs/spec/page.md
deleted file mode 100644
index e36f177f..00000000
--- a/docs/spec/page.md
+++ /dev/null
@@ -1,467 +0,0 @@
-# Page Specification
-
-## Overview
-
-Pages are the visual interface layer in ObjectQL applications. They define composable UI layouts that can render data from objects, display custom components, and orchestrate user interactions. Pages are defined using `*.page.yml` files and follow a declarative, component-based architecture.
-
-## File Convention
-
-```
-src/
-  ├── dashboard.page.yml
-  ├── project_detail.page.yml
-  └── create_wizard.page.yml
-```
-
-## Schema
-
-### Root Structure
-
-```typescript
-interface PageConfig {
-  // Identity
-  name: string;                    // Unique identifier
-  label: string;                   // Display name
-  description?: string;            // Page description
-  icon?: string;                   // Icon identifier
-  
-  // Layout
-  layout: PageLayoutType;          // Layout type
-  sections?: PageSection[];        // Page sections (for structured layouts)
-  components?: PageComponent[];    // Components (for simple layouts)
-  
-  // Data & Logic
-  data_sources?: Record<string, ComponentDataSource>;
-  actions?: Record<string, ComponentAction>;
-  
-  // Styling & Behavior
-  style?: ComponentStyle;
-  responsive?: ResponsiveConfig;
-  
-  // Access Control
-  permissions?: {
-    view?: string[];
-    edit?: string[];
-  };
-  
-  // Metadata
-  meta?: {
-    title?: string;
-    description?: string;
-    keywords?: string[];
-  };
-  
-  // State Management
-  state?: {
-    initial?: Record<string, any>;
-    persist?: boolean;
-    storage_key?: string;
-  };
-  
-  // Features
-  realtime?: boolean;
-  refresh_interval?: number;
-  
-  // AI Context
-  ai_context?: {
-    intent?: string;
-    persona?: string;
-    tasks?: string[];
-  };
-}
-```
-
-### Layout Types
-
-```typescript
-type PageLayoutType = 
-  | 'single_column'   // Single vertical column
-  | 'two_column'      // Left and right columns
-  | 'three_column'    // Left, center, right
-  | 'dashboard'       // Grid-based dashboard
-  | 'canvas'          // Free-form positioning
-  | 'tabs'            // Tab-based layout
-  | 'wizard'          // Multi-step wizard
-  | 'custom';         // Custom layout
-```
-
-### Component Types
-
-```typescript
-type PageComponentType =
-  // Data Display
-  | 'data_grid'       // Table/grid
-  | 'detail_view'     // Record details
-  | 'list'            // List view
-  | 'chart'           // Visualizations
-  | 'metric'          // KPI display
-  | 'calendar'        // Calendar view
-  | 'kanban'          // Kanban board
-  | 'timeline'        // Timeline/Gantt
-  
-  // Data Input
-  | 'form'            // Data entry form
-  | 'button'          // Action button
-  
-  // Layout
-  | 'container'       // Group components
-  | 'tabs'            // Tab container
-  | 'divider'         // Visual separator
-  
-  // Content
-  | 'text'            // Text/markdown
-  | 'html'            // Custom HTML
-  | 'image'           // Image display
-  | 'iframe'          // Embedded content
-  
-  | 'custom';         // Custom component
-```
-
-### Component Structure
-
-```typescript
-interface PageComponent {
-  id: string;                      // Unique component ID
-  type: PageComponentType;         // Component type
-  label?: string;                  // Display label
-  description?: string;            // Description
-  
-  // Data binding
-  data_source?: ComponentDataSource;
-  
-  // Component configuration
-  config?: Record<string, any>;
-  
-  // Actions
-  actions?: {
-    on_click?: ComponentAction;
-    on_submit?: ComponentAction;
-    on_load?: ComponentAction;
-    on_change?: ComponentAction;
-    [key: string]: ComponentAction | undefined;
-  };
-  
-  // Styling
-  style?: ComponentStyle;
-  responsive?: ResponsiveConfig;
-  
-  // Visibility & Access
-  visible_when?: Record<string, any>;
-  permissions?: string[];
-  
-  // Nested components
-  components?: PageComponent[];
-  
-  // Grid positioning (for dashboard layout)
-  grid?: {
-    x: number;      // Column (0-11)
-    y: number;      // Row
-    w: number;      // Width in grid units
-    h: number;      // Height in grid units
-  };
-  
-  // Custom component reference
-  component?: string;
-}
-```
-
-### Data Sources
-
-```typescript
-interface ComponentDataSource {
-  object?: string;                 // Object to query
-  filters?: any[];                 // Filter conditions
-  fields?: string[];               // Fields to display
-  sort?: Array<[string, 'asc' | 'desc']>;
-  limit?: number;
-  paginate?: boolean;
-  expand?: Record<string, any>;    // Related objects
-  query?: any;                     // Custom query
-}
-```
-
-### Actions
-
-```typescript
-interface ComponentAction {
-  type: 'navigate' | 'open_modal' | 'run_action' | 'submit_form' | 'refresh' | 'custom';
-  
-  // Navigation
-  path?: string;
-  
-  // Modal
-  modal?: string;
-  
-  // Action execution
-  action?: string;
-  object?: string;
-  
-  // Custom handler
-  handler?: string;
-  
-  // User feedback
-  confirm?: string;
-  success_message?: string;
-  on_error?: 'show_toast' | 'show_modal' | 'ignore';
-}
-```
-
-### Responsive Configuration
-
-```typescript
-interface ResponsiveConfig {
-  mobile?: {
-    columns?: number;
-    visible?: boolean;
-    order?: number;
-  };
-  tablet?: {
-    columns?: number;
-    visible?: boolean;
-    order?: number;
-  };
-  desktop?: {
-    columns?: number;
-    visible?: boolean;
-    order?: number;
-  };
-}
-```
-
-## Examples
-
-### Dashboard Layout
-
-```yaml
-name: dashboard
-label: Project Dashboard
-layout: dashboard
-
-components:
-  # KPI Metric
-  - id: total_projects
-    type: metric
-    label: Total Projects
-    data_source:
-      object: projects
-      query:
-        op: count
-    config:
-      format: number
-      icon: folder
-      color: blue
-    grid:
-      x: 0
-      y: 0
-      w: 3
-      h: 2
-  
-  # Chart
-  - id: status_chart
-    type: chart
-    label: Projects by Status
-    data_source:
-      object: projects
-      fields: ['status']
-      query:
-        op: group_by
-        field: status
-        aggregate: count
-    config:
-      chart_type: pie
-    grid:
-      x: 3
-      y: 0
-      w: 6
-      h: 4
-  
-  # Data Grid
-  - id: tasks_grid
-    type: data_grid
-    label: Recent Tasks
-    data_source:
-      object: tasks
-      fields: ['name', 'status', 'due_date']
-      sort: [['created_at', 'desc']]
-      limit: 10
-    grid:
-      x: 0
-      y: 2
-      w: 12
-      h: 6
-
-permissions:
-  view: ['admin', 'manager', 'user']
-```
-
-### Two-Column Detail Page
-
-```yaml
-name: project_detail
-label: Project Details
-layout: two_column
-
-sections:
-  # Main content
-  - id: main_content
-    type: content
-    style:
-      width: 70%
-    components:
-      - id: edit_form
-        type: form
-        label: Project Information
-        data_source:
-          object: projects
-          query:
-            op: findOne
-            filter: [['_id', '=', '{{route.params.id}}']]
-        config:
-          mode: edit
-          fields:
-            - name: name
-              label: Name
-              type: text
-            - name: description
-              label: Description
-              type: textarea
-        actions:
-          on_submit:
-            type: run_action
-            object: projects
-            action: update
-  
-  # Sidebar
-  - id: sidebar
-    type: sidebar
-    style:
-      width: 30%
-    components:
-      - id: stats
-        type: metric
-        label: Task Count
-        data_source:
-          object: tasks
-          filters:
-            - ['project', '=', '{{route.params.id}}']
-          query:
-            op: count
-```
-
-### Wizard Layout
-
-```yaml
-name: create_project
-label: Create Project
-layout: wizard
-
-components:
-  # Step 1
-  - id: step_basic
-    type: container
-    label: Basic Information
-    config:
-      step: 1
-    components:
-      - id: basic_form
-        type: form
-        config:
-          fields:
-            - name: name
-              label: Name
-              type: text
-              required: true
-  
-  # Step 2
-  - id: step_team
-    type: container
-    label: Team
-    config:
-      step: 2
-    components:
-      - id: team_form
-        type: form
-        config:
-          fields:
-            - name: owner
-              label: Owner
-              type: lookup
-              reference_to: users
-
-actions:
-  submit_wizard:
-    type: run_action
-    object: projects
-    action: create
-    success_message: Project created!
-```
-
-## Usage in Applications
-
-Pages can be referenced in application navigation:
-
-```yaml
-# app.yml
-navigation:
-  type: sidebar
-  items:
-    - type: page
-      name: dashboard
-      label: Dashboard
-      icon: dashboard
-      path: /dashboard
-    
-    - type: section
-      label: Projects
-      items:
-        - type: page
-          name: project_list
-          path: /projects
-```
-
-## Best Practices
-
-1. **Component IDs**: Use descriptive IDs (e.g., `tasks_grid` not `grid1`)
-2. **Data Binding**: Leverage `{{}}` syntax for dynamic values
-3. **Responsive Design**: Always configure responsive behavior
-4. **Access Control**: Define clear permissions
-5. **AI Context**: Provide intent and tasks for AI understanding
-6. **State Management**: Use page state for complex interactions
-7. **Performance**: Use pagination and limits for large datasets
-
-## Validation Rules
-
-- `name` must be unique within the application
-- `layout` is required
-- Either `sections` or `components` must be defined (not both for simple layouts)
-- Component `id` must be unique within the page
-- Grid positions must not overlap in dashboard layouts
-- Responsive breakpoints must be valid
-
-## File Loading
-
-Pages are automatically loaded from `*.page.yml` files by the ObjectQL loader:
-
-```typescript
-// Automatically registered
-loader.load('./src');
-
-// Access via registry
-const page = registry.get('page', 'dashboard');
-```
-
-## Integration with Studio
-
-The ObjectQL Studio provides a visual interface for:
-- Browsing registered pages
-- Previewing page layouts
-- Editing page metadata
-- Testing responsive behavior
-- Managing permissions
-
-## See Also
-
-- [Application Configuration](./application.md)
-- [Form Specification](./form.md)
-- [View Specification](./view.md)
-- [Component Library](../guide/components.md)
diff --git a/docs/spec/report.md b/docs/spec/report.md
deleted file mode 100644
index 73146925..00000000
--- a/docs/spec/report.md
+++ /dev/null
@@ -1,789 +0,0 @@
-# Report & Dashboard Metadata
-
-Report and dashboard metadata defines data visualization, analytics, and reporting capabilities. This enables business intelligence directly from ObjectQL metadata.
-
-## 1. Overview
-
-Reporting features include:
-
-- **Multiple Report Types**: Tabular, summary, matrix (pivot), chart
-- **Multi-Object Joins**: Query across related objects
-- **Grouping & Aggregations**: COUNT, SUM, AVG, MIN, MAX
-- **Filtering**: Dynamic filters and criteria
-- **Scheduling**: Automated report generation and delivery
-- **Export**: PDF, Excel, CSV formats
-- **Dashboards**: Combine multiple reports and charts
-
-**File Naming Convention:** `<report_name>.report.yml`, `<dashboard_name>.dashboard.yml`
-
-The filename (without the `.report.yml` or `.dashboard.yml` extension) automatically becomes the report/dashboard identifier.
-
-**Examples:**
-- `sales_summary.report.yml` → Report name: `sales_summary`
-- `executive_dashboard.dashboard.yml` → Dashboard name: `executive_dashboard`
-
-## 2. Report Types
-
-| Type | Description | Use Case |
-|:---|:---|:---|
-| `tabular` | Simple list/table | Flat data lists, exports |
-| `summary` | Grouped with subtotals | Sales by region, tasks by status |
-| `matrix` | Pivot table/cross-tab | Time-series analysis, comparisons |
-| `chart` | Visualization only | Dashboards, presentations |
-
-## 3. Tabular Reports
-
-Simple list reports with columns and filters:
-
-```yaml
-# File: open_tasks.report.yml
-# Report name is inferred from filename!
-
-label: Open Tasks
-type: tabular
-object: tasks
-
-# Columns
-columns:
-  - field: name
-    label: Task Name
-    width: 300
-  
-  - field: assignee.name
-    label: Assigned To
-    width: 150
-  
-  - field: priority
-    label: Priority
-    width: 100
-  
-  - field: due_date
-    label: Due Date
-    width: 120
-    format: MM/DD/YYYY
-  
-  - field: project.name
-    label: Project
-    width: 200
-
-# Filters
-filters:
-  - field: status
-    operator: "!="
-    value: completed
-  
-  - field: due_date
-    operator: ">="
-    value: $today
-
-# Sorting
-sort:
-  - field: priority
-    direction: desc
-  - field: due_date
-    direction: asc
-
-# Limit
-limit: 1000
-
-# Allow export
-export:
-  enabled: true
-  formats: [csv, excel, pdf]
-```
-
-## 4. Summary Reports
-
-Grouped reports with aggregations:
-
-```yaml
-name: sales_by_region
-label: Sales Summary by Region
-type: summary
-object: orders
-
-# Grouping Levels
-groupings:
-  # Primary grouping
-  - field: customer.region
-    label: Region
-    sort: asc
-  
-  # Secondary grouping
-  - field: product_category
-    label: Category
-    sort: asc
-
-# Detail Columns
-columns:
-  - field: order_number
-    label: Order #
-  
-  - field: customer.name
-    label: Customer
-  
-  - field: order_date
-    label: Date
-    format: MM/DD/YYYY
-  
-  - field: amount
-    label: Amount
-    format: currency
-
-# Aggregations
-aggregations:
-  # Count of records
-  - function: count
-    field: id
-    label: Total Orders
-    display_at: [group, total]
-  
-  # Sum
-  - function: sum
-    field: amount
-    label: Total Sales
-    format: currency
-    display_at: [group, total]
-  
-  # Average
-  - function: avg
-    field: amount
-    label: Average Order Value
-    format: currency
-    display_at: [group, total]
-  
-  # Min/Max
-  - function: min
-    field: order_date
-    label: First Order
-    format: date
-    display_at: [group]
-  
-  - function: max
-    field: order_date
-    label: Last Order
-    format: date
-    display_at: [group]
-
-# Filters
-filters:
-  - field: status
-    operator: "="
-    value: completed
-  
-  - field: order_date
-    operator: between
-    value: [$start_of_year, $end_of_year]
-
-# Chart
-chart:
-  enabled: true
-  type: bar
-  x_axis: customer.region
-  y_axis: amount
-  aggregation: sum
-```
-
-## 5. Matrix Reports
-
-Pivot table / cross-tab reports:
-
-```yaml
-name: sales_by_month_and_product
-label: Sales Matrix
-type: matrix
-object: orders
-
-# Row Grouping
-row_groupings:
-  - field: product.category
-    label: Product Category
-    sort: asc
-  
-  - field: product.name
-    label: Product
-    sort: asc
-
-# Column Grouping
-column_groupings:
-  - field: order_date
-    label: Month
-    date_function: month  # year, quarter, month, week, day
-    format: MMM YYYY
-
-# Measure (Value in cells)
-measure:
-  function: sum
-  field: amount
-  label: Total Sales
-  format: currency
-
-# Show Totals
-totals:
-  row_totals: true
-  column_totals: true
-  grand_total: true
-
-# Filters
-filters:
-  - field: order_date
-    operator: ">="
-    value: $start_of_year
-  
-  - field: status
-    operator: "="
-    value: completed
-
-# Chart
-chart:
-  enabled: true
-  type: stacked_bar
-```
-
-## 6. Chart Reports
-
-Visualization-focused reports:
-
-```yaml
-name: revenue_trend
-label: Revenue Trend
-type: chart
-object: orders
-
-# Chart Configuration
-chart:
-  type: line  # line, bar, pie, donut, area, scatter
-  title: Monthly Revenue Trend
-  
-  # Data
-  x_axis:
-    field: order_date
-    label: Month
-    date_function: month
-    format: MMM YYYY
-  
-  y_axis:
-    function: sum
-    field: amount
-    label: Revenue
-    format: currency
-  
-  # Multiple series
-  series:
-    field: product_category
-    label: Category
-  
-  # Styling
-  height: 400
-  show_legend: true
-  show_grid: true
-  show_data_labels: false
-  
-  # Colors
-  color_scheme: default  # default, blue, green, red, custom
-  
-  # Interactive
-  interactive: true
-  allow_drill_down: true
-
-# Filters
-filters:
-  - field: order_date
-    operator: ">="
-    value: $start_of_year
-  
-  - field: status
-    operator: "="
-    value: completed
-```
-
-### 6.1 Chart Types
-
-```yaml
-# Bar Chart
-chart:
-  type: bar
-  orientation: vertical  # vertical, horizontal
-  stacked: false
-
-# Line Chart
-chart:
-  type: line
-  smooth: true
-  fill_area: false
-
-# Pie/Donut Chart
-chart:
-  type: pie  # or donut
-  show_percentage: true
-  show_labels: true
-
-# Area Chart
-chart:
-  type: area
-  stacked: true
-
-# Scatter Plot
-chart:
-  type: scatter
-  x_axis: { field: quantity }
-  y_axis: { field: price }
-  size_by: { field: discount }
-
-# Combo Chart
-chart:
-  type: combo
-  series:
-    - type: bar
-      field: revenue
-      y_axis: primary
-    - type: line
-      field: profit_margin
-      y_axis: secondary
-```
-
-## 7. Dashboard Configuration
-
-Combine multiple reports and charts:
-
-```yaml
-name: sales_dashboard
-label: Sales Dashboard
-description: Executive sales overview
-
-# Layout
-layout:
-  columns: 12  # Grid system
-  
-  # Widgets
-  widgets:
-    # KPI Cards
-    - type: metric
-      title: Total Revenue
-      position: { row: 1, col: 1, width: 3, height: 2 }
-      metric:
-        object: orders
-        function: sum
-        field: amount
-        format: currency
-        filters:
-          - field: status
-            value: completed
-      
-      # Comparison
-      compare_to: previous_month
-      show_trend: true
-    
-    - type: metric
-      title: Active Customers
-      position: { row: 1, col: 4, width: 3, height: 2 }
-      metric:
-        object: customers
-        function: count
-        field: id
-        filters:
-          - field: status
-            value: active
-    
-    - type: metric
-      title: Avg Order Value
-      position: { row: 1, col: 7, width: 3, height: 2 }
-      metric:
-        object: orders
-        function: avg
-        field: amount
-        format: currency
-    
-    - type: metric
-      title: Conversion Rate
-      position: { row: 1, col: 10, width: 3, height: 2 }
-      metric:
-        formula: (completed_orders / total_leads) * 100
-        format: percentage
-    
-    # Chart Widget
-    - type: chart
-      title: Revenue Trend
-      position: { row: 3, col: 1, width: 8, height: 4 }
-      report: revenue_trend
-    
-    # Table Widget
-    - type: table
-      title: Top Products
-      position: { row: 3, col: 9, width: 4, height: 4 }
-      report: top_products
-      limit: 10
-    
-    # Chart Widget 2
-    - type: chart
-      title: Sales by Region
-      position: { row: 7, col: 1, width: 6, height: 4 }
-      report: sales_by_region
-    
-    # Chart Widget 3
-    - type: chart
-      title: Product Mix
-      position: { row: 7, col: 7, width: 6, height: 4 }
-      chart:
-        type: pie
-        object: order_items
-        measure: { function: sum, field: quantity }
-        grouping: product_category
-
-# Filters (apply to all widgets)
-filters:
-  - name: date_range
-    label: Date Range
-    type: date_range
-    default: this_month
-  
-  - name: region
-    label: Region
-    type: select
-    object: regions
-    field: name
-    allow_all: true
-
-# Refresh
-refresh:
-  auto_refresh: true
-  interval: 300  # 5 minutes
-
-# Permissions
-permissions:
-  view: [admin, manager, sales]
-  edit: [admin]
-```
-
-## 8. Report Filters
-
-### 8.1 Standard Filters
-
-```yaml
-filters:
-  # Equality
-  - field: status
-    operator: "="
-    value: active
-  
-  # Comparison
-  - field: amount
-    operator: ">"
-    value: 1000
-  
-  # Range
-  - field: created_date
-    operator: between
-    value: [2024-01-01, 2024-12-31]
-  
-  # List
-  - field: category
-    operator: in
-    value: [electronics, computers, phones]
-  
-  # String matching
-  - field: name
-    operator: contains
-    value: laptop
-  
-  # Null check
-  - field: deleted_date
-    operator: is_null
-```
-
-### 8.2 Dynamic Filters
-
-```yaml
-filters:
-  # Current user
-  - field: owner_id
-    operator: "="
-    value: $current_user.id
-  
-  # Date functions
-  - field: created_date
-    operator: "="
-    value: $today
-  
-  # Relative dates
-  - field: created_date
-    operator: ">="
-    value: $start_of_month
-  
-  # Formulas
-  - field: total
-    operator: ">"
-    value: $average_order_value * 2
-```
-
-### 8.3 User Filters
-
-Allow users to customize filters:
-
-```yaml
-user_filters:
-  - name: date_range
-    label: Date Range
-    field: order_date
-    type: date_range
-    default: this_month
-    required: false
-  
-  - name: status
-    label: Status
-    field: status
-    type: multi_select
-    options:
-      - draft
-      - pending
-      - completed
-    default: [pending, completed]
-  
-  - name: region
-    label: Region
-    field: customer.region
-    type: lookup
-    object: regions
-    allow_all: true
-  
-  - name: amount_min
-    label: Min Amount
-    field: amount
-    type: number
-    operator: ">="
-```
-
-## 9. Formulas & Calculated Fields
-
-Create computed values:
-
-```yaml
-columns:
-  # Simple calculation
-  - name: profit
-    label: Profit
-    formula: revenue - cost
-    format: currency
-  
-  # Percentage
-  - name: profit_margin
-    label: Profit Margin
-    formula: (revenue - cost) / revenue * 100
-    format: percentage
-  
-  # Conditional
-  - name: status_category
-    label: Category
-    formula: |
-      if (amount > 10000) {
-        return 'High Value';
-      } else if (amount > 1000) {
-        return 'Medium Value';
-      } else {
-        return 'Low Value';
-      }
-  
-  # Date calculations
-  - name: days_open
-    label: Days Open
-    formula: $today - created_date
-    format: number
-  
-  # Lookup
-  - name: account_owner_name
-    label: Account Owner
-    formula: customer.account.owner.name
-```
-
-## 10. Scheduling & Distribution
-
-Automate report generation:
-
-```yaml
-schedule:
-  # Enable scheduling
-  enabled: true
-  
-  # Frequency
-  frequency: weekly  # daily, weekly, monthly, custom
-  
-  # Custom schedule
-  cron: "0 9 * * 1"  # Every Monday at 9 AM
-  
-  # Time zone
-  timezone: America/New_York
-  
-  # Distribution
-  recipients:
-    - email: sales-team@company.com
-    - user_id: manager_123
-    - role: executive
-  
-  # Email settings
-  email:
-    subject: Weekly Sales Report - ${date}
-    body: |
-      Please find attached the weekly sales report.
-      
-      Report Period: ${start_date} to ${end_date}
-    
-    # Attachment format
-    format: pdf  # pdf, excel, csv
-    
-    # Inline preview
-    include_preview: true
-  
-  # Filters for scheduled run
-  filter_values:
-    date_range: last_week
-    region: all
-```
-
-## 11. Export Configuration
-
-```yaml
-export:
-  enabled: true
-  
-  # Available formats
-  formats:
-    - csv
-    - excel
-    - pdf
-  
-  # Excel options
-  excel:
-    sheet_name: Sales Report
-    include_filters: true
-    include_chart: true
-    freeze_header: true
-  
-  # PDF options
-  pdf:
-    page_size: letter  # letter, a4, legal
-    orientation: portrait  # portrait, landscape
-    include_logo: true
-    header: Company Sales Report
-    footer: "Page ${page} of ${total_pages}"
-  
-  # CSV options
-  csv:
-    delimiter: ","
-    include_header: true
-    encoding: utf-8
-```
-
-## 12. Performance Optimization
-
-```yaml
-performance:
-  # Caching
-  cache:
-    enabled: true
-    ttl: 3600  # 1 hour
-    
-    # Cache key includes
-    cache_key_fields:
-      - filters
-      - user_id
-  
-  # Pagination
-  pagination:
-    enabled: true
-    page_size: 100
-    max_records: 10000
-  
-  # Indexing hints
-  use_indexes:
-    - customer.region
-    - order_date
-  
-  # Query optimization
-  optimize:
-    push_down_filters: true
-    parallel_execution: true
-```
-
-## 13. Access Control
-
-```yaml
-permissions:
-  # Who can view
-  view:
-    - admin
-    - manager
-    - sales_rep
-  
-  # Who can edit report definition
-  edit:
-    - admin
-  
-  # Row-level security
-  row_level_security:
-    enabled: true
-    filter:
-      # Users only see their own data
-      field: owner_id
-      operator: "="
-      value: $current_user.id
-    
-    # Except for admins
-    bypass_roles:
-      - admin
-      - manager
-  
-  # Field-level security
-  field_restrictions:
-    cost:
-      visible_to: [admin, finance]
-    
-    profit_margin:
-      visible_to: [admin, executive]
-```
-
-## 14. Implementation Example
-
-```typescript
-// src/reports/sales_summary.report.yml
-import { ReportDefinition } from '@objectql/types';
-
-export const sales_summary: ReportDefinition = {
-  name: 'sales_summary',
-  type: 'summary',
-  object: 'orders',
-  groupings: [
-    { field: 'customer.region', label: 'Region' }
-  ],
-  aggregations: [
-    { function: 'sum', field: 'amount', label: 'Total Sales' },
-    { function: 'count', field: 'id', label: 'Order Count' }
-  ],
-  filters: [
-    ['status', '=', 'completed']
-  ],
-  chart: {
-    enabled: true,
-    type: 'bar',
-    x_axis: 'customer.region',
-    y_axis: 'amount'
-  }
-};
-```
-
-## 15. Best Practices
-
-1. **Performance**: Use indexes, limit record counts
-2. **Filters**: Provide sensible default filters
-3. **Aggregations**: Use appropriate summary functions
-4. **Formatting**: Apply proper number/date formatting
-5. **Permissions**: Implement row-level security
-6. **Caching**: Enable caching for frequently-run reports
-7. **Naming**: Use clear, descriptive names
-8. **Documentation**: Document report purpose and filters
-
-## 16. Related Specifications
-
-- [Objects & Fields](./object.md) - Data models
-- [Query Language](./query-language.md) - Query syntax
-- [Views](./view.md) - Display layouts
-- [Permissions](./permission.md) - Access control
diff --git a/docs/spec/view.md b/docs/spec/view.md
deleted file mode 100644
index 4f899bd4..00000000
--- a/docs/spec/view.md
+++ /dev/null
@@ -1,416 +0,0 @@
-# View & Layout Metadata
-
-Views define how data is presented to users in different contexts (list, detail, grid, kanban, calendar, etc.). They are the UI presentation layer of ObjectQL metadata.
-
-## 1. Overview
-
-View metadata separates the presentation logic from the data model, allowing the same object to be displayed differently based on context, user role, or device type.
-
-**File Naming Convention:** `<view_name>.view.yml`
-
-The filename (without the `.view.yml` extension) automatically becomes the view's identifier. This eliminates the need for a redundant `name` property.
-
-**Examples:**
-- `task_list.view.yml` → View name: `task_list`
-- `customer_kanban.view.yml` → View name: `customer_kanban`
-- `project_calendar.view.yml` → View name: `project_calendar`
-
-## 2. View Types
-
-ObjectQL supports multiple view types for different use cases:
-
-| View Type | Description | Use Case |
-|:---|:---|:---|
-| `list` | Tabular list of records | Default view for browsing data |
-| `grid` | Data grid with inline editing | Power user data entry |
-| `kanban` | Kanban board grouped by field | Task/project management |
-| `calendar` | Calendar view with events | Scheduling, timeline views |
-| `timeline` | Gantt-style timeline | Project planning |
-| `card` | Card-based layout | Mobile-friendly browsing |
-| `detail` | Single record detail view | Record inspection |
-| `form` | Editable form layout | Data entry/editing |
-
-## 3. Root Properties
-
-```yaml
-# File: task_list.view.yml
-# View name is inferred from filename!
-
-label: Task List
-type: list
-object: tasks  # Must specify which object to display
-description: Default task listing view
-
-# View Configuration
-config:
-  columns: [...]
-  filters: [...]
-  sort: [...]
-  actions: [...]
-```
-
-| Property | Type | Required | Description |
-|:---|:---|:---|:---|
-| `label` | `string` | ✓ | Display name for the view |
-| `type` | `ViewType` | ✓ | Type of view (list, grid, kanban, etc.) |
-| `object` | `string` | ✓ | Target object name |
-| `description` | `string` | | Help text or purpose |
-| `icon` | `string` | | Icon identifier |
-| `default` | `boolean` | | Whether this is the default view for the object |
-| `config` | `object` | ✓ | View-specific configuration |
-
-**Note:** The `name` property is **no longer needed** - it's automatically inferred from the filename.
-
-## 4. List View Configuration
-
-The most common view type for browsing records.
-
-```yaml
-# File: task_list.view.yml
-
-type: list
-object: tasks
-config:
-  # Column Definitions
-  columns:
-    - field: name
-      label: Task Name
-      width: 300
-      sortable: true
-      searchable: true
-      
-    - field: status
-      label: Status
-      width: 120
-      renderer: badge
-      
-    - field: priority
-      label: Priority
-      width: 100
-      renderer: priority_indicator
-      
-    - field: assignee.name
-      label: Assigned To
-      width: 150
-      
-    - field: due_date
-      label: Due Date
-      width: 120
-      renderer: date
-      format: MM/DD/YYYY
-  
-  # Default Filters
-  default_filters:
-    - field: status
-      operator: "!="
-      value: completed
-  
-  # Default Sort Order
-  default_sort:
-    - field: priority
-      direction: desc
-    - field: due_date
-      direction: asc
-  
-  # Pagination
-  page_size: 50
-  
-  # Available Actions
-  row_actions:
-    - complete_task
-    - edit
-    - delete
-  
-  bulk_actions:
-    - bulk_assign
-    - bulk_delete
-```
-
-### 4.1 Column Configuration
-
-| Property | Type | Description |
-|:---|:---|:---|
-| `field` | `string` | Field path (supports dot notation for related fields) |
-| `label` | `string` | Column header text |
-| `width` | `number` | Column width in pixels |
-| `sortable` | `boolean` | Enable column sorting |
-| `searchable` | `boolean` | Include in search filter |
-| `renderer` | `string` | Custom renderer type (badge, link, date, etc.) |
-| `format` | `string` | Format string for dates/numbers |
-| `hidden` | `boolean` | Hide by default (user can unhide) |
-
-## 5. Kanban View Configuration
-
-Kanban views group records by a specific field value.
-
-```yaml
-name: task_kanban
-type: kanban
-object: tasks
-config:
-  # Grouping Field
-  group_by: status
-  
-  # Card Configuration
-  card:
-    title_field: name
-    subtitle_field: assignee.name
-    description_field: description
-    image_field: cover_image
-    
-    # Additional fields to display on card
-    fields:
-      - field: priority
-        renderer: badge
-      - field: due_date
-        renderer: date_badge
-    
-    # Card Actions
-    actions:
-      - edit
-      - delete
-  
-  # Column Configuration
-  columns:
-    - value: backlog
-      label: Backlog
-      color: gray
-      
-    - value: in_progress
-      label: In Progress
-      color: blue
-      limit: 5  # WIP limit
-      
-    - value: done
-      label: Done
-      color: green
-  
-  # Enable drag & drop between columns
-  draggable: true
-  
-  # Filter
-  filters:
-    - field: archived
-      operator: "="
-      value: false
-```
-
-## 6. Calendar View Configuration
-
-Calendar views display records as events on a timeline.
-
-```yaml
-name: event_calendar
-type: calendar
-object: events
-config:
-  # Date Field Mapping
-  start_date_field: start_time
-  end_date_field: end_time
-  all_day_field: is_all_day
-  
-  # Event Display
-  title_field: name
-  color_field: event_type
-  
-  # Color Mapping
-  color_mapping:
-    meeting: blue
-    deadline: red
-    holiday: green
-  
-  # Default View
-  default_view: month  # month, week, day, agenda
-  
-  # Allow creation via click
-  allow_create: true
-  
-  # Actions
-  event_actions:
-    - edit
-    - delete
-    - duplicate
-```
-
-## 7. Detail View Configuration
-
-Detail views show a single record with full field display.
-
-```yaml
-name: project_detail
-type: detail
-object: projects
-config:
-  # Layout Sections
-  sections:
-    - name: overview
-      label: Project Overview
-      columns: 2
-      fields:
-        - name
-        - status
-        - owner
-        - start_date
-        - end_date
-        - budget
-    
-    - name: description
-      label: Description
-      columns: 1
-      fields:
-        - description
-        - objectives
-    
-    - name: team
-      label: Team Members
-      type: related_list
-      relation: team_members
-      columns:
-        - member.name
-        - role
-        - hours_allocated
-  
-  # Related Lists (child objects)
-  related_lists:
-    - object: tasks
-      relation_field: project_id
-      label: Project Tasks
-      default_view: task_list
-      allow_create: true
-      
-    - object: files
-      relation_field: project_id
-      label: Attachments
-      view_type: grid
-```
-
-## 8. Responsive Design
-
-Views can define responsive breakpoints for mobile/tablet optimization.
-
-```yaml
-config:
-  responsive:
-    mobile:
-      # Show fewer columns on mobile
-      columns:
-        - name
-        - status
-      
-      # Use card layout instead of table
-      layout: card
-      
-    tablet:
-      columns:
-        - name
-        - status
-        - assignee
-        - due_date
-```
-
-## 9. Conditional Rendering
-
-Show/hide elements based on conditions.
-
-```yaml
-config:
-  columns:
-    - field: internal_notes
-      label: Internal Notes
-      # Only show to admins
-      visible_if:
-        user_role: admin
-    
-    - field: approval_status
-      label: Approval
-      # Only show if amount > 1000
-      visible_if:
-        field: amount
-        operator: ">"
-        value: 1000
-```
-
-## 10. Custom Renderers
-
-Define custom rendering logic for specific field types.
-
-```yaml
-config:
-  renderers:
-    priority_indicator:
-      type: component
-      component: PriorityBadge
-      props:
-        showIcon: true
-        
-    status_badge:
-      type: badge
-      color_mapping:
-        draft: gray
-        pending: yellow
-        approved: green
-        rejected: red
-```
-
-## 11. View Permissions
-
-Control who can see and use specific views.
-
-```yaml
-permissions:
-  # Who can see this view
-  read:
-    - admin
-    - manager
-    - user
-  
-  # Who can modify view settings
-  modify:
-    - admin
-  
-  # Field-level visibility
-  field_permissions:
-    salary:
-      visible_to: [admin, hr_manager]
-```
-
-## 12. Implementation Example
-
-```typescript
-// src/views/task_list.view.yml
-import { ViewDefinition } from '@objectql/types';
-
-export const task_list: ViewDefinition = {
-  name: 'task_list',
-  type: 'list',
-  object: 'tasks',
-  config: {
-    columns: [
-      { field: 'name', label: 'Task', width: 300 },
-      { field: 'status', label: 'Status', renderer: 'badge' }
-    ],
-    default_filters: [
-      ['status', '!=', 'completed']
-    ],
-    default_sort: [
-      ['priority', 'desc']
-    ]
-  }
-};
-```
-
-## 13. Best Practices
-
-1. **Start Simple**: Begin with list and detail views, add specialized views as needed
-2. **Reusable Renderers**: Create custom renderers for commonly used patterns
-3. **Mobile First**: Always define responsive behavior for mobile devices
-4. **Performance**: Limit initial column count for large datasets
-5. **User Customization**: Allow users to save personal view preferences
-6. **Accessibility**: Ensure proper ARIA labels and keyboard navigation
-
-## 14. Related Specifications
-
-- [Objects & Fields](./object.md) - Data model definition
-- [Forms](./form.md) - Editable form layouts
-- [Permissions](./permission.md) - Access control
-- [Actions](./action.md) - Available operations
diff --git a/examples/browser/README.md b/examples/browser/README.md
deleted file mode 100644
index df1b932f..00000000
--- a/examples/browser/README.md
+++ /dev/null
@@ -1,154 +0,0 @@
-# Browser Example for @objectql/sdk
-
-This example demonstrates how to use `@objectql/sdk` in different environments:
-
-- **`index.html`** - Pure browser example (no build tools)
-- **`example-node.ts`** - Node.js/TypeScript example
-
-## 🚀 Quick Start
-
-### Prerequisites
-
-You need a running ObjectQL server. You can start one using:
-
-```bash
-# From the repository root
-cd examples/starters/hello-world
-npm install
-npm start
-```
-
-The server will be available at `http://localhost:3000`.
-
-### Running the Browser Example
-
-1. **Open the HTML file directly in a browser:**
-
-```bash
-# Open in your default browser
-open index.html  # macOS
-xdg-open index.html  # Linux
-start index.html  # Windows
-```
-
-2. **Or serve it with a simple HTTP server:**
-
-```bash
-# Using Python
-python3 -m http.server 8080
-
-# Using Node.js http-server
-npx http-server -p 8080
-
-# Using PHP
-php -S localhost:8080
-```
-
-Then navigate to `http://localhost:8080` in your browser.
-
-### Running the Node.js Example
-
-```bash
-# Install dependencies (if not already installed)
-cd ../../
-pnpm install
-
-# Run the example
-cd examples/browser
-npx ts-node example-node.ts
-```
-
-Or compile and run:
-
-```bash
-npx tsc example-node.ts
-node example-node.js
-```
-
-## 📋 Features Demonstrated
-
-The example shows how to:
-
-- ✅ Initialize `DataApiClient` and `MetadataApiClient` in the browser
-- ✅ List records with filtering and pagination
-- ✅ Get object metadata and schema
-- ✅ Create new records
-- ✅ Count records with filters
-- ✅ Handle errors and loading states
-- ✅ Works in all modern browsers (polyfill built-in!)
-
-## 🌐 Browser Compatibility
-
-This example works in all modern browsers:
-
-- Chrome 90+
-- Firefox 90+
-- Safari 15+
-- Edge 90+
-
-**Note:** The `@objectql/sdk` package automatically includes a polyfill for `AbortSignal.timeout()`, so it works seamlessly in older browsers without any additional configuration!
-
-## 🔧 Using in Production
-
-For production applications, we recommend:
-
-### Option 1: Using a Module Bundler (Recommended)
-
-```bash
-npm install @objectql/sdk @objectql/types
-```
-
-```javascript
-import { DataApiClient, MetadataApiClient } from '@objectql/sdk';
-
-const client = new DataApiClient({
-    baseUrl: process.env.API_URL
-});
-```
-
-### Option 2: Using ES Modules via CDN
-
-```html
-<script type="module">
-    import { DataApiClient } from 'https://cdn.skypack.dev/@objectql/sdk';
-    
-    const client = new DataApiClient({
-        baseUrl: 'https://api.example.com'
-    });
-</script>
-```
-
-### Option 3: Self-hosted ES Modules
-
-After building the package, you can serve the dist files:
-
-```html
-<script type="module">
-    import { DataApiClient } from '/node_modules/@objectql/sdk/dist/index.js';
-    
-    const client = new DataApiClient({
-        baseUrl: 'http://localhost:3000'
-    });
-</script>
-```
-
-## 🔒 Security Considerations
-
-When using the SDK in the browser:
-
-1. **Never hardcode sensitive tokens** - Store them in environment variables or secure storage
-2. **Use HTTPS** in production
-3. **Implement CORS** properly on your ObjectQL server
-4. **Validate all user input** before sending to the API
-5. **Use Content Security Policy (CSP)** headers
-
-## 📚 Additional Resources
-
-- [ObjectQL SDK Documentation](../../packages/drivers/sdk/README.md)
-- [Client SDK API Guide](../../docs/api/client-sdk.md)
-- [REST API Reference](../../docs/api/rest.md)
-- [ObjectQL Website](https://objectql.org)
-
-## 🤝 Contributing
-
-Found an issue or want to improve this example? Please open an issue or submit a PR!
diff --git a/examples/browser/example-node.ts b/examples/browser/example-node.ts
deleted file mode 100644
index 067846db..00000000
--- a/examples/browser/example-node.ts
+++ /dev/null
@@ -1,86 +0,0 @@
-/**
- * Simple Node.js example using @objectql/sdk
- * 
- * This demonstrates how to use the ObjectQL SDK in a Node.js environment.
- * The same code works in browsers, Deno, and edge runtimes!
- */
-
-import { DataApiClient, MetadataApiClient } from '@objectql/sdk';
-
-// Initialize clients
-const dataClient = new DataApiClient({
-    baseUrl: process.env.OBJECTQL_URL || 'http://localhost:3000',
-    token: process.env.OBJECTQL_TOKEN // Optional authentication
-});
-
-const metadataClient = new MetadataApiClient({
-    baseUrl: process.env.OBJECTQL_URL || 'http://localhost:3000'
-});
-
-async function main() {
-    try {
-        console.log('🚀 ObjectQL SDK Node.js Example\n');
-
-        // 1. List all available objects
-        console.log('📚 Listing all objects...');
-        const objectsResponse = await metadataClient.listObjects();
-        console.log(`Found ${objectsResponse.items?.length || 0} objects:\n`);
-        objectsResponse.items?.forEach(obj => {
-            console.log(`  - ${obj.name} (${obj.label})`);
-        });
-
-        // 2. Get schema for a specific object (e.g., 'users')
-        console.log('\n🔍 Getting schema for "users" object...');
-        const userSchema = await metadataClient.getObject('users');
-        console.log(`\nObject: ${userSchema.label}`);
-        console.log('Fields:');
-        Object.entries(userSchema.fields).forEach(([key, field]) => {
-            console.log(`  - ${field.name} (${field.type})${field.required ? ' *required' : ''}`);
-        });
-
-        // 3. List users with filtering
-        console.log('\n📋 Listing active users...');
-        const usersResponse = await dataClient.list('users', {
-            filter: [['status', '=', 'active']],
-            sort: [['created_at', 'desc']],
-            limit: 5
-        });
-        console.log(`Found ${usersResponse.items?.length || 0} active users`);
-        usersResponse.items?.forEach(user => {
-            console.log(`  - ${user.name} (${user.email})`);
-        });
-
-        // 4. Count total users
-        console.log('\n🔢 Counting all users...');
-        const countResponse = await dataClient.count('users');
-        console.log(`Total users: ${countResponse.count}`);
-
-        // 5. Create a new user (example - commented out to avoid side effects)
-        /*
-        console.log('\n➕ Creating a new user...');
-        const newUser = await dataClient.create('users', {
-            name: 'SDK Example User',
-            email: `sdk-example-${Date.now()}@example.com`,
-            status: 'active'
-        });
-        console.log(`Created user: ${newUser.name} (ID: ${newUser._id})`);
-        */
-
-        console.log('\n✅ Example completed successfully!');
-    } catch (error) {
-        console.error('\n❌ Error:', error.message);
-        
-        if (error.code) {
-            console.error('Error code:', error.code);
-        }
-        
-        if (error.details) {
-            console.error('Details:', error.details);
-        }
-
-        process.exit(1);
-    }
-}
-
-// Run the example
-main();
diff --git a/examples/browser/index.html b/examples/browser/index.html
deleted file mode 100644
index bb3bb58c..00000000
--- a/examples/browser/index.html
+++ /dev/null
@@ -1,519 +0,0 @@
-<!DOCTYPE html>
-<html lang="en">
-<head>
-    <meta charset="UTF-8">
-    <meta name="viewport" content="width=device-width, initial-scale=1.0">
-    <title>ObjectQL SDK Browser Example</title>
-    <style>
-        * {
-            margin: 0;
-            padding: 0;
-            box-sizing: border-box;
-        }
-
-        body {
-            font-family: -apple-system, BlinkMacSystemFont, 'Segoe UI', Roboto, Oxygen, Ubuntu, sans-serif;
-            background: linear-gradient(135deg, #667eea 0%, #764ba2 100%);
-            min-height: 100vh;
-            padding: 20px;
-        }
-
-        .container {
-            max-width: 1200px;
-            margin: 0 auto;
-        }
-
-        header {
-            background: white;
-            padding: 30px;
-            border-radius: 10px;
-            box-shadow: 0 10px 30px rgba(0, 0, 0, 0.2);
-            margin-bottom: 30px;
-        }
-
-        h1 {
-            color: #667eea;
-            margin-bottom: 10px;
-        }
-
-        .subtitle {
-            color: #666;
-            font-size: 1.1em;
-        }
-
-        .config-panel {
-            background: white;
-            padding: 25px;
-            border-radius: 10px;
-            box-shadow: 0 10px 30px rgba(0, 0, 0, 0.2);
-            margin-bottom: 20px;
-        }
-
-        .config-panel h2 {
-            color: #333;
-            margin-bottom: 20px;
-        }
-
-        .input-group {
-            margin-bottom: 15px;
-        }
-
-        label {
-            display: block;
-            margin-bottom: 5px;
-            color: #555;
-            font-weight: 500;
-        }
-
-        input[type="text"],
-        input[type="url"] {
-            width: 100%;
-            padding: 10px;
-            border: 2px solid #e0e0e0;
-            border-radius: 5px;
-            font-size: 14px;
-            transition: border-color 0.3s;
-        }
-
-        input:focus {
-            outline: none;
-            border-color: #667eea;
-        }
-
-        button {
-            background: #667eea;
-            color: white;
-            border: none;
-            padding: 12px 30px;
-            border-radius: 5px;
-            font-size: 16px;
-            cursor: pointer;
-            transition: background 0.3s;
-            margin-right: 10px;
-            margin-top: 10px;
-        }
-
-        button:hover {
-            background: #5568d3;
-        }
-
-        button:disabled {
-            background: #ccc;
-            cursor: not-allowed;
-        }
-
-        .results-panel {
-            background: white;
-            padding: 25px;
-            border-radius: 10px;
-            box-shadow: 0 10px 30px rgba(0, 0, 0, 0.2);
-        }
-
-        .results-panel h2 {
-            color: #333;
-            margin-bottom: 20px;
-        }
-
-        #results {
-            background: #f7f7f7;
-            padding: 20px;
-            border-radius: 5px;
-            max-height: 500px;
-            overflow-y: auto;
-        }
-
-        .loading {
-            text-align: center;
-            color: #667eea;
-            padding: 40px;
-        }
-
-        .error {
-            background: #fee;
-            color: #c33;
-            padding: 15px;
-            border-radius: 5px;
-            border-left: 4px solid #c33;
-        }
-
-        .success {
-            background: #efe;
-            color: #3c3;
-            padding: 15px;
-            border-radius: 5px;
-            border-left: 4px solid #3c3;
-        }
-
-        pre {
-            background: #2d2d2d;
-            color: #f8f8f2;
-            padding: 15px;
-            border-radius: 5px;
-            overflow-x: auto;
-            white-space: pre-wrap;
-            word-wrap: break-word;
-        }
-
-        .item-card {
-            background: white;
-            padding: 15px;
-            margin-bottom: 10px;
-            border-radius: 5px;
-            border-left: 4px solid #667eea;
-        }
-
-        .item-card h3 {
-            color: #333;
-            margin-bottom: 10px;
-        }
-
-        .item-card p {
-            color: #666;
-            margin: 5px 0;
-        }
-
-        .tabs {
-            display: flex;
-            gap: 10px;
-            margin-bottom: 20px;
-        }
-
-        .tab {
-            padding: 10px 20px;
-            background: #f0f0f0;
-            border: none;
-            border-radius: 5px;
-            cursor: pointer;
-            transition: all 0.3s;
-        }
-
-        .tab.active {
-            background: #667eea;
-            color: white;
-        }
-
-        .tab-content {
-            display: none;
-        }
-
-        .tab-content.active {
-            display: block;
-        }
-    </style>
-</head>
-<body>
-    <div class="container">
-        <header>
-            <h1>🚀 ObjectQL SDK Browser Example</h1>
-            <p class="subtitle">Demonstrating @objectql/sdk in a pure browser environment</p>
-        </header>
-
-        <div class="config-panel">
-            <h2>⚙️ Configuration</h2>
-            <div class="input-group">
-                <label for="baseUrl">API Base URL</label>
-                <input type="url" id="baseUrl" value="http://localhost:3000" placeholder="http://localhost:3000">
-            </div>
-            <div class="input-group">
-                <label for="token">Authentication Token (Optional)</label>
-                <input type="text" id="token" placeholder="your-auth-token">
-            </div>
-            <div class="input-group">
-                <label for="objectName">Object Name</label>
-                <input type="text" id="objectName" value="users" placeholder="users">
-            </div>
-        </div>
-
-        <div class="results-panel">
-            <h2>📊 Actions</h2>
-            <div class="tabs">
-                <button class="tab active" data-tab="list">List Records</button>
-                <button class="tab" data-tab="metadata">Get Metadata</button>
-                <button class="tab" data-tab="create">Create Record</button>
-                <button class="tab" data-tab="count">Count Records</button>
-            </div>
-
-            <div id="list" class="tab-content active">
-                <button onclick="listRecords()">📋 List All Records</button>
-                <button onclick="listActiveRecords()">✅ List Active Records</button>
-            </div>
-
-            <div id="metadata" class="tab-content">
-                <button onclick="getObjectMetadata()">🔍 Get Object Schema</button>
-                <button onclick="listAllObjects()">📚 List All Objects</button>
-            </div>
-
-            <div id="create" class="tab-content">
-                <button onclick="createSampleRecord()">➕ Create Sample Record</button>
-            </div>
-
-            <div id="count" class="tab-content">
-                <button onclick="countRecords()">🔢 Count All Records</button>
-                <button onclick="countActiveRecords()">🔢 Count Active Records</button>
-            </div>
-
-            <h2 style="margin-top: 30px;">📄 Results</h2>
-            <div id="results">
-                <p style="color: #999; text-align: center;">Click a button above to perform an action...</p>
-            </div>
-        </div>
-    </div>
-
-    <script type="module">
-        // Import ObjectQL SDK
-        // Note: In a real application, you would import from:
-        // - CDN: import { DataApiClient } from 'https://unpkg.com/@objectql/sdk/dist/index.js';
-        // - Bundler: import { DataApiClient } from '@objectql/sdk';
-        // 
-        // For this demo, we implement a simple version inline.
-        // The @objectql/sdk package automatically includes a polyfill for older browsers!
-        
-        // Simple DataApiClient implementation for demo
-        // This includes the same polyfill approach as the real SDK
-        
-        // Helper function to create timeout signal with fallback
-        function createTimeoutSignal(ms) {
-            if (typeof AbortSignal !== 'undefined' && AbortSignal.timeout) {
-                return AbortSignal.timeout(ms);
-            }
-            // Fallback for older browsers
-            const controller = new AbortController();
-            setTimeout(() => controller.abort(), ms);
-            return controller.signal;
-        }
-        
-        class DataApiClient {
-            constructor(config) {
-                this.baseUrl = config.baseUrl.replace(/\/$/, '');
-                this.token = config.token;
-                this.headers = config.headers || {};
-                this.timeout = config.timeout || 30000;
-            }
-
-            async request(method, path, body, queryParams) {
-                const url = new URL(`${this.baseUrl}${path}`);
-                
-                if (queryParams) {
-                    Object.entries(queryParams).forEach(([key, value]) => {
-                        if (value !== undefined && value !== null) {
-                            url.searchParams.append(key, typeof value === 'object' ? JSON.stringify(value) : String(value));
-                        }
-                    });
-                }
-
-                const headers = {
-                    'Content-Type': 'application/json',
-                    ...this.headers
-                };
-
-                if (this.token) {
-                    headers['Authorization'] = `Bearer ${this.token}`;
-                }
-
-                const response = await fetch(url.toString(), {
-                    method,
-                    headers,
-                    body: body ? JSON.stringify(body) : undefined,
-                    signal: createTimeoutSignal(this.timeout)
-                });
-
-                return await response.json();
-            }
-
-            async list(objectName, params) {
-                return this.request('GET', `/api/data/${objectName}`, undefined, params);
-            }
-
-            async get(objectName, id) {
-                return this.request('GET', `/api/data/${objectName}/${id}`);
-            }
-
-            async create(objectName, data) {
-                return this.request('POST', `/api/data/${objectName}`, data);
-            }
-
-            async count(objectName, filters) {
-                return this.request('GET', `/api/data/${objectName}`, undefined, { filter: filters, limit: 0 });
-            }
-        }
-
-        class MetadataApiClient {
-            constructor(config) {
-                this.baseUrl = config.baseUrl.replace(/\/$/, '');
-                this.token = config.token;
-                this.headers = config.headers || {};
-                this.timeout = config.timeout || 30000;
-            }
-
-            async request(method, path) {
-                const headers = {
-                    'Content-Type': 'application/json',
-                    ...this.headers
-                };
-
-                if (this.token) {
-                    headers['Authorization'] = `Bearer ${this.token}`;
-                }
-
-                const response = await fetch(`${this.baseUrl}${path}`, {
-                    method,
-                    headers,
-                    signal: createTimeoutSignal(this.timeout)
-                });
-
-                return await response.json();
-            }
-
-            async listObjects() {
-                return this.request('GET', '/api/metadata/objects');
-            }
-
-            async getObject(objectName) {
-                return this.request('GET', `/api/metadata/object/${objectName}`);
-            }
-        }
-
-        // Global clients
-        let dataClient;
-        let metadataClient;
-
-        function initClients() {
-            const baseUrl = document.getElementById('baseUrl').value;
-            const token = document.getElementById('token').value;
-
-            dataClient = new DataApiClient({ baseUrl, token });
-            metadataClient = new MetadataApiClient({ baseUrl, token });
-        }
-
-        function showLoading() {
-            document.getElementById('results').innerHTML = '<div class="loading">⏳ Loading...</div>';
-        }
-
-        function showError(error) {
-            document.getElementById('results').innerHTML = `
-                <div class="error">
-                    <strong>❌ Error:</strong> ${error.message || error}
-                </div>
-            `;
-        }
-
-        function showSuccess(message) {
-            document.getElementById('results').innerHTML = `
-                <div class="success">
-                    <strong>✅ Success:</strong> ${message}
-                </div>
-            `;
-        }
-
-        function showJSON(data) {
-            document.getElementById('results').innerHTML = `
-                <pre>${JSON.stringify(data, null, 2)}</pre>
-            `;
-        }
-
-        // Action handlers
-        window.listRecords = async function() {
-            try {
-                initClients();
-                showLoading();
-                const objectName = document.getElementById('objectName').value;
-                const response = await dataClient.list(objectName);
-                showJSON(response);
-            } catch (error) {
-                showError(error);
-            }
-        };
-
-        window.listActiveRecords = async function() {
-            try {
-                initClients();
-                showLoading();
-                const objectName = document.getElementById('objectName').value;
-                const response = await dataClient.list(objectName, {
-                    filter: [['status', '=', 'active']],
-                    limit: 10
-                });
-                showJSON(response);
-            } catch (error) {
-                showError(error);
-            }
-        };
-
-        window.getObjectMetadata = async function() {
-            try {
-                initClients();
-                showLoading();
-                const objectName = document.getElementById('objectName').value;
-                const response = await metadataClient.getObject(objectName);
-                showJSON(response);
-            } catch (error) {
-                showError(error);
-            }
-        };
-
-        window.listAllObjects = async function() {
-            try {
-                initClients();
-                showLoading();
-                const response = await metadataClient.listObjects();
-                showJSON(response);
-            } catch (error) {
-                showError(error);
-            }
-        };
-
-        window.createSampleRecord = async function() {
-            try {
-                initClients();
-                showLoading();
-                const objectName = document.getElementById('objectName').value;
-                const response = await dataClient.create(objectName, {
-                    name: 'Sample User ' + Date.now(),
-                    email: `user${Date.now()}@example.com`,
-                    status: 'active'
-                });
-                showJSON(response);
-            } catch (error) {
-                showError(error);
-            }
-        };
-
-        window.countRecords = async function() {
-            try {
-                initClients();
-                showLoading();
-                const objectName = document.getElementById('objectName').value;
-                const response = await dataClient.count(objectName);
-                showJSON(response);
-            } catch (error) {
-                showError(error);
-            }
-        };
-
-        window.countActiveRecords = async function() {
-            try {
-                initClients();
-                showLoading();
-                const objectName = document.getElementById('objectName').value;
-                const response = await dataClient.count(objectName, [['status', '=', 'active']]);
-                showJSON(response);
-            } catch (error) {
-                showError(error);
-            }
-        };
-
-        // Tab switching
-        document.querySelectorAll('.tab').forEach(tab => {
-            tab.addEventListener('click', function() {
-                const tabName = this.dataset.tab;
-                
-                document.querySelectorAll('.tab').forEach(t => t.classList.remove('active'));
-                document.querySelectorAll('.tab-content').forEach(c => c.classList.remove('active'));
-                
-                this.classList.add('active');
-                document.getElementById(tabName).classList.add('active');
-            });
-        });
-    </script>
-</body>
-</html>
diff --git a/package.json b/package.json
index a1c288ba..a362b2a2 100644
--- a/package.json
+++ b/package.json
@@ -5,7 +5,6 @@
     "build": "tsc -b && pnpm -r run build",
     "check-versions": "node scripts/check-versions.js",
     "test": "pnpm run check-versions && pnpm -r run test",
-    "studio": "node packages/tools/cli/dist/index.js studio",
     "ai": "node packages/tools/cli/dist/index.js ai",
     "changeset": "changeset",
     "version": "changeset version",
diff --git a/packages/foundation/core/src/ai-agent.ts b/packages/foundation/core/src/ai-agent.ts
index 73dc1f46..fb876829 100644
--- a/packages/foundation/core/src/ai-agent.ts
+++ b/packages/foundation/core/src/ai-agent.ts
@@ -51,7 +51,7 @@ export interface GenerateAppResult {
     files: Array<{
         filename: string;
         content: string;
-        type: 'object' | 'validation' | 'form' | 'view' | 'page' | 'menu' | 'action' | 'hook' | 'permission' | 'workflow' | 'report' | 'data' | 'application' | 'typescript' | 'test' | 'other';
+        type: 'object' | 'validation' | 'action' | 'hook' | 'permission' | 'workflow' | 'data' | 'application' | 'typescript' | 'test' | 'other';
     }>;
     /** Any errors encountered */
     errors?: string[];
@@ -464,8 +464,7 @@ export class ObjectQLAgent {
         const fileTypes = new Set(currentFiles.map(f => f.type));
         
         const allTypes = [
-            'object', 'validation', 'form', 'view', 'page', 
-            'menu', 'action', 'hook', 'permission', 'workflow', 'report', 'data'
+            'object', 'validation', 'action', 'hook', 'permission', 'workflow', 'data'
         ];
         
         const missingTypes = allTypes.filter(t => !fileTypes.has(t as any));
@@ -478,17 +477,9 @@ export class ObjectQLAgent {
             suggestions.push('Add permissions to control access');
         }
         
-        if (!fileTypes.has('menu')) {
-            suggestions.push('Create a menu for navigation');
-        }
-        
         if (!fileTypes.has('workflow') && fileTypes.has('object')) {
             suggestions.push('Add workflows for approval processes');
         }
-        
-        if (!fileTypes.has('report') && fileTypes.has('object')) {
-            suggestions.push('Generate reports for analytics');
-        }
 
         return suggestions;
     }
@@ -512,14 +503,7 @@ Follow ObjectQL metadata standards for ALL metadata types:
   - beforeCreate, afterCreate, beforeUpdate, afterUpdate, beforeDelete, afterDelete
 - Workflows (*.workflow.yml): approval processes, automation
 
-**3. Presentation Layer:**
-- Pages (*.page.yml): composable UI pages with layouts
-- Views (*.view.yml): list views, kanban, calendar displays
-- Forms (*.form.yml): data entry forms with field layouts
-- Reports (*.report.yml): tabular, summary, matrix reports
-- Menus (*.menu.yml): navigation structure
-
-**4. Security Layer:**
+**3. Security Layer:**
 - Permissions (*.permission.yml): access control rules
 - Application (*.application.yml): app-level configuration
 
@@ -696,7 +680,6 @@ Include:
 - 2-3 core objects with essential fields
 - Basic relationships between objects
 - Simple validation rules
-- At least one form and view per object
 - At least one action with TypeScript implementation
 - At least one hook with TypeScript implementation
 
@@ -708,21 +691,15 @@ Output: Provide each file separately with clear filename headers (e.g., "# filen
 Include ALL necessary metadata types WITH implementations:
 1. **Objects**: All entities with comprehensive fields
 2. **Validations**: Business rules and constraints
-3. **Forms**: Create and edit forms for each object
-4. **Views**: List views for browsing data
-5. **Pages**: Dashboard and detail pages
-6. **Menus**: Navigation structure
-7. **Actions WITH TypeScript implementations**: Common operations (approve, export, etc.) - Generate BOTH .yml metadata AND .action.ts implementation files
-8. **Hooks WITH TypeScript implementations**: Lifecycle triggers - Generate .hook.ts implementation files
-9. **Permissions**: Basic access control
-10. **Data**: Sample seed data (optional)
-11. **Workflows**: Approval processes if applicable
-12. **Reports**: Key reports for analytics
-13. **Tests**: Generate test files (.test.ts) for actions and hooks to validate business logic
+3. **Actions WITH TypeScript implementations**: Common operations (approve, export, etc.) - Generate BOTH .yml metadata AND .action.ts implementation files
+4. **Hooks WITH TypeScript implementations**: Lifecycle triggers - Generate .hook.ts implementation files
+5. **Permissions**: Basic access control
+6. **Data**: Sample seed data (optional)
+7. **Workflows**: Approval processes if applicable
+8. **Tests**: Generate test files (.test.ts) for actions and hooks to validate business logic
 
 Consider:
 - Security and permissions from the start
-- User experience in form/view design
 - Business processes and workflows
 - Data integrity and validation
 - Complete TypeScript implementations for all actions and hooks
@@ -863,15 +840,10 @@ Provide feedback in the specified format.`;
     private inferFileType(filename: string): GenerateAppResult['files'][0]['type'] {
         if (filename.includes('.object.yml')) return 'object';
         if (filename.includes('.validation.yml')) return 'validation';
-        if (filename.includes('.form.yml')) return 'form';
-        if (filename.includes('.view.yml')) return 'view';
-        if (filename.includes('.page.yml')) return 'page';
-        if (filename.includes('.menu.yml')) return 'menu';
         if (filename.includes('.action.yml')) return 'action';
         if (filename.includes('.hook.yml')) return 'hook';
         if (filename.includes('.permission.yml')) return 'permission';
         if (filename.includes('.workflow.yml')) return 'workflow';
-        if (filename.includes('.report.yml')) return 'report';
         if (filename.includes('.data.yml')) return 'data';
         if (filename.includes('.application.yml') || filename.includes('.app.yml')) return 'application';
         if (filename.includes('.action.ts') || filename.includes('.hook.ts')) return 'typescript';
diff --git a/packages/runtime/server/src/index.ts b/packages/runtime/server/src/index.ts
index 2c4239b2..de49a20d 100644
--- a/packages/runtime/server/src/index.ts
+++ b/packages/runtime/server/src/index.ts
@@ -3,7 +3,6 @@ export * from './utils';
 export * from './openapi';
 export * from './server';
 export * from './metadata';
-export * from './studio';
 export * from './storage';
 export * from './file-handler';
 // We export createNodeHandler from root for convenience, 
diff --git a/packages/runtime/server/src/studio.ts b/packages/runtime/server/src/studio.ts
deleted file mode 100644
index c81aa169..00000000
--- a/packages/runtime/server/src/studio.ts
+++ /dev/null
@@ -1,164 +0,0 @@
-import { IncomingMessage, ServerResponse } from 'http';
-import * as fs from 'fs';
-import * as path from 'path';
-
-/**
- * Creates a handler to serve the Studio UI static files.
- */
-export function createStudioHandler() {
-    let distPath: string | null = null;
-
-    // 1. Try to resolve from installed package (Standard way)
-    try {
-        const studioPkg = require.resolve('@objectql/studio/package.json');
-        const candidate = path.join(path.dirname(studioPkg), 'dist');
-        if (fs.existsSync(candidate)) {
-            distPath = candidate;
-        }
-    } catch (e) {
-        // @objectql/studio might not be installed
-    }
-
-    // 2. Fallback for local development (Monorepo)
-    if (!distPath) {
-        const possiblePaths = [
-            path.join(__dirname, '../../studio/dist'),
-            path.join(process.cwd(), 'packages/studio/dist'),
-            path.join(process.cwd(), 'packages/tools/studio/dist'),
-        ];
-        
-        for (const p of possiblePaths) {
-            if (fs.existsSync(p)) {
-                distPath = p;
-                break;
-            }
-        }
-    }
-    
-    return async (req: IncomingMessage, res: ServerResponse) => {
-        if (!distPath) {
-            // Return placeholder page if studio is not built
-            const html = getPlaceholderPage();
-            res.setHeader('Content-Type', 'text/html');
-            res.statusCode = 200;
-            res.end(html);
-            return;
-        }
-        
-        // Parse the URL and remove /studio prefix
-        let urlPath = (req.url || '').replace(/^\/studio/, '') || '/';
-        
-        // Default to index.html for SPA routing
-        if (urlPath === '/' || !urlPath.includes('.')) {
-            urlPath = '/index.html';
-        }
-        
-        const filePath = path.join(distPath, urlPath);
-        
-        // Security check: ensure the file is within distPath
-        if (!filePath.startsWith(distPath)) {
-            res.statusCode = 403;
-            res.end('Forbidden');
-            return;
-        }
-        
-        // Check if file exists
-        if (!fs.existsSync(filePath)) {
-            // For SPA, return index.html for any non-existent routes
-            const indexPath = path.join(distPath, 'index.html');
-            if (fs.existsSync(indexPath)) {
-                const content = fs.readFileSync(indexPath);
-                res.setHeader('Content-Type', 'text/html');
-                res.statusCode = 200;
-                res.end(content);
-                return;
-            }
-            
-            res.statusCode = 404;
-            res.end('Not Found');
-            return;
-        }
-        
-        // Read and serve the file
-        const content = fs.readFileSync(filePath);
-        const ext = path.extname(filePath);
-        const contentType = getContentType(ext);
-        
-        res.setHeader('Content-Type', contentType);
-        res.statusCode = 200;
-        res.end(content);
-    };
-}
-
-function getContentType(ext: string): string {
-    const types: Record<string, string> = {
-        '.html': 'text/html',
-        '.js': 'application/javascript',
-        '.css': 'text/css',
-        '.json': 'application/json',
-        '.png': 'image/png',
-        '.jpg': 'image/jpeg',
-        '.gif': 'image/gif',
-        '.svg': 'image/svg+xml',
-        '.ico': 'image/x-icon',
-    };
-    return types[ext] || 'application/octet-stream';
-}
-
-function getPlaceholderPage(): string {
-    return `<!DOCTYPE html>
-<html lang="en">
-<head>
-    <meta charset="UTF-8">
-    <meta name="viewport" content="width=device-width, initial-scale=1.0">
-    <title>ObjectQL Studio</title>
-    <style>
-        * { margin: 0; padding: 0; box-sizing: border-box; }
-        body {
-            font-family: -apple-system, BlinkMacSystemFont, 'Segoe UI', sans-serif;
-            background: linear-gradient(135deg, #667eea 0%, #764ba2 100%);
-            min-height: 100vh;
-            display: flex;
-            align-items: center;
-            justify-content: center;
-            color: white;
-        }
-        .container {
-            text-align: center;
-            max-width: 600px;
-            padding: 2rem;
-        }
-        h1 { font-size: 3rem; margin-bottom: 1rem; }
-        p { font-size: 1.25rem; opacity: 0.9; line-height: 1.6; }
-        .info {
-            background: rgba(255, 255, 255, 0.1);
-            padding: 1.5rem;
-            border-radius: 8px;
-            margin-top: 2rem;
-            backdrop-filter: blur(10px);
-        }
-        code {
-            background: rgba(0, 0, 0, 0.2);
-            padding: 0.25rem 0.5rem;
-            border-radius: 4px;
-            font-family: monospace;
-        }
-    </style>
-</head>
-<body>
-    <div class="container">
-        <h1>ObjectQL Studio</h1>
-        <p>Web-based admin studio for database management</p>
-        <div class="info">
-            <p style="margin-bottom: 1rem;">
-                The studio is available but needs to be built separately.
-            </p>
-            <p style="font-size: 1rem;">
-                To use the full studio UI, run:<br>
-                <code>cd packages/studio && pnpm run build</code>
-            </p>
-        </div>
-    </div>
-</body>
-</html>`;
-}
diff --git a/packages/tools/cli/package.json b/packages/tools/cli/package.json
index 5a2e67d7..9848b7ca 100644
--- a/packages/tools/cli/package.json
+++ b/packages/tools/cli/package.json
@@ -22,7 +22,6 @@
   "scripts": {
     "build": "tsc",
     "watch": "tsc -w",
-    "studio": "node dist/index.js studio",
     "test": "jest"
   },
   "dependencies": {
diff --git a/packages/tools/cli/src/commands/ai.ts b/packages/tools/cli/src/commands/ai.ts
index 71afb374..85f4d096 100644
--- a/packages/tools/cli/src/commands/ai.ts
+++ b/packages/tools/cli/src/commands/ai.ts
@@ -263,10 +263,11 @@ export async function aiValidate(options: ValidateOptions): Promise<void> {
     const patterns = [
         '**/*.object.yml',
         '**/*.validation.yml',
-        '**/*.form.yml',
-        '**/*.view.yml',
-        '**/*.page.yml',
         '**/*.action.yml',
+        '**/*.hook.yml',
+        '**/*.permission.yml',
+        '**/*.workflow.yml',
+        '**/*.data.yml',
     ];
 
     const files = await glob(patterns, {
diff --git a/packages/tools/cli/src/commands/new.ts b/packages/tools/cli/src/commands/new.ts
index 56822466..49b7ecac 100644
--- a/packages/tools/cli/src/commands/new.ts
+++ b/packages/tools/cli/src/commands/new.ts
@@ -11,16 +11,11 @@ interface NewOptions {
 
 const METADATA_TYPES = [
     'object',
-    'view',
-    'form',
-    'page',
     'action',
     'hook',
     'permission',
     'validation',
     'workflow',
-    'report',
-    'menu',
     'data'
 ];
 
@@ -35,35 +30,6 @@ const TEMPLATES: Record<string, any> = {
             }
         }
     },
-    view: {
-        label: '{{label}} View',
-        object: '{{objectName}}',
-        columns: [
-            { field: 'name', label: 'Name' }
-        ]
-    },
-    form: {
-        label: '{{label}} Form',
-        object: '{{objectName}}',
-        layout: {
-            sections: [
-                {
-                    label: 'Basic Information',
-                    fields: ['name']
-                }
-            ]
-        }
-    },
-    page: {
-        label: '{{label}} Page',
-        type: 'standard',
-        components: [
-            {
-                type: 'title',
-                text: '{{label}}'
-            }
-        ]
-    },
     action: {
         label: '{{label}} Action',
         object: '{{objectName}}',
@@ -118,24 +84,6 @@ const TEMPLATES: Record<string, any> = {
             }
         ]
     },
-    report: {
-        label: '{{label}} Report',
-        type: 'tabular',
-        object: '{{objectName}}',
-        columns: [
-            { field: 'name', label: 'Name' }
-        ]
-    },
-    menu: {
-        label: '{{label}} Menu',
-        items: [
-            {
-                label: 'Home',
-                page: 'home',
-                icon: 'home'
-            }
-        ]
-    },
     data: {
         label: '{{label}} Data',
         object: '{{objectName}}',
diff --git a/packages/tools/cli/src/commands/studio.ts b/packages/tools/cli/src/commands/studio.ts
deleted file mode 100644
index 71adae89..00000000
--- a/packages/tools/cli/src/commands/studio.ts
+++ /dev/null
@@ -1,354 +0,0 @@
-import { ObjectQL } from '@objectql/core';
-import { ObjectLoader, createDriverFromConnection } from '@objectql/platform-node';
-import { createNodeHandler, createStudioHandler, createMetadataHandler } from '@objectql/server';
-import { createServer } from 'http';
-import * as path from 'path';
-import * as fs from 'fs';
-import chalk from 'chalk';
-import { exec } from 'child_process';
-import { register } from 'ts-node';
-import glob from 'fast-glob';
-
-const SWAGGER_HTML = `
-<!DOCTYPE html>
-<html lang="en">
-<head>
-  <meta charset="utf-8" />
-  <meta name="viewport" content="width=device-width, initial-scale=1" />
-  <title>ObjectQL Swagger UI</title>
-  <link rel="stylesheet" href="https://unpkg.com/swagger-ui-dist@5.11.0/swagger-ui.css" />
-  <style>
-    body { margin: 0; padding: 0; }
-  </style>
-</head>
-<body>
-<div id="swagger-ui"></div>
-<script src="https://unpkg.com/swagger-ui-dist@5.11.0/swagger-ui-bundle.js" crossorigin></script>
-<script>
-  window.onload = () => {
-    window.ui = SwaggerUIBundle({
-      url: '/openapi.json',
-      dom_id: '#swagger-ui',
-    });
-  };
-</script>
-</body>
-</html>
-`;
-
-function openBrowser(url: string) {
-    const start = (process.platform == 'darwin' ? 'open' : process.platform == 'win32' ? 'start' : 'xdg-open');
-    exec(`${start} ${url}`);
-}
-
-export async function startStudio(options: { port: number; dir: string, open?: boolean }) {
-    const startPort = options.port || 5555;
-    const rootDir = path.resolve(process.cwd(), options.dir || '.');
-    
-    console.log(chalk.blue('Starting ObjectQL Studio...'));
-    console.log(chalk.gray(`Project Root: ${rootDir}`));
-
-    // Register ts-node
-    register({
-        transpileOnly: true,
-        compilerOptions: {
-            module: "commonjs"
-        }
-    });
-
-    let app: ObjectQL;
-    const configTs = path.join(rootDir, 'objectql.config.ts');
-    const configJs = path.join(rootDir, 'objectql.config.js');
-
-    if (fs.existsSync(configTs)) {
-        console.log(chalk.gray(`Loading config from ${configTs}`));
-        const mod = require(configTs);
-        app = mod.default || mod;
-    } else if (fs.existsSync(configJs)) {
-        console.log(chalk.gray(`Loading config from ${configJs}`));
-        const mod = require(configJs);
-        app = mod.default || mod;
-    } else {
-        console.error(chalk.red('\n❌ Error: Configuration file (objectql.config.ts) not found.'));
-        process.exit(1);
-    }
-
-    if (!app) {
-         console.error(chalk.red('\n❌ Error: No default export found in configuration file.'));
-         process.exit(1);
-    }
-
-    // Initialize App if it's a configuration object
-    if (typeof (app as any).init !== 'function') {
-        const config = app as any;
-        console.log(chalk.gray('Configuration object detected. Initializing ObjectQL instance...'));
-        
-        const datasources: any = {};
-        
-        if (config.datasource && config.datasource.default) {
-            const dbConfig = config.datasource.default;
-            if (dbConfig.type === 'sqlite') {
-                try {
-                    const { SqlDriver } = require('@objectql/driver-sql');
-                    datasources.default = new SqlDriver({
-                        client: 'sqlite3',
-                        connection: {
-                            filename: dbConfig.filename ? path.resolve(rootDir, dbConfig.filename) : ':memory:'
-                        },
-                        useNullAsDefault: true
-                    });
-                } catch (e) {
-                    console.warn(chalk.yellow('Failed to load @objectql/driver-sql. Ensure it is installed.'));
-                }
-            }
-        }
-
-        // Fallback to memory if no datasource
-        if (!datasources.default) {
-            console.warn(chalk.yellow('No valid datasource found. Using in-memory SQLite.'));
-            const { SqlDriver } = require('@objectql/driver-sql');
-            datasources.default = new SqlDriver({
-                client: 'sqlite3',
-                connection: { filename: ':memory:' },
-                useNullAsDefault: true
-            });
-        }
-
-        app = new ObjectQL({ datasources });
-        
-        // Load Schema
-        const loader = new ObjectLoader(app.metadata);
-
-        // Load Presets
-        if (Array.isArray(config.presets)) {
-            console.log(chalk.gray(`Loading ${config.presets.length} presets...`));
-            for (const preset of config.presets) {
-                try {
-                    loader.loadPackage(preset);
-                } catch (e: any) {
-                    console.warn(chalk.yellow(`Failed to load preset ${preset}:`), e.message);
-                }
-            }
-        }
-
-        // Load Schema from Directory
-        // In a monorepo root with presets, scanning everything is dangerous.
-        // We check if we are in a monorepo-like environment.
-        const isMonorepoRoot = fs.existsSync(path.join(rootDir, 'pnpm-workspace.yaml')) || fs.existsSync(path.join(rootDir, 'pnpm-lock.yaml'));
-        
-        // If we are in a likely monorepo root AND have presets, skip recursive scan
-        if (isMonorepoRoot && config.presets && config.presets.length > 0) {
-             console.log(chalk.yellow('Monorepo root detected with presets. Skipping recursive file scan of root directory to avoid conflicts.'));
-        } else {
-             loader.load(rootDir);
-        }
-    }
-
-    // 2. Load Schema & Init
-    try {
-        await app.init();
-    } catch (e: any) {
-        console.error(chalk.red('❌ Failed to initialize application:'), e.message);
-        process.exit(1);
-    }
-
-    // 3. Setup HTTP Server
-    const nodeHandler = createNodeHandler(app);
-    const studioHandler = createStudioHandler();
-    const metadataHandler = createMetadataHandler(app);
-
-    const server = createServer(async (req, res) => {
-        // CORS
-        res.setHeader('Access-Control-Allow-Origin', '*');
-        res.setHeader('Access-Control-Allow-Methods', 'GET, POST, OPTIONS');
-        res.setHeader('Access-Control-Allow-Headers', 'Content-Type');
-
-        if (req.method === 'OPTIONS') {
-            res.writeHead(200);
-            res.end();
-            return;
-        }
-
-        if (req.url === '/openapi.json') {
-            return nodeHandler(req, res);
-        }
-
-        if (req.url === '/swagger') {
-            res.writeHead(200, { 'Content-Type': 'text/html' });
-            res.end(SWAGGER_HTML);
-            return;
-        }
-
-        // Routing
-        if (req.url?.startsWith('/studio')) {
-            return studioHandler(req, res);
-        }
-
-        if (req.url?.startsWith('/api/schema/files')) {
-            // List all metadata files
-            try {
-                // Find all *.*.yml files relative to rootDir
-                // Note: User might have configured objectql with specific source paths. 
-                // We ignore common build folders to avoid duplicates/editing compiled files.
-                // We broadly match all objectql-like files: *.object.yml, *.view.yml, etc.
-                const files = await glob('**/*.{object,app,view,permission,report,validation,workflow,form,data,hook,action}.yml', { 
-                    cwd: rootDir, 
-                    ignore: ['node_modules/**', 'dist/**', 'build/**', 'out/**', '.git/**', '.next/**'] 
-                });
-                res.setHeader('Content-Type', 'application/json');
-                res.end(JSON.stringify({ files }));
-            } catch (e: any) {
-                res.statusCode = 500;
-                res.end(JSON.stringify({ error: e.message }));
-            }
-            return;
-        }
-
-        if (req.url?.startsWith('/api/schema/content')) {
-            const urlObj = new URL(req.url, `http://${req.headers.host}`);
-            const file = urlObj.searchParams.get('file');
-
-            if (!file) {
-                res.statusCode = 400;
-                res.end(JSON.stringify({ error: 'Missing file parameter' }));
-                return;
-            }
-
-            const filePath = path.join(rootDir, file);
-            // Security check
-            if (!filePath.startsWith(rootDir)) {
-                res.statusCode = 403;
-                res.end(JSON.stringify({ error: 'Access denied' }));
-                return;
-            }
-
-            if (req.method === 'GET') {
-                try {
-                    const content = fs.readFileSync(filePath, 'utf-8');
-                    res.setHeader('Content-Type', 'text/plain'); // Plain text (YAML)
-                    res.end(content);
-                } catch (e) {
-                    res.statusCode = 404;
-                    res.end(JSON.stringify({ error: 'File not found' }));
-                }
-                return;
-            }
-
-            if (req.method === 'POST') {
-                let body = '';
-                req.on('data', chunk => body += chunk);
-                req.on('end', () => {
-                   try {
-                       fs.writeFileSync(filePath, body, 'utf-8');
-                       res.statusCode = 200;
-                       res.end(JSON.stringify({ success: true }));
-                   } catch (e: any) {
-                       res.statusCode = 500;
-                       res.end(JSON.stringify({ error: e.message }));
-                   }
-                });
-                return;
-            }
-        }
-
-        if (req.url?.startsWith('/api/schema/find')) {
-            const urlObj = new URL(req.url, `http://${req.headers.host}`);
-            const objectName = urlObj.searchParams.get('object');
-            
-            if (!objectName) {
-                res.statusCode = 400;
-                res.end(JSON.stringify({ error: 'Missing object parameter' }));
-                return;
-            }
-
-            try {
-                // Find all object.yml files
-                const files = await glob('**/*.object.yml', { 
-                    cwd: rootDir, 
-                    ignore: ['node_modules/**', 'dist/**', 'build/**', 'out/**', '.git/**', '.next/**'] 
-                });
-                let foundFile = null;
-
-                // Naive parsing to find the object definition
-                // We don't use the FULL parser, just checks if "name: objectName" is present
-                for (const file of files) {
-                    const content = fs.readFileSync(path.join(rootDir, file), 'utf-8');
-                    // Simple check: name: <objectName> or name: "<objectName>"
-                    // This creates a regex that looks for `name:` followed by the objectName
-                    // Handles spaces, quotes
-                    const regex = new RegExp(`^\\s*name:\\s*["']?${objectName}["']?\\s*$`, 'm');
-                    if (regex.test(content)) {
-                        foundFile = file;
-                        break;
-                    }
-                }
-
-                if (foundFile) {
-                    res.setHeader('Content-Type', 'application/json');
-                    res.end(JSON.stringify({ file: foundFile }));
-                } else {
-                    res.statusCode = 404;
-                    res.end(JSON.stringify({ error: 'Object definition file not found' }));
-                }
-            } catch (e: any) {
-                res.statusCode = 500;
-                res.end(JSON.stringify({ error: e.message }));
-            }
-            return;
-        }
-
-        if (req.url?.startsWith('/api/metadata')) {
-            return metadataHandler(req, res);
-        }
-        
-        if (req.url?.startsWith('/api')) {
-            // Strip /api prefix if needed by the handler, 
-            // but ObjectQL node handler usually expects full path or depends on internal routing.
-            // Actually createNodeHandler handles /objectql/v1/ etc? 
-            // Let's assume standard behavior: pass to handler
-            return nodeHandler(req, res);
-        }
-
-        // Redirect root to studio
-        if (req.url === '/') {
-            res.writeHead(302, { 'Location': '/studio' });
-            res.end();
-            return;
-        }
-
-        res.statusCode = 404;
-        res.end('Not Found');
-    });
-
-    const tryListen = (port: number) => {
-        server.removeAllListeners('error');
-        server.removeAllListeners('listening'); // Prevent stacking callbacks
-
-        server.on('error', (e: any) => {
-            if (e.code === 'EADDRINUSE') {
-                if (port - startPort < 10) {
-                    console.log(chalk.yellow(`Port ${port} is in use, trying ${port + 1}...`));
-                    server.close();
-                    tryListen(port + 1);
-                } else {
-                    console.error(chalk.red(`❌ Unable to find a free port.`));
-                    process.exit(1);
-                }
-            } else {
-                console.error(chalk.red('❌ Server error:'), e);
-            }
-        });
-
-        server.listen(port, () => {
-            const url = `http://localhost:${port}/studio`;
-            console.log(chalk.green(`\n🚀 Studio running at: ${chalk.bold(url)}`));
-            console.log(chalk.gray(`   API endpoint: http://localhost:${port}/api`));
-            
-            if (options.open) {
-                openBrowser(url);
-            }
-        });
-    };
-
-    tryListen(startPort);
-}
diff --git a/packages/tools/cli/src/index.ts b/packages/tools/cli/src/index.ts
index 6601a001..10a9d43a 100644
--- a/packages/tools/cli/src/index.ts
+++ b/packages/tools/cli/src/index.ts
@@ -8,7 +8,6 @@ import { build } from './commands/build';
 import { test } from './commands/test';
 import { lint } from './commands/lint';
 import { format } from './commands/format';
-import { startStudio } from './commands/studio';
 import { initProject } from './commands/init';
 import { newMetadata } from './commands/new';
 import { i18nExtract, i18nInit, i18nValidate } from './commands/i18n';
@@ -291,22 +290,6 @@ program
         await serve({ port: parseInt(options.port), dir: options.dir });
     });
 
-// Studio command
-program
-    .command('studio')
-    .alias('ui')
-    .description('Start the ObjectQL Studio')
-    .option('-p, --port <number>', 'Port to listen on', '5555')
-    .option('-d, --dir <path>', 'Directory containing schema', '.')
-    .option('--no-open', 'Do not open browser automatically')
-    .action(async (options) => {
-        await startStudio({ 
-            port: parseInt(options.port), 
-            dir: options.dir,
-            open: options.open
-        });
-    });
-
 // AI command - Interactive by default, with specific subcommands for other modes
 const aiCmd = program
     .command('ai')
diff --git a/packages/tools/studio/CHANGELOG.md b/packages/tools/studio/CHANGELOG.md
deleted file mode 100644
index ca1becd6..00000000
--- a/packages/tools/studio/CHANGELOG.md
+++ /dev/null
@@ -1,89 +0,0 @@
-# @objectql/studio
-
-## 1.8.3
-
-### Patch Changes
-
-- Release patch version 1.8.3
-
-  Small version update with latest improvements and bug fixes.
-
-## 1.8.2
-
-### Patch Changes
-
-- Patch release v1.8.2 - Small version update with latest improvements
-
-## 1.8.1
-
-### Patch Changes
-
-- Patch release with documentation updates and bug fixes
-
-## 1.8.0
-
-### Minor Changes
-
-- Release minor version 1.8.0
-
-## 1.7.3
-
-### Patch Changes
-
-- Release patch version 1.7.3 with latest improvements and bug fixes
-
-## 1.7.2
-
-### Patch Changes
-
-- Release patch version 1.7.2
-
-## 1.7.1
-
-### Patch Changes
-
-- Release small version update with latest improvements
-
-## 1.7.0
-
-### Minor Changes
-
-- Release version 1.7.0 with improvements and bug fixes:
-  - Updated default port for ObjectQL Studio to 5555
-  - Improved port listening logic in Studio
-  - Enhanced stability and performance
-
-## 1.6.1
-
-## 1.6.0
-
-### Minor Changes
-
-- Minor version release - 1.6.0
-
-## 1.5.0
-
-### Minor Changes
-
-- Minor version release - 1.5.0
-
-## 1.4.0
-
-### Minor Changes
-
-- Release version 1.4.0 with new features and enhancements:
-  - Added complete REST API implementation with CRUD operations
-  - Enhanced error handling with standardized error codes and HTTP status mapping
-  - Added AI context support for tracking intent and use cases
-  - Enhanced metadata API with detailed field information and action listing
-  - Improved JSON-RPC API with better error categorization
-  - Added hooks and actions validation and implementation
-  - Updated documentation and examples
-
-## 1.3.1
-
-## 0.2.0
-
-### Minor Changes
-
-- 7df2977: 拆分 objectos
diff --git a/packages/tools/studio/README.md b/packages/tools/studio/README.md
deleted file mode 100644
index ed5e0114..00000000
--- a/packages/tools/studio/README.md
+++ /dev/null
@@ -1,47 +0,0 @@
-# @objectql/studio
-
-Web-based admin studio for ObjectQL database management.
-
-## Features
-
-- **Object Browser**: View all registered objects/tables in your database
-- **Data Grid**: Browse and search records with pagination
-- **CRUD Operations**: Create, read, update, and delete records
-- **Schema Inspector**: View object definitions and field metadata
-- **Modern UI**: Clean, responsive design with intuitive navigation
-
-## Usage
-
-The console is typically served alongside your ObjectQL server:
-
-```typescript
-import express from 'express';
-import { ObjectQL } from '@objectql/core';
-import { createNodeHandler, createStudioHandler } from '@objectql/server';
-
-const app = new ObjectQL({ /* ... */ });
-const server = express();
-
-// ... setup objectql ...
-
-// Serve the Studio
-server.get('/studio*', createStudioHandler());
-```
-
-// API endpoints
-server.all('/api/objectql', createNodeHandler(app));
-
-// Serve console UI
-server.use('/console', serveConsole());
-
-server.listen(3004);
-```
-
-Then visit `http://localhost:3004/console` in your browser.
-
-## Development
-
-```bash
-pnpm install
-pnpm run dev
-```
diff --git a/packages/tools/studio/index.html b/packages/tools/studio/index.html
deleted file mode 100644
index 77e4e9c3..00000000
--- a/packages/tools/studio/index.html
+++ /dev/null
@@ -1,12 +0,0 @@
-<!DOCTYPE html>
-<html lang="en">
-  <head>
-    <meta charset="UTF-8" />
-    <meta name="viewport" content="width=device-width, initial-scale=1.0" />
-    <title>ObjectQL Console</title>
-  </head>
-  <body>
-    <div id="root"></div>
-    <script type="module" src="/src/main.tsx"></script>
-  </body>
-</html>
diff --git a/packages/tools/studio/package.json b/packages/tools/studio/package.json
deleted file mode 100644
index 2ddc8cad..00000000
--- a/packages/tools/studio/package.json
+++ /dev/null
@@ -1,47 +0,0 @@
-{
-  "name": "@objectql/studio",
-  "version": "1.8.3",
-  "description": "Web-based admin studio for ObjectQL - Visual database management, schema editor, and data browser",
-  "keywords": [
-    "objectql",
-    "studio",
-    "admin",
-    "gui",
-    "database",
-    "management",
-    "react",
-    "vite",
-    "ag-grid",
-    "visual-editor"
-  ],
-  "license": "MIT",
-  "type": "module",
-  "scripts": {
-    "dev": "vite",
-    "build": "tsc && vite build",
-    "preview": "vite preview"
-  },
-  "dependencies": {
-    "ag-grid-community": "^31.0.0",
-    "ag-grid-react": "^31.0.0",
-    "class-variance-authority": "^0.7.0",
-    "clsx": "^2.1.0",
-    "lucide-react": "^0.300.0",
-    "react": "^18.2.0",
-    "react-dom": "^18.2.0",
-    "react-router-dom": "^6.20.0",
-    "tailwind-merge": "^2.2.0",
-    "tailwindcss-animate": "^1.0.7"
-  },
-  "devDependencies": {
-    "@types/node": "^20.10.0",
-    "@types/react": "^18.2.43",
-    "@types/react-dom": "^18.2.17",
-    "@vitejs/plugin-react": "^4.2.1",
-    "autoprefixer": "^10.4.16",
-    "postcss": "^8.4.32",
-    "tailwindcss": "^3.4.0",
-    "typescript": "^5.3.0",
-    "vite": "^5.0.8"
-  }
-}
diff --git a/packages/tools/studio/postcss.config.cjs b/packages/tools/studio/postcss.config.cjs
deleted file mode 100644
index 96bb01e7..00000000
--- a/packages/tools/studio/postcss.config.cjs
+++ /dev/null
@@ -1,6 +0,0 @@
-module.exports = {
-  plugins: {
-    tailwindcss: {},
-    autoprefixer: {},
-  },
-}
\ No newline at end of file
diff --git a/packages/tools/studio/src/App.css b/packages/tools/studio/src/App.css
deleted file mode 100644
index c07731f5..00000000
--- a/packages/tools/studio/src/App.css
+++ /dev/null
@@ -1,308 +0,0 @@
-.app {
-  display: flex;
-  flex-direction: column;
-  min-height: 100vh;
-}
-
-.container {
-  max-width: 1200px;
-  margin: 0 auto;
-  padding: 0 20px;
-  width: 100%;
-}
-
-/* Header */
-.app-header {
-  background: linear-gradient(135deg, #667eea 0%, #764ba2 100%);
-  color: white;
-  padding: 1rem 0;
-  box-shadow: 0 2px 10px rgba(0, 0, 0, 0.1);
-}
-
-.app-header .container {
-  display: flex;
-  justify-content: space-between;
-  align-items: center;
-}
-
-.logo {
-  font-size: 1.5rem;
-  font-weight: 700;
-  letter-spacing: -0.5px;
-}
-
-.logo a {
-  color: white;
-  text-decoration: none;
-  transition: opacity 0.2s;
-}
-
-.logo a:hover {
-  opacity: 0.9;
-}
-
-.nav {
-  display: flex;
-  gap: 1.5rem;
-}
-
-.nav-link {
-  color: white;
-  text-decoration: none;
-  padding: 0.5rem 1rem;
-  border-radius: 6px;
-  transition: background 0.2s;
-  font-weight: 500;
-}
-
-.nav-link:hover {
-  background: rgba(255, 255, 255, 0.15);
-}
-
-/* Main */
-.app-main {
-  flex: 1;
-  padding: 2rem 0;
-}
-
-/* Footer */
-.app-footer {
-  background: #2d3748;
-  color: #a0aec0;
-  padding: 1.5rem 0;
-  text-align: center;
-  font-size: 0.875rem;
-}
-
-/* Card Component */
-.card {
-  background: white;
-  border-radius: 8px;
-  padding: 1.5rem;
-  box-shadow: 0 1px 3px rgba(0, 0, 0, 0.1);
-  margin-bottom: 1.5rem;
-}
-
-.card-title {
-  font-size: 1.25rem;
-  font-weight: 600;
-  margin-bottom: 1rem;
-  color: #2d3748;
-}
-
-/* Button */
-.btn {
-  padding: 0.5rem 1rem;
-  border: none;
-  border-radius: 6px;
-  font-weight: 500;
-  cursor: pointer;
-  transition: all 0.2s;
-  text-decoration: none;
-  display: inline-block;
-  font-size: 0.875rem;
-}
-
-.btn-primary {
-  background: #667eea;
-  color: white;
-}
-
-.btn-primary:hover {
-  background: #5568d3;
-  transform: translateY(-1px);
-  box-shadow: 0 4px 6px rgba(102, 126, 234, 0.3);
-}
-
-.btn-secondary {
-  background: #e2e8f0;
-  color: #2d3748;
-}
-
-.btn-secondary:hover {
-  background: #cbd5e0;
-}
-
-.btn-danger {
-  background: #f56565;
-  color: white;
-}
-
-.btn-danger:hover {
-  background: #e53e3e;
-}
-
-.btn-sm {
-  padding: 0.375rem 0.75rem;
-  font-size: 0.8125rem;
-}
-
-/* Table */
-.table-container {
-  overflow-x: auto;
-  margin-top: 1rem;
-}
-
-.table {
-  width: 100%;
-  border-collapse: collapse;
-  background: white;
-}
-
-.table th,
-.table td {
-  padding: 0.75rem 1rem;
-  text-align: left;
-  border-bottom: 1px solid #e2e8f0;
-}
-
-.table th {
-  background: #f7fafc;
-  font-weight: 600;
-  color: #2d3748;
-  font-size: 0.875rem;
-  text-transform: uppercase;
-  letter-spacing: 0.5px;
-}
-
-.table tr:hover {
-  background: #f7fafc;
-}
-
-.table td {
-  color: #4a5568;
-}
-
-/* Form */
-.form-group {
-  margin-bottom: 1rem;
-}
-
-.form-label {
-  display: block;
-  margin-bottom: 0.5rem;
-  font-weight: 500;
-  color: #2d3748;
-  font-size: 0.875rem;
-}
-
-.form-input,
-.form-textarea,
-.form-select {
-  width: 100%;
-  padding: 0.5rem 0.75rem;
-  border: 1px solid #e2e8f0;
-  border-radius: 6px;
-  font-size: 0.875rem;
-  transition: border-color 0.2s;
-}
-
-.form-input:focus,
-.form-textarea:focus,
-.form-select:focus {
-  outline: none;
-  border-color: #667eea;
-  box-shadow: 0 0 0 3px rgba(102, 126, 234, 0.1);
-}
-
-.form-textarea {
-  min-height: 100px;
-  resize: vertical;
-}
-
-/* Grid */
-.grid {
-  display: grid;
-  gap: 1rem;
-}
-
-.grid-2 {
-  grid-template-columns: repeat(auto-fit, minmax(250px, 1fr));
-}
-
-/* Alert */
-.alert {
-  padding: 1rem;
-  border-radius: 6px;
-  margin-bottom: 1rem;
-}
-
-.alert-info {
-  background: #e6f7ff;
-  color: #0050b3;
-  border-left: 4px solid #1890ff;
-}
-
-.alert-error {
-  background: #fff1f0;
-  color: #cf1322;
-  border-left: 4px solid #f5222d;
-}
-
-.alert-success {
-  background: #f6ffed;
-  color: #389e0d;
-  border-left: 4px solid #52c41a;
-}
-
-/* Loading */
-.loading {
-  text-align: center;
-  padding: 3rem;
-  color: #a0aec0;
-}
-
-.spinner {
-  display: inline-block;
-  width: 40px;
-  height: 40px;
-  border: 4px solid #e2e8f0;
-  border-top-color: #667eea;
-  border-radius: 50%;
-  animation: spin 1s linear infinite;
-}
-
-@keyframes spin {
-  to { transform: rotate(360deg); }
-}
-
-/* Breadcrumb */
-.breadcrumb {
-  display: flex;
-  gap: 0.5rem;
-  margin-bottom: 1.5rem;
-  font-size: 0.875rem;
-  color: #718096;
-}
-
-.breadcrumb a {
-  color: #667eea;
-  text-decoration: none;
-}
-
-.breadcrumb a:hover {
-  text-decoration: underline;
-}
-
-.breadcrumb-separator {
-  color: #cbd5e0;
-}
-
-/* Badge */
-.badge {
-  display: inline-block;
-  padding: 0.25rem 0.5rem;
-  border-radius: 4px;
-  font-size: 0.75rem;
-  font-weight: 500;
-}
-
-.badge-primary {
-  background: #667eea;
-  color: white;
-}
-
-.badge-secondary {
-  background: #e2e8f0;
-  color: #2d3748;
-}
diff --git a/packages/tools/studio/src/App.tsx b/packages/tools/studio/src/App.tsx
deleted file mode 100644
index c6682ed9..00000000
--- a/packages/tools/studio/src/App.tsx
+++ /dev/null
@@ -1,36 +0,0 @@
-import { BrowserRouter, Routes, Route, useParams } from 'react-router-dom';
-import { Sidebar } from '@/components/Sidebar';
-import { Dashboard } from '@/pages/Dashboard';
-import { ObjectView } from '@/pages/ObjectView';
-import { SchemaEditor } from '@/pages/SchemaEditor';
-import { MetadataBrowser } from '@/pages/MetadataBrowser';
-import './index.css';
-
-// Wrapper to extract params
-function ObjectViewWrapper() {
-  const { name } = useParams();
-  if (!name) return null;
-  return <ObjectView objectName={name} />;
-}
-
-function App() {
-  return (
-    <BrowserRouter basename="/studio">
-      <div className="flex h-screen bg-background text-foreground overflow-hidden font-sans antialiased">
-        <Sidebar />
-        <main className="flex-1 overflow-auto bg-muted/20">
-          <Routes>
-            <Route path="/" element={<Dashboard />} />
-            <Route path="/schema" element={<SchemaEditor />} />
-            <Route path="/metadata" element={<MetadataBrowser />} />
-            <Route path="/metadata/:type" element={<MetadataBrowser />} />
-            <Route path="/object/:name" element={<ObjectViewWrapper />} />
-          </Routes>
-        </main>
-      </div>
-    </BrowserRouter>
-  );
-}
-
-export default App;
-
diff --git a/packages/tools/studio/src/components/DataGrid.tsx b/packages/tools/studio/src/components/DataGrid.tsx
deleted file mode 100644
index 4f98a37a..00000000
--- a/packages/tools/studio/src/components/DataGrid.tsx
+++ /dev/null
@@ -1,227 +0,0 @@
-import { useState, useEffect } from 'react';
-import { useParams, Link, useNavigate } from 'react-router-dom';
-
-interface Record {
-  _id?: string;
-  id?: string;
-  [key: string]: any;
-}
-
-function DataGrid() {
-  const { objectName } = useParams<{ objectName: string }>();
-  const navigate = useNavigate();
-  const [records, setRecords] = useState<Record[]>([]);
-  const [fields, setFields] = useState<string[]>([]);
-  const [loading, setLoading] = useState(true);
-  const [error, setError] = useState<string | null>(null);
-  const [showCreateForm, setShowCreateForm] = useState(false);
-
-  useEffect(() => {
-    fetchRecords();
-    fetchObjectMetadata();
-  }, [objectName]);
-
-  const fetchObjectMetadata = async () => {
-    try {
-      const response = await fetch(`/api/metadata/object/${objectName}`);
-      if (response.ok) {
-        const data = await response.json();
-        if (data.fields) {
-          const fieldsArray = Array.isArray(data.fields) ? data.fields : Object.values(data.fields);
-          setFields(fieldsArray.map((f: any) => f.name || f));
-        }
-      }
-    } catch (e) {
-      console.error('Failed to fetch metadata:', e);
-    }
-  };
-
-  const fetchRecords = async () => {
-    try {
-      setLoading(true);
-      const response = await fetch('/api/objectql', {
-        method: 'POST',
-        headers: { 'Content-Type': 'application/json' },
-        body: JSON.stringify({
-          op: 'find',
-          object: objectName,
-          args: { limit: 100 }
-        })
-      });
-
-      if (!response.ok) {
-        throw new Error(`HTTP error! status: ${response.status}`);
-      }
-
-      const result = await response.json();
-      const data = result.items || result.data || [];
-      setRecords(data);
-
-      // Auto-detect fields if not already set
-      if (data.length > 0 && fields.length === 0) {
-        const sampleRecord = data[0];
-        const detectedFields = Object.keys(sampleRecord).filter(
-          k => !k.startsWith('_') || k === '_id'
-        );
-        setFields(detectedFields);
-      }
-    } catch (e: any) {
-      console.error('Failed to fetch records:', e);
-      setError(e.message);
-    } finally {
-      setLoading(false);
-    }
-  };
-
-  const handleCreate = async (formData: Record) => {
-    try {
-      const response = await fetch('/api/objectql', {
-        method: 'POST',
-        headers: { 'Content-Type': 'application/json' },
-        body: JSON.stringify({
-          op: 'create',
-          object: objectName,
-          args: { data: formData }
-        })
-      });
-
-      if (!response.ok) {
-        throw new Error('Failed to create record');
-      }
-
-      setShowCreateForm(false);
-      fetchRecords();
-    } catch (e: any) {
-      alert(`Error: ${e.message}`);
-    }
-  };
-
-  const formatValue = (value: any): string => {
-    if (value === null || value === undefined) return '-';
-    if (typeof value === 'object') return JSON.stringify(value);
-    if (typeof value === 'boolean') return value ? 'Yes' : 'No';
-    return String(value);
-  };
-
-  const getRecordId = (record: Record): string => {
-    return record._id || record.id || '';
-  };
-
-  if (loading) {
-    return (
-      <div className="loading">
-        <div className="spinner"></div>
-        <p>Loading records...</p>
-      </div>
-    );
-  }
-
-  return (
-    <div>
-      <div className="breadcrumb">
-        <Link to="/">Objects</Link>
-        <span className="breadcrumb-separator">/</span>
-        <span>{objectName}</span>
-      </div>
-
-      <div className="card">
-        <div style={{ display: 'flex', justifyContent: 'space-between', alignItems: 'center', marginBottom: '1rem' }}>
-          <h2 className="card-title" style={{ marginBottom: 0 }}>{objectName}</h2>
-          <button className="btn btn-primary" onClick={() => setShowCreateForm(!showCreateForm)}>
-            {showCreateForm ? 'Cancel' : 'New Record'}
-          </button>
-        </div>
-
-        {error && (
-          <div className="alert alert-error">
-            <strong>Error:</strong> {error}
-          </div>
-        )}
-
-        {showCreateForm && (
-          <CreateRecordForm
-            fields={fields}
-            onSubmit={handleCreate}
-            onCancel={() => setShowCreateForm(false)}
-          />
-        )}
-
-        {records.length === 0 ? (
-          <div className="alert alert-info">
-            No records found. Click "New Record" to create one.
-          </div>
-        ) : (
-          <div className="table-container">
-            <table className="table">
-              <thead>
-                <tr>
-                  {fields.map((field) => (
-                    <th key={field}>{field}</th>
-                  ))}
-                  <th>Actions</th>
-                </tr>
-              </thead>
-              <tbody>
-                {records.map((record, idx) => (
-                  <tr key={getRecordId(record) || idx}>
-                    {fields.map((field) => (
-                      <td key={field}>{formatValue(record[field])}</td>
-                    ))}
-                    <td>
-                      <button
-                        className="btn btn-sm btn-secondary"
-                        onClick={() => navigate(`/object/${objectName}/${getRecordId(record)}`)}
-                      >
-                        View
-                      </button>
-                    </td>
-                  </tr>
-                ))}
-              </tbody>
-            </table>
-          </div>
-        )}
-
-        <div style={{ marginTop: '1rem', color: '#718096', fontSize: '0.875rem' }}>
-          Showing {records.length} record{records.length !== 1 ? 's' : ''}
-        </div>
-      </div>
-    </div>
-  );
-}
-
-function CreateRecordForm({ fields, onSubmit, onCancel }: {
-  fields: string[];
-  onSubmit: (data: Record) => void;
-  onCancel: () => void;
-}) {
-  const [formData, setFormData] = useState<Record>({});
-
-  const handleSubmit = (e: React.FormEvent) => {
-    e.preventDefault();
-    onSubmit(formData);
-  };
-
-  return (
-    <form onSubmit={handleSubmit} className="card" style={{ background: '#f7fafc', marginBottom: '1rem' }}>
-      <h3 style={{ marginBottom: '1rem', fontSize: '1rem', fontWeight: '600' }}>Create New Record</h3>
-      {fields.filter(f => f !== '_id' && f !== 'id').map((field) => (
-        <div key={field} className="form-group">
-          <label className="form-label">{field}</label>
-          <input
-            type="text"
-            className="form-input"
-            value={formData[field] || ''}
-            onChange={(e) => setFormData({ ...formData, [field]: e.target.value })}
-          />
-        </div>
-      ))}
-      <div style={{ display: 'flex', gap: '0.5rem', marginTop: '1rem' }}>
-        <button type="submit" className="btn btn-primary">Create</button>
-        <button type="button" className="btn btn-secondary" onClick={onCancel}>Cancel</button>
-      </div>
-    </form>
-  );
-}
-
-export default DataGrid;
diff --git a/packages/tools/studio/src/components/FileEditor.tsx b/packages/tools/studio/src/components/FileEditor.tsx
deleted file mode 100644
index d82d1d0f..00000000
--- a/packages/tools/studio/src/components/FileEditor.tsx
+++ /dev/null
@@ -1,95 +0,0 @@
-import { useState, useEffect } from 'react';
-import { Button } from '@/components/ui/button';
-import { Card, CardContent, CardHeader, CardTitle } from '@/components/ui/card';
-import { Save } from 'lucide-react';
-
-interface FileEditorProps {
-    filePath: string;
-    className?: string;
-    onSaveSuccess?: () => void;
-}
-
-export function FileEditor({ filePath, className, onSaveSuccess }: FileEditorProps) {
-    const [content, setContent] = useState('');
-    const [loading, setLoading] = useState(false);
-    const [saving, setSaving] = useState(false);
-    const [error, setError] = useState<string | null>(null);
-    const [status, setStatus] = useState<string | null>(null);
-
-    useEffect(() => {
-        if (filePath) {
-            loadFile(filePath);
-        }
-    }, [filePath]);
-
-    const loadFile = async (file: string) => {
-        setLoading(true);
-        setError(null);
-        try {
-            const res = await fetch(`/api/schema/content?file=${encodeURIComponent(file)}`);
-            if (!res.ok) throw new Error('Failed to load file');
-            const text = await res.text();
-            setContent(text);
-        } catch (e) {
-            console.error(e);
-            setError('Failed to read file content');
-        } finally {
-            setLoading(false);
-        }
-    };
-
-    const saveFile = async () => {
-        if (!filePath) return;
-        setSaving(true);
-        setStatus(null);
-        try {
-            const res = await fetch(`/api/schema/content?file=${encodeURIComponent(filePath)}`, {
-                method: 'POST',
-                body: content
-            });
-            if (!res.ok) throw new Error('Failed to save');
-            setStatus('File saved successfully!');
-            setTimeout(() => setStatus(null), 3000);
-            if (onSaveSuccess) onSaveSuccess();
-        } catch (e) {
-            setError('Failed to save file');
-        } finally {
-            setSaving(false);
-        }
-    };
-
-    return (
-        <Card className={`flex flex-col h-full ${className}`}>
-            <CardHeader className="py-2 px-4 flex flex-row items-center justify-between border-b space-y-0 min-h-[50px]">
-                <CardTitle className="text-sm font-mono text-muted-foreground flex items-center">
-                    {filePath}
-                </CardTitle>
-                <div className="flex items-center gap-2">
-                    {status && <span className="text-xs text-green-600 font-medium animate-fade-in">{status}</span>}
-                    {error && <span className="text-xs text-red-600 font-medium">{error}</span>}
-                    <Button size="sm" onClick={saveFile} disabled={saving || loading}>
-                        {saving ? 'Saving...' : (
-                            <>
-                                <Save className="mr-2 h-3 w-3" /> Save
-                            </>
-                        )}
-                    </Button>
-                </div>
-            </CardHeader>
-            <CardContent className="flex-1 p-0 relative min-h-[400px]">
-                {loading && (
-                    <div className="absolute inset-0 flex items-center justify-center bg-background/50 z-10 transition-all backdrop-blur-sm">
-                        <div className="animate-spin rounded-full h-8 w-8 border-b-2 border-primary"></div>
-                    </div>
-                )}
-                <textarea
-                    className="w-full h-full p-4 font-mono text-sm resize-none focus:outline-none bg-muted/10 leading-normal"
-                    value={content}
-                    onChange={(e) => setContent(e.target.value)}
-                    spellCheck={false}
-                    disabled={loading}
-                />
-            </CardContent>
-        </Card>
-    );
-}
diff --git a/packages/tools/studio/src/components/ObjectList.tsx b/packages/tools/studio/src/components/ObjectList.tsx
deleted file mode 100644
index 5f56ed71..00000000
--- a/packages/tools/studio/src/components/ObjectList.tsx
+++ /dev/null
@@ -1,137 +0,0 @@
-import { useState, useEffect } from 'react';
-import { Link } from 'react-router-dom';
-
-interface ObjectInfo {
-  name: string;
-  label?: string;
-  icon?: string;
-  recordCount?: number;
-}
-
-function ObjectList() {
-  const [objects, setObjects] = useState<ObjectInfo[]>([]);
-  const [loading, setLoading] = useState(true);
-  const [error, setError] = useState<string | null>(null);
-
-  useEffect(() => {
-    fetchObjects();
-  }, []);
-
-  const fetchObjects = async () => {
-    try {
-      setLoading(true);
-      const response = await fetch('/api/metadata/object');
-      if (!response.ok) {
-        throw new Error(`HTTP error! status: ${response.status}`);
-      }
-      const data = await response.json();
-      setObjects(data.items || []);
-    } catch (e: any) {
-      console.error('Failed to fetch objects:', e);
-      setError(e.message);
-    } finally {
-      setLoading(false);
-    }
-  };
-
-  if (loading) {
-    return (
-      <div className="loading">
-        <div className="spinner"></div>
-        <p>Loading objects...</p>
-      </div>
-    );
-  }
-
-  if (error) {
-    return (
-      <div className="alert alert-error">
-        <strong>Error:</strong> {error}
-      </div>
-    );
-  }
-
-  if (objects.length === 0) {
-    return (
-      <div className="card">
-        <h2 className="card-title">No Objects Found</h2>
-        <p>No objects are registered in the ObjectQL instance.</p>
-        <p className="alert alert-info" style={{ marginTop: '1rem' }}>
-          Make sure your ObjectQL server has loaded object definitions.
-        </p>
-      </div>
-    );
-  }
-
-  return (
-    <div>
-      <div className="card">
-        <h2 className="card-title">Database Objects</h2>
-        <p style={{ color: '#718096', marginBottom: '1.5rem' }}>
-          Browse and manage data across all registered objects
-        </p>
-
-        <div className="grid grid-2">
-          {objects.map((obj) => (
-            <Link
-              key={obj.name}
-              to={`/object/${obj.name}`}
-              style={{ textDecoration: 'none', color: 'inherit' }}
-            >
-              <div
-                className="card"
-                style={{
-                  cursor: 'pointer',
-                  transition: 'all 0.2s',
-                  border: '1px solid #e2e8f0',
-                }}
-                onMouseOver={(e) => {
-                  e.currentTarget.style.borderColor = '#667eea';
-                  e.currentTarget.style.transform = 'translateY(-2px)';
-                  e.currentTarget.style.boxShadow = '0 4px 6px rgba(0, 0, 0, 0.1)';
-                }}
-                onMouseOut={(e) => {
-                  e.currentTarget.style.borderColor = '#e2e8f0';
-                  e.currentTarget.style.transform = 'translateY(0)';
-                  e.currentTarget.style.boxShadow = '0 1px 3px rgba(0, 0, 0, 0.1)';
-                }}
-              >
-                <div style={{ display: 'flex', alignItems: 'center', gap: '1rem' }}>
-                  <div
-                    style={{
-                      width: '48px',
-                      height: '48px',
-                      borderRadius: '8px',
-                      background: 'linear-gradient(135deg, #667eea 0%, #764ba2 100%)',
-                      display: 'flex',
-                      alignItems: 'center',
-                      justifyContent: 'center',
-                      color: 'white',
-                      fontSize: '1.5rem',
-                      fontWeight: 'bold',
-                    }}
-                  >
-                    {obj.icon || obj.name.charAt(0).toUpperCase()}
-                  </div>
-                  <div style={{ flex: 1 }}>
-                    <h3 style={{ fontSize: '1.125rem', fontWeight: '600', marginBottom: '0.25rem' }}>
-                      {obj.label || obj.name}
-                    </h3>
-                    <p style={{ fontSize: '0.875rem', color: '#718096' }}>
-                      {obj.name}
-                      {typeof obj.recordCount === 'number' && (
-                        <span> • {obj.recordCount} records</span>
-                      )}
-                    </p>
-                  </div>
-                </div>
-              </div>
-            </Link>
-          ))}
-        </div>
-      </div>
-    </div>
-  );
-}
-
-export default ObjectList;
diff --git a/packages/tools/studio/src/components/RecordDetail.tsx b/packages/tools/studio/src/components/RecordDetail.tsx
deleted file mode 100644
index 29126304..00000000
--- a/packages/tools/studio/src/components/RecordDetail.tsx
+++ /dev/null
@@ -1,229 +0,0 @@
-import { useState, useEffect } from 'react';
-import { useParams, Link, useNavigate } from 'react-router-dom';
-
-interface Record {
-  _id?: string;
-  id?: string;
-  [key: string]: any;
-}
-
-function RecordDetail() {
-  const { objectName, recordId } = useParams<{ objectName: string; recordId: string }>();
-  const navigate = useNavigate();
-  const [record, setRecord] = useState<Record | null>(null);
-  const [loading, setLoading] = useState(true);
-  const [error, setError] = useState<string | null>(null);
-  const [editing, setEditing] = useState(false);
-  const [formData, setFormData] = useState<Record>({});
-
-  useEffect(() => {
-    fetchRecord();
-  }, [objectName, recordId]);
-
-  const fetchRecord = async () => {
-    try {
-      setLoading(true);
-      const response = await fetch('/api/objectql', {
-        method: 'POST',
-        headers: { 'Content-Type': 'application/json' },
-        body: JSON.stringify({
-          op: 'findOne',
-          object: objectName,
-          args: {
-            filters: [['_id', '=', recordId]].concat(
-              recordId ? [['id', '=', recordId]] : []
-            )
-          }
-        })
-      });
-
-      if (!response.ok) {
-        throw new Error(`HTTP error! status: ${response.status}`);
-      }
-
-      const result = await response.json();
-      // For findOne, the result is the record itself (no data wrapper)
-      const recordData = result.data || result;
-      setRecord(recordData);
-      setFormData(recordData || {});
-    } catch (e: any) {
-      console.error('Failed to fetch record:', e);
-      setError(e.message);
-    } finally {
-      setLoading(false);
-    }
-  };
-
-  const handleUpdate = async () => {
-    try {
-      const response = await fetch('/api/objectql', {
-        method: 'POST',
-        headers: { 'Content-Type': 'application/json' },
-        body: JSON.stringify({
-          op: 'update',
-          object: objectName,
-          args: {
-            id: recordId,
-            data: formData
-          }
-        })
-      });
-
-      if (!response.ok) {
-        throw new Error('Failed to update record');
-      }
-
-      setEditing(false);
-      fetchRecord();
-    } catch (e: any) {
-      alert(`Error: ${e.message}`);
-    }
-  };
-
-  const handleDelete = async () => {
-    if (!confirm('Are you sure you want to delete this record?')) {
-      return;
-    }
-
-    try {
-      const response = await fetch('/api/objectql', {
-        method: 'POST',
-        headers: { 'Content-Type': 'application/json' },
-        body: JSON.stringify({
-          op: 'delete',
-          object: objectName,
-          args: { id: recordId }
-        })
-      });
-
-      if (!response.ok) {
-        throw new Error('Failed to delete record');
-      }
-
-      navigate(`/object/${objectName}`);
-    } catch (e: any) {
-      alert(`Error: ${e.message}`);
-    }
-  };
-
-  const formatValue = (value: any): string => {
-    if (value === null || value === undefined) return '-';
-    if (typeof value === 'object') return JSON.stringify(value, null, 2);
-    if (typeof value === 'boolean') return value ? 'Yes' : 'No';
-    return String(value);
-  };
-
-  if (loading) {
-    return (
-      <div className="loading">
-        <div className="spinner"></div>
-        <p>Loading record...</p>
-      </div>
-    );
-  }
-
-  if (error || !record) {
-    return (
-      <div>
-        <div className="breadcrumb">
-          <Link to="/">Objects</Link>
-          <span className="breadcrumb-separator">/</span>
-          <Link to={`/object/${objectName}`}>{objectName}</Link>
-          <span className="breadcrumb-separator">/</span>
-          <span>{recordId}</span>
-        </div>
-        <div className="alert alert-error">
-          <strong>Error:</strong> {error || 'Record not found'}
-        </div>
-      </div>
-    );
-  }
-
-  return (
-    <div>
-      <div className="breadcrumb">
-        <Link to="/">Objects</Link>
-        <span className="breadcrumb-separator">/</span>
-        <Link to={`/object/${objectName}`}>{objectName}</Link>
-        <span className="breadcrumb-separator">/</span>
-        <span>{recordId}</span>
-      </div>
-
-      <div className="card">
-        <div style={{ display: 'flex', justifyContent: 'space-between', alignItems: 'center', marginBottom: '1rem' }}>
-          <h2 className="card-title" style={{ marginBottom: 0 }}>Record Detail</h2>
-          <div style={{ display: 'flex', gap: '0.5rem' }}>
-            {editing ? (
-              <>
-                <button className="btn btn-primary" onClick={handleUpdate}>Save</button>
-                <button className="btn btn-secondary" onClick={() => {
-                  setEditing(false);
-                  setFormData(record);
-                }}>Cancel</button>
-              </>
-            ) : (
-              <>
-                <button className="btn btn-primary" onClick={() => setEditing(true)}>Edit</button>
-                <button className="btn btn-danger" onClick={handleDelete}>Delete</button>
-              </>
-            )}
-          </div>
-        </div>
-
-        {editing ? (
-          <div>
-            {Object.entries(formData).map(([key, value]) => (
-              <div key={key} className="form-group">
-                <label className="form-label">{key}</label>
-                {typeof value === 'object' && value !== null ? (
-                  <textarea
-                    className="form-textarea"
-                    value={JSON.stringify(value, null, 2)}
-                    onChange={(e) => {
-                      try {
-                        setFormData({ ...formData, [key]: JSON.parse(e.target.value) });
-                      } catch {
-                        // Invalid JSON, keep as string
-                      }
-                    }}
-                  />
-                ) : (
-                  <input
-                    type="text"
-                    className="form-input"
-                    value={String(value || '')}
-                    onChange={(e) => setFormData({ ...formData, [key]: e.target.value })}
-                    disabled={key === '_id' || key === 'id'}
-                  />
-                )}
-              </div>
-            ))}
-          </div>
-        ) : (
-          <div className="table-container">
-            <table className="table">
-              <thead>
-                <tr>
-                  <th style={{ width: '30%' }}>Field</th>
-                  <th>Value</th>
-                </tr>
-              </thead>
-              <tbody>
-                {Object.entries(record).map(([key, value]) => (
-                  <tr key={key}>
-                    <td><strong>{key}</strong></td>
-                    <td style={{ whiteSpace: 'pre-wrap', fontFamily: typeof value === 'object' ? 'monospace' : 'inherit' }}>
-                      {formatValue(value)}
-                    </td>
-                  </tr>
-                ))}
-              </tbody>
-            </table>
-          </div>
-        )}
-      </div>
-    </div>
-  );
-}
-
-export default RecordDetail;
diff --git a/packages/tools/studio/src/components/SchemaInspector.tsx b/packages/tools/studio/src/components/SchemaInspector.tsx
deleted file mode 100644
index c0aa01c8..00000000
--- a/packages/tools/studio/src/components/SchemaInspector.tsx
+++ /dev/null
@@ -1,207 +0,0 @@
-import { useState, useEffect } from 'react';
-import { useParams, Link } from 'react-router-dom';
-
-interface Field {
-  name: string;
-  type?: string;
-  label?: string;
-  required?: boolean;
-  defaultValue?: any;
-}
-
-interface ObjectMetadata {
-  name: string;
-  label?: string;
-  fields?: Field[];
-  [key: string]: any;
-}
-
-function SchemaInspector() {
-  const { objectName } = useParams<{ objectName?: string }>();
-  const [objects, setObjects] = useState<ObjectMetadata[]>([]);
-  const [selectedObject, setSelectedObject] = useState<ObjectMetadata | null>(null);
-  const [loading, setLoading] = useState(true);
-  const [error, setError] = useState<string | null>(null);
-
-  useEffect(() => {
-    fetchObjects();
-  }, []);
-
-  useEffect(() => {
-    if (objectName) {
-      fetchObjectDetails(objectName);
-    }
-  }, [objectName]);
-
-  const fetchObjects = async () => {
-    try {
-      setLoading(true);
-      const response = await fetch('/api/metadata/object');
-      if (!response.ok) {
-        throw new Error(`HTTP error! status: ${response.status}`);
-      }
-      const data = await response.json();
-      setObjects(data.items || []);
-    } catch (e: any) {
-      console.error('Failed to fetch objects:', e);
-      setError(e.message);
-    } finally {
-      setLoading(false);
-    }
-  };
-
-  const fetchObjectDetails = async (name: string) => {
-    try {
-      const response = await fetch(`/api/metadata/object/${name}`);
-      if (!response.ok) {
-        throw new Error(`HTTP error! status: ${response.status}`);
-      }
-      const data = await response.json();
-      if (data.fields && !Array.isArray(data.fields)) {
-        data.fields = Object.values(data.fields);
-      }
-      setSelectedObject(data);
-    } catch (e: any) {
-      console.error('Failed to fetch object details:', e);
-      setError(e.message);
-    }
-  };
-
-  if (loading) {
-    return (
-      <div className="loading">
-        <div className="spinner"></div>
-        <p>Loading schema...</p>
-      </div>
-    );
-  }
-
-  if (error) {
-    return (
-      <div className="alert alert-error">
-        <strong>Error:</strong> {error}
-      </div>
-    );
-  }
-
-  return (
-    <div>
-      {objectName && (
-        <div className="breadcrumb">
-          <Link to="/schema">Schema</Link>
-          <span className="breadcrumb-separator">/</span>
-          <span>{objectName}</span>
-        </div>
-      )}
-
-      <div className="card">
-        <h2 className="card-title">Schema Inspector</h2>
-        <p style={{ color: '#718096', marginBottom: '1.5rem' }}>
-          View object definitions and field metadata
-        </p>
-
-        {!objectName ? (
-          <div className="grid grid-2">
-            {objects.map((obj) => (
-              <Link
-                key={obj.name}
-                to={`/schema/${obj.name}`}
-                style={{ textDecoration: 'none', color: 'inherit' }}
-              >
-                <div
-                  className="card"
-                  style={{
-                    cursor: 'pointer',
-                    transition: 'all 0.2s',
-                    border: '1px solid #e2e8f0',
-                  }}
-                  onMouseOver={(e) => {
-                    e.currentTarget.style.borderColor = '#667eea';
-                    e.currentTarget.style.boxShadow = '0 4px 6px rgba(0, 0, 0, 0.1)';
-                  }}
-                  onMouseOut={(e) => {
-                    e.currentTarget.style.borderColor = '#e2e8f0';
-                    e.currentTarget.style.boxShadow = '0 1px 3px rgba(0, 0, 0, 0.1)';
-                  }}
-                >
-                  <h3 style={{ fontSize: '1.125rem', fontWeight: '600', marginBottom: '0.25rem' }}>
-                    {obj.label || obj.name}
-                  </h3>
-                  <p style={{ fontSize: '0.875rem', color: '#718096' }}>
-                    {obj.name}
-                  </p>
-                </div>
-              </Link>
-            ))}
-          </div>
-        ) : selectedObject ? (
-          <div>
-            <div style={{ marginBottom: '2rem' }}>
-              <h3 style={{ fontSize: '1.25rem', fontWeight: '600', marginBottom: '0.5rem' }}>
-                {selectedObject.label || selectedObject.name}
-              </h3>
-              <p style={{ color: '#718096' }}>API Name: <code>{selectedObject.name}</code></p>
-            </div>
-
-            {selectedObject.fields && selectedObject.fields.length > 0 ? (
-              <div>
-                <h4 style={{ fontSize: '1rem', fontWeight: '600', marginBottom: '1rem' }}>Fields</h4>
-                <div className="table-container">
-                  <table className="table">
-                    <thead>
-                      <tr>
-                        <th>Name</th>
-                        <th>Label</th>
-                        <th>Type</th>
-                        <th>Required</th>
-                        <th>Default Value</th>
-                      </tr>
-                    </thead>
-                    <tbody>
-                      {selectedObject.fields.map((field) => (
-                        <tr key={field.name}>
-                          <td><code>{field.name}</code></td>
-                          <td>{field.label || '-'}</td>
-                          <td>
-                            <span className="badge badge-primary">{field.type || 'text'}</span>
-                          </td>
-                          <td>{field.required ? 'Yes' : 'No'}</td>
-                          <td>{field.defaultValue !== undefined ? String(field.defaultValue) : '-'}</td>
-                        </tr>
-                      ))}
-                    </tbody>
-                  </table>
-                </div>
-              </div>
-            ) : (
-              <div className="alert alert-info">
-                No field metadata available for this object.
-              </div>
-            )}
-
-            <div style={{ marginTop: '2rem' }}>
-              <h4 style={{ fontSize: '1rem', fontWeight: '600', marginBottom: '1rem' }}>Raw Definition</h4>
-              <pre style={{
-                background: '#f7fafc',
-                padding: '1rem',
-                borderRadius: '6px',
-                overflow: 'auto',
-                fontSize: '0.875rem',
-                border: '1px solid #e2e8f0'
-              }}>
-                {JSON.stringify(selectedObject, null, 2)}
-              </pre>
-            </div>
-          </div>
-        ) : (
-          <div className="loading">
-            <div className="spinner"></div>
-            <p>Loading object details...</p>
-          </div>
-        )}
-      </div>
-    </div>
-  );
-}
-
-export default SchemaInspector;
diff --git a/packages/tools/studio/src/components/Sidebar.tsx b/packages/tools/studio/src/components/Sidebar.tsx
deleted file mode 100644
index c4776e9d..00000000
--- a/packages/tools/studio/src/components/Sidebar.tsx
+++ /dev/null
@@ -1,128 +0,0 @@
-import { NavLink } from 'react-router-dom';
-import { useMetadata } from '@/hooks/use-metadata';
-import { Database, Home, Loader2, Table2, FileCode, BookOpen, Layers, Layout, Shield, FileText, AlertTriangle, Workflow, Activity, FileJson } from 'lucide-react';
-import { cn } from '@/lib/utils';
-
-const METADATA_TYPES = [
-    { id: 'object', label: 'Objects', icon: Layers },
-    { id: 'app', label: 'Apps', icon: FileJson },
-    { id: 'view', label: 'Views', icon: Layout },
-    { id: 'permission', label: 'Permissions', icon: Shield },
-    { id: 'report', label: 'Reports', icon: FileText },
-    { id: 'validation', label: 'Validations', icon: AlertTriangle },
-    { id: 'workflow', label: 'Workflows', icon: Workflow },
-    { id: 'form', label: 'Forms', icon: Activity },
-];
-
-export function Sidebar() {
-    const { objects, loading, error } = useMetadata();
-
-    return (
-        <div className="w-64 border-r bg-card h-screen flex flex-col">
-            <div className="p-6 border-b flex items-center space-x-2">
-                <Database className="h-6 w-6 text-primary" />
-                <span className="font-bold text-lg">ObjectQL Studio</span>
-            </div>
-            
-            <div className="flex-1 overflow-auto py-4">
-                <nav className="space-y-1 px-2">
-                    <NavLink 
-                        to="/" 
-                        className={({isActive}) => cn(
-                            "flex items-center space-x-2 px-4 py-2 rounded-md text-sm font-medium transition-colors hover:bg-accent hover:text-accent-foreground",
-                            isActive && "bg-accent/50 text-accent-foreground"
-                        )}
-                        end
-                    >
-                        <Home className="h-4 w-4" />
-                        <span>Dashboard</span>
-                    </NavLink>
-
-                    <div className="pt-4 px-4 pb-2">
-                        <h4 className="text-xs font-semibold text-muted-foreground uppercase tracking-wider">
-                            Metadata
-                        </h4>
-                    </div>
-
-                    {METADATA_TYPES.map(type => (
-                        <NavLink 
-                            key={type.id}
-                            to={`/metadata/${type.id}`} 
-                            className={({isActive}) => cn(
-                                "flex items-center space-x-2 px-4 py-2 rounded-md text-sm font-medium transition-colors hover:bg-accent hover:text-accent-foreground",
-                                isActive && "bg-accent/50 text-accent-foreground"
-                            )}
-                        >
-                            <type.icon className="h-4 w-4" />
-                            <span>{type.label}</span>
-                        </NavLink>
-                    ))}
-
-                    <div className="pt-4 px-4 pb-2">
-                        <h4 className="text-xs font-semibold text-muted-foreground uppercase tracking-wider">
-                            Development
-                        </h4>
-                    </div>
-
-                    <NavLink 
-                        to="/schema" 
-                        className={({isActive}) => cn(
-                            "flex items-center space-x-2 px-4 py-2 rounded-md text-sm font-medium transition-colors hover:bg-accent hover:text-accent-foreground",
-                            isActive && "bg-accent/50 text-accent-foreground"
-                        )}
-                    >
-                        <FileCode className="h-4 w-4" />
-                        <span>Schema Editor</span>
-                    </NavLink>
-
-                    <a
-                        href="/swagger" 
-                        target="_blank"
-                        rel="noreferrer"
-                        className="flex items-center space-x-2 px-4 py-2 rounded-md text-sm font-medium transition-colors hover:bg-accent hover:text-accent-foreground"
-                    >
-                        <BookOpen className="h-4 w-4" />
-                        <span>API Docs</span>
-                    </a>
-
-                    <div className="pt-4 px-4 pb-2">
-                        <h4 className="text-xs font-semibold text-muted-foreground uppercase tracking-wider">
-                            Data
-                        </h4>
-                    </div>
-
-                    {loading && (
-                        <div className="px-4 py-2 text-sm text-muted-foreground flex items-center">
-                            <Loader2 className="mr-2 h-4 w-4 animate-spin" />
-                            Loading...
-                        </div>
-                    )}
-
-                    {error && (
-                        <div className="px-4 py-2 text-sm text-red-500">
-                           Failed to load
-                        </div>
-                    )}
-
-                    {!loading && objects.map(obj => (
-                        <NavLink
-                            key={obj.name}
-                            to={`/object/${obj.name}`}
-                            className={({isActive}) => cn(
-                                "flex items-center space-x-2 px-4 py-2 rounded-md text-sm transition-colors hover:bg-accent hover:text-accent-foreground",
-                                isActive ? "bg-accent text-accent-foreground" : "text-muted-foreground"
-                            )}
-                        >
-                            <Table2 className="h-4 w-4" />
-                            <span>{obj.name}</span>
-                        </NavLink>
-                    ))}
-                </nav>
-            </div>
-            
-            <div className="p-4 border-t text-xs text-center text-muted-foreground">
-                v1.3.1
-            </div>
-        </div>
-    );
-}
diff --git a/packages/tools/studio/src/components/ui/button.tsx b/packages/tools/studio/src/components/ui/button.tsx
deleted file mode 100644
index ffcf5941..00000000
--- a/packages/tools/studio/src/components/ui/button.tsx
+++ /dev/null
@@ -1,60 +0,0 @@
-import * as React from "react"
-import { cva, type VariantProps } from "class-variance-authority"
- 
-import { cn } from "@/lib/utils"
- 
-const buttonVariants = cva(
-  "inline-flex items-center justify-center whitespace-nowrap rounded-md text-sm font-medium ring-offset-background transition-colors focus-visible:outline-none focus-visible:ring-2 focus-visible:ring-ring focus-visible:ring-offset-2 disabled:pointer-events-none disabled:opacity-50",
-  {
-    variants: {
-      variant: {
-        default: "bg-primary text-primary-foreground hover:bg-primary/90",
-        destructive:
-          "bg-destructive text-destructive-foreground hover:bg-destructive/90",
-        outline:
-          "border border-input bg-background hover:bg-accent hover:text-accent-foreground",
-        secondary:
-          "bg-secondary text-secondary-foreground hover:bg-secondary/80",
-        ghost: "hover:bg-accent hover:text-accent-foreground",
-        link: "text-primary underline-offset-4 hover:underline",
-      },
-      size: {
-        default: "h-10 px-4 py-2",
-        sm: "h-9 rounded-md px-3",
-        lg: "h-11 rounded-md px-8",
-        icon: "h-10 w-10",
-      },
-    },
-    defaultVariants: {
-      variant: "default",
-      size: "default",
-    },
-  }
-)
- 
-export interface ButtonProps
-  extends React.ButtonHTMLAttributes<HTMLButtonElement>,
-    VariantProps<typeof buttonVariants> {
-  asChild?: boolean
-}
- 
-const Button = React.forwardRef<HTMLButtonElement, ButtonProps>(
-  ({ className, variant, size, asChild = false, ...props }, ref) => {
-    // Note: I am removing @radix-ui/react-slot dependency assumption by falling back to simple render if needed,
-    // but for shadcn strict compliance we need it. I'll assume users can install it or I should have added it.
-    // I forgot to add @radix-ui/react-slot to package.json.
-    // I will stick to standard button for now if I can't depend on radix.
-    // Actually, let's keep it simple and just return 'button'.
-    const Comp = "button"
-    return (
-      <Comp
-        className={cn(buttonVariants({ variant, size, className }))}
-        ref={ref}
-        {...props}
-      />
-    )
-  }
-)
-Button.displayName = "Button"
- 
-export { Button, buttonVariants }
diff --git a/packages/tools/studio/src/components/ui/card.tsx b/packages/tools/studio/src/components/ui/card.tsx
deleted file mode 100644
index 6c39df87..00000000
--- a/packages/tools/studio/src/components/ui/card.tsx
+++ /dev/null
@@ -1,76 +0,0 @@
-import * as React from "react"
- 
-import { cn } from "@/lib/utils"
- 
-const Card = React.forwardRef<
-  HTMLDivElement,
-  React.HTMLAttributes<HTMLDivElement>
->(({ className, ...props }, ref) => (
-  <div
-    ref={ref}
-    className={cn(
-      "rounded-xl border bg-card text-card-foreground shadow",
-      className
-    )}
-    {...props}
-  />
-))
-Card.displayName = "Card"
- 
-const CardHeader = React.forwardRef<
-  HTMLDivElement,
-  React.HTMLAttributes<HTMLDivElement>
->(({ className, ...props }, ref) => (
-  <div
-    ref={ref}
-    className={cn("flex flex-col space-y-1.5 p-6", className)}
-    {...props}
-  />
-))
-CardHeader.displayName = "CardHeader"
- 
-const CardTitle = React.forwardRef<
-  HTMLParagraphElement,
-  React.HTMLAttributes<HTMLHeadingElement>
->(({ className, ...props }, ref) => (
-  <h3
-    ref={ref}
-    className={cn("font-semibold leading-none tracking-tight", className)}
-    {...props}
-  />
-))
-CardTitle.displayName = "CardTitle"
- 
-const CardDescription = React.forwardRef<
-  HTMLParagraphElement,
-  React.HTMLAttributes<HTMLParagraphElement>
->(({ className, ...props }, ref) => (
-  <p
-    ref={ref}
-    className={cn("text-sm text-muted-foreground", className)}
-    {...props}
-  />
-))
-CardDescription.displayName = "CardDescription"
- 
-const CardContent = React.forwardRef<
-  HTMLDivElement,
-  React.HTMLAttributes<HTMLDivElement>
->(({ className, ...props }, ref) => (
-  <div ref={ref} className={cn("p-6 pt-0", className)} {...props} />
-))
-CardContent.displayName = "CardContent"
- 
-const CardFooter = React.forwardRef<
-  HTMLDivElement,
-  React.HTMLAttributes<HTMLDivElement>
->(({ className, ...props }, ref) => (
-  <div
-    ref={ref}
-    className={cn("flex items-center p-6 pt-0", className)}
-    {...props}
-  />
-))
-CardFooter.displayName = "CardFooter"
- 
-export { Card, CardHeader, CardFooter, CardTitle, CardDescription, CardContent }
diff --git a/packages/tools/studio/src/hooks/use-metadata.ts b/packages/tools/studio/src/hooks/use-metadata.ts
deleted file mode 100644
index 7bfdb381..00000000
--- a/packages/tools/studio/src/hooks/use-metadata.ts
+++ /dev/null
@@ -1,39 +0,0 @@
-import { useState, useEffect } from 'react';
-
-export interface Field {
-    type: string;
-    required?: boolean;
-    label?: string;
-}
-
-export interface ObjectConfig {
-    name: string;
-    fields: Record<string, Field>;
-    description?: string;
-}
-
-export function useMetadata() {
-    const [objects, setObjects] = useState<ObjectConfig[]>([]);
-    const [loading, setLoading] = useState(true);
-    const [error, setError] = useState<Error | null>(null);
-
-    useEffect(() => {
-        fetch('/api/metadata/object')
-            .then(async res => {
-                if (!res.ok) throw new Error('Failed to fetch metadata');
-                // The API might return { objects: [...] } or just [...]
-                // Assuming standard objectql server returns { objects: [...] } or Array
-                const data = await res.json();
-                // Check format
-                const list = Array.isArray(data) ? data : (data.items || []);
-                setObjects(list);
-            })
-            .catch(err => {
-                console.error(err);
-                setError(err);
-            })
-            .finally(() => setLoading(false));
-    }, []);
-
-    return { objects, loading, error };
-}
diff --git a/packages/tools/studio/src/index.css b/packages/tools/studio/src/index.css
deleted file mode 100644
index f53b908c..00000000
--- a/packages/tools/studio/src/index.css
+++ /dev/null
@@ -1,59 +0,0 @@
-@tailwind base;
-@tailwind components;
-@tailwind utilities;
- 
-@layer base {
-  :root {
-    --background: 0 0% 100%;
-    --foreground: 222.2 84% 4.9%;
-    --card: 0 0% 100%;
-    --card-foreground: 222.2 84% 4.9%;
-    --popover: 0 0% 100%;
-    --popover-foreground: 222.2 84% 4.9%;
-    --primary: 222.2 47.4% 11.2%;
-    --primary-foreground: 210 40% 98%;
-    --secondary: 210 40% 96.1%;
-    --secondary-foreground: 222.2 47.4% 11.2%;
-    --muted: 210 40% 96.1%;
-    --muted-foreground: 215.4 16.3% 46.9%;
-    --accent: 210 40% 96.1%;
-    --accent-foreground: 222.2 47.4% 11.2%;
-    --destructive: 0 84.2% 60.2%;
-    --destructive-foreground: 210 40% 98%;
-    --border: 214.3 31.8% 91.4%;
-    --input: 214.3 31.8% 91.4%;
-    --ring: 222.2 84% 4.9%;
-    --radius: 0.5rem;
-  }
- 
-  .dark {
-    --background: 222.2 84% 4.9%;
-    --foreground: 210 40% 98%;
-    --card: 222.2 84% 4.9%;
-    --card-foreground: 210 40% 98%;
-    --popover: 222.2 84% 4.9%;
-    --popover-foreground: 210 40% 98%;
-    --primary: 210 40% 98%;
-    --primary-foreground: 222.2 47.4% 11.2%;
-    --secondary: 217.2 32.6% 17.5%;
-    --secondary-foreground: 210 40% 98%;
-    --muted: 217.2 32.6% 17.5%;
-    --muted-foreground: 215 20.2% 65.1%;
-    --accent: 217.2 32.6% 17.5%;
-    --accent-foreground: 210 40% 98%;
-    --destructive: 0 62.8% 30.6%;
-    --destructive-foreground: 210 40% 98%;
-    --border: 217.2 32.6% 17.5%;
-    --input: 217.2 32.6% 17.5%;
-    --ring: 212.7 26.8% 83.9%;
-  }
-}
- 
-@layer base {
-  * {
-    @apply border-border;
-  }
-  body {
-    @apply bg-background text-foreground;
-  }
-}
diff --git a/packages/tools/studio/src/lib/utils.ts b/packages/tools/studio/src/lib/utils.ts
deleted file mode 100644
index 04b43bf9..00000000
--- a/packages/tools/studio/src/lib/utils.ts
+++ /dev/null
@@ -1,6 +0,0 @@
-import { type ClassValue, clsx } from "clsx"
-import { twMerge } from "tailwind-merge"
- 
-export function cn(...inputs: ClassValue[]) {
-  return twMerge(clsx(inputs))
-}
\ No newline at end of file
diff --git a/packages/tools/studio/src/main.tsx b/packages/tools/studio/src/main.tsx
deleted file mode 100644
index 9aa52ffd..00000000
--- a/packages/tools/studio/src/main.tsx
+++ /dev/null
@@ -1,10 +0,0 @@
-import React from 'react';
-import ReactDOM from 'react-dom/client';
-import App from './App';
-import './index.css';
-
-ReactDOM.createRoot(document.getElementById('root')!).render(
-  <React.StrictMode>
-    <App />
-  </React.StrictMode>,
-);
diff --git a/packages/tools/studio/src/pages/Dashboard.tsx b/packages/tools/studio/src/pages/Dashboard.tsx
deleted file mode 100644
index 5b46a8c7..00000000
--- a/packages/tools/studio/src/pages/Dashboard.tsx
+++ /dev/null
@@ -1,36 +0,0 @@
-import { useMetadata } from '@/hooks/use-metadata';
-import { Card, CardHeader, CardTitle, CardContent, CardDescription } from '@/components/ui/card';
-
-export function Dashboard() {
-    const { objects } = useMetadata();
-
-    return (
-        <div className="p-8">
-            <h1 className="text-3xl font-bold mb-6">Dashboard</h1>
-            
-            <div className="grid grid-cols-1 md:grid-cols-2 lg:grid-cols-3 gap-6">
-                <Card>
-                    <CardHeader>
-                        <CardTitle>Total Collections</CardTitle>
-                        <CardDescription>Registered objects in schema</CardDescription>
-                    </CardHeader>
-                    <CardContent>
-                        <div className="text-2xl font-bold">{objects.length}</div>
-                    </CardContent>
-                </Card>
-
-                {objects.map(obj => (
-                    <Card key={obj.name} className="hover:bg-accent/10 transition-colors">
-                        <CardHeader>
-                            <CardTitle>{obj.name}</CardTitle>
-                            <CardDescription className="truncate">{obj.description || 'No description'}</CardDescription>
-                        </CardHeader>
-                        <CardContent className="flex justify-between items-center text-sm">
-                             <span className="text-muted-foreground">{Object.keys(obj.fields).length} fields</span>
-                        </CardContent>
-                    </Card>
-                ))}
-            </div>
-        </div>
-    );
-}
diff --git a/packages/tools/studio/src/pages/MetadataBrowser.tsx b/packages/tools/studio/src/pages/MetadataBrowser.tsx
deleted file mode 100644
index 949e4f84..00000000
--- a/packages/tools/studio/src/pages/MetadataBrowser.tsx
+++ /dev/null
@@ -1,214 +0,0 @@
-import { useState, useEffect } from 'react';
-import { useParams, useNavigate } from 'react-router-dom';
-import { Card, CardHeader, CardTitle, CardContent } from '@/components/ui/card';
-import { Button } from '@/components/ui/button';
-import { Loader2, ArrowLeft, FileJson, Layers, Shield, FileText, Activity, Layout, AlertTriangle, Workflow } from 'lucide-react';
-import { cn } from '@/lib/utils';
-
-// Helper to format JSON
-function JsonViewer({ data }: { data: any }) {
-    return (
-        <pre className="bg-muted p-4 rounded-md overflow-auto text-xs font-mono max-h-[600px]">
-            {JSON.stringify(data, null, 2)}
-        </pre>
-    );
-}
-
-const METADATA_TYPES = [
-    { id: 'object', label: 'Objects', icon: Layers },
-    { id: 'app', label: 'Apps', icon: FileJson },
-    { id: 'view', label: 'Views', icon: Layout },
-    { id: 'permission', label: 'Permissions', icon: Shield },
-    { id: 'report', label: 'Reports', icon: FileText },
-    { id: 'validation', label: 'Validations', icon: AlertTriangle },
-    { id: 'workflow', label: 'Workflows', icon: Workflow },
-    { id: 'form', label: 'Forms', icon: Activity },
-];
-
-export function MetadataBrowser() {
-    const { type: urlType } = useParams<{ type: string }>();
-    const navigate = useNavigate();
-    
-    // State
-    const [selectedType, setSelectedType] = useState<string | null>(urlType || null);
-    const [selectedItem, setSelectedItem] = useState<string | null>(null);
-    
-    const [items, setItems] = useState<any[]>([]);
-    const [itemDetail, setItemDetail] = useState<any>(null);
-    
-    const [loading, setLoading] = useState(false);
-    const [error, setError] = useState<string | null>(null);
-
-    // Sync selectedType with URL
-    useEffect(() => {
-        if (urlType) {
-            setSelectedType(urlType);
-        } else {
-            setSelectedType(null);
-        }
-    }, [urlType]);
-
-    // Fetch list when type changes
-    useEffect(() => {
-        if (!selectedType) return;
-
-        setLoading(true);
-        setItems([]);
-        setSelectedItem(null);
-        setError(null);
-
-        fetch(`/api/metadata/${selectedType}`)
-            .then(async res => {
-                if (!res.ok) throw new Error(`Failed to fetch ${selectedType}`);
-                const data = await res.json();
-                // API returns { [type]: [...] } or for object: { object: [...], objects: [...] }
-                // Handle singular/plural mismatch from API response
-                const list = data[selectedType] || data.items || []; 
-                setItems(list);
-            })
-            .catch(err => setError(err.message))
-            .finally(() => setLoading(false));
-
-    }, [selectedType]);
-
-    // Fetch detail when item changes
-    useEffect(() => {
-        if (!selectedType || !selectedItem) return;
-
-        setLoading(true);
-        setItemDetail(null);
-        setError(null);
-
-        // For objects, the ID is the name. For others, it relies on file structure or id
-        fetch(`/api/metadata/${selectedType}/${selectedItem}`)
-            .then(async res => {
-                if (!res.ok) throw new Error(`Failed to fetch detail for ${selectedItem}`);
-                const data = await res.json();
-                setItemDetail(data);
-            })
-            .catch(err => setError(err.message))
-            .finally(() => setLoading(false));
-
-    }, [selectedType, selectedItem]);
-
-    // --- Render: Main Menu (Type Selection) ---
-    if (!selectedType) {
-        return (
-            <div className="p-8 max-w-6xl mx-auto">
-                <h1 className="text-3xl font-bold mb-6">Metadata Registry</h1>
-                <p className="text-muted-foreground mb-8">
-                    Browse the active runtime metadata loaded in the ObjectQL engine.
-                </p>
-
-                <div className="grid grid-cols-1 md:grid-cols-3 lg:grid-cols-4 gap-6">
-                    {METADATA_TYPES.map((type) => {
-                        const Icon = type.icon;
-                        return (
-                            <Card 
-                                key={type.id} 
-                                className="cursor-pointer hover:bg-accent/50 transition-colors border-2 hover:border-primary/50"
-                                onClick={() => navigate(`/metadata/${type.id}`)}
-                            >
-                                <CardHeader className="flex flex-row items-center space-y-0 space-x-4">
-                                    <div className="p-2 bg-primary/10 rounded-full text-primary">
-                                        <Icon className="h-6 w-6" />
-                                    </div>
-                                    <CardTitle className="text-xl">{type.label}</CardTitle>
-                                </CardHeader>
-                                <CardContent>
-                                    <p className="text-sm text-muted-foreground">
-                                        Browse {type.label.toLowerCase()} definitions
-                                    </p>
-                                </CardContent>
-                            </Card>
-                        );
-                    })}
-                </div>
-            </div>
-        );
-    }
-
-    // --- Render: List or Detail ---
-    return (
-        <div className="flex h-screen overflow-hidden">
-            {/* Left Panel: List */}
-            <div className="w-1/3 border-r bg-card flex flex-col">
-                <div className="p-4 border-b flex items-center space-x-2">
-                    <Button variant="ghost" size="sm" onClick={() => navigate('/metadata')}>
-                        <ArrowLeft className="h-4 w-4" />
-                    </Button>
-                    <h2 className="font-semibold text-lg capitalize">{selectedType} List</h2>
-                </div>
-                
-                 <div className="flex-1 overflow-auto p-2 space-y-2">
-                    {error && (
-                        <div className="p-4 text-sm text-red-500 bg-red-50 rounded mb-2">
-                            Error: {error}
-                        </div>
-                    )}
-
-                    {loading && items.length === 0 && (
-                        <div className="flex justify-center p-8 text-muted-foreground">
-                            <Loader2 className="h-6 w-6 animate-spin mr-2" /> Loading...
-                        </div>
-                    )}
-
-                    {!loading && items.map((item: any) => {
-                        const id = item.name || item.id;
-                        return (
-                            <div 
-                                key={id}
-                                onClick={() => setSelectedItem(id)}
-                                className={cn(
-                                    "p-3 rounded-md cursor-pointer text-sm font-medium transition-colors border",
-                                    selectedItem === id 
-                                        ? "bg-primary text-primary-foreground border-primary" 
-                                        : "hover:bg-accent border-transparent"
-                                )}
-                            >   
-                                <div className="flex justify-between items-center">
-                                    <span>{item.label || item.name}</span>
-                                    {item.name !== item.label && (
-                                        <span className="text-xs opacity-70 ml-2 font-mono">({item.name})</span>
-                                    )}
-                                </div>
-                            </div>
-                        );
-                    })}
-
-                    {!loading && items.length === 0 && (
-                        <div className="text-center p-8 text-muted-foreground text-sm">
-                            No {selectedType} found.
-                        </div>
-                    )}
-                </div>
-            </div>
-
-            {/* Right Panel: Detail */}
-            <div className="flex-1 bg-muted/20 flex flex-col h-full overflow-hidden">
-                {!selectedItem ? (
-                    <div className="flex-1 flex items-center justify-center text-muted-foreground">
-                        Select an item to view details
-                    </div>
-                ) : (
-                    <div className="flex-1 flex flex-col h-full overflow-hidden">
-                         <div className="p-4 border-b bg-card">
-                             <h2 className="text-xl font-bold">{selectedItem}</h2>
-                         </div>
-                         <div className="flex-1 overflow-auto p-6">
-                            {loading && !itemDetail ? (
-                                <div className="flex items-center text-muted-foreground">
-                                     <Loader2 className="h-4 w-4 animate-spin mr-2" /> Loading details...
-                                </div>
-                            ) : (
-                                <JsonViewer data={itemDetail} />
-                            )}
-                         </div>
-                    </div>
-                )}
-            </div>
-        </div>
-    );
-}
-
-export default MetadataBrowser;
diff --git a/packages/tools/studio/src/pages/ObjectView.tsx b/packages/tools/studio/src/pages/ObjectView.tsx
deleted file mode 100644
index 03c79795..00000000
--- a/packages/tools/studio/src/pages/ObjectView.tsx
+++ /dev/null
@@ -1,264 +0,0 @@
-import { useEffect, useState, useMemo } from 'react';
-import { AgGridReact } from 'ag-grid-react';
-import { ColDef } from 'ag-grid-community';
-import 'ag-grid-community/styles/ag-grid.css';
-import 'ag-grid-community/styles/ag-theme-quartz.css';
-import { Button } from '@/components/ui/button';
-import { RefreshCw, Plus, Table2, FileCode } from 'lucide-react';
-import { cn } from '@/lib/utils';
-import { FileEditor } from '@/components/FileEditor';
-
-interface ObjectViewProps {
-    objectName: string;
-}
-
-export function ObjectView({ objectName }: ObjectViewProps) {
-    // const [rowData, setRowData] = useState<any[]>([]); // Using Server Side
-    const [columnDefs, setColumnDefs] = useState<ColDef[]>([]);
-    const [loading, setLoading] = useState(false);
-    const [activeTab, setActiveTab] = useState<'data' | 'schema'>('data');
-    const [schemaFile, setSchemaFile] = useState<string | null>(null);
-
-    const [gridApi, setGridApi] = useState<any>(null);
-
-    // Initial load for columns
-    useEffect(() => {
-        const loadColumns = async () => {
-             const metaRes = await fetch('/api/metadata');
-             const meta = await metaRes.json();
-             const objects = Array.isArray(meta) ? meta : meta.objects;
-             const currentObj = objects.find((o: any) => o.name === objectName);
-
-             if (currentObj) {
-                 const cols: ColDef[] = [
-                     { field: 'id', headerName: 'ID', width: 100, pinned: 'left', filter: 'agTextColumnFilter' }
-                 ];
-                 
-                 Object.entries(currentObj.fields).forEach(([key, field]: [string, any]) => {
-                     cols.push({
-                         field: key,
-                         headerName: field.label || key,
-                         flex: 1,
-                         filter: 'agTextColumnFilter', // Enforce text filter for simplicity in Infinite Model
-                         filterParams: {
-                            filterOptions: ['contains', 'equals'],
-                            suppressAndOrCondition: true
-                         }
-                     });
-                 });
-                 
-                 setColumnDefs(cols);
-             }
-        };
-        loadColumns();
-    }, [objectName]);
-
-    const onGridReady = (params: any) => {
-        setGridApi(params.api);
-        setLoading(true);
-        
-        const datasource = {
-            getRows: async (params: any) => {
-                const { startRow, endRow, filterModel, sortModel } = params;
-                setLoading(true);
-                
-                try {
-                    // 1. Convert Filters
-                    const filters: any[] = [];
-                    if (filterModel) {
-                        for (const key of Object.keys(filterModel)) {
-                            const model = filterModel[key];
-                            // agTextColumnFilter model: { filterType: 'text', type: 'contains', filter: 'value' }
-                            if (model.filterType === 'text') {
-                                if (model.type === 'contains') {
-                                    filters.push([key, 'contains', model.filter]);
-                                } else if (model.type === 'equals') {
-                                    filters.push([key, '=', model.filter]);
-                                }
-                            }
-                        }
-                    }
-
-                    // 2. Convert Sort
-                    const sort = sortModel.map((s: any) => [s.colId, s.sort]);
-
-                    // 3. Fetch Data
-                    const response = await fetch('/api/objectql', {
-                        method: 'POST',
-                        headers: { 'Content-Type': 'application/json' },
-                        body: JSON.stringify({
-                            op: 'find',
-                            object: objectName,
-                            args: {
-                                skip: startRow,
-                                limit: endRow - startRow,
-                                filters: filters.length > 0 ? filters : undefined,
-                                sort: sort.length > 0 ? sort : undefined
-                            }
-                        })
-                    });
-                    const resJson = await response.json();
-                    // Support new format (items) and old format (data)
-                    const rows = resJson.items || resJson.data || resJson; // normalize
-
-                    // 4. Fetch Count (for total pagination)
-                    // Optimization: Only fetch count if we don't know it or filter changed? 
-                    // For Infinite Scroll simplicity, we fetch it.
-                    let lastRow = -1;
-                    if (rows.length < (endRow - startRow)) {
-                        lastRow = startRow + rows.length;
-                    } else {
-                         const countRes = await fetch('/api/objectql', {
-                            method: 'POST',
-                            headers: { 'Content-Type': 'application/json' },
-                            body: JSON.stringify({
-                                op: 'count',
-                                object: objectName,
-                                args: {
-                                    filters: filters.length > 0 ? filters : undefined
-                                }
-                            })
-                        });
-                        const countJson = await countRes.json();
-                        // Count operation returns { count: number, '@type': string }
-                        lastRow = typeof countJson === 'number' ? countJson : countJson.count;
-                    }
-
-                   params.successCallback(rows, lastRow);
-
-                } catch (e) {
-                    console.error('Datasource getRows error:', e);
-                    params.failCallback();
-                } finally {
-                    setLoading(false);
-                }
-            }
-        };
-
-        params.api.setDatasource(datasource);
-    };
-
-    const refreshData = () => {
-        if (gridApi) {
-            gridApi.refreshInfiniteCache();
-        }
-    };
-
-    const fetchSchemaFile = async () => {
-        // If we already have the file for this object, don't re-fetch unless objectName changed
-        // But here we rely on useEffect deps
-        try {
-            const res = await fetch(`/api/schema/find?object=${objectName}`);
-            if (res.ok) {
-                const data = await res.json();
-                setSchemaFile(data.file);
-            } else {
-                setSchemaFile(null);
-                console.error('Failed to find schema file');
-            }
-        } catch (e) {
-            console.error(e);
-        }
-    };
-
-    useEffect(() => {
-        setActiveTab('data');
-    }, [objectName]);
-
-    useEffect(() => {
-        if (activeTab === 'schema') {
-            fetchSchemaFile();
-        }
-    }, [objectName, activeTab]);
-
-
-    const defaultColDef = useMemo(() => {
-        return {
-            sortable: true,
-            filter: true,
-            resizable: true,
-            floatingFilter: true, // Enable Floating Filter
-        };
-    }, []);
-
-    return (
-        <div className="flex h-full flex-col">
-            {/* Header */}
-            <div className="border-b px-6 py-4 flex items-center justify-between bg-card text-card-foreground">
-                <div className="flex flex-col gap-1">
-                    <h1 className="text-2xl font-bold tracking-tight capitalize">{objectName}</h1>
-                    <div className="flex space-x-1">
-                         <button
-                            onClick={() => setActiveTab('data')}
-                            className={cn(
-                                "flex items-center space-x-2 px-3 py-1.5 text-sm font-medium rounded-md transition-colors",
-                                activeTab === 'data' 
-                                    ? "bg-primary/10 text-primary" 
-                                    : "text-muted-foreground hover:bg-muted hover:text-foreground"
-                            )}
-                        >
-                            <Table2 className="h-4 w-4" />
-                            <span>Data</span>
-                        </button>
-                        <button
-                            onClick={() => setActiveTab('schema')}
-                            className={cn(
-                                "flex items-center space-x-2 px-3 py-1.5 text-sm font-medium rounded-md transition-colors",
-                                activeTab === 'schema' 
-                                    ? "bg-primary/10 text-primary" 
-                                    : "text-muted-foreground hover:bg-muted hover:text-foreground"
-                            )}
-                        >
-                            <FileCode className="h-4 w-4" />
-                            <span>Schema</span>
-                        </button>
-                    </div>
-                </div>
-                
-                {activeTab === 'data' && (
-                    <div className="flex items-center space-x-2">
-                        <Button variant="outline" size="sm" onClick={refreshData} disabled={loading}>
-                            <RefreshCw className={cn("mr-2 h-4 w-4", loading && "animate-spin")} />
-                            Refresh
-                        </Button>
-                        <Button size="sm">
-                            <Plus className="mr-2 h-4 w-4" />
-                            New Record
-                        </Button>
-                    </div>
-                )}
-            </div>
-
-            {/* Content */}
-            <div className="flex-1 overflow-hidden p-6 bg-muted/20">
-                {activeTab === 'data' ? (
-                     <div className="rounded-md overflow-hidden bg-card h-full" style={{opacity: loading ? 0.6 : 1}}>
-                        <div className="ag-theme-quartz h-full w-full">
-                            <AgGridReact
-                                rowModelType="infinite"
-                                onGridReady={onGridReady}
-                                columnDefs={columnDefs}
-                                defaultColDef={defaultColDef}
-                                pagination={true}
-                                paginationPageSize={20}
-                                cacheBlockSize={20}
-                                rowSelection="multiple"
-                                maxBlocksInCache={10}
-                            />
-                        </div>
-                    </div>
-                ) : (
-                    <div className="h-full bg-card rounded-md border">
-                        {schemaFile ? (
-                            <FileEditor filePath={schemaFile} className="h-full border-0" />
-                        ) : (
-                            <div className="flex h-full items-center justify-center text-muted-foreground">
-                                {loading ? 'Loading schema...' : 'Could not find definition file for this object.'}
-                            </div>
-                        )}
-                    </div>
-                )}
-            </div>
-        </div>
-    );
-}
diff --git a/packages/tools/studio/src/pages/SchemaEditor.tsx b/packages/tools/studio/src/pages/SchemaEditor.tsx
deleted file mode 100644
index 1471840a..00000000
--- a/packages/tools/studio/src/pages/SchemaEditor.tsx
+++ /dev/null
@@ -1,85 +0,0 @@
-import { useState, useEffect } from 'react';
-import { Button } from '@/components/ui/button';
-import { Card, CardContent, CardHeader, CardTitle, CardDescription } from '@/components/ui/card';
-import { FileCode, RefreshCw } from 'lucide-react';
-import { cn } from '@/lib/utils';
-import { FileEditor } from '@/components/FileEditor';
-
-export function SchemaEditor() {
-    const [files, setFiles] = useState<string[]>([]);
-    const [selectedFile, setSelectedFile] = useState<string | null>(null);
-    const [error, setError] = useState<string | null>(null);
-
-    useEffect(() => {
-        fetchFiles();
-    }, []);
-
-    const fetchFiles = async () => {
-        try {
-            const res = await fetch('/api/schema/files');
-            if (!res.ok) throw new Error('Failed to fetch files');
-            const data = await res.json();
-            setFiles(data.files || []);
-        } catch (e) {
-            console.error(e);
-            setError('Failed to load file list');
-        }
-    };
-
-    return (
-        <div className="flex h-full flex-col p-6 space-y-6">
-            <div className="flex items-center justify-between">
-                <div className="flex flex-col gap-1">
-                    <h2 className="text-3xl font-bold tracking-tight">Schema Editor</h2>
-                    {error && <p className="text-sm text-red-500">{error}</p>}
-                </div>
-                <Button variant="outline" size="sm" onClick={fetchFiles}>
-                    <RefreshCw className="mr-2 h-4 w-4" /> Refresh
-                </Button>
-            </div>
-
-            <div className="grid grid-cols-1 md:grid-cols-4 gap-6 h-full min-h-[500px]">
-                {/* File List */}
-                <Card className="md:col-span-1 flex flex-col">
-                    <CardHeader className="py-4">
-                        <CardTitle className="text-lg">Files</CardTitle>
-                        <CardDescription>Select a schema file to edit</CardDescription>
-                    </CardHeader>
-                    <CardContent className="flex-1 overflow-auto p-2">
-                        <div className="space-y-1">
-                            {files.map(file => (
-                                <button
-                                    key={file}
-                                    onClick={() => setSelectedFile(file)}
-                                    className={cn(
-                                        "w-full text-left px-3 py-2 text-sm rounded-md transition-colors flex items-center",
-                                        selectedFile === file 
-                                            ? "bg-primary text-primary-foreground font-medium" 
-                                            : "hover:bg-muted"
-                                    )}
-                                >
-                                    <FileCode className="mr-2 h-4 w-4 opacity-70" />
-                                    {file}
-                                </button>
-                            ))}
-                            {files.length === 0 && (
-                                <div className="text-sm text-muted-foreground p-2">No schema files found</div>
-                            )}
-                        </div>
-                    </CardContent>
-                </Card>
-
-                {/* Editor */}
-                <div className="md:col-span-3 h-full">
-                    {selectedFile ? (
-                        <FileEditor filePath={selectedFile} />
-                    ) : (
-                        <Card className="h-full flex items-center justify-center">
-                            <div className="text-muted-foreground">Select a file to view content</div>
-                        </Card>
-                    )}
-                </div>
-            </div>
-        </div>
-    );
-}
diff --git a/packages/tools/studio/tailwind.config.cjs b/packages/tools/studio/tailwind.config.cjs
deleted file mode 100644
index 7cb7e37a..00000000
--- a/packages/tools/studio/tailwind.config.cjs
+++ /dev/null
@@ -1,77 +0,0 @@
-/** @type {import('tailwindcss').Config} */
-module.exports = {
-  darkMode: ["class"],
-  content: [
-    './pages/**/*.{ts,tsx}',
-    './components/**/*.{ts,tsx}',
-    './app/**/*.{ts,tsx}',
-    './src/**/*.{ts,tsx}',
-  ],
-  prefix: "",
-  theme: {
-    container: {
-      center: true,
-      padding: "2rem",
-      screens: {
-        "2xl": "1400px",
-      },
-    },
-    extend: {
-      colors: {
-        border: "hsl(var(--border))",
-        input: "hsl(var(--input))",
-        ring: "hsl(var(--ring))",
-        background: "hsl(var(--background))",
-        foreground: "hsl(var(--foreground))",
-        primary: {
-          DEFAULT: "hsl(var(--primary))",
-          foreground: "hsl(var(--primary-foreground))",
-        },
-        secondary: {
-          DEFAULT: "hsl(var(--secondary))",
-          foreground: "hsl(var(--secondary-foreground))",
-        },
-        destructive: {
-          DEFAULT: "hsl(var(--destructive))",
-          foreground: "hsl(var(--destructive-foreground))",
-        },
-        muted: {
-          DEFAULT: "hsl(var(--muted))",
-          foreground: "hsl(var(--muted-foreground))",
-        },
-        accent: {
-          DEFAULT: "hsl(var(--accent))",
-          foreground: "hsl(var(--accent-foreground))",
-        },
-        popover: {
-          DEFAULT: "hsl(var(--popover))",
-          foreground: "hsl(var(--popover-foreground))",
-        },
-        card: {
-          DEFAULT: "hsl(var(--card))",
-          foreground: "hsl(var(--card-foreground))",
-        },
-      },
-      borderRadius: {
-        lg: "var(--radius)",
-        md: "calc(var(--radius) - 2px)",
-        sm: "calc(var(--radius) - 4px)",
-      },
-      keyframes: {
-        "accordion-down": {
-          from: { height: "0" },
-          to: { height: "var(--radix-accordion-content-height)" },
-        },
-        "accordion-up": {
-          from: { height: "var(--radix-accordion-content-height)" },
-          to: { height: "0" },
-        },
-      },
-      animation: {
-        "accordion-down": "accordion-down 0.2s ease-out",
-        "accordion-up": "accordion-up 0.2s ease-out",
-      },
-    },
-  },
-  plugins: [require("tailwindcss-animate")],
-}
\ No newline at end of file
diff --git a/packages/tools/studio/tsconfig.json b/packages/tools/studio/tsconfig.json
deleted file mode 100644
index 841ca8af..00000000
--- a/packages/tools/studio/tsconfig.json
+++ /dev/null
@@ -1,25 +0,0 @@
-{
-  "extends": "../../../tsconfig.base.json",
-  "compilerOptions": {
-    "target": "ES2020",
-    "useDefineForClassFields": true,
-    "lib": ["ES2020", "DOM", "DOM.Iterable"],
-    "module": "ESNext",
-    "skipLibCheck": true,
-    "moduleResolution": "bundler",
-    "allowImportingTsExtensions": true,
-    "resolveJsonModule": true,
-    "isolatedModules": true,
-    "noEmit": true,
-    "jsx": "react-jsx",
-    "strict": true,
-    "noUnusedLocals": true,
-    "noUnusedParameters": true,
-    "noFallthroughCasesInSwitch": true,
-    "baseUrl": ".",
-    "paths": {
-      "@/*": ["./src/*"]
-    }
-  },
-  "include": ["src"]
-}
diff --git a/packages/tools/studio/vite.config.ts b/packages/tools/studio/vite.config.ts
deleted file mode 100644
index 06b6a44e..00000000
--- a/packages/tools/studio/vite.config.ts
+++ /dev/null
@@ -1,26 +0,0 @@
-import { defineConfig } from 'vite';
-import react from '@vitejs/plugin-react';
-import path from 'path';
-
-export default defineConfig({
-  plugins: [react()],
-  resolve: {
-    alias: {
-      "@": path.resolve(__dirname, "./src"),
-    },
-  },
-  base: '/studio/',
-  build: {
-    outDir: 'dist',
-    emptyOutDir: true,
-  },
-  server: {
-    port: 3005,
-    proxy: {
-      '/api': {
-        target: 'http://localhost:3004',
-        changeOrigin: true,
-      }
-    }
-  }
-});

From 5122915c49b821e7ed3d7120f9fcb9f86521248d Mon Sep 17 00:00:00 2001
From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com>
Date: Thu, 15 Jan 2026 03:22:23 +0000
Subject: [PATCH 3/7] Changes before error encountered

Co-authored-by: hotlong <50353452+hotlong@users.noreply.github.com>
---
 packages/starters/basic/src/main.menu.yml     |  30 --
 .../pages/create_project_wizard.page.yml      | 244 ----------------
 .../projects/pages/project_detail.page.yml    | 258 ----------------
 .../projects/project_status.report.yml        |  39 ---
 .../src/modules/projects/projects.form.yml    |  41 ---
 .../src/modules/projects/projects.view.yml    |  35 ---
 .../basic/src/pages/dashboard.page.yml        | 206 -------------
 .../starters/basic/src/pages/landing.page.yml | 275 ------------------
 .../enterprise/src/menus/erp.menu.yml         |  11 -
 .../starters/express-api/src/test.view.yml    |   9 -
 10 files changed, 1148 deletions(-)
 delete mode 100644 packages/starters/basic/src/main.menu.yml
 delete mode 100644 packages/starters/basic/src/modules/projects/pages/create_project_wizard.page.yml
 delete mode 100644 packages/starters/basic/src/modules/projects/pages/project_detail.page.yml
 delete mode 100644 packages/starters/basic/src/modules/projects/project_status.report.yml
 delete mode 100644 packages/starters/basic/src/modules/projects/projects.form.yml
 delete mode 100644 packages/starters/basic/src/modules/projects/projects.view.yml
 delete mode 100644 packages/starters/basic/src/pages/dashboard.page.yml
 delete mode 100644 packages/starters/basic/src/pages/landing.page.yml
 delete mode 100644 packages/starters/enterprise/src/menus/erp.menu.yml
 delete mode 100644 packages/starters/express-api/src/test.view.yml

diff --git a/packages/starters/basic/src/main.menu.yml b/packages/starters/basic/src/main.menu.yml
deleted file mode 100644
index 6df5cb96..00000000
--- a/packages/starters/basic/src/main.menu.yml
+++ /dev/null
@@ -1,30 +0,0 @@
-name: main
-label: Main Menu
-type: sidebar
-app: demo_app
-
-items:
-  - name: core_business
-    label: Core Business
-    icon: briefcase
-    type: section
-    items:
-      - object: projects
-      - object: tasks
-
-  - name: showcase
-    label: Showcase
-    icon: flask
-    type: section
-    items:
-      - object: kitchen_sink
-        label: Component Gallery
-
-  - name: reporting
-    label: Reporting
-    icon: bar-chart
-    type: section
-    items:
-      - type: url
-        label: Dashboard
-        path: /dashboard
diff --git a/packages/starters/basic/src/modules/projects/pages/create_project_wizard.page.yml b/packages/starters/basic/src/modules/projects/pages/create_project_wizard.page.yml
deleted file mode 100644
index 01b1b988..00000000
--- a/packages/starters/basic/src/modules/projects/pages/create_project_wizard.page.yml
+++ /dev/null
@@ -1,244 +0,0 @@
-# Project Creation Wizard
-# A multi-step wizard for creating new projects
-
-name: create_project_wizard
-label: Create New Project
-description: Step-by-step wizard for creating a project
-icon: plus-circle
-layout: wizard
-
-# Only admins and managers can create projects
-permissions:
-  view: ['admin', 'manager']
-
-# Wizard steps
-components:
-  # Step 1: Basic Information
-  - id: step_basic
-    type: container
-    label: Basic Information
-    description: Enter the project name and description
-    config:
-      step: 1
-      icon: info
-    components:
-      - id: basic_form
-        type: form
-        config:
-          layout: vertical
-          fields:
-            - name: name
-              label: Project Name
-              type: text
-              required: true
-              placeholder: My Awesome Project
-              help_text: Choose a descriptive name for your project
-            - name: description
-              label: Project Description
-              type: textarea
-              rows: 5
-              placeholder: Describe what this project is about
-            - name: category
-              label: Category
-              type: select
-              options:
-                - label: Development
-                  value: development
-                - label: Marketing
-                  value: marketing
-                - label: Research
-                  value: research
-                - label: Operations
-                  value: operations
-        actions:
-          on_validate:
-            type: custom
-            handler: validateBasicInfo
-  
-  # Step 2: Team & Resources
-  - id: step_team
-    type: container
-    label: Team & Resources
-    description: Assign team members and set budget
-    config:
-      step: 2
-      icon: users
-    components:
-      - id: team_form
-        type: form
-        config:
-          layout: vertical
-          fields:
-            - name: owner
-              label: Project Manager
-              type: lookup
-              reference_to: users
-              required: true
-              help_text: Select the person responsible for this project
-            - name: team_members
-              label: Team Members
-              type: lookup
-              reference_to: users
-              multiple: true
-              help_text: Add team members who will work on this project
-            - name: budget
-              label: Budget
-              type: currency
-              currency: USD
-              help_text: Estimated budget for this project
-            - name: department
-              label: Department
-              type: select
-              options:
-                - label: Engineering
-                  value: engineering
-                - label: Product
-                  value: product
-                - label: Sales
-                  value: sales
-                - label: Marketing
-                  value: marketing
-  
-  # Step 3: Timeline
-  - id: step_timeline
-    type: container
-    label: Timeline
-    description: Set project dates and milestones
-    config:
-      step: 3
-      icon: calendar
-    components:
-      - id: timeline_form
-        type: form
-        config:
-          layout: vertical
-          fields:
-            - name: start_date
-              label: Start Date
-              type: date
-              required: true
-              defaultValue: '{{today}}'
-            - name: end_date
-              label: Target End Date
-              type: date
-              required: true
-              help_text: Expected completion date
-            - name: priority
-              label: Priority
-              type: select
-              required: true
-              options:
-                - label: Low
-                  value: low
-                - label: Medium
-                  value: medium
-                - label: High
-                  value: high
-                - label: Critical
-                  value: critical
-              defaultValue: medium
-            - name: milestones
-              label: Key Milestones
-              type: grid
-              help_text: Define important project milestones
-              config:
-                columns:
-                  - name: name
-                    label: Milestone
-                    type: text
-                  - name: date
-                    label: Target Date
-                    type: date
-                  - name: description
-                    label: Description
-                    type: text
-                allow_add: true
-                allow_delete: true
-  
-  # Step 4: Review & Create
-  - id: step_review
-    type: container
-    label: Review & Create
-    description: Review your project details before creating
-    config:
-      step: 4
-      icon: check-square
-    components:
-      - id: review_summary
-        type: detail_view
-        label: Project Summary
-        config:
-          mode: readonly
-          sections:
-            - label: Basic Information
-              fields: ['name', 'description', 'category']
-            - label: Team
-              fields: ['owner', 'team_members', 'budget', 'department']
-            - label: Timeline
-              fields: ['start_date', 'end_date', 'priority']
-      
-      - id: terms_checkbox
-        type: container
-        components:
-          - id: accept_terms
-            type: boolean
-            label: I confirm that all information is correct
-            required: true
-
-# Wizard navigation actions
-actions:
-  next_step:
-    type: custom
-    handler: validateAndProceed
-  
-  previous_step:
-    type: custom
-    handler: goToPreviousStep
-  
-  submit_wizard:
-    type: run_action
-    object: projects
-    action: create
-    success_message: Project created successfully!
-    on_error: show_modal
-  
-  save_draft:
-    type: custom
-    handler: saveDraft
-    success_message: Draft saved
-
-# Page state to track wizard progress
-state:
-  initial:
-    current_step: 1
-    completed_steps: []
-    form_data:
-      name: ''
-      description: ''
-      category: ''
-      owner: null
-      team_members: []
-      budget: 0
-      department: ''
-      start_date: null
-      end_date: null
-      priority: medium
-      milestones: []
-  persist: true
-  storage_key: project_wizard_draft
-
-# Page styling
-style:
-  max_width: 800px
-  margin: 0 auto
-  padding: 40px 20px
-
-# AI context
-ai_context:
-  intent: Guide users through project creation with validation
-  persona: Project managers and team leads
-  tasks:
-    - Create new projects step by step
-    - Validate input at each stage
-    - Review before submission
-    - Save drafts for later
diff --git a/packages/starters/basic/src/modules/projects/pages/project_detail.page.yml b/packages/starters/basic/src/modules/projects/pages/project_detail.page.yml
deleted file mode 100644
index 23fb9a28..00000000
--- a/packages/starters/basic/src/modules/projects/pages/project_detail.page.yml
+++ /dev/null
@@ -1,258 +0,0 @@
-# Project Detail Page
-# A page for viewing and editing project details with a clean layout
-
-name: project_detail
-label: Project Details
-description: View and edit project information
-icon: folder
-layout: two_column
-
-# Page permissions
-permissions:
-  view: ['admin', 'manager', 'user']
-  edit: ['admin', 'manager']
-
-# Sections-based layout for two-column design
-sections:
-  # Left Column - Main Content
-  - id: main_content
-    type: content
-    style:
-      width: 70%
-    components:
-      # Project Information Form
-      - id: project_form
-        type: form
-        label: Project Information
-        data_source:
-          object: projects
-          query:
-            op: findOne
-            filter: [['_id', '=', '{{route.params.id}}']]
-        config:
-          mode: edit  # view, edit, create
-          layout: vertical
-          fields:
-            - name: name
-              label: Project Name
-              type: text
-              required: true
-              placeholder: Enter project name
-            - name: description
-              label: Description
-              type: textarea
-              rows: 4
-            - name: status
-              label: Status
-              type: select
-              options:
-                - label: Planning
-                  value: planning
-                - label: Active
-                  value: active
-                - label: On Hold
-                  value: on_hold
-                - label: Completed
-                  value: completed
-            - name: owner
-              label: Project Manager
-              type: lookup
-              reference_to: users
-              display_field: name
-            - name: start_date
-              label: Start Date
-              type: date
-            - name: end_date
-              label: End Date
-              type: date
-            - name: budget
-              label: Budget
-              type: currency
-              currency: USD
-          field_layout:
-            - row: [name]
-            - row: [description]
-            - row: [status, owner]
-            - row: [start_date, end_date]
-            - row: [budget]
-        actions:
-          on_submit:
-            type: run_action
-            object: projects
-            action: update
-            success_message: Project updated successfully
-          on_cancel:
-            type: navigate
-            path: /projects
-        style:
-          margin: 0 0 24px 0
-      
-      # Tasks List
-      - id: project_tasks
-        type: data_grid
-        label: Tasks
-        data_source:
-          object: tasks
-          filters:
-            - ['project', '=', '{{route.params.id}}']
-          fields: ['name', 'status', 'priority', 'assigned_to', 'due_date']
-          sort: [['created_at', 'desc']]
-          expand:
-            assigned_to:
-              fields: ['name']
-        config:
-          columns:
-            - field: name
-              label: Task
-              width: 250
-            - field: status
-              label: Status
-              width: 120
-            - field: priority
-              label: Priority
-              width: 100
-            - field: assigned_to.name
-              label: Assigned To
-              width: 150
-            - field: due_date
-              label: Due Date
-              width: 120
-          toolbar_actions:
-            - label: New Task
-              icon: plus
-              action: create_task
-          row_actions:
-            - label: Edit
-              icon: edit
-              action: edit_task
-            - label: Delete
-              icon: trash
-              action: delete_task
-              confirm: Are you sure you want to delete this task?
-        actions:
-          on_load:
-            type: refresh
-
-  # Right Column - Sidebar
-  - id: sidebar
-    type: sidebar
-    style:
-      width: 30%
-      padding: 0 0 0 24px
-    components:
-      # Project Metrics
-      - id: project_stats
-        type: container
-        label: Project Statistics
-        components:
-          - id: task_count
-            type: metric
-            label: Total Tasks
-            data_source:
-              object: tasks
-              filters:
-                - ['project', '=', '{{route.params.id}}']
-              query:
-                op: count
-            config:
-              format: number
-              size: small
-          
-          - id: completed_tasks
-            type: metric
-            label: Completed
-            data_source:
-              object: tasks
-              filters:
-                - ['project', '=', '{{route.params.id}}']
-                - 'and'
-                - ['status', '=', 'completed']
-              query:
-                op: count
-            config:
-              format: number
-              size: small
-              color: green
-          
-          - id: progress
-            type: metric
-            label: Progress
-            config:
-              format: percent
-              value: '{{completed_tasks / task_count}}'
-              size: small
-      
-      # Activity Timeline
-      - id: activity_timeline
-        type: timeline
-        label: Recent Activity
-        data_source:
-          object: activities
-          filters:
-            - ['related_to', '=', '{{route.params.id}}']
-            - 'and'
-            - ['entity_type', '=', 'project']
-          fields: ['action', 'user', 'created_at', 'description']
-          sort: [['created_at', 'desc']]
-          limit: 10
-        config:
-          group_by: date
-          show_user_avatar: true
-      
-      # Quick Actions
-      - id: quick_actions
-        type: container
-        label: Quick Actions
-        components:
-          - id: archive_btn
-            type: button
-            label: Archive Project
-            config:
-              variant: outline
-              icon: archive
-            actions:
-              on_click:
-                type: run_action
-                object: projects
-                action: archive
-                confirm: Archive this project?
-                success_message: Project archived
-          
-          - id: export_btn
-            type: button
-            label: Export Data
-            config:
-              variant: outline
-              icon: download
-            actions:
-              on_click:
-                type: custom
-                handler: exportProjectData
-
-# Responsive configuration
-responsive:
-  mobile:
-    # Stack columns vertically on mobile
-    columns: 1
-  tablet:
-    columns: 1
-  desktop:
-    columns: 2
-
-# Page-level state
-state:
-  initial:
-    edit_mode: false
-  persist: true
-  storage_key: project_detail_state
-
-# AI context
-ai_context:
-  intent: View and manage individual project details with tasks and metrics
-  persona: Project managers and team members
-  tasks:
-    - View project information
-    - Update project details
-    - Manage tasks within the project
-    - Track project progress
-    - View activity history
diff --git a/packages/starters/basic/src/modules/projects/project_status.report.yml b/packages/starters/basic/src/modules/projects/project_status.report.yml
deleted file mode 100644
index 710056a6..00000000
--- a/packages/starters/basic/src/modules/projects/project_status.report.yml
+++ /dev/null
@@ -1,39 +0,0 @@
-name: project_status_summary
-label: "Project Status Report"
-type: summary
-object: projects
-description: "Overview of projects grouped by status and priority"
-
-# Columns to display in details
-columns:
-  - field: name
-    label: Project Name
-  - field: owner
-    label: Owner
-  - field: budget
-    label: Budget
-    format: currency
-
-# Grouping Configuration
-groupings:
-  - field: status
-    label: Status
-  
-  - field: priority
-    label: Priority
-
-# Aggregations
-aggregations:
-  - field: budget
-    function: sum
-    label: Total Budget
-  
-  - field: _id
-    function: count
-    label: Project Count
-
-# Default Filters
-filters:
-  - field: created_at
-    operator: ">="
-    value: "2024-01-01"
diff --git a/packages/starters/basic/src/modules/projects/projects.form.yml b/packages/starters/basic/src/modules/projects/projects.form.yml
deleted file mode 100644
index 0aa02062..00000000
--- a/packages/starters/basic/src/modules/projects/projects.form.yml
+++ /dev/null
@@ -1,41 +0,0 @@
-name: project_main_form
-label: "Project Details"
-type: edit
-object: projects
-description: "Main form for creating and editing projects"
-
-layout:
-  tabs:
-    - label: "General Info"
-      sections:
-        - label: "Basic Details"
-          columns: 2
-          fields:
-            - name
-            - owner
-            - status
-            - priority
-        
-        - label: "Description"
-          columns: 1
-          fields:
-            - description
-
-    - label: "Planning"
-      sections:
-        - label: "Schedule & Budget"
-          columns: 2
-          fields:
-            - start_date
-            - end_date
-            - budget
-
-    - label: "Approval Info"
-      sections:
-        - label: "Audit Trail"
-          fields:
-             - name: approved_by
-               readonly: true
-             - name: approved_at
-               readonly: true
-             - approval_comment
diff --git a/packages/starters/basic/src/modules/projects/projects.view.yml b/packages/starters/basic/src/modules/projects/projects.view.yml
deleted file mode 100644
index 51cb7681..00000000
--- a/packages/starters/basic/src/modules/projects/projects.view.yml
+++ /dev/null
@@ -1,35 +0,0 @@
-name: all_projects
-label: "Active Projects"
-type: list
-object: projects
-description: "Standard list view of all active projects"
-
-config:
-  columns:
-    - field: name
-      width: 250
-    - field: status
-      width: 120
-    - field: priority
-      width: 100
-    - field: owner
-      width: 150
-    - field: budget
-      width: 120
-    - field: end_date
-      width: 120
-
-  sort:
-    - field: created_at
-      direction: desc
-
-  filters:
-    - field: status
-      operator: "!="
-      value: "archived"
-
-  actions:
-    - edit
-    - delete
-    - clone
-    - custom: approve
diff --git a/packages/starters/basic/src/pages/dashboard.page.yml b/packages/starters/basic/src/pages/dashboard.page.yml
deleted file mode 100644
index 794d1074..00000000
--- a/packages/starters/basic/src/pages/dashboard.page.yml
+++ /dev/null
@@ -1,206 +0,0 @@
-# Dashboard Page Example
-# A comprehensive dashboard showing project metrics and tasks
-
-name: dashboard
-label: Project Dashboard
-description: Overview of projects, tasks, and key metrics
-icon: dashboard
-layout: dashboard
-
-# Page-level permissions
-permissions:
-  view: ['admin', 'manager', 'user']
-  edit: ['admin', 'manager']
-
-# SEO metadata
-meta:
-  title: Project Dashboard - ObjectQL Demo
-  description: Real-time overview of project status and team performance
-
-# Real-time updates
-realtime: true
-
-# Components arranged in a grid layout
-components:
-  # KPI Metrics Row
-  - id: total_projects
-    type: metric
-    label: Total Projects
-    data_source:
-      object: projects
-      query:
-        op: count
-    config:
-      format: number
-      icon: folder
-      color: blue
-    grid:
-      x: 0
-      y: 0
-      w: 3
-      h: 2
-    
-  - id: active_tasks
-    type: metric
-    label: Active Tasks
-    data_source:
-      object: tasks
-      filters:
-        - ['status', 'in', ['in_progress', 'pending']]
-      query:
-        op: count
-    config:
-      format: number
-      icon: check-circle
-      color: green
-    grid:
-      x: 3
-      y: 0
-      w: 3
-      h: 2
-    
-  - id: overdue_tasks
-    type: metric
-    label: Overdue Tasks
-    data_source:
-      object: tasks
-      filters:
-        - ['due_date', '<', '{{today}}']
-        - 'and'
-        - ['status', '!=', 'completed']
-      query:
-        op: count
-    config:
-      format: number
-      icon: alert-circle
-      color: red
-    grid:
-      x: 6
-      y: 0
-      w: 3
-      h: 2
-    
-  - id: completion_rate
-    type: metric
-    label: Completion Rate
-    data_source:
-      object: tasks
-      query:
-        op: aggregate
-        function: avg
-        field: completed
-    config:
-      format: percent
-      icon: trending-up
-      color: purple
-    grid:
-      x: 9
-      y: 0
-      w: 3
-      h: 2
-  
-  # Charts Row
-  - id: projects_by_status
-    type: chart
-    label: Projects by Status
-    data_source:
-      object: projects
-      fields: ['status']
-      query:
-        op: group_by
-        field: status
-        aggregate: count
-    config:
-      chart_type: pie
-      colors: ['#10b981', '#3b82f6', '#f59e0b', '#ef4444']
-    grid:
-      x: 0
-      y: 2
-      w: 6
-      h: 4
-    
-  - id: tasks_timeline
-    type: chart
-    label: Tasks Completion Timeline
-    data_source:
-      object: tasks
-      fields: ['created_at', 'completed_at']
-      query:
-        op: time_series
-        field: created_at
-        interval: week
-    config:
-      chart_type: line
-      show_trend: true
-    grid:
-      x: 6
-      y: 2
-      w: 6
-      h: 4
-  
-  # Recent Tasks List
-  - id: recent_tasks
-    type: data_grid
-    label: Recent Tasks
-    data_source:
-      object: tasks
-      fields: ['name', 'status', 'priority', 'due_date', 'assigned_to']
-      sort: [['created_at', 'desc']]
-      limit: 10
-      expand:
-        assigned_to:
-          fields: ['name', 'email']
-    config:
-      columns:
-        - field: name
-          label: Task Name
-          width: 300
-        - field: status
-          label: Status
-          width: 120
-          badge: true
-        - field: priority
-          label: Priority
-          width: 100
-        - field: due_date
-          label: Due Date
-          width: 120
-          format: date
-        - field: assigned_to.name
-          label: Assigned To
-          width: 150
-      row_actions:
-        - label: View
-          action: navigate
-          path: /tasks/{{id}}
-        - label: Edit
-          action: open_modal
-          modal: edit_task
-      enable_search: true
-      enable_filters: true
-    grid:
-      x: 0
-      y: 6
-      w: 12
-      h: 6
-
-# Page-level actions
-actions:
-  refresh_data:
-    type: refresh
-    success_message: Data refreshed successfully
-  
-  export_dashboard:
-    type: custom
-    handler: exportDashboardData
-    confirm: Export dashboard data to CSV?
-
-# AI context for understanding this page
-ai_context:
-  intent: Provide a comprehensive overview of project and task status
-  persona: Project managers and team leads
-  tasks:
-    - Monitor project progress
-    - Identify overdue tasks
-    - Track team performance
-    - Export data for reporting
diff --git a/packages/starters/basic/src/pages/landing.page.yml b/packages/starters/basic/src/pages/landing.page.yml
deleted file mode 100644
index c6047cb0..00000000
--- a/packages/starters/basic/src/pages/landing.page.yml
+++ /dev/null
@@ -1,275 +0,0 @@
-# Custom Landing Page
-# A canvas layout for flexible positioning
-
-name: landing_page
-label: Welcome
-description: Custom landing page with free-form layout
-icon: home
-layout: canvas
-
-# Public page - no authentication required
-permissions:
-  view: ['*']
-
-# Components with absolute positioning
-components:
-  # Hero Section
-  - id: hero_section
-    type: container
-    style:
-      position: absolute
-      top: 0
-      left: 0
-      width: 100%
-      height: 400px
-      background: linear-gradient(135deg, #667eea 0%, #764ba2 100%)
-      padding: 60px 20px
-    components:
-      - id: hero_title
-        type: text
-        config:
-          content: Welcome to ObjectQL
-          format: markdown
-        style:
-          font_size: 48px
-          font_weight: bold
-          color: white
-          text_align: center
-          margin: 0 0 20px 0
-      
-      - id: hero_subtitle
-        type: text
-        config:
-          content: One Protocol, Any Database, AI-Ready
-          format: text
-        style:
-          font_size: 24px
-          color: white
-          text_align: center
-          opacity: 0.9
-      
-      - id: cta_button
-        type: button
-        label: Get Started
-        config:
-          variant: primary
-          size: large
-        style:
-          margin: 40px auto 0
-          display: block
-          width: 200px
-        actions:
-          on_click:
-            type: navigate
-            path: /dashboard
-  
-  # Features Grid
-  - id: features_section
-    type: container
-    style:
-      position: absolute
-      top: 450px
-      left: 50%
-      transform: translateX(-50%)
-      width: 90%
-      max_width: 1200px
-    components:
-      - id: features_title
-        type: text
-        config:
-          content: '## Key Features'
-          format: markdown
-        style:
-          text_align: center
-          margin: 0 0 40px 0
-      
-      - id: features_grid
-        type: container
-        style:
-          display: grid
-          grid_template_columns: repeat(3, 1fr)
-          gap: 30px
-        components:
-          - id: feature_1
-            type: container
-            style:
-              padding: 30px
-              background: white
-              border_radius: 8px
-              box_shadow: 0 2px 8px rgba(0,0,0,0.1)
-            components:
-              - id: feature_1_icon
-                type: image
-                config:
-                  src: /icons/database.svg
-                  alt: Database
-                style:
-                  width: 64px
-                  height: 64px
-                  margin: 0 auto 20px
-              - id: feature_1_title
-                type: text
-                config:
-                  content: '**Universal Engine**'
-                  format: markdown
-                style:
-                  text_align: center
-                  margin: 0 0 10px 0
-              - id: feature_1_desc
-                type: text
-                config:
-                  content: Run on MongoDB or PostgreSQL with the same API
-                  format: text
-                style:
-                  text_align: center
-                  color: '#666'
-          
-          - id: feature_2
-            type: container
-            style:
-              padding: 30px
-              background: white
-              border_radius: 8px
-              box_shadow: 0 2px 8px rgba(0,0,0,0.1)
-            components:
-              - id: feature_2_icon
-                type: image
-                config:
-                  src: /icons/ai.svg
-                  alt: AI
-                style:
-                  width: 64px
-                  height: 64px
-                  margin: 0 auto 20px
-              - id: feature_2_title
-                type: text
-                config:
-                  content: '**AI-Native**'
-                  format: markdown
-                style:
-                  text_align: center
-                  margin: 0 0 10px 0
-              - id: feature_2_desc
-                type: text
-                config:
-                  content: JSON-based queries perfect for LLM integration
-                  format: text
-                style:
-                  text_align: center
-                  color: '#666'
-          
-          - id: feature_3
-            type: container
-            style:
-              padding: 30px
-              background: white
-              border_radius: 8px
-              box_shadow: 0 2px 8px rgba(0,0,0,0.1)
-            components:
-              - id: feature_3_icon
-                type: image
-                config:
-                  src: /icons/metadata.svg
-                  alt: Metadata
-                style:
-                  width: 64px
-                  height: 64px
-                  margin: 0 auto 20px
-              - id: feature_3_title
-                type: text
-                config:
-                  content: '**Metadata-Driven**'
-                  format: markdown
-                style:
-                  text_align: center
-                  margin: 0 0 10px 0
-              - id: feature_3_desc
-                type: text
-                config:
-                  content: Define schemas in YAML with built-in validation
-                  format: text
-                style:
-                  text_align: center
-                  color: '#666'
-  
-  # Stats Section
-  - id: stats_section
-    type: container
-    style:
-      position: absolute
-      top: 900px
-      left: 0
-      width: 100%
-      background: '#f7fafc'
-      padding: 60px 20px
-    components:
-      - id: stats_grid
-        type: container
-        style:
-          display: grid
-          grid_template_columns: repeat(4, 1fr)
-          gap: 40px
-          max_width: 1200px
-          margin: 0 auto
-        components:
-          - id: stat_1
-            type: metric
-            label: Objects Created
-            data_source:
-              object: objects
-              query:
-                op: count
-            config:
-              format: number
-              size: large
-              color: blue
-          
-          - id: stat_2
-            type: metric
-            label: Total Records
-            data_source:
-              object: records
-              query:
-                op: count
-            config:
-              format: number
-              size: large
-              color: green
-          
-          - id: stat_3
-            type: metric
-            label: API Calls Today
-            config:
-              value: 12453
-              format: number
-              size: large
-              color: purple
-          
-          - id: stat_4
-            type: metric
-            label: Uptime
-            config:
-              value: 99.9
-              format: percent
-              size: large
-              color: orange
-
-# Responsive overrides
-responsive:
-  mobile:
-    # Override grid layouts to single column
-    visible: true
-  tablet:
-    visible: true
-
-# No real-time updates needed for landing page
-realtime: false
-
-# AI context
-ai_context:
-  intent: Introduce users to ObjectQL and showcase key features
-  persona: New visitors and potential users
-  tasks:
-    - Learn about ObjectQL
-    - Understand key features
-    - Navigate to dashboard
diff --git a/packages/starters/enterprise/src/menus/erp.menu.yml b/packages/starters/enterprise/src/menus/erp.menu.yml
deleted file mode 100644
index 3c1a59cc..00000000
--- a/packages/starters/enterprise/src/menus/erp.menu.yml
+++ /dev/null
@@ -1,11 +0,0 @@
-name: erp_main
-label: ERP Main Menu
-app: erp
-type: sidebar
-items:
-  - name: projects
-    label: Projects
-    type: section
-    items:
-      - object: project_project
-      - object: project_task
diff --git a/packages/starters/express-api/src/test.view.yml b/packages/starters/express-api/src/test.view.yml
deleted file mode 100644
index 24798177..00000000
--- a/packages/starters/express-api/src/test.view.yml
+++ /dev/null
@@ -1,9 +0,0 @@
-name: test-view
-label: Test View
-description: A sample view for testing metadata loading
-query: select * from users
-fields:
-  - name: id
-    label: ID
-  - name: name
-    label: Name

From 0f004ec015934ee1a7b1b47476a73145ef881613 Mon Sep 17 00:00:00 2001
From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com>
Date: Thu, 15 Jan 2026 03:27:58 +0000
Subject: [PATCH 4/7] Changes before error encountered

Co-authored-by: huangyiirene <7665279+huangyiirene@users.noreply.github.com>
---
 docs/ai/cli-usage.md           |   6 +-
 docs/spec/index.md             |   8 --
 docs/spec/metadata-standard.md | 218 +--------------------------------
 3 files changed, 8 insertions(+), 224 deletions(-)

diff --git a/docs/ai/cli-usage.md b/docs/ai/cli-usage.md
index 74b84a9d..6a7eb08c 100644
--- a/docs/ai/cli-usage.md
+++ b/docs/ai/cli-usage.md
@@ -110,11 +110,9 @@ For a `complete` application, you get:
 1. **Metadata Files (YAML)**
    - `*.object.yml` - Data entities
    - `*.validation.yml` - Validation rules
-   - `*.form.yml` - Data entry forms
-   - `*.view.yml` - List views
-   - `*.page.yml` - UI pages
-   - `*.menu.yml` - Navigation
    - `*.permission.yml` - Access control
+   - `*.workflow.yml` - Automation
+   - `*.data.yml` - Seed data
 
 2. **TypeScript Implementation Files**
    - `*.action.ts` - Custom business operations
diff --git a/docs/spec/index.md b/docs/spec/index.md
index 950ef8b8..042e603c 100644
--- a/docs/spec/index.md
+++ b/docs/spec/index.md
@@ -18,14 +18,6 @@ This section contains the complete metadata specifications for the ObjectQL plat
 *   [**Actions (RPC)**](./action.md) - Custom server-side functions and APIs ✅
 *   [**Workflows & Processes**](./workflow.md) - Automated business processes and approval chains ⚠️ *Spec complete, implementation pending*
 
-### Presentation Layer
-*   [**Applications**](./app.md) - Application container and simple metadata ✅
-*   [**Pages**](./page.md) - Composable UI pages with layouts, components, and interactions ✅
-*   [**Menus & Navigation**](./menu.md) - Application structure and navigation hierarchy ✅
-*   [**Views & Layouts**](./view.md) - Data presentation configurations (list, grid, kanban, calendar) ⚠️ *Spec complete, implementation pending*
-*   [**Forms**](./form.md) - Data entry and editing interfaces ⚠️ *Spec complete, implementation pending*
-*   [**Reports & Dashboards**](./report.md) - Analytics and BI ⚠️ *Spec complete, implementation pending*
-
 ## Security & Access Control
 
 *   [**Permissions**](./permission.md) - Role-based access control, field-level security, and record-level rules ✅
diff --git a/docs/spec/metadata-standard.md b/docs/spec/metadata-standard.md
index 1666a105..65abec8c 100644
--- a/docs/spec/metadata-standard.md
+++ b/docs/spec/metadata-standard.md
@@ -14,8 +14,6 @@ In ObjectQL, **metadata** is machine-readable configuration that describes:
 2. **How to validate it** (Validation Rules, Constraints)
 3. **Who can access it** (Permissions, Security)
 4. **What business logic to execute** (Hooks, Actions, Workflows)
-5. **How to present it** (Pages, Views, Forms, Reports)
-6. **How to navigate it** (Menus, Dashboards)
 
 ## Complete Metadata Taxonomy
 
@@ -200,179 +198,7 @@ steps:
       field: manager_id
 ```
 
-### 3. Presentation Layer
-
-#### [Pages](./page.md)
-**Purpose**: Define composable UI pages with layouts, components, and interactions.
-
-**What you define**:
-- Page layouts (dashboard, wizard, canvas, two-column)
-- UI components (data grids, forms, charts, metrics)
-- Data source bindings
-- Component actions (navigate, submit, open modal)
-- Responsive configurations
-- Page-level permissions and state
-- AI context for page understanding
-
-**Example**:
-```yaml
-name: dashboard
-label: Project Dashboard
-layout: dashboard
-
-components:
-  - id: total_projects
-    type: metric
-    label: Total Projects
-    data_source:
-      object: projects
-      query: { op: count }
-    grid: { x: 0, y: 0, w: 3, h: 2 }
-  
-  - id: tasks_grid
-    type: data_grid
-    data_source:
-      object: tasks
-      fields: [name, status, due_date]
-      sort: [[created_at, desc]]
-    grid: { x: 0, y: 2, w: 12, h: 6 }
-```
-
-#### [Views & Layouts](./view.md)
-**Purpose**: Define how data is displayed to users.
-
-**What you define**:
-- List views (tabular data)
-- Grid views (inline editing)
-- Kanban boards (drag & drop)
-- Calendar views (events, timeline)
-- Card layouts (mobile-friendly)
-- Column configurations
-- Default filters and sorting
-
-**Example** (`task_list.view.yml`):
-```yaml
-# File: task_list.view.yml
-# View name is inferred from filename!
-
-type: list
-object: tasks  # Still specify which object to display
-config:
-  columns:
-    - field: name
-      width: 300
-      sortable: true
-    - field: status
-      renderer: badge
-  default_filters:
-    - field: status
-      operator: "!="
-      value: completed
-```
-
-#### [Forms](./form.md)
-**Purpose**: Define data entry and editing interfaces.
-
-**What you define**:
-- Form layouts (sections, tabs, columns)
-- Field configurations (labels, help text, defaults)
-- Conditional logic (show/hide based on values)
-- Validation rules
-- Wizard forms (multi-step)
-- Quick create forms
-
-**Example** (`project_form.form.yml`):
-```yaml
-# File: project_form.form.yml
-# Form name is inferred from filename!
-
-type: edit
-object: projects
-layout:
-  sections:
-    - name: basic_info
-      label: Basic Information
-      columns: 2
-      fields:
-        - name
-        - status
-        - owner
-conditional_logic:
-  - condition:
-      field: status
-      operator: "="
-      value: completed
-    actions:
-      - show_fields: [completion_date]
-```
-
-#### [Reports & Dashboards](./report.md)
-**Purpose**: Analytics, visualization, and business intelligence.
-
-**What you define**:
-- Tabular reports (data lists)
-- Summary reports (grouped with totals)
-- Matrix reports (pivot tables)
-- Charts (bar, line, pie, etc.)
-- Dashboards (KPIs, charts, metrics)
-- Scheduled reports
-- Export formats
-
-**Example** (`sales_by_region.report.yml`):
-```yaml
-# File: sales_by_region.report.yml
-# Report name is inferred from filename!
-
-type: summary
-object: orders
-groupings:
-  - field: customer.region
-    label: Region
-aggregations:
-  - function: sum
-    field: amount
-    label: Total Sales
-  - function: count
-    field: id
-    label: Order Count
-chart:
-  enabled: true
-  type: bar
-```
-
-#### [Menus & Navigation](./menu.md)
-**Purpose**: Define application structure and navigation.
-
-**What you define**:
-- Menu hierarchies
-- Navigation items
-- Quick actions
-- Breadcrumbs
-- Favorites
-- Search integration
-- Role-based menu visibility
-
-**Example** (`sales_crm.app.yml`):
-```yaml
-name: main_navigation
-type: sidebar
-items:
-  - name: sales
-    label: Sales
-    icon: currency
-    type: section
-    items:
-      - name: leads
-        label: Leads
-        path: /sales/leads
-        object: leads
-      - name: opportunities
-        label: Opportunities
-        path: /sales/opportunities
-        object: opportunities
-```
-
-### 4. Security & Access Control
+### 3. Security & Access Control
 
 #### [Permissions](./permission.md)
 **Purpose**: Control who can access what data and operations.
@@ -451,21 +277,6 @@ src/
   workflows/                 # Business processes
     order_approval.workflow.yml
     customer_onboarding.workflow.yml
-  
-  views/                     # Presentation
-    customer_list.view.yml
-    customer_kanban.view.yml
-  
-  forms/                     # Data entry
-    customer_form.form.yml
-    quick_customer.form.yml
-  
-  reports/                   # Analytics
-    sales_summary.report.yml
-    sales_dashboard.dashboard.yml
-  
-  navigation/                # App structure
-    main_menu.menu.yml
 ```
 
 ## Development Workflow
@@ -481,19 +292,13 @@ src/
 2. Create custom actions
 3. Design workflows and approvals
 
-### 3. UI Phase
-1. Design views for different contexts
-2. Create forms for data entry
-3. Build reports and dashboards
-4. Configure navigation menus
-
-### 4. Testing Phase
+### 3. Testing Phase
 1. Test with different user roles
 2. Validate business rules
 3. Check permission enforcement
 4. Performance testing
 
-### 5. Deployment
+### 4. Deployment
 1. Commit metadata to Git
 2. Deploy to ObjectOS runtime
 3. Monitor and iterate
@@ -511,10 +316,7 @@ ObjectQL provides a universal loader and generic API for all metadata types.
 | Type | Extension | Identifier Source | Example |
 |---|---|---|---|
 | Object | `*.object.yml` | Filename = Object name | `project.object.yml` → object: `project` |
-| View | `*.view.yml` | Filename = View name | `task_list.view.yml` → view: `task_list` |
-| Form | `*.form.yml` | Filename = Form name | `project_form.form.yml` → form: `project_form` |
 | Application | `*.app.yml` | Filename = App name | `crm.app.yml` → app: `crm` |
-| Report | `*.report.yml` | Filename = Report name | `sales_summary.report.yml` → report: `sales_summary` |
 | Workflow | `*.workflow.yml` | Filename = Workflow name | `approval.workflow.yml` → workflow: `approval` |
 | Permission | `*.permission.yml` | Filename = Object name | `project.permission.yml` → applies to: `project` |
 | Validation | `*.validation.yml` | Filename = Object name | `project.validation.yml` → applies to: `project` |
@@ -530,9 +332,9 @@ ObjectQL provides a universal loader and generic API for all metadata types.
 All metadata types can be queried via the REST API:
 
 - `GET /api/metadata/:type`
-  - List all entries for a specific type (e.g. `/api/metadata/view`)
+  - List all entries for a specific type (e.g. `/api/metadata/object`)
 - `GET /api/metadata/:type/:id`
-  - Get the JSON content of a specific entry (e.g. `/api/metadata/view/task_list`)
+  - Get the JSON content of a specific entry (e.g. `/api/metadata/object/customer`)
 - `POST /api/metadata/:type/:id`
   - Update metadata content (if supported by storage)
 
@@ -566,17 +368,9 @@ function CustomerList() {
 fields:
   name: { type: text }
   email: { type: email }
-
-# customer_list.view.yml
-# View name comes from filename!
-type: list
-object: customer
-columns:
-  - name
-  - email
 ```
 
-**Result**: ObjectOS automatically generates API, UI, validation, and security - all from metadata!
+**Result**: ObjectOS automatically generates API, validation, and security - all from metadata!
 
 ## Benefits
 

From ecd12c5cd3686236111a2d9a4fa5c2beb2ac5d62 Mon Sep 17 00:00:00 2001
From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com>
Date: Thu, 15 Jan 2026 03:34:27 +0000
Subject: [PATCH 5/7] Clean up remaining UI metadata references in
 documentation and tests

Co-authored-by: hotlong <50353452+hotlong@users.noreply.github.com>
---
 docs/spec/app.md                              |  12 +-
 docs/spec/index.md                            |  20 +--
 .../test/fixtures/test_dashboard.page.yml     |  42 ------
 .../test/fixtures/test_page.page.yml          |  54 -------
 .../test/fixtures/test_responsive.page.yml    |  39 -----
 .../test/fixtures/test_sections.page.yml      |  45 ------
 .../platform-node/test/page.test.ts           | 137 ------------------
 .../__tests__/metadata-loading.test.ts        |  11 --
 8 files changed, 7 insertions(+), 353 deletions(-)
 delete mode 100644 packages/foundation/platform-node/test/fixtures/test_dashboard.page.yml
 delete mode 100644 packages/foundation/platform-node/test/fixtures/test_page.page.yml
 delete mode 100644 packages/foundation/platform-node/test/fixtures/test_responsive.page.yml
 delete mode 100644 packages/foundation/platform-node/test/fixtures/test_sections.page.yml
 delete mode 100644 packages/foundation/platform-node/test/page.test.ts

diff --git a/docs/spec/app.md b/docs/spec/app.md
index c3e5084a..66869ab0 100644
--- a/docs/spec/app.md
+++ b/docs/spec/app.md
@@ -38,11 +38,9 @@ is_active: true
 | `sort_no` | number | No | Integer for sorting applications in the launcher. |
 | `is_active` | boolean | No | Whether the app is visible to users. Defaults to `true`. |
 
-## 4. Relationship with Menus
+## 4. Application Usage
 
-Menus are defined separately in `*.menu.yml` files and can be linked to an application. This separation allows for:
-- Reusing menus across applications.
-- Keeping the application definition lightweight.
-- Frontend plugins to dynamically inject or modify menus without touching the app definition.
-
-See [Menu Metadata](./menu.md) for details on defining structure and items.
+Application metadata serves as a container for grouping related functionality. The application definition is intentionally kept simple and lightweight to allow for:
+- Organizing related objects, workflows, and actions
+- Defining application-level configuration
+- Frontend plugins to dynamically integrate with the application without modifying core definitions
diff --git a/docs/spec/index.md b/docs/spec/index.md
index 042e603c..be898db5 100644
--- a/docs/spec/index.md
+++ b/docs/spec/index.md
@@ -52,29 +52,13 @@ src/
   workflows/           # Business processes
     *.workflow.yml     # Workflow definitions
   
-  pages/              # UI pages
-    *.page.yml         # Page definitions
-  
-  views/              # UI presentation
-    *.view.yml         # View configurations
-    *.form.yml         # Form layouts
-  
-  reports/            # Analytics
-    *.report.yml       # Report definitions
-    *.dashboard.yml    # Dashboard configurations
-
   data/               # Initial Seeding
     *.data.yml         # Seed data
-  
-  navigation/         # App structure
-    *.menu.yml         # Menu definitions
 ```
 
 ## Getting Started
 
 1. **Start with Objects**: Define your data model using [Objects & Fields](./object.md)
 2. **Add Business Logic**: Implement validation, hooks, and actions
-3. **Design UI**: Create views, forms, and navigation
-4. **Secure Your App**: Configure permissions and access rules
-5. **Build Workflows**: Automate processes and approvals
-6. **Create Reports**: Add analytics and dashboards
+3. **Secure Your App**: Configure permissions and access rules
+4. **Build Workflows**: Automate processes and approvals
diff --git a/packages/foundation/platform-node/test/fixtures/test_dashboard.page.yml b/packages/foundation/platform-node/test/fixtures/test_dashboard.page.yml
deleted file mode 100644
index 5d3ec901..00000000
--- a/packages/foundation/platform-node/test/fixtures/test_dashboard.page.yml
+++ /dev/null
@@ -1,42 +0,0 @@
-# Test Dashboard Page
-name: test_dashboard
-label: Test Dashboard
-description: Dashboard layout test
-icon: dashboard
-layout: dashboard
-
-components:
-  # Metric with grid positioning
-  - id: metric_1
-    type: metric
-    label: Total Count
-    data_source:
-      object: projects
-      query:
-        op: count
-    config:
-      format: number
-      color: blue
-    grid:
-      x: 0
-      y: 0
-      w: 3
-      h: 2
-  
-  # Chart with grid positioning
-  - id: chart_1
-    type: chart
-    label: Projects by Status
-    data_source:
-      object: projects
-      fields: ['status']
-    config:
-      chart_type: bar
-    grid:
-      x: 3
-      y: 0
-      w: 6
-      h: 4
-
-permissions:
-  view: ['admin', 'manager']
diff --git a/packages/foundation/platform-node/test/fixtures/test_page.page.yml b/packages/foundation/platform-node/test/fixtures/test_page.page.yml
deleted file mode 100644
index c38b4b27..00000000
--- a/packages/foundation/platform-node/test/fixtures/test_page.page.yml
+++ /dev/null
@@ -1,54 +0,0 @@
-# Test Page - Simple Single Column Layout
-name: test_page
-label: Test Page
-description: A test page for unit tests
-icon: test-tube
-layout: single_column
-
-# Permissions
-permissions:
-  view: ['admin', 'user']
-  edit: ['admin']
-
-# Simple components
-components:
-  - id: header_text
-    type: text
-    label: Welcome
-    config:
-      content: Welcome to the test page
-      format: text
-  
-  - id: test_grid
-    type: data_grid
-    label: Test Data
-    data_source:
-      object: projects
-      fields: ['name', 'status']
-      sort: [['created_at', 'desc']]
-      limit: 10
-    config:
-      columns:
-        - field: name
-          label: Project Name
-        - field: status
-          label: Status
-    actions:
-      on_click:
-        type: navigate
-        path: /projects/{{id}}
-  
-  - id: action_button
-    type: button
-    label: Click Me
-    actions:
-      on_click:
-        type: run_action
-        object: projects
-        action: custom_action
-        success_message: Action completed
-
-# AI context
-ai_context:
-  intent: Test page for unit testing
-  persona: Test users
diff --git a/packages/foundation/platform-node/test/fixtures/test_responsive.page.yml b/packages/foundation/platform-node/test/fixtures/test_responsive.page.yml
deleted file mode 100644
index 3558df6d..00000000
--- a/packages/foundation/platform-node/test/fixtures/test_responsive.page.yml
+++ /dev/null
@@ -1,39 +0,0 @@
-# Test Responsive Page
-name: test_responsive
-label: Test Responsive
-description: Page with responsive configuration
-icon: mobile
-layout: single_column
-
-# Responsive breakpoints
-responsive:
-  mobile:
-    columns: 1
-    visible: true
-  tablet:
-    columns: 2
-    visible: true
-  desktop:
-    columns: 3
-    visible: true
-
-components:
-  - id: responsive_grid
-    type: data_grid
-    label: Responsive Grid
-    data_source:
-      object: projects
-      fields: ['name']
-    responsive:
-      mobile:
-        visible: true
-        columns: 1
-      tablet:
-        visible: true
-        columns: 2
-      desktop:
-        visible: true
-        columns: 3
-
-permissions:
-  view: ['*']
diff --git a/packages/foundation/platform-node/test/fixtures/test_sections.page.yml b/packages/foundation/platform-node/test/fixtures/test_sections.page.yml
deleted file mode 100644
index 815c774a..00000000
--- a/packages/foundation/platform-node/test/fixtures/test_sections.page.yml
+++ /dev/null
@@ -1,45 +0,0 @@
-# Test Sections Page
-name: test_sections
-label: Test Sections
-description: Two-column layout with sections
-icon: layout
-layout: two_column
-
-sections:
-  # Main content section
-  - id: main_section
-    type: content
-    label: Main Content
-    style:
-      width: 70%
-    components:
-      - id: content_form
-        type: form
-        label: Edit Form
-        data_source:
-          object: projects
-        config:
-          mode: edit
-          fields:
-            - name: name
-              label: Name
-              type: text
-            - name: description
-              label: Description
-              type: textarea
-  
-  # Sidebar section
-  - id: sidebar_section
-    type: sidebar
-    label: Sidebar
-    style:
-      width: 30%
-    components:
-      - id: stats
-        type: metric
-        label: Statistics
-        config:
-          format: number
-
-permissions:
-  view: ['admin']
diff --git a/packages/foundation/platform-node/test/page.test.ts b/packages/foundation/platform-node/test/page.test.ts
deleted file mode 100644
index 392cc41b..00000000
--- a/packages/foundation/platform-node/test/page.test.ts
+++ /dev/null
@@ -1,137 +0,0 @@
-import { ObjectLoader } from '../src/loader';
-import { MetadataRegistry } from '@objectql/types';
-import * as path from 'path';
-import * as fs from 'fs';
-
-describe('Page Metadata Loader', () => {
-    let registry: MetadataRegistry;
-    let loader: ObjectLoader;
-
-    beforeEach(() => {
-        registry = new MetadataRegistry();
-        loader = new ObjectLoader(registry);
-    });
-
-    it('should load page from .page.yml file', () => {
-        const fixturesDir = path.join(__dirname, 'fixtures');
-        loader.load(fixturesDir);
-        
-        const pages = registry.list('page');
-        expect(pages.length).toBeGreaterThan(0);
-    });
-
-    it('should parse page metadata correctly', () => {
-        const fixturesDir = path.join(__dirname, 'fixtures');
-        loader.load(fixturesDir);
-        
-        const page = registry.get('page', 'test_page');
-        expect(page).toBeDefined();
-        expect(page.label).toBe('Test Page');
-        expect(page.layout).toBe('single_column');
-        expect(page.components).toBeDefined();
-        expect(Array.isArray(page.components)).toBe(true);
-    });
-
-    it('should load page with dashboard layout', () => {
-        const fixturesDir = path.join(__dirname, 'fixtures');
-        loader.load(fixturesDir);
-        
-        const page = registry.get('page', 'test_dashboard');
-        expect(page).toBeDefined();
-        expect(page.layout).toBe('dashboard');
-        expect(page.components).toBeDefined();
-        
-        // Check if components have grid positions
-        const componentWithGrid = page.components?.find((c: any) => c.grid);
-        expect(componentWithGrid).toBeDefined();
-        if (componentWithGrid && componentWithGrid.grid) {
-            expect(componentWithGrid.grid.x).toBeDefined();
-            expect(componentWithGrid.grid.y).toBeDefined();
-            expect(componentWithGrid.grid.w).toBeDefined();
-            expect(componentWithGrid.grid.h).toBeDefined();
-        }
-    });
-
-    it('should load page with sections', () => {
-        const fixturesDir = path.join(__dirname, 'fixtures');
-        loader.load(fixturesDir);
-        
-        const page = registry.get('page', 'test_sections');
-        expect(page).toBeDefined();
-        expect(page.sections).toBeDefined();
-        expect(Array.isArray(page.sections)).toBe(true);
-        
-        if (page.sections && page.sections.length > 0) {
-            const section = page.sections[0];
-            expect(section.id).toBeDefined();
-            expect(section.components).toBeDefined();
-        }
-    });
-
-    it('should support page permissions', () => {
-        const fixturesDir = path.join(__dirname, 'fixtures');
-        loader.load(fixturesDir);
-        
-        const page = registry.get('page', 'test_page');
-        expect(page).toBeDefined();
-        expect(page.permissions).toBeDefined();
-        expect(page.permissions.view).toBeDefined();
-        expect(Array.isArray(page.permissions.view)).toBe(true);
-    });
-
-    it('should support component actions', () => {
-        const fixturesDir = path.join(__dirname, 'fixtures');
-        loader.load(fixturesDir);
-        
-        const page = registry.get('page', 'test_page');
-        expect(page).toBeDefined();
-        
-        const componentWithAction = page.components?.find((c: any) => c.actions);
-        expect(componentWithAction).toBeDefined();
-        if (componentWithAction && componentWithAction.actions) {
-            expect(componentWithAction.actions.on_click).toBeDefined();
-        }
-    });
-
-    it('should support data source configuration', () => {
-        const fixturesDir = path.join(__dirname, 'fixtures');
-        loader.load(fixturesDir);
-        
-        const page = registry.get('page', 'test_page');
-        expect(page).toBeDefined();
-        
-        const componentWithDataSource = page.components?.find((c: any) => c.data_source);
-        expect(componentWithDataSource).toBeDefined();
-        if (componentWithDataSource && componentWithDataSource.data_source) {
-            expect(componentWithDataSource.data_source.object).toBeDefined();
-        }
-    });
-
-    it('should support responsive configuration', () => {
-        const fixturesDir = path.join(__dirname, 'fixtures');
-        loader.load(fixturesDir);
-        
-        const page = registry.get('page', 'test_responsive');
-        expect(page).toBeDefined();
-        expect(page.responsive).toBeDefined();
-        
-        if (page.responsive) {
-            expect(page.responsive.mobile).toBeDefined();
-            expect(page.responsive.tablet).toBeDefined();
-            expect(page.responsive.desktop).toBeDefined();
-        }
-    });
-
-    it('should support AI context', () => {
-        const fixturesDir = path.join(__dirname, 'fixtures');
-        loader.load(fixturesDir);
-        
-        const page = registry.get('page', 'test_page');
-        expect(page).toBeDefined();
-        expect(page.ai_context).toBeDefined();
-        
-        if (page.ai_context) {
-            expect(page.ai_context.intent).toBeDefined();
-        }
-    });
-});
diff --git a/packages/starters/express-api/__tests__/metadata-loading.test.ts b/packages/starters/express-api/__tests__/metadata-loading.test.ts
index 58f5d470..7887b8e5 100644
--- a/packages/starters/express-api/__tests__/metadata-loading.test.ts
+++ b/packages/starters/express-api/__tests__/metadata-loading.test.ts
@@ -133,15 +133,4 @@ describe('Metadata Loading', () => {
             expect(userMetadata.name).toBe('user');
         });
     });
-
-    describe('View Metadata', () => {
-        it('should load view metadata if present', () => {
-            const views = app.metadata.list('view');
-            
-            // The express-api starter has test.view.yml
-            if (views && views.length > 0) {
-                expect(views.length).toBeGreaterThanOrEqual(1);
-            }
-        });
-    });
 });

From aaaf0fc50f29903fa689006124f8fc4dfbd112b2 Mon Sep 17 00:00:00 2001
From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com>
Date: Thu, 15 Jan 2026 03:44:46 +0000
Subject: [PATCH 6/7] Restore docs/guide directory (server-side documentation)

Co-authored-by: hotlong <50353452+hotlong@users.noreply.github.com>
---
 docs/guide/architecture/overview.md           |  34 +
 docs/guide/architecture/why-objectql.md       |  54 ++
 docs/guide/cli.md                             | 258 +++++++
 docs/guide/configuration.md                   |  44 ++
 docs/guide/data-modeling.md                   | 154 ++++
 docs/guide/drivers/extensibility.md           | 178 +++++
 .../drivers/implementing-custom-driver.md     | 552 ++++++++++++++
 docs/guide/drivers/index.md                   |  62 ++
 docs/guide/drivers/mongo.md                   | 154 ++++
 docs/guide/drivers/sql.md                     | 127 ++++
 docs/guide/formulas-and-rules-quick-ref.md    | 275 +++++++
 docs/guide/formulas-and-rules.md              | 690 ++++++++++++++++++
 docs/guide/getting-started.md                 | 158 ++++
 docs/guide/ide-setup.md                       |  24 +
 docs/guide/index.md                           |  69 ++
 docs/guide/license.md                         |  64 ++
 docs/guide/logic-actions.md                   | 199 +++++
 docs/guide/logic-hooks.md                     | 184 +++++
 docs/guide/metadata-organization.md           | 365 +++++++++
 docs/guide/microservices.md                   |  61 ++
 docs/guide/migration-id-field.md              | 294 ++++++++
 docs/guide/plugins.md                         | 249 +++++++
 docs/guide/querying.md                        | 195 +++++
 docs/guide/server-integration.md              | 114 +++
 24 files changed, 4558 insertions(+)
 create mode 100644 docs/guide/architecture/overview.md
 create mode 100644 docs/guide/architecture/why-objectql.md
 create mode 100644 docs/guide/cli.md
 create mode 100644 docs/guide/configuration.md
 create mode 100644 docs/guide/data-modeling.md
 create mode 100644 docs/guide/drivers/extensibility.md
 create mode 100644 docs/guide/drivers/implementing-custom-driver.md
 create mode 100644 docs/guide/drivers/index.md
 create mode 100644 docs/guide/drivers/mongo.md
 create mode 100644 docs/guide/drivers/sql.md
 create mode 100644 docs/guide/formulas-and-rules-quick-ref.md
 create mode 100644 docs/guide/formulas-and-rules.md
 create mode 100644 docs/guide/getting-started.md
 create mode 100644 docs/guide/ide-setup.md
 create mode 100644 docs/guide/index.md
 create mode 100644 docs/guide/license.md
 create mode 100644 docs/guide/logic-actions.md
 create mode 100644 docs/guide/logic-hooks.md
 create mode 100644 docs/guide/metadata-organization.md
 create mode 100644 docs/guide/microservices.md
 create mode 100644 docs/guide/migration-id-field.md
 create mode 100644 docs/guide/plugins.md
 create mode 100644 docs/guide/querying.md
 create mode 100644 docs/guide/server-integration.md

diff --git a/docs/guide/architecture/overview.md b/docs/guide/architecture/overview.md
new file mode 100644
index 00000000..c6d750a8
--- /dev/null
+++ b/docs/guide/architecture/overview.md
@@ -0,0 +1,34 @@
+# Architecture & Concepts
+
+ObjectQL is built with a modular architecture that separates the data definition (Metadata) from the execution engine (Driver). This design allows applications to run on different database stacks (SQL vs NoSQL) without changing the business logic.
+
+## High-Level Overview
+
+An ObjectQL application consists of three main layers:
+
+1.  **Metadata Layer**: JSON/YAML files that define the shape of your data (`.object.yml`) and operations.
+2.  **Core Engine**: The `ObjectQL` class that loads metadata, validates requests, and orchestrates execution.
+3.  **Driver Layer**: Adapters that translate ObjectQL requests into database-specific queries (SQL, Mongo Protocol, etc.).
+
+## Dependency Graph
+
+The project is structured as a monorepo with strict dependency rules to ensure scalability and maintainability.
+
+*   **`@objectql/types`**: The shared contract. Contains all interfaces (`ObjectConfig`, `ObjectQLDriver`). Has **zero dependencies**.
+*   **`@objectql/core`**: The main runtime. It depends on `types`.
+*   **`@objectql/driver-*`**: Database adapters. They implement interfaces from `types` but do **not** depend on `core` (avoiding circular dependencies).
+
+## Core Concepts
+
+### 1. Metadata-First
+In traditional ORMs (like TypeORM or Prisma), you define classes/schema in code. In ObjectQL, the schema is data itself. This allows:
+*   Dynamic schema generation at runtime.
+*   Building "No-Code" table designers.
+*   Hot-reloading of data structure without recompiling.
+
+### 2. Universal Protocol
+ObjectQL uses a unified JSON-based query language (AST). This allows frontends, AI agents, or external systems to send complex queries (`filters`, `expand`, `aggregates`) in a safe, serializable format.
+
+### 3. Logic: Actions & Hooks
+*   **Hooks**: Intercept standard CRUD operations (e.g., "Before Create", "After Update") to enforce business rules.
+*   **Actions**: Define custom RPC methods (e.g., "Approve Invoice") exposed via the API.
diff --git a/docs/guide/architecture/why-objectql.md b/docs/guide/architecture/why-objectql.md
new file mode 100644
index 00000000..d6af4b7a
--- /dev/null
+++ b/docs/guide/architecture/why-objectql.md
@@ -0,0 +1,54 @@
+# Why ObjectQL?
+
+In the era of AI automation, the requirements for backend infrastructure have shifted. We are no longer just building for human users on web forms; we are building systems that **AI Agents** need to read, understand, and manipulate.
+
+## The Problem with Traditional ORMs
+
+Tools like TypeORM, Prisma, or Sequelize are fantastic for human developers. They rely heavily on:
+1.  **Complex TypeScript Types**: Great for IDE autocomplete, but invisible to an LLM running in a production execution environment.
+2.  **Chained Method Calls**: `db.users.where(...).include(...)`. This requires the AI to synthesize valid executable code, which is prone to syntax errors and hallucinations.
+3.  **Code-First Schema**: The schema is buried in class definitions, making it hard to extract a simple "map" of the data for the AI context window.
+
+## The ObjectQL Solution: Protocol-First
+
+ObjectQL treats **Logic as Data**.
+
+### 1. Schema is JSON (The Context)
+Instead of parsing TypeScript files, an AI Agent can simply read a JSON definition. This is the native tongue of LLMs.
+
+```json
+{
+  "name": "contact",
+  "fields": { "email": { "type": "text", "required": true } }
+}
+```
+
+This compact format fits perfectly in RAG (Retrieval-Augmented Generation) contexts.
+
+### 2. Queries are ASTs (The Action)
+To fetch data, the AI doesn't need to write SQL or function code. It generates a JSON object (Abstract Syntax Tree).
+
+```json
+{
+  "op": "find",
+  "from": "contact",
+  "filters": [["email", "contains", "@gmail.com"]]
+}
+```
+*   **Safe**: No SQL Injection possible. The Driver handles escaping.
+*   **Deterministic**: It either parses or it fails. No subtle logic bugs from misplaced parentheses in code.
+*   **Portability**: The same JSON runs on Mongo, Postgres, or a REST API.
+
+## Comparison
+
+| Feature | Traditional ORM | ObjectQL |
+| :--- | :--- | :--- |
+| **Schema Definition** | TypeScript Classes / Migration Files | JSON / YAML Metadata |
+| **Query Language** | Fluent API / Raw SQL | JSON AST |
+| **Runtime** | Node.js / Python Runtime | Universal Protocol (Any Language) |
+| **AI Friendliness** | Low (Requires Code Gen) | High (Requires JSON Gen) |
+| **Dynamic Fields** | Hard (Migration required) | Native (Metadata-driven) |
+
+## Conclusion
+
+If you are building a Copilot, an Autonomous Agent, or a Low-Code platform, ObjectQL provides the structured, safe, and descriptive layer that connects your LLM to your database.
diff --git a/docs/guide/cli.md b/docs/guide/cli.md
new file mode 100644
index 00000000..b5f13237
--- /dev/null
+++ b/docs/guide/cli.md
@@ -0,0 +1,258 @@
+# CLI Guide
+
+The ObjectQL CLI (`@objectql/cli`) is an essential tool for development, automating tasks like type generation and database migrations.
+
+## 1. Installation
+
+The CLI is typically installed as a dev dependency in your project.
+
+```bash
+npm install -D @objectql/cli
+```
+
+You can then run it via `npx objectql` or add scripts to your `package.json`.
+
+## 2. Core Commands
+
+### 2.1 `init` (Create Project)
+
+Create a new ObjectQL project from a starter template.
+
+```bash
+npx objectql init [options]
+```
+
+**Options:**
+
+| Option | Alias | Default | Description |
+| :--- | :--- | :--- | :--- |
+| `--template <template>` | `-t` | `basic` | Template to use (`basic`, `express-api`, `enterprise`). |
+| `--name <name>` | `-n` | - | Project name. |
+| `--dir <path>` | `-d` | - | Target directory. |
+| `--skip-install` | | `false` | Skip dependency installation. |
+| `--skip-git` | | `false` | Skip git initialization. |
+
+**Example:**
+
+```bash
+npx objectql init -t express-api -n my-app
+```
+
+### 2.2 `generate` (Type Generation)
+
+Scans your `*.object.yml` files and generates TypeScript interfaces. This is crucial for maintaining type safety in your Hooks and Actions.
+**Alias**: `g`
+
+```bash
+npx objectql generate [options]
+```
+
+**Options:**
+
+| Option | Alias | Default | Description |
+| :--- | :--- | :--- | :--- |
+| `--source <path>` | `-s` | `.` | Root directory to search for object files. |
+| `--output <path>` | `-o` | `./src/generated` | Directory where `.ts` files will be generated. |
+
+**Example:**
+
+```bash
+# Generate types from /src/objects to /src/types
+npx objectql generate --source ./src/objects --output ./src/types
+```
+
+### 2.3 `new` (Scaffold Metadata)
+
+Generate a new metadata file (Object, View, Form, etc.) in the project.
+
+```bash
+npx objectql new <type> <name> [options]
+```
+
+**Arguments:**
+*   `<type>`: The type of metadata to generate (e.g., `object`, `view`, `page`).
+*   `<name>`: The name of the file/entity.
+
+**Options:**
+
+| Option | Alias | Default | Description |
+| :--- | :--- | :--- | :--- |
+| `--dir <path>` | `-d` | `.` | Output directory. |
+
+**Example:**
+```bash
+npx objectql new object customer
+```
+
+## 3. Development Tools
+
+### 3.1 `serve` (Dev Server)
+
+Start a standalone development server.
+**Alias**: `s`
+
+```bash
+npx objectql serve [options]
+```
+
+**Options:**
+
+| Option | Alias | Default | Description |
+| :--- | :--- | :--- | :--- |
+| `--port <number>` | `-p` | `3000` | Port to listen on. |
+| `--dir <path>` | `-d` | `.` | Directory containing schema. |
+
+### 3.2 `studio` (Admin UI)
+
+Starts the web-based admin studio to browse data and view schema.
+**Alias**: `ui`
+
+```bash
+npx objectql studio [options]
+```
+
+**Options:**
+
+| Option | Alias | Default | Description |
+| :--- | :--- | :--- | :--- |
+| `--port <number>` | `-p` | `3000` | Port to listen on. |
+| `--dir <path>` | `-d` | `.` | Directory containing schema. |
+| `--no-open` | | `false` | Do not open the browser automatically. |
+
+### 3.3 `repl` (Interactive Shell)
+
+Starts an interactive terminal similar to the MongoDB shell, allowing you to directly query your database using the ObjectQL API.
+**Alias**: `r`
+
+```bash
+npx objectql repl [options]
+```
+
+**Options:**
+
+| Option | Alias | Default | Description |
+| :--- | :--- | :--- | :--- |
+| `--config <path>` | `-c` | - | Path to `objectql.config.ts/js`. |
+
+**Example Session:**
+
+```javascript
+objectql> await tasks.find({ status: 'todo' })
+[ { id: 1, title: 'Fix bug', status: 'todo' } ]
+```
+
+## 4. Internationalization (i18n)
+
+Tools for managing translations.
+
+### 4.1 `i18n extract`
+
+Extract translatable strings from metadata files into JSON.
+
+```bash
+npx objectql i18n extract [options]
+```
+
+**Options:**
+
+| Option | Alias | Default | Description |
+| :--- | :--- | :--- | :--- |
+| `--source <path>` | `-s` | `.` | Source directory to scan. |
+| `--output <path>` | `-o` | `./src/i18n` | Output directory for translation files. |
+| `--lang <lang>` | `-l` | `en` | Language code. |
+
+### 4.2 `i18n init`
+
+Initialize i18n structure for a new language.
+
+```bash
+npx objectql i18n init <lang> [options]
+```
+
+**Options:**
+
+| Option | Alias | Default | Description |
+| :--- | :--- | :--- | :--- |
+| `--base-dir <path>` | `-b` | `./src/i18n` | Base i18n directory. |
+
+### 4.3 `i18n validate`
+
+Validate translation completeness against a base language.
+
+```bash
+npx objectql i18n validate <lang> [options]
+```
+
+**Options:**
+
+| Option | Alias | Default | Description |
+| :--- | :--- | :--- | :--- |
+| `--base-dir <path>` | `-b` | `./src/i18n` | Base i18n directory. |
+| `--base-lang <lang>` | | `en` | Base language to compare against. |
+
+## 5. Database Migration
+
+Manage database schema changes.
+
+### 5.1 `migrate`
+
+Run pending database migrations.
+
+```bash
+npx objectql migrate [options]
+```
+
+**Options:**
+
+| Option | Alias | Default | Description |
+| :--- | :--- | :--- | :--- |
+| `--config <path>` | `-c` | - | Path to `objectql.config.ts/js`. |
+| `--dir <path>` | `-d` | `./migrations` | Migrations directory. |
+
+### 5.2 `migrate create`
+
+Create a new migration file.
+
+```bash
+npx objectql migrate create <name> [options]
+```
+
+**Options:**
+
+| Option | Alias | Default | Description |
+| :--- | :--- | :--- | :--- |
+| `--dir <path>` | `-d` | `./migrations` | Migrations directory. |
+
+### 5.3 `migrate status`
+
+Show the status of migrations (applied/pending).
+
+```bash
+npx objectql migrate status [options]
+```
+
+**Options:**
+
+| Option | Alias | Default | Description |
+| :--- | :--- | :--- | :--- |
+| `--config <path>` | `-c` | - | Path to `objectql.config.ts/js`. |
+| `--dir <path>` | `-d` | `./migrations` | Migrations directory. |
+
+## 6. Integration with Workflow
+
+We recommend adding the CLI commands to your lifecycle scripts.
+
+**package.json:**
+
+```json
+{
+  "scripts": {
+    "codegen": "objectql generate -s ./src -o ./src/generated",
+    "build": "npm run codegen && tsc",
+    "dev": "npm run codegen && ts-node src/index.ts",
+    "studio": "objectql studio"
+  }
+}
+```
+
+This ensures that whenever you build or start your app, your TypeScript types are perfectly synced with your YAML definitions.
diff --git a/docs/guide/configuration.md b/docs/guide/configuration.md
new file mode 100644
index 00000000..68d26ecb
--- /dev/null
+++ b/docs/guide/configuration.md
@@ -0,0 +1,44 @@
+# Configuration
+
+ObjectQL is configured by passing an `ObjectQLConfig` object to the constructor.
+
+## Basic Layout
+
+```typescript
+// objectql.config.ts
+import { ObjectQL } from '@objectql/core';
+
+export const db = new ObjectQL({
+    connection: 'sqlite://data.db', // 1. Infrastructure
+    presets: ['@objectql/preset-auth'], // 2. Base Capabilities
+    source: ['src'], // 3. Application Logic
+    plugins: [] // 4. Extensions
+});
+```
+
+## Reference
+
+### `connection` (string)
+The Connection String URI defining the database connection.
+*   `sqlite://path/to/db`
+*   `postgres://user:pass@host:5432/db`
+*   `mongodb://host:27017/db`
+
+The engine will automatically load the appropriate driver (`@objectql/driver-sql` or `@objectql/driver-mongo`).
+
+### `source` (string | string[])
+One or more directory paths (relative or absolute) containing your schema files (`*.object.yml`).
+The loader scans these directories recursively.
+
+### `presets` (string[])
+A list of NPM packages to load as presets.
+ObjectQL will try to resolve the package and load schema files from its directory.
+Useful for sharing common business objects (User, Role, File, etc.).
+
+### `plugins` ((ObjectQLPlugin | string)[])
+A list of plugin instances OR package names to extend the core functionality.
+See [Plugin System](./plugins.html) for details.
+
+### `objects` (Record<string, ObjectConfig>)
+(Advanced) In-memory definition of objects. Useful for dynamic runtime schema generation.
+Objects defined here take highest priority.
diff --git a/docs/guide/data-modeling.md b/docs/guide/data-modeling.md
new file mode 100644
index 00000000..39b36186
--- /dev/null
+++ b/docs/guide/data-modeling.md
@@ -0,0 +1,154 @@
+# Data Modeling Guide
+
+Data modeling in ObjectQL is **Metadata-First**. You define your application's schema using `*.object.yml` files (or JSON), and ObjectQL handles validation, database mapping, and type generation.
+
+## 1. The Object Definition
+
+**ObjectQL uses filename-based identification.** The object name is automatically inferred from the filename (without the `.object.yml` extension), eliminating redundancy.
+
+**File naming:** `<object_name>.object.yml`
+
+```yaml
+# File: product.object.yml
+# Object name "product" is automatically inferred from filename!
+
+label: Product
+description: "Catalog items for sale"
+icon: standard:product
+
+fields:
+  name:
+    type: text
+    required: true
+    label: Product Name
+  
+  price:
+    type: currency
+    scale: 2
+    label: Price
+    
+  category:
+    type: select
+    options:
+      - electronics
+      - furniture
+      - clothing
+```
+
+**Note:** The redundant `name: product` property is no longer needed - it's automatically inferred from the filename!
+
+## 2. Fields & Relationships
+
+ObjectQL supports rich field types that automate UI rendering and validation.
+
+### Core Types
+*   **Text**: `text`, `textarea`, `markdown`, `html`
+*   **Numbers**: `number`, `currency`, `percent`
+*   **Flags**: `boolean`
+*   **Media**: `image`, `file`, `avatar`
+
+### Relationships
+*   **Lookup**: A loose foreign key. Can be optional.
+    ```yaml
+    created_by: { type: lookup, reference_to: user }
+    ```
+*   **Master-Detail**: A strong parent-child bond. Deleting the parent cascades to the child.
+    ```yaml
+    order_id: { type: master_detail, reference_to: order }
+    ```
+
+### Specialized Types
+*   **Vector**: Stores embeddings (arrays of floats) for AI search.
+    ```yaml
+    embedding: { type: vector, dimension: 1536, index: true }
+    ```
+
+## 3. Indexes & Constraints
+
+Optimize query performance and ensure data integrity.
+
+### Field-Level Shortcuts
+Use these for simple, single-column definitions.
+
+```yaml
+fields:
+  sku:
+    type: text
+    unique: true  # Enforce uniqueness
+  
+  status:
+    type: select
+    index: true   # Speed up filters
+```
+
+### Composite Indexes
+Define these at the root of your object file for multi-column optimizations (e.g., sorting by Date within a Category).
+
+```yaml
+indexes:
+  category_date_idx:
+    fields: [category, created_at]
+  
+  unique_product_variant:
+    fields: [product_id, color, size]
+    unique: true
+```
+
+## 4. Internationalization (i18n)
+
+ObjectQL adopts a "clean schema, external translation" philosophy.
+
+*   **Schema**: Keep `*.object.yml` clean and technical (usually English keys/labels).
+*   **Metadata Translations**: Store UI labels in `i18n/[lang]/[object].json`.
+*   **Data Translations**: If you need to translate record content (like a Product Name), we recommend modeling it explicitly (e.g., a `ProductTranslation` table) rather than complicating the core column types.
+
+## 5. Extending Objects
+
+ObjectQL supports a powerful **Schema Merging** capability. This allows you to extend or modify objects defined in external packages (like plugins or standard libraries) without touching their source code.
+
+This mechanism works by defining a new `.object.yml` file with the **same object name**.
+
+### How it works
+
+When ObjectQL loads schemas, if it encounters multiple definitions for the same object (e.g., `user`), it merges them together. The priority depends on the loading order (usually Application layer overrides Package/Plugin layer).
+
+### Example: Extending the User Object
+
+Suppose a plugin defines a basic `user` object. You want to add a `phone` field and enforce that `email` is required.
+
+**Original Definition (in Plugin):**
+```yaml
+# node_modules/@objectql/plugin-auth/user.object.yml
+name: user
+fields:
+  name: { type: text }
+  email: { type: text }
+```
+
+**Your Extension (in App):**
+```yaml
+# src/objects/user-extension.object.yml
+name: user                 # Must match exactly
+label: System User (Ext)   # Overrides the label
+
+fields:
+  # 1. Modify existing field
+  email:
+    required: true
+
+  # 2. Add new field
+  phone:
+    type: text
+    label: Mobile Phone
+    unique: true
+```
+
+### Merge Rules
+
+| Component | Behavior |
+| :--- | :--- |
+| **Top-level Props** | **Override**. (`label`, `icon`, `description` in your file replace the original). |
+| **Fields** | **Deep Merge**. Existing fields are updated (properties merged), new fields are added. |
+| **Actions** | **Merge**. You can add new actions or override existing ones. |
+| **Indexes** | **Merge**. New indexes are added. |
+
diff --git a/docs/guide/drivers/extensibility.md b/docs/guide/drivers/extensibility.md
new file mode 100644
index 00000000..0be72d14
--- /dev/null
+++ b/docs/guide/drivers/extensibility.md
@@ -0,0 +1,178 @@
+# Driver Extensibility Guide
+
+ObjectQL is designed to support multiple database backends through its **Driver** abstraction layer. This guide explains how to extend ObjectQL with additional database types.
+
+## Current Official Drivers
+
+ObjectQL currently provides official support for:
+
+| Driver | Package | Databases Supported | Status |
+|--------|---------|---------------------|--------|
+| **SQL Driver** | `@objectql/driver-sql` | PostgreSQL, MySQL, SQLite, SQL Server | ✅ Production Ready |
+| **MongoDB Driver** | `@objectql/driver-mongo` | MongoDB 4.0+ | ✅ Production Ready |
+| **SDK/Remote Driver** | `@objectql/sdk` | HTTP-based ObjectQL servers | ✅ Production Ready |
+
+## Potential Database Types for Extension
+
+ObjectQL's Driver interface can theoretically support any database system. Here are common database types that could be implemented:
+
+### Key-Value Stores
+
+| Database | Use Case | Implementation Complexity |
+|----------|----------|--------------------------|
+| **Redis** | Caching, real-time data, pub/sub | 🟢 Low - Simple key-value operations |
+| **Memcached** | Distributed caching | 🟢 Low - Basic get/set operations |
+| **etcd** | Configuration management, service discovery | 🟡 Medium - Hierarchical keys |
+
+### Document Databases
+
+| Database | Use Case | Implementation Complexity |
+|----------|----------|--------------------------|
+| **CouchDB** | Multi-master replication, offline-first | 🟡 Medium - Similar to MongoDB |
+| **Firebase/Firestore** | Real-time sync, mobile apps | 🟡 Medium - Cloud-native features |
+| **RavenDB** | .NET integration, ACID transactions | 🟡 Medium - Advanced indexing |
+
+### Wide Column Stores
+
+| Database | Use Case | Implementation Complexity |
+|----------|----------|--------------------------|
+| **Cassandra** | High availability, time-series data | 🔴 High - Distributed architecture |
+| **HBase** | Hadoop ecosystem, big data | 🔴 High - Complex data model |
+| **DynamoDB** | AWS-native, serverless | 🟡 Medium - Single-table design patterns |
+
+### Search Engines
+
+| Database | Use Case | Implementation Complexity |
+|----------|----------|--------------------------|
+| **Elasticsearch** | Full-text search, analytics | 🟡 Medium - Query DSL mapping |
+| **OpenSearch** | Fork of Elasticsearch, AWS managed | 🟡 Medium - Similar to Elasticsearch |
+| **Algolia** | Hosted search, real-time indexing | 🟢 Low - REST API based |
+| **Meilisearch** | Typo-tolerant search | 🟢 Low - Simple REST API |
+
+### Graph Databases
+
+| Database | Use Case | Implementation Complexity |
+|----------|----------|--------------------------|
+| **Neo4j** | Social networks, recommendation engines | 🔴 High - Cypher query language |
+| **ArangoDB** | Multi-model (graph + document) | 🟡 Medium - AQL query language |
+| **OrientDB** | Multi-model graph database | 🟡 Medium - SQL-like syntax |
+
+### Time-Series Databases
+
+| Database | Use Case | Implementation Complexity |
+|----------|----------|--------------------------|
+| **InfluxDB** | Metrics, IoT, monitoring | 🟡 Medium - Time-based queries |
+| **TimescaleDB** | PostgreSQL extension for time-series | 🟢 Low - SQL compatible |
+| **Prometheus** | Monitoring and alerting | 🟡 Medium - PromQL query language |
+
+### NewSQL Databases
+
+| Database | Use Case | Implementation Complexity |
+|----------|----------|--------------------------|
+| **CockroachDB** | Distributed SQL, PostgreSQL compatible | 🟢 Low - PostgreSQL protocol |
+| **TiDB** | MySQL compatible, horizontal scaling | 🟢 Low - MySQL protocol |
+| **YugabyteDB** | PostgreSQL compatible, cloud-native | 🟢 Low - PostgreSQL protocol |
+
+### Cloud-Native Databases
+
+| Database | Use Case | Implementation Complexity |
+|----------|----------|--------------------------|
+| **AWS DynamoDB** | Serverless, auto-scaling | 🟡 Medium - NoSQL patterns |
+| **Google Cloud Firestore** | Real-time sync, mobile | 🟡 Medium - Document-based |
+| **Azure Cosmos DB** | Multi-model, global distribution | 🟡 Medium - Multiple APIs |
+| **Supabase** | PostgreSQL-as-a-service | 🟢 Low - PostgreSQL protocol |
+| **PlanetScale** | MySQL-compatible, serverless | 🟢 Low - MySQL protocol |
+
+### Columnar Databases
+
+| Database | Use Case | Implementation Complexity |
+|----------|----------|--------------------------|
+| **ClickHouse** | OLAP, analytics, data warehousing | 🔴 High - Column-oriented queries |
+| **Apache Druid** | Real-time analytics | 🔴 High - Complex aggregations |
+
+### Embedded Databases
+
+| Database | Use Case | Implementation Complexity |
+|----------|----------|--------------------------|
+| **LevelDB** | Embedded key-value store | 🟢 Low - Simple operations |
+| **RocksDB** | High-performance embedded DB | 🟢 Low - LevelDB-compatible |
+| **LMDB** | Memory-mapped key-value store | 🟢 Low - Fast read operations |
+
+## Implementation Complexity Guide
+
+- 🟢 **Low Complexity** (1-2 weeks): Database has SQL compatibility or simple REST API, straightforward query mapping
+- 🟡 **Medium Complexity** (3-6 weeks): Custom query language, moderate feature mapping required
+- 🔴 **High Complexity** (2-3 months): Distributed systems, complex data models, significant architectural differences
+
+## Choosing a Database to Implement
+
+When deciding which database to add support for, consider:
+
+### 1. **Use Case Alignment**
+- Does the database solve a specific problem for ObjectQL users?
+- Does it complement existing drivers?
+
+### 2. **Community Demand**
+- Is there active interest in this database?
+- Are there existing GitHub issues requesting it?
+
+### 3. **Technical Feasibility**
+- How well does the database's data model map to ObjectQL's abstraction?
+- Does it support required operations (CRUD, filters, sorting)?
+
+### 4. **Maintenance Burden**
+- Is the database actively maintained?
+- Does it have a stable API?
+- Is there good documentation?
+
+### 5. **Ecosystem Maturity**
+- Are there quality Node.js/TypeScript clients?
+- Is the client library actively maintained?
+
+## Recommended First Extensions
+
+Based on community needs and implementation complexity, we recommend prioritizing:
+
+1. **Redis Driver** - High demand, simple implementation, excellent for caching
+2. **Elasticsearch Driver** - Popular for search features, clear use case
+3. **DynamoDB Driver** - AWS ecosystem, serverless applications
+4. **ClickHouse Driver** - Analytics and reporting use cases
+
+## Getting Started
+
+To implement a custom driver:
+
+1. Review the [Driver Implementation Guide](./implementing-custom-driver.md)
+2. Study existing driver implementations:
+   - [`@objectql/driver-sql`](../../../packages/drivers/sql/src/index.ts) - SQL databases
+   - [`@objectql/driver-mongo`](../../../packages/drivers/mongo/src/index.ts) - MongoDB
+3. Review the [Driver Interface](../../../packages/foundation/types/src/driver.ts)
+4. Follow the [Driver Testing Guide](./testing-drivers.md) (coming soon)
+
+## Community Drivers
+
+We encourage the community to create and maintain third-party drivers for additional databases. If you've implemented a driver, please:
+
+1. Follow the ObjectQL driver conventions
+2. Include comprehensive tests
+3. Document configuration and usage
+4. Submit a PR to add your driver to this list
+
+### Publishing Community Drivers
+
+Name your package following the convention: `@your-org/objectql-driver-<database>`
+
+Example: `@acme/objectql-driver-redis`
+
+## Need Help?
+
+- 📖 Read the [Driver Implementation Guide](./implementing-custom-driver.md)
+- 💬 Join the [ObjectQL Discord](https://discord.gg/objectql) (if available)
+- 🐛 [Open a GitHub Issue](https://github.com/objectstack-ai/objectql/issues)
+- 📧 Contact the maintainers
+
+## Related Documentation
+
+- [SQL Driver Documentation](./sql.md)
+- [MongoDB Driver Documentation](./mongo.md)
+- [Driver Interface Reference](../../../packages/foundation/types/src/driver.ts)
diff --git a/docs/guide/drivers/implementing-custom-driver.md b/docs/guide/drivers/implementing-custom-driver.md
new file mode 100644
index 00000000..212d0135
--- /dev/null
+++ b/docs/guide/drivers/implementing-custom-driver.md
@@ -0,0 +1,552 @@
+# Implementing a Custom Driver
+
+This guide walks you through implementing a custom database driver for ObjectQL. By the end, you'll understand how to create a driver that seamlessly integrates with ObjectQL's universal data protocol.
+
+## Table of Contents
+
+1. [Understanding the Driver Interface](#understanding-the-driver-interface)
+2. [Implementation Steps](#implementation-steps)
+3. [Best Practices](#best-practices)
+4. [Testing Your Driver](#testing-your-driver)
+5. [Example: Redis Driver](#example-redis-driver)
+
+## Understanding the Driver Interface
+
+All ObjectQL drivers implement the `Driver` interface defined in `@objectql/types/src/driver.ts`:
+
+```typescript
+export interface Driver {
+    // Basic CRUD Operations
+    find(objectName: string, query: any, options?: any): Promise<any[]>;
+    findOne(objectName: string, id: string | number, query?: any, options?: any): Promise<any>;
+    create(objectName: string, data: any, options?: any): Promise<any>;
+    update(objectName: string, id: string | number, data: any, options?: any): Promise<any>;
+    delete(objectName: string, id: string | number, options?: any): Promise<any>;
+    count(objectName: string, filters: any, options?: any): Promise<number>;
+    
+    // Schema / Lifecycle (Optional)
+    init?(objects: any[]): Promise<void>;
+    introspectSchema?(): Promise<IntrospectedSchema>;
+    
+    // Advanced Operations (Optional)
+    aggregate?(objectName: string, query: any, options?: any): Promise<any>;
+    distinct?(objectName: string, field: string, filters?: any, options?: any): Promise<any[]>;
+    
+    // Bulk / Atomic Operations (Optional)
+    createMany?(objectName: string, data: any[], options?: any): Promise<any>;
+    updateMany?(objectName: string, filters: any, data: any, options?: any): Promise<any>;
+    deleteMany?(objectName: string, filters: any, options?: any): Promise<any>;
+    findOneAndUpdate?(objectName: string, filters: any, update: any, options?: any): Promise<any>;
+    
+    // Transaction Support (Optional)
+    beginTransaction?(): Promise<any>;
+    commitTransaction?(trx: any): Promise<void>;
+    rollbackTransaction?(trx: any): Promise<void>;
+    
+    // Connection Management (Optional)
+    disconnect?(): Promise<void>;
+}
+```
+
+### Required Methods
+
+These methods **must** be implemented:
+
+- `find()` - Query multiple records
+- `findOne()` - Get a single record by ID
+- `create()` - Create a new record
+- `update()` - Update an existing record
+- `delete()` - Delete a record
+- `count()` - Count records matching filters
+
+### Optional Methods
+
+These methods enhance functionality but are not required:
+
+- `init()` - Initialize database schema
+- `introspectSchema()` - Read existing database schema
+- `aggregate()` - Perform aggregation operations
+- `distinct()` - Get distinct values
+- `createMany()`, `updateMany()`, `deleteMany()` - Bulk operations
+- `beginTransaction()`, `commitTransaction()`, `rollbackTransaction()` - Transaction support
+- `disconnect()` - Clean up resources
+
+## Implementation Steps
+
+### Step 1: Set Up the Package
+
+Create a new package in `packages/drivers/<driver-name>/`:
+
+```bash
+mkdir -p packages/drivers/redis
+cd packages/drivers/redis
+```
+
+Create `package.json`:
+
+```json
+{
+  "name": "@objectql/driver-redis",
+  "version": "1.0.0",
+  "description": "Redis driver for ObjectQL",
+  "main": "dist/index.js",
+  "types": "dist/index.d.ts",
+  "scripts": {
+    "build": "tsc",
+    "test": "jest"
+  },
+  "dependencies": {
+    "@objectql/types": "workspace:*",
+    "redis": "^4.6.0"
+  },
+  "devDependencies": {
+    "typescript": "^5.0.0",
+    "jest": "^29.0.0",
+    "@types/jest": "^29.0.0"
+  }
+}
+```
+
+Create `tsconfig.json`:
+
+```json
+{
+  "extends": "../../../tsconfig.base.json",
+  "compilerOptions": {
+    "outDir": "./dist",
+    "rootDir": "./src"
+  },
+  "include": ["src/**/*"]
+}
+```
+
+### Step 2: Create the Driver Class
+
+Create `src/index.ts`:
+
+```typescript
+import { Driver } from '@objectql/types';
+import { createClient, RedisClientType } from 'redis';
+
+export class RedisDriver implements Driver {
+    private client: RedisClientType;
+    private config: any;
+    private connected: Promise<void>;
+
+    constructor(config: { url: string }) {
+        this.config = config;
+        this.client = createClient({ url: config.url });
+        this.connected = this.connect();
+    }
+
+    private async connect(): Promise<void> {
+        await this.client.connect();
+    }
+
+    // Implement required methods...
+}
+```
+
+### Step 3: Implement Core CRUD Methods
+
+#### `find()`
+
+The `find()` method must handle:
+- **Filters**: Array of filter conditions
+- **Sorting**: Sort order specifications
+- **Pagination**: `skip` and `limit`
+- **Field Projection**: `fields` array
+
+```typescript
+async find(objectName: string, query: any, options?: any): Promise<any[]> {
+    await this.connected;
+    
+    // Get all keys for this object type
+    const pattern = `${objectName}:*`;
+    const keys = await this.client.keys(pattern);
+    
+    // Retrieve all documents
+    let results: any[] = [];
+    for (const key of keys) {
+        const data = await this.client.get(key);
+        if (data) {
+            const doc = JSON.parse(data);
+            results.push(doc);
+        }
+    }
+    
+    // Apply filters
+    if (query.filters) {
+        results = this.applyFilters(results, query.filters);
+    }
+    
+    // Apply sorting
+    if (query.sort) {
+        results = this.applySort(results, query.sort);
+    }
+    
+    // Apply pagination
+    if (query.skip) {
+        results = results.slice(query.skip);
+    }
+    if (query.limit) {
+        results = results.slice(0, query.limit);
+    }
+    
+    // Apply field projection
+    if (query.fields) {
+        results = results.map(doc => this.projectFields(doc, query.fields));
+    }
+    
+    return results;
+}
+```
+
+#### `findOne()`
+
+```typescript
+async findOne(objectName: string, id: string | number, query?: any, options?: any): Promise<any> {
+    await this.connected;
+    
+    const key = `${objectName}:${id}`;
+    const data = await this.client.get(key);
+    
+    if (!data) {
+        return null;
+    }
+    
+    return JSON.parse(data);
+}
+```
+
+#### `create()`
+
+```typescript
+async create(objectName: string, data: any, options?: any): Promise<any> {
+    await this.connected;
+    
+    // Generate ID if not provided
+    const id = data.id || this.generateId();
+    const doc = {
+        ...data,
+        id,
+        created_at: new Date().toISOString(),
+        updated_at: new Date().toISOString()
+    };
+    
+    const key = `${objectName}:${id}`;
+    await this.client.set(key, JSON.stringify(doc));
+    
+    return doc;
+}
+```
+
+#### `update()`
+
+```typescript
+async update(objectName: string, id: string | number, data: any, options?: any): Promise<any> {
+    await this.connected;
+    
+    const key = `${objectName}:${id}`;
+    const existing = await this.client.get(key);
+    
+    if (!existing) {
+        throw new Error(`Record not found: ${objectName}:${id}`);
+    }
+    
+    const doc = {
+        ...JSON.parse(existing),
+        ...data,
+        id,
+        updated_at: new Date().toISOString()
+    };
+    
+    await this.client.set(key, JSON.stringify(doc));
+    
+    return doc;
+}
+```
+
+#### `delete()`
+
+```typescript
+async delete(objectName: string, id: string | number, options?: any): Promise<any> {
+    await this.connected;
+    
+    const key = `${objectName}:${id}`;
+    const result = await this.client.del(key);
+    
+    return result > 0;
+}
+```
+
+#### `count()`
+
+```typescript
+async count(objectName: string, filters: any, options?: any): Promise<number> {
+    await this.connected;
+    
+    const pattern = `${objectName}:*`;
+    const keys = await this.client.keys(pattern);
+    
+    if (!filters) {
+        return keys.length;
+    }
+    
+    // Count only records matching filters
+    let count = 0;
+    for (const key of keys) {
+        const data = await this.client.get(key);
+        if (data) {
+            const doc = JSON.parse(data);
+            if (this.matchesFilters(doc, filters)) {
+                count++;
+            }
+        }
+    }
+    
+    return count;
+}
+```
+
+### Step 4: Implement Filter Logic
+
+ObjectQL uses a universal filter format:
+
+```typescript
+// Example filters:
+[
+  ['name', '=', 'John'],           // Simple equality
+  'or',                            // Logical operator
+  ['age', '>', 25],                // Comparison
+  'and',
+  ['status', 'in', ['active', 'pending']]  // IN operator
+]
+```
+
+Implement filter matching:
+
+```typescript
+private applyFilters(records: any[], filters: any[]): any[] {
+    return records.filter(record => this.matchesFilters(record, filters));
+}
+
+private matchesFilters(record: any, filters: any[]): boolean {
+    if (!filters || filters.length === 0) {
+        return true;
+    }
+    
+    let result = true;
+    let nextJoin = 'and';
+    
+    for (const item of filters) {
+        if (typeof item === 'string') {
+            // Logical operator
+            nextJoin = item.toLowerCase();
+            continue;
+        }
+        
+        if (Array.isArray(item)) {
+            const [field, operator, value] = item;
+            const matches = this.evaluateCondition(record[field], operator, value);
+            
+            if (nextJoin === 'and') {
+                result = result && matches;
+            } else {
+                result = result || matches;
+            }
+            
+            nextJoin = 'and'; // Reset to default
+        }
+    }
+    
+    return result;
+}
+
+private evaluateCondition(fieldValue: any, operator: string, compareValue: any): boolean {
+    switch (operator) {
+        case '=':
+            return fieldValue === compareValue;
+        case '!=':
+            return fieldValue !== compareValue;
+        case '>':
+            return fieldValue > compareValue;
+        case '>=':
+            return fieldValue >= compareValue;
+        case '<':
+            return fieldValue < compareValue;
+        case '<=':
+            return fieldValue <= compareValue;
+        case 'in':
+            return Array.isArray(compareValue) && compareValue.includes(fieldValue);
+        case 'nin':
+            return Array.isArray(compareValue) && !compareValue.includes(fieldValue);
+        case 'contains':
+            return String(fieldValue).includes(String(compareValue));
+        default:
+            return false;
+    }
+}
+```
+
+### Step 5: Implement Sorting
+
+```typescript
+private applySort(records: any[], sort: any[]): any[] {
+    const sorted = [...records];
+    
+    // Apply sorts in reverse order for correct precedence
+    for (let i = sort.length - 1; i >= 0; i--) {
+        const [field, direction] = Array.isArray(sort[i]) 
+            ? sort[i] 
+            : [sort[i].field, sort[i].order || 'asc'];
+        
+        sorted.sort((a, b) => {
+            const aVal = a[field];
+            const bVal = b[field];
+            
+            if (aVal < bVal) return direction === 'asc' ? -1 : 1;
+            if (aVal > bVal) return direction === 'asc' ? 1 : -1;
+            return 0;
+        });
+    }
+    
+    return sorted;
+}
+```
+
+### Step 6: Add Cleanup
+
+```typescript
+async disconnect(): Promise<void> {
+    await this.client.quit();
+}
+```
+
+### Step 7: Add Helper Methods
+
+```typescript
+private generateId(): string {
+    // Simple UUID v4 generation
+    return 'xxxxxxxx-xxxx-4xxx-yxxx-xxxxxxxxxxxx'.replace(/[xy]/g, (c) => {
+        const r = Math.random() * 16 | 0;
+        const v = c === 'x' ? r : (r & 0x3 | 0x8);
+        return v.toString(16);
+    });
+}
+
+private projectFields(doc: any, fields: string[]): any {
+    const result: any = {};
+    for (const field of fields) {
+        if (doc[field] !== undefined) {
+            result[field] = doc[field];
+        }
+    }
+    return result;
+}
+```
+
+## Best Practices
+
+### 1. **Consistent ID Handling**
+
+- Use `id` as the primary key field name (not `_id`)
+- Support both string and number IDs
+- Auto-generate IDs when not provided
+
+### 2. **Error Handling**
+
+```typescript
+import { ObjectQLError } from '@objectql/types';
+
+async create(objectName: string, data: any): Promise<any> {
+    try {
+        // Implementation
+    } catch (error) {
+        throw new ObjectQLError({
+            code: 'CREATE_FAILED',
+            message: `Failed to create ${objectName}: ${error.message}`,
+            details: { objectName, error }
+        });
+    }
+}
+```
+
+### 3. **TypeScript Strict Mode**
+
+- Enable `strict: true` in `tsconfig.json`
+- Avoid using `any` where possible
+- Define proper types for configuration
+
+### 4. **Async/Await Consistency**
+
+- All driver methods should be `async`
+- Always await database operations
+- Handle connection pooling properly
+
+### 5. **Performance Optimization**
+
+- Use connection pooling
+- Batch operations when possible
+- Implement proper indexing strategies
+
+### 6. **Testing**
+
+Create comprehensive tests in `test/index.test.ts`:
+
+```typescript
+import { RedisDriver } from '../src';
+
+describe('RedisDriver', () => {
+    let driver: RedisDriver;
+    
+    beforeAll(async () => {
+        driver = new RedisDriver({ url: 'redis://localhost:6379' });
+    });
+    
+    afterAll(async () => {
+        await driver.disconnect();
+    });
+    
+    describe('CRUD Operations', () => {
+        it('should create a record', async () => {
+            const result = await driver.create('users', {
+                name: 'Alice',
+                email: 'alice@example.com'
+            });
+            
+            expect(result).toHaveProperty('id');
+            expect(result.name).toBe('Alice');
+        });
+        
+        // Add more tests...
+    });
+});
+```
+
+## Example: Redis Driver
+
+See the complete Redis driver implementation in [`packages/drivers/redis/`](../../../packages/drivers/redis/) (if available).
+
+## Publishing Your Driver
+
+1. **Test Thoroughly**: Ensure all required methods work correctly
+2. **Document**: Create clear README with usage examples
+3. **Version**: Follow semantic versioning (SemVer)
+4. **Publish**: Publish to npm with appropriate tags
+
+```bash
+npm publish --access public
+```
+
+## Getting Help
+
+- Review existing drivers: [SQL](../../../packages/drivers/sql/), [MongoDB](../../../packages/drivers/mongo/)
+- Check the [Driver Interface](../../../packages/foundation/types/src/driver.ts)
+- Open an issue on [GitHub](https://github.com/objectstack-ai/objectql/issues)
+
+## Next Steps
+
+- Read the [Driver Extensibility Guide](./extensibility.md)
+- Study the [SQL Driver Implementation](../../../packages/drivers/sql/src/index.ts)
+- Join the ObjectQL community for support
diff --git a/docs/guide/drivers/index.md b/docs/guide/drivers/index.md
new file mode 100644
index 00000000..3c0c430a
--- /dev/null
+++ b/docs/guide/drivers/index.md
@@ -0,0 +1,62 @@
+# Database Drivers
+
+ObjectQL relies on **Drivers** to communicate with the underlying database. A driver is responsible for translating the ObjectQL specific query format (AST) into the native query language of the database (SQL, MongoDB Query, etc.).
+
+You can configure multiple drivers for different parts of your application, or use a single driver for everything.
+
+## Available Drivers
+
+We currently support the following official drivers:
+
+*   **[SQL Driver](./sql)**: Supports PostgreSQL, MySQL, SQLite, MSSQL, etc.
+*   **[MongoDB Driver](./mongo)**: Supports MongoDB.
+
+## Extensibility
+
+ObjectQL is designed to support additional database types through custom drivers. 
+
+*   **[Driver Extensibility Guide](./extensibility)**: Learn about potential database types that can be supported and how to choose the right one for your needs.
+*   **[Implementing a Custom Driver](./implementing-custom-driver)**: Step-by-step guide to building your own database driver for ObjectQL.
+
+## Unified ID Field
+
+ObjectQL provides a **consistent API** across all database drivers by standardizing on the `id` field name for primary keys:
+
+- **MongoDB Driver**: Automatically maps `id` (API) ↔ `_id` (database)
+- **SQL Driver**: Uses `id` natively in the database schema
+
+This means you can write database-agnostic code:
+
+```typescript
+// Same code works with MongoDB OR SQL drivers!
+const user = await app.create('users', {
+  id: 'user-123',     // Works with both drivers
+  name: 'Alice'
+});
+
+const query = {
+  filters: [['id', '=', 'user-123']]  // Consistent across drivers
+};
+const results = await app.find('users', query);
+```
+
+**No more switching between `_id` and `id` depending on your database!**
+
+See the individual driver documentation for implementation details.
+
+## Configuring a Driver
+
+Drivers are instantiated and passed to the `ObjectQL` constructor under the `driver` property (or `datasources` map for multi-db setup).
+
+```typescript
+import { ObjectQL } from '@objectql/core';
+import { SqlDriver } from '@objectql/driver-sql';
+
+const myDriver = new SqlDriver({ /* options */ });
+
+const app = new ObjectQL({
+  driver: myDriver
+});
+```
+
+See the specific pages for configuration options for each driver.
diff --git a/docs/guide/drivers/mongo.md b/docs/guide/drivers/mongo.md
new file mode 100644
index 00000000..6e087137
--- /dev/null
+++ b/docs/guide/drivers/mongo.md
@@ -0,0 +1,154 @@
+# MongoDB Driver
+
+The MongoDB driver allows ObjectQL to store data in a MongoDB database (version 4.0+). It takes advantage of MongoDB's document model to store JSON fields natively and flexible schemas.
+
+## Installation
+
+```bash
+npm install @objectql/driver-mongo mongodb
+```
+
+## Configuration
+
+The `MongoDriver` accepts connection parameters directly.
+
+```typescript
+import { MongoDriver } from '@objectql/driver-mongo';
+
+const driver = new MongoDriver({
+  url: 'mongodb://localhost:27017', // Connection string
+  dbName: 'my_app_db',              // Database name
+  options: {
+    // Optional MongoDB client options
+    maxPoolSize: 10
+  }
+});
+```
+
+## Unified ID Field
+
+ObjectQL provides a **unified `id` field** across all database drivers for a consistent API experience.
+
+### How It Works
+
+- **API Level**: You always use `id` in your application code (queries, filters, documents)
+- **Database Level**: MongoDB internally uses `_id` as required by MongoDB conventions
+- **Automatic Mapping**: The driver transparently converts between `id` and `_id`
+
+### Examples
+
+**Querying by ID:**
+```typescript
+// ✅ Use 'id' in queries - works consistently across all drivers
+const query = {
+  filters: [['id', '=', '507f1f77bcf86cd799439011']]
+};
+const users = await app.find('users', query);
+```
+
+**Creating Documents:**
+```typescript
+// ✅ Use 'id' when creating - the driver maps it to '_id' internally
+const newUser = await app.create('users', {
+  id: '507f1f77bcf86cd799439011',  // Optional: specify custom ID
+  name: 'Alice',
+  email: 'alice@example.com'
+});
+
+// Result returned with 'id' field (not '_id')
+console.log(newUser.id); // '507f1f77bcf86cd799439011'
+```
+
+**Finding by ID:**
+```typescript
+// ✅ Use 'id' parameter
+const user = await app.findOne('users', '507f1f77bcf86cd799439011');
+console.log(user.id); // Always 'id', never '_id'
+```
+
+**Sorting by ID:**
+```typescript
+const query = {
+  sort: [['id', 'desc']]  // ✅ Use 'id' for sorting
+};
+const users = await app.find('users', query);
+```
+
+**Field Projection:**
+```typescript
+const query = {
+  fields: ['id', 'name', 'email']  // ✅ Use 'id' to select the ID field
+};
+const users = await app.find('users', query);
+// Results contain 'id', not '_id'
+```
+
+### Migration from Legacy Code
+
+If you have existing code using `_id`, you have two options:
+
+1. **Recommended: Migrate to `id`** for consistency across drivers:
+
+**Before (Legacy):**
+```typescript
+// ❌ Old way - inconsistent with SQL drivers
+const query = {
+  filters: [['_id', '=', '507f1f77bcf86cd799439011']],
+  sort: [['_id', 'desc']],
+  fields: ['_id', 'name']
+};
+```
+
+**After (Recommended):**
+```typescript
+// ✅ New way - consistent across all drivers
+const query = {
+  filters: [['id', '=', '507f1f77bcf86cd799439011']],
+  sort: [['id', 'desc']],
+  fields: ['id', 'name']
+};
+```
+
+2. **Backward Compatible Mode:** Continue using `_id` in queries (results still return `id`)
+
+The MongoDB driver **fully supports `_id` in filters, sorting, and field projections** for backward compatibility:
+
+```typescript
+// ✅ This works - backward compatible
+const query = {
+  filters: [['_id', '=', '507f1f77bcf86cd799439011']],
+  sort: [['_id', 'desc']],
+  fields: ['_id', 'name']
+};
+const users = await app.find('users', query);
+
+// Results ALWAYS use 'id' regardless of query field name
+console.log(users[0].id); // '507f1f77bcf86cd799439011'
+console.log(users[0]._id); // undefined
+```
+
+**Key Points:**
+- Queries accept both `id` and `_id` (automatically mapped to MongoDB's `_id`)
+- Results always return `id` field (never `_id`)
+- Using `id` is recommended for database portability
+
+## ID Generation
+
+When creating documents without specifying an `id`, the driver automatically generates a string ID:
+
+```typescript
+const newUser = await app.create('users', {
+  name: 'Bob',
+  // No id specified
+});
+
+// Driver generates a unique string ID (not ObjectId)
+console.log(newUser.id); // e.g., '507f1f77bcf86cd799439011'
+```
+
+The generated IDs are hexadecimal strings (24 characters) that maintain MongoDB's uniqueness guarantees without using ObjectId objects.
+
+## Limitations
+
+*   **Joins**: While MongoDB supports `$lookup` (which this driver uses for joins), complex relationships across many collections can be slower than SQL.
+*   **Transactions**: Transactions are supported but require a MongoDB Replica Set deployment.
diff --git a/docs/guide/drivers/sql.md b/docs/guide/drivers/sql.md
new file mode 100644
index 00000000..21d4260f
--- /dev/null
+++ b/docs/guide/drivers/sql.md
@@ -0,0 +1,127 @@
+# SQL Driver (Knex)
+
+The SQL driver implementation is based on [Knex.js](https://knexjs.org/), a powerful SQL query builder. It supports all major SQL databases including PostgreSQL, MySQL, SQLite3, and SQL Server.
+
+## Installation
+
+```bash
+npm install @objectql/driver-sql knex pg
+# Replace 'pg' with 'mysql', 'sqlite3', or 'mssql' depending on your database.
+```
+
+## Configuration
+
+The `SqlDriver` constructor accepts the standard [Knex configuration object](https://knexjs.org/guide/#configuration-options).
+
+```typescript
+import { SqlDriver } from '@objectql/driver-sql';
+
+const driver = new SqlDriver({
+  client: 'pg', // 'mysql', 'sqlite3', etc.
+  connection: {
+    host: '127.0.0.1',
+    port: 5432,
+    user: 'your_user',
+    password: 'your_password',
+    database: 'your_app_db'
+  },
+  // Optional: Connection pool settings
+  pool: { min: 2, max: 10 }
+});
+```
+
+### SQLite Example
+
+For local development or testing with SQLite:
+
+```typescript
+const driver = new SqlDriver({
+  client: 'sqlite3',
+  connection: {
+    filename: './local.db'
+  },
+  useNullAsDefault: true // Required for SQLite support
+});
+```
+
+## Unified ID Field
+
+ObjectQL uses **`id`** as the primary key field name across all SQL databases for consistency with the MongoDB driver.
+
+### How It Works
+
+- **Database Column**: SQL tables use `id` as the primary key column (VARCHAR/TEXT type)
+- **API Level**: You use `id` in your queries, filters, and documents
+- **Consistency**: Same API as MongoDB driver - no need to remember `_id` vs `id`
+
+### Examples
+
+**Table Schema:**
+```sql
+CREATE TABLE users (
+  id VARCHAR(255) PRIMARY KEY,  -- Primary key is 'id'
+  name VARCHAR(255),
+  email VARCHAR(255),
+  created_at TIMESTAMP,
+  updated_at TIMESTAMP
+);
+```
+
+**Creating Documents:**
+```typescript
+// Create with auto-generated ID
+const user = await app.create('users', {
+  name: 'Alice',
+  email: 'alice@example.com'
+});
+console.log(user.id); // Auto-generated UUID or custom ID
+
+// Create with custom ID
+const user = await app.create('users', {
+  id: 'custom-user-123',
+  name: 'Bob'
+});
+```
+
+**Querying by ID:**
+```typescript
+const query = {
+  filters: [['id', '=', 'custom-user-123']]
+};
+const users = await app.find('users', query);
+```
+
+**Finding by ID:**
+```typescript
+const user = await app.findOne('users', 'custom-user-123');
+```
+
+### Legacy `_id` Support
+
+For backward compatibility, if you provide `_id` in a create operation, the driver will automatically map it to `id`:
+
+```typescript
+// Legacy code - automatically mapped
+const user = await app.create('users', {
+  _id: 'user-123',  // Mapped to 'id' internally
+  name: 'Charlie'
+});
+
+console.log(user.id); // 'user-123'
+```
+
+This ensures smooth migration for projects that previously used MongoDB-style `_id` fields.
+
+## Schema Mapping
+
+The driver automatically maps ObjectQL types to SQL column types:
+
+| ObjectQL Type | SQL Type | Notes |
+| :--- | :--- | :--- |
+| `text` | `VARCHAR(255)` | |
+| `textarea` | `TEXT` | |
+| `boolean` | `BOOLEAN` | or `TINYINT` in MySQL |
+| `number` | `FLOAT` / `DECIMAL` | |
+| `date` | `DATE` | |
+| `datetime` | `TIMESTAMP` | |
+| `json` | `JSON` | or `TEXT` if not supported |
diff --git a/docs/guide/formulas-and-rules-quick-ref.md b/docs/guide/formulas-and-rules-quick-ref.md
new file mode 100644
index 00000000..bd152a95
--- /dev/null
+++ b/docs/guide/formulas-and-rules-quick-ref.md
@@ -0,0 +1,275 @@
+# Formulas & Rules Quick Reference
+
+**Quick syntax reference for ObjectQL formulas and validation rules.**
+
+For complete documentation, see:
+- 📖 [English Guide](./formulas-and-rules.md)
+
+## Formula Syntax Quick Reference
+
+### Basic Formula
+
+```yaml
+calculated_field:
+  type: formula
+  expression: "field1 + field2"
+  data_type: number
+```
+
+### Common Patterns
+
+```yaml
+# Arithmetic
+profit:
+  type: formula
+  expression: "revenue - cost"
+  data_type: currency
+
+# String concatenation
+full_name:
+  type: formula
+  expression: "first_name + ' ' + last_name"
+  data_type: text
+
+# Conditional
+status_label:
+  type: formula
+  expression: "score > 80 ? 'High' : 'Low'"
+  data_type: text
+
+# Date math
+days_old:
+  type: formula
+  expression: "$today - created_date"
+  data_type: number
+
+# Lookup reference
+owner_email:
+  type: formula
+  expression: "project.owner.email"
+  data_type: text
+```
+
+### Special Variables
+
+| Variable | Example |
+|----------|---------|
+| `$today` | Current date |
+| `$now` | Current timestamp |
+| `$current_user.id` | Current user ID |
+| `$current_user.name` | Current user name |
+
+## Validation Rules Quick Reference
+
+### Field Validation
+
+```yaml
+# In object.yml
+fields:
+  email:
+    type: email
+    required: true
+    validation:
+      format: email
+      message: "Please enter a valid email"
+  
+  age:
+    type: number
+    validation:
+      min: 0
+      max: 150
+```
+
+### Cross-Field Validation
+
+```yaml
+# In project.validation.yml
+rules:
+  - name: valid_date_range
+    type: cross_field
+    rule:
+      field: end_date
+      operator: ">="
+      compare_to: start_date
+    message: "End date must be after start date"
+```
+
+### Conditional Validation
+
+```yaml
+rules:
+  - name: description_required_for_high_budget
+    type: conditional
+    condition:
+      field: budget
+      operator: ">"
+      value: 10000
+    rule:
+      field: description
+      operator: "not_empty"
+    message: "Description required for budgets over $10,000"
+```
+
+### State Machine
+
+```yaml
+rules:
+  - name: status_transition
+    type: state_machine
+    field: status
+    transitions:
+      draft:
+        allowed_next: [submitted, cancelled]
+      submitted:
+        allowed_next: [approved, rejected]
+      approved:
+        allowed_next: []
+        is_terminal: true
+```
+
+## Operators Quick Reference
+
+### Comparison
+
+| Operator | Example |
+|----------|---------|
+| `=` | `field: status, operator: "=", value: "active"` |
+| `!=` | `field: status, operator: "!=", value: null` |
+| `>` | `field: amount, operator: ">", value: 1000` |
+| `>=` | `field: end_date, operator: ">=", compare_to: start_date` |
+| `<` | `field: age, operator: "<", value: 18` |
+| `<=` | `field: discount, operator: "<=", value: 1` |
+| `in` | `field: status, operator: "in", value: ["active", "pending"]` |
+| `not_in` | `field: status, operator: "not_in", value: ["deleted"]` |
+| `contains` | `field: tags, operator: "contains", value: "urgent"` |
+| `not_empty` | `field: description, operator: "not_empty"` |
+
+### Logical
+
+```yaml
+# AND - all must be true
+condition:
+  all_of:
+    - field: status
+      operator: "="
+      value: active
+    - field: amount
+      operator: ">"
+      value: 1000
+
+# OR - any must be true
+condition:
+  any_of:
+    - field: priority
+      operator: "="
+      value: high
+    - field: amount
+      operator: ">"
+      value: 10000
+
+# NOT - must be false
+condition:
+  none_of:
+    - field: status
+      operator: "="
+      value: deleted
+```
+
+## Permission Rules Quick Reference
+
+```yaml
+# In project.permission.yml
+rules:
+  - name: owner_full_access
+    condition:
+      field: owner_id
+      operator: "="
+      value: $current_user.id
+    permissions:
+      read: true
+      create: true
+      update: true
+      delete: true
+```
+
+## Common Use Cases
+
+### Budget Validation
+
+```yaml
+rules:
+  - name: budget_approval_required
+    type: conditional
+    condition:
+      field: budget
+      operator: ">"
+      value: 50000
+    rule:
+      field: approved_by
+      operator: "not_empty"
+    message: "Budget over $50K requires approval"
+```
+
+### Date Range Validation
+
+```yaml
+rules:
+  - name: valid_date_range
+    type: cross_field
+    rule:
+      field: end_date
+      operator: ">="
+      compare_to: start_date
+    message: "End date must be after start date"
+```
+
+### Status Workflow
+
+```yaml
+rules:
+  - name: order_workflow
+    type: state_machine
+    field: status
+    transitions:
+      draft:
+        allowed_next: [submitted, cancelled]
+      submitted:
+        allowed_next: [approved, rejected]
+      approved:
+        allowed_next: [processing, cancelled]
+      processing:
+        allowed_next: [shipped, cancelled]
+      shipped:
+        allowed_next: [delivered]
+      delivered:
+        allowed_next: []  # terminal
+```
+
+### Calculated Metrics
+
+```yaml
+# Profit margin
+profit_margin:
+  type: formula
+  expression: "(revenue - cost) / revenue * 100"
+  data_type: percent
+
+# Days since creation
+age_days:
+  type: formula
+  expression: "$today - created_date"
+  data_type: number
+
+# Full address
+full_address:
+  type: formula
+  expression: "street + ', ' + city + ', ' + state + ' ' + zip"
+  data_type: text
+```
+
+## Related Docs
+
+- 📖 [Complete Formulas & Rules Guide](./formulas-and-rules.md)
+- 📖 [Object Definitions](../spec/object.md)
+- 📖 [Validation Spec](../spec/validation.md)
+- 📖 [Permission Spec](../spec/permission.md)
diff --git a/docs/guide/formulas-and-rules.md b/docs/guide/formulas-and-rules.md
new file mode 100644
index 00000000..f5da18dd
--- /dev/null
+++ b/docs/guide/formulas-and-rules.md
@@ -0,0 +1,690 @@
+# Formulas and Rules Syntax Guide
+
+This guide covers the complete syntax for formulas and validation rules in ObjectQL. Understanding these patterns will help you create powerful calculated fields and enforce business rules.
+
+## Table of Contents
+
+1. [Formula Syntax](#formula-syntax)
+2. [Validation Rule Syntax](#validation-rule-syntax)
+3. [Permission Rule Syntax](#permission-rule-syntax)
+4. [Expression Evaluation](#expression-evaluation)
+5. [Common Operators](#common-operators)
+6. [Best Practices](#best-practices)
+
+## Formula Syntax
+
+Formulas are used to create calculated fields that derive their values from other fields or expressions. They are read-only and automatically computed.
+
+### Basic Formula Structure
+
+```yaml
+fields:
+  field_name:
+    type: formula
+    expression: "field1 + field2"
+    data_type: number  # Result type: number, text, date, boolean
+```
+
+### Expression Syntax
+
+ObjectQL formulas use **JavaScript-style expressions** with field references:
+
+#### Field References
+
+```yaml
+# Simple field reference - use field name directly
+calc_total:
+  type: formula
+  expression: "price * quantity"
+  data_type: number
+
+# With curly braces (alternative syntax)
+calc_total_alt:
+  type: formula
+  expression: "{price} * {quantity}"
+  data_type: number
+```
+
+#### Arithmetic Operations
+
+```yaml
+# Addition
+profit:
+  type: formula
+  expression: "revenue - cost"
+  data_type: currency
+
+# Multiplication
+area:
+  type: formula
+  expression: "width * height"
+  data_type: number
+
+# Division
+average_score:
+  type: formula
+  expression: "total_score / num_attempts"
+  data_type: number
+
+# Percentage
+profit_margin:
+  type: formula
+  expression: "(revenue - cost) / revenue * 100"
+  data_type: percent
+```
+
+#### String Operations
+
+```yaml
+# Concatenation
+full_name:
+  type: formula
+  expression: "first_name + ' ' + last_name"
+  data_type: text
+
+# String methods
+uppercase_name:
+  type: formula
+  expression: "name.toUpperCase()"
+  data_type: text
+```
+
+#### Date Calculations
+
+```yaml
+# Date difference
+days_open:
+  type: formula
+  expression: "$today - created_date"
+  data_type: number
+
+# Date comparison
+is_overdue:
+  type: formula
+  expression: "due_date < $today && status != 'completed'"
+  data_type: boolean
+```
+
+#### Conditional Formulas
+
+```yaml
+# Simple if/else
+priority_label:
+  type: formula
+  expression: "score > 80 ? 'High' : 'Low'"
+  data_type: text
+
+# Multi-condition
+status_category:
+  type: formula
+  expression: |
+    if (amount > 10000) {
+      return 'High Value';
+    } else if (amount > 1000) {
+      return 'Medium Value';
+    } else {
+      return 'Low Value';
+    }
+  data_type: text
+```
+
+#### Lookup Field References
+
+```yaml
+# Access related object fields using dot notation
+account_owner_name:
+  type: formula
+  expression: "customer.account.owner.name"
+  data_type: text
+
+# Nested lookups
+region_manager:
+  type: formula
+  expression: "account.region.manager.email"
+  data_type: text
+```
+
+### Special Variables
+
+| Variable | Description | Example |
+|----------|-------------|---------|
+| `$today` | Current date (YYYY-MM-DD) | `$today - created_date` |
+| `$now` | Current timestamp | `$now` |
+| `$current_user.id` | Current user ID | `owner_id == $current_user.id` |
+| `$current_user.name` | Current user name | `$current_user.name` |
+
+### Formula Examples
+
+#### Revenue Calculations
+
+```yaml
+# Simple profit
+profit:
+  type: formula
+  expression: "revenue - cost"
+  data_type: currency
+
+# Profit margin percentage
+profit_margin:
+  type: formula
+  expression: "(revenue - cost) / revenue * 100"
+  data_type: percent
+
+# Discounted price
+final_price:
+  type: formula
+  expression: "list_price * (1 - discount_rate)"
+  data_type: currency
+```
+
+#### Date & Time
+
+```yaml
+# Age calculation
+days_since_created:
+  type: formula
+  expression: "$today - created_date"
+  data_type: number
+
+# Is expired
+is_expired:
+  type: formula
+  expression: "expiration_date < $today"
+  data_type: boolean
+
+# Duration
+project_duration_days:
+  type: formula
+  expression: "end_date - start_date"
+  data_type: number
+```
+
+#### Status & Categorization
+
+```yaml
+# Risk level based on multiple factors
+risk_level:
+  type: formula
+  expression: |
+    if (amount > 100000 && customer.credit_score < 600) {
+      return 'High Risk';
+    } else if (amount > 50000 || customer.credit_score < 700) {
+      return 'Medium Risk';
+    } else {
+      return 'Low Risk';
+    }
+  data_type: text
+
+# Priority score
+priority_score:
+  type: formula
+  expression: |
+    (urgency_level * 0.4) + 
+    (impact_level * 0.4) + 
+    (customer_tier * 0.2)
+  data_type: number
+```
+
+## Validation Rule Syntax
+
+Validation rules enforce data quality and business logic. They can be simple field checks or complex cross-field validations.
+
+### Rule Types
+
+ObjectQL supports several types of validation rules:
+
+1. **Field Validation** - Single field constraints
+2. **Cross-Field Validation** - Compare multiple fields
+3. **Conditional Validation** - Apply rules based on conditions
+4. **State Machine** - Enforce state transitions
+5. **Business Rule** - Complex business logic
+6. **Custom Validation** - JavaScript functions
+
+### Field Validation
+
+Defined directly in field configuration:
+
+```yaml
+# In object.yml
+fields:
+  email:
+    type: email
+    required: true
+    validation:
+      format: email
+      message: "Please enter a valid email address"
+  
+  age:
+    type: number
+    validation:
+      min: 0
+      max: 150
+      message: "Age must be between 0 and 150"
+  
+  username:
+    type: text
+    required: true
+    validation:
+      min_length: 3
+      max_length: 20
+      pattern: "^[a-zA-Z0-9_]+$"
+      message: "Username must be 3-20 alphanumeric characters"
+```
+
+### Cross-Field Validation
+
+Compare values between multiple fields:
+
+```yaml
+# In project.validation.yml
+rules:
+  - name: valid_date_range
+    type: cross_field
+    rule:
+      field: end_date
+      operator: ">="
+      compare_to: start_date
+    message: "End date must be on or after start date"
+    error_code: "INVALID_DATE_RANGE"
+```
+
+#### Supported Operators
+
+| Operator | Description | Example |
+|----------|-------------|---------|
+| `=` | Equals | `field: status, operator: "=", value: "active"` |
+| `!=` | Not equals | `field: status, operator: "!=", value: null` |
+| `>` | Greater than | `field: end_date, operator: ">", compare_to: start_date` |
+| `>=` | Greater than or equal | `field: budget, operator: ">=", value: 0` |
+| `<` | Less than | `field: age, operator: "<", value: 18` |
+| `<=` | Less than or equal | `field: discount, operator: "<=", value: 1` |
+| `in` | In array | `field: status, operator: "in", value: ["active", "pending"]` |
+| `not_in` | Not in array | `field: status, operator: "not_in", value: ["deleted"]` |
+| `contains` | String/array contains | `field: tags, operator: "contains", value: "urgent"` |
+| `not_empty` | Field is not empty | `field: description, operator: "not_empty"` |
+
+### Conditional Validation
+
+Apply validation only when certain conditions are met:
+
+```yaml
+rules:
+  - name: description_required_for_high_budget
+    type: conditional
+    description: "Description is required for high budget projects"
+    condition:
+      field: budget
+      operator: ">"
+      value: 10000
+    rule:
+      field: description
+      operator: "not_empty"
+    message: "Description is required for projects over $10,000"
+```
+
+### State Machine Validation
+
+Enforce valid state transitions:
+
+```yaml
+rules:
+  - name: status_transition
+    type: state_machine
+    field: status
+    transitions:
+      planning:
+        allowed_next: [active, cancelled]
+      active:
+        allowed_next: [on_hold, completed, cancelled]
+      on_hold:
+        allowed_next: [active, cancelled]
+      completed:
+        allowed_next: []
+        is_terminal: true
+      cancelled:
+        allowed_next: []
+        is_terminal: true
+    message: "Invalid status transition from {{old_status}} to {{new_status}}"
+    error_code: "INVALID_STATE_TRANSITION"
+```
+
+### Business Rule Validation
+
+Complex business logic with multiple conditions:
+
+```yaml
+rules:
+  - name: budget_within_limits
+    type: business_rule
+    constraint:
+      expression: "budget <= department.budget_limit OR executive_approval = true"
+      relationships:
+        department:
+          via: department_id
+          fields: [budget_limit]
+    message: "Budget exceeds department limit. Executive approval required."
+    error_code: "BUDGET_LIMIT_EXCEEDED"
+    trigger: [create, update]
+    fields: [budget, department_id, executive_approval]
+```
+
+### Custom Validation
+
+JavaScript validation functions for complex logic:
+
+```yaml
+rules:
+  - name: credit_check
+    type: custom
+    message: "Customer credit limit exceeded"
+    error_code: "CREDIT_LIMIT_EXCEEDED"
+    trigger: [create, update]
+    fields: [amount, customer_id]
+    validator: |
+      async function validate(record, context) {
+        const customer = await context.api.findOne('customers', record.customer_id);
+        const totalOrders = await context.api.sum('orders', 'amount', [
+          ['customer_id', '=', record.customer_id],
+          ['status', 'in', ['pending', 'processing']]
+        ]);
+        
+        return (totalOrders + record.amount) <= customer.credit_limit;
+      }
+```
+
+## Permission Rule Syntax
+
+Permission rules control data access based on user roles and record conditions.
+
+### Basic Permission Rules
+
+```yaml
+# In project.permission.yml
+rules:
+  - name: owner_full_access
+    description: "Record owner has full access"
+    priority: 10
+    condition:
+      field: owner_id
+      operator: "="
+      value: $current_user.id
+    permissions:
+      read: true
+      create: true
+      update: true
+      delete: true
+```
+
+### Complex Conditions
+
+```yaml
+rules:
+  - name: public_approved_read_only
+    description: "Public approved records are read-only"
+    condition:
+      all_of:
+        - field: status
+          operator: "="
+          value: approved
+        - field: is_public
+          operator: "="
+          value: true
+    permissions:
+      read: true
+      update: false
+      delete: false
+```
+
+### Conditional Operators
+
+| Operator | Description |
+|----------|-------------|
+| `all_of` | All conditions must be true (AND) |
+| `any_of` | Any condition must be true (OR) |
+| `none_of` | No conditions can be true (NOT) |
+
+## Expression Evaluation
+
+### Expression Context
+
+When expressions are evaluated, they have access to:
+
+1. **Record Fields** - Current record data
+2. **Related Records** - Via lookup/master-detail relationships
+3. **System Variables** - `$today`, `$now`, `$current_user`
+4. **Previous Values** - For update operations (in validation)
+
+### Evaluation Order
+
+1. Field-level validations (required, format, range)
+2. Cross-field validations
+3. Business rule validations
+4. Custom validations
+5. State machine validations
+
+### Error Handling
+
+```yaml
+rules:
+  - name: safe_division
+    type: custom
+    validator: |
+      function validate(record) {
+        if (record.denominator === 0) {
+          return false;
+        }
+        return (record.numerator / record.denominator) < 100;
+      }
+    message: "Result must be less than 100 (division by zero not allowed)"
+```
+
+## Common Operators
+
+### Comparison Operators
+
+```javascript
+// Equality
+field = value
+field != value
+
+// Numerical comparison
+field > value
+field >= value
+field < value
+field <= value
+
+// Set membership
+field in [value1, value2, value3]
+field not_in [value1, value2]
+
+// String operations
+field contains "substring"
+field starts_with "prefix"
+field ends_with "suffix"
+
+// Existence
+field is_null
+field is_not_null
+field not_empty
+```
+
+### Logical Operators
+
+```yaml
+# AND - All conditions must be true
+condition:
+  all_of:
+    - field: status
+      operator: "="
+      value: active
+    - field: budget
+      operator: ">"
+      value: 1000
+
+# OR - At least one condition must be true
+condition:
+  any_of:
+    - field: priority
+      operator: "="
+      value: high
+    - field: amount
+      operator: ">"
+      value: 10000
+
+# NOT - Condition must be false
+condition:
+  none_of:
+    - field: status
+      operator: "="
+      value: deleted
+```
+
+### Array Filters
+
+Used in query language for filtering records:
+
+```javascript
+// Basic filter - [field, operator, value]
+["status", "=", "active"]
+
+// Multiple filters with AND
+[
+  ["status", "=", "active"],
+  "and",
+  ["amount", ">", 1000]
+]
+
+// Multiple filters with OR
+[
+  ["priority", "=", "high"],
+  "or",
+  ["amount", ">", 50000]
+]
+
+// Complex nested conditions
+[
+  ["status", "=", "active"],
+  "and",
+  [
+    ["priority", "=", "high"],
+    "or",
+    ["amount", ">", 10000]
+  ]
+]
+```
+
+## Best Practices
+
+### Formula Best Practices
+
+1. **Keep formulas simple** - Complex logic should be in hooks or actions
+2. **Use appropriate data types** - Specify correct `data_type` for the result
+3. **Handle null values** - Use conditional checks for optional fields
+4. **Document complex formulas** - Add comments explaining business logic
+5. **Test edge cases** - Verify division by zero, null values, etc.
+
+```yaml
+# Good - Simple and clear
+discount_amount:
+  type: formula
+  expression: "list_price * discount_rate"
+  data_type: currency
+
+# Good - Handles null
+full_name:
+  type: formula
+  expression: "(first_name || '') + ' ' + (last_name || '')"
+  data_type: text
+
+# Avoid - Too complex for a formula
+complex_score:
+  type: formula
+  expression: |
+    var base = weight * coefficient;
+    for (var i = 0; i < iterations; i++) {
+      base = base * (1 + rate);
+    }
+    return base;
+  data_type: number
+  # Better: Move to a hook or action
+```
+
+### Validation Rule Best Practices
+
+1. **Use declarative rules when possible** - Prefer `cross_field` over `custom`
+2. **Provide clear error messages** - Help users understand what's wrong
+3. **Set appropriate severity** - Use `error`, `warning`, or `info`
+4. **Order rules by likelihood of failure** - Fast-fail optimization
+5. **Use AI context** - Help AI tools understand business intent
+
+```yaml
+# Good - Clear message and intent
+rules:
+  - name: valid_date_range
+    type: cross_field
+    ai_context:
+      intent: "Ensure timeline is logical"
+      business_rule: "Projects cannot end before they start"
+    rule:
+      field: end_date
+      operator: ">="
+      compare_to: start_date
+    message: "End date must be on or after start date"
+    severity: error
+
+# Good - Conditional validation
+  - name: approval_required_for_high_value
+    type: conditional
+    condition:
+      field: amount
+      operator: ">"
+      value: 50000
+    rule:
+      field: approved_by
+      operator: "not_empty"
+    message: "Approval required for transactions over $50,000"
+    severity: error
+```
+
+### Performance Optimization
+
+1. **Minimize async validations** - They slow down operations
+2. **Use indexes** - For fields used in validation lookups
+3. **Cache validation results** - When appropriate
+4. **Batch validation** - For bulk operations
+
+```yaml
+rules:
+  - name: inventory_check
+    type: custom
+    batch_enabled: true
+    batch_size: 100
+    validator: |
+      async function validateBatch(records, context) {
+        const skus = records.map(r => r.sku);
+        const inventory = await context.api.find('inventory', {
+          filters: [['sku', 'in', skus]]
+        });
+        
+        return records.map(record => {
+          const inv = inventory.find(i => i.sku === record.sku);
+          return inv && inv.available_quantity >= record.quantity;
+        });
+      }
+```
+
+## Related Documentation
+
+- [Object Definition](../spec/object.md) - Complete object metadata reference
+- [Validation Rules](../spec/validation.md) - Detailed validation specification
+- [Permission Rules](../spec/permission.md) - Access control documentation
+- [Query Language](../spec/query-language.md) - Query syntax and filters
+- [Hooks & Actions](./logic-hooks.md) - Custom business logic
+
+## Examples
+
+For working examples, see:
+
+- `/packages/starters/basic/src/modules/projects/` - Project validation examples
+- `/packages/starters/enterprise/src/modules/crm/` - CRM business rules
+- `/examples/tutorials/` - Tutorial projects with formulas and rules
diff --git a/docs/guide/getting-started.md b/docs/guide/getting-started.md
new file mode 100644
index 00000000..29e2204b
--- /dev/null
+++ b/docs/guide/getting-started.md
@@ -0,0 +1,158 @@
+# Getting Started with ObjectQL
+
+**ObjectQL** is a universal, metadata-driven ORM designed for building dynamic business applications. Unlike traditional ORMs where you define schema in class files (like TypeORM entities), ObjectQL uses a **Metadata-First** approach.
+
+## Why ObjectQL?
+
+1.  **Metadata-Driven**: Define your data models in JSON or YAML. Perfect for low-code platforms where schema changes at runtime.
+2.  **Universal Protocol**: The query language is a JSON AST, making it easy for frontends or AI agents to generate queries.
+3.  **Action & Hook System**: Built-in support for "Button Actions" (RPC) and "Triggers" (Hooks), allowing you to model **Behavior** alongside **Data**.
+
+## Quick Start: The "Hello World"
+
+You can experience ObjectQL with a single file. No YAML, no complex config.
+
+### 1. Minimal Setup
+
+Install the core and SQLite driver (for zero-config database).
+
+```bash
+npm install @objectql/core @objectql/driver-sql sqlite3
+# or
+pnpm add @objectql/core @objectql/driver-sql sqlite3
+```
+
+### 2. The Universal Script
+
+Create `index.ts`. This script defines the schema, boots the engine, and runs queries in one go.
+
+```typescript
+import { ObjectQL } from '@objectql/core';
+import { SqlDriver } from '@objectql/driver-sql';
+
+async function main() {
+  // 1. Initialize Driver (In-Memory SQLite)
+  const driver = new SqlDriver({
+    client: 'sqlite3',
+    connection: { filename: ':memory:' }, 
+    useNullAsDefault: true
+  });
+
+  // 2. Initialize Engine
+  const app = new ObjectQL({
+    datasources: { default: driver }
+  });
+
+  // 3. Define Metadata Inline (Code as Configuration)
+  app.registerObject({
+    name: 'todo',
+    fields: {
+      title: { type: 'text', required: true },
+      completed: { type: 'boolean', defaultValue: false }
+    }
+  });
+
+  await app.init();
+
+  // 4. Run Business Logic
+  // We use a system context here for simplicity
+  const ctx = app.createContext({ isSystem: true });
+  const repo = ctx.object('todo');
+
+  await repo.create({ title: 'Build the Future' });
+  
+  const results = await repo.find();
+  console.log('Todos:', results);
+}
+
+main();
+```
+
+## Scaling Up: The Metadata Approach
+
+Once you are comfortable with the core, you should move your definitions to YAML files.
+
+```typescript
+import { ObjectQL } from '@objectql/core';
+import * as path from 'path';
+
+async function main() {
+    const db = new ObjectQL({
+        // 1. Connection String (Protocol://Path)
+        // Detects 'sqlite', 'postgres', 'mongodb' automatically
+        connection: 'sqlite://data.db', 
+        
+        // 2. Schema Source
+        // Where your *.object.yml files are located
+        source: ['src/objects'],
+
+        // 3. Load Presets (Optional)
+        // Load standard objects from npm packages
+        presets: ['@objectql/preset-auth']
+    });
+
+    await db.init();
+    
+    // ...
+    
+    // 3. Create Data (CRUD)
+    // Create a context (representing a user request)
+    const ctx = db.createContext({}); 
+    const todoRepo = ctx.object('todo');
+
+    const newTask = await todoRepo.create({
+        title: 'Learn ObjectQL',
+        completed: false
+    });
+    console.log('Created:', newTask);
+
+    // 4. Query Data
+    const tasks = await todoRepo.find({
+        filters: [['completed', '=', false]]
+    });
+    console.log('Pending Tasks:', tasks);
+}
+
+main();
+```
+
+## Adding Business Logic
+
+ObjectQL shines when you need to add logic.
+
+### Adding a Hook
+
+Triggers logic automatically when data changes.
+
+```typescript
+app.on('beforeCreate', 'todo', async (ctx) => {
+    if (ctx.doc.title === 'Sleep') {
+        throw new Error("Cannot sleep yet!");
+    }
+    // Auto-tagging
+    ctx.doc.title = `[Task] ${ctx.doc.title}`;
+});
+```
+
+### Adding an Action
+
+Defines a custom operation (RPC) that frontends can call.
+
+```typescript
+// Define protocol
+app.registerAction('todo', 'mark_done', async (ctx) => {
+    const { id } = ctx;
+    await ctx.object('todo').update(id, { completed: true });
+    return { message: 'Good job!' };
+});
+
+// Invocation
+await ctx.object('todo').execute('mark_done', 'id_123', {});
+```
+
+## Next Steps
+
+*   **[Database Drivers](./drivers/index.md)**: Connect to PostgreSQL, MongoDB, etc.
+*   **[Data Modeling](./data-modeling.md)**: Learn about all field types (Select, Lookup, Date, etc.)
+*   **[SDK Reference](./sdk-reference.md)**: Explore the full API.
+*   **[Hooks](./logic-hooks.md)**: Deep dive into the event system.
diff --git a/docs/guide/ide-setup.md b/docs/guide/ide-setup.md
new file mode 100644
index 00000000..29ff0edb
--- /dev/null
+++ b/docs/guide/ide-setup.md
@@ -0,0 +1,24 @@
+# IDE Setup
+
+To get the best experience developing with ObjectQL, we recommend Visual Studio Code with the following configuration.
+
+## Visual Studio Code
+
+We recommend using [VS Code](https://code.visualstudio.com/) as your primary editor.
+
+### Recommended Extensions
+
+**1. YAML (Red Hat)**  
+Essential for editing `*.object.yml` files. It provides syntax highlighting and validation.  
+[Install Extension](https://marketplace.visualstudio.com/items?itemName=redhat.vscode-yaml)
+
+**2. JSON (Official)**  
+For editing configuration files.
+
+## AI Assistant Configuration
+
+ObjectQL is designed to be "AI-Native". The most efficient way to write schema and hooks is by pairing with an LLM.
+
+We strongly recommend configuring your AI Coding Assistant (GitHub Copilot, Cursor, Windsurf) with our specialized System Prompts. These prompts teach the AI about ObjectQL's metadata protocol.
+
+[👉 Go to AI Coding Assistant Guide](/ai/coding-assistant)
diff --git a/docs/guide/index.md b/docs/guide/index.md
new file mode 100644
index 00000000..351f39d0
--- /dev/null
+++ b/docs/guide/index.md
@@ -0,0 +1,69 @@
+# Introduction
+
+**ObjectQL** is a protocol-first application engine. It rethinks backend development by treating everything—Data Models, Queries, and Logic—as **structured data** rather than code strings.
+
+## The Core Philosophy
+
+### 1. The JSON Protocol
+In traditional development, you write SQL strings (`SELECT * FROM users`) or use fluent builders (`db.select('users')`).
+In ObjectQL, the query **IS** the data structure.
+
+```json
+// Find users where age > 18
+{
+  "op": "find",
+  "object": "user",
+  "args": {
+    "filters": [["age", ">", 18]]
+  }
+}
+```
+
+This makes the protocol:
+*   **Universal**: Can be generated by any client (JS, Python, Swift, or LLMs).
+*   **Serialization-ready**: Pass it over HTTP, WebSocket, or save it to a file.
+*   **Secure**: Zero SQL injection risk by design.
+
+### 2. Metadata as Source of Truth
+Instead of defining TypeScript classes or SQL DDL, you define your business domain in declarative YAML.
+
+```yaml
+# user.object.yml
+name: user
+fields:
+  email: { type: email, unique: true }
+  role: { type: select, options: [admin, user] }
+```
+
+This metadata is loaded at runtime to:
+*   Auto-generate database schemas (tables/collections).
+*   Auto-generate TypeScript types.
+*   Auto-validate incoming requests.
+
+### 3. Logic as Graph
+Your application logic isn't hidden inside controller functions. It's attached to the Graph as **Hooks** and **Actions**.
+
+*   **Hook**: "When `user` is created, send email."
+*   **Action**: "Expose RPC `resetPassword` on `user`."
+
+## Why use ObjectQL?
+
+*   **For AI**: It demands structured input/output, which fits AI Agent capabilities perfectly.
+*   **For Low-Code**: The rigorous structure makes it easy to build UI visual editors on top of it.
+*   **For Microservices**: The federation protocol allows you to stitch multiple services into one graph instantly.
+
+## 📡 API Access
+
+ObjectQL exposes your data through multiple API styles:
+
+*   **[Complete API Reference](../api/README.md)** - Comprehensive guide to all endpoints
+*   **[JSON-RPC API](../api/README.md#json-rpc-style-api)** - Universal protocol for all operations
+*   **[REST API](../api/README.md#rest-style-api)** - Traditional REST endpoints
+*   **[Metadata API](../api/README.md#metadata-api)** - Runtime schema discovery
+*   **[Authentication Guide](../api/authentication.md)** - Securing your APIs
+
+## Next Steps
+
+*   [**Getting Started**](./getting-started.md): Build your first ObjectQL app
+*   [**CLI Tool**](./cli.md): Using the command line interface for codegen
+*   [**API Reference**](../api/README.md): Complete API documentation
diff --git a/docs/guide/license.md b/docs/guide/license.md
new file mode 100644
index 00000000..de394337
--- /dev/null
+++ b/docs/guide/license.md
@@ -0,0 +1,64 @@
+# License
+
+ObjectQL is released under the **MIT License**.
+
+## About This License
+
+The MIT License is one of the most permissive and widely-used open source licenses. It:
+
+- ✅ **Allows** you to use, modify, and distribute the software freely
+- ✅ **Permits** commercial use without restrictions
+- ✅ **Enables** you to sublicense and use in proprietary software
+- ✅ **Requires** only that you include the copyright notice and license text
+- ✅ **Provides** no warranty (software is provided "as is")
+
+This license maximizes freedom while protecting the copyright holders from liability.
+
+## Full License Text
+
+The complete license text is available in the [LICENSE](https://github.com/objectql/objectql/blob/main/LICENSE) file in the repository.
+
+You can also view the official MIT License at:
+[https://opensource.org/licenses/MIT](https://opensource.org/licenses/MIT)
+
+## Key Points
+
+### What You Can Do
+
+- **Use** ObjectQL in your applications and projects (personal or commercial)
+- **Modify** the source code to fit your needs
+- **Distribute** copies of ObjectQL (with proper attribution)
+- **Sublicense** and incorporate into proprietary software
+- **Sell** products built with or based on ObjectQL
+- **Use** ObjectQL in competitive products
+
+### What You Must Do
+
+- **Include** the original copyright notice and license text when distributing the software
+- **Provide** attribution to ObjectQL Contributors
+
+### What the License Does Not Provide
+
+- **No warranty**: The software is provided "as is" without warranty of any kind
+- **No liability**: Authors are not liable for any claims or damages arising from use of the software
+
+### Important Notes
+
+1. **Attribution Required**: You must include the copyright notice and license text in all copies or substantial portions of the software
+2. **No Patent Grant**: Unlike some other licenses (e.g., Apache 2.0), the MIT License does not explicitly grant patent rights
+3. **Simple and Permissive**: One of the shortest and most permissive licenses available
+
+## Questions?
+
+If you have questions about the license or how it applies to your use case, please:
+
+- Open a [GitHub Discussion](https://github.com/objectql/objectql/discussions)
+- Review the official [Open Source Initiative documentation](https://opensource.org/licenses/MIT)
+
+## Copyright Notice
+
+```
+MIT License
+
+Copyright (c) 2026 ObjectQL Contributors (https://github.com/objectql)
+```
diff --git a/docs/guide/logic-actions.md b/docs/guide/logic-actions.md
new file mode 100644
index 00000000..9ed768be
--- /dev/null
+++ b/docs/guide/logic-actions.md
@@ -0,0 +1,199 @@
+# Logic: Actions (RPC)
+
+Actions (Remote Procedure Calls) allow you to define custom backend functions that go beyond simple CRUD. They are integrated into the metadata, meaning the Frontend knows exactly how to render them (buttons, confirmation dialogs, forms) and the Backend knows how to validate them.
+
+## 1. What is an Action?
+
+Unlike a Hook (which reacts to CRUD events), an **Action** is explicitly invoked by a user or a system.
+
+| Feature | Action | Hook |
+| :--- | :--- | :--- |
+| **Trigger** | Explicit (Button, API Call) | Implicit (Database Event) |
+| **Input** | Custom Arguments (`params`) | Database Record |
+| **Output** | Custom Result (JSON) | None (Void) |
+| **Use Case** | "Approve Invoice", "Sync LDAP" | "Validation", "Audit Log" |
+
+## 2. Defining Actions
+
+Actions require two parts:
+1.  **Declaration**: in `*.object.yml` (Defines the "Interface" & "UI").
+2.  **Implementation**: in `*.action.ts` (Defines the "Logic").
+
+### Step 1: Declare in YAML
+
+Define the action's signature in the Object file.
+
+```yaml
+# invoice.object.yml
+actions:
+  mark_paid:
+    type: record           # 'record' = acts on a specific row (needs ID)
+    label: Mark as Paid
+    icon: standard:money
+    confirm_text: "Are you sure? This will trigger a receipt email."
+    params:                # Input arguments (Schema)
+      note:
+        type: textarea
+        label: Payment Note
+        required: false
+      method:
+        type: select
+        options: [cash, card, transfer]
+        default: transfer
+
+  import_csv:
+    type: global           # 'global' = acts on the collection
+    label: Import Invoices
+    params:
+      file_url:
+        type: text
+```
+
+### Step 2: Implement in TypeScript
+
+Create a corresponding `.action.ts` file in the same directory.
+Use the `ActionDefinition` type for full type safety.
+
+```typescript
+// invoice.action.ts
+import { ActionDefinition } from '@objectql/types';
+// import { Invoice } from './types'; // generated types
+
+interface PayInput {
+    note?: string;
+    method: 'cash' | 'card' | 'transfer';
+}
+
+export const mark_paid: ActionDefinition<any, PayInput> = {
+    handler: async ({ id, input, api, user, objectName }) => {
+        // 1. Fetch current state
+        const invoice = await api.findOne(objectName, id);
+        if (!invoice) throw new Error("Invoice not found");
+        
+        if (invoice.status === 'Paid') {
+            throw new Error("Invoice is already paid.");
+        }
+
+        // 2. Perform updates
+        await api.update(objectName, id, {
+            status: 'Paid',
+            payment_method: input.method,
+            payment_note: input.note,
+            paid_by: user?.id,
+            paid_at: new Date()
+        });
+
+        // 3. Return result to UI
+        return { 
+            success: true, 
+            message: `Invoice #${invoice.code} marked as paid.` 
+        };
+    }
+};
+
+interface ImportInput {
+    file_url: string;
+}
+
+export const import_csv: ActionDefinition<any, ImportInput> = {
+    handler: async ({ input, api }) => {
+        // Logic to download CSV and parse it...
+        return { count: 100 };
+    }
+};
+```
+
+## 3. Action Context (`ctx`)
+
+The `handler` function receives a single context object with the following properties:
+
+| Property | Type | Description |
+| :--- | :--- | :--- |
+| `objectName` | `string` | The API name of the object (e.g., `invoice`). |
+| `actionName` | `string` | The API name of the action (e.g., `mark_paid`). |
+| `id` | `string \| number` | **(Record Actions only)** The ID of the target record. |
+| `input` | `T` | The validated arguments passed by the caller. |
+| `api` | `HookAPI` | Database API (`find`, `create`, `update`, `delete`, `count`). |
+| `user` | `object` | The current session user (contains `id`, `name`, etc.). |
+
+## 4. Parameter Types
+
+The `params` section in YAML supports the same types as Object Fields. This allows the Frontend to auto-generate beautiful forms.
+
+*   `text`, `textarea`, `number`, `boolean`, `date`, `datetime`
+*   `select` (Dropdown)
+*   `lookup` (Reference to another object)
+*   `file` (Attachment)
+
+**Example: Lookup Parameter**
+```yaml
+params:
+  assign_to:
+    type: lookup
+    reference: user
+    label: Assign To Staff
+```
+
+## 5. Invoking Actions
+
+### A. Via Server-Side Code (`app.executeAction`)
+
+You can call actions from other parts of your backend (e.g., Cron jobs, Webhooks).
+
+```typescript
+// Cron Job
+await app.executeAction('invoice', 'mark_paid', {
+    id: 'inv_123',
+    input: {
+        method: 'card', 
+        note: 'Auto-processed'
+    },
+    user: { id: 'system' } // Simulate a user
+});
+```
+
+### B. Via HTTP API (RPC)
+
+ObjectQL Server uses a unified RPC endpoint (typically mounted at `/api/objectql`).
+
+```http
+POST /api/objectql
+Content-Type: application/json
+
+{
+    "op": "action",
+    "object": "invoice",
+    "args": {
+        "action": "mark_paid",
+        "id": "inv_123",
+        "input": {
+            "method": "cash",
+            "note": "Paid at counter"
+        }
+    }
+}
+```
+
+> **Note on Versioning:** It is recommended to mount the ObjectQL handler under a versioned prefix like `/api/v1/objectql` in your Express/Node app to manage future breaking changes.
+
+### C. Via Frontend SDK
+
+```javascript
+// React / Client Code
+await objectql.action('invoice', 'mark_paid').call({
+    id: recordId,
+    input: { method: 'cash' }
+});
+```
+
+## 6. Transaction Safety
+
+By default, Actions are **NOT** automatically wrapped in a database transaction. If you need atomicity (all-or-nothing), you should manage it manually, or if using a driver that supports it, rely on the `api` methods which might share a transaction context if configured (though `HookAPI` is currently stateless).
+
+*Future versions of ObjectQL may introduce transactional decorators.*
+
+## 7. Best Practices
+
+1.  **Thin Controllers**: Keep your `.action.ts` handlers relatively thin. If the logic is complex, move it to a dedicated Service class.
+2.  **Input Validation**: Although ObjectQL checks types defined in YAML, always validate business rules (e.g., "Amount must be positive") inside the handler.
+3.  **Return JSON**: Always return a JSON serializable object. Do not return database cursors or complex class instances.
diff --git a/docs/guide/logic-hooks.md b/docs/guide/logic-hooks.md
new file mode 100644
index 00000000..c9108029
--- /dev/null
+++ b/docs/guide/logic-hooks.md
@@ -0,0 +1,184 @@
+# Logic Hooks
+
+Hooks (often called "Triggers" in SQL databases) allow you to intercept database operations to inject custom logic. They are transaction-aware and fully typed.
+
+## 1. Registration Methods
+
+You can define hooks in two ways: **File-based** (Static) or **Programmatic** (Dynamic).
+
+### A. File-based (Recommended)
+Place a `*.hook.ts` file next to your object definition. The loader automatically discovers it.
+
+**File:** `src/objects/project.hook.ts`
+
+```typescript
+import { ObjectHookDefinition } from '@objectql/types';
+
+const hooks: ObjectHookDefinition = {
+    beforeCreate: async (ctx) => {
+        // ...
+    },
+    afterUpdate: async (ctx) => {
+        // ...
+    }
+};
+
+export default hooks;
+```
+
+### B. Programmatic (Dynamic)
+Use the `app.on()` API, typically inside a [Plugin](./plugins.md).
+
+```typescript
+app.on('before:create', 'project', async (ctx) => {
+    // ...
+});
+
+// Wildcard listener
+app.on('after:delete', '*', async (ctx) => {
+    console.log(`Object ${ctx.objectName} deleted record ${ctx.id}`);
+});
+```
+
+## 2. Event Lifecycle
+
+| Event Name | Description | Common Use Case |
+| :--- | :--- | :--- |
+| `before:create` | Before inserting a new record. | Validation, Default Values, ID generation. |
+| `after:create` | After insertion is committed. | Notifications, downstream sync. |
+| `before:update` | Before modifying an existing record. | Permission checks, Immutable field protection. |
+| `after:update` | After modification is committed. | Audit logging, history tracking. |
+| `before:delete` | Before removing a record. | Referential integrity checks. |
+| `after:delete` | After removal is committed. | Clean up related resources (e.g. S3 files). |
+| `before:find` | Before executing a query. | **Row-Level Security (RLS)**, Force filters. |
+| `after:find` | After fetching results. | Decryption, Sensitive data masking. |
+
+## 3. The Hook Context
+
+The context object (`ctx`) changes based on the event type.
+
+### Common Properties (Available Everywhere)
+
+| Property | Type | Description |
+| :--- | :--- | :--- |
+| `objectName` | `string` | The name of the object being operated on. |
+| `user` | `ObjectQLUser` | Current user session/context. |
+| `broker` | `IStation` | (If Microservices enabled) Station broker instance. |
+
+### Mutation Context (Create/Update/Delete)
+
+| Property | Type | Available In | Description |
+| :--- | :--- | :--- | :--- |
+| `data` | `Any` | Create/Update | The data payload being written. **Mutable**. |
+| `id` | `string` | Update/Delete | The ID of the record being acted upon. |
+| `previousData` | `Any` | Update/Delete | The existing record fetched from DB before operation. |
+| `result` | `Any` | After * | The final result returned from the driver. |
+
+### Query Context (Find)
+
+| Property | Type | Description |
+| :--- | :--- | :--- |
+| `query` | `steedos-filters` | The query AST (filters, fields, sort). **Mutable**. |
+| `result` | `Any[]` | (After Find) The array of records found. **Mutable**. |
+
+## 4. Common Patterns & Examples
+
+### A. Validation & Default Values
+Throwing an error inside a `before` hook aborts the transaction.
+
+```typescript
+beforeCreate: async ({ data, user }) => {
+    if (data.amount < 0) {
+        throw new Error("Amount cannot be negative");
+    }
+    // Set default owner if not provided
+    if (!data.owner) {
+        data.owner = user.userId;
+    }
+}
+```
+
+### B. Immutable Fields Protection
+Prevent users from changing critical fields during update.
+
+```typescript
+beforeUpdate: async ({ data, previousData }) => {
+    if (data.code !== undefined && data.code !== previousData.code) {
+        throw new Error("Cannot change project code once created.");
+    }
+}
+```
+
+### C. Row-Level Security (RLS)
+The most secure place to enforce permissions is `before:find`. This injects filters into *every* query (API, GraphQL, or internal).
+
+```typescript
+beforeFind: async ({ query, user }) => {
+    if (!user.is_admin) {
+        // Enforce: owners can only see their own records
+        // Merging into existing filters
+        query.filters = [
+            (query.filters || []), 
+            ['owner', '=', user.userId]
+        ];
+    }
+}
+```
+
+### D. Side Effects (Notifications)
+Use `after` hooks for logic that strictly relies on success.
+
+```typescript
+afterCreate: async ({ data, objectName }) => {
+    await NotificationService.send({
+        to: data.owner,
+        message: `New ${objectName} created.`
+    });
+}
+```
+
+### E. Result Masking
+Hide sensitive fields based on rules.
+
+```typescript
+afterFind: async ({ result, user }) => {
+    if (!user.has_permission('view_salary')) {
+        result.forEach(record => {
+            delete record.salary;
+            delete record.bonus;
+        });
+    }
+}
+```
+
+### F. Auto-Numbering / ID Generation
+Generate complex business keys.
+
+```typescript
+beforeCreate: async ({ data }) => {
+    if (!data.code) {
+        data.code = await SequenceService.next('PROJECT_CODE');
+    }
+}
+```
+
+### G. Conditional Deletion
+Use `previousData` in delete hooks to prevent deleting records based on their state.
+
+```typescript
+beforeDelete: async ({ previousData, user }) => {
+    // Prevent deletion if project is active
+    if (previousData.status === 'active') {
+         throw new Error("Cannot delete an active project. Archive it first.");
+    }
+}
+```
+
+## 5. Transaction Safety
+
+Hooks participate in the database transaction.
+*   If a `before` hook throws -> The DB operation is never executed.
+*   If the DB operation fails -> `after` hooks are never executed.
+*   If an `after` hook throws -> **The entire transaction rolls back** (including the DB write).
+
+> **Tip:** If you want a "Fire and Forget" action that shouldn't rollback the transaction (e.g. sending an email), wrap your logic in a `try/catch` or execute it without `await`.
diff --git a/docs/guide/metadata-organization.md b/docs/guide/metadata-organization.md
new file mode 100644
index 00000000..299bd2e4
--- /dev/null
+++ b/docs/guide/metadata-organization.md
@@ -0,0 +1,365 @@
+# Organizing Metadata for Large Projects
+
+When building enterprise-scale applications with ObjectQL, proper metadata organization becomes critical. This guide demonstrates best practices for structuring your object definitions, actions, hooks, and translations in a maintainable way.
+
+## The Challenge
+
+As your application grows beyond 30-50 objects, a flat file structure becomes problematic:
+
+**Problems with Flat Structure:**
+```
+src/objects/
+├── user.object.yml
+├── organization.object.yml
+├── account.object.yml
+├── contact.object.yml
+├── opportunity.object.yml
+├── employee.object.yml
+├── department.object.yml
+├── invoice.object.yml
+├── payment.object.yml
+├── project.object.yml
+├── task.object.yml
+... (100+ files)
+```
+
+- ❌ Hard to find related objects
+- ❌ Merge conflicts when multiple teams work simultaneously
+- ❌ Unclear ownership boundaries
+- ❌ Can't deploy modules independently
+- ❌ Difficult to understand relationships
+
+## Recommended Structure: Domain-Driven Modules
+
+For applications with **30+ objects** and **multiple teams**, organize by business domain:
+
+```
+src/
+├── core/                    # Foundation objects (user, org, etc.)
+│   ├── objects/
+│   ├── i18n/
+│   └── index.ts
+│
+├── modules/                 # Business domain modules
+│   ├── crm/                # Customer management
+│   │   ├── objects/
+│   │   ├── actions/
+│   │   ├── hooks/
+│   │   ├── i18n/
+│   │   ├── README.md
+│   │   └── index.ts
+│   │
+│   ├── hr/                 # Human resources
+│   ├── finance/            # Finance & accounting
+│   └── project/            # Project management
+│
+├── extensions/             # Custom overrides
+├── shared/                 # Shared utilities
+└── index.ts               # Application entry
+```
+
+## Real-World Example
+
+See the complete working example at:
+```
+packages/starters/enterprise/
+```
+
+This demonstrates:
+- ✅ 20+ objects organized across 5 modules
+- ✅ Domain-driven structure (CRM, HR, Finance, Project)
+- ✅ Cross-module relationships
+- ✅ Extension pattern for customization
+- ✅ Comprehensive indexing strategy
+- ✅ Multi-language support (en, zh-CN)
+- ✅ Module documentation
+
+## Module Anatomy
+
+Each module follows a consistent pattern:
+
+```
+modules/[domain]/
+├── objects/              # Object definitions
+│   ├── [object1].object.yml
+│   └── [object2].object.yml
+├── actions/              # Custom actions
+│   └── [object1].action.ts
+├── hooks/                # Lifecycle hooks
+│   └── [object1].hooks.ts
+├── i18n/                 # Translations
+│   ├── en/
+│   └── zh-CN/
+├── README.md             # Module documentation
+└── index.ts              # Module exports
+```
+
+### Module Documentation Template
+
+Each module should have a README explaining:
+
+1. **Overview** - What business domain it covers
+2. **Objects** - List of objects with descriptions
+3. **Relationships** - How objects relate to each other
+4. **Team Ownership** - Who maintains this module
+5. **Dependencies** - What other modules/objects it depends on
+6. **Usage Examples** - Common query patterns
+
+## Object Naming Conventions
+
+### File-Based Naming
+
+**ObjectQL uses filename-based identification.** The object name is automatically inferred from the filename (without the `.object.yml` extension), eliminating redundancy.
+
+**Examples:**
+- `crm_account.object.yml` → Object name: `crm_account`
+- `finance_invoice.object.yml` → Object name: `finance_invoice`
+- `project_task.object.yml` → Object name: `project_task`
+
+Inside the file, you **no longer need** to specify `name: crm_account` - it's inferred from the filename!
+
+```yaml
+# File: crm_account.object.yml
+# Object name "crm_account" is automatically inferred!
+
+label: CRM Account
+fields:
+  company_name:
+    type: text
+    required: true
+```
+
+### Prefixing Strategy
+
+For large projects with multiple modules, use prefixes in your **filenames** to avoid name collisions:
+
+```
+# ✅ Good: Clear module ownership via filenames
+crm/objects/crm_account.object.yml       → Object: crm_account
+finance/objects/finance_invoice.object.yml → Object: finance_invoice
+project/objects/project_task.object.yml   → Object: project_task
+
+# ❌ Avoid: Risk of collision
+crm/objects/account.object.yml           → Object: account (ambiguous)
+finance/objects/account.object.yml       → Object: account (collision!)
+```
+
+**When to prefix:**
+- ✅ Multi-module applications (30+ objects)
+- ✅ Plugin architectures
+- ✅ When similar concepts exist across domains
+
+**When NOT to prefix:**
+- ❌ Core shared objects (`user.object.yml`, `organization.object.yml`)
+- ❌ Small applications (< 30 objects)
+- ❌ When it reduces clarity
+
+## Dependency Management
+
+### Dependency Layers
+
+```
+┌─────────────────────────────────┐
+│   Application Layer             │
+│   (modules/*)                   │
+│   - Can depend on Core          │
+│   - Can depend on other modules │
+└─────────────────────────────────┘
+           ↓
+┌─────────────────────────────────┐
+│   Foundation Layer              │
+│   (core/*)                      │
+│   - No dependencies             │
+│   - Used by everyone            │
+└─────────────────────────────────┘
+```
+
+### Cross-Module References
+
+When modules need to reference each other's objects:
+
+```yaml
+# In modules/finance/objects/invoice.object.yml
+fields:
+  account:
+    type: lookup
+    reference_to: crm_account  # Reference to CRM module
+```
+
+**Best Practices:**
+1. Document cross-module dependencies in module README
+2. Avoid circular dependencies
+3. Use core objects to break dependency cycles
+4. Consider extracting shared concepts to core layer
+
+## Index Strategy by Module
+
+Different modules have different performance requirements:
+
+### High-Traffic Modules (CRM, Sales)
+```yaml
+# Aggressive indexing
+fields:
+  status: { type: select, index: true }
+  owner: { type: lookup, index: true }
+  created_at: { type: datetime, index: true }
+
+indexes:
+  owner_status_idx: { fields: [owner, status] }
+  status_created_idx: { fields: [status, created_at] }
+```
+
+### Low-Traffic Modules (Admin, Config)
+```yaml
+# Minimal indexing
+fields:
+  name: { type: text, index: true }
+  status: { type: select, index: true }
+# Add more indexes only when needed
+```
+
+## Extension Pattern
+
+Use extensions to customize objects without modifying source files.
+
+**Original** (`core/objects/user.object.yml`):
+```yaml
+# File: user.object.yml
+# Object name "user" is inferred from filename
+
+fields:
+  name: { type: text }
+  email: { type: text }
+```
+
+**Extension** (`extensions/user.extension.object.yml`):
+```yaml
+# File: user.extension.object.yml
+# Extends the "user" object (matches by filename base)
+
+fields:
+  employee_id: { type: text }
+  email: { required: true, unique: true }
+```
+
+**Result:** ObjectQL merges both definitions, adding `employee_id` and making `email` required.
+
+## Internationalization at Scale
+
+### Three-Layer i18n Strategy
+
+```
+1. Core Layer (core/i18n/)
+   → Shared objects (user, organization)
+   
+2. Module Layer (modules/[domain]/i18n/)
+   → Domain-specific objects
+   
+3. Extension Layer (extensions/i18n/)
+   → Customer/regional customizations
+```
+
+### Directory Structure
+```
+core/i18n/
+  en/core.json
+  zh-CN/core.json
+
+modules/crm/i18n/
+  en/crm.json
+  zh-CN/crm.json
+```
+
+## Migration Path
+
+### From Flat to Modular
+
+**Step 1: Analyze**
+Group existing objects by business domain.
+
+**Step 2: Plan**
+Create module structure, decide on prefixes.
+
+**Step 3: Migrate Gradually**
+```
+src/
+├── objects/          # Legacy (keep temporarily)
+├── modules/          # New structure
+│   └── crm/          # Start with one module
+└── index.ts          # Loads from both
+```
+
+**Step 4: Update References**
+Update imports and references to use new module structure.
+
+**Step 5: Clean Up**
+Remove legacy flat structure once migration is complete.
+
+## Project Size Guidelines
+
+| Size | Objects | Teams | Recommended Structure |
+|------|---------|-------|----------------------|
+| **Small** | 1-30 | 1 | Flat `objects/` directory |
+| **Medium** | 30-100 | 2-3 | Domain modules |
+| **Large** | 100-500 | 5-10 | Modules + plugins |
+| **Enterprise** | 500+ | 10+ | Monorepo with packages |
+
+## Testing Strategy
+
+### Module Tests
+```typescript
+// modules/crm/__tests__/integration.test.ts
+describe('CRM Module', () => {
+  it('should handle lead conversion', async () => {
+    const lead = await createLead();
+    await convertLead(lead.id);
+    // Verify account, contact, opportunity created
+  });
+});
+```
+
+### Object Schema Tests
+```typescript
+// modules/crm/objects/__tests__/account.test.ts
+describe('Account Object', () => {
+  it('should have required fields', () => {
+    const schema = loadObjectSchema('crm_account');
+    expect(schema.fields.name.required).toBe(true);
+  });
+});
+```
+
+## Complete Working Example
+
+Explore the full example with 20+ objects:
+```bash
+cd packages/starters/enterprise
+pnpm install
+pnpm build
+```
+
+The example includes:
+- Core module (user, organization, attachment)
+- CRM module (account, contact, opportunity, lead)
+- HR module (employee, department, position, timesheet)
+- Finance module (invoice, payment, expense, budget)
+- Project module (project, task, milestone, timesheet entry)
+- Extensions pattern
+- Multi-language support
+- Comprehensive documentation
+
+## Key Takeaways
+
+1. **Start simple** - Don't over-engineer for small projects
+2. **Think in domains** - Organize by business capability, not technical layers
+3. **Document boundaries** - Make module ownership and dependencies explicit
+4. **Plan for scale** - Use prefixes and modules when you hit 30-50 objects
+5. **Test modules** - Each module should be testable independently
+6. **Version control** - Use module-level versioning for independent deployments
+
+## See Also
+
+- [Data Modeling Guide](./data-modeling.md)
+- [Plugin Development](./plugins.md)
+- [Logic Hooks](./logic-hooks.md)
+- [Complete Example](../../packages/starters/enterprise/)
diff --git a/docs/guide/microservices.md b/docs/guide/microservices.md
new file mode 100644
index 00000000..a4a8f112
--- /dev/null
+++ b/docs/guide/microservices.md
@@ -0,0 +1,61 @@
+# Microservices & Federation
+
+ObjectQL provides a built-in mechanism to aggregate data from multiple services into a single unified graph. This is similar to **GraphQL Federation** or Salesforce's **External Objects**, but strictly for the ObjectQL protocol.
+
+## Concept: Remote Remotes
+
+You can configure an ObjectQL instance to act as a **Gateway**. It connects to other ObjectQL instances, downloads their metadata (Schema), and automatically creates proxy drivers for them.
+
+*   **Source of Truth**: The microservice defines the object (`user.object.yml`).
+*   **Proxy**: The gateway sees a virtual object (`user`) and forwards all queries (Find, Update, Actions) to the microservice.
+
+## Configuration
+
+### The Subgraph (Service A)
+
+This is a standard ObjectQL service running standard drivers (SQL/Mongo).
+It must expose the metadata API (default in `@objectql/server`).
+
+```typescript
+// user-service/index.ts
+const app = new ObjectQL({
+    source: './src/objects', // Defines 'user', 'role'
+    datasources: { ... }
+});
+// Exposes http://user-service:3000/api/metadata/objects
+```
+
+### The Gateway
+
+The gateway aggregates multiple services.
+
+```typescript
+// gateway/index.ts
+const app = new ObjectQL({
+    // No local source needed, just remotes
+    remotes: [
+        'http://user-service:3000',
+        'http://order-service:3000'
+    ]
+});
+
+await app.init();
+```
+
+### Usage
+
+Once initialized, the Gateway behaves exactly like a monolith.
+
+```typescript
+// Code running on Gateway
+// Transparently forwards request to User Service via HTTP
+const users = await app.object('user').find({
+    filters: [['status', '=', 'active']]
+});
+```
+
+## Benefits
+
+1.  **Decoupling**: Services manage their own schema migrations and domain logic.
+2.  **Unity**: Frontend or upper layers see a single API surface.
+3.  **Hybrid**: A Gateway can *also* have local objects. You can mix "local cache tables" with "remote live tables" in the same application.
diff --git a/docs/guide/migration-id-field.md b/docs/guide/migration-id-field.md
new file mode 100644
index 00000000..a0b58785
--- /dev/null
+++ b/docs/guide/migration-id-field.md
@@ -0,0 +1,294 @@
+# Migration Guide: Unified ID Field
+
+This guide helps you migrate from the legacy `_id` field to the unified `id` field API.
+
+## What Changed?
+
+ObjectQL now provides a **unified `id` field** across all database drivers:
+
+- **Before**: MongoDB used `_id`, SQL used `id` - inconsistent API
+- **After**: Both drivers use `id` at the API level - consistent API
+
+The MongoDB driver now automatically maps between `id` (API) and `_id` (database) internally.
+
+## Benefits
+
+✅ **Consistent API**: Write database-agnostic code  
+✅ **Easier Migration**: Switch between MongoDB and SQL without code changes  
+✅ **Better Developer Experience**: No need to remember which driver uses which field  
+✅ **Backward Compatible**: Legacy `_id` usage still works (MongoDB only)
+
+## Migration Steps
+
+### 1. Update Filters
+
+**Before:**
+```typescript
+// MongoDB-specific code
+const query = {
+  filters: [['_id', '=', 'user-123']]
+};
+```
+
+**After:**
+```typescript
+// Works with both MongoDB and SQL
+const query = {
+  filters: [['id', '=', 'user-123']]
+};
+```
+
+### 2. Update Document Creation
+
+**Before:**
+```typescript
+// MongoDB-specific code
+const user = await app.create('users', {
+  _id: 'user-123',
+  name: 'Alice'
+});
+```
+
+**After:**
+```typescript
+// Works with both MongoDB and SQL
+const user = await app.create('users', {
+  id: 'user-123',
+  name: 'Alice'
+});
+```
+
+### 3. Update Field Access in Results
+
+**Before:**
+```typescript
+const users = await app.find('users', {});
+console.log(users[0]._id); // MongoDB
+console.log(users[0].id);  // SQL
+```
+
+**After:**
+```typescript
+const users = await app.find('users', {});
+console.log(users[0].id);  // Works for both MongoDB and SQL
+```
+
+### 4. Update Sorting
+
+**Before:**
+```typescript
+const query = {
+  sort: [['_id', 'desc']]  // MongoDB-specific
+};
+```
+
+**After:**
+```typescript
+const query = {
+  sort: [['id', 'desc']]  // Works for both
+};
+```
+
+### 5. Update Field Projection
+
+**Before:**
+```typescript
+const query = {
+  fields: ['_id', 'name', 'email']  // MongoDB-specific
+};
+```
+
+**After:**
+```typescript
+const query = {
+  fields: ['id', 'name', 'email']  // Works for both
+};
+```
+
+## Automated Migration
+
+You can use a find-and-replace tool to migrate your codebase:
+
+### Search Patterns
+
+1. **In Filters**: `['_id',` → `['id',`
+2. **In Objects**: `_id:` → `id:`
+3. **In Access**: `.\_id` → `.id`
+4. **In Fields**: `'_id'` → `'id'`
+
+### Example Script
+
+```bash
+# Search for _id usage in your codebase
+grep -r "_id" src/
+
+# Use your editor's find-and-replace with caution
+# Or use a tool like:
+find src/ -type f -name "*.ts" -exec sed -i "s/\['_id'/\['id'/g" {} +
+```
+
+**⚠️ Warning**: Always review changes manually and test thoroughly after automated replacement.
+
+## Backward Compatibility
+
+### MongoDB Driver
+
+The MongoDB driver maintains **full backward compatibility** for `_id` usage:
+
+- `_id` in **filters** is automatically mapped to MongoDB's `_id`
+- `_id` in **sorting** is automatically mapped to MongoDB's `_id`
+- `_id` in **field projections** is automatically mapped to MongoDB's `_id`
+- `_id` in **create operations** is mapped to `id`
+- Results **always** return `id` (not `_id`)
+
+**Example:**
+```typescript
+// Legacy code - fully supported for backward compatibility
+const query = {
+  filters: [['_id', '=', 'user-123']],
+  sort: [['_id', 'desc']],
+  fields: ['_id', 'name', 'email']
+};
+const users = await app.find('users', query);
+
+// Results use 'id' (not '_id')
+console.log(users[0].id); // 'user-123'
+console.log(users[0]._id); // undefined
+```
+
+**No Breaking Changes:** Your existing queries using `_id` will continue to work without modification. However, migrating to `id` is recommended for:
+- Consistency with SQL drivers
+- Database portability
+- Future-proofing your code
+
+### SQL Driver
+
+The SQL driver has always used `id`, so no migration needed for SQL-only codebases.
+
+For codebases using MongoDB-style `_id` with SQL:
+```typescript
+// Legacy code with _id
+const user = await app.create('users', {
+  _id: 'user-123',  // Automatically mapped to 'id'
+  name: 'Alice'
+});
+
+// Result uses 'id'
+console.log(user.id); // 'user-123'
+```
+
+## Testing Your Migration
+
+After migrating, verify the following:
+
+### 1. Create Operations
+```typescript
+const user = await app.create('users', {
+  id: 'test-123',
+  name: 'Test User'
+});
+assert(user.id === 'test-123');
+assert(user._id === undefined); // Should not have _id
+```
+
+### 2. Find Operations
+```typescript
+const users = await app.find('users', {
+  filters: [['id', '=', 'test-123']]
+});
+assert(users[0].id === 'test-123');
+```
+
+### 3. Update Operations
+```typescript
+await app.update('users', 'test-123', {
+  name: 'Updated Name'
+});
+const updated = await app.findOne('users', 'test-123');
+assert(updated.name === 'Updated Name');
+```
+
+### 4. Sort and Projection
+```typescript
+const users = await app.find('users', {
+  fields: ['id', 'name'],
+  sort: [['id', 'asc']]
+});
+assert(users[0].id !== undefined);
+assert(users[0]._id === undefined);
+```
+
+## Database Migration
+
+### MongoDB Collections
+
+No database migration needed! The MongoDB driver:
+- Continues to use `_id` in the database (MongoDB requirement)
+- Automatically maps `id` ↔ `_id` at the driver level
+- Existing data works without changes
+
+### SQL Tables
+
+If you have legacy SQL tables using `_id` as the primary key:
+
+```sql
+-- The driver will detect and automatically recreate tables
+-- But you can also migrate manually:
+
+-- Option 1: Rename column (PostgreSQL)
+ALTER TABLE users RENAME COLUMN _id TO id;
+
+-- Option 2: Create new table and migrate data
+CREATE TABLE users_new (
+  id VARCHAR(255) PRIMARY KEY,
+  name VARCHAR(255),
+  -- ... other columns
+);
+
+INSERT INTO users_new (id, name, ...)
+SELECT _id, name, ... FROM users;
+
+DROP TABLE users;
+ALTER TABLE users_new RENAME TO users;
+```
+
+## Common Issues
+
+### Issue: `undefined` for `id` field
+
+**Cause**: Using old code that accesses `_id` on results
+
+**Solution**: Change `result._id` to `result.id`
+
+### Issue: Filters not working
+
+**Cause**: Still using `_id` in filter arrays
+
+**Solution**: Change `['_id', '=', value]` to `['id', '=', value]`
+
+### Issue: Custom ID not working in MongoDB
+
+**Cause**: Passing `_id` instead of `id` in create
+
+**Solution**: Change `{ _id: 'custom' }` to `{ id: 'custom' }`
+
+## Need Help?
+
+If you encounter issues during migration:
+
+1. Check the [Driver Documentation](./drivers/index.md)
+2. Review the [API Reference](../api/README.md)
+3. Open an issue on [GitHub](https://github.com/objectql/objectql/issues)
+
+## Summary
+
+| Aspect | Before (Legacy) | After (Unified) |
+|--------|----------------|-----------------|
+| MongoDB Filter | `['_id', '=', '123']` | `['id', '=', '123']` |
+| SQL Filter | `['id', '=', '123']` | `['id', '=', '123']` |
+| MongoDB Create | `{ _id: '123', ... }` | `{ id: '123', ... }` |
+| SQL Create | `{ id: '123', ... }` | `{ id: '123', ... }` |
+| MongoDB Result | `result._id` | `result.id` |
+| SQL Result | `result.id` | `result.id` |
+
+**Recommendation**: Migrate all code to use `id` for maximum consistency and portability.
diff --git a/docs/guide/plugins.md b/docs/guide/plugins.md
new file mode 100644
index 00000000..b6d331ff
--- /dev/null
+++ b/docs/guide/plugins.md
@@ -0,0 +1,249 @@
+# Plugin System
+
+Plugins are the primary way to extend ObjectQL. They allow you to bundle behavior, schema modifications, and logic (hooks/actions) into reusable units.
+
+## 1. Anatomy of a Plugin
+
+A plugin is simply an object that implements the `ObjectQLPlugin` interface.
+
+```typescript
+import { IObjectQL } from '@objectql/types';
+
+export interface ObjectQLPlugin {
+    /**
+     * The unique name of the plugin
+     */
+    name: string;
+    
+    /**
+     * Called during initialization, before drivers connect.
+     * @param app The ObjectQL instance
+     */
+    setup(app: IObjectQL): void | Promise<void>;
+}
+```
+
+## 2. Execution Lifecycle
+
+Understanding valid execution timing is critical.
+
+1.  **Phase 1: Construction (`new ObjectQL`)**
+    *   Load Metadata from `packages`.
+    *   Load Metadata from `source` directories (`*.object.yml`).
+    *   Load Metadata from `config.objects`.
+    *   **Result:** `app.metadata` holds all static definitions.
+
+2.  **Phase 2: Initialization (`await app.init()`)**
+    *   **Step A: Remotes:** Fetch metadata from remote services.
+    *   **Step B: Plugins (`plugin.setup`)**:  <-- **YOU ARE HERE**
+        *   This is the last chance to modify metadata before it touches the DB.
+        *   You can access all objects loaded in Phase 1 & Step A.
+    *   **Step C: Drivers:** Drivers connect and synchronize schema (create tables, etc.).
+
+## 3. Creating Plugins
+
+You can define plugins in two styles: **Object** or **Class**.
+
+### Option A: Object Style (Simpler)
+Useful for stateless, simple logic or one-off modifications.
+
+```typescript
+const MySimplePlugin = {
+    name: 'my-simple-plugin',
+    setup(app) {
+        app.on('before:create', 'user', async (ctx) => {
+            console.log('Creating user...');
+        });
+    }
+};
+```
+
+### Option B: Class Style (Recommended)
+Useful when your plugin needs to maintain internal state, configuration, or complex initialization logic.
+
+```typescript
+class MyComplexPlugin implements ObjectQLPlugin {
+    name = 'my-complex-plugin';
+    private config;
+
+    constructor(config = {}) {
+        this.config = config;
+    }
+
+    async setup(app: IObjectQL) {
+        // Access config here
+        if (this.config.enableLogging) {
+            app.on('before:*', '*', async (ctx) => {
+                console.log(`[${ctx.event}] ${ctx.objectName}`);
+            });
+        }
+    }
+}
+```
+
+## 3. Loading Plugins
+
+Plugins are passed to the `ObjectQL` constructor via the `plugins` array. The loader is very flexible.
+
+### Method 1: Inline Instance
+Pass the plugin object or class instance directly.
+
+```typescript
+const db = new ObjectQL({
+    plugins: [
+        MySimplePlugin,          // Object
+        new MyComplexPlugin({})  // Class Instance
+    ]
+});
+```
+
+### Method 2: NPM Package (String)
+You can specify the package name as a string. ObjectQL uses `require()` (Node.js) to resolve it.
+
+```typescript
+const db = new ObjectQL({
+    plugins: [
+        '@objectql/plugin-audit', // Searches node_modules
+        './local-plugins/my-plugin' // Relative path
+    ]
+});
+```
+
+#### Package Resolution Rules
+When loading from a string, ObjectQL tries to find the plugin in the exported module in this order:
+
+1.  **Class Constructor**: If the module exports a Class (default or module.exports), it tries to instantiation it (`new Plugin()`).
+2.  **Plugin Object**: If the module exports an object with a `setup` function, it uses it directly.
+3.  **Default Export**: If the module has a `default` export, it checks that recursively.
+
+**Example Package (`node_modules/my-plugin/index.js`):**
+```javascript
+// This works
+module.exports = class MyPlugin { ... }
+
+// This also works
+module.exports = { name: '..', setup: () => {} }
+
+// This also works (ESM/TS)
+export default class MyPlugin { ... }
+```
+
+## 4. What can Plugins do?
+
+The `setup(app)` method gives you full access to the `ObjectQL` instance.
+
+### A. Manipulate Metadata (Schema)
+Plugins have full control over the schema. You can modify existing objects or register new ones.
+
+**Example 1: Injecting a global field**
+```typescript
+setup(app) {
+    const allObjects = app.metadata.list('object');
+    for (const obj of allObjects) {
+        // Add 'createdAt' to every object if missing
+        if (!obj.fields.createdAt) {
+            obj.fields.createdAt = { type: 'datetime' };
+        }
+    }
+}
+```
+
+**Example 2: Registering a new Object**
+Plugins can bundle their own data models (e.g. an audit log table).
+
+```typescript
+setup(app) {
+    app.registerObject({
+        name: 'audit_log',
+        fields: {
+            action: { type: 'string' },
+            userId: { type: 'string' },
+            timestamp: { type: 'datetime' }
+        }
+    });
+}
+```
+
+**Example 3: Scanning a Directory**
+Plugins can also scan a directory to load metadata files, just like the main application. This is useful for bundling a set of objects.
+
+```typescript
+import * as path from 'path';
+
+setup(app) {
+    // Scan the 'objects' folder inside the plugin directory
+    const objectsDir = path.join(__dirname, 'objects');
+    app.loadFromDirectory(objectsDir);
+}
+```
+
+### B. Register Global Hooks
+Listen to lifecycle events on specific objects or `*` (wildcard).
+
+```typescript
+setup(app) {
+    app.on('before:delete', '*', async (ctx) => {
+        if (ctx.objectName === 'system_log') {
+            throw new Error("Logs cannot be deleted");
+        }
+    });
+}
+```
+
+### C. Register Custom Actions
+Add new capabilities to objects.
+
+```typescript
+setup(app) {
+    // Usage: objectql.executeAction('user', 'sendEmail', { ... })
+    app.registerAction('user', 'sendEmail', async (ctx) => {
+        await emailService.send(ctx.args.to, ctx.args.body);
+    });
+}
+```
+
+### D. Custom Metadata Loaders
+Plugins can register new loaders to scan for custom file types (e.g. `*.workflow.yml`). This allows ObjectQL to act as a unified metadata engine.
+
+```typescript
+import * as yaml from 'js-yaml';
+
+setup(app) {
+    app.addLoader({
+        name: 'workflow-loader',
+        glob: ['**/*.workflow.yml'],
+        handler: (ctx) => {
+            const doc = yaml.load(ctx.content);
+            const workflowName = doc.name;
+            
+            // Register into MetadataRegistry with a custom type
+            ctx.registry.register('workflow', {
+                type: 'workflow',
+                id: workflowName,
+                path: ctx.file,
+                content: doc
+            });
+        }
+    });
+}
+```
+
+### E. Manage Packages (Presets)
+Plugins can dynamically load or unload other packages. This is useful for plugins that act as "features" which bring in a set of dependencies.
+
+```typescript
+setup(app) {
+    // Dynamically load another package
+    app.addPackage('@objectos/standard-objects');
+
+    // Or remove a package if it conflicts with this plugin
+    app.removePackage('@objectos/legacy-objects');
+}
+```
+
+## 5. Scope Isolation
+
+
+When a plugin is loaded via **Package Name** (Method 2), ObjectQL automatically marks the hooks and actions registered by that plugin with its package name.
+
+This allows `app.removePackage('@objectql/plugin-auth')` to cleanly remove all hooks and actions associated with that plugin, without affecting others.
diff --git a/docs/guide/querying.md b/docs/guide/querying.md
new file mode 100644
index 00000000..e43ed500
--- /dev/null
+++ b/docs/guide/querying.md
@@ -0,0 +1,195 @@
+# Querying Data
+
+ObjectQL uses a **JSON-based Protocol** for all data operations. Unlike SQL (strings) or Query Builders (chained methods), ObjectQL queries are **Data Structures**.
+
+This design makes it strictly typed, easy to serialise/transport over HTTP, and safe from injection—perfect for both human developers and AI Agents.
+
+## The `find()` Operation
+
+The `find` method recovers a list of records matching specific criteria.
+
+```typescript
+const products = await app.object('product').find({
+    filters: [
+        ['category', '=', 'electronics'],
+        ['price', '>', 500]
+    ],
+    fields: ['name', 'price', 'category'],
+    sort: ['-price'], // Descending
+    skip: 0,
+    limit: 10
+});
+```
+
+### Filters
+
+Filters are defined as a 2D array: `[[ field, operator, value ]]`.
+
+**Implicit AND**:
+```typescript
+filters: [
+    ['status', '=', 'active'],
+    ['stock', '>', 0]
+]
+// SQL: WHERE status = 'active' AND stock > 0
+```
+
+**Explicit OR**:
+Use the `_or` special operator in complex filters (see advanced docs).
+
+### Sorting
+
+*   `field`: Ascending.
+*   `-field`: Descending.
+
+## CRUD Operations
+
+### Create (Insert)
+
+```typescript
+const id = await app.object('user').insert({
+    name: "Alice",
+    email: "alice@example.com",
+    role: "admin"
+});
+```
+
+### Update
+
+Updates are always bulk operations targeted by `filters`. To update a single record, filter by ID.
+
+```typescript
+// Update specific record
+await app.object('user').update(
+    { filters: [['_id', '=', '123']] }, // Target
+    { doc: { status: 'active' } }       // Change
+);
+
+// Bulk update
+await app.object('product').update(
+    { filters: [['stock', '=', 0]] },
+    { doc: { status: 'out_of_stock' } }
+);
+```
+
+### Delete
+
+```typescript
+// Delete specific record
+await app.object('user').delete({
+    filters: [['_id', '=', '123']]
+});
+```
+
+## Relationships (Joins & Expand)
+
+ObjectQL handles relationships distinctively. Instead of SQL `JOIN` keywords, we use the `expand` property to hydrate related records. This ensures compatibility across SQL and NoSQL drivers (where joins might be separate queries).
+
+### 1. The `expand` Syntax
+
+To get related data, define the relationship in `expand`.
+
+```typescript
+// Fetch tasks and include project details
+const tasks = await app.object('task').find({
+    fields: ['name', 'status', 'project'], // 'project' key returns the ID
+    expand: {
+        project: {
+            fields: ['name', 'start_date', 'owner']
+        }
+    }
+});
+/* Result:
+{
+    name: "Fix Bug",
+    project: {
+        name: "Q1 Web App",
+        owner: "Alice"
+    }
+}
+*/
+```
+
+### 2. Nested Expansion
+
+You can nest expansions arbitrarily deep.
+
+```typescript
+expand: {
+    project: {
+        fields: ['name'],
+        expand: {
+            // Expand the 'manager' field on the 'project' object
+            manager: {
+                fields: ['name', 'email']
+            }
+        }
+    }
+}
+```
+
+### 3. Filtering on Related Records
+
+There are two ways to filter based on relationships:
+
+**A. Filter the Root (Dot Notation)**
+Find tasks where the *project's status* is active.
+*(Note: Requires a driver that supports SQL Joins)*
+```typescript
+filters: [
+    ['project.status', '=', 'active']
+]
+```
+
+**B. Filter the Expanded List**
+Find projects, but only include *completed* tasks in the expansion.
+```typescript
+app.object('project').find({
+    expand: {
+        tasks: {
+            filters: [['status', '=', 'completed']]
+        }
+    }
+})
+```
+
+## Aggregation
+
+ObjectQL supports SQL-like aggregation via the `aggregate()` method on the repository.
+
+```typescript
+const stats = await app.object('order').aggregate({
+    // 1. Filter first
+    filters: [['status', '=', 'paid']],
+    
+    // 2. Group by specific fields
+    groupBy: ['customer_id'],
+    
+    // 3. Define aggregate functions
+    aggregate: [
+        { func: 'sum', field: 'total', alias: 'total_revenue' },
+        { func: 'count', field: 'id', alias: 'order_count' },
+        { func: 'max', field: 'created_at', alias: 'last_order_date' }
+    ]
+});
+
+/* Result:
+[
+    { customer_id: "101", total_revenue: 5000, order_count: 3, last_order_date: "2023-12-01..." },
+    { customer_id: "102", total_revenue: 1200, order_count: 1, last_order_date: "2023-11-15..." }
+]
+*/
+```
+
+### Supported Functions
+*   `count`
+*   `sum`
+*   `avg`
+*   `min`
+*   `max`
+
+## Why JSON?
+
+1.  **Transportable**: The query IS the HTTP request body. No translation needed.
+2.  **Secure**: Impossible to inject SQL syntax.
+3.  **Generatable**: LLMs produce perfect JSON structures naturally.
diff --git a/docs/guide/server-integration.md b/docs/guide/server-integration.md
new file mode 100644
index 00000000..e5b8d55a
--- /dev/null
+++ b/docs/guide/server-integration.md
@@ -0,0 +1,114 @@
+# Server Integration
+
+ObjectQL is designed to be framework-agnostic. While it can be used directly as a library, we provide a standard `@objectql/server` package to expose your application via HTTP.
+
+## The `@objectql/server` Package
+
+This package provides a standardized way to handle HTTP requests, similar to libraries like `better-auth`. It receives a standard JSON request body and routes it to the correct internal ObjectQL operation (`find`, `create`, `action`, etc.).
+
+### Installation
+
+```bash
+pnpm add @objectql/server
+```
+
+## Supported Frameworks
+
+### 1. Node.js (Raw HTTP)
+
+You can mount the handler directly on a native Node.js `http.Server`.
+
+```typescript
+import { createNodeHandler } from '@objectql/server';
+import { app } from './my-objectql-app'; // Your ObjectQL instance
+import { createServer } from 'http';
+
+const server = createServer(createNodeHandler(app));
+server.listen(3000);
+```
+
+### 2. Express
+
+Mount ObjectQL on any route path.
+
+```typescript
+import express from 'express';
+import { createNodeHandler } from '@objectql/server';
+import { app } from './my-objectql-app';
+
+const server = express();
+// ObjectQL server adapter handles body parsing automatically,
+// but works fine if you already used express.json()
+server.all('/api/objectql', createNodeHandler(app));
+
+server.listen(3000);
+```
+
+### 3. Next.js (Pages Router)
+
+```typescript
+// pages/api/objectql.ts
+import { createNodeHandler } from '@objectql/server';
+import { app } from '../../lib/store';
+
+export const config = {
+  api: {
+    bodyParser: false, // Let ObjectQL handle it, or true if you prefer
+  },
+};
+
+export default createNodeHandler(app);
+```
+
+## The Protocol
+
+The server exposes a single endpoint that accepts POST requests with a JSON body defined by `ObjectQLRequest`:
+
+```typescript
+interface ObjectQLRequest {
+    op: 'find' | 'findOne' | 'create' | 'update' | 'delete' | 'count' | 'action';
+    object: string;
+    args: any;
+    user?: any; // For passing authentication context
+}
+```
+
+## 📖 OpenAPI / Swagger Support
+
+`@objectql/server` automatically generates an OpenAPI 3.0 specification from your registered schema.
+
+You can access the spec by appending `/openapi.json` to your handler's mount path.
+
+**Example URLs:**
+*   **CLI Serve:** `http://localhost:3000/openapi.json`
+*   **Express (mounted at /api/objectql):** `http://localhost:3000/api/objectql/openapi.json`
+*   **Next.js (pages/api/objectql.ts):** `http://localhost:3000/api/objectql/openapi.json`
+
+This JSON file describes your data objects as "Virtual REST" endpoints (`GET /user`, `POST /user`, etc.), allowing you to easily import them into **Swagger UI**, **Postman**, or other API tools for visualization and testing.
+
+## Example Usage
+
+**Example (cURL):**
+
+```bash
+curl -X POST http://localhost:3000/api/objectql \
+  -H "Content-Type: application/json" \
+  -d '{
+    "op": "create",
+    "object": "User",
+    "args": {
+      "data": { "name": "Alice", "email": "alice@example.com" }
+    }
+  }'
+```
+
+## Dev Server
+
+For rapid prototyping, `@objectql/cli` provides a built-in dev server.
+
+```bash
+# Serves the current directory schema on port 3000
+objectql serve
+```
+
+See [CLI Documentation](../package/cli) for more details.

From 9dee0fc514f4c1b9331bc5f4f7c9e728b17313cf Mon Sep 17 00:00:00 2001
From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com>
Date: Thu, 15 Jan 2026 03:52:53 +0000
Subject: [PATCH 7/7] Fix build errors: remove studio references from tsconfig
 and express-api starter

Co-authored-by: hotlong <50353452+hotlong@users.noreply.github.com>
---
 packages/starters/express-api/src/index.ts | 5 +----
 tsconfig.json                              | 1 -
 2 files changed, 1 insertion(+), 5 deletions(-)

diff --git a/packages/starters/express-api/src/index.ts b/packages/starters/express-api/src/index.ts
index fe2cdf9b..e8876692 100644
--- a/packages/starters/express-api/src/index.ts
+++ b/packages/starters/express-api/src/index.ts
@@ -2,7 +2,7 @@ import express from 'express';
 import { ObjectQL } from '@objectql/core';
 import { SqlDriver } from '@objectql/driver-sql';
 import { ObjectLoader } from '@objectql/platform-node';
-import { createNodeHandler, createMetadataHandler, createStudioHandler, createRESTHandler } from '@objectql/server';
+import { createNodeHandler, createMetadataHandler, createRESTHandler } from '@objectql/server';
 import * as path from 'path';
 
 async function main() {
@@ -29,7 +29,6 @@ app.init().then(async () => {
     const objectQLHandler = createNodeHandler(app);
     const restHandler = createRESTHandler(app);
     const metadataHandler = createMetadataHandler(app);
-    const studioHandler = createStudioHandler();
 
     // 4. Setup Express
     const server = express();
@@ -51,7 +50,6 @@ app.init().then(async () => {
     server.all('/api/objectql*', objectQLHandler);
     server.all('/api/data/*', restHandler);
     server.all('/api/metadata*', metadataHandler);
-    server.get('/studio*', studioHandler);
 
     // Create some sample data
     const ctx = app.createContext({ isSystem: true });
@@ -66,7 +64,6 @@ app.init().then(async () => {
 
     server.listen(port, () => {
         console.log(`\n🚀 ObjectQL Server running on http://localhost:${port}`);
-        console.log(`\n📊 Console UI: http://localhost:${port}/console`);
         console.log(`\n🔌 APIs:`);
         console.log(`  - JSON-RPC:  http://localhost:${port}/api/objectql`);
         console.log(`  - REST:      http://localhost:${port}/api/data`);
diff --git a/tsconfig.json b/tsconfig.json
index afb32114..2fe0f9df 100644
--- a/tsconfig.json
+++ b/tsconfig.json
@@ -9,7 +9,6 @@
     { "path": "./packages/foundation/platform-node" },
     { "path": "./packages/runtime/server" },
     { "path": "./packages/tools/cli" },
-    { "path": "./packages/tools/studio" },
     { "path": "./packages/starters/express-api" },
     { "path": "./packages/starters/basic" },
     { "path": "./packages/starters/enterprise" },