Provider authority
The provider answers Type relationships and policy from its own model.
Compose capabilities across languages, runtimes, and tools.Share contracts. Keep implementation authority local.
Establish a shared boundary
TTX gives independently built systems one boundary for the data and operations used by an interaction. The provider controls its context. The consumer binds the contract it understands.
The boundary has three layers, each responsible for a narrower agreement.
- Data
- Describes canonical forms and transfers represented values.
- Semantic
- Agrees on the representation of a UUID contract before transfer.
- Graph
- Connects Abstract observations through provider supplied routes and capabilities.
Compose systems through the capabilities they own
A provider publishes the Type relationships and operations it can answer. Consumers navigate those relationships through the supplied Abstract.
Negotiated transfer
The provider and consumer agree on representation, access and lifetime before the consumer receives a callable interface.
Graph navigation
Routes connect Abstracts. Each provider interprets its own context.
Replaceable providers
Any provider that satisfies the contract can supply the capability.
Infrastructure in practice
The Godot image lab binds the same TTX image contracts from GDScript, C++ and CUDA. Godot requests operations through those contracts; each provider executes them under its own policy.
Native builds include CUDA. The browser uses C++ WebAssembly and GDScript. The Godot consumer stays unchanged.
Build on focused providers
TTX defines the shared boundary. Each surrounding repository owns a concrete provider domain and release boundary.