docs: arch: open architecture: Restructure and add references

References grabbed via case insensitive search for: open architecture

.. code-block:: console

    $ git grep -i open\ architecture | sed -e 's/:.*//g' | sort | uniq

Signed-off-by: Alice A <[email protected]>
Signed-off-by: John Andersen <[email protected]>

Author: Open Architecture Working Group

docs/arch/0009-Open-Architecture.rst

@@ -1,63 +1,81 @@
-Open Architecture Working Group
-Internet-Draft
-Intended status: Draft
-Expires: June 1, 2023
-                                                                  March 12, 2022
-
-
-      Open Architecture: Methodology for interpreting directed graphs as
-                          any system architecture
-
-Abstract
-
-   This document describes the Open Architecture, aka Alice; a proxy format
-   for domain specific representations of architecture.
-
-   The Open Architecture is a methodology for intepretation of exisitng
-   well established, formats, protocols, and other domain specific
-   representations of architecture. We define a methodology for interpreting
-   a directed graph representing a system architecture.
-
-   We provide implementations which interpret those graphs as software and hardware
-   architectures.
-
-Status of This Memo
-
-   This Internet-Draft will be submitted in full conformance with the
-   provisions of BCP 78 and BCP 79.
-
-   This draft will expire on June 1st, 2023.
-
-Table of Contents
-
-   1.  Introduction
-   2.  References
-
-1.  Introduction
-
-   The Open Architecture enables hybrid on/off chain smart contacts.
-   It does this by incorporating risk management into architecture definition /
-   smart contract. Smart contracts with understanding of risk are effectively
-   entities making decisions based on models. This allows for mutation in
-   implementation while maintaining principles.
-
-   The smart contract is able to make its own decisions based on learned
-   experience so as to continue to operate until its strategic goals are meet.
-   As measured by oracle data ordained from trusted parties as is
-   applicable to context. Where chains of trust are established via Peer DIDs
-   between entities and data for provenance. Leveraging verifiable credentials
-   for review system to measure risk in absence of attestation.
-
-2.  References
-
-2.1.  Normative References
-
-2.2.  Informative References
-
-   [alice-reveiw]
-              DFFML Authors, "Alice", May 2022,
-              <https://github.com/intel/dffml/pulls/1401>.
-
-   [living-threat-models]
-              John L Whiteman & John S Andersen, "Living Threat Models", June 11th 2022,
-              <https://github.com/johnlwhiteman/living-threat-models>.
+Open Architecture
+#################
+
+Version: 0.0.1
+Date: 2022-04-17
+
+Status
+******
+
+Proposed
+
+Description
+***********
+
+The Open Architecture is a methodology for interpreting directed graphs as
+any system architecture.
+
+Context
+*******
+
+This document describes the Open Architecture; a proxy format for domain
+specific representations of architecture.
+
+The Open Architecture is a methodology for intepretation of exisitng
+well established, formats, protocols, and other domain specific
+representations of architecture. We define a methodology for interpreting
+a directed graph representing a system architecture.
+
+We provide implementations which interpret graphs as software and hardware
+architectures.
+
+The Open Architecture also enables hybrid on/off chain smart contacts.
+It does this by incorporating risk management into architecture definition /
+smart contract. Smart contracts with understanding of risk are effectively
+entities making decisions based on models. This allows for mutation in
+implementation while maintaining principles.
+
+The smart contract is able to make its own decisions based on learned
+experience so as to continue to operate until its strategic goals are meet.
+As measured by oracle data ordained from trusted parties as is
+applicable to context. Where chains of trust are established via Peer DIDs
+between entities and data for provenance. Leveraging verifiable credentials
+for review system to measure risk in absence of attestation.
+
+Intent
+******
+
+- ``upstream`` MUST be treated as the document itself if the document is a
+  domain sepcific architecture or manifest already.
+
+- ``overlay`` MUST be applied to upstream following overlay application process
+  describied in [0010-Overlay.rst](https://github.com/intel/dffml/blob/alice/Overlay) if given.
+
+- ``orchestrator`` SHOULD be loaded and inspected for compliance with top level
+  system context's policy (sandbox) before execution.
+
+References
+**********
+
+- Living Threat Models
+  - John L Whiteman & John S Andersen, "Living Threat Models", June 11th 2022
+  - https://github.com/johnlwhiteman/living-threat-models
+- TODO
+  - Add content from discussion thread
+    - [docs/arch/alice/discussion/0004/reply_0005.md](https://github.com/intel/dffml/blob/alice/docs/arch/alice/discussion/0004/reply_0005.md)
+    - [docs/arch/alice/discussion/0023/reply_0020.md](https://github.com/intel/dffml/blob/alice/docs/arch/alice/discussion/0023/reply_0020.md)
+    - [docs/arch/alice/discussion/0023/reply_0022.md](https://github.com/intel/dffml/blob/alice/docs/arch/alice/discussion/0023/reply_0022.md)
+    - [docs/arch/alice/discussion/0023/reply_0028.md](https://github.com/intel/dffml/blob/alice/docs/arch/alice/discussion/0023/reply_0028.md)
+    - [docs/arch/alice/discussion/0023/reply_0037.md](https://github.com/intel/dffml/blob/alice/docs/arch/alice/discussion/0023/reply_0037.md)
+    - [docs/arch/alice/discussion/0023/reply_0040.md](https://github.com/intel/dffml/blob/alice/docs/arch/alice/discussion/0023/reply_0040.md)
+    - [docs/arch/alice/discussion/0023/reply_0055.md](https://github.com/intel/dffml/blob/alice/docs/arch/alice/discussion/0023/reply_0055.md)
+    - [docs/arch/alice/discussion/0036/reply_0022.md](https://github.com/intel/dffml/blob/alice/docs/arch/alice/discussion/0036/reply_0022.md)
+    - [docs/arch/alice/discussion/0036/reply_0045.md](https://github.com/intel/dffml/blob/alice/docs/arch/alice/discussion/0036/reply_0045.md)
+    - [docs/arch/alice/discussion/0036/reply_0062.md](https://github.com/intel/dffml/blob/alice/docs/arch/alice/discussion/0036/reply_0062.md)
+    - [docs/arch/alice/discussion/0036/reply_0066.md](https://github.com/intel/dffml/blob/alice/docs/arch/alice/discussion/0036/reply_0066.md)
+    - [docs/arch/alice/discussion/0036/reply_0067.md](https://github.com/intel/dffml/blob/alice/docs/arch/alice/discussion/0036/reply_0067.md)
+    - [docs/arch/alice/discussion/0039/index.md](https://github.com/intel/dffml/blob/alice/docs/arch/alice/discussion/0039/index.md)
+    - [docs/tutorials/rolling_alice/0000_architecting_alice/README.md](https://github.com/intel/dffml/blob/alice/docs/tutorials/rolling_alice/0000_architecting_alice/README.md)
+    - [docs/tutorials/rolling_alice/0000_forward.md](https://github.com/intel/dffml/blob/alice/docs/tutorials/rolling_alice/0000_forward.md)
+    - [docs/tutorials/rolling_alice/0000_preface.md](https://github.com/intel/dffml/blob/alice/docs/tutorials/rolling_alice/0000_preface.md)
+    - [docs/tutorials/rolling_alice/README.md](https://github.com/intel/dffml/blob/alice/docs/tutorials/rolling_alice/README.md)