Architect

To plan a safe schema migration across multiple repositories, you need architecture guidance that defines contract impacts, identifies operational risks, and outlines rollout constraints before implementation begins. This ensures downstream engineers apply changes without breaking runtime behavior.

An architecture review for API contract changes is required when a request crosses repository boundaries, introduces new interface constraints, or carries operational risk that necessitates design tradeoffs and migration planning prior to writing code.

Documenting design tradeoffs for operational risk involves proposing the smallest valid approach, explicitly stating assumptions, and flagging only blocking questions when information is missing, which provides clear migration and operational impact notes for engineers.

Reviewing cross-repo design impacts involves analyzing where interface boundaries will change, which existing contracts are affected, and generating a scoped design recommendation with migration paths to prevent breaking established behavior.

Architecture guidance for schema changes does not include code implementation, but instead provides tradeoff-driven recommendations, scoped design approaches, and operational impact notes to safely direct downstream engineering efforts.