Identity before authority
A sender email address is useful for routing. Action authority requires ownership checks and authentication.
ARKHAI’s architecture separates receiving a request from authorizing the action it asks for.
Inspect a communication policyA sender email address is useful for routing. Action authority requires ownership checks and authentication.
An approval is tied to the selected proposal, its version and an authorized role. Changing the proposal invalidates the earlier decision.
A late response can remain in the thread without resuming an expired action. Rejection keeps execution blocked.
Routing, denials and state changes need correlated events so a team can understand why a workflow continued—or did not.
Retention, deletion and organization boundaries belong to the service policy. Keep only the context each workflow needs.
Keep authorization tied to a specific action, proposal version and reviewer role.
Inspect the selected route and its permission boundary alongside the conversation history.
Read the architecture