# 08. Open Questions For Flow Owners

## 1) Resolved Decisions (Captured)
As of Sunday, February 15, 2026, the following decisions are confirmed:

1. 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.

2. Soft-cap buffer:
- Default soft-cap buffer is `+10`.

3. Startup/concept ratio behavior:
- Ratio is a slight bias/suggestion only.
- It must not be fully deterministic.
- Onboarding must explicitly disclose this to judges.

4. Mode A pull-out behavior:
- Pull-out from main pool is admin-confirmed (not automatic).

5. Mentoring promotion authority:
- Promotion to official submission is allowed for team lead + admin.

6. Admin member invite pre-assignment:
- Both modes should be supported when possible:
  - assignment intent mode
  - direct policy-validated assignment mode

7. 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.

8. Result unlock policy:
- Unlock after finalization is allowed only for super admins.
- Unlock must require explicit reason/audit metadata.

9. Jury identity naming:
- Main and award juries are custom-labeled.
- Runtime behavior binds to jury purpose/stage contracts, not fixed `Jury1/Jury2/Jury3` labels.

## 2) Remaining P0 Questions (Need Before Schema Freeze)
None as of Sunday, February 15, 2026.

## 3) Remaining P1 Questions (Needed Before UI/Router Refactor)

1. 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?

2. Mentoring stage applicability:
- Is mentoring strictly finalists-only by default, or configurable to include semi-finalists?

3. Document mutability after lock:
- Can admins replace locked submissions post-deadline, and should applicants see replacement history?

4. Audience reveal timing:
- Should audience totals be visible to Jury 3 in real time or only at deliberation start?

## 4) Remaining P2 Questions

1. Reporting visibility:
- Should per-jury cap/bias compliance be visible to all admins or only super admins?

2. Override transparency:
- Which override details are visible to jury users versus admin-only?

3. Applicant communication policy:
- Which exact transitions trigger applicant notifications?

4. Tie-break policy ordering:
- Confirm strict precedence when ties remain after configured scoring.

## 5) Invite/Onboarding Follow-Up Questions

1. Invitation expiry policy:
- Keep role-specific invite expiry differences (7-day admin invite vs 30-day team invite) or unify?

2. 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?

3. CSV template scope:
- Should CSV bulk invite support explicit jury binding + stage + pre-assignment mode columns?

## 6) Suggested Defaults For Remaining Items
1. Judges can edit cap/bias in onboarding only when admin enables this per jury.
2. Mentoring defaults to finalists-only, with optional semi-finalist extension.
