{"family":"regulation","slug":"TDCA-SPEC-REGISTER-OF-RIGHTS-001-TDCA注册登记制度（英文人读版V0.1-DRAFT）.md","filename":"TDCA-SPEC-REGISTER-OF-RIGHTS-001-TDCA注册登记制度（英文人读版V0.1-DRAFT）.md","display_name":"TDCA-SPEC-REGISTER-OF-RIGHTS-001-TDCA注册登记制度（英文人读版·V1.0-FROZEN已生效）.md","version":"V1.0-FROZEN","bytes":10901,"sha256":"105f68efbf15b69243d60986eeffaedf7799849f04361ee5008158a790da763e","sha256_16":"105F68EFBF15B692","content":"# TDCA-SPEC-REGISTER-OF-RIGHTS-001 · **TDCA Registration System** (English Human-Readable Version · `V1.0-FROZEN (IN FORCE)`)\n\n\n---\n\n## 0. One-line summary\n\nThis draft **transcribes the Chinese human-readable version article by article** ( `8` chapters · **`24`** articles ＋ **`3`** annexes): **binary registration** ( ownership registration = confirming rights attribution · authorization registration = determining authority and scenario) ｜ the ownership entry **is broad** ( anything with a form of expression may be registered) while the authorization entry **is strict** ( three requirements · fail-closed) ｜ the **authorization instrument** is uniform in form ( special and custom terms **are agreed by smart contract**) ｜ **compliance-first** ( register and authorize before configuration) ｜ exceptions **only in sandbox or drill**, **leaving the sandbox requires authorization** ｜ **NOT IN FORCE** ( pending four steps ＋ sign-off). This side **does not decide** any threshold, weight, bar, scale, rate or signing authority.\n\n---\n\n## 1. General provisions\n\n**Article 1 (Purpose)** In order to regulate **registration activities** within the TDCA ecosystem, so that **ownership** and **authorization** are each properly ordered, verifiable and queryable, and so that **configuration (invocation)** always has an instrument, this system is enacted.\n\n**Article 2 (Scope)** This system applies to the **registration of all assets** within the TDCA ecosystem and to their **configuration-admission** activities.\n\n**Article 3 (Basis)** Per registered instruments: *TDCA Metafunction–Interpretant Relation Reconciliation Specification* (** configuration right = the relation between metafunction and interpretant**) ｜ `terminology item` (** minimum configuration unit = scenario** · internal elements **do not participate in configuration directly**) ｜ `terminology item` (** five-tier generalized utility right**) ｜ *IP Copyright Asset Valuation Management Measures* ( registered regulation) ｜ the three new-baseline institutional instruments.\n\n**Article 4 (Basic principles)**\n1. **Compliance first**: register first, authorize first, configure afterwards ( **no inversion of order**).\n2. **Binary separation**: **ownership registration** and **authorization registration** **are two matters and two ledgers**.\n3. **Configuration by instrument**: configuration **always requires an authorization instrument** ( **whether the asset is one's own or another's**).\n4. **Exceptions do not cross the cabinet**: exceptions apply **inside sandbox or drill**; **once out of the sandbox an authorization is required**.\n\n---\n\n## 2. Binary registration\n\n**Article 5 (Registration split)**\n\n| | **Ownership registration** | **Authorization registration** |\n|---|---|---|\n| What it governs | **Rights confirmation** — confirming **attribution of rights** (\"who owns this\") | **Authority and scenario** — confirming **who may use it, with what authority, in what scenario** |\n| Layer | ownership layer | configuration-right layer |\n| Entry | **anything with a form of expression may be registered** ( broad) | **three requirements complete** ( strict · see Article 11) |\n\n**Article 6 (Order)** **confirm rights first → then authorize (instrument required) → only then configure**; if any link is missing ⟹ **configuration is not permitted**.\n\n---\n\n## 3. Ownership registration (rights confirmation)\n\n**Article 7 (Entry criterion)** **Anything that has a form of expression may be registered.**\n\n**Article 8 (Assignment of legal domain)**\n1. Anything with a **form of expression** ⟹ **governed by copyright**.\n2. An expression that is an **invention** ⟹ **governed by patent law**.\n3. An expression that is a **digital structuring** ⟹ **governed by data law**.\n4. ( a mark) ⟹ governed by **trademark law**.\n\n**Article 9 (Distinction from valuation)** Ownership registration **is identification** ( determining nature and position); a **valuation-capable subject** ( content that can be uniquely marked) **is measurement** —— **the two are at different layers and must not be conflated**.\n\n---\n\n## 4. Authorization registration (determining authority and scenario)\n\n**Article 10 (Content)** Authorization registration **determines authority and scenario** ( who, with what authority, in what scenario).\n\n**Article 11 (Three requirements for validity)**\n1. **Scenario constraint** ( scenario mandatory).\n2. **Form of the five-tier asset** ( including **smart contracts** and the like).\n3. **Full composition authorized** —— missing any one ⟹ **registration is refused** ( **fail-closed**).\n\n**Article 12 (Authorization instrument)**\n1. **All of them are authorization instruments** ( **no distinction** between a \"self-authorization instrument\" and an \"other-authorization instrument\").\n2. **The format is the same**: **a fixed format applies**.\n3. **Special terms and custom terms** ⟹ **are all agreed by smart contract**.\n\n**Article 13 (Own assets also require an instrument)** **Whether ownership is one's own or another's**, authorization registration **must have an authorization instrument**; **without the instrument configuration is not permitted** ( \"it is mine\" **≠ \"it may be configured\"**).\n\n---\n\n## 5. Configuration admission\n\n**Article 14 (Interpretant and authorization instrument)** The metafunction's **interpretants are all constituted by authorization-registration instruments**; **without an authorization-registration instrument ⟹ no invocation and no configuration**.\n\n**Article 15 (Exceptions)**\n1. **Inside the sandbox**: **exception** ( instrument waived).\n2. **Drill**: **exception** ( instrument waived).\n3. **Leaving the sandbox**: **authorization must be obtained** —— **no leaving the sandbox without authorization**; configuration after leaving **returns to the normal track** ( instrument required).\n\n**Article 16 (Instrument of configuration)** The instrument of configuration ＝ **the authorization-registration instrument** ( the **reduction to an instrument** of \"configuration right = the relation between metafunction and interpretant\").\n\n---\n\n## 6. Registration review (compliance-first)\n\n**Article 17 (Review at metafunction registration)** **At the registration of a metafunction**, the interpretants' ① **ownership** and ② **authorization tier** **are subject to compliance review**; registration is permitted only after the review passes.\n\n**Article 18 (Effect)** **Compliance review at the registration stage** replaces ex-post stocktaking; **no separate \"interpretant inventory\" needs to be established**.\n\n---\n\n## 7. Responsibility and exceptions\n\n**Article 19 (Nature of unauthorized configuration)** **Configuration without authorization ＝ infringement**.\n\n**Article 20 (Effect of compliance-first)** Because of **compliance-first**, infringement **is not expected to occur** ( except where **the system malfunctions**); system anomalies are routed to the **exception-handling** line.\n\n---\n\n## 8. Supplementary provisions\n\n**Article 21 (Languages and versions)** This system **requires human and machine versions** ( Chinese / English **human-readable** ＋ **machine-readable**), **with the same version number**, **the human-readable version being the semantic authority**.\n\n**Article 22 (Procedure)** This system follows the registered **four-step institutional-promotion procedure**; where hard constraints are involved **a draft may not be treated as effective**.\n\n**Article 23 (Amendment)** Amendments go through **amending instruments** ( **no rewrite of earlier text**); matters involving red lines and the do-not-decide list **require the founder's highest-authority instruction**.\n\n**Article 24 (Effectiveness)** This system **takes effect on the date of the founder's sign-off**; the scope and batch of effectiveness **are reserved to the founder**.\n\n---\n\n## Annex 1 Source of positions ( founder's verbatim index · this side neither adds nor deletes)\n\n| # | Founder's verbatim ( excerpt) |\n|---|---|\n| `1` | 「当前的版权登记是权属登记，无授权登记。权属登记只是凡是具备表达形式的都可以登记归著作权保护，属于发明的表达归专利法管，属于数字结构化的表达归数据法管。TDCA 是需要对授权登记管理的，目前站点建设暂时也做权属登记，但是授权登记和权属登记不一样」 |\n| `2` | 「授权登记则需要场景约束，需要有智能合约等五阶资产的形态，所有构成无授权不得登记」 |\n| `3` | 「元函数的解释项都是由授权登记件构成的，否则无法被调用，配置，配置即侵权」 |\n| `4` | 「权属登记确权，授权登记确定权限与场景，无论产权自有还是他有，授权登记必须要有授权件，否则无法配置」 |\n| `5` | 「统一都是授权件，格式一样，有固定格式，特别条款，自定义条款都用智能合约约定」 |\n| `6` | 「无授权配置即侵权，演练和沙盒内例外，但出盒必须取得授权」 |\n| `7` | 「合规前置，不会有这个问题。除非系统出问题」 |\n| `8` | 「元函数登记时，解释项权属和授权等级需要合规审查的」 |\n\n## Annex 2 Reserved to the founder ( one item per line · this side does not decide)\n\n| # | Item |\n|---|---|\n| `1` | the **concrete fields of the authorization instrument's fixed format** ( this side may first produce a draft) |\n| `2` | the **interface form** for carrying special / custom terms **by smart contract** ( this side may first produce a draft) |\n| `3` | the **compliance-review bar and the tiers of \"authorization grade\"** ( institution layer ⟹ reserved to the founder) |\n| `4` | the **phase-one ownership-registration entry-form fields** ( this side may first produce a draft) |\n| `5` | the **sign-off and the batch in which this system takes effect** |\n\n## Annex 3 Boundaries\n\n1. This instrument is an **institutional draft** ( not a judicial ruling); it **amends** no registered instrument, counterparty-side instrument or in-repo instrument; changes go through `PR`.\n2. **Zero external exposure**; this side has **not pushed, not merged, not deployed, not logged in, not handed over**; **no credential values and no personal names**; **time zone +08**.\n3. Does not decide thresholds / weights / bars / scale / signing authority / **institution-layer semantics** on the founder's behalf; **no mathematical content, no legal opinion, no legal determination**.\n4. **Faithful registration**: every article **is compiled from the founder's verbatim positions** ( Annex 1), **nothing added by this side**; reconciliation with registered instruments **is recorded in Articles 3 and 8** ( Chinese human-readable version **is the semantic authority**).\n\n---\n\n---\n\n**Version** V1.0-FROZEN (in force 2026-10-03; scope: Phase-1 internal operation; public launch requires a separate statement)\n"}