Axiom#36114 Sponsor us

#36114

An axiom is the point every proof has to start from.

FIRST Tech Challenge · Illinois

The mark

Five curves. One point.

The logo is the org chart. Each line is something the team does, and they only add up to a robot where they cross.

The Axiom team mark
Violet
Design
Cyan
Programming
Green
Outreach
Amber
Competition
Lime
Constitution
White
The team

Subteams

Three lines of work, one robot

Design · CAD

Sketch to competition-legal

Drivetrain, mechanisms, and rebuilding whatever snapped in the third match.

  • PoovendiranCaptain
  • Rishi
  • Ved
Programming

Autonomous and TeleOp

Java in Android Studio. Path following, PIDF, AprilTags for localisation.

  • AarushCaptain
  • Litesh
  • Suld
Outreach

Funding and portfolio

Sponsors, demos, and the engineering portfolio judges actually read.

How we build

The same six steps, every season

The game changes every September. The loop doesn't.

  1. Read the gameScore every path to points before touching a part.
  2. Pick a strategyCommit to an archetype. Say what we're not doing.
  3. Prototype uglyCardboard and zip ties. Find the failure early.
  4. CAD and buildModel it, make it, write down why.
  5. Code and tuneAutonomous first. It's worth the most.
  6. Drive it to deathPractice until the controls stop needing thought.

How we run

We wrote a constitution, and we follow it

What sinks most teams isn't the robot. It's attendance and decisions nobody agreed to.

3captains
3×meetings a week in season
24hnotice before a vote
75%to amend it

Robots

Season one, in progress

2026–27Current

In design

Our first competition robot. Strategy locks the week after kickoff, drivetrain goes first, and this row gets a result next spring.

Building

Contact

Sponsor us, or come build

No experience needed. Show up, follow through, and be willing to be wrong in front of people.