damir / ai.
02 / Technical evidence

Inspect the code.
Check the result.

Public examples with explicit scope, reproducible checks and clear limitations. Internal project names and proprietary implementation details are withheld.

A small example.
A reproducible check.

Written for this portfolio. It is a public reference example, not a client case study or an excerpt from an internal project.

Python / standard library / public example

Check a process result before reporting success

Problem: A process can print an expected message and still exit with an error.

Approach: Require both a zero exit code and an exact expected output line.

def check_result(result, expected):
    return (
        result.returncode == 0
        and expected in result.stdout.splitlines()
    )

Observed local result: 5/5 checks passed on 26 October 2026: success with expected output; nonzero exit despite expected output; missing expected output; empty output; and one real local subprocess.

python process_check.py
# Expected final line:
# 5/5 checks passed
Download the full runnable example →

Scope: a basic exit-status and output check. It does not authenticate the process, prove an external action occurred or establish production security. Tested in this site's development environment; other environments have not been verified.

What a scoped engagement can deliver

Evidence you can inspect

  • A reproducible problem description and acceptance criteria.
  • The agreed correction or configuration change.
  • Commands and outputs for the checks actually performed.
  • Usage notes, known limits and a clear handover.

Private source code and internal architecture are shared only where authorised and necessary for the agreed work.

Describe your technical problem →