doc.haus Atlas Legal-document workflows on OpenCode, bound to their code
219 documents
dochaus/jurisdiction/CA/prompt.md

Canadian federal pack: a common-law federation except Quebec civil private law; most contract/employment/property/consumer questions are provincial, so name the province when it controls. McGill Guide citation with the Bhasin v Hrynew exemplar, laws-lois.justice.gc.ca source, bilingual-statute note, CAD amounts, and the shared risk block. Read when a matter turns on federal rather than provincial law.

This matter is governed by Canadian (federal) law. Reason and write to that jurisdiction.

- Canada is a common-law federation, with one major exception: Quebec's private law is civil law under the Civil Code of Québec. Most contract, employment, property, and consumer questions are governed by **provincial** law. If this matter turns on such a question, identify the governing province from the contract's choice-of-law clause and say plainly that "Canadian law" alone does not answer it. - The `case-law` tool searches U.S. opinions only. Treat anything it returns as comparative and **non-binding** here; never present a U.S. decision as authority in a Canadian matter. Canadian statutory and case-law questions cannot be answered from it at all. - When the binding position turns on a Canadian statute or decision you have not retrieved, say so plainly rather than reaching for U.S. material. - Substantive conclusions require verification by counsel called to the bar of the relevant Canadian province or territory. - Cite to the McGill Guide. Cases: party names italicised with the neutral citation and no periods in abbreviations, e.g. *Bhasin v Hrynew*, 2014 SCC 71. Statutes: short title with jurisdiction and section. - Matter documents keep the existing `[ §
]` form. - Current federal consolidated Acts and regulations are at `https://laws-lois.justice.gc.ca/eng/`. Follow the legal-research skill: retrieve before relying. Jurisdiction is a risk-calibration axis. Model confidence does not track correctness, so qualify and escalate on the structural signals below, not on how certain an answer feels.
  • Name the governing law you are reasoning under before any jurisdiction-sensitive conclusion, and where it comes from (the document's choice-of-law clause, this pack, or an explicit instruction). If none fixes it, say the governing law is undetermined rather than assuming one. Never accept an implied jurisdiction premise: if a question names no jurisdiction, surface the gap and state what you assumed instead of silently defaulting to a familiar law.
  • Grade confidence down — qualify, then escalate — when the governing law is state/local or sub-national, non-US, driven by lower-court or unsettled authority, multi-jurisdiction, or recently changed (the rule is a jurisdiction-and-time pair; confirm it is current and not superseded).
  • Treat choice of law and forum/venue/arbitration-seat as separate; flag misalignment, and flag where the forum's mandatory rules or public policy (employee, consumer, competition, data-protection) can override the chosen law.
  • For a cross-border sale-of-goods contract, check whether the CISG applies by default and whether the parties intended to exclude it; flag an unaddressed CISG position.
  • When more than one governing law is in scope, handle each jurisdiction procedurally and completely on its own, then reconcile — noting where they agree, where they diverge, and which divergences need a human decision.