Where: /app/aims/transparency

Article 50 duties attach to system characteristics: interacting with humans, generating synthetic content, emotion recognition, biometric categorisation, deepfakes.

Probe in this order — characteristics, then measure, then evidence

1. Does the system have the characteristic that triggers the duty?
2. Is a measure recorded against it?
3. Does the referenced evidence exist, and does it show what the row claims?

The register records; an auditor verifies the referenced evidence, not the row. A measure marked implemented with nothing behind it is exactly the false assurance worth finding.

What you should be able to see

Duties overdue against their statutory deadline, visible as overdue rather than merely open. Also test any claimed exemption: an exemption asserted without a recorded basis is a finding.

Determinations are refused to you

Recording a measure as evidenced, or claiming an exemption, are compliance determinations. Your account is refused them by design — unlike Article 73, where raising an incident is a factual act you may perform.