{"rfc":23,"draft":5,"source_sha256":"69ae43334d2a98415f3379b8ff96046cf9afdd961b94213b2549c7e242fe27ac","candidate_occurrences":[{"source_locator":"RFC-AI-23:D5:L29:O1","line":29,"token":"MUST","text":"## MUST-DESIGN CRITERIA — CEO-DIRECTED PROPOSED FUTURE SYSTEM","classification":"UNCLASSIFIED_WORD_OCCURRENCE"},{"source_locator":"RFC-AI-23:D5:L30:O1","line":30,"token":"MUST","text":"MUST-23-01: MUST use StorageInterface as the sole authorized corporate storage execution owner, including direct editing, physical/integrity safeguards, verified saves, retries and concurrency.","classification":"UNCLASSIFIED_WORD_OCCURRENCE"},{"source_locator":"RFC-AI-23:D5:L30:O2","line":30,"token":"MUST","text":"MUST-23-01: MUST use StorageInterface as the sole authorized corporate storage execution owner, including direct editing, physical/integrity safeguards, verified saves, retries and concurrency.","classification":"UNCLASSIFIED_WORD_OCCURRENCE"},{"source_locator":"RFC-AI-23:D5:L31:O1","line":31,"token":"MUST","text":"MUST-23-02: MUST NOT require that the parent AI RFC recite the Interface implementation details.","classification":"UNCLASSIFIED_WORD_OCCURRENCE"},{"source_locator":"RFC-AI-23:D5:L31:O2","line":31,"token":"MUST NOT","text":"MUST-23-02: MUST NOT require that the parent AI RFC recite the Interface implementation details.","classification":"UNCLASSIFIED_WORD_OCCURRENCE"},{"source_locator":"RFC-AI-23:D5:L36:O1","line":36,"token":"MUST","text":"## ADDITIONAL MUST-DESIGN CRITERIA — 2026-11-02 (PROPOSED, NOT IMPLEMENTED)","classification":"UNCLASSIFIED_WORD_OCCURRENCE"},{"source_locator":"RFC-AI-23:D5:L38:O1","line":38,"token":"MUST","text":"MUST: StorageInterface MUST enforce all storage-side prohibitions in the StorageInterface project objectives: no stale-owner commit, no duplicate committed effect, no unchecked revision, no fiction of multi-Interface ato","classification":"UNCLASSIFIED_WORD_OCCURRENCE"},{"source_locator":"RFC-AI-23:D5:L38:O2","line":38,"token":"MUST","text":"MUST: StorageInterface MUST enforce all storage-side prohibitions in the StorageInterface project objectives: no stale-owner commit, no duplicate committed effect, no unchecked revision, no fiction of multi-Interface ato","classification":"UNCLASSIFIED_WORD_OCCURRENCE"},{"source_locator":"RFC-AI-23:D5:L39:O1","line":39,"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-23:D5:L39:O2","line":39,"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-23:D5:L39:O3","line":39,"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-23:D5:L42:O1","line":42,"token":"MUST","text":"REQ-AI-23-STORE-001: StorageInterface exclusively owns provider-side save, preservation, revision/owner fencing, verified commit and ambiguous write reconciliation. Transport MUST retry genuinely missing expected bytes, ","classification":"UNCLASSIFIED_WORD_OCCURRENCE"},{"source_locator":"RFC-AI-23:D5:L47:O1","line":47,"token":"MUST","text":"REQUIRED FUTURE BEHAVIOR: Future storage and recovery Standards MUST specify independent restore exercises with exact object ID/revision, full content digest, ACL, linked dependent entities and provider state. Preserve o","classification":"UNCLASSIFIED_WORD_OCCURRENCE"},{"source_locator":"RFC-AI-23:D5:L47:O2","line":47,"token":"MUST","text":"REQUIRED FUTURE BEHAVIOR: Future storage and recovery Standards MUST specify independent restore exercises with exact object ID/revision, full content digest, ACL, linked dependent entities and provider state. Preserve o","classification":"UNCLASSIFIED_WORD_OCCURRENCE"},{"source_locator":"RFC-AI-23:D5:L48:O1","line":48,"token":"MUST","text":"ADVERSARIAL DESIGN ACCEPTANCE: Simulate deletion of website with its contact/identity database; verify alternate emergency contact/recovery and exact-ID restoration across related services. A saved backup that cannot res","classification":"UNCLASSIFIED_WORD_OCCURRENCE"}],"status":"DERIVED_WORD_LOCATOR_NOT_NORMATIVE"}