Skip to content
This repository has been archived by the owner on Aug 25, 2024. It is now read-only.

Latest commit

 

History

History
138 lines (96 loc) · 6.89 KB

0009-Open-Architecture.rst

File metadata and controls

138 lines (96 loc) · 6.89 KB

Open Architecture

Version: 0.0.1 Date: 2022-04-17

Status

Proposed - #1401

Description

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.

Context

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.

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 TODO Overlay if given
  • orchestrator SHOULD be loaded and inspected for compliance with top level system context's policy (sandbox) before execution.

References