Do not turn evidence-exchange readiness into OOTS access eligibility
Keep Ukraine's readiness testing separate from the current legal connection scope and the citizen's service outcome.
Convenience and eligibility are different
Direct exchange of official evidence can reduce repeated document requests. Describing a readiness test as a service already available to everyone would create a different burden. Truthound can check states and authority references in a preparation table; it cannot grant connection eligibility or authenticate a certificate.
The Finland–Ukraine preparation
The EU's October 7, 2026 OOTS account describes Finland's KEHA Centre preparing interoperability tests and expertise exchange with Ukraine during autumn. It also distinguishes the existing legal framework, under which full connection is limited to EU and EEA countries. Preparation is not the same stage as formal connection.
Do not make an evidence state a citizen failure
An illustrative fixture should include evidence type, issuing authority, requesting authority, observation state and readiness stage. Evidence not found must not automatically mean the individual lacks entitlement. An incomplete authority connection, unobserved data and a procedure outside scope need different states.
Two boundaries in the authority map
Keep a technical endpoint separate from the authority entitled to handle the procedure. Merging similar institution names or replacing an operating address with a test endpoint can promote a preparation result into apparent approval. Preserve the evidence and owner of each mapping.
The inputs Truthound can check
Truthound Core Python SDK 3.3.4, operating on a prepared Polars table, provides InSetValidator for supplied allowed states and ForeignKeyValidator for caller-provided child and parent tables and keys. The responsible owner supplies the authority register and scope. These are table-validation interfaces, not substitutes for OOTS transport or authorisation processes.
Keep the useful join
An existing pandas 3.1.1 merge(validate=...) can retain 1:1 or 1:m key checks. Join cardinality and an authority's eligibility for a particular procedure are different questions. Keep the useful join while making authorised-reference membership and state review explicit. Because pandas can match null keys, an unidentified test record must not appear linked to an eligible authority.
What a successful fixture does not mean
A successfully linked illustrative evidence row does not authorise access to a citizen's actual record. Preserve the test input, operating environment and legal scope so a later owner cannot read a fixture result as general approval. Revisit access conditions when the workflow begins handling real evidence.
Return exceptions to a responsible owner
An exception should not end automatically in another document request to the citizen. Make the unfinished authority mapping or definition visible to its owner, and let the service responsible for the procedure explain an available alternative. A failed data contract should not silently become an individual's fault.
Communicate readiness precisely
The useful output distinguishes ready, awaiting confirmation and currently outside scope. Update the evidence when technical preparation advances. This keeps the aim of reducing user burden connected to an accurate account of the service that can actually be offered.
Conditions
Confirm authority and legal scope before using personal data; use appropriate illustrative records for readiness tests.
Alternatives
Keep pandas 3.1.1 join-cardinality checks for authority mappings while assessing their authorised scope separately.
Limitations
A table check does not grant OOTS access or establish the authenticity of an official certificate.
Evidence
- Event checked
- Subject checked
- Modified
