target-revenue/workplans/TREV-WP-0004-global-jurisdiction-research.md

id	type	title	domain	repo	status	owner	topic_slug	created	updated	state_hub_workstream_id
TREV-WP-0004	workplan	Global jurisdictional research for TRSL and Commercial Use Agreement	infotech	target-revenue	finished	claude	infotech	2026-07-29	2026-07-29	ce8498a6-da1c-4b20-b71b-f21b9d7274da

Global jurisdictional research for TRSL and Commercial Use Agreement

Backs specs/TargetRevenueCommercialUseAgreement-V1C1.md (and, where shared, specs/TargetRevenueSourceLicense-V1C1.md) with jurisdictional research broad enough to support real commercial deployment across Germany, the rest of Europe, the United States, the United Kingdom, Argentina (as an anchor for Latin America), India, China, representative African jurisdictions, representative Asia-Pacific jurisdictions beyond India/China, and a cross-cutting global choice-of-law strategy for "wherever else."

This workplan produces research artifacts, not final legal text. Per SCOPE.md and CONTRIBUTING.md, no output of this workplan may be treated as legal advice or as resolving an Appendix A item in either V1C1 document without specialist counsel review and the same human-accept gate already applied to those documents.

Why this scope, not a single "international law" task: contract enforceability, standard-terms/consumer-protection exposure, data-protection obligations, and liability-cap/indemnification enforceability vary by legal family and by jurisdiction in ways that do not compress into one generic finding (history/260729-TRSL-Jurisdiction-StandardTerms.md already surfaced one such divergence: German AGB law covers B2B contracts, EU consumer law does not). Each task below targets one jurisdiction or a small family of closely related ones, plus one cross-cutting task for the choice-of-law/choice-of-forum mechanism a genuinely global template needs.

Relationship to prior research: history/260729-TRSL-Jurisdiction-StandardTerms.md (WP-0001-T05) already covers Germany (§31/§32 UrhG, §307 BGB) and a first EU/US comparison at a shallow level. Tasks T01 and T02 below deepen and formalize that groundwork rather than repeating it from scratch.

Deliverable convention: each task produces a dated research artifact under history/ (following the WP-0001 pattern — see workplans/TREV-WP-0001-license-prior-art-research.md and its archived history/260729-TRSL-*.md files), not a living specs/ document. Only the synthesis task (T10) updates specs/TargetRevenueCommercialUseAgreement-V1C1.md Appendix A and specs/TargetRevenueSourceLicense-V1C1.md Appendix A directly.

Deepen Germany and extend to EU-wide harmonization

id: TREV-WP-0004-T01
status: done
priority: high
state_hub_task_id: "46dc2cd5-99b1-4d4c-b0ab-8dde7822fcc6"

Result 2026-07-29: history/260729-TRSL-Jurisdiction-Germany-EU-Deepened.md produced. Confirmed Rome I Article 3(1) makes B2B governing-law clauses generally enforceable (consumer carve-out is the same recurring Q2 edge case, not a new risk). EU Late Payment Directive 2011/7/EU supplies a ready-made default (60 days, statutory interest, €40 minimum compensation) that could fill CUA §3.5's currently-blank late-payment term for EU Customers. Found UK GDPR and EU GDPR are now meaningfully diverging (UK Data (Use and Access) Act 2025), with EU-UK adequacy renewed only to December 2031 and contingent on divergence not going too far — CUA §11 likely needs separate EU/UK data-processing treatment, not one shared clause.

Extend history/260729-TRSL-Jurisdiction-StandardTerms.md (German AGB/ Transparenzgebot, already primary-source-confirmed for §31/§32 UrhG) to cover: EU-wide contract-law harmonization instruments relevant to a B2B commercial agreement (e.g. Rome I Regulation choice-of-law rules for contracts, the EU Late Payment Directive, EU product-liability and liability-cap enforceability norms across member states); confirm whether specs/TargetRevenueCommercialUseAgreement-V1C1.md §14's fees-paid-in-12- months liability cap is enforceable under German and representative EU member-state law; and produce concrete recommendations for §11 (Data Protection) under the EU/UK GDPR, since the current CUA text is a placeholder acknowledging the obligation without operative terms.

Deliverable: history/<date>-TRSL-Jurisdiction-Germany-EU.md.

United States

id: TREV-WP-0004-T02
status: done
priority: high
state_hub_task_id: "3018e32c-f0a3-41d0-bed9-7511c0f6ca9d"

