AI Inquiry Atlas

An unofficial, independent guide to the public records of the Joint Select Committee on Artificial Intelligence. Not connected with the Parliament of Australia or the committee. Its makers also made a submission (no. 481; see About). Summaries and scores are written by AI and can be wrong: check the original before relying on them.

Submission 400

N

Submitter group: Individuals.

Position labels are not shown for individual submitters.

An AI model identified the submitter group and wrote the summary, key points and recommendation summaries. Counts do not measure importance or merit.

Open in the interactive guide

Summary

Read the original submission for the full text.

Argues that sovereign AI capability depends on assured access, control, resilience and portability, not domestic megawatts alone. Proposes functional tests, milestone-linked support, enforceable infrastructure commitments, resilient procurement and common reporting through existing institutions. Opposes a new compute authority, general data-centre licensing or nationality tests, and blanket closure bonds; recommends proportionate safeguards.

Key points

Quotes are the submitter’s own words. Text taken from documents, including scanned pages read by text-recognition software, can differ from the PDF. Check the original. Listed in the same order as on the submission’s page in the interactive guide.

  1. The submitter argues that sovereign capability exists when Australian users can obtain suitable compute under Australian law, keep practical control of critical workloads, recover from disruption and move data and services.

    Sovereign capability exists when Australian users can obtain suitable compute under Australian law, maintain practical control of critical workloads, recover through disruption and move data, models and services when an arrangement fails.

  2. The submitter argues that claims about sovereign capacity and energy should be verified against delivery, using existing institutions rather than a new compute authority.

    Claims about sovereign capacity, additional energy, flexibility, regional benefit and Australian access should be described in common terms, verified against delivery and adjusted when they do not materialise. This can be done through existing procurement, investment, planning, network, water and security institutions. A new compute authority is not required.

  3. The submitter argues that attributable network, generation, water and site costs should remain with the project that causes them.

    Attributable network, generation, water, treatment, pumping, resilience and site-remediation costs should remain with the project that causes them.

  4. The submitter argues that flexibility should earn policy or connection credit only when defined, controllable and auditable.

    Flexibility should receive policy or connection credit only when the agreement defines megawatts, response time, duration, frequency, notice, telemetry, override rights, recovery profile and rebound peak. The operator must have the technical and contractual authority to deliver it, including tenant flow-down where workloads are controlled by customers.

  5. The submitter argues that data sovereignty should be addressed contractually and operationally, since local storage alone does not resolve who holds administrative power or whether assets can be recovered.

    This approach also provides a disciplined meaning for data sovereignty. Local storage is useful, but it does not resolve who holds administrative power, whether model or data assets can be recovered, or whether a foreign legal or supply-chain disruption can interrupt the service. Those questions should be answered contractually and operationally.

Recommendations

