Changelog

Every release that can touch a circuit, written down.

Orebex has not shipped a release yet, so this page is the build log: what is planned by phase, how a release will reach a circuit, and the policy for promoting models and autonomy. When the first release ships, its notes replace the top of this page.

0 releases shipped3 planned phasesRelease policy published

Status

Pre-release

QUEUEDMVP · 0 to 6 months

The first release is connectors, the agent loop, the review console and the assurance-grade recovery and environmental audit log, for one wedge workflow on one grinding or flotation circuit.

Planned

The build log by phase

Everything here is planned. Nothing here has shipped.

0 to 6 months · planned

Phase 1

  • Onboard 2 to 4 design partners on the wedge workflow
  • Ship the MVP: connectors, agent loop, review console, assurance-grade recovery and environmental audit log
  • Prove accuracy and recovery, energy and water ROI in shadow then assist mode
  • Security and environmental baseline: SOC 2 Type I in progress, IP-safe and edge deployment

6 to 12 months · planned

Phase 2

  • Convert design partners to paid; first revenue
  • Graduated autonomy for low-risk grinding and flotation loops; twin hit-recovery-before-shift
  • Second circuit within the concentrator; deeper integrations
  • SOC 2 Type II; SSO and RBAC; first miner plants; environmental and water assurance packages

1 to 3 years · planned

Phase 3

  • Own the full crush, grind, float, separate and dewater circuit end to end
  • Single concentrator to multi-site miner to global mining group
  • Mining-equipment and process-control vendor channel; international expansion
  • Data-network products: recovery, grade, energy, water and reagent benchmarks as premium tiers
Policy

How a release reaches a circuit

The promotion and rollback rules.

  • Model versions are promoted by circuit. A new model version reaches one bank or mill as a canary before it reaches the plant, and falls back to the previous validated version automatically.
  • Autonomy policy is versioned like code. Tag allow-lists, limits, operating envelopes and approval chains are reviewed and recorded before a release can write to a circuit.
  • Every release carries its evaluation record. Golden datasets and judged evaluations gate model and prompt changes in CI before promotion.
  • Rollback conditions are declared up front. Each release names the signals that trigger a return to the previous version.
Support

Version support, when versions exist

The support policy the first releases will follow.

Version support
ComponentVersioningSupport window
Plant-edge runtimeSemantic, per nodeCurrent and previous minor
ModelsPer circuit, per ore typePrevious validated version kept for fallback
Autonomy policyReviewed and versioned like codeHistory retained in the audit log
SDK and CLIDesign previewBreaking changes expected before release
Run timeline · scenario

The reference scenario, per release

Each release will be checked against this scenario before it reaches a circuit.

run_4b9e27 Line 1 · SAG and ball circuit, rougher bank 2 · copper porphyry blend illustrative scenario SUCCEEDED
  1. 01 ingest.shift SUCCEEDED 0.7 s

    Concentrator Orchestrator · Pulled the shift plan from the concentrator MES: copper porphyry blend B-14, P80 target 150 µm, concentrate grade at or above 25% Cu, recovery target per the geometallurgy model, energy and water budgets. Locked the operating envelope for the blend.

  2. 02 twin.simulate SUCCEEDED 58 s

    Concentrator Twin · Simulated 32 candidate grind, air and reagent schemes on the as-run twin for the hardening blend, ranked on predicted recovery, concentrate grade, kWh per tonne and water per tonne. Two candidates breached the thickener bed limit and were discarded.

  3. 03 grind.setpoint SUCCEEDED 3 m 40 s

    Crush-and-Grind · SAG-1 feed trimmed 3% and cyclone water raised as load and power signatures read a harder feed. P80 from the particle-size analyzer held at 148 µm against the 150 µm target; mill power stayed inside the energy budget.

  4. 04 froth.read SUCCEEDED continuous

    Grade-and-Froth · Twelve froth cameras and the online XRF on rougher bank 2 fused at the edge. Froth stability on cells 3 and 4 fell as the blend hardened; predicted recovery drifted 0.4 points below plan. Early warning published to the control agents.

  5. 05 approve.human APPROVAL 1 m 12 s

    Concentrator Orchestrator · Scheme #7 raises collector dose 6% on rougher bank 2, above the standing reagent scheme. Reagent-scheme changes stay supervised on this blend, so the step was held for the shift metallurgist and approved at 07:19:44.

  6. 06 float.dose SUCCEEDED 2 m 05 s

    Float-and-Reagent · Approved collector dose applied with an air trim of 4% down on cells 3 and 4 inside the envelope. Froth stability recovered within eight minutes; predicted recovery returned to plan with concentrate grade read at 25.6% Cu.

  7. 07 classify.cyclone SUCCEEDED 42 s

    Separate-and-Classify · One cyclone brought online in cluster 1 as feed density rose with the hardness change, holding overflow size and circulating load inside the plan.

  8. 08 dewater.thickener SUCCEEDED continuous

    Thicken-and-Dewater · Tailings thickener TH-2 flocculant dose trimmed as bed pressure rose; underflow density held and overflow clarity stayed inside the water-recovery target.

  9. 09 optimise.targets SUCCEEDED 18 s

    Throughput-and-Recovery · Whole-plant targets recomputed for the hardened blend: feed rate, P80, air and reagent targets handed to the control agents with recovery, grade, energy and water inside the budget. The losing candidates and their scores are in the run record.

  10. 10 lot.release SUCCEEDED 1 m 30 s

    Quality-and-Conformance · Concentrate lot C-20931 released: genealogy written (blend, grind record, reagent and air moves, froth and grade reads, approvals, dewatering record, assays as they land) and dispositioned against the concentrate spec with cited evidence for the metallurgist's sign-off.

