Methods
Protecting Intellectual Work - Provenance & OTS
Digital work is easiest to protect while it is still local, still yours, and still traceable.
The problem usually does not begin with a formal dispute. It begins earlier, when a file is copied, a proposal is reused, a codebase is modified, a message is forwarded, or a draft passes through enough tools and edits that its original decision trail quietly disappears.
By the time someone has to explain what existed, when it existed, and whether it has changed, the evidence should already exist.
That is the point of provenance.
Provenance is not drama. It is not suspicion. It is not a legal argument by itself.
It is a record of state.
For digital work, that record can be simple: the exact file, its hash, its size, its modification time, the machine and user that recorded it, and a sidecar file that preserves those details in a form that can be checked later.
A filename is not proof. A folder date is weak. A screenshot may help, but it rarely answers the precise question. Memory is not evidence.
The useful question is narrower:
What exact content existed at this point in time?
A provenance record helps answer that question.
If the file changes, the hash changes. If the file remains unchanged, the same hash can be produced again. That gives the work an evidential floor: not a claim that someone must simply trust, but a checkable record that can be compared later.
OpenTimestamps adds the time anchor.
With OpenTimestamps, the private work itself does not need to be published. The timestamp is attached to a fingerprint of the work, not to the work’s private content. That matters. A creator, student, developer, researcher, or small business owner may need evidence that something existed without exposing the actual material before they are ready to share it.
This is especially relevant now because intellectual work moves through more layers than it used to.
A single piece of work may pass through local folders, cloud storage, AI systems, editors, exports, commits, deployments, chat logs, attachments, and public platforms. Each layer can be useful. Each layer can also blur origin if meaningful states are never recorded.
That does not mean every file needs a provenance record.
It means the person doing the work should decide deliberately which states matter.
A first draft of a business proposal may matter. A codebase before handoff may matter. A set of research notes before submission may matter. A client deliverable before delivery may matter. A local tool before publication may matter. A message, specification, design, or dataset may matter if it carries authorship, timing, or responsibility.
Signalane’s first public tool is a portable provenance script.
It is designed for a practical purpose: record the state of selected files or folders, generate SHA-256 hashes, write sidecar provenance records, and prepare material that can be anchored with OpenTimestamps.
The provenance script and launch helper are available in the Signalane GitHub repository.
The tool is released under the MIT License. Reuse, modification, redistribution, or commercial use must follow the terms of that license.
This is not a full legal system, not a replacement for contracts, not a replacement for Git, and not professional legal advice.
It is a working evidence habit.
That distinction matters.
Many people only think about evidence after something has gone wrong. By then, the work may already have moved through too many hands, folders, exports, tools, or rewritten versions. The original state may still be true, but truth is harder to use when it was never recorded.
A provenance script does not make a claim stronger by making it louder.
It makes the record cleaner.
For students, this can protect project work, research drafts, and original technical material. For developers, it can preserve the state of code before handoff, refactor, publication, or external review. For creators and small businesses, it can record proposals, concepts, documents, and assets before they leave the local machine.
The principle is simple:
Record meaningful states before they are shared, modified, published, delivered, or disputed.
That does not turn creation into bureaucracy. It gives digital work a stronger starting point.
Provenance records the state.
OpenTimestamps anchors the time.
Together, they help keep intellectual work attached to its origin.