Returns the evidence status of every integration mechanism in this release: what ANKATech has exercised against the real external system, how, and what stands in the way of the rest.

Each row carries four independent facts, and their independence is the point. A mechanism can be CERTIFIED, reached by a MANUAL probe, and still IAM_GRANT-blocked from automation — three simultaneously true statements that a single ranking could not express. selectable is COMPOSED by the server from the level AND, for a key-protection mechanism, this deployment's grant of the EXPERIMENTAL mechanisms it offers today — so the same release answers differently on two deployments, and an operator's edit takes effect on the next call with no restart. That deployment half is carried only to a caller already holding key-protection authority; every other caller receives the level's own answer for those rows, which is identical on every deployment. A client filters on this flag either way and never compares level itself.

This is not a connection test. It states whether ANKATech has ever exercised a mechanism, not whether your configured endpoint is reachable right now. The two are independent, and an EXPERIMENTAL mechanism whose connection test passes is a correct state.

Non-selectable rows are returned rather than filtered: the server states the status and the caller decides what to render, so a picker and a documentation consumer read the same response.

No tenant dimension: the response never varies by tenant, and two callers holding the same authority receive the same bytes. The evidence axes are release-fixed, so contentSha256 identifies the RELEASE; selectable is composed per DEPLOYMENT and is the one field two deployments reporting that same digest can disagree on — and the one field a caller without key-protection authority is answered from the release rather than from this deployment.