objectstack-ai · os-zhuang · Jul 15, 2026 · Jul 15, 2026 · Jul 15, 2026
diff --git a/apps/docs/redirects.mjs b/apps/docs/redirects.mjs
@@ -109,6 +109,9 @@ export const docsRedirects = [
   // folder moves (wildcards — keep after exact entries)
   ['/docs/guides/runtime-services/:path*', '/docs/kernel/runtime-services/:path*'],
   ['/docs/guides/contracts/:path*', '/docs/kernel/contracts/:path*'],
+  // ObjectOS layer-name retirement: the System Protocol section is now "kernel"
+  // (:path* matches zero or more segments, so this also covers the bare URL)
+  ['/docs/protocol/objectos/:path*', '/docs/protocol/kernel/:path*'],
   // safety net for anything else under retired sections — keep last
   ['/docs/guides/:path*', '/docs'],
 ];

diff --git a/content/docs/api/data-flow.mdx b/content/docs/api/data-flow.mdx
@@ -212,7 +212,7 @@ flowchart LR
 How data changes propagate to connected clients in real time.
 
 <Callout type="warn">
-**Implementation status:** This diagram (and the `emit(...)` → `EB->>WS` broadcast step in the Write Flow diagram above) shows the target design. The realtime service that ships today is an **in-memory pub/sub adapter** (`InMemoryRealtimeAdapter` in `@objectstack/service-realtime`), delivered to JS clients via **long-polling** (`RealtimeAPI` in `@objectstack/client`) — no WebSocket transport is wired up yet. The adapter also only matches subscriptions by `object` and `eventTypes`; per-field `filter` conditions (e.g. `{ project: 'prj_1' }`) are accepted in the request shape but are not yet enforced server-side. See [Real-Time Protocols](/docs/protocol/objectos/realtime-protocol) for the full implementation-status breakdown.
+**Implementation status:** This diagram (and the `emit(...)` → `EB->>WS` broadcast step in the Write Flow diagram above) shows the target design. The realtime service that ships today is an **in-memory pub/sub adapter** (`InMemoryRealtimeAdapter` in `@objectstack/service-realtime`), delivered to JS clients via **long-polling** (`RealtimeAPI` in `@objectstack/client`) — no WebSocket transport is wired up yet. The adapter also only matches subscriptions by `object` and `eventTypes`; per-field `filter` conditions (e.g. `{ project: 'prj_1' }`) are accepted in the request shape but are not yet enforced server-side. See [Real-Time Protocols](/docs/protocol/kernel/realtime-protocol) for the full implementation-status breakdown.
 </Callout>
 
 ```mermaid

diff --git a/content/docs/api/index.mdx b/content/docs/api/index.mdx
@@ -71,7 +71,7 @@ See [Actions as Tools](/docs/ai/actions-as-tools) for the `run_action` bridge an
 - [Error Catalog](/docs/api/error-catalog) — the full list of error codes
 - [Wire Format](/docs/api/wire-format) — request/response envelopes on the wire
 
-Spec: [HTTP API](/docs/protocol/objectos/http-protocol), [Real-Time Protocols](/docs/protocol/objectos/realtime-protocol)
+Spec: [HTTP API](/docs/protocol/kernel/http-protocol), [Real-Time Protocols](/docs/protocol/kernel/realtime-protocol)
 
 Schema reference: [API](/docs/references/api)
 

diff --git a/content/docs/automation/index.mdx b/content/docs/automation/index.mdx
@@ -49,6 +49,6 @@ Rule of thumb: model *state* with workflows, model *steps* with flows, use hooks
 
 ## Related
 
-- **Spec:** [State Machine (Lifecycle)](/docs/protocol/objectql/state-machine), [Runtime Capabilities](/docs/protocol/objectos/runtime-capabilities)
+- **Spec:** [State Machine (Lifecycle)](/docs/protocol/objectql/state-machine), [Runtime Capabilities](/docs/protocol/kernel/runtime-capabilities)
 - **Schema reference:** [Automation](/docs/references/automation)
 - **Neighbors:** validation rules that block bad data live in [Data Modeling](/docs/data-modeling/validation); who may trigger an automation is governed by [Permissions & Identity](/docs/permissions); the services hooks call (email, queue, storage…) are documented in [Kernel & Services](/docs/kernel/runtime-services).
diff --git a/content/docs/concepts/architecture.mdx b/content/docs/concepts/architecture.mdx
@@ -561,7 +561,7 @@ The three protocols are **loosely coupled** but **tightly integrated**:
 
 - [ObjectQL: Data Protocol](/docs/protocol/objectql) - Full data protocol specification
 - [ObjectUI: UI Protocol](/docs/protocol/objectui) - Full view protocol specification
-- [Kernel: System Protocol](/docs/protocol/objectos) - Full control protocol specification
+- [Kernel: System Protocol](/docs/protocol/kernel) - Full control protocol specification
 - [Developer Guide](/docs/getting-started/quick-start) - Build your first ObjectStack application
 
 ---

diff --git a/content/docs/kernel/index.mdx b/content/docs/kernel/index.mdx
@@ -5,7 +5,7 @@ description: The ObjectKernel runtime — plugin host, event bus, service regist
 
 # Kernel & Services
 
-The kernel is ObjectStack's runtime: it loads your metadata artifact, hosts plugins, wires up services, and enforces the lifecycle that keeps the system stable. This module documents the **ObjectOS layer** in practice — the [System Protocol](/docs/protocol/objectos) is its normative spec. If you write hooks or plugins, this is where the capability surface you call — `ctx.api`, `ctx.getService(...)`, and the `services.*` contract they implement — is documented.
+The kernel is ObjectStack's runtime: it loads your metadata artifact, hosts plugins, wires up services, and enforces the lifecycle that keeps the system stable. This module documents the **ObjectOS layer** in practice — the [System Protocol](/docs/protocol/kernel) is its normative spec. If you write hooks or plugins, this is where the capability surface you call — `ctx.api`, `ctx.getService(...)`, and the `services.*` contract they implement — is documented.
 
 ## How it fits together
 
@@ -40,6 +40,6 @@ The kernel is ObjectStack's runtime: it loads your metadata artifact, hosts plug
 
 ## Related
 
-- **Spec:** [System Lifecycle](/docs/protocol/objectos/lifecycle), [Runtime Capabilities](/docs/protocol/objectos/runtime-capabilities), [Metadata Service](/docs/protocol/objectos/metadata-service)
+- **Spec:** [System Lifecycle](/docs/protocol/kernel/lifecycle), [Runtime Capabilities](/docs/protocol/kernel/runtime-capabilities), [Metadata Service](/docs/protocol/kernel/metadata-service)
 - **Schema reference:** [Kernel](/docs/references/kernel), [System](/docs/references/system), [Contracts](/docs/references/contracts)
 - **Neighbors:** building and packaging plugins is covered in [Plugins & Packages](/docs/plugins); running the kernel in production is covered in [Deployment & Operations](/docs/deployment).
diff --git a/content/docs/plugins/index.mdx b/content/docs/plugins/index.mdx
@@ -18,7 +18,7 @@ ObjectStack is built on a **microkernel architecture** where nearly everything b
 - **[Package Overview](/docs/plugins/packages)** — All ObjectStack packages, services, drivers, plugins, and adapters
 - **[Adding a Metadata Type](/docs/plugins/adding-a-metadata-type)** — Register a new metadata type in the Studio Metadata Admin
 - Schema reference: [Kernel](/docs/references/kernel)
-- Spec: [Plugin Package Specification](/docs/protocol/objectos/plugin-spec)
+- Spec: [Plugin Package Specification](/docs/protocol/kernel/plugin-spec)
 
 ---
 

diff --git a/content/docs/protocol/index.mdx b/content/docs/protocol/index.mdx
@@ -12,7 +12,7 @@ The ObjectStack Protocol defines three interconnected layers that together descr
 <Cards>
   <Card icon={<Database />} title="ObjectQL: Data Protocol" href="/docs/protocol/objectql" description="Schema definitions, field types, state machines, query syntax, and data security." />
   <Card icon={<Layout />} title="ObjectUI: UI Protocol" href="/docs/protocol/objectui" description="Server-driven UI contracts for layouts, widgets, forms, and actions." />
-  <Card icon={<Cpu />} title="Kernel: System Protocol" href="/docs/protocol/objectos" description="Runtime lifecycle, HTTP/realtime protocols, plugins, configuration, and i18n." />
+  <Card icon={<Cpu />} title="Kernel: System Protocol" href="/docs/protocol/kernel" description="Runtime lifecycle, HTTP/realtime protocols, plugins, configuration, and i18n." />
 </Cards>
 
 ## Design Principles

diff --git a/...s/protocol/objectos/config-resolution.mdx → ...ocs/protocol/kernel/config-resolution.mdx b/...s/protocol/objectos/config-resolution.mdx → ...ocs/protocol/kernel/config-resolution.mdx
@@ -898,4 +898,4 @@ ObjectStack configuration resolution:
 - **Boot-time validation** using Zod schemas
 - **Inspection tools** for debugging config issues
 
-**Next:** Learn about internationalization in [i18n Standard](/docs/protocol/objectos/i18n-standard).
+**Next:** Learn about internationalization in [i18n Standard](/docs/protocol/kernel/i18n-standard).
diff --git a/...docs/protocol/objectos/error-handling.mdx → ...t/docs/protocol/kernel/error-handling.mdx b/...docs/protocol/objectos/error-handling.mdx → ...t/docs/protocol/kernel/error-handling.mdx
@@ -1047,12 +1047,12 @@ for (let i = 0; i < 1000000; i++) {
     icon={<Radio />}
     title="HTTP API"
     description="Learn REST endpoint conventions and CRUD operations"
-    href="/docs/protocol/objectos/http-protocol"
+    href="/docs/protocol/kernel/http-protocol"
   />
   <Card
     icon={<Zap />}
     title="Real-Time Protocols"
     description="Implement WebSocket subscriptions and event streaming"
-    href="/docs/protocol/objectos/realtime-protocol"
+    href="/docs/protocol/kernel/realtime-protocol"
   />
 </Cards>
diff --git a/.../docs/protocol/objectos/http-protocol.mdx → ...nt/docs/protocol/kernel/http-protocol.mdx b/.../docs/protocol/objectos/http-protocol.mdx → ...nt/docs/protocol/kernel/http-protocol.mdx
@@ -860,7 +860,7 @@ X-RateLimit-Reset: 1705324800
 }
 ```
 
