Version the system
Register Service, Agent, Model, Data and Verifier Cards with exact versions and relationships.
From autonomous agents and support workflows to payment APIs and ML services, Wyrd checks requirements against what actually ran. Keep your existing execution framework; add independent, versioned verification across steps and outcomes.
Refund response complied with the declared policy.
requirement: policy-004 · cited policy checkPayment flow skipped a required eligibility lookup.
requirement: pay-eligibility-002 · trace checkA training feature used values unavailable at prediction time.
requirement: feature-time-017 · data checkDeclare components and obligations for an agent, API or ML workflow; preserve real execution evidence; then check the relevant requirements independently.
Register Service, Agent, Model, Data and Verifier Cards with exact versions and relationships.
Capture a run across service steps, model calls, custom data, and other relevant operations.
Use assertions, trace checks, code, or cited model judges for the requirements that apply.
Wyrd is not an agent orchestrator or general workflow runner. Your application or framework handles execution; Wyrd records evidence and evaluates explicit, versioned requirements for the relevant Service or component.
Bind a versioned Verifier to a Service, Agent or other declared component.
Record relevant data under the same run_id and exact component version.
Ask for a synchronous verdict, submit an asynchronous check, or schedule a drift check.
Use the same foundation for agent responses, API decisions, and ML/data pipelines—each with different requirements and the evidence those checks need.
Check that an agent followed policy and used required tools before responding.
Check that a payment or fulfillment service followed its business process.
Check that features, metrics and evaluation logic satisfy versioned requirements.