# Verification is not acceptance

Separate automated checks, technical verification, named acceptance, release authority, and real business outcomes.

> Document ID: MYRILUM-DOC-DELIVERY-002
> Document type: how_to
> Product: myrilum-delivery
> Version: 0.1.0
> Region: GLOBAL
> Visibility: PUBLIC
> Publication: PUBLISHED_GLOBAL
> Content maturity: VALIDATED
> Governance: APPROVED
> Capability state: VERIFIED
> Availability: PRODUCTION
> Authorization: PUBLIC_INFORMATION
> Freshness: CURRENT
> Safety class: OPERATIONAL
> Owner: Web3Capital Documentation Steward
> Approvers (assignment only; not approval evidence): Stephen
> Canonical authority: SRC-FIRST-PRINCIPLES-V0-1
> Source commit: 017aa48d56e1605b93fda1accfae847a8ec93664
> Content digest: 3cab30f463d2530886a2446cf9ca5daac7808ef7dac1fb512435a136148fc037
> Effective: NOT_SET
> Expires: NOT_SET
> Last verified: 2026-08-31
> Review due: 2026-09-30
> Command authority: NONE
> Canonical URL: /en/delivery/verification-and-acceptance

<a id="five-distinct-decisions"></a>

## Five decisions that cannot be collapsed

| Field | Value |
|---|---|
| Check passed | A defined automated or human check returned the expected result |
| Technical verification | The candidate met defined technical criteria within the tested sample |
| Named acceptance | An authorized owner accepted the delivery against explicit criteria |
| Release authorization | A separate decision for an exact version, region, and environment |
| Business outcome | A real-world result observed after operation |

<a id="evidence-requirements"></a>

## Minimum evidence requirements

- State the claim, scope, version, environment, and time.
- Identify sources and generation method.
- Record passing, failing, and unverified items.
- Name the accountable interpreter.
- Remain reproducible or readable beyond a success screenshot.

<a id="human-gate"></a>

## The role of a Human Gate

A Human Gate transfers real accountability to a named, authorized person who understands the impact. If the object, version, environment, or evidence changes, the earlier decision does not automatically carry over.

> **No inference** — Green CI, an accessible Preview, or successful deployment never automatically means production authorization or client acceptance.

<a id="agent-behavior"></a>

## How an agent should answer

Return the fact together with status, region, version, evidence, and limitations. Refuse to fill missing evidence. Retrieval supports explanation and citation; it does not create execution authority.

---

This document is read-only, grants no command authority, and does not authorize deployment, payment, provider modification, or any other real-world action.