---
canonical: "https://yuanhaochen.dev/contact"
path: "/contact"
section: "Contact"
title: "Bring a concrete workflow constraint."
language: "en"
agentUse: "summary, retrieval, citation, hiring evaluation"
---

# Bring a concrete workflow constraint.

Best for concrete AI workflow problems, research questions, market bottlenecks, or trust boundaries that could become an inspectable artifact.

Email: ie.yuanhao@tum.de. Best for a concrete workflow, research question, market bottleneck, or trust boundary where a small artifact, map, or memo could make the problem inspectable.

GitHub: @89325516. Public repositories, implementation boundaries, validation paths, and current build evidence live here.

Website: yuanhaochen.dev. Canonical public map for notes, work, open questions, proof boundaries, and verified contact paths.

Location: Germany. Germany-based builder; useful context when the problem depends on European workflows, institutions, procurement habits, compliance expectations, or operator trust.

Fit gate: A useful message usually includes one concrete workflow, one trust boundary, one artifact to inspect, or one objection that could change the work.

Work style: Good collaboration should produce visible objects: a map, memo, issue, proof bar, prototype, or narrower claim.

Stay in orbit: A useful weak tie can start with one objection, one source, one field note, or one artifact worth inspecting.

First reply: The best first exchange should produce a map, proof bar, memo outline, repo issue, or next artifact target.