deletions | additions       diff --git a/future-work-intro.tex b/future-work-intro.tex  index 453bf60..06aee8e 100644  --- a/future-work-intro.tex  +++ b/future-work-intro.tex 
...
In looking for ways to manage and encourage serendipity, we are drawn  to the approach taken by the \emph{design pattern} community  \cite{alexander1999origins}. %%  The essential features of this approach %%  are described below, but we point out straight away that we propose to %%  use design patterns in rather nonstandard fashion. These adaptations %%  to the typical design pattern methodology are proposed to parallel the %%  four themes outlined above. %%  \begin{itemize} %%  \item[(1)] We want to encode our design patterns directly in runnable %%  programs, not just give them to programmers as heuristic guidance. %%  \item[(2)] We want the (automated) programmer to generate new design %%  patterns, not just apply or adapt old ones. %%  \item[(3)] We want our design patterns themselves, working in %%  combination, to contribute to the discovery of new emergent problems %%  and patterns, not just capture the solutions to existing known %%  problems. %%  \item[(4)] We want our design patterns to play an overt role in the %%  dynamical systems they describe. %%  \end{itemize} %%  \citeA{meszaros1998pattern} describe the typical scenario for authors of design  patterns: ``You are an experienced practitioner in your  field. You have noticed that you keep using a certain solution to a