Everyday use¶

There is very little to say here, which is the point.

You open your usual writing app — iA Writer, Scrivener, Word, a plain text editor, whatever you have always used — and work exactly as you do now. Save when you would have saved. Walk away when you would have walked away. BlindProof runs quietly in the background, notices each save, takes its fingerprint, and files it away privately on your own computer. Nothing about your rhythm needs to change.

Once a day, without being asked, BlindProof takes a summary of that day's saves to the public registrar. You will not feel it happen. If your computer is asleep or offline at the moment, it will happen the next time BlindProof can reach the internet. No saves are lost.

What the dashboard shows¶

A small window on your computer, and a webpage if you prefer a browser, show the basics:

• How many saves BlindProof has seen.
• The time of your most recent save.
• The time of your most recent sync to the registrar.
• A chart of your word count over time.

None of this shows your words. It is metadata only — the shape of your work, not its content. You can keep the window open, leave it closed, or ignore it entirely. It makes no difference to the evidence being gathered.

When to produce a proof bundle¶

Only when you actually need one — typically when delivering a manuscript to your publisher, or at a point in a contract that calls for a dated version. You are not meant to generate bundles constantly. A single proof bundle, generated on the day of delivery, proves everything about everything that came before it.

If you need to produce more than one — say, a bundle for the full manuscript and another for a later revision — that is fine. Each bundle stands alone.

When to stop¶

You do not need to "finish" with BlindProof. If you move on to a second book, point it at a new folder and carry on. Old manuscripts stay in the record unchanged. Nothing is ever retroactively altered; nothing can be.