In February 2025, a studio programme was approaching handover with two IP transport fabrics. The duplicated paths were an important part of the design, but they did not answer every timing question. During a seven-week, CAD920,000 investigation covering six selected fault scenarios, degradation of the primary clock exposed endpoint behaviour that the handover team had not expected. Under the then-current selection policy, affected endpoints did not move to the healthy reserve as intended.
The project sponsor argued that the transport redundancy had passed its checks and that the remaining timing concern could be monitored after handover. The engineering team wanted the selection behaviour understood before programme operations depended on it. I supported a three-week hold and authorised CAD260,000 of additional work. The cost and delay were explicit; describing two networks as redundant could not resolve a different dependency shared by the receiving equipment.
Specialists examined the clock-selection policy and the monitoring needed to recognise degraded timing. They revised the arrangement and repeated the selected scenarios. The repeat showed the intended behaviour within that test set and supported the next handover decision. I did not prescribe a universal configuration or substitute my judgement for the engineers responsible for the design. My role was to ensure that the unanswered question had the time, authority and funding needed for a useful answer.
The result did not establish a probability of future availability. Six selected scenarios were an investigation plan, not a representative sample of every fault the studio might encounter. Operational monitoring, documented responsibilities and wider programme preparation remained necessary. The project also retained a clear distinction between a transport-path failure and a timing-source problem, so later reports would not use one successful test as evidence for both.
The useful organisational change was a more precise handover account. Programme operations could see what had been examined, what had changed and which responsibilities continued after acceptance. I would now ask for the timing-degradation scenarios at the beginning of the studio plan, alongside the transport tests. That would expose the relationship between duplicated infrastructure and shared selection behaviour before a fixed handover date made the finding look like an avoidable late objection.