ACCORD 23 — Trusted Autonomous Mobility
Working demonstrator and proposal for Villanova AI + TIM
14 October 2026

We have built a first demonstrator around a simulated Cagliari airport transfer,
using the already installed public Villanova 2B model for actual retrospective
AI analysis. The browser replays three recorded AI outputs alongside synthetic
vehicle and network events. A local encrypted journal, a 32-byte commitment and
an Ed25519 signature can be checked, including rejection of an altered copy.

The scenarios are normal delivery, edge handover and a communication interruption.
AI does not control driving. The scripted safe stop is a simulation, not evidence
of Level 4 capability. TIM connectivity and vehicle integration are proposed;
there is no live TIM endpoint or vehicle in this version. New ACCORD 23 commitments
have not yet been submitted to the NEO rail. ACCORD 22's existing witness proofs
are not reused as proof of these new journeys.

VILLANOVA — WHAT WE NEED
1. Mobility integration technical owner.
2. Working VPN / SSH cluster access, Slurm partition, allocation and container guidance.
3. Agree a useful model task and evaluation cases: incident summaries, event
   classification, or analysis of outputs from a vehicle simulator.
4. Confirm which model and runtime should run on the offered GPU infrastructure.

TIM — WHAT WE NEED
1. A technical owner and 5G/edge test environment, or an anonymised event trace first.
2. Message/session IDs, send/receive timestamps, clock source and uncertainty,
   edge IDs, delivery results, handover and interruption events.
3. A lab window for normal delivery, edge handover and an intentionally delayed message.
4. Agree event ownership, permitted retention and evidence-sharing boundaries.

COTRUGLI — WHAT WE BRING NEXT
Correlate simulator, AI and network events through an owner-side adapter. Keep
confidential payloads with their owners and submit only the 32-byte binary
commitment through the existing NeoFX/edge route, without changing the rail.
Obtain and verify a fresh rail receipt for each selected test journal. JSON stays
in the application layer, never enters the rail. NEO Chamber is the proposed
route for agreed evidence acceptance and dispute review, not an automated verdict.

JOINT SUCCESS CRITERIA
A reproducible run with one real TIM telemetry source and real Villanova inference;
traceable source IDs and timestamps; explicit clock uncertainty; verified fresh
rail receipts; altered evidence rejected; duplicate/reordered/missing events
reported separately from cryptographic integrity. No claim of L4 certification.

A physical vehicle can follow later through the same event interface. The first
joint lab version needs a simulator, not a road deployment.