HumanMark · a Regulayer surface · Voice and performance

A signed record of the take, made at the moment it is captured.

HumanMark records the facts of a captured performance as it is produced, on the device that captures it, and signs them. The record can be carried with the work or associated with it in your own systems, and any party can verify it without Regulayer.

It captures. It does not detect.

At capture

The strongest provenance starts at capture.

a cryptographic digest of the take exactly as captured
the duration of the take and the time of capture
the capture path: recorded live through the device’s own input, distinguished from a finished file handed to the system
the deployment that issued the record, and the signing key that issued it
where Presence is enrolled, a fingerprint or passkey check on the maker’s own device at the moment of sealing, binding the take to the enrolled credential used

The audio stays where it was captured. The digest and the recorded facts are what enter the record, which is why this works inside a studio, a newsroom or a customer environment that does not release material.

Claim discipline

Four questions, kept apart, so the record still means something later.

Established by the record

this take existed, in exactly this form, at the recorded time
it was captured live through the capture path, rather than supplied as a finished file
the record was issued by a named deployment and signed by its key
where Presence is enrolled, that the take is bound to the enrolled credential used at sealing
the take is unaltered since: change one sample and the digest no longer matches

Established elsewhere, and bound in when you hold it

Identity. Who the person is comes from your enrolment. The record binds to it; it does not assert it.
Authorship. Who wrote the words or the music is a separate fact, referenced by the record rather than concluded by it.
Ownership and rights. Held in your rights system. The record can be associated with the work there.
Originality. A question about the work, not about the capture.

Keeping those claims separate makes the record precise and independently testable later.

See the capture

Record a few seconds and watch the facts a record is built from.

Say a sentence, or sing a line.

Specimen · computed locally · unsigned

Captured	live, just now
Length
Take digest
Capture path	live input

Computed in this browser and not signed. An issued record is signed by the deployment that captured the take, and verifies against that deployment’s public key.

The audio stays in the browser. Only the digest is computed here, and nothing is uploaded.

Voice and performance workflows

The record is created in the capture path, not bolted on at the end.

Recording and production

The take is sealed as it is captured in the session, before it moves into the editing environment, the asset store or the delivery pipeline.

Rights and catalogue

Each take carries a record that can be associated with the work in the rights system, so provenance survives the move from session to catalogue and from catalogue to licensee.

News and documentary

An interview or a piece of field audio carries a record of its own capture, checkable by anyone downstream of the newsroom, including a party that does not trust the newsroom.

Platforms and distribution

The record can be checked at ingest, so a platform acts on provenance it verified itself rather than on a claim typed into a metadata field.

Verification

Anyone can check it. Nobody has to ask Regulayer.

Verification needs the record and the public key. No account, no call home, and it works with the network switched off.
Regulayer publishes the format and the verifier. The check itself is arithmetic that any competent party can run, and can reimplement.
If the take is edited, re-encoded or regenerated, the digest no longer matches and the check fails plainly rather than quietly.
A transcode is a different file with a different digest. The record covers the take as captured; a derived master is associated with that record rather than covered by it.

Verify a record, free · The open verifier

How it is licensed

Verification is open. Issuing and embedding are licensed.

Anyone can verify a record without charge. A licence covers issuing records and embedding capture into a system that other people rely on: platforms and distribution networks, labels and rights administrators, media and broadcast organisations, capture hardware and production software vendors, and infrastructure providers who want provenance created inside their own path rather than around it.

Records are issued under the customer’s own deployment and the customer’s own key. Two deployment shapes, one invariant:

Hosted, content-freeNo install. Only the digest and the recorded facts ever leave the device. The material itself does not.

Sealed, on-premiseRuns inside the customer environment, with no network egress required for capture, sealing or verification.

In both, the material stays with the customer. Verification does not depend on a live Regulayer service.

Scope is written before any call.

The wider layer

Voice is one capture surface.

HumanMark is the evidence surface for human participation and provenance. Different surfaces record different facts: authored work records composition, reported across five descriptive production bands in words rather than a percentage; voice and performance record the facts of capture.

Alongside it: the Regulayer Receipt records that a person reviewed the work. Drift Control checks a consequential action against current human authority. The Witness records which human decision governed at the time.

HumanMark · HumanMark for the enterprise