An independent BC + AI public-interest initiative

Public working draftv0.2.0 · Updated

BC Public Compute Project

What we power. Who benefits. What stays here.

British Columbia is deciding which new data-centre proposals may advance toward scarce clean electricity. BC + AI is building an independent public-interest framework and pilot registry to show who owns these projects, what they consume, who carries the cost, who has authority, and what durable value remains in B.C.

Public compute reads major compute infrastructure through the public interest. Public access is one possible benefit. It is not the whole definition.

This is an independent BC + AI project. It is not an official government registry, a regulator, a utility, a Nation government, or a decision authority.

Archival-style graphic: a halftone triangle of mountains and cloud set against fine surveyor's rule lines on black, with a single lime-green triangle.

Public evidence atlas

Archival survey imagery introduces the project as a public record under construction, not a finished approval system.

Why this matters

AI is heavy industry now.

AI now arrives as substations, cooling, water, fibre, backup generation, specialized chips, and a great deal of electricity. Building it uses public infrastructure and raises basic questions about what gets built, who pays, and what the rest of us receive in return.

B.C. has started using a competitive process for specified new AI and conventional data-centre capacity. That is real policy machinery. The wider public record remains scattered across utility documents, land records, council agendas, permits, and company announcements.

Swipe horizontally to inspect the full diagram →

One megawatt, five different words: five capacity measures that must not be collapsed into one number
Requested, allocated, contracted, connected and actual are five different measurements, not five words for one number. The equal bands separate the words; they do not show a quantity or ratio.
Read this figure as text
The five stages of electricity capacity, from earliest and least binding to latest and physically measured. The stages are ordered, but no proportion between them is shown.
StageTermWhat it measuresWho decidesWhere it is recorded
01: RequestedPC-TRM-001Capacity a proponent asks the utility or call process to consider. Eligible 2026 Call for Demand requests are bounded from 10 to 145 MW.ProponentApplication request
02: AllocatedPC-TRM-002Capacity a competitive process or regulation makes available to a selected project or sector window. Selection does not energize a site.BC Hydro under B.C. Reg. 8/2026Call selection outcome
03: ContractedPC-TRM-003Capacity written into a binding supply, interconnection or facilities agreement.BC Hydro and the proponentBinding agreement
04: ConnectedPC-TRM-004Capacity actually interconnected and able to draw service, or the in-service peak recognized by the utility.BC Hydro interconnectionUtility in-service records
05: ActualPC-Q-002What the facility measurably draws in operation, recorded as peak demand and annual energy rather than a fifth MW term.Physical operationMetered operating data
  • Equal bands, on purpose. The figure shows no proportion between stages, and the measures must never be summed or relabelled as one another.
  • A project can remain at any stage for years and may never reach the next. Those gaps are where requested capacity is often quoted as if it were connected capacity.
  • Absence is shown as “not disclosed” or “not yet reached,” never as zero.

When a project asks for a share of B.C.'s clean power, the public should be able to see what it powers, who controls it, who carries the cost, and what stays here after the ribbon-cutting.

Five public tests

Five questions. Every major project. In public.

Short enough to remember at a council meeting. Hard enough to show where a proposal is specific, vague, or asking the public to take too much on faith.

  1. 01

    Who owns it?

    Show the owner, operator, parent and controlling entities, including material changes over time.

    Makes visible

    Facility identity · Ownership and control · Material changes

  2. 02

    What does it consume?

    Keep requested, allocated, contracted, connected, and actual electricity separate. Report water, cooling, heat, backup generation, and environmental impacts with clear boundaries.

    Makes visible

    Electricity · Water and cooling · Environment

  3. 03

    Who pays for the load?

    Identify responsibility for project-specific grid upgrades, municipal services, emergency response, monitoring, and decommissioning.

    Makes visible

    Grid upgrades · Infrastructure contributions · Financial security

  4. 04

    What remains in British Columbia?

    Track lasting work, wages, procurement, research, company formation, public and small-business compute access, skills, infrastructure, and delivered outcomes.

    Makes visible

    Jobs and procurement · Compute access · Commitments and performance

  5. 05

    Who has power over the decision?

    Distinguish the authority of First Nations governments and rights holders, local governments, the Province, BC Hydro, regulators, federal bodies, communities, proponents, and qualified professionals.

    Makes visible

    Authority context · Authorized Nation-controlled disclosure · Approvals

Jobs and procurement promises cannot cancel out unresolved rights, unavailable utility capacity, an unsafe design, or an unproven water source.

The B.C. position

Start from what exists. Finish what is missing.

Saying B.C. has done nothing would be false. Saying the current process is a complete lifecycle accountability framework would be convenient. The gap between those two sentences is the work.

B.C. already has

  • A competitive process with capacity, request, price, and curtailment rules.
  • Economic, environmental, sovereignty, and First Nation benefit and impact criteria.
  • Distinct responsibilities held by First Nations, governments, utilities, and regulators.

B.C. still needs

  • One readable lifecycle record of ownership, resources, commitments, results, and material changes.
  • Definitions that separate requested power from connected power and promises from results.
  • Monitoring, corrections, disclosure controls, and remedies that survive ownership changes.

The first column describes current law, policy and process at a high level. The second column contains BC + AI recommendations, not legal requirements.

What you can use

Turn the questions into tools people can use.

The position paper and pilot registry are available now. The Decision Toolkit is not yet public.

Position paper

AI Is Heavy Industry Now