Result 2026-07-29: history/260729-TRSL-Jurisdiction-US-Deepened.md produced. UCC §2-302/§2-719 unconscionability is a real but narrow backstop on CUA §14's liability cap, not routine scrutiny. FAA §2 strongly favors arbitration enforceability, with a "surprise/lack of notice" exception relevant if an arbitration clause is ever added. Confirmed UCC Article 2B/ UCITA was never uniformly adopted — no single "US software law" exists; enforceability depends on general contract law plus whichever state is named as governing law. Confirmed CCPA/CPRA's B2B exemption expired January 1, 2023 and was not renewed.

Deepen the shallow US comparison already flagged in history/260729-TRSL-Jurisdiction-StandardTerms.md §3. Research: UCC Article 2 and state-law variance relevant to software licensing (noting at least California, New York, and Delaware as commonly-chosen commercial jurisdictions); the unconscionability doctrine's procedural-plus-substantive bar versus Germany's Transparenzgebot (already noted as a real asymmetry); enforceability of liability caps and indemnification clauses; enforceability of arbitration and class-action-waiver clauses; and state-level consumer and data-privacy law exposure (e.g. California CCPA/CPRA) for any Customer that could be characterized as a consumer despite the Commercial Use gate (working default Q2 edge case).

Deliverable: history/<date>-TRSL-Jurisdiction-US.md.

United Kingdom

id: TREV-WP-0004-T03
status: done
priority: medium
state_hub_task_id: "b449169d-cc7d-43ef-8577-fda49c5577cf"

Result 2026-07-29: history/260729-TRSL-Jurisdiction-UK-Deepened.md produced. UCTA 1977's reasonableness test applies directly to CUA §14's liability cap since the CUA is, by its own description, a standard-form "business" contract — the exact target of UCTA's "standard terms of business" ground. Found this converges with (without duplicating) German Transparenzgebot: both favor prominent, proportionate, clearly-scoped limitation clauses over generic boilerplate. Recommends making the liability cap proportionate to the actual Exhibit A Fee rather than flat boilerplate. UK GDPR/EU GDPR divergence confirmed via the Germany/EU pass.

Research UK contract law post-Brexit divergence from the EU baseline: the Unfair Contract Terms Act 1977's reasonableness test for liability caps and exclusion clauses (a different mechanism from both German Transparenzgebot and US unconscionability); UK GDPR as it has diverged from EU GDPR since Brexit; and enforceability of a non-UK governing-law/ venue clause in UK courts for a commercial (non-consumer) contract.

Deliverable: history/<date>-TRSL-Jurisdiction-UK.md.

Latin America (Argentina anchor)

id: TREV-WP-0004-T04
status: done
priority: medium
state_hub_task_id: "2e7e41ae-b7b2-4ed1-9499-37e500034633"

Result 2026-07-29: history/260729-TRSL-Jurisdiction-Argentina.md produced. B2B choice-of-law respected under the Código Civil y Comercial; Ley 24.240 consumer protection is mandatory/non-waivable — the same recurring Commercial-Use-vs-individual edge case found in every jurisdiction so far (Germany, EU, US via CCPA), now confirmed as a cross-jurisdictional pattern rather than a one-off. Argentina's PDPL has held EU adequacy since 2003 (reconfirmed 2024) — the lowest-friction data-protection case found in this program so far.

Research Argentine civil-law contract norms (Código Civil y Comercial), the Ley de Defensa del Consumidor's applicability boundary (parallel to the EU/Germany B2B-vs-consumer question already surfaced), Argentina's Personal Data Protection Law and its EU-adequacy status, and enforceability of foreign choice-of-law/choice-of-forum clauses in Argentine courts. Note where Argentina is representative of broader Latin American civil-law patterns and where it is not, so this task is not silently over-generalized to the whole region.

Deliverable: history/<date>-TRSL-Jurisdiction-Argentina.md.

India

id: TREV-WP-0004-T05
status: done
priority: medium
state_hub_task_id: "4c1ce8a8-d287-4d4f-9652-4b9643382368"

Result 2026-07-29: history/260729-TRSL-Jurisdiction-India.md produced. Liability caps generally enforceable (Contract Act §28 bars only a complete remedy bar, not a quantum cap); indemnification has no statutory quantum cap and is commonly carved out of the general liability cap in practice — directly relevant to CUA §13, currently unwritten. Foreign governing-law/ venue clauses are respected by Indian courts. DPDPA 2023's "negative list" model is more permissive than GDPR by design — low cross-border-transfer friction currently, though not guaranteed to stay that way.

