Personal OS

A local-first knowledge workspace that turns scattered project context into useful reviews.

Personal project

Source unavailable publicly
Folded archival folio with indexed paper layers; concept artwork for Personal OS
Concept artwork · illustrative, not a product screenshot.

Notes, project decisions and software activity accumulate in separate places. A useful workspace needs to connect them while preserving which source is authoritative.

From scattered context to useful reviews

  • An Obsidian information model with raw captures, durable wiki notes and generated output.
  • Refresh, status and review workflows across multiple project domains.
  • A project radar that groups recent repository activity into candidates for follow-up.

Separate sources from views

  • Source repositories remain authoritative; curated notes provide context and generated summaries are read-only views.
  • Refresh commands read configured sources and write to the output layer.
  • An Obsidian actions plugin exposes workspace automation controls.

Human follow-up stays explicit

  • Separate captured material from maintained knowledge and generated output.
  • Keep refreshes read-only with respect to source repositories.
  • Surface candidates for review instead of silently deploying code or changing external systems.

Context and limits

Previously called Akhil OS. The vault, personal notes and source configuration are private; this case study describes the software structure.