AgentPulse, drift investigation for multi vs How It Works

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

RuleMesh structures regulatory requirements, maps them to controls, and specifies the evidence that proves them. Your coding agent calls it over MCP; RuleMesh never...

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 How It Works

RuleMesh structures regulatory requirements, maps them to controls, and specifies the evidence that proves them. Your coding agent calls it over MCP; RuleMesh never accesses your code. Compliance requirements your engineers and AI agents can actually implement. RuleMesh defines what a regulation requires, maps it to the controls your team should implement, and specifies the evidence that proves it was done. RuleMesh has no access to your code, your cloud, or your pipeline. It answers questions about regulation over MCP, and the agent you already use (Claude Code, Cursor, Codex) does the reading and the changing; you review it like any other work.