Dispatch

Who sees a Task first, and for how long is it theirs alone?

Set dispatch on the Pool or on one role to override the default. { cascade: 3 } offers each round to three members at once.

The legal example names parties, so its Tasks go by cascade. One member turns work around the same day and another in two days, so the faster one is offered it first. A pass hands it on at once, and a window that runs out hands it on too:

→ POST /matters {"service":"contract-review","contract":"lease.pdf","client":{"name":"Ada Lovelace","email":"signs@example.test"},"client_region":"US-CA","max_usd":99,"key":"lease"}

← job_7Hq2 · waiting · on claim · $99.00 held · advise · tsk_7Hq2

# dispatch cascade: offered to mbr_7Hq3 alone, for a window
  mbr_7Hq3      GET /tasks → tsk_7Hq2
  mbr_7Hq2      GET /tasks → nothing
  mbr_eligible  GET /tasks → nothing

→ POST /reviews/tsk_7Hq2/pass   # as mbr_7Hq3

# a pass moves it on at once: mbr_7Hq2
  mbr_7Hq3      GET /tasks → nothing
  mbr_7Hq2      GET /tasks → tsk_7Hq2
  mbr_eligible  GET /tasks → nothing

→ POST /test_clocks/default/advance {"to":"61min"}

# the window ran out: the sandbox's eligible member, last in every cascade
  mbr_7Hq3      GET /tasks → nothing
  mbr_7Hq2      GET /tasks → nothing
  mbr_eligible  GET /tasks → tsk_7Hq2

The sandbox's eligible member is last in every cascade, so a walk always ends with a member who can take it.

A member's feed lists every Task offered to them in one order, whichever brand posted it: fit first, then the fee per estimated hour, then the due date. Placement, the brand that runs the Pool and a brand's plan never move a Task up. Only affinity gives first refusal, and an exporter's preference for its own brands exists only as a declared export.first, printed on every importer's check and on the door's /terms.

A member's own declarations filter their feed before any rank runs. None of them is ever scored:

What those declarations kept from them is theirs to read, at /me/missed, and never a Task eligibility kept from them:

cascade ranks eligible members by rank: fit (what they declared at join: areas, minimum fee, hours), then track, then speed. A member still on probation ranks by fit and speed alone until their probation.tasks are done. Tiers sit above rank and offer to the top eligible tier first. Neither ever overrides eligibility.

affinity gives the member who did a subject's last Task first refusal on its next one, for its window. A member who is ineligible by then is skipped.

The owner, or a staff role, names the member a Task goes to from the console. The member must be eligible. A client's direction after a decline names the next member the same way, and they are offered it alone.

Worked in: the closers' Pool, ranked by fit, then track.