Software engineer · systems architect · poet
Kyiv, Ukraine · mind.aiaiaiai.org
I build systems that remain clear when the world becomes complicated.
Most software problems are not code problems. They begin earlier — as blurred intent, weak boundaries, or assumptions that were never turned into contracts.
I work across that entire distance: from the first idea to the architecture, from the architecture to the implementation, and from the implementation to a system a person can actually trust.
My work lives where product, infrastructure, protocols, automation, and AI meet. I care about software that is legible under pressure, provider-agnostic by design, secure at its boundaries, and honest about what it can do.
Built from Kyiv, where reliability is not a slogan and reality reaches production before the roadmap does.
- contracts over assumptions
- predictability over cleverness
- architecture before implementation
- explicit boundaries over invisible coupling
- security enforced in code, not promised in slides
- aesthetics without loss of purpose
- movement without haste
Swift is how I shape public surfaces — safe, readable, and intentional.
Ruby is how I think about private motion — expressive, flexible, and close to the problem.
C is the instrument underneath the instrument — structures, types, memory, algorithms.
Rust and Go enter where infrastructure, portability, and hard boundaries matter.
AI/ML is leverage, not theater.
Poetry is compression without the loss of meaning.
mind— a versioned public context graph for identity, engineering practice, systems, organizations, and writingmcp-control— a read-only host control plane split across a real security boundaryinfraCLI— a runtime-independent infrastructure model expressed through one small declarative contractinfraBot— remote infrastructure interaction designed around explicit authorization and narrow capabilitiesnilx.one / 0x1— a separate project currently centered on0x1, with its public documentation still taking shape0xda-market— an evolving commerce ecosystem built around clean domain boundaries and provider independenceaiaiaiai tech.— the parent engineering organization formind,nilx.one,0xda-market, and related work
These are not isolated projects. They are parts of one direction: software that can explain itself, infrastructure that does not require ritual, and tools that increase human agency without hiding their own behavior.
I believe identity should be portable.
I believe infrastructure should be understandable from first principles.
I believe AI systems should operate through explicit permissions, observable actions, and reversible decisions.
I believe protocols can describe more than machines — they can describe trust, connection, consent, and coordinated action without reducing people to data.
And I believe the best product architecture feels less like machinery and more like inevitability: every part has a reason to exist, and nothing needs to shout.
Poetry taught me that the shortest line can carry the greatest weight.
Engineering taught me that every line must carry its own weight.
I practice both for the same reason: to make complexity breathable.
Code is a decision made executable.
Poetry is what remains when execution is not enough.



