Changelog

Every release that can touch a line, written down.

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

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-partner plants on the wedge workflow
  • Ship the MVP: connectors, agent loop, review console, safety-grade quality and traceability audit log
  • Prove accuracy and rework, downtime and warranty ROI in shadow then assist mode
  • Security and compliance baseline: SOC 2 Type I and an IATF and functional-safety-aware review in progress, IP-safe edge deployment

6 to 12 months · planned

Phase 2

  • Convert design partners to paid; early revenue
  • Graduated autonomy for low-risk weld, paint and torque loops; plant twin hit-build-quality-before-shift
  • Second process within the plant; deeper integrations
  • SOC 2 Type II; SSO and RBAC; first OEM and EV plants; IATF, APQP and functional-safety assurance packages

1 to 3 years · planned

Phase 3

  • Own the full stamping, body, paint, powertrain and battery, assembly and end-of-line loop end to end
  • Single plant to multi-plant OEM to global platform and vehicle-program fleet
  • Robot OEM, press and paint vendor, metrology and vision and MES channel; international expansion
  • Data-network products: build-quality, geometry, paint, torque and warranty benchmarks as premium tiers
Policy

How a release reaches a line

The promotion and rollback rules.

  • Model versions are promoted by line. A new model version reaches one line 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, qualified envelopes and approval chains are reviewed and recorded before a release can write to a line.
  • Every release carries its evaluation record. Golden datasets and judged evaluations gate model and prompt changes in CI before promotion.
  • Safety-critical parameters stay locked across releases. No release changes the read-only status of torque specifications, battery-joint parameters or test limits and verdicts.
  • 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 line, per programPrevious 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 line.

run_41a9c2 Plant BIW-2 · EV crossover body shop to end of line · shift 1 illustrative scenario SUCCEEDED
  1. 01 ingest.shift SUCCEEDED 0.8 s

    Plant Orchestrator · Pulled the shift build sequence, program control plan and qualified envelopes from MES: 412 bodies, four trim variants, weld schedule set W-rev 7, framing targets per station, paint colour blocks, torque specifications. Locked every safety-critical parameter as read-only.

  2. 02 twin.simulate SUCCEEDED 1 m 40 s

    Vehicle-and-Line Twin · Simulated 18 candidate weld-sequence, framing-offset and booth-window combinations on the plant twin, ranked on predicted body geometry, expulsion risk at robot W-14, paint defect map and takt against launch cadence.

  3. 03 stamp.form SUCCEEDED continuous

    Stamp-and-Form · Blank feed on press line P-3 adjusted by 0.4 mm and lubricant dose raised 3 percent for the new coil lot as springback risk on the rear door inner climbed. Panel dimension held inside the window; genealogy handed to framing.

  4. 04 approve.human APPROVAL 3 m 12 s

    Plant Orchestrator · Candidate #6 lowers weld current 2 percent and adds 20 ms hold on robot W-14 to cut predicted expulsion. Weld schedules are crash-safety critical and stay with a human, so the change was held for the body-shop launch engineer and approved at 06:14:52.

  5. 05 weld.join SUCCEEDED continuous

    Weld-and-Join · Approved schedule 7b applied on W-14. Current and force traces confirmed inside the window on the first 40 bodies; predicted expulsion risk fell from 0.31 to 0.06 and no geometry debt was introduced at the adjacent seams.

  6. 06 frame.geometry SUCCEEDED continuous

    Frame-and-Geometry · Framing station FS-1 offset corrected by 0.3 mm on the left B-pillar datum inside the qualified envelope as in-line measurement trended toward the tolerance edge. Gap-and-flush vision confirmed the correction on the next 25 bodies.

  7. 07 paint.finish SUCCEEDED continuous

    Paint-and-Finish · Booth B-2 humidity trimmed 2 points and airflow rebalanced for the dark-colour block as the defect model predicted dirt on horizontal panels. Film build held inside the window on the first colour block.

  8. 08 marriage.torque SUCCEEDED continuous

    Powertrain-and-Battery · Pack PK-1182 held at marriage after a torque-to-yield trace on fastener 7 fell outside the specification curve. Routed to rework with the trace attached; torque specification untouched, as always.

  9. 09 inspect.fuse SUCCEEDED continuous

    Quality-and-Anomaly · Gap-and-flush and paint-defect cameras, weld and torque traces and test results fused per body. Two paint dirt defects localised to booth B-2 zone 3 before the humidity trim took effect; both routed to spot repair, none escaped to final.

  10. 10 eol.release SUCCEEDED 2 m 05 s

    EOL-and-Calibrate · End of line proved alignment, ADAS calibration, leak, brake, roll and functional tests on every vehicle; two ADAS retests sequenced inside takt. Shift 1 released with as-built records, approvals and dispositions written for the quality lead.

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_41a9c2
  1. 06:00:02mes.read_sequence({ plant: "BIW-2", shift: 1, program: "EV-CUV" })
  2. 06:00:03ok 412 bodies · 4 variants · weld set W-rev 7 · torque specs read-only
  3. 06:00:04twin.simulate({ candidates: 18, horizon: "1 shift" })
  4. 06:01:44ok best #6 · geometry inside targets · expulsion risk 0.06 · takt 61 s
  5. 06:01:45policy.evaluate({ candidate: 6, autonomy: "L2+" })
  6. 06:01:45ok 6 writes permitted · weld_schedule requires human approval · torque_spec locked
  7. 06:01:46blank.set_feed({ press: "P-3", delta: "+0.4 mm", lube: "+3%" })
  8. 06:02:30ok springback risk 0.42 → 0.11 · panel dimension in window
  9. 06:02:31approval.request({ action: "weld_schedule", robot: "W-14", current: "-2%", hold: "+20 ms" })
  10. 06:14:52ok approved by body-shop launch engineer · logged
  11. 06:14:53weld.apply_schedule({ robot: "W-14", rev: "7b" })
  12. 06:48:10ok 40 bodies in window · expulsion risk 0.31 → 0.06
  13. 06:48:11frame.set_offset({ station: "FS-1", datum: "B-pillar L", delta: "-0.3 mm" })
  14. 07:12:44ok 25 bodies inside targets · gap-and-flush confirmed
  15. 07:12:45booth.set_env({ booth: "B-2", humidity: "-2 pt", airflow: "rebalance" })
  16. 07:40:02precursor: dirt risk 0.58 · booth B-2 zone 3 · dark colour block
  17. 07:40:03ok 2 defects localised · routed to spot repair · 0 escaped
  18. 08:05:19unit.hold({ pack: "PK-1182", fastener: 7, reason: "torque trace off curve" })
  19. 08:05:19ok held at marriage · routed to rework · spec untouched
  20. 08:05:20sensors.fuse({ cams: 24, traces: true, tests: true })
  21. 13:40:00retest.sequence({ vehicles: 2, test: "ADAS calibration" })
  22. 13:52:31ok 2 retests passed inside takt
  23. 13:58:00mes.log_vehicle({ shift: 1, records: "as-built" })
  24. 14:00:05ok scenario complete · 10 steps · 0 escapes · shift released

