Skip to content
Numinance

Integrations

Open interfaces, not custom plumbing.

Numinance reaches the systems engineers already use through provider and adapter contracts. The contract is public. The intelligence behind it is not.

Provider and adapter contracts

  1. 01

    Ports define the contract

    A port is a typed interface for one kind of engineering capability: source control, CI, verification, knowledge. Every port uses the same request, result and diagnostic conventions.

  2. 02

    Adapters implement it

    A provider or adapter connects an existing system to a port. Swapping one adapter for another does not change how the engine reasons or how policy is evaluated.

  3. 03

    Boundaries are declared

    An adapter states what it may and may not do. The host enforces that declaration. Extension happens through typed, governed interfaces instead of unrestricted access.

Select a port. Select an adapter.

See the shared contract and the capability boundary an adapter declares.

Interactive architecture preview

Adapters

Reads and proposes changes to repositories.

Shared contract · Source control

  • Typed requests and results for repository operations
  • Every call carries the action context of the requesting principal
  • Failures return structured diagnostics, not free text

Declared capability boundary · GitHub source-control provider

May

  • Read repository content within the granted scope
  • Propose a change for review

May not

  • Hold reusable credentials
  • Merge or release without the required identity
  • Reach outside the declared scope

Illustrative summary. Typed, governed interfaces instead of unrestricted access; each provider's manifest declares its capabilities and network destinations. Authoritative contracts are the protos under numinance-spec/proto/numinance/ports.

Labels name where each provider sits in the public tree (numinance-spec/plugins). Pre-alpha: presence in the tree does not imply production support.

Adapter development and conformance

Building an adapter means implementing a port and declaring its boundary. Conformance suites are intended to let anyone check an implementation against the contract, independently of Numinance.

Providers listed here exist in the public tree under numinance-spec/plugins. Numinance is pre-alpha: presence in the tree does not imply production support.