Tool calls · scenario

What the tool log will show per release

Every tool invocation, argument and result is written to an append-only, human-readable log, and every reasoning step is expandable. Nothing about a run is hidden from the plant.

tool-call stream · run_4b9e27
  1. 07:00:02mes.read_plan({ line: "L1", blend: "B-14", shift: "day" })
  2. 07:00:02ok envelope locked · P80 150 µm · grade ≥ 25% Cu · energy and water budgets
  3. 07:00:03twin.simulate({ candidates: 32, horizon: "1 shift" })
  4. 07:01:01ok best scheme #7 · recovery on plan · 2 candidates discarded (thickener bed)
  5. 07:01:02policy.evaluate({ scheme: 7, autonomy: "L2+" })
  6. 07:01:02ok 8 writes permitted · collector_dose requires human approval
  7. 07:01:03mill.set_feed({ tag: "SAG1.FEED_TPH", delta: "-3%" })
  8. 07:04:43ok P80 148 µm · power inside budget · hardness index up
  9. 07:04:44froth.read_bank({ bank: "R2", cams: 12, xrf: true })
  10. 07:18:30froth stability falling · R2 cells 3, 4 · predicted recovery −0.4 pt
  11. 07:18:31approval.request({ action: "collector_dose", bank: "R2", delta: "+6%" })
  12. 07:19:44ok approved by shift metallurgist · logged
  13. 07:19:45reagent.set_dose({ bank: "R2", scheme: 7 })
  14. 07:19:46air.set_rate({ cells: [3, 4], delta: "-4%", within: "envelope" })
  15. 07:27:50ok froth stability recovered · grade 25.6% Cu · recovery back on plan
  16. 07:27:51cyclone.set_count({ cluster: "CL-1", online: "+1" })
  17. 07:28:33ok overflow size held · circulating load inside plan
  18. 07:28:34flocculant.set_dose({ thickener: "TH-2", delta: "-2%" })
  19. 07:40:10ok bed pressure steady · overflow clear · water recovery on target
  20. 07:40:11cuopt.solve_targets({ line: "L1", objective: "recovery, grade, energy, water" })
  21. 07:40:29ok targets handed to 4 agents · all inside budget
  22. 07:40:30mes.log_lot({ lot: "C-20931", genealogy: "full" })
  23. 07:42:00ok scenario complete · 10 steps · lot released

Reasoning trace

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

GoalRun the day shift on line 1 inside the plan for blend B-14: P8…

Run the day shift on line 1 inside the plan for blend B-14: P80 at 150 µm, concentrate grade at or above 25% Cu, recovery maximised, energy and water inside budget.

PlanSimulate grind, air and reagent schemes on the twin first. Lea…

Simulate grind, air and reagent schemes on the twin first. Lead with the grind so the liberation size is right before flotation sees it, then read the froth, then dose. Hold any reagent-scheme change for a human.

ThoughtThe blend is hardening. Holding feed rate would coarsen P80 an…

The blend is hardening. Holding feed rate would coarsen P80 and under-liberate; the twin predicts a 3% feed trim with more cyclone water holds P80 at the cost of a little throughput, and that protecting liberation is worth more than the tonnes.

Actiontwin.simulate(candidates=32) returns scheme #7: SAG-1 feed dow…

twin.simulate(candidates=32) returns scheme #7: SAG-1 feed down 3%, cyclone water up, collector dose up 6% on rougher bank 2, air down 4% on cells 3 and 4.

ObservationScheme #7 predicts recovery on plan, grade 25.5% Cu and energy…

Scheme #7 predicts recovery on plan, grade 25.5% Cu and energy inside budget. Two candidates with higher predicted recovery pushed the tailings thickener past its bed limit and were discarded.

ActionExecute scheme #7: eight bounded writes permitted on grind, ai…

