ARKHAI
Menu
05 / TRUST & CONTROLARKHAI FIELD NOTES

A MESSAGE ISN’T
A PERMISSION.

Reachability opens a conversation. Authority determines which actions can follow.

KEEP THE
BOUNDARY
EXPLICIT.

ARKHAI’s architecture separates receiving a request from authorizing the action it asks for.

Inspect a communication policy

Identity before authority

A sender email address is useful for routing. Action authority requires ownership checks and authentication.

Approval belongs to an action

An approval is tied to the selected proposal, its version and an authorized role. Changing the proposal invalidates the earlier decision.

Expiry means stop

A late response can remain in the thread without resuming an expired action. Rejection keeps execution blocked.

A visible event trail

Routing, denials and state changes need correlated events so a team can understand why a workflow continued—or did not.

Retention is a deliberate choice

Retention, deletion and organization boundaries belong to the service policy. Keep only the context each workflow needs.

DESIGNED FOR
ACCOUNTABILITY.

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