diff --git a/.changeset/readme-hero-16k-ontology.md b/.changeset/readme-hero-16k-ontology.md
new file mode 100644
index 000000000..8a0f21ff8
--- /dev/null
+++ b/.changeset/readme-hero-16k-ontology.md
@@ -0,0 +1,4 @@
+---
+---
+
+README-only rewrite of the hero tagline ("A complete business system in 16k tokens.") weaving in the business-ontology narrative. Docs only, so this releases nothing.
diff --git a/README.md b/README.md
index a22fc31ae..2ae5f0441 100644
--- a/README.md
+++ b/README.md
@@ -4,24 +4,27 @@
 ![TypeScript](https://img.shields.io/badge/TypeScript-5.x-blue.svg)
 ![Tests](https://img.shields.io/badge/tests-6%2C507%20passing-brightgreen.svg)
 
-> ## AI writes the app. ObjectStack is what it writes.
+> ## A complete business system in 16k tokens.
 >
-> The open target format and runtime for AI-written business apps. Your coding
-> agent writes models, UI, workflows, and permissions as compact typed metadata —
-> [a complete CRM is under 2,000 lines](#why-the-mistakes-dont-ship), so the whole
-> app fits in the agent's context — and strict TypeScript, Zod schemas, and a
-> validation gate catch its mistakes at authoring time. The runtime derives the
-> database, REST API, UI, and MCP server, and enforces permissions and audit on
-> every call.
+> ObjectStack compresses an entire app — data model, UI, workflows,
+> permissions — into typed metadata an AI agent can hold in context, reason
+> about, and refactor whole ([a complete CRM is under 2,000
+> lines](#why-the-mistakes-dont-ship)). That metadata is your **business
+> ontology** — an open, versioned definition of your objects, permissions, and
+> flows that you own, not code scattered across a framework. Strict TypeScript,
+> Zod schemas, and a validation gate catch the agent's mistakes at authoring
+> time; the runtime derives the database, REST API, UI, and MCP server, and
+> enforces permissions and audit on every call.
 
 `Fits in an agent's context` · `Typed, validated, governed` · `Self-host anywhere` · Apache-2.0
 
 **Everything in this repo is the open stack** — protocol, microkernel, SDK,
-CLI, and the production runtime, Apache-2.0 with no open-core asterisks. You
-can build, ship, and self-host real apps from here alone. Rather have the
-platform run for you, AI Builder and governance included? That's
-**[ObjectOS](https://github.com/objectstack-ai/objectos)**, the commercial
-runtime environment built on this stack.
+CLI, and the production runtime, Apache-2.0 with no open-core asterisks. The
+workflow here is **build & ask with Claude Code** (or any coding agent): the
+agent writes the metadata in your repo, and operates the running app over
+MCP. Rather **build & ask online** — in the browser, nothing to install?
+That's **[ObjectOS](https://github.com/objectstack-ai/objectos)**, the
+commercial runtime environment built on this stack.
 
 <p align="center">
   <img src="docs/screenshots/architecture.png" width="940" alt="ObjectStack architecture: author typed Zod metadata (objects, flows, views, policies); the microkernel compiles it into a versioned JSON artifact and loads plugins, drivers, and services; it generates a REST API, client SDK, Console and Studio UI, and MCP tools used by developers and AI agents, governed by Auth, RBAC, RLS, FLS, and audit, over PostgreSQL, MySQL, SQLite, or MongoDB">