What it does
MORTEM streams real cardiac telemetry, an implanted pacemaker and an Apple Watch, into a live dashboard: an ECG canvas, heart-rate variability metrics, a Poincaré plot, and a voice layer. The signal is then reduced to an attestation and anchored, which is what makes it an identity primitive rather than a health widget.
It is the biological axis of Proof of Coherence, and deliberately the lowest-weighted one at 10 percent.
In the code
// The heartbeat overlay token is a read-only public credential: it can
// display a rate and nothing else. Anything that could reveal clinical
// data stays server side. A public liveness signal should not require
// trusting the page with anything worth stealing.
const HR_TOKEN = window.__HR_PUBLIC_TOKEN__ || null;From the public overlay. Scoping a credential so narrowly that publishing it is uninteresting is usually better than protecting a broad one.
How this differs from the ordinary version
It is a liveness signal, not a health record
The design goal is proving a specific living person is behind an action at a specific moment. It deliberately does not become a clinical dataset, the attestation is a hash, and the raw stream is not what gets anchored.
The hardware is the point
A wearable can be left on a desk. A pacemaker cannot. Using an implanted device as the source raises the cost of forging the signal from trivial to surgical, which is the only reason a biological axis is worth including at all.
In the field
Where liveness matters
High-value authorizations, a wire release, a chain-of-custody handoff, a legal attestation, are exactly the places where "someone who has the key" and "the person" have diverged in every major fraud of the last decade.
Questions
- Is clinical data published?
- No. The public overlay exposes a rate only. What gets anchored is an attestation hash, not the underlying stream.