# Governance Guardrails plugin v1 (Malcolm Peralty) > [!question] Lingering Questions > - Which features does the plugin actually gate, and at what enforcement layer (mu-plugin, filter, capability check)? > - What is the file format, and is it protected from unauthorized edits (file-integrity question)? > - How does it behave on WordPress multisite versus a fleet of separate single-site installs? > [!tip] Article Ideas > - Config-as-code feature governance for WordPress fleets, contrasted with WP 7.1's native feature-flags/canary direction once both are documented. > [!link] Cross Reference > - [[3. Resources/Permanent Notes/Default-Off Feature Flags Decouple Shipping Speed From Production Risk]] — same feature-flag territory, different mechanism (runtime flag vs. file-based governance) > - [[3. Resources/MOCs/WordPress Hosting Security Stack MOC]] — file-write and enforcement-layer questions are a hosting-security concern > [!quote] Vocabulary > - **Config-as-code governance** — policy expressed as version-controllable files rather than per-site database toggles, so the same policy can be copied across a fleet. ## Metadata - Source: [[3. Resources/Literature Notes/Governance Guardrails plugin v1 (Malcolm Peralty)]] - Author: Malcolm Peralty (@findpurpose) - URL: https://twitter.com/findpurpose/status/2068488141615276185 ## Author's thesis A 41-word release announcement: v1 of "Governance Guardrails," a WordPress.org plugin that controls feature availability through files, is now shipped — with the explicit, candid caveat that no marketing material exists yet. The claimed benefit is that file-based policy is easy to persist across many WordPress sites at once. ## Key arguments 1. File-based (config-as-code) governance is portable by construction — the same policy file can be copied to every site in a fleet, avoiding per-site database toggling. 2. Shipping v1 with an openly-flagged gap (no marketing material) is treated as good practice, not a weakness to hide. ## Claim atoms ### File-based governance persists policy across many WordPress sites > [!quote] ID:rw_pending > "a plug-in to control feature availability with files, making it easy to persist across a bunch of WordPress sites." Where/why: the plugin's stated mechanism and benefit, straight from the release tweet. Relevant to fleet/multi-site governance and the WP 7.1 feature-flags/canary conversation. ### Shipping v1 candidly beats waiting for marketing polish > [!quote] ID:rw_pending > "It doesn't have good marketing images or material yet but I finally packaged up and released v1 of Governance Guardrails" Where/why: models low-ego, ship-then-polish release behavior — the author names the gap rather than concealing it. ## Permanent candidates - **File-based governance persistence across a fleet** — promoted below; it is a real, reusable claim about how config-as-code governance works, even though the source itself is thin (a single tweet). - The "ship candidly, flag the gap" behavior is a minor pattern, not promoted — it restates a general norm (honest v1 shipping) already well covered elsewhere in the vault rather than adding new evidence. ## Processing checklist - [ ] Install and inspect the plugin's actual file format + enforcement layer once documentation exists - [ ] Compare against WP 7.1's native feature-flag direction when both are documented - [x] Connect into the relevant MOC — [[3. Resources/MOCs/Open Source Governance MOC]] ## Links - [[3. Resources/MOCs/Open Source Governance MOC]] — a config-as-code governance tool entering the WordPress plugin ecosystem - [[3. Resources/MOCs/WordPress Hosting Security Stack MOC]] — file-driven policy raises file-integrity and write-permission questions relevant to fleet security posture - [[3. Resources/Permanent Notes/File-Based Configuration Lets Governance Policy Travel With the Codebase]] — extends: the permanent note promoted from this tweet's claim that file-based policy persists across many sites - [[3. Resources/Permanent Notes/Default-Off Feature Flags Decouple Shipping Speed From Production Risk]] — contrasts: runtime flags gate exposure per environment, while this plugin gates features through files - [[3. Resources/Permanent Notes/Prose Configuration Cannot Substitute for a Real Access Boundary]] — applies-in: a policy file only governs if something outside the site owner's reach enforces it, the file-integrity question raised above