Capture
Bind the methods that create run evidence and the actions that change business state.
The action boundary runtime
VerifiedX sits immediately before a real side effect. It checks the proposed action against the evidence gathered in that run, then returns a decision your agent can execute, replan from, or route upstream.
Tool results, retrievals, messages, memory, upstream context.
Outcome, reasons, safe next steps, retry and routing contract.
The runtime contract
Keep the agent architecture you already chose. Add VerifiedX only where a method crosses from reasoning into money movement, external communication, record mutation, or another durable side effect.
Bind the methods that create run evidence and the actions that change business state.
Check the exact proposed action against direct, same-target facts before execution.
Continue downstream, replan locally, pass the receipt upstream, or stop the unsafe path.
Executable outcomes
A concrete runtime decision with the information the next node needs.
The evidence positively supports the proposed effect.
The action is justified; the receipt preserves a bounded caution.
Block this execution and return the supported next path for the same goal.
Use only when the goal cannot continue safely through this route.
Bind your real seam
Wrap the business methods you already own. VerifiedX observes the run and preflights only the actions you classify as consequential.
Read the integration guideimport { initVerifiedX } from "@verifiedx-core/sdk";
const vx = await initVerifiedX();
vx.bindHarness(agent, {
retrievals: {
fetchInvoice: "invoice evidence",
},
actions: {
issueRefund: "issueRefund",
},
});
Built for operators too
Every boundary outcome can be logged with its direct reasons, safe next steps, execution status, and resume contract.
See which observed fact supported or contradicted the pending action.
Return an actionable alternative that keeps the original goal alive.
Separate what was approved from what actually executed successfully.
Give downstream agents, upstream orchestrators, and humans the same decision record.
Start at one boundary
Use 25-50 anonymized historical traces to select the seam, estimate the allow / replan split, and define a production-relevant pilot.