Clarify how legal responsibility is allocated across the AI supply chain
9 submissions. Each submission counts once for this shared ask. Counts do not measure importance or merit.
A shared ask groups requests for substantially the same action from three or more submissions when the group was created. Groups remain listed if withdrawals reduce their counts. AI models summarised recommendations, grouped them and checked the groups. The label summarises the requests; it is not a quote. A shared ask does not mean agreement on anything else.
Theme: Developer and deployer obligations
Recommendations from submissions
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. Extracts are chosen by an AI model. Submissions are listed in submission number order; recommendations follow their order on each submission’s page.
PwC Submission 46
Close targeted gaps in existing frameworks first, prioritising supply chain accountability, agent identity and authorisation, and inventory and assurance obligations for high-risk uses.
Close targeted gaps in existing frameworks first, prioritising supply chain accountability, agent identity and authorisation, and inventory and assurance obligations for high- risk uses.
Workday Submission 51
Preserve clear delineation of developer and deployer roles across the agentic AI value chain.
Preserve clear delineation of roles and responsibilities across the agentic AI value chain, tailoring obligations to developers and deployers according to their distinct visibility and control.
Vault Submission 84
For higher-risk AI deployments, have regulation and assurance frameworks give greater clarity on responsibility for underlying infrastructure, including data location, administrative access, operational control, supply-chain dependencies and incident response.
For higher-risk AI deployments, regulation and assurance frameworks should provide greater clarity around responsibility for the underlying infrastructure. This should extend beyond the AI system itself to include data location, administrative access, operational control, supply-chain dependencies and incident response, consistent with emerging international approaches to cloud and AI sovereignty.
AQ Intelligence (AQI), Guardrail Technologies Australia (GTA) and First Nations Strategic Alliance (FNSA) Submission 202
Clarify accountability across the AI supply chain by allocating responsibility between developer, deployer, integrator and professional user.
Clarify accountability across the AI supply chain, allocating responsibility between developer, deployer, integrator and professional user to remove the liability uncertainty that is freezing adoption.
ARC Centre of Excellence for Automated Decision-Making and Society Submission 203
Clarify liability across the AI value chain: how responsibility passes between or is shared among actors, and how to coordinate to address co-created risks.
We have recommended measures to clarify to stakeholders across the AI value chain how responsibility passes between them or is shared, and how to coordinate to address co-created risks.
Bravehearts Submission 219
Establish clear accountability across the AI supply chain so responsibility for child safety cannot be avoided through fragmentation between model developers, platforms and downstream services.
Establish clear accountability across the AI supply chain, so responsibility for child safety cannot be avoided through fragmentation between model developers, platforms and downstream services.
Westpac Submission 302
Continue to examine how accountability is shared across the AI value chain, including the responsibilities of model developers and platform providers where foreseeable misuse arises from capabilities within their control.
Policymakers should continue to examine how accountability is shared across the AI value chain, including the responsibilities of model developers and platform providers where foreseeable misuse arises from capabilities within their control.
Woolworths Group Submission 303
Allocate responsibility for AI based on the context and nature of the decision and who is best placed to manage the risk, rather than codifying a fixed developer and deployer split.
Rather than codifying a fixed developer and deployer split, we think a more durable framework is one that allocates responsibility based on the context and nature of the decision being made and who is best placed to manage its associated risk.
Google Submission 319
Align accountability with operational controls across the AI lifecycle: upstream developers provide technical documentation, evaluations and baseline safety benchmarks for foundation models; downstream deployers manage operational contexts, user controls and human oversight.
Accountability must align with operational controls across the AI lifecycle: ● Upstream developers: Provide technical documentation, evaluations, and baseline safety benchmarks for foundation models. ● Downstream deployers: Manage operational contexts, deploy user controls, and maintain human oversight.
A program corrected obvious text-recognition errors in this quote for display.