Version: 0.0.1 Date: 2022-04-17
Proposed - #1401
The Open Architecture is a methodology for interpreting directed graphs as any system architecture.
The Open Architecture is fully nocode compatible. It is a process for problem description and solving which can be implemented via arbitrary execution primitives.
This document describes the Open Architecture; a proxy to 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 DIDs between entities and data for provenance. Leveraging verifiable credentials for review system to measure risk in absence of attestation.
Our reference architecture is built around a specs such as SBOM, VDR, and DIDs. We leverage the concept of a Manifest to talk about a node within the graph. A manifest is any document which is aligned with the guidelines within the Manifest ADR. A DID doc is an example of an instance of a manifest.
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 TODO Overlay if givenorchestrator
SHOULD be loaded and inspected for compliance with top level system context's policy (sandbox) before execution.
- System Context
- Manifests
- Overlays
- https://intel.github.io/dffml/main/examples/dataflows.html#combining-operations
- https://oca.colossi.network/guide/introduction.html#what-is-decentralised-semantics
In the domain of decentralised semantics, task-specific objects are called "Overlays". They provide layers of definitional or contextual information to a stable base object called a "Capture Base".
- The DFFML project equivalent vocabulary term for "Capture Base" would probably be "upstream".
- Living Threat Models
- John L Whiteman & John S Andersen, "Living Threat Models", June 11th 2022
- https://github.com/johnlwhiteman/living-threat-models
- An Architecture for Trustworthy and Transparent Digital Supply Chains (IETF/SCITT)
- https://datatracker.ietf.org/doc/charter-ietf-scitt/
- https://datatracker.ietf.org/doc/html/draft-birkholz-scitt-architecture
- #1406 (reply in thread)
- https://docs.google.com/document/d/1vf-EliXByhg5HZfgVbTqZhfaJFCmvMdQuZ4tC-Eq6wg/edit?pli=1#
- https://github.com/ietf-scitt/use-cases/blob/main/hardware_microelectronics.md
- ietf-scitt/use-cases#14
- GUAC: Graph for Understanding Artifact Composition
- DIDs
- https://github.com/pdxjohnny/pdxjohnny.github.io/blob/dev/content/posts/2022-03-02-did-twitter-space.md
- https://github.com/WebOfTrustInfo/rwot5-boston/blob/master/topics-and-advance-readings/did-primer.md
- https://github.com/SmithSamuelM/Papers/blob/master/whitepapers/A_DID_for_everything.pdf
- IPVM
- TODO
- Add content from discussion thread
- docs/arch/alice/discussion/0004/reply_0005.md
- docs/arch/alice/discussion/0023/reply_0020.md
- docs/arch/alice/discussion/0023/reply_0022.md
- docs/arch/alice/discussion/0023/reply_0028.md
- docs/arch/alice/discussion/0023/reply_0037.md
- docs/arch/alice/discussion/0023/reply_0040.md
- docs/arch/alice/discussion/0023/reply_0055.md
- docs/arch/alice/discussion/0036/reply_0022.md
- docs/arch/alice/discussion/0036/reply_0045.md
- docs/arch/alice/discussion/0036/reply_0062.md
- docs/arch/alice/discussion/0036/reply_0066.md
- docs/arch/alice/discussion/0036/reply_0067.md
- docs/arch/alice/discussion/0039/index.md
- docs/tutorials/rolling_alice/0000_architecting_alice/README.md
- docs/tutorials/rolling_alice/0000_forward.md
- docs/tutorials/rolling_alice/0000_preface.md
- docs/tutorials/rolling_alice/README.md
- Add content from discussion thread