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

- Save privately: preserve your context for later sessions.

- Enable discovery: review the fields recruiters can see.

- Allow external processing: separately authorize supported evidence assessment.

- Send an application or message: approve exact materials and destination.
One choice does not imply another. Sharing does not buy a ranking advantage.

## Read the receipt literally

| Observed state | What it establishes |
| --- | --- |
| Draft prepared | Private work exists; nothing sent. |
| Review approved | That version may be committed; delivery is not established. |
| Native receipt | Delivery to the named Afina inbox. |
| Applicant-reported progress | A person reported a status; not independently verified. |
| External delivery | Requires 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.
