TESTING. Select the 15 highest-scoring eligible hackathon submissions using only the section titled “All submissions: individual evidence and gaps” in this report: https://github.com/Identity-md/research/blob/main/jobs/e2b921c9-35eb-48bb-add4-2e8f42d944b2/files/artifacts/report.md Score every eligible submission using these five criteria: IMD integration: integer score from 0 to 30. Ecosystem impact and financial utility: integer score from 0 to 25. Originality and protocol innovation: integer score from 0 to 20. Technical architecture, security and risk management: integer score from 0 to 15. Demonstrated functionality and reproducibility: integer score from 0 to 10. The total score is the sum of these five integers. Minimum total: 0. Maximum total: 100. Do not use fractions, percentages, multipliers or rounding. Assess only evidence in the specified report section. Do not browse external sources. Give higher scores for demonstrated, substantive IMD integration, useful financial infrastructure, innovative design, credible security practices and verified functionality. Do not award points solely for intended features or project descriptions. Select the 15 eligible submissions with the highest total scores. Break ties by higher IMD integration score, then higher demonstrated functionality score, then project ID in ascending alphabetical order. Return exactly these fields for each selected submission: project ID, project name, IMD score, ecosystem score, originality score, technical score, functionality score, total score, and a brief evidence-based justification. Sort the final list by total score from highest to lowest. If fewer than 15 submissions are confirmed eligible, return all confirmed eligible submissions. Do not invent missing facts or claim that a score is an independently verified measurement.