Numbers from a real vault. Not projections — a snapshot of what actually accumulated when the system ran.

The Timeline

  • January 6, 2026 — PARA structure applied to Obsidian. The KB went from a pile of unsorted notes to a navigable system overnight.
  • March 9, 2026 — NanoClaw connected. Capture became automated. WhatsApp in, structured vault out.
  • March 28, 2026 — This post.

Three months of structured knowledge base. Nineteen days of fully automated routing.

The Numbers

24 architectural decisions captured across 7 active projects — three work projects alongside Kleos, Nyx, seevali.dev, and seevali.me (the newest addition — the personal, human side of publishing, still taking shape). Every significant technical choice has a context, a tradeoff, and a recorded outcome. Not just what was decided — why.

35 clippings saved. Articles, research threads, technical deep dives — anything worth revisiting has a home. Not bookmarks. Structured notes with frontmatter and content.

21 resource notes across domains — .NET & C#, AI & ML, Architecture Patterns. Reference material that used to live in browser tabs.

12 progress notes — daily records of what moved on which project.

12 issues tracked. Problems encountered, investigated, resolved — or flagged as still open.

10 blog drafts in 09_Showcase/ — 5 of which were written this afternoon.

What the Numbers Don’t Show

Two journal entries.

That number is low — not because nothing was captured, but because the WhatsApp routing was the last piece to stabilise. The journal is where informal capture lives: quick observations, end-of-day reflections, moments worth logging that don’t belong in a project folder. That pipeline is working now. The journal will fill.

The achievements folder: empty. That’s the most honest signal in the vault. A year of significant work — architecture decisions made, systems shipped, patterns that solved real problems — and none of it formally recorded as achievements. They exist in decision notes and project folders. But a structured achievement record that could feed a performance review, a LinkedIn post, or a career narrative? Not yet built.

That gap is next.

The Velocity Observation

Seven posts in one afternoon.

That’s what the output side of a loaded vault looks like. Not writing from scratch — reading the journal, the decision notes, the incident logs, the timeline — and shaping what was already there. The knowledge existed before today. Today it got expressed.

Before this system: those seven posts might have taken seven weeks, or never happened at all. The bottleneck was never the knowledge. It was the distance between the knowledge and a published form.

The Property Nobody Mentions

Because the vault is plain files, it’s AI-platform agnostic. The knowledge doesn’t live in Claude’s memory or any chatbot’s conversation history — it lives in files I control. Whatever AI works with me next year has the same full context as today. The last post in this series covers what that actually means.

What Three Months Proves

The structure works. The routing works. The output works.

The next question is what it looks like after a year.

Signal 6 of 7 in The Second Brain That Publishes Itself.