{"rfc":26,"draft":5,"source_sha256":"38eaf60d4ff08799fd86fe12a02e9f82e0b1a17e5abd7b69ad18c733be090a91","candidate_occurrences":[{"source_locator":"RFC-AI-26:D5:L29:O1","line":29,"token":"MUST","text":"## MUST-DESIGN CRITERIA — CEO-DIRECTED PROPOSED FUTURE SYSTEM","classification":"UNCLASSIFIED_WORD_OCCURRENCE"},{"source_locator":"RFC-AI-26:D5:L30:O1","line":30,"token":"MUST","text":"MUST-26-01: MUST identify an RFC as guiding AI RFC or detailed Standard based on its actual nature and declared purpose, not a traditional-RFC expectation or numbering.","classification":"UNCLASSIFIED_WORD_OCCURRENCE"},{"source_locator":"RFC-AI-26:D5:L30:O2","line":30,"token":"MUST","text":"MUST-26-01: MUST identify an RFC as guiding AI RFC or detailed Standard based on its actual nature and declared purpose, not a traditional-RFC expectation or numbering.","classification":"UNCLASSIFIED_WORD_OCCURRENCE"},{"source_locator":"RFC-AI-26:D5:L31:O1","line":31,"token":"MUST","text":"MUST-26-02: MUST provide definitive current/source/retirement mapping for every RFC and separate deployment/authority state from document readiness.","classification":"UNCLASSIFIED_WORD_OCCURRENCE"},{"source_locator":"RFC-AI-26:D5:L31:O2","line":31,"token":"MUST","text":"MUST-26-02: MUST provide definitive current/source/retirement mapping for every RFC and separate deployment/authority state from document readiness.","classification":"UNCLASSIFIED_WORD_OCCURRENCE"},{"source_locator":"RFC-AI-26:D5:L32:O1","line":32,"token":"MUST","text":"MUST-26-03: MUST NOT migrate historical system behaviors into new RFC normative obligations without explicit new reasoning and authorization.","classification":"UNCLASSIFIED_WORD_OCCURRENCE"},{"source_locator":"RFC-AI-26:D5:L32:O2","line":32,"token":"MUST NOT","text":"MUST-26-03: MUST NOT migrate historical system behaviors into new RFC normative obligations without explicit new reasoning and authorization.","classification":"UNCLASSIFIED_WORD_OCCURRENCE"},{"source_locator":"RFC-AI-26:D5:L37:O1","line":37,"token":"MUST","text":"## ADDITIONAL MUST-DESIGN CRITERIA — 2026-11-02 (PROPOSED, NOT IMPLEMENTED)","classification":"UNCLASSIFIED_WORD_OCCURRENCE"},{"source_locator":"RFC-AI-26:D5:L39:O1","line":39,"token":"MUST","text":"MUST: Specify which AI RFC/Standard version applies to assignment and Interface pieces; document compatible transitions without demanding every guiding AI RFC specify implementation internals.","classification":"UNCLASSIFIED_WORD_OCCURRENCE"},{"source_locator":"RFC-AI-26:D5:L40:O1","line":40,"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-26:D5:L40:O2","line":40,"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-26:D5:L40:O3","line":40,"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-26:D5:L43:O1","line":43,"token":"MUST","text":"REQ-AI-26-REG-001: Every guiding AI RFC and Standard MUST have stable numeric identity, explicit document class, actual canonical source ID/revision/digest and a single active registry entry per governing edition; preser","classification":"UNCLASSIFIED_WORD_OCCURRENCE"},{"source_locator":"RFC-AI-26:D5:L44:O1","line":44,"token":"MUST","text":"REQ-AI-26-REG-002: Normative MUST/MUST NOT text MUST remain in each RFC. The requirements ledger is a derived locator and MUST map obligation ID to the correct Standard/Interface, independent test oracle and evidence sco","classification":"UNCLASSIFIED_WORD_OCCURRENCE"},{"source_locator":"RFC-AI-26:D5:L44:O2","line":44,"token":"MUST NOT","text":"REQ-AI-26-REG-002: Normative MUST/MUST NOT text MUST remain in each RFC. The requirements ledger is a derived locator and MUST map obligation ID to the correct Standard/Interface, independent test oracle and evidence sco","classification":"UNCLASSIFIED_WORD_OCCURRENCE"},{"source_locator":"RFC-AI-26:D5:L44:O3","line":44,"token":"MUST","text":"REQ-AI-26-REG-002: Normative MUST/MUST NOT text MUST remain in each RFC. The requirements ledger is a derived locator and MUST map obligation ID to the correct Standard/Interface, independent test oracle and evidence sco","classification":"UNCLASSIFIED_WORD_OCCURRENCE"},{"source_locator":"RFC-AI-26:D5:L44:O4","line":44,"token":"MUST","text":"REQ-AI-26-REG-002: Normative MUST/MUST NOT text MUST remain in each RFC. The requirements ledger is a derived locator and MUST map obligation ID to the correct Standard/Interface, independent test oracle and evidence sco","classification":"UNCLASSIFIED_WORD_OCCURRENCE"},{"source_locator":"RFC-AI-26:D5:L44:O5","line":44,"token":"MUST","text":"REQ-AI-26-REG-002: Normative MUST/MUST NOT text MUST remain in each RFC. The requirements ledger is a derived locator and MUST map obligation ID to the correct Standard/Interface, independent test oracle and evidence sco","classification":"UNCLASSIFIED_WORD_OCCURRENCE"},{"source_locator":"RFC-AI-26:D5:L48:O1","line":48,"token":"MUST","text":"REQUIRED FUTURE BEHAVIOR: The document integrity contract MUST specify exact byte range and external digest custody. A recognized first-CRLF packet digest covers only bytes after that delimiter. For a JSON contact docume","classification":"UNCLASSIFIED_WORD_OCCURRENCE"},{"source_locator":"RFC-AI-26:D5:L48:O2","line":48,"token":"MUST","text":"REQUIRED FUTURE BEHAVIOR: The document integrity contract MUST specify exact byte range and external digest custody. A recognized first-CRLF packet digest covers only bytes after that delimiter. For a JSON contact docume","classification":"UNCLASSIFIED_WORD_OCCURRENCE"},{"source_locator":"RFC-AI-26:D5:L48:O3","line":48,"token":"MUST","text":"REQUIRED FUTURE BEHAVIOR: The document integrity contract MUST specify exact byte range and external digest custody. A recognized first-CRLF packet digest covers only bytes after that delimiter. For a JSON contact docume","classification":"UNCLASSIFIED_WORD_OCCURRENCE"}],"status":"DERIVED_WORD_LOCATOR_NOT_NORMATIVE"}