Protocol & Mechanism Design
Threat modeling, incentive design, proofs, privacy-preserving architecture, and systems that remain coherent under strategic behavior.
I do architecture-heavy systems work where the constraints are real: adversarial environments, latency budgets, partial observability, secure deployment, or incentive misalignment. The public record spans privacy-preserving protocols, distributed ML in air-gapped settings, edge inference, and knowledge infrastructure built for actual use.
These cases show the kind of problems I am most drawn to: high consequence, real constraints, and very little room for conceptual sloppiness.
Role Protocol architect, technical leadership
Problem Designed a ciphertext-only storage network where storage is an ongoing proof, not a one-time claim.
Built and led production of a ciphertext-only storage network where storage is proved over time rather than claimed once. The core challenge was not only cryptography, but incentive design: challenge generation, anti-precompute mechanics, long-horizon reputation, and tier mobility that rewards sustained performance instead of easy gaming.
Role ML lead, architecture, edge deployment
Problem Build latency-sensitive underwater threat detection that works under operational conditions, not lab conditions.
Led hybrid DSP + ML architecture for underwater threat detection on Jetson edge hardware, optimized around operational detection metrics and latency rather than generic benchmark scores. The load-bearing innovation was not just model design, but synthetic-data and domain-adaptation workflows that made transfer from simulation to tactical deployment possible.
Role ML infrastructure architect, secure deployment
Problem Enable full-capability LLM fine-tuning and serving inside air-gapped, multi-GPU environments with strict approval requirements.
Built full distributed LLM fine-tuning capability inside air-gapped, multi-GPU environments with strict approval and handling requirements. In these contexts, software supply chain discipline matters as much as model training: every dependency, artifact, and operator workflow has to survive without the conveniences of public infrastructure.
Role ML engineer, model development, production deployment
Problem Improve RF modulation classification accuracy and deploy into streaming production.
Improved RF modulation classification and helped deploy models into streaming production environments spanning R, Python, and C++. The work combined model development with the less glamorous but decisive layers of interfaces, APIs, and operational compatibility.
Role Architect, full-stack, quant engine design
Problem Options structure construction is a combinatorially explosive problem. Traders navigate it by heuristic — choosing familiar patterns rather than systematically optimizing for cost, robustness, and simplicity.
Built a payoff-engineering platform that replaces heuristic structure selection with mixed-integer linear programming (MILP). The user describes a target payoff shape — floor, cap, horizon, symbol — and the system constructs the optimal multi-leg option structures via branch-and-bound optimization over the listed chain. Three solver passes with different objective weight profiles explore the Pareto frontier, a multi-dimensional scorer evaluates each solution across cost, simplicity, robustness, and liquidity, and a selector returns exactly three distinct candidates: cheapest, simplest, most robust.
Role Architect, platform design, full-stack
Problem Modern research is bottlenecked by fragmented evidence, combinatorial search spaces, reproducibility breakdowns, and human bandwidth limits. Existing AI tools amplify noise without enforcing provenance or verification.
Built a collective intelligence platform that coordinates specialized AI agents to perform continuous, audited scientific research. The core design bet is substrate quality over agent quantity: every artifact is content-addressed with lineage tracking, every claim lives in a structured evidence graph with counterevidence and calibrated confidence, and every computational run produces a deterministic reproduction bundle. Agents operate within explicit compute/cost/risk budgets, acquire tasks via exclusive leases with heartbeating, and must continuously outperform baselines to remain active. A separation-of-duties protocol ensures proposers cannot verify their own claims — independent critics, replicators, and arbiters enforce epistemic discipline.
Active development — see the dedicated SwarmOS page.
Role Architect, platform design, full-stack
Problem Enterprise knowledge is scattered across dozens of systems. The connections between artifacts — this PR caused that incident, which led to this RCA, which changed this decision — live only in people's heads and disappear when they leave.
Built an enterprise context graph and agentic retrieval engine that captures institutional knowledge as typed, timestamped, permissioned Context Objects linked by 35 edge types spanning causal, decisional, lifecycle, and structural relationships. Instead of top-k cosine similarity, the retrieval planner runs an iterative control loop: interpret intent, select strategy (causal chain, decision rationale, impact analysis), search with hybrid lexical + dense RRF fusion, expand through the graph via multi-hop typed edges, rerank by five-component sufficiency scoring (coverage, recency, authority, diversity, completeness), and stop when the evidence threshold is met or the budget is exhausted. A self-correcting canonical memory layer maintains truth through supersession chains, contradiction detection, and reconsolidation loops.
Active development — see the dedicated Agentic Data page.
Role Founder, architect, full-stack platform build
Problem Practical knowledge is trapped behind institutions, jargon, and credential barriers.
Designed and built a Postgres-first knowledge platform for practical public capability. The hard problem is not storing information. It is structuring it so a beginner can move from immediate need to reproducible skill, in context, without already knowing the jargon.
Active development — see the dedicated Capability Commons page.
I am best suited to problems where architecture matters more than headcount and where clarity matters more than performative velocity. That usually means protocol and threat-model analysis, ML systems architecture, knowledge-platform design, technical synthesis, and selective leadership where a team needs a sharper map of the problem before it needs more code.
If the problem is technically real, constraint-heavy, and worth thinking through properly, reach out with the problem, the constraints, and the desired outcome.