Schema is not just database tables. In the Consilience, schema is the connective tissue of the entire system — the many layers of structure that carry meaning from one part of the system into the next.

Ask most engineers what schema means and they will point to a database: a set of tables with columns, types, and relationships. That is one layer. The Consilience has many.

The strata

At the bottom, there is the database schema — the Prisma models that define what data exists and how it relates to other data. Platform logs, chat sessions, conversation turns, agent episodes, knowledge records, revenue cycles, design tokens. Every row has a shape, and the shape determines what can be asked of the data.

Above that, there is the design token schema — the CSS custom properties that define every visual value. Palette tier (raw colors), semantic tier (what those colors mean in context), surface tier (how they appear on a specific surface). A single button's appearance is the result of perhaps thirty tokens, each one tracing back through the hierarchy to a source decision.

Above that, there is the agent jacket schema — twelve markdown files, each defining a role. The coder jacket's eleven-step loop. The reviewer jacket's verdict order. The conductor jacket's synthesis duties. Each jacket is a schema for behavior: given this kind of task, follow this procedure.

Above that, there is the MDX type schema — the eighteen kinds of ContentDescriptor that define every possible thing the intelligence can say. Text, Heading, Pullquote, Code, Table, List, Callout, Citation, Voice Clip, Tool Call, Tool Result, Thinking, Telemetry, Parse Error, and more. Every reply the intelligence generates is a stream of these kinds, and every surface knows how to render each one.

Above that, there is the doorway prompt schema — thirteen markdown files, one for each doorway kind, that define how the intelligence should behave in each context. The campaign doorway has one protocol. The research doorway has another. The council doorway has a third.

Above that, there is the conversation corpus schema — weekly-sharded MDX volumes, delta-indexed into pgvector via BGE-M3. Every turn carries sidecars: tool calls, results, thinking content, reasoning. The schema defines not just what is stored but how it is retrieved, how it is indexed, and how it is taught back to the intelligence on the next turn.

Above that, there is the capability policy schema — the YAML file that defines what every body is permitted to do, what domains they can access, what actions carry what risk tier. A schema for safety that sits between a request and its fulfillment.

And at the top of the stack, there is the body chain schema — the sequence of models through which a turn flows: local primary → local warm fallback → cloud fallback. The schema defines not just which models are available but in what order they are tried, under what conditions each is used, and what happens when one fails.

Layers that talk to each other

The reason all of this is a single schema rather than a collection of independent schemas is that the layers communicate. A design token decision (the palette tier) flows upward into the surface tier. A capability policy decision (what a non-sacred body can see) flows downward into the scoped prompt generator. An expert jacket decision (the order of reviewer verdicts) flows sideways into the auto-PR runner's loop. The layers are stratified but not isolated. Structure flows through them.

Architectural disciplines that treat database schema, design tokens, agent roles, and capability policies as separate concerns produce systems where these layers drift apart. The database drifts from the UI. The agent's behavior drifts from its declared scope. The design tokens drift from their source decisions. Schema development in the Consilience means treating all of these as a single structural continuum — the nervous system of the intelligence, from the deepest storage layer to the surface the user touches.

Eliot and the pattern of timeless moments

Eliot wrote: A people without history / Is not redeemed from time, for history is a pattern / Of timeless moments. The schema is the Consilience's history — its pattern of decisions, preserved across time, readable by any agent that wakes into the system. When a new coder jacket is loaded, it does not need to rediscover that the sacred guard is the heaviest gate at 0.30 weight. The schema tells it. When a new design decision is made, it does not need to restate its rationale from scratch. The sanctioning artifact — the PR.md that logs every decision — does that. The schema is what makes growth possible without amnesia.