AgentPulse, drift investigation for multi vs Axtary

Open-source drift investigation for multi-agent systems: which agent drifted, where it originated, and what to check next.

Axtary checks the exact tool call, payload, policy, and approval before an AI agent touches GitHub, Slack, MCP tools, or production APIs.

About AgentPulse, drift investigation for multi

Open-source drift investigation for multi-agent systems: which agent drifted, where it originated, and what to check next. What did change is the payload it receives from writer, starting at the same run. So critic is probably downstream damage, not the source. After the change, writer responses run ~180% longer and drop the section structure critic expects, earlier payloads were structured summaries, newer ones read as prose. If restoring the format fixes critic, make the fix in writer.

About Axtary

Axtary checks the exact tool call, payload, policy, and approval before an AI agent touches GitHub, Slack, MCP tools, or production APIs. If an agent is mistaken or compromised, its authority remains limited to the approved action. Human approval is bound to the reviewed payload hash. If the payload changes after approval, adapter-side verification rejects the mismatch before the provider is called. The approved and presented hashes are recorded in the ledger. ActionPass artifact Approval is bound to the payload, not a summary.