What is the difference between a reply, a proposal, and execution?

The answer may be useful while the action still needs policy checks, human review, idempotency, or fresh host validation. Keeping the proposal separate gives the host a place to accept, reject, expire, and reconcile the outcome.

Why this goes wrong

A single agent loop can hide authority inside implementation. Tool access becomes permission, a successful HTTP response becomes business truth, and retries can repeat a mutation without a stable identity.

How Tonetify handles it

Govern creates a bounded proposal with evidence. The host reviews and executes it under its own policy. A lifecycle callback records what happened, while Relay only transports the selected conversation reply.

Before you implement

01Persist the proposal before delivery
02Keep execution credentials in the host
03Use stable idempotency identities
04Record acceptance, execution, and outcome separately

Choose the next step

Put this question back into your product flow. Confirm the business boundary first, then choose the infrastructure layer you need.

01 See the industry scenario See how the same failure separates host authority from Tonetify responsibilities. 02 Read the technical contract Inspect how the Reply Contract rejects unsafe answers. 03 Discuss an integration Bring one real conversation or workflow. We will identify the smallest useful integration surface.