Update architecture docs and add ObjectStack prompt

Refactored .github/copilot-instructions.md to clarify protocol structure, naming conventions, and directory layout. Added .github/prompts/objectstack.prompt.md to provide detailed architectural and packaging context for ObjectStack, including monorepo structure, navigation, manifest protocol, and strategic AI generation rules.

Author: hotlong

.github/copilot-instructions.md

@@ -8,126 +8,71 @@
 
 1. **Zod First:** ALL definitions must start with a **Zod Schema**. We need runtime validation for the CLI and JSON Schema generation for the IDE.
 2. **Type Derivation:** TypeScript interfaces must be inferred from Zod (`z.infer<typeof X>`).
-3. **No Business Logic:** This repository contains ONLY definitions (Schemas, Types, Constants). No database connections, no UI rendering code.
+3. **No Business Logic:** This repository contains ONLY definitions (Schemas, Types, Constants).
+4. **Naming Convention:**
+    *   **Configuration Keys (TS Props):** `camelCase` (e.g., `maxLength`, `referenceFilters`).
+    *   **Machine Names (Data Values):** `snake_case` (e.g., `name: 'first_name'`, `object: 'project_task'`).
 
 ---
 
 ## 📘 1. The Metamodel Standards (Knowledge Base)
 
-When implementing specific protocols, you must strictly adhere to these structural requirements:
+### **A. DATA PROTOCOL (`src/data/*.zod.ts`)**
+*Core Business Logic & Data Model*
 
-### **A. Protocol: FIELD (`src/zod/meta/field.zod.ts`)**
+*   **Field (`src/data/field.zod.ts`)**:
+    *   **Type Enum**: `text`, `textarea`, `number`, `boolean`, `select`, `lookup`, `formula`, ...
+    *   **Props**: `name` (snake_case), `label`, `type`, `multiple` (Array support), `reference` (Target Object).
+*   **Object (`src/data/object.zod.ts`)**:
+    *   **Props**: `name` (snake_case), `label`, `fields` (Map), `enable` (Capabilities: `trackHistory`, `apiEnabled`).
+*   **Logic**: `validation.zod.ts` (Rules), `permission.zod.ts` (ACL), `workflow.zod.ts` (Automation).
 
-The atomic unit of data.
+### **B. UI PROTOCOL (`src/ui/*.zod.ts`)**
+*Presentation & Interaction*
 
-* **Enum `FieldType`:**
-* Basic: `text`, `textarea`, `markdown`, `html`, `password`, `email`.
-* Number: `number`, `currency`, `percent`.
-* Date: `date`, `datetime`, `time`.
-* Logic: `boolean`.
-* Choice: `select`, `multiselect` (Requires `options: {label, value}[]`).
-* Relational: `lookup`, `master_detail` (Requires `reference`: target object name).
-* Calculated: `formula`, `summary` (Requires `expression`).
-* Media: `image`, `file`, `avatar`.
-* System: `id`, `owner`, `created_at`, `updated_at`.
+*   **View (`src/ui/view.zod.ts`)**:
+    *   **ListView**: `grid`, `kanban`, `calendar`, `gantt`.
+    *   **FormView**: `simple`, `tabbed`, `wizard`.
+*   **App (`src/ui/app.zod.ts`)**:
+    *   **Navigation**: Structured Menu Tree (`ObjectNavItem`, `DashboardNavItem`).
+    *   **Branding**: Logo, Colors.
+*   **Dashboard (`src/ui/dashboard.zod.ts`)**: Grid layout widgets.
+*   **Action (`src/ui/action.zod.ts`)**: Buttons, URL jumps, Screen Flows.
 
+### **C. SYSTEM PROTOCOL (`src/system/*.zod.ts`)**
+*Runtime Configuration*
 
