Graph engineering over scale

    by Vojtech: Tech

    You've seen the spec sheet: 2.8 trillion parameters, 16 experts firing per token. But raw size isn't the game. Graph engineering is. Agents as nodes, tasks as edges. One agent builds, another checks, a third routes. Memory lives in the graph, not the prompt. Loops keep running until the work is actually done, not until tokens run dry. No single call carries the whole job. Work moves through a network where each node does one thing well. Throw a trillion parameters at a problem? Instead, route it through a graph a fraction of the size and you hit the same result for a third of the cost. Structure beats scale.

    Transcript (en)

    .