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>
40 lines
1.1 KiB
Markdown
40 lines
1.1 KiB
Markdown
# Award Track and Governance Specification
|
|
|
|
## Award Track Principle
|
|
Awards share the same orchestration engine as the main competition; they are tracks, not detached side workflows.
|
|
|
|
## Routing Modes
|
|
|
|
- `PARALLEL`: award path runs while main path continues
|
|
- `EXCLUSIVE`: project exits main continuation path and runs award-only
|
|
- `POST_MAIN`: award route starts after configured main gate
|
|
|
|
## Governance Modes
|
|
|
|
- `JURY_VOTE`: assigned award jurors vote
|
|
- `AWARD_MASTER`: designated award owner decides within scope
|
|
- `ADMIN`: program/super admin decides
|
|
|
|
## Decision Requirements
|
|
|
|
- every winner/finalist decision emits audit entry
|
|
- manual overrides require reason code and text
|
|
- tie-break policy explicit and deterministic
|
|
|
|
## Permission Enforcement
|
|
|
|
- governance mode checked server-side on every decision mutation
|
|
- unauthorized attempts return `FORBIDDEN`
|
|
|
|
## Representative Decision Payload
|
|
|
|
```json
|
|
{
|
|
"awardId": "award_123",
|
|
"decisionMode": "AWARD_MASTER",
|
|
"winnerProjectId": "project_789",
|
|
"reasonCode": "SPONSOR_DECISION",
|
|
"reasonText": "Award sponsor selected based on category fit"
|
|
}
|
|
```
|