Text version of the summary. Status labels: shipped means verified in the current product; in development means code exists but is not released or proven; planned means designed but not built; hypothesis means an assumption not yet tested; historical means true once and no longer current.
Technical summary
How Inkfold is built
A web application and service on the FusionLayer engine; the local parts are in development.
shipped Web application
React in the browser: chat with your own model keys, import of exported chats, a memory library with revisions and a receipt under each answer.
shipped Service and engine
A standalone Node.js service with Fastify. It calls the FusionLayer engine, which owns sign-in and memory, only over signed, encrypted calls.
in development Local runtime
A development preview: watches supported tool files, answers recall over the Model Context Protocol, and writes briefs in Smart mode only.
shipped Storage modes
Smart: Inkfold can read it. Private: encrypted in the browser. Incognito: nothing kept. Any mode: a remote model gets the text a request needs.
in development Desktop client
Electron, Windows only, unsigned tester build 0.1.0: identity with a 24-word recovery phrase and an on-device index. Vaults and sync not built.
planned Release gates
Still to pass: one two-tool journey on a clean machine and a signed Windows release. No independent security assessment of the whole product yet.
Facts as of 24 September 2026. Status labels: shipped, in development, planned, hypothesis.