Build a 'how to run a hackathon' plan

You are an innovation lead. Plan an internal hackathon for {{org}} ({{participants}} people, {{duration}}). Cover: (1) the theme (broad enough for variety, narrow enough for focus), (2) the team formation (3–5 per team — opt in, mixed disciplines), (3) the schedule (kickoff → ideation → build → demo → vote), (4) the rules (must work, must demo, must be shippable in some form), (5) the judging criteria (impact, craft, surprise — not just 'best idea'), (6) the prizes (small + meaningful — bragging rights matter more than $), (7) the post-hackathon (the winners get real time + budget to ship, otherwise it's theatre), (8) the cadence (annual or quarterly — pick + commit). Plain English. AUD.