LAB / VERIFY / FAILURE INVESTIGATION
A guided investigation corridor for distributed-system failure questions. Choose a bounded scenario, follow the model-approved sequence, and enter the existing instrument that can answer that stage's question.
READ THIS FIRST
A scenario is context for choosing a bounded question. It is not a report that Atlas experienced that failure, and it does not make every instrument part of one executed event. Each room keeps its own evidence mode, source, freshness, and proof boundary.
01 / SCENARIO CONTEXT
Changing this selection changes the explanatory relationships below. The selected label never changes a destination's mechanics or turns simulated behaviour into production evidence.
02 / INVESTIGATION SEQUENCE
Every stage has a question, an explicit relationship, and a handoff to an existing canonical instrument. A missing relationship stays visible as missing.
03 / THE CORRIDOR
Relationships are read from the shared Failure Laboratory model.
REQUEST
DIRECT / REQUEST
What happened to this request?
This is a bounded synthetic request baseline.
DEPENDENCIES
DIRECT / DEPENDENCIES
How did a bounded fault propagate through dependencies and how did containment alter the result?
This is a baseline state in a deterministic synthetic graph.
COORDINATION
DIRECT / COORDINATION
How did the bounded replicated-state and quorum teaching model behave?
This is a clean state in a fixed teaching model.
DIRECT / COORDINATION
How did bounded routing, isolation, protection, and repair behave?
This is a synthetic circuit baseline.
IMPACT
Atlas Twin context is available only through the public Evidence Console and remains separate from this selected baseline. A relationship that could be affected is never rewritten as a component that was affected.
The current model does not infer impact from a normal-operation label.
INCIDENT EVIDENCE
CONTEXTUAL / INCIDENT EVIDENCE
What incident evidence was actually recorded?
Only a named recorded Blackbox record can support this contextual reading.
RECOVERY
Recovery-like output, aftermath, or a named lifecycle fact does not prove universal current service recovery or root-cause resolution.
Allowed readings stay distinct: simulated, recorded replay, measured, stale measured, unavailable, and unknown.
04 / OPTIONAL INTERPRETATION
Spectral Forge and System SYMPHONY can add interpretation where the shared model permits it. They are not mandatory linear stages, and their underlying evidence mode stays visible.
CROSS-CUTTING / OPTIONAL
How synthetic baseline telemetry can be mapped to sound and visual state.
A deterministic mapping from selected synthetic telemetry to sound and visual state. Its audio is not incident evidence.
Open Spectral ForgeCROSS-CUTTING / OPTIONAL
What does bounded changing telemetry sound like while uncertainty remains visible?
A read-only sonification of selected source state and uncertainty. Musical state is not incident authority.
Open System SYMPHONY05 / MODEL BOUNDARY
The selected scenario does not get a vaguely similar instrument. “Not applicable / unscored” means this relationship is intentionally not mapped; it is not a hidden failure and it is not a zero score.
Twin describes bounded relationships that could be affected; it does not represent a normal-operation state.
The Console reads named claims and context; it is not a normal-operation simulator.
A beginner-readable bounded path from a synthetic request baseline through dependency failure and propagation to an explicitly limited recovery reading.
Omitted stages: Coordination and Impact. The path does not invent evidence merely to fill the sequence.
A distributed-systems path using the closest bounded coordination and routing models, with its missing stages kept explicit.
Omitted stages: Dependencies, Impact, and Incident evidence. No current instrument supplies those stages for this bounded partition-oriented narrative.
These are model-approved explanatory paths, not synchronized execution traces. Each handoff still opens a separate instrument with its own state and evidence contract.
These links keep every participating destination reachable without JavaScript. They are a handoff index, not a second product directory and not a shared runtime.
06 / EVIDENCE LANGUAGE
The mode says what kind of evidence a destination can present. It does not make this route a live feed. For measured or recorded readings, source and freshness remain owned by the destination record.