Organizations and roles connected to Project River, separated from assumptions about responsibility, experience, or legal obligation.
Public project materials identify the Wright family as the landowner/development sponsor. Parcel ownership and the legally responsible project entity should be verified phase by phase through deeds and executed agreements.
Sources:RIV-013RIV-014RIV-015RIV-016RIV-020RIV-021RIV-022RIV-023
Azure Engineering lists Project River and describes feasibility/conceptual work plus future preliminary engineering and permitting. Exact contractual scope, engineer-of-record status, EPC responsibility, and performance guarantees remain important open evidence questions.
An SEC filing confirms Algorhythm’s Sept. 15 acquisition transaction involving Azure Energy. The filing establishes the corporate transaction; it does not by itself establish what obligations Algorhythm has assumed toward Project River.
The city controls municipal annexation/zoning proceedings within its authority and announced the temporary suspension of direct Project River meetings pending an engineering review.
Bradley County records are directly relevant to the surrounding unincorporated community and to the documented interlocal annexation history. County planning, road, parcel, and service records remain important evidence sources for evaluating the project.
Sources:RIV-005
Environmental permits, traffic/access approvals, and utility/interconnection arrangements are distinct from city land-use approval. The responsible agency depends on the specific facility component and filing.
Two evidence questions should remain separate: what the current company has completed and what individual team members worked on at previous employers or ventures. Algorhythm’s press release says the Azure team has participated in 72 power-generation facilities representing 17.5 GW. That is a company statement about collective team experience, not a project-by-project independent audit of Azure Energy’s own completed plants.
A stronger due-diligence record would include owner-verifiable operating references, exact personnel roles, current engineering licenses, signed scopes, warranties, bonds, and performance obligations rather than relying only on aggregate portfolio claims.
Needed to verify actual modules, operating references, warranties, fuel quality limits, and acceptance testing.
Needed to verify turbine/generator configuration, controls, emissions, cooling, and first-phase design.
Needed to establish delivery interfaces, bonding, commissioning, and corrective-work responsibilities.
Needed to establish actual load, cooling requirements, staffing, emergency plans, and operating obligations.
