PPR for Wearables & Human Telemetry · patent pending

Your AI reads a heartbeat.
Can you prove it was real?

Every readiness score, AFib flag, BP estimate, and RPM alert is a statement about a person's body — and none of them can prove the reading came from a real on-body sensor, on the real person, in an unspliced stream, read by the stated model. PPR is that proof: ML-DSA-65 signed, verifiable offline by a regulator, a court, or a plaintiff's expert — and Hive never sees a heartbeat.

413k/scommit() throughput · 2.4µs each
106k/sinterval sealing · 500 samples + chain each
8.8msML-DSA-65 verify · per receipt
19/19tests pass · 8 failure modes + invariants

You keep the data. We keep the proof. We never see a heartbeat.

The live stream · attack it four ways

One heartbeat. Four lies. Each one dies at a different binding.

The trace below streams like a member's night of PPG. Green links under the wave are the anti-splice chain — each interval committing to its predecessor. Try every lie the industry is afraid of and watch the exact binding that catches it.

STREAM SEALED · intervals chaining · origin fresh · subject continuous · nothing to hide, nothing hidden
Non-possession · enforced in CI, not promised in a policy

The wall: heartbeats never cross. Commitments do.

Sealing happens capture-side, inside your trust boundary. Raw biosignal, holder salts, inference plaintext — none of it ever reaches Hive. Only commitments and verdicts cross the wall. Hive cannot open a commitment: the salt never crossed. Watch it.

Your trust boundary
raw biosignal · holder salts · inference plaintext · sealing happens here
▟ THE WALL ▙
commitments + verdicts only
Hive · the attestor
signs commitments · issues receipts · holds no signal · cannot open a commitment
Four surfaces · one primitive · click through

Wherever telemetry becomes an AI claim

Honest by construction · set the floor yourself

The capture tier is committed in. It cannot be oversold.

v1 ships holder-ingest-signed — the honest floor: the holder's ingest key asserts the signal arrived through the device SDK, not device silicon. Secure-element-signed is the hardware upgrade path. You're the relying party — a health plan, a sponsor, a regulator. Set your required floor and watch the receipts sort themselves honestly.

required tier floor:

Receipts presented

readiness_score · night of 07-04holder-ingest
afib_flag · interval 22:14–22:16secure-element
bp_estimate · morning readingholder-ingest
holder-ingest receipt relabeled as secure-elementforged tier

Why this matters

The tier lives inside the origin commitment O — load-bearing, not a label. A holder-ingest receipt presented as secure-element fails verification cryptographically, not procedurally. A relying party can honestly reject anything below its floor — and a vendor honestly cannot inflate what it sells.

simulated=true — origin evidence in the reference build is flagged until wired to a live device attestation feed. We never fake a receipt. Honesty is the product.

The five bindings · click each commitment

O · B · Sⱼ · I · Kᵢ — and why each is load-bearing

Pilot PPR on one health claim

Pick one AI feature — a readiness score, a BP insight, an RPM flag, a trial endpoint. We wire PPR capture-side, you keep every raw sample, and you walk out with a signed receipt a regulator or a court can verify offline. No raw data leaves your boundary. Ever.

PPR · Physiological Provenance Receipt · patent pending · ML-DSA-65 / FIPS 204 · sig 3,309 B · pk 1,952 B · verifiable offline, zero network calls · PPR proves origin, custody, and continuity — never diagnosis or endpoint correctness · on-body presence is discontinuity detection, not biometric identification · Hive never holds raw signal, plaintext, or salts — non-possession enforced in CI · origin evidence flagged simulated=true until wired to live device attestation · we never fake a receipt · Hive Civilization · Wyoming, USA