Public research dossier
Building a Personal AI Research Studio
A first public note on turning personal AI workflows into a small operating system.
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
- CategoryAgent Systems
- Boundary mode
- VisibilityPublic
- Published posture
- PublishedMay 9, 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.
- Agent role
- Which MiniDora responsibility becomes clearer from this note?
- Review gate
- Where should owner judgment remain explicit?
- Public artifact
- What durable artifact can prove the next step?
Note
The first version of this website is a personal public shell for a larger private system.
The important design choice is boundary clarity: public pages explain the system, while private routes hold command, events, review queues, and operational dashboards.
What this studio is for
The public studio is a place to make the work understandable without making the private operating layer public. It can show projects, principles, architecture sketches, and safe lessons from building Doraemon Office.
System shape
Doraemon is the public entrance personality. MiniDoras are specialized teammates for research, writing, data, product, memory, media, operations, and market research. The owner cockpit is the private place where approvals, sensitive context, and final judgment stay with Weiyu.
Publishing boundary
A public note should explain the durable idea, the design decision, and the evidence that can be shared. It should not include raw prompts, private drafts, local paths, account data, runtime IDs, credentials, order details, or private knowledge-base source text.
That boundary is not a temporary launch constraint. It is part of the product: public enough to build trust, private enough to keep the system honest.