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 schema
A receipt includes its schema identifier, version number, version hash, timestamp, source hash, tool version, local verification state, proof state, and an explicit limitation notice. Copy and download happen only when the user presses the corresponding control. Receipt verification establishes byte-level consistency, not 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
A proof anchor commits one selected version hash to an explicitly configured BOT Chain contract. Sourvia reads the already-authorized account, checks the chain again, previews the business ID, hash, wallet, contract, calldata, zero-value amount, and gas estimate, then requires a second confirmation. A valid wallet-returned transaction hash creates a pending record. RPC receipts alone move it to confirmed or failed; lookup errors produce a recoverable state. Without a verified contract and audited function selector, the feature remains Local Demo / Unavailable.
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 hash can prove that the same payload was presented again, but it cannot prove who created it, whether cited claims are accurate, whether a timestamp is independently trusted, or whether content was copied.
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.