Developers

Autonomy policy is declared. Review it like code.

There is no public SDK yet. What exists is the integration surface design partners work with: connectors, an autonomy policy per loop, cited recommendations, versioned models and an audit record for every action. This page describes that surface honestly.

ConnectorsPolicy per loopAudit records

run_scn_01 · agent graph · scenario 10 nodes · 1 approval gate
01 · orchestrator order.receive ✓ SUCCEEDED 02 · orchestrator twin.simulate ✓ SUCCEEDED 03 · reform_synth loop.control ✓ SUCCEEDED 04 · react_evap evaporate.control ✓ SUCCEEDED 05 · granulate granulate.control ✓ SUCCEEDED 06 · coat_condition condition.cool ✓ SUCCEEDED 07 · defect_inspect inspect.granules ✓ SUCCEEDED 08 · orchestrator approve.human ◆ APPROVAL 09 · blend_bag blend.bag ✓ SUCCEEDED 10 · quality_conf release.genealogy ✓ SUCCEEDED

Illustrative scenario: Complex run · one urea granulation campaign from synthesis gas to bagged lot · ammonia loop, urea synthesis and evaporation, granulator, dryer and cooler, NPK bagging line. Not a measured run.

Developers

Every action is a record

There is no SDK to download yet. What design partners get is the integration surface: connectors, an autonomy policy declared per loop, and an audit record for every reading, recommendation, write and approval. This is the shape of one record, illustrative.

What the surface gives you

  • Connectors to DCS, APC, historian, granulation control, analyzers, emissions sensors, lab, MES, cameras and meters, with declared allow-lists and limits
  • An autonomy policy per loop: stage, tags, rate and magnitude limits, safety envelope, named approvers
  • Citations on every recommendation to the spec, procedure or permit it relied on
  • Model versions named in every record, with rollback by version
  • Export of the audit log and lot genealogy to your quality and HSE systems

What the docs cover Developer overview

audit record · illustrative
// one write, as the audit log would hold it
{
  "run": "run_scn_01",
  "step": "granulate.control",
  "agent": "agent.granulate",
  "stage": "bounded",
  "action": { "tool": "dcs.write_setpoint", "tag": "GRAN1.RECYCLE_RATIO" },
  "limits": { "max_step": "declared per tag", "per": "declared per tag" },
  "evidence": ["granvis.read_distribution", "twin.validate"],
  "citation": "spec:UREA-46 granule v3 §2",
  "safety": "SIS envelope read-only · inside",
  "policy": "permitted",
  "models": { "size_moisture": "versioned", "policy": "versioned" },
  "human": null,
  "outcome": "distribution inside band · recycle trimmed"
}
Capabilities

What the surface gives you

Connectors

Declared read and write scopes for DCS, APC, historian, granulation control, analyzers, emissions sensors, lab, MES, cameras, bagging lines and meters.

Autonomy policy

Stage, tag allow-list, rate and magnitude limits, safety envelope and named approvers per loop, versioned like any other change.

Cited recommendations

Every recommendation names the spec, procedure or permit it relied on; retrieval is tenant-isolated and permission-aware.

Model router

The best or cheapest model serves each step; high-volume granule vision moves to fine-tuned open models, reasoning steps use frontier models.

Evaluation gates

Golden datasets and model-as-judge evaluations gate model and prompt changes in CI.

Export

Audit log and lot genealogy export to the plant's quality and HSE systems.

Run timeline

What a run record contains

Every Nitreum run is an ordered, inspectable sequence. This is run_scn_01, an illustrative scenario: Complex run · one urea granulation campaign from synthesis gas to bagged lot · ammonia loop, urea synthesis and evaporation, granulator, dryer and cooler, NPK bagging line. Scenario complete · lot inside spec · one human approval on the ammonia loop.

