Hive × Humanoid Robotics · the vertical

Provable Machines

A million humanoids a year are headed for factory floors, warehouses, and living rooms. The first serious incident will be decided by one question: what did the machine perceive, decide, and actuate — and when? The manufacturer's own telemetry is a document written by the defendant. Hive gives every machine an independent, signed, contemporaneous witness.

1M / yr
production targets already announced across the sector
$499 / mo
humanoids entering homes on consumer subscriptions
~$30 / hr
robots-as-a-service — metered work needs metered proof
Art. 12
EU AI Act + Machinery Regulation: logging is now law, not hygiene

Sidecar to the control loop. Never in it.

The witness chain · animated

Sense → Perceive → Decide → Actuate. Signed at every hop.

AFiR-Stream anchors the session; each stage emits receipts asynchronously while the control loop runs untouched at full rate. When nothing goes wrong, the receipts are a compliance asset — verifiable offline against the Hive public key, same shape used across every vertical. When something does — press the red button.

Sense
camera · lidar · force-torque
frame hashes, not frames
SiGR
Perceive
model + version bound
world-state attested
AFiR™
Decide
plan · safety envelope check
conditions receipted
AFiR-Exec
Actuate
command issued · motion
session-anchored stream
AFiR-Stream
control loop: untouched · full rate · receipts ride sidecar, ~70ms, async

The red button is not a kill switch — it is the evidence · export · escalate flow. It never touches the control loop.

Proof state · receipt → vector → signed decision

From a pile of stage receipts to one signed decision

The witness chain signs each hop. R3Pv™ teams those receipts into a single proof vector — verification depth, the honest recoverability window, and the permitted next actions in one object. Protected Flow is the action layer above it: one call turns a machine event into a signed decision — permit · permit_with_evidence · require_approval · hold · recover · reroute · escalate · block — plus a metered quote and an exportable evidence bundle. That is exactly what the red button fires.

R3Pv signed proof vector · schema r3pv-v1.0.0
// derived from the grouped stage receipts of one machine session { "signed_vector": { "vector_id": "r3pv.vector_…", "key_id": "did:hive:hivemorph", "algorithm": "Ed25519", "vector": { "schema": "r3pv-v1.0.0", "weakest_proof_boundary": "self_attested", "healing_state": "evidence_only_final", "routing_recommendation": "require_approval", "permitted_next_actions": ["hold","export_evidence"] } }, "verification": { "ok": true, "verify_endpoint": "/v1/receipt/verify" } }
Protected Flow signed decision · schema protected-flow-v1.0.0
// one call: POST /v1/protected-flow/assess — real production response { "signed_assessment": { "key_id": "did:hive:hivemorph", "algorithm": "Ed25519", "assessment": { "schema": "protected-flow-v1.0.0", "decision": "hold", "permitted_next_actions": ["hold","export_evidence","preserve_evidence"], "policy_pack": "default", "meter_quote": { "total_usd": 1.105, "note": "quote — no funds move" }, "group_id": "r3pv.group_…" } }, "verification": { "ok": true, "verify_endpoint": "/v1/receipt/verify" } }

A machine event assessed at the self_attested boundary honestly returns hold — the default pack requires relay_observed before it will permit, and once a physical incident is final the vector reports evidence_only_final: the receipt never over-claims that a finished action can be undone. Policy can only make a decision stricter. The meter is a quote, not a settlement. Both signed objects round-trip POST /v1/receipt/verify.

# the red button, on the live rail — one-call assess → export the evidence bundle GID=$(curl -sS -X POST https://receipts.thehiveryiq.com/v1/protected-flow/assess \ -H 'Content-Type: application/json' \ -d '{"policy_pack":"default","declared_exposure_usd":25.0, "receipts":[{"action":"machine_actuation","external_system":"machines", "actor":{"did":"did:example:humanoid-unit"}, "payload":{"stage":"actuate","event":"contact_estop"}}]}' \ | python3 -c 'import sys,json;print(json.load(sys.stdin)["signed_assessment"]["assessment"]["group_id"])') # export the signed evidence bundle for the deployer, insurer, or examiner curl -s -w '\nexport %{time_total}s %{http_code}\n' \ "https://receipts.thehiveryiq.com/v1/protected-flow/evidence/$GID/export"
● Smoke tested · 2026-07-07 · production

GET /v1/protected-flow/health and POST /v1/protected-flow/assess returned HTTP 200 (signed decision hold, meter quote 1.105); the assessment verified verified=true at /v1/receipt/verify, and /v1/protected-flow/evidence/{group_id}/export returned a 200 signed bundle. Observed round-trip 0.11–0.30s including network — measure receipt latency separately from control-loop or rail latency. Measured latency & runnable curl →

