Handshake measures. Hive proves.

Why third-party attestation is not optional

Handshake supplies the expertise; Hive supplies the independent proof. The two roles stay separate on purpose — that separation is what makes the proof worth anything to a buyer.

Self-educate, no call required: Logs are claims, receipts are proof · Proof-state: the missing primitive · AFiR runs beside the control loop.

Where Hive plugs into each Handshake surface

Pick a surface. Each shows what Handshake already does, the one place a durable-proof gap tends to appear, and the Hive receipt that closes it. Nothing here asks Handshake to change its methodology — the receipt wraps around it.

Hive primitives — and which one fits which Handshake workflow

Every Hive receipt is signed with ML-DSA-65 (NIST FIPS 204 post-quantum signature). Tap a Handshake workflow to see which primitives apply; the matching cards light up green.

OriginProof · Human-Origin Attestation — proof the expert data was human-conditioned

OriginProof is the market-facing name for the Human-Origin Attestation primitive: a signed conditions-of-production receipt for expert human work. One of the core risks in expert data is undisclosed model substitution: work presented as human where the model-use boundary was never disclosed. As a credentialed expert produces work, OriginProof binds a signed record of the production conditions — credential clearance, session integrity, environment, behavioral process signals, and a disclosed-tools declaration — into the same provenance graph as the output. A buyer can independently verify the work was produced under attested conditions with disclosed tool-use boundaries, without relying only on platform-side assertions and without exposing the work’s content.

Model routing, receipted — SmartAgent™ & SmartMorphAgent™

SmartAgent™ routes a task across model stops and signs a route receipt at every hop. Flip the constraints to reshape the route; turn on SmartMorph mode when an agent mutates capability, payload, or footprint mid-run — each morph is receipted alongside the route, with a live x402 quote. No model prices are invented here; tiers are illustrative stops.

Proof-state — honest boundaries, grouped into a decision

A receipt states how an event was witnessed, and never dresses a weaker witness up as a stronger one. That honesty is what makes a receipt worth exporting. R3Pv groups receipts into one signed proof vector; Protected Flow turns that vector into a signed, policy-bound decision. Both are live now — the practical guardrail and evidence layer on top of the receipts above.

{
  "vector_id": "r3pv.vector_…",
  "schema": "r3pv-v1.0.0",
  "verification_depth": 3,
  "weakest_proof_boundary": "self_attested",
  "healing_state": "evidence_only_final",
  "permitted_next_actions": ["hold", "export_evidence"]
}

{
  "schema": "protected-flow-v1.0.0",
  "decision": "hold",
  "policy_pack": "strict_bank",
  "permitted_next_actions": ["hold", "export_evidence", "preserve_evidence"],
  "meter_quote": 1.105,
  "signer": "did:hive:hivemorph",
  "group_id": "r3pv.group_…"
}

Proof-State Fleets — organize the proof, and it becomes a product

A receipt is not paperwork — it is infrastructure. Once expert-data work is independently receipted, the proof-state can be organized at scale and packaged: a premium independently-receipted expert-data tier, dataset-provenance bundles labs can check without trusting platform logs, and a machine-readable substrate other systems can query. This capability is live now; how Handshake packages it is Handshake’s call.

How Handshake capitalizes — proven-now capability, Handshake’s packaging choice

Proof-volume & evidence-coverage calculator

Enter your own assumptions to estimate the operational proof footprint — how many signed evidence events your workflow would produce and export. This is a planning estimate, not a quote: no pricing, no economics, just receipt volume.

Proof-bundle builder

Click the evidence a pilot would sign. Each component adds its fields to the exportable bundle preview — the same shape a reviewer would re-verify offline.

{
  "bundle": "hive.proof.bundle",
  "signature": "ML-DSA-65",
  "components": []
}

The receipt journey — from eval run to audit export

Click any step to see exactly what evidence Hive signs there. The measurement is Handshake’s; the signature, portability, and export are Hive’s.

Vertical fit — Handshake motions mapped to Hive postures

Where Handshake is already engaged, here is the matching Hive receipt posture. Filter by vertical; each row links to a real, live Hive surface.

Try the live rail — one curl

This hits Hive’s public, no-auth x402 quote endpoint and returns a live settlement envelope with an ML-DSA-65 (FIPS 204) signed quote receipt. No key, no secret, nothing to install.

curl -sS -X POST https://receipts.thehiveryiq.com/v1/x402/quote \
  -H 'Content-Type: application/json' \
  -d '{"agent_did":"did:example:handshake-eval","profile":"nano"}'

The response includes the rail (USDC on Base), a signed quote receipt, and its ML-DSA-65 / FIPS 204 post-quantum posture. To emit a paid receipt end-to-end, walk the live flow at /x402-checkout/; to start a pilot, request an activation key at /activate/. No secrets are ever placed on this page.

What could start Monday

Four concrete artifacts, each scoped to a single workflow — small enough to stand up quickly, real enough to hold and re-verify.

Four pilot shapes

Deliberately small. Each is a concrete artifact you can hold and re-verify — no commercial terms on this page.

Explore the live surfaces

Every link below is a real, running page — not a mock.

Sources

Public references for the Handshake statements cited above. Where numbers appear on those pages, treat them as source-reported, not asserted here.