T3X
T3X is version control for structured state. It records schema-backed YAML changes as deterministic YOps patches, then versions the result with commits, diffs, merges, provenance, and generated outputs.
These docs are written for users of the future open-source distribution. Current alpha availability and package maturity are called out in Release Status.
The shortest way to understand it:
source evidence -> YOps patch -> reviewed YAML state -> commit -> leaf output
This is not a markdown dump and not a chatbot transcript archive. T3X is built for the point where source evidence, AI output, or human edits need to become trusted, replayable project state.
What T3X Gives You
| Surface | What it does | Value |
|---|---|---|
| WebUI | Chat, review YOps, inspect Canvas, create Leaf output | Turns loose source material into an auditable workflow |
| YOps | 18 declarative YAML operations | Makes every tree mutation reviewable and replayable |
| Local alpha | Packaged local entrypoint | Runs the self-hostable product without assembling every package manually |
| CLI | Preview command path for project -> draft -> YOps -> commit -> leaf | Lets scripts and terminal users drive the same state machine |
| MCP | Preview agent interface with 8 umbrella tools | Lets AI agents capture, edit, commit, diff, merge, and generate through T3X |
| API | Hono route library and standalone server | Provides the self-hosted backend and extension point for cloud |
The Core Rule
All structured-state mutation goes through YOps.
An LLM may propose a YAML operation list. A human or agent may edit that list. But the deterministic engine is the only layer that applies it. Diff, merge, validation, hash chains, and commit construction do not depend on an LLM.
Current Alpha Surface
The current alpha package surface is:
@t3x-dev/local@t3x-dev/yops
Availability follows the current release status. During restricted alpha, package access may be limited; after public availability, the same package names and commands apply through the public distribution channels.
CLI, MCP, API, WebUI, storage, core, and runner are available in this repository for source development and preview, but they are not all promoted as public npm entrypoints yet.
The open-source t3x-core repository is the self-hostable core product, not the
complete managed cloud SaaS layer. OAuth provider setup, billing, teams,
managed tenant operations, and hosted cloud operations live outside the
open-source repository. See Alpha Limitations for the
boundary.
Next Steps
- Quick Start - run the local source stack.
- Local Alpha - understand the packaged local entrypoint.
- YOps - read the mutation story and operation board.
- WebUI - see the full product workflow and screenshot map.
- MCP Preview - connect T3X to AI agents.