adr-workflow

To enforce an ADR process for architectural changes, you direct users through drafting, reviewing, and accepting Architecture Decision Records before any implementation begins, preventing unauthorized or unreviewed code from being written.

The ADR workflow for Athena schema changes is a process that ensures proposed modifications follow proper documentation, drafting, and review stages, ultimately requiring an accepted ADR before allowing implementation.

To draft a new Architecture Decision Record in Nygard format, you start the process by creating a draft title, ensuring the subsequent documentation follows house rules and tracks status through Draft, Review, and Accepted stages.

No, you cannot implement code changes without an accepted ADR, because the workflow bars unauthorized code by strictly enforcing that an Architecture Decision Record reaches Accepted status before any implementation begins.

A limitation of relying on an ADR workflow for change management is that it bars implementation until the ADR process is fully accepted, which can delay urgent schema or architectural changes requiring immediate deployment.