Status and supported surface
A source-backed matrix of what the public Numinance tree ships, what is designed, and what is deliberately not claimed. Dated 2026-11-09, spec revision 3c74d59.
numi build and the evidence verifier are in the public tree; the autonomous engine is private and not generally available.This page is dated 2026-11-09 and describes numinance-spec at revision 3c74d59. It is a snapshot of one checkout, not a promise about later ones. Every row links to the source that backs it where one exists. Presence in the public tree is never a readiness claim.
How to read the matrix
Each row has a state, the public surface, how to try it, and the next milestone. The state vocabulary is fixed.
Open CLI
The open build of numi has five working functions: version, init, validate, validate --files and evidence verify. The earlier version of this page omitted numi init; it ships in the open build and writes a .numinance/ template for a Python repository.
| Capability | State | Public surface | How to try | Next milestone |
|---|---|---|---|---|
| numi version Open CLI | Available in public spec | Open build of numi | go run ./cli/numi version | Tagged releases |
| numi init Open CLI | Available in public spec | Scaffolds .numinance/ for a Python repository | go run ./cli/numi init --ci github-actions <repo> | More languages and SCM providers |
| numi validate --files Open CLI | Available in public spec | Strict schema + loader check of kind documents | go run ./cli/numi validate --files schemas/examples | None: profile resolution lives in the engine build |
| numi validate (repository) Open CLI | Available in public spec | Schema pass, then exit 7: profile resolution needs the engine build | go run ./cli/numi validate <repo> | Full resolution ships only in the private engine build |
| numi run / connect / plan / approve / doctor Open CLI | Under development | Designed command surface of the unified CLI | Not in the open build | Engine build; interface subject to change |
| numi evidence export Open CLI | Under development | Engine-side export of an evidence bundle | Unknown subcommand in the open build (exit 2) | Engine build |
Two details matter more than the table:
- Ordinary
numi validatein the open build schema-checks every document, then exits 7 with "profile resolution needs the Numinance engine build". A pipeline that uses it cannot mistake a schema pass for a full one. numi validate --filesexits 0 after the schema and loader check only. It runs no resolver and no floors, so it is not a substitute for validating a repository.
Evidence
| Capability | State | Public surface | How to try | Next milestone |
|---|---|---|---|---|
| numi evidence verify Evidence | Available in public spec | Offline verifier over an evidence/v1 export | go run ./cli/numi evidence verify --runner-key … --log-key … --log-origin … DIR | Engine build delegates to the same package |
| evidence/v1 specification + conformance vectors Evidence | Available in public spec | docs/evidence/, schemas/evidence/v1/, conformance/evidence/v1/ | Verify a golden export offline | Independent third-party implementations |
numi evidence verify reports verified only under runner keys, a log key and a log origin that you pin. There is no built-in trust root. numi evidence export is not in the open build: it is an unknown subcommand and exits 2.
Protocol
| Capability | State | Public surface | How to try | Next milestone |
|---|---|---|---|---|
| Protobuf contracts Protocol | Pre-alpha | PluginService, HostService, ports, annotations, kinds | Read proto/numinance/ | First tagged release (see VERSIONING.md) |
| JSON Schemas and kind examples Protocol | Available in public spec | Generated kind schemas and schemas/examples/ | numi validate --files schemas/examples | Additional kinds as they are accepted |
The protobuf contracts are pre-alpha: names and layouts can change before the first tagged release. The generated JSON Schemas and the kind examples are exercised by numi validate --files schemas/examples in CI.
SDKs
| Capability | State | Public surface | How to try | Next milestone |
|---|---|---|---|---|
| Go SDK SDKs | Pre-alpha | Handwritten plugin, kindyaml, schema, cli, evidenceverify + generated stubs | go test ./sdk/go/... | Tagged module release |
| Python SDK SDKs | Pre-alpha | Generated Protobuf/gRPC stubs (version 0.0.0) | Generate from source; not a verified PyPI package | Ergonomic plugin SDK; publication when verified |
| TypeScript SDK SDKs | Pre-alpha | Generated protobuf-es code, private package at 0.0.0 | Build from source; not a verified npm package | Ergonomic plugin SDK; publication when verified |
| Rust SDK SDKs | Coming soon | No source distribution yet | Generate clients from the .proto files with your own toolchain | Roadmap; no date, crate name or version promised |
| Java SDK SDKs | Coming soon | No source distribution yet | Generate clients from the .proto files with your own toolchain | Roadmap; no date, coordinates or version promised |
- Go has handwritten packages (plugin, kindyaml, schema, cli, evidenceverify) plus generated stubs.
- Python and TypeScript hold generated stubs only. The Python version is
0.0.0; the TypeScript package is private at0.0.0. Neither is a verified published package, so no install command is given. - Rust and Java are Coming soon. Until they exist, generate clients from the
.protofiles with your own toolchain.
Integrations
| Capability | State | Public surface | How to try | Next milestone |
|---|---|---|---|---|
| Sample knowledge plugin Integrations | Available in public spec | A host-launched Go provider of numinance.ports.knowledge.v1 | go build ./plugins/examples/sample-knowledge | Conformance replay wiring |
| Official providers (GitHub SCM, GitHub Actions, verifiers) Integrations | Pre-alpha | Source and tests under plugins/official/ | go test ./plugins/official/... | Live-run verification; presence is not a readiness claim |
The sample knowledge plugin builds and refuses to run by hand, by design; it has no unit tests (go test reports no test files for it). The official providers sit under plugins/official/. A live run of the GitHub Actions provider is not yet verified.
Runtime
| Capability | State | Public surface | How to try | Next milestone |
|---|---|---|---|---|
| Numinance engine (autonomous runtime) Runtime | Under development | Private, proprietary; not generally available | Not installable | Not scheduled publicly |
| Managed and sovereign deployment Runtime | Under development | Customer data plane + thin vendor control plane | Not installable | Design partners (pre-alpha) |
| Air-gapped deployment Runtime | Coming soon | Later design milestone | Not available | After managed and sovereign |
The engine is proprietary. There is no installer, no download and no hosted trial described anywhere in these docs.
Distribution
| Capability | State | Public surface | How to try | Next milestone |
|---|---|---|---|---|
| GitHub source build of the open CLI Distribution | Available in public spec | git clone + go run / go build | See Install | Tagged releases |
| GitHub Releases binaries Distribution | Planned distribution | Signed binaries with checksums | Not published; no command given | Verify release artifacts first |
| Homebrew Distribution | Planned distribution | Tap/formula | Not published; no command given | Verify formula first |
The only install path that exists is a source build from a clone. GitHub Releases and Homebrew are planned channels, not published ones, so the install page gives no command for either.
What is not claimed
- No generally available release and no tagged release of the public repository.
- No production customers, certifications, benchmarks, uptime or reliability figures.
- No independent third-party audit.
- No live demo of the engine, and no claim that the engine runs outside the maintainers' own environments.
- No provider readiness: a provider being present in
plugins/does not mean it is verified against a live system. - No claim that
verifiedevidence proves code correctness. It proves provenance and chain integrity under keys you pinned. - No published Python, TypeScript, Rust or Java packages.
Reading source paths
Pages cite paths such as proto/numinance/plugin/v1/plugin.proto. They are relative to the root of the public numinance-spec repository, where the normative text lives. The Go module path is github.com/numinance/numinance-spec; the clone URL is https://github.com/dsha256/numinance-spec.git.
Next steps
Evidence quickstart
Verify a real evidence/v1 export offline under pinned keys, then watch a wrong key, a self-stated trust bundle and skipped signatures each change the result.
Concepts
The mental model behind Numinance - what an autonomous engineer is, how authority is separated from intelligence, and what you can check afterwards.