# Agentic-commerce readiness workbook

Use one copy for one dated pilot. “Unknown” is a valid result; do not convert
missing evidence into readiness.

## 1. Pilot boundary

- Review date:
- Pilot item IDs:
- Physical quantity:
- Permitted surface:
- Current controlling policy/specification URL and version:
- Merchant eligibility evidence:
- Explicit exclusions:

## 2. Ownership

| Control | Named owner | Backup | Evidence location |
| --- | --- | --- | --- |
| Product facts and condition |  |  |  |
| Price and availability source |  |  |  |
| Feed or channel delivery |  |  |  |
| Policy review |  |  |  |
| Incident response |  |  |  |
| Privacy and analytics |  |  |  |

## 3. Readiness levels

| Level | Pass evidence | Gap | Decision |
| --- | --- | --- | --- |
| Visible: permitted surface can retrieve the item |  |  | pass / fail / unknown |
| Interpretable: exact object and condition are distinguishable |  |  | pass / fail / unknown |
| Current: changed facts converge within the service level |  |  | pass / fail / unknown |
| Transactable: a documented supported path exists |  |  | pass / fail / unknown |
| Measurable: events and incidents can be observed safely |  |  | pass / fail / unknown |

## 4. Freshness test

- Change tested: price / availability / reserve / release / sold / withdrawn
- Source change timestamp:
- Delivery timestamp:
- Acknowledgment or validation timestamp:
- Independent public verification timestamp:
- Maximum allowed propagation delay:
- Measured delay:
- Surfaces checked:
- Conflicts found:
- Corrective action:

## 5. Incident rehearsal

For each scenario, name detection, containment, correction, verification, owner,
and customer response.

- [ ] Sold item remains actionable.
- [ ] Available item shows quantity zero.
- [ ] Price or currency conflicts with checkout.
- [ ] Condition evidence belongs to another unit.
- [ ] Two orders target the same one-of-one item.
- [ ] Platform policy or access condition changes.
- [ ] Delegated purchase authority is disputed or absent.
- [ ] Analytics begins collecting an unapproved identifier.

## 6. Privacy-safe measurement

- Course or artifact events used:
- Referral evidence used:
- Order evidence used:
- Data intentionally not collected:
- Retention period:
- Person approving privacy posture:
- Known attribution limitations:

Do not treat a user-agent string, vague referrer, download, or course completion
as proof of an agent buyer, delegated authority, revenue, or causal outcome.

## 7. Rollback and release

- Stale-offer rollback trigger:
- Policy-change rollback trigger:
- Validation-error rollback trigger:
- Incident-rate rollback trigger:
- Rollback owner and procedure:
- Editorial reviewer and date:
- Legal/policy reviewer and date:
- Product/technical reviewer and date:
- Unresolved findings:
- Release decision: approve / reject / revise
- Expansion decision and evidence: