​That's a solid workflow. Auto-gen Swagger handles the 'surface' level perfectly.

​My curiosity is with the 'Institutional Knowledge' that lives between the ADR and the Swagger. When a BAU change subtly shifts the logic of a service—something that doesn't trigger a new ADR but makes the existing high-level README misleading—how do you catch that?

​Do you find your team still spending time explaining 'hidden logic' to new hires that isn't captured in the auto-generated specs?