Team overview
Research should ship artifacts people can inspect.
We work on source-backed datasets, scorecards, registries, evaluation artifacts, and small tools tied to public-interest questions.
data Public data Messy government and civic sources become reusable, versioned, and inspectable datasets.
corpora Legal and civic corpora Fragmented public material becomes structured source trails, corpus cards, and research inputs.
evals Model evaluations Evaluation work should separate correctness, abstention, hallucination, and evidence quality.
Operating model
From source material to reusable artifacts.
Question, sources, artifact, review, documentation, release.
- Question
A public-interest question tied to a real source, corpus, or model behavior.
- Sources
A source trail with URLs, dates, limitations, and evidence quality notes.
- Artifact
A dataset, eval, registry, scorecard, CLI, or accountability tool.
- Review
Check reproducibility, source quality, and limitations before claims harden.
- Documentation
Shareable notes that do not require private vault access to understand the work.
- Next gate
Promote, hold, or reshape the project based on evidence rather than excitement.
Work surfaces
The lab is organized around four artifact types.
Projects can move at different speeds, but the output should stay inspectable and reusable.
Public data Datasets and manifests
Public sources made easier to cite, refresh, verify, and reuse.
Source trails, hashes, refresh logs Legal and civic corpora Structured source material
Fragmented law, records, and civic text turned into reusable research inputs.
Corpus cards, coverage notes Model evaluations Evals and scorecards
Evaluation artifacts that make model behavior and evidence quality easier to inspect.
Rubrics, runs, agreement checks Accountability tools Registries and small interfaces
Focused tools that help people inspect public systems without hiding the source trail.
Registries, CLIs, dashboards