Vipin Wiki Bootstrap

Summary

This note records the initial decisions used to instantiate the LLM Wiki pattern in this repository.

Chosen Structure

• raw/ for immutable source material
• wiki/ for maintained knowledge pages
• AGENTS.md as the operating schema

Within wiki/, the first stable sections are:

• entities/
• concepts/
• sources/
• analyses/
• queries/

Why This Shape

• It is simple enough to operate manually at small scale.
• It works well with Obsidian.
• It supports incremental growth without needing search infrastructure on day one.
• It makes ingest, query, and maintenance legible to future agent sessions.

Initial Assumptions

• The wiki will likely mix personal notes, research material, and project knowledge.
• High-value outputs from future conversations should be saved back into the wiki.
• The structure should remain lightweight until usage patterns become clearer.

Counterpoints and Gaps

• the original bootstrap favored simplicity over scale, so it did not yet solve cataloged search, layered context, or source-type-aware ingest
• a lightweight structure can become underspecified once the wiki spans multiple domains and hundreds of pages
• bootstrapping a serious system requires later hardening, not just continued note accumulation

Next Recommended Steps

1. Ingest one real source into raw/inbox/.
2. Ask the agent to process it and update the wiki.
3. Start defining Vipin’s major domains, such as:
   • projects
   • health
   • learning
   • relationships
   • long-term goals
4. After 5 to 10 ingests, review whether more page types or metadata are needed.

Related

• home
• index
• log
• vipin
• llm-wiki
• 2026-04-21-llm-wiki-pattern