Changelog

Every release that can touch a press, written down.

Forgiron has not shipped a release yet, so this page is the build log: what is planned by phase, how a release will reach a cell, 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 quality and safety audit log, for one wedge workflow on one cell.

Planned

The build log by phase

Everything here is planned. Nothing here has shipped.

0 to 6 months · planned

Phase 1

  • Onboard 3 to 5 design partners on the wedge workflow
  • Ship the MVP: connectors, agent loop, review console, assurance-grade quality and safety audit log
  • Prove accuracy and scrap, die-life and energy ROI in shadow then assist mode
  • Security and quality baseline: SOC 2 Type I in progress, IP-safe deployment

6 to 12 months · planned

Phase 2

  • Convert design partners to paid; first revenue
  • Graduated autonomy for low-risk heating, forging and inspection cells; twin hit-soundness-before-stroke
  • Second module within the forge; deeper integrations
  • SOC 2 Type II; SSO and RBAC; first enterprise plants; AS9100 and NADCAP assurance packages

1 to 3 years · planned

Phase 3

  • Own the full heat, forge, die, trim and heat-treat, inspect loop end to end
  • Single forge to multi-site forging maker to global forging group
  • Forging-machinery and heating and inspection vendor channel; international expansion
  • Data-network products: yield, scrap, die-life, energy and defect benchmarks as premium tiers
Policy

How a release reaches a cell

The promotion and rollback rules.

  • Model versions are promoted by cell. A new model version reaches one cell 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, process envelopes and approval chains are reviewed and recorded before a release can write to a cell.
  • 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 cell, per part familyPrevious 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 cell.

run_7c2e41 Cell F-2 · 2,500 t closed-die press · 42CrMo4 connecting rod illustrative scenario SUCCEEDED
  1. 01 ingest.order SUCCEEDED 0.6 s

    Plant Orchestrator · Pulled the part spec for the 42CrMo4 connecting rod from MES: forging window 1,180 to 1,230 °C, two-blow closed-die schedule, flash land 2.4 mm, temper to 28 to 32 HRC, 1,200 pieces. Locked the qualified process envelope.

  2. 02 twin.simulate SUCCEEDED 52 s

    Forge Twin · Simulated 24 candidate heat-and-stroke recipes on the as-forged twin for soak time, blow energy and spray timing, ranked on predicted fill, lap risk at the flash land, die load and kWh per piece.

  3. 03 heat.soak SUCCEEDED 2 m 10 s

    Heat-and-Billet · Induction power on IH-2 stepped down 4% in the final soak stage as the pyrometer read 1,205 °C at the surface. Core-to-surface spread estimated at 14 °C against a 20 °C limit, no overheat, scale growth inside the window.

  4. 04 die.spray SUCCEEDED 48 s

    Die-and-Lube · Lower-die spray dose raised 6% and cooling extended 0.3 s as die surface temperature climbed through 240 °C. Heat-check growth on cavity 2 flagged at 0.31 of the die-change threshold.

  5. 05 approve.human APPROVAL 46 s

    Plant Orchestrator · Recipe #9 moves second-blow energy 3% below the standing schedule. Press-schedule changes stay supervised on this part family, so the step was held for the shift forging engineer and approved at 05:47:31.

  6. 06 forge.stroke SUCCEEDED 1 m 36 s

    Forge-and-Press · Two-blow schedule executed with the approved energy. High-speed vision and force curves confirmed complete fill on the first ten pieces; predicted lap risk at the flash land fell from 0.27 to 0.08.

  7. 07 inspect.fuse SUCCEEDED continuous

    Defect-and-Inspect · Eight cameras, two thermal cameras and the ultrasonic station fused at the edge. One lap precursor at the flash land on piece 212 flagged and cleared by a 1.5% blow-energy trim inside the approved envelope; the piece was routed to MPI and passed.

  8. 08 handle.transfer SUCCEEDED continuous

    Robot-and-Handling · Press-to-trim transfer planned and executed by the handling robot at 11 s per piece, temperature loss in transfer 38 °C against a 60 °C limit, interlock zones clear throughout.

  9. 09 heat.treat SUCCEEDED continuous

    Trim-and-Heat · Temper furnace HT-1 zone 2 trimmed 5 °C against the predicted hardness from the recorded heat and stroke history. First hardness checks read 30 HRC, inside 28 to 32.

  10. 10 lot.release SUCCEEDED 1 m 20 s

    Quality-and-Conformance · Lot L-80412 released: genealogy written (billet lot, heat curve, stroke record, die cycles, inspection map, approvals, temper record) and dispositioned against IATF 16949 criteria with cited evidence for the quality engineer'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 forge.

