Platform
Existing AI governance tools govern models. Editorrah governs output: who made the work, how much of it was machine assisted, whether its facts are real, and which human is responsible.
01The engine
The writing editor is one capture point among several. The product is the record.
Capture points
Provenance engine
The record
02The record
Editorrah Authorship record
Sample
Process timeline
4 sessions. 6 h 12 min active. 212 revisions.
Verification
| Authorship match | Consistent with 6 verified prior works | Verified |
|---|---|---|
| AI assistance | 2 segments detected, both declared | Declared |
| Fact verification | 14 of 15 references verified at source | 1 unverifiable |
| Human sign-off | J. Doe, Course instructor | Signed |
Sample record. Illustrative data, not a real submission.
Process timelineHow the work was drafted, revised, and assembled.
Authorship matchStylometric consistency against the author's verified history.
AI assistanceDeclared use alongside detected machine-assisted segments.
Fact verificationEach claim, citation, and reference checked against its source.
Human sign-offThe responsible person, named and timestamped.
SignatureCryptographic seal, tamper evident, exportable.
A court, a journal, a regulator, or an employer can act on this. A score, they cannot.
03The API
A dashboard is bought once and reviewed at renewal. An endpoint is written into a workflow and called every time that workflow runs.
The public API is not yet open. Request access and tell us what you need to verify.
04Integrations
| Integration | Record | Status |
|---|---|---|
| The Editorrah editor | Authorship Verification | Live |
| The Editorrah editor | Research Authorship | Live |
| LMS: Canvas, Moodle, Blackboard | Authorship Verification | Roadmap |
| Submission systems: Editorial Manager, ScholarOne, eJournalPress, OJS | Manuscript Verification | Roadmap |
| E-filing submission step and practice management | Filing Verification | Roadmap |
| Document systems, agent platforms, workflow tools | AI-Use Attestation | Roadmap |
05Why it compounds
01
Every endpoint call returns verified work.
02
Verification accuracy rises with volume.
03
Accuracy is the only durable moat.
04
The best record wins the next integration.
Detection accuracy is a feature. A closed loop that keeps improving it is infrastructure.
06Security and data
| Encryption in transit and at rest | Data is encrypted between your systems and ours, and in the database where it is stored. |
|---|---|
| Signed, tamper-evident records | Records are cryptographically signed. The underlying event log is hash chained, so a later alteration is evident on verification. |