Bindings
Partly builtCode from outside Clay: what the registry is, and the four ways a binding reaches your program.
The registry lists code that comes from outside Clay and that Clay uses: a Parquet reader, a native matrix multiply, a model’s weights. Clay libraries are not in it; those are shared by hash from a codebase. Each binding pins the exact bytes, says how Clay may use them and where they run, and is signed.
It is at bindings.withclay.org.
Four ways a binding reaches Clay
A binding has one or more of four roles. The role answers the question a visitor brings: can my program call this, and what does that mean?
Handler. It answers an ability. Your program’s type says it needs the ability (<Tensor>); policy decides which handler answers, and a handler written in Clay can answer in tests. Example: clay-tensor-host, a native program that answers Tensor and Tokenizer on a server.
Accelerator. It runs instead of one exact Clay definition, only faster. The Clay code stays the meaning. If the definition changes, its hash changes, no claim matches and the Clay code runs: never wrong, only slower. Example: clay-kernel runs Json.fromText natively.
Data. Files a handler reads, such as a model’s weights. The registry may keep only the fingerprints and say where to fetch the files. Example: gpt2-small-weights.
Built in. Loaded by Clay’s own tools: the editor, Phaistos, the runner. Your programs don’t call it, so it never appears in their types. Example: hyparquet, which Phaistos uses to import Parquet files.
A binding can have more than one role. clay-kernel is built in (the editor loads it) and is also an accelerator.
Where a binding runs
Each binding says where it runs: Browser, Server, or Clay Cloud (shown dashed: designed, not built). A native program also names its platform, such as macOS on Apple silicon. Data runs “with its handler”.
The same facts read as four tags: Host (Browser, Native), Compute (CPU, GPU), Platform and Network (Offline, Online). The list can be filtered by them, and ?node=cloud-nbg1-1 on the list shows what runs on a node and, for each binding that does not, the one facet that stops it (“Needs macOS arm64”). A binding’s own page has a Runs on section: the same check from the other side. None of this changes a manifest or its id: the tags are derived from kind, runsIn, platforms and needs.
What a tick means
Every binding is signed. A tick on the registry means the binding has not changed since it was signed, by a key the page checked when it was built. It does not mean the code is safe. Today every signature is by a development key; see Trust and signing.
What is built
The registry is a static site with a signed manifest for each binding, signed stand-in claims, a revocation list, and the function a runner calls before loading (checkLoadable). The runner does not call it yet, there is no production key, and nobody outside the team can publish. Each page here says what is real.