Enterprise AI Energy
Editorial policy and corrections
How source quality, AI assistance, human review, corrections, and energy boundaries shape this site.
Source-led, transparent, and cautious about claims
Enterprise AI Energy is informational research, not professional advice. Pages show their review date and link to evidence. Product comparisons must state intended use, market, evidence date, limitations, and why a reader might choose an option.
AI-assisted publishing
AI may help discover sources and prepare research proposals. A human editor must verify public copy, sources, scores, market claims, product scope, and safety boundaries before publication. The weekly GitHub workflow cannot publish directly to the main branch.
Who is responsible
Douglas Ross is the Publisher and platform editor. Responsible for the site editorial process and platform operations; not an energy regulator, engineer of record, safety professional, or cyber security assessor.
Independent energy-domain reviewer is Required before publication. No sector-specific energy, safety, engineering, or cyber reviewer is claimed for this release. Domain review remains an explicit publication gate.
Usage measurement
We use Microsoft Clarity to understand how visitors use these public research pages. Clarity is configured with its default masking, and this site does not ask visitors to submit sensitive information.
Corrections
Material changes in regulation, product availability, evidence, or security can trigger an earlier correction. A correction should preserve enough dated context for a reader to understand what changed and why. Contact research@enterpriseaigroup.com.
Please do not send operational technology details, customer records, vulnerability information, credentials, commercial secrets, or other sensitive data. The site does not replace institutional policy or professional advice.
Keep the useful part
Tell us what energy decision is next.
Send the asset, grid, market, customer, safety, cyber, or engineering workflow you are assessing. We will use it to shape the next practical buyer brief.
Useful detail: include the market, workflow, or category behind an editorial correction.
Please do not send operational technology details, customer records, vulnerability information, credentials, commercial secrets, or other sensitive data.