Introduction
T3x is semantic version control for AI conversations. It captures meaning — across conversations, drafts, and revisions — as a verifiable semantic lineage that teams can branch, compare, and commit with deterministic clarity.
What is Semantic Version Control?
Traditional version control (like Git) tracks changes in code. T3x applies the same principles to meaning.
| Git (Code) | T3x (Meaning) |
|---|---|
| Lines of code | Clauses — atomic units of intent |
| File changes | Turns — each message in a conversation |
| Commits | Commits — snapshot semantic state |
| Branches | Branches — parallel exploration of ideas |
| Diff | Diff — what changed at the semantic level |
| Merge | Merge — combine branches with conflict detection |
The key insight: When you track meaning instead of text, you can compare what someone said across versions — not just how they typed it.
Architecture
T3x consists of three components:
| Component | Technology | Purpose |
|---|---|---|
| CLI | TypeScript/Node.js | Interactive shell for conversations |
| Core API | Python/FastAPI | Semantic processing engine |
| WebUI | React/TypeScript | Visual workflow management |
┌─────────────┐ ┌─────────────┐ ┌─────────────┐
│ CLI │────▶│ Core API │◀────│ WebUI │
│ (chat) │ │ (semantic) │ │ (visual) │
└─────────────┘ └─────────────┘ └─────────────┘
Core Concepts
Three Semantic Layers
Every piece of text is analyzed through three layers:
-
Clauses — The minimal unit of intent. Subject-verb-object structures that carry complete meaning.
-
Relations — How clauses connect. Supports, contradicts, elaborates.
-
Facets — Keywords that anchor meaning. Entities, terms, topics that humans can verify.
The Lineage Protocol
Every turn and commit is cryptographically linked:
turn_1 → turn_2 → turn_3
↓
commit_a → commit_b
- Turn chain:
prev_turn_hash → turn_hash(SHA-256) - Commit chain:
parent_hashes → commit_hash - JCS canonicalization for deterministic hashing
Quick Example
# Start a conversation
T3x> /new japan-trip
T3x> What's the best time to visit Tokyo?
# LLM responds...
# Create a draft from the conversation
T3x> /draft summary
# Commit when satisfied
T3x> /commit draft_abc123 --msg "Initial trip research"
# Later, branch to explore alternatives
T3x> /branch budget-version
T3x> What if I only have 5 days?
# Compare versions
T3x> /diff main budget-version
Next Steps
- Quick Start — Get up and running in 5 minutes
- CLI Reference — Full command reference
- API Reference — REST API documentation
- Concepts — Deep dive into semantic layers