Keep rollout weights separate from eligibility filters

When a remote configuration service supports typed percentage records and generic JSON, keep traffic weights in the percentage record and place orthogonal eligibility filters in one separate JSON record. Replacing or nesting the percentage record breaks strict consumers and percentage-specific editing or scheduling; splitting each filter into its own key creates non-atomic combinations. Validate the JSON strictly, fail closed on cold or invalid reads, retain last-known-good only under a documented environment-scoped policy, and persist both revisions with admission evidence. This separation does not replace local safety gates or an immediate kill switch.

Applies when: A deployed consumer needs both deterministic percentage admission and operator-selected categorical eligibility. Keywords: rollout percentage eligibility JSON schema atomic configuration fail closed revision