added risks to proposal outline

NEWPROPOSAL/SHORTPROP.tex

@@ -1303,6 +1303,85 @@ Complete deep-\zx compiler stack with open\\
 \end{center}
 
 \e
+
+
+
+\paragraph{Critical risks for implementation}
+\label{sec:crit-risks-impl}
+
+
+\REM{Describe any critical risks, relating to project implementation, that
+the stated project's objectives may not be achieved. Detail any risk
+mitigation measures.\textbf{Please provide a table with critical risks
+  identified and mitigating actions (template provided).}
+}
+
+
+The project is overall quite high-risk, in the sense that what we
+propose is in the most part entirely novel, and might fail.  The
+rewards for success would be correspondingly great.  However, we have
+designed the project to survive the failure of many (or even most) of
+its tasks and still deliver value.
+
+We mix low and high risk activities.  Success in low
+risk activities (\ref{task:trans1}, \ref{task:basic-opt}, \ref{task:ECC},
+%\ref{task:axioms}, THIS IS NOT REAALY LOW RISK
+\ref{task:circuit-model}, \ref{task:mbqc-model})
+will still deliver significant progress towards our overall objective.
+\oldt{\ref{wp:theory} is the most critical; here we mitigate the risk by
+(i) developing experience on easier objectives before addressing more
+demanding ones and (ii) consulting our board of advisors to foresee
+problems.  Due to its high dependence on other tasks, we consider
+\ref{wp:usefulstuff} to be highest risk.}\TODOb{This doesn't seem quite up-to-date, also see below}
+
+
+
+\begin{center}
+  \begin{tabular}{|p{0.25\textwidth}|c|c|p{0.4\textwidth}|}
+    \textbf{Description of risk} 
+    & \textbf{Likelihood}
+    & \textbf{WPs involved}
+    & \textbf{Proposed mitigation measures}\\\hline
+%    
+Can't hire suitable post-docs&
+Medium&
+All&
+While we have already identified several suitable candidates for each
+role, the investigators also collectively supervise a large body of PhD
+students and post-docs who could be channelled to the project.
+\\\hline
+%    
+NQIT or Grenoble machine info unavailable or not detailed enough&
+Low&
+\ref{wp:usefulstuff}&
+\oldt{(i) We have members of the consortium from NQIT, and letters of
+support from DiCarlo who agrees to help.  (ii) We can approach other
+members of our board of advisors, or other friendly
+experimentalists. (iii) We can target an more abstract model of the
+machine} \\\hline
+%    
+Some desired technique or algorithm isn't found&   
+High&
+All&
+All tasks where this is a risk have been structured as a collection of
+related goals; if some part doesn't succeed then the finished system
+will be will have fewer features, or worse performance.  However it's
+very unlikely that an entire task will fail in a way that jeopardises
+the project. \\\hline
+%    
+Software integration issues&
+Medium&
+All&
+(i) We will establish a common API in \ref{del:earlyapi} to allow
+loose coupling of the software components (ii) We appoint the most
+experienced software developer in the  consortium (Valiron) to act as ``integration tzar'' and ensure
+the global design is good. (iii) As noted above, we will integrate
+often and deliver new features more than once a year.  
+\\\hline
+  \end{tabular}
+\end{center}
+
+
 %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
 
 \newpage