You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Updated the homepage and documentation index to reflect ObjectStack as a metadata-driven protocol, clarifying its architecture, terminology, and target audience. Added a new meta.json for documentation structure. The homepage now uses updated terminology and code samples, and the docs index provides a clearer introduction and navigation for users.
**ObjectStack** is not just a framework; it is a **Protocol** for building enterprise software.
9
+
It decouples the *Business Intent* (defined in JSON/YAML) from the *Technical Execution* (handled by the Kernel).
8
10
9
-
**ObjectStack Protocol** is the "DNA" and constitution of the ObjectStack platform. It defines the metadata standards, schemas, and runtime behaviors that power a metadata-driven, low-code operating system.
11
+
This documentation is the authoritative reference for the ObjectStack Protocol.
10
12
11
-
<Callouttype="info">
12
-
This specification serves as the Single Source of Truth for all ObjectStack implementations. All definitions are strictly typed using Zod and TypeScript.
13
-
</Callout>
14
-
15
-
## The Metamodel Architecture
16
-
17
-
The protocol is divided into three fundamental pillars that decouple data, presentation, and system configuration.
13
+
## How to navigate
18
14
19
15
<Cards>
20
16
<Card
21
-
icon={<Database />}
22
-
href="/docs/concepts/architecture"
23
-
title="Data Protocol"
24
-
description="Core business logic and data modeling. Defines Objects, Fields, Validation Rules, and Flows."
17
+
icon={<Compass />}
18
+
title="Concepts"
19
+
href="/docs/concepts/manifesto"
20
+
description="Start here. Understand the philosophy of 'Intent over Implementation' and the 'Local-First' architecture."
25
21
/>
26
22
<Card
27
-
icon={<Layout />}
28
-
href="/docs/references/ui/App"
29
-
title="UI Protocol"
30
-
description="Presentation layer specifications. Defines Views, Layouts, Menus (Apps), and Dashboards."
23
+
icon={<Layers />}
24
+
title="Specifications"
25
+
href="/docs/specifications/data/architecture"
26
+
description="The Architecture Blueprints. Deep dive into ObjectQL (Data), ObjectUI (View), and ObjectOS (Control)."
31
27
/>
32
28
<Card
33
-
icon={<Settings />}
34
-
href="/docs/references/system/Datasource"
35
-
title="System Protocol"
36
-
description="Runtime configuration and environment binding. Defines Datasources, APIs, and Manifests."
29
+
icon={<Book />}
30
+
title="Protocol Reference"
31
+
href="/docs/references/data/index"
32
+
description="The Dictionary. Comprehensive reference for every Schema, Field Type, and Configuration option."
37
33
/>
38
34
</Cards>
39
35
40
-
## Core Principles
41
-
42
-
### 1. Schema First
43
-
Every protocol definition starts with a **Zod Schema**. This ensures runtime validation for the CLI and strict type derivation (`z.infer<T>`) for the IDE. We do not write code without a schema.
44
-
45
-
### 2. Configuration as Code
46
-
All business logic is expressed as serializable JSON/YAML configuration. This enables:
47
-
-**Version Control**: Git-based history for business logic.
48
-
-**Reviewability**: Pull requests for application changes.
49
-
-**Portability**: Move applications between environments instantly.
50
-
51
-
### 3. Separation of Concerns
52
-
We strictly separate the **Metamodel** (pure definitions) from the **Runtime** (execution engine). The `spec` package contains *only* definitions, constants, and types—no heavy business logic.
53
-
54
-
## Directory Structure
36
+
## The "Trinity" Architecture
55
37
56
-
The specification is organized reflecting the protocol pillars:
38
+
ObjectStack is built on three pillars that work in unison:
|**Data Layer**|**[ObjectQL](/docs/specifications/data/architecture)**| Defines the shape of data (`Object`) and how to access it (`AST`). Agnostic to SQL/NoSQL. |
43
+
|**Control Layer**|**[ObjectOS](/docs/specifications/server/kernel-architecture)**| The Kernel. Handles Identity, Security, Sync, and Automation. |
44
+
|**View Layer**|**[ObjectUI](/docs/specifications/ui/sdui-protocol)**| The Projection. Defines the User Interface as abstract JSON layouts, enabling Server-Driven UI. |
61
45
62
-
## Next Steps
46
+
## For whom is this?
63
47
64
-
<Cards>
65
-
<Card
66
-
icon={<Book />}
67
-
href="/docs/concepts/manifesto"
68
-
title="Read the Manifesto"
69
-
description="Understand the philosophy behind the Post-SaaS Operating System."
70
-
/>
71
-
<Card
72
-
icon={<FileText />}
73
-
href="/docs/references"
74
-
title="API Reference"
75
-
description="Explore the complete API and Schema reference documentation."
76
-
/>
77
-
</Cards>
48
+
***Platform Architects:** Who want to build internal developer platforms (IDP) that scale.
49
+
***Protocol Implementers:** Who want to write a new Driver for ObjectQL (e.g., for FoundationDB) or a new Renderer for ObjectUI (e.g., for Flutter).
50
+
***AI Agent Developers:** Who need a deterministic, structured generic language for AI to generate software.
0 commit comments