rooster
Judge Refinement
Settle one refinement: kept, rolled back, or not yet.
TAKES NO NUMBERS FROM THE CALLER. The after-rate is measured here, over exactly the window that starts when the refinement was applied, and the verdict is reached by refinement.judge. A worker that reported its own before/after could report flattering ones, and the entire value of this ledger is that the comparison can be trusted -- so the only thing the watch pass gets to do is ask.
"Not yet" comes back as a normal body with settled: false. A young refinement having too little fresh evidence is the expected case, not a fault.
post/api/rooster/refine/judge/{refinement_id}
Request
- Base URL: https://api.pigeonly.com (the document declares no server; this is the origin it was published from)
- URL: https://api.pigeonly.com/api/rooster/refine/judge/{refinement_id}
- Auth: none declared
Path parameters
refinement_idstring uuid required
Response
Successful Response
object required
Changes
No recorded changes to this operation across all 1 revision of this API.