One route to a four-eyes exemption

Four-eyes answers three questions for engineers creating a repository.

• A repository with a production environment, a production deploy pipeline, or access to production data is production from its first commit, launched or not.
• A repository that is never used in production requests a four-eyes exemption through one ticket, with manager and director approval and an attestation.
• A decision table sends each repository to review or to the exemption route. When unsure, treat the repository as production and ask an Engineering Navigator.

When it doesn’t fit separates exemptions from exception ADRs. References lists the Payward policy behind the attestation.