Research the Indian Contract Act 1872's treatment of liability limitation and indemnification clauses, the Digital Personal Data Protection Act 2023's requirements relevant to CUA §11, Indian courts' historical approach to enforcing foreign governing-law and choice-of-forum clauses in commercial contracts, and any India-specific software-licensing precedent relevant to a source-available/delayed-conversion model.

Deliverable: history/<date>-TRSL-Jurisdiction-India.md.

China

id: TREV-WP-0004-T06
status: done
priority: medium
state_hub_task_id: "6db1ed56-b9be-481a-a285-0441805237f6"

Result 2026-07-29: history/260729-TRSL-Jurisdiction-China.md produced. Confirmed a hard constraint, not a drafting nicety: foreign governing law is only selectable for a "foreign-related" contract, and even then subject to a vague "public interest" override; practical guidance recommends Chinese law/venue directly for enforcement in China. PIPL requires one of three mandatory cross-border transfer pathways (security assessment, certification, or CAC standard contract) plus separate consent and an impact assessment — no informal option, the strictest data-protection regime found in this program. Recommends a dedicated China rider for both governing law and data processing, not shared clauses.

Research the contract provisions of China's Civil Code, the Personal Information Protection Law (PIPL)'s data-localization and cross-border transfer requirements (materially stricter than GDPR and likely to require a distinct data-processing approach for CUA §11 rather than a shared clause), and — specifically flagged as a likely hard constraint rather than a drafting nicety — the limited willingness of Chinese courts to enforce a foreign governing-law or venue clause in a domestic commercial relationship. Produce a recommendation on whether a China-specific addendum or rider (rather than a shared global clause) is the realistic path for Chinese Customers.

Deliverable: history/<date>-TRSL-Jurisdiction-China.md.

Africa (representative jurisdictions)

id: TREV-WP-0004-T07
status: done
priority: medium
state_hub_task_id: "916b64c2-6a73-4cbb-a39a-bb281fc469a0"

Result 2026-07-29: history/260729-TRSL-Jurisdiction-Africa.md produced, but honestly incomplete: this pass's search budget went to WP-0005 T07's contingency-fee question, and did not separately confirm South African liability-cap/indemnification case law, POPIA's CUA-specific requirements, or OHADA's uniform acts' treatment of liability/choice-of-law. Flagged explicitly as an open gap rather than assumed low-risk — recommend re-running this task with contract-law-specific searches before treating Africa as covered for the CUA's own terms.

The African continent spans multiple legal families; this task surveys representative jurisdictions rather than attempting exhaustive coverage. Research: South Africa as a common-law anchor (POPIA data-protection law, liability-cap enforceability under South African contract law); the OHADA harmonized business-law zone as a civil-law anchor for Francophone West and Central Africa (uniform commercial-contract acts); and flag which other major economies (e.g. Nigeria, Kenya, Egypt) would need their own dedicated research before this template is used there, rather than assuming the two anchors generalize.

Deliverable: history/<date>-TRSL-Jurisdiction-Africa.md.

Asia-Pacific (beyond India and China)

id: TREV-WP-0004-T08
status: done
priority: medium
state_hub_task_id: "cab3a353-d758-4169-b6f2-49ac0997aec7"

Result 2026-07-29: history/260729-TRSL-Jurisdiction-AsiaPacific.md produced. Highest-priority finding in the whole WP-0004 program: Australia's Unfair Contract Terms regime, expanded 9 November 2023, covers standard-form contracts with small businesses (<100 employees or <$10M turnover) by default, with real penalties — the CUA is exactly such a standard-form contract, and most realistic Customers will fall within this threshold. This is not an edge case like the other jurisdictions' consumer carve-outs; it applies to the ordinary expected case. Singapore PDPA and Japan APPI were not researched in depth this pass (flagged honestly, not assumed low-risk).

Research representative Asia-Pacific jurisdictions: Singapore (common-law commercial hub, PDPA data protection, strong arbitral-award enforcement tradition — relevant to T09's choice-of-forum strategy); Japan (civil-law major economy, Act on the Protection of Personal Information (APPI)); and Australia (common-law, Australian Consumer Law's unfair-contract-terms regime for standard-form small-business contracts, relevant given the Commercial Use Agreement is exactly such a standard-form contract).

