Wesley SteehouwerArchitecture remains the constant.
I work on systems because systems reveal where reality resides. Infrastructure, security, networks, distributed environments, operating models, and now AI all present the same underlying question: how parts interact, where failure accumulates, and where durable advantage can be designed rather than assumed.
Two decades of operational depth across infrastructure, networks, security, and distributed systems.
- 2005 to 2010
Hosting, systems administration, FreeBSD and Linux estates, switching, firewalling, identity provisioning, and early architectural work. - 2010 to 2015
Network architecture across datacentres, carriers, rail, aviation, and enterprise environments, covering BGP, MPLS, QoS, migration design, vendor transitions, and large-scale operational change. - 2015 onwards
Architecture, security, automation, retained advisory work, solution engineering, API integrations, and event-driven systems.
The work spans Brocade, Juniper, Cisco, VMware, Active Directory, telecom integrations, security architecture, distributed environments, Kafka-based systems, and incident analysis. The continuity lies in practical design for environments in which errors compound quickly.
Applying systems thinking to AI and execution support.
My present work extends into AI, not as a break from earlier domains, but as the next expression of the same discipline. The question remains architectural: how context is preserved, how decisions propagate, how constraints are enforced, and how execution continues without repeated reconstruction.
Abel is complementary to that role. I provide architecture, judgement, direction, and standards. Abel is being shaped to provide continuity, operational memory, coordination, and follow-through. Distinct functions, one system. Further detail sits on /abel.
Useful systems make structure and trade-offs explicit.
- Clarity over simplification.
Exact language is operationally important. - Continuity over isolated output.
A system should remain coherent across time. - Constraint over theatre.
Useful systems understand their limits.
- Traceability over convenience.
Important actions should be reviewable. - Architecture over features.
Tools matter less than system shape. - Operational fit over broad appeal.
Not every system belongs in every environment.