Incident Procedure

1. Failure before an entry list is sealed

Until a list is sealed, no public commitment exists — there is nothing an incident could corrupt. If an upload or validation step fails, the operator simply corrects the list and tries again. This is not an incident and nothing is recorded.

2. Failure after sealing, before the draw is triggered

The seal already fixes the complete entry list, and it cannot be altered by anyone — including us — during any outage. If a technical failure prevents the draw from running at its advertised time, the draw is run as soon as service is restored, using exactly the sealed list.

A delay of more than a few minutes to an advertised draw time is noted on the draw's public page: what happened, and the new draw time. A delayed draw is still the same draw — the sealed list, and every entrant's tickets in it, are unchanged.

3. Failure after the trigger, before certification

Once the draw is triggered, the winning number is already mathematically determined by the sealed list, the committed secret salt, and the seed source defined by the Standard. A failure in this window can delay certification, but cannot change the result — there is no step where a person chooses anything.

When the required public records become retrievable, certification completes exactly as it would have, and the certificate shows the full working as normal. The delay and its cause are noted on the draw's public page.

4. When completion is impossible: void and re-run

In the rare case where a draw cannot be completed under the Standard at all — for example, the seed source required by the rule is permanently unrecoverable for the triggered window — the attempt is voided.

A void is public and permanent: the voided attempt remains visible on the draw's public page with the reason logged. It is never quietly deleted.

The draw is then re-run with the same sealed entry list — no entries added, removed, or changed — at a new advertised draw time. Entrants keep exactly the tickets they had.

What never happens

• — A valid result is never re-drawn. The trigger is one-shot; there are no re-rolls, whatever the outcome.
• — A sealed entry list is never edited, in an incident or otherwise. Correction is void-and-reseal — publicly visible, reason logged.
• — A void is never hidden. Voided attempts stay on the public record with their reason, permanently.
• — Certification of an already-sealed draw is never withheld — not for account suspension, not for an unpaid invoice, not for any commercial reason.
• — Operators are never charged for incident handling. Completing or re-running a draw under this procedure is free.

How incidents are communicated

Any incident affecting a sealed draw is noted on that draw’s public page within 24 hours — what happened, what stage the draw is at, and what happens next — so entrants can see the status for themselves rather than relying on the operator’s social media. The operator is notified directly at the same time.

Versioning

This procedure is versioned with the Fair Draw Standard and may be amended only by published version. Amendments never apply retrospectively: an incident is always handled under the version in force when the affected draw was sealed, and prior versions remain available.