validation-authority

name	validation-authority
description	Treat upstream validators as authoritative. Align local config to them. Use when validation fails unexpectedly, before modifying validator behavior, or when tempted to change upstream tool code.
license	MIT
metadata	{"version":"1.0.0","source":"Session 366 retrospective","id":"Validation-Authority-001"}

Validation Authority

When integrating external validators (PSScriptAnalyzer, markdownlint, ESLint, etc.), respect upstream defaults. Modify local configuration to match upstream behavior. Do not modify upstream tool code.

Triggers

Activate when:

• Validation fails unexpectedly
• Before modifying validator behavior or configuration
• When tempted to change upstream tool source code
• When adding a new external validator to the project
• When suppressing validator warnings without rationale

Decision Tree

Validation failure occurred
        |
        v
Is the validator upstream (external tool)?
        |               |
       YES              NO (local/custom)
        |               |
        v               v
Modify LOCAL config   Modify tool as needed
to align with tool    (you own the code)
        |
        v
Document override rationale
in config comments

Process

1. Classify the validator: Determine if the tool is upstream (external) or local (project-owned).
2. Identify the conflict: Find the specific rule or default causing the failure.