Share without SaaS: publish the open document to IPFS / Fileverse

[criptogus]

Community suggestion: bridge to decentralized suites like Fileverse (dDocs/dSheets — AGPL-3.0, local-first web, IPFS sync, e2e encryption).

Proposal

An agent tool + UI action, "Share without SaaS": publish the currently open document so it can be shared by link with no centralized service.

• v1 — IPFS file publish: upload the saved file (optionally encrypted with a user key first) to IPFS via a configurable gateway/pinning endpoint; return the CID and a shareable link in the chat. Opt-in per document, nothing automatic.
• v2 — Fileverse-native export: dDocs/dSheets are open source; map our block/workbook model to their document format so the shared artifact opens natively at ddocs.new / dsheets.new instead of as a file download.

Constraints

• Publishing is irreversible in practice (content-addressed, cacheable) — the UI must say so plainly and require explicit confirmation; the agent tool must never publish without the user asking.
• Encryption before upload by default; plaintext publish is a deliberate second confirmation.
• Keep it a thin, optional layer: the local file remains the source of truth, per the roadmap's local-first principle.

Part of the "off SaaS" track (see the exodus-skill and sync-layer issues).