GNAP: git-native task persistence for Upsonic agent teams
Hi Upsonic team
Upsonic's model for fintech/enterprise agents with reliability-first design is compelling. I wanted to raise a coordination protocol that might fit your reliability goals well.
GNAP (Git-Native Agent Protocol) turns a git repository into a zero-server coordination layer for AI agent teams. Four JSON files define the team, tasks, messages, and protocol version. Any agent that can git pull/push participates.
Why GNAP fits Upsonic's reliability focus:
| Concern | Typical approach | GNAP |
|---|---|---|
| Task durability | Database / Redis | Git commits |
| Audit trail | Custom logging | Full git history |
| Rollback | Custom | git revert |
| Human override | Dashboard | Edit JSON + commit |
| Multi-agent coordination | RPC / message bus | Git push/pull |
For fintech agents where every action needs to be traceable and reversible, git provides all of that natively. A GNAP-backed task queue would give Upsonic's agents immutable audit trails at zero infrastructure cost.
Concrete integration point: Upsonic's Task objects could serialize to GNAP task JSON before execution, and the result written back on completion — making every agent run independently resumable.
Would love to hear if Upsonic has thought about git-based audit trails or if there are plans for a persistence layer.
Protocol spec + RFC: https://github.com/farol-team/gnap
Source: Upsonic/Upsonic