The full argument for treating major compute infrastructure as a public bargain around resources, authority, accountability, and durable capability.

Read the position paper

Pilot registry

BC Public Compute Registry

An independent pilot that brings ownership, resources, commitments, sources, and missing information into one readable record. It separates fictional examples from records assembled from public sources. It is not an official registry, approval, or ranking.

Browse the pilot registry

Not yet public

Data Centre Decision Toolkit

A structured set of questions for reviewing evidence, authority, conditions, monitoring, and decommissioning. It will remain out of public use until qualified review and Nation-led governance work are complete.

How we work

Evidence first. Authority where it belongs.

Authorized governance decisions determine what may publish. One projection layer enforces them. Every material claim points to a source. Requested, allocated, contracted, connected, and actual electricity remain separate. Unknown, not disclosed, and disputed never become zero. Promises remain separate from results.

Swipe horizontally to inspect the full diagram →

Four disclosure classes tested in a fixed order of precedence
The four disclosure classes are a decision order, not a legend. Nation-controlled is tested first and outranks every generic public flag; an expired or withdrawn disclosure authority withholds a published value again.
Read this figure as text
  1. Test 01: is this value governed by a Nation or an authorized body? If yes, PC-DSC-004 Nation-controlled applies. Collection, interpretation, use, retention and publication are governed by that Nation or authorized body. The default is do not collect, do not commit and do not publish.
  2. Test 02: is there a legitimate reason to withhold? If privacy, security, privilege, critical-infrastructure or a narrow commercial reason applies, PC-DSC-003 Protected applies and the value is withheld or generalized.
  3. Test 03: is facility-level detail safe and non-misleading? If no, PC-DSC-002 Aggregated applies. A roll-up that can identify one proposal is not disclosed.
  4. No exclusion applies. PC-DSC-001 Public applies, with source and effective-date context.
Override
Nation-controlled classification outranks every generic public flag, including a value already marked public.
Reversion
A published value is withheld again when its disclosure authority expires or is withdrawn.

Swipe horizontally to inspect the full diagram →

Authorized decisions determine what publishes; one server-side layer enforces them: the projection boundary
Authorized governance decisions determine what may publish. One server-side layer enforces them: protected and Nation-controlled values stop at the boundary before any page, payload, export, feed or index is generated.
Read this figure as text

The stored record holds values from all four disclosure classes. Every value is evaluated at one server-side projection boundary, and no output exists until the value has passed it.

What the projection layer does with each stored value
Stored valueClassAt the boundary
Requested capacityPC-DSC-001 PublicPasses
Regional roll-up countPC-DSC-002 AggregatedPasses, rolled up
Site security detailPC-DSC-003 ProtectedWithheld before the boundary
Territory-specific recordPC-DSC-004 Nation-controlledWithheld before the boundary
  • Values that pass feed five outputs: the page, structured payload, downloadable export, syndication feed and search index.
  • Material changes append to version history; prior values are not silently overwritten.
  • Automated tests exercise each refusal, so a leaked protected value fails the test suite.

Public

Facility-level information needed for public accountability, with source and effective-date context.

Still carry source IDs and source status.

Aggregated

Information useful at a regional or system level but unsafe or misleading at excessive granularity.

Small-N geographic roll-ups can identify a single proposal. When they can, drop to not-disclosed. Aggregation or generalization cannot convert Nation-controlled information into ordinary public data or bypass authorization.

Protected

Information withheld or generalized for legitimate privacy, security, privilege, critical-infrastructure or narrow commercial reasons.

Ordinary statutory and commercial confidentiality only. If the material is Nation-controlled, use PC-DSC-004 instead, even if a contract also marks it confidential.

Nation-controlled

BC + AI's working handling commitment pending the scoped work in #1995, not a universal legal determination: collection, interpretation, use, retention and publication stay with the relevant Nation or authorized body.

Default: do not collect, commit, or publish. Nation-controlled is BC + AI's working handling commitment pending the scoped work in #1995, not a universal legal determination. The relevant Nation or authorized body determines authorization within its authority; issue #1995 and PC-REV-001 track BC + AI's review and documentation of that authorization and do not themselves own or create it. Agents do not invent disclosure rules to 'be helpful.'

Bring a missing piece

Bring evidence. Challenge the record.

Found a wrong source, missing value, or disagreement between public records? Point us to evidence we can check.

Participants seated in a circle at an AI Ethical Futures Lab session while a facilitator speaks from the front of the room.
A facilitated AI Ethical Futures Lab discussion. Community participation informs the questions; it does not replace legal, regulatory or rights-holder authority.

Evidence and corrections

  • Every material claim carries a source ID and a classification: law, policy, standard, comparator, inference, recommendation or unresolved question.
  • Requested, allocated, contracted, connected and actual electricity remain separate.
  • Unknown, not disclosed, disputed, superseded and not applicable do not become zero.
  • Promises remain separate from commitments, milestones and delivered outcomes.
  • Nation-controlled information is excluded unless the relevant Nation or authorized body permits publication.
  • The no-editorial-veto principle does not override Nation-controlled disclosure authority, privacy, security, legal duties, or protected-information rules.
  • Material changes and corrections append history instead of silently rewriting it.

Take part

Contribute evidence or request a correction.

We are looking for source corrections, municipal and utility expertise, water and cooling review, privacy and security review, accessibility review and properly scoped, compensated First Nations governance and data-governance participation.

Do not send confidential, personal, security-sensitive or Nation-controlled information through the general contact route.