Mechanism-by-design themes
| Theme | Primary DI layer | Comparator type | Common artifacts | Typical KPI | CMO exemplar (1-line) | Limitation |
|---|---|---|---|---|---|---|
| Observability/Assurance as the Verification Layer | Processes/Pipelines (CI/CD), Human-Ops (SRE) | SLO threshold | Logs, dashboards, lineage/audit | SLO adherence, audit completeness | In a multi-region context (C), SLO-bound monitoring (M) sustains SLO adherence (O) with dashboards and audit entries | Some records lack explicit KPI or a co-located assurance locus |
| Carbon/Energy SLOs in SRE Practice | Human-Ops (SRE) | SLO threshold | Dashboards, SLO docs, lineage/audit | SLO adherence, error budget | Under regulatory pressure (C), SRE runbooks (M) keep carbon/energy SLOs within target (O), evidenced by dashboards and SLO docs | Comparator/telemetry details are partially reported in several cases |
| Energy-Aware Workload Placement & Autoscaling | Compute/Orchestration (runtime) | SLO threshold, runtime controller | telemetry logs, dashboards, drift report | SLO adherence, bounded drift | With rich telemetry and edge density (C), runtime controllers (M) maintain energy/carbon SLOs (O), evidenced by logs and drift report | Fails where telemetry is sparse or setpoints are unspecified |
| Policy-as-Code Gates in CI/CD for ESG Controls | Processes/Pipelines (CI/CD) | Pre-commit/CI gate, policy-as-code rule | Policy repo, gate logs, lineage/audit | Gate pass/fail, policy conformance | In CI, policy rules (M) block non-conformant builds (O), verified by policy repo ID and gate pass/fail logs | Small-n, several mentions lack gate logs or KPI |
| Theme | Primary DI layer | Comparator type | Common artifacts | Typical KPI | CMO exemplar (1-line) | Limitation |
|---|---|---|---|---|---|---|
| Observability/Assurance as the Verification Layer | Processes/Pipelines (CI/CD), Human-Ops (SRE) | SLO threshold | Logs, dashboards, lineage/audit | SLO adherence, audit completeness | In a multi-region context (C), SLO-bound monitoring (M) sustains SLO adherence (O) with dashboards and audit entries | Some records lack explicit KPI or a co-located assurance locus |
| Carbon/Energy SLOs in SRE Practice | Human-Ops (SRE) | SLO threshold | Dashboards, SLO docs, lineage/audit | SLO adherence, error budget | Under regulatory pressure (C), SRE runbooks (M) keep carbon/energy SLOs within target (O), evidenced by dashboards and SLO docs | Comparator/telemetry details are partially reported in several cases |
| Energy-Aware Workload Placement & Autoscaling | Compute/Orchestration (runtime) | SLO threshold, runtime controller | telemetry logs, dashboards, drift report | SLO adherence, bounded drift | With rich telemetry and edge density (C), runtime controllers (M) maintain energy/carbon SLOs (O), evidenced by logs and drift report | Fails where telemetry is sparse or setpoints are unspecified |
| Policy-as-Code Gates in CI/CD for ESG Controls | Processes/Pipelines (CI/CD) | Pre-commit/CI gate, policy-as-code rule | Policy repo, gate logs, lineage/audit | Gate pass/fail, policy conformance | In CI, policy rules (M) block non-conformant builds (O), verified by policy repo ID and gate pass/fail logs | Small-n, several mentions lack gate logs or KPI |
Note(s): Comparator terms are controlled: SLO threshold, pre-commit/CI gate, admission/runtime rule, policy-as-code rule. Artifacts are drawn from: logs, dashboards, lineage/audit, drift report, (model/data) card, policy repo, config snapshot. KPIs include: gate pass/fail, SLO adherence, policy conformance, audit completeness, bounded drift. When multiple layers appear, the primary DI layer is assigned to the layer where the comparator executes (e.g. SLO to SRE, CI gate to CI/CD, runtime to Compute/Orchestration)
Sharing content requires targeting cookies to be enabled. Please update your cookie preferences to use this feature.