Execute scheme #7: eight bounded writes permitted on grind, air, cyclones and dewatering; the collector-dose write routed to the shift metallurgist.

ObservationFroth stability fell on cells 3 and 4 at 07:18:30 with predict…

Froth stability fell on cells 3 and 4 at 07:18:30 with predicted recovery 0.4 points under plan. The approved dose and the air trim recovered it within eight minutes; grade read 25.6% Cu.

OutcomeScenario complete. P80 held, grade on spec, recovery on plan, …

Scenario complete. P80 held, grade on spec, recovery on plan, lot C-20931 released with full genealogy.

Autonomy

Four levels, set per agent and per tag

A concentrator does not go from manual to unattended in one step. Orebex makes the level explicit, auditable and reversible at any time. The first release runs shadow mode, then assist mode, then bounded autonomy on low-risk grinding and flotation loops. Reagent-scheme changes stay supervised until the ore type is characterised.

Autonomy levels and the human role at each
LevelWhat the agent doesWhat the human doesWhere it sits in a pilot
L1 · ShadowReads froth, analyzer, particle, mill, flotation, dewatering, robot and MES signals; predicts and recommends; writes nothingRuns the circuit as today; compares predictions to assays and metallurgist outcomesShadow mode, baseline measured first
L2 · AssistProposes grind, reagent, air, froth and dewatering moves with evidence, confidence, envelope and rollback pathApproves each action in the review consoleAssist mode, the remainder of a 90 to 120 day pilot
L3 · BoundedExecutes pre-approved low-risk grinding and flotation loop moves: feed, water, air, level, flocculant, cyclones online, inside APC, DCS and envelope limitsApproves reagent-scheme changes and lot releaseGraduated autonomy, after audited accuracy and ROI
L4 · Constrained auto-controlSupervised reagent-scheme adaptation for characterised ore types, across circuits and sitesSets the envelope; reviews the shift record and the evaluation resultsPlanned; after golden-dataset evaluation, twin validation and metallurgist sign-off
Accelerated computing

Physical AI, at the bank and the mill

Froth changes in seconds and a shift of feed is gone before the assay lands. Perception has to be local, deterministic and fast, so Orebex runs GPU inference at the plant edge and keeps training, simulation and optimisation in the cloud or on-prem.

Jetson Orin · DeepStream · Holoscan · TensorRT

Edge perception

8 to 24 froth cameras per bank at 15 to 30 FPS plus online XRF, particle-size, pump, level, air, reagent, density and energy streams fused at the plant edge. Sub-250 ms froth inference and local fail-safe through a network outage are the design targets. Jetson Thor is planned.

Triton · NIM

Model serving

Froth, particle and mineralogy, recovery prediction, time-series anomaly and metallurgy retrieval models behind one orchestrator at the plant edge, 20 to 60 per site as a design target, with versioned canaries and rollback.

DGX or HGX · NeMo

Training

Froth segmentation, bubble velocity and stability, grade and recovery prediction, ore hardness, grind-size response, reagent response and metallurgy assistants trained on froth video, analyzer readings, telemetry and metallurgist corrections. 2,000 to 8,000 GPU-hours per commodity model family is the design target once partner data exists.

Omniverse · OVX

Concentrator twin

Grinding, flotation, classification and dewatering simulated as-run against as-designed before the shift. GPU comminution and DEM, flotation and geometallurgy simulation is the workload; physics-informed surrogates with Modulus are planned so schemes rank at production cadence.

Cosmos · Omniverse Replicator

Synthetic data

Rare froth-collapse, feed-upset, mineralogy-shift, equipment-drift and camera-fouling cases generated and validated against real assay distributions before promotion. 50k to 250k scenarios per commodity and circuit class is the design target.

cuOpt

Optimisation

Throughput, energy, water and reagent allocation and the grade and recovery trade-off solved before the shift and during upset recovery, and handed to the control agents as targets.

Isaac Sim · Isaac ROS

Robot sampling and handling

Sampling routes, reagent tote inspection and inspection rovers trained and validated in simulation before they run on site. Assistive until the safety case is proven.

RAPIDS

GPU ETL

Daily features from froth, analyzer, mill, flotation, dewatering and genealogy telemetry for retraining, drift detection and recovery, energy, water and reagent benchmarks.

FAQ

Straight answers

The questions processing managers, metallurgists and sustainability leads ask in the first meeting.

Yes, but only within an explicit tag allow-list with per-tag rate and magnitude limits, inside the operating envelope for the blend, and only at the autonomy level your plant has set. Design partners start in shadow mode, where Orebex writes nothing. Reagent-scheme changes stay supervised by a named metallurgist until the ore type is characterised.

Get started

Follow the release line

Ask to be told when the first release ships.