Hackathon/Project Submission
AIRA'S 2035 • Time-Gated Submission Portal

PROJECT SUBMISSION

“Discover tomorrow's problem today. Build the solution.”

Project submissions for the Aira International Hackathon are strictly time-gated. Ensure your Project Report PDF, public GitHub repository, and demo video walkthrough are prepared for submission during the official window.

Submission Architecture

4-Step Submission Process

Follow these simple steps to ensure your project is properly evaluated by the judges.

STEP 01

Discover & Build

Finalize your 2035 problem identification, evidence, and software prototype. Verify all code runs cleanly with simulated hardware where applicable.

STEP 02

Prepare Your Report

Compile one clean, structured PDF answering the 6 core 2035 discovery questions, architecture diagrams, screenshots, and member contributions.

STEP 03

Prepare Your Links

Ensure your public GitHub repo has a clean README setup guide and your 3–5 min demo video is uploaded to Google Drive or YouTube with view permissions.

STEP 04

Submit Via Official Form

Submit your Team ID, Project Details, Report PDF, and URLs through the centralized AIRA Google Form during the active submission window.

Pre-Flight Inspection

“Before You Submit” Checklist

Verify all items before opening the form
Valid Team ID (e.g. AGT-T-XXXXX from your registration confirmation)
Correct registered Team Name & Team Leader Email
Final Project Report PDF answering the 6 core 2035 questions
Public GitHub Repository Link with README setup instructions
Demo Video Link (Google Drive / YouTube — Anyone with link can view)
Project Title, 2035 Problem Statement & Tech Stack Summary
All member contributions documented and verified
Confirmed permissions: No private or restricted links
Duplicate Submission Policy: Only ONE final submission is permitted per registered team. Your Team ID serves as the primary key. If you make an error, do not submit another form; contact the AIRA team via the official WhatsApp channel or support email for corrections.

Deliverable Specifications

What Judges Will Evaluate (40% Problem Discovery + 60% Solution)

Ensure each of your three primary assets adheres strictly to the guidelines below.

Deliverable 1

Project Report PDF

Upload a single compiled PDF file via the Google Form. It must answer the 6 core 2035 discovery questions and include system architecture and screenshots.

Required 17 PDF Sections:
1. Team Name & Official Team ID
2. Team Member Names & Individual Contributions
3. Project Title & Preferred Domain
4. What Changes by 2035? (Future Scenario Anchor)
5. The Discovered 2035 Problem (Novel, Plausible, Significant)
6. Grounding Evidence vs. 2035 Future Assumptions
7. Who Will Be Affected? (Target Audience & Ecosystems)
8. Why Existing Solutions Are Insufficient
9. Proposed Technological Solution & Innovation Factor
10. System Architecture & Workflow Diagram
11. Technologies Used & Tech Stack Breakdown
12. Software Prototype Implementation & Hardware Simulation
13. UI/UX Screenshots & Working Walkthrough
14. Results, Evaluation & Output Metrics
15. Technical Challenges Faced & Future Roadmap
16. Public GitHub Repository URL Link
17. Demo Video Walkthrough Link & Team Declaration
• Format: PDF only • Single document • Maximum clarity
Deliverable 2

GitHub Repository Link

Provide the link to your team's public GitHub repository containing the complete working software prototype.

Public VisibilityJudges must be able to view and clone the repo without requesting permissions.
Meaningful README.mdInclude project description, 2035 problem insight, prerequisites, and setup instructions.
Active Commit HistoryEnsure genuine commit history by registered team members during 30–31 October 2026.
• Format: https://github.com/username/repo
Deliverable 3

Demo Video Link

Host your video on Google Drive or YouTube and submit the accessible link.

Duration: 3–5 MinutesConcise walkthrough explaining problem, evidence, architecture, and live prototype.
All Team Members PresentAll registered members must explain their contributions in the video.
Critical Permission SettingEnsure Google Drive is set to “Anyone with the link can view” or YouTube is Unlisted/Public.
• DO NOT upload raw video files to AIRA website directly.
Official Intake Structure

What the Google Form Asks

The Google Form is streamlined into 4 clear sections to take less than 5 minutes to submit.

Section 1: Team Identification
  • Team ID (Required — e.g. AGT-T-XXXXX)
  • Team Name (Required)
  • Team Leader Name & Email (Required)
  • Team Member 2 Name (if applicable)
  • Team Member 3 Name (if applicable)
Section 2: Project & 2035 Problem
  • Project Title (Required)
  • 2035 Predicted Problem Statement (Required)
  • Summary & Innovation Factor (Required)
  • Technologies Used / Tech Stack (Required)
  • Preferred Domain (AI, Biotech, Climate, Cyber, etc.)
Section 3: Project Submission
  • Project Report PDF File Upload (Required)
  • GitHub Repository URL Link (Required)
  • Demo Video Link (Drive / YouTube URL) (Required)
  • Live Deployment URL (Optional)
Section 4: Declaration

Mandatory confirmation checkbox:
“I confirm that the submitted project has been developed by our registered hackathon team and that the information provided is accurate.”