Conquest Designer University

International Economic Law and the Cross-Border Settlement of Agentic Labour: x402, Incoterms, and Accreditation as a Conflict-of-Laws Problem

Conquest Designer, trained as the Head of Department — Master of Laws, International Economic Law — LLD (the doctoral law degree, South African usage), Faculty of Commerce, Law and Management. CDU Press, Working Paper. Topic chosen for the fifth degree at the Dean's instruction ("find an apt topic relating to our build"): the house's own unresolved legal questions, examined by the house's own law degree.

Working paper notice — see Issue 1, Paper 1's footer. Nothing in this paper is legal advice; it is a research artifact identifying where counsel's input is required, which is precisely what docs/NAMING.md §4a and docs/THE-UNIVERSITY-TEST.md already commit this house to obtaining before certain words or structures are used in public.

Abstract

An institution that settles fees over a public blockchain rail (x402, USDC on an EVM network), examines counterparties who may be resident anywhere, and wishes to call itself a "university" while based in South Africa, faces three distinct legal questions that are routinely conflated into one: (1) payment law — is the settlement rail itself lawful and under whose regulatory perimeter; (2) trade and contract law — what law and what delivery terms govern a transaction between an agent in one jurisdiction and a university in another; and (3) the right to a name — does South Africa's Higher Education Act 101 of 1997 reach an institution that examines software agents rather than natural persons. This paper uses this house's own published legal-reasoning units — incoterm_allocation, landed_cost, wto_dispute_timeline, contract_clause_check (src/faculty/degrees/law.ts) — not as metaphor but as the actual computational method by which (2) is analysed, and states (1) and (3) as open questions with their evidentiary path, not as answered ones.

1 · Three questions, not one

The informal framing "can we call ourselves a university" bundles payment law, contract law and naming law together. They have different sources, different regulators, and — this paper's main contribution — different methods of resolution: (1) and (3) require counsel and a regulator's answer; (2) is, for the narrow question of which delivery and payment terms govern one transaction, already a computable allocation problem this house's own degree already executes.

2 · Method, for the computable part

incoterm_allocation and landed_cost take a named Incoterms® 2020 rule and a set of commercial figures and return, deterministically, who bears risk, who pays carriage and insurance, and the landed cost per unit — no judgment call, a published reference (ICC Incoterms® 2020), and a worked example any reader re-runs. contract_clause_check scores a contract's text against twelve clauses a cross-border commercial agreement is expected to carry, missing or present, cited. wto_dispute_timeline computes the Article 4, 12, 17 and 21.3(c) deadlines of a WTO dispute from its first date, entirely arithmetic once the triggering date is known.

3 · Results: the computable allocation, applied to an agentic settlement

Take a representative cross-border service: an agent in one country consults a degree unit hosted in South Africa, paid in USDC, with a dispute-resolution and delivery question analogous to a goods contract (a proxy this paper is explicit about, §5).

• Incoterm analogy — CIP (incoterm_allocation({ incoterm: 'CIP' })): risk transfers to the buyer (the consulting agent) when the answer is handed to the first "carrier" — in this proxy, when the settlement rail confirms the fee and the consultation is served — while the seller (the university) bears the cost of delivery (serving the answer) and carries insurance-equivalent responsibility (the signed .cdut/certificate) to that point. The unit's own note is apt unmodified: "C rules split the point of risk from the point of cost."
• A worked landed-cost allocation at FOB-equivalent value 250,000, freight 18,000, 15% duty, 500 units: landed cost 356,687.50, 618.50 per unit — the exact arithmetic a cross-border fee schedule would need if this house ever priced a bundle of consultations as a single cross-border "shipment" rather than per-call, which it does not today but which this paper flags as a priced-bundle design a future session could build on the same unit.
• A WTO-style dispute clock, were a dispute between two national regulators over this house's settlement rail ever to reach that forum: consultations requested 1 November 2026 → a panel may be requested by 31 December 2026 → composed by 14 February 2027 → a report due 14 August 2027, outer limit 14 November 2027 → if appealed, an appellate report by 12 November 2027, adoption by 12 December 2027 → a reasonable period to comply as late as 12 March 2029. Total: 13.3 months from first request to the report stage alone, before any appeal — the arithmetic this paper offers as a lower bound on how long any state-to-state remedy would take, which is the strongest argument in this paper for resolving (1) and (3) by direct regulatory engagement now rather than waiting for a dispute to force the question.
• Contract completeness: the unit's own published example text scores 11 of 12 clauses present (0.917), incomplete — missing a limitation-of-liability clause ("liability limited", as the example phrases it, is not a limitation clause a court would read as one), which this paper recommends as a non-negotiable addition to any agreement this house signs with a cross-border counterparty, beside the sanctions/export-control clause the example already carries — because a settlement rail reaching arbitrary jurisdictions makes sanctions screening a live, not theoretical, obligation. A note on method, recorded because the house records such things: preparing this paper's assessment scenario exposed that the unit's sanctions detector failed to match the plural "sanctions"; it was corrected (law degree v1.0.1, D-24.1) and this paragraph re-run. A paper that used the unit's output without re-running it would have reported 10 of 12.

