Flow Mesh — Canonical Docs Index
This file is the single map of all Flow Mesh documentation. Start here. Rule: product truth lives in this repo's docs/. Deployment runbooks live in the server master plan (linked below, not copied).
Published subset: https://flowme.sh/docs/ carries the documents named in docs/public.manifest — install, CLI, API, providers, security, interface, licensing. Everything else in this folder is internal. The manifest is an allowlist because most of these files name unfinished work, unbuilt endpoints, or decisions we reversed; publishing the folder would publish all of that. scripts/build-docs-site.sh renders the allowlist and scripts/publish-docs-site.sh publishes it and verifies the public URLs, including that the internal documents stay unreachable.
docs.flowme.sh does not exist: creating that hostname is a DNS change that needs owner authorization, so the docs live under the existing domain instead.
Product docs (this folder)
| Doc | Role | Status |
|---|---|---|
SCOPE.md |
Engineering spec (deterministic) | Current spec backbone |
CLI.md |
CLI specification, including mesh onboard flags, JSON report, exit codes, and recovery verbs |
Current 2026-10-27 |
API.md |
API reference | Reference |
COMMERCIAL.md |
Pricing, tiers, GTM plan | Current 2026-09-26 (trial + launch deals + closed source) |
DECISIONS.md |
Design decisions E17–E18.6 (onboarding ownership, authority mode vs credential type, eleven projection surfaces, executable join atoms, silent env-file outage) | Current 2026-10-27 |
DISTRO.md |
Distribution grid (flowme.sh tarball) | Current 2026-09-26 |
VIBE-CODER-GTM.md |
Vibe-coder go-to-market stories | Current 2026-09-26 (trial wording) |
SECURITY.md |
Security model | Reference; re-verify against trial/lock changes |
INTELLIGENCE.md |
Intelligence layer | Reference (largest doc; split if it grows) |
SYNC_GRID.md |
Sync grid design | Reference |
AUTO-DECOMPOSE.md |
Asana → Beads sub-task pipeline | Reference; feeds the two-way-tasks track |
AGENT-NATIVE.md |
Agent-native integration strategy | Reference; feeds the Wirebot track |
DECOMPOSITION.md |
Full bead decomposition | Reference; cross-check against live beads before trusting counts |
HOOKS.md |
Hook system design | Reference |
BOOTSTRAP.md |
Intelligence-first setup | Reference; feeds the onboarding-simplification track |
UI.md |
UI design system | Reference; feeds the interface track |
PROVIDERS.md |
How to write a provider | Reference |
INFRA.md |
Infrastructure | Reference |
CLOUD.md |
Managed SaaS (unbuilt) | Future-gated, not a promise |
SYNC_STATUS.md |
Sync audit snapshot, Feb 2026 | Historical evidence only (Asana sync proof; re-verify in the Asana track) |
TRAJECTORY.md |
Pre-Wirebot plans re-aimed at the owner routine | Current 2026-09-26 |
WIREBOT-ARCH.md |
Mesh feeds the owner routine; authorized ops back | Current 2026-09-26 |
GOOGLE-TASKS.md |
Tasks API mapping, poll-sync design, and the operator runbook for bringing Google Tasks live (cascade, consent boundary, failure signatures) | Current 2026-10-27 |
TWO-WAY-TASKS.md |
User↔mesh contract, conflict rule | Current 2026-09-26 |
BEADS-DIFF.md |
Legacy bd vs br rust impact + close-policy watch | Current 2026-09-26 |
EXTENSION-LINK.md |
Workforce extension contract (endpoints + auth) | Current 2026-09-26 |
2026-09-26-FLOW-MESH-MASTER-GAP-PLAN.md |
Sole decomposition authority: all gaps, shared fabric, generic API/CLI, adapters, SendyKit, progress cards, acceptance, safety, and implementation order | Current 2026-09-26 |
2026-09-27-FLOW-MESH-PROVIDER-SETUP-CAPABILITY-MATRIX.md |
Documented provider setup automation and external-authority boundaries | Current |
2026-09-27-FLOW-MESH-PORTABLE-AUTHORITY-BOOTSTRAP.md |
Deployment-neutral direct, broker, and workload authority contract | Current |
ONBOARDING-ARCH.md |
One-command setup design, the implemented mesh onboard surface with recovery verbs, and its executable proof |
Current 2026-10-27 |
Staleness rule: anything untouched since Feb 2026 is reference, not proof. Re-verify against running code before quoting it to the owner.
Deployment runbooks (server master plan, not copied here)
- Wirebot↔Flow Mesh connection recovery:
runbooks/25-wirebot-flowmesh-full-connection-recovery-runbook.md - Product/Focusa/UIAI architecture draft:
drafts/24-flow-mesh-product-focusa-uiai-callgraph-architecture-spec.md - Deployment proof:
proof/flow-mesh/
Program tracks (live beads, not docs)
Trajectory, Wirebot architecture, Google Tasks, Asana hardening, two-way tasks, beads-vs-br, interface pass, GitHub extension link, gap review, and onboarding simplification are tracked as beads in this repo — check status there, not in prose docs.