Skip to content

Main content

Protective Inventory Transfer Credit Tool

Reconcile generic protective inventory transfers with supplied duplicate-receipt counts.

Loading tool…

Description

Reconcile protective inventory transfer counts.

Biosecurity administration records training assertions, custody, access purposes, inventories and document handling. Local counts, time checks and permission predicates describe supplied metadata; they do not authenticate people or items, enforce access or establish actual protective conditions.

Reconcile protective inventory transfer counts.

When to use this tool

Use Protective Inventory Transfer Credit when checking the stated benign biosecurity record, inventory, support or authorization convention.

How to use the tool and how it works

  1. Enter starting, sent, received, duplicatedReceipt. 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 ending, netTransfer. Use the output convention below.

Reconcile protective inventory transfer counts. Require nonnegative whole starting/received, sent <= starting and duplicatedReceipt <= received; ending = starting-sent+received-duplicate via exact intermediates, netTransfer = received-duplicate-sent.1

Input fieldMeaning and unitsAccepted input
startingStartingRequired. Safe integer; minimum 0.
sentSentRequired. Safe integer; minimum 0.
receivedReceivedRequired. Safe integer; minimum 0.
duplicatedReceiptDuplicated ReceiptRequired. Safe integer; minimum 0.
Output fieldInterpretationReturned shape
endingEndingRequired. Safe integer.
netTransferNet TransferRequired. Safe integer.
json
{
  "input": {
    "starting": 100,
    "sent": 20,
    "received": 30,
    "duplicatedReceipt": 5
  },
  "output": {
    "ending": 105,
    "netTransfer": 5
  }
}

Limitations and assumptions

  • Outputs must fit numeric contracts; no actual custody, equipment suitability or physical stock is verified.
  • 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

Verify actual records, permissions and conditions through the responsible organization's procedures; use qualified risk assessment and appropriate professional oversight for practical decisions.

References

  1. Calculation and input contract: biosecurity/protective-inventory-transfer-credit — tool.io

Similar or alternative tools