Skip to content

START HERE

You're looking at the compiled knowledge base for Sam Aguiar Injury Lawyers, hundreds of Notion entries from the SAIL Knowledge Base database, compiled into a navigable wiki that an LLM can read and answer questions against. The wiki refreshes daily from Notion, so exact counts live in _stats.json.

This is the Karpathy-style "LLM Knowledge Base" pattern: https://gist.github.com/karpathy/442a6bf555914893e9891c11519de94f

The two halves

Half Lives in Who writes it
Raw raw/notion/ The Notion ingest (scripts/notion_ingest.py)
Wiki wiki/ Structural: scripts/wiki_compile.py. Synthetic: LLM passes.

You read the wiki. The wiki links back to the raw entries when you need primary sources.

Where to start

Browse by project

Exact entry counts per project: see index.md.

Browse by concept (the synthesized articles)

The real value is in concepts/, synthesized articles that each pull together multiple sessions on a recurring theme. If you want to understand what's going on with something, start there:

Full index: concepts/README.md

Browse by time

Timeline — all entries in reverse chronological order, grouped by month.

Browse by type

Routines

The firm runs on 12 structured routines, each available as a Claude Code slash command. See routines/README.md for the full calendar and specifications.

Questions an LLM can answer against this wiki

Once the wiki is loaded, a Claude session can answer questions like:

  • "What's the status of the RingCentral SMS sync?" → reads concepts/ringcentral-litify-sms-sync.md first, drops to raw entries if more detail is needed
  • "How many CallRail DNI incidents have we had and what causes them?" → reads concepts/callrail-dni.md
  • "Which approaches to fixing schema have worked and which haven't?" → reads concepts/schema-fix-system.md
  • "What are all the active projects across Litify?" → reads projects/litify.md, then expands into each relevant concept
  • "When was the March 2026 Core Update response, what did we change, and what's still open?" → reads concepts/march-core-update-response.md and follows its links
  • "What's in my 'Needs Follow-up' pile right now?" → walks timeline.md filtering on status (or reads wiki/_stats.json)

Keeping the wiki fresh

Two GitHub Actions workflows handle this automatically:

  • Daily (wiki-refresh.yml): pulls Notion, recompiles structural wiki, commits. No LLM needed.
  • Weekly (wiki-enhance.yml): runs Claude Code to write new concept articles, opens a PR for review.

Manual refresh:

export NOTION_TOKEN="$(grep '^NOTION_TOKEN=' .credentials/vault.env | cut -d= -f2)"
python3 scripts/notion_ingest.py         # pulls new + updated pages
python3 scripts/wiki_compile.py           # rebuilds index/timeline/categories
python3 scripts/wiki_lint.py              # reports health

Viewing this

  • Web: sail-wiki.onrender.com — searchable, navigable, dark/light mode
  • Obsidian: open the repo as a vault for graph view, backlinks, and fuzzy search
  • GitHub: browse directly at github.com/samaguiar1982-cpu/projects/tree/main/wiki