A growing project can reach the point where one founder cannot settle every consequential question, while a vote of every contributor would be cumbersome. A steering council concentrates final authority in a small group. It can set direction, resolve difficult disputes, and delegate ordinary decisions to people closer to the work.

Python places this authority in an elected five-person council with defined powers and procedures. The significant feature is not the number five. It is that the source of authority, scope of responsibility, and means of replacing council members are made explicit.

Small enough to act, visible enough to challenge

A public-data project might elect a council from its experienced contributors and let specialist teams manage releases and documentation. The council would become involved when a decision crosses those domains or changes the project's overall commitments.

That can distribute the burden previously held by a founder, but it creates a new center of influence. If only established contributors can vote, newer users and people affected by the project may still lack a formal voice. A council can also become a bottleneck if every disagreement is escalated to it. Publishing decisions and maintaining clear delegation boundaries make it easier to distinguish strategic stewardship from routine interference. Rotation and removal rules matter because collegial leadership is still leadership with power.

Real cases