EdgeNode Ontology and Domain Model
The EdgeNode domain model is built upon a formal mathematical ontology that cleanly separates static graph topology, domain context (semantics), artifact transformation dynamics (processes), resource allocation, and integration superstructures.
- Topological Foundation: Nodes and Edges define the system framework and hierarchy.
- Semantic Layer: Contours group Definitions and Relations into explicit conceptual contexts.
- Dynamic Layer: Streams govern artifact lifecycles via intra-node Cycles and inter-node Transactions.
- Resource Base: Roles and Assets define compensation rates, degradation (entropy), and RACI governance.
- Superstructures: Plans and Digital Twins enable inter-stream automation and priority-driven contour aggregation.
1. Node — Basic Structural Element
A Node represents the base anchor element of the graph topology. At the fundamental level, a node is decoupled from any specific subject domain: it acts as a generic spatial anchor where operations occur, assets reside, or organizational units are situated.
| Property | Ontological Meaning | Axiomatic Rule |
|---|---|---|
| Identifier (ID) | Unique address of the entity in the graph space. | Generated automatically, immutable throughout the entity lifecycle. |
| Parent Node (Parent ID) | Reference to the enclosing scope for hierarchical decomposition. | A node cannot be its own parent. Root-level nodes have an empty parent reference. |
Node Axiomatics
- Hierarchical Nesting (Decomposition)
- Each node can encapsulate an entire child subgraph. This enables system modeling across arbitrary abstraction levels, from high-level system context down to internal functional modules.
- Cascade Integrity
- Removing a parent node from the model cascades to all nested child nodes, along with their associated cycles and definitions, preventing orphaned references.
- Primacy of Form Over Meaning
- A node acquires domain meaning only when bound to a Definition within a Contour or a Cycle within a Stream.
2. Edge — Directed Topological Connection
An Edge represents a unidirectional vector between two nodes. It establishes the fundamental capability of interaction by defining a "source target" relationship.
Edge Axiomatics
- Directionality: An edge is strictly asymmetric; the pair (Node A Node B) is not identical to (Node B Node A).
- No Base Self-Loops: An edge cannot connect a node to itself; the source and target must be distinct. Self-processing operations within a single node are modeled via Cycles.
- Base Edge Uniqueness: Only one base topological edge may exist between two specific nodes in a single direction. However, that single edge can be concurrently utilized across multiple contours and streams.
3. Contour & Semantic Layer: Definition and Relation
A Contour defines a logical boundary or domain context of modeling (e.g., organizational structure, software architecture, or physical facility layout). Within a single contour, nodes and edges receive unambiguous semantic classifications.
3.1. Node Definition
A Definition classifies an abstract node within a specific contour and links it to an Accountable role (A in RACI):
| Definition Type (definition_type) | Domain Purpose | System Analysis Example |
|---|---|---|
process |
A function, procedure, or transformation activity. | Quality audit, code compilation, mechanical assembly. |
structural_unit |
An organizational entity or governance unit. | R&D Department, QA Team, Assembly Workshop. |
location |
A physical or virtual facility/placement. | Server rack, production site, regional warehouse. |
artifact |
A passive physical or digital asset at rest. | Document repository, database, component inventory. |
concept |
An abstract term, policy, or business requirement. | Security standard, compliance rule, target KPI. |
3.2. Relation
A Relation specifies the semantic link between nodes along an existing base edge within a specific contour and can reference a Consulted role (C in RACI):
- composes
- Aggregation/decomposition relationship: one element structurally constitutes another.
- extends
- Specialization/inheritance: the target element expands or refines the baseline functionality.
- couples
- General associative, collaborative, or communication link.
- requires
- Hard functional dependency: the source element cannot operate without the target.
- constraints
- Regulatory, technical, or temporal constraint imposed on another entity.
- influences
- Indirect or probabilistic impact without a rigid functional constraint.
- aligns
- Alignment or compliance with an external standard, policy, or goal.
- alternates
- Alternative execution option, redundancy, or XOR branching.
- characterizes
- Specification of an attribute, quality, or quantitative property.
4. Stream & Dynamic Layer: Cycle and Transaction
A Stream defines the end-to-end pathway and transformation lifecycle of a specific artifact type through the graph. A stream models the behavioral aspect of the system as a state machine.
- Each stream must possess exactly one global entry node with an origin state of
(entry). - Each stream must possess exactly one global exit node with a target state of
(exit). - The sentinel state
(entry)cannot be a target state, and(exit)cannot be an origin state for any operation.
Artifact Classifier (artifact type)
The artifact type designates the informational or physical nature of the entity traversing the stream: requirement, design, document, code, digital_asset, prototype, part, and assembly.
4.1. Cycle
A Cycle is an intra-node operation that transforms an artifact from an origin state into a target state over a specified duration under the oversight of a Responsible role (R in RACI).
4.2. Transaction
A Transaction is the directed transfer of an artifact from one node to another along a base topological edge. It is characterized by a latency interval, a queuing priority, and an Informed role (I in RACI).
4 Artifact Realization Paths
The combination of cycles and transactions creates executable dynamic subgraphs. The system calculates 4 distinct realization paths:
- Optimal Path: A balanced trajectory minimizing weighted time, financial cost, and degradation risk.
- Priority Path: A trajectory routed strictly along transactions holding the highest queuing priority.
- Fastest Path (Critical Path): The route with the shortest cumulative duration of operations and transfer latencies.
- Cheapest Path: The trajectory with the lowest financial cost across labor wages and asset depreciation.
5. Role — Labor Economics and the RACI Matrix
A Role defines an actor within system operations (job position, external contractor, or automated service) associated with a defined wage rate. Roles allow the system to automatically build an end-to-end RACI matrix.
Rate Units (rate unit)
Labor costs for roles are normalized to a consistent operational time unit:
hour— Hourly billing rate;day— Daily rate (standard 8-hour workday);week— Weekly rate (sprint / iteration interval);month— Monthly salary baseline.
RACI Governance Mapping
EdgeNode enforces a strict one-to-one mapping between the RACI matrix and schema entities:
| RACI Designation | Governance Function | Target Entity in EdgeNode | Scope of Responsibility |
|---|---|---|---|
| A — Accountable | Accountable (approves/owns the definition) | Node Definition (Definitions) | Holds ultimate accountability for the semantic classification of the node in the contour. |
| R — Responsible | Responsible (executes the task) | Processing Cycle (Cycles) | Directly executes the transformation of the artifact state over the cycle duration. |
| C — Consulted | Consulted (two-way expert input) | Contour Relation (Relations) | Engaged as a subject matter expert when defining the relation parameters between nodes. |
| I — Informed | Informed (one-way notification) | Transfer Transaction (Transactions) | Receives notifications upon the completion and dispatch of an artifact between nodes. |
6. Asset & Derivatives: Cycle Assets, Entropy, and Costs
An Asset represents a tangible, computational, or licensed capital resource associated with a fixed initial purchase cost.
Derivative Entity: Cycle Assets
Represents the allocation of an asset to a specific intra-node operation. It is defined by two metrics:
- Amount: The count of resource units allocated to the cycle.
- Entropy: The wear coefficient, degradation rate, or failure probability of the asset per cycle. Entropy is bounded in a normalized range from 0 (zero degradation) to 1 (complete depletion or write-off).
Cost Axiomatics
- CAPEX (Capital Expenditures): Cumulative purchase cost of all registered capital assets.
- OPEX (Operational Expenditures): Total cost of labor across responsible roles during cycle durations plus the depreciation wear of assets based on entropy values.
- TCO (Total Cost of Ownership): Integral cost of the modeled system combining total CAPEX and accumulated OPEX.
7. Plan & Digital Twin — Integration Superstructures
Plans and Digital Twins are high-level aggregates that integrate semantic graph topology with dynamic artifact streams.
| Superstructure | Core Aggregation | Complementary Axis | Primary Analytical Function |
|---|---|---|---|
| Plan (Plan) | Streams and inter-stream trigger rules (Pipelines). | Contours (enrich nodes with semantic meaning). | Event orchestration, total plan duration calculation, and semantic density analysis. |
| Digital Twin (Twin) | Contours with assigned conflict resolution priorities. | Streams (enrich nodes with computability). | Domain focusing, end-to-end throughput calculation, and bottleneck detection. |
7.1. Plan Automation Pipelines (Plan pipelines)
A Plan Pipeline specifies a reactive cross-stream trigger: an artifact in a trigger stream reaching a designated state automatically initiates execution in a dependent target stream.
Orchestration Axiom: A stream cannot act as its own direct trigger within a single pipeline rule (preventing recursive self-invocation without intermediate stages).
7.2. Digital Twin and Contour Priorities (Twin contours)
A Digital Twin aggregates multiple contours into a single unified analytical view.
Conflict Resolution Axiom: If a node possesses conflicting definitions across aggregated contours, the definition belonging to the contour with the highest priority rank takes precedence. Every contour assigned to a twin must possess a strictly unique priority rank.