Regulayer Enterprise licensing
Main site The engine By problem What is licensed Deployment Assurance AI audit trail Human authorship and review The record format What it proves Security review Begin with the problem

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. Five plain bands, from human-authored to AI-generated, never a fake percentage. It captures. It does not detect.

Two human acts, not one

Authorship and review are different questions. Was this made by a person is the first. Did a person check it is the second. HumanMark answers the first; the receipt answers the second. Together they are the capability this estate is built on: human authorship 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 guess, and no false alarm on writing that does not fit a model's idea of human.

Five plain 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 organisation holds editorial responsibility. That exemption turns on evidence of review. A probability score is not that evidence. A signed record of authorship 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 authorship 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 nothing of the work leaves the building.

The kernel binds the loopback interface and refuses any client that is not local. The signing key is generated on your own machine on first run and never leaves it. In the default mode there is no outbound call of any kind. Where independent time is required, a single cryptographic digest goes to a public timestamp authority, never the file and never its contents. The source ships readable, so your own security function can satisfy itself line by line.

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

The estate

Part of the filed estate: eighteen patent filings and a PCT. Patent pending across the estate.

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:

A scoped pilot, inside your estate, on your machines. An architecture briefing, for your security function, one hour. The diligence pack: the record format and the estate, in writing. The problem itself, in your own words.

hello@regulayer.com