This investigation examines the public cost, authorization, procurement, safeguards, and operating commitments behind Newport News' AI factory. The test is whether the city can connect its announced infrastructure to documented decisions, enforceable orders, a defensible business case, and measurable public benefits. Total equipment spending and lifecycle cost have not been established.
The project is described publicly as local AI infrastructure. The CIO's October interview outlines a December operating target, regional educational access, and proposed sustainability measures. The detailed attributed account appears in the timeline. Procurement evidence is still needed to identify what the city actually ordered.
AI Governance was listed for the June 16 committee meeting, whose posted minutes record “No discussion.” It appears on August 18's agenda again. No August outcome was located in either the linked committee page or its public minutes folder. This remains a records gap, not proof staff did no reviews. Bethany chaired the June meeting; Long and Janjua were listed present. The founding resolution makes committees advisory and unable to bind the city or Council. It requires committee-report copies to be maintained by the City Clerk, providing a specific additional records route.
The reseller trail has two stages. The city list identifies ePlus arrangement 20-3019-00. The UVA master agreement UVA-AGR-IT-00178-ePlus closely matches the title and start date. A city-specific record must connect them before master terms can be applied to a factory order. The cooperative agreement's participation-reporting provisions create a second records route through UVA. The linked financial extracts narrow the city transaction inquiry without establishing which order acquired factory hardware. An absence of a separate city solicitation, by itself, establishes no procurement violation.
The staffing allocation is now documented in the adopted FY2027 budget: $96,703 to add one AI Developer. The approved line-item book corroborates one position and that amount in fund 1000, department 13, division 1310, object 517999. This establishes an allocation, without proving hiring, actual compensation, exclusive assignment to the factory, or hardware cost.
The $6 million cybersecurity figure now has primary financial support. Council enacted Resolution 13963-26 on March 24, 2026, appropriating General Fund Assigned Balance to the IT Investment Fund for cybersecurity and ransomware defensive software. Its expenditure account is fund 4001, object 570284, project E1903. Clause 2 directs remaining balances to be carried forward and made available for appropriation in the next fiscal year. April 28 Ordinance 8157-26 reflects that same appropriation. Neither instrument establishes a factory purchase or payment. The separate FY2026-2030 CIP estimates $700,000 for relocating the City Hall data center. No factory connection has been shown.
The newer FY2027-2031 adopted CIP identifies $1.5 million for FY2027's IT Investment Fund, $850,000 for network modernization, $600,000 for backup modernization and $750,000 for public-safety server infrastructure. These published project scopes identify accounts and decisions to reconcile. They are planning amounts, with no demonstrated factory charge. Neither a generic budget heading nor the lack of a factory-named line resolves spending authority; match each commitment to its appropriation, approved purpose and any transfer or carryforward.
City-specific purchasing controls now sharpen the inquiry. The posted code assigns Purchasing cooperative and award authority and requires department-head-authorized requisitions. Vendor guidance requires an authorized P-Card or Purchasing-issued PO before ordering. Published PO terms and AP instructions identify the invoice, line-item, delivery and acceptance trail. Obtain the actual incorporated terms, operative rules and delegations before evaluating a transaction; a job title or committee membership does not establish purchase authority.
The published AI policy requires review before purchase or operation, maintained factsheets, and public explanation. Its operative procedures and any superseding edition remain needed. The deputy AI-officer job description identifies evaluation and risk functions, giving the inquiry a defined administrative route. These documents do not establish whether the required work occurred for this infrastructure or its individual applications.
The financial test should reconcile separate stages: authorized budget; signed purchase commitments; invoices; accepted goods and services; payments; remaining obligations; and forecast ongoing costs. Include installation, facilities, energy, cooling, software, support, staffing, replacement, and decommissioning where applicable. Request any vendor financing, leases, grants, discounts, or donated equipment rather than assuming the purchase structure. Expected external receipts must be tested against signed agreements and approved rates.
The technical inquiry is about measured capacity and use. Obtain installed equipment and workload summaries, commissioning records, electrical demand, annual energy forecasts, the cooling method and source of water, and the status and cost of proposed solar or recycled-water measures. Public reporting should distinguish design capacity from actual use and planned measures from operational ones. Generic resource-use claims about very large data centers do not quantify this city facility.
The city's Digital Infrastructure Readiness Plan is a separate published planning process. Its statements about developer deals and hyperscale facilities must be read within that scope. A documented crosswalk is needed before treating that page as evidence about this internal project. No false-statement finding follows simply from placing the two pages side by side.
Named applications now provide a separate test of AI governance. The July 18, 2025 City Detect notice concerns AI/computer vision for housing and code work. The October 18 register separately lists contract 26-1303-00, vendor 37370, as sole source. Neither supplies factory spending, a payment, an executed agreement, or proof of factory hosting. Keep that software trail separate from ePlus/vendor 16681. A later FOIA financial-register extract supplies recorded totals; read those fields with the qualifications in the financial update and source note.
The committee’s July 15, 2025 summary discusses AI-enabled communications tools and chatbot integration. It documents earlier AI-related discussion; June 2026’s no-discussion entry describes its particular agenda item. Neither summary establishes approval of a factory purchase.
The city announced HR, ordinance and citywide-services chatbots on October 31, 2025. The current code-assistant page identifies its answers as general information, rather than official policy or legal advice, and refers official or sensitive matters to city staff. Its Microsoft Copilot Studio embed does not establish backend data flows or factory hosting. The sitewide privacy notice recognizes public-record access and legal exemptions; it does not specify chatbot retention or training terms.
The application-level test is to match each tool to its review, factsheet, data classification, accuracy monitoring, human oversight and retention schedule. An HR information assistant is not proof of prohibited candidate screening. The published disclaimer and feedback invitation are existing controls, without establishing that all required reviews were either completed or omitted.
Earlier council discussion and the separate City Detect presentation show AI work predating the October event. The July interview already describes the factory strategy, so October 15 is not presented as its necessarily first public disclosure. The ePlus event recap confirms participation; sponsor or speaker status does not establish a hardware sale or imply influence over a purchasing decision.
An earlier assessment is also identifiable: the FY2024 financial report's management narrative says the Innovation Office conducted an AI readiness assessment with the Bloomberg Harvard City Leadership Initiative. The underlying assessment and any recommendations carried into the factory business case remain needed. The introductory narrative is not an auditor finding on AI readiness.
The open questions below define the next records work. No new FOIA request or comment inquiry has been sent for this case, and no refusal, missed deadline, or failure to answer is alleged. The case remains an active investigation. A later finding must weigh the actual approvals, applicable terms, implementation evidence, costs, and the city's substantive explanation.
AI-use authorities added October 26, 2026: city policy 1404 controls review before purchase or operation, factsheets, public disclosure, human oversight and prohibited uses. General IT and hiring policies add operational criteria. Covered government personal-information systems also face chapter38 purpose, accuracy, security, access/correction and public-inventory duties, subject to statutory exclusions. Prohibited-product and qualifying cyberincident laws expressly include local public bodies. AI-related public-business records retain normal preservation/access obligations. VITA’s state policy is included for scope comparison: no city adoption is established. EO22 preserves implementing state policies despite rescinding EO30; the consumer-data act expressly exempts governmental bodies. These sources frame records to obtain and do not establish any project-specific breach. Selected court opinions supply five additional legal benchmarks: personal-data system boundaries, persistent movement surveillance, meaningful review of protected-interest decisions, legal-billing redactions and public-body/vendor records custody. The source notes identify each court, procedural posture and precedential weight; the Houston settlement is separately identified as party-published context. These benchmarks guide fact gathering and do not establish a City violation. Court-decision dates are legal background, not events in the factory project.
Source notes and limitations
Project evidence cutoff: October 26, 2026; AI-use legal/policy review added October 26, 2026. This case supports a spending and governance inquiry, not a finding of unlawful procurement, missing money, excessive utility use, an AI-policy breach, or intentional misrepresentation. The city-to-UVA contract link is provisional. June committee minutes are described as posted, not adopted; the March Council minutes are separately identified as adopted. No August outcome, factory purchase order, quantified load, approved chargeback rate, or completed project-specific AI review was obtained. An unavailable recording or missing website link is not proof a record does not exist. Public plans, appropriations, signed commitments and payments are distinct. The $6 million cybersecurity appropriation and its later budget reflection are not two purchases. No factory charge to E1903 is established. The posted purchasing-code edition and internal controls require purchase-date confirmation. No new FOIA or comment inquiry has been sent. Vendor event participation and general AI initiatives are not equipment-sale evidence. No private tip email, source identity, raw resident comments or unrelated meeting testimony is republished. Current authority and actual system/data scope must be matched before assessing compliance. Sector-specific and state-only authorities do not automatically apply to the factory. Application records are separate from factory acquisition: no City Detect or chatbot hosting/funding link is established. The City Detect notice announces intended award, not a signed agreement or paid amount. The posted code-assistant disclaimer is acknowledged; no chatbot accuracy test or sensitive-data submission was performed. The notice’s code citation and the later purchasing-code copy differ; the purchase-date reference remains to be confirmed. Court opinions and later case history were reviewed October 26, 2026. The paired Neal appeals must be read together; current statutory text governs current uses. No commercial citator or independent human/legal review is represented. No protected-interest scoring or comprehensive personal-movement tracking by Newport News is established. The three financial releases are published as labeled selected-field spreadsheet extracts; complete originals are preserved. Two PO releases describe the same order and must not be added. Register Expended Total and PO Total Liquidated do not establish bank clearing. The archive search and attachment review were scoped, not exhaustive.