Benefit menu keyed to the wrong date

REC-HV-1102-3REVIEWEXCEPTIONSHADOW v1.0HV-1102

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: Accident benefits version selector: two keys
Version selected: Prior benefit set
Instrument: O. Reg. 383/24 (amending O. Reg. 34/10), Benefit menu and payer order, in force 1 July 2026
Enforcement: reference, routes to review or escalation
Verification status: VERIFIED Reform and in-force date (FSRA, RIBO)VERIFIED Benefit menu keyed to policy dateCOUNSEL-CONFIRMS Payer order section and subsection numbers
Policy sources

What it rests on

Input	Value	Basis	Source
Policy renewal date	2026-03-01	Inferred, needs counsel
Next renewal	2027-03-01	Inferred, needs counsel
Declarations page	Not on file	Missing	no document
Written agreement changing coverage	Not on file	Missing	no document
Date the memo used to choose the benefit menu	Accident date	From a document
What the client was told	Income replacement not available	From a document
Accident date	2026-08-14	From a document

Deterministic reasoningno model sits here, by design

Key 1, benefit menu: the policy date. 2026-03-01 (inferred from a broker email).
2026-03-01 is before 1 July 2026, so the edition is "Policy renewed before 1 July 2026".
The memo keyed the menu to the accident date (2026-08-14). That is the key for payer order, not the menu.
The declarations page is not on file; the policy date stays inferred until it arrives.

The record's slots

Confidence: Inferred, needs counsel
Question: Upload the declarations page. Is there a written agreement changing coverage before renewal? (benefits clerk)
Which date selects the benefit menu on this file: the accident date or the policy renewal date? (knowledge partner)
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: 6 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.