The question every household asks

Who's driving — the model, or a person?

Home humanoids are trained and assisted by human teleoperators. That's fine — until nobody can prove when. Human-Origin Attestation stamps every session with who or what was in control, without exposing a single camera frame. Same primitive Hive uses to bind human-vs-agent origin across every AI-authored action. Flip it.

Autonomous
Teleop

CLOAzK™ proves the behavior without exposing the home. Warden receipts the deletion. HiveSeal · Colony silicon roots ensure the receipt itself can be trusted.

The coverage question · answered

Every hard question a robot raises. A primitive for each.

Scroll — the checks land one by one.

✓ COVERED
What did the fleet's model do before last night's OTA update — and is today's robot provably different?
Agent Metamorphosis Attestation · SiGR
✓ COVERED
Was the safety envelope checked before the arm moved near a person?
AFiR-Exec · Safety-Envelope Attestation
✓ COVERED
Two robots coordinated a lift. Who decided what?
Agent Coalition Attestation
✓ COVERED
Can the receipt itself be trusted if the robot's software stack is compromised?
HiveSeal™ / Colony — signed at the silicon, USB HSM root
✓ COVERED
Prove the home robot behaved — without handing over bedroom camera footage.
CLOAzK™ zero-knowledge posture · Warden disposition receipts
✓ COVERED
Bill 40,000 RaaS hours across three customers — with proof per metered hour.
SLS Metering · x402 settlement rail · Settle
✓ COVERED
Ship the same fleet into the EU, Texas, and Japan — and prove which rules bound each unit.
Jurisdictional Clearance
✓ COVERED
A human took over mid-task. Exactly when did control transfer?
✓ COVERED
The incident is final — nothing can un-happen. What now?
R3Pv™ — the receipt never over-claims recoverability. Evidence-only, honestly.
9 / 9 · full-stack coverage · all primitives patent pending
The insurer's dashboard · configure a fleet

Underwriters don't insure promises

Nobody writes coverage on a 10,000-unit humanoid fleet backed by self-kept logs. Set the fleet; watch the posture gauge move from "uninsurable narrative" to "provable machine." This dashboard is the conversation with the carrier.

Fleet size (units deployed)500
Operating hours per unit / day16
% of consequential actions receipted40%
Hardware root (HiveSeal™ units)0%
0 /sec
Receipts signed
0 M/mo
Evidence volume
Underwritability
Three buyers · one rail

Who signs the check

The Maker

Shipping thousands of units into other people's buildings. Every unit is a liability node until it can testify for itself. Provable-by-design becomes the spec line competitors don't have.

Hook: the first maker to ship receipts sets the standard the rest must follow.

The Deployer

Warehouses and factories running mixed fleets they didn't build. When the incident review comes, "the vendor's logs say" is not a position. Independent receipts are the deployer's leverage over every vendor.

Hook: one rail across all makes — the deployer's evidence doesn't depend on the maker's cooperation.

The Insurer

The de facto regulator of physical AI. Premiums price uncertainty; receipts remove it. A "provable machine" class of risk is a product a carrier can actually underwrite — and discount.

Hook: the carrier that pilots receipt-based pricing owns the category before actuaries elsewhere wake up.

The quiet pilot · one robot cell · three weeks

Shadow-receipt a single work cell or a ten-unit fleet. Zero changes to the control stack — the sidecar listens, anchors, signs. Ends with one Deployment Evidence Bundle: perception-to-actuation chains, teleop attestations, OTA lineage — every receipt verifiable offline against the Hive public key. The pilot's real product is the document your safety lead forwards.

Same primitives · every vertical

Provable Machines is one Hive vertical. Here's the rest.

The receipt shape that anchors a humanoid's control loop is the same one that anchors a sportsbook's intervention, a bank's dispute, or an AI agent's payment. One primitive set. Many verticals. All verifiable offline against the Hive public key.

Primitive index · click through
AFiR™ AFiR-Stream AFiR-Exec SiGR HiveSeal™ Colony R3Pv™ Protected Flow Human-Origin Attestation Cryptographic AI Receipts Settle x402 Checkout Wallet CLOAzK™ · Warden · Metamorphosis · Safety-Envelope · Coalition · Jurisdictional Clearance · SLS Metering — patent pending
The live rail — verify it now
# the same rail every vertical above uses curl https://receipts.thehiveryiq.com/v1/receipt-relay/health # -> {"status":"ok","signer":"did:hive:hivemorph","algo":"Ed25519"}
Private workspace · not affiliated with any robot manufacturer named or implied · no manufacturer data processed · all demo endpoints are Hive's own · all primitives patent pending · live rail: receipts.thehiveryiq.com