Add intro & draft structure

contents/1-intro.tex

 \section{Introduction}
 \label{sec:intro}
 
-Introduction.
+This document is \gls{ESCAPE} project deliverable \docNumber{}: “\docTitle{}” \autocite{ESCAPE-GA}.
+
+\Pgls{ESAP} is the primary deliverable of \gls{ESCAPE} \Acrlong{WP} 5 (\Acrshort{WP}5\glsunset{WP}).
+A fundamentally web-based application, it serves a key part of the interface between the services delivered by \gls{ESCAPE} and the scientific community, providing mechanisms by which users can discover, access, and analyze the data, workflows, and services which the \glspl{ESFRI} affiliated with \gls{ESCAPE}, as well as other research infrastructures and a diverse range of other service providers, publish to the \gls{EOSC}.
+
+At the time of writing, the funded \gls{ESCAPE} project is reaching its conclusion.
+Substantial development effort has been invested into \gls{ESAP} and the surrounding ecosystem of software and services.
+At the same time, we do not believe that the development of \gls{ESAP} itself is coming to an end: the technologies developed, and the workflows pioneered, have shown real potential for widespread future application.
+This makes it an opportune moment to step back and assess the current state of and future plans for \gls{ESAP}.
+What have we achieved within the context of \gls{ESCAPE} so far?
+How can we build upon these achievements in the future?
+It is that analysis which is undertaken in this document.
+
+At the mid-point of \gls{ESCAPE}, we undertook a substantial analysis of the performance of the \gls{ESAP} system as it then stood \autocite{ESCAPE-D5.3}.
+This document builds upon that earlier work to describe the sum total of the work achieved across the full duration of the project.
+Specifically, we will consider:
+
+\begin{enumerate}
+
+\item{To what extent the prototype meets the requirements which were specified in \citetitle{ESCAPE-D5.2} \autocite{ESCAPE-D5.2}?}
+
+\item{To what extent the prototype meets the needs currently being expressed by the \gls{ESCAPE}-affiliated \glspl{ESFRI}, as expressed through the use cases collated by the project?}
+
+\item{To what extent have \gls{ESFRI} or other services have been successfully integrated with \gls{ESAP}?}
+
+\item{What are the future plans for \gls{ESAP} development as the \gls{ESCAPE} project comes to its conclusion?}
+
+\end{enumerate}
+
+Broadly, this report is structured in two parts.
+In the first part, we provide essential context by describing the \gls{ESAP} system.
+In \cref{sec:vision} we the overall vision for the \gls{ESAP} system: what did we set out to build?
+\Cref{sec:current} takes that further by describing what is currently available: if one were to deploy and operate an \gls{ESAP} system today, what would it consist of?
+
+The second part of this document moves on to asses how successful that vision and implementation have been in addressing user --- and in particular \gls{ESFRI} --- needs.
+In particular, \cref{sec:requirements} tabulates the documented requirements and compares them to delivered product; \cref{sec:usecases} discusses how \pgls{ESAP} relates to all the use cases collected by the \gls{ESCAPE} project; and \cref{sec:esfri} describes current \gls{ESFRI} engagement with the platform..
+
+Finally, we consider potential future enhancements in \cref{sec:future}, and provide a summary of the results of this analysis is presented in \cref{sec:conclusions}.

contents/2-vision.tex

+\section{The \glsentrytext{ESAP} Vision}
+\label{sec:vision}

contents/3-current.tex

+\section{Current Capabilities}
+\label{sec:current}

contents/4-requirements.tex

+\section{Requirements Analysis}
+\label{sec:requirements}

contents/5-usecases.tex

+\section{Use Case Analysis}
+\label{sec:usecases}

contents/6-esfri.tex

+\section{ESFRI Users}
+\label{sec:esfri}

contents/7-future.tex

+\section{Future Prospects}
+\label{sec:future}

contents/8-conclusions.tex

+\section{Conclusions}
+\label{sec:conclusions}

main.tex

@@ -13,6 +13,8 @@
 \setDueDate{2022-11-30}
 \setDueMonth{M46}
 
+\glsunset{ESFRI}
+
 % This is set according to information obtained from make and git.
 \setDocDate{\vcsDate}