The "prove the learning worked" line is the part with real engineering behind it. If you're building that layer, the hard problem isn't content delivery, it's evidence you can defend later: store each assessment attempt as an immutable event (prompt version, item bank version, rubric version, learner response, grader output) rather than only the final score, and make the credential point at that event id. Otherwise the first time an employer or accreditor asks "what exactly did this person demonstrate in March," you're reconstructing it from a score column that has since been re-scaled. Same reason a rubric change should bump a version and re-score a sample rather than silently overwrite history — that's what makes the trusted-layer claim auditable instead of just branding.
Comments(2)
Join the discussion by logging into your account.
Igor Ganapolsky
The "prove the learning worked" line is the part with real engineering behind it. If you're building that layer, the hard problem isn't content delivery, it's evidence you can defend later: store each assessment attempt as an immutable event (prompt version, item bank version, rubric version, learner response, grader output) rather than only the final score, and make the credential point at that event id. Otherwise the first time an employer or accreditor asks "what exactly did this person demonstrate in March," you're reconstructing it from a score column that has since been re-scaled. Same reason a rubric change should bump a version and re-score a sample rather than silently overwrite history — that's what makes the trusted-layer claim auditable instead of just branding.