Wallet-Native Review And Signing
TIDBIT-share-WEAVE is a zero-trust document workspace for review, signing, sharing, evidence export, and version lineage with wallet-native identity and optional external anchoring.
Upload, review, sign, share, version, and export evidence from one workspace with wallet-native access.
Open from wallet share, email link, SMS link, or public signing route, then review before signing.
Keep timestamps, actors, signatures, versions, share routes, and evidence together in one custody ledger.
The production app already combines ML-KEM-oriented envelope custody with browser-local ML-DSA key generation and signing, so users can keep PQ signing keys in their own browser while the backend preserves the evidence trail.
Each file is tied to hashes, custody events, signer metadata, share activity, session-aware actor history, version lineage, evidence bundle data, and optional external anchoring so the record stays portable and tamper-evident over time.
Full browser-side PQ encryption for document contents is not the default web path yet, and organization-managed PQ key custody, recovery, and crypto-agility are still ahead. Today the strongest shipped PQ user path is local ML-DSA signing plus the backend custody and evidence model.
ML-KEM Envelope Model
Active application storage stays practical, while document custody uses a post-quantum envelope model so the file is handled as protected evidence instead of a trusted plain blob in storage.
ML-DSA Signatures
Human wallet flows still support EVM and Solana, and the web app now also supports browser-local ML-DSA key generation, backup, import, and signing for users who want a stronger post-quantum signature path.
Evidence And Anchoring
Evidence bundles, event-chain metadata, bundle signatures, hashes, and optional Arweave anchoring make the record verifiable beyond the immediate app session or any single storage provider.
For Crypto Teams
Keep MetaMask and Phantom in the core flow for upload, sharing, recipient access, and signatures.
For Security Workflows
Track versions, signatures, access events, and share routes in a verifiable record instead of scattered logs.
For AI-Agent Teams
Prepare the same document workflow for human and agent actions, with exportable history and policy direction.
Create the document record and start its custody history.
Preview the file, verify context, and log access before signing.
Route by wallet, email, phone, or public signing link.
Support EVM, Solana, policy-gated guest attestation, and browser-local ML-DSA signing paths.
Preserve evidence, version lineage, and anchoring references.
Enter through MetaMask or Phantom and bind the session to a real wallet identity.
Store the document, capture its hash, start custody events, and optionally anchor evidence later.
Route by wallet, email, phone, or public signing link depending on the recipient and workflow.
Preview before signing, then verify signer identity with EVM, Solana, guest, or ML-DSA paths.
Preserve the version lineage, custody history, share state, and signature evidence as one package.
Agent Identity
Agents should not act as anonymous helpers. They need an identity, policy scope, and attributable event trail.
Agent Review
Agents can inspect a file, summarize it, suggest edits, or create a new version without silently overwriting the record.
Agent Sign
Agents can sign only if allowed by the document policy, and their actions stay exportable for audit and review.
Register an agent identity, issue its token, define whether it can review, version, or sign, then route it into the same custody ledger as human actors.
Evidence exports can include which agent reviewed or signed, when it acted, which policy path was used, and what document state it touched.
The point is not “AI in the workflow.” The point is making AI actions attributable, reviewable, and non-silent.
Teams handling vendor approvals, grants, research records, and governance artifacts.
Teams that need attributable review, routing, and evidence around agent participation.
Teams that need more than a signed PDF and care about version lineage, export, and auditability.
Get Started
Use the live login entry to connect a wallet, upload a file, share it, review it, and inspect the custody history.
Documentation
Architecture, user guide, code walkthrough, custody concepts, and audit notes are all documented in the GitHub docs folder.
Source And Audit
The GitHub repo includes workflow files, audit reports, dependency notes, and the current implementation state.
TIDBIT-share-WEAVE is meant to bridge document workflow, wallet identity, evidence export, optional Arweave anchoring, and auditable AI participation.
This section is where product tour videos, signer walkthroughs, and AI-agent demos should live once you publish Loom or YouTube links.
Login, upload a file, share it to another wallet or public link, review it, sign it, then export the evidence package.
Demo Slot 1
Use this slot for a Loom or YouTube video showing login, upload, review, sign, share, and evidence export.
Demo Slot 2
Use this slot to show wallet routing, public link signing, and how shared activity appears in the custody ledger.
Demo Slot 3
Use this slot to show how agents review, create versions, sign by policy, and export attributable evidence.