Definition
Schema gravity is the tendency for systems to drift toward whatever their schemas, contracts, and validators will accept.
If a schema becomes the easiest path through the gates, the system will “fall” into it.
Why it matters in agentic work
Agents follow constraints. If your schemas are explicit and enforced, agents naturally converge on:
- consistent data shapes,
- predictable output formats,
- and safer interfaces.
If schemas are loose or wrong, agents still converge—just into a swamp of edge cases.
How to use it intentionally
- Put schemas at boundaries (API inputs, config, content collections).
- Validate early and loudly.
- Generate docs from schemas so definitions stay aligned.
- Add schema checks as gates in a gated multi-agent flow.
Symptoms of bad schema gravity
- “Works locally” but fails in CI because validation differs
- Silent coercions (“string or number, we accept both”) creating ambiguity
- Agents guessing fields because the schema doesn’t say
This often shows up as context starvation: the agent doesn’t know what shape is expected, so it improvises.
A concrete example
If a glossary term schema requires:
slugdescriptionaliases[]
…then “definition pages” automatically become linkable and indexable, because the content structure is enforced.
Practical rule
Prefer one strong schema with a few escape hatches over ten informal “conventions.”