Evidence Package Seal Share Tool

Description

Count distinct packages, any sealed IDs and any IDs with a sealed-and-verified row; divide verified count by all, or flagged undefined zero.

Evidence records link identifiers, packaging, quantities and source assertions. Literal equality and balanced counts can reveal local inconsistencies, but they cannot authenticate physical evidence, establish custody completeness or determine legal admissibility.

Count distinct packages, any sealed IDs and any IDs with a sealed-and-verified row; divide verified count by all, or flagged undefined zero.

When to use this tool

Use Evidence Package Seal Share when you need a scoped evidence-record or quantity-reconciliation diagnostic.

How to use the tool and how it works

Enter packageIds, sealed, sealVerified. Keep parallel arrays aligned. Use the units and conventions below.
Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
Read packages, sealedPackages, verifiedSealedPackages, verifiedShare, defined. Inspect defined before interpreting the associated values.

Require aligned package IDs and sealed/verified flags. Count distinct packages, any sealed IDs and any IDs with a sealed-and-verified row; divide verified count by all, or flagged undefined zero.^[1]

Input field	Meaning and units	Accepted input
packageIds	Package Ids	Required. Array of text; maximum UTF-16 length 8192; maximum items 256.
sealed	Sealed	Required. Array of boolean; maximum items 256.
sealVerified	Seal Verified	Required. Array of boolean; maximum items 256.

Output field	Interpretation	Returned shape
packages	Packages	Required. Safe integer.
sealedPackages	Sealed Packages	Required. Safe integer.
verifiedSealedPackages	Verified Sealed Packages	Required. Safe integer.
verifiedShare	Verified Share	Required. Finite number.
defined	Whether the stated denominator or normalization exists; inspect before interpreting a zero placeholder.	Required. Boolean.

json

{
  "input": {
    "packageIds": [
      "a",
      "a",
      "b"
    ],
    "sealed": [
      true,
      false,
      true
    ],
    "sealVerified": [
      true,
      false,
      false
    ]
  },
  "output": {
    "packages": 2,
    "sealedPackages": 2,
    "verifiedSealedPackages": 1,
    "verifiedShare": 0.5,
    "defined": true
  }
}

Limitations and assumptions

Any matching duplicate row supports that package. Flags are supplied rather than independently checked and no physical seal or custody authenticity 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.

Alternative or Complementary methods

Review authenticated source records and the complete custody process through the appropriate professional procedure. Treat local flags as prompts for investigation rather than independent evidentiary conclusions.

References

Calculation and input contract: forensic-science/evidence-package-seal-share — tool.io

Similar or alternative tools

Exhibit Bag Seal ID Pair
Compare literally or after JavaScript lowercasing according to caseSensitive, and return individual flags and their conjunction.
Exhibit Seal Version Match Flag
Compare recorded and expected seal/version strings exactly and return separate flags plus their conjunction.