+\subsubsection{On Deck}
+\color{red} The
+table below lists the actions which may be taken when an
+instruction arrives on deck:
+
+\begin{center}
+\def\side#1{\begin{sideways}\parbox{15mm}{#1}\end{sideways}}
+\begin{tabular}{|r|ccccc|cccccc|}\hline
+%&\multicolumn{10}{c}{Predicate}&\\
+%&\multicolumn{10}{c}{True}&\\\hline
+&\multicolumn{5}{c}{Outer-Looping} &\multicolumn{5}{c}{One-Shot}&\\
+&\multicolumn{5}{c}{{\tt (OS=0)}} &\multicolumn{5}{c}{{\tt (OS=1)}}&\\
+&\side{{\tt move}}
+&\side{{\tt literal}}
+&\side{{\tt setFlags}}
+&\side{{\tt setInner}}
+&\side{{\tt setOuter}}
+&\side{{\tt move}}
+&\side{{\tt literal}}
+&\side{{\tt setFlags}}
+&\side{{\tt setInner}}
+&\side{{\tt setOuter}}
+&
+\\\hline
+Wait for hatch sealed & + & + & + & + & + & & & & & & \\
+Fill IF0 w/ copy of self & + & + & + & + & + & & & & & & \\\hline
+Request arbiter & P+$\star$ & & & & & P+$\star$ & & & & & \\
+Potentially torpedoable & P+$\star$ & & & & & P+$\star$ & & & & & \\\hline
+Execute & P+ & P+& P+& P+& P+ & ? & ? & ? & ? & P & \\
+Inner-looping & P+ & & & & ? & P+ & & & & ? & \\
+\hline
+\end{tabular}
+
+\begin{tabular}{|r|l|}\hline
++ & Only if {\tt OLC>0} (ie {\tt OLC} is positive) \\
+P & Only if predicate is true \\
+P+ & Only if predicate is true and {\tt OLC>0} \\
+P+$\star$ & Only if predicate is true and {\tt OLC>0} and {\tt I=1} and one of {\tt Ti},{\tt Di},{\tt Do} true. \\
+? & to discuss \\\hline
+\end{tabular}
+\end{center}
+
+\subsubsection{\color{red}Torpedo\color{black}}
+
+\color{red}
+There is a small fifo (not shown) before the latch marked
+``Instruction Horn''; after the {\tt tail} instruction seals the
+hatch, any subsequent instructions will queue up in this fifo until
+the hatch is unsealed. This is typically used as storage for a ``loop
+epilogue'' -- a sequence of instructions to be executed after a
+torpedo arrives or the outer loop counter expires.
+
+Each dock has a fourth connection to the switch fabric (not shown),
+called its {\it torpedo destination}. Anything (even a token) sent to
+this destination is treated as a torpedo. Note that because this is a
+distinct destination, instructions or data queued up in the other
+destination fifos will not prevent a torpedo from occuring.
+
+When a data item or token arrives at the torpedo destination, it lies
+there in wait until On Deck holds a potentially torpedoable
+instruction (see previous table). Once this is the case, the torpedo
+causes the inner and outer loop counters to be set to zero (and
+therefore also unseals the hatch).\footnote{it is unspecified whether
+ the torpedoed instruction is requeued or not; this may or may not
+ occur, nondeterministically. It is the programmer's responsibility
+ to ensure that the program behaves the same whether this happens or
+ not. We think that this will not matter in most situations.}
+
+\color{black}
+
+