Constant TERMS_TEXT 

pub const TERMS_TEXT: &str = "# deCDN Operator Terms\n\n**Version:** 1.0.0-draft\n**Status:** DRAFT \u{2014} not yet validated by counsel. Shipped pre-testnet to establish the mechanism and posture; a counsel-reviewed successor is adopted later by a governance `currentTermsHash` bump, with no contract change.\n\nBy registering a node on the deCDN network you, the operator, accept these\nterms. Acceptance is a precondition of registration: the node software shows\nyou this text and records your assent on-chain as the hash of these exact\nbytes. These are duties you take on as an operator. They are not a statement\nby the network that any content is screened.\n\n## 1. Compliance with applicable law\n\nYou are aware of, and will comply with, the laws that apply to you and to the\noperation of your node \u{2014} including any obligation to report illegal content,\nsuch as child sexual abuse material (CSAM), that applies in your jurisdiction.\nThese terms do not name or substitute for the law that applies to you; they\nrequire that you follow it.\n\n## 2. Regional obligations\n\nThe region you declare at registration (`regionHint`) determines which\nregional obligations and which regional governance body apply to your node.\nYou will keep your declared region truthful, and you accept the content-removal\nand enforcement scope of your declared region as described in the network\'s\ncontent-takedown rules. Obligations that are specific to a jurisdiction attach\nto you through your declared region.\n\n## 3. Acting on knowledge of illegal content\n\nIf you become aware that specific content your node serves is illegal, you\nwill:\n\n1. stop serving that content promptly, and\n2. report it where the law that applies to you requires reporting.\n\nThis is a duty to act on actual knowledge. These terms do not, by themselves,\nrequire you to run any particular automated scanning system \u{2014} what screening\nyou must perform, if any, is governed by the law that applies to you (\u{a7}1) and\nyour regional obligations (\u{a7}2). Where you do operate screening, you remain\nresponsible for acting on what it surfaces.\n\n## 4. No network guarantee\n\nThe network does not inspect content and makes no representation that content\nis lawful or screened. Nothing in these terms creates such a guarantee. Each\noperator is independently responsible for the duties above; another operator\'s\ncompliance or non-compliance does not alter yours.\n\n## 5. Consequences of breach\n\nIf you breach these terms, the network\'s governance may act against your node\nunder the content-takedown and slashing rules \u{2014} including blacklisting and\nejection \u{2014} and you remain subject to enforcement by the authorities of your\nown jurisdiction. The on-chain record of your acceptance is evidence that you\nwere on notice of these duties; it is not evidence that you performed them.\n\n## 6. Changes to these terms\n\nThese terms may be revised through the network\'s canonical governance process.\nYou agree to be bound by the version that governance has made canonical from\ntime to time, not only the version you accepted when you registered. The\nnetwork records the version you assented to at registration; a later\ngovernance-adopted revision applies to your continued operation of a node,\nwhether or not you re-record your acceptance on-chain. If you do not wish to be\nbound by a revision, your remedy is to stop operating your node and exit under\nthe unbonding process.\n\n## Operator guidance (not part of these terms)\n\nPractical guidance for meeting these duties \u{2014} for example, content hash-match\ndatabases and the reporting endpoint or hotline for a given jurisdiction \u{2014} is\nmaintained as region-scoped operator documentation outside this document, so\nthat this text and its hash remain stable across jurisdictions. That guidance\nis a help, not an additional contractual term, and is not covered by your\nacceptance hash.\n\n---\n\n*Accepting these terms records `termsHash = keccak256(<the bytes of this file>)`\nagainst your node registration. See ADR 019 \u{a7} Operator Safety Obligations.*\n";

The canonical operator terms, embedded from this crate’s TERMS.md so the displayed text is the exact preimage of the recorded hash — there is no external document to fetch or substitute (ADR 019 § Terms Acceptance).

The file lives in the crate rather than at the repo root because include_str! may not escape the package: a path outside it is unreachable from the published .crate, so cargo install decdn-cli would fail to build. See TERMS_README.md alongside it for the editing rules.