Systems Architect · Est. 2004
Architecture that survives contact with reality.
I help engineering teams design identity, protocol, and data systems that remain understandable as they scale — and as the people, tooling, and trust models around them change.
01 · Overview
Architectural judgment, not tool familiarity.
I am a software solution architect and full-stack engineer with more than 20 years of professional experience designing, building, modernizing, and operating complex software systems.
My career spans enterprise platforms, developer tooling, distributed systems, data-intensive applications, and emerging decentralized infrastructure — across Microsoft and Linux ecosystems, from early client/server architectures through modern cloud-native and protocol-driven systems.
What distinguishes my work is not familiarity with tools, but architectural judgment — knowing which decisions matter, when they matter, and how teams will live with them.
02 · What I do
Design systems teams can live with for years.
Scale without collapse
Architectures that remain legible and operable as codebases, teams, and responsibilities grow.
Change without rewrites
Explicit boundaries and predictable failure modes, so systems survive personnel and technology change.
Legacy meets modern
Integration layers that connect decades-old systems with cloud-native and protocol-driven platforms — safely.
Trust as first-class
Identity, data provenance, and authorization treated as architectural concerns, not afterthoughts.
03 · Domains
Where I’ve designed & delivered.
I am equally comfortable working at whiteboard, codebase, and operational levels — and I expect architectures to survive contact with reality.
04 · AI & emerging tech
Architectural forces, not consumer tools.
My recent focus is the architectural implications of generative AI, agent-based systems, and decentralized infrastructure — how they alter system boundaries, governance models, and long-term sustainability.
AI Agent Systems
How generative and agent-based AI reshapes system design, operational boundaries, and governance.
Protocol Engineering
Lockb0x Codex Forge — a Chrome extension for secure, verifiable digital provenance with cryptographic proofs.
Decentralized Infrastructure
Trust models, financial primitives, and enterprise integration patterns across Stellar, IPFS, and UCC Article 12.
AI Portfolio
An active portfolio of certification labs, experiments, and reference implementations. See Continuing Education.
05 · Philosophy
Architecture is decision-making under constraint.
Good architecture answers hard questions early:
- What must not fail
- What must scale
- What must remain flexible over time
- What can be allowed to change — and what cannot
My approach favors explicit boundaries, predictable failure modes, and systems that can evolve without rewrites.
06 · Public work
Reference implementations over demos.
My public repositories are intentionally architectural in nature — reusable system components, not one-off solutions. They emphasize explicit handling of identity, trust, and integration boundaries.
Stellar Identity Framework
Blazor component library that simplifies blockchain-backed authentication integration.
Pakana
Decentralized deliverables and escrow solution integrating Azure, IPFS, and Stellar.
Lockb0x Protocol
Classifies and manages private on-chain assets with hash identifiers, de-identified metadata, and zk-proof rollups under UCC Article 12.
Reusable .NET components
Identity-aware ASP.NET frameworks and Razor component systems maintained as living examples.
07 · How I work
Best with teams facing complexity and long-term responsibility.
My contribution is rarely just code — it is helping teams understand:
- Which problems are real
- Which problems are premature
- Which problems are inevitable
The goal is not architectural purity, but systems teams can live with for years.