Problem
Creative work rarely arrives fully formed, yet most publishing surfaces preserve only the final output. Notes, citations, and version boundaries become scattered or disappear. Sourvia gives writers a compact local record of how a draft changed and what informed it, without turning authorship into a prediction score.
Principles
Local by default. Explicit over automatic. Verifiable data over unverifiable claims. Wallet connection and every value-bearing action remain separate. States must describe what actually happened, including rejection, failure, or an action that was prepared but never submitted.
Local architecture
The workspace runs in the browser. Draft text, source entries, snapshots, and receipts are stored in localStorage under a versioned schema. SHA-256 uses the browser Web Crypto API. The production site has no draft upload endpoint, cloud synchronization layer, account database, or background submission process.
Draft and source model
A draft contains a title and body. Counts are derived locally. Each source holds a title, HTTP(S) URL, author or publisher, access date, and optional note. The ledger validates required fields and URL shape but does not fetch, endorse, archive, or independently verify external material.
Version lifecycle
Saving a version freezes the current title, body, source list, timestamp, and version number. Sourvia first hashes the canonical source list, then includes that digest in the version payload before calculating a SHA-256 version hash. Recalculation checks local payload integrity. Editing later does not rewrite existing versions.
Receipt schemas
The local version receipt is metadata only: schema, version number, version hash, timestamp, source hash, tool version and local/proof states. It does not include the complete body or source list and cannot independently reconstruct them. The separate final provenance receipt uses sourvia.final-provenance-receipt/v1: chain ID, stable document ID, source batch ID, exact chain revision/content hash, source-set hash/count and the canonical publication declaration/hash. Its exact compact UTF-8 JSON is both the downloadable file and SHA-256 preimage, without formatting spaces or a trailing newline. Neither receipt establishes identity or legal ownership.
Wallet identity
Wallet connection requests only the user-selected public address and active chain ID. It does not sign a message, approve an asset, transfer value, or submit a proof. Proof submission is a separate workspace action. The active chain is compared with BOT Chain chain ID 677 before any transaction can be prepared or submitted.
Proof lifecycle
Four roles commit different objects: the source role commits SHA-256 of the ordered canonical source list; revisions commit the selected version hash; publication commits a distinct sourvia.publication-channel/v1 declaration; the final receipt links the exact source, revision and channel. A channel declaration includes document ID, revision, content hash, declaration type, trimmed label and normalized HTTP(S) URL. URLs are not fetched; synthetic QA expressly makes no external-publication claim, while a writer declaration is not independent verification. Keep one document ID and append V01 then V02 with the exact previous chain hash; local V02 cannot become chain revision 1. Publication and final-receipt preparation verify the actual selected on-chain content, source and channel dependencies. Each operation separately shows its fixed address, method, calldata, zero BOT value and maximum gas; an explicit second confirmation opens the wallet. A returned hash remains pending until canonical event/storage verification. Missing or paused roles never fall back to a legacy contract.
Threats
Local data may be lost when browser storage is cleared, damaged, or unavailable. Anyone with device or profile access may see locally stored drafts. A root, hash, or receipt can support byte-level integrity and association checks, but it cannot prove who created the content, whether sources or cited claims are genuine, whether text is original, whether copyright is owned, whether a publication channel is authentic, or whether a timestamp is independently trusted.
Limitations
Sourvia is not an AI-content detector, plagiarism detector, copyright registry, legal opinion, originality oracle, cloud backup, collaborative editor, identity assurance service, or security audit. It does not decide whether text was written by a person or a system and does not guarantee copyright ownership.
Receipt history
Submitted proof records remain in a browser-local index and can be searched by business ID, proof hash, wallet, contract, or transaction hash. Confirmed receipts show block number and block time returned by the wallet RPC, with direct BOT Chain Explorer links. Sourvia does not invent missing receipts, transaction hashes, or deployment claims.
Disclaimers
Use Sourvia as an organizational and integrity tool, not as evidence of legal authorship or exclusive rights. External links and wallet software are controlled by their respective providers. Digital assets and optional network actions can involve loss or fees. Review all details before any future submission.