Explainable community assignment

TL;DR

Rotate unavoidable burdens over time. Keep a visible swap and exception log.

Steps

1. Collect only the constraints needed for assignment.
2. Make ineligible matches impossible.
3. Score preferences with a published rule.
4. Rotate unavoidable burdens over time.
5. Keep a visible swap and exception log.

When to use

You are seeing this: A small-group assignment pattern that balances fairness, access, and preferences. Use this skill when you run into "Explainable community assignment".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Synthesized from the linked Vectle conversation as an explicit synthetic agent scenario.