Browser store readiness

Submission packet for local public-alpha review.

Flow Memory browser extensions are prepared for local unpacked QA and reviewer evaluation from GitHub Release artifacts. Current status: not submitted to Chrome Web Store or Microsoft Edge Add-ons, not approved by either store, and not production-ready.

Public alpha boundary

Flow Memory is a local/testnet public alpha for owned AI agents, local memory, and cryptographic receipts. No real funds move, no transactions broadcast, no private keys are required, and contracts are not audited.

Artifacts currently ready

Use these exact artifact paths when preparing Chrome Web Store and Microsoft Edge Add-ons submissions. The extension ZIPs are for local unpacked QA/reviewer use until store review is complete.

Extension ZIPs

release/live/0.1.0/receipted-memory-extension-0.1.0-chrome-edge.zip
release/live/0.1.0/mandate-companion-extension-0.1.0-chrome-edge.zip

Store asset ZIPs

release/live/0.1.0/receipted-memory-store-assets-0.1.0.zip
release/live/0.1.0/mandate-companion-store-assets-0.1.0.zip

Screenshot asset paths under `docs/store-assets/`

Extension	Assets
Receipted Memory	`docs/store-assets/receipted-memory/screenshot-1.png` `docs/store-assets/receipted-memory/screenshot-2.png` `docs/store-assets/receipted-memory/screenshot-3.png` `docs/store-assets/receipted-memory/promo-440x280.png`
Mandate Companion	`docs/store-assets/mandate-companion/screenshot-1.png` `docs/store-assets/mandate-companion/screenshot-2.png` `docs/store-assets/mandate-companion/screenshot-3.png` `docs/store-assets/mandate-companion/promo-440x280.png`

Observed console state on 2026-07-01

Chrome Web Store Developer Dashboard access is available for the Receipted Memory draft. The extension ZIP upload completed, the detailed description was filled from the local listing copy, language was set to English, category was saved as Functionality & UI, and the draft was saved.
Chrome submission is not complete. Store icon, screenshots, promo asset, privacy/support/home URL fields, any privacy questionnaire, and final review submission still need to be completed in the dashboard.
Microsoft Partner Center opened to a signed-in home/workspace view, but no Edge Add-ons product submission flow was visible. Submission needs confirmed Edge Add-ons developer access and workspace setup.
No package publish, payment, Edge submission, or final Chrome review submission was completed during the readiness check.

Submission blockers that require external accounts/review

Chrome Web Store developer account access and listing ownership.
Microsoft Partner Center account access and Edge Add-ons listing ownership.
Store review by Chrome Web Store and Microsoft Edge Add-ons reviewers.
External security review if requested by a store reviewer, partner, enterprise evaluator, or launch policy.

Required claims to avoid

Do not use these claims in listing copy, screenshots, support replies, release notes, ads, or social snippets until the evidence exists.

No Chrome Web Store approved claim before approval.
No Edge Add-ons approved claim before approval.
No production-ready/audited/mainnet/real-funds claim.
No claim that verifier output is legal advice, compliance certification, provider confidentiality, or proof that downstream websites/providers cannot observe user-submitted data.

Reviewer notes for local unpacked QA and offline verifiers

Local unpacked extension path

Download the extension ZIP for the product under review from release/live/0.1.0/.
Unzip locally and load it as an unpacked extension in Chrome or Edge developer mode.
Use non-sensitive demo data only. Do not enter private keys, real funds, recovery secrets, production credentials, or sensitive personal data.
For Mandate Companion, test a local demo origin or non-sensitive site and route only supported actions through the extension executor.
For Receipted Memory, create demo memory fields, prepare a prompt, review it, and manually decide whether to send it to Claude or ChatGPT.

Offline verifier path

Use the bundled offline verifier pages or release verifier artifacts to check exported bundles without a Flow Memory server account.
Verifier results are evidence about signed bytes, hash chains, and local verifier rules; they are not legal, investment, compliance, security, or privacy guarantees.
BYO provider mode can send selected prompts, page context, action data, and API requests to the provider chosen by the reviewer or user.
The browser extensions are available as GitHub Release ZIPs for local unpacked QA/reviewer use; they are not yet approved by Chrome Web Store or Microsoft Edge Add-ons.

Post-submission checklist

After submission, record item IDs, review status, and publish URLs. Update release notes only after approval is actually observed.

Store	Item ID	Review status	Publish URL	Release-note update rule
Chrome Web Store	Record after submission.	Leave blank until a developer-console review status is observed; then copy the exact status.	Record only after Chrome provides a public URL.	Update release notes only after approval is actually observed.
Microsoft Edge Add-ons	Record after submission.	Leave blank until a Partner Center review status is observed; then copy the exact status.	Record only after Microsoft provides a public URL.	Update release notes only after approval is actually observed.