---
name: synthetic-order-status-review
description: Review fictional order-status records through a prepared CLI contract while preserving evidence, dry-run output, and explicit human confirmation.
---

# Synthetic Order Status Review

This is a public Portfolio example, not an installed production Skill. Every API path, command, organization, and record is fictional.

## Use when

- A user asks to inspect a fictional `SYN-ORD-NNNN` record.
- A user asks for the evidence supporting its current review state.
- A user asks to prepare an accept, modify, or return decision.

## Do not use when

- The identifier does not match `SYN-ORD-NNNN`.
- The request concerns a real order, customer, system, credential, or private endpoint.
- The user has not explicitly confirmed a state-changing submission.

## Workflow

1. Read the record with `order-status show ID --include-evidence --json`.
2. Separate API facts, system recommendation, and missing evidence.
3. Explain the proposed decision and its reason to the user.
4. Prepare a dry run with `order-status decision prepare`.
5. Show the complete dry-run receipt.
6. Stop and request explicit human confirmation.
7. Submit only when the user supplies the confirmation ID.
8. Read the audit receipt and report the final recorded state.

## Decision boundary

- Reading and dry-run preparation are reversible.
- Submission is externally visible and requires explicit human confirmation.
- Never invent or reuse a confirmation ID.
- Never translate a system recommendation into a human decision silently.
- Never omit missing evidence, API errors, or dry-run status.

## Output format

Report:

1. `Record` — ID, current status, and scoped fields.
2. `Evidence` — each evidence item and its source label.
3. `Recommendation` — system-provided text, clearly labeled.
4. `Human decision` — pending, confirmed, or not submitted.
5. `Receipt` — dry-run or recorded receipt ID and audit state.

## Public-demo limitation

The companion OpenAPI document and CLI help are prepared artifacts. No executable CLI, live API, authentication flow, private schema, or enterprise permission has been published with this example.