Identity: one capability, one accountable payment

Identity: one capability, one accountable payment A sequence diagram generated by Archify. signed Invoke + action derive required keys anchors + budget + nonce capability + state + proof Allow(debit) or Reject allowed account post-images checked updates staged result enclosing transaction outcome Presenter · originator of Invoke · Sequence participant Presenter originator of Invoke Identity · native handler · Sequence participant Identity native handler Accounts · token-derived state · Sequence participant Accounts token-derived state Cap checker · pure authorization · Sequence participant Cap checker pure authorization Writeback · native executor · Sequence participant Writeback native executor Journal · enclosing transaction · Sequence participant Journal enclosing transaction

All authority state comes from the capability

  • • The handler derives root, ancestor anchors, budget, nonce, vault and receipt keys. The checker validates encoding, delegation, time, scope, proof of possession, replay and budget. Rejection stages no payment.

Payment and accountability share one transaction

  • • An allowed draw stages budget + nonce changes, vault debit, recipient credit and an audit receipt after writable/authority checks. Presenter and executor are distinct; no external tool or automatic bridge action is implied.