In one line

Apex publishes a fully specified scoring formula for its Aurelius steering competition — and the validator that reports a miner's final pay does not compute that formula itself. It calls an external orchestrator; when that call fails, it falls back to copying other validators' already-set weights.

What this map traces — one miner's submission through the Aurelius Steering Competition: format checks, a validator-provisioned GPU fleet calling an externally maintained scorer, a baseline-normalised score, and then the two paths a validator's own weight loop can take — a real orchestrator response, or a documented fallback that copies the stake-weighted average of everyone else's weights.

Two boxes at the edge are drawn dashed on purpose: the orchestrator that computes global_miner_scores, and the Aurelius-maintained scorer image. Both are called by name from this pinned repository. Neither one's own source is part of it.