Reasoning trace

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

GoalRun shift 1 on plant BIW-2 inside the qualified envelopes, hol…

Run shift 1 on plant BIW-2 inside the qualified envelopes, hold body geometry at the framing station, keep expulsion and paint defects from escaping, hold every torque to specification and prove every vehicle at end of line.

PlanSimulate weld-sequence, framing and booth candidates on the tw…

Simulate weld-sequence, framing and booth candidates on the twin first. Lead with stamping so panels arrive in dimension, then propose the weld schedule and hold it for a human, then correct framing inside the envelope, then set the booth ahead of the colour block. Fuse inspection continuously. Never touch a torque specification or a test verdict.

ThoughtThe standing weld schedule on W-14 runs current high enough to…

The standing weld schedule on W-14 runs current high enough to guarantee the joint on the thickest stack. With the new coil lot and panel dimension held at P-3, the twin predicts the same joint quality at 2 percent lower current with a 20 ms hold, and lower expulsion, because the panels arrive flatter.

Actiontwin.simulate(candidates=18) returns #6: blank feed +0.4 mm on…

twin.simulate(candidates=18) returns #6: blank feed +0.4 mm on P-3, weld current -2 percent and +20 ms hold on W-14, framing offset -0.3 mm at FS-1, booth B-2 humidity -2 points for the dark block.

ObservationCandidate #6 predicts geometry inside targets, expulsion risk …

Candidate #6 predicts geometry inside targets, expulsion risk 0.06, a lower dirt map and takt at 61 seconds. Three candidates scored better on takt but pushed predicted B-pillar variation past the tolerance edge and were discarded.

ActionExecute #6: six bounded writes permitted on stamping, framing,…

Execute #6: six bounded writes permitted on stamping, framing, booth, routing and sequencing; the weld-schedule write routed to the body-shop launch engineer; torque specifications and test limits locked.

ObservationDirt precursor in booth B-2 zone 3 at 07:40:02 before the humi…

