Public-safe
Agent systems and Doraemon
Discuss Personal OS ideas, MiniDora team design, public command-room interfaces, or agent workflow architecture.
Open DoraemonPublic collaboration entry
Start with a focused note.
Contact is the public front door for research questions, AI systems, creative workflows, and Personal OS collaboration. Share the context that is safe to make public; keep private operations out of the inbox.
Public-safe firstNo owner operationsSpecific context helps
Good reasons to reach out
Pick the surface that best matches the conversation.
Evidence-first
Research tools and experiments
Share a research question, interface problem, note, paper, dataset shape, or workflow that deserves a better tool.
Read researchPublic artifacts
Projects and product surfaces
Talk about a public project, prototype, dashboard, visual system, or collaboration path with clear boundaries.
Browse projectsHuman layer
Writing and creative work
Start from a note, photo, field observation, or media workflow that could become a small public artifact.
Open journalA useful first message
Give the work a shape before asking for time.
The fastest way to start is a short note that makes the question, artifact, and desired next step clear. It does not need to be polished. It does need to be safe to read in a public-contact context.
Write the note01
What are you trying to understand or build?
02
Which public project, research note, or workflow does it connect to?
03
What artifact can you share safely: link, screenshot, sketch, repo, paper, or short context?
04
What would make the first response useful: critique, collaboration, introduction, or a focused call?
Boundary
Public contact is not a command channel.
Doraemon Office and the owner cockpit have clear roles. Contact is for starting a conversation, not for sending instructions into the private operating layer.
Use public summaries. Do not send private tasks, prompts, owner notes, raw logs, or internal IDs.
Do not include credentials, account details, tokens, broker data, or private operational channels.
Trading-related conversations stay research-only: not an order, recommendation, or execution system.
What usually works
Small, specific, public-safe starts compound best.
Research exchangeA question, paper, note, or experiment that benefits from careful reasoning.
Interface collaborationA dashboard, workflow, product surface, or agent experience that needs sharper design.
Long-term Personal OSA broader conversation about Doraemon, MiniDoras, and human-bounded automation.