Runtime Contract Drift Audit

Audits source-defined contracts against live runtime copies and reports discrepancies with blocker metadata.

Updated Mar 13, 2026

Search Tags:#workflow #audit #runtime #pipeline #drift #contract #charter

Ready to run

npx skills add https://github.com/JDL440/nfl-eval --skill runtime-contract-drift-audit

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Runtime Contract Drift Audit
Source: https://github.com/JDL440/nfl-eval/tree/main/.squad/skills/runtime-contract-drift-audit
Command: npx skills add https://github.com/JDL440/nfl-eval --skill runtime-contract-drift-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audits and flags divergences between the repository-defined contracts (source defaults) and the live runtime copies loaded by the editor/server, preventing stalls caused by contract drift.

Core Features & Use Cases

Compare source and runtime contracts across dataDir, chartersDir, and skillsDir.
Flag drift and generate actionable remediation guidance for operators.
Provide a consolidated report with revision and artifact context to support quick fixes.

Quick Start

Run the drift audit against a repository with seeded contracts to verify alignment between source and live runtime copies.

Frequently Asked Questions about Runtime Contract Drift Audit

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

FAQPage Schema

How do I detect runtime contract drift between source defaults and live pipeline copies?▼

To detect runtime contract drift, you can audit the alignment between source-defined contracts and live runtime copies. This process validates the active dataDir, resolves chartersDir and skillsDir, and flags divergences in timestamps and contents. You receive a structured report with remediation guidance to prevent pipeline stalls.

What causes pipeline stalls when using seeded charter and skill files in a persistent data directory?▼

Pipeline stalls during runtime are caused by contract drift between repository-defined source defaults and the live runtime copies loaded by the server. Auditing the alignment of these active dataDir, chartersDir, and skillsDir artifacts identifies and flags the divergences causing the stalls.

How do I audit charter and skill file alignment across deployed pipelines?▼

You audit charter and skill file alignment by comparing source and runtime contracts across the active dataDir, chartersDir, and skillsDir. The audit checks timestamp and content consistency, producing a consolidated report with revision and artifact context to support quick fixes.

Can I use a runtime contract drift audit for pipelines with a persistent data directory?▼

Yes, this audit specifically applies to pipelines that seed charter and skill files in a persistent data directory and require alignment to deployed behavior. It resolves the chartersDir and skillsDir to compare live runtime copies against source defaults.

What is the best way to resolve source and runtime contract drift in CI pipelines?▼

The best way to resolve source and runtime contract drift is to run a drift audit that compares timestamps and contents across the active dataDir. It generates a structured report with blocker metadata and actionable remediation guidance for operators to quickly fix deployed behavior.

Why does my deployed runtime behavior mismatch the source-defined contracts?▼

Deployed runtime behavior mismatches source-defined contracts due to contract drift between repository defaults and live runtime copies. An audit resolves this by validating the active dataDir and comparing chartersDir and skillsDir artifacts to produce a structured report with revision context.