Workflow changed
What process changed, who used the output and where human judgment stayed in the loop.
Selected work
These write-ups are intentionally selective: enough to show the problem shape, system approach, and proof of execution, without exposing internal material that should stay internal. Current public cases draw from in-house work at Delta Holding; external client work is added when disclosure allows.
How to read the proof
Each case is public-safe and selective. The useful proof is the workflow shape, the constraint set, the operating choices and the measured signal.
Workflow changed
What process changed, who used the output and where human judgment stayed in the loop.
System shape
Why the work became a recommendation layer, internal assistant, hardening path or no-build decision instead of generic chatbot work.
Operating constraints
Access, review, ownership, cost visibility and handoff are part of the proof, not implementation detail.
Measured signal
Outcome or adoption is shown only where the measurement is public-safe.
Delta Holding
Case 01A credit-risk decision-support workflow built in-house at Delta Holding. Combines public-company risk signals with internal context into recommendations.
Delta Holding
Case 02A self-hosted internal knowledge assistant built in-house at Delta Holding, with Azure AD access, operator surfaces, and usage + cost observability.
Workflow review
A short note on the workflow, users, current stage, and constraints is usually enough to tell whether build or advisory work makes sense.