After years building products for real users across startups in travel, education, and payments, I kept running into the same problems. Business logic rewritten for every runtime. Codebases that no one could navigate. Systems that worked in isolation but broke at the seams. I stopped accepting those as facts of life and started building frameworks to fix them.

That's where UMA, C-DAD, and Traverse came from. Not from theory. From real problems that kept showing up.

Business logic gets rewritten for every runtime — browser, backend, edge, AI pipeline. Most architectures assume the environment too early. The same logic ends up duplicated four or five times across a codebase, and teams pay that cost forever.

→ Universal Microservices Architecture (UMA) — a portable, contract-driven execution model for distributed systems. Write once, run where it makes sense. → UMA-code-examples — 13 chapters of runnable Rust/WASM code. 100% business logic coverage enforced in CI. Live reference app. → Book on Amazon — the full model, the tradeoffs, and the design sequence behind it.

Most codebases aren't navigable by AI agents — not because the AI is bad, but because the code has no contracts. Tribal knowledge is locked in people's heads. There's no map. Agents guess, hallucinate, and break things. The fix isn't more prompting. It's better structure.

→ the-day-after-toolkit — a CLI (cdad) that audits codebase agent-readiness and scaffolds the contracts needed to fix it. → The Day After — the book behind the toolkit. Explores what it takes to restructure software organizations for the age of AI agents. → C-DAD white paper — Contract-Driven AI Development: verifiable contracts, automated reasoning, hybrid governance.

Traverse — a contract-driven Rust/WASM runtime for discovering, validating, and composing portable business capabilities. Pre-implementation, spec-governed, personal R&D.

youaskm3 — a WASM-native, MCP-powered personal knowledge layer. Runs entirely on GitHub Pages. No server, no database, no cost. Federation model so anyone can fork and run their own instance.

Five years of thinking about portable systems, AI-native architecture, and contract-driven development. In white papers and two active Medium publications.

Medium: Mastering Software Architecture for the AI Era (Wednesdays) · The Rise of Device-Independent Architecture (Fridays)

I talk about portable systems, contract-driven AI development, and what it actually takes to restructure software for the age of AI agents. Drawn directly from the books, white papers, and shipped tooling above.

Three topics I'm currently submitting to conferences:

• "Write Once, Run Where It Makes Sense" — the architecture of portable business logic with WASM and UMA. Architecture and platform engineering tracks.
• "Contract-Driven AI Development" — how verifiable contracts change how we build AI-assisted systems. AI engineering tracks.
• "The Day After: Restructuring Software for the Age of AI Agents" — practical patterns for making codebases navigable by AI agents. Engineering leadership tracks.

I'm a Software Architect at Autodesk by day. I moved from Italy to Canada about ten years ago and ended up in Golden, BC. Purcell Mountains, population small, snow quality excellent. I'm a certified ski instructor. When there's fresh snow, everything else waits.

Traverse and The Day After are next. youaskm3 is in progress.

enricopiovesan.com · LinkedIn · Medium · X