The master switch.
Off means false. A simple boolean gate makes the first decision explicit.
OFF / FALSE
FEATURE CONTROL / MADE INSPECTABLE
A SWITCH.
A RULE.
A REASON.
See what a flag does, who matches, and why the answer changes. A working local bench for the decisions behind a release.
LATCH / EXAMPLE CIRCUITLOCAL
01 / BOOLEAN GATE
example-switch
INPUTenabled
→CHECKboolean
→OUTPUTtrue
SIMULATED RESULTTRUE
The example switch is enabled.
No remote system attached.Try conditions + rollout ↗
THE DECISION IS THE PRODUCT
DON'T JUST
FLIP A SWITCH.
FOLLOW THE SIGNAL.
A percentage without an identity is a guess. A rule without a trace is a mystery. Latch makes the path from configuration to result visible.
THREE PARTS.
ONE EVALUATION.
Open the rule bench ↗The matching context.
Plan, country, beta status and account age. Every condition must match.
planequalspro
The stable rollout.
The same flag and subject produce the same bucket. Change the percentage, not the identity.
1285<5000
NO BLACK-BOX MOMENT
THE ANSWER
COMES WITH
ITS WORKING.
Inspect the boolean, each condition and the exact rollout threshold. Test fictional attributes and see what changes.
Evaluate a sample subject ↗SUBJECT / sample-001STAGING SIMULATION
- ✓Master switchEnabled
- ✓plan equals proContext matched
- ✓Bucket 1285 < 5000Included in the 50% rollout
RETURNtrue
SAME FLAG.
DIFFERENT
SIMULATIONS.
Compare Lab, Staging and Release side by side.
These are local examples, not connected environments.
BUILT TO BE TAKEN APART
A SMALL MODEL.
A COMPLETE
WORKING LOOP.
Change a boolean. Add a condition. Move a rollout from 12% to 13%. Evaluate the same subject again and read the reason.
Save the local configuration, compare the simulations, or export JSON. Nothing connects to a service, account or SDK.
See the exact hash and boundary rules ↗YOUR NEXT DECISION, IN PLAIN SIGHT