PLATFORM TEAM CHARTER
Version, approver, and review date: [fill in]

Purpose and users
- Recurring delivery problem: [observed task and current friction]
- Initial users and pilot application team: [names]
- Supported capability and interface: [scope]
- Out of scope: [product logic, unsupported runtimes, other exclusions]

Structure and authority
- Topology: [centralized / federated with shared core]
- Engineering sponsor and reporting line: [name / role]
- Core funding and priority decision-maker: [name / role]
- Product discovery and backlog owner: [name / role]
- Domain extensions, owners, and funding, if any: [list]
- Authority for compatibility and scope disputes: [name / role]

Ownership and operation
- Deployment platform owner and operator: [names; distinguish them]
- Backing-service operators and contact routes: [list]
- Product-service owners and application on-call: [list]
- Security policy owner and control implementers: [names]
- Security exception reviewer and risk acceptor: [names]
- SRE-supported services and acceptance boundaries: [list or none]

Team interactions
- Pilot work and completion criteria: [task / evidence]
- Self-service interfaces and documentation: [locations]
- Routine support channel and support hours: [details]
- Feedback and roadmap review: [cadence / participants]
- Exception request and domain-extension process: [details]

Reliability and escalation
- Platform service objectives and monitoring owner: [details]
- Initial alert recipient and response commitment: [details]
- Incident declaration authority and coordination lead: [names / roles]
- Core, extension, application, and backing-service escalation: [routes]
- Security incident escalation: [route]
- Handoff rule: [named recipient accepts before coordination transfers]
- Recovery procedure and incident follow-up owners: [locations / names]

Pilot evidence and review
- Baseline task, workload, and observation period: [details]
- Success criteria: [self-service completion, manual steps, reliability]
- Developer feedback and unresolved friction: [method]
- Capacity for maintenance, support, and improvement: [assumptions]
- Decision date: [expand / revise / stop]
- Structure review triggers: [persistent domain needs, duplication,
  incompatible interfaces, unclear ownership, unsustainable support]