NPMIntegrator.AI / Platform / Router

The Router decides what is allowed to run.

NPM Integrator is being developed as a provider-neutral control plane for governed life-sciences workflows. CIW is the first workbench designed to run on it.

The product is not the model. It is the governed operating system surrounding the model — classification, capability selection, mandatory safety and evidence co-routing, minimum-authorized context, deterministic calculation, verification, human review and release control.

Explore NPM Integrator Technology Connect Your Workbench

Route Decision

Every run
selected primary capability
mandatory co-routes
denied capabilities
exact package versions and digests
required source classes
required human reviewers
risk classification and confidence
budgets and stop conditions
A model may recommend route candidates. Deterministic policy decides the permitted route.

Control and context separation

One decides what may run. The other decides what it may see.

The Router owns execution authority. The Interpretable Context Methodology owns context.

Separating the two is what makes a run reconstructable — the decision to execute and the information that execution received are recorded independently.

The Router

Owns execution authority.

Who may initiate a workflow, which capabilities are permitted, which exact versions may run, which gates must pass, and whether an artifact may be released.

ICM Context Plane

Owns context construction and semantic handoffs. Each worker receives only the identity, policies, capability contract, evidence, tools, schemas and run artifacts its task requires.

Models do not determine their own permissions, data access, tools, safety requirements, or release authority.

The control plane

Ten decisions taken before anything runs

The Router is designed as an executable control plane rather than a conversational layer.

Each request is classified, routed and bounded before any model or tool is permitted to act.

who may initiate a workflow what the user is actually asking which scientific capabilities are required which safety, evidence, privacy and review capabilities must be added which exact capability, policy, model, prompt, tool, source and workflow versions may execute what information each execution step may receive which actions a model or tool may propose which deterministic calculations and gates must run when human review is required whether the resulting artifact may be released

The Router does not ask

“Which model should answer this?”

It asks

“Which capability is required, which policy applies, which evidence must be produced, and who must review it before anything is released?”

The result is designed to be a governed routing decision that can be recorded, inspected, reproduced, and audited.

Architectural principles

How the platform is designed to behave

Eight principles govern the platform. Each one constrains what the software may decide on its own.

They are specification commitments, not marketing claims — each one is written into the requirements document.

NPM Integrator

Specification commitments

Deterministic authority

Authorization, co-routing, calculations, gates and release decisions are policy-controlled, not model-decided.

Provider neutrality

Every model call passes through an internal Model Gateway. No domain service calls a provider directly.

Signed, immutable capabilities

Every mode, agent, step and verifier is a signed, versioned package, mounted read-only.

Minimum-authorized context

Each worker receives only what its task requires. Nothing further is in scope.

Graph-based execution

Workflows are directed dependency graphs rather than forced linear prompt chains.

Human review as a product function

Review is a first-class state transition, not a disclaimer appended to model output.

Fail closed

Missing authority, invalid packages or unresolved P0 risks result in explicit denial or hold.

Reproducibility

Deterministic results are intended to reproduce exactly from the same retained inputs and versions.

First application on the Router

CIW is the first workbench designed to run on the Router

The Combination Intelligence Workbench is positioned as a governed workflow for evidence-bounded combination research, experiment planning and scientific dossier production.

Its defensible value does not sit in access to any one model. It sits in the controlled chain below.

Controlled chain

Research question → Evidence → Claims → Candidate combinations → Mechanism and safety analysis
Deterministic scoring → Human review → Experiment plan → Reviewed dossier

Evidence to claims, claims to candidates, candidates to scored and screened options, and options to a reviewed, reproducible dossier.

See the Combination Intelligence Workbench

Open by design

CIW is the first workbench on the Router. Not the only one.

The Router is being built as an independent orchestration, policy, context, execution, verification and provenance service.

That separation is what lets it support more than one application — including a workbench or development platform a customer brings with them.

Other NPM applications

Additional Cadenome workflows routed through the same control plane.

External life-sciences platforms

Third-party research systems connecting through the Router rather than replacing it.

Private research environments

Customer-operated workbenches and development platforms.

Sovereign deployments

Jurisdiction-bound installations where data and execution stay in place.

Integration boundary

Authenticated, versioned APIs and webhooks. Direct cross-platform database access is not permitted.

Discuss an Integration

Development status

This page describes a platform specification under development. The Router and CIW services are documented as an implementation candidate. Capabilities described here are designed and specified — they should not be read as validated, accredited, compliant or production-proven.