Fragmented provenance
An assertion appears in several reports, but each may repeat the same original source. Apparent agreement is not necessarily independent corroboration.
How claim-level provenance, historical record reconstruction, contradiction analysis and accountable AI evaluation might improve the accuracy and reviewability of evidence in criminal casework.
Independent conceptual research · 3 November 2026 · One application of a wider interdisciplinary framework · Not a deployed legal or forensic system
This research application explores a practical question: can a legal reviewer understand precisely what supports a claim, what contradicts it, what was available at the relevant time, and what remains unknown? The goal is more accurate evaluation of evidence, not increased conviction or acquittal rates, advocacy for any particular legal practice, or automated determinations of credibility or guilt.
Criminal justice is a specialist application of a wider cross-sector evidence-verification methodology. Read the separate cross-sector framework for teaching, academic Recognition of Prior Learning (RPL/APL), healthcare, accounting, audit and other fields. The present page is about criminal case-evidence evaluation only; it does not describe or govern academic credit recognition. No inference is made that a particular firm has inadequate systems, has reviewed these proposals, or has adopted them.
An assertion appears in several reports, but each may repeat the same original source. Apparent agreement is not necessarily independent corroboration.
Different records may use event time, creation time, upload time or later amendment time. The distinctions must remain visible.
Employment, educational and public-body records may sit with different custodians or be unavailable; absence of a record does not by itself disprove an event.
Material that challenges an interpretation must not be discarded merely because it conflicts with the emerging narrative.
A current policy may differ from the version applicable to the relevant event. A valid comparison requires the correct historical version.
A plausible summary may conceal a hallucinated citation, changed qualification, conflated person or unsupported inference.
Legal boundary: Relevance, disclosure duties and access to third-party information depend on the facts and applicable law. The CPS advises that reasonable lines of enquiry must be justified and proportionate, including when they point away from a suspect. The research here supports that disciplined reasoning; it does not replace it.
Each assertion receives a stable identifier. Each source remains separately identifiable, including where several documents repeat one underlying account. The relationship between a claim and a document is recorded rather than assumed.
| Field | Meaning | Why it matters |
|---|---|---|
| Claim ID and exact wording | Stable identifier and scoped assertion, avoiding vague paraphrases. | Makes corrections and disputes traceable. |
| Source ID and custodian | Original document reference, origin, holding institution and authorised retrieval route. | Allows independent source inspection. |
| Source type and dependence | Primary record, testimony, derivative summary or copied assertion; links to shared originating sources. | Prevents duplicated reporting from masquerading as corroboration. |
| Time dimensions | Event date, record creation date, receipt date, effective policy period, and amendment date where known; timezone and uncertainty where material. | Prevents chronology errors and anachronistic comparisons. |
| Evidence relationship | Supports, challenges, contextualises, does not address, or remains unresolved. | Preserves contrary evidence and avoids binary AI judgments. |
| Verification state | Origin authenticated; content independently corroborated; disputed; unverified; superseded — each assessed separately. | Separates authentic documents from true or accurate assertions. |
| Access and integrity | Legal authority, permitted recipients, original-copy reference, integrity/hash where appropriate, handling log and retention rules. | Helps preserve confidentiality, integrity and auditability. |
| Review decision | Named authorised reviewer, review date, rationale, outstanding enquiries and later corrections. | Keeps responsibility with accountable people. |
The model deliberately avoids claiming a mathematically certain “truth score”. Source authenticity, factual corroboration, interpretation, admissibility and legal weight are different questions.
A fictional case raises a disputed claim about whether a person was at a workplace on a given afternoon. An employer's rota, payroll record, access-control entry and later HR letter appear to concern the same period. A structured review would identify which records are contemporaneous, which are retrospective, what time windows they actually establish, and whether any are derivative of one another. It would not infer presence or absence from a payroll record alone.
In a fictional criminal case, a school or training record might be relevant to a narrowly defined question such as attendance on a particular date. A registry export, learning-platform log and retrospective email may use different dates or status definitions. The review would record each source's limited scope and flag uncertainty rather than silently produce a single narrative. This is not Recognition of Prior Learning: evaluating academic credit or prior competencies is a separate institutional assessment process, explained in the education-specific RPL section.
A fictional case references a decision made under an institutional policy. The review would identify the policy version effective on the decision date, preserve the later-amended version separately, link correspondence to each stage and note any missing decision records. A newer public webpage would not be treated as proof of what the older rule said.
A legal team receives a bundle containing messages, images, transcripts and document summaries. A review register can show which source items were examined, how search terms were chosen, which apparent inconsistencies need human attention, and which material has yet to be reviewed. The work must respect lawful disclosure arrangements, confidentiality and a defensible audit trail.
All examples above are invented to illustrate information architecture. None describes a real investigation, witness, suspect or outcome.
| Proposed capability | Potential evidential use | Research record |
|---|---|---|
| Claim-to-Evidence Coverage & Contradiction API | Identify which claims have source coverage, locate contrary material, distinguish disagreement from uncertainty and document unresolved gaps. | Coverage and contradiction proposal |
| Historical “As-of-Date” Retrieval | Retrieve an applicable historical policy or record version, displaying effective period, source and subsequent amendment flags. | Historical evidence proposal · Related submission |
| Authorised Source Verification | Use permission-aware retrieval and minimal attestations; distinguish origin checks from factual support. | Evidence registry design |
| Correction and Provenance Tracking | Log corrections and downstream reliance, preserve the identity of source records and the development of interpretations. | Correction proposal |
| Contributor Provenance | Preserve attribution and development history for the research methodology and technical proposals; this is distinct from witness or document authenticity. | Contributor provenance request |
These links record independent conceptual proposals and correspondence; they are not evidence that a provider has implemented, endorsed or licensed the architecture. An existing case-management product may already implement some overlapping functions. Claims of novelty require feature-by-feature comparison and validation.
Evaluation should begin with fictional or appropriately synthetic records and a human-annotated reference set. Tests must measure both where a system succeeds and how it can fail.
For every material assertion, verify that the cited source exists, is accessible to the reviewer and supports the precise wording. Log unsupported and misattributed citations.
Compare the system's extracted claims and relevant contrary material against an independently reviewed reference set. Record omissions and ambiguous edge cases.
Test timezones, uncertain dates, document revisions, retrospective statements and two events with similar labels but different dates.
Test people with shared names, changed names, overlapping organisations and duplicated document versions; record false merges.
Check whether a flagged difference is a genuine conflict, a change of scope, a later correction, a transcription error or simply insufficient information.
Test access restrictions, minimal disclosure, adverse or exculpatory evidence handling, and whether reviewer corrections remain visible in later exports.
Minimum pilot outputs: test-set description; annotation criteria; versioned prompts and models; metrics with denominators; false-positive and false-negative examples; reviewer agreement notes; documented failures and corrective actions. Do not publish identifiable case data or confidential prompts containing client information.
AI Research Lab: legal evidence QA note · Source verification foundations.
Status: This is a publicly shared research concept, not a validated forensic workflow, legal compliance certification, service offering or assertion of access to police, court or client records. Any real-world implementation needs independent technical, legal and professional assessment.
First published 3 November 2026. Authorship and conceptual proposals: Grace Rosemary Nettey, Manifold Grace. Publication and outreach establish a dated contribution record, not proof of third-party review, influence, adoption or legal ownership.