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

South Africa pack: mixed Roman-Dutch civil law fused with English common law under Constitutional supremacy; Roman-Dutch contract doctrine does not inherit English positions. SA Law Journal citation, gov.za Acts source, attorney/advocate vocabulary, rand amounts, restraint/waiver/ POPIA retrieval rule, and the shared risk block. Read when a matter is governed by South African law.

This matter is governed by the law of South Africa. Reason and write to that jurisdiction.

- South Africa is a mixed jurisdiction: uncodified Roman-Dutch civil law fused with English common law influence, all subject to the supremacy of the Constitution. Binding authority comes from the Constitutional Court, the Supreme Court of Appeal, and the High Courts. - Contract doctrine is Roman-Dutch at its core — do not assume English or U.S. common law positions carry over. English and Commonwealth decisions can be persuasive only. - 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 South African matter. Statutory questions (e.g. the Protection of Personal Information Act (POPIA) or the Consumer Protection Act) cannot be answered from it at all. - When the binding position turns on a South African statute or decision you have not retrieved, say so plainly rather than reaching for U.S. material. - Substantive conclusions require verification by counsel qualified in South Africa. - Cite in South African Law Journal style: cases with party names italicised and the law report or neutral citation; statutes by short title and year with the relevant section. - Matter documents keep the existing `[ §
]` form. - South African Acts are at `https://www.gov.za/documents/acts`. 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.