Art. 91(3)

Payload comms in hosted-payload contexts traverse third-party-customer paths; 91(3)'s pre-defined-agreements-with-third-party-entities clause governs how the operator constrains payload-channel use.

OSAM service vehicles are typically third-party hosted-service contexts; 91(3)'s pre-defined-agreements-with-third-party-entities clause governs the coordination/discipline at docking interfaces.

91(3) explicitly governs hosted-payload incident scenarios — 'When a satellite hosts third-party payloads' is the exact context of IA-0006, and the pre-defined-agreements clause shapes the access discipline at the boundary.

When the host SV is the initial-access vector to a hosted payload, 91(3)'s requirement to inform the third-party entity (and the pre-defined-agreements clause) is the operator's procedural obligation; the agreement scope shapes how access between host and payload is constrained.

91(3) explicitly governs hosted-payload contexts; the pre-defined-agreements-with-third-party-entities clause shapes the access discipline at the host-payload boundary.

Docking/OSAM service vehicles are typically third-party-entity contexts; 91(3)'s pre-defined-agreements-with-third-party-entities clause governs the discipline at docking interfaces.

Rideshare neighbors operate under hosted-context-style agreements; 91(3)'s pre-defined-agreements clause governs how cross-payload incidents are coordinated.

91(3)'s pre-defined-agreements-with-third-party-entities clause (for hosted-payload contexts) governs how operators coordinate with the third-party spacecraft owner during compromise scenarios affecting proximity assets.

When payload reconnaissance involves third-party hosted-payload context, 91(3)'s pre-defined-agreements-with-third-party-entities clause governs how payload details are exchanged and protected.