The product is simple on purpose. You write, Humanums records behavioral evidence, you certify the finished document, and you get proof you can attach to the work wherever it lives.
In practice, Humanums records writing behavior while the draft is created, certifies the finished version, and generates a badge plus verification page that can be shared with readers, clients, or editors.
Write your draft while Humanums records behavioral signals like pause timing, revisions, and paste patterns.
Run certification when the document is ready. The system scores the writing session and issues a signed certificate if the evidence is strong enough.
Embed the badge or share the verification link so clients, editors, or readers can inspect the proof themselves.
As the document is written, Humanums captures how the text is produced rather than only what the final text looks like. That includes timing patterns, revision behavior, session structure, and paste usage.
The point is to build evidence during authorship, not attempt to infer authorship after the fact.
When the draft is ready, the writer runs certification. Humanums evaluates the collected signals, generates a confidence score, and assigns a badge level when the evidence passes threshold.
The system also hashes the finished content so the proof stays attached to the exact certified version.
After certification, the writer gets an embeddable badge, a certificate ID, and a public verification page. The badge works on blogs, portfolios, newsletters, and other public surfaces.
The verification page gives other people a place to inspect the certificate instead of relying on a detector screenshot or a self-reported claim.
They see a badge they can click, a certificate ID, and a public verification page with the score and writing-session details behind the certification.
The document does not get a certificate, and the writer can review which signals came in weak rather than receiving a vague detector-style accusation.
The strongest workflow is to write in Humanums first, certify the finished version, and then publish the badge or verification link wherever the content is distributed.
Create a draft, run certification, and inspect the badge and verification page the way your readers will.