Recipient acknowledgement

Access, download and acknowledgement are three different events.

A download is not receipt. The named recipient acknowledges the exact package.

How it works

A recipient can prepare and download the authorised package, and that action alone leaves receipt unacknowledged. The named recipient must deliberately acknowledge the exact package, including its identity and hash.

Boundaries

Acknowledgement is not proof that every sentence was understood, or that the assessment was accepted as correct.

Recipient acknowledgement

Element

Feedback

Versioning

Package hash

Human decision

Explicit

Status

Implemented

Related capabilities