Credit
The Independent 100 list was curated by dan (@irl_danB) and published on 2026-09-24 at independent.prose.md (announcement). The ranks and section names are his, and number 100 is his open wild-card slot. This study is ours and is not endorsed by him or by anyone on the list.
What they publicly do
Cofounder of Grove Research, previously at Eleos AI and OpenAI [Reported: X profile x.com/lfschiavo]. Grove describes itself as 'the agent ecology company' [Verified: groveresearch.com] and is co-hosting an AI Swarm Dynamics hackathon with AI Village on tools to discover and understand agent swarms [Verified: swarmchasing.com].
- X profile: x.com/lfschiavo
- Also: groveresearch.com
- Also: larissaschiavo.com
- Also: larissaschiavo.substack.com
Public work
- Grove Research product no license stated last activity 2026
Company site: 'The agent ecology company' (one line, no public output yet) [Verified]
- AI Swarm Dynamics Hackathon (AI Village x Grove Research) other no license stated last activity 2026-10-03
Oct 3-4 2026 hackathon for tools that discover, summarize and trace agent swarms; gives access to the AI Village transcript dataset (>170k messages, >2M computer-use turns) [Verified]
- AI Village dataset (host: AI Digest) dataset no license stated
Long-running multi-agent collaboration transcripts, offered to hackathon participants; not published by her [Verified link on hackathon page]
- Substack newsletter no license stated
Personal writing, linked from her site [Verified link; posts not read]
Licenses of GitHub repositories are from the authenticated GitHub license API on 2026-09-25, one row per repository in evidence/licenses.jsonl (“no license file” means the API found none; “license file present, not recognised by GitHub” means GitHub could not classify it). Other licenses are as the source states. Check the license file before reusing anything.
Relevance to our work
3 of 5 lenses: orchestration, agents, research-method
'Agent ecology' and swarm-observation tooling address the problem of supervising a fleet (making sense of many interacting agents), but there is no adoptable code from her or Grove yet.
Scored 0 to 5 against the study’s relevance rubric: 5 means public, openly licensed work squarely in our lanes that we could study or adopt now, and 1 means little connection to our work. The score is one reviewer’s judgement of how much this public work bears on our own work. It is not a ranking of people and says nothing about the person or the quality of their work.
What we would study next
- Follow the swarmchasing hackathon outputs and the linked 'cheating and whistleblowing in research swarms' case study (arxiv.org/html/2609.04170v1). Submissions are required to include GitHub repos; likely source of open swarm-analysis tools for multi-agent transcripts Effort: small.
- Request AI Village dataset access for multi-agent transcript analysis (huggingface.co/datasets/aidigestorg/ai-village). Real long-horizon multi-agent traces to test fleet-monitoring heuristics against Effort: medium.
Before reusing anything: No code or license to assess. AI Village dataset access is gated by request; check its terms before any reuse.
Sources
- x.com/lfschiavo
- groveresearch.com
- swarmchasing.com
- larissaschiavo.com
- x.com/lfschiavo/status/2100643710329589981
Overall confidence in this record: Medium. Sources were read on 2026-09-24 and every link was checked on 2026-09-25. The full record is line 27 of people.jsonl.
Limits
Not verified: Grove's research output, products and team beyond the two named founders; her Substack posts were not read; the arXiv case study on the hackathon page is not attributed to her.
This record comes from a first-pass survey of public material by an AI agent session on 2026-09-24, edited for publication on 2026-09-25. Nothing was installed or run for it. Roles, stars and licenses change; see the study’s limits.
Request a correction
Is something about this record wrong or out of date, or would you rather not be covered? Open a correction (a GitHub issue form with this page’s address filled in). A request to remove a record is honoured without argument; accepted corrections are recorded in the changelog with the date.