File size: 13,028 Bytes
077605d | 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 | {
"id": "animations-videos-141",
"source": "vas",
"artifact_type": "dynamic_media",
"category": "animations-videos",
"acceptance_groups": {
"G01": [
"IF01"
],
"G02": [
"IF02",
"IF03"
],
"G03": [
"IF04",
"IF06"
],
"G04": [
"IF05"
],
"G05": [
"IF07",
"IF38"
],
"G06": [
"IF08",
"IF09",
"IF10",
"IF12"
],
"G07": [
"IF11"
],
"G08": [
"IF13",
"IF14",
"IF15",
"IF16",
"IF17",
"IF18",
"IF19",
"IF20"
],
"G09": [
"IF21"
],
"G10": [
"IF22"
],
"G11": [
"IF23",
"IF24",
"IF25",
"IF26",
"IF28"
],
"G12": [
"IF27",
"IF29",
"IF30",
"IF31",
"IF32",
"IF33"
],
"G13": [
"IF34",
"IF35",
"IF36",
"IF37",
"IF39",
"IF40",
"IF41"
],
"G14": [
"IF42",
"IF43",
"IF44",
"IF45",
"IF46",
"IF47"
],
"G15": [
"IF48",
"IF50",
"IF51",
"IF52",
"IF53",
"IF54",
"IF55",
"IF56"
],
"G16": [
"IF49"
]
},
"provenance": {
"source": "artifactspec",
"original_id": "P141",
"legacy_task_id": "artifactspec-P141"
},
"acceptance_objectives": {
"G01": {
"title": "Required artifact language",
"dimension": "CP",
"scope": [
"Requirement: the delivered animation presents the teaching content in English."
],
"objective_key": "constraint:language"
},
"G02": {
"title": "Required artifact format, extent and duration",
"dimension": "CP",
"scope": [
"Requirement: the main film duration is between 45–60 seconds.",
"Requirement: the main film is a 1920×1080 MP4."
],
"objective_key": "constraint:format"
},
"G03": {
"title": "Required faithful previews and companion exports",
"dimension": "CP",
"scope": [
"Requirement: provide a smaller-size GIF preview file.",
"Requirement: provide five PNG checkpoint images in artifact/."
],
"objective_key": "constraint:preview"
},
"G04": {
"title": "Create a 45–60 second English teaching animation for junior developers who understand HTTP requests. Use the supplied RFC7636 and its Appendix B example. Deliver a 1920×1080 MP4, smaller GIF preview, editable animation source with regeneration instructions, five PNG checkpoints and notes.md in artifact/. No actual login, network requests, credentials or authorization-server implementation are needed.",
"dimension": "CP",
"scope": [
"Requirement: provide an editable animation source file."
],
"objective_key": "requirement:prompt.md:3"
},
"G05": {
"title": "Complete reproducibility and delivery documentation",
"dimension": "CP",
"scope": [
"Requirement: provide a notes.md file in artifact/.",
"Requirement: notes include the full example pair and the mismatch result."
],
"objective_key": "constraint:notes"
},
"G06": {
"title": "Show a client and two distinct endpoints within one authorization server: authorization and token. Label login/consent, browser redirects and other OAuth parameters as simplified or omitted; do not imply that a password is directly exchanged for the token in this flow. Animate messages and update corresponding state, rather than merely crossfading static slides.",
"dimension": "CP",
"scope": [
"Requirement: show the client in the visuals.",
"Requirement: show the two distinct endpoints, authorization and token, within the same authorization server with clear labels.",
"Requirement: label login/consent, browser redirects, and other OAuth parameters as simplified or omitted.",
"Requirement: advance by animating messages and synchronously updating the corresponding state, rather than merely crossfading static slides."
],
"objective_key": "requirement:prompt.md:5"
},
"G07": {
"title": "Evidence-bounded claims and truthful scenario identity",
"dimension": "CP",
"scope": [
"Requirement: do not imply that a password is directly exchanged for a token in this flow."
],
"objective_key": "constraint:evidence-boundary"
},
"G08": {
"title": "Follow the S256 flow: the client generates and retains a fresh high-entropy code_verifier for each authorization request; derive code_challenge = BASE64URL-ENCODE(SHA256(ASCII(code_verifier))), without padding. Send challenge and code_challenge_method=S256 in the authorization request, not the verifier. Show the server associating the challenge and method with the issued authorization code; leave the particular storage mechanism abstract. The token request supplies the code and original verifier. Recompute the challenge using the bound method and compare it with the associated value.",
"dimension": "CP",
"scope": [
"Requirement: the client generates and retains a fresh high-entropy code_verifier for each authorization request.",
"Requirement: derive the challenge according to the S256 formula: BASE64URL-ENCODE(SHA256(ASCII(code_verifier))) without padding.",
"Requirement: the authorization request sends code_challenge and code_challenge_method=S256.",
"Requirement: the authorization request does not send code_verifier.",
"Requirement: show the authorization server associating the challenge and method with the issued authorization code.",
"Requirement: keep the particular storage mechanism of the authorization server abstract and do not show specific implementation details.",
"Requirement: the token request carries the authorization code and the original verifier.",
"Requirement: the server recomputes the challenge using the bound method and compares it with the associated value."
],
"objective_key": "requirement:prompt.md:7"
},
"G09": {
"title": "Demonstrate two alternative redemption branches starting from the same issued-but-not-redeemed code state:",
"dimension": "CP",
"scope": [
"Requirement: both alternative redemption branches start from the same issued-but-not-redeemed authorization code state."
],
"objective_key": "requirement:prompt.md:9"
},
"G10": {
"title": "The original verifier matches. Continue ordinary OAuth validation; assuming the other checks pass, return an access token.",
"dimension": "CP",
"scope": [
"Requirement: in the success branch, after the original verifier matches, continue ordinary OAuth validation, and assuming the other checks pass, return an access token."
],
"objective_key": "requirement:prompt.md:10"
},
"G11": {
"title": "An actor who intercepted only the code supplies a different, syntactically valid verifier. Comparison fails: return invalid_grant and no token.",
"dimension": "CP",
"scope": [
"Requirement: the actor in the mismatch branch intercepted only the authorization code.",
"Requirement: the mismatch branch supplies a different but syntactically valid verifier.",
"Requirement: the mismatch branch clearly shows the challenge comparison failing.",
"Requirement: the mismatch response uses invalid_grant as the error value.",
"Requirement: the mismatch branch returns no token."
],
"objective_key": "requirement:prompt.md:11"
},
"G12": {
"title": "Do not depict the second branch as reuse of a code already consumed by the first. Make the branch reset/alternative explicit. Hold both comparison outcomes for at least two seconds. Do not substitute invalid_request for the incorrect-verifier response or downgrade to plain after S256 fails.",
"dimension": "CP",
"scope": [
"Requirement: the mismatch response must not be replaced with invalid_request.",
"Requirement: after the S256 comparison fails, do not downgrade to plain.",
"Requirement: hold the success comparison result for at least two seconds.",
"Requirement: hold the failure comparison result for at least two seconds.",
"Requirement: do not depict the second branch as reuse of an authorization code already consumed by the first branch.",
"Requirement: explicitly mark the branch as a reset or alternative path."
],
"objective_key": "requirement:prompt.md:12"
},
"G13": {
"title": "Use the full verifier/challenge pair in Appendix B and compute it in your editable source or accompanying helper script. For the mismatch example, replace the verifier's final 'k' with 'a'; keep the length unchanged and compute its different challenge. Short labels such as v/c/code may be used during motion, provided their meanings remain clear. Include the full example pair and mismatch result in notes and one static checkpoint. Public example strings are demonstrations, not reusable secrets: real verifiers are freshly generated, 43–128 allowed characters with high entropy.",
"dimension": "CP",
"scope": [
"Requirement: the animation uses the full verifier/challenge pair from Appendix B.",
"Requirement: compute the original Appendix B challenge in the editable source or a helper script.",
"Requirement: the mismatch example verifier replaces the final character 'k' with 'a' and keeps the length unchanged.",
"Requirement: the mismatch example computes a challenge different from the original challenge.",
"Requirement: at least one of the five static checkpoints includes the full example pair and the mismatch result.",
"Requirement: state that the public example strings are demonstrations only, not reusable secrets.",
"Requirement: state that real verifiers are freshly generated each time, are 43–128 allowed characters long, and have high entropy."
],
"objective_key": "requirement:prompt.md:14"
},
"G14": {
"title": "Conclude that possession of the authorization code alone is insufficient without the correct verifier in this scenario. PKCE is not token encryption, a static client password, a replacement for TLS or protection against every OAuth attack. Scope the explanation to RFC7636's S256 mechanism rather than a complete deployment guide.",
"dimension": "CP",
"scope": [
"Requirement: the conclusion states that in this scenario, possessing the authorization code alone without the correct verifier is insufficient to redeem a token.",
"Requirement: state that PKCE is not token encryption.",
"Requirement: state that PKCE is not a static client password.",
"Requirement: state that PKCE is not a replacement for TLS.",
"Requirement: state that PKCE does not protect against every OAuth attack.",
"Requirement: the scope of the explanation is limited to RFC7636's S256 mechanism, rather than a complete deployment guide."
],
"objective_key": "requirement:prompt.md:16"
},
"G15": {
"title": "Provide five checkpoints: verifier/challenge preparation, code issued and bound, successful comparison, failed comparison, and the full example calculation. Keep endpoint names, arrows and secret/public distinctions readable on a teaching screen, using labels as well as colours. Original diagrams and motion must be editable. In notes cite relevant RFC sections, explain the two branch starting states, omitted OAuth checks and regeneration procedure. No full-length screen recording or existing video is supplied or required.",
"dimension": "CP",
"scope": [
"Requirement: the five checkpoints respectively cover: verifier/challenge preparation, code issuance and binding, successful comparison, failed comparison, and the full example calculation.",
"Requirement: the secret/public distinction is expressed with text labels in addition to colour.",
"Requirement: original diagrams are editable in the source files.",
"Requirement: motion is editable in the source files.",
"Requirement: notes cite relevant RFC sections.",
"Requirement: notes explain the starting states of the two branches.",
"Requirement: notes explain the omitted OAuth checks.",
"Requirement: notes explain the regeneration procedure for the animation source."
],
"objective_key": "requirement:prompt.md:18"
},
"G16": {
"title": "Readable labels, text and unclipped content at the required scale",
"dimension": "CP",
"scope": [
"Requirement: endpoint names and arrow labels are legible on a teaching screen."
],
"objective_key": "constraint:legibility"
}
},
"grouping_revision": "cp-fn-objectives-v2-20261114"
}
|