u0577-observability-regression-sentinel

name	u0577-observability-regression-sentinel
description	Operate the "Observability Regression Sentinel" capability in production for workflows. Use when mission execution explicitly requires this capability and outcomes must be reproducible, policy-gated, and handoff-ready.

Observability Regression Sentinel

Why This Skill Exists

We need this skill because decisions are only as good as the quality and visibility of data. This specific skill prevents unnoticed quality drift after updates.

When To Use

Use this skill when the request explicitly needs "Observability Regression Sentinel" outcomes in the Data Quality and Observability domain.

Step-by-Step Implementation Guide

1. Define the scope and success metrics for Observability Regression Sentinel, including at least three measurable KPIs tied to data drift and blind spots.
2. Design and version the input/output contract for freshness, drift, schema health, and telemetry coverage, then add schema validation and failure-mode handling.
3. Implement the core capability using baseline-delta detection, and produce regression watchlists with deterministic scoring.
4. Integrate the skill into swarm orchestration: task routing, approval gates, retry strategy, and rollback controls.
5. Add unit, integration, and simulation tests that explicitly cover data drift and blind spots, then run regression baselines.
6. Deploy behind a feature flag, monitor telemetry/alerts for two release cycles, and iterate thresholds based on observed outcomes.

Deterministic Workflow Notes

• Core method: baseline-delta detection
• Archetype: detection-guard
• Routing tag: data-quality-and-observability:detection-guard

Input Contract

• freshness (signal, source=upstream, required=true)
• drift (signal, source=upstream, required=true)
• (signal, source=upstream, required=true)