Public research dossier
Designing the Doraemon Office Public Boundary
How the public command room can show motion, rhythm, and agent presence without exposing private work.
Publishing protocol
From private signal to public research artifact.
Raw notes, prompts, sources, and drafts stay in the private working layer.
The note turns the useful idea into a principle, method, or public sketch.
Readers get durable public context, related routes, and inspectable artifacts.
Private source text, credentials, runtime IDs, accounts, and controls stay out.
Research dossier
Research context, evidence, and next questions
Structured for public reading: enough context to understand the work, enough evidence to inspect it, and enough open questions to keep it honest.- Public role
- Frames this as a public-safe research artifact, not a private source record.
- Research lane
- CategoryDoraemon Office
- Boundary mode
- VisibilityPublic
- Published posture
- PublishedMay 16, 2026
- Curated note body
- The note below is the public-safe narrative.
- Related project
- A public project route is attached.
- Artifact links
- No public artifact links yet.
- Public boundary
- Which signals can be shown without exposing private work?
- Office route
- Which Doraemon Office route should this improve next?
- Demo fallback
- How should the page stay honest when live data is unavailable?
Note
Doraemon Office is most useful when it feels alive, but public life needs a boundary.
The public surface can show a sanitized rhythm: which MiniDora is active, what kind of event happened, whether review is waiting, and whether the relay is healthy. It should not show the private task title, prompt body, local path, account state, source text, or operational control that produced the signal.
Design stance
The command room is a window, not a console. Visitors should understand that a real system exists, but they should not receive the keys to it.
What can be public
- stable agent names and roles
- fixed public event labels
- safe timestamps and high-level status
- public schema health
- links to curated project pages
What stays private
- raw IDs, prompts, and task titles
- private owner notes and memory records
- tool details, accounts, and credentials
- repair, restart, purge, or deploy controls
The long-term product direction is not to hide the system. It is to make the public layer honest enough to be useful and restrained enough to be trusted.