Weiyu DangPhysics, quantum computing, and personal AI systems.

I am building a public research studio and a private Personal OS: Doraemon as the entrance personality, MiniDoras as specialized teammates, and an owner cockpit where final judgment stays human.

  • PhysicsStart with structure, models, and reality checks.
  • AI systemsBuild tools that make thinking easier without hiding judgment.
  • Research workflowsTurn questions, evidence, and review into repeatable loops.

Personal OS map

The person, the studio, and the operating layer stay connected.

About is the human layer: where the physics background, product taste, agent systems, and public writing make sense together before you enter Doraemon Office or the private cockpit.

How I think

Rigorous when it matters. Playful when it helps.

The through-line is a taste for systems that compound: physics intuition, AI tools, research notes, product surfaces, and the private loops that keep work honest.

  • Physics-first curiosity

    I like questions that survive contact with equations, experiments, constraints, and messy real systems.

  • Taste before automation

    Agents are useful when they amplify judgment. They are dangerous when they hide it.

  • Evidence before confidence

    Research notes, trading work, and product decisions should keep assumptions inspectable.

Working rhythm

Study, build, review, then make the loop better.

The site should feel alive because the work is alive: notes become interfaces, interfaces become systems, and systems become review loops with clearer boundaries over time.

01

Study the world

Physics, markets, tools, and interfaces are treated as systems worth understanding before optimizing.

02

Build the interface

Ideas become pages, dashboards, agent workflows, and small tools that can be inspected and improved.

03

Review the loop

Doraemon and MiniDoras prepare evidence, but decisions stay reviewable and human-bounded.

What stays private

Useful in public. Careful by default.

This site can show concepts, public artifacts, sanitized Doraemon surfaces, and research summaries. It should not pretend the private operating layer is public.

  • No private tasks, prompts, credentials, accounts, raw IDs, runtime logs, or owner notes on public pages.
  • Doraemon can be public as a story and interface; owner work stays behind authentication.
  • Trading surfaces are research-only. Not an order, recommendation, or execution system.