harness-adr-write

name	harness-adr-write
description	Write ADRs for harness boundaries, provider choices, dependency exceptions, and enforcement changes
metadata	{"type":"Playbook","origin":"harness-engineering/ch15","helpful":0,"harmful":0,"status":"active"}

Harness ADR Write

When to use

• A layer rule needs an exception
• Provider implementation changes
• A layer is split, merged, or renamed
• CI enforcement changes severity

Rules

1. Put ADRs under docs/adr/NNNN-slug.md.
2. Include Status, Context, Decision, and Consequences.
3. Include rejected alternatives when the choice is non-obvious.
4. Link ADRs from dependency-cruiser/ESLint rule comments when relevant.
5. Give temporary exceptions a sunset date.

Checklist

• Status / Context / Decision / Consequences are present
• Opposing option and rejection reason are recorded
• Enforcement rule and ADR link to each other
• Sunset is present for exceptions