-
Notifications
You must be signed in to change notification settings - Fork 0
epic E2: source provenance and versioned controls #12
Copy link
Copy link
Open
Labels
area/dataSource registry, ingestion, normalization, and historySource registry, ingestion, normalization, and historyphase/1-mvpRequired or evaluated for the Phase 1 service MVPRequired or evaluated for the Phase 1 service MVPpriority/nowRefine or execute now for the current sprint/critical pathRefine or execute now for the current sprint/critical pathrisk/complianceLegal/compliance interpretation or control riskLegal/compliance interpretation or control risktype/epicEnd-to-end capability spanning multiple storiesEnd-to-end capability spanning multiple stories
Milestone
Description
Activity
Metadata
Metadata
Assignees
Labels
area/dataSource registry, ingestion, normalization, and historySource registry, ingestion, normalization, and historyphase/1-mvpRequired or evaluated for the Phase 1 service MVPRequired or evaluated for the Phase 1 service MVPpriority/nowRefine or execute now for the current sprint/critical pathRefine or execute now for the current sprint/critical pathrisk/complianceLegal/compliance interpretation or control riskLegal/compliance interpretation or control risktype/epicEnd-to-end capability spanning multiple storiesEnd-to-end capability spanning multiple stories
Outcome: source operators can register, retrieve, quarantine, hash, validate, diff, approve, activate, roll back, and rescreen from versioned evidence.
Scope: TS-201 through TS-206; existing spikes #2, #3 and #4.
Requirements: FR-SRC-001 through FR-SRC-007 and FR-ADM-001.
Exit evidence:
Risks: format/access/licence/history changes, parser failures, false deletion, incomplete legal scope.