Recommendations are shown beside the submission’s own words. Listed in the same order as on its page in the interactive guide.

  1. Apply a functional sovereign-compute test to Commonwealth procurement, support and strategic planning, assessing availability and control under deteriorating commercial, technical or geopolitical conditions.

    The Committee should recommend a functional sovereign-compute test for Commonwealth procurement, support and strategic planning. It should assess whether a capability remains available and controllable when commercial, technical or geopolitical conditions deteriorate.

  2. Assess legal/operational jurisdiction over data, weights, controls, logs, providers and subcontractors, plus assured access for defined Australian users/functions with committed type, quantity, priority, duration and service level.

    Legal and operational jurisdiction, including where data, model weights, administrative controls and security logs are held, and who can direct material providers and subcontractors. Assured availability for defined Australian users or critical functions, including the compute type, quantity, priority, duration and service level actually committed.

  3. Assess local operation, maintenance and restoration capability, provider/geographic/energy/telecommunications/equipment concentration, and usable data/weights/configuration export and transition assistance.

    Local capability to operate, maintain and restore the service, and exposure to provider, geographic, energy, telecommunications and equipment-supply concentration. Portability and exit, including access to data, model weights, configurations and transition assistance in usable formats.

  4. Avoid general data-centre licensing or nationality tests; credit international facilities where they assure Australian capability, rather than substituting Australian ownership or address for evidence of control, continuity and access.

    This should not become a general licence for every data centre or a nationality test. International investment and globally operated facilities can contribute materially if the arrangements produce assured Australian capability. Conversely, Australian ownership or an Australian street address should not substitute for evidence of control, continuity and access.

  5. Where developers offer Australian start-ups, researchers, not-for-profits or critical services favourable compute for public support, specify eligibility, capacity, availability, pricing, duration and termination; credit promises only when contractible and measurable.

    Where a developer offers favourable compute access to Australian start-ups, researchers, not-for-profits or critical services in return for public support, the commitment should specify eligible users, capacity, availability, pricing basis, duration and termination rights. A broad promise of future access should carry no policy credit until it is contractible and measurable.

  6. Report each maturity stage separately in national reporting and government decisions; never add stages together as operational capacity.

    National reporting and government decisions should use a common maturity ladder. Stages should be reported separately; they should not be added together and presented as if all capacity were operational.

  7. Use evidence-specific stages: announced intentions; site control/approvals pathways; service studies without reserved capacity; identified binding contracts/finance/conditions; funded construction; tested operating commissioning; and commissioned capacity with enforceable Australian access, control and resilience.

    Announced Public intention or non-binding target only Site and approvals Site control and a defined planning and approvals pathway Services studied Network, generation, water and telecommunications studies; no implication that capacity is reserved Contracted and financed Binding material contracts, finance and conditions precedent capable of being identified Under construction Physical works underway against a funded program Commissioned Energised, tested and operating at a stated level Available sovereign capability | Commissioned capacity plus enforceable Australian access, control and resilience attributes

  8. Where support depends on promised capacity or public benefit, release assistance against objective milestones, with proportionate step-down, recovery or reallocation on material failure.

    If Commonwealth procurement, grants, tax support, land access or project facilitation depends on promised capacity or public benefit, assistance should be released against objective milestones. Material failure should trigger a proportionate step-down, recovery or reallocation of the benefit.

  9. Do not create tradable/property-like future grid or compute rights through the maturity ladder; keep connection and forecasting management with existing network and market bodies.

    The maturity ladder should inform planning and forecasting without creating a tradable or property-like right to future grid or compute capacity. Existing network and market bodies should continue to manage connections and system forecasts.

  10. Have the Commonwealth set outcome definitions and federal-support conditions, relying on state, territory and market instruments for detailed planning, connections and pricing.

    The Commonwealth's role should be to set outcome definitions and conditions for federal support, then rely on state, territory and market instruments for detailed planning, connection and pricing.

  11. For projects offering new generation/storage, specify assets, commercial commitment, commissioning, demand matching, firmness and scarcity treatment; do not relabel existing clean supply as additional when a new buyer acquires it.

    Where a project claims that new generation or storage supports its load, it should identify the assets, commercial commitment, expected commissioning date, demand-matching method, firmness and treatment during scarcity. Existing clean supply should not be relabelled as additional merely because a new buyer acquires it.

  12. Keep attributable network, generation, water, treatment, pumping, resilience and site-remediation costs with the project causing them.

    Attributable network, generation, water, treatment, pumping, resilience and site-remediation costs should remain with the project that causes them.

  13. Credit flexibility only with defined MW, timing, duration, frequency, notice, telemetry, override/recovery/rebound, and operator technical/contractual authority, including tenant flow-down where customers control workloads.

    Flexibility should receive policy or connection credit only when the agreement defines megawatts, response time, duration, frequency, notice, telemetry, override rights, recovery profile and rebound peak. The operator must have the technical and contractual authority to deliver it, including tenant flow-down where workloads are controlled by customers.

  14. Review performance where flexibility earns material concessions and adjust them for persistent deficiencies; do not assume critical or technically inflexible workloads participate.

    Where a material concession depends on flexibility, actual performance should be reviewed and the concession adjusted if delivery is persistently deficient. Critical or technically inflexible workloads should not be assumed to participate.

  15. Cover source, annual and peak demand, reuse, drought settings and indirect demand in water reporting, and assess grid, water, fibre, hazards, housing, workforce and local impacts together rather than presuming regional suitability.

    Water reporting should cover source, annual and peak demand, reuse, drought settings and material indirect demand. Regional location should not be presumed beneficial or suitable. Grid strength, water security, fibre, hazards, housing, workforce and cumulative local impacts should be assessed together.

  16. Tie public support for regional development to measurable local outcomes rather than broad forecasts.

    Public support for regional development should be tied to measurable local outcomes rather than broad forecasts.

  17. For higher-consequence workloads, apply risk-proportionate contracting for locations/jurisdictions, dependencies, recovery/failover, asset and audit export, transition/deletion, ownership/insolvency/termination/degradation rights, local response/security and agency information-sharing.

    For higher-consequence workloads, procurement and contracting should address the following matters in proportion to risk. • Workload classification and the permitted locations and legal jurisdictions for data, models, logs, backups and administration. • Provider, region, telecommunications, electricity and critical-equipment dependencies, including material subcontractors. • Recovery objectives, alternate capacity and evidence from periodic continuity or failover testing. • Export of data, model weights, configurations and audit records in usable formats, plus transition assistance and deletion confirmation. • Change-of-control, insolvency, termination and severe service-degradation rights. • Local escalation, maintenance and security capability and timely information-sharing with responsible agencies.

  18. Require realistic tested exit routes, allowing alternate capacity/geographic separation for the most critical workloads and documented export/transition for lower-consequence workloads, without requiring simultaneous multi-provider operation.

    Portability does not require every workload to run simultaneously across multiple providers. It requires a realistic, tested route out of a failed or unacceptable arrangement. For the most critical workloads, that may justify alternate capacity or geographic separation; for lower-consequence workloads, documented export and transition arrangements may be sufficient.

  19. Have the Commonwealth lead a compact data dictionary for existing Commonwealth, state and market bodies to collect once and reuse lawfully.

    The Commonwealth should lead a compact data dictionary that existing Commonwealth, state and market bodies can collect once and reuse for their lawful purposes.

  20. Include project identity, operator/controllers, site/maturity; requested/contracted/commissioned/utilised electrical capacity, IT load/efficiency; water source/peaks/reuse/discharge/drought; generation/firming/storage additionality; contracted/delivered flexibility/rebound/failure; and public support/concessions with Australian-access/local-capability commitments.

    • Project identity, operator, controlling entities, site and maturity stage. • Requested, contracted, commissioned and utilised electrical capacity, plus IT load and relevant efficiency measures. • Annual and peak water use by source, reuse, discharge and drought-response settings. • Generation, firming and storage commitments and the evidence relied on for additionality. • Flexibility contracted and delivered, including rebound and material non-performance. • Public support, infrastructure concessions and corresponding Australian-access or local-capability commitments.

  21. Include decommissioning/making-safe plans assigning responsibility for equipment, hazardous materials, utilities, data-bearing assets and site handback.

    A decommissioning and making-safe plan identifying responsibility for equipment, hazardous materials, utilities, data-bearing assets and site handback.

  22. Report in two layers: project-level information to responsible agencies under protected arrangements, and aggregated information to the public.

    Reporting should have two layers. Responsible agencies should receive the project-level information they need under protected arrangements. The public should receive aggregated information sufficient to understand system demand, water use, delivery status and public commitments without exposing security-sensitive architecture or commercially harmful detail.

  23. Use proportionate decommissioning plans at approval/contracting, without blanket bonds; exhaust existing planning, lease, corporate and security mechanisms, reserving financial assurance for credible closure risks from structure, tenure, special-purpose entities or hazardous residual obligations.

    The lifecycle element should remain proportionate. A standard plan at approval or contracting stage is sensible. A blanket bond for every project is not. Existing planning, lease, corporate and security mechanisms should be used first, with financial assurance reserved for cases where project structure, land tenure, special-purpose entities or hazardous residual obligations create a credible closure risk.

  24. Ask government to publish common definitions and a responsibility map alongside the standards, showing where each obligation sits.

    The Committee should ask government to publish the common definitions and responsibility map alongside the standards so proponents and communities can see where each obligation sits.

Read the original

Open in the interactive guide