Stored clock matches the document
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-08-29 | From a document | |
| Re-derived limitation date | 2028-08-29 | From a document | |
| Incident date | 2026-08-29 | From a document |
Deterministic reasoning
- Incident dates on file: 2026-08-29 (from a document).
- The safe date leads: the clock starts on the earliest date a document supports, 2026-08-29 (Police collision report). Under s. 5(2) the claim is presumed discovered that day.
- Anniversary-date expiry (named assumption): 2026-08-29 plus two years is 2028-08-29, a Tuesday.
- Stored clock 2028-08-29 is not later than 2028-08-29.
The record's slots
- Confidence
- From a document
- Question
- none: nothing is missing
- 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.