# Transformative Ontology

> The canonical system that defines how Transformative Studio thinks, speaks, and presents itself.

This is the canonical Transformative-hosted Ontology. It is a public reference
for design, language, implementation, and agent workflows. Do not conflate it
with Clark Valberg's personal Ontology.

## Canonical context

- [Complete agent corpus](https://ontology.transformative.studio/llms-full.txt): Full visual, language, and implementation guidance
- [Structured manifest](https://ontology.transformative.studio/design-system.json): Versioned JSON contract
- [Design tokens](https://ontology.transformative.studio/design-tokens.tokens.json): DTCG 2025.10 token file
- [Implementation instructions](https://ontology.transformative.studio/AGENTS.md): Coding-agent rules and verification
- [Human reference](https://ontology.transformative.studio/): Rendered source of truth

## Structured access

- [MCP endpoint](https://ontology.transformative.studio/mcp): Read-only Streamable HTTP resources
- [MCP server metadata](https://ontology.transformative.studio/server.json): Preview MCP Registry-compatible descriptor
- [Schema](https://ontology.transformative.studio/design-system.schema.json): JSON Schema for the manifest

## Primary sections

- [Visual system](https://ontology.transformative.studio/#/visuals): Identity, color, typography, and hierarchy
- [Language system](https://ontology.transformative.studio/#/language): Narrative assets, lifecycle vocabulary, and canonical terms

The `llms.txt` format is an agent-discovery convention, not a ratified web
standard. The JSON manifest and rendered site remain the versioned contract.