Reference architecture

The event-to-interaction loop

Activity, Govern, and Relay can form one system without becoming one authority. The host remains the composition root.

The complete three-module diagram is a reference composition for a production pilot integration. It does not represent a customer deployment or a self-service setup.

Product event
→ Activity: ordered projection
→ Host: fresh truth revalidation
→ Govern: bounded proposal
→ Host: review and execution
→ Relay: reliable follow-up
→ Next product event

Why the modules belong together

They sit between real product events, AI-assisted proposals, and user-facing interactions. Each removes a different hard systems problem while preserving the same host boundary.

Why orchestration stays outside

Tonetify does not infer business meaning by coupling the modules behind the host’s back. The host chooses when an event becomes context, when a proposal can proceed, and what execution means.

Governed action boundary

Every operation that changes business state must answer seven questions:

1. Who is acting?
2. What exactly may change?
3. What host state supports the proposal?
4. Who authorized it, and is that authority still valid?
5. Did the host execute exactly what was approved?
6. Was this action already executed?
7. What happened afterward?

Integration shapes

• Relay alone for a self-hosted conversation substrate
• Activity alone for product timelines and event projection
• Govern alone for bounded AI proposal lifecycles
• Any combination through explicit host integration