Public project dossier
OpenClaw Runtime
The private runtime and monitoring substrate that supports Doraemon, MiniDoras, health checks, and owner-visible operational posture.
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 private runtime and monitoring substrate that supports Doraemon, MiniDoras, health checks, and owner-visible operational posture.
- Operating lane
- Agent Infrastructure · Prototype
- 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 are either public-safe or owner-gated.
- Related research
- No public related note yet.
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
OpenClaw Runtime is the private operating substrate beneath the Personal OS.
Public visitors do not need runtime internals. They need to know that Doraemon Office has a safe system posture, a public schema boundary, and a graceful fallback. The owner cockpit can show deeper health and review queues without turning public pages into an operations console.
Public Version
The public System route shows coarse, safe posture:
- live or demo mode
- public schema status
- event freshness at a safe abstraction level
- read-only fallback behavior
Private Version
The owner system surface can summarize service posture, review gaps, degraded sources, and boundary checks for Weiyu. It should remain diagnostic and owner-gated.
Boundary
Public pages must not show local paths, private service labels, tokens, internal hostnames, raw logs, or repair controls. System health should reassure without exposing the control plane.