| title | Documentation — build apps from metadata |
|---|---|
| description | ObjectStack documentation: one executable business ontology — AI writes it, the runtime runs it, agents operate it, you own it. Start here for guides, concepts and APIs. |
The ontology is the software. One executable business ontology. AI writes it, the runtime runs it, agents operate it, you own it. What the word means here — and what it does not — is Business Ontology.
flowchart LR
A["Describe<br/>in plain language"] --> B["Claude Code authors<br/>typed metadata"]
B --> G{"os validate<br/>the gate"}
G -->|fails| B
G -->|passes| V["You verify in<br/>the Console"]
V -->|iterate| A
V -->|ship| M["MCP — your app<br/>is AI-operable"]
- What Can It Do? — the platform's capabilities in business language, no code — start here if you're evaluating
- Build Without Code — what admins and analysts do visually in Console, Studio, and Setup
- Build with Claude Code — the main workflow: an agent builds the app, you verify it in the Console
- How AI Development Works — why AI-builds / human-verifies is fast and safe
- What is ObjectStack? — the protocol model and runtime layers
- Core Concepts — the ideas behind metadata-driven development
- Architecture — how the runtime turns your metadata into a database, API, UI, and MCP surface
Each module documents one capability in depth — overview first, then guides, with links to the matching protocol spec and schema reference.
- Protocol Spec — the normative ObjectQL / Kernel / ObjectUI specifications for implementers
- Schema Reference — generated Zod schema reference for every metadata type
- Quick Reference — fast lookup tables across all protocols
- Glossary — the shared vocabulary used across these docs
- Releases — release notes and implementation status