tournament_position
Where a declared score sits against declared cut points, and how far the FIELD would have to move to cross each one with that score held still. Route here whenever a rating, a star, a band or a tier is being read as a standard. It is not one. Cut points set from the year's own distribution move with the distribution, so a plan can improve absolutely and lose a star because the field improved more, and that sentence is what this tool makes computable in the caller's own numbers. Declare `score`, the score you are placing; `cut_points`, the band boundaries you are reasoning against, strictly ascending; and `field`, the scores of the plans you are counting as the field. All three are required and this world ships no default for any of them. Cut points that do not ascend are refused rather than sorted, because the order you typed is how the bands were read and reordering silently would change which band your score lands in without saying so. THE FIGURE THAT MATTERS IS THE FIELD SHIFT, NOT THE DISTANCE. The distance to the next cut is what everybody already has. Beside it, for every cut, sits the shift in the whole field that crosses that cut with your score unchanged: a cut above you is crossed by the field falling, and a cut already below you is lost when the field rises, and the sign says which. The arithmetic behind it is stated on the payload rather than buried, because it is an assumption and not a fact: a cut defined as a percentile of the field moves one for one with a uniform shift of the field, which makes the shift the gap between your score and the cut, and CMS sets Medicare Advantage star cut points by clustering rather than by percentile, so read these as the order of movement rather than as a threshold. The field is the field you declared, whatever set of scores you typed, which need not be every plan and need not include your own. Every figure carries a basis of assumption, because you declared all of it. THIS YEAR'S ACTUAL CUT POINTS ARE NOT HELD, AND THE REASON IS PRECISE. They are CMS's. The source register carries the Medicare Advantage star ratings source with a state of available and a table state of raw_only: fetched and staged upstream, never opened, never converted, never validated, never read by anything here. That is a different fact from missing, and it is a conversion task upstream rather than a decision not to ship, so an argument asking this world to use the actual cut points is refused with that distinction intact rather than told the source is absent. NEXT YEAR'S CUT POINT IS A FORECAST OF EVERY OTHER PLAN'S BEHAVIOUR, and is refused as one. A cut set from the year's distribution is made out of what every other plan does: how many improve, by how much, and how the ones you have never heard of move. This world observes no plan's behaviour and holds no history of the distribution. AND A POSITION IS NEVER A SUM OF MONEY. What a band is worth turns on enrolment, on the benchmark and rebate rules that apply to that contract, and on which members are in it, and this world publishes that it cannot state a saving for a named payer's own book. An argument naming an enrolment, a premium or a bonus is refused by name. There is no field on the payload a forecast or a sum of money could be written into, and that absence is the design: a payload offering a slot for a figure gets a figure written into it.
Use this form for new arguments. Follow concrete links for known values. Fetch-only readers may be unable to submit new URLs.
Exact input contract
{
"additionalProperties": false,
"properties": {
"cut_points": {
"description": "The band boundaries to reason against, strictly ascending, in the same units as the score. Required; this world holds none of its own, and an argument asking it to supply the actual ones is refused with the register's state named. Boundaries that do not ascend, a repeated boundary included, are refused rather than sorted.",
"items": {
"type": "number"
},
"minItems": 1,
"type": "array"
},
"field": {
"description": "The scores of the plans you are counting as the field, in the same units as the score. Required. This is your declared field, which need not be every plan and need not include your own, and the payload says so beside every figure read off it.",
"items": {
"type": "number"
},
"minItems": 1,
"type": "array"
},
"score": {
"description": "The score being placed, in whatever units the cut points and the field are in. Required; this world ships no default and holds no plan's score of its own.",
"type": "number"
}
},
"required": [
"score",
"cut_points",
"field"
],
"type": "object"
}