target-revenue/specs/EnforcementNetworkConcept.md

Enforcement Network Concept

Working name: Target Revenue Enforcement Network (TREN) Document status: Concept draft — new, 2026-07-29 Purpose: Define the conceptual foundation for a decentralized, contingency-incentivized mechanism by which License §3 (Commercial Use) violations are pursued and recovered, jurisdiction by jurisdiction, without requiring the Licensor to litigate everywhere directly.

Any commercial user of a Milestone Release without a valid Commercial Entitlement is, in effect, taking value the framework is designed to capture as Development Credit. A single, centrally-operated Licensor cannot practically pursue that value across every jurisdiction where a violation might occur. The Enforcement Network proposes that independent, locally-licensed legal practitioners ("Enforcement Partners") may pursue such violations in their home jurisdiction, funded by a share of what they recover, so that enforcement scales the same way the framework's other monetization already does: through aligned incentive rather than central capacity.

---

1. Motivation

specs/TargetRevenueSourceLicense-V1C1.md §3 restricts Commercial Use without a Commercial Entitlement. Like any license restriction, this is only as strong as its enforcement. A Licensor with one home jurisdiction's legal resources cannot practically:

• detect unauthorized Commercial Use occurring in dozens of other jurisdictions;
• retain qualified local counsel in each one before a violation is even confirmed;
• fund upfront litigation costs against every plausible violation, most of which may not be worth pursuing to a distant, resource-constrained Licensor but might be entirely worth pursuing to a local practitioner who already operates in that market and bears no other case's costs.

This is structurally the same problem the framework's core monetization model already solves for revenue: centralizing everything doesn't scale, but an explicit, transparent incentive structure can recruit distributed effort. The core Target Revenue Framework aligns commercial users' payments with Development Credit; the Enforcement Network proposes to align local legal practitioners' pursuit of unpaid Commercial Use with a share of what they recover.

2. Scope

This concept defines:

• the minimal terminology of the Enforcement Network;
• the relationship between an Enforcement Partner, the Licensor, and the Trust Service;
• the Enforcement Action lifecycle (report → vetting → engagement → pursuit → recovery → allocation);
• the Recovery split (Contingency Share / Platform Share) and its integration with the existing Development Credit / Monetization Extension model;
• the central, framework-breaking legal risk this concept must not paper over: contingency fees for lawyers are not universally available — some jurisdictions ban or tightly restrict them, and the mechanism must degrade gracefully where they do;
• quality-control and anti-abuse principles needed before any Enforcement Action is authorized;
• the new legal instruments this concept requires beyond the License and Commercial Use Agreement.

This concept does not yet define:

