1. Projects should meaningfully use Motia's core model of Steps and Workflows. Using the Motia CLI and showcasing unified flows that tie together APIs, background jobs, scheduled tasks, events, or AI agents will score higher, since that's the heart of Motia.
2. You must build a new project during the hackathon. Repackaging or lightly modifying an existing project is not allowed.
3. All design elements, code, and assets for your project must be created during the event. You may use third-party tools, frameworks, open-source libraries, public APIs, and publicly available assets such as Creative Commons images, fonts, datasets, or music.
4. Teams can plan and discuss ideas in advance, but coding and design work should start only after the hackathon begins. Written notes, sketches, architecture diagrams, and workflow drafts are allowed before kickoff.
5. Projects must involve building software that runs on Motia as the backend framework. You can mix languages inside one project when it helps your workflow. Hardware components are optional.
6. Teams may consist of 1–4 members.
7. Any intellectual property developed during the hackathon belongs to the team that created it. Teams are encouraged to agree internally on IP ownership, though this is not mandatory.
8. Please treat all participants with respect. Act kindly and professionally. Harassment, discrimination, or exclusionary behavior of any kind will not be tolerated. If you see something concerning, notify an organizer immediately.
9. Failure to follow these rules or the Code of Conduct may result in disqualification.