That's the point. If you want a reliable separate path, you must test it, and you must be prepared to spend time and money on fixing it. The tests include calling up the engineering manager for the separate path and verifying that it has not been "re-groomed" into sharing a path with your primary -- monthly or quarterly, depending on your risk tolerance.
Operations work does not end because the world keeps changing.
it certainly ends in somewhere resembling cost-effective. "reliable" has its meanings in context, and backhoe issues aren't so much of a problem architecturally for starlink.
they have incentive and capability to get that traffic off the shared fate should it occur (even if that extends up to starlink serving one of their IP transit providers for OOB). that's why i question the wisdom of being overly concerned with starlink's particular paths.
That's the point. If you want a reliable separate path, you must test it, and you must be prepared to spend time and money on fixing it. The tests include calling up the engineering manager for the separate path and verifying that it has not been "re-groomed" into sharing a path with your primary -- monthly or quarterly, depending on your risk tolerance.
Operations work does not end because the world keeps changing.