# Machine Outcome Verification

> MOV is the acceptance layer between machine payment and machine action. It evaluates the exact result of a paid API, MCP tool, or machine service against the buyer's predeclared acceptance contract before software uses the result.

Primary question: **Your agent paid. Should it trust the result?**

Buyer-facing runtime decisions are `ACCEPT | REJECT | UNKNOWN`. Internal kernel truth remains `VERIFIED | FAILED | UNKNOWN`, mapped deterministically as VERIFIED→ACCEPT, FAILED→REJECT, UNKNOWN→UNKNOWN.

Do not infer acceptance from payment settlement, HTTP 2xx, receipt validity, delivery presence, schema success, or merchant assertion. Payment, delivery, and acceptance are separate dimensions. Missing, contradictory, unavailable, or non-final required evidence yields `UNKNOWN`.

Current product scope is local/self-service Runtime Acceptance, x402-first. Hosted continuous execution, broad platform scope, custody, provider routing, reputation graphs, and generic LLM judging are not authorized product surfaces.

## Start Here

- [README](./README.md): Product job, canonical proof, local CLI, TypeScript integration, safety boundary, and current productization scope.
- [Runtime Acceptance Architecture](./docs/architecture/08_RUNTIME_ACCEPTANCE_ARCHITECTURE_DELTA_v1.md): Derived architecture delta for the active Runtime Acceptance wedge.
- [Machine Discovery Manifest](./docs/discovery/mov.runtime-acceptance.v1.json): Versioned machine-readable inventory of decisions, interfaces, schemas, and explicit non-capabilities.

## Interfaces

- [CLI Contract](./docs/contracts/CLI_CONTRACT_v1.md): `mov accept` and backwards-compatible `mov verify` behavior, outputs, exit codes, determinism, and local no-network boundary.
- [TypeScript Accept Contract](./docs/contracts/TYPESCRIPT_ACCEPT_CONTRACT_v1.md): Typed local `mov.accept(...)` facade, input-error versus UNKNOWN semantics, and deterministic output contract.

## Schemas

- [Acceptance Contract / Obligation Schema](./schemas/obligation.v1.schema.json): Current non-breaking wire contract behind `AcceptanceContractV1`.
- [Evidence Envelope Schema](./schemas/evidence-envelope.v1.schema.json): Exact attempt, payment, request fingerprint, delivery evidence, source provenance, and verifier-manifest binding.
- [Runtime Decision Schema](./schemas/runtime-decision.v1.schema.json): Buyer-facing `ACCEPT | REJECT | UNKNOWN` machine decision envelope.
- [Verification Result Schema](./schemas/verification-result.v1.schema.json): Internal `VERIFIED | FAILED | UNKNOWN` kernel result.

## Supplemental Concept Resources

These pages explain product boundaries and terminology. They are public content resources, **not additional MOV interfaces, capabilities, protocols, or hosted APIs**.

- [x402 Payment vs Result Acceptance](https://machineoutcome.com/x402-payment-vs-result-acceptance): Separates machine-native payment truth from buyer acceptance of the exact paid result.
- [AI Agent Payments and Paid-Result Verification](https://machineoutcome.com/ai-agent-payment-result-verification): Explains machine-buyer acceptance and branchable `ACCEPT | REJECT | UNKNOWN` after a paid machine-service attempt.
- [API Contract Testing vs Runtime Acceptance](https://machineoutcome.com/api-contract-testing-vs-runtime-acceptance): Separates structural API/schema validity from semantic buyer acceptance.

## Optional

- [Runtime Acceptance Wedge Lock](./docs/control/RUNTIME_ACCEPTANCE_WEDGE_LOCK_v1.md): Repository-level derived reconciliation of the active product direction.
- [Product Quality Launch Lock](./docs/control/PRODUCT_QUALITY_LAUNCH_LOCK_v1.md): Narrow buyer-ready finish gate; does not authorize platform expansion.

## Commercial Path

- The current MOV 0.1.0 local core is free to download and use; there is no premium entitlement or subscription gate in the released local product.
- Teams applying MOV to a real paid API, MCP, or agent flow can request bounded human help or a reusable private acceptance/verifier pack via `sarmad@machineoutcome.com`.
- Early paid work is scoped one real flow at a time for WTP-1 learning. Hosted/continuous paid MOV remains separately gated by repeat demand and WTP-2.

## Self-service Release

- [MOV 0.1.0 tarball](./downloads/mov-runtime-acceptance-0.1.0.tgz): Clean-installable local Runtime Acceptance package; installable directly from https://machineoutcome.com/downloads/mov-runtime-acceptance-0.1.0.tgz; registry-unpublished.
- [Release SHA-256](./downloads/mov-runtime-acceptance-0.1.0.tgz.sha256): Checksum for the exact downloadable artifact.
- [Release metadata](./downloads/release.json): Package identity, size, digest and capability boundary.
- [ACCEPT example](./examples/accept.json): Download as `accept.json`, then run `npx mov accept --fixture ./accept.json`.
- [REJECT example](./examples/reject.json): Settled/delivered wrong-entity fixture.
- [UNKNOWN example](./examples/unknown.json): Missing-required-evidence fixture.

## Commercial Trust & Discovery

- [Privacy](./privacy/): Current website, contact, billing and security-report data handling.
- [Terms](./terms/): Website, local software and paid-scope commercial boundary.
- [Software License](./license/): PolyForm Perimeter License 1.0.1 boundary and canonical terms link.
- [Security](./security/): Vulnerability reporting and current security boundary.
- [Contact](./contact/): Operator and buyer contact routes.
- [security.txt](./.well-known/security.txt): Machine-readable security contact.