• final legal text for an Enforcement Partner Agreement;
• a finalized, universal Contingency Share percentage (the 50% figure below is a proposed working default, not a settled rule — see §6);
• jurisdiction-by-jurisdiction legal feasibility findings (that is workplans/TREV-WP-0005-enforcement-network-research.md's job);
• the Trust Service's Enforcement Registry implementation.

3. Design goals

3.1 Locally lawful by construction

The mechanism must not assume every jurisdiction permits the same fee structure. It must be designed from the start to route around jurisdictions where a direct lawyer contingency fee is unavailable, rather than being drafted for one jurisdiction and applied everywhere by assumption.

3.2 No new discretionary authority for the Trust Service

Consistent with the framework's existing principle (specs/TargetRevenueFrameworkCore.md §1.10: the Trust Service observes, records, calculates, and attests — never decides), the Trust Service must not become the body that decides whether an Enforcement Action is authorized, meritorious, or successful. Those are the Licensor's and the relevant legal system's decisions; the Trust Service records the resulting facts (an Enforcement Action exists, its status, its Recovery, its allocation), the same way it already records Development Credit and Remission Credit without deciding whether a Phase's commercial hypothesis was sound.

3.3 Explicit allocation, not implied recovery

Recovered amounts must be explicitly allocated between Contingency Share and Platform Share, and the Platform Share must be explicitly allocated toward Development Credit (or not) under a canonical Monetization Extension — following Rule 2 (explicit allocation) exactly as every other payment in the framework must.

3.4 Quality control before incentive

A 50%-of-recovery incentive is a strong one, and strong incentives attract both genuinely valuable enforcement and low-quality or frivolous claims. This concept must not treat "an Enforcement Partner is willing to take the case" as sufficient authorization on its own.

4. Non-goals

The Enforcement Network is not intended to:

• replace the Licensor's own discretion over whether to pursue a given violation;
• guarantee that any jurisdiction's contingency-fee rules permit the mechanism as literally described;
• create a bounty system that rewards reporting a violation, as distinct from successfully litigating or settling one (see §7 — this concept currently contemplates compensating the Enforcement Partner's legal work, not a separate whistleblower/reporting bounty; whether those should be different roles with different incentives is an open question, §11);
• authorize an Enforcement Partner to act before a formal engagement instrument exists (§9);
• apply to Noncommercial Use — the Enforcement Network exists solely to pursue unauthorized Commercial Use under License §3.

5. Minimal core terminology

5.1 Alleged Violation

A reported instance of apparent Commercial Use of a Milestone Release without a valid Commercial Entitlement for the applicable Phase.

5.2 Enforcement Partner

An independently practicing lawyer or law firm, licensed in a given jurisdiction, engaged by the Licensor under an Enforcement Partner Agreement to pursue one or more Alleged Violations in that jurisdiction.

5.3 Enforcement Action

A specific legal action (litigation, arbitration, demand/settlement negotiation, or equivalent local procedure) pursued by an Enforcement Partner against a specific party with respect to a specific Alleged Violation.

5.4 Recovery

The total amount actually collected as a result of an Enforcement Action (judgment, settlement, or equivalent), before any split.

5.5 Contingency Share

The portion of Recovery paid to the Enforcement Partner (or, where local law requires a different structure, to the Litigation Funder — see §8) for pursuing the Enforcement Action. Working default: 50%, per the Licensor's original proposal — not yet validated against any jurisdiction's fee-regulation limits (see workplans/TREV-WP-0005-enforcement-network-research.md).

5.6 Platform Share

The remaining portion of Recovery after the Contingency Share, payable to the Licensor and subject to explicit allocation under §6.

5.7 Enforcement Registry

The Trust Service component that records Alleged Violations' status, Enforcement Partner engagement, Enforcement Action status, and Recovery/allocation facts, per §3.2's non-discretionary principle.

5.8 Enforcement Partner Agreement (EPA)

The instrument, distinct from the License, Commercial Use Agreement, and CLA, under which the Licensor engages an Enforcement Partner for a specific jurisdiction and/or Alleged Violation. See §9.

6. Recovery allocation and Development Credit

Recovery represents value the framework's Commercial Use restriction should already have captured. The Platform Share should therefore, by default, flow to Development Credit for the applicable Phase — this is arguably the single clearest case of "target-relevant allocation" the framework has, clearer even than a voluntarily-purchased Commercial Entitlement, since it corresponds to Commercial Use that already occurred without payment.

Proposed canonical extension: trsl:extension:enforcement-recovery, with:

extension:
  id: trsl:extension:enforcement-recovery
  version: "0.1 (proposed)"
  value:
    description: Recovery collected from an Enforcement Action against unauthorized Commercial Use.
  pricing:
    method: court/settlement-determined, not priced by the Licensor
  allocation:
    rule: Platform Share (Recovery minus Contingency Share) becomes Development Credit for the applicable Phase in full, unless a specific portion is separately and explicitly allocated to reimbursing the Licensor's own direct costs of the Enforcement Action.
    default_rate: 1.0 (of the Platform Share, not of gross Recovery)
  recognition:
    event: payment-settled (Recovery actually collected, not merely awarded)
  reversal:
    rule: A reversed or overturned Recovery (e.g. on appeal) generates a compensating credit-reversal Target Ledger entry.
  evidence:
    requirement: Enforcement Action case reference, settlement/judgment document, and Recovery collection evidence.
  status: registered (proposed; not yet canonical)

This keeps Recovery fully inside the existing accounting model (Rule 2 explicit allocation, Rule 3 no duplicate credit) rather than inventing a parallel bucket.

7. Enforcement Action lifecycle

Extends the framework's five-verb lifecycle (specs/TargetRevenueFrameworkCore.md §3) with an enforcement-specific sub-lifecycle:

1. Report — an Alleged Violation is reported (by anyone: the Licensor, a Trust Service operator, a third party, or an Enforcement Partner itself) to the Enforcement Registry.
2. Vet — the Licensor (not the Trust Service, per §3.2) reviews the Alleged Violation for plausibility before authorizing pursuit. See §10 for anti-abuse principles this step must satisfy.
3. Engage — the Licensor and a prospective Enforcement Partner in the relevant jurisdiction enter an Enforcement Partner Agreement scoped to the specific Alleged Violation(s).
4. Pursue — the Enforcement Partner conducts the Enforcement Action under local law and procedure.
5. Recover — a Recovery is collected (or the action concludes without one).
6. Allocate — Recovery is split into Contingency Share and Platform Share; the Platform Share is allocated per §6; all facts are recorded in the Enforcement Registry and, where applicable, the Target Ledger.

8. The central legal risk: contingency fees are not universal

This is the concept's most important open question, and it must not be resolved by assumption.

Many legal systems restrict or prohibit a lawyer taking a direct percentage of a client's recovery:

• Germany's Rechtsanwaltsvergütungsgesetz (RVG) §4a permits a conditional/contingency fee (Erfolgshonorar) only in narrow circumstances (broadly: where the client would otherwise be economically deterred from pursuing the claim at all) — a general-purpose 50% contingency arrangement as the Licensor describes it is very unlikely to qualify as drafted.
• Many civil-law jurisdictions historically treat pactum de quota litis (a lawyer's fee agreement tied to a percentage of the outcome) as a breach of professional ethics rules, though the details and degree of liberalization vary by country and have shifted over time.
• India's Bar Council of India Rules prohibit advocates from agreeing to fees contingent on the outcome of litigation.
• The United States, by contrast, permits contingency fees broadly (subject to state-bar reasonableness rules).
• The United Kingdom permits Conditional Fee Agreements and Damages-Based Agreements, but under statutory caps and structural conditions distinct from a plain 50% cut.

Working hypothesis (not yet validated — see workplans/TREV-WP-0005-enforcement-network-research.md): where a jurisdiction restricts direct lawyer contingency fees, the mechanism should separate two roles the Licensor's original proposal collapses into one:

• Litigation Funder — a non-lawyer party (which may or may not be affiliated with the Trust Service operator) that bears the economic risk of the Enforcement Action and is contractually entitled to the Contingency Share, structured as a funding arrangement rather than a legal-fee arrangement;
• Local Counsel — the retained, locally-licensed lawyer or firm, compensated under whatever fee structure that jurisdiction's professional-conduct rules actually permit (hourly, fixed, capped conditional fee, etc.), paid by the Litigation Funder or the Licensor rather than receiving the Contingency Share directly.

Where a jurisdiction does permit a lawyer to be both funder and counsel (the US being the clearest case), the Enforcement Partner role can collapse back into a single party, as originally envisioned. This split-role model is a proposed design response to a real legal constraint, not yet confirmed to be sufficient in any specific jurisdiction — third-party litigation funding is itself separately regulated (registration, disclosure, and champerty/maintenance doctrines in some common-law jurisdictions) and needs its own per-jurisdiction check.

8.1 Findings so far (workplans/TREV-WP-0005-enforcement-network-research.md T01–T09, all 8 jurisdiction/family tasks done)

All eight jurisdiction/family tasks are now complete. The pattern is more varied than a simple "civil law needs split-role, common law doesn't" split:

Jurisdiction	Single-role viable?	Realistic ceiling	Note
Germany	Very likely not	N/A — narrow §4a gates, not percentage-based	Split-role realistic path
France	Likely yes	Uncapped (fixed-fee-plus-result-fee structure)	Pactum de quota litis (pure %) void
United States	Yes	No fixed cap (state-bar reasonableness)	Needs timely copyright registration to be economically attractive
United Kingdom	Yes	50% (DBA statutory max, "all other cases")	Only jurisdiction where 50% is exactly validated
Argentina	Yes	35% ordinarily (Buenos Aires City); 50% only with risk-assumption	50%-with-risk-assumption resembles the Litigation Funder model natively
India	No — flat prohibition, no exception gates	N/A	Cleanest confirmation of split-role necessity; funding explicitly permitted
China	Yes	18% down to 6%, sliding scale by claim size (larger claims get a smaller ceiling)	Also likely needs its own governing-law/venue rider (§8, cross-refs License Appendix A item 6)
South Africa	Yes	25% (or 2× normal fee if lower)	Hard statutory cap, confirmed via the Contingency Fees Act itself
OHADA zone	Not confirmed	—	Genuinely unresearched; do not assume the French pattern applies
Singapore	Only for arbitration/SICC/mediation	N/A	Ordinary litigation likely needs the fallback structure
Japan	Yes, broadly	No fixed cap	Article 12 bans lawyer fee-splitting with non-lawyers — a compliance risk for the split-role model itself, not just the single-role fallback
Australia	Only Victoria, only class actions	N/A	Litigation funding market is mature nationally — split-role by default, for a different reason than Germany/India

Key findings beyond the per-jurisdiction ceiling:

1. 50% is not a safe global default anywhere except the UK. Most jurisdictions cap meaningfully lower (18–35%), several ban direct lawyer contingency outright, and the "with risk assumption" pattern that unlocks higher percentages (Argentina) or avoids professional-conduct problems entirely (Germany, India, Australia) recurs often enough that the split-role Litigation Funder structure should probably be the default EPA option, with single-role as the jurisdiction-specific exception — the reverse of how the concept was originally framed in §8.
2. The split-role structure is not universally safe either. Japan's Article 12 fee-splitting rule is the first finding in this program suggesting the Funder/Counsel split needs jurisdiction-specific structuring, not just jurisdiction-specific availability checking.
3. China likely needs a dedicated EPA governing-law rider, not just a dedicated fee structure — the same foreign-related-contract constraint found in workplans/TREV-WP-0004-global-jurisdiction-research.md T06 applies to the EPA itself.

A concrete Litigation Funder/Local Counsel mechanism design and payment-flow diagram (built from the first three jurisdictions researched) is at history/260729-TREN-MechanismDesign.md — its §4 feasibility table is now superseded by the fuller table above and should be read alongside it, not in place of it, pending T10's formal synthesis and human-accept update.

9. New legal instrument: Enforcement Partner Agreement (EPA)

A fourth instrument type, alongside the License, Commercial Use Agreement, and (for contributors) the CLA. Should address, at minimum:

• scope (which Alleged Violation(s) and jurisdiction the engagement covers);
• authorization (the Licensor's grant of authority to pursue the Enforcement Action on its behalf — likely a power of attorney or equivalent local instrument, not an assignment of the underlying copyright);
• Contingency Share / fee structure, jurisdiction-appropriate per §8;
• conduct standards and reporting obligations back to the Licensor;
• confidentiality and coordination with any Trust Service publication of the Enforcement Action's existence and status;
• termination and withdrawal (including the Licensor's ability to settle or withdraw independently of the Enforcement Partner's preference, and how that interacts with the Contingency Share if the Licensor settles directly).

This instrument is not drafted in this concept document. It is a future deliverable, analogous to how the Commercial Use Agreement was recommended in history/260729-TRSL-ContributorRights-Research.md before being drafted as specs/TargetRevenueCommercialUseAgreement-V1C1.md.

10. Quality control and anti-abuse principles

A strong financial incentive to find and pursue violations creates real risk: aggressive or mistaken claims against parties who are actually within Noncommercial Use or who hold a valid Commercial Entitlement the Enforcement Partner simply didn't check for, reputational harm to the framework (compounding the risk already flagged for License §7.4's breach-naming mechanism), and adversarial dynamics resembling "copyright trolling" if registry admission and case vetting are too permissive.

Proposed principles (not yet finalized):

1. Registry admission is not case authorization. An Enforcement Partner may be registered as available in a jurisdiction without any specific Alleged Violation being authorized for pursuit.
2. The Licensor vets before engagement, per §7 step 2 — not the Trust Service (§3.2), and not the Enforcement Partner unilaterally.
3. A minimum evidentiary bar for an Alleged Violation to proceed to vetting (analogous to the Target Ledger's evidence tiering, specs/TargetRevenueFrameworkCore.md concept, working default Q10's E0/E1/E2 tiers) — e.g., some E1-equivalent showing of actual Commercial Use, not mere suspicion.
4. Published Enforcement Action outcomes (win/loss/settlement rate per Enforcement Partner) as a Trust Service transparency measure, giving the ecosystem the same kind of conformity signal License §7.4 already establishes for breaches — this could double as a check on Enforcement Partner quality over time.

11. Open design questions

1. Should reporting an Alleged Violation carry its own, smaller incentive, separate from the Contingency Share paid for successfully litigating it — i.e., should "finder" and "pursuer" be different, separately-compensated roles? Not resolved here.
2. Is 50% the right Contingency Share in jurisdictions that do permit direct lawyer contingency fees, or is that a Licensor-set parameter that should vary by expected case value/complexity? Currently a working default, not a rule.
3. How does an Enforcement Action's Recovery interact with License §7.4's breach-disclosure mechanism, given litigation is typically a public record already in most jurisdictions — does the CUA's opt-in naming election even apply to a party who was never a Commercial Entitlement holder in the first place (they had no CUA to route the election through)?
4. Should the Licensor bear the risk of an unsuccessful Enforcement Action (Enforcement Partner/Litigation Funder absorbs the loss, standard contingency structure) uniformly, or could some jurisdictions' fee-shifting rules ("loser pays") expose the Licensor to the losing defendant's costs — and if so, who bears that risk?
5. Does an Enforcement Partner's local engagement require the Licensor to have standing/presence recognized in that jurisdiction, or can a foreign copyright holder generally engage local counsel without separate registration? Jurisdiction-specific.
6. Should there be a cap on aggregate Enforcement Actions pursued against a single class of common, good-faith mistakes (e.g., a small business that exceeded Noncommercial Use inadvertently) before a lighter-touch remedy (a cure notice, as in License §7.2) is required, to avoid the Enforcement Network becoming disproportionate to ordinary License §7 breach-and-cure process for parties who already hold some relationship with the Licensor?

12. Relationship to existing framework documents

• License (specs/TargetRevenueSourceLicense-V1C1.md): §3's Commercial Use restriction is what the Enforcement Network enforces; §7's breach/termination process governs parties who already hold a Commercial Entitlement, and is legally distinct from pursuing a party with no Commercial Entitlement at all (the latter is closer to infringement than to contract breach — see open question 3).
• Commercial Use Agreement (specs/TargetRevenueCommercialUseAgreement-V1C1.md): not directly implicated, since Enforcement Actions target parties who lack one — but its §9 breach-disclosure mechanism is the closest existing analog for how Enforcement Action outcomes might be published.
• Monetization Extension Specification: §6 above proposes a new canonical extension, enforcement-recovery, following the existing six-field contract exactly.
• Trust Service (specs/TechnicalSpecificationDocument.md §4.1): needs a new component, the Enforcement Registry, following the same observe/record/publish boundary as the existing Breach/Compliance Record component.

13. Concise definition

The Enforcement Network is a proposed mechanism by which independent, locally-licensed Enforcement Partners pursue unauthorized Commercial Use of a Milestone Release in their home jurisdiction, funded by a Contingency Share of any Recovery, with the remaining Platform Share flowing to Development Credit for the applicable Phase. Because lawyer contingency fees are not available in every jurisdiction, the mechanism must be capable of separating the economic-risk-bearing role (Litigation Funder) from the locally-compliant legal-representation role (Local Counsel) where local professional-conduct rules require it, rather than assuming a single global fee structure works everywhere.