fpf-skilltelemetry-verify-compliance

venikman's avatarfrom venikman

Verifies that a telemetry span complies with FPF Discipline-Health (G.12).

⭐0stars🔀0forks📁View on GitHub🕐Updated Jan 10, 2026
[Monitoring]

When & Why to Use This Skill

This Claude skill automates the verification of telemetry spans to ensure full compliance with the FPF Discipline-Health (G.12) standard. By validating 4D completeness and anchor integrity, it helps engineering teams maintain high-quality observability data and 'Lawful Telemetry' records essential for robust system monitoring.

Use Cases

  • Automated Compliance Auditing: Periodically analyze telemetry span batches to identify records that fail G.12 standards, ensuring long-term data health.
  • Observability Debugging: Quickly diagnose missing context in distributed traces by identifying which mandatory FPF anchors (spec, performer, context, or system) are absent.
  • CI/CD Quality Gates: Integrate into testing workflows to verify that new instrumentation in the codebase produces compliant telemetry before it reaches production.
  • Governance Reporting: Generate structured compliance reports to document adherence to internal data discipline and health protocols.
namefpf-skill:telemetry-verify-compliance
descriptionVerifies that a telemetry span complies with FPF Discipline-Health (G.12).
version0.1.0
allowed_tools[]

telemetry/verify-compliance Kernel

Context

This skill acts as a Discipline-Health Checkpoint (G.12). It validates that a given telemetry record (Span) contains the necessary evidence to be considered "Lawful Telemetry".

Instructions

Analyze the provided Span JSON and verify the following invariants:

1. 4D Completeness

Check for the presence of all mandatory FPF Anchors:

  • fpf.spec_ref
  • fpf.performer_ref
  • fpf.context_ref
  • fpf.system_ref

2. Validity Checks

  • Spec Validity: fpf.spec_ref must start with method: or compatible scheme.
  • Context Validity: fpf.context_ref must start with ctx: or U.BoundedContext.

3. Output

Return a structured Compliance Report:

{
  "compliant": boolean,
  "missing_anchors": string[],
  "violations": string[]
}

If compliant is false, violations must list the specific G.12 rules broken.