Distinguish engineering mode from survey mode, at SFL

intro.tex

@@ -8,7 +8,7 @@ \section{Introduction}
 \item	Encrypt data using strong, approved encryption standards,  following \citeds{NIST.SP.800-171} for \gls{CUI} at non federal organizations. The required use of these \gls{NIST} security standards is limited to the physical security and encryption points. It does not extend to treating the data as \gls{CUI}. The data should \emph{not} be marked as \gls{CUI}.
 \item	Use firewalls and physical security best practices to prevent unauthorized network  access. Documented compliance shall be in accordance with \citeds{NIST.SP.800-171}.
 \item	Delay public release of  focal plane scientific data for an embargo period of at least 80 hours following the  observation.
-Hold engineering and commissioning imaging data for an embargo period of at least 30 days.
+Hold engineering-mode commissioning imaging data for an embargo period of at least 30 days.
 Data aside from focal plane data may be made available following the original project plan which includes astronomical metadata (within 24 hours), standard \gls{postage stamp} images (within 60 sec) not corresponding to artificial  Earth-orbiting satellites (see Requirement 4), and weather and sky monitoring data.
 NSF and \gls{DOE} require a system in  place to extend the embargo times for the release of focal plane scientific data in the unlikely event that it is needed.
 
@@ -45,8 +45,13 @@ \section{Introduction}
 In the rare event an unknown solar system object source with a streak length greater than 10 \gls{deg}/day relative to sidereal potentially corresponds with an Earth-impacting asteroid, the \gls{USDF} will implement a method to send any candidate impactors to the \gls{MPC} during the embargo period.
 All data in transit shall comply with the strong, approved encryption standards outlined for the embargo period.
 
-In addition, commissioning and engineering data will be embargoed for all non-commissioning team staff for 30 days.
-After this 30 day embargo, only with explicit approval may proprietary data products from commissioning be shared outside the \gls{Commissioning} Team   \citeds{SITCOMTN-010}.
+In addition, commissioning engineering data will be embargoed for all non-commissioning team staff for 30 days.
+After this 30 day embargo, only with explicit approval may proprietary data products from commissioning be shared outside the \gls{Commissioning} Team  \citeds{SITCOMTN-010}.
+
+The transition from the 30-day embargo to an 80-hour embargo will happen at System First Light (SFL), as long as all federal reviews of Rubin Data Management Standards have been passed. 
+NSF and DOE will provide simple email confirmation of this, following the final review outbrief.
+(Prior to SFL, LSSTCam commissioning takes place in ``engineering mode,'' with observations executed in custom blocks that do not resemble routine sky surveying. 
+After SFL, Rubin will switch to ``survey mode,'' with observations executed in schedule blocks similar to those of the LSST.)  
 
 Commissioning Team members are expected to use approved Project tools and processes for communication, data access and analysis, documentation, \gls{software} development, work management, etc.
 In practice, we expect most work done by the \gls{Commissioning} Team on the commissioning data to be done within private directories at the Rubin US Data Facility at SLAC.