Task · SKT-0073

Classify every standalone Datadog host capture family before further implementation

Description

The standalone host artifact observes 281 families but only the example family is implemented. A per-family evidence verdict is required before honest breadth work.

Acceptance Criteria

Definition of Done

Implementation Plan

L4 proposes the verdict in scratch; root verifies complete coverage and rules, integrates JSON and records the outcome.

Implementation Notes

Root independently verified all 281 unique families and all 300 envelope semantics and placements against the immutable host artifact, with gauge missing temporality represented as empty string per existing verdict. Counts: 1 declaration-backed, 0 implemented fixtures, 155 fixture candidates, 125 Agent descriptors needed. All 31 shared-name differences are Kubernetes-only implementations; the 75 host network candidates still require source-grounded mechanics before implementation. Proposed JSON applied unchanged.

Landed verdict in 0ac777b5fd87c14e836d496402844aa556968eea. Root verified every family and all 300 native shapes against the immutable host artifact. JSON digest 4a0ca98bff12a9663ac5ee7951bb80113b73a414b5aac150fed41c96ab462ffc. Root just check passed with the verdict present; just dump shows unchanged OTLP metric inventory. just gen, unit tests and CodeRabbit were skipped for this JSON documentation-only change; no generated schema input changed.

Final Summary

Completed at 0ac777b5fd87c14e836d496402844aa556968eea: 281 families classified as 1 declaration-backed, 0 implemented fixtures, 155 fixture candidates and 125 descriptor-needed. All 31 shared-name divergences are explicit Kubernetes-only implementations. The 75 host-only system.net candidates need value sourcing before any implementation. No host breadth emission or corpus shape change. Evidence: codex/scratch/wave-2026-09-18/l4/evidence.md and l4-root-validation.txt.

View the source file on GitHub