constraint-check

Evidence-based compliance auditing reads conversation history and tool-call records to verify that mandatory workflow constraints were actually followed. It checks temporal ordering across invoked skills to confirm required steps occurred rather than just trusting compliance claims.

A hard-gate violation is a blocking failure indicating a mandatory step was skipped, while a warning-level constraint miss notes a softer rule was broken. This classification separates blocking issues from minor misses to focus remediation efforts appropriately.

Multi-skill compliance review reads skill definitions and conversation evidence to evaluate every invoked skill, not just the orchestrator. It verifies temporal ordering of tool-calls and test-first discipline across all invoked skills to catch hidden violations that slip past single-skill checks.

Yes, compliance auditing applies to build, team, audit, and manual session reviews. It checks approval steps, test ordering, and tool-call discipline across invoked skills to verify that validation gates were followed in practice during manual reviews.

Run a compliance audit on the build session to classify violations and emit a remediation-focused report. It summarizes blocking hard-gate failures versus warning-level misses with supporting evidence from the conversation history to guide clear corrective actions.