Skip to content
Menu ▾
Patent pending

HumanMark · a Regulayer surface

You cannot tell what a person made from what a machine made.

HumanMark records how work is made, as it is made, on the maker's own device, and signs the result. It shows how input entered the artifact and places those observations into one of five descriptive production bands, never a fake percentage. It captures. It does not detect. It does not determine or claim authorship.

Two human acts, not one

Production and review are different questions. How the input entered the work is the first. Did a person check it is the second. HumanMark records the first; the receipt answers the second. Together they are the capability this estate is built on: verifiable production evidence and review.

Detection answers neither. A detector reads finished work, runs a model on it, and returns a probability that is sometimes right. In Stanford research, seven widely used detectors falsely flagged essays by non-native English writers 61.2 per cent of the time. HumanMark is the opposite: it records the creation facts as the work is made and signs them. A record issued at creation, verifiable for as long as the work exists. No after-the-fact estimate, and no false positive on writing a model scores as atypical.

Five bands

Human-authored, human-led, mixed, AI-led, AI-generated. Where the work landed, said in words a court, a regulator or an editor can read, recorded as the work was made, on the device where it was made. The words themselves never leave that device.

Declared

A signed statement of how the work was made, over a name.

Observed

The creation facts recorded at creation: typed live versus pasted, the moment generated text entered. Watched, never guessed.

Present

At the moment of sealing, a named, enrolled person passes a fingerprint or passkey check on their own device, and the seal binds that person, that material and that moment. This is Presence, and it is the difference between a key and a person.

Why now

Article 50 of the EU AI Act applies from 2 August 2026, and its transparency duties carry an exemption for published content that has undergone human review where a named person or organization holds editorial responsibility. That exemption turns on evidence of review. A probability score is not that evidence. A signed record of production evidence and review, issued at creation, is.

Where it belongs

Publishers and platforms

Provenance stated in words, issued at creation, checkable by any reader.

Regulated disclosure

Filings and reports where production evidence and review must be shown, not asserted.

Research and expert work

What the person did and what the tool did, recorded while it happened.

Content operations at scale

The five bands as a standing property of everything you publish.

Deployment

It runs on your machines, and enforcement and evidence signing require no network egress.

Regulayer operates within the customer-controlled environment. Ordinary enforcement and evidence signing do not require network egress, and the underlying work is not sent to Regulayer. Where independent time evidence is used, the underlying content remains within the customer environment.

Every answer your security function will ask for, on one page you can forward

Related capabilities

What do you need to control or prove?

Licensing begins with the problem, not the product.

Describe the system, what it decides, and what it would cost you to be unable to prove it. A written scope follows before any call.

Ways to begin:

hello@regulayer.com