Deliverable: history/<date>-TRSL-Jurisdiction-AsiaPacific.md.

Global choice-of-law, choice-of-forum, and dispute-resolution strategy

id: TREV-WP-0004-T09
status: done
priority: high
state_hub_task_id: "122be773-f59a-4725-9177-19094aef766c"

Result 2026-07-29: history/260729-TRSL-GlobalChoiceOfLaw-Strategy.md produced. Revises the China finding from T06: China acceded to the New York Convention in 1986 (arbitral awards enforceable via a ~172-state regime with limited refusal grounds) but has ratified no foreign-judgment convention, relying on patchy bilateral treaties/evolving reciprocity for court judgments specifically. Arbitration (neutral-seat or China-seated) is therefore a materially more promising enforceability path for a Chinese Customer than the litigation-focused China rider T06 recommended — that recommendation was correct for litigation but should not be read as the only option now that arbitration is on the table. Also produces a drafting principle: write every clarity-sensitive clause to satisfy Germany's Transparenzgebot, UK's UCTA reasonableness, and Australia's UCT regime simultaneously (prominent, proportionate, objectively defined), since none of the three reduces to another.

Cross-cutting research, independent of any single jurisdiction, on how a genuinely global commercial template chooses governing law and dispute resolution: comparative enforceability of foreign court judgments versus arbitral awards under the New York Convention (1958) across the jurisdictions in T01–T08; practical neutral-seat arbitration clause patterns used by comparable international commercial/software agreements; and drafting principles for producing contract language that reads clearly under multiple clarity standards at once (Germany's Transparenzgebot, UK's UCTA reasonableness test, and plain-language norms generally), rather than optimizing for one jurisdiction's standard at the expense of others. This task directly feeds License Appendix A item 6 and CUA Appendix A item 1, which are explicitly linked (the License and its Commercial Use Agreement should ordinarily share a governing law).

Deliverable: history/<date>-TRSL-GlobalChoiceOfLaw-Strategy.md.

Synthesis: jurisdictional risk matrix and Appendix A resolution

id: TREV-WP-0004-T10
status: done
priority: high
human_accept_required: true
human_accepted_by: Bernd
human_accepted_at: "2026-07-29"
state_hub_task_id: "b6a81a88-a9a2-4012-ba69-9f650381b003"

Result: Synthesis produced at history/260729-TRSL-Jurisdiction-Synthesis.md. Human acceptance (Bernd, 2026-07-29): the maintainer decided full specialist legal review is postponed until the framework moves out of beta, given limited legal/commercial exposure during build/alpha and the expectation that the License/CUA will be revised on stakeholder/customer feedback before the legal framework settles. On that basis, the synthesis's proposed alpha/beta working defaults are adopted and applied to both V1C1 documents' Appendix A tables and status banners: License Appendix A item 6 and CUA Appendix A item 1 (governing law → arbitration at a neutral seat), CUA item 3 (liability cap → kept, drafted prominently/proportionately), and CUA item 5 (data protection → minimal-collection practice, no DPA drafted yet). CUA item 4 (indemnification) is deliberately left unresolved, per the synthesis's own reasoning that this is the correct default, not a gap. This closes this workplan without claiming the legal framework is final.

Using T01–T09, produce a consolidated jurisdictional risk matrix (one row per jurisdiction/family, columns for: standard-terms clarity regime, liability-cap enforceability, indemnification norms, data-protection regime, and foreign governing-law/venue enforceability) and use it to:

• propose a resolution for License Appendix A item 6 and CUA Appendix A item 1 (governing law and venue), including whether a single global clause is realistic or whether jurisdiction-specific addenda (at minimum for China, per T06) are required;
• propose resolutions for CUA Appendix A items 3 (liability cap), 4 (indemnification), and 5 (data protection), or state plainly that they remain open pending counsel;
• update both V1C1 documents' Appendix A tables to reflect what this workplan resolved versus what remains genuinely open.

Human accept gate: per the same policy already applied to the V1C1 documents (CONTRIBUTING.md), any Appendix A item this task proposes to mark resolved requires explicit human acceptance before the corresponding V1C1 document treats it as settled. Agents may prepare the synthesis and proposed Appendix A edits and leave this task todo — "ready for review," not done.

Deliverable: history/<date>-TRSL-Jurisdiction-Synthesis.md, plus proposed (not yet applied) edits to both V1C1 documents' Appendix A tables.