System Requirements

A valid QELLVIS system consists of two lists: nodes and dependencies.

• • Nodes must contain a unique id and a numeric load value
• • Dependencies must define a directional relation: from → to
• • Status is optional and may be included on nodes
• • No additional metadata is required

{
  "nodes": [
    { "id": "A", "load": 10 },
    { "id": "B", "load": 0 }
  ],
  "dependencies": [
    { "from": "A", "to": "B" }
  ]
}

QELLVIS accepts multiple payload formats for flexibility.

• • payload — primary format
• • system — alternative key
• • record — alternative key
• • data — alternative key
• • graph — alternative key

Systems must meet the following technical constraints to ensure deterministic engine execution.

• • Maximum 2,000 nodes
• • Maximum 8,000 dependencies
• • Maximum payload size: 250 KB
• • Must be valid JSON

Systems delivered through QELLVIS Connect must satisfy additional requirements for browser‑based fetching.

• • External API must allow POST and OPTIONS
• • External API must allow Authorization header if used
• • External API must return nodes and dependencies
• • External API must implement CORS

QELLVIS is domain‑agnostic. Any system with nodes and directional dependencies is compatible.

• • Microservice architectures
• • Event‑driven systems
• • Data pipelines
• • ETL / ELT flows
• • Task dependency graphs
• • Workflow engines
• • Supply chain structures
• • Manufacturing chains
• • CI/CD pipelines
• • Kubernetes dependency graphs
• • CRM / ERP process flows
• • Any graph‑based system