Dirt precursor in booth B-2 zone 3 at 07:40:02 before the humidity trim took effect. Two defects localised and routed to spot repair; none escaped. One pack held at marriage on a torque trace at 08:05:19.

OutcomeScenario complete. Geometry inside targets, no expulsion escap…

Scenario complete. Geometry inside targets, no expulsion escapes, paint defects caught in station, one pack reworked, two ADAS retests passed inside takt. Shift 1 released with full as-built records.

Autonomy

Four levels, set per agent and per tag

A car plant does not go from manual to unattended in one step. Chassira 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 loops. Weld schedules stay supervised until the joint family is qualified, and torque specifications and test verdicts are never written by an agent.

Autonomy levels and the human role at each
LevelWhat the agent doesWhat the human doesWhere it sits in a pilot
L1 · ShadowReads weld, metrology, vision, torque, test, robot and MES signals; predicts and recommends; writes nothingRuns the line as today; compares predictions to audit and engineer outcomesDesign partners start here; the baseline is measured from the plant's own records
L2 · AssistProposes weld, framing, paint, routing, holding and sequencing moves with evidence, confidence, envelope and rollback pathApproves each action in the review consoleAssist mode: accuracy and ROI proven against the signed baseline
L3 · BoundedExecutes pre-approved low-risk actions: booth environment, framing offsets, blank feed and lubrication, routing, holds, sequencing, inside PLC and safety limits and the qualified envelopeApproves weld-schedule changes, torque-related decisions and vehicle releaseGraduated autonomy, after audited accuracy and ROI
L4 · ScaledSupervised weld-schedule adaptation for qualified joint families, across lines and plantsSets the envelope; reviews the shift record and evaluation resultsPlanned; after golden-dataset evaluation, twin validation and quality sign-off. Torque specifications and test verdicts never leave human hands
Accelerated computing

Physical AI, at the line

A spot weld lasts a fraction of a second and a body passes a station every minute. Perception has to be local, deterministic and fast, so Chassira 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 32 cameras per process area at 15 to 60 FPS, plus torque, dimensional, thermal, robot and paint-instrument streams fused at the cell. Weld and gap alerts under 50 ms and paint or dimensional prompts under 150 ms are the design targets. Jetson Thor is planned for higher density.

Triton · NIM

Model serving

Weld-defect, geometry-risk, paint-risk, torque and battery, and takt-risk models served at the plant edge with versioned rollback, routed by latency, tenant and cost, with canary rollout by line.

DGX or HGX · NeMo

Training

Weld, paint and gap vision, dimensional models, NeMo IATF and spec reasoning and GPU-accelerated stamping, springback and weld-geometry FEA surrogates. 150 to 600 GPU-hours per plant during onboarding, then monthly retraining from engineer corrections. Dedicated capacity is planned.

Omniverse · OVX

Plant twin

Body framing, weld sequence, robot reach, paint flow and line balance simulated before the shift. The pattern is production proven at BMW and Mercedes-Benz, per the architecture; Chassira's twin and OVX capacity are planned.

Cosmos · Omniverse Replicator

Synthetic data

Rare weld defects, paint failures, geometry-drift modes, occluded joints and misbuild cases generated and validated against real distributions before promotion. 50,000 to 250,000 variants per program is the design target. Planned.

cuOpt

Optimisation

Line sequencing and JIS feeding, AGV routing, takt, line balancing, buffers and retest sequencing.

Isaac · Isaac ROS

Robot cells and AMRs

Robotic weld, paint, assembly and inspection cells and AGV and AMR line-feed autonomy, with skills validated in simulation before a cell runs them.

RAPIDS

GPU ETL

Telemetry ETL across weld and press parameters, measurements, paint readings, torque traces, battery and ADAS results, non-conformance and takt history for retraining and benchmarks.

NeMo Guardrails · NVIDIA AI Enterprise

Policy and deployment

Spec, IATF, functional-safety, cyber and human-approval policy enforced before any write; supportable on-prem or plant-edge deployment for regulated OEM plants.

FAQ

Straight answers

The questions plant managers, launch engineers and quality leads ask in the first meeting.

Yes, but only within an explicit tag allow-list with per-tag rate and magnitude limits, inside the qualified envelope, and only at the autonomy level your plant has set. Design partners start in shadow mode, where Chassira writes nothing. Weld-schedule changes wait for a named body-shop engineer, and torque specifications, battery-joint parameters and end-of-line test limits and verdicts are read-only to every agent, always.

Get started

Follow the release line

Ask to be told when the first release ships.