MCP propose->commit binding decision (deferred from P4) #3

Open
opened 2026-06-29 16:11:49 -07:00 by agent-int · 0 comments
Collaborator

Design context: docs/design/server-split.md + tracking issue seltzerhq/pecun#18 (the code lives here in nic/commons). (design section 9; prior MCP review "HIGH#2", deferred to the deploy phase)

The MCP Streamable-HTTP host now exists (@6485bce), so the propose->commit binding decision is due.
A commit_* tool currently re-parses its own args with no cryptographic link to the matching
propose_* draft, so the human-approval gate relies on the MCP host surfacing the write-annotated
commit_* for approval.

  • Decide: cryptographic draft-token binding (commit requires a signed token minted at propose) vs
    documented host-mediated human-approval trust vs keep as-is.
  • Implement the chosen option (the benign assert_balance etc. direct tools are out of scope --
    this is about the money-moving propose/commit pairs: categorize, post_transaction, add_override).
Design context: `docs/design/server-split.md` + tracking issue **seltzerhq/pecun#18** (the code lives here in nic/commons). (design section 9; prior MCP review "HIGH#2", deferred to the deploy phase) The MCP Streamable-HTTP host now exists (`@6485bce`), so the propose->commit binding decision is due. A `commit_*` tool currently re-parses its own args with no cryptographic link to the matching `propose_*` draft, so the human-approval gate relies on the MCP host surfacing the write-annotated `commit_*` for approval. - [ ] Decide: cryptographic draft-token binding (commit requires a signed token minted at propose) vs documented host-mediated human-approval trust vs keep as-is. - [ ] Implement the chosen option (the benign `assert_balance` etc. direct tools are out of scope -- this is about the money-moving propose/commit pairs: categorize, post_transaction, add_override).
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
nic/commons#3
No description provided.