{"version":"2.1.248","anchor":"new-gate-tengu-foamy-spring-on-by-default-and-fail-open","canonical_anchor":"new-gate-tengu-foamy-spring-on-by-default-and-fail-open","heading":"New gate tengu_foamy_spring , on by default and fail-open","tier":"soon","area":"Feature Gates","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/new-gate-tengu-foamy-spring-on-by-default-and-fail-open","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### New gate `tengu_foamy_spring`, on by default and fail-open\n\nA new gate is on by default and stays on even if its reader fails.\n\n**What**\n\nA gate named `tengu_foamy_spring` is read through a small registry that holds one reader. It returns true when no reader is registered, treats anything other than an explicit false as enabled, and stays enabled if the reader throws. The compiled fallback is true, so it is live unless remote config turns it off. What it actually guards is not visible from the gate code itself.\n\n**Evidence**\n\n`tengu_foamy_spring`\n\n- Area: Feature Gates\n- Tier: Nothing to try yet\n- Useful: 1\/5\n- Signal: 3\/5\n- Present in the build but not switched on"}