Research cutoff: 9 September 2026. This lane did not acquire an actual Briver attestation, supporting domain evidence, paragraph 16 disclosure response, satisfaction of judgment, or Briver compliance/enforcement filing. It established the public court route and encountered its explicit human-verification boundary before any case-number search. The result is an access and publication gap, not evidence that Briver failed to comply or that the records do not exist.
The previously read judgment directs paragraph 16 information to the People, and paragraphs 17–18 attestations and supporting evidence to the People through the notice procedure in paragraph 47. It does not in those clauses require every response to be publicly filed with the court. Thus even a complete docket search would not necessarily disclose all compliance material. The City Attorney and Briver/counsel are the apparent primary holders of those responses; the court holds whatever was actually filed. This custody distinction comes from the accepted judgment analysis, PDF pages 4–5 and 10 of the retained instrument, not a newly obtained response.
| Public route | Exact scope and outcome |
|---|---|
| First indexed discovery batch | Queries: "CGC-24-617237" "compliance"; "Briver" "attestation" "2025"; site.sf.courts.ca.gov case information civil online case query. The combined results exposed the official court access page, the already acquired judgment and a June 13, 2025 Tilak declaration. No actual Briver response was identified. |
| Official court access page | [Case Information](http[local research file] The web reader returned 403 Forbidden; one ordinary GET substitute succeeded. The complete main Case Calendar & Query content and actual Civil Case Query href were read. This page advertises civil case lookup; it is not the case’s docket. |
| Actual Civil Case Query link | http[local research file]. An ordinary GET returned the court’s gateway, which explicitly verifies a person rather than an automated program. No verification response, CAPTCHA solution or underlying CaseInfo.dll request was submitted. No case-number search or register-of-actions inspection occurred. |
| Second indexed discovery batch | Queries: site:sf.gov "Briver" "attestation"; site:sfcityattorney.org "Briver" "satisfaction"; "CGC-24-617237" "Briver" "compliance". The combined returned material included the prior judgment and secondary explanatory articles, not a newly acquired Briver response, satisfaction or enforcement record. Secondary summaries were not accepted as implementation evidence. |
| Already retained Tilak declaration | Root acquired the [June 13 declaration republished by Ars Technica](http[local research file] This lane performed only a targeted search of root’s local page-text derivatives for Briver, attestation, satisfaction, compliance and comply. The caption names Briver; the “Statement of Compliance” on PDF 47 concerns Companies Act 2006 registration. It is not a Briver judgment attestation. This limited search is not a full visual audit, and sparse/image-only extraction cannot prove absence from the PDF. Root owns substantive provider/disclosure review; it must remain separate from Briver compliance. |
The exact gateway statement and successful original-response metadata are retained in filings-captures.json and filings-case-query-gateway.html/.txt. Its anti-automation condition is a site access boundary, not an automatic sandbox approval rejection. No attempt was made to work around it. Closed LegInfo routes were not revisited. The six queries are preserved in filings-query-log.json, a derived search log rather than a complete search-index snapshot.
filings-court-information.html: official court page, HTTP 200, 638,340 bytes, SHA-256 bfe73a633bbe71ef78bc26bfd736eee6183d26d5cede085e78980ec1da5fc3f7. Reading scope is the public main query content and link; navigation scripts are captured, not interpreted as case records.
filings-case-query-gateway.html: actual linked court gateway, HTTP 200, 2,167 bytes, SHA-256 c1cb249fe448f2cd3687036b8bd0a48271f71cd853f0169161ebfefbe4e3adb0. Complete visible text and form action were inspected. The case record remained inaccessible behind that boundary.
Root’s separately retained tilak-declaration-june13-2025.pdf: SHA-256 bbd7cfa2059c35fd203ce7202b1bb6072d7bbfe6412ea061ffdf7aa58d2183a5. No duplicate download occurred. Its primary-instrument content and republisher custody are described in root’s packet; this lane claims only the limited text-search scope above.
The strongest current conclusion is that the judgment created recurrent reporting and discovery rights, but this public pass did not verify their exercise or fulfillment. The missing discriminator remains the actual attestation with domain evidence, paragraph 16 response, payment/satisfaction record, or a court filing enforcing or recording those obligations. A legitimately supplied case file or a newly public city/court publication could reopen that question. No account, fee, contact, records submission, CAPTCHA solution, target-site visit or further research branch was undertaken.