tool-call stream · run_7c2e41
  1. 05:40:02mes.read_order({ cell: "F-2", part: "CR-42CrMo4-118", qty: 1200 })
  2. 05:40:02ok envelope locked · 1,180 to 1,230 °C · 2 blows · 28 to 32 HRC
  3. 05:40:03twin.simulate({ candidates: 24, horizon: "1 lot" })
  4. 05:40:55ok best recipe #9 · fill 1.00 · lap risk 0.08 · 1.9 kWh/pc
  5. 05:40:56policy.evaluate({ recipe: 9, autonomy: "L2+" })
  6. 05:40:56ok 7 writes permitted · press_schedule requires human approval
  7. 05:40:57induction.set_power({ tag: "IH2.STAGE3_KW", delta: "-4%" })
  8. 05:43:07ok surface 1,205 °C · core-to-surface spread 14 °C · no overheat
  9. 05:43:08spray.set_dose({ die: "F2.LOWER", dose: "+6%", cool: "+0.3 s" })
  10. 05:43:56ok die surface 240 °C · heat-check index 0.31
  11. 05:43:57approval.request({ action: "press_schedule", blow2: "-3%" })
  12. 05:47:31ok approved by shift forging engineer · logged
  13. 05:47:32press.set_schedule({ press: "F-2", recipe: 9 })
  14. 05:49:08ok fill complete on 10 pieces · lap risk 0.27 → 0.08
  15. 05:49:09sensors.fuse({ cams: 8, thermal: 2, ut: true })
  16. 06:21:40precursor: lap risk 0.52 · flash land · piece 212
  17. 06:21:41press.set_schedule({ press: "F-2", blow2: "-1.5%", within: "approved envelope" })
  18. 06:21:58ok lap risk 0.52 → 0.07 · piece 212 routed to MPI · passed
  19. 06:22:00isaac.plan_path({ task: "press_to_trim", cell: "F-2" })
  20. 06:22:11ok 11 s per piece · transfer loss 38 °C · zones clear
  21. 06:22:12furnace.set_zone({ furnace: "HT-1", zone: 2, delta: "-5 °C" })
  22. 06:58:40ok first hardness 30 HRC · inside 28 to 32
  23. 06:58:41mes.log_forging({ lot: "L-80412", genealogy: "full" })
  24. 07:00:01ok scenario complete · 10 steps · 0 laps escaped · released

Reasoning trace

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

GoalRun the 42CrMo4 connecting-rod lot on cell F-2 inside the qual…

Run the 42CrMo4 connecting-rod lot on cell F-2 inside the qualified window, hold full fill with zero laps at the flash land, and land hardness between 28 and 32 HRC.

PlanSimulate heat-and-stroke recipes on the twin first. Lead with …

Simulate heat-and-stroke recipes on the twin first. Lead with heating so the billet state is right before the stroke, then set spray against die temperature, then execute the approved press schedule. Fuse inspection continuously. Hold any press-schedule change for a human.

ThoughtThe standing schedule runs the second blow hot enough to guara…

The standing schedule runs the second blow hot enough to guarantee fill on a cold billet. With the induction soak held at 1,205 °C the twin predicts the same fill at 3% less energy and lower flash-land lap risk, because the metal arrives more uniform.

Actiontwin.simulate(candidates=24) returns recipe #9: stage-3 induct…

twin.simulate(candidates=24) returns recipe #9: stage-3 induction power down 4%, lower-die spray up 6%, second-blow energy down 3%.

ObservationRecipe #9 predicts fill 1.00, lap risk 0.08 and 1.9 kWh per pi…

Recipe #9 predicts fill 1.00, lap risk 0.08 and 1.9 kWh per piece. Two candidates scored lower on energy but pushed predicted die load past the cavity-2 limit and were discarded.

