TOVREK / OutcomeSeal Preview

Decide whether supplied evidence is enough to accept an outcome

Give OutcomeSeal one expected outcome, one explicit rule and one caller-supplied observation. It returns a deterministic structured ACCEPT, PARTIAL, REJECT or UNKNOWN result before your workflow acts.

Use it when accepting the wrong outcome would cost more than one preflight call.

Evidence basis: CALLER_SUPPLIED_UNVERIFIED. TOVREK does not independently verify the authority, independence or freshness of the evidence in this Preview.

10-second example

Expected outcome: Delivery completed as agreed.

Rule: delivered equals yes.

Observation supplied by caller: delivered = yes.

OutcomeSeal evaluates the rule exactly as supplied. If required evidence is missing, conflicting or insufficient, the result does not become a confident acceptance by assumption.

Try OutcomeSeal

No request sent yet.

When to use it

before an agent accepts a delivery, completion or compliance claim;
when an explicit rule should be evaluated without silently upgrading trust;
when missing evidence should remain UNKNOWN instead of becoming a guess.

Preview limits

Caller evidence is evaluated as supplied. Trust claims from the caller do not upgrade the evidence basis. This Preview does not claim independent verification, verified authority or verified freshness.

Free use is bounded by TOVREK credits and shared safety limits. A successful OutcomeSeal run uses one credit. Invalid input and server failures do not.

The browser creates a random tab-local principal in memory. It is not stored in localStorage, sessionStorage or cookies. Retries of the same logical request reuse the same idempotency key.

Machine endpoint: POST /v1/outcomeseal/verify.

Developer documentation · OpenAPI · Machine discovery · Privacy