Handle deputy assignment after a bias decision
After a bias vote is completed, the secretary cannot reliably see or assign the canonical deputy. Earlier examples showed a vacant approved seat with no discoverable post-decision action, and meeting 11 showed an active Langbein assignment while the processed proposal editor displayed only “Ingen vara”. Additional stress evidence from meeting 6: Councillor 14 was unanimously declared inhabil with Deputy 11 and canonical participants correctly retained Deputy 11, but reopening the processed proposal omitted Deputy 11 from the selector and showed no selected value. A title-only save preserved canonical state, proving this is form presentation/workflow drift. Make processed forms read-only with the retained deputy or provide an explicit audited reassignment flow; never present a blank/contradictory selection. Preserve completed outcome, history, eligibility revalidation, and active-poll safeguards.
Checklist
0 of 4 complete- Confirm the intended product flow: reset and revote versus post-decision deputy assignment
- Make the chosen flow discoverable and explicit in the secretary UI
- Preserve the decided bias outcome and canonical audit history when changing only deputy fulfillment
- Add eligibility, active-poll, controller, and regression coverage
- Area
- Kaukus
- Kind
- Feature
- Priority
- High
- Task ID
tsk_v6m9eys9gv- Updated