Fission is not just one product and not just a generic local-first company. Its own organization materials frame it as building three explicit primitive layers — identity, data, and compute — through the UCAN, WNFS, and IPVM working groups.
The most important corpus insight is the decomposition itself. Fission keeps delegated authority, encrypted state, and execution/runtime concerns legible instead of collapsing them into one hosted app platform.
The ODD SDK README shows how this thesis becomes an application stack: user accounts come from browser crypto or wallet plugins, authorization comes from UCAN, filesystem state comes from WNFS/IPLD, and recovery/linking flows are pushed into reusable SDK surfaces rather than improvised per app.
The ODD capability-request flow is especially important because it exposes a concrete local-first permission model: apps request scoped access, a separate lobby mediates approval, encrypted UCANs and filesystem secrets are returned, and the app builds a session from those artifacts.
The whitepaper abstract makes Fission useful as more than a product catalog entry. It presents WebNative as an architectural response to cloud complexity and platform control, with user-owned identity/data and executable code portable across machines.
The wallet-auth plugin is a valuable crypto-native signal because it shows the stack can use blockchain wallets as the root key material for accessing encrypted personal state, not only for payments or chain transactions.
Specific source signals worth retaining
The org-profile README is the strongest source for the top-level identity / data / compute decomposition and for the placement of UCAN, WNFS, and IPVM as working-group layers.
The ODD SDK README is the strongest source for operational details: auth paths, account-linking, capability-request UX, WNFS-backed filesystem access, recovery kits, and wallet-based identity extensions.
The whitepaper README is the strongest concise source for the broader WebNative thesis: secure-by-default edge execution, user ownership of identity/data, and removal of deployment as a separate concern.
The wallet-auth README is the strongest source for Fission’s bridge into wallet-centric crypto UX.
Why this entry belongs in the corpus
It gives the corpus a higher-level organizational comparison point for several already-useful lower-layer primitives, especially UCAN and WNFS.
It helps separate protocol design, SDK defaults, recovery/linking policy, and developer-distribution strategy from the lower-layer claims of user-owned data or non-custodial auth.
The durable insight is that local-first systems often have at least four distinct control planes: root identity, delegated authority, encrypted state, and recovery/runtime defaults. Fission makes those seams visible enough to be analytically valuable.