-See [Error Handling](/docs/protocol/objectos/error-handling) for more details.
+See [Error Handling](/docs/protocol/kernel/error-handling) for more details.
 
 ## Best Practices
 
@@ -923,12 +923,12 @@ if (!response.ok) {
     icon={<Zap />}
     title="Real-Time Protocols"
     description="Learn WebSocket subscriptions and event streaming"
-    href="/docs/protocol/objectos/realtime-protocol"
+    href="/docs/protocol/kernel/realtime-protocol"
   />
   <Card
     icon={<AlertCircle />}
     title="Error Handling"
     description="Master error codes and debugging strategies"
-    href="/docs/protocol/objectos/error-handling"
+    href="/docs/protocol/kernel/error-handling"
   />
 </Cards>
diff --git a/.../docs/protocol/objectos/i18n-standard.mdx → ...nt/docs/protocol/kernel/i18n-standard.mdx b/.../docs/protocol/objectos/i18n-standard.mdx → ...nt/docs/protocol/kernel/i18n-standard.mdx
diff --git a/content/docs/protocol/objectos/index.mdx → content/docs/protocol/kernel/index.mdx b/content/docs/protocol/objectos/index.mdx → content/docs/protocol/kernel/index.mdx
@@ -85,25 +85,25 @@ Traditional enterprise platforms tightly couple infrastructure concerns with bus
   <Card
     icon={<Layers />}
     title="Lifecycle Management"
-    href="/docs/protocol/objectos/lifecycle"
+    href="/docs/protocol/kernel/lifecycle"
     description="Boot sequence, plugin installation, zero-downtime upgrades, rollback strategies"
   />
   <Card
     icon={<Package />}
     title="Plugin Specification"
-    href="/docs/protocol/objectos/plugin-spec"
+    href="/docs/protocol/kernel/plugin-spec"
     description="Manifest structure, dependency graph, versioning semantics, distribution format"
   />
   <Card
     icon={<Cog />}
     title="Configuration Resolution"
-    href="/docs/protocol/objectos/config-resolution"
+    href="/docs/protocol/kernel/config-resolution"
     description="Merge strategies, precedence rules, environment overrides, tenant isolation"
   />
   <Card
     icon={<Globe />}
     title="i18n Standard"
-    href="/docs/protocol/objectos/i18n-standard"
+    href="/docs/protocol/kernel/i18n-standard"
     description="Translation bundles, locale resolution, date/number formatting, dynamic loading"
   />
 </Cards>
@@ -491,25 +491,25 @@ const message = context.i18n.t('slack.button.send');
   <Card
     icon={<Layers />}
     title="Learn Lifecycle Management"
-    href="/docs/protocol/objectos/lifecycle"
+    href="/docs/protocol/kernel/lifecycle"
     description="Understand boot sequence, installation, upgrade strategies, and rollback procedures"
   />
   <Card
     icon={<Package />}
     title="Build Your First Plugin"
-    href="/docs/protocol/objectos/plugin-spec"
+    href="/docs/protocol/kernel/plugin-spec"
     description="Create a plugin manifest, define dependencies, and implement lifecycle hooks"
   />
   <Card
     icon={<Cog />}
     title="Master Configuration"
-    href="/docs/protocol/objectos/config-resolution"
+    href="/docs/protocol/kernel/config-resolution"
     description="Learn merge strategies, environment overrides, and tenant-specific settings"
   />
   <Card
     icon={<Globe />}
     title="Internationalize Your App"
-    href="/docs/protocol/objectos/i18n-standard"
+    href="/docs/protocol/kernel/i18n-standard"
     description="Add multi-language support with translation bundles and locale resolution"
   />
 </Cards>

diff --git a/content/docs/protocol/objectos/lifecycle.mdx → content/docs/protocol/kernel/lifecycle.mdx b/content/docs/protocol/objectos/lifecycle.mdx → content/docs/protocol/kernel/lifecycle.mdx
@@ -792,4 +792,4 @@ ObjectStack lifecycle management provides:
 - **Automatic Rollback:** Failed upgrades auto-revert to previous version
 - **Health Monitoring:** Built-in health checks validate system state
 
-**Next:** Learn how to define plugin manifests in [Plugin Specification](/docs/protocol/objectos/plugin-spec).
+**Next:** Learn how to define plugin manifests in [Plugin Specification](/docs/protocol/kernel/plugin-spec).
diff --git a/content/docs/protocol/objectos/meta.json → content/docs/protocol/kernel/meta.json b/content/docs/protocol/objectos/meta.json → content/docs/protocol/kernel/meta.json
diff --git a/...cs/protocol/objectos/metadata-service.mdx → ...docs/protocol/kernel/metadata-service.mdx b/...cs/protocol/objectos/metadata-service.mdx → ...docs/protocol/kernel/metadata-service.mdx
diff --git a/...nt/docs/protocol/objectos/plugin-spec.mdx → content/docs/protocol/kernel/plugin-spec.mdx b/...nt/docs/protocol/objectos/plugin-spec.mdx → content/docs/protocol/kernel/plugin-spec.mdx
@@ -952,4 +952,4 @@ Plugin packages in ObjectStack:
 - **Lifecycle-aware:** Hooks for install, upgrade, boot, and uninstall
 - **NPM-compatible:** Distribute via NPM or `.osplugin` archives
 
-**Next:** Learn how configuration is resolved in [Configuration Resolution](/docs/protocol/objectos/config-resolution).
+**Next:** Learn how configuration is resolved in [Configuration Resolution](/docs/protocol/kernel/config-resolution).
diff --git a/...s/protocol/objectos/realtime-protocol.mdx → ...ocs/protocol/kernel/realtime-protocol.mdx b/...s/protocol/objectos/realtime-protocol.mdx → ...ocs/protocol/kernel/realtime-protocol.mdx
@@ -1026,12 +1026,12 @@ WebSocket messages are rate-limited:
     icon={<Radio />}
     title="HTTP Protocol"
     description="Learn REST endpoint conventions and CRUD operations"
-    href="/docs/protocol/objectos/http-protocol"
+    href="/docs/protocol/kernel/http-protocol"
   />
   <Card
     icon={<AlertCircle />}
     title="Error Handling"
     description="Master error codes and debugging strategies"
-    href="/docs/protocol/objectos/error-handling"
+    href="/docs/protocol/kernel/error-handling"
   />
 </Cards>
diff --git a/...rotocol/objectos/runtime-capabilities.mdx → .../protocol/kernel/runtime-capabilities.mdx b/...rotocol/objectos/runtime-capabilities.mdx → .../protocol/kernel/runtime-capabilities.mdx
@@ -529,6 +529,6 @@ export function SemanticSearch() { /* ... */ }
 
 - [ObjectQL Reference](/docs/protocol/objectql)
 - [ObjectUI Reference](/docs/protocol/objectui)
-- [ObjectStack Reference](/docs/protocol/objectos)
+- [ObjectStack Reference](/docs/protocol/kernel)
 - [API Discovery](/docs/references/api/discovery)
 - [Driver Capabilities](/docs/references/data/driver)
diff --git a/content/docs/protocol/meta.json b/content/docs/protocol/meta.json
@@ -6,7 +6,7 @@
     "diagram",
     "objectql",
     "objectui",
-    "objectos",
+    "kernel",
     "knowledge",
     "backward-compatibility"
   ]

