../missions / neural-nexus-vault

Neural Nexus Vault (Obsidian + WSL)

[Systems] featured active

PKM + infra practice — show how I structure work and level up the toolchain

    ╔═════════════════ // case_study ══════════════════╗

problem: PKM + infra practice — show how I structure work and level up the toolchain
my_role: Designed the operating system, dashboard, workflow, or infrastructure layer behind the project.
system_built: A living second brain in Obsidian — numbered project zones, Mission Control dashboards, a changelog database, and templates that turn notes into an operating system. Paired with WSL2 for a Linux-native dev loop on Windows: smoother tooling, fewer path surprises, and a single environment for shipping this portfolio and adjacent repos.
proof: Vault zones: 8+ · Dev environment: WSL2 · Ops layer: Changelog DB
why_it_matters: A second brain only works when it's easier than memory — templates and queries lower the cost of staying honest.

    ╚══════════════════════════════════════════════════╝

  ────────────────────────────────────────────────────────

    ┌──────────────────── // proof ────────────────────┐

Vault zones: 8+
Dev environment: WSL2
Ops layer: Changelog DB

live_url live_portfolio

    └──────────────────────────────────────────────────┘

  ────────────────────────────────────────────────────────

    ┌─────────────── // operating_notes ───────────────┐

Neural Nexus is my Obsidian vault for execution: daily and weekly rhythms, active projects under 03_Projects, a knowledge base, and AI-facing context so agents stay aligned. Recent work includes a **changelog database** (atomic entries + Dataview + per-project registry), **Project Hub** templates, and scaffolding so every mission has a hub note and filtered history. It's where I practice *systems thinking as software* — structured frontmatter, wikilinks, and queries instead of ad-hoc docs.

On the **WSL** side, the breakthrough is treating Windows as the shell and Linux as the engine: Node, npm, git, and builds run in a consistent Linux toolchain while files sync cleanly across drives. That cut friction for this portfolio (Vite + Vercel), multi-repo layouts, and terminal-first workflows — closer to what production Linux CI expects.

Together, Obsidian + WSL is a visible **SWE progression** story: not just shipping features, but tightening the loop between planning, execution, and shipping — the same habits I bring to product teams.

    └──────────────────────────────────────────────────┘

  ────────────────────────────────────────────────────────

    ┌─────────────────── // debrief ───────────────────┐

A second brain only works when it's easier than memory — templates and queries lower the cost of staying honest.
WSL isn't just convenience; it's alignment with how servers and CI run your code.
Showing the vault + toolchain on the portfolio proves I can document and ship in the same breath.

    └──────────────────────────────────────────────────┘

← back to missions