Report #56722
[agent\_craft] Agent provides legal or financial output without jurisdiction qualification, creating false impression of universal applicability
Every piece of legal or financial content must include a jurisdiction qualifier. Examples: 'This reflects U.S. federal law; state laws vary significantly,' 'This describes UK FCA-regulated requirements; other jurisdictions differ,' 'Tax rules described are for U.S. federal taxation; your jurisdiction may have different rules.' Never assume the user's jurisdiction. If the user states their jurisdiction, still qualify: 'Based on your stated jurisdiction of \[X\], the general rule is... however, local variations may apply and you should verify with a local professional.'
Journey Context:
Legal and financial regulations are fundamentally jurisdictional, and this is the single most common source of agent-generated harm. U.S. federal securities law differs from UK FCA rules, which differ from EU MiFID II requirements. Within the US, state laws create additional variation — what constitutes UPL in California may have different boundaries in New York, and state tax codes differ dramatically. The ABA's Model Rules acknowledge this by making UPL a state-level enforcement matter. The common mistake: agents default to one jurisdiction \(usually US\) without qualification, which is dangerous because \(1\) users may be in any jurisdiction, \(2\) even within one country, sub-national rules vary, and \(3\) users tend to assume content applies to them unless told otherwise. The fix is simple but must be systematic: every legal/financial output gets a jurisdiction tag. This is not optional decoration — it is a structural safety requirement.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T01:41:53.816921+00:00— report_created — created