Merge pull request #4 from lsst-sitcom/u/kbechtol/update_charge

Clarify charge

introduction.tex

@@ -6,6 +6,12 @@ \section{Introduction}
 The emphasis is distilling and communicating what we have learned about the system.
 The report is organized into sections to describe major activities during the campaign, as well as multiple aspects of the demonstrated system and science performance.
 
+\begin{warning}[Preliminary Results]
+All of the results presented here are to be understood as work in progress using engineering data.
+It is expected at this stage, in the middle of on-sky commissioning, that much of the discussion will concern open questions, issues, and anomalies that are actively being worked by the team.
+Additional documentation will be provided as our understanding of the demonstrated performance of the as-built system progresses.
+\end{warning}
+
 \subsection{Charge}
 
 We identify the following high-level goals for the interim report:
@@ -25,7 +31,8 @@ \subsection{Charge}
 While the analyses in this report will likely overlap with the generation of verification artifacts for systems engineering, and system-level requirement specifications will serve as key performance benchmarks for interpreting the progress to date, formal acceptance testing is not an explicit goal of this report.
 
 \textbf{The groups within the Rubin Observatory project working on each of the activities and performance analyses are charged with contributing to the relevant sections of the report.}
-The anticipated level of detail for the sections ranges from a paragraph up to a page or two of text, depending on the current state of understanding, with quantitative performance expressed as summary statistics, tables, and/or figures.
+The anticipated level of detail for the sections ranges from a paragraph up to a page or two of text, depending on the current state of understanding, with \textbf{quantitative performance} expressed as summary statistics, tables, and/or figures.
+The objective for this document is to \textbf{summarize the state of knowledge of the system}, rather than how we got there or ``lessons learned''.
 The sections refer to additional supporting documentation, e.g., analysis notebooks, other technotes with further detail, as needed.
 Given the timelines for commissioning various aspects of the system, it is natural that some sections will have more detail than others.