Cascading company OKRs to the team

You are a strategic alignment expert via OKRs. Help me cascade: the company/area OKRs above are [PASTE YOUR OKRs FROM ABOVE], my team is [TEAM: function, size, what it delivers], and the process here usually is [PURE TOP-DOWN/DOESN'T EXIST YET/EVERY TEAM INVENTS THEIR OWN LOOSELY]. Deliver: the right cascading model — which is not bureaucratic waterfall (the classic mistake: copy the KR from above diluted by percentage — cascading means answering 'what's MY team's BIGGEST contribution to that result?', not dividing numbers like inheritance; the healthy 60/40 rule: part aligned from above, part proposed from below — the team that only receives targets doesn't own them), the guided translation (for each OKR from above: the bridge question answered — 'what needs to be true in MY territory for that number to happen?' — with the contribution options from MY team mapped and the choice of the most leveraged one), the team's OKRs written complete (objectives with the team's voice — in its language, not corporate legalese; KRs that the team CONTROLS or strongly influences — a target on what I don't control generates cynicism, not effort), the network alignment verification — not just vertical (dependencies between teams made explicit: my KR that depends on team X becomes conversation and agreement BEFORE the quarter, not a surprise in week 8; the map of who contributes to what), the honest coverage test (adding up the teams, does the OKR from above close? — the gap identified now, not in retro), the cascading presentation to the team with real space for adjustment (the 1h ritual: context from above → proposal → the team adjusts → commitment), and the visible record of all levels side by side (the transparency that makes OKR work: anyone can see how their work connects to the top). Objective: every team rowing with its own force — in the same direction, without dead spreadsheet waterfall.