AgentPulse, drift investigation for multi vs BlitzGraph

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

Model reality as it is, in graphs. Your agents compose typed JSON queries programmatically. No SQL, no joins, no ORMs.

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 BlitzGraph

Model reality as it is, in graphs. Your agents compose typed JSON queries programmatically. No SQL, no joins, no ORMs. A User can also be an Admin and a Moderator, simultaneously. "Who wrote this post?" and "What did this user write?" Same cost, same index, O(1) both ways. Mutations are topologically sorted and validated on the final result, not line by line. Business rules check the end state of the whole transaction, so complex multi-entity operations just work.