|
| 1 | +# Data-Center / AI Infrastructure Governance Profile |
| 2 | + |
| 3 | +**Status**: APPLIED PROFILE DRAFT |
| 4 | +**Scope**: evidence surfaces for AI infrastructure and data-center public-benefit claims |
| 5 | +**Implementation status**: NOT_IMPLEMENTED |
| 6 | +**Core mutation**: NONE |
| 7 | + |
| 8 | +## Purpose |
| 9 | + |
| 10 | +AI infrastructure is not only compute. It can affect energy systems, water systems, land use, heat flows, grid flexibility, public benefit, and local accountability. |
| 11 | + |
| 12 | +This profile uses Riverbraid's claim-versus-evidence pattern to make those claims inspectable. |
| 13 | + |
| 14 | +## Core question |
| 15 | + |
| 16 | +```text |
| 17 | +What public-benefit claims are being made, and what evidence supports each claim? |
| 18 | +``` |
| 19 | + |
| 20 | +Riverbraid does not decide the politics of infrastructure. It can help prevent public-value claims from hiding inside fragmented paperwork. |
| 21 | + |
| 22 | +## Evidence surfaces |
| 23 | + |
| 24 | +| Surface | Question | Example evidence | |
| 25 | +|---|---|---| |
| 26 | +| Energy use | How much power is consumed and when? | metered load data, utility reports, interconnection records | |
| 27 | +| Water use | What water source is used and how much? | potable/reclaimed/closed-loop data, permits, water reports | |
| 28 | +| Heat reuse | Is waste heat reused? | thermal delivery records, heat reuse contracts, metered MWh thermal | |
| 29 | +| Grid flexibility | Can the site reduce load or support the grid? | demand response records, battery dispatch logs, response time evidence | |
| 30 | +| Compute commons | Is public or research compute offered? | allocated hours, user groups, access policy, usage logs | |
| 31 | +| Public benefit | What benefit is claimed and who receives it? | public ledger, community agreements, benefit reports | |
| 32 | +| Agency responsibility | Who is responsible for each claim? | agency map, owner map, escalation route | |
| 33 | +| Transparency | What is visible to public reviewers? | dashboard, audit packet, public reports | |
| 34 | + |
| 35 | +## Suggested metrics |
| 36 | + |
| 37 | +- PUE / WUE / CUE where relevant |
| 38 | +- MWh consumed |
| 39 | +- MWh thermal reused |
| 40 | +- percentage of water from non-potable or closed-loop sources |
| 41 | +- MW of flexible load |
| 42 | +- response time for grid events |
| 43 | +- battery capacity available for public/grid support |
| 44 | +- public compute hours allocated |
| 45 | +- local ratepayer cost impact |
| 46 | +- unresolved community burden reports |
| 47 | + |
| 48 | +## Claim record format |
| 49 | + |
| 50 | +```yaml |
| 51 | +claim_id: |
| 52 | +claim_text: |
| 53 | +claim_owner: |
| 54 | +evidence_required: |
| 55 | +evidence_available: |
| 56 | +verification_status: |
| 57 | +known_limitations: |
| 58 | +non_claims: |
| 59 | +responsible_agency: |
| 60 | +review_cadence: |
| 61 | +``` |
| 62 | +
|
| 63 | +## Failure behavior |
| 64 | +
|
| 65 | +If a public-benefit claim lacks evidence, the claim should move to: |
| 66 | +
|
| 67 | +```text |
| 68 | +CLAIM_UNSUPPORTED_PENDING_EVIDENCE |
| 69 | +``` |
| 70 | + |
| 71 | +If a metric is promised but not measurable, the profile should mark: |
| 72 | + |
| 73 | +```text |
| 74 | +MEASUREMENT_SURFACE_ABSENT |
| 75 | +``` |
| 76 | + |
| 77 | +## Non-scope |
| 78 | + |
| 79 | +This profile does not: |
| 80 | + |
| 81 | +- approve or reject a data center |
| 82 | +- claim environmental compliance |
| 83 | +- replace local permitting |
| 84 | +- replace utility review |
| 85 | +- certify public benefit |
| 86 | +- guarantee community consent |
| 87 | +- prove climate benefit |
| 88 | + |
| 89 | +## Boundary |
| 90 | + |
| 91 | +This is an applied profile draft. It does not create a live dashboard, legal status, infrastructure approval, or external audit claim. |
0 commit comments