Relay
77.1A shared incident timeline three responders can write to at once without stepping on each other.
First team challenge. Three builders, one repository, 30 minutes.
Cabins compete as a unit. The scoring rubric is unchanged, but coordination overhead is real and the judges know it โ expect execution scores to run lower than a solo day.
Challenge closed
3 submissions ยท 3 scored
Results
Scored by 3 judges against the standard daily rubric, blended with community votes.
Community choice
SortieSubmission gallery
Every submission from this challenge, including what shipped and what didn't.
A shared incident timeline three responders can write to at once without stepping on each other.
Splits a large refactor into parallel agent tasks and merges the results.
A live audience-reaction layer for technical talks, built to be readable from the back of a room.
The brief
Judging
The default rubric for daily challenges. Weights are tuned so that a working, honest, well-explained build beats an ambitious broken one.
| OriginalityIs the idea fresh, or a well-worn demo with a new coat of paint? | 15% |
| ExecutionDoes it actually run? How much of the promise is real? | 20% |
| UsefulnessWould a real person use this? Is the problem worth solving? | 15% |
| Technical QualitySound architecture and sensible tradeoffs for a 30-minute build. | 12% |
| Design & UXClarity, polish, and accessibility of the interface. | 12% |
| Effective Use of AIIs AI load-bearing here, or decorative? | 13% |
| Completion in TimeHow much shipped inside the clock, per the disclosure fields. | 8% |
| Demo & PresentationDid the live demo land? Was the process explained well? | 5% |