ICT-Governance-Framework-Application

Data pillar — classification, DLP ingest (backlog). Use when adding Purview/ Macie-style signals or app-layer DLP. Write data.contract.test.js first.

Network pillar — segmentation, exposure scanning (backlog). Use when adding topology or port-exposure features. Write network.contract.test.js first.

Resilience engine — Git-to-cloud DR, RTO/RPO measurement. Use before recovery orchestrator or DR field changes. Write resilience.contract.test.js first.

Software supply chain pillar — CASB catalog, shadow IT, SBOM gating. Use before CASB ingest or app catalog changes. Write software.contract.test.js first.

SecOps engine — Sentinel ingest, incident lifecycle, FAIR trigger, SecOps UI. Use before incident API, SLA, or CISO dashboard changes. Write secops.contract.test.js first.

Devices pillar — multi-cloud asset register, DR posture, incident binding. Use before asset sync, CASB correlation, or register UI changes. Write devices.contract.test.js first.

Identity pillar (JIT elevation, Break Glass, RBAC). Use before changing auth, privileged access, or break-glass flows. Write identity.contract.test.js first.

Contract-first delivery for the ICT Governance Framework — write Jest contract tests and read the pillar SKILL.md before implementing a seven-pillar feature. Use when starting a new pillar module, sprint item, or NIST gate remediation.

Run and unblock npm run verify:post-feature for the ICT Governance Framework — pre-flight checks, API/DB prerequisites, VB-CP rollback expectations, and troubleshooting. Use before commit, after pillar work, when regression fails, or when the user asks to run the post-feature quality gate.