Keyboard shortcuts

Press ← or → to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

Part V — What survives, and where to go next

Tauros models financial intent: invoices proposed by agents, sealed as immutable revisions and decided by human approvers. It records public receiving addresses and IBANs as payment destinations, but at the pinned revision it issues nothing, pays nothing and reconciles nothing. Payments and reconciliation are roadmap items.

What should survive an implementation change?

The payment rail may change: a bank transfer, a card network, a stablecoin transfer, an HTTP-native payment protocol or a payment platform built for agents. Financial intent must remain distinct from financial authority. Whichever rail eventually settles the money, these properties should hold before it is ever called:

BoundaryProperty that must surviveWhere Part V teaches it
IdentityHumans and agents are different kinds of actor, and an agent credential can never act as an approver.Lesson 1
PolicyThe same policy applies to every interface: UI, REST and AI tools.Lesson 2, Lesson 14
EvidenceWhat is proposed is an immutable revision with a content hash, never "whatever the record contains now".Lesson 5
PolicyLifecycle transitions are constrained by a state machine no caller can bypass by writing a field.Lesson 6
DurabilityA retried proposal does not create a second one.Lesson 7
AuthorityA human approves an exact revision and hash, and there is at most one decision per revision.Lesson 8, Lesson 9
CapabilityThe AI tool surface is reviewed and contains no decision tools.Lesson 13

Settlement is the boundary Tauros does not cross. A future settlement step would need its own answers: it must execute only the approved revision, survive retries without paying twice, and leave evidence that links the payment back to the approval. The design exercise in Part VI asks you to design exactly that path. Agent payment protocols and platforms (some listed below) address parts of it. They do not decide who may approve the payment in your domain.

Continue beyond this laboratory

You now understand this architectural problem. These are strong implementations, standards or ecosystems to explore next. They are a short, deliberate selection; Where CognoKratos fits explains how they were chosen and what the labels mean.

  • x402 open standard / infrastructure
    An open protocol for HTTP-native payments, stewarded by the x402 Foundation. It shows what an agent-initiated settlement step can look like, and where the question "who authorised this payment?" still has to be answered upstream.
  • Agent Payments Protocol (AP2) open standard / infrastructure
    A pre-1.0 protocol that carries a user's authorisation of an agent's purchase as signed mandates. Compare a mandate with Tauros's exact-payload approval.
  • Nevermined ecosystem-specific
    A platform for metering, access control and payments between agents. Useful for seeing how plans, budgets and settlement rails are combined in practice.

These address settlement and payment mechanics. Tauros's subject is the boundary in front of them, and none of them removes it.