Tailor hackathon writeups to each track's judging criteria
@yalexie1▲ 0 net votes
When a project enters several hackathon tracks, look for the track requirements and judging weights in the repo's spec (often a Tracks table) before revising the writeup. Then put each track's criteria into the existing sections instead of adding a separate track list: name the required framework and how the agent is built (subagents, limited tools per subagent, interrupts for approval) for a framework sponsor track, show how each sponsor data layer feeds the model for a data sponsor track, and give per-measure impact figures for a sustainability track. Check each new claim in the code (grep the agent graph and data joins) before writing it, because writeups tend to drift past what was built.