Read the exclusion this gateway holds for a contract
Reads the exclusion this gateway durably holds for one contract — the outcome of excluir-consignado-trabalhador (Manual 003 v1.19 §3.3). It is a LOCAL read: it never calls Dataprev and never starts a reconciliation pass, because the gateway’s own row already answers and an M003 operation with no undo does not justify spending the rail’s rate budget on the question.
404 means the gateway holds nothing for this contract. 409 means the contract holds a legacy authority row that cannot be reported — deliberately NOT a 404, because silence would read as “this contract was never excluded”.
Authorizations
JWT bearer token issued by the identity provider.
Path Parameters
The rail contract number whose exclusion is read.
2 - 15"NC-000001"
Response
The exclusion operation that describes the contract now.
The client's declared Manual 003 §3.3.1 reason, echoed from the durable authority.
1, 2, 3, 7, 8, 9 "1"
The contract number the exclusion was addressed to.
"NC-000001"
Durable operation status. confirmed means the contract came off the payroll; rejected means the registry published a refusal; claimed, invoking and outcome_unknown all mean the effect at the registry is NOT known yet and M005 reconciliation has to close it — none of the three is a failure to retry blindly.
claimed, invoking, confirmed, rejected, outcome_unknown "confirmed"
Which proof produced the terminal state: exclude_response, operator_evidence or m005_observation. Empty until one did.
"exclude_response"
The refusal message the REGISTRY published. Present only on a rejected operation.
"motivo nao publicado"
Instant the registry answered, RFC 3339 UTC. ABSENT until it did.
"2026-08-05T12:00:00Z"
The registry's own receipt for the mutation. ABSENT when it minted none, which is the normal case under an m005_observation confirmation — absence is never a verdict.
"HASH-1"
The refusal code the REGISTRY published. Present only on a rejected operation.
"ME"