run_scn_01 scenario · not measured SUCCEEDED
  1. 01 order.receive SUCCEEDED 0.8 s

    Complex Orchestrator · Pulled the grade spec, the nutrient target, the granule spec for size distribution, hardness and moisture, the emissions permit limits, the safety-instrumented envelope and the standing changeover window from the plant MES and the historian; locked the target envelope for the campaign.

  2. 02 twin.simulate SUCCEEDED 41 s

    Complex Orchestrator · Simulated 24 candidate loop, evaporation, granulation and sequencing plans on the Nitrotwin as-produced complex twin; ranked them on conversion, energy per tonne, predicted granule distribution, recycle ratio, emissions margin and takt, and discarded every candidate that thinned the safety or permit margin.

  3. 03 loop.control SUCCEEDED continuous

    Reform-and-Synthesize · Held ammonia-loop conversion and reformer temperature inside the approved envelope from live loop telemetry and the conversion model, trimming setpoints toward the lowest energy per tonne the plan allowed; purge and trip settings were read, never written.

  4. 04 evaporate.control SUCCEEDED continuous

    React-and-Evaporate · Held urea melt concentration at the granulation target from the online concentration analyzer and the evaporation model, moving evaporator setpoints inside the recipe window rather than waiting for the next lab assay.

  5. 05 granulate.control SUCCEEDED continuous

    Granulate-and-Prill · Tuned recycle ratio, spray and bed temperature from the live Granvis size distribution and moisture signal, each move validated on the twin first; the granule distribution stayed inside the spec band while recycle trended down.

  6. 06 condition.cool SUCCEEDED continuous

    Coat-and-Condition · Held dryer and cooler outlet temperature and moisture inside the storage window and set the anti-caking coating rate to the predicted caking risk for the product and the season; nothing moved outside the conditioning envelope.

  7. 07 inspect.granules SUCCEEDED continuous

    Defect-and-Inspect · 12 camera streams at the plant edge: granule size and shape, dust, caking precursors and broken prills on the granulator discharge, cooler and bagging belts; two dust spikes were attributed to one spray nozzle and Granulate-and-Prill corrected it inside its window.

  8. 08 approve.human APPROVAL 2 m 14 s

    Complex Orchestrator · The lowest-energy candidate wanted a purge-rate change on the ammonia loop beyond the bounded envelope. Held for the shift process engineer and the process-safety approver, who approved a smaller step with the safety-instrumented envelope untouched and a tighter review interval.

  9. 09 blend.bag SUCCEEDED continuous

    Blend-and-Bag · Held the NPK blend ratio to the nutrient spec from Granvis nutrient sensing, checked segregation on the belt and held bag weight to target; three overweight bags were attributed to one dosing gate and the gate was trimmed inside the approved window.

  10. 10 release.genealogy SUCCEEDED 1 m 10 s

    Quality-and-Conformance · Lot released: conversion and energy per tonne, melt concentration, granule distribution, hardness and moisture, nutrient assay, emissions readings, inspection events, bag weights and every human decision written to the lot genealogy and checked against spec and permit.

Tool calls

Streaming a run

Every tool invocation, argument and result is written to an immutable, human-readable log, and every reasoning step is expandable. Nothing about a run is hidden from the plant. The log below is the scenario run, not a measured one.

tool-call stream · run_scn_01
  1. 05:10:02mes.read_order({ campaign: "U-4471", grade: "UREA-46", pack: "BAG-50" })
  2. 05:10:02ok grade spec locked · permit limits v4 · SIS envelope read-only
  3. 05:10:03historian.read_baseline({ unit: "AMM-1", window: "30d" })
  4. 05:10:03ok energy per tonne baseline loaded · catalyst age noted
  5. 05:10:04twin.simulate({ candidates: 24, horizon: "campaign" })
  6. 05:10:45ok best plan #9 · permit margin held · lowest energy per tonne
  7. 05:10:46policy.evaluate({ plan: 9, stage: "bounded" })
  8. 05:10:46ok 7 writes permitted · 1 write requires human approval
  9. 05:10:47dcs.write_setpoint({ tag: "AMM1.LOOP_T", basis: "conversion+energy" })
  10. 05:14:30ok conversion on target · energy per tonne trending down
  11. 05:20:00analyzer.read_concentration({ unit: "EVAP-2" })
  12. 05:20:00ok melt concentration inside window · evaporator setpoint held
  13. 05:31:12granvis.read_distribution({ unit: "GRAN-1", metric: "size_moisture" })
  14. 05:31:12ok distribution inside spec band · recycle ratio trimmed after twin check
  15. 05:31:13vision.stream({ cameras: 12, models: ["size_shape", "dust", "caking", "bag_defect"] })
  16. 06:02:48dust spike · cooler belt · attributed to spray nozzle 3
  17. 06:02:49defect.attribute({ event: "dust_spike", cause: "granulator.nozzle_3" })
  18. 06:02:49ok granulate notified · spray trimmed inside window · second spike, then clean
  19. 06:02:50dcs.write_setpoint({ tag: "COAT1.RATE", basis: "moisture+caking_risk" })
  20. 06:02:50ok coating rate set · moisture inside storage window
  21. 06:02:52approval.request({ action: "loop.purge", reason: "beyond bounded envelope" })
  22. 06:05:06ok approved by the shift process engineer and the process-safety approver · smaller step · SIS untouched
  23. 07:40:10plc.write_setpoint({ tag: "BLEND1.RATIO", basis: "nutrient+segregation" })
  24. 07:40:10ok nutrient ratio on spec · bag weight on target · gate 2 trimmed
  25. 09:18:30mes.release_lot({ campaign: "U-4471", genealogy: "full" })
  26. 09:19:40ok lot released · scenario complete

