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

The capability, defined

Human authorship and review. Two acts, not one.

Was this made by a person, and did a person check it? Two different questions, two different records. Language that names only one gives away the other half, and most of the market is selling one half or the other.

The two acts

Authorship: was this made by a person?

Answered by HumanMark, on five plain bands from human-authored to AI-generated, recorded as the work is made, on the device where it is made. Never a probability, never a percentage.

Review: did a person check it, and which parts?

Answered by the receipt: a signed, dated record of what a named individual verified, sealed at the moment of the decision, checkable by anyone afterwards.

An authorship certificate with no review is a publishing credential. A review log with no authorship is a signature on an unexamined origin. Regulated work increasingly requires both: the EU AI Act's human oversight duties turn on a person, its transparency exemption for published content turns on review with named editorial responsibility, and every standing order in the legal market asks some version of both questions at once.

Why detectors answer neither

A detector reads finished work and returns a probability that it was machine-written. It was not present at creation, so it guesses. It says nothing about review, because review is an act, not a texture. And in Stanford research its false-positive rate on non-native English writers reached 61.2 per cent, which makes its guess an accusation rather than evidence.

The alternative is capture, not detection: record the creation facts as the work is made, and record the review as it happens. Both records signed, both checkable by anyone holding them, both stating their assurance level on their face.

Where it is built

Authorship and review run through the whole estate: HumanMark and Presence for the first act, The Witness for the second, and the engine underneath both. The attorney product, the Regulayer Receipt, is the same capability packaged for a court-facing duty.

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