FM / docs

/home/techb158/cosmic-risk.abdallabala.com/docs/

/home/techb158/cosmic-risk.abdallabala.com/docs

Name	Size	Mode	Actions
00-design-study.md	3678	0644	edit dl rm
01-uml-class-diagram.puml	11869	0644	edit dl rm
02-use-case-diagram.puml	3763	0644	edit dl rm
03-sequence-diagrams.puml	9732	0644	edit dl rm
04-database-entity-model.mmd	7051	0644	edit dl rm
05-database-schema.sql	13372	0644	edit dl rm
06-diagram-preview.html	5021	0644	edit dl rm
07-design-checklist.md	3256	0644	edit dl rm
08-step-2-storage-layer.md	5325	0644	edit dl rm
09-step-3-risk-crud-ui.md	3380	0644	edit dl rm
10-step-4-mitigation-workflow.md	3996	0644	edit dl rm
11-step-5-deployment-gate-workflow.md	2292	0644	edit dl rm
12-step-6-multi-pm-integration.md	3770	0644	edit dl rm
13-step-6-1-microsoft-planner-integration.md	2335	0644	edit dl rm
14-step-7-reporting-export.md	4158	0644	edit dl rm
15-step-7-1-oauth-live-connectors.md	4545	0644	edit dl rm
16-step-8-user-roles-access-control.md	3297	0644	edit dl rm
17-step-9-production-deployment-security.md	4228	0644	edit dl rm
18-step-10-final-academic-submission.md	3199	0644	edit dl rm
19-final-report-draft.md	6814	0644	edit dl rm
20-instructor-submission-checklist.md	3639	0644	edit dl rm
21-demo-script.md	3948	0644	edit dl rm
22-traceability-matrix.md	4847	0644	edit dl rm
23-testing-evidence.md	2961	0644	edit dl rm
24-evaluation-rubric-mapping.md	2910	0644	edit dl rm
25-final-deployment-runbook.md	3214	0644	edit dl rm
26-known-limitations-and-future-work.md	2632	0644	edit dl rm
27-final-qa-checklist.md	2893	0644	edit dl rm
28-demo-rehearsal-script.md	3618	0644	edit dl rm
29-submission-freeze-report.md	2769	0644	edit dl rm
30-final-known-issues.md	1876	0644	edit dl rm
31-saas-rebuild-implementation.md	2573	0644	edit dl rm
application-documentation.md	27515	0644	edit dl rm
conversation-log.md	18503	0644	edit dl rm
dashboard-spec.md	3691	0644	edit dl rm
database-guide.md	37826	0644	edit dl rm
development-summary.md	7070	0644	edit dl rm
github-architecture.svg	6288	0644	edit dl rm
integration-pull-push-plan.md	7384	0644	edit dl rm

Edit: /home/techb158/cosmic-risk.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
```

cmd: