# Pulaski County Clerk — Quorum Court May 2026 Agenda Records (production overview)
Five PDFs emailed directly by the **Pulaski County/Circuit Clerk's office** (Keith Rancifer, Chief Administrator) on **2026-07-09**, in response to what the office treated as a standalone FOIA — the courtesy copy of NextRequest **#26-439** that had been cc'd to the Clerk. This is a **supplement to, and largely a re-production of,** the [[county-pulaski/data-center-moratorium-26-439-2026-07-07/_overview|#26-439 record set]]: three of the five files are **byte-identical** to records already ingested from #26-439, and the two new files are the Clerk-of-record's filed **agenda records** for the May 12 and May 26, 2026 meetings — the meetings surrounding the failed data-center moratorium vote (Item **26-I-37**). Its evidentiary value is **provenance and consolidation** (the custodian of record authenticating the agenda packet and the vote records), not new substance. **It does not supply the certified/approved May 26 minutes** — those remain outstanding.
## Provenance
Emailed 2026-07-09 14:53 UTC by **Keith Rancifer, MPA, Chief Administrator, Pulaski County/Circuit Clerk** (`
[email protected]`, cc `
[email protected]`), subject *"FOIA Request"* ([correspondence thread](https://mail.google.com/mail/u/0/#all/19f475ff625bcee9)). The Clerk had received the courtesy copy of NextRequest **#26-439** and treated it as a fresh records request to the Clerk's office; this email is the response, and it **closes** the request and **redirects** future requests: *"Here is the information requested, this FOIA is closed, please for future request visit the pulaskicounty.net website and click on nextrequest to submit your request."* See the delivery event [[2026-07 Pulaski County Clerk Produces May-2026 Quorum Court Agenda Records]].
The five produced PDFs are stored, unmodified, in `raw/county-pulaski/clerk-quorum-court-may-2026-2026-07-09/`. A sixth attachment, `image001.jpg`, is the sender's email-signature graphic (a "picture containing text" logo) and was **not** ingested. FOIA correspondence lives in Gmail (thread above), not in `raw/`.
**Duplication and re-production (by SHA-256).** A checksum pass (`_phase0_workdir/inventory.py`) confirms the split:
| File (name preserved) | SHA-256 (first 8) | Status |
|---|---|---|
| `Committee Reports.pdf` | `E24A54C6` | **byte-identical** to `#26-439` → variant; cited to [[Quorum Court Committee Reports on the Data-Center Measures]] |
| `Roll Call.pdf` | `7DA2A7C7` | **byte-identical** to `#26-439` → variant; cited to [[Quorum Court Roll Call and Vote Sheets on the Moratorium (2026-05-26)]] |
| `Vote Sheets.pdf` | `6D53F6DE` | **byte-identical** to `#26-439` → variant; cited to [[Quorum Court Roll Call and Vote Sheets on the Moratorium (2026-05-26)]] |
| `5.12.26 Agenda Meeting.pdf` | `CFD7754F` | **new file** (unique across #26-341 and #26-439) — May 12 Agenda Committee agenda |
| `5.26.26 5th Reg Meeting.pdf` | `8DB27470` | **new file** (unique) — May 26 5th Regular Meeting agenda + as-introduced item texts |
The three byte-identical files were **not re-extracted** and get **no new page** (per the #26-439 re-production convention); the two new files were extracted with `dump_pdf.py` (embedded scan-OCR text layer). See `extracted/.../README_variants.md`.
## What's inside
Organized into a single new source page plus three variant cross-references:
- [[Quorum Court Agenda Records — May 12 and May 26 2026 (Clerk's Filed Packet)]] — the two **new** files: the May 12 Agenda Committee agenda (`5.12.26 Agenda Meeting.pdf`, 3 pp.) and the Clerk-filed May 26 5th Regular Meeting agenda + full **as-introduced** text of all agendaed items (`5.26.26 5th Reg Meeting.pdf`, 52 pp.), including 26-I-32/33 (HIDI-regulation resolutions), 26-I-34 (HIDI/CUP ordinance + Appendix A fee schedule), and **26-I-37** (the moratorium emergency ordinance) with **Stowers' Amendment 1** grandfather clause.
- **Byte-identical re-productions** (cited to their existing #26-439 pages, no new page): `Committee Reports.pdf` → [[Quorum Court Committee Reports on the Data-Center Measures]]; `Roll Call.pdf` and `Vote Sheets.pdf` → [[Quorum Court Roll Call and Vote Sheets on the Moratorium (2026-05-26)]] (the handwritten roll call and per-item tally sheets that embody the **9–4–2** moratorium vote).
## Central findings
- **No certified minutes.** This production does **not** contain the certified/approved minutes of the May 26 meeting. A full-text sweep of the 52-page packet returns **zero** hits for a minutes-of-proceedings document (`minutes of`, `the following vote`, `ayes`/`nays`/`abstain`); [[Luke McCoy]] appears only as the agenda's invocation-giver (p. 3), never as a recorded vote; every signature/ATTEST block is **blank** (the item texts are the *as-introduced* versions, not the executed/certified record). The certified May 26 minutes — which under normal practice are approved at a later meeting — **remain outstanding** (a follow-up FOIA target). This is an "absence is information" finding, not a gap filled by inference.
- **The vote record was already in the corpus.** The 9–4–2 corrected tally and the [[Luke McCoy]] AYE→Present correction live in `Vote Sheets.pdf`/`Roll Call.pdf` — here **byte-identical** to the copies ingested under #26-439, which already anchor [[T004 - Did the Pulaski County Data-Center Moratorium Pass]]. This production **corroborates** that record from the custodian of record; it does not change it and is **not** re-adjudicated here.
- **Predominantly a re-compilation, valued for provenance.** The May 12 and May 26 agendas and the as-introduced item texts are, in substance, already held in the corpus — the May 26 agenda + item texts via the #26-341 [[May 2026 Quorum Court Agenda Packet]] (the 27-page "May FQC packet"), the May 12 agenda embedded in #26-439's bulk scan `0283_001.pdf`, and the data-center ordinances/resolutions as separate drafts under [[Draft Data-Center Moratorium Ordinances (26-I-37 45 45A 52 Temporary)]] and [[Draft Data-Center Regulatory Framework — HIDIU, CUP, and Related Resolutions]]. The new files' contribution is the **fuller, single-document Clerk-filed packet** (52 pp. vs. 27), carrying every item's QCS file stamp, delivered by the Clerk of record.
- **The AVAIO/"Project Leo carve-out" is the grandfather clause, not a by-name exemption.** The packet contains no by-name AVAIO or Project Leo reference; the functional carve-out is **Stowers' Amendment 1** to 26-I-37 and **Article 17** of the 26-I-34 HIDI ordinance, exempting projects with executed binding utility-interconnection agreements, final County approvals, or complete interconnection applications with preliminary utility-study acceptance before the effective date — criteria that, as applied, reach the already-approved [[AVAIO Digital Partners|AVAIO Project Leo]] site. See [[Data Center Moratorium Ordinance 26-I-37A and the Grandfather Amendment]].
## People and orgs
- [[Luke McCoy]] — the miscounted "Present" vote (in the byte-identical vote record); named on the May 26 agenda as invocation-giver.
- Moratorium sponsors [[Rebekah L. Davis]], [[Tina Ward]], [[Julie Blackwood]]; grandfather-amendment sponsor [[Phil Stowers]]; Agenda Committee chair [[Curtis A. Keith]] (the byte-identical committee reports).
- [[Barry Hyde]] (County Judge; signature blocks throughout the item texts), [[Terri Hollingsworth]] (Circuit/County Clerk; office of record).
- [[Pulaski County Government]], [[Pulaski County Quorum Court]], [[AVAIO Digital Partners]].
## Concepts
- [[High-Intensity Digital Infrastructure Use (HIDIU)]] and [[Conditional Use Permit (CUP)]] — the as-introduced 26-I-34 ordinance classifies HIDIUs as heavy-industrial uses permitted only via CUP.
- [[Arkansas Data Centers Act of 2023 (Act 851) and 2024 Amendments]] and [[Pulaski County Zoning and Land-Use Authority]] — the 26-I-32 resolution's asserted authority basis (Ark. Code §§ 14-14-801/802, 14-1-407).
- [[Arkansas Quorum Court Ordinance Procedure]] — the two-thirds (10-of-15) emergency threshold the moratorium fell short of.
## Events
- [[2026-07 Pulaski County Clerk Produces May-2026 Quorum Court Agenda Records]] — this production's delivery event.
- [[2026-05 Pulaski County Quorum Court Vote on Data Center Moratorium]] — the meeting these agenda records serve.
- [[2026-07 Pulaski County Quorum Court Scheduled Re-Vote on the Refiled Moratorium]] — the July 14 re-vote for which this agenda material is antecedent.
## Cross-references
- [[county-pulaski/data-center-moratorium-26-439-2026-07-07/_overview|#26-439 production]] — the set this re-produces in part (three byte-identical files).
- [[county-pulaski/data-center-moratorium-2026-05-29/_overview|#26-341 Clerk production]] — the earlier Clerk production and its [[May 2026 Quorum Court Agenda Packet]] (a distinct, earlier agenda packet for the same May 26 meeting).
- [[T004 - Did the Pulaski County Data-Center Moratorium Pass]] — corroborated (not changed) by the byte-identical vote record.
## Open questions / follow-ups
- **Certified May 26 minutes remain outstanding — follow-up filed.** This production supplies agenda records, not the approved minutes-of-proceedings. A targeted NextRequest for the certified minutes of the 2026-05-26 5th Regular Meeting was filed 2026-07-09 as **#26-445** (per the Clerk's redirect) — see [[2026-07 Pulaski County FOIA for the Certified May-26 Quorum Court Minutes (26-445)]]; response pending.
- **26-I-38** (a [[Donna Massey]] resolution in the packet, pp. 49–52) and **26-I-17** (a meeting-times ordinance) are non-data-center items not previously characterized; routed for the sibling `ar-pulaski-county` investigation, not developed here.