Add initial documentation and remove .cursorrules

Added comprehensive documentation under the docs directory, including guides for data modeling, logic actions, hooks, SDK reference, security, and protocol specifications. Removed the .cursorrules file containing internal coding standards and architecture guidelines.

Author: hotlong

.cursorrules

@@ -0,0 +1,24 @@
+# Data Modeling
+
+ObjectOS uses YAML to define data models.
+
+## Object Definition
+
+Files named `*.object.yml` define your entities.
+
+```yaml
+code: project
+label: Project
+fields:
+  name:
+    label: Project Name
+    type: text
+    required: true
+```
+
+## Field Types
+
+- `text`
+- `number`
+- `currency`
+- `lookup` (Relationship)

docs/guide/data-modeling.md

@@ -0,0 +1,19 @@
+# Getting Started with ObjectOS
+
+ObjectOS is a high-performance, metadata-driven low-code runtime engine.
+
+## Core Concepts
+
+- **Kernel**: The brain of the operation.
+- **Drivers**: How we talk to databases.
+- **Server**: Exposing APIs over HTTP.
+
+## Installation
+
+```bash
+npm install @objectos/kernel @objectos/server
+```
+
+## Quick Start
+
+Initialize the kernel and register your first object.

docs/guide/index.md

@@ -0,0 +1,14 @@
+# Custom Actions
+
+Actions are custom business logic endpoints.
+
+## Defining an Action
+
+Actions are often defined in YAML files (`*.action.yml`) or registered programmatically.
+
+```typescript
+kernel.registerAction('project.archive', async (ctx) => {
+  const { id } = ctx.params;
+  // Custom logic to archive project
+});
+```

docs/guide/logic-actions.md

@@ -0,0 +1,21 @@
+# Logic Hooks Examples
+
+## Auto-Populate Current User
+
+```typescript
+kernel.on('beforeCreate', async (ctx) => {
+  if (ctx.objectName === 'task' && ctx.user) {
+    ctx.data.created_by = ctx.user.id;
+  }
+});
+```
+
+## Validation
+
+```typescript
+kernel.on('beforeUpdate', async (ctx) => {
+  if (ctx.objectName === 'project' && ctx.data.budget < 0) {
+    throw new ValidationError('Budget cannot be negative');
+  }
+});
+```

docs/guide/logic-hooks-examples.md

@@ -0,0 +1,18 @@
+# Writing Hooks
+
+Hooks allow you to intercept and modify standard operations.
+
+## Hook Events
+
+- `beforeFind`, `afterFind`
+- `beforeCreate`, `afterCreate`
+- `beforeUpdate`, `afterUpdate`
+- `beforeDelete`, `afterDelete`
+
+## Registration
+
+```typescript
+kernel.on('beforeCreate', async (ctx) => {
+  console.log('Creating object:', ctx.objectName);
+});
+```

docs/guide/logic-hooks.md

@@ -0,0 +1,21 @@
+# SDK Reference
+
+The Kernel SDK provides methods to interact with your data programmatically.
+
+## `kernel.find(objectName, options)`
+
+Retrieves records matching the query options.
+
+```typescript
+const projects = await kernel.find('project', {
+  filters: [['status', '=', 'active']]
+});
+```
+
+## `kernel.create(objectName, data)`
+
+Creates a new record.
+
+```typescript
+await kernel.create('project', { name: 'New API' });
+```

docs/guide/sdk-reference.md

@@ -0,0 +1,18 @@
+# Security Guide
+
+Security in ObjectOS is handled through Permissions and Plugins.
+
+## Authentication
+
+Use `@objectos/plugin-auth` for handling user sessions.
+
+## Authorization
+
+Permissions are defined in object definitions or via permission sets.
+
+```typescript
+// Example of permission check
+if (!ctx.hasPermission('project', 'create')) {
+  throw new PermissionDeniedError();
+}
+```

docs/guide/security-guide.md

@@ -0,0 +1,23 @@
+---
+layout: home
+
+hero:
+  name: "ObjectOS"
+  text: "A Unified Data Management Framework"
+  tagline: "Kernel handles logic, Drivers handle data, Server handles HTTP."
+  actions:
+    - theme: brand
+      text: Get Started
+      link: /guide/
+    - theme: alt
+      text: View Spec
+      link: /spec/
+
+features:
+  - title: Metadata Driven
+    details: Define your business logic and data schema using simple YAML files.
+  - title: Kernel & Drivers
+    details: Core logic is decoupled from data storage implementation.
+  - title: HTTP Ready
+    details: Built-in NestJS server integration for instant API generation.
+---

docs/index.md

@@ -0,0 +1,25 @@
+# HTTP Protocol
+
+The Server exposes a RESTful API following these conventions.
+
+## Headers
+
+- `Content-Type: application/json`
+- `Authorization: Bearer <token>`
+
+## Response Envelope
+
+```json
+{
+  "code": 200,
+  "data": { ... },
+  "message": "Success"
+}
+```
+
+## Standard Endpoints
+
+- `GET /api/v4/{object}/query`
+- `POST /api/v4/{object}`
+- `PUT /api/v4/{object}/{id}`
+- `DELETE /api/v4/{object}/{id}`