Notary gives your work provenance you can prove.
Create local proofs in Bookcicle web projects for drafts, uploads, history snapshots, exports, and collaborator handoffs. In native Studio, you can create a manuscript proof that preserves an exact content state and its authorship history at a meaningful milestone. Bookcicle can then attest those local receipts in the cloud and optionally anchor signatures publicly for a stronger timestamp over time.
Notary produces cryptographic receipts that bind content bytes to timestamps and signers. This creates verifiable provenance for milestones, outputs, AI transforms, and contributor handoffs.
Multiple humans and AI systems can touch the same artifact. Notary helps create verifiable checkpoints around authorship, handoffs, and revisions without relying on screenshots or informal history.
Every service can export a .bkclp proof capsule. Anyone can verify later using the capsule plus the content bytes (embedded or provided).
Where Notary fits across Bookcicle
Notary is not a separate product you have to manage. It is an evidence layer across web projects, native Studio, project history, collaboration, downloads, AI-assisted work, and final delivery.
Andrew drafts and revises The Fragment Murder in native Studio. At an important milestone, he creates a manuscript proof that preserves the exact content state and its authorship history. Notary attaches the receipt metadata to the project history.
For higher-value milestones, Bookcicle can attest the local receipt in the cloud and optionally anchor the signature publicly. If a dispute ever occurs, he can export a .bkclp capsule and share it for independent verification.
An author sends a manuscript section to a freelance editor for revisions. Before and after the handoff, each party creates their own proof records. The author can prove what was delivered, while the editor can prove what was received, changed, and returned.
This creates clean provenance around revisions without depending on screenshots, email timestamps alone, or disputed version histories. Each side has independently verifiable receipts for their role in the workflow.
A creator drafts source material locally, then runs AI-based transforms such as restructuring, language cleanup, or guided expansion. Notary can create proof points around the original source, the transformed output, and the delivery milestone.
When later asked how the work was produced, the creator has a more defensible provenance trail: what existed first, what was transformed, and what was ultimately delivered or published.
From manuscript to verifiable proof
Notary creates the evidence locally first. Your device signs a fingerprint of the exact content, then you decide whether to keep the proof local, add Bookcicle evidence, or share it for verification.
Create a device key
Notary generates a signing-key pair associated with this browser profile or native Studio installation. The private key stays local.
Fingerprint the content
The exact manuscript or file bytes are converted locally into a unique cryptographic fingerprint. The fingerprint reveals no manuscript text.
Sign the local proof
The private key signs a proof record that binds the fingerprint to its public key and context. Any later content change produces a different fingerprint.
Strengthen the evidence
Bookcicle can attest the local receipt, and a public anchor can timestamp its signature. The manuscript itself is not published.
Share and verify
Export a .bkclp capsule. A recipient can compare the exact content bytes and independently verify the proof and its signatures.
Private by default. Creating a local proof does not require publishing the manuscript. Source bytes are included in a shared capsule only when you choose to embed them.
