HTTP carries hypertext. SMTP carries mail. TCP carries bytes. Every protocol defines a capsule — a unit of transfer — and the semantics that govern what happens when it arrives. We have never defined one for context: the structured information an agent needs to act. Every tool invents its own packaging. Skills arrive as zip files, git repos, bash scripts, paste-and-pray markdown. Nothing composes.
The bitter lesson of AI research is that scale beats craft. The same lesson is landing in software: context beats interfaces. You don’t need a perfectly typed API when you have a capable model — you need context that transfers reliably across boundaries. CTP/1.0 is the wire format for that transfer. Three layers, three operations, one file. It reads as markdown. It runs as bash. The format is the executable.
| Operation | Syntax | What it does |
|---|---|---|
| pack | fold <dir> | Serialize a directory tree into a single capsule file |
| ship | xdown <capsule.md> --url <url> | Host the capsule; wrap with transport layer and self-install semantics |
| land | land: <directive> | Declare what the receiver does on arrival — resolved at unpack time |
| Operation | Implementation | Endpoint | Status |
|---|---|---|---|
| pack | fold | fold.dom.vin | live |
| ship | xdown | xdown.dom.vin | live |
| land | — | — | draft |