Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/moradoadrian/carneroDev/llms.txt

Use this file to discover all available pages before exploring further.

Carnero.Dev is built on a commitment to a transparent, constructive, and high-quality competition. Every team participates under the same conditions, and every project is judged against the same objective criteria. The rules below exist to protect the integrity of the event, ensure fairness across all participants, and create an environment where genuine innovation can thrive. Please read them in full before registering — by submitting your team’s registration, you confirm your acceptance of each point.

​
Eligibility

To participate in Carnero.Dev, all team members must meet the following requirements:
  • Active university students enrolled in a programme related to Information and Communication Technologies (TICs), Software Engineering, Mechatronics, Computer Systems, or any comparable technical field
  • Forming part of a team of 1 to 4 members — solo participation is explicitly allowed
  • Each team member must arrive at the venue with their own laptop, chargers, power strips, adapters, and any physical or hardware components their prototype requires — the organisers do not supply individual equipment

​
Core Rules

  1. Teams must be composed of 1 to 4 members actively enrolled in a TICs or related programme.
  2. All code — software and hardware firmware alike — must be written from scratch beginning at the official hackathon kickoff: Friday, October 16 at 11:00 AM. No work done before this moment is permitted.
  3. Pre-built projects, finished MVPs, or templates adapted from previous hackathons are strictly prohibited. Every line of code submitted must originate during the 36-hour window.
  4. AI tools (such as GitHub Copilot, ChatGPT, or equivalent) may be used to assist with debugging, code acceleration, and research — they may not be used to generate the entire solution or substitute the team’s original engineering effort.
  5. All projects must be hosted in a public GitHub repository carrying an Open Source or MIT license. Teams are expected to commit frequently throughout the 36-hour period to provide a transparent, verifiable development timeline.
  6. A functional, interactive demo must be presented live to the judge panel. Static mockups, wireframes, or slide-only presentations do not qualify for a technical score.
  7. All teams must deliver their final pitch on stage to be eligible for scoring and feedback. Teams that do not present will not receive a grade.
  8. Zero tolerance for misconduct. Harassment, discrimination, offensive language, or any form of technical sabotage directed at other teams, organisers, or mentors results in immediate disqualification from the event.
Any evidence of pre-built software, code lifted from a previous project, or plagiarism of another team’s work will result in an immediate 0% on the technical rubric and may lead to full disqualification. Judges and mentors will review commit histories and actively compare solutions.

​
Delivery Milestones

All teams are required to participate in each checkpoint below. Missing a milestone impacts your mentorship access and may affect your eligibility to present at the final stage.
1

Milestone 1 — Physical Registration & Workspace Setup

Friday, October 16 · 8:00 AM – 9:30 AMCheck in at the venue, claim your team’s workspace, verify your network connectivity, and collect your smart accreditation badges. This is the moment to get settled, test hardware, and prepare your environment before hacking begins.
2

Milestone 2 — Idea Validation (Checkpoint 1)

Friday, October 16 · 6:00 PM – 7:30 PMEach team gets a 3-minute round with their assigned mentors to present and validate the viability of their idea. Mentors will offer critical feedback, help correct technical scope, and confirm the team is on a feasible path before the heavy development phase begins.
3

Milestone 3 — Mid-Point Code Demo (Checkpoint 2)

Saturday, October 17 · 11:00 AM – 1:00 PMTeams present real, demonstrable progress to the mentor-judges. This means functional backend endpoints, working database connections, or physical circuit integrations — not slides. The mid-point demo gives judges early insight into your technical trajectory.
4

Milestone 4 — Repository Freeze

Sunday, October 18 · 8:00 AMAll GitHub branches are locked at this time. No commits pushed after 8:00 AM on Sunday will be accepted or considered by judges. Make sure your final code, README, and documentation are committed and pushed before the freeze.

​
Allowed Technologies

There are no absolute restrictions on languages, frameworks, or database engines — teams are free to use any stack that best serves their project. The following technologies are recommended by the organisers for their balance of power and speed under time pressure:
  • Frontend / Markup: HTML, CSS, JavaScript
  • Backend Runtimes: Node.js, Python, Go
  • Frontend Frameworks: React, Astro, Svelte
  • Mobile: Flutter, React Native
  • Databases: PostgreSQL, MongoDB
  • Hardware / IoT: ESP32, Arduino IDE
  • Version Control: Git, GitHub

Build docs developers (and LLMs) love

Get started for freeTalk to us