The words
Partly builtWhat each word on the registry means: binding, artifact, the four roles, stand-in claim, wrapper, Runs in, Form.
These are the words the registry, its pages and the manifest use. The first column is what you read; the third is where it is in the manifest, for people who need it.
| Word | Means | In the manifest | Not called |
|---|---|---|---|
| Binding | One signed record in the registry: a name, a version, the exact bytes, and what Clay may do with them. | a manifest | Package (taken by Clay libraries), plug-in, extension (accelerators add no features) |
| Artifact | The exact bytes a binding pins, known by their SHA-256 fingerprint. A runner refuses anything else. | artifact |
|
| Handler | A binding that answers an ability. The program’s type says it needs the ability; policy decides which handler answers; a Clay handler can answer in tests. | interface.abilities |
Binding, provider, ability seam |
| Accelerator | A binding that runs instead of one exact Clay definition, only faster. It has no effects and changes no answers; the Clay code stays the meaning. | entries and claims |
Native, intrinsic, substitution (kept for the mechanism) |
| Stand-in claim | A signed statement that one of an accelerator’s entry points stands in for one Clay definition, by hash, with the evidence. Signed separately, so adding one never changes the binding. | substitution claim | |
| Data | Files a handler reads, such as a model’s weights. The registry may keep only the fingerprints and where to fetch them. | kind: weights |
Weights (too narrow: datasets will come) |
| Built in | A binding Clay’s own tools load (the editor, Phaistos, the runner). Your programs don’t call it, so it never appears in their types. | uses: ["built-in"] |
Runtime, internal |
| Wrapper | Clay code that declares an ability and gives it friendly functions over a handler. It lives with Clay code, not in the registry; a binding links to it. | none | |
| Runs in | Browser, Server, or Clay Cloud (designed, not built). A native program also names its platform: macOS on Apple silicon, Linux x86-64. | runsIn, platforms |
Host type |
| Host | Where a binding can run: Browser (a tab) or Native (a process on a machine). Most WebAssembly and JavaScript can do both. | runsIn (browser; server and cloud read as Native) |
|
| Compute | CPU or GPU: what a binding needs, and what a node has. CPU runs anywhere. | derived (CPU today) | |
| Platform | For a native program only: the operating system and chip it is built for, such as macOS arm64 or Linux x64. | platforms |
|
| Network | Offline or Online: whether a binding needs the internet, and whether a node lets jobs reach it. | needs.network |
|
| Node | Somewhere Clay code can run: Clay Cloud’s server, a machine of yours, or the browser tab you are reading this in. Listed on the Nodes page in Clay Cloud. | none | |
| Form | What the bytes are: JavaScript, WebAssembly, Native program, Data files. | kind |
|
| Same answer every time | Same input, same output, on any machine. The alternative is “May change between versions”. | determinism: pure |
Pure, deterministic |
A binding can have more than one role
clay-kernel is built in and also an accelerator (three definitions). A future Parquet binding could be built in for Phaistos and a handler for a Parquet ability.
Optional manifest fields
uses lists the roles and runsIn and platforms say where the binding runs. They are optional and present only when set, so every manifest written before them keeps its id. When a manifest has none, the registry page infers them: JavaScript and WebAssembly run in the browser and on a server, a native program on a server, data with its handler; a binding is an accelerator if any claim names it, a handler if its interface lists abilities, data if it is weights, and otherwise built in.