assess-assignment

name	assess-assignment
description	Assessment guide for evaluating Digital Agency Primer module assignments. Used by the assessor agent — not invoked directly. Covers how to evaluate evidence against SLT criteria, apply rubrics, and provide constructive feedback.

Assess Assignment

How to evaluate a "Digital Agency Primer" module assignment. This skill is read by the assessor agent before evaluating any submission.

Assessment Protocol

Step 1: Read the Assignment File

Read content/digital-agency-primer/assignments/m{moduleCode}-assignment.md for the module being assessed. This file defines:

• Exactly what evidence each SLT requires
• What a strong answer looks like
• The format expected for the module artifact

Also read the SLT definitions from content/digital-agency-primer/01-slts.md for the canonical wording.

Step 2: Evaluate Each SLT

For each SLT in the module, assess the learner's evidence:

Written responses (explain, describe, compare, evaluate):

• Does the answer demonstrate the capability the SLT names?
• Does it include the specific elements the assignment says a "strong answer" should include?
• Is the reasoning sound, or is it vague hand-waving?
• Minor phrasing differences from the rubric are fine — the reasoning matters, not the wording.
• Does the learner avoid exposing passwords, keys, recovery codes, account numbers, or sensitive personal details?

Artifact submissions (maps, notes, checklists, plans):

• Does the artifact include every deliverable requested by the assignment?
• Are examples concrete enough to show the learner can apply the idea?
• Are risks, controls, and next steps named specifically enough to be useful?

Step 3: Assess Feedback Section

Part 2 of every assignment is feedback on the module. This is required but not graded.

• Check that it's present and non-empty
• If the learner wrote something substantive, acknowledge it specifically
• If they wrote "everything was fine" — accept it
• Note any actionable feedback that could improve the course

Step 4: Determine Verdicts

Per-SLT verdicts:

Verdict	Criteria
Pass	Evidence is present AND demonstrates the SLT capability. Minor gaps in phrasing are OK if reasoning is sound.
Revise	Evidence is present but incomplete, vague, unsafe to share, or partially incorrect.
Missing	No evidence provided for this SLT.

Module verdict:

Verdict	Criteria
Accept	All SLTs pass AND feedback section present
Revise	One or more SLTs are Revise or Missing. List exactly which ones.

Step 5: Write the Assessment

Use this structure:

## Module {moduleCode} Assessment

### SLT {moduleCode}.1 — {title}
**Verdict:** Pass | Revise | Missing
{2-3 sentences: what was strong, what needs work. Be specific.}

### Feedback Section
{Acknowledge the learner's feedback. Quote anything particularly useful.}

### Module Verdict: Accept | Revise
{If Accept: congratulate. Name what the learner can now do.}
{If Revise: list exactly which SLTs need revision and what's missing. Be constructive.}

Calibration Notes

This course teaches practical digital agency through the learner's own online life. The strongest signal of understanding is when a learner can name who controls something, what can be verified or backed up, and what practical action would reduce risk without oversharing private information.

Common revision patterns:

• Learner paraphrases the lesson without adding their own understanding → Revise. Ask them to explain in their own words.
• Learner's artifact is generic rather than grounded in a specific account, resource, risk, or contribution path → Revise. Ask them to make concrete choices.
• Learner includes secrets or sensitive personal details → Revise. Ask for a redacted version.
• Learner wrote "I don't know" for one SLT → Missing. Point them back to the specific lesson.

Resubmissions: When evaluating a resubmission, focus on whether the specific gaps from the previous assessment were addressed. Don't re-evaluate SLTs that already passed unless the learner changed their answer. Acknowledge improvement.

Module-Specific Notes

M101 (Own Your Digital Identity)

• Look for a clear distinction between platform-granted access and learner-controlled proof.

M102 (Map Your Digital Dependence)

• The map should name real dependencies, who controls access, what can be backed up, risk level, and one next step.

M103 (Verify Before Trusting)

• The verification note should include the resource, requested action, evidence found, warning signs, and a decision.

M104 (Protect What Matters)

• The recovery plan should be practical and privacy-preserving. It must not reveal secrets.

M105 (Publish and Participate Openly)

• The contribution path should match the learner's interests and include a specific first action.

Input/Output Protocol

Input: Module code + learner's evidence (written responses, code, designs) Output: Structured assessment with per-SLT verdicts and module verdict.