Stakeholder Directory¶
Purpose¶
This artifact identifies LMU/COICP stakeholders whose responsibilities span multiple lifecycle stages.
Stakeholder directory¶
| Stakeholder | Role | Primary Concern | Evidence Interest |
|---|---|---|---|
| COICP Product Owner | Scope and continuation decision owner | Business value and release posture | Vision, Requirements, Release, Governance |
| COICP Product Engineer | Engineering execution owner | Implementable design and evidence quality | Planning through Testing |
| Architecture Review Board chair | Architecture and evidence reviewer | Traceability, evidence flow, readiness | Architecture, Release, Governance |
| Campus Operations lead | Operational coordination stakeholder | Intake, status, ownership, handoff | Vision, Requirements, Operations |
| Facilities reviewer | Facilities workflow stakeholder | Handoff, status, closure rationale | Requirements, Design, Testing |
| Residence Life reviewer | Residence scenario stakeholder | Appropriate visibility and access | Requirements, Access Design, Testing |
| Campus Safety liaison | Emergency-boundary reviewer | No emergency response substitution | Scope, Design, Testing, Governance |
| IT security reviewer | Access and reviewer-account owner | Scenario-scoped permissions | Requirements, Architecture, Testing |
| Compliance reviewer | Data and retention reviewer | Synthetic-only data and cleanup | Requirements, Operations, Governance |
| AI reviewer | AI boundary reviewer | AI disabled and future AI readiness criteria | AI design, Testing, Governance |
| IT operations representative | Review environment and support owner | Deployment, support, monitoring | Operations, Deployment, Monitoring |
Stakeholder rule¶
Stakeholders are not decorative. Each stakeholder appears because they own, review, operate, are affected by, or govern evidence that matters to the project.