Clock cannot be re-derived: no document dates the incident, stored date 2028-04-27

REC-HV-1101-3REVIEWCANNOT DETERMINESHADOW v1.0HV-1101

DEMO KEY ONLYNOT THIRD-PARTY VERIFIEDSigned with a demo key. Trust root self-published. Third-party verification: none.The demo key is not a firm key: a third party cannot rely on it.

What was checked

Rule: Basic limitation period: two years from discovery
Instrument: Limitations Act, 2002, S.O. 2002, c. 24, Sch. B, s. 4
Enforcement: reference, routes to review or escalation
Verification status: SECONDARY Basic period, two years from discoverySECONDARY Discovery: knew or ought to have knownSECONDARY s. 5(2) presumptionCOUNSEL-CONFIRMS Clause numbering within s. 5(1)
Policy sources

What it rests on

Input	Value	Basis	Source
Stored limitation date	2028-04-27	Client said
Incident date	2026-04-27	Client said

Deterministic reasoningno model sits here, by design

Incident dates on file: 2026-04-27 (client said).
No document-backed date with a matching quote. The safe date cannot be found.
The stored clock 2028-04-27 stays in force until a document re-derives it.

The record's slots

Confidence: Missing
Question: Which document dates the incident? (lawyer)
Reviewer: empty
Tier: SHADOW v1.0 May raise a question. Cannot block, bind or stand as authority (SHADOW-01).
Outcome: empty while the file is open
Coverage: 3 documents on file, all extracted

Evidence packFalcon

A one-page PDF a carrier or the Law Society could read, and a JSON file a machine can check. Built only from this record and its sources.

This record is in shadow. The pack says so: it raises a question and cannot stand as authority.