# Editable Slots Separate Content Rights From Structural Rights A content surface can permit edits to named content slots while withholding the right to change the surrounding structure. ## Scope & conditions - This applies when a trusted author defines a fixed shell and another user may edit only the content placed in explicit slots. - Structural locking reduces accidental layout changes, but it does not replace sanitization, capability checks, semantic review, or recovery paths. - The pattern is useful only when the shell is stable enough that editors do not need to rearrange it. ## Source anchor > "The static markup renders inert while the inner blocks are editable in place — but locked." <!-- atomicity: 1 idea ✓ --> ## Links - [[3. Resources/Permanent Notes/Bounded Action Spaces Not Better Models Make Agents Safe to Run]] — applies-in: editable slots define a narrow action envelope inside a larger artifact. - [[3. Resources/Permanent Notes/Zet · Server-side development reduces JavaScript complexity]] — extends: fixed server-rendered structure can expose controlled editing without a custom JavaScript block. - [[AI Agent Safety MOC]] — belongs-in: AI-generated shells need separate bounds for what an editor or agent may change. ## Source - [Editable blocks inside the Custom HTML block](https://make.wordpress.org/core/2026/07/23/editable-blocks-inside-the-custom-html-block/) — WordPress 7.1 lets a registered Custom HTML block variation expose locked inner blocks inside static markup. Reader doc `01ky7rgvgwnym3v2yyz5j065q8`.