A Gate project is not a working submission path.

The eFTI4EU project reports 29 defined scenarios, user acceptance testing and end-to-end exchange with selected port authorities. No live shipments were used: data were generated from examples and real freight documents, and carriers were simulated. Cross-border live shipment and production acceptance remain NOT VERIFIED; our adapter is NOT PRODUCTION TESTED.

Evidence labels are independent, scope-specific observations, not an official maturity scale or automatic progression: specification, component, synthetic end-to-end, authority UAT, real shipment, cross-border live shipment and production. Machine-readable case ↗

Track separate milestones: specification → emulator → lab interoperability → real-environment authority pilot → verified roadside inspection → cross-border pilot → commercial onboarding → production. These are evidence labels for a defined country, mode, authority interface and platform—not a universal score or automatic progression. Portugal’s IMT pilot reached a real-environment test with GNR and Luís Simões; the public report does not explicitly verify a roadside vehicle stop. The project architecture names a Gate prototype and platform emulator. No public commercial-onboarding or production-acceptance claim follows from those facts.

Current PL/PT test observations: authority-inspection-readiness.json ↗.

A proposed simulation pack would exercise UID/QR presentation, authority access, dataset retrieval, timeout, audit trail and a reviewed fallback. Scenarios include no GSM, Gate unavailable, driver device unavailable and platform failure. TLP requests official Polish procedures for such incidents; we have not verified a government response. The site therefore does not prescribe a lawful roadside workaround, guarantee inspector acceptance or retry an authority submission.

The Croatian NSCP reports national technical readiness and describes its eFTI Portal, AAP and registries. That does not by itself establish public developer documentation, onboarding, a sandbox, an interoperability test, a certified platform connection or production acceptance for a commercial vendor. Each step remains NOT_VERIFIED until separately sourced.

Two-axis record: gate-capability-registry.json ↗. Our adapter: NOT_PRODUCTION_TESTED.

Belgium’s official erratum (TED 661742-2026) replaces an “as a service” delivery with a system running on the SPF Mobilité et Transports platform. That is procurement evidence for a proposed authority-platform deployment, not proof of the eventual host, cloud location, data residency, operator, identity boundary or security controls.

Machine-readable profile: gate-deployment-profiles.json ↗. Unpublished fields stay UNKNOWN pending awarded technical documentation and tests.

The Belgium tender supports a procurement-stage label only. It does not establish a sandbox, tested interface or production availability. This site does not poll authority feeds; a future monitored record needs a primary source, update cadence and incident handling.