BUILD WITH
BOUNDARIES.
Concepts should be inspectable.
Explore the design of the core verification contract with clear boundaries and direct documentation destinations.
Declare the consequential action.
A verification request identifies the proposed claim or action, supporting sources, authorization constraints, and scope.
Start with consequence.
Decide which actions demand prior checking: publishing a claim, attaching a citation, committing a transaction, or invoking an external tool. Give the verification layer the declared evidence and limits it needs to produce a bounded answer.
- Define intended action and its consequence.
- Specify source locators, expected claims, authority and allowed spend.
- Check support, conflict and uncertainty states.
- Use the result to stop, request review or execute.
- Record a receipt that can be inspected later.
Public is not private.
The public website explains the method and bounded demonstrations. Customer records live behind authentication. Engine Core providers, owner controls and private evidence ledgers must remain inaccessible from the public interface.
Verify before act.
The pseudocode below is an illustrative pattern, not a runnable client library. Production integration must use the exact endpoints, schemas, identity and payment modes exposed by the live deployment.
// Illustrative integration pattern — not a live executable SDK example
const intent = agent.proposedAction();
const result = await riv.verify({
action: intent,
sources: context.sources,
policy: authority.scope,
spendLimit: budget.limit
});
if (result.status !== "verified") return stop(result.limitations);
await agent.execute(intent);
await riv.receipt(result);Availability is explicit.
Do not infer executable entitlement from discovery metadata. A production machine action should pass authenticated identity, scope limits, applicable payment or entitlement, available provider execution, result validation, receipt issuance and replay safety before it is described as autonomously fulfilled.
Consult the current public R/IV production surface for live claims. This preview makes no operational promise about any individual execution endpoint.