coverify

Extract commitment kernels and score semantic preservation with Jaccard similarity.

1|Updated Mar 12, 2026
One-click install
npx skills add https://github.com/SunrisesIllNeverSee/moses-claw-gov --skill coverify
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: coverify
Source: https://github.com/SunrisesIllNeverSee/moses-claw-gov/tree/main/skills/coverify
Command: npx skills add https://github.com/SunrisesIllNeverSee/moses-claw-gov --skill coverify

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Semantic commitment can drift or be leaked when signals are transformed; CoVerify provides a lightweight instrument to extract and compare the commitment kernel.

Core Features & Use Cases

  • Kernel extraction: Pulls the irreducible commitment kernel from a text signal.
  • Comparison & scoring: Uses Jaccard similarity to quantify preservation and detect leakage.
  • Ghost-token analysis: Identifies cascade-risk leakage patterns and cross-model structural holes.
  • Audit-ready: Supports an input-output ledger and cross-model comparisons for governance validation.
  • Use Case: Validate model swaps and transformation pipelines where preserving intent matters.

Quick Start

Run commitment_verify.py extract "Agents must always verify lineage before executing." to extract the commitment kernel from a sample signal.

Frequently Asked Questions about coverify

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

FAQPage Schema
How do I verify semantic commitment preservation across signal transformations?

To verify semantic commitment preservation, you extract an irreducible commitment kernel from input text and score its Jaccard similarity against the transformed output to detect intent drift or leakage.

What is ghost-token analysis for transformation pipelines?

Ghost-token analysis identifies cascade-risk leakage patterns and cross-model structural holes to validate governance and model swap workflows where preserving original intent is critical.

How do I audit model swaps for semantic leakage and drift?

You audit model swaps by running cross-model comparisons and maintaining an input-output ledger to detect semantic commitment loss, structural holes, or transformation leakage across pipelines.

When do I need commitment kernel extraction for governance validation?

You need commitment kernel extraction when validating governance workflows, model swaps, or transformation pipelines to quantify exactly how much semantic intent is preserved or lost.

Can I use Jaccard similarity to detect structural holes in cross-model comparisons?

Yes, Jaccard similarity quantifies the preservation of semantic commitment across cross-model comparisons, directly highlighting structural holes and cascade-risk leakage patterns in audit workflows.

What are the limitations of using commitment kernels for transformation auditing?

Commitment kernel auditing focuses strictly on quantifying semantic preservation via Jaccard similarity, meaning it detects drift and leakage but does not automatically correct transformation pipeline failures.