/home/techb158/cosmic.abdallabala.com/docs
Edit: /home/techb158/cosmic.abdallabala.com/docs/28-demo-rehearsal-script.md (3618B)
# Demo Rehearsal Script
Date: 2026-07-04
Target duration: 10 to 15 minutes
## Demo objective
Show that COSMIC AI-Risk Dashboard converts a conceptual AI-risk framework into a working software prototype with measurable risk scoring, mitigation tracking, governance gates, project-management integration, reporting, and auditability.
## Demo path
### 1. Introduce the problem, 1 minute
Say:
> AI projects are difficult to manage because risks emerge from data, models, people, governance, and deployment conditions. The dashboard addresses this by making AI project risk measurable and governable.
Show:
- Conference presentation slide 2 or infographic section "Why it matters".
- Dashboard title and overview page.
### 2. Explain the foundation, 1 minute
Say:
> The conceptual foundation comes from the AI governance triangle and AI lifecycle governance. The software design is an operational extension that converts the framework into entities, services, API endpoints, and workflows.
Show:
- UML Class Diagram.
- Use Case Diagram.
- Database Entity Model.
### 3. Show the dashboard overview, 2 minutes
Open:
```text
http://localhost:8090
```
Show:
- Overall risk score.
- Deployment gate status.
- Open risks.
- Mitigation completion.
- Governance dimensions.
Explain:
> The dashboard uses normalized scores so that risk can be compared across projects and phases.
### 4. Demonstrate risk CRUD, 2 minutes
Actions:
1. Open Risk Register.
2. Add a sample risk.
3. Set probability, impact, and detectability.
4. Save the risk.
5. Edit the risk.
6. Delete or keep the risk depending on demo needs.
Say:
> Each risk belongs to a lifecycle phase and governance dimension, which supports traceability from framework to implementation.
### 5. Demonstrate mitigation workflow, 2 minutes
Actions:
1. Open Mitigations.
2. Add or edit a mitigation.
3. Set progress and effectiveness.
4. Add evidence reference.
5. Return to dashboard and show updated residual risk.
Say:
> Mitigation is not only a checklist. It changes residual risk and contributes to deployment readiness.
### 6. Demonstrate deployment gate, 2 minutes
Actions:
1. Open Deployment Gate.
2. Run gate evaluation.
3. Review failed and passed criteria.
4. Add reviewer decision.
5. Show gate history and audit trail.
Say:
> The gate converts measurement into a governance decision. Deployment can be blocked, warned, or allowed based on measurable criteria.
### 7. Demonstrate PM integrations, 1 minute
Actions:
1. Open Integrations.
2. Show Trello, Jira, Asana, and Microsoft Planner.
3. Show simulated sync.
4. Explain OAuth-ready live connector boundary.
Say:
> The system uses a shared adapter layer so the risk model is independent from a specific project-management tool.
### 8. Demonstrate reporting, 1 minute
Actions:
1. Open Reports.
2. Open executive HTML report.
3. Export risk register CSV.
4. Mention full JSON evidence package.
Say:
> Reporting creates submission evidence and supports audit-ready governance review.
### 9. Close with validation, 1 minute
Say:
> The prototype includes tests for the risk engine, storage layer, workflows, integrations, OAuth boundary, reporting, access control, and production hardening. The final submission package freezes the system for evaluation.
## Backup demo path
If live server startup fails, use:
1. Final conference PowerPoint.
2. Infographic image.
3. `SUBMISSION-README.md`.
4. `docs/22-traceability-matrix.md`.
5. `docs/23-testing-evidence.md`.
## Demo commands
```bash
npm install
npm test
npm start
```
Open:
```text
http://localhost:8090
```