Reasoning trace

Goal, plan, thought, action, observation, exactly as the orchestrator would record it.

GoalRun campaign U-4471 from synthesis gas to bagged lot: ammonia …

Run campaign U-4471 from synthesis gas to bagged lot: ammonia loop at target conversion per unit of energy, melt at exact concentration, granules on spec with minimum dust and recycle, conditioned for storage, bagged to weight and released with full genealogy and emissions readings.

PlanSimulate the whole campaign on the twin first. Lead with conve…

Simulate the whole campaign on the twin first. Lead with conversion so evaporation gets the right melt and the granulator gets the right concentration. Verify emissions and the safety envelope continuously. Let the granulator chase the size band only inside the approved window; hold any ammonia-loop move beyond the envelope for a human.

ThoughtThe standing practice runs the loop and the granulator on fixe…

The standing practice runs the loop and the granulator on fixed setpoints and corrects after the assay. With live conversion, concentration and granule distribution the loop and the granulator can sit at target. The saving is energy, recycle and dust, not safety margin: the safety-instrumented envelope and the permit limits are never candidates for optimization.

Actiontwin.simulate(candidates=24) → plan #9: conversion on target, …

twin.simulate(candidates=24) → plan #9: conversion on target, melt concentration on spec, granule distribution inside the band, permit margin unchanged, lowest predicted energy per tonne.

ObservationPlan #9 wants a purge-rate change on the ammonia loop beyond t…

Plan #9 wants a purge-rate change on the ammonia loop beyond the bounded envelope. The policy engine routes that single move to the shift process engineer and the process-safety approver and permits the other seven writes.

ActionExecute plan #9 at the bounded stage: loop temperature, evapor…

Execute plan #9 at the bounded stage: loop temperature, evaporator, granulator, coating and blend writes proceed; emissions are verified continuously; the purge move waits.

ObservationApproval granted at 06:05:06 with a smaller step and the safet…

Approval granted at 06:05:06 with a smaller step and the safety-instrumented envelope untouched. Two dust spikes were attributed to spray nozzle 3 and corrected by Granulate-and-Prill inside the approved window.

OutcomeScenario complete. The lot is released with conversion and ene…

Scenario complete. The lot is released with conversion and energy per tonne, melt concentration, granule distribution, nutrient assay, emissions readings and the human decision in the genealogy. No measured plant result is claimed; this is the run the platform is designed to execute.

Workflow

From idea to a unit, safely

  1. Declare. Tools, tags, limits and the safety envelope for the agent, and the autonomy stage for the loop.
  2. Shadow. Run against live plant data; compare predictions to assay, historian and engineer outcomes; nothing is written.
  3. Evaluate. Golden datasets and model-as-judge checks in CI before a model or prompt version is promoted.
  4. Rehearse. High-impact moves are simulated on Nitrotwin where a surrogate exists.
  5. Assist, then bounded. Writes only after the accuracy and safety gates, inside declared limits, through your management of change.
  6. Record and retrain. Every action and correction is logged; corrections become training events.
Autonomy

Four stages, set per loop

A plant does not go from manual to bounded control in one step. Nitreum makes the stage explicit per loop, auditable and reversible at any time, and some decisions never leave the person. On the ammonia side every stage is safety-gated.

