ADPA is the in-repository policy-to-code bridge for the ICT Governance Framework. All ADPA systematics live in this single product repo alongside RPAS governance, framework documentation, Compliance as Code templates, and the ICT governance web application.
| Property | Value |
|---|---|
| Mode | in-repo (single product repository) |
| Project ID | ADPA-ICT-GOV |
| RPAS binding | governance/rpas/project.binding.json |
| CSR baseline | CSR-42 v2.3.0 |
adpa/
├── project.manifest.json Product manifest and path registry
├── config/
│ └── processor-config.json AI processor routing (PMBOK + ICT templates)
├── systematics/
│ ├── tiers.json Intelligence / orchestration / experience / data
│ └── lifecycle.json Proposal → Decision → Execution stages
├── templates/
│ ├── manifest.json ICT Governance Framework template registry
│ ├── ict-governance/ Ten canonical ADPA document templates
│ └── governance-artifacts/ JSON templates for IaC / CaC generation (seven pillars)
├── schemas/
│ ├── telemetry-entity.schema.json
│ ├── generation-request.schema.json
│ ├── governance-artifact-template.schema.json
│ ├── governance-requirement.schema.json
│ ├── generated-artifact.schema.json
│ └── tenant-artifact-store.schema.json
├── entities/ Telemetry-hydrated entity catalog
├── tenants/ Per-tenant requirements and generated artifacts
├── infrastructure/ Global regional hub registry and network topology
├── translators/ Cloud JSON → IaC/CaC translators (future phase)
├── bridge/
│ └── ict-governance-framework.json
├── runtime/ Future Aspire orchestrator (see README)
└── scripts/
├── generate.js Document generation CLI
├── prioritize-from-telemetry.js
└── validate-project.js
From repository root:
npm run adpa:validate # Validate ADPA project structure
npm run adpa:validate:templates # Validate governance artifact templates + tenant store
npm run adpa:list # List ICT framework templates
npm run adpa:list:artifacts # List governance artifact templates (seven pillars)
npm run adpa:generate:governance-doc -- tenant-contoso-health # Governance DOCX + Markdown
npm run adpa:generate -- policy-alignment --var entityId=tenant-01
npm run adpa:prioritize # Demo telemetry → template queue
npm run governance:validate # RPAS / AEV baseline validation
| Template ID | Framework source |
|---|---|
framework-charter |
ICT Governance Framework |
multi-tenant-governance |
Multi-Cloud Multi-Tenant Framework |
operating-model |
Strategic & Tactical Overview |
target-state |
Target Governance Framework |
policy-alignment |
ICT Governance Policies |
raci-authority |
Roles & Responsibilities |
kpi-catalog |
ICT Governance Metrics |
compliance-as-code-map |
IaC Integration guide |
iso38500-crosswalk |
ISO/IEC 38500 Standards |
zero-trust-assessment |
Zero Trust Maturity Model |
JSON templates under templates/governance-artifacts/ define the LLM pipeline from governance requirement → generated artifact JSON → cloud IaC/CaC. One template per seven-pillar domain:
| Template ID | Pillar | Output type |
|---|---|---|
identity-access-control |
Identity | hybrid |
device-compliance |
Devices | hybrid |
software-supply-chain |
Software | compliance-policy |
network-segmentation |
Network | infrastructure |
data-protection |
Data | hybrid |
security-monitoring |
SecOps | hybrid |
resilience-backup |
Resilience | infrastructure |
Tenant requirements and outputs: adpa/tenants/. See templates/governance-artifacts/README.md.
Outputs are written to generated-documents/ with generation metadata in .adpa-generation.json.
ict-governance-framework enterprise connectors (Sentinel, CASB).adpa/entities/.npm run adpa:prioritize with a telemetry event JSON.npm run adpa:generate.npm run governance:validate, AMD rituals).