Provely uses one approved word for one meaning. This glossary defines each term in one sentence and links to the page that explains it.

TermDefinition
IntentWhat the user asked for, stated before any action.
ActionWhat the agent attempted against the provider.
AcknowledgementWhat the provider returned at once, such as HTTP 200 and an object.
OutcomeThe observable resulting state in the real system.
CompletionThe outcome satisfies the completion contract.
Completion contractA machine-readable, versioned, hashable definition of done for one operation.
Completion levelOne named promise of a service, proven by one contract.
CorrelationThe binding of evidence to the exact operation through keys such as a resource id.
IdempotencyThe property that a retried request creates no second side effect.
Evidence levelThe rank of a piece of evidence by its independence from the action path, E0 to E5.
VerdictThe result of one verification attempt: VERIFIED, PENDING, CONTRADICTED, FAILED, or UNVERIFIABLE.
PENDINGThe verdict while an operation can still make progress.
UNVERIFIABLEThe verdict when the evidence never became sufficient.
CONTRADICTEDThe verdict when the evidence shows a different outcome than the intent.
False VERIFIEDA VERIFIED verdict for an outcome that did not happen. The highest-severity defect.
Evidence receiptA signed, machine-readable record of what was verified and how.
IntegrationThe package that Provely compiles for one provider and signs. It states what "done" means there.
Agent SkillOne SKILL.md file in the Anthropic format. An agent loads it and follows the instructions in it.
MCP serverA process that publishes tools over the Model Context Protocol. An agent calls them to act on a provider.
Permission envelopeThe allow list of tool names and argument values that a person confirmed.
GuardThe interceptor that checks each tool call against the permission envelope before it runs.
ConformanceThe mandatory test matrix a skill must pass before certification.
Intent compilationThe step that turns a task in natural language into a completion contract.
Intent fidelityThe agreement between what the user asked for and what the contract checks.
REQUIRES_REVIEWThe mark on a part of a task that no contract can check.
DriftA change in a provider schema, docs, or behaviour that can change a contract.