Task · GCI-0092.01

Add Adaptive, DB O11y and App O11y rows to capability adoption and fix the applied-rules null

Description

GCI-0092 gaps 2, 3 and 4. Point-in-time view rows from inputs the collector already holds; zero new series unless budget.py justifies one.

Acceptance Criteria

Definition of Done

Implementation Plan

Resume after root shared source/compose seam foundation; use measured Adaptive inputs and live-witnessed App/AdaptiveTrace reporting, explicitly unknown DB per-stack attribution, mechanically derive view dependencies.

Implementation Notes

Loop12:2 implementation attempts,0 review-repair rounds. Landed ed5d417714df3e104600fb2c4a0ba4e31cd96a38; publiccompose reds, completeCR0 all9files, independentPASS, cleanprelanding/composed2090passed2skipped12768subtests and CI37347229164 success. Five view-only rows accurately qualify populations/windows, DB adoption remainsunknown despite positive reporting markers, segmented/unknown Adaptive excluded from confident whole-stack assertions. No new metrics/enums/scoring. Resourcecap512->8192 preserves ALL global minimality/sufficiency cases, measured exhaustive derivation21.36s under unchanged9min2GiB guard; old signature-only test adapted only authorizedviewbehavior. Root maturitynullable fix retained. LocalCLI emitted91synthetic view envelopes and actual5rows readback; notlive/browser proof.

Final Summary

Coverage shows configured Adaptive Metrics/Logs and observed Adaptive Traces/App reporting with measured/unknown populations and explicit windows; DB row states unverified adoption/unit contract. Cost overall applied-rule total stays qualified with measured subtotal. Evidence /Users/rob/repos/grafana-cloud-org-insights/codex/loop12-evidence/L-adoption/.

View the source file on GitHub