/home/techb158/trellopowerup.abdallabala.com/docs
NameSizeModeActions
00-design-study.md36780644editdlrm
01-uml-class-diagram.puml118690644editdlrm
02-use-case-diagram.puml37630644editdlrm
03-sequence-diagrams.puml97320644editdlrm
04-database-entity-model.mmd70510644editdlrm
05-database-schema.sql133720644editdlrm
06-diagram-preview.html50210644editdlrm
07-design-checklist.md32560644editdlrm
08-step-2-storage-layer.md53250644editdlrm
09-step-3-risk-crud-ui.md33800644editdlrm
10-step-4-mitigation-workflow.md39960644editdlrm
11-step-5-deployment-gate-workflow.md22920644editdlrm
12-step-6-multi-pm-integration.md37700644editdlrm
13-step-6-1-microsoft-planner-integration.md23350644editdlrm
14-step-7-reporting-export.md41580644editdlrm
15-step-7-1-oauth-live-connectors.md45450644editdlrm
16-step-8-user-roles-access-control.md32970644editdlrm
17-step-9-production-deployment-security.md42280644editdlrm
18-step-10-final-academic-submission.md31990644editdlrm
19-final-report-draft.md68140644editdlrm
20-instructor-submission-checklist.md36390644editdlrm
21-demo-script.md39480644editdlrm
22-traceability-matrix.md48470644editdlrm
23-testing-evidence.md29610644editdlrm
24-evaluation-rubric-mapping.md29100644editdlrm
25-final-deployment-runbook.md32140644editdlrm
26-known-limitations-and-future-work.md26320644editdlrm
27-final-qa-checklist.md28930644editdlrm
28-demo-rehearsal-script.md36180644editdlrm
29-submission-freeze-report.md27690644editdlrm
30-final-known-issues.md18760644editdlrm
31-trello-powerup-implementation-guide.md76080644editdlrm
32-vps-deployment-guide.md36970644editdlrm
dashboard-spec.md36910644editdlrm
methodology-mapping.md24710644editdlrm
next-implementation-step.md13040644editdlrm
trello-admin-setup.md21750644editdlrm
Edit: /home/techb158/trellopowerup.abdallabala.com/docs/10-step-4-mitigation-workflow.md (3996B)
# Step 4: Mitigation Workflow Management ## Purpose Step 4 turns mitigation actions into a first-class workflow. Earlier versions allowed a mitigation to be added from the risk register. This step adds a dedicated mitigation page and backend support for managing mitigation progress, effectiveness, evidence, and residual-risk impact. ## Source alignment The source deck defines COSMIC-Risk as a measurable AI project risk framework. It also identifies the need for ISO-style indicators, risk analysis software, API architecture, and integration with project-management tools. The detailed mitigation workflow implemented here is a software design extension that operationalizes those concepts. ## Implemented use cases | Use case | Status | |---|---| | View mitigation dashboard | Implemented | | Search mitigation actions | Implemented | | Filter mitigation actions by status | Implemented | | Create mitigation action | Implemented | | Edit mitigation action | Implemented | | Mark mitigation as done | Implemented | | Delete mitigation action | Implemented | | Link evidence to mitigation | Implemented | | Recalculate residual risk after mitigation change | Implemented | | Reflect mitigation progress in deployment gate | Implemented | ## UI changes New navigation item: ```text Mitigations ``` New dashboard section: ```text viewMitigations ``` The page includes: - Mitigation actions summary. - Average mitigation progress. - Average mitigation effectiveness. - Overdue mitigation count. - Mitigation table with linked risk, owner, due date, progress, effectiveness, evidence, and residual-risk impact. ## Backend changes New or extended repository methods: | Method | Purpose | |---|---| | listMitigations(projectId) | Return enriched project mitigation list | | getMitigation(mitigationId) | Read one mitigation action | | createMitigation(riskId, payload) | Create mitigation and optional evidence | | updateMitigation(mitigationId, payload) | Update mitigation and optional evidence | | deleteMitigation(mitigationId) | Delete mitigation and linked mitigation evidence | | addEvidenceToMitigation(mitigationId, payload) | Add evidence to a mitigation action | ## API changes | Method | Endpoint | Purpose | |---|---|---| | GET | /api/projects/{projectId}/mitigations | List project mitigations | | POST | /api/risks/{riskId}/mitigations | Create mitigation action | | GET | /api/mitigations/{mitigationId} | Read one mitigation action | | PATCH | /api/mitigations/{mitigationId} | Update mitigation action | | DELETE | /api/mitigations/{mitigationId} | Delete mitigation action | | POST | /api/mitigations/{mitigationId}/evidence | Add mitigation evidence | ## Database model change The `evidence_artifacts` entity now supports an optional mitigation link: ```sql mitigation_id TEXT REFERENCES mitigation_actions(id) ON DELETE SET NULL ``` This keeps evidence usable at both levels: 1. Risk-level evidence. 2. Mitigation-level evidence. ## Residual-risk logic The mitigation workflow feeds the existing residual-risk calculation: ```text Residual score = normalized score x (1 - mitigation progress x mitigation effectiveness) ``` The project dashboard recalculates after each mitigation create, update, mark done, or delete action. ## Validation Added test file: ```text tests/mitigation-workflow.test.js ``` The test verifies: - Mitigation creation. - Evidence creation. - Mitigation update. - Residual-risk reduction. - Mitigation list enrichment. - Mitigation deletion. Run: ```bash npm test ``` Expected output: ```text All COSMIC AI-Risk engine tests passed. All COSMIC AI-Risk storage layer tests passed. All COSMIC AI-Risk mitigation workflow tests passed. All COSMIC AI-Risk API workflow tests passed. ``` ## Next recommended step Step 5 should implement deployment gate workflow controls: - Reviewer decision form. - Gate history page. - Gate criteria override notes. - Approval, rejection, or acceptance workflow. - Audit trail view.