Public research studio
Research that can be inspected.
A public notebook for system sketches, design decisions, build logs, and research fragments around the Personal OS. It shows the method and the evidence without exposing the private operating layer.
3public notes7research lanes0execution controls
Public by designShare what's safe. Protect what's not.
Evidence firstShow the why, the how, and the limits.
Linked to workEvery note connects to projects and artifacts.
Selected note
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 artifact.
1Capture privatelyRaw notes, prompts, and source material stay inside the private vault.
2Distill safelyTurn the useful idea into a principle, method, or public sketch.
3Attach evidenceLink only public artifacts, screenshots, project pages, or durable summaries.
4Publish with boundaryKeep the note useful without exposing accounts, paths, raw logs, or controls.
Public ResearchPublic
Curated summaries
Design sketches
Concepts and methods
Project links
Private VaultPrivate
Raw notes and drafts
Prompts and credentials
Internal runtime and logs
Account and system state
We publish what is safe, useful, and durable. Raw prompts, private source notes, credentials, accounts, runtime identifiers, and execution controls stay private by default.
This is a living research shelf.
New notes land when experiments evolve. The point is not volume; it is a durable trail of decisions, evidence, and useful boundaries.