Pillar 04
Programs
A program is a procedure for transforming a system while tracking what the parts cannot tell you alone. In Synergetics that surplus has a name: synergy.
Synergy as non-summative output
Fuller defines synergy as the behavior of whole systems unpredicted by the behavior of their parts taken separately. That is not mysticism; it is a warning about partition. If you only measure parts in isolation, you will miss relational effects that only exist when the graph is connected.
Programs that assemble, fold, route, encrypt, train, or tensegrity-prestress are synergy engines when their output is not a linear sum of component logs.
§ notes · synergy
Synergy is a methodological commitment: study relationships and closed systems, not only inventories of parts. Alloys, ecosystems, and tensegrity structures are classic illustrations; software and protocols are modern ones.
Procedures on structure
Geometry gives you the graph. Quantum-ish thinking forces discrete steps. Computers run the steps. Programs are the chosen sequence and branch rules — including what to do when equilibrium is intentionally broken (form-finding), when frequency increases (refinement), when modules associate (composition).
Raising frequency in a geodesic or packing model is already a program: “for each module, subdivide by rule R.” The lab on this site makes that rule thumb-sized; manufacturing and compilers scale it.
Programs that respect Universe-cost
Fuller obsesses over ephemeralization and doing more with less — a resource ethic. Programs inherit it when they minimize unnecessary state, reuse structure, and refuse continuum theater that hides discrete waste (compute, energy, attention).
Technical · algorithms
Map: program ≈ rewrite system on a graph; synergy ≈ observable depending on multi-vertex motifs; frequency raise ≈ subdivision operator; VE bias ≈ optimization away from a symmetric fixed point. Test synergy by ablation: remove edges/parts and watch global metrics fail to decompose additively.