Skip to content

Main content

Proportional Burden Cap One Party Tool

Calculate proportional burden cap one party from explicit caller-supplied inputs.

Loading tool…

Description

Return proportional share, capped allocation and excess.

Allocation models distribute resources, burdens or compensation using explicit weights and reference values. Arithmetic transparency can expose assumptions, but a proportional share or restored balance does not establish fairness, entitlement or responsibility.

Return proportional share, capped allocation and excess.

When to use this tool

Use Proportional Burden Cap One Party when you need one stated allocation, burden or compensation term.

How to use the tool and how it works

  1. Enter totalBurden, weight, totalWeight, cap. Use the units and conventions below.
  2. Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
  3. Read uncapped, allocated, excess. Use the output convention below.

Require nonnegative totalBurden, weight and cap with positive totalWeight and weight no greater than total. Return proportional share, capped allocation and excess.1

Input fieldMeaning and unitsAccepted input
totalBurdenTotal BurdenRequired. Finite number; minimum 0.
weightWeightRequired. Finite number; minimum 0.
totalWeightTotal WeightRequired. Finite number; strictly above 0.
capCapRequired. Finite number; minimum 0.
Output fieldInterpretationReturned shape
uncappedUncappedRequired. Finite number.
allocatedAllocatedRequired. Finite number.
excessExcessRequired. Finite number.
json
{
  "input": {
    "totalBurden": 100,
    "weight": 3,
    "totalWeight": 10,
    "cap": 25
  },
  "output": {
    "uncapped": 30,
    "allocated": 25,
    "excess": 5
  }
}

Limitations and assumptions

  • Only one party is modeled and excess is not redistributed. Weights and caps are supplied, without determining a just burden or legal obligation.
  • Inputs must satisfy both the field types and the cross-field conditions above. Invalid input causes an error; a successful false flag or documented placeholder is a different result.
  • Numeric calculations use binary floating point unless exact decimal-integer arithmetic is explicitly stated. No hidden measurement tolerance or decimal rounding is added; nonfinite or out-of-contract results are rejected. Numeric signed-zero results are exported as zero.

Alternative or Complementary methods

Review the underlying needs, rights, valuation and distribution process. Consider the complete allocation and affected parties rather than inferring justice from one calculated share.

References

  1. Calculation and input contract: ethics/proportional-burden-cap-one-party — tool.io

Similar or alternative tools