Level-eight deliverable evidence package · 03

TurtleBot3 bounded-site navigation release evidence package

An eighth-level release archive binding one robot, software, map, parameter set and supervised indoor site to complete route, obstacle, failure and intervention evidence.

Evidence statusSupervised indoor release package · blank JSON manifest · no unattended-service approvalStructure 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 to transfer a bounded release candidate without losing the map, site contract, route coverage, interventions, near misses, failure exercises and regression triggers that define its actual scope.

Package structure

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

0100_manifest/

Release identity

manifest.json, signed route matrix, bounded claim, expiry and reviewers

One release candidate

0210_robot-software/

Robot baseline

Serial, hardware, OpenCR/SBC firmware, ROS 2/Nav2 packages and diagnostics

Immutable candidate manifest

0320_map-site/

Map and site contract

Map, TF, footprint, parameters, dated site drawing, inspection and operating period

Hash and revision for each asset

0430_routes/

Coverage catalogue

Start/goal zones, both directions, obstacle cases, repetitions and success criteria

Declared before trials

0540_runs-failures/

Run and fault evidence

Rosbags, logs, video index, outcomes, interventions, near misses and injected failures

Every attempt, including aborts

0650_release-regression/

Bounded release

Golden routes, thresholds, deviations, supervision, expiry and retest triggers

Signed reviewer decision

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": "mobile",
    "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.

Candidate closure

Review question

Do robot, software, map, parameters and site revision resolve to one immutable candidate?

Reject when

A successful run cannot be reconstructed

Coverage closure

Review question

Are both directions, all start/goal zones, obstacles, failures and interventions indexed?

Reject when

Aborts or interventions are counted as autonomous success

Release closure

Review question

Does the signed decision name supervision, site, time, configuration and regression triggers?

Reject when

The evidence is used to imply unattended or other-site operation

Recipient verification

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

01Verify the robot and candidate manifest at the receiving site.
02Compare the dated site contract and map against current conditions.
03Replay one golden route and one declared failure under supervision.
04Issue a new package when map, footprint, critical parameter or site contract changes.

FUURAA analysis

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

A navigation release is a relationship among robot, software, map, parameters, site and supervision. The package prevents evidence from being detached from any one of those conditions and reused as a broader autonomy claim.

Primary technical sources

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

ROBOTIS · TurtleBot3 NavigationPrimary mapping, bring-up and navigation workflow↗Nav2 · Configuration GuidePlanner, controller, recovery and lifecycle configuration↗Nav2 · Collision MonitorZones, sensor sources, timeouts and velocity constraints↗

Return to the level-seven field evidence record →