Students and writers
Show that your thinking came first.
Keep your reading notes, ideas, and outlines as your own dated sources, with any AI help labeled as AI's. When someone asks how you got there, you have more than your memory.
For teams building with AI
Add an origin layer to your product.
Your users think with your model. Capture what they expressed before the model responds, keep every generation attributable, and let a reviewer see what a person actually accepted or changed.
Why now
Marking AI output is half the record.
Rules such as the EU AI Act's transparency obligations, and standards such as C2PA, focus on marking content that a machine generated or edited. That matters. It does not, by itself, show what a person contributed.
If your product sits between people and a model, you are in a position to keep the human side of the record too: the input, the response, and the decision, captured before the model speaks.
Origo does not make a product compliant with any regulation, and it does not claim conformance with the C2PA specification.
File-level credentials compared with the origin layer
| File-level credentials (C2PA and similar) | The origin layer (Origo) | |
|---|---|---|
| The question it answers | What touched this asset? | What did this person express before AI answered? |
| What it describes | A finished file: an image, video, audio clip, or document, with its edit history. | A person's own words and how they developed: notes, transcripts, responses, decisions. |
| Where AI appears | As a tool that generated or edited the file. | As separate, labeled output, linked to the exact version of the words it used. |
| When it is recorded | When the file is created or edited. | Before the model speaks. Saving your words does not depend on any model. |
The two are complementary. Origo does not replace Content Credentials and does not claim conformance with the C2PA specification.
What an origin layer means
Four design commitments.
These are the commitments behind Chronicle, Origo's record, and the starting point for a pilot conversation.
- 01
Source-first capture
The user's input is saved as an immutable source record, with its capture time, before the model responds. Saving it does not depend on a model provider.
- 02
Derivations, not overwrites
Model output is stored as a separate derived record with the model identifier and links to the exact source versions it used. Corrections create new versions and keep the old ones.
- 03
Human response on the record
What the person accepted, changed, or rejected is recorded as their own contribution, so a reviewer can see the human decision rather than infer it. The full sequence is in development.
- 04
Inspectable integrity evidence
A per-workspace hash chain with a root witnessed outside Origo, and open, published evidence formats, so later changes to a covered record can be detected.
Where it fits
Products where authorship matters.
- AI writing and editing tools
- Research assistants and knowledge tools
- Education and learning platforms
- Decision-support and agent workflows
- Publishing and editorial systems that ask about AI use
Pilots are scoped design partnerships. A production SDK or API, commercial terms, and service guarantees are not available today.
Take the next step
Talk with us about a pilot.
Tell us what your product does, where people and models meet in it, and what a reviewer needs to see.
Opens an email to begin@helloorigo.com.
Also built for
The same record, for individuals.
Researchers, journalists, consultants, freelancers
Keep your judgment on the record.
Use AI for research and drafting while your own analysis, sources, and decisions stay distinct, so you can show clients and editors what was yours.