Public project dossier
Weiyu Personal OS
The integrated website, Doraemon Office, owner cockpit, and research surfaces that make Weiyu's work visible without collapsing public and private boundaries.
System connection
How this project connects back to the Personal OS.
Curated pages explain the visible project shape.
Doraemon Office makes status, agents, and rhythm legible.
Owner work, source material, prompts, and controls stay gated.
Public dossier
Context, evidence, and next questions
Project pages should explain the public story, name the evidence a visitor can inspect, and keep the next unknowns visible without exposing private work.
Project context
Where this artifact sits inside the Personal OS.
- Public role
- The integrated website, Doraemon Office, owner cockpit, and research surfaces that make Weiyu's work visible without collapsing public and private boundaries.
- Operating lane
- Personal AI Systems · Active
- Boundary mode
- Public concept, private implementation details.
Evidence
What a visitor can inspect without crossing the private boundary.
- Curated project body
- Markdown body explains only public-safe context.
- Reviewed routes
- Links are either public-safe or owner-gated.
- Related research
- No public related note yet.
Next questions
Open questions keep the project from becoming a static portfolio card.
- Public summary
- What can be safely summarized for the public site?
- Owner route
- Which routes must stay owner-only?
- Research note
- What evidence can become a public research note?
Overview
Weiyu Personal OS is the product shape behind this website.
It is not just a portfolio. It is a public studio, a Doraemon command room, a private owner cockpit, and a set of research surfaces that share one language: public things should be understandable, private things should stay bounded, and important work should leave evidence.
Surfaces
- The public site explains projects, notes, and the operating philosophy.
- Doraemon Office shows sanitized agent activity, team presence, schedules, tasks, knowledge, and system posture.
- The owner cockpit keeps priorities, approvals, private knowledge work, schedules, and system health behind authentication.
- Research surfaces such as MiniDora Trading stay evidence-first and execution-free.
Boundary
The public side can show concepts, public-safe state, and curated outputs. It does not expose private prompts, raw task names, private memory, credentials, account data, orders, local paths, or execution controls.
Current Shape
The v1 system is being built slice by slice. Each slice should improve the real product surface, preserve the public/private contract, and leave enough verification evidence that the next agent can continue safely.