Two-Way Tasks Contract (2026-09-26)

Surfaces: Asana + Google Tasks only. Beads is the local truth; the mesh syncs both directions. One shared noise definition (WIREBOT-ARCH).

Direction 1: user creates → mesh (fast)

  • A task created on either surface appears in the mesh on the next poll (Asana webhook where configured, otherwise poll; Google poll with updatedMin).
  • Required inbound fields: title + source id + updated stamp. Missing stamps lose conflicts — reject, don't guess.
  • User edits (rename, notes, due, complete, reopen, delete, assignee) replay as mesh events with source receipts, per the Feb audit matrix.

Direction 2: agent creates → user sees (fast)

  • Agent-created beads sync out on the next poll cycle with the mesh id stored beside the source id (no duplicates on re-sync).
  • Completions, blocks, and at-risk states surface on both surfaces, not just the routine digest.
  • Suppressed noise (auto-repaired drift, heartbeats, FYI receipts) never creates surface tasks.

Conflict rule (both directions, both surfaces)

Last-write-wins on the source updated stamp. The loser is kept as a sync receipt on the mesh event — visible, never silently dropped.

Shared progress cards

Project progress cards are execution views linked to existing work, not new task authority. Asana and Google Tasks render the same card through parent/child tasks or a bounded checklist summary; Discord, Pi, Wirebot App, and Flow Mesh web render their native equivalent. Visibility policy prevents internal agent steps from becoming owner tasks. See the progress-card contract in 2026-09-26-FLOW-MESH-MASTER-GAP-PLAN.md.

Out of scope

Linear, Jira, and every other task tracker. New surface adapters need an owner decision, not a drive-by task integration.

Generated from the Flow Mesh repository by scripts/build-docs-site.sh. If a page is wrong here, the file it was rendered from is wrong.