| title | Documentation |
|---|---|
| description | Technical documentation for ObjectStack. |
ObjectStack is an AI-native business backend protocol for structured, auditable business applications. The way you build it: an AI agent (Claude Code) authors your application as typed metadata — data model, logic, permissions, UI — a validation gate rejects mistakes that would fail silently at runtime, and you verify the result in a visual Console. From that one source of truth the runtime derives everything else — the database schema on interchangeable drivers, a generated REST + realtime API, permission-checked automation, server-driven UI, and an MCP server, so the app you build is itself AI-operable. Agents act through the same typed, permission-aware surface — never raw SQL or scraped UI.
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"]
- 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