Extending Ledgrr to model "Model-Feed-Engine" value chains

[djwork]

Extending Ledgrr to model "Model-Feed-Engine" value chains

Graph Data Model
Primative Types

• Engine
  • A process/algorithm/workflow that takes in both “Model” & “Feed” and produces “Product”
  • Long lived, evolves over time
  • Wardley Association = Activity
  • Subclass
    • Software Engine
    • Human Agent
• Model
  • A model of a thing
  • Long lived, evolves over time
  • Usually has a team dedicated to ongoing alignment with the changing state of the entity being modelled
  • Model Versioning is not rigorously applied, or not up to the standard of modern software versioning
  • The structure/content of the model more reflects the needs of the “Engine” than the reality of the entities being modelled (ie power system being modelled as linear equations for use by a linear solver)
  • Wardley Association = Data
• Feed
  • A stream of data
  • Only relevant for a specific slice of time
  • Normally requires a continuous information network connection to another system or an outside entity
  • Streams frequently required a chain of internal and external networks/systems, if any element of the chain breaks the steam is out of service
  • Stream values only make sense in context of the associated Model
  • Wardley Association = Data
  • Subclass
    • Feed Embedded Model
• Product
  • The output ready for delivery
  • Information Based, not a physical thing
  • The Product's Payload is an instance of type "Feed" or "Model"
• Supplier
  • Entity external to the Organization
  • Supplies the Organization with 1 to many "Feed" or "Model" -
• Consumer
  • Entity external to the Organization
  • Receives 1 to many "Product" from the "Organization"

Compsite Types

• Organization
  • Singleton
  • Owner of all "Value Chain"
• Team
  • Workunit of 1 or more Human
  • Belongs to another "Team" or "Organization"
• Component
  • Input 1 to many "Feed"
  • Input 1 to many "Model" or "Feed Embedded Model"
  • Each Input should come from an Output of another Component or from a Supplier
  • A single "Engine"
  • Output 1 to many "Product"
  • Each Output should go to another Component Input or to a Consumer

[elasticdotventures]

Agent: search existing codebase ledgrrr may already have many if not all of these types by different names ex: flux capacitor.

These are high level diagramming & simulation node constructs that represent named repetitive black box containers of abstract logic which have their own modelling & layout rules. The current system being used for modelling these is vision but it would be better to have a DSL such as rhai or equivalent for version controlled modelling and visualization via ledgrrr; ultimately we are building a next generation mbse style tool that includes many different visualization layers (not just physical, logical, and functional)

consider how to use comptime parameticy
https://noelwelsh.com/posts/comptime-is-bonkers/

[elasticdotventures]

the conceptual modelling is in the domain of visualization of https://en.wikipedia.org/wiki/Information_architecture