We would rather tell you where things stand than let you find out by clicking. This page is the single place that says what exists, what is being built, and what is still a design.
Available now
You can use all of this today. None of it needs an account, and none of it is a promise.
| What | Where |
|---|---|
| The method — Gherkin, OpenAPI, assertion strength, cross-format consistency | Spec formats |
| The template library — copy-ready starting points for REST APIs, CRUD contracts, event-driven behaviour, payment and refund workflows | Templates |
| The guides — how to apply the method to a specific domain | Guides |
| The API contracts and testing approach | OpenAPI contract testing |
| This documentation | Documentation |
The method is the part that is ready, and it is ready in the strongest sense available: it is how we build ourselves. Our own development is specification-driven — the canonical specification is the source of truth, changes are reviewed as diffs against it, and the checks that guard it are executable. What you read in these pages is a description of a process that is running, not an aspiration.
In development
This is the first thing we are building, and it is what the platform is for.
| What | Where |
|---|---|
| The box — an isolated machine on our compute, with SSH access | The box |
tnt box create / list / exec / destroy | The box |
tnt box ssh-proxy ssh — a local proxy that carries an ordinary SSH session to the box | The box |
| Box lifecycle — idle reclamation, snapshots, destruction | The box |
The point of the box is the thing it fixes: an agent that stops when your laptop sleeps. You get a machine, you get a shell, you run your own commands, and it keeps running whether or not you are connected.
Still being designed
We are working on this. It is a large piece of work and we are not going to pretend it is further along than it is.
| What | Where |
|---|---|
Drafting a specification — tnt draft | How TNTHUB works |
Clause-level review, rejection and approval — tnt review | Approval workflow |
Builds and the four verification layers — tnt build, tnt verify | Build pipeline |
Trial environments from an approved snapshot — tnt env | Trial environments |
The style guide derived from rejection reasons — tnt style | Approval workflow |
Every document in that section is a design document. They describe what the system will do, in enough detail to be argued with, and they are labelled as designs on the page itself.
Why this order
It is worth explaining, because the order is unusual.
The tempting way to build this is to start with the part that looks like the product: the model writes a specification, you review it, the platform builds it. That is the demo. It is also the part that depends on everything else working.
We started at the bottom instead. An isolated machine that runs your work, that stays up, that you can reach over SSH, and that is destroyed when you are finished — that is the hard part. Everything above it needs the same substrate: an execution environment you can trust, reproduce, and throw away.
The specification pipeline is a client of that substrate, not a replacement for it. When it ships, the build runs inside a box. You will still be able to get a shell and look at what happened — which is the same access you have today.
Starting at the bottom also means the thing we ship first is useful on its own. A remote machine for an agent that has to keep working is a real answer to a real problem, and it does not need the specification pipeline to be worth anything.
How to read the labels
Every page in this documentation carries one of three states, unless it is a normal page with nothing to declare:
| Label | What it means |
|---|---|
| (nothing) | Available now. |
| In development | Being built. Not available yet. |
| Design document | Describes what we are building. Not a feature that exists today. |
If a command appears in these docs and it does not run, that is a bug in the docs, not in your setup — tell us and we will fix it.
Next: the documentation index.