Skip to main content

Season 2 registrations are open — Chennai · 28 August 2026 and Coimbatore · 25 September 2026.

Register Your Team
Register Your Team

Lock 3 · Prove

GitHub Submission

What evaluators look for in your repository: a README that orients in ninety seconds, commits that tell the real story, and code that matches your claims.

7 minute read · applies to Lock 3

Paired programming: one builder explaining while the other commits work on a laptop.

The repository is evidence

Your GitHub link exists so evaluators can verify what was actually built, by whom, and how. Technical quality carries ten Lock 3 points and the contribution declaration is checked against commit reality. A repository with three commits made the night before submission tells a story — make sure the story your repo tells is the one in your declaration.

The ninety-second README

  • What this is: one paragraph, problem and solution
  • Live link and demo video link at the top
  • Architecture: your one-page diagram, embedded
  • Setup: exact commands to run locally, tested on a clean machine
  • Data and models: what is used, from where, under what licence
  • Team: who built what — matching your contribution declaration
  • Known limitations: same honesty as your submission

Commit hygiene without theatre

Nobody expects enterprise git discipline from a student team. Evaluators do notice: whether commits span the build period or cluster suspiciously, whether messages describe changes, and whether every member’s work is visible. Commit as you build, from each member’s own account.

Secrets and licences

  • No API keys in the repo — use environment variables and a .env.example
  • Respect dataset and model licences; state them in the README
  • If the repo is private, share evaluation access exactly as instructed in the portal
  • Third-party code is fine when attributed; unattributed copying is plagiarism under the rules

Before you submit — the checklist

  • README orients a stranger in ninety seconds
  • Live link and video linked at the top
  • Setup instructions verified on a clean machine
  • No secrets committed; .env.example provided
  • Commits span the build and cover every member
  • Licences stated for data, models and borrowed code

Related guides

All Locks

Responsible AI

The responsible-AI plan Foundry expects: concrete harms analysis, privacy by design, bias testing and human ac...

9 minute read Lock 3 · Prove

Prototype Development

Building a working prototype in a student-realistic window: scope ruthlessly, ship the core loop, and make "wo...

9 minute read Lock 3 · Prove

Demo Video

A demo video that proves function, not production values: structure, honesty and the five minutes that carry y...

6 minute read

Put this guide to work.

The rubric this guide addresses is waiting inside your team’s build journey.

Register Your Team