Q2 2026 Λ Investigative Supplement · Evidence Library
← Structural Custody in Agentic AI — the slideshow

Custody Inversion.
The primary sources.

Source supplement to Structural Custody in Agentic AI · The Grove Foundation · July 2026 · slide references point to the published slideshow

A neutral, primary-source evidence base a journalist, general counsel, or procurement officer can use to independently verify every load-bearing claim in the published supplement — and reach their own conclusions. Each card carries the argument the supplement makes, the primary text it rests on, and the capture that proves it. Every claim is dual-captured (live page and archived snapshot), every screenshot is hashed, and misses are published, never inferred.

The Grove Foundation · CC BY 4.0 · 501(c)(6) · Indianapolis · 30 cards: 17 Type-A · 5 Type-B · 8 Type-C · Adversarial QA 8/8 hold
Computer scientists, not lawyers — not legal advice

The Grove Foundation studies how AI systems capture and use data. We are technologists, not attorneys; nothing here is legal advice or creates an attorney–client relationship. What we tell you is technical — what these systems capture, and what the words say. What a court would do with those clauses is a question for your counsel. Contract language is quoted verbatim and dated so you can read the primary text yourself.

The vector — read every card through it

In the SaaS era, the contractual bucket “Usage Data” meant benign operational exhaust — uptime, latency, crash logs. In the agentic era the same category, often the same words, now carries the harness's high-value telemetry: accept/reject reward labels, edit-distance, embeddings and vectors of the codebase, metadata, outcome verification. Each card documents (1) the ownership / retention / definition clause and (2) what non-SaaS-era artifacts now populate that bucket. Fact is separated from interpretation; no scope or legal conclusion is asserted.

Confirmed: 22 Interpretation — supported: 8 Partial: 0 · Not found: 0 · Unverifiable: 0 Hashes + capture records: metadata.json
Loading evidence manifest…
{{ sec.angle }} {{ sec.count }} card(s)
{{ c.id }} {{ c.vendor }} {{ c.badge }}
{{ c.docLine }}

{{ c.deckClaim }}

Deck claim — {{ c.deckSlide }}
The supplement's argument · {{ c.deckSlideLabel }}
{{ c.deckHead }}
{{ p }}
AXIS · {{ c.axis }}
{{ q.head }}

{{ q.text }}

Underlying primary · rests on {{ c.restsOn }}

{{ c.underlyingQuote }}

{{ s.cap }}
{{ s.cap }}
The vector

{{ c.vector }}

Grove's reading — interpretation, not evidence

{{ c.interpretation }}

{{ c.practicalPoint }}

{{ n.label }} · {{ n.text }}
Our lane — computer scientists, not lawyers

{{ c.lane }}

LIVE → {{ c.sourceShort }} CO-SOURCE → {{ c.coSourceShort }} ARCHIVE → {{ c.archiveShort }} ARCHIVE → {{ c.archiveNote }} DATED {{ c.effectiveDate }} {{ c.shaCount }} ASSET(S) HASHED · metadata.json