Spec-Lint Checklist for IMPLEMENTATION_PLAN.md (Fail-Closed)

To validate an implementation plan against safety contracts during PR review, you run an automated spec-lint suite that checks for explicit gate definitions, test mappings, and verifiable artifact paths. This ensures plan governance and prevents unsafe merges.

Split-brain detection in implementation plan governance identifies conflicting thresholds and schedules within a safety plan. It prevents contradictory guidance by enforcing a single PolicyGuard ladder with a clear, non-bypassable chokepoint.

You enforce canonical safety gates by applying lint rules that require precise inputs, comparators, durations, and exit criteria for every gate. This canonicalization ensures all safety checks are explicit and testable.

Yes, you can use automated linting to verify test mapping and artifact freshness in implementation plans. The lint suite ensures every rule has a corresponding test and all required artifacts have explicitly defined freshness paths.

If an implementation plan lacks explicit precedence and chokepoint definitions, the fail-closed spec-lint suite will surface policy violations and block the plan. It requires a single PolicyGuard ladder to prevent bypass behavior.