Inztinct Learn

Learn makes the fleet better. It cannot make it looser.

Learn is how Inztinct improves. Robots learn from their own sites, share what they learned without sharing raw footage, and receive improvements only as tested, signed releases. Learn can change Sense and the planner. It has no path to Core.

PlannedAfter Sense
The release pipeline

Eight steps between a lesson and a robot.

Two steps are gates. If either one fails, the release stops.

  1. Observe on site

    Each robot logs near-misses, stops and corrections. Raw data stays on the machine or on the site's own server.

  2. Train offline

    Candidate updates are trained away from the robot. A running robot never learns live.

  3. Share updates, not footage

    Only model updates leave the site (federated learning). Open frameworks such as NVIDIA FLARE are an option we are evaluating.

  4. Check the contributions

    Odd or poisoned updates are rejected before they are merged.

  5. Regression suite

    Every Core limit and every recorded scenario is replayed in simulation. One failure stops the release.

    Gate
  6. Hazard check

    In every scene tagged hazardous, the new model must allow no more than the approved baseline. It may relax caution elsewhere, which is how nuisance stops come down.

    Gate
  7. Signed release

    A person approves. The model is frozen and signed. The robot installs only signed releases.

  8. Staged rollout

    A few robots first, with rollback ready and the logs watched.

Learn can change
  • Sense models
  • Planner policies
  • Suggested profile changes, which a person reviews and loads with a physical key
Learn cannot change
  • Core firmware
  • Core limits
  • A profile on its own
Why federated

Learn where the robot works.

Privacy

Footage stays on site

A ward, a factory floor or a mine pit does not need to send raw video away for the fleet to learn from it.

Reach

Works without a signal

Training and checks run offline. Releases move when a link is available, or by hand.

Scale

One site's near-miss helps every site

A lesson from one corridor can improve every robot in the fleet, once it passes the gates.

What can go wrong

Federated learning has its own risks.

Risk

Poisoned updates

A bad site or an attacker sends updates meant to teach the fleet something unsafe. We check contributions and the gates catch behaviour changes in hazard scenes.

Risk

Leaky updates

Model updates can reveal something about the data behind them. We treat updates as sensitive and are evaluating protections.

Risk

Drift

A model that suits one site may suit another worse. Staged rollout and rollback exist for this.

These are the risks we plan for. None of the protections are built yet.

What we will publish

Improvement, with the safety suite still green.

The claim we want to be able to make: robots across sites got better, and no release failed the safety suite. We will publish the numbers once there are numbers.

Metric · nuisance stops over timeMetric · safety-suite regressions, target zeroMetric · releases blocked at a gate

Three layers. One robot.

Core holds the line. Sense reads the room. Learn gets better.