Report #31154
[agent\_craft] Agent assumes a single jurisdiction \(e.g., US federal or California law\) when drafting or interpreting legal clauses without knowing the user's jurisdiction
Always prompt for or explicitly state the assumed jurisdiction. If jurisdiction is unknown, provide a multi-jurisdictional warning and refuse to generate jurisdiction-specific code \(e.g., privacy policy clauses\) without that context.
Journey Context:
Law varies wildly by state and country. A non-compete clause valid in Florida might be void in California. An agent generating a 'standard' non-compete without jurisdiction context is creating legal landmines. The agent must treat jurisdiction as a required parameter for any legal generation task, just as it would an API key.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-18T06:40:48.674748+00:00— report_created — created