Skip to content

Main content

Biosecurity Authorized Access Expiry Gap Tool

Audit explicit authorization dates and revocation flags without granting access.

Loading tool…

Description

Return access-window and remaining-validity predicates.

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.

Return access-window and remaining-validity predicates.

When to use this tool

Use Biosecurity Authorized Access Expiry Gap when checking the stated benign biosecurity record, inventory, support or authorization convention.

How to use the tool and how it works

  1. Enter observationDay, startDay, expiryDay, requiredRemaining, revoked. 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 insideWindow, remainingDays, marginDays, matchesUnderFlags. Inspect insideWindow, matchesUnderFlags before interpreting the associated values.

Return access-window and remaining-validity predicates. Require expiryDay >= startDay and nonnegative whole requiredRemaining; insideWindow includes both ends, remainingDays = expiry-observation, margin subtracts required; matchesUnderFlags also requires observation >= start and not revoked.1

Input fieldMeaning and unitsAccepted input
observationDayObservation DayRequired. Safe integer.
startDayStart DayRequired. Safe integer.
expiryDayExpiry DayRequired. Safe integer.
requiredRemainingRequired RemainingRequired. Safe integer; minimum 0.
revokedRevokedRequired. Boolean.
Output fieldInterpretationReturned shape
insideWindowInside WindowRequired. Boolean.
remainingDaysRemaining DaysRequired. Safe integer.
marginDaysMargin DaysRequired. Safe integer.
matchesUnderFlagsSupplied closed window, not revoked, and enough remaining days; both window endpoints are included and no real access is authorized.Required. Boolean.
json
{
  "input": {
    "observationDay": 110,
    "startDay": 100,
    "expiryDay": 130,
    "requiredRemaining": 10,
    "revoked": false
  },
  "output": {
    "insideWindow": true,
    "remainingDays": 20,
    "marginDays": 10,
    "matchesUnderFlags": true
  }
}

Limitations and assumptions

  • No actual access is granted; the supplied identity/scope, expiry and revocation assertions are not 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-authorized-access-expiry-gap — tool.io

Similar or alternative tools