<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>multimodal transfer instruction &#8211; Science</title>
	<atom:link href="https://scienmag.com/tag/multimodal-transfer-instruction/feed/" rel="self" type="application/rss+xml" />
	<link>https://scienmag.com</link>
	<description></description>
	<lastBuildDate>Thu, 15 Oct 2026 20:11:59 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=7.1.3</generator>

<image>
	<url>https://scienmag.com/wp-content/uploads/2024/07/cropped-scienmag_ico-32x32.jpg</url>
	<title>multimodal transfer instruction &#8211; Science</title>
	<link>https://scienmag.com</link>
	<width>32</width>
	<height>32</height>
</image> 
<site xmlns="com-wordpress:feed-additions:1">73899611</site>	<item>
		<title>Five-Pillar Framework Proposed to Govern Generative AI in Urban Mobility</title>
		<link>https://scienmag.com/five-pillar-framework-proposed-to-govern-generative-ai-in-urban-mobility/</link>
		
		<dc:creator><![CDATA[Courtney Benton]]></dc:creator>
		<pubDate>Thu, 15 Oct 2026 20:11:59 +0000</pubDate>
				<category><![CDATA[Science News]]></category>
		<category><![CDATA[AI accountability]]></category>
		<category><![CDATA[AI ethics]]></category>
		<category><![CDATA[AI failure modes in transport]]></category>
		<category><![CDATA[AI in urban transit planning]]></category>
		<category><![CDATA[AI safety and oversight in mobility]]></category>
		<category><![CDATA[AI-assisted transit dispatch]]></category>
		<category><![CDATA[AI-driven traffic management]]></category>
		<category><![CDATA[algorithmic auditing]]></category>
		<category><![CDATA[challenges of governing generative AI in mobility]]></category>
		<category><![CDATA[foundation models]]></category>
		<category><![CDATA[four-quadrant governance model]]></category>
		<category><![CDATA[future transportation AI governance framework]]></category>
		<category><![CDATA[generative AI]]></category>
		<category><![CDATA[generative AI in transportation]]></category>
		<category><![CDATA[governance framework]]></category>
		<category><![CDATA[human-in-the-loop]]></category>
		<category><![CDATA[institutional AI regulation for cities]]></category>
		<category><![CDATA[maturity model]]></category>
		<category><![CDATA[multimodal transfer instruction]]></category>
		<category><![CDATA[public transit]]></category>
		<category><![CDATA[transport governance]]></category>
		<category><![CDATA[transport policy]]></category>
		<category><![CDATA[urban mobility]]></category>
		<category><![CDATA[urban mobility AI governance]]></category>
		<guid isPermaLink="false">https://scienmag.com/?p=277478</guid>

					<description><![CDATA[Researchers have proposed a five-pillar, twelve-proposition governance framework to close the widening gap between generative AI capabilities in urban mobility and the instruments available to regulate them.]]></description>
										<content:encoded><![CDATA[<p>Generative artificial intelligence has swept into the control rooms and dispatch desks of urban transport faster than any governance framework can follow. Large language models now justify traffic-signal phase changes, foundation models draft multimodal transfer instructions, diffusion models synthesize travel-demand scenarios, and agentic planners coordinate bus, rail, and micro-mobility fleets. According to a new hypothesis-and-theory article published in Frontiers in Future Transportation, this wave of capability has crossed a deployment threshold while the oversight architecture that is supposed to constrain it has not moved at all, creating what the authors call the four-quadrant problem: methods are mature, governance is absent, and no existing institutional remedy covers that asymmetry.</p>
<p>The study, authored by Nirmal Acharya of Central Queensland University and Padmaja Kar of the Australian International Institute of Higher Education, argues that conventional transport-AI governance was built for a different species of machine. Older tools such as adaptive signal controllers, origin-destination estimators, and automatic vehicle location pipelines had bounded decision envelopes, numerical outputs, and failure modes that could be written into procurement documents. Generative systems break every one of those assumptions simultaneously. Their outputs are open-ended natural language, their failure modes include hallucination and prompt injection, and their decision envelopes shift whenever a vendor silently updates the base model, something a municipal contract cannot pin down.</p>
<p>The authors first test whether the four canonical cross-sector AI instruments can fill the void: the NIST AI Risk Management Framework, the EU AI Act, the OECD AI Principles, and ISO/IEC 42001. Each, they conclude, is serious but insufficient. The NIST framework&#8217;s domain-agnostic functions do not specify safety-critical, spatially distributed failure modes. The EU AI Act&#8217;s high-risk obligations assume the product-lifecycle conformity familiar from medical devices, not foundation models that retrain continuously. The OECD principles are non-binding and offer no maturity scale, and ISO/IEC 42001&#8217;s annual audit cadence is incompatible with systems that drift on weekly timescales. These instruments answer what values an agency should uphold, but not how mature a given system&#8217;s governance is today or what the next operational increment should be.</p>
<p>To make the gap tractable, the paper organizes the missing controls into six governance voids, split into two classes. Operability voids break day-to-day assurance: output-level traceability, where a single prompt&#8217;s output cannot be traced to an audit artifact because prompt-response logs and versioned model snapshots are not contractually retained; audit-cadence mismatch, where a system passes a scheduled audit and then changes materially the following week through a vendor-side update; and meaningful human control, where operators flooded with high-frequency co-pilot recommendations learn to rubber-stamp approvals, leaving logs that are formally complete but cognitively empty. Institutional voids break the contracts that make operability enforceable: liability diffusion across the vendor, integrator, and operator chain; equity measurement that ignores the conversational surface where accents and dialects determine whether service is delivered at all; and cross-jurisdictional portability, where conformity in a strict regulatory regime does not transfer to a lighter one.</p>
<p>The remedy is a five-pillar lifecycle governance framework: transparency and explainability, accountability and liability, equity and non-discrimination, auditability and oversight, and human-in/on-the-loop control. Each pillar carries a five-level maturity scale from 0 to 4, anchored in concrete transport failure scenarios. On transparency, level 2 requires public model cards, disclosed geographic and linguistic training boundaries, and prompt-response logs retained for at least 90 days, while level 4 offers citizens a public API to query and appeal decisions. On accountability, level 2 demands a formally mapped decision authority chain, frozen third-party updates before validation, and insurance covering generative-AI failures. On human control, level 2 requires a real-time override usable within five seconds and logged in structured form.</p>
<p>The framework&#8217;s dependency lattice is where the argument becomes sharpest: transparency feeds auditability, which feeds accountability, which feeds human control, with equity feeding back into transparency as disparate-impact findings reveal which lineages must be disclosed. The ordering is causal, not decorative. A city that writes strong accountability contracts while publishing no model or data-lineage cards cannot enforce those contracts after an incident, because the audit trail needed to allocate responsibility does not exist. Similarly, operators pressing override controls cannot reconstruct outcomes if auditability is missing. The authors frame this as a ceiling effect rather than a temporal rule: upstream maturity is necessary but not sufficient, and out-of-order investment yields diminishing returns rather than certain failure.</p>
<p>What distinguishes the paper from most governance literature is its commitment to falsifiability. The authors propose twelve testable propositions linking pillar maturity to observable outcomes, including incident severity, mean-time-to-resolution, disparate-impact detection latency, override-exercise rate, deployment survival, and public trust. Candidate designs range from partial least squares structural equation modeling on transit-authority surveys, to difference-in-differences comparisons of matched incidents, to Cox proportional-hazards survival analysis on metropolitan pilots, to scenario-based rider surveys testing whether transparency builds trust indirectly through perceived contestability. All sample sizes are explicitly labeled as illustrative pending pilot power analysis, and the authors stress that no proposition counts as tested until its design is pre-registered.</p>
<p>For practice, the framework translates into a procurement-grade baseline of level 2 on all five pillars, written into generative-AI tenders as enforceable evaluation criteria. Agencies are advised to negotiate clauses requiring at least 24 hours notice of vendor-side model updates and prompt-log retention of at least 90 days. Vendors get design-phase boundaries, and regulators get a lifecycle conformity-assessment scaffold calibrated to generative drift timescales rather than annual cycles, with jurisdictions able to set minimum pillar levels vendors must demonstrate across all operating territories to prevent governance race-to-the-bottom. The authors caution that the framework is theoretically derived and not yet empirically validated, and that data-access friction, particularly undisclosed vendor prompt logs, will require partnerships with municipal authorities.</p>
<p>The validation path proceeds in three phases: pilot testing of the maturity matrix on three to five metropolitan planning organizations with inter-rater reliability targets, early empirical tests of four propositions using publicly available data, and comparative case studies of the cross-pillar predictions over six-to-eighteen-month operating windows. Whether the framework survives contact with real dispatch rooms, chatbot deployments, and signal-control centers will determine if generative AI in urban mobility gets the lifecycle scaffolding that, the authors argue, currently exists nowhere in the transport governance toolkit.</p>
<p><strong>Subject of Research:</strong> Governance of generative AI in urban mobility operations</p>
<p><strong>Article Title:</strong> Governing generative AI in urban mobility: a five-pillar framework and twelve falsifiable propositions for operations, accountability, and public trust</p>
<p><strong>Article References:</strong> Acharya, N., &amp; Kar, P. (2026). Governing generative AI in urban mobility: a five-pillar framework and twelve falsifiable propositions for operations, accountability, and public trust. <em>Frontiers in Future Transportation, 7</em>, Article 1951756. <a href="https://doi.org/10.3389/ffutr.2026.1951756" rel="noopener noreferrer">https://doi.org/10.3389/ffutr.2026.1951756</a></p>
<p><strong>Image Credits:</strong> AI Generated</p>
<p><strong>DOI:</strong> <a href="https://doi.org/10.3389/ffutr.2026.1951756" rel="noopener noreferrer">10.3389/ffutr.2026.1951756</a></p>
<p><strong>Keywords:</strong> generative AI, urban mobility, governance framework, transport policy, AI accountability, algorithmic auditing, public transit, foundation models, AI ethics, maturity model, human-in-the-loop, transport governance</p>
]]></content:encoded>
					
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">277478</post-id>	</item>
	</channel>
</rss>
