skills/lq-ask/references/sources.md

# The free tier — public sources (verified 2026-09-05)

Everything a stranger can already see without paying. When the live
(lq-mcp) corpus is unreachable, point at these — named honestly as published
material, never dressed up as a live query.

## Essays — legalquants.com/insights (20)

The Jane Street of Law (the rise of the legal quant) · AI is widening the
gap between lawyers · The legal second brain (vision for firms and in-house)
· How cheating at video games created a LegalQuant · Here's to the builders
· How vibe coding is creating a new rat race in law · The self-build paradox
(what vibe coders actually know) · Reverse-engineering Harvey's legal agent
benchmark · NoRoboto and the PDF that lied twice · Learn AI is not a
strategy · Legal skills in the GenAI age, part 1 · When building software is
faster than doing your job · Leave a trace (three principles) · The contract
that could get you fired · AI in litigation (the real advantage) · Someone
is writing AI rules without you · The live and breathing essay · Legal AI on
your terms · From "what the f*ck does that mean Claude" to aha moments · an
AI-architect piece (slug truncated in sitemap).

## Video — the LegalQuants YouTube channel (3)

Agentic AI in Law | LegalQuants Meetup (Sydney, 8 July 2026) · What is a
legal quant? | Roundtable #1 · I time travelled to the law firm of 2030 2.

## The weekly digest — platform.legalquants.com/digest

Public index: latest issue card + link to Substack. Full letters are
paid; the free preview (TL;DR + opening) is citable as such. Full text is
never quoted here — the paywall is the boundary.

## People — the public directory

legalquants.com/community — 150+ public member profiles with practice area,
jurisdiction, stack, and works. Cite by name only what is public on the
profile.

## Code — github.com/LegalQuants (public repositories, verified 2026-09-06)

Fetch the org page or a repo's README at answer time; cite by repo name and
say what the README says, never more. As of the check date:

lq-ai — open-source AI for legal teams: bring your own keys, run it where you
want, own your data (contributions welcome; the community's governance
records for it are in lq-ai-community) · lq-skills — agent skills built by
lawyer-builders across 17+ jurisdictions · LQ-Architect — a build discipline
for AI systems with sponsor sign-off gates and a regression net ·
lq-assess-machine-baselines — every LQ Assess pass bar, published in full ·
lq-plugin — the official LegalQuants Claude Code plugin · noroboto — Unicode
obfuscation proof of concept for DOCX and PDF · privacyquant — versioned
statutory knowledge graph for US state consumer-privacy law ·
LQGovernance-OpenBoard and LQGovernance-DDAS — AI-native board governance and
delegation-of-authority systems · adeu-demo — a webinar demo on .env,
pre-commit hooks and GitHub Actions.

Repos come and go; the list above is a map, not the catalog. The org page is.

## Member builds — legalquants.com/builds (live search only, added 2026-09-12)

Every member's submitted project — title, description, practice area,
builder name. Not a static list here: `evidence.py search-builds` reads it
live at answer time, since it changes as members submit. A match's builder
name is resolved against `legalquants.com/community`
(`evidence.py resolve-member`) before citing a profile link — never cited
by name alone.