You can have working code and still not have a system.
A system has boundaries, contracts, and data flow.
That is what makes it hold in production.
I help teams design systems that actually hold.
AI, data, distributed systems.
Treated as systems — not features.
Three ways to engage. Each is scoped for clarity and a concrete outcome.
Engagement
System Design Advisory
When options conflict or the next step is unclear.
Focused sessions on goals, constraints, and trade-offs — written recommendations you can act on.
Outcome: a decision-ready view of the system you need.
Engagement
Architecture Deep Dive
When the design needs stress-testing before more build cost.
Review of flows, boundaries, failure modes, and data/AI touchpoints — no slide-only theater.
Outcome: risks and fixes ranked by impact.
Engagement
Custom System Design
When you need a blueprint from intent to operation.
Structured design pass — components, interfaces, and evolution path aligned to your constraints.
Outcome: an implementable system picture, not a wishlist.
Plain language. No mystery.
What must be true for this system to succeed?
Before tools or vendors enter the room.
Boundaries and contracts that enforce it.
What still holds when teams, traffic, and regulation scale.
What runs, scales, and fails in production.
How you observe, contain, and correct it when reality disagrees with the plan.
Intent → Structure → System
Where systems meet real constraints. Where the system meets reality — a domain product, not a slide exercise.
A system designed under real constraints.
Not a concept — something that had to work.
Martial arts competition and event software — the domain product this architecture serves.
From vague intent → working system.
Full case study when we publish it.
If this maps to something you’re thinking through — we can always talk. What comes next depends on context.
Discuss your systemField Notes are written in English.
System thinking applied to real problems.
Not a blog. Models and patterns used in practice.
Field Notes: body copy is English-only.
Notes from real systems work — what breaks, what scales, what holds in production. Start with the RAG pattern catalog, then the Field Notes hub.
Explore Field Notes View patternsSeparating delivery artifacts from the operating system you actually need.
PATTERN · DRAFTA compact lens for how retrieval behaves from classic search through modern embeddings to production-grade RAG.
PATTERN · DRAFTWhy a card library beats scattered tips when you need defensible systems thinking.
Shape systems before they exist in code — intent and structure visible before the first merge.
A tool for turning system design into working code.
A workspace for shaping intent into structure before code — contracts, seams, and operational shape on the table before tribal knowledge hardens. No waitlist or data capture on the homepage; the product story comes first.
How GeneStudio worksComing soon
Production over presentation.
Paweł Procaj (Dan Katana) — system designer behind ProLogic Labs
I design and build real systems.
Not diagrams. Not slide decks.
Experience across banking, enterprise, and product systems.
Clear intent.
Explicit structure.
Systems that behave in production.
Technology depth and implementation detail live in Writing (Field Notes in English).
ProLogic — logic on real products and platforms. Labs — experiments shipped with rigor, without needless buzz.
This is how I work with teams — in the open.
If this matches how you think, let's talk.
When you email: rough problem, timeline, constraints — enough to start.
[email protected]