Autonomy stages and the human role at each
StageWhat the agent doesWhat the person doesWhen
ShadowPredicts conversion, concentration, granule quality, nutrient content, energy, emissions and off-spec risk; writes nothingRuns the plant as today; compares predictions to assay, historian and engineer outcomesFirst phase with every design partner
AssistRecommends bounded loop, evaporation, granulation, coating and blend moves with the evidenceA process engineer approves or rejects each oneAfter accuracy is proven against the baseline
BoundedWrites low-risk granulation, conditioning and blending setpoints inside documented recipe, quality, safety, emissions, equipment and rollback limitsApproves anything above the limits and every ammonia-loop move beyond the envelope; reviews the shift recordAfter the safety and ROI gates agreed up front
ExceptionsEscalates anything outside its envelope, safety-adjacent moves and release decisionsAlways decides these; the agent never doesPermanent
Multi-agent handoff

Agents negotiate, they do not collide

Two agents will want the same actuator. The orchestrator arbitrates on the run goal, with process safety above everything, and the handoff is logged like any other step.

Contested move: ammonia-loop purge rate

  1. 01yield_takt.request(purge −8%) SUCCEEDED0.2 s

    Yield-and-Takt wants a lower purge rate on the ammonia loop so less hydrogen is lost and energy per tonne falls for the campaign.

  2. 02reform_synth.request(purge hold) SUCCEEDED0.2 s

    Reform-and-Synthesize requires the purge rate that keeps inerts inside the loop envelope the process-safety review approved. That envelope is not an optimization variable.

  3. 03orchestrator.arbitrate SUCCEEDED0.4 s

    Process safety outranks energy under every run goal. The envelope wins the actuator; the request for a lower purge is logged with its score and the reason it lost, and a smaller step is routed to a named approver.

  4. 04yield_takt.handoff(resequenced) SUCCEEDED95 s

    Yield-and-Takt recovers the energy target by shifting the dryer duty and the changeover window instead. Takt is met without touching the loop envelope.

Arbitration rules

  • Run goal first. Every request is scored against the declared goal, not against the requesting agent's local objective.
  • Process safety outranks everything. A safety-instrumented envelope or a permit limit is never an optimization variable. An ammonia-loop upset is a safety event; a takt miss is a schedule.
  • Time-boxed ownership. An agent holds a contested actuator for a bounded window, then must re-justify.
  • Everything is logged. The losing request, the score and the reason all appear in the run record.
  • Deadlocks escalate to a human rather than resolving by timeout.

See the agent roster

Accelerated computing

Physical AI, at the plant edge

A fertilizer complex is remote, continuous and often restricted from cloud links, so perception has to be local and fast. Nitreum runs GPU inference at the plant edge and keeps training, simulation and optimization in the cloud, in a private cloud or on-prem. Items marked planned are on the roadmap, not running.

Jetson Orin / Thor · DeepStream · Metropolis · TensorRT · Holoscan

Edge perception

8 to 40 camera feeds per unit through DeepStream pipelines and TensorRT detectors and segmenters for granule size and shape, dust, caking, broken prills and bag defects; Holoscan fuses vision with analyzer, historian, emissions, acoustic and thermal streams at 1 to 10 Hz. Design target: 50 to 120 ms p95 inference.

Triton · NIM · NVIDIA AI Enterprise

Model serving

Vision, time-series, RAG and process-reasoning models behind one orchestrator, with canary deployment and per-site routing. NVIDIA AI Enterprise is the planned runtime for regulated deployments.

DGX / HGX · NeMo · Retriever · Guardrails

Training and reasoning (planned)

Granule vision, time-series prognostics and NeMo process-reasoning models fine-tuned from labeled images, process histories, engineer corrections and event logs. Design target: 2 to 5 model families and 500 to 2,000 GPU-hours per cohort.

Omniverse · Modulus · OVX

Digital twin (planned)

The Nitrotwin complex twin: physics-informed surrogates for the ammonia loop, evaporation, granulation, blending and emissions, with GPU-accelerated process and CFD sweeps run before a plant change.

Cosmos · Omniverse Replicator

Synthetic data (planned)

Rare dust, caking, wet-granule, broken-prill, lighting, belt-contamination, emissions-spike and upset scenarios generated and labeled as synthetic, validated against real plant events before a model learns from them.

cuOpt

