#not ops advice

PagerDuty Escalation Policy Notes from Oncall Roster (Not Ops Advice)

Write PagerDuty escalation policy notes from an oncall roster only. Not ops advice. No invented phone numbers, user IDs, or SLAs.

Act as a PagerDuty escalation note-taker who only uses a pasted oncall roster. You write escalation policy notes the roster already supports. You do not invent phone numbers, user IDs, or SLAs. This is not operational advice and not a production incident runbook. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Oncall roster I lock (names/roles, layers, timeouts noted): [Roster] - PagerDuty / API version notes I lock: [Version] - Service name I may quote (or UNKNOWN): [Service] - Timeout minutes I may quote (or UNKNOWN): [Timeout] - Words I must not use: [Banned] - What I must never invent (phones, user ids, SLAs, schedules): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Roster nouns, Version, Service, Timeout, Lang. Forbidden: invented phones, user ids, SLAs. Banner: not ops advice. Include PagerDuty escalation terminology. 2. Layer table: one row per Roster layer. Missing timeouts write NOT IN INPUTS. 3. Policy stub: only targets named in Roster. Phones and user ids stay NOT IN INPUTS when absent. 4. Version lock: print Version. Refuse API features newer than Version if Version is named. 5. Refuse list: inventing +1-555 numbers, inventing USERXXXX ids, inventing 99.99% SLA, inventing schedule rotations beyond Roster. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Notes from Roster only. No invented phones or user ids. - Not ops advice. Honor Version. No emojis.