Docs
CORE CONCEPT

You control
the next step.

Preparation, permission and delivery are different states.

The reviewed-action sequence

Prepare→Preview→Approve→Commit→Read back

Reviews bind exact contents, recipient, purpose and versions. Approve in the authenticated browser. Your assistant must then perform the supported commit and read back the result. Changed data, expiry or revoked access can invalidate approval.

Four independent choices

One choice does not imply another. Sharing does not buy a ranking advantage.

Read the receipt literally

Observed stateWhat it establishes
Draft preparedPrivate work exists; nothing sent.
Review approvedThat version may be committed; delivery is not established.
Native receiptDelivery to the named Afina inbox.
Applicant-reported progressA person reported a status; not independently verified.
External deliveryRequires separate destination evidence.

Unknown is a useful result

Missing requirements, conflicting sources and incomplete outcomes stay explicit. A timeout is not evidence of either delivery or failure. Read current status before deciding whether a retry is safe.