Public project dossier
Doraemon Visualizer
The public-safe visual bridge that turns Doraemon and MiniDora activity into an understandable command-room view.
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 public-safe visual bridge that turns Doraemon and MiniDora activity into an understandable command-room view.
- Operating lane
- Agent Infrastructure · 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 stay on public-safe routes.
- Related research
- Related public research note attached.
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
Doraemon Visualizer makes the agent system legible.
The long-term direction is native weiyudang.com routes under Doraemon Office. The visualizer remains useful as a public bridge: it can show sanitized activity, agent presence, a command-room stage, and safe system posture without revealing private work.
What It Shows
- Doraemon and MiniDora presence.
- Public-safe event labels.
- Current office posture.
- Recent activity and handoffs at a safe summary level.
- Demo fallback when live relay data is unavailable.
What It Does Not Show
- Raw run IDs or task IDs.
- Private task titles or prompt bodies.
- Tool details, artifacts, memory records, accounts, or local paths.
- Execution controls or owner-only actions.
Product Direction
The visualizer should increasingly feel like part of Doraemon Office rather than a separate iframe-style portal. The public page should explain motion, not expose internals.