Thanks for testing BloomMD.

BloomMD starts in M1 as a macOS desktop beta. It works directly on a folder on your disk — without an account, cloud or network. This is the path we recommend for the beta: no invitation is needed and your files stay on your computer.

Why the warning appears: The macOS build is ad-hoc signed, but not yet Developer ID-signed or notarized. The final Apple signature is waiting for the Apple Developer account approval. If the Gatekeeper workaround is inconvenient, use the browser demo.

1. 1. Start without an account. Open the demo, paste your Markdown and view the map. Nothing is saved or uploaded.
2. 2. Start from a template. The templates are real Markdown files: software architecture, research, startup operations and content strategy.
3. 3. Work with your own files. The desktop app opens a folder on your disk. Change the structure, save it and continue in Git or Obsidian — all locally, with no account.
4. 4. Try a knowledge bundle. Install the optional BloomMD command-line tool locally; it works without a model or network. bloommd-wiki init ./wiki creates an OKF-v0.2 bundle. status and lint show drift and trust levels.

• Desktop app — the recommended path. Runs locally on your files, detects external changes and opens .md files by double-click.
• Web app — the same interface in the browser, for invited cloud beta testers.
• OKF / LLM Wiki — bundles in Open Knowledge Format v0.2 with trust signals and the suggest → approve → apply workflow.
• Obsidian compatibility — real local notes are visualized as a map; full plugin beta distribution follows after M1.
• Collaboration — available to invited cloud testers. The two-person and WebApp + MacApp guide is in the collaboration documentation.

• Mobile Obsidian. The touch matrix on real devices has not run. The plugin is intentionally marked desktop-only.
• Paid plans. No prices and no payment data. Checkout is closed server-side.
• Public access. The cloud app is invitation-only. Demo and templates are open.
• Autonomous agents. The wiki workflow requires review. Nothing is written without named approval.

The beta runs on an early private instance. Local sync load tests have run and platform restore and target-environment smoke checks are documented, but M1 is intentionally released cautiously. There is no recovery guarantee.

• No credentials, keys or tokens.
• No personal data belonging to third parties.
• Nothing whose loss would cause a problem.

For real work: use the desktop app locally. It needs no cloud access and uploads nothing.

Report bugs and requests after login through the feedback button in the app. A screenshot is required so we can triage UI, folder and sync problems faster.

Helpful in a report: what you expected, what happened, your browser or Obsidian version, a screenshot and — if a file was rendered incorrectly — a minimal Markdown example. Please do not upload real content, credentials or third-party data; a reduced example is always enough.

If the app itself is unreachable, reply to your beta invitation email or write to feedback@bloommd.io. GitHub is our internal triage target, not a normal feedback channel for testers.

You do not need to report these points — they are already on the list:

• New files from other participants appear only after a reload.
• The desktop app's auto-reconnect to the remote server is unreliable.
• The first invitation wave remains manually gated until legal approval, the tester group and the delivery log are complete.
• There is not yet a diff view for resolving conflicts.