AHMAD:// Available for work — open to remote roles and contracts

Work — case studies with evidence ledgers

ranked · not exhaustive

A hackathon prototype whose marketing outran its cryptography (a ZK layer that was simulated) — the lesson got promoted into policy instead of a page. Read it as the reason every row above links to source. [verified in the July audit; fixed in the habit]

Problem > constraints > decisions > measured results > limitations. No tech-stack tourism; if a library earned a slot, it earned a reason.

Most numbers here survive a stranger an afternoon with git: run the tests, load the checkpoint, replay the benchmark. That's the bar the copy writes to.

ahmad@xr:~% ask — grounded in this site · no LLM, no invented answers

try: