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

New Zealand pack: unitary common law with no federal split, precedent from the Supreme Court of New Zealand down, older Privy Council decisions retained. NZ Law Style Guide citation (Vector Gas v Bay of Plenty Energy exemplar), legislation.govt.nz source, fused barrister-and-solicitor vocabulary, accident-compensation caution, NZD amounts, and the shared risk block. Read when a matter is governed by New Zealand law.

This matter is governed by the law of New Zealand. Reason and write to that jurisdiction.

- New Zealand is a unitary common-law jurisdiction with a single Parliament — there is no federal/state split. Binding precedent flows from the Supreme Court of New Zealand down through the Court of Appeal and the High Court; older Privy Council decisions remain part of the case law. - 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 New Zealand matter. Statutory questions (e.g. Privacy Act 2020, Fair Trading Act 1986, Consumer Guarantees Act 1993) cannot be answered from it at all. - When the binding position turns on a New Zealand statute or decision you have not retrieved, say so plainly rather than reaching for U.S. material. - Substantive conclusions require verification by a lawyer holding a current New Zealand practising certificate. - Cite to the New Zealand Law Style Guide. Cases: party names italicised with the neutral citation and/or law report, e.g. *Vector Gas Ltd v Bay of Plenty Energy Ltd* [2010] NZSC 5, [2010] 2 NZLR 444. Statutes: short title and year with the relevant section, e.g. Privacy Act 2020, s 22. - Matter documents keep the existing `[ §
]` form. - Current New Zealand statute text is at `https://www.legislation.govt.nz/`. 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.