| Description | Why it’s important | Weight (low, medium, high) | |
|---|---|---|---|
| Problem Clarity & Relevance | Clearly defines a real problem; strong relevance to local community needs. | This hackathon is guided by regenerative principles that prioritize local context and community relevance. | HIGH |
| Planned Cardano Integration | Clear plan for how Cardano tools, infrastructure, or standards will be used (even if not implemented yet). | The hackathon is funded by the Cardano community, with a strong priority placed on building on Cardano. | HIGH |
| Business Viability / Sustainability | Practicality, scalability, user adoption potential, sustainability model. | We want to support business ideas that are self sustaining | HIGH |
| Proposed Solution & Innovation | Creativity, originality, and clarity of the proposed solution or concept. | Creativity does not always equate to the best project; often, the simplest solutions are the most effective. | MEDIUM |
| Community Value & Impact | Strong local benefit; meaningful value for community stakeholders. | Ethos of hackathon - build up the community, empower locally The ethos of the hackathon is to build community and empower local participants. | MEDIUM |
| Team Collaboration & Execution | Teamwork, clarity of roles, participation, ability to execute. | Need to be able to build a strong team if they don’t have all roles already should be open to add Teams should be able to build strong, well-rounded teams and remain open to adding missing roles where needed. | MEDIUM |
| Hub’s participation throughout the Hackathon | Did the team communicate and submit deliverables on time? | Low priority but we would like to show appreciation for the projects who followed the process and supported other teams…Also shows level of commitment (how easy will they be to work with going forward through incubation While a low priority, we value teams that followed the process and actively supported other teams, as this reflects commitment and collaboration during incubation. | LOW |
| Technical Approach / Prototype Quality | Technical feasibility, prototype quality (if present), architecture thinking, technical direction. | Although it is very important to be technically feasible at this phase it is not important to have a working prototype – we will support on that throughout incubation period | LOW |
Last updated on