Membership Predicate Test¶
Decision test — instantiates Complement Space Mapping
Runs the in-or-out rule on a single case and returns one of three verdicts — member, non-member, or genuinely unknown — never collapsing 'we can't tell' into 'outside.'
Membership Predicate Test is the executable rule that decides, for one case at a time, whether it belongs to the focal subset. Its defining move among its siblings is that it operates at the level of the individual case and returns a three-valued verdict — in A, not in A, or undetermined — refusing to let a case the predicate cannot evaluate silently fall into the complement. This is the mechanism that keeps "we don't have the data to decide" from masquerading as "confirmed outside," which is the single most common way complement reasoning goes wrong. Where the query differences whole tables, this test adjudicates the one record in front of you and knows when it cannot.
Example¶
A fintech's onboarding system must decide whether an applicant belongs to the subset "accounts cleared for the beta lending product." The membership predicate is explicit: cleared if identity is verified and the applicant is in a supported state and the credit file returned a score. The test runs it on applicant #7731. Identity: verified. State: supported. Credit file: no response yet — the bureau timed out. A naive gate would read "score present? no → not cleared → route to the everyone-else bucket," treating a pending case as a rejection. The three-valued test does not: it returns undetermined, routes the applicant to a hold queue for re-check, and only ever emits "not cleared" when the predicate has actually evaluated to false on known inputs. The result is that the complement of "cleared accounts" contains genuine non-qualifiers, not a mix of non-qualifiers and people the system simply had not finished looking at.
How it works¶
- State the predicate as a Boolean over known inputs. Membership is a rule — a conjunction or decision tree of testable conditions — not a hand-curated list, so any case can be run through it.
- Evaluate under an explicit knowledge model. Decide up front whether an absent input means "false" (closed-world) or "unknown" (open-world); the test carries this choice rather than defaulting to it silently.[n1]
- Emit three outcomes, not two. Return member, non-member, or undetermined, and route each differently — the undetermined verdict is a first-class output, not an error.
- Keep the unknowns separate. Undetermined cases are held apart from confirmed non-members so that neither the subset nor the complement is contaminated by cases the rule never actually decided.
Tuning parameters¶
- Knowledge assumption — closed-world (missing = false) versus open-world (missing = unknown); the former shrinks the unknown pool but manufactures false non-members, the latter is honest but grows a queue someone must clear.
- Predicate strictness — how many conditions must hold and how tightly; tighter predicates put more cases outside A, looser ones pull marginal cases in.
- Undetermined routing — whether unknowns go to a hold queue, a default assignment, or human review; the choice trades throughput against correctness.
- Evidence sufficiency threshold — how complete the inputs must be before the test is willing to return a definite verdict at all.
- Re-evaluation trigger — whether an undetermined case is automatically re-tested when its missing input arrives, or waits for a manual rerun.
When it helps, and when it misleads¶
Its strength is precision at the case level: it gives a defensible, repeatable answer for any single unit and — critically — an honest "don't know" when the inputs are incomplete, which prevents the complement from silently swelling with cases that were never really decided.
It misleads when the predicate is treated as more knowledgeable than it is. Under a closed-world assumption, every gap in the data becomes a confident "not a member," so a poorly-fed predicate quietly manufactures a huge, spurious complement — the classic misuse is running a strict gate over sparse records and reading the resulting "not in A" as a finding rather than an artifact of missing inputs. The test also decides membership but says nothing about what non-membership means downstream. The guarding discipline is to make the closed- versus open-world choice explicit, keep undetermined as a live third state with its own queue, and never let an informal eyeball check of the outputs substitute for actually re-running the predicate when new inputs land.
How it implements the components¶
Membership Predicate Test realizes the per-case adjudication side of the archetype — deciding one unit's status and being honest when it cannot:
membership_predicate— it is the executable in-or-out rule, applied to an individual case as a Boolean over testable conditions.unknown_state_separator— its three-valued output holds cases the predicate cannot decide in a distinct undetermined state, apart from confirmed non-members.
It does not enumerate the whole complement as data — that is complement_inventory in Set-Difference Query — and it does not constrain how a non-member verdict may be interpreted downstream; prohibiting the "not in A therefore the opposite" leap is opposite_property_test and downstream_use_constraint in Downstream Inference Guardrail.
Related¶
- Instantiates: Complement Space Mapping — it supplies the case-level membership verdicts everything else builds on.
- Consumes: Universe–Subset–Complement Map supplies the focal-subset definition the predicate operationalizes.
- Sibling mechanisms: Universe–Subset–Complement Map · Set-Difference Query · Inclusion/Exclusion Matrix · Disjointness and Exhaustiveness Review · Residual Case Backlog · Downstream Inference Guardrail · Complement Sensitivity Checklist · Universe Scope Change Log
Editorial Notes¶
Form Classification¶
Form family: Decision, Gate & Allocation
Rationale: Membership Predicate Test operates as a case-specific gate, selection, routing, prioritization, or resource disposition because it runs the in-or-out rule on a single case and returns one of three verdicts — member, non-member, or genuinely unknown — never collapsing 'we can't tell' into 'outside.'.
Independent corroboration: The frozen evidence defines Membership Predicate Test as 'Runs the in-or-out rule on a single case and returns one of three verdicts — member, non-member, or genuinely unknown — never collapsing 'we can't tell' into 'outside.'', so its operative form is Decision, Gate & Allocation.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Mathematics
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Universal
Rationale: Applying an in-or-out predicate is foundational set-theoretic and logical practice.
Related originating lineages:
- Computer Science & Software Engineering — Three-valued logic and database null semantics preserve an unknown result operationally.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Independent reviewer agreement; high confidence.
Notes¶
[n1] The closed-world assumption (CWA), from database theory and knowledge representation, holds that anything not known to be true is false — convenient, but it turns every missing fact into a positive non-membership claim. The open-world assumption instead treats the unknown as unknown. Datalog and SQL lean closed-world; RDF/OWL lean open-world. Which one a predicate uses decides whether its complement is honest. ↩