Public product evidence
I publish TraceHawk source, a guided demo, reproducible verification gates, screenshots, and explicit production limits.
Review the TraceHawk evidence →Systems engineering · automation · internal software
I design and improve reliable digital systems, automation workflows, and data-driven tools that make complex work clearer, safer, and easier to maintain.
My work connects software delivery with operational reality. I build internal applications, infrastructure-aware services, reporting workflows, and evidence-driven technical documentation for environments where maintainability and precise execution matter.
Verifiable signals
I separate public evidence from private operational context. These entry points show source code, a constrained live product, a verified credential, and bounded case studies without exposing restricted systems.
I publish TraceHawk source, a guided demo, reproducible verification gates, screenshots, and explicit production limits.
Review the TraceHawk evidence →I document my Microsoft Azure Fundamentals credential separately from broader Microsoft community and learning work.
Review the AZ-900 evidence →I maintain eleven project case studies that state my role, constraints, outcome type, public evidence, and proof limits.
Compare the case studies →Featured work
I select projects that show different parts of my engineering range: a public security product, a private infrastructure data system, and a public workflow library. Each project page states what can and cannot be independently verified.
Public source and demo
I built a local-first security investigation workspace with deterministic YAML detection, multi-source cases, line-level evidence, bounded live monitoring, local AI, and redactable reports.
Evidence: public source, guided demo, screenshots, release artifacts, and verification gates.
Open case studyPrivate operational system
I worked on a PostGIS-backed web platform for structured infrastructure data, geometry-aware workflows, schema evolution, and safer downstream reporting.
Proof limit: operational data and detailed infrastructure views remain private; the public page documents architecture and engineering decisions.
Open case studyPublic workflow library
I maintain a public, interactive catalog of reusable engineering skills with searchable source documents, repository-backed activity, and explicit evidence boundaries.
Evidence: the interactive explorer exposes the current public-safe skill snapshot and source files directly.
Open workflow libraryExperience
I build Microsoft 365 reporting and access-review tooling, and develop local AI infrastructure. My goal is an internal RCUM AI assistant; the current work includes architecture, component pilots and evaluation.
I extend a Django/MySQL platform for measurement processing, corrections, tariffs, visualization and monitoring. I track production improvements, local verification and pilot acceptance separately.
I developed a bilingual Astro website and Django/PostgreSQL editorial CMS with preview, revisions, scheduled publishing, media workflows and technical SEO.
My EUDOM project →Research and learning
I keep verified credentials, active research, and community learning separate. A credential proves a defined milestone; a working paper remains active research until a stable artifact exists; community participation is not presented as an official title without direct confirmation.
Contact
I am based in Slovenia and use LinkedIn for professional conversations about software, automation, and operational systems.