ActionExecute recipe #9: seven bounded writes permitted on heating, …

Execute recipe #9: seven bounded writes permitted on heating, spray, handling and heat-treat; the press-schedule write routed to the shift forging engineer.

ObservationLap precursor at the flash land on piece 212 at 06:21:40. A 1.…

Lap precursor at the flash land on piece 212 at 06:21:40. A 1.5% blow-energy trim inside the approved envelope cleared it in 17 s; the piece was routed to MPI and passed.

OutcomeScenario complete. Fill confirmed, no laps escaped, hardness 3…

Scenario complete. Fill confirmed, no laps escaped, hardness 30 HRC. Lot L-80412 released with full genealogy.

Autonomy

Four levels, set per agent and per tag

A forge does not go from manual to unattended in one step. Forgiron 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 actions. Press control stays supervised until the part family is qualified.

Autonomy levels and the human role at each
LevelWhat the agent doesWhat the human doesWhere it sits in a pilot
L1 · ShadowReads thermal, vision, ultrasonic, MPI, press, die, robot and MES signals; predicts and recommends; writes nothingRuns the cell as today; compares predictions to inspection and engineer outcomesShadow mode, baseline 30 to 60 days
L2 · AssistProposes heating, press, die-lube, routing and handling actions with evidence, confidence, envelope and rollback pathApproves each action in the review consoleAssist mode, the remainder of a 90 to 180 day pilot
L3 · BoundedExecutes pre-approved low-risk actions: inspection routing, lube timing, heating and soak adjustments, robot path variants, inside PLC and safety limitsApproves press-schedule changes, die changes and lot releaseGraduated autonomy, after audited accuracy and ROI
L4 · ScaledSupervised press-schedule adaptation for qualified part families, across cells and sitesSets the envelope; reviews the shift record and the evaluation resultsPlanned; after golden-dataset evaluation, simulation validation and quality sign-off
Accelerated computing

Physical AI, at the press

A stroke lasts a fraction of a second and a billet cools while it waits. Perception has to be local, deterministic and fast, so Forgiron 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 cameras per line plus thermal, ultrasonic, MPI, press and ram streams fused at the cell. Sub-100 ms visual alerts and sub-500 ms recommendations are the design targets. Jetson Thor is planned for higher sensor density.

Triton · NIM

Model serving

Defect, ultrasonic and MPI fusion, die-wear, heating, press-fill, property and disposition models behind one orchestrator at the plant edge, routed by latency, tenant, sensitivity and cost, with canary rollout by cell.

DGX or HGX · NeMo

Training

Multimodal defect, die-wear, heating, press-fill, property and quality-disposition models trained on thermal images, high-speed vision, ultrasonic and MPI signals, press curves and engineer corrections. Dedicated training capacity is planned.

Omniverse · OVX · Modulus

Forge-line twin

Billet heating, die thermal state, press stroke, fill, stress, die load and robot handling simulated before the stroke. GPU forging FEM is the workload; physics-informed surrogates are planned so recipes rank at production cadence.

Cosmos · Omniverse Replicator

Synthetic data

Rare lap, fold, underfill, crack and die-wear scenarios generated and validated against real inspection distributions before promotion. Planned.

cuOpt

Optimisation

Die allocation, press sequencing, heating batches, heat-treat queues, robot and takt coordination and inspection routing.

Isaac Sim · Isaac Lab · Isaac ROS

Robot handling

Hot billet, forging, die and trim handling skills trained and validated in simulation before they run next to a press.

RAPIDS

GPU ETL

Daily features from thermal, video, ultrasonic, MPI, press and genealogy data for retraining, drift detection and yield, scrap, die-life and energy benchmarks.

FAQ

Straight answers

The questions plant directors, forging engineers and quality engineers ask in the first meeting.

Yes, but only within an explicit tag allow-list with per-tag rate and magnitude limits, inside the qualified process envelope, and only at the autonomy level your plant has set. Design partners start in shadow mode, where Forgiron writes nothing. Press-schedule changes stay supervised by a named forging engineer until the part family is qualified.

Get started

Follow the release line

Ask to be told when the first release ships.