Level-eight deliverable evidence package · 01

SO-101 calibration and bounded-motion evidence package

An eighth-level handoff structure that binds one physical leader/follower pair, calibration identity, software baseline, raw motion evidence and bounded disposition into one reviewable archive.

Evidence statusReusable package structure · blank JSON manifest · not a certificationStructure reviewed 4 August 2026

Open evidence-package verifier ↗View package structure ↓Back to level-seven field record ↗

Handoff purpose

Enable the recipient to verify, restore, review and reject an incomplete claim.

Use this package only after the level-seven record is complete. It enables another engineer to restore the exact calibration context, inspect every attempt and decide whether a claimed result can be reproduced.

Package structure

A fixed directory keeps evidence legible across teams, time and tools.

0100_manifest/

Identity and review

manifest.json, signed record, claim boundary, deviations and release decision

Required before transfer

0210_as-built/

Physical pair

Serials, servo IDs, revision, substitutions, photographs and wiring

Exact leader and follower

0320_software/

Reproducible baseline

LeRobot commit, lockfile, OS, ports, configuration and environment digest

Clean rebuild evidence

0430_calibration/

Calibration identity

Original calibration files, digests, joint limits, offsets and recovery copy

Bound to the physical pair

0540_trials/

Every attempt

Run matrix, raw command/state traces, video index, interventions and failures

Successes, aborts and exclusions

0650_disposition/

Decision

Accepted boundary, unresolved deviations, recalibration triggers and signatures

Independent review

Machine-readable manifest

JSON carries index and integrity; the signed record carries the human decision.

Key	Meaning	Rule
`package_id`	Globally unique evidence-package identity	Immutable after review begins; never recycle an identifier
`record_id`	Identity of the level-seven field record	Must resolve to the signed source record
`subject`	Exact robot, module or release candidate	Use serials, revisions and as-built configuration—not a product family name
`baseline_hash`	Configuration, software, map or calibration baseline	Record the algorithm, digest and source artifact
`evidence_index`	Machine-readable list of every retained artifact	Each entry needs path, media type, size, digest, producer and capture time
`claim_boundary`	Exact claim supported by this package	Name the build, task, site, energy and supervision limits
`deviations`	Open, accepted and rejected deviations	Never omit failed or excluded runs from the index
`review`	Owner, independent reviewer, decision and time	A machine-readable decision must point to a signed human record

{
  "schema": "https://fuuraa.com/schemas/robotics-evidence-package/v1",
  "package_id": "",
  "record_id": "",
  "subject": {
    "family": "arm",
    "serial": "",
    "revision": "",
    "as_built_reference": ""
  },
  "baseline_hash": {
    "algorithm": "sha256",
    "value": "",
    "source_artifact": ""
  },
  "claim_boundary": {
    "task": "",
    "configuration": "",
    "site": "",
    "energy_or_speed": "",
    "supervision": "",
    "excluded_uses": []
  },
  "evidence_index": [
    {
      "path": "",
      "media_type": "",
      "bytes": 0,
      "sha256": "",
      "producer": "",
      "captured_at": ""
    }
  ],
  "deviations": {
    "open": [],
    "accepted": [],
    "rejected": []
  },
  "review": {
    "owner": "",
    "independent_reviewer": "",
    "decision": "pending",
    "signed_record": "",
    "decided_at": ""
  }
}

Review gates

If any gate remains open, the package remains unreleased.

Identity closure

Review question

Do serials, servo IDs, calibration digest and configuration digest identify one exact pair?

Reject when

Any asset can be silently substituted

Time-base closure

Review question

Can commands, state, video, intervention and stop events be ordered on one documented clock?

Reject when

Only edited video or summary plots remain

Claim closure

Review question

Does the decision name the exact build, task, objects, workspace, speed and retest triggers?

Reject when

A successful demonstration is presented as general capability

Recipient verification

Handoff is complete when the recipient can independently reconstruct the decision—not when files were copied.

01Verify every indexed digest from a read-only copy.
02Restore software and calibration without oral knowledge.
03Re-run one bounded reference motion under the original stop arrangement.
04Record the receiving reviewer and any migration performed after transfer.

FUURAA analysis

An evidence package must support review—and allow the reviewer to reject.

The package is complete only when identity, calibration, software, raw evidence and decision form one cryptographically checkable chain. A folder full of files without this chain is storage, not engineering evidence.

Primary technical sources

The package structure does not enlarge the capability or safety claims of its sources.

Hugging Face · Assemble SO-101Assembly, servo configuration and calibration workflow↗Hugging Face · Real-world robotsPersistent identities and calibration reuse↗Hugging Face · LeRobotDataset v3Multimodal records, metadata and time-series structure↗

Return to the level-seven field evidence record →