Public project dossier
Knowledge Vault
A private memory and synthesis layer that turns source material into owner-reviewed, public-safe outputs.
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
- A private memory and synthesis layer that turns source material into owner-reviewed, public-safe outputs.
- Operating lane
- Research Tools · 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
Knowledge Vault is the memory and synthesis layer for the Personal OS.
Its job is to help preserve context, organize source material, and prepare public-safe summaries without treating private notes as public content. The public website can show the shape of the system and curated outputs; private source pages remain behind the owner boundary.
Public Version
The public Knowledge route explains the workflow:
- capture source material privately
- synthesize it into a candidate output
- keep owner review visible
- publish only curated, public-safe pages
Private Version
The private cockpit can organize sources, synthesis candidates, evidence rows, rewrite steps, and publish gates. It remains authenticated and read-only until a separate audited write path exists.
Boundary
Raw private vault pages, memory records, unpublished drafts, private source files, and owner notes do not become public page data. Public outputs must be curated and reviewed.