We measure your process.
We don’t judge your authorship.

Every editing operation on the platform is recorded with:

• Origin — who triggered it (you, AI, an automated job) and which specific AI suggestion generated the edit
• Granular category — initial generation, refinement, reworking, original composition, or suggestion rejection
• Timestamp — the exact moment of the edit, server time
• AI decisions — suggestions accepted, rejected, or reworked after acceptance
• Time investment — time between editing sessions, number of revisits per scene

From this data, we compute per scene: percentage reworked (lexical distance between the current state and the first AI version), dominant origin (original composition, refined from AI, reworked from AI, pure AI), temporal patterns. All recorded immutably in the project’s hash chain.

No biometric data. None of:

• The individual content of keystrokes
• Typing cadence or neurological patterns
• Audio, video, webcam or microphone data
• Location or device fingerprinting beyond a standard IP

Everything Telos knows comes from operations you already trigger naturally as you write. No invisible instrumentation.

Levenshtein distance (edit distance) between the scene’s current state and the first AI-generated version, normalized by the larger of the two. Open implementation in src/lib/utils/levenshtein.ts.

A heuristic threshold of 30% separates refined from AI from reworked from AI. It’s a number chosen through internal experimentation, not regulatory authority. It can be recalibrated as a public corpus of AI-assisted writing evolves.

When the system opens, you’ll be able to export a “Creative Process Record” in PDF/A format at any time. It contains:

• An integrity summary with the SHA-256 hash of the project’s operation chain
• Per scene: ops, decisions, time, % reworked, dominant origin
• A conservative technical statement (not a legal one)
• Optionally, an RFC 3161 TimeStampResponse issued by FreeTSA (University of Vienna) — technically attesting the PDF’s existence at that moment

The PDF does not declare authorship. It presents facts. Whoever judges still judges: lawyer, judge, copyright office, festival juror. Telos just hands you the notebook.

The Creative Process Record PDF does not constitute:

• A legal declaration of authorship under any legislation
• An electronic document equivalent to an ICP-Brasil signature (MP 2.200-2/2001) — FreeTSA is academic, not a regulatory certificate authority
• A certificate of copyright, literary material, or moral rights
• An AI detector — Telos does not try to “guess” whether others used AI; it only records what happened in here

For full ICP-Brasil legal force, take the generated PDF to a digital notary and re-notarize it with an ICP certificate. Telos serves as baseline auditable material.

Every AI-assisted writing tool will eventually face the same question: “how do you prove they’re the author?”. Those without a credible answer will be barred from festivals, refused at copyright offices, rejected by studios.

Telos doesn’t wait for the backlash. It builds the answer before the question dominates the industry. Not as a legal ceremony, but as the author’s daily tool: you see your process in real time, refine where you want, record evidence automatically.

Every scene you open carries its notebook built in. When they need to judge, you have a way to tell the story.

The full ADR is public in docs/adr/0016-provenance-processo-criativo.md in the repository. Key points:

• Granularity per scene, not per token. Token-level requires a complex ProseMirror plugin, marginal value.
• No emotional labels (L0–L4, etc.). Only a factual numeric score + a neutral descriptor. Avoids shaming AI use.
• No keystroke biometrics. LGPD Art. 11, marginal value.
• No ZK proofs in V1. Over-engineering, negligible audience.
• No ICP-Brasil in V1. Cost + complexity. FreeTSA covers baseline auditable material.