Skip to content

Main content

Exhibit Seal Version Match Flag Tool

Literal supplied seal/version consistency only, without authenticity or evidentiary conclusions.

Loading tool…

Description

Compare recorded and expected seal/version strings exactly and return separate flags plus their conjunction.

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.

Compare recorded and expected seal/version strings exactly and return separate flags plus their conjunction.

When to use this tool

Use Exhibit Seal Version Match Flag when you need a scoped evidence-record or quantity-reconciliation diagnostic.

How to use the tool and how it works

  1. Enter recordedSeal, recordedVersion, expectedSeal, expectedVersion. 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 sealMatches, versionMatches, matches. Inspect sealMatches, versionMatches, matches before interpreting the associated values.

Compare recorded and expected seal/version strings exactly and return separate flags plus their conjunction.1

Input fieldMeaning and unitsAccepted input
recordedSealRecorded SealRequired. Text; maximum UTF-16 length 8192.
recordedVersionRecorded VersionRequired. Text; maximum UTF-16 length 8192.
expectedSealExpected SealRequired. Text; maximum UTF-16 length 8192.
expectedVersionExpected VersionRequired. Text; maximum UTF-16 length 8192.
Output fieldInterpretationReturned shape
sealMatchesSeal MatchesRequired. Boolean.
versionMatchesVersion MatchesRequired. Boolean.
matchesMatchesRequired. Boolean.
json
{
  "input": {
    "recordedSeal": "S1",
    "recordedVersion": "v2",
    "expectedSeal": "S1",
    "expectedVersion": "v2"
  },
  "output": {
    "sealMatches": true,
    "versionMatches": true,
    "matches": true
  }
}

Limitations and assumptions

  • Literal metadata equality does not authenticate a seal, establish intact packaging, or verify chain of custody.
  • 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

  1. Calculation and input contract: forensic-science/exhibit-seal-version-match-flag — 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 ID Check Token

    Check token starts with their concatenation and return its remaining suffix, or empty text when unmatched.