Flow Mesh ↔ Wirebot Owner-Routine Architecture (2026-09-26)
Current state (verified)
/data/wirebot/bin/flowmesh-apiexists on OVH: read-only (health,status,providers,list). Wirebot can read mesh state.- Authority boundaries (Aug runbook 25, still valid): Focusa governs workflow/approval/evidence; Flow Mesh executes and syncs providers; Wirebot reads through the wrapper and runs explicitly authorized ops.
Gap: the routine needs signal, not raw lists
The owner's signal-vs-noise review needs a shaped feed, not task list dumps. Missing pieces:
- Digest feed — per routine run: completed since last run, blocked items needing the owner, items at risk (stale, conflicted), and noise explicitly suppressed (routine heartbeats, auto-repaired drift, FYI sync receipts). New wrapper verb:
digest --since <ts>. - Owner actions back into the mesh — approve, complete, delegate, reassign. The wrapper is read-only today; add authorized write verbs (
complete,delegate,note) gated per call by the routine's existing operator authority. No ambient write access. - Noise rules live in the mesh, not the routine — suppression criteria (auto-repaired, duplicate, sub-threshold) are mesh config so every surface (routine, Asana, Google Tasks) shares one definition.
- Native project progress cards — Wirebot App consumes the versioned progress list/get/SSE API and renders the same card visible in Pi, Discord, Asana, Google Tasks, and Flow Mesh web. It does not parse shell output or maintain a separate checklist. See the progress-card contract in
2026-09-26-FLOW-MESH-MASTER-GAP-PLAN.md.
Non-goals (unchanged)
No second task authority beside beads; no token copying between products; no routine-side mesh writes outside the authorized verbs.