This epic covers delivery of an end-to-end workflow for the generation and publication of notebook-based reports (such as the characterisation report). To avoid pollution of the existing namespace and to support additional features, these will be published as a new series (eg DMQA). 

The principal steps are:

• Following some data reprocessing workflow [the ability to trigger and execute that workflow is an outside deliverable]
• Metrics of interest are dispatched to the SQuaSH via lsst_verify
• A notebook in jellybean is generated from a template and pulls in the specific values requested [this step will be manual, at least in this epic's scope]
• The notebook is "unit-tested" and run
• The resultant notebook+output is an artifact published through LtD

More information will be provided in a design note. Note that we intend that the template notebook is the primary publication and a particular execution is an issue - eg. the science pipelines characterisation notebook is DMQ-001 and the their installment is DMQ-001-0003 (or perhaps DMQ-001-(datestamp) - discussions will be had with the DM Systems Engineer I am sure)