Theoretical Foundation
The Theoretical View of the "World"
Graphs, Structure, and Grammar in Project Management
When we shift from pure software architecture to the theoretical view of the "world", we move from engineering into systems theory, ontology, and cybernetics. We're not just building a tool — we're building an ontology model: a model of how reality is structured in your organization.
01 Ontology: The "World" as a Relational Network
Classical management thinks in "objects": a project is a thing, an employee is a thing, a budget is a thing. These things are managed in isolated silos.
Our graph perspective follows a relational ontology (related to Bruno Latour's Actor-Network Theory):
Nothing exists in isolation
An FTE is defined only by their relationships: works on Task X, blocked by Board Y, communicates with Customer Z.
Actors aren't just humans
An RFQ document, CI/CD script, ASPICE audit, and project manager are all equally valid "nodes."
The power of edges
A missing eval board has more "power" in the network than the project manager — because it interrupts the flow.
02 Structure: Hypergraphs and Fractals
A normal graph (node A connects to node B) is too simplistic for the real world. Reality is multi-dimensional.
Hypergraphs
A "Sprint Review" is not a 1-to-1 relationship. It's a hyperedge that simultaneously connects 5 FTEs, 10 tasks, 1 budget pool, and 3 customer features. The system state cannot be described by pairwise relations, only by transactions or contexts.
Fractals / Scale Invariance
A graph looks the same at every zoom level:
The "DC/DC Converter" project is a node, connected to the customer.
The project opens up and is itself a massive graph of HW, SW, QA.
The "SW Implementation" task opens as a graph of code commits, tickets, and pipelines.
Consequence: Our structure is recursive. A node can always itself be a complete graph.
03 Epistemology: From Status Reporting to Spatial Understanding
Classic Reporting
"We are 40% done." — This is an illusion, the myth of the waterfall.
Graph Reporting
"The 'HW Design' subgraph is fully connected, but the 'SW Integration' subgraph has 3 broken edges." — That is topological knowledge.
"We're not building another project tracker. We're building a Digital Twin of project reality. We view projects not as static lists, but as living, relational networks governed by physical laws."
Next Step
Enough theory. Let's check your reality.
What does this mean for your next audit? Instead of telling the assessor "We estimate we're 80% done," show them the graph: "The SW Integration subgraph has 3 broken edges to ASIL-D requirements." Subjective reporting becomes topological, provable knowledge.
The vimpact Data-Readiness Check: 2 weeks, a subset of your data, deterministic gap analysis.
Go to Reality Check →