FREQUENTLY ASKED QUESTIONS

DOOMS PROTOCOL is a month-long online developer event built around a fictional digital-collapse scenario.

In the story, Earth-606 is experiencing a catastrophic breakdown of its digital infrastructure. Communication, navigation, commerce, and access to human knowledge are progressively failing.

Participants are called upon to rebuild these systems through four week-long recovery missions during December 2026.

The event combines software development with a continuing narrative, so each completed mission represents another layer of the fictional network being restored.

Earth-606 was once a highly interconnected world whose communication, navigation, commerce, and knowledge systems depended on a seamless digital infrastructure.

Multiversal fractures caused a catastrophic digital infrastructure crisis. The systems did not simply experience ordinary outages; they began to disappear from the fictional reality itself.

The remaining recovery authority discovered that the collapse was also being accelerated from within its own infrastructure.

The event is planned for December 2026.

Exact dates, recovery windows, submission deadlines, and evaluation periods will be published through the official Event channels.

Eligibility is determined by the official Event rules and registration requirements.

Participants must provide accurate registration information and satisfy applicable age, location, and other eligibility requirements.

If minors are permitted to participate, additional parental or guardian consent may be required.

The event may require an initial registration or participation fee.

If a fee applies, the exact amount, currency, payment method, taxes, refund conditions, and other payment information will be displayed during registration.

Each week provides a specific recovery mission.

The mission brief defines required functionality, constraints, datasets, submission requirements, and evaluation criteria.

The general expectation is a working software prototype, not merely a concept or presentation.

A valid submission must satisfy the requirements published for the relevant mission.

Depending on the mission, this may include a working deployment, source repository, documentation, demonstration, architecture information, test instructions, or other required material.

No. The fictional story does not authorize participants to attack or exploit real Event infrastructure.

Unauthorized access, denial-of-service activity, credential attacks, destructive testing, or attacks against other participants are strictly prohibited.

No hacking another participant's project unless an explicit mission authorizes security testing within a defined scope.