# Named-role and contact collection template

Do not infer or invent people. Complete this table through authorized human
review. Use role mailboxes where appropriate, but identify the accountable
human in the controlled system of record. Do not put private contact details in
public-chain data.

| Mandatory role | Organization | Legal name | Title | Approved contact/channel | Coverage/delegate | Authority boundary | Conflict disclosed? | Evidence ID | Confirmed at |
|---|---|---|---|---|---|---|---|---|---|
| Commercial owner | TBD | TBD | TBD | TBD | TBD | Scope/fees; no deployment authority unless separately granted | TBD | ROLE-ASSIGNMENTS | TBD |
| Authorized signatory | TBD | TBD | TBD | TBD | TBD | Contract signature only within documented authority | TBD | AUTHORIZED-SIGNATORY | TBD |
| Security contact | TBD | TBD | TBD | TBD | TBD | Vulnerability intake and security escalation | TBD | ACTUAL-CONTACTS | TBD |
| Privacy contact | TBD | TBD | TBD | TBD | TBD | Data-map, consent, retention, incident review | TBD | ACTUAL-CONTACTS | TBD |
| Incident commander | TBD | TBD | TBD | TBD | TBD | Incident coordination; no unilateral commercial amendment | TBD | ROLE-ASSIGNMENTS | TBD |
| Support owner | TBD | TBD | TBD | TBD | TBD | SLA intake/reporting | TBD | ROLE-ASSIGNMENTS | TBD |
| Change approver | TBD | TBD | TBD | TBD | TBD | Candidate/scope change approval | TBD | ROLE-ASSIGNMENTS | TBD |

## Collection controls

1. Confirm identity and authority outside this repository.
2. Record consent to use the contact for the stated operational purpose.
3. Record business-hours/time-zone and out-of-hours routing without publishing
   personal phone numbers unnecessarily.
4. Test the security and incident routes before activation; retain timestamped
   evidence.
5. Reconfirm quarterly and on personnel, authority, or channel changes.

Actual assignments, contacts, acceptance, and signatures are external human
blockers until evidence is candidate-bound in the readiness manifest.

