Skip to content

Main content

Public Case Suffix Sequence Gap Tool

Audit a bounded supplied public case-suffix sequence without accessing case records.

Loading tool…

Description

Find missing and duplicate public-case suffix numbers.

Case and statute records use identifiers, stages, time coordinates and supplied procedural assumptions. A literal comparison, count or charge calculation can help reconcile records, while actual rights, deadlines, evidence and duties depend on the applicable jurisdiction and authoritative documents.

Find missing and duplicate public-case suffix numbers.

When to use this tool

Use Public Case Suffix Sequence Gap when checking the stated legal-record, timing or fee convention.

How to use the tool and how it works

  1. Enter observed, expectedStart. 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 missing, duplicates. Use the output convention below.

Find missing and duplicate public-case suffix numbers. Require a nonempty numeric sequence at/above whole expectedStart and maximum-start <= 255; enumerate absent integer suffixes through the maximum and distinct duplicates.1

Input fieldMeaning and unitsAccepted input
observedSupplied suffix values; missing integers are enumerated only through the maximum observed value.Required. Array of safe integer; maximum items 256.
expectedStartExpected StartRequired. Safe integer; minimum 0.
Output fieldInterpretationReturned shape
missingMissingRequired. Array of safe integer; maximum items 256.
duplicatesDuplicatesRequired. Array of safe integer; maximum items 256.
json
{
  "input": {
    "observed": [
      1,
      2,
      4,
      4
    ],
    "expectedStart": 1
  },
  "output": {
    "missing": [
      3
    ],
    "duplicates": [
      4
    ]
  }
}

Limitations and assumptions

  • No missing suffix beyond the observed maximum is inferred; supplied labels do not establish actual missing cases.
  • 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

Consult the actual case records, governing rules and qualified legal advice for legal conclusions; use an appropriate calendar and complete document workflow for real deadlines.

References

  1. Calculation and input contract: criminal-justice/public-case-suffix-sequence-gap — tool.io

Similar or alternative tools