FM / docs

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

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

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

Edit: /home/techb158/cosmic.abdallabala.com/docs/13-step-6-1-microsoft-planner-integration.md (2335B)

# Step 6.1: Microsoft Planner Integration

## Purpose

This step adds Microsoft Planner as a fourth project-management application in the shared COSMIC AI-Risk integration layer. Trello, Jira, Asana, and Microsoft Planner now use the same adapter interface.

## Planner mapping

| COSMIC AI-Risk object | Microsoft Planner object | Notes |
|---|---|---|
| Project | Plan | A plan belongs to a Microsoft 365 group in the live Microsoft Graph model. |
| Risk | Task | Each COSMIC risk can be represented as one Planner task. |
| Lifecycle phase | Bucket or progress state | The prototype stores this as external status. |
| Risk score | Category, description, or task details | The prototype stores this in field mapping metadata. |
| Mitigation action | Checklist item | Mitigations can be represented as checklist items on the task. |
| Evidence | Task reference or checklist evidence | Evidence is modeled as a traceable external reference. |
| Owner | Assignee | Live Graph integration would require Microsoft 365 user IDs. |
| Due date | Task due date | The prototype keeps the mapping metadata. |

## Implementation changes

- Added `Microsoft Planner` to `SUPPORTED_PM_PROVIDERS`.
- Added a seeded Microsoft Planner integration in `data/database.json`.
- Added provider-specific status mapping.
- Updated UI text and summary cards from three providers to four providers.
- Updated OpenAPI provider enums.
- Updated UML, use case, sequence, ER, and SQL artifacts.
- Updated API and integration workflow tests.

## Current boundary

The prototype does not call live Microsoft Graph. It creates deterministic local mappings and sync history. This is intentional for the academic prototype because it avoids OAuth configuration and keeps instructor testing simple.

## Production note

A live Microsoft Planner connector should use Microsoft Graph OAuth. Planner tasks are created inside plans, and plans are commonly contained by Microsoft 365 groups. Live update and delete requests must handle Microsoft Graph Planner etags.

## Acceptance criteria

- `/api/integration-providers` returns Microsoft Planner.
- `/api/projects/{projectId}/integrations` returns four integrations.
- Planner sync creates one external mapping per COSMIC risk.
- Planner mappings use `Task` as the external work-item type.
- Tests pass with `npm test`.

# Step 6.1: Microsoft Planner Integration ## Purpose This step adds Microsoft Planner as a fourth project-management application in the shared COSMIC AI-Risk integration layer. Trello, Jira, Asana, and Microsoft Planner now use the same adapter interface. ## Planner mapping | COSMIC AI-Risk object | Microsoft Planner object | Notes | |---|---|---| | Project | Plan | A plan belongs to a Microsoft 365 group in the live Microsoft Graph model. | | Risk | Task | Each COSMIC risk can be represented as one Planner task. | | Lifecycle phase | Bucket or progress state | The prototype stores this as external status. | | Risk score | Category, description, or task details | The prototype stores this in field mapping metadata. | | Mitigation action | Checklist item | Mitigations can be represented as checklist items on the task. | | Evidence | Task reference or checklist evidence | Evidence is modeled as a traceable external reference. | | Owner | Assignee | Live Graph integration would require Microsoft 365 user IDs. | | Due date | Task due date | The prototype keeps the mapping metadata. | ## Implementation changes - Added `Microsoft Planner` to `SUPPORTED_PM_PROVIDERS`. - Added a seeded Microsoft Planner integration in `data/database.json`. - Added provider-specific status mapping. - Updated UI text and summary cards from three providers to four providers. - Updated OpenAPI provider enums. - Updated UML, use case, sequence, ER, and SQL artifacts. - Updated API and integration workflow tests. ## Current boundary The prototype does not call live Microsoft Graph. It creates deterministic local mappings and sync history. This is intentional for the academic prototype because it avoids OAuth configuration and keeps instructor testing simple. ## Production note A live Microsoft Planner connector should use Microsoft Graph OAuth. Planner tasks are created inside plans, and plans are commonly contained by Microsoft 365 groups. Live update and delete requests must handle Microsoft Graph Planner etags. ## Acceptance criteria - `/api/integration-providers` returns Microsoft Planner. - `/api/projects/{projectId}/integrations` returns four integrations. - Planner sync creates one external mapping per COSMIC risk. - Planner mappings use `Task` as the external work-item type. - Tests pass with `npm test`.