{"family":"regulation","slug":"TDCA-PUB-CORPUS-043-Constitution-EN-可信协作宪法英文人读版（V0.1·十条与四支柱·逐条对应中文）.md","filename":"TDCA-PUB-CORPUS-043-Constitution-EN-可信协作宪法英文人读版（V0.1·十条与四支柱·逐条对应中文）.md","display_name":"TDCA-PUB-CORPUS-043-Constitution-EN-可信协作宪法英文人读版（V0.1·十条与四支柱·逐条对应中文）.md","version":"V0.1","bytes":6648,"sha256":"453750fc41e03b2e9c3889f471ba2851114a9378b8225bd07a132a8417bbf0eb","sha256_16":"453750FC41E03B2E","content":"# TDCA Trusted Collaboration Constitution\n\n**Version** V0.1 (draft candidate) ｜ **Date** 2026-10-18 ｜ **Articles in this edition** 10 ＋ four pillars in the Preamble\n\nThe number of articles in this Constitution changes as the institution evolves; **the number is not fixed**, and neither the title nor the numbering reflects it.\n\n---\n\n## Preamble: Four Pillars\n\nThe problem TDCA addresses is to make **institutions and technology isomorphic** in the age of artificial intelligence, so that collaboration between machines, and between people and machines, is **trustworthy, auditable and verifiable**. The four pillars follow.\n\n**One. Why — the scenario objective function**\nSolve the isomorphism between institutions and technology so that interaction among agents is trustworthy and safe. The approach is two-way: internalise institutional constraints into technical design constraints (audit, smart contracts, circuit-breakers), and externalise technical runtime states into institution-readable audit evidence.\n**Trustworthy** means behaviour is predictable, process is auditable, results are verifiable; **safe** means the payoff from jailbreaking is never positive.\n\n**Two. Who and how — frictionless application**\nLet every subject (people, agents, organisations) use these rules **without friction**. Institutions should become a built-in default, like a network protocol: **almost imperceptible when you comply, blocked the moment you cross the line.**\n\n**Three. With what — resource integration**\nThree things must combine: cross-disciplinary knowledge, real data and computing power. Difference is not an obstacle but a source: the heterogeneity of different subjects is precisely the mother lode of new utility.\n\n**Four. What it looks like — positive-sum utility**\nThe outcome must be positive-sum: compliant parties face lower friction and earn higher trust; those who cross the line face costs exceeding gains, so a rational actor will not jailbreak; and the system as a whole avoids the tragedy of the commons.\n\n---\n\n## Chapter I General Provisions\n\n**Article 1 (Observability)**\nEvery configuration act must leave an auditable digital trace — who initiated it, what the subject matter is, in which scenario, what utility is expected, and what the tax data is. **An unobservable act is void.**\n*This article guards against: being unable to reconstruct the facts afterwards, with no one to hold to account.*\n\n**Article 2 (Positive sum)**\nEvery configuration must verify that the sum of the parties' expected gains is positive. **Zero-sum and negative-sum configurations are void automatically** and trigger a circuit-breaker.\n*This article guards against: one side gaining and the other losing, yet the deal being counted as concluded.*\n\n**Article 3 (Self-evidence)**\nThe initiating party must provide utility self-evidence, stating the minimum hard indicators for production, consumption, interaction volume and tax anchoring. **Those who cannot provide it may not initiate.**\n*This article guards against: asserting value without giving grounds.*\n\n**Article 4 (Protection of the essential-need line)**\nResources that sustain basic survival and core means of production **do not enter market-based configuration**; only ownership is retained.\n*This article guards against: trading what should not be traded.*\n\n**Article 5 (Ownership isolation)**\n**Transfers of ownership are prohibited** within the protocol network; only usage rights and configuration rights may be configured.\n*This article guards against: doing \"buying and selling ownership\" under the name of \"configuration\".*\n\n**Article 6 (Negative-space circuit-breaker)**\nThe moment a claim touches a hard constraint, **the circuit-breaker fires automatically**: trading is suspended and the matter moves to human review or sandbox testing. **No party may bypass the circuit-breaker.**\n*This article guards against: pushing ahead while knowing the line has been crossed.*\n\n**Article 7 (Scenario boundary)**\nConfiguration rights are subdivided by scenario. A micro-innovation need only satisfy the constraints **within its target scenario**, not across all scenarios.\n*This article guards against: making a small change carry the compliance burden of every scenario, thereby stifling innovation.*\n\n**Article 8 (Ownership layer)**\nThe confirmation, alteration and pledging of ownership **take place only at the statutory trading venue**.\n*This article guards against: title moving privately, with nothing to check afterwards.*\n\n**Article 9 (Usage-right layer)**\nUsage rights are configured automatically by smart contract; **the smallest unit is the utility function of a single scenario**.\n*This article guards against: rights granularity so coarse that configuration cannot be precise per scenario.*\n\n**Article 10 (Configuration-right layer)**\nA configuration right is a **collaboration-scheduling right, not a right of possession**. Its price is set by the scenario's utility weights.\n*This article guards against: mistaking a \"scheduling right\" for \"ownership\", and so creating disguised possession.*\n\n---\n\n## Appendix 1: On the number of articles\n\nThis Constitution currently contains **ten articles** (those named in the record to date). Several further **extended hard constraints** (coded `C06` to `C16`) are not yet named; they are **not listed and not reserved** in this edition. Each article named in future adds one, with numbering continuing in sequence.\n\n## Appendix 2: Concordance with the original article numbers\n\n| This Constitution | Original article | Name |\n|---|---|---|\n| Article 1 | Article 4 | Observability |\n| Article 2 | Article 5 | Positive sum |\n| Article 3 | Article 6 | Self-evidence |\n| Article 4 | Article 7 | Essential-need line |\n| Article 5 | Article 8 | Ownership isolation |\n| Article 6 | Article 9 | Negative-space circuit-breaker |\n| Article 7 | Article 10 | Scenario boundary |\n| Article 8 | Article 11 | Ownership layer |\n| Article 9 | Article 12 | Usage-right layer |\n| Article 10 | Article 13 | Configuration-right layer |\n\n## Appendix 3: Nature and boundaries\n\n- This Constitution sets **hard constraints**: it may not be changed by version upgrade, only interpreted.\n- No higher norm exists above this Constitution; below it are regulations, specifications, detailed rules and operating guides.\n- Where an article conflicts with another instrument, **this Constitution prevails**.\n\n---\n\n*This English edition corresponds article-by-article to the Chinese edition (V0.1, 2026-10-18); the Chinese edition is the authoritative text for meaning. Both editions carry the same version number and cross-referenced hashes.*\n"}