Roadmap
What is available now, under development, next, and coming soon across the Numinance public tree, with no dates and no package names promised.
Available
These exist in the public numinance-spec tree at revision 3c74d59 and can be exercised from a source build. Pre-alpha still applies.
- The open
numibuild:version,init,validate,validate --files,evidence verify. See Install. - The protobuf contracts, generated JSON Schemas and kind examples. See Protocol.
- The
evidence/v1specification, the offline Go verifier and the conformance vectors. See Evidence. - The Go SDK, with handwritten packages and generated stubs. See Go SDK.
- The sample knowledge plugin and the conformance kits (authorexecutor, ciexecutor, evidence, evidencestore, knowledge, sandboxprovider, scm, ticketing, transparencylog, verifier).
Under development
Part of the designed architecture. Interfaces may change, and none of it is installable from the public tree.
- The Numinance engine, the proprietary autonomous runtime. See Architecture.
- Managed and sovereign deployment with a customer-controlled data plane. See Deployment modes.
- The unified
numicommand surface beyond the open build (run,connect,plan,approve,doctor) andnumi evidence export. - Live verification of the official providers. Presence under
plugins/official/is not a readiness claim.
Next
Direction that follows from the current state of the tree. No order or date is implied.
- A first tagged release of the public repository, after which versioning rules apply to tagged packages.
- Verified, published packaging for the generated Python and TypeScript stubs, and an ergonomic plugin SDK for each.
- Additional languages and source-control providers for
numi init, which today scaffolds Python and GitHub only. - Wiring the sample knowledge plugin into the conformance replay.
Coming soon
A Rust SDK is on the roadmap. There is no crate, version, import path or date. Until it exists, generate clients from the .proto files with your own toolchain.
A Java SDK is on the roadmap. There are no Maven coordinates, version, import or date. Until it exists, generate clients from the .proto files with your own toolchain.
Air-gapped operation is a later design milestone that follows managed and sovereign deployment. It is not available and is not scheduled.
Planned distribution
Two install channels are intended and neither is published. These docs give no command for either, and will not until the artifacts are published and verified.
| Capability | State | Public surface | How to try | Next milestone |
|---|---|---|---|---|
| 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 |
Until then the only supported way to get numi is a source build. See Install.
How items move
An item moves up this page only when the public tree supports it: a source file, a schema, a conformance vector or a verifier run. A change of state is a change to the capability table that backs the Status matrix, so the two pages cannot disagree.