Skip to content

Main content

Reinforcement Earned Token Balance

Reconcile supplied reinforcement token counts without selecting or evaluating an intervention.

Loading tool…

Description

Update a supplied earned-and-redeemed reinforcement-token balance.

Behavioral records distinguish observed outcomes, missing observations, response deadlines, code conflicts and sampling opportunities. Unobserved trials differ from observed wrong responses, while time coverage differs from event probability. Supplied observations and cutoff values do not by themselves validate a task or identify a behavioral mechanism.

Update a supplied earned-and-redeemed reinforcement-token balance.

When to use this tool

Use Reinforcement Earned Token Balance when you already have openingTokens, earnedTokens, redeemedTokens and need to update a supplied earned-and-redeemed reinforcement-token balance.

How to use the tool and how it works

  1. Enter openingTokens, earnedTokens, redeemedTokens. 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 closingBalance. Use the output convention below.

Require nonnegative safe whole opening, earned and redeemed counts; add/subtract exactly with BigInt and export a safe numeric closing balance.1

Input fieldMeaning and unitsAccepted input
openingTokensOpening TokensRequired. Safe integer; minimum 0.
earnedTokensEarned TokensRequired. Safe integer; minimum 0.
redeemedTokensRedeemed TokensRequired. Safe integer; minimum 0.
Output fieldInterpretationReturned shape
closingBalanceExact opening+earned-redeemed integer balance, exported only when safe; negative discrepancies retained.Required. Safe integer.
json
{
  "input": {
    "openingTokens": 20,
    "earnedTokens": 8,
    "redeemedTokens": 5
  },
  "output": {
    "closingBalance": 23
  }
}

Limitations and assumptions

  • Negative discrepancies are retained. No entitlement, actual delivery, reinforcement effectiveness or appropriate intervention is established.
  • 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

Use the complete protocol, observation records and analysis plan. Check missingness, coding rules, timing and sampling design before interpreting local counts, labels or interval fractions as research outcomes or appropriate interventions.

References

  1. Calculation and input contract: behavioral-science/reinforcement-earned-token-balance — tool.io

Similar or alternative tools