S2 — Who’s Who

This segment maps the key actors in the Anthropic–customer relationship and the broader legal and governance environment. It is designed as a table-setter for the more detailed scenarios and acceptance matrices later in the pack.

What this page does

Identifies the main internal and external stakeholders (counsel, product, risk).
Clarifies Anthropic’s role versus the customer’s role across deployment stages.
Connects individual roles to the tools and templates in S5/S6.

1. Who is in the conversation?

Use this section when you need a fast, counsel-readable map of who is usually in the room for Anthropic matters that touch on product liability, foreseeable misuse, privacy, or safety. The goal is not to be exhaustive, but to make it easier to see where questions and duties naturally land.

Core Anthropic stakeholders

Anthropic Legal / Policy. Leads on contractual allocation of risk, negotiation of terms, and interpretation of Anthropic’s governance posture in concrete matters.
Product and Engineering. Owns how models and safety features are actually exposed in products and integrations, including controls relevant to foreseeable misuse.
Safety, Security, and Risk teams. Own system-level safety analyses, red-teaming, incident response, and security controls that backstop Anthropic’s commitments (for example, those expressed in RSP v2.2 and ASL tiers).
Trust & Safety / Support. Interacts with customers and end users when incidents, misuse, or edge cases are reported, and feeds learning back into product and policy.

Customer-side stakeholders

Customer Counsel. Brings the customer’s view on product liability, regulation, and internal risk appetite; often the primary partner for Anthropic Legal.
Data Protection / Privacy leads. Focus on data flows, retention, and regulatory obligations (for example, DPOs or privacy counsel).
Security / Risk / Compliance. Evaluate how Anthropic’s systems fit into the customer’s internal controls, incident response, and risk management frameworks.
Product and technical owners. Decide how models are integrated into the customer’s workflows and what guardrails or overlays they add on their side.

2. Role splits across the lifecycle

The same stakeholders do different work at different points in the lifecycle of a deal or deployment. This section gives a quick map of how responsibilities tend to fall at Pre-Sign, At-Sign, and Post-Sign.

Pre-Sign

Anthropic Legal / Policy. Explains Anthropic’s governance posture (including RSP/ASL), proposes contractual allocations of risk, and flags scenarios that may need bespoke safeguards.
Customer Counsel. Tests whether the proposed posture and allocations are acceptable in light of the customer’s regulatory environment and internal policies.
Product / Technical teams (both sides). Clarify the intended use cases, user populations, and integration surface, which drive later risk analysis.

At-Sign

Anthropic Legal. Finalises terms, including disclaimers, use restrictions, and responsibilities for monitoring and incident handling.
Customer Counsel and Risk. Confirm that the resulting allocations and controls fit the customer’s internal approval processes (for example, risk committee sign-off).
Technical owners. Commit to specific deployment architectures and controls that will be implemented as the contract goes live.

Post-Sign

Anthropic Safety / Support. Monitor for incidents and misuse reports, and execute on incident response and mitigation duties described in the terms and governance posture.
Customer Product / Risk / Compliance. Monitor how the system is actually used in practice, including adherence to internal policies and external obligations.
Both sides’ counsel. Re-enter the conversation when changes in capability, use cases, or the regulatory environment require updates to terms or safeguards.