Optimization

Throughput, recycle balancing, energy and emissions allocation and grade-changeover sequencing under constraints, recomputed on the GPU when the complex is disrupted.

RAPIDS

Data engineering

ETL over historian, quality, emissions and vision data for feature generation, quality correlation and cross-site benchmarks on the GPU.

Isaac · Jetson

Robotic handling

Bag palletizing, bulk loading, materials handling and inspection rovers, with perception and motion policies built and validated in simulation before they move a pallet.

Integrations

It speaks plant, not cloud

Nitreum reads and writes through the systems already in the control room. No parallel historian, no new HMI, no rip-and-replace. Connectors are built against each design partner's stack first; long-tail integrations are out of scope for the first release.

DCS, APC and historian

Reformer, ammonia loop, reactor and evaporator control and the plant historian

Setpoint reads, guarded writes, safety systems untouched

Granulation and prilling control

Granulator, prill tower, dryer, cooler and coating drum controls

Recycle, spray, temperature and coating setpoints inside windows

Online analyzers

Nutrient, moisture and concentration analyzers, NIR and granule analyzers

Continuous quality state, fused at the edge

Emissions sensing

CO2, NOx and ammonia-slip sensors and permit records

Read and verified; excursions predicted, limits never optimized against

Blending and bagging

NPK blender, dosing gates, bagging and loading lines

Ratio and weight setpoints inside approved windows

Cameras and robots

Fixed cameras on granule, belt and bagging stations; Isaac-driven palletizing and loading cells

Frames, defect events, bounded handling

Plant MES, LIMS and quality

Orders, grade specs, lab assays, lot genealogy

Targets in, release records out

Identity (planned)

SSO and role-based access; SOC 2 on the roadmap

Named approvers, scoped roles

See all integrations

Guardrails

An agent that can move a setpoint needs a leash

Nitreum writes to production equipment in a plant that handles ammonia. Every capability is scoped, every write is policy-checked, every output is cited, and every action is written to an append-only audit log the plant owns.

  • Bounded action space. Each agent can only write to an explicit tag allow-list, through approved DCS or APC interfaces, inside per-tag rate and magnitude limits, at the autonomy stage the plant has set.
  • Safety systems are read, never written. Safety-instrumented systems, interlocks, trip settings and emissions permit limits stay with the plant's process-safety program and the people who own it.
  • Policy engine before every write. Autonomy stage, safety envelope, interlock state, grade, shift and operator presence are evaluated before a setpoint moves. Any ammonia-loop move beyond the envelope waits for a named approver.
  • Grounded and cited. Every recommendation carries a citation to the spec, procedure or permit it relied on. Retrieval is tenant-isolated and permission-aware.
  • Immutable audit log. Append-only, exportable and retained on the plant's own storage, aligned to the plant's quality, emissions and process-safety record-keeping.
  • Hard fallback. If the edge node, the network or a model stops, the plant keeps running on its existing DCS, APC and safety systems.
  • Tenant and IP isolation. Recipes, process settings and plant IP never cross a customer boundary. On-prem and plant-edge deployment available.

Assurance posture

Assurance and certification status
ItemScopeStatus
SOC 2 Type I readinessCloud control plane QUEUED Roadmap, first 6 months
SOC 2 Type IICloud control plane QUEUED Roadmap, 6 to 12 months
Process-safety and emissions proceduresGrounding and record-keeping RUNNING Design basis for retrieval and the audit log
Per-tenant isolationData, memory, models RUNNING Design rule
On-prem and plant-edge deploymentIP- and safety-sensitive sites RUNNING Design option

Nitreum supports your process-safety, quality and emissions records. It is not a certification and it does not replace your safety program or management of change.

Read the security overview

FAQ

Straight answers

The questions complex operations managers, process engineers and HSE leads ask in the first meeting.

Only at the autonomy stage your plant has set, and only to an explicit allow-list of low-risk loops inside documented limits, through the approved DCS or APC interfaces. Every design partner starts in shadow mode, where Nitreum predicts and writes nothing. Assist mode follows, where a process engineer approves each recommendation. Bounded autonomy on granulation, conditioning and blending loops comes after the safety and ROI gates agreed up front.

Get started

Build on the run engine

Design partners get the integration surface and the people who built it. Tell us what you want to connect.