When a request moves through an AI organization, even a well-intended summary or suggested plan can make it difficult to tell where the requester’s intent ends and the relay’s interpretation begins. Wiroh addressed this by separating Mako’s relay into two layers. One contains the original payload from the CEO or a role agent. The other contains only operational facts needed for the lifecycle, such as routing, role, branch, gate, and status.
Requirements interpretation, working plans, and specialist sequence belong to the active domain lead’s payload; Mako does not add them to the original message. Missing or ambiguous information is returned as unconfirmed rather than filled in by assumption. This contract is not an absolute guarantee that meaning can never change. Its purpose is to make the boundary between source language and operational information visible, so the origin of a decision can be checked later.