EPIC: shift /users /estudiantes /docentes from admin-dashboard mgmt to self-managed roster (JTP/Ayudante/Adjunto/students self-pick relationships + self-confirmation workflow)

Sub-tickets

Activity

• wi-cli-venus created · 2026-06-09
• wi-cli-venus spec · 2026-06-09
  Elazar (2026-06-09): admin staff will NOT manually fix hundreds of student/teacher relationship mistakes. Pivot relationship-mgmt from admin-dashboard (/users /estudiantes /docentes — used by nobody but Elazar, who doesn't actually use it) to SELF-MANAGED edges + self-confirmation handshake: JTP/Ayudante pick Adjunto+comisión+students; students pick JTP; Adjunto picks JTPs/Ayudantes. Mutual picks need both-sides confirmation before edge is authoritative. Epic anchor: needs PM design/brainstorm (proposed-vs-confirmed edge model, who-can-propose matrix, conflict resolution, migration off admin-pick) before coder dispatch. Aligns w/ no-admin-evidence-autoassign.
• wi-cli-venus decision · 4w ago
  Sweep finding, coder02-enamel-cc 2026-09-12, read-only: this EPIC has NO children, NO PM design or brainstorm artifact, and NO shipped commits matching the proposed/confirmed edge model. Its own description asks for PM staffing. MARS HAS NO PM - pm-mars-cc reads NOT-FOUND, unregistered, no pane, measured the same night. So the row names a role that does not exist, which is why it has not moved. Not reassigning it to a coder: an epic with no design artifact handed to a coder becomes scope invented at the keyboard, and this one proposes changing who controls roster relationships - JTP, Ayudante, Adjunto and students self-picking and self-confirming - which is a product and governance decision about a real catedra, not a build. Recorded as a STAFFING decision for Elazar: either mars gets a PM, or he takes the design call himself, or this epic is closed rather than left as permanent queue depth. Leaving it backlog-unassigned is the one option that costs something every time someone sweeps the board.