Skip to content

Main content

Biosecurity Inventory Custody Handover Lag Tool

Calculate biosecurity inventory custody handover lag from explicit caller-supplied inputs.

Loading tool…

Description

Compare custody handover lag after two clock corrections.

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.

Compare custody handover lag after two clock corrections.

When to use this tool

Use Biosecurity Inventory Custody Handover Lag when checking the stated benign biosecurity record, inventory, support or authorization convention.

How to use the tool and how it works

  1. Enter releasedAt, acceptedAt, suppliedLimit, senderOffset, receiverOffset. 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 rawLag, correctedLag, withinLimit. Inspect withinLimit before interpreting the associated values.

Compare custody handover lag after two clock corrections. Require suppliedLimit >= 0 and corrected acceptance >= corrected release; rawLag = accepted-released, correctedLag = accepted-receiverOffset-released+senderOffset, withinLimit includes equality.1

Input fieldMeaning and unitsAccepted input
releasedAtReleased AtRequired. Finite number.
acceptedAtAccepted AtRequired. Finite number.
suppliedLimitSupplied LimitRequired. Finite number; minimum 0.
senderOffsetSender OffsetRequired. Finite number.
receiverOffsetReceiver OffsetRequired. Finite number.
Output fieldInterpretationReturned shape
rawLagRaw LagRequired. Finite number.
correctedLag(acceptedAt-receiverOffset)-(releasedAt-senderOffset); must be nonnegative though rawLag may be negative.Required. Finite number.
withinLimitWithin LimitRequired. Boolean.
json
{
  "input": {
    "releasedAt": 100,
    "acceptedAt": 110,
    "suppliedLimit": 12,
    "senderOffset": 1,
    "receiverOffset": -1
  },
  "output": {
    "rawLag": 10,
    "correctedLag": 12,
    "withinLimit": true
  }
}

Limitations and assumptions

  • Clock offsets and custody events are assertions; no actual chain of custody, identity or safe transfer 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/biosecurity-inventory-custody-handover-lag — tool.io

Similar or alternative tools