document non-normative examples

[monkeypants]

TODO: raise tickets for each of a number of interesting scenarios that seem to validate the utility of the ICL, or seem to highlight relevant issues or challenges.

Conversation in PR #2 suggested removing non-normative scenarios into separate documents. These could be tickets first, then either separate documents or non-normative sections of the document (to be determined.

The comment was:

Maybe we should create non-normative documents (not part of the spec per-se) documenting scenarios, and reference them from this document.

ticket needed: The spec itself does need a scoping statement re: protocol and payloads

* are we talking about artefacts that are linked to a single export event and a single import event? or is that just the simple case...
* is there a consistent signalling pattern {approved, exported, imported} or is this one of multiple supported patterns?

The comment was in relation to this text

#### Example Scenarios
> FIXME  
> provide step by step description of the end to end process for a simple scenario, and a more complex one, focussing on the creation and transfer of documents.   
> Get full list of documents required for a simple case where only additional  
> documentation beyond generic shipment documentation is a Certificate of Origin  
> maybe a wine shipment?  
> 
> as well as all documents required for a more complex scenario, maybe orchids (certificate of origin, CITES, phytosanitary...) as well as full list of parties involved (e.g. Customs, CMA, Quarantine, CoC)