Match a support request to every required capability

Require the complete capability set

Original local desk example: request T1 needs cantonese and exports. An agent is eligible only when every required capability is recorded, status is active and spare slots are positive. Status describes this fixture, not an employee attendance record. null means the relevant fact is unknown. A known failed condition establishes ineligibility even when another condition is unknown.

Keep each exclusion visible

Only A is eligible. B has more slots but lacks exports; C has both skills but is inactive. The result is an eligible set, not an automatic staff assignment. If several agents pass, this model does not choose among them.

1. Read required skills
2. Check each recorded skill set
3. Check status and slots
4. Retain the eligibility trace

Do not replace a missing skill record with an assumed capability.

Change a fact, then check the set

Use B’s exports checkbox to add/remove the capability. The local result changes from A to A,B and back; the source request still requires both skills. Reset restores the original three agents.

With A’s skills unknown, A is an unknown candidate; B and C still fail known conditions. Input lists contain at most 30 distinct IDs, skills are distinct nonempty labels, and slots are whole numbers 0–1,000 or null. Invalid values are rejected rather than partially assigned.

If the eligible set is unexpectedly empty, inspect the channel capacity example next. Impact priority remains a separate decision.