How this portfolio was made

You should know exactly what you are looking at.

The situations are invented so I can show the work without borrowing a client’s story. The judgment, tools, documents, code, and design are mine. Here is the line between them.

The scenarios are invented

Organization names
Budgets and timelines
Vendor choices
Project data
Staffing and pricing
Any illustrative result

The thinking is mine

Questions and diagnosis
Frameworks and recommendations
Interactive tools
Templates and documents
Visual design and code

What I will not imply

That fictional results really happened
That client work is mine to publish
That an employer approved these demonstrations
That AI output equals professional judgment

AI, plainly stated

I used it. I did not hand it the steering wheel.

The interesting question is not whether AI touched the work. It is whether I can explain what it did, what I checked, and which decisions remained mine.

I used AI for speed, not authority

It helped me pressure-test structure, draft scenario language, generate safe fictional data, and accelerate routine code. Those are useful jobs for it.

I did not outsource the decisions

I chose the problems, questions, tradeoffs, recommendations, interactions, and boundaries. If a tool gives weak advice, that is my design problem—not the model’s excuse.

I checked what a visitor can test

I ran the interactive tools end to end, checked every file link, reviewed the claims and numbers, and labelled fictional material where it appears.

Judge this portfolio for what it proves

It shows how I frame decisions and make reasoning usable. It does not pretend that a fictional scenario is a client result or that a polished prototype has survived a real implementation.

These projects are original solution-architecture demonstrations created to show my consulting approach. The organizations, requirements, data, budgets, vendors, timelines, and results shown are fictional and do not represent previous clients or employers.