diff --git a/content/docs/protocol/objectui/index.mdx b/content/docs/protocol/objectui/index.mdx
@@ -566,5 +566,5 @@ Using ObjectUI to build applications?
 ### Related Protocols
 
 - **[ObjectQL (Data Protocol)](/docs/protocol/objectql)** - Define objects and queries
-- **[ObjectOS (System Protocol)](/docs/protocol/objectos)** - Runtime configuration
+- **[ObjectOS (System Protocol)](/docs/protocol/kernel)** - Runtime configuration
 - **[UI Reference](/docs/references/ui)** - Complete API reference
diff --git a/content/docs/references/data/object.mdx b/content/docs/references/data/object.mdx
@@ -14,8 +14,8 @@ API Operations Enum
 ## TypeScript Usage
 
 ```typescript
-import { ApiMethod, Index, ObjectAccessConfig, ObjectCapabilities, ObjectExternalBinding, ObjectFieldGroup, ObjectOwnershipEnum, ObjectRequiredPermissions, PerOperationRequiredPermissions, SoftDeleteConfig, TenancyConfig, VersioningConfig } from '@objectstack/spec/data';
-import type { ApiMethod, Index, ObjectAccessConfig, ObjectCapabilities, ObjectExternalBinding, ObjectFieldGroup, ObjectOwnershipEnum, ObjectRequiredPermissions, PerOperationRequiredPermissions, SoftDeleteConfig, TenancyConfig, VersioningConfig } from '@objectstack/spec/data';
+import { ApiMethod, Index, Lifecycle, LifecycleClass, ObjectAccessConfig, ObjectCapabilities, ObjectExternalBinding, ObjectFieldGroup, ObjectOwnershipEnum, ObjectRequiredPermissions, PerOperationRequiredPermissions, SoftDeleteConfig, TenancyConfig, VersioningConfig } from '@objectstack/spec/data';
+import type { ApiMethod, Index, Lifecycle, LifecycleClass, ObjectAccessConfig, ObjectCapabilities, ObjectExternalBinding, ObjectFieldGroup, ObjectOwnershipEnum, ObjectRequiredPermissions, PerOperationRequiredPermissions, SoftDeleteConfig, TenancyConfig, VersioningConfig } from '@objectstack/spec/data';
 
 // Validate data
 const result = ApiMethod.parse(data);
@@ -58,6 +58,35 @@ const result = ApiMethod.parse(data);
 | **partial** | `string` | optional | Partial index condition (SQL WHERE clause for conditional indexes) |
 
 
+---
+
+## Lifecycle
+
+### Properties
+
+| Property | Type | Required | Description |
+| :--- | :--- | :--- | :--- |
+| **class** | `Enum<'record' \| 'audit' \| 'telemetry' \| 'transient' \| 'event'>` | ✅ | Persistence contract: record (business truth, permanent) | audit (compliance ledger) | telemetry (high-freq log) | transient (ephemeral state) | event (bus messages). |
+| **retention** | `Object` | optional | Age-based retention window enforced by the LifecycleService Reaper. |
+| **ttl** | `Object` | optional | Per-row TTL auto-expiry (transient/event classes). |
+| **storage** | `Object` | optional | Physical storage strategy for high-frequency telemetry (LifecycleService Rotator). |
+| **archive** | `Object` | optional | Cold-store archival (LifecycleService Archiver) — audit-class hot→cold hand-off. |
+| **reclaim** | `boolean` | optional | Run driver space reclamation (SQLite incremental_vacuum) after sweeping this object. Default true for non-record classes. |
+
+
+---
+
+## LifecycleClass
+
+### Allowed Values
+
+* `record`
+* `audit`
+* `telemetry`
+* `transient`
+* `event`
+
+
 ---
 
 ## ObjectAccessConfig

diff --git a/content/docs/references/identity/position.mdx b/content/docs/references/identity/position.mdx
@@ -84,6 +84,7 @@ const result = Position.parse(data);
 | **name** | `string` | ✅ | Unique position name (lowercase snake_case) |
 | **label** | `string` | ✅ | Display label (e.g. VP of Sales) |
 | **description** | `string` | optional |  |
+| **delegatable** | `boolean` | ✅ | ADR-0091 D3: holders may self-service delegate this position, time-boxed (default false). |
 
 
 ---

diff --git a/content/docs/references/kernel/execution-context.mdx b/content/docs/references/kernel/execution-context.mdx
@@ -57,6 +57,7 @@ const result = ExecutionContext.parse(data);
 | **positions** | `string[]` | ✅ |  |
 | **principalKind** | `Enum<'human' \| 'agent' \| 'service' \| 'guest' \| 'system'>` | optional |  |
 | **audience** | `Enum<'internal' \| 'external'>` | optional |  |
+| **posture** | `Enum<'PLATFORM_ADMIN' \| 'TENANT_ADMIN' \| 'MEMBER' \| 'EXTERNAL'>` | optional | ADR-0095 D2 posture rung — PLATFORM_ADMIN crosses the tenant wall where object posture permits; TENANT_ADMIN sees all rows in the org; MEMBER gets business RLS; EXTERNAL sees only explicitly shared rows. |
 | **onBehalfOf** | `Object` | optional |  |
 | **permissions** | `string[]` | ✅ |  |
 | **systemPermissions** | `string[]` | optional |  |
@@ -65,6 +66,7 @@ const result = ExecutionContext.parse(data);
 | **rlsMembership** | `Record<string, string[]>` | optional |  |
 | **isSystem** | `boolean` | ✅ |  |
 | **skipTriggers** | `boolean` | optional |  |
+| **skipAutomations** | `boolean` | optional |  |
 | **oauthScopes** | `string[]` | optional |  |
 | **accessToken** | `string` | optional |  |
 | **transaction** | `any` | optional |  |