INTEGRATION MOCKClaude Code
Tool call → mandate check → decision
Mock · Not evidence of an available integration.
w⁴iya integrations
The gateway is independent. Each harness needs an integration that covers its real execution paths.
Read moreDeepSeek Harness and Deins
The development integration connects native tool calls and the Deins interface to agent identities, mandates and approvals. Direct program effects, external agent behaviour and shared-user socket access are not fully contained.
Other agent environments
Adapters are the route to other environments. A tool catalogue or MCP connection alone is not proof of enforcement. The check must be bound to the action and the action must follow a controlled execution path.
In your agent environment
Three examples of what a w⁴iya integration could look like.
INTEGRATION MOCK
INTEGRATION MOCKCodex
Planned action → gateway → receipt
Mock · Not evidence of an available integration.
INTEGRATION MOCKHermes Agent
Agent identity → mandate → controlled call
Mock · Not evidence of an available integration.