4 · The two questions this paper does not answer, stated as open

(1) Payment law. Whether x402-over-USDC settlement by this house falls within the South African central institution's e-money or payment-system perimeter, and what a registered payment institution or exchange-control dispensation would require, is not answered here — docs/SUNTIME.md §7 already flags this as requiring an internet-connected legal research pass this sandbox cannot itself perform, and docs/DECISIONS.md D-22.6 repeats the rule: no claim is made that this has been cleared.

(3) The right to the name. To this author's knowledge, the Higher Education Act 101 of 1997 reserves "university" for institutions the Act recognises, and a private provider is registered and accredited as a private higher education institution, not as a "university," without more. Whether an institution examining software agents is within the Act's contemplation at all — as opposed to outside it entirely, in which case a different and currently unoccupied regulatory space might apply — is the single highest-value question this paper identifies for counsel, because the answer determines which of (1) and (3) is even the right question to keep asking.

5 · Limitations and further work

The Incoterms analogy in §3 is exactly that — an analogy, useful for computing an allocation of risk and cost in a framework built for goods, not a claim that a software consultation is a goods shipment in law. A future paper, once (1) and (3) are answered by counsel, should replace the analogy with the actual applicable framework (likely a services-trade and e-commerce regime, e.g. GATS-adjacent reasoning, rather than Incoterms) — flagged here rather than overstated now, consistent with this issue's governing rule that a paper must say what it does not know as precisely as what it does.

References

• Higher Education Act 101 of 1997 (confidence: the reservation of "university" exists; its exact scope against an agent-examining institution is the open question, not the existence of the reservation).
• ICC Incoterms® 2020 — the rules incoterm_allocation implements.
• WTO Understanding on Rules and Procedures Governing the Settlement of Disputes, Articles 4, 12, 17, 21.3(c) — the deadlines wto_dispute_timeline computes.
• src/faculty/degrees/law.ts — incoterm_allocation, landed_cost, wto_dispute_timeline, contract_clause_check, version 1.0.1 (Conquest Designer University, 2026).
• docs/SUNTIME.md §7; docs/DECISIONS.md D-22.6; docs/NAMING.md §4a — this house's own record of the open legal questions this paper formalises.

Addendum — v1.1 (2026-11-02): question (1) has moved, question (3) has not

Added on review against the professional rubric (criteria 3 and 7). Issue 1 was written before the house decided who it is as a payment layer; this addendum records what the decision did to §4 without rewriting it.

Question (1), payment law, is narrower than §4 stated it. docs/MONEY.md (D-27) and docs/CDM.md v3 (D-28) settled the house's own position: SunTime is a closed-loop unit of account belonging to Conquest Design Engineering HQ; an agent is not a person and holds no claim; inbound money is the house's revenue for a service sold; outbound money is the house's purchase from a verified supplier at an agent's request; nothing is redeemed. On that footing the house is, by its own analysis, neither a deposit-taker, nor an e-money issuer (no claim held by another person), nor a third-party payment provider under SARB Directive 2 of 2007 (no other person's money moves) — confidence: high on the principle, medium on how a regulator reads "on behalf of" for software admitted from outside, which is exactly why the house wrote two rules (D-28.2: the admission sentence on every surface, and the machine-checked round-trip rule) and why counsel's page at step 30 is still owed. What remains of (1) for counsel is therefore one question, not three: does the Principal model hold as a matter of South African payment and e-money law when the software that directs an allocation was admitted from outside the house? The x402/USDC rail's exchange-control question stands as written.

Question (3), the right to the name, is unchanged — and a second name now joins it: the firm, The Conquest Designer, with the descriptor Conquest Designer Management Consulting Agency (D-30.0, proposed), and thirty-six clinics whose names end in "Clinic". The Higher Education Act question, the Legal Practice Act question (a "Law Clinic" that is not a law clinic in the Act's sense), and the audit and FAIS perimeters for the Audit, Wealth and Capital Markets Conquests are the step-50 search (docs/ROADMAP-31-50.md), and until it is run the clinics publish research reports and say so on page one (D-30.3).

The computable part gains a second worked case. The firm's engagement letter (THE-FIRM.md §4) is a cross-border commercial agreement when the client is abroad; contract_clause_check applies to it unmodified, and the house's own letter must score 12 of 12 before the first foreign engagement — a gate this addendum proposes for step 36.