ce-payload-governance

Validate explanation payload schemas and provenance against ADR-005 and ADR-028 invariants.

78|15|Updated May 1, 2023
One-click install
npx skills add https://github.com/Moffran/calibrated_explanations --skill ce-payload-governance
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ce-payload-governance
Source: https://github.com/Moffran/calibrated_explanations/tree/main/.claude/skills/ce-payload-governance
Command: npx skills add https://github.com/Moffran/calibrated_explanations --skill ce-payload-governance

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validate explanation payload schemas, metadata and provenance fields, and ADR-005 and ADR-028 governance invariants.

Core Features & Use Cases

  • Enforces the v1.0.0 Payload Schema contract for serialized explanations.
  • Verifies governance metadata (provenance and metadata blocks) per ADR-005/028.
  • Supports correct deserialization workflows and safe generation of payloads.

Quick Start

Run the payload validator on a produced explanation payload to confirm adherence to ADR-005 v1.0.0 and ADR-028 governance invariants.

Frequently Asked Questions about ce-payload-governance

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I validate explanation payload schemas for ADR-005 and ADR-028 compliance?

Validate explanation payload schemas by checking required fields like schema_version, task, index, explanation_type, and prediction against v1.0.0 contracts. This ensures serialized and deserialized payloads meet ADR-005 and ADR-028 governance invariants for provenance and metadata blocks.

What governance invariants are required for classification and regression explanation payloads?

Governance invariants for explanation payloads require mandatory provenance and metadata blocks per ADR-005 and ADR-028. The v1.0.0 schema enforces specific fields including schema_version, task, index, explanation_type, and prediction to ensure consistent, auditable payloads.

Does payload validation apply to both serialization and deserialization workflows?

Payload validation applies to both serialization and deserialization workflows to ensure consistent, auditable payloads. Checking schemas and governance invariants during both processes prevents invalid explanation data from entering or leaving the system.

What's the best way to enforce v1.0.0 payload schema contracts for explanation metadata?

Enforce v1.0.0 payload schema contracts by validating mandatory fields such as schema_version, task, index, explanation_type, and prediction. This confirms that provenance and metadata blocks meet ADR-005 and ADR-028 governance requirements for safe generation.

When do I need to validate provenance fields in serialized explanation payloads?

Validate provenance fields in serialized explanation payloads whenever generating or receiving classification and regression explanations. This confirms adherence to ADR-005 and ADR-028 governance invariants, ensuring the metadata blocks remain consistent and auditable.