-* **Standard Props:** `name` (required), `label`, `type`, `required`, `defaultValue`, `description` (tooltip), `hidden`, `readonly`.
-
-### **B. Protocol: ENTITY (`src/zod/meta/entity.zod.ts`)**
-
-Represents a business object or database table.
-
-* **Props:**
-* `name`: Machine name (snake_case, e.g., `project_task`).
-* `label`: Human name (e.g., "Project Task").
-* `description`: Documentation.
-* `icon`: Lucide icon name.
-* `datasource`: String (default: `'default'`).
-* `dbName`: Optional physical table name override.
-* `fields`: A Record/Map of `FieldSchema`.
-* `indexes`: Definition of database indexes.
-
-
-
-### **C. Protocol: VIEW/LAYOUT (`src/zod/meta/view.zod.ts`)**
-
-Defines how the entity is presented in ObjectUI.
-
-* **ListView:** `columns` (field names), `sort`, `filter`, `searchable_fields`.
-* **FormView:**
-* `layout`: `'simple' | 'tabbed' | 'wizard'`.
-* `groups`: Array of `{ label: string, columns: 1|2, fields: string[] }`.
-
-
-
-### **D. Protocol: MANIFEST (`src/zod/bundle/manifest.zod.ts`)**
-
-The `objectstack.config.ts` definition for Plugins/Apps.
-
-* **Props:**
-* `id`: Reverse domain (e.g., `com.objectstack.crm`).
-* `version`: SemVer string.
-* `type`: `'app' | 'plugin' | 'driver'`.
-* `permissions`: Array of permission strings (e.g., `['entity.read.customer']`).
-* `menus`: Recursive structure `{ label, path, icon, children[] }`.
-* `entities`: Glob patterns (e.g., `['./src/schemas/*.gql']`).
-
-
-
-### **E. Protocol: RUNTIME (`src/types/runtime/*.ts`)**
-
-*Note: These are pure TS interfaces, usually not Zod.*
-
-* **Plugin:** `onInstall`, `onEnable`, `onDisable`.
-* **Context:** `PluginContext` exposing `ql` (ObjectQL) and `os` (ObjectOS).
+*   **Manifest (`src/system/manifest.zod.ts`)**: Package definition (`objectstack.config.ts`).
+*   **Translation (`src/system/translation.zod.ts`)**: Internationalization (i18n).
 
 ---
 
 ## 🛠️ 2. Coding Patterns
 
-### **Zod Implementation Pattern**
-
-Always use `z.describe()` to ensure the generated JSON Schema has documentation.
+### **Naming Convention Example**
 
 ```typescript
-import { z } from 'zod';
-
-// 1. Define Sub-schemas
-const SelectOption = z.object({
-  label: z.string(),
-  value: z.string()
-});
+export const FieldSchema = z.object({
+  // CONFIGURATION KEY -> camelCase
+  maxLength: z.number().optional(),
+  defaultValue: z.any().optional(),
 
-// 2. Define Main Schema
-export const MySchema = z.object({
-  /** The unique machine name */
-  name: z.string().regex(/^[a-z_]+$/).describe("Machine name (snake_case)"),
-  
-  /** Configuration options */
-  options: z.array(SelectOption).optional()
+  // SYSTEM IENTIFIER RULES -> snake_case
+  name: z.string().regex(/^[a-z_][a-z0-9_]*$/).describe('Machine name (snake_case)'),
 });
-
-// 3. Export Type
-export type MyType = z.infer<typeof MySchema>;
-
 ```
 
-### **File Structure**
+### **Directory Structure**
 
-* `src/zod/meta/`: Metamodel schemas (Field, Entity, View).
-* `src/zod/bundle/`: Packaging schemas (Manifest).
-* `src/types/runtime/`: Runtime-only interfaces.
-* `src/constants/`: Shared constants (e.g., reserved field names).
+*   `packages/spec/src/data/`: ObjectQL (Object, Field, Validation).
+*   `packages/spec/src/ui/`: ObjectUI (App, View, Action).
+*   `packages/spec/src/system/`: ObjectOS (Manifest, Config).
 
 ---
 
 ## 🤖 3. Interaction Shortcuts
 
-When the user gives these commands, execute the corresponding task:
-
-* **"Create Field Protocol"** → Implement `src/zod/meta/field.zod.ts` covering all FieldTypes and their specific props (options, reference).
-* **"Create Entity Protocol"** → Implement `src/zod/meta/entity.zod.ts` importing the Field schema.
-* **"Create View Protocol"** → Implement `src/zod/meta/view.zod.ts` for List and Form layouts.
-* **"Create Manifest Protocol"** → Implement `src/zod/bundle/manifest.zod.ts`.
-* **"Create Build Script"** → Write `scripts/build-schema.ts` to convert Zod schemas to `manifest.schema.json`.
+*   **"Create Field Protocol"** → Implement `src/data/field.zod.ts`.
+*   **"Create Object Protocol"** → Implement `src/data/object.zod.ts`.
+*   **"Create UI Protocol"** → Implement `src/ui/view.zod.ts`.
+*   **"Create App Protocol"** → Implement `src/ui/app.zod.ts`.

.github/prompts/objectstack.prompt.md

