Description
Evaluate a supplied expiry boundary only when the caller asserts comparable clocks.
A policy scenario makes eligibility bases, rates, thresholds, periods, and costs explicit. A calculated share or balance follows those assumptions. It does not select the governing policy or establish what caused an observed program outcome.
Evaluate a supplied expiry boundary only when the caller asserts comparable clocks.
When to use this tool
Use it for voucher expiry supplied clock token when the required inputs and conventions are already available.
How to use the tool and how it works
- Enter queryTime, expiryTime, includeExpiry, clockKnown. Use the stated units and boundary conventions.
- Run the calculation. Correct any input error before interpreting a result.
- Read known, usableUnderClock. Inspect any known, defined, inclusion, or boundary flags before interpreting numeric values.
Return known=clockKnown. Set usableUnderClock only when the clock is known and queryTime is before expiryTime, admitting equality only when includeExpiry is true.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| queryTime | Query Time | Required. Finite number. |
| expiryTime | Expiry Time | Required. Finite number. |
| includeExpiry | Include Expiry | Required. Boolean. |
| clockKnown | Clock Known | Required. Boolean. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| known | Whether the supplied token or clock is known under the stated rule. | Required. Boolean. |
| usableUnderClock | Usable Under Clock | Required. Boolean. |
{
"input": {
"queryTime": 100,
"expiryTime": 100,
"includeExpiry": false,
"clockKnown": true
},
"output": {
"known": true,
"usableUnderClock": false
}
}Limitations and assumptions
- An unknown clock always yields usableUnderClock false without asserting actual expiry. This checks only a supplied expiry clock, not issuance, eligibility, redemption history, or voucher rights.
- The field tables describe structural bounds; the mechanics also state cross-field requirements. Malformed input shapes, disallowed keys, and invalid domains cause input errors. Results must remain finite and within the declared output contract. A successful false flag or zero placeholder is distinct from an error.
- Numeric arithmetic uses binary floating point. Exact comparisons have no hidden tolerance or decimal rounding; negative zero is exported as zero. Decimal-text integer operations retain the exactness specifically stated above.
Alternative or Complementary methods
For voucher expiry supplied clock token, check the source records and the supplied rule before comparing the result with another method. Consult the applicable authoritative rule when deciding eligibility, legal timing, fees, or obligations.
References
Similar or alternative tools
- Voucher Copayment Per Use Term
Calculate voucher copayment per use term from explicit caller-supplied inputs.
- Benefit Cliff Discrete Income Gap
Calculate benefit cliff discrete income gap from explicit caller-supplied inputs.