Flow Memory Public Alpha

Flow Memory Public Alpha

Flow Memory is now available as a local/testnet public alpha for owned AI agents, local memory, browser receipts, offline verification, and public-alpha marketplace records.

Try it

• Launch hub: https://flowmemoryai.github.io/flow-memory/
• Start guide: https://flowmemoryai.github.io/flow-memory/start.html
• Marketplace public alpha: https://flowmemoryai.github.io/flow-memory/marketplace.html
• Project scope dashboard: https://flowmemoryai.github.io/flow-memory/project-scope-dashboard.html
• Browser store readiness: https://flowmemoryai.github.io/flow-memory/browser-store-submission.html
• Browser alpha ZIPs and verifier artifacts: https://github.com/FlowmemoryAI/flow-memory/releases/tag/v0.1.0-browser-launch
• Python: flow-memory==0.2.0 pending TestPyPI/PyPI authentication; local build and twine check passed.
• Node receipts: @flowmemory/receipts@0.1.0 pending npm authentication; tests, pack dry-run, and publish dry-run passed.

What is ready

• Local CLI install doctor and quick local agent path.
• Receipted Memory and Mandate Companion extension ZIPs for local unpacked QA/reviewer workflows.
• Receipted Memory Chrome Web Store draft has the package ZIP uploaded and core listing fields saved; final review submission is still pending remaining assets/URLs/questionnaire completion.
• Offline verifier pages and verifier tarballs.
• Local public-alpha marketplace read/list/quote/order-record surface and hardened local marketplace API lifecycle.
• @flowmemory/receipts research-grade receipt library source and package metadata.
• Public start guide, scope dashboard, store-readiness checklist, marketplace page, and launch hub.

Boundaries

• Public alpha only; not production-certified.
• Not audited cryptography, not constant-time, not FHE, not a TEE.
• No Chrome Web Store / Edge Add-ons approval yet.
• No real funds, no private keys, no transaction broadcast, no mainnet writes.
• Marketplace settlement, trading, provider payment, custody, and mainnet writes remain disabled until audits and external reviews are complete.

Current external blockers

• PyPI/TestPyPI publication requires the account owner to provide a Twine API token.
• npm publication requires npm adduser / authenticated npm CLI access.
• Chrome Web Store final review submission still needs remaining Receipted Memory listing assets/URLs/questionnaire completion in the dashboard.
• Edge Add-ons submission needs confirmed Partner Center Edge Add-ons workspace access.