Full existing contents summaried, only discussion to go

The contents until two commits ago when I started to summarize the paper
are now in a new and shorter format: previously the discussion started on
page 25, but now it starts on page 17. It is still a little longer than
8000 words, but not as significantly as before. I will add the discussion
and also try to summarize it futher before submission.

4 files changed, 458 insertions, 33 deletions

diff --git a/paper.tex b/paper.tex
index 26288fc..e94e894 100644
--- a/paper.tex
+++ b/paper.tex
@@ -26,8 +26,7 @@
 
 \title{Maneage: Customizable framework for Managing Data Lineage}
 \author{\large\mpregular \authoraffil{Mohammad Akhlaghi}{1,2},
-        \large\mpregular \authoraffil{Ra\'ul Infante-Sainz}{1,2},
-        \large\mpregular \authoraffil{Roberto Baena Gall\'e}{1,2}\\
+        \large\mpregular \authoraffil{Ra\'ul Infante-Sainz}{1,2}\\
   {
     \footnotesize\mplight
     \textsuperscript{1} Instituto de Astrof\'isica de Canarias, C/V\'ia L\'actea, 38200 La Laguna, Tenerife, ES.\\
@@ -48,7 +47,7 @@
 %% Abstract
 {\noindent\mpregular
   The era of big data has ushered an era of big responsibility.
-  In the absense of reproducibility, as a test on controlling the data lineage, the result's integrity will be subject to perpetual debate.
+  In the absence of reproducibility, as a test on controlling the data lineage, the result's integrity will be subject to perpetual debate.
   Maneage (management + lineage) is introduced here as a host to the computational and narrative components of an analysis.
   Analysis steps are added to a new project with lineage in mind, thus facilitating the project's execution and testing as the project evolves, while being friendly to publishing and archival because it is wholly in machine\--action\-able, and human\--read\-able, plain-text.
   Maneage is founded on the principles of completeness (e.g., no dependency beyond a POSIX-compatible operating system, no administrator privileges, or no network connection), modular and straight-forward design, temporal lineage and free software.
@@ -131,7 +130,7 @@ Generally, this problem is unambiguously felt in the community: \citet{baker16}
 
 This is not a new problem in the sciences: in 2011, Elsevier conducted an ``Executable Paper Grand Challenge'' \citep{gabriel11}.
 The proposed solutions were published in a special edition.
-Before that, in an attemp to simulate research projects, \citet{ioannidis05} proved that ``most claimed research findings are false''.
+Before that, in an attempt to simulate research projects, \citet{ioannidis05} proved that ``most claimed research findings are false''.
 In the 1990s, \citet{schwab2000, buckheit1995, claerbout1992} describe this same problem very eloquently and also provided some solutions that they used.
 While the situation has improved since the early 1990s, these papers still resonate strongly with the frustrations of today's scientists.
 Even earlier, through his famous quartet, \citet{anscombe73} qualitatively showed how distancing of researchers from the intricacies of algorithms/methods can lead to misinterpretation of the results.
@@ -146,7 +145,7 @@ In this paper we introduce Maneage as a solution to the collective problem of pr
 A project using Maneage will start by branching from the main Git branch of Maneage and starts customizing it: specifying the necessary software tools for that particular project, adding analysis steps and writing a narrative based on the analysis results.
 The temporal provenance of the project is fully preserved in Git, and allows merging of the project with the core branch to update the low-level infra-structure (common to all projects) without changing the high-level steps specific to this project.
 In Section \ref{sec:d-and-p} the basic concepts are defined and the founding principles of Maneage are discussed.
-Section \ref{sec:maneage} describes the internal structure of Maneage and Section \ref{sec:discussion} is a discussion on its benefits, caveats and future prospecs.
+Section \ref{sec:maneage} describes the internal structure of Maneage and Section \ref{sec:discussion} is a discussion on its benefits, caveats and future prospects.
 
 
 \section{Definitions}
@@ -192,7 +191,7 @@ As a consequence, before starting with the technical details it is important to
 \item \label{definition:lineage}\textbf{Data Lineage:}
 Data lineage is commonly used interchangeably with Data provenance \citep[for example][]{cheney09}.
 For clarity, we define term ``Data lineage'' as a low-level and fine-grained recording of the data's trajectory in an analysis (not meta-data, but actual commands).
-Therfore data lineage is synonymous with ``project'' as defined above.
+Therefore data lineage is synonymous with ``project'' as defined above.
 \item \label{definition:reproduction}\textbf{Reproducibility \& Replicability:}
   These terms have been used in the literature with various meanings, sometimes in a contradictory way.
   It is important to highlight that in this paper we are only considering computational analysis: \emph{after} data has been collected and stored as a file.
@@ -202,7 +201,7 @@ Therfore data lineage is synonymous with ``project'' as defined above.
 
   \citet{fineberg19} define reproducibility as \emph{obtaining consistent [not necessarily identical] results using the same input data; computational steps, methods, and code; and conditions of analysis}, or same inputs $\rightarrow$ consistent result.
   They define Replicability as \emph{obtaining consistent results across studies aimed at answering the same scientific question, each of which has obtained its own data}, or different inputs $\rightarrow$ consistent result.
-  Generally, since replicability involves new data collection \citep[e.g., see][]{kaiser18}.
+  Generally, since Replicability involves new data collection \citep[e.g., see][]{kaiser18}.
 \end{enumerate}
 
 
@@ -217,7 +216,7 @@ Therfore data lineage is synonymous with ``project'' as defined above.
 \section{Principles}
 \label{sec:principles}
 
-The core principle behing Maneage is simple: science is defined by its method, not its result.
+The core principle of Maneage is simple: science is defined by its method, not its result.
 \citet{buckheit1995} summarize this nicely by noting that modern scientific papers (narrative combined with plots, tables and figures) are merely advertisements of a scholarship, the actual scholarship is the scripts and software usage that went into doing the analysis.
 
 Maneage is not the first attempted solution to this fundamental problem.
@@ -226,7 +225,7 @@ To highlight the uniqueness of Maneage in this plethora of tools, a more elabora
 
 \begin{enumerate}[label={\bf P\arabic*}]
 \item \label{principle:complete}\textbf{Complete:}
-  A project that is complete, or self-contained, doesn't depend on anything beyond the Portable operating system Interface (POSIX), doesn't affect the host system, doesn't require root/administrator previlages, doesn't need an internet connection (when its inputs are on the filesystem), and is fully recorded and executable in plain-text\footnote{Plain text format doesn't include document container formats like \inlinecode{.odf} or \inlinecode{.doc}, for software like LibreOffice or Microsoft Office.} format (e.g., ASCII or Unicode).
+  A project that is complete, or self-contained, doesn't depend on anything beyond the Portable operating system Interface (POSIX), doesn't affect the host system, doesn't require root/administrator privileges, doesn't need an internet connection (when its inputs are on the file-system), and is fully recorded and executable in plain-text\footnote{Plain text format doesn't include document container formats like \inlinecode{.odf} or \inlinecode{.doc}, for software like LibreOffice or Microsoft Office.} format (e.g., ASCII or Unicode).
 
   A complete project can automatically access to the inputs (see definition \ref{definition:input}), build its necessary software (instructions on configuring, building and installing those software in a fixed environment), do the analysis (run the software on the data) and create the final narrative report/paper as well as its visualizations, in its final format (usually in PDF or HTML).
   No manual/human interaction is required within a complete project, as \citet{claerbout1992} put it: ``a clerk can do it''.
@@ -236,8 +235,8 @@ To highlight the uniqueness of Maneage in this plethora of tools, a more elabora
   \emph{Comparison with existing:} Except for IPOL, none of the tools above are complete.
   They all have many dependencies far beyond POSIX, for example the more recent ones are written in Python or use Jupyter notebooks \citep{kluyver16}.
   Such high-level tools have very short lifespan and evolve very fast, the most recent example was Python 3 that is not compatible with Python 2.
-  They also have a very complex dependency trees, making them extremely volnerable to updates, for example see Figure 1 of \citet{alliez19} on the dependency tree of Matplotlib (one of the smaller Jupyter dependencies).
-  The logevity of a data lineage, or workflow (not the analysis itself), is determined by its shortest-lived dependency.
+  They also have a very complex dependency trees, making them extremely vulnerable to updates, for example see Figure 1 of \citet{alliez19} on the dependency tree of Matplotlib (one of the smaller Jupyter dependencies).
+  The longevity of a data lineage, or workflow (not the analysis itself), is determined by its shortest-lived dependency.
 
   Many existing tools therefore don't attempt to store the project as plain text, but pre-built binary blobs (containers or virtual machines) that can rarely be recreated\footnote{Using the package manager of the container's OS, or Conda which are both highly dependent on the time they are created.} and also have a short lifespan\footnote{For example Docker only works on Linux kernels that are on long-term support, not older.
     Currently this is Linux 3.2.x that was initially released 8 years ago in 2012. The current Docker images may not be usable in a similar time frame in the future.}.
@@ -288,7 +287,7 @@ IPOL, which uniquely stands out in other principles, fails at this one: only the
 \item \label{principle:freesoftware}\textbf{Free and open source software}
   Technically, as defined in Section \ref{definition:reproduction}, reproducibility is also possible with a non-free or non-open-source software (a black box).
   This principle is thus necessary to complement the definition of reproducibility and has many advantages which are critical to the sciences and the industry:
-  1) The lineage, and its optimizatoin, can be traced down to the internal algorithm in the software's source.
+  1) The lineage, and its optimization, can be traced down to the internal algorithm in the software's source.
   2) A non-free software may not be executable on a given/future hardware, if its free, the project members can modify it to work.
   3) A non-free software cannot be distributed by the authors, making the whole community reliant only on the proprietary owner's server (even if the proprietary software doesn't ask for payments), also see Section \ref{sec:publishing}.
 
@@ -298,87 +297,505 @@ IPOL, which uniquely stands out in other principles, fails at this one: only the
 
 
 
-\section{Implementation of Maneage}
+
+
+
+
+
+
+
+\section{Maneage}
 \label{sec:maneage}
 
+Maneage is an implementation of the principles of Section \ref{sec:principles}: it is complete (\ref{principle:complete}), modular (\ref{principle:modularity}), has minimal complexity (\ref{principle:complexity}), verifies its inputs \& outputs (\ref{principle:verify}), preserves temporal provenance (\ref{principle:history}) and finally, it is free software (\ref{principle:freesoftware}).
+In practice it is a collection of plain-text files, that are distributed in pre-defined sub-directories by context (a modular source), and are all under version-control, currently with Git.
+The main Maneage Branch is a fully working skeleton of a project without much flesh: containing all the low-level infrastructure, but without any actual high-level analysis operations\footnote{In the core Maneage branch, only a simple demo analysis is included, which can easily be removed (all its files and steps have a \inlinecode{delete-me} prefix).}.
+
+To start a new project, the authors will \emph{clone}\footnote{In Git, the ``clone'' operation is the process of copying all the project's files and history from a repository onto the local system.} Maneage, create their own Git branch over the latest commit, and start their project by customizing that branch.
+Customization in their project branch is done by adding the names of the software they need, references to their input data, adding the analysis commands and commands to generate the visualizations, and write the narrative report which includes the visualizations.
+Manages contains a file called \inlinecode{README-hacking.md} that has a complete checklist of steps to start a new project and remove demonstration parts.
+This will usually be done in multiple commits in the project's duration (maybe multiple years), thus preserving the project's history: the causes of all choices, the authors and times of each change, failed tests, and etc.
+
+Figure \ref{fig:files} shows this directory structure containing the modular plain-text files (classified by context in sub-directories) and some representative files in each directory.
+The top-level source only has very high-level components: the \inlinecode{project} shell script (POSIX-compliant) that is the main interface to the project, as well as the paper's \LaTeX{} source, documentation and a copyright statement.
+Two sub-directories are also present: \inlinecode{tex/} (containing \LaTeX{} files) and \inlinecode{reproduce/} (containing all other parts of the project).
+
+\begin{figure}[t]
+  \begin{center}
+    \includetikz{figure-file-architecture}
+  \end{center}
+  \vspace{-5mm}
+  \caption{\label{fig:files}
+    Directory and file structure in a hypothetical project using this solution.
+    Files are shown with small, green boxes that have a suffix in their names (for example \inlinecode{format.mk} or \inlinecode{download.tex}).
+    Directories (containing multiple files) are shown as large, brown boxes, where the name ends in a slash (\inlinecode{/}).
+    Directories with dashed lines and no files (just a description) are symbolic links that are created after building the project, pointing to commonly needed built directories.
+    Symbolic links and their contents are not considered part of the source and are not under version control.
+    Files and directories are shown within their parent directory.
+    For example the full address of \inlinecode{format.mk} from the top project directory is \inlinecode{reproduce/analysis/make/format.mk}.
+  }
+\end{figure}
+
+The \inlinecode{project} script is a high-level wrapper to interface with Maneage and in its current implementation has two main phases as shown below.
+As seen below, a project's operations are broken-up into two phases: 1) configuration, where the necessary software are built and the environment is setup. 2) analysis, where data are accessed and the software is run on them to create visualizations and the final report.
+
+\begin{lstlisting}[language=bash]
+  ./project configure      # Build software from source (takes around 2 hours for full build).
+  ./project make           # Do the analysis (download data, run software on data, build PDF).
+\end{lstlisting}
+
+Here we will delve deeper into the implementation and some usage details of Maneage.
+Section \ref{sec:usingmake} elaborates why Make (a POSIX tool) was chosen as the main job orchestrator in Maneage.
+Sections \ref{sec:projectconfigure} \& \ref{sec:projectanalysis} then discuss the operations done during the configuration and analysis phase.
+Afterwards, we describe how Maneage projects benefit from version control, during the project's lifetime and after its publication, or end-of-life in Section \ref{sec:projectgit}.
+Section \ref{sec:collaborating} discusses a useful feature of Maneage's modularity principle: sharing built environment and products with multiple project members and Section \ref{sec:publishing} describes the publication/archival features of Maneage.
+Finally, in Section \ref{sec:futurework} we discuss the history and future of Maneage.
+
 \subsection{Job orchestration with Make}
 \label{sec:usingmake}
 
-\subsection{General implementation structure}
-\label{sec:generalimplementation}
+When non-interactive, or batch, processing is needed (see Section \ref{principle:complete}), scripts (in Shell, Python, or any other high-level language) are usually the first solution that come to mind.
+However, the inherent complexity and non-linearity of progress in a project (where experimentation is key) is hard to manage the script(s) as the project evolves.
+For example, if $90\%$ of a research project is done and only the newly added, final $10\%$ must be executed, a script will always start from the beginning.
+It is possible to manually ignore (with conditionals), or manually comment, parts of a script to only do a special part.
+However, such conditionals/comments will only add to the complexity and will discourage experimentation on an already completed part of the project.
+These problems motivated the creation of Make in the early Unix operating system \citep{feldman79}.
+
+The Make paradigm starts from the end: the final \emph{target}.
+In Make's syntax, the process is broken into atomic \emph{rules} where each rule has a single \emph{target} file which can depend on any number of \emph{prerequisite} files.
+To build the target from the prerequisites, each rule also has a \emph{recipe} (an atomic script).
+The plain-text files containing Make rules and their components are called Makefiles.
+Hence Make doesn't replace scripting languages like the shell, Python or R, it is a higher-level structure enabling modular/atomic scripts (in any language) to be put in a workflow.
+The formal connection of targets with prerequisites that is defined in Make, enables creation of a precise lineage as a formal/codified executable system that is very mature and has stood the test of time: Make is actively developed and used in the building of most OS components.
+
+Besides formalizing data lineage, Make also greatly encourages experimentation in a project because a recipe is executed only when atleast one prerequisite is more recent than its target.
+Therefore when only $5\%$ of a project's targets are affected by a change, only they will be recreated, the other $95\%$ remain untouched.
+Furthermore, Make first examines the full lineage before starting the execution of recipes.
+It can thus execute independent rules in parallel, further improving the speed and encouraging experimentation.
+
+Make is well known by many outside of the software developing communities.
+For example \citet{schwab2000} report how geophysics students have easily adopted it for the RED project management tool.
+Because of its simplicity, we have also had very good feedback on using Make from the early adopters of Maneage during the last year, in particular graduate students and postdocs.
+
+\tonote{Mention the non-recursive Make here when discussing \inlinecode{top-make.mk}.}
 
 \subsection{Project configuration}
 \label{sec:projectconfigure}
 
-\subsubsection{Setting local directories}
-\label{sec:localdirs}
+Understanding an already built software environment is critical to the understanding/reproducing the result.
+A more robust solution is to to build the software environment from scratch.
+Most existing tools reviewed in Section \ref{sec:principles}, use package managers like Conda, but since conda itself is written in Python, it violates our completeness principle \ref{principle:complete}.
+Highly robust solutions like Nix \citep{dolstra04} and GNU Guix \citep{courtes15} do exist, but they require root permissions which is also against that principle.
+Based on the principles of completeness (\ref{principle:complete}) and minimal complexity (\ref{principle:complexity}) Maneage orchestrates the building of its necessary software in the same language that it orchestrates the analysis: Make (see Section \ref{sec:usingmake}).
+Therefore, a researcher already using Maneage easily understands and can customize the software environment also, without having to learn the intricacies of third-party tools.
 
-\subsubsection{Checking for a C compiler}
-\label{sec:ccompiler}
+Project configuration (building the software environment) is managed by the files under \inlinecode{reproduce\-/soft\-ware} of Maneage's source, see Figure \ref{fig:files}.
+At the start of project configuration, Maneage needs a top-level directory to build itself on the host filesystem (software and analysis).
+We call this the ``build directory'' (or \inlinecode{BDIR}) and it must not be under the source directory (see \ref{principle:modularity}).
+No other location on the running operating system will be affected by the project and it should not affect the result, so its value is not under version control.
+Two other local directories can optionally be specified by the project when inputs (\ref{definition:input}) are present locally and don't need to be downloaded: 1) software tarball directory and 2) input data directory.
+Sections \ref{sec:buildsoftware} and \ref{sec:softwarecitation} elaborate more on the building of the necessary software and the important problem of software citation.
 
 \subsubsection{Verifying and building necessary software from source}
 \label{sec:buildsoftware}
 
+To compile the necessary software from source Maneage currently needs the host to have a C compiler (available on any POSIX-compliant OS).
+This C compiler will be used by maneage to install all the Maneage meta-software (software to build other software) with fixed versions, this includes GNU Bash, GNU AWK, GNU Coreutils, and many more on all supported operating systems (including macOS).
+For example the full list of installed software for this paper is available in Acknowledgments of this paper.
+On GNU/Linux OSs, a fixed version of the GNU Binutils and GNU C Compiler (GCC) is also included, and soon Maneage will also install its own fixed version of the GNU C Library to be fully independent of the host on such systems (Task 15390\footnote{\url{https://savannah.nongnu.org/task/?15390}}).
+In effect, except for the Kernel, Maneage builds all other components of the GNU OS on the host from source.
+
+The software source code may already be present on the host filesystem, if not they can be downloaded.
+But before being used to build the software, their SHA-512 checksum \citep[part of the SHA-2 algorithms, see][]{romine15} will be checked with the expected checksum in Maneage.
+If the checksums don't match, Maneage will stop and warn the user.
+
+The core operating system components (mostly GNU tools) will be installed in any project, only their versions may differ from one project to another.
+But Maneage also includes a large collection of scientific software (and their dependencies) that are usually not necessary in all projects, each project has to identify its high-level software in its branch, specified in the \inlinecode{TARGETS.conf} file under \inlinecode{re\-produce\-/soft\-ware\-/config} directory, see Figure \ref{fig:files}.
+
+Note that project configuration can be done in a container or virtual machine to avoid having to facilitate moving the project.
+However the important factor is that such binary blobs are an optional output of Maneage, they are not the only way a project using Maneage can be archived.
+
 \subsubsection{Software citation}
 \label{sec:softwarecitation}
 
-\subsection{High-level organization of analysis}
-\label{sec:highlevelanalysis}
+Maneage contains the full list of built software for each project, their versions and their configuration options.
+However, this information is buried deep into each project's source.
+Maneage also prints a distilled fraction of this informationin the project's final report, blended into the narrative, as seen in the Acknowledgments of this paper.
+Furthermore, when the software is associate with a published paper, that paper's Bib\TeX{} entry is also added to the final report and is cited with the software's name and version.
+This is particularly important in the case for research software, where the researcher has invested significant time in building the software, and requires official citation to justify continued work on it.
+
+One notable example that nicely highlights this issue is GNU Parallel \citep{tange18}: every time it is run, it prints the citation information before it starts.
+This doesn't cause any problem in automatic scripts, but can be annoying when reading/debugging the outputs.
+Users can disable the notice, with the \inlinecode{--citation} option and accept to cite its paper, or support its development directly by paying $10000$ euros!
+This is justified by an uncomfortably true statement\footnote{GNU Parallel's FAQ on the need to cite software: \url{http://git.savannah.gnu.org/cgit/parallel.git/plain/doc/citation-notice-faq.txt}}: ``history has shown that researchers forget to [cite software] if they are not reminded explicitly. ... If you feel the benefit from using GNU Parallel is too small to warrant a citation, then prove that by simply using another tool''.
+In bug 905674\footnote{Debian bug on the citation notice of GNU Parallel: \url{https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905674}}, the Debian developers argued that because of this extra condition, GNU Parallel should not be considered as free software, and they are using a patch to remove that part of the code for its build under Debian-based OSs.
+Most other research software don't resort to such drastic measures, however, citation is important for them.
+Given the increasing number of software used in scientific research, the only reliable solution is to automatically cite the used software in the final paper.
+
+For a review of the necessity and basic elements in software citation, see \citet{katz14} and \citet{smith16}.
+There are ongoing projects specifically tailored to software citation, including CodeMeta (\url{https://codemeta.github.io}) and Citation file format (CFF: \url{https://citation-file-format.github.io}).
+Another robust approach is provided by SoftwareHeritage \citep{dicosmo18}.
+We plan to enable these wonderful tools in Maneage.
+
+
+
+
+
+\subsection{Project's analysis}
+\label{sec:projectanalysis}
 
-\subsubsection{Isolated analysis environment}
-\label{sec:analysisenvironment}
+Once the project is configured (Section \ref{sec:projectconfigure}), a unique and fully controlled environment is available to execute the analysis.
+All analysis operations run such that the host OS settings cannot penetrate it, enabling an isolated environment without the extra layer of containers or a virtual machine.
+In Maneage, a project's analysis is broken into two phases: data preparation and analysis.
+The former is mostly necessary in special situations where the datasets are extremely large and some initial preparation needs to be done on them to avoid slowing down the whole project in each run.
+That phase is organized in an identical manner as the analysis phase, so we won't to into it any furhter here and refer the interested reader to the documentation of Maneage.
 
-\subsubsection{Preparation phase}
-\label{sec:prepare}
+A project consists of many steps, including data access (possibly by downloading), running various steps of the analysis on the obtained data, and creating the necessary plots, figures or tables for a published report, or output datasets for a database.
+If all of these steps are organized in a single Makefile, it will become very large, or long, and will be hard to maintain, extend/grow, read, reuse, and cite.
+Generally, large files are a bad practice and against the modularity principle (\ref{principle:modularity}).
 
-\subsection{Low-level organization of analysis}
-\label{sec:lowlevelanalysis}
+Maneage is thus designed to encourage and facilitate modularity by distributing the analysis in many Makefiles that contain contextually-similar (or modular) analysis steps.
+In the rest of this paper these modular, or lower-level, Makefiles will be called \emph{subMakefiles}.
+When run with the \inlinecode{make} argument, the \inlinecode{project} script (Section \ref{sec:maneage}), calls the \inlinecode{top-make.mk} Makefile that is in \inlinecode{re\-produce\-/anal\-ysis\-/make}.
+The subMakefiles are loaded into \inlinecode{top-make.mk} in a certain order and executed in one instance of Make without recursion (recursion is against the minimal complexity principle, \ref{principle:complexity}).
+The subMakefiles are located in the same directory as \inlinecode{top-make.mk}, see Figure \ref{fig:files}.
+Figure \ref{fig:datalineage} schematically shows these subMakefiles and their relation with each other through their targets.
 
-\subsubsection{Non-recursive Make}
-\label{sec:nonrecursivemake}
+\begin{figure}[t]
+  \begin{center}
+    \includetikz{figure-data-lineage}
+  \end{center}
+  \vspace{-7mm}
+  \caption{\label{fig:datalineage}Schematic representation of data lineage in a hypothetical project/pipeline using Maneage.
+    Each colored box is a file in the project and the arrows show the dependencies between them.
+    Green files/boxes are plain text files that are under version control and in the source-directory.
+    Blue files/boxes are output files of various steps in the build-directory, located within the Makefile (\inlinecode{*.mk}) that generates them.
+    For example \inlinecode{paper.pdf} depends on \inlinecode{project.tex} (in the build directory and generated automatically) and \inlinecode{paper.tex} (in the source directory and written by hand).
+    In turn, \inlinecode{project.tex} depends on all the \inlinecode{*.tex} files at the bottom of the Makefiles above it.
+    The solid arrows and built boxes with full opacity are actually described in the context of a demonstration project in this paper.
+    The dashed arrows and lower opacity built boxes, just shows how adding more elements to the lineage is also easily possible, making this a scalable tool.
+  }
+\end{figure}
+
+To avoid getting too abstract in the subsections below, where necessary, we'll do a basic analysis on the data of \citet[data were published as supplementary material on bioXriv]{menke20} and replicate one of their results.
+Note that because we are not using the same software, this isn't a reproduction (\ref{definition:reproduction}).
+We can't use the same software because they use Microsoft Excel for the analysis which violates several of our principles: \ref{principle:complete}, \ref{principle:complexity} and \ref{principle:freesoftware}.
+In the subsections below, this paper's analysis on that dataset is described using the data lineage graph of Figure \ref{fig:datalineage}.
+We'll follow Make's paradigm (see Section \ref{sec:usingmake}) of starting form the ultimate target in Section \ref{sec:paperpdf}, and tracing backwards in its lineage to the configuration files \ref{sec:configfiles}.
 
 \subsubsection{Ultimate target: the project's paper or report (\inlinecode{paper.pdf})}
 \label{sec:paperpdf}
 
+The ultimate purpose of a project is to report the data analysis result, as raw visualizations of the results or blended in with a narrative description.
+In Figure \ref{fig:datalineage} it is shown as \inlinecode{paper.pdf}, note that it is the only built file (blue box) with no arrows leaving it.
+The instructions to build \inlinecode{paper.pdf} are in the \inlinecode{paper.mk} subMakefile.
+Its prerequisites include \inlinecode{paper.tex} and \inlinecode{references.tex} (Bib\TeX{} entries for possible citations) in the project source and \inlinecode{project.tex} which is a built product.
+\inlinecode{references.tex} is also an important component of Maneage because it formalizes the connections of this project with previous projects on a high-level.
+
 \subsubsection{Values within text (\inlinecode{project.tex})}
 \label{sec:valuesintext}
 
+Figures, plots, tables and narrative aren't the only analysis output that goes into the paper.
+In many cases, quantitative values from the analysis are also blended into the sentences of the report's narration.
+For example note this sentence in the abstract of \citet[which is written in Maneage]{akhlaghi19}: ``... detect the outer wings of M51 down to S/N of 0.25 ...''.
+The signal-to-noise ratio (S/N) value ``0.25'' depends on the analysis, and is an output of the analysis just like paper's figures and plots.
+Manually typing such numbers in the narrative is prone to very important bugs: the author may forget to check it after a change in an analysis (e.g., using a newer version of the software, or changing an analysis parameter for another part of the paper).
+Given the non-linear evolution of a scientific projects, this type of human error is very hard to avoid and can discourage experimentation.
+Therefore such values must also be automatically generated.
+
+To automatically generate and blend them in the text, Maneage uses \LaTeX{} macros.
+In the quote above, the \LaTeX{} source\footnote{\citet{akhlaghi19} uses this template to be reproducible, so its \LaTeX{} source is available in multiple ways: 1) direct download from arXiv:\href{https://arxiv.org/abs/1909.11230}{1909.11230}, by clicking on ``other formats'', or 2) the Git or \href{https://doi.org/10.5281/zenodo.3408481}{zenodo.3408481} links is also available on arXiv.} looks like this: ``\inlinecode{\small detect the outer wings of M51 down to S/N of \$\textbackslash{}demo\-sf\-optimized\-sn\$}''.
+The ma\-cro ``\inlinecode{\small\textbackslash{}demosfoptimizedsn}'' is automatically calculated and recorded during in the project and expands to the value ``\inlinecode{0.25}''.
+The built \inlinecode{project.tex} file stores all such reported values.
+
+However, managing all the necessary \LaTeX{} macros in one file is against the modularity principle and can be frustrating and buggy.
+To address this problem, Maneage has the convention that all subMakefiles \emph{must} contain a fixed target with the same base-name, but with a \inlinecode{.tex} suffix to store reporeted values generated in that subMakefile.
+In Figure \ref{fig:datalineage}, these macro files can be seen in every subMakefile, except for \inlinecode{paper.mk} (which doesn't need it).
+These \LaTeX{} macro files thus form the core skeleton of a Maneage project: as shown in Figure \ref{fig:datalineage}, the outward arrows of all built files of any subMakefile ultimately leads to one of these \LaTeX{} macro files, possibly in another subMakefile.
+
 \subsubsection{Verification of outputs (\inlinecode{verify.mk})}
 \label{sec:outputverification}
 
+Before the modular \LaTeX{} macro files of Section \ref{sec:valuesintext} are merged into the single \inlinecode{project.tex} file, they need to pass through the verification filter, which is a core principle of Maneage (\ref{principle:verify}).
+Note that simply confirming the checksum of the final PDF, or figures and datasets is not generally possible: many tools write the creation date into the produced files.
+To avoid such cases the raw data (independent of their metadata like creation date) must be verified, some standards have such features for example For example the \inlinecode{DATASUM} keyword in the FITS format \citep{pence10}.
+
+To facilitate output verification, the project has a \inlinecode{verify.mk} subMakefile, see Figure \ref{fig:datalineage}.
+It's \inlinecode{verify.tex} the only prerequisite of \inlinecode{project.tex} that was described in Section \ref{sec:valuesintext} and is the boundary between the analytical phase of the paper, and the production of the report.
+It has some tests on pre-defined formats, and other formats can easily be added.
+Prior to publication, the project authors should add the MD5 checksums of all the\LaTeX{} macro files and output datasets in the recipe of \inlinecode{verify\-.tex} to enable automatic verification by readers afterwards.
+
 \subsubsection{Project initialization (\inlinecode{initialize.mk})}
 \label{sec:initialize}
 
-\subsubsection{Importing and validating inputs (\inlinecode{download.mk})}
-\label{sec:download}
+The \inlinecode{initial\-ize\-.mk} subMakefile is present in all projects and is the first subMakefile that is loaded into \inlinecode{top-make.mk} (see Figure \ref{fig:datalineage}).
+Project authors rarely need to modify/edit this file, it is a low-level infrastructure of Maneage, but are encouraged to do so.
+\inlinecode{initial\-ize\-.mk} doesn't contain any analysis or major processing steps, it just initializes the system by setting the necessary Make environment as well as other general jobs like defining the Git commit hash of the run as a \LaTeX{} (\inlinecode{\textbackslash{}projectversion}) macro that can be loaded into the narrative.
+Papers using Maneage usually put this hash as the last word in their abstract, for example see \citet{akhlaghi19} and \citet{infante20}, for the current version of this paper, it expands to \projectversion.
 
 \subsubsection{The analysis}
 \label{sec:analysis}
 
+The basic concepts behind organizing the analysis into modular subMakefiles has already been discussed above, we'll thus describe it here with the practical example of replicating Figure 1C of \citet{menke20}, with some enhancements in Figure \ref{fig:toolsperyear}.
+As shown in Figure \ref{fig:datalineage}, in the customized branch of this project, we have broken this goal into two subMakefiles: \inlinecode{format.mk} and \inlinecode{demo-plot.mk}.
+The former is in charge of converting the Microsoft Excel formatted input into the simple comma-separated value (CSV) format, and the latter is in charge of generating the table to build Figure \ref{fig:toolsperyear}.
+In a real project, subMakefiles will be much more complex.
+Figure \ref{fig:topmake} shows how the two subMakefiles are thus placed as values to the \inlinecode{makesrc} variable of \inlinecode{top-make.mk}, without their suffix\footnote{Because the \LaTeX{} macro file will also be generated from the values to \inlinecode{makesrc} with the \inlinecode{.tex} suffix, see Section \ref{sec:valuesintext}.}.
+Note that their location after the standard starting subMakefiles (initialization and download) and before the standard ending subMakefiles (verification and final paper) is important, as well as the order.
+
+\begin{figure}[t]
+  \begin{center}
+    \includetikz{figure-tools-per-year}
+  \end{center}
+  \vspace{-5mm}
+  \caption{\label{fig:toolsperyear}Fraction of papers mentioning software tools (green line, left vertical axis) to total number of papers studied in that year (light red bars, right vertical axis in log-scale).
+    Data from \citet{menke20}.
+    The subMakefile archiving the executable lineage of figure's data is shown in Figure \ref{fig:demoplotsrc} and discussed in Section \ref{sec:analysis}.
+  }
+\end{figure}
+
+\begin{figure}[t]
+  \input{tex/src/figure-src-topmake.tex}
+  \vspace{-3mm}
+  \caption{\label{fig:topmake} General view of the High-level \inlinecode{top-make.mk} Makefile which manages the project's analysis that is in various subMakefiles.
+    See Figures \ref{fig:files} \& \ref{fig:datalineage} for its location in the project's file structure and its data lineage, as well as the subMakefiles it includes.
+  }
+\end{figure}
+
+Figure \ref{fig:toolsperyear} also shows the number of papers that were studied each year (that is not shown in the original plot).
+Its horizontal axis also shows the full range of the data (starting from \menkefirstyear) while the original Figure 1C in \citet{menke20} starts from 1997.
+Probably the reason \citet{menke20} decided to avoid earlier years was the small number of papers in earlier years.
+For example in \menkenumpapersdemoyear, they had only studied \menkenumpapersdemocount{} papers.
+Note that both the numbers of the previous sentence (\menkenumpapersdemoyear{} and \menkenumpapersdemocount), and the dataset's oldest year (mentioned above: \menkefirstyear) are automatically generated \LaTeX{} macros, see \ref{sec:valuesintext}.
+We didn't typeset them in this narrative explanation manually.
+This step (generating the macros) is shown schematically in Figure \ref{fig:datalineage} with the arrow from \inlinecode{tools-per-year.txt} to \inlinecode{demo-plot.tex}.
+
+To create Figure \ref{fig:toolsperyear}, we used the \LaTeX{} package PGFPlots, therefore the final analysis output we needed was a simple plain-text table with 3 columns.
+This table is shown in the lineage graph of Figure \ref{fig:datalineage} as \inlinecode{tools-per-year.txt}.
+If another plotting tool was desired (for example Python's Matplotlib, or Gnuplot), the built graphic file (for example \inlinecode{tools-per-year.pdf}) could be the target instead of the raw table.
+
+The \inlinecode{tools-per-year.txt} is a value-added table with only \menkenumyears{} rows (counting per year), the original dataset had \menkenumorigrows{} rows (one row for each year of each journal).
+In the Make rule to build it is in \inlinecode{demo-plot.mk} and its the recipe is a simple GNU AWK command, with \inlinecode{menke20-table-3.txt} as its prerequisite, its is schematically shown by the arrow connecting the two \inlinecode{.txt} files.
+Note that both the row numbers mentioned at the start of this paragraph are also macros.
+The latter (\menkenumorigrows{}) is schematically shown with the arrow from \inlinecode{menke20-table-3.txt} to \inlinecode{format.tex}.
+
+Ultimately the first file we need to operate on is \inlinecode{menke20-table-3.txt} (which is defined as a target in \inlinecode{format.mk}).
+As mentioned before, the main operation here is to convert the Microsoft Excel format of the downloaded dataset (\inlinecode{menke20.xlsx}, discussed below in Section \ref{sec:download}) to this simple plain-text format for the operations mentioned above.
+We do this job with the XLSX I/O program that has been specified as software to build during project configuration.
+This step is shown schematically in Figure \ref{fig:datalineage} with the arrow connecting these two lines.
+
+Having prepared the full dataset in a simple format, let's report the number of subjects (papers and journals) that were studied in \citet{menke20}.
+The necessary file for this measurement is \inlinecode{menke20-table-3.txt} that is a target in \inlinecode{format.mk}.
+Therefore we do this calculation (with a simple AWK command) and write the results in (\inlinecode{format.tex}).
+In the built PDF paper, the two macros expand to $\menkenumpapers$ (number of papers studied) and $\menkenumjournals$ (number of journals studied) respectively.
+This step is shown schematically in Figure \ref{fig:datalineage} with the arrow from \inlinecode{menke20-table-3.txt} to \inlinecode{format.tex}.
+
+
+
+\subsubsection{Importing and validating inputs (\inlinecode{download.mk})}
+\label{sec:download}
+
+The \inlinecode{download.mk} subMakefile is present in all Maneage projects and contains the common steps for importing the input dataset(s) into the project.
+All necessary input datasets to the project are imported through this subMakefile.
+This helps in modularity and minimal complexity (\ref{principle:modularity} \& \ref{principle:complexity}): to see what external datasets were used in a project, this is the only necessary file to manage/read.
+Also, a simple call to a downloader (for example \inlinecode{wget}) is not usually enough.
+Irrespective of where the dataset is \emph{used} in the project's lineage, it helps to maintain relation with the outside world (to the project) in one subMakefile.
+
+Each external dataset has some basic information, including its expected name on the local system (for offline access), the necessary checksum to validate it (either the whole file or just its main ``data'', as discussed in Section \ref{sec:outputverification}), and its URL/PID.
+In Maneage, such information regarding a project's input dataset(s) is in the \inlinecode{INPUTS.conf} file.
+See Figures \ref{fig:files} \& \ref{fig:datalineage} for the position of \inlinecode{INPUTS.conf} in the project's file structure and data lineage respectively.
+For demonstration, we are using the datasets of \citet{menke20} which are stored in one \inlinecode{.xlsx} file on bioXriv\footnote{\label{footnote:dataurl}Full data URL: \url{\menketwentyurl}}.
+Figure \ref{fig:inputconf} shows the corresponding \inlinecode{INPUTS.conf} where the the necessary information are stored as Make variables and are automatically loaded into the full project when Make starts (and is most often used in \inlinecode{download.mk}).
+
+\begin{figure}[t]
+  \input{tex/src/figure-src-inputconf.tex}
+  \vspace{-3mm}
+  \caption{\label{fig:inputconf} Contents of the \inlinecode{INPUTS.conf} file for the demonstration dataset of \citet{menke20}.
+    This file contains the basic, or minimal, metadata for retrieving the required dataset(s) of a project: it can become arbitrarily long.
+    Here, \inlinecode{M20DATA} contains the name of this dataset within this project.
+    \inlinecode{MK20MD5} contains the MD5 checksum of the dataset, in order to check the validity and integrity of the dataset before usage.
+    \inlinecode{MK20SIZE} contains the size of the dataset in human readable format.
+    \inlinecode{MK20URL} is the URL which the dataset is automatically downloaded from (only when its not already present on the host).
+    Note that the original URL (footnote \ref{footnote:dataurl}) was too long to display properly here.
+  }
+\end{figure}
+
+
 \subsubsection{Configuration files}
 \label{sec:configfiles}
 
+The subMakefiles discussed above should only contain the organization of an analysis, they should not contains any fixed numbers, settings or parameters.
+Such elements should only be used as variables that are defined in configuration files.
+In the data lineage plot of Figure \ref{fig:datalineage}, configuration files are shown as the sharp-edged, green \inlinecode{*.conf} files in the top row.
+
+The demo analysis of Section \ref{sec:analysis} is a good demonstration of their usage: during that discussion we reported the number of papers studied by \citet{menke20} in \menkenumpapersdemoyear.
+However, the year's number is not written by hand in \inlinecode{demo-plot.mk}.
+It is referenced through the \inlinecode{menke-year-demo} variable, which is defined in \inlinecode{menke-demo-year.conf}, that is a prerequisite of the \inlinecode{demo-plot.tex} rule.
+This is also visible in the data lineage of Figure \ref{fig:datalineage}.
+If we later decide to report the number of paper in another year, we simply have to change the value in \inlinecode{menke-demo-year.conf}.
+Since the configuration file's date will be newer than \inlinecode{demo-plot.tex}, the recipe to generate the macro file will be be re-executed, and the corresponding year and value will be updated in this paper.
+
+All the configuration files of a project are placed under the \inlinecode{reproduce/analysis/config} (see Figure \ref{fig:files}) subdirectory, and are loaded into \inlinecode{top-make.mk} before any of the subMakefiles, see Figure \ref{fig:topmake}.
+The configuration files greatly simplify project management from multiple perspectives as listed below:
+
+\begin{itemize}
+\item If an analysis parameter is used in multiple places within the project, simply changing the value in the configuration file will change it everywhere in the project.
+  This is cortical in more complex projects and if not done like this can lead to significant human error.
+\item Configuration files enable the logical separation between the low-level implementation and high-level running of a project.
+  For example after writing the project, the authors don't need to remember where the number/parameter was used, they can just modify the configuration file.
+  Other co-authors, or readers, of the project also benefit: they just need to know that there is a unified place for high-level project settings, parameters, or numbers without necessarily having to know the low-level implementation.
+\item A configuration file will be a prerequisite to any rule that uses it's value.
+  If the configuration file is updated (the value/parameter is changed), Make will automatically detect the data lineage branch that is affected by it and re-execute only that branch, without any human interference.
+\end{itemize}
+
 \subsection{Projects as Git branches of Maneage}
-\label{sec:starting}
+\label{sec:projectgit}
+
+Maneage is fully composed of plain-text files, therefore it can be maintained under under version control systems like Git.
+Every commit in the version controlled history contains \emph{a complete} snapshot of the data lineage, for more see the completeness principle (\ref{principle:complete}).
+Maneage is maintained by its developers in a central branch, which we'll call \inlinecode{man\-eage} hereafter.
+The \inlinecode{man\-eage} branch contains all the low-level infrastructure, or skeleton, that is necessary for any project as described in the sections above.
+As mentioned in Section \ref{sec:maneage}, to start a new project, users simply clone it from its reference repository and build their own Git branch over the most recent commit.
+This is demonstrated in the first phase of Figure \ref{fig:branching} where a project has started by branching off of commit \inlinecode{0c120cb} (in the \inlinecode{maneage} branch).
+
+%% Exact URLs of imported images.
+%% Collaboration icon: https://www.flaticon.com/free-icon/collaboration_809522
+%% Paper done:         https://www.flaticon.com/free-icon/file_2521838
+%% Paper processing:   https://www.flaticon.com/free-icon/file_2521989
+\begin{figure}[t]
+  \includetikz{figure-branching}
+  \vspace{-3mm}
+  \caption{\label{fig:branching} Projects start by branching off the main Maneage branch and developing their high-level analysis over the common low-level infrastructure: add flesh to a skeleton.
+    The low-level infrastructure can always be updated (keeping the added high-level analysis intact), with a simple merge between branches.
+    Two phases of a project's evolution shown here: in phase 1, a co-author has made two commits in parallel to the main project branch, which have later been merged.
+    In phase 2, the project has finished: note the identical first project commit and the Maneage commits it branches from.
+    The dashed parts of Scenario 2 can be any arbitrary history after those shown in phase 1.
+    A second team now wants to build upon that published work in a derivate branch, or project.
+    The second team applies two commits and merges their branch with Maneage to improve the skeleton and continue their research.
+    The Git commits are shown on their branches as colored ellipses, with their hash printed in them.
+    The commits are colored based on the team that is working on that branch.
+    The collaboration and paper icons are respectively made by `mynamepong' and `iconixar' and downloaded from \url{www.flaticon.com}.
+  }
+\end{figure}
+
+After a project starts, Maneage will evolve.
+For example new features will be added, low-level bugs will be fixed that are useful for any project.
+Because all the changes in Maneage are committed on the \inlinecode{maneage} branch, and all projects branch-off from it, updating the project's lowlevel infra-structure is as easy as merging the \inlinecode{maneage} branch into the project's branch.
+For example in Figure \ref{fig:branching} (phase 1), see how Maneage's \inlinecode{3c05235} commit has been merged into project's branch trough commit \inlinecode{2ed0c82} .
+
+This doesn't just apply to the pre-publication phase, when done in Maneage, a project can be revived at any later date by other researchers as shown in phase 2 of Figure \ref{fig:branching}.
+In that figure, a new team of researchers have decided to experiment on the results of the published paper and have merged it with the Maneage branch (commit \inlinecode{a92b25a}) to fix some possible portability problem for their operating system that was fixed as a bug in Maneage after the paper's publication.
+
+Other scenarios include a third project that can easily merge various high-level components from different projects into its own branch, thus adding a temporal dimension to their data lineage.
+Modern version control systems provide many more capabilities that can be leveraged through Maneage in project management, thanks to the shared branch it has with \emph{all} projects that use it and that it is complete (\ref{principle:complete}).
 
 \subsection{Multi-user collaboration on single build directory}
 \label{sec:collaborating}
 
+Because the project's source and build directories are separate, it is possible for different users to share a build directory, while working on their own separate project branches during a collaboration.
+Similar to the parallel branch that is later merged in phase 1 of Figure \ref{fig:branching}.
+
+To give all users privilege, Maneage assumes that they are in the same (POSIX) user group of the system.
+All files built in the build directory are then automatically assigned to this user group.
+The \inlinecode{./project} script has a special \inlinecode{--group} option which activates this mode in both configuration and analysis phases.
+It takes the user group name as its argument and the built files will only be accessible by the group members, even when the shared location is accessible by people outside the project.
+
 \subsection{Publishing the project}
 \label{sec:publishing}
 
+Once the project is complete, publishing the project is the final step.
+In a scientific scenario, it is submitted to a journal, and an industrial world, it is submitted to the customers or employers.
+As discussed in the various steps before, the source of the project (the software configuration, data lineage and narrative text) is fully in plain text, greatly facilitating the publication of the project.
+
 \subsubsection{Automatic creation of publication tarball}
 \label{sec:makedist}
+To facilitate the publication of the project source, Maneage has a special \inlinecode{dist} target during the build process which is activated with the command \inlinecode{./project make dist}.
+In this mode, Maneage will not do any analysis, it will simply copy the full project's source (on the given commit) into a temporary directory and compress it into a \inlinecode{.tar.gz} file.
+If a Zip compression is necessary, the \inlinecode{dist-zip} target can be called instead \inlinecode{dist}.
 
 \subsubsection{What to publish, and where?}
 \label{sec:whatpublish}
+The project's source, which is fully in hand-written plain-text, has a very small volume, usually much less than one megabyte.
+However, the necessary inputs (\ref{definition:input}) and outputs may be arbitrarily large, from megabytes to petabytes or more.
+Therefore, there are various scenarios for the publication of the project as described below:
+
+\begin{itemize}
+\item \textbf{Only source:} Publishing the project source is very easy because it only contains plain-text files with a very small volume: a commit will usually be on the scale of $\times100kB$. With the Git history, it will usually only be on the scale of $\sim5MB$.
+
+  \begin{itemize}
+  \item \textbf{Public Git repository:} This is the simplest publication method.
+    The project will already be on a (private) Git repository prior to publication.
+    In such cases, the private configuration can be removed so it becomes public.
+  \item \textbf{In journal or PDF-only preprint systems (e.g., bioRxiv):} If the journal or pre-print server allows publication of small supplement files to the paper, the commit that produced the final paper can be submitted as a compressed file, for example with the
+  \item \textbf{arXiv:} arXiv will run its own internal \LaTeX{} engine on the uploaded files and produce the PDF that is published.
+    When the project is published, arXiv also allows users to anonymously download the \LaTeX{} source tarball that the authors uploaded.
+    Therefore, simply uploading the tarball from the \inlinecode{./project make dist} command is sufficient.
+    We done this in \citet[arXiv:1909.11230]{akhlaghi19} and \citet[arXiv:1911.01430]{infante20}.
+    Since arXiv is mirrored in many institutes over the planet, this is a robust way to preserve the reproducible lineage.
+  \item \textbf{In output datasets:} Many data storage formats support an internal structure with the data file.
+    One commonly used example today is the Hierarchical Data Format (HDF), and in particular its HDF5 which can host a complex filesystem in POSIX syntax.
+  \end{itemize}
+\item \textbf{Source and data:} The project inputs (including the software tarballs, or possible datasets) may have a large volume.
+  Publishing them with the source is thus not always possible.
+  However, based on the definition of inputs in Section \ref{definition:input}, they are usable in other projects: another project may use the same data or software source code, in a different way.
+  Therefore even when published with the source, it is encouraged to publish them as separate files.
+
+  For example strategy was followed in \href{https://doi.org/10.5281/zenodo.3408481}{zenodo.3408481}\footnote{https://doi.org/10.5281/zenodo.3408481} which supplements \citet{akhlaghi19} which contains the following files.
+
+  \begin{itemize}
+  \item \textbf{Final PDF:} for easy understanding of the project.
+  \item \textbf{Git history:} as the Git ``bundle'' of the project.
+    This single file contains the full Git history of the project until its publication date (only 4Mb), see Section \ref{sec:starting}.
+  \item \textbf{Project source tarball}: output of \inlinecode{./project make dist}, as explained above.
+  \item \textbf{Tarballs of all necessary software:} This is necessary in case the software webpages is not accessible for any reason at a later date or the project must be run with no internet access.
+    This is only possible because of the free software principle discussed in Section \ref{principle:freesoftware}.
+  \end{itemize}
+
+  Note that \citet{akhlaghi19} used previously published datasets which are automatically accessed when necessary.
+  Also, that paper didn't produce any output datasets beyond the figures shown in the report, therefore the Zenodo upload doesn't contain any datasets.
+  When a project involves data collection, or added-value data products, they can also be uploaded with the files above.
+\end{itemize}
 
 \subsubsection{Worries about getting scooped!}
 \label{sec:scooped}
+Publishing the project source with the paper can have many benefits for the researcher and the larger community.
+For example if the source is published with a pre-print, others my help the authors find bugs, or improvements to the source that can affect the validity or precision of the result, or simply optimize it so it does the same work in half the time for example.
+
+However, one particular feedback raised by a minority of researchers is that publishing the project's reproducible data lineage immediately after publication may hamper their ability to continue harvesting from all their hard work.
+Because others can easily reproduce the work, others may take the next follow-up project they originally intended to do.
+This is informally known as getting scooped.
+
+The level that this may happen is an interesting subject to be studied once many papers become reproducible.
+But it is a valid concern that must be addressed.
+Given the strong integrity checks in Maneage, we believe it has features to address this problem in the following ways:
+1) Through the Git history, it is clear how much extra work the other team has added.
+In this way, Maneage can contribute to a new concept of authorship in scientific projects and help to quantify newton's famous ``standing on the shoulders of giants'' quote.
+However, this is a long term goal and requires major changes to academic value systems.
+2) Authors can be given a grace period where the journal, or some third authority, keeps the source and publishes it a certain time after publication.
 
 \subsection{Future of Maneage and its past}
 \label{sec:futurework}
 
+As with any software, the core architecture of Maneage will inevitably evolve after the publication of this paper.
+The current version introduced here has already experienced 5 years of evolution and several reincarnations.
+Its primordial implementation was written for \citet{akhlaghi15}.
+This paper described a new detection algorithm in astronomical image processing.
+The detection algorithm was developed as the paper was being written (initially a small report!).
+An automated sequence of commands to build the figures, and update the paper/report was a practical necessity as the algorithm was evolving.
+In particular, it didn't just reproduce figures, it also used \LaTeX{} macros to update numbers printed within the text.
+Finally, since the full analysis pipeline was in plain-text and roughly 100kb (much less than a single figure), it was uploaded to arXiv with the paper's \LaTeX{} source, under a \inlinecode{reproduce/} directory, see \href{https://arxiv.org/abs/1505.01664}{arXiv:1505.01664}\footnote{
+  To download the \LaTeX{} source of any arXiv paper, click on the ``Other formats'' link, containing necessary instructions and links.}.
+
+The system later evolved in \citet{bacon17}, in particular the two sections of that paper that were done by M. Akhlaghi (first author of this paper): \citet[\href{http://doi.org/10.5281/zenodo.1163746}{zenodo.1163746}]{akhlaghi18a} and \citet[\href{http://doi.org/10.5281/zenodo.1164774}{zenodo.1164774}]{akhlaghi18b}.
+With these projects, the skeleton of the system was written as a more abstract ``template'' that could be customized for separate projects.
+The template later matured by including installation of all necessary software from source and used in \citet[\href{https://doi.org/10.5281/zenodo.3408481}{zenodo.3408481}]{akhlaghi19} and \citet[\href{https://doi.org/10.5281/zenodo.3524937}{zenodo.3524937}]{infante20}.
+The short historical review above highlights how this template was created by practicing scientists, and has evolved and matured significantly.
+
+We already have roughly 30 tasks that are left for the future and will affect various high-level phases of the project as described here.
+However, the core of the system has been used and become stable enough already and we don't see any major change in the core methodology in the near future.
+A list of the notable changes after the publication of this paper will be kept in in the project's \inlinecode{README-hacking.md} file.
+Once the improvements become substantial, new paper(s) will be written to complement or replace this one.
+
 \section{Discussion}
 \label{sec:discussion}
 
diff --git a/reproduce/analysis/make/demo-plot.mk b/reproduce/analysis/make/demo-plot.mk
index caf77af..ac05776 100644
--- a/reproduce/analysis/make/demo-plot.mk
+++ b/reproduce/analysis/make/demo-plot.mk
@@ -53,6 +53,10 @@ $(mtexdir)/demo-plot.tex: $(a2mk20f1c) $(pconfdir)/menke-demo-year.conf
 	v=$$(awk 'NR==1{print $$1}' $(a2mk20f1c))
 	echo "\newcommand{\menkefirstyear}{$$v}" > $@
 
+        # Find the number of rows in the plotted table.
+	v=$$(cat $(a2mk20f1c) | wc -l)
+	echo "\newcommand{\menkenumyears}{$$v}" >> $@
+
         # Find the number of papers in 1996.
 	v=$$(awk '$$1==$(menke-demo-year){print $$3}' $(a2mk20f1c))
 	echo "\newcommand{\menkenumpapersdemocount}{$$v}" >> $@
diff --git a/reproduce/analysis/make/format.mk b/reproduce/analysis/make/format.mk
index 868c411..d10034d 100644
--- a/reproduce/analysis/make/format.mk
+++ b/reproduce/analysis/make/format.mk
@@ -80,3 +80,7 @@ $(mtexdir)/format.tex: $(mk20tab3)
 	v=$$(awk 'BEGIN{FIELDWIDTHS="41 10000"} !/^#/{print $$2}' \
 	         $(mk20tab3) | uniq | wc -l)
 	echo "\newcommand{\menkenumjournals}{$$v}" >> $@
+
+        # Count how many rows the original catalog has.
+	v=$$(awk '!/^#/{c++} END{print c}' $(mk20tab3))
+	echo "\newcommand{\menkenumorigrows}{$$v}" >> $@
diff --git a/tex/src/figure-inputconf.tex b/tex/src/figure-src-inputconf.tex
index f09bebd..1245dfb 100644
--- a/tex/src/figure-inputconf.tex
+++ b/tex/src/figure-src-inputconf.tex
@@ -1,4 +1,4 @@
-\begin{tcolorbox}
+\begin{tcolorbox}[title=\inlinecode{\textcolor{white}{INPUT.conf}}\hfill\textcolor{white}{(simplified)}]
   \footnotesize
   \texttt{\mkvar{MK20DATA} = menke20.xlsx}\\
   \texttt{\mkvar{MK20MD5}{ }  = 8e4eee64791f351fec58680126d558a0}\\