letsbe
/
MOPC-App
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
MOPC-App/docs/round-redesign-architecture.../mixed-round-design-implemen.../master-implementation-plan.md

3.4 KiB
Raw Blame History

Master Implementation Plan

Program Objective

Rebuild MOPC round orchestration from a round-centric model into a stage-native pipeline model that is easier to configure, more deterministic, and robust for main competition plus special awards and live finals.

Program Constraints

  • Preserve existing visual language and core UI component style.
  • Complete architecture rebuild is allowed and encouraged.
  • Delivery must be production-safe and verifiable.
  • Release requires one atomic cutover commit after full validation.

Hard Invariants

  1. Every state transition is explicit, validated, and auditable.
  2. Every override action captures reasonCode + reasonText + actor metadata.
  3. No eligible project is left unassigned unless explicitly flagged as overflow with admin visibility.
  4. Live active project state is admin-cursor driven.
  5. Award routing behavior is explicit per award (parallel, exclusive, post_main).
  6. Event contracts are deterministic and machine-readable.
  7. At release, no runtime dependency on legacy roundId orchestration semantics remains.

Phase Chain

  1. Phase 00: Contract freeze
  2. Phase 01: Schema and runtime foundation
  3. Phase 02: Backend orchestration engine
  4. Phase 03: Admin control-plane UX
  5. Phase 04: Participant journeys
  6. Phase 05: Special awards governance
  7. Phase 06: Platform dependency refit
  8. Phase 07: Validation and release

Required Deliverables by Phase

  • Phase 00: locked contracts, decision log, authz matrix, initial risk register
  • Phase 01: canonical schema spec, migration/cutover scripts, reseed spec, integrity checks
  • Phase 02: transition/routing/filtering/assignment/live runtime implementation specs
  • Phase 03: wizard IA, advanced editor spec, form behavior and safety guardrails
  • Phase 04: applicant/jury/audience runtime and UX contracts
  • Phase 05: award governance modes and decision workflow implementation
  • Phase 06: module-by-module refit completion + legacy symbol sweeps
  • Phase 07: full test evidence, performance evidence, release runbook and sign-off

Entry and Exit Criteria (Program Level)

Entry

  • Shared contracts and decisions are locked.
  • Team alignment on cutover model and no-compatibility policy.

Exit

  • All phase acceptance gates complete.
  • Test matrix green for U/I/E/P suites.
  • Performance and resilience evidence approved.
  • Legacy symbol sweeps are empty.
  • Release evidence report signed by Engineering + Product + Operations.

Release Blockers

  1. Any failing acceptance gate.
  2. Any unresolved CRITICAL or HIGH risk without approved mitigation.
  3. Any missing test evidence for mandatory scenario IDs.
  4. Any legacy orchestration symbol found in runtime code paths.

Timeline Model

  • Phase 00: 2-3 days
  • Phase 01: 1-1.5 weeks
  • Phase 02: 1.5-2.5 weeks
  • Phase 03: 1-1.5 weeks
  • Phase 04: 1-1.5 weeks
  • Phase 05: 0.75-1.25 weeks
  • Phase 06: 1-1.5 weeks
  • Phase 07: 1 week

Total estimate: 8-11 weeks depending on test depth and refit complexity.

Evidence Standards

Every acceptance gate requires at least one of:

  • Unit/integration/E2E output
  • API response captures
  • deterministic symbol sweeps
  • migration integrity query output
  • performance benchmark output
  • release runbook logs

Enforcement Notes

  • No phase skipping.
  • No deferred blocker carry-forward.
  • No "ship and patch later" for contract-level gaps.