The legal path behind one obligation, not only the outcome
explain_applicabilityUse this whenever you have to justify why an obligation does or does not bear on a case, and an outcome on its own is not enough. It returns the legal path: the conditions under which the rule is about a situation, the exceptions under which it is not despite those conditions, and the statements of the obligation split by kind, each with the primary source, the locator inside that source and the source record behind it. Supply a profile as well and the deterministic rule trace is added: which rule was met, not met or unknown for this case, plus the assumptions and the questions the engine could not settle. Use this rather than paraphrasing an obligation yourself: the conditions, the exceptions and the citations are published data and are not to be reconstructed from prose.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| lang | No | Language of the labels and explanations. Dutch is the default. | nl |
| detail | No | Amount of data to return. brief keeps the outcome, the dates, the reasons, the open questions and the source with its locator; full adds the complete objects, every statement text and every hash, for re-computation or archiving. | brief |
| profile | No | The same coded profile that classify_system takes, with the same fields and codes: see the profile schema of classify_system. Send a version 2 profile to have the wider set assessed, including Article 26 for a deployer. The server validates the profile against that full schema. | |
| known_at | No | Knowledge time pin, a date or an ISO instant. Defaults to the release default. | |
| effective_at | No | Legal time pin, a date or an ISO instant. Defaults to the release default. | |
| obligation_id | Yes | The stable identifier, for example praxikon:eu:ai-act:obligation:article-50-transparency. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| pin | No | The release and the two time axes this answer resolved against. Store it next to anything you keep: an unpinned query is not reproducible, because the defaults move with each release. | |
| view | No | ||
| caveats | No | ||
| sources | Yes | ||
| assessment | Yes | Present only when a profile was supplied and the decision engine assessed this obligation for it. Null otherwise, with the reason in assessment_absent_reason and, when the engine said why, the detail in not_assessed. | |
| legal_path | Yes | ||
| obligation | Yes | ||
| provenance | Yes | Which published endpoints produced this result. Every call is listed with its full URL, so a reader can re-issue it and check the answer rather than trust it. | |
| not_assessed | No | Why the engine did not assess this obligation for this profile, as the engine reported it, with the facts that would have it assessed. For example profile_version_below_2: send a version 2 profile. | |
| assessment_absent_reason | No |