Meta

Status

• 2026-03-XX: started drafting. Not ready for general consumption.

Purpose

This is a component-focused view on our operational readiness which feeds up to 202503 FOC GA Operational Readiness Review. It is intended to help capture the current operational fitness of a component so we can properly assess our operational health and any risks we’re taking as we move to GA. We’re seeking to get answers to questions like:

• What are the likely things to fail?
• If they fail, how do we know?
• If they fail, what do we do about it?
• If they fail, how/where to communicate?

This is not intended to be the durable place for operational information about this component. That should live in FOC Operational Excellence, in a subpage, or someone else (but linked from there). This is a pre-GA snapshot.

Scope

• PDP Explorer UI
• PDP Subgraph

Failure Modes and Risks

<aside>

What are the risks and failures modes we want leadership to be aware of “eyes wide open” so they are making an informed decision about us launching? Think especially about single points of failures, processes that rely on “best intentions”, etc.

Severity:

• sev2: requires oncall engagement, even outside of business hours.
• sev2.5: top priority during business hours. Trumps everything else, including meeting.
• sev3: top priority during business hours for anyone “oncall”, outside of higher severity items or team meetings. These items should generally trump general feature/cycle work. </aside>

Untitled

Communication

<aside>

We’re particularly reliant on being able to talk with users and hear from them in case where we don’t have good monitoring.

</aside>