Submission Submitted
The sender initiates and submits the message.
A controlled vocabulary for submission, acceptance, delivery, handover, acknowledgement and failure, preventing over-interpretation.
Each event has its own trigger, time, hash, issuing party and interpretation limits.
The sender initiates and submits the message.
The service accepts the message and starts the delivery process.
The service rejects the submission and produces rejection evidence where required.
The content is made available within the service domain for the recipient.
The message reaches the recipient domain or controlled system.
The content crosses the service boundary into the recipient application or system.
The recipient acknowledges the item where the business process requires it.
A delivery step cannot be completed; failure evidence records the reason code.
The delivery window expires under the policy or sender option.
“Handed over to the recipient system” does not inherently mean “read” or “accepted”.
Evidence describes an observable system event at a defined boundary.
Legal effect depends on the service policy, contract, applicable law and supporting evidence.
The data model must support event re-validation and change detection.
Unique, immutable event identifier.
Sender, recipient and authentication context.
Hash algorithm and document digest.
Event time and timestamp token reference.
Evidence issuer and electronic-seal reference.
Policy OID, version, retention and interpretation limits.
This page is the controlled vocabulary source for landing pages, technical documents and policies.