Architecture & Protocols
System design, protocol analysis, threat modeling, proofs, mechanism design, and verification-heavy technical problems.
For architecture-heavy technical work, research collaborations, writing, publication, speaking, or selective advisory conversations.
The most useful inquiries are clear about the problem, the constraints, and the desired outcome. A short, concrete description beats a polished pitch every time.
These are the kinds of conversations that tend to be the best fit.
System design, protocol analysis, threat modeling, proofs, mechanism design, and verification-heavy technical problems.
Distributed ML, deployment architecture, air-gapped or high-constraint environments, edge inference, and production workflows.
Research collaboration, technical memos, publication, long-form synthesis, and translating difficult systems questions into clear language.
Schema design, capability infrastructure, retrieval systems, curriculum architecture, and teach-forward knowledge products.
Conversations on verification, AI, money, capability, culture, institutional drift, and related systems questions.
Email is the fastest path. LinkedIn and GitHub are also here for context, prior work, and verification.