Chain Of Custody Link Integrity Count Checker

Audit actual caller chronologically ordered custody transfer ledger for adjacent actor continuity, retaining unknown evidence. No timestamp authentication, admissibility, physical integrity or proof of misconduct.

Description

A chain-of-custody record links the receiver of one transfer to the sender of the next.

A chain-of-custody record links the receiver of one transfer to the sender of the next.^[1]

Continuity of submitted actor IDs does not establish authenticity or legal admissibility. Use this tool to calculate the stated observation or conditional model from supplied measurements.

When to use Chain Of Custody Link Integrity Count Checker

Use this tool to calculate the stated observation or conditional model from supplied measurements. Establish the jurisdiction or research scope, observation and event definitions, reference date, matched period and denominator basis.

How to use Chain Of Custody Link Integrity Count Checker and understand its results

Establish the jurisdiction or research scope, observation and event definitions, reference date, matched period and denominator basis.
Enter callerTransferIds, independentlyRecordedSenderIds, independentlyRecordedReceiverIds, transferEvidenceKnownFlags, using the field meanings and rules below, then run the tool.
Read result.brokenKnownLinkIndices, result.unknownAdjacentLinkIndices. Interpret each field using the units, signs and evidence rules below.
If input validation fails, correct the reported field and run again. Before applying a successful result, check the stated reference scope, units, assumptions and any retained unknown evidence.

Input field	Meaning	Value type	Requirement
callerTransferIds	Caller transfer ids	list of string	Required
independentlyRecordedSenderIds	Independently recorded sender ids	list of string	Required
independentlyRecordedReceiverIds	Independently recorded receiver ids	list of string	Required
transferEvidenceKnownFlags	Transfer evidence known flags; 1 means known and 0 means unknown; keep the same item order	list of number	Required

Supply nonempty unique nonblank transfer IDs with aligned nonblank sender/receiver IDs and binary evidence-known flags in the intended sequence. For each index i>0, compare sender[i] with receiver[i−1] only when both transfers are known. Return mismatching known indices and indices whose adjacent pair contains unknown evidence separately. Exact case-sensitive identity labels are used; no timestamp or first-link origin validation occurs.

brokenIndices={i>0:known_i=known_(i−1)=1 and sender_i≠receiver_(i−1)}; unknownAdjacentIndices={i>0:known_i=0 or known_(i−1)=0}

Apply the field units and exact ordering, boundary and evidence rules above.

Output field	Meaning	Value type
result	Structured result containing the calculation or selected reference fields below	object
result.brokenKnownLinkIndices	Zero-based transfer indices i>0 where known sender[i] differs from known receiver[i−1]	list of values
result.unknownAdjacentLinkIndices	Zero-based transfer indices i>0 where either adjacent transfer is unknown	list of values

json

{
  "input": {
    "callerTransferIds": [
      "t1",
      "t2",
      "t3"
    ],
    "independentlyRecordedSenderIds": [
      "a",
      "b",
      "c"
    ],
    "independentlyRecordedReceiverIds": [
      "b",
      "c",
      "d"
    ],
    "transferEvidenceKnownFlags": [
      1,
      1,
      1
    ]
  },
  "output": {
    "result": {
      "brokenKnownLinkIndices": [],
      "unknownAdjacentLinkIndices": []
    }
  }
}

Limitations and assumptions

Continuity of submitted actor IDs does not establish authenticity or legal admissibility. Results depend on the independently established measurement basis and the exact model assumptions above.

Every listed input requires an explicit value. Unexpected fields, incorrect value types, nonfinite numbers and sparse numeric arrays fail validation; tool-specific bounds and alignment rules apply as described above. Extremely large inputs or outputs can also be rejected. An input error is distinct from a successful calculation that reports a false comparison or retains unknown evidence.

Alternative or Complementary methods

Use GPS Monitoring Tamper Inclusion Zone Flag Checker to examine a related aspect: Tamper and zone-breach telemetry alerts require independent reliability review.

Use Evidence Room Audit Retention Cycle Lookup where its separate inputs and scope apply: Evidence retention and audit cycles depend on case status, evidence category and holds.

References

Chain Of Custody Link Integrity Count Checker — tool.io

Similar or alternative tools

GPS Monitoring Tamper Inclusion Zone Flag Checker
Tamper and zone-breach telemetry alerts require independent reliability review.
Evidence Room Audit Retention Cycle Lookup
Evidence retention and audit cycles depend on case status, evidence category and holds.