adding competition structure

ZenCompetition.tex

@@ -72,6 +72,29 @@
 
 \item \textbf{Performance:} Before proceeding into the obstacle course, the robot will be judged on a 90 second animation intended to hype up the crowd. At each save-point through the course another 90 second animation will be required. 
 
+\item \textbf{Eligibility:} High school and Jr High school students affiliated with public schools or not for profit organizations. 
+
+ \pagebreak
+
+{\huge \textbf{Competition structure}}
+
+The competition will be held over the same weekend by all teems wishing to compete. 
+
+Teams will register with the completion central ranking server and may submit early if they so choose. Early submissions with novel code elements may be picked up by other teams, increasing the likelihood the team that posts early gets recognition for design contributions award.
+
+All teams that compete in the code portion must have at least on hardware submission. Multiple code teams may use a single hardware entry. A code entry may be used on more than one hardware entry. 
+
+Hardware only teams may compete for the design award. They must demonstrate that the design works with an existing software release, or that they have developed and released a working software stack by performing well in the obstacle course. 
+
+Performance only teams may compete so long as the animations and costume can be demonstrated to still work within the obstacle course. 
+
+All teams that wish to compete for top prizes must compete over the competition weekend. All robots source must be posted and tagged by the provided time the day before competition. 
+
+Competition consists of the judges running the tagged code against the student provided robot, connected to the judges station's network. The judge will run the tagged code in a standard execution environment. Students code must work as a self contained system, or bootstrap components as they are needed. Judges station will have access to the internet during practice run to ensure bootstrapping. Student downloads are limited to 8gb of total used disk space. The student provided software will have a competition.groovy file that will perform then entire task of animation, course navigation and stopping at the end to press the button. Animation audio will play through the station computer. 
+
+Each team in the competition must perform some portion of the obstacle course to be counted for judging. All runs of the course are recorded for the instant runnoff judging. Judging for objective measures such ad distance and timme will be judged instantly. Performance and design contribution judging will be performed over the following weeks. Finalists will be invited to submit a new animation for second round judging at a central event. The finalists will be judged and awarded at that time. 
+
+