CAIN-42 CAIN Studio

AGENTIC AI 75 · #8

Robot programming through agent teams

Berkeley described agents that write, simulate, test and refine interpretable robot-control programmes.

Last reviewed 2026-11-11

Agentic AI 75 / #8

SIMULATEDMoat 4 · Execution Provenance & AttestationBundle · Physical & LabStream 2

2026 status: Robotics research · Category: Robotics

The 2026 development

Berkeley described agents that write, simulate, test and refine interpretable robot-control programmes.

The governance gap

Generated control code is executable in the physical world. The dangerous transition is not the code generation; it is the promotion of a simulated success into a real actuator command.

Where CAIN-42 fits: Moat 4 — Execution Provenance & Attestation

Core question: Can we prove what actually happened? Hash-chained, signed records binding decision to execution to observable effect.

Keep generation, simulation, test and deployment as separate signed stages. A programme may be promoted only when the same artifact hash passed the simulator and the deployment gate, and the gate records the operator who released it.

How the wiring works

  1. Hash the generated programme and its test corpus.
  2. Run the simulator in an isolated sandbox with no actuator access.
  3. Require a human release step for the first physical deployment of any new programme.
  4. Record actuator commands and observed motion as effects bound to the released hash.

What is real today

SIMULATED A lab, replay or physical-simulation path. It is not hardware, not a real customer action, and not a safety certification.

Sandboxing and provenance are real. No robot-control programme has been generated, simulated or deployed by this deployment.

Component in this repositoryWhat the module says it is
cain/isolation/sandbox.pyHardened Execution Isolation Fabric — Evolution 6: Project Sovereign Isolation.
cain/argus/physical.pyCAIN ARGUS — physical-AI assurance (Prompt 14, section 15). SIMULATED.
keystone/sandbox.pyRun a module's tests inside a bubblewrap sandbox: no network, read-only system, only its own files, time-boxed.
cain/talos/talos_sandbox_launcher.pyTALOS sandbox launcher. Run as a program (``python -I talos_sandbox_launcher.py``), never imported by the

Descriptions are the first line of each module's own docstring, read without importing it. A module path is a pointer into this repository, not a hosted endpoint. Its existence is checked by the test suite; its status for this use is the label above.

Check it yourself

Commercial package

OfferRobotics Release Gate Review
BuyerRobotics vendors and industrial automation teams
Price (proposal)$7,500–$15,000 per review
BundlePhysical & Lab — A validity check between the plan and the machine.
Operator streamStream 2 of the 10-stream operator playbook

Lab automation, robotics, industrial operations, construction technology is the bundle buyer. The entry offer for this bundle is Physical-action assurance review (advisory, simulation-first); the range is $5,000–$15,000 per engagement. A price on this page is a proposal, not a validated rate, and no customer is claimed.

Buy this as a product or service

CAIN-A75-008 — Robotics Release Gate Review DELIVERABLE

A bounded engine run on the buyer's sample: findings, a written report, and a SHA-256 artifact manifest. The manifest is unsigned: it is not a signature and not an attestation.

Kind: Assessment · Price (proposal): $7,500–$15,000 per review · Lead time: 5 business days.

Open the product page · all 75 products

What this page does not claim

What this page is not. CAIN-42 is not affiliated with, endorsed by, integrated into, or shipped with the organisation named in the 2026 item. The item is public context; the page describes how CAIN-42 would govern that class of capability. No page here claims a customer, a partnership, a certification, a patent, or a production integration. Prices are proposals. Built by a three-person team.

← #7 Digital twins for safe physical agent actionsAll 75#9 End-to-end autonomous R&D loops →