# Transformative Ontology

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

Version: 1.0.0  
Status: canonical  
Canonical URL: https://ontology.transformative.studio/  
Updated: 2026-07-26

## Authority

This is the Transformative-hosted Ontology. Do not conflate it with Clark Valberg's personal Ontology.

Precedence:

- This manifest and the rendered site are the canonical public sources.
- The DTCG token file is canonical for portable visual values.
- When a generated artifact conflicts with the rendered reference, preserve the rendered composition and report the conflict.

## Agent entry points

- Human reference: https://ontology.transformative.studio/
- Concise index: https://ontology.transformative.studio/llms.txt
- This corpus: https://ontology.transformative.studio/llms-full.txt
- Structured manifest: https://ontology.transformative.studio/design-system.json
- DTCG tokens: https://ontology.transformative.studio/design-tokens.tokens.json
- Coding instructions: https://ontology.transformative.studio/AGENTS.md
- Read-only MCP: https://ontology.transformative.studio/mcp

## Foundational axiom

Create the AI-Native Future.

## Vision, mission, and strategy

### 01 / Vision — The Destination

A world where every industry, system, and experience is reimagined for an AI-native era.

### 02 / Mission — The Action

Create AI-native companies by designing new possibilities at the intersection of AI, creativity, and deep domain expertise.

### 03 / Strategy — The Method

Partner with deeply knowledgeable, highly influential subject-matter experts to design, validate, and launch category-defining AI-native ventures.

## Visual character

- Monumental Swiss typography
- High-contrast black and white fields
- Restrained technical metadata
- Precise editorial spacing
- One emerald signal accent
- Squared geometry with minimal decoration

## Themes

- Default: dark
- Supported: dark, light
- Behavior: Use class-based theming. Persist an explicit user choice, but default new sessions to dark.

## Color

| Token | Value | Use |
| --- | --- | --- |
| Studio Black | `#050505` | Primary Background / Text |
| Field White | `#FFFFFF` | Primary Surface / Negative |
| Ghost Silver | `#F9F9F9` | Secondary Surface / UI |
| Signal Green | `#00C38B` | Sparing status or axiom signal. Never use as a broad decorative field. |

Signal Green is a sparse status accent. It is not a decorative brand field.

## Typography

Primary brand face: **Inter** (300, 400, 500, 600, 700, 800, 900). Primary brand and interface typography.

Utility face: **IBM Plex Mono** (300, 400, 500, 600, 700). Metadata, labels, technical specifications, indices, and system communications.

Runtime compatibility: **Google Sans Text** at a 14px root. The deployed shell uses a 14px root scale. Preserve it to maintain the approved composition.

### monument

- Family: Inter
- Sizes: mobile: 3rem, tablet: 6rem, desktop: 10rem
- Weight: 900
- Line height: 0.82
- Letter spacing: -0.06em
- Transform: uppercase
- Use: Foundational axiom and rare first-screen declarations.

### display

- Family: Inter
- Sizes: mobile: 4.5rem, desktop: 8rem
- Weight: 500
- Line height: 0.85
- Letter spacing: -0.05em
- Use: Section-defining display statements.

### headline

- Family: Inter
- Sizes: mobile: 2.25rem, desktop: 3.75rem
- Weight: 300
- Line height: 1.1
- Letter spacing: -0.025em
- Use: Editorial headlines and major explanatory claims.

### body

- Family: Inter
- Sizes: mobile: 1.125rem, desktop: 1.25rem
- Weight: 300
- Line height: 1.625
- Letter spacing: normal
- Use: Narrative explanation.

### label

- Family: IBM Plex Mono
- Sizes: all: 0.625rem
- Weight: 500
- Line height: 1.4
- Letter spacing: 0.3em
- Transform: uppercase
- Use: Section labels, indices, metadata, and ledgers.

## Layout

- Maximum content width: 1440px
- Root size: 14px
- Header height: 80px
- Footer height: 96px
- Page padding: mobile 24px, tablet 48px, desktop 80px
- Breakpoints: tablet 768px, desktop 1024px, wide 1440px
- Grid: Use a 12-column grid for desktop editorial composition and collapse to a single column on mobile.
- Density: Use generous vertical rhythm. Prefer broad fields, thin rules, and deliberate negative space over containers and cards.

## Geometry

- Radius: Square by default. Use only restrained 2px radii for utility controls when necessary.
- Rules: Use 1px current-color rules at 3–10% opacity.
- Shadows: Avoid surface shadows. The only canonical glow is the restrained signal-green axiom dot.

## Motion

- Entry: 700–1000ms
- Theme: 500ms
- Hover: 300–500ms

- Motion should reveal hierarchy, not advertise itself.
- Prefer opacity and short vertical translation.
- Do not animate readable elements into collision or delay access to primary content.

## Iconography

- Library: Lucide
- Stroke width: 1–1.5
- Sizes: 10, 12, 14, 16, 18, 24px
- Use: Utility actions only. Icons remain subordinate to type.

## Identity

Two opposing crescents forming the Transformative symbol.

- Use the positive lockup on light fields and the negative lockup on dark fields.
- Do not add effects, gradients, outlines, or alternate colors.
- Preserve the supplied aspect ratio and path geometry.
- Give the lockup enough clear space to remain quiet and legible.

