fusion-bicc-drift-remediation

## Copyright (c) 2026, Oracle and/or its affiliates. ## Licensed under the Universal Permissive License v 1.0 as shown at http://oss.oracle.com/licenses/upl # Fusion BICC Drift Remediation Planning Use this skill after drift detection to transform findings into execution-ready remediation actions. ## When to use - Drift reports contain critical/high findings requiring immediate response. - Data Transforms mappings need updates due to schema changes. - AI DP ingestion contracts require type/nullability revisions. - You need a single prioritized action plan for release gating. ## Inputs - `schema_drift_report.json` (optional but recommended) - `data_drift_report.json` (optional but recommended) - Optional remediation policy (`assets/remediation_policy.yaml`) ## Workflow 1. Ingest schema/data drift reports. 2. Normalize findings into a common remediation model. 3. Prioritize by severity (`critical` first). 4. Generate: - machine-readable remediation plan JSON - markdown runbook with immediate critical actions ## Commands ```bash python skills/fusion-bicc-drift-remediation/scripts/generate_remediation_plan.py \ --schema-report ./outputs/schema_drift_report.json \ --data-report ./outputs/data_drift_report.json \ --policy skills/fusion-bicc-drift-remediation/assets/remediation_policy.yaml \ --output-json ./outputs/remediation_plan.json \ --output-md ./outputs/remediation_plan.md # Optional end-to-end wrapper bash skills/fusion-bicc-drift-remediation/scripts/run_drift_pipeline.sh \ --baseline-dir ./inputs/baseline \ --current-dir ./inputs/current \ --out-dir ./outputs ``` ## Output - `remediation_plan.json` with action queue grouped by severity. - `remediation_plan.md` with `Critical Findings & Immediate Actions` section. See `references/remediation-playbook.md` and `references/critical-response-runbook.md`.