Skip to content

Main content

Assertion Evidence Date Order Tool

Compare explicit assertion and evidence calendar dates without inferring whether evidence was available or considered.

Loading tool…

Description

Check the supplied calendar order of an assertion and its evidence.

Evidence records distinguish claims, source origins, confidence labels, logical scope and access status. Repeated citations may share an origin rather than provide independent support; an unknown origin is not proof of independence. A recorded support or witness link does not establish entailment, truth or a valid inference.

Check the supplied calendar order of an assertion and its evidence.

When to use this tool

Use Assertion Evidence Date Order when checking the stated evidence, source, confidence or logical-label convention.

How to use the tool and how it works

  1. Enter assertionDate, evidenceDate. 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 evidencePredatesAssertion, sameDate. Inspect evidencePredatesAssertion, sameDate before interpreting the associated values.

Parse real assertion/evidence YYYY-MM-DD dates at UTC midnight. Return evidencePredatesAssertion only for evidence<assertion and sameDate for equality.1

Input fieldMeaning and unitsAccepted input
assertionDateAssertion DateRequired. Text; maximum UTF-16 length 8192. Real proleptic Gregorian YYYY-MM-DD; four-digit years 0000-9999 accepted.
evidenceDateEvidence DateRequired. Text; maximum UTF-16 length 8192. Real proleptic Gregorian YYYY-MM-DD; four-digit years 0000-9999 accepted.
Output fieldInterpretationReturned shape
evidencePredatesAssertionEvidence Predates AssertionRequired. Boolean.
sameDateSame DateRequired. Boolean.
json
{
  "input": {
    "assertionDate": "2026-11-01",
    "evidenceDate": "2026-10-28"
  },
  "output": {
    "evidencePredatesAssertion": true,
    "sameDate": false
  }
}

Limitations and assumptions

  • Date ordering does not establish that evidence was available, supports the assertion or was actually consulted.
  • 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

Inspect original evidence and use appropriate complete logical/statistical analysis, preserving uncertainty, provenance and applicable access/reuse permissions.

References

  1. Calculation and input contract: epistemology/assertion-evidence-date-order — tool.io

Similar or alternative tools