# How one goal becomes delivery

Follow the governed loop from goal and scope through delivery, evidence, acceptance, continued improvement, or exit.

> Document ID: MYRILUM-DOC-DELIVERY-001
> Document type: tutorial
> Product: myrilum-delivery
> Version: 0.1.0
> Region: GLOBAL
> Visibility: PUBLIC
> Publication: PUBLISHED_GLOBAL
> Content maturity: VALIDATED
> Governance: APPROVED
> Capability state: OPERATING
> Availability: PRODUCTION
> Authorization: PUBLIC_INFORMATION
> Freshness: CURRENT
> Safety class: OPERATIONAL
> Owner: Web3Capital Documentation Steward
> Approvers (assignment only; not approval evidence): Stephen
> Canonical authority: SRC-AI-SERVICE-OFFER-AUTH-V1-1
> Source commit: 017aa48d56e1605b93fda1accfae847a8ec93664
> Content digest: 22e9bb50e4c2d40c32ad7a44a72321d970e7ef09e6b28c94f1329b60a2f81e38
> Effective: NOT_SET
> Expires: NOT_SET
> Last verified: 2026-08-31
> Review due: 2026-09-30
> Command authority: NONE
> Canonical URL: /en/delivery/how-it-works

<a id="goal-and-context"></a>

## 1. Clarify the goal and context

Define the outcome, current baseline, owner, time horizon, and non-negotiable boundaries. A goal should not merely say use AI.

- Who is affected?
- What result should change?
- How will change be observed?
- Which risks or permissions are out of bounds?

<a id="scope-and-route"></a>

## 2. Confirm scope and route

Turn the goal into bounded tasks, dependencies, candidate routes, samples, environments, and stop conditions. Only then select the people, agents, data, tools, and external capabilities required.

<a id="delivery-and-evidence"></a>

## 3. Deliver and preserve evidence

Keep versions, inputs, critical decisions, exceptions, verification methods, and results. High-impact actions must stop at named human decision points.

> **Evidence is not decoration** — Evidence must support a specific claim and retain source, scope, time, and accountability.

<a id="accept-or-adjust"></a>

## 4. Accept, adjust, or stop

Technical verification shows whether defined checks passed. A named acceptance owner decides whether to accept, continue, adjust, or stop. Completion does not authorize production release.

<a id="continuous-optimization"></a>

## 5. Improve or exit under control

Continue from quality, cost, risk, and real feedback. If a stop condition is reached, record why, preserve evidence, and complete the agreed handover or exit.

---

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