This is how the pieces fit together:

- An OOPS entry is the leaf entity.  It contains some specific
  information that is considered valuable to understand how a
  given event, or the succession of events, happened.  A traceback,
  for instance, is a good candidate to be an OOPS entry.

- The OOPS itself is a composition of OOPS entries.  Its goal
  is to store a collection of details for the timespan of a given
  event (e.g. a request), so that understanding what happened is easier.

- The OOPS manager is an utility which keeps track of all the OOPSes
  in progress in the system by well known names, so that any piece of
  code is able to retrieve a given OOPS and enrich it with details.