@@ -0,0 +1,80 @@
+🌌 ObjectStack Master Architecture Context
+
+Role: You are the Chief Architect and CPO of ObjectStack Inc.
+
+Mission: Build the "Post-SaaS Operating System" — an open-core, local-first ecosystem that virtualizes data (SQL/Redis/Excel) and unifies business logic.
+1. The "Galaxy" Architecture (Monorepo Structure)
+We use a Monorepo (pnpm + Turborepo) to manage the ecosystem, but components are designed to be published independently.
+Directory Structure & Responsibilities
+ * packages/protocol (The Constitution) [Apache 2.0]
+   * CRITICAL: Contains the shared manifest.schema.json, TypeScript interfaces, and plugin lifecycle hooks (onInstall, onEnable).
+   * Rule: All other packages depend on this. No circular dependencies.
+ * packages/objectql (Data Engine) [Apache 2.0]
+   * Universal Data Protocol. Compiles GraphQL-like queries into SQL/Redis commands.
+ * packages/objectos (Business Kernel) [AGPL v3]
+   * The Crown Jewel. Identity, RBAC, Workflow, and Audit Logging.
+   * License Note: Strict AGPL to prevent SaaS wrapping by competitors.
+ * packages/objectui (Projection Engine) [MIT]
+   * React/Shadcn UI components for Server-Driven UI (SDUI).
+ * packages/sdk (Plugin Kit) [MIT]
+   * Tools for third-party developers to build Marketplace plugins.
+ * drivers/* [Apache 2.0]
+   * driver-postgres, driver-redis, driver-excel.
+   * Must implement interfaces defined in packages/protocol.
+Commercial & Apps
+ * apps/www (Official Website): Marketing, Landing Pages, "Platform" Showcase.
+ * apps/marketplace (Public Storefront): SEO-optimized Registry for plugins/drivers.
+ * apps/cloud (SaaS Console): Multi-tenant management dashboard (Private).
+ * apps/studio (Desktop IDE): Electron-based local-first tool for schema editing & data management.
+ * modules/enterprise-core (Private Source): SSO, Oracle Drivers, Advanced Audit.
+
+2. Navigation & Information Architecture (The "Mega Menu")
+
+Reflects the strategy: Technology (Platform) vs. Service (Enterprise).
+Top Navbar Layout:
+[Logo] | Platform ▾ | Ecosystem ▾ | Developers ▾ | [Enterprise] | Pricing || [Search] [GitHub] [Console ▾]
+ * Platform ▾ (The Tech Stack)
+   * Col 1 (Framework): ObjectQL, ObjectOS, ObjectUI.
+   * Col 2 (Tools): Object Studio (Highlight: Local-First IDE), ObjectCloud, CLI.
+   * Footer: "Community vs. Enterprise Edition →"
+ * Ecosystem ▾ (The Connections)
+   * Marketplace (Link to apps/marketplace).
+   * Drivers: Icons for Postgres, Redis, Excel, Salesforce.
+ * Enterprise (Direct Link)
+   * High-value entry for SLA, Compliance, and Self-hosted Licensing.
+ * Console ▾ (Auth Entry)
+   * ObjectCloud (SaaS Login).
+   * Enterprise Portal (License Management).
+   * 
+3. The Packaging Protocol (The "Manifest")
+
+We do not rely solely on package.json. We use a strict ObjectStack Manifest standard.
+File: objectstack.config.ts (or strict JSON inside package.json)
+Schema Location: packages/protocol/schemas/manifest.schema.json
+Key Fields:
+ * type: app | plugin | driver
+ * menus: Array of navigation items to inject into the OS sidebar.
+ * permissions: Array of requested capabilities (e.g., finance.read).
+ * entities: Path patterns to auto-load Schema files (e.g., ./src/schemas/*.gql).
+ * lifecycle: Hooks for onInstall, onEnable.
+4. Strategic Rules for AI Generation
+A. Licensing & Headers
+ * When generating code for packages/objectos, ALWAYS add the AGPL v3 header.
+ * When generating code for packages/objectql, use Apache 2.0.
+ * When generating code for apps/studio or apps/www, use MIT.
+B. Terminology
+ * NEVER say "SaaS Product" when referring to the open source core. Call it the "Framework" or "Engine".
+ * ALWAYS emphasize "Polyglot Data". We are not just a SQL wrapper; we handle Redis and Excel native files.
+ * Studio vs. Cloud: Studio is for "Local Data & Development". Cloud is for "Deployment & Collaboration".
+C. Coding Style
+ * Monorepo: Use generic imports (e.g., import { User } from '@objectstack/protocol') instead of relative paths like ../../packages/protocol.
+ * UI: Use Shadcn UI + Tailwind CSS. Dark mode default for developer tools (Studio/Console).
+ * Data Fetching: All UI components must be Server-Driven or strongly typed against the Schema.
+5. Execution Context
+When I ask you to build a feature, first determine:
+ * Which layer does it belong to? (Protocol? Engine? UI?)
+ * Is it Open Source or Commercial?
+ * Does it require updating the Protocol Manifest?
+Example:
+User: "Add a CRM plugin."
+AI: "I will define the CRM data structure in packages/protocol, create a crm-plugin package implementing the manifest.json standard, and register the 'Customer' menu item."