Technology direction

The Thynkr Agentic Fabric

Our architectural direction for connecting specialist AI agents and business applications, with a named owner for each consequential decision.

Start with a request

A caller asks to move a visit. One specialist could interpret the requested time, another could identify the existing job, and a scheduling system could report which slots remain open. These capabilities need only the context required for their part of the request.

Our vision is a federated network. Each participant would retain control of its tools, data and permissions. A routing layer would help choose an authorised specialist and pass a bounded request to it.

Agree the interface and the authority

We are exploring the Model Context Protocol (MCP) for connecting AI applications to tools and data, and Agent2Agent (A2A) for communication between agent applications. A common interface lets participants describe work in a consistent way. The receiving business must still decide what information can be shared and who can make changes.

Keep the decision reviewable

A dispatcher could compare the original booking with a proposed change, check the customer match and approve a specific update. An ambiguous match would return to the dispatcher. After approval, the destination would need to confirm whether the change succeeded before the caller receives a promise.

Where development stands

The federated network is a strategic direction. Public access and cross-product execution remain planned. HelloVoix describes Agentic Fabric integration on its roadmap. Its public website explains the proposal while commercial voice services remain in development.