additionalBrackets property
Additional bracket axes for detectors whose runtimeVerified evidence covers more than one independent observable. The top-level bracket fields (bracketStableId, bracketThreshold, bracketUnit, etc.) describe the canonical bracket; each entry in additionalBrackets describes a parallel axis with its own threshold, capture triad, and validation rules.
Use cases:
PlatformChannelDetectorruns both a frequency axis (calls/sec) and a cumulative-duration axis (ms/window) on the same stableId. Each axis is bracketed independently; both must pass for the raise to stand.NetworkMonitorDetectorcovers five families (slow_request,large_response,request_frequency,http_error_spike,high_frequency_same_path); a future raise of multiple families declares one canonical bracket plus one BracketSpec per additional family.
Audit invariants enforced when non-null:
- Empty list rejected — encode missing additional axes as null, not
[]. An empty list signals an in-progress edit or copy-paste error. - Each spec has its own three-capture triad, validated by
ProfileCaptureSchema.validateBracketindependently. The audit gate calls validateBracket once per spec (top-level + each entry). - Cross-spec uniqueness on
(stableId, severityLabel, argKey)tuples spans the union of {top-level, additionalBrackets*}. Top-level is treated as logical spec #0; additionalBracketsias spec #(i+1). Two specs with the same (stableId, severityLabel, argKey) are rejected — the same trace eventsleuth.issue.<stableId>.<severity>would be double-counted across brackets with the same observed-axis arg. Two specs that differ on argKey are accepted (multi-axis pattern). Two specs that differ on severityLabel are also accepted — they validate disjoint trace events (warning vs critical), which is the canonical tier-stack raise (e.g.heavy_compute.warning+heavy_compute.criticalbrackets on a single family). - Every runtimeVerified family declared via perStableIdTier must
be covered either by the canonical bracket (via coveredThresholds)
OR by some BracketSpec whose BracketSpec.coveredThresholds
contains the matching
<stableId>.<severity>entry. Audit fails when a perStableIdTier raise is unmoored from any bracket evidence. - All capture paths (top-level profileCapturePaths +
additionalBrackets*.profileCapturePaths) are walked by the orphan-capture-audit so a stray file undertest/validation/captures/not referenced from any spec is rejected.
Default null preserves v0.19.7 behavior — every existing detector keeps a single canonical bracket and the field is implicit.
Implementation
final List<BracketSpec>? additionalBrackets;