A decoy outage must not reopen the protected origin

DungeonQ's defensive deception runtime keeps designated sessions working inside persistent synthetic worlds. What happens when that path fails matters as much as the successful walkthrough.

In the self-hosted reference, a synthetic transport failure does not fall back to the protected origin. Invalid authority, missing evidence, or unreadable state return bounded errors. The gateway records an attempt before dispatch, so an interrupted operation cannot simply disappear from the evidence.

The published September 18 acceptance record includes a useful negative check: with the containers stopped, verification returned INCONCLUSIVE instead of reusing an earlier passing result.

For operators, preserve the failed run's records and inspect the uncertainty. Automatic reconciliation of unknown outcomes is not implemented; deleting state is not a recovery procedure.

These are documented mechanisms and historical checks of an owned reference using artificial resources, not a new release or proof of production protection or AI deception.

Operation guide:

https://github.com/Ranopha/dungeonq-astra/blob/v0.11.1/docs/RUNTIME.md

Recorded acceptance and limits:

https://github.com/Ranopha/dungeonq-astra/blob/v0.11.1/docs/RUNTIME_ACCEPTANCE.md