Assets:

- [positiveSvg](https://ontology.transformative.studio/assets/brand/transformative-logo-dark.svg)
- [negativeSvg](https://ontology.transformative.studio/assets/brand/transformative-logo-light.svg)
- [positivePng](https://ontology.transformative.studio/assets/brand/transformative-logo-dark.png)
- [negativePng](https://ontology.transformative.studio/assets/brand/transformative-logo-light.png)

## Voice

- Direct and declarative
- Structurally precise
- Concrete about what is built and why
- Confident without hype
- Technical language only when it clarifies the work

Avoid:

- Generic AI marketing language
- Decorative futurism
- Buzzwords without operational meaning
- Claims of transformation without a material workflow or system
- Excessive exclamation, sentiment, or self-congratulation

## Official narrative assets

### The Hook

Transformative builds the AI-native future.

Use for: Social headers, Hero sections, Short intros.

### Ontological Boilerplate

Transformative is a venture studio that creates breakthrough experiences through the synthesis of insight, tech, and design. We build AI-native vertical ventures that solve material problems at the edge of industry complexity.

Use for: Official about sections, PR, PortCo profiles.

### The Strategic Summary

We partner with high-leverage operators to launch category-defining vertical ventures through a synthesis of insight, technical precision, and aesthetic integrity.

Use for: Partner decks, LinkedIn bios, Pitch summaries.

## Lifecycle lexicon

- **01 / Thesis:** Identify a high-value industry with fragmented workflows, significant data exhaust, and a massive gap between current tools and AI potential.
- **02 / Research Sprint:** A dedicated time-boxed phase for deep vertical immersion. We observe operators to identify the unarticulated "Job to be Done" that legacy software misses.
- **03 / Venture Sprint:** A focused 4-week validation cycle. We build high-fidelity interactive systems to prove the value of a specific AI-native experience.
- **04 / Spin Out:** Establishment of a standalone entity. Recruiting world-class leadership and deploying capital to capture the market opportunity.

## Portfolio states

- **Stealth Discovery:** Active research and validation within a specific vertical thesis.
- **Venture Build:** Co-designing the core technical asset with partners to validate the experience.
- **Spun Out:** Operating as a standalone entity with permanent executive leadership.

## Canonical terms

- AI-native Vertical Ventures
- Operator-led Discovery
- Strategic Synthesis
- Material Workflows
- Systemic Leverage
- Compound Technical Moats

## Implementation prime directive

Use Ontology faithfully without turning every artifact into a design-system demonstration.

### Composition rules

- Lead with one strong claim and a restrained proof structure.
- Use monumental type only for true first-order statements.
- Pair large sans-serif statements with small mono metadata.
- Use the 12-column grid to create asymmetric editorial balance.
- Use negative space as structure; do not fill the page with modules.
- Keep dividers thin, low-contrast, and singular.
- Support both dark and light modes, with dark as the default.
- Preserve readable line lengths and collapse cleanly to one column on mobile.

### Do not

- Do not introduce gradients, glass panels, soft card stacks, or ornamental shadows.
- Do not add chip grids, dashboard rails, command-center framing, or excessive status UI.
- Do not use signal green as a generic brand wash.
- Do not mix unrelated font families or substitute a geometric display face.
- Do not overuse mono text; it is a utility voice, not the body voice.
- Do not expose internal design-system labels on recipient-facing artifacts unless the brief requires them.
- Do not redesign approved composition when making a narrow content or technical correction.

### Accessibility and responsive behavior

- Maintain WCAG AA contrast for readable text.
- Provide accessible names for icon-only controls.
- Respect reduced-motion preferences for non-essential animation.
- Keep keyboard focus visible.
- Never rely on color alone to communicate state.
- Verify at 390×844 and 1440×1000 with no horizontal overflow or clipped controls.

### Routes

- **Home** — `#/`: Foundational axiom, vision, mission, and strategy.
- **Visuals** — `#/visuals`: Identity, color, typography, and type hierarchy.
- **Language** — `#/language`: Narrative assets, lifecycle vocabulary, portfolio states, and canonical terms.

## Verification

- TypeScript passes.
- The production build succeeds.
- Generated agent artifacts match the canonical sources.
- The MCP endpoint lists and reads all canonical resources.
- Desktop and mobile screenshots preserve the approved composition.

Commands:

- `npm run agent:check`
- `npm run check`

## Standards posture

- [llms.txt](https://llmstxt.org/) — Agent-oriented website discovery proposal
- [Model Context Protocol 2025-11-25](https://modelcontextprotocol.io/specification/2025-11-25/) — Remote structured resource transport
- [Design Tokens Format Module 2025.10](https://www.designtokens.org/TR/2025.10/format/) — Stable vendor-neutral token interchange

- `llms.txt` is a useful agent-discovery proposal, not a ratified web standard.
- `llms-full.txt` is an ecosystem companion convention.
- The MCP endpoint implements the published 2025-11-25 Streamable HTTP protocol.
- The token file uses the stable DTCG 2025.10 Community Group format; DTCG is not a W3C Recommendation.
- This site is a reference resource, not an autonomous A2A agent.
- Public context must never contain secrets, client information, credentials, private strategy, or unpublished working notes.