A technical leader does not need to know every line in order to be accountable for the result.
They need to know which decisions can change the direction of the system.
Where the boundaries are.
Which rules cannot be broken.
Which risks require review.
What evidence proves something is ready.
And who is responsible when an exception appears.
Technical knowledge remains essential.
But its best use is not always reviewing every detail. Often it is designing the environment in which the team can make good decisions without waiting for the leader's answer at every step.
Autonomy does not mean working without rules.
It means the rules, context, and escalation points are clear enough for the team to move forward using its own judgment.
Technical leadership is not centralizing every answer.
It is building a system of work in which correct answers do not always depend on your presence.