SPIKE Prime

Prime Team Manager

Everything the team lends out, locks down and runs

One place for the SPIKE Prime kits, the robots built from them, the world locks those robots trust before they drive, and every scored run. A lock is tied to the build block it was set against — change that block and the lock goes stale.

Loading from the prime-team database…

1 · Kits

Who has what, where it lives, and when it is due back.

Book a kit in or out

Sends to the kit-checkout flow at POST /api/kits/checkout.

2 · Robots

Each robot tracks the build block it is on and the program version loaded into the hub.

3 · World locks

The stored heading a robot trusts before it drives. Locks past 5° of drift, or set against a block that has since changed, need setting again.

Record or verify a lock

Sends to the lock-checkout flow at POST /api/locks/verify.

4 · Runs

Every run is logged against the lock it used, so a bad score can be traced back to a drifting lock.

Log a run

Sends to the log-run flow at POST /api/runs. It warns you when the lock used was unverified or drifting.

5 · Weekly digest

What the team has to fix before the next practice: kits out, locks to re-set, kits in maintenance.

Reads the team-digest flow at GET /api/digest.