Matt
331b67dae0
Full pipeline/track/stage architecture replacing the legacy round system. Schema: 11 new models (Pipeline, Track, Stage, StageTransition, ProjectStageState, RoutingRule, Cohort, CohortProject, LiveProgressCursor, OverrideAction, AudienceVoter) + 8 new enums. Backend: 9 new routers (pipeline, stage, routing, stageFiltering, stageAssignment, cohort, live, decision, award) + 6 new services (stage-engine, routing-engine, stage-filtering, stage-assignment, stage-notifications, live-control). Frontend: Pipeline wizard (17 components), jury stage pages (7), applicant pipeline pages (3), public stage pages (2), admin pipeline pages (5), shared stage components (3), SSE route, live hook. Phase 6 refit: 23 routers/services migrated from roundId to stageId, all frontend components refitted. Deleted round.ts (985 lines), roundTemplate.ts, round-helpers.ts, round-settings.ts, round-type-settings.tsx, 10 legacy admin pages, 7 legacy jury pages, 3 legacy dialogs. Phase 7 validation: 36 tests (10 unit + 8 integration files) all passing, TypeScript 0 errors, Next.js build succeeds, 13 integrity checks, legacy symbol sweep clean, auto-seed on first Docker startup. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
44 lines
990 B
Markdown
44 lines
990 B
Markdown
# Assignment Engine Specification
|
|
|
|
## Objective
|
|
Generate high-quality, fair assignments while guaranteeing eligible project coverage.
|
|
|
|
## Inputs
|
|
|
|
- stage ID
|
|
- eligible project set
|
|
- assignee pool
|
|
- required reviews per project
|
|
- assignment strategy config
|
|
- availability and COI policies
|
|
|
|
## Hard Constraints
|
|
|
|
1. COI exclusion
|
|
2. role/status eligibility
|
|
3. explicit max-load cap
|
|
4. minimum review floor
|
|
|
|
## Soft Scoring Dimensions
|
|
|
|
- expertise overlap
|
|
- bio/project similarity
|
|
- availability weighting
|
|
- workload balancing
|
|
- optional geo diversity
|
|
- optional prior-familiarity weighting
|
|
|
|
## Guarantee Rules
|
|
|
|
1. No eligible project left uncovered.
|
|
2. If capacity insufficient, create overflow assignments with warning markers.
|
|
3. Preview and execution must match constraints and scoring semantics.
|
|
|
|
## Output Contract
|
|
|
|
- assigned count
|
|
- uncovered count (must be zero unless in explicit error mode)
|
|
- overflow assignment list
|
|
- conflict skips list
|
|
- fairness metrics (median load, max load)
|