Adding a justification section

ZenCompetition.tex

@@ -36,6 +36,28 @@ To push forward the edge of the known possible means that we compete against phy
 This pentathlon is designed to foster a connection to these principles for each student. The intent of the rules and scoring structure is to encourage collaboration across teams, and across the world. Students compete against the course, not against each other. Each teams accomplishments are intended to be acknowledged on their own merits. We are all competing together against the edge of the known possible.
 \pagebreak
 
+
+{\huge \textbf{Justification of Decisions}}
+\vspace{1cm}
+
+This competition was inspired as an act of schismogenesis in response to FIRST and Vex competitions. The competition structure, team-on-team competition and my-win-requires-your-loss aspects are the motivations for a change. There are elements that are desirable, such as team collaboration, across-team collaboration and high school engineering. 
+
+Why Linux as the runtime? 
+\begin{enumerate}
+\item We want to encourage full-scale compute hardware as the runtime for robot programs. 
+
+\item We want to see tight integration of Control Code, Robot Kinematics, Robot CAD and Robot Simulation. 
+
+\item We want to see fully open source designs that can be composites of many repositories, with runtime self-bootstrapping on new systems. 
+
+\item We want to have students able to open up the robot in an Integrated Robotics Development Environment. 
+
+\item We want to encourage a distributed architecture of compute and edge devices. 
+
+\end{enumerate}
+\pagebreak
+
+
 {\huge \textbf{Overview}}
 \vspace{1cm}
 
@@ -98,7 +120,7 @@ Students will compete in independent categories for recognition awards. These aw
 
 \begin{enumerate}
 	
-\item \textbf{Composition Of Robot:} A robot that competes in the competition must be composed of FFF printed parts made on an approved printer in an approved material with sources provided, Vitamins from the approved list with BoM provided and cloth or paper elements with provided sources. Using the posted price list, all vitamins in a submitted robot must not exceed \$500
+\item \textbf{Composition Of Robot:} A robot that competes in the competition must be composed of FFF printed parts made on an approved printer in an approved material with sources provided, Vitamins from the approved list with BoM provided. Using the posted price list, all vitamins in a submitted robot must not exceed \$500, or from a drag-knife cutter using paper, hardboard or cloth. 
 
 \item \textbf{Open Source Requirement:} All of the sources for the design elements of the robot, the robots control code, all dependent libraries, and all software tools used must be open source at the time of competition. 
 
@@ -110,7 +132,7 @@ Students will compete in independent categories for recognition awards. These aw
 \item \textbf{Eligibility:} High school and Jr High school students affiliated with public schools or not-for-profit private schools. Pay-to-play organizations are explicitly forbidden, all students must be able to join teams without a per student cost borne by the students or their families. 
 
 
-\item \textbf{Team Composition:} Teams can be 1-6 students. Each team member registers an email address with the team submission for automatic contribution allocation. Teams must have at least on adult coach to register for events. Teams may consist of students from any eligible organization and need not all be from a single organization.  
+\item \textbf{Team Composition:} Teams can be 1-6 students. Each team member registers an email address with the team submission for automatic contribution allocation. Teams must have at least one adult coach to register for events. Teams may consist of students from any eligible organization and need not all be from a single organization.  
 
  
 \item \textbf{Attribution} Everything submitted for competition must be attributed accurately. This includes the students code. Big blocks of changes copy and pasted into a students repository will be flagged as a potential attribution violation. If work is done collaboratively then the email of each student that contributed must be included in the commit message. Work done by, or modified by, an ML model may not be claimed as a contribution of the student, and must be attributed to the model that created or modified it. (Note that according to the open source tools rule, only open weight ML models may be used)