The original title is "Two Doors, One Gate: Navigating Governance Beyond EDD"

Short summary

Separate 'awareness' tools (guidance that relies on developer choice) from 'governance' tools (structural enforcement) when scaling AI-assisted development. Repository-level governance should be uniform and inescapable; personal scaffolding should shrink as developers demonstrate judgment. Credible governance is earned through visible accomplishment, not granted by title.

• •Conflating onboarding guardrails with governance creates friction for experienced developers while failing to protect newer ones
• •Separate governance (repository-bound, uniform, enforced structurally) from scaffolding (personal, skill-calibrated, earned)
• •Make advancement paths visible and credible: developers' track records on actual work determine what guardrails apply to them

Generated with AI, which can make mistakes.