Skip to content

Main content

Statutory Cap Component Inclusion Tool

Apply supplied component-inclusion flags and a supplied cap; no statutory classification is inferred.

Loading tool…

Description

Apply supplied component-inclusion flags and a supplied cap; no statutory classification is inferred.

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.

Apply supplied component-inclusion flags and a supplied cap; no statutory classification is inferred.

When to use this tool

Use it for statutory cap component inclusion when the required inputs and conventions are already available.

How to use the tool and how it works

  1. Enter components, included, suppliedCap. Keep parallel arrays aligned and use the stated units and conventions.
  2. Run the calculation. Correct any input error before interpreting a result.
  3. Read includedTotal, excess. Inspect any known, defined, inclusion, or boundary flags before interpreting numeric values.

Require aligned nonnegative components and included flags and nonnegative suppliedCap. Sum only included components and return excess=max(0,includedTotal-suppliedCap).1

Input fieldMeaning and unitsAccepted input
componentsComponentsRequired. Array of Finite number.; maximum items 256.
includedIncludedRequired. Array of Boolean.; maximum items 256.
suppliedCapSupplied CapRequired. Finite number; minimum 0.
Output fieldInterpretationReturned shape
includedTotalIncluded TotalRequired. Finite number.
excessExcessRequired. Finite number.
json
{
  "input": {
    "components": [
      20,
      40,
      30
    ],
    "included": [
      true,
      false,
      true
    ],
    "suppliedCap": 40
  },
  "output": {
    "includedTotal": 50,
    "excess": 10
  }
}

Limitations and assumptions

  • Excluded components remain outside the base. The tool does not choose legally includable components, reduce any individual payment, or determine an actual statutory cap.
  • 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 statutory cap component inclusion, 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

  1. Calculation and input contract: public-policy/statutory-cap-component-inclusion — tool.io

Similar or alternative tools