Software Management Procedure
*****************************

.. for revisions, put the full system revision in, so that the entire
   QA/documentation package is always at the same global revision.
   For instance if a doc is introduced at rev 2.1.2, then that should
   be listed as the version of initial release. And then if it's changed
   next at 2.4.22, that will be the next entry

.. list-table:: Revisions
   :widths: 20 80
   :header-rows: 1

   * - Version
     - Change summary
   * - 0.1.0
     - Initial release


Purpose
=======

Scope
=====

Definitions
===========

Roles & Responsibilities
========================

Design Authority
----------------

Design Agency
-------------

Design Agency Manager
---------------------

Quality Reviewers
-----------------

Independent Reviewers
---------------------


Requirements
============

General
-------

References
==========

Records
=======

Forms
-----
.. Hmm problem: when rendering individual PDFs of each proc the linked requirements
    are not available. So they'd show up in the HTML version, or a master PDF of all
    docs, but not in individual procs. Maybe that's a bug not a feature, and we can
    suppress in all pdfs with .. only html or whatever? Oof but then even the footnotes
    wouldn't have a target in the PDFs.... this needs more thinking

This section explains how this procedure meets the linked
regulatory commitments and links to specific requirements.

.. note:: This can help explain why the procedure is designed
    the way it is to aid in future improvements.


.. [sn1] Document things

    .. impl:: Think software here
        :links: R_APPB_39

        Hi there.