Spectral Engineering | Alex Wolf

Your org chart says one thing.
Your communication graph says another.

The graph is right.

The offering

Bi-directional socio-technical engineering. DGSF-certified. Supervised.

The human informs the tech. The tech informs the human. That's the loop. I'm the translation node.

I embed with your team. I measure your communication topology with spectral. Not your org chart. The actual communication topology of your organization. The code. The pull requests. The tickets. The slack messages. All local. On your infrastructure. We measure what's there. Not what's described. Not "who says what?" But "who talks to whom when in which function?"

We don't look at what people say. That data stays invisible. We look at how your organization connects.

The measurement informs the intervention. The intervention produces a new graph. The new graph refines what spectral knows about socio-technical systems. The loop repeats.

This is not consulting. This is not a tool. It's the practice of deriving technology from human behavior and feeding the learning back. Bi-directional.

What I measure

Fiedler value.
How close your organization is to splitting in two. I measure it. I show you the number. Then we talk about what it means.

Star-graph detection.
One person connected to everyone, everyone connected only through them. The bus factor made mathematical. The architect who IS the architecture. spectral identifies these topologies. Then we decide what to do about them — together.

Communication bottlenecks.
Where information actually flows. Where it doesn't. Where two teams think they're collaborating but the graph says they're passing messages through a single person who never signed up for that role.

Load distribution.
Who carries the glue work. Who carries the ambiguity. Who carries the context that isn't written down anywhere. The graph shows it. The number confirms it. No narratives required.

What `spectral` does

Local-first runtime. Formally verified compiler. 450-parameter graph navigation model. Content-addressed package manager at garden.spectral.engineer (ETA June).

It runs on your infrastructure. Your data stays. The runtime does not phone home. Content never leaves the machine. What leaves — if you opt in — are eigenvalues. Thirteen numbers. The shape of your topology. Not the content.

What changes

Decisions converge instead of looping
Incidents produce fewer narratives and more agreement
Responsibility becomes explicit without blame
Leaders stop carrying unbounded ambiguity alone
The person who was silently load-bearing gets visible

This is upstream work. Before tech debt. Before burnout. Before the third reorg that solves nothing.

Is this real?

Yes.

About me

Hi, I'm Alex.
(they/them)

Neuroqueer (AuDHD). Systemic engineer.
Supervised systemic practitioner (DGSF-certified, in training).
15 years building distributed systems.
Scientific Programming degree from Europe's biggest supercomputing centre.
Three burnouts. Still shipping.

My brain works differently from most people. Where people see stories, I see Ricci flows. Where people see a party, I see a social topology. Where people see polite conversation, I see no new information.

I didn't choose to be like this. And for most of my life I didn't understand the shape of my particular nervous system. I do now. systemic.engineering is the formalization of that understanding. mirror the compiler that produces spectral triples, a mathematical object that also describes the shape of my cognition. spectral the runtime built on top, the 15 years of distributed system's engineering put to good use.

The math measures the graph. The graph doesn't lie. I help you handle the ripples of your gap.

EU compliance

GDPR. AI Act. Digital Services Act. spectral provides compliance by construction. Consent architecture. Anti-extraction. Data locality. Not a checklist you maintain. Architecture that makes violation structurally difficult.

The license

All work is governed by the systemic.engineering License (SEL). Three structural commitments:

Anti-extraction. Cognitive labor has value. The license names it and creates liability.
Consent architecture. Every offer genuinely declinable. Silence is not consent.
Duty of care. I accept a duty of care toward downstream users of any system I help you build. So do you, by working with me.