The gatekeeper is the keeper of every gate. This is every on/off switch, setting and flag, sorted into where each one belongs. Pick a call on each row; picks save for everyone.
The four places a switch can go.Gatekeeper if a customer, tenant or vendor would notice it: it goes on the customer page under its module. Platform level if it's our own plumbing (emergency off switches, timeouts, test settings): staff-only, one click for everyone. Just ship it if it's a fix or safety rule hiding behind a switch. Delete if nothing uses it.
What the columns mean
Scope: who it applies to. Platform means everyone at once; company and building are per customer.
Kind: module (Off / Supervised / Live), feature (a customer-facing on/off or mode), kill switch (emergency off for one capability), setting (a value like a timeout or model), test/safety, or a hard-coded list.
Owner: who should flip it. Fede turns customer features on at real customers.
Source: where it lives today: the settings registry, hosting config, a platform row, a field on a record, a hard-coded list, or the code itself.
Customer-visible: whether it should show on that customer's page. Platform-level switches never do.
On today?: On, Off, Partly (some companies or buildings), Set (holds a value), Unused, or Unknown.