Matt
6ca39c976b
All checks were successful
Build and Push Docker Image / build (push) Successful in 7m45s
Replace Pipeline/Stage system with Competition/Round architecture. New schema: Competition, Round (7 types), JuryGroup, AssignmentPolicy, ProjectRoundState, DeliberationSession, ResultLock, SubmissionWindow. New services: round-engine, round-assignment, deliberation, result-lock, submission-manager, competition-context, ai-prompt-guard. Full admin/jury/applicant/mentor UI rewrite. AI prompt hardening with structured prompts, retry logic, and injection detection. All legacy pipeline/stage code removed. 4 new migrations + seed aligned. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
3.3 KiB
3.3 KiB
08. Open Questions For Flow Owners
1) Resolved Decisions (Captured)
As of Sunday, February 15, 2026, the following decisions are confirmed:
- Final confirmation scope:
- Unanimity applies by default to category winners and jury-based award winners.
- Admin override must be possible in both cases with full audit reasoning.
- Some special awards can use a single-judge decision mode after eligibility filtering.
- Soft-cap buffer:
- Default soft-cap buffer is
+10.
- Startup/concept ratio behavior:
- Ratio is a slight bias/suggestion only.
- It must not be fully deterministic.
- Onboarding must explicitly disclose this to judges.
- Mode A pull-out behavior:
- Pull-out from main pool is admin-confirmed (not automatic).
- Mentoring promotion authority:
- Promotion to official submission is allowed for team lead + admin.
- Admin member invite pre-assignment:
- Both modes should be supported when possible:
- assignment intent mode
- direct policy-validated assignment mode
- Jury absence during final confirmation:
- Quorum fallback is allowed.
- If a judge is absent, admins can either:
- replace the judge, or
- mark the judge as absent so they do not count toward required confirmation votes.
- Result unlock policy:
- Unlock after finalization is allowed only for super admins.
- Unlock must require explicit reason/audit metadata.
- Jury identity naming:
- Main and award juries are custom-labeled.
- Runtime behavior binds to jury purpose/stage contracts, not fixed
Jury1/Jury2/Jury3labels.
2) Remaining P0 Questions (Need Before Schema Freeze)
None as of Sunday, February 15, 2026.
3) Remaining P1 Questions (Needed Before UI/Router Refactor)
- Judge self-service onboarding controls:
- Are judges allowed to edit their own cap/bias preferences during onboarding for both main semi-final and finalist juries, or admin-only?
- Mentoring stage applicability:
- Is mentoring strictly finalists-only by default, or configurable to include semi-finalists?
- Document mutability after lock:
- Can admins replace locked submissions post-deadline, and should applicants see replacement history?
- Audience reveal timing:
- Should audience totals be visible to Jury 3 in real time or only at deliberation start?
4) Remaining P2 Questions
- Reporting visibility:
- Should per-jury cap/bias compliance be visible to all admins or only super admins?
- Override transparency:
- Which override details are visible to jury users versus admin-only?
- Applicant communication policy:
- Which exact transitions trigger applicant notifications?
- Tie-break policy ordering:
- Confirm strict precedence when ties remain after configured scoring.
5) Invite/Onboarding Follow-Up Questions
- Invitation expiry policy:
- Keep role-specific invite expiry differences (7-day admin invite vs 30-day team invite) or unify?
- Multi-role default landing:
- If a user is both jury and applicant team member, what is default post-login landing and should role-switch be mandatory?
- CSV template scope:
- Should CSV bulk invite support explicit jury binding + stage + pre-assignment mode columns?
6) Suggested Defaults For Remaining Items
- Judges can edit cap/bias in onboarding only when admin enables this per jury.
- Mentoring defaults to finalists-only, with optional semi-finalist extension.