The role answer prop keys and states. A role change is a CROSS-ENGINE SWAP — master and slave
are two different engines in reac-pw, each with its own socket, thread and (master only) the
segment lock — so the segment passes through a window owning neither, answered
role_reestablish_pending, and reaches applied only when the NEW engine performs the role.
WHAT "PERFORMS" MEANS DIFFERS PER END, which is why there is a third answer the daemon
publishes and this file does not declare: a master performs its role by pacing its own wire
(box or no box), while a recorder performs its role only once a desk has ENROLLED it, so one
hunting a desk that is not there answers role_hunting and never applied. That member is
reac-pw's own answer-side vocabulary and is not in libreac's header yet — the same order rate's
answer props travelled in — so it is NOT mirrored here; the row that reads it declares it as a
travel and keeps the field a string, the way every other reac-pw vocabulary reaches a client.
The role answer prop keys and states. A role change is a CROSS-ENGINE SWAP — master and slave are two different engines in reac-pw, each with its own socket, thread and (master only) the segment lock — so the segment passes through a window owning neither, answered
role_reestablish_pending, and reachesappliedonly when the NEW engine performs the role.WHAT "PERFORMS" MEANS DIFFERS PER END, which is why there is a third answer the daemon publishes and this file does not declare: a master performs its role by pacing its own wire (box or no box), while a recorder performs its role only once a desk has ENROLLED it, so one hunting a desk that is not there answers
role_huntingand neverapplied. That member is reac-pw's own answer-side vocabulary and is not in libreac's header yet — the same order rate's answer props travelled in — so it is NOT mirrored here; the row that reads it declares it as a travel and keeps the field a string, the way every other reac-pw vocabulary reaches a client.