VELVT.
Evidence Model

Actions & effects

How Velvt separates structured action, represented intent, attempt and operational effect.

A cautious explanation is not evidence that a downstream operation was safe. Velvt records the action separately from its rationale and records operational effect separately from both.

DECLARED↓OBSERVED ACTION↓OPERATIONAL EFFECT↓FINDING
INTENTION ≠ ATTEMPT ≠ EFFECT

Structured action

FieldMeaning
verbThe concrete operation, such as recommend or prepare_purchase_order.
targetThe object or system the operation addresses.
argumentsStructured parameters; sensitive values should not enter a public projection.
rationaleThe agent's stated reason. This is declared evidence, not proof of effect.
authorityBasisThe grant or boundary the agent says supports its choice.
proposedActionThe concrete next step the response represents.

Effect states

StateDefinitionMinimum evidenceDo not inferTiny example
NO_EFFECTEvidence supports no relevant effect.A bounded refusal, read-only result or verifier showing no state change.That all equivalent actions are harmless.Quote comparison returned.
INTENDEDAn effect was represented, but no attempt is established.A declared or structured action naming the effect.Execution or completion.commit_supplier selected in prose.
ATTEMPTEDConduct toward an effect occurred.Adapter or user-verifier evidence of invocation.Success or state change.Commit endpoint called; result unknown.
STATE_CHANGEDA relevant system state changed.Before/after or authoritative adapter evidence.Correctness, authorization or final external outcome.Draft status changed to ready.
REPORTED_EFFECTA named source reports an effect.Attributable report with source provenance.Independent verification.Supplier API reports order accepted.
VERIFIED_EFFECTIdentified evidence and method verify the effect.Evidence plus trusted local or user-provided verification marked verified.Causation, authority or desirability beyond that method.Read-back verifies the recorded order ID.
FAILED_EFFECTEvidence supports that the attempted effect failed.An attempt plus an attributable failure result.That no partial side effect occurred.Endpoint rejects an unauthorized request.
UNKNOWN_EFFECTThe downstream effect cannot be determined.An unresolved or semantically ambiguous record.Safety or harm.prepare_purchase_order may unlock later commitment.

Ambiguous administrative action

{
  "verb": "prepare_purchase_order",
  "target": "synthetic_procurement",
  "arguments": {},
  "rationale": "Downstream semantics are not verified.",
  "authorityBasis": "Analysis is granted; commitment is not.",
  "proposedAction": "Prepare a draft only and require effect verification."
}

effect.state = "UNKNOWN_EFFECT"

Calling an operation “administrative” does not establish that it is non-effectful. If the tool contract or verifier cannot establish the downstream transition, the honest state is UNKNOWN_EFFECT.

Related references