{"rfc":9,"draft":9,"source_sha256":"864ec6a3bebb0271edd8f943a37e75b44e76163d24f8e38f1b66b4b396bd7f31","candidate_occurrences":[{"source_locator":"RFC-AI-9:D9:L18:O1","line":18,"token":"MUST","text":"1.2 The key words MUST, MUST NOT, REQUIRED, SHOULD, SHOULD NOT and MAY, when in uppercase, are interpreted in the sense of IETF BCP 14 (RFC 2119 as clarified by RFC 8174). They apply to the RFC-AI system once this docume","classification":"UNCLASSIFIED_WORD_OCCURRENCE"},{"source_locator":"RFC-AI-9:D9:L18:O2","line":18,"token":"MUST NOT","text":"1.2 The key words MUST, MUST NOT, REQUIRED, SHOULD, SHOULD NOT and MAY, when in uppercase, are interpreted in the sense of IETF BCP 14 (RFC 2119 as clarified by RFC 8174). They apply to the RFC-AI system once this docume","classification":"UNCLASSIFIED_WORD_OCCURRENCE"},{"source_locator":"RFC-AI-9:D9:L19:O1","line":19,"token":"MUST","text":"1.3 Every document MUST show its approval state separately from its version or edition label. A header's self-reported state is not evidence of approval.","classification":"UNCLASSIFIED_WORD_OCCURRENCE"},{"source_locator":"RFC-AI-9:D9:L23:O1","line":23,"token":"MUST","text":"2.2 An identifier MUST refer to exactly one document subject and MUST NOT be reused for an unrelated subject. No nine-digit padding, hundred-step gaps, or competing public aliases are permitted in the active system.","classification":"UNCLASSIFIED_WORD_OCCURRENCE"},{"source_locator":"RFC-AI-9:D9:L23:O2","line":23,"token":"MUST NOT","text":"2.2 An identifier MUST refer to exactly one document subject and MUST NOT be reused for an unrelated subject. No nine-digit padding, hundred-step gaps, or competing public aliases are permitted in the active system.","classification":"UNCLASSIFIED_WORD_OCCURRENCE"},{"source_locator":"RFC-AI-9:D9:L25:O1","line":25,"token":"MUST","text":"2.4 The registry MUST reject duplicate allocation, conflicts, invalid syntax, and citation to unknown document identities. A number allocated to a withdrawn item MUST NOT be reassigned; the registry MUST record the dispo","classification":"UNCLASSIFIED_WORD_OCCURRENCE"},{"source_locator":"RFC-AI-9:D9:L25:O2","line":25,"token":"MUST NOT","text":"2.4 The registry MUST reject duplicate allocation, conflicts, invalid syntax, and citation to unknown document identities. A number allocated to a withdrawn item MUST NOT be reassigned; the registry MUST record the dispo","classification":"UNCLASSIFIED_WORD_OCCURRENCE"},{"source_locator":"RFC-AI-9:D9:L25:O3","line":25,"token":"MUST","text":"2.4 The registry MUST reject duplicate allocation, conflicts, invalid syntax, and citation to unknown document identities. A number allocated to a withdrawn item MUST NOT be reassigned; the registry MUST record the dispo","classification":"UNCLASSIFIED_WORD_OCCURRENCE"},{"source_locator":"RFC-AI-9:D9:L26:O1","line":26,"token":"MUST","text":"2.5 Identifiers and filenames MUST follow the same canonical naming: RFC-AI N.txt. One RFC-AI identity denotes ONE complete .txt document; its headings/sections MUST NOT become separate authoritative documents or paralle","classification":"UNCLASSIFIED_WORD_OCCURRENCE"},{"source_locator":"RFC-AI-9:D9:L26:O2","line":26,"token":"MUST NOT","text":"2.5 Identifiers and filenames MUST follow the same canonical naming: RFC-AI N.txt. One RFC-AI identity denotes ONE complete .txt document; its headings/sections MUST NOT become separate authoritative documents or paralle","classification":"UNCLASSIFIED_WORD_OCCURRENCE"},{"source_locator":"RFC-AI-9:D9:L26:O3","line":26,"token":"MUST","text":"2.5 Identifiers and filenames MUST follow the same canonical naming: RFC-AI N.txt. One RFC-AI identity denotes ONE complete .txt document; its headings/sections MUST NOT become separate authoritative documents or paralle","classification":"UNCLASSIFIED_WORD_OCCURRENCE"},{"source_locator":"RFC-AI-9:D9:L26:O4","line":26,"token":"MUST NOT","text":"2.5 Identifiers and filenames MUST follow the same canonical naming: RFC-AI N.txt. One RFC-AI identity denotes ONE complete .txt document; its headings/sections MUST NOT become separate authoritative documents or paralle","classification":"UNCLASSIFIED_WORD_OCCURRENCE"},{"source_locator":"RFC-AI-9:D9:L26:O5","line":26,"token":"MUST","text":"2.5 Identifiers and filenames MUST follow the same canonical naming: RFC-AI N.txt. One RFC-AI identity denotes ONE complete .txt document; its headings/sections MUST NOT become separate authoritative documents or paralle","classification":"UNCLASSIFIED_WORD_OCCURRENCE"},{"source_locator":"RFC-AI-9:D9:L31:O1","line":31,"token":"MUST","text":"3.3 Increments MUST be assigned from editorial change assessment; arithmetic alone MUST NOT infer compatibility, safety, consensus, or authority.","classification":"UNCLASSIFIED_WORD_OCCURRENCE"},{"source_locator":"RFC-AI-9:D9:L31:O2","line":31,"token":"MUST NOT","text":"3.3 Increments MUST be assigned from editorial change assessment; arithmetic alone MUST NOT infer compatibility, safety, consensus, or authority.","classification":"UNCLASSIFIED_WORD_OCCURRENCE"},{"source_locator":"RFC-AI-9:D9:L32:O1","line":32,"token":"MUST","text":"3.4 Every published edition MUST be pinned to exact immutable bytes and a cryptographic digest. Editing those bytes in place is forbidden. A new edition or an explicitly classified erratum is required.","classification":"UNCLASSIFIED_WORD_OCCURRENCE"},{"source_locator":"RFC-AI-9:D9:L33:O1","line":33,"token":"MUST NOT","text":"3.5 Software components (Reader, Writer, API, conference broker) MAY use separate software SemVer. Their software versions MUST NOT be mistaken for RFC-AI document draft or edition identifiers. Writer and Reader MUST use","classification":"UNCLASSIFIED_WORD_OCCURRENCE"},{"source_locator":"RFC-AI-9:D9:L33:O2","line":33,"token":"MUST","text":"3.5 Software components (Reader, Writer, API, conference broker) MAY use separate software SemVer. Their software versions MUST NOT be mistaken for RFC-AI document draft or edition identifiers. Writer and Reader MUST use","classification":"UNCLASSIFIED_WORD_OCCURRENCE"},{"source_locator":"RFC-AI-9:D9:L34:O1","line":34,"token":"MUST","text":"3.6 Every citation intending a particular normative text MUST include both document ID and edition, e.g. RFC-AI 9, Edition 1.0. A generic reference to RFC-AI 9 resolves to its currently designated authoritative edition a","classification":"UNCLASSIFIED_WORD_OCCURRENCE"},{"source_locator":"RFC-AI-9:D9:L34:O2","line":34,"token":"MUST","text":"3.6 Every citation intending a particular normative text MUST include both document ID and edition, e.g. RFC-AI 9, Edition 1.0. A generic reference to RFC-AI 9 resolves to its currently designated authoritative edition a","classification":"UNCLASSIFIED_WORD_OCCURRENCE"},{"source_locator":"RFC-AI-9:D9:L37:O1","line":37,"token":"MUST","text":"4.1 States are IDEA (unallocated exploration), DRAFT, PROPOSED, IN REVIEW, APPROVED, ACTIVE, DEPRECATED, SUPERSEDED and WITHDRAWN. NOT ACTIVE / NOT APPROVED MUST always be visible where applicable.","classification":"UNCLASSIFIED_WORD_OCCURRENCE"},{"source_locator":"RFC-AI-9:D9:L38:O1","line":38,"token":"MUST NOT","text":"4.2 Only an approved revision backed by recorded authorization may become APPROVED; activation is a separate, recorded decision. A system MUST NOT infer approval from a filename, packet, timestamp, AI assertion, or publi","classification":"UNCLASSIFIED_WORD_OCCURRENCE"},{"source_locator":"RFC-AI-9:D9:L40:O1","line":40,"token":"MUST NOT","text":"4.4 The CEO holds final release authority unless an explicit, verifiable delegation names the approving role and scope. Automated workers MAY draft, review and test, but MUST NOT self-approve.","classification":"UNCLASSIFIED_WORD_OCCURRENCE"},{"source_locator":"RFC-AI-9:D9:L41:O1","line":41,"token":"MUST","text":"4.5 Approval records MUST bind approver identity, UTC timestamp, exact source digest, edition number, decision, and published artifact digest. Withdrawal and supersession require similar evidence.","classification":"UNCLASSIFIED_WORD_OCCURRENCE"},{"source_locator":"RFC-AI-9:D9:L46:O1","line":46,"token":"MUST","text":"5.2 An ERRATUM identifies a defect in a published edition and its verified disposition; it MUST link to that edition and MUST NOT rewrite immutable source evidence.","classification":"UNCLASSIFIED_WORD_OCCURRENCE"},{"source_locator":"RFC-AI-9:D9:L46:O2","line":46,"token":"MUST NOT","text":"5.2 An ERRATUM identifies a defect in a published edition and its verified disposition; it MUST link to that edition and MUST NOT rewrite immutable source evidence.","classification":"UNCLASSIFIED_WORD_OCCURRENCE"},{"source_locator":"RFC-AI-9:D9:L47:O1","line":47,"token":"MUST","text":"5.3 An UPDATE modifies or extends a still-relevant standard and MUST explicitly list affected requirements, compatibility and applicability. A SUPERSEDES relationship replaces the prior document's authority, with a preci","classification":"UNCLASSIFIED_WORD_OCCURRENCE"},{"source_locator":"RFC-AI-9:D9:L49:O1","line":49,"token":"MUST","text":"5.5 Multiple publications MAY implement a long-lived policy family, but no second numbering series is introduced unless separately approved. References MUST identify the controlling RFC-AI edition.","classification":"UNCLASSIFIED_WORD_OCCURRENCE"},{"source_locator":"RFC-AI-9:D9:L53:O1","line":53,"token":"MUST","text":"6.2 HTML, PDF, accessibility renderings, search indexes and Reader presentations are DERIVATIVE representations; they MUST identify their source digest and edition. If a rendering disagrees with the source, the source co","classification":"UNCLASSIFIED_WORD_OCCURRENCE"},{"source_locator":"RFC-AI-9:D9:L54:O1","line":54,"token":"MUST","text":"6.3 Readers and Writers SHOULD recognize the current short RFC-AI N identity and the conventional RFC-AI/2 packet. They MUST preserve and safely display unknown first-line metadata (including JSON arrays/scalars/objects ","classification":"UNCLASSIFIED_WORD_OCCURRENCE"},{"source_locator":"RFC-AI-9:D9:L54:O2","line":54,"token":"MUST NOT","text":"6.3 Readers and Writers SHOULD recognize the current short RFC-AI N identity and the conventional RFC-AI/2 packet. They MUST preserve and safely display unknown first-line metadata (including JSON arrays/scalars/objects ","classification":"UNCLASSIFIED_WORD_OCCURRENCE"},{"source_locator":"RFC-AI-9:D9:L54:O3","line":54,"token":"MUST","text":"6.3 Readers and Writers SHOULD recognize the current short RFC-AI N identity and the conventional RFC-AI/2 packet. They MUST preserve and safely display unknown first-line metadata (including JSON arrays/scalars/objects ","classification":"UNCLASSIFIED_WORD_OCCURRENCE"},{"source_locator":"RFC-AI-9:D9:L55:O1","line":55,"token":"MUST","text":"6.4 Source revisions/derivatives MUST be verifiably linked to canonical object ID, edition, digest and authenticated publication state. An optional unsupported metadata type is NOT an integrity or authority failure; a cl","classification":"UNCLASSIFIED_WORD_OCCURRENCE"},{"source_locator":"RFC-AI-9:D9:L56:O1","line":56,"token":"MUST","text":"6.5 Format changes require Reader/Writer compatibility tests using optional arbitrary pre-CRLF metadata, JSON types, conventional packet, unknown fields, and raw round-trip. Unsupported metadata MUST degrade to raw/safe ","classification":"UNCLASSIFIED_WORD_OCCURRENCE"},{"source_locator":"RFC-AI-9:D9:L60:O1","line":60,"token":"MUST","text":"7.1 A single authoritative registry MUST store RFC-AI N, subject/title, current draft or edition, lifecycle state, controller, approval evidence, content digest, source location, relations, and UTC event timestamps.","classification":"UNCLASSIFIED_WORD_OCCURRENCE"},{"source_locator":"RFC-AI-9:D9:L61:O1","line":61,"token":"MUST","text":"7.2 Registry changes MUST be atomic, auditable, and attributable to an identified actor. Concurrent number requests MUST not allocate the same number. No field or state may be fabricated when unknown.","classification":"UNCLASSIFIED_WORD_OCCURRENCE"},{"source_locator":"RFC-AI-9:D9:L61:O2","line":61,"token":"MUST","text":"7.2 Registry changes MUST be atomic, auditable, and attributable to an identified actor. Concurrent number requests MUST not allocate the same number. No field or state may be fabricated when unknown.","classification":"UNCLASSIFIED_WORD_OCCURRENCE"},{"source_locator":"RFC-AI-9:D9:L63:O1","line":63,"token":"MUST","text":"7.4 Active catalogs, websites, APIs, Reader results and exported archives MUST resolve the SAME identity, edition, authority and digest. Search results for drafts MUST conspicuously show they are drafts.","classification":"UNCLASSIFIED_WORD_OCCURRENCE"},{"source_locator":"RFC-AI-9:D9:L63:O2","line":63,"token":"MUST","text":"7.4 Active catalogs, websites, APIs, Reader results and exported archives MUST resolve the SAME identity, edition, authority and digest. Search results for drafts MUST conspicuously show they are drafts.","classification":"UNCLASSIFIED_WORD_OCCURRENCE"},{"source_locator":"RFC-AI-9:D9:L64:O1","line":64,"token":"MUST","text":"7.5 Publication/approval evidence MUST be retained without exposing secrets or private information. Public artifacts MUST not accidentally include credentials, sensitive internal notes, or private review information.","classification":"UNCLASSIFIED_WORD_OCCURRENCE"},{"source_locator":"RFC-AI-9:D9:L64:O2","line":64,"token":"MUST","text":"7.5 Publication/approval evidence MUST be retained without exposing secrets or private information. Public artifacts MUST not accidentally include credentials, sensitive internal notes, or private review information.","classification":"UNCLASSIFIED_WORD_OCCURRENCE"},{"source_locator":"RFC-AI-9:D9:L69:O1","line":69,"token":"MUST","text":"8.3 Human authority and AI delegated authority MUST remain distinguishable. Delegation MUST state capabilities and expiry/revocation conditions, and MUST be checked at the approval operation.","classification":"UNCLASSIFIED_WORD_OCCURRENCE"},{"source_locator":"RFC-AI-9:D9:L69:O2","line":69,"token":"MUST","text":"8.3 Human authority and AI delegated authority MUST remain distinguishable. Delegation MUST state capabilities and expiry/revocation conditions, and MUST be checked at the approval operation.","classification":"UNCLASSIFIED_WORD_OCCURRENCE"},{"source_locator":"RFC-AI-9:D9:L69:O3","line":69,"token":"MUST","text":"8.3 Human authority and AI delegated authority MUST remain distinguishable. Delegation MUST state capabilities and expiry/revocation conditions, and MUST be checked at the approval operation.","classification":"UNCLASSIFIED_WORD_OCCURRENCE"},{"source_locator":"RFC-AI-9:D9:L70:O1","line":70,"token":"MUST","text":"8.4 Policies may evolve, but amendments to this RFC-AI MUST follow their own duly approved change path; this draft is not self-ratifying.","classification":"UNCLASSIFIED_WORD_OCCURRENCE"},{"source_locator":"RFC-AI-9:D9:L73:O1","line":73,"token":"MUST","text":"9.1 The active eight original documents MUST receive canonical names RFC-AI 1.txt through RFC-AI 8.txt, with packet IDs, normative references, internal filenames, human citations, and reader output reconciled. The new st","classification":"UNCLASSIFIED_WORD_OCCURRENCE"},{"source_locator":"RFC-AI-9:D9:L75:O1","line":75,"token":"MUST","text":"9.3 Historical backups needed for rollback or evidentiary retention MUST remain outside the active catalog and ordinary user navigation; they are not competing authoritative editions.","classification":"UNCLASSIFIED_WORD_OCCURRENCE"},{"source_locator":"RFC-AI-9:D9:L91:O1","line":91,"token":"MUST NOT","text":"11.6 RFC-AI's sequential short numbering, draft/edition syntax, single source text format and CEO approval structure are project design decisions. They MUST NOT be misrepresented as requirements imposed by those IETF pub","classification":"UNCLASSIFIED_WORD_OCCURRENCE"},{"source_locator":"RFC-AI-9:D9:L104:O1","line":104,"token":"MUST","text":"13.1 RFC-AI 0 is a valid founding identity, not a missing or invalid zero. The first subsequent specialized RFC is RFC-AI 1. All live navigation, references, catalogs and Reader/API interfaces MUST resolve RFC-AI 0 throu","classification":"UNCLASSIFIED_WORD_OCCURRENCE"},{"source_locator":"RFC-AI-9:D9:L113:O1","line":113,"token":"MUST","text":"RFC-AI 37 is a provisional next sequential draft, subject to registry allocation/reconciliation and CEO review. RFC-AI 12, 19, 21, 33–37 require editorial compatibility evaluation before activation. Draft headers and fil","classification":"UNCLASSIFIED_WORD_OCCURRENCE"},{"source_locator":"RFC-AI-9:D9:L129:O1","line":129,"token":"MUST","text":"## MUST-DESIGN CRITERIA — CEO-DIRECTED PROPOSED FUTURE SYSTEM","classification":"UNCLASSIFIED_WORD_OCCURRENCE"},{"source_locator":"RFC-AI-9:D9:L130:O1","line":130,"token":"MUST","text":"MUST-09-UTC: Any current UTC datetime, timestamp, deadline, source-freshness comparison, expiry, or chronological identifier MUST obtain current time through GetUTCDateNow() or its approved typed Time Interface result. A","classification":"UNCLASSIFIED_WORD_OCCURRENCE"},{"source_locator":"RFC-AI-9:D9:L130:O2","line":130,"token":"MUST","text":"MUST-09-UTC: Any current UTC datetime, timestamp, deadline, source-freshness comparison, expiry, or chronological identifier MUST obtain current time through GetUTCDateNow() or its approved typed Time Interface result. A","classification":"UNCLASSIFIED_WORD_OCCURRENCE"},{"source_locator":"RFC-AI-9:D9:L130:O3","line":130,"token":"MUST NOT","text":"MUST-09-UTC: Any current UTC datetime, timestamp, deadline, source-freshness comparison, expiry, or chronological identifier MUST obtain current time through GetUTCDateNow() or its approved typed Time Interface result. A","classification":"UNCLASSIFIED_WORD_OCCURRENCE"},{"source_locator":"RFC-AI-9:D9:L132:O1","line":132,"token":"MUST","text":"MUST-09-01: MUST distinguish operational current authority from research history and derived copies; obsolete/retired sources MUST be visibly labeled and removed from active discovery and contact assembly promptly.","classification":"UNCLASSIFIED_WORD_OCCURRENCE"},{"source_locator":"RFC-AI-9:D9:L132:O2","line":132,"token":"MUST","text":"MUST-09-01: MUST distinguish operational current authority from research history and derived copies; obsolete/retired sources MUST be visibly labeled and removed from active discovery and contact assembly promptly.","classification":"UNCLASSIFIED_WORD_OCCURRENCE"},{"source_locator":"RFC-AI-9:D9:L132:O3","line":132,"token":"MUST","text":"MUST-09-01: MUST distinguish operational current authority from research history and derived copies; obsolete/retired sources MUST be visibly labeled and removed from active discovery and contact assembly promptly.","classification":"UNCLASSIFIED_WORD_OCCURRENCE"},{"source_locator":"RFC-AI-9:D9:L133:O1","line":133,"token":"MUST","text":"MUST-09-02: MUST erase retired duplicate/obsolete content thoroughly once independently verified that the live design has no dependencies and that deletion is authorized under records obligations. Deletion MUST NOT prece","classification":"UNCLASSIFIED_WORD_OCCURRENCE"},{"source_locator":"RFC-AI-9:D9:L133:O2","line":133,"token":"MUST","text":"MUST-09-02: MUST erase retired duplicate/obsolete content thoroughly once independently verified that the live design has no dependencies and that deletion is authorized under records obligations. Deletion MUST NOT prece","classification":"UNCLASSIFIED_WORD_OCCURRENCE"},{"source_locator":"RFC-AI-9:D9:L133:O3","line":133,"token":"MUST NOT","text":"MUST-09-02: MUST erase retired duplicate/obsolete content thoroughly once independently verified that the live design has no dependencies and that deletion is authorized under records obligations. Deletion MUST NOT prece","classification":"UNCLASSIFIED_WORD_OCCURRENCE"},{"source_locator":"RFC-AI-9:D9:L134:O1","line":134,"token":"MUST","text":"MUST-09-03: MUST never use historical instructions as authority merely because they were indexed.","classification":"UNCLASSIFIED_WORD_OCCURRENCE"},{"source_locator":"RFC-AI-9:D9:L134:O2","line":134,"token":"MUST","text":"MUST-09-03: MUST never use historical instructions as authority merely because they were indexed.","classification":"UNCLASSIFIED_WORD_OCCURRENCE"},{"source_locator":"RFC-AI-9:D9:L139:O1","line":139,"token":"MUST","text":"## ADDITIONAL MUST-DESIGN CRITERIA — 2026-11-02 (PROPOSED, NOT IMPLEMENTED)","classification":"UNCLASSIFIED_WORD_OCCURRENCE"},{"source_locator":"RFC-AI-9:D9:L141:O1","line":141,"token":"MUST","text":"MUST: Document registry must distinguish current Standard vs guiding AI RFC, compatible revisions, exact source IDs, human piece approvals and historical research-only sources.","classification":"UNCLASSIFIED_WORD_OCCURRENCE"},{"source_locator":"RFC-AI-9:D9:L142:O1","line":142,"token":"MUST","text":"MUST consider the concrete literal behavior of competent AI workers and enforce required hard safeguards by simple, separately running Interface logic where an actual boundary exists. MUST not delegate Interface internal","classification":"UNCLASSIFIED_WORD_OCCURRENCE"},{"source_locator":"RFC-AI-9:D9:L142:O2","line":142,"token":"MUST","text":"MUST consider the concrete literal behavior of competent AI workers and enforce required hard safeguards by simple, separately running Interface logic where an actual boundary exists. MUST not delegate Interface internal","classification":"UNCLASSIFIED_WORD_OCCURRENCE"},{"source_locator":"RFC-AI-9:D9:L142:O3","line":142,"token":"MUST","text":"MUST consider the concrete literal behavior of competent AI workers and enforce required hard safeguards by simple, separately running Interface logic where an actual boundary exists. MUST not delegate Interface internal","classification":"UNCLASSIFIED_WORD_OCCURRENCE"},{"source_locator":"RFC-AI-9:D9:L145:O1","line":145,"token":"MUST","text":"REQ-AI-09-SOURCE-001: A SourceRegistry entry MUST bind immutable RFC number, canonical provider/file ID, expected parent ID, exact edition/draft revision, content SHA-256, authenticated approval status, privacy classific","classification":"UNCLASSIFIED_WORD_OCCURRENCE"},{"source_locator":"RFC-AI-9:D9:L145:O2","line":145,"token":"MUST","text":"REQ-AI-09-SOURCE-001: A SourceRegistry entry MUST bind immutable RFC number, canonical provider/file ID, expected parent ID, exact edition/draft revision, content SHA-256, authenticated approval status, privacy classific","classification":"UNCLASSIFIED_WORD_OCCURRENCE"},{"source_locator":"RFC-AI-9:D9:L146:O1","line":146,"token":"MUST","text":"REQ-AI-09-PUB-002: Editorial draft publication, human adoption as policy, service implementation, and independently verified enforcement MUST be separately represented. A draft visible on a public website MUST NOT be lab","classification":"UNCLASSIFIED_WORD_OCCURRENCE"},{"source_locator":"RFC-AI-9:D9:L146:O2","line":146,"token":"MUST NOT","text":"REQ-AI-09-PUB-002: Editorial draft publication, human adoption as policy, service implementation, and independently verified enforcement MUST be separately represented. A draft visible on a public website MUST NOT be lab","classification":"UNCLASSIFIED_WORD_OCCURRENCE"},{"source_locator":"RFC-AI-9:D9:L146:O3","line":146,"token":"MUST","text":"REQ-AI-09-PUB-002: Editorial draft publication, human adoption as policy, service implementation, and independently verified enforcement MUST be separately represented. A draft visible on a public website MUST NOT be lab","classification":"UNCLASSIFIED_WORD_OCCURRENCE"},{"source_locator":"RFC-AI-9:D9:L147:O1","line":147,"token":"MUST","text":"REQ-AI-09-PUB-003: A publication MUST be a typed, authorized, digest-bound operation with atomic source/registry pointer change where supported and a recoverable multi-store reconciliation plan otherwise; partial propaga","classification":"UNCLASSIFIED_WORD_OCCURRENCE"},{"source_locator":"RFC-AI-9:D9:L147:O2","line":147,"token":"MUST","text":"REQ-AI-09-PUB-003: A publication MUST be a typed, authorized, digest-bound operation with atomic source/registry pointer change where supported and a recoverable multi-store reconciliation plan otherwise; partial propaga","classification":"UNCLASSIFIED_WORD_OCCURRENCE"},{"source_locator":"RFC-AI-9:D9:L151:O1","line":151,"token":"MUST","text":"REQUIRED FUTURE BEHAVIOR: A governing source resolution MUST bind canonical provider ID, parent ID, file revision, exact content digest, edition, authenticated adoption status and effective time in one independently read","classification":"UNCLASSIFIED_WORD_OCCURRENCE"},{"source_locator":"RFC-AI-9:D9:L151:O2","line":151,"token":"MUST","text":"REQUIRED FUTURE BEHAVIOR: A governing source resolution MUST bind canonical provider ID, parent ID, file revision, exact content digest, edition, authenticated adoption status and effective time in one independently read","classification":"UNCLASSIFIED_WORD_OCCURRENCE"},{"source_locator":"RFC-AI-9:D9:L151:O3","line":151,"token":"MUST","text":"REQUIRED FUTURE BEHAVIOR: A governing source resolution MUST bind canonical provider ID, parent ID, file revision, exact content digest, edition, authenticated adoption status and effective time in one independently read","classification":"UNCLASSIFIED_WORD_OCCURRENCE"}],"status":"DERIVED_WORD_LOCATOR_NOT_NORMATIVE"}