Integrated Litigation Strategy (Overall + Per Front)
This document explains the complete strategy architecture for the RS-221578 system and the role of each front, including deferred tracks.
Primary objective
Preserve all remedies
Design principle
Forum separation
Operational model
Parallel fronts, controlled language
Series control
RS-221578 (1000/2000/3000/4000)
Core thesis: use HRTO as the discrimination/accommodation anchor, keep civil and regulatory fronts legally independent, and trigger deferred civil tracks only when timing risk is acceptable.
2. Integrated Strategy
- Maintain one master chronology and evidence corpus, but run separate legal theories per forum.
- Use regulatory fronts (FSRA/PIPEDA/AODA) to pressure process integrity, disclosure completeness, and record correction.
- Avoid any pleading language that could contaminate HRTO rights under s. 34(11).
- Keep constructive dismissal and some civil damages tracks deferred until HRTO posture is secured.
- Use RS series discipline and file-reference workflow for audit-grade traceability.
3. Front Map (Current + Deferred)
| Front | Forum | Respondent | Series | Status | Strategic Role |
|---|---|---|---|---|---|
| 1 | HRTO | Dare + individuals + Manulife | 1000 | Filed / amendment pending | Primary merits forum for discrimination and accommodation failure. |
| 2A | Superior Court | Dare | 1000 | Deferred | Reserved civil leverage; activate only after HRTO risk window. |
| 2B | Superior Court | Manulife | 2000 | Draft-ready | Insurance bad-faith/civil damages track, timed to avoid cross-forum prejudice. |
| 3A | FSRA | Manulife | 3000 | Ready to file | Regulatory pressure on unfair claims handling and investigation quality. |
| 3B | OPC (PIPEDA) | Manulife | 3000 | Correspondence sent | Access/completeness/accuracy enforcement over claim file data. |
| 3C | OPC (PIPEDA) | Dare | 3000 | Placeholder | Privacy/accountability track for employer-side data handling. |
| 3D | AODA | Dare | 3000 | Placeholder | Accessibility-process compliance lever. |
| 4 (deferred) | CD / Civil | Dare-centric | 4000 | Deferred | Constructive dismissal track reserved for controlled activation. |
4. Per-Front Strategy
Front 1 (HRTO)
- Theme: discrimination, failure to accommodate, injury to dignity.
- Objective: liability findings and Code-consistent remedies.
- Guardrail: exclude civil-contract framing from HRTO filings.
Front 2A (Civil vs Dare) - Deferred
- Theme: constructive dismissal, unilateral breach, notice damages.
- Objective: preserve civil recovery without collapsing HRTO positioning.
- Trigger: post-HRTO milestone or formal strategy unlock.
Front 2B (Civil vs Manulife)
- Theme: bad faith claims handling and consequential damages.
- Objective: create insurer-specific accountability track distinct from HRTO remedies.
- Dependency: strengthened by FSRA/PIPEDA factual record.
Front 3A (FSRA)
- Theme: unfair/deceptive insurance practices and deficient investigation.
- Objective: regulatory findings, pressure on insurer conduct, stronger appeal context.
- Output: tightly cross-referenced evidentiary allegations.
Front 3B/3C (PIPEDA)
- Theme: access, completeness, accuracy, and accountability principles.
- Objective: force complete file production and correct data basis of decisions.
- Role: procedural integrity and documentary leverage across fronts.
Front 3D (AODA)
- Theme: accessibility and process compliance.
- Objective: independent compliance pressure where accommodation process failed.
Front 4 (Constructive Dismissal, deferred)
- Theme: reserved dismissal framework and damage model.
- Objective: keep optionality without premature contamination of active fronts.
5. Sequence and Triggers
| Phase | Action | Trigger | No-Go Condition |
|---|---|---|---|
| Stabilize | Continue HRTO + regulatory evidence hardening | Ongoing filings and responses | Cross-forum language drift |
| Pressure | Advance FSRA/PIPEDA/AODA tracks | Disclosure gaps or process defects | Unverified factual claims |
| Escalate | Activate civil tracks when safe | HRTO milestones reached | s.34(11) contamination risk unresolved |
| Consolidate | Use findings/records across fronts | Regulatory and tribunal outputs available | Broken exhibit traceability |
6. Language Firewalls (Mandatory)
| Forum | Use | Never Use |
|---|---|---|
| HRTO | Discrimination, failure to accommodate, injury to dignity | Constructive dismissal, breach of contract, bad-faith civil framing |
| Civil | Breach of contract, bad faith, damages | Code section pleading language from HRTO fronts |
| FSRA/PIPEDA/AODA | Regulatory fairness, investigation quality, privacy/accessibility principles | HRTO/Civil damages phrasing |
Critical Filing civil language with Code framing can impair HRTO rights. Every outgoing document must pass language audit before send.
7. Evidence Strategy (Integral Across Fronts)
- Single evidence corpus, multi-forum interpretation.
- Every allegation tied to exhibit IDs and chronology entries.
- Outgoing documents require `File Ref: RS-221578-{series}-{TYPE}-{YYYY-MM-DD}`.
- Document workflow: File Ref -> Header -> Draft -> Validation -> Registry -> PDF protection.
- Original evidence and AI analysis must remain segregated by path policy.
8. Risk Controls
- R1 Forum contamination: mitigated by hard language firewall and review gates.
- R2 Exhibit breakage: mitigated by timeline/API exhibit health checks.
- R3 Sequence drift: mitigated by trigger-based phase activation.
- R4 Document traceability gaps: mitigated by RS series + registry discipline.
9. Traceability
| Item | Value |
|---|---|
| Document path | /mnt/c/rod_hub/personal/case-files/rod_case_master/docker/nginx/html/tools/strategy-narrative.html |
| Primary source | /mnt/c/rod_hub/personal/case-files/ACTIVE_FILINGS/README.md |
| Policy source | /mnt/c/rod_hub/personal/case-files/AGENTS.md |
| Last validated | 2026-03-01 |