Runtime Contract Drift Audit

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.

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.

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.

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.

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.

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.