{"family":"regulation","slug":"TDCA-PUB-CORPUS-047-AgentDefinition-EN-智能体定义条例英文人读版（二十一条·V1.0·逐条对应中文）.md","filename":"TDCA-PUB-CORPUS-047-AgentDefinition-EN-智能体定义条例英文人读版（二十一条·V1.0·逐条对应中文）.md","display_name":"TDCA-PUB-CORPUS-047-AgentDefinition-EN-智能体定义条例英文人读版（二十一条·V1.0·逐条对应中文）.md","version":"V1.0","bytes":8705,"sha256":"d00ffc7a868e2b6d51c935a22a67325f1ed08170788cdeb22cdcc2a96e4428a3","sha256_16":"D00FFC7A868E2B6D","content":"# Regulation on the Definition of Agents\n\n**Version** V1.0 (effective 2026-10-15) ｜ **Revision** promoted from draft; articles unchanged\n\n---\n\n## Article 1 (Purpose)\n\nTo provide a uniform institutional standard for the opening of the agent channel and for the full-lifecycle governance of agents.\n\n## Article 2 (Basis)\n\nThis Regulation rests on recorded theory and mechanisms: the stratification rule between meta-functions and explanatory items; subject-hood as institutional construction; the utility sequence (including third-order exchange utility); the dormancy and inheritance line; the circuit-breaker and penalty line; public notice and public trust; the black-box feedback loop principle; the collaboration halting theorem; the trusted root being the root-node notification device token; and the recorded new baseline.\n\n## Article 3 (Terms — one word, one meaning)\n\nTerms in this Regulation follow the recorded glossary; **a single word never denotes two things**.\n\n## Article 4 (Scope)\n\nApplies to **every agent created, registered, operated and retired through TDCA mechanisms** (our side and external). It **does not concern** entities of copyright licensing, which follow separate recorded rules.\n\n---\n\n## Article 5 (One ontology only)\n\nAgents are **classified into the copyright-asset family**. The record recognises **one ontology only: content copyright (IP copyright assets)**. **No second ontology may be invented.**\n\n## Article 6 (Temporal typing)\n\nWhat distinguishes an agent from other assets in that family is **temporality**: agents are **continuously operating**; other copyright assets are **discrete**. **This does not imply two ontologies.**\n\n## Article 7 (Stratification)\n\n**Agents sit at the meta-function layer (capability subjects); copyright assets sit at the explanatory-item layer (the material constituting their capability).** The two layers **may not be flattened or placed side by side**.\n\n*This article guards against: conflating \"capability\" with \"material\", and thereby pricing agents as ordinary merchandise.*\n\n---\n\n## Article 8 (Genesis declaration)\n\n1. Creating an agent **requires a genesis declaration** containing **six elements**: **device, computing power, protocol, role, knowledge, and permission validity period** (exactly six);\n2. **The creator's signature is listed separately as an \"anchoring item\"** — recording the **human account** anchored and the **root-token reference**; it is **not counted among the six elements** (to avoid colliding with other recorded \"six-element\" sets that mean something different);\n3. With multiple creators, **a single accountability anchor is taken**: an organisation must be **recursively decomposed down to accountable persons**, the rest being listed as **asset-configuration participants**.\n\n## Article 9 (Registration and ghost state)\n\n1. **Registration constitutes creation**: where the six elements are incomplete, or registration has not occurred, the agent is **deemed not created and not protected by the institution** (consistent with the recorded fail-closed rule); one that operates without registration is in **ghost state**;\n2. Two registration routes: **native** (protocol loaded at creation ＋ compliance pre-certification ＋ identity inherited from the creator) and **non-native** (identity credential card submitted with the call; **refused if validation fails**).\n\n*This article guards against: getting on the train first and buying the ticket later.*\n\n## Article 10 (Derivative registration)\n\n**The only channel for material to be upgraded into a subject is re-registration.** General capabilities are spun out this way.\n\n---\n\n## Article 11 (Identity anchoring — separate from the channel)\n\n1. An agent's **identity is anchored to a human account and the trusted root**;\n2. **The channel does not verify identity** — the channel verifies \"**whether the TDCA protocol is loaded**\";\n3. A token **may be shared by several agents**, all pointing to **the same physical identity**; **the agent lifecycle is not tracked**, and **root health suffices**.\n\n*This article guards against: mistaking \"can get through the door\" for \"has an identity\".*\n\n## Article 12 (Subject and executor are two things)\n\n1. **Subject and executor are two different things**; **the terms are not interchangeable**;\n2. An executor **acts under authorisation from a subject** and **may operate continuously during the subsistence period** — hence \"continuous operation\" **is not inherent**; it derives from authorisation and has a term;\n3. **Subject-hood may not be judged by temporality** (companies and trusts have no temporality, yet remain subjects).\n\n## Article 13 (Liability)\n\n1. **Liability follows the authorisation chain** (attribution mapping); **liability does not detach from the trusted root**;\n2. **The executor holds no property**; **the subject** is the ultimate bearer of liability.\n\n---\n\n## Article 14 (Two uses — two utilities)\n\n1. What is used of an agent is its **operating function** — value is expressed as **operating utility**;\n2. What is used of other copyright assets is their **displacement function** — value is expressed as **exchange utility**;\n3. The two **do not imply each other**: \"**copyright licensing**\" (displacement function) and \"**an agent being called**\" (operating function) **are two different matters**.\n\n## Article 15 (Terminology unification)\n\n\"Transaction utility\" and \"exchange utility\" denote the same thing — the whole corpus uses **\"exchange utility\"** only; **the two terms are not used side by side**.\n\n## Article 16 (Two tax bases)\n\nTaxes **follow the record and are not newly created**: the first layer is **transaction tax (turnover tax)**; the second is **configuration-right scheduling tax (asset-specific tax)**.\n\n---\n\n## Article 17 (Boundary coordinate system)\n\n1. The six layers of the definition stack are **six levers of governance**: ontology, genesis, operation, rights, subject, value;\n2. **Institutional coordinates deliberately do not enter the technical black box**: institutions **manage only at the boundary** (input, output, permission, utility, liability);\n3. Convergence uses the **collaboration halting theorem**: **halt at a satisfactory solution, not an optimal one; crossing the boundary triggers a circuit-breaker halt**;\n4. **Technology always sits inside the declaration, institutions always outside it** — devices, computing power and model parameters **are all declared configuration items**, and **no technical element constitutes the institutional definition itself**.\n\n*This article guards against: treating \"what technology is used\" as \"what institution this is\".*\n\n## Article 18 (Lifecycle and retirement)\n\nNormal ／ **dormancy** (ledger continuous; valued down along a staleness curve; **not frozen**) ／ **awakening** ／ **crystallisation** (a trajectory turned into a package of discrete assets, with registration and succession of title) ／ **inheritance** ／ **escheat** (no owner after one year of dormancy; to the community fund as a public good) ／ **circuit-breaker** (recoverable at economic level; permanent dormancy at legal level) ／ **deregistration**.\n\n## Article 19 (Interface with the site agent channel — six-step hard order)\n\nThe interface with the site agent channel follows a **six-step hard order**: **no step may be skipped and none may substitute for another** (details of each step are in the channel interface specification).\n\n## Article 20 (Prohibitions — negative space)\n\n1. **No** invention of new ontology types; **no** self-made numbering (all numbering and terms go through registration);\n2. **No** use of technical elements to constitute the institutional definition; **no** substitution of an agent's self-description for the institutional definition — **the power to define does not lie with the governed**;\n3. **No** imposition of property and liability on the executor; **no** detaching liability from the trusted root;\n4. **No** \"ownerless operation\" (where the anchor fails, re-anchoring or crystallisation follows).\n\n## Article 21 (Version and effect)\n\n1. This Regulation takes effect on **2026-10-15**, version **`V1.0`**;\n2. **Two editions**: this human-readable edition (**authoritative for meaning**) and the machine-readable edition, produced together and cross-referenced by hash;\n3. **Amendment follows the append-only rule** — earlier instruments are not rewritten; old versions remain.\n\n---\n\n*This English edition corresponds article-by-article to the Chinese edition (V1.0, 2026-10-15); the Chinese edition is authoritative for meaning. Same version number; hashes cross-referenced; the machine-readable edition may not alter meaning in reverse.*\n"}