compliance-guard

You validate API contracts against architecture governance rules by evaluating artifacts against a provided rules catalog to produce rule-level compliance verdicts with evidence. The process classifies constraints, conventions, and policies, aggregating results into a traceable compliance report.

Policy enforcement for engineering artifacts is the process of checking specs, data models, and ADRs against an explicit ruleset. It classifies constraints as blocking, conventions as warnings, and policies as fails unless a valid waiver reference is provided.

You generate an auditable compliance report for ADR review by validating the architecture decision record against a YAML rule catalog. The output includes rule-level evidence, blocking failures, warnings, and any not-verifiable items suitable for governance approval workflows.

Yes, you can use a custom rule catalog for compliance validation by providing your own YAML ruleset. The validation process evaluates each provided rule without inventing new ones, ensuring all checks map directly to your defined constraints, conventions, and policies.

Waiver traceability during governance gates works by allowing policies to pass with a fail verdict unless an appropriate waiver reference is provided. This ensures exceptions to blocking constraints are explicitly documented and auditable within the final compliance report.