SYNTHETIC COMPATIBILITY PREVIEW

Known combinations.
Explicit limits.

A registry for documented firmware, calibration, and policy constraints. Every rule here is invented to demonstrate the workflow. No real hardware or software combination has been validated.

Check a synthetic run

hardware
G-02 / B
firmware
gripper-fw-1.9
calibration
camera-cal-08
model
pick-policy-v4
procedure
pick-v2
object
Pick block-A
Synthetic known-bad match

All six recorded values match the invented rule below. This is an illustration, not a diagnosis of this run or a real safety determination.

INVENTED KNOWN-BAD EXAMPLE

SYN-RULE-001 · revision 1

Invented constraint: this combination uses an incompatible gripper coordinate convention in the block-A picking procedure.

Hardware scope
G-02 / revision B
Combination
gripper-fw-1.9 + camera-cal-08 + pick-policy-v4
Procedure scope
pick-v2; block-A picking
Author / recorded
Demo test engineer / 2026-09-01T14:00:00Z
Evidence
SYN-EVIDENCE-001 — invented bench-check reference; underlying evidence unavailable
Validation status
Synthetic only. No verified customer constraint.

A real rule needs repeatable checks, an identified author, exact scope, version history, and accessible evidence. A changed version alone does not establish incompatibility.

Inspect the full run and working setup reference →

Read-only synthetic registry. No enforcement, deployment, automatic rollback, or robot communication.

Meet Tav
A good place to start

Curious about Tav?

Explore an example or talk through your workflow with the founders.

Book a demo ↗Explore the synthetic demo →Demo & contact guide · Not a live chat