Technical portfolio
I build systems where work becomes state.
Not screens. The path underneath them, and the contract it keeps.
01 · The contract
Every signal owes you
four answers.
-
Where did this come from?
A form, a call, a message, an event. If the source is unknown, nothing downstream can be trusted.
-
What is allowed to happen next?
Validation before action. The set of legal moves is decided before anything runs.
-
Who decides the parts a machine should not?
Approval, sensitive judgement, irreversible actions. Named, not implied.
-
What does finished mean?
An owner, a next action, a written outcome. Not "the workflow ran".
02 · Refusals
Trust is built from
what it won't do.
-
It will not invent a fact
No price, no promise, no availability it cannot verify.
-
It will not act past its permission
Consent decides the channel. Scope decides the action.
-
It will not fail silently
Retry, queue, alert, log. A dropped job is a bug, not an edge case.
-
It will not hide its status
Implemented, prototype, product, demonstration. Stated at the point of use.
The stack
Tools are chosen for the path.
A system you cannot inspect is a story someone told you.