Description
Calculate protective stock reserve fraction from explicit caller-supplied inputs.
Security records often depend on explicit counts, clock origins, status flags, and provenance dates. Checking their internal arithmetic can reveal a bookkeeping gap while leaving the underlying evidence and operational decisions for separate review.
Calculate protective stock reserve fraction from explicit caller-supplied inputs.
When to use this tool
Use it for protective stock reserve fraction when the required inputs and conventions are already available.
How to use the tool and how it works
- Enter physical, reserved, quarantined, sharedExclusion. Use the stated units and boundary conventions.
- Run the calculation. Correct any input error before interpreting a result.
- Read available, reservedFraction. Inspect any known, defined, inclusion, or boundary flags before interpreting numeric values.
Calculate available = physical-reserved-quarantined+sharedExclusion and reservedFraction = reserved/physical. Validate safe integer counts, a positive physical base, and a feasible overlap between reserved and quarantined sets.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| physical | Physical | Required. Safe integer; minimum 1. |
| reserved | Reserved | Required. Safe integer; minimum 0. |
| quarantined | Quarantined | Required. Safe integer; minimum 0. |
| sharedExclusion | Shared Exclusion | Required. Safe integer; minimum 0. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| available | Available | Required. Safe integer. |
| reservedFraction | Reserved Fraction | Required. Finite number. |
{
"input": {
"physical": 100,
"reserved": 20,
"quarantined": 10,
"sharedExclusion": 5
},
"output": {
"available": 75,
"reservedFraction": 0.2
}
}Limitations and assumptions
- The overlap count is supplied rather than inferred from item identities. Reserved fraction uses the full physical base and does not equal unavailable fraction when quarantine or overlap is present.
- 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 protective stock reserve fraction, check the source records and the supplied rule before comparing the result with another method. Use a separate evidence or method review when arithmetic consistency alone cannot establish the required conclusion.
References
Similar or alternative tools
- Protective Stock Unit Balance
Balance explicitly supplied protective-supply records and packaging units; no operational security planning.
- Protective Asset Review Slack
Compare explicit protective asset record review times without security assessment.