Trust is expensive. Proof isn’t.
BitGraph is useful wherever order matters but the only evidence of that order belongs to whoever holds the files. A digital file has no inherent place in a sequence: its metadata is editable, its timestamp is asserted, and a copy is indistinguishable from the original. A hash can show that two files are identical. On its own it says nothing about order.
A BitGraph gives a file a position. The slot is reserved from hardware entropy before the file's hash is known, the hash is bound to that slot inside a measured boundary, and the sequence is anchored to a public timeline nobody involved controls.
Only the hash of a file is committed. The file itself is never handed to the protocol, so material that cannot be disclosed can still be recorded. The record shows that some exact bits took a position, not what they were.
Two conditions
Recording a BitGraph makes sense where both hold.
The trust gap is frequent and expensive. Someone pays repeatedly, in staff time or in liability, to re-establish something that was settled once already. A problem that comes up once a year and is closed by one email does not need a protocol.
Someone stands behind the artifact. Where an authority issues documents, a BitGraph keeps what it issued distinguishable from what merely resembles it. Where nobody issues anything, as with drafts and prior art, the same record defends a position against a later challenge. Neither protects the truth of what was recorded, only the ability to keep standing behind it.
The subjects
Every entry has the same shape: who is protecting something, what fails today, and what a BitGraph changes.
Photography and photojournalism
Nothing in a photograph's file says which version is the one the photographer delivered. Metadata is editable, and a crop or a re-encode produces different bytes, so anything bound to an earlier version stops matching the file in hand.
What a BitGraph changes. A BitGraph stays external to the image. The image's exact bytes are bound to a position reserved before those bytes were known, so a photographer can show that this version, exactly as delivered, held that position. It sits alongside Content Credentials rather than replacing them: the manifest describes the image's path, the BitGraph records the position this exact version took.
Periodic reporting and attestations
A reserve report or a compliance statement is issued, then measured against events that come after it. When the two disagree, the question becomes whether the copy produced today is what was actually filed, and the only archive belongs to the party being questioned.
What a BitGraph changes. Each report takes the next position in a sequence, and that position is fixed in a public timeline the issuer does not control. A rewritten report no longer matches the position the original occupied. Where the workflow requires one recorded entry per reporting period, an omitted report becomes visible too.
Clinical records and chart entries
Malpractice and consent disputes often turn on when a note entered the chart rather than on what it says. Record systems do keep audit trails, but they are maintained by the same organization whose care is in question, which is the position a provider is least able to argue from.
What a BitGraph changes. A note takes a position in a sequence when it is written, and that position is fixed in a public timeline the provider does not control. An entry added or revised after an event cannot occupy the earlier position. Only the hash is committed, so nothing in the chart is disclosed in order to record it.
Evidence and chain of custody
Custody disputes are usually about order rather than content: which file existed before which, and whether an item entered the record before or after a claim was made. A file's own timestamp is asserted by whoever holds the file, and system clocks are adjustable.
What a BitGraph changes. Ordering does not depend on any clock. A position exists before the file that occupies it, so a later file cannot be inserted at an earlier point, and each anchor fixes the order of everything committed before it. Time is subjective. The order is not.
Issued documents and credentials
What an authority issues is valuable only while it can be told apart from what merely looks like it. Today that distinction usually depends on calling the issuer back, which does not scale, or on visual security features, which are designed to frustrate reproduction rather than to be checked cryptographically.
What a BitGraph changes. Every issued document takes a position in the authority's own sequence at the moment it is issued. A holder presents the document with its proof, and the position can be checked without a fresh lookup against the issuer's records. The organization paying to record the document is the same one whose credibility the record protects.
Instrument and field data
Readings are trusted because of the process that produced them, and that trust does not travel outside the organization that ran the process. Once data leaves the instrument, a downstream reader cannot tell whether readings were added later, removed, or reordered.
What a BitGraph changes. Each reading, batch, or acquisition session takes a position in the instrument's sequence. A later insertion cannot occupy an earlier position, so the record has an order that someone who was not present can check. Where the expected readings are defined by an instrument counter, a schedule, or a batch manifest, an omitted reading becomes visible too.
Drafts, designs and prior art
Showing that you had something in a particular form at a particular stage normally means producing your own files and asking to be believed, which is precisely the evidence an opponent will dispute.
What a BitGraph changes. Recording a draft as it is made gives those exact bytes a position that cannot be created later. Revisions take later positions, so the development history itself becomes the evidence.
The edge of the claim
Every case above rests on one narrow claim: these exact bytes occupied this position in this sequence, and the position was fixed before the anchor that follows it. A reader tends to assume three neighboring claims. None of them follow.
Truth. A recorded document can be wrong in exactly the form it was recorded.
Authorship. A BitGraph attests the boundary that committed the file's hash, not the person who made the file.
First creation. The same bytes may have existed elsewhere beforehand. What is fixed is the position they took here.
What BitGraph is not →Applying it
Recording a file needs no integration. The home page hashes the file locally and returns a portable proof without uploading the file itself. Everything past that, issuing in volume or recording from inside your own systems, is covered in the integration guide.