/technology/capabilities/ · The whole surface
Every capability, its status, and the evidence.
Two things are described here and the label controls the tense. Harness is the open-source Rust core, and most of it is shipping in the public repo today. Cratefield is the managed service that would run it, and it is not running yet. Nothing below claims otherwise, and every shipping row links to the code that backs it.
Shippingmerged, tested, in the public repo Designedspecified in public issues, unbuilt Plannednamed, unspecified
| Capability | What it is | Status | Evidence |
|---|---|---|---|
| Harness core | Module trait, Harness builder, ten ports, problem+json errors, request scope, event bus, template registry | Shipping | cratefield-core |
| Edge runtime | D1, KV, rate limiting and wait_until mapped to ports | Shipping | cratefield-runtime-cloudflare |
| Adapters | Resend, Turnstile, SQLite, Postgres | Shipping | crates/adapter-* |
| Modules | email-signup, waitlist, cms; each declares a UI surface | Shipping | crates/module-* |
| fz CLI, conformance kit, contract versioning | CI: fmt, clippy -D warnings, tests, cargo deny, worker-build --release | Shipping | .github/workflows |
| Postgres adapter, native runtime | The same modules as a native tokio binary on Postgres; every module tested against both engines; fz data export moves a venture across | Shipping | #18–#21 |
| Auto-constructed UI | Modules declare a surface; the harness serves /__surface, renders forms and admin pages at /ui, and ships a 4 KB embed for static sites | Shipping | cratefield-ui |
| Auth: passkeys, Google | Sessions, account linking, authorization code + PKCE, ES256 JWTs with JWKS, and a client crate that verifies them | Shipping | Factory-Zero/auth |
| Auth: the rest | Apple, Meta, email and password, magic links, rate limiting and lockout | Designed | #16–#21 |
| Sidecar mount | A module as its own worker over a service binding, mounted at the same path, its surface merged into /__surface | Shipping | #57, #60, #76 |
| Sidecar programme | Build-artifact cache, cold-start handshake, module template, conformance parity across both mounts, deployment model (#67 decided for v1) | Designed | #56, #59, #61–#67 |
| Multi-tenant schema system | Per-tenant migration history and checksums ship; boot-time reconciliation and one database per tenant on the native runtime are specified, unbuilt | Designed | #23, #26–#36 |
| Secrets, KMS, audit | Two-tier secrets, envelope encryption, KMS trait, tamper-evident audit chain, key rotation | Shipping | crates/secrets, crates/kms |
| Cratefield control plane | Sign in behind a whitelist, pick modules, connect Google, get a running backend: accounts, catalog, connections and the provisioning engine | Planned | building · private, not yet running |
| Hosted on our account | Workers for Platforms, dispatch namespaces | Planned | a pre-scale upgrade, not adopted |
| Published crates | 18 crates on crates.io, MIT. cargo add cratefield pulls the core and picks a runtime, adapters and modules by feature | Shipping | crates.io/crates/cratefield |
The three modules each have a page under /technology/modules/, with the ports they ask for and the routes they serve. The managed control plane is being built in a private repository; when it runs, this table says so and links to it. Until then it stays Planned, and no fee for it is purchasable.