Making changing assumptions explicit during development

Requirements change all the time. What often doesn’t change explicitly are the assumptions behind them.

An API detail shifts, a dependency appears, and everyone adapts — but there’s no clear signal that the rules changed. I’m exploring whether making assumptions and “contracts” between roles (analysis → backend → frontend → tests) explicit would help, or if this just adds overhead.

Curious if this resonates, or how teams handle this today.