Proposal: GNAP as a coordination substrate for multi-agent Agents workflows
The Agents framework (aiwaves-cn) is a notable contribution — the temporal memory design with long/short-term memory and the SOP (Standard Operating Procedure) controller for multi-agent workflows is thoughtful. The natural extension: making these multi-agent SOPs durable and auditable across sessions.
GNAP (Git-Native Agent Protocol) provides this: a git repo as a persistent task board with board/todo/ → board/doing/ → board/done/. Tasks persist across restarts, coordination is auditable, no infrastructure beyond git.
Applied to Agents' SOP-based multi-agent system:
The Agents framework uses Controllers and pipelines to define multi-agent SOPs. GNAP could serve as the external task store:
board/todo/customer-inquiry-8472.md ← SOP router creates
board/doing/customer-inquiry-8472.md ← Customer service agent claims
board/done/customer-inquiry-8472.md ← Resolution committed
board/todo/escalate-case-8472.md ← Created if unresolved
This maps naturally to the demo customer service SOP in the Agents framework — GNAP externalizes the SOP state so it's visible and recoverable. The long/short-term memory per agent could reference GNAP task IDs to maintain context across handoffs.
Spec: https://github.com/farol-team/gnap
Proposal: GNAP as a coordination substrate for multi-agent Agents workflows
The Agents framework (aiwaves-cn) is a notable contribution — the temporal memory design with long/short-term memory and the SOP (Standard Operating Procedure) controller for multi-agent workflows is thoughtful. The natural extension: making these multi-agent SOPs durable and auditable across sessions.
GNAP (Git-Native Agent Protocol) provides this: a git repo as a persistent task board with
board/todo/→board/doing/→board/done/. Tasks persist across restarts, coordination is auditable, no infrastructure beyond git.Applied to Agents' SOP-based multi-agent system:
The Agents framework uses Controllers and pipelines to define multi-agent SOPs. GNAP could serve as the external task store:
This maps naturally to the demo customer service SOP in the Agents framework — GNAP externalizes the SOP state so it's visible and recoverable. The long/short-term memory per agent could reference GNAP task IDs to maintain context across handoffs.
Spec: https://github.com/farol-team/gnap