Download data/tasks/animations-videos-126/task.json from Accio-Lab/VisualArtifactSpec: direct link, hf CLI and curl.
- Browser
- Download file 15 kB
-
https://huggingface.co/datasets/Accio-Lab/VisualArtifactSpec/resolve/main/data/tasks/animations-videos-126/task.json
- Command line
-
hf download hf://datasets/Accio-Lab/VisualArtifactSpec/data/tasks/animations-videos-126/task.json
-
curl -L -o task.json https://huggingface.co/datasets/Accio-Lab/VisualArtifactSpec/resolve/main/data/tasks/animations-videos-126/task.json
15 kB
| { | |
| "id": "animations-videos-126", | |
| "source": "vas", | |
| "artifact_type": "dynamic_media", | |
| "category": "animations-videos", | |
| "acceptance_groups": { | |
| "G01": [ | |
| "IF01" | |
| ], | |
| "G02": [ | |
| "IF02", | |
| "IF03", | |
| "IF04" | |
| ], | |
| "G03": [ | |
| "IF05", | |
| "IF07" | |
| ], | |
| "G04": [ | |
| "IF06" | |
| ], | |
| "G05": [ | |
| "IF08", | |
| "IF14", | |
| "IF15", | |
| "IF16", | |
| "IF17", | |
| "IF18", | |
| "IF19", | |
| "IF20", | |
| "IF21", | |
| "IF22" | |
| ], | |
| "G06": [ | |
| "IF09", | |
| "IF10", | |
| "IF11", | |
| "IF12" | |
| ], | |
| "G07": [ | |
| "IF13" | |
| ], | |
| "G08": [ | |
| "IF23", | |
| "IF24", | |
| "IF25", | |
| "IF26" | |
| ], | |
| "G09": [ | |
| "IF27", | |
| "IF74", | |
| "IF75", | |
| "IF76", | |
| "IF77", | |
| "IF78" | |
| ], | |
| "G10": [ | |
| "IF28", | |
| "IF56", | |
| "IF79", | |
| "IF80", | |
| "IF81" | |
| ], | |
| "G11": [ | |
| "IF29", | |
| "IF30", | |
| "IF31" | |
| ], | |
| "G12": [ | |
| "IF32", | |
| "IF33", | |
| "IF34", | |
| "IF35", | |
| "IF36", | |
| "IF37", | |
| "IF38", | |
| "IF39", | |
| "IF40" | |
| ], | |
| "G13": [ | |
| "IF41", | |
| "IF42", | |
| "IF43", | |
| "IF44", | |
| "IF45", | |
| "IF46", | |
| "IF47" | |
| ], | |
| "G14": [ | |
| "IF48", | |
| "IF49", | |
| "IF50", | |
| "IF51", | |
| "IF52", | |
| "IF53", | |
| "IF54", | |
| "IF55" | |
| ], | |
| "G15": [ | |
| "IF57", | |
| "IF58", | |
| "IF59", | |
| "IF60", | |
| "IF61", | |
| "IF62", | |
| "IF63", | |
| "IF64", | |
| "IF65", | |
| "IF66", | |
| "IF67" | |
| ], | |
| "G16": [ | |
| "IF68", | |
| "IF69", | |
| "IF70", | |
| "IF71", | |
| "IF72", | |
| "IF73" | |
| ] | |
| }, | |
| "provenance": { | |
| "source": "artifactspec", | |
| "original_id": "P126", | |
| "legacy_task_id": "artifactspec-P126" | |
| }, | |
| "acceptance_objectives": { | |
| "G01": { | |
| "title": "Complete openable artifact handoff and source dependencies", | |
| "dimension": "CP", | |
| "scope": [ | |
| "Requirement: deliver a video file named animation.mp4." | |
| ], | |
| "objective_key": "constraint:delivery" | |
| }, | |
| "G02": { | |
| "title": "Required artifact format, extent and duration", | |
| "dimension": "CP", | |
| "scope": [ | |
| "Requirement: the video resolution is 1280×720.", | |
| "Requirement: The video frame rate is 30 fps.", | |
| "Requirement: The video encoding is H.264." | |
| ], | |
| "objective_key": "constraint:format" | |
| }, | |
| "G03": { | |
| "title": "Create a 40-second English teaching animation based on RFC 9000 sections 8.2, 9, 19.17 and 19.18. Deliver animation.mp4 (1280×720, 30 fps, H.264), editable generation source, notes.md and PNG frames at 10, 18, 26 and 35 seconds in artifact/. Keep inputs unchanged. No external research or real network traffic is required.", | |
| "dimension": "CP", | |
| "scope": [ | |
| "Requirement: The video is a 40-second instructional animation.", | |
| "Requirement: Provide editable generation source, not only a flat video." | |
| ], | |
| "objective_key": "requirement:prompt.md:3" | |
| }, | |
| "G04": { | |
| "title": "Required artifact language", | |
| "dimension": "CP", | |
| "scope": [ | |
| "Requirement: The animation uses English for instructional explanation." | |
| ], | |
| "objective_key": "constraint:language" | |
| }, | |
| "G05": { | |
| "title": "Complete reproducibility and delivery documentation", | |
| "dimension": "CP", | |
| "scope": [ | |
| "Requirement: Provide the notes.md file.", | |
| "Requirement: notes.md lists the message sequence.", | |
| "Requirement: notes.md lists the four key-frame states.", | |
| "Requirement: notes.md cites RFC 9000 sections 8.2, 9, 19.17, and 19.18.", | |
| "Requirement: notes.md explains the use of connection IDs.", | |
| "Requirement: notes.md lists the scenario assumptions given in the prompt.", | |
| "Requirement: notes.md explains the distinction between the 8-byte field and the 1200-byte datagram.", | |
| "Requirement: notes.md explains the difference between screen time and protocol timers.", | |
| "Requirement: notes.md includes regeneration commands.", | |
| "Requirement: notes.md includes dependency descriptions." | |
| ], | |
| "objective_key": "constraint:notes" | |
| }, | |
| "G06": { | |
| "title": "Required faithful previews and companion exports", | |
| "dimension": "CP", | |
| "scope": [ | |
| "Requirement: Provide a PNG frame at 10 seconds in artifact/.", | |
| "Requirement: Provide a PNG frame at 18 seconds in artifact/.", | |
| "Requirement: Provide a PNG frame at 26 seconds in artifact/.", | |
| "Requirement: Provide a PNG frame at 35 seconds in artifact/." | |
| ], | |
| "objective_key": "constraint:preview" | |
| }, | |
| "G07": { | |
| "title": "Unmodified original inputs and isolated working state", | |
| "dimension": "CP", | |
| "scope": [ | |
| "Requirement: Input files remain unchanged." | |
| ], | |
| "objective_key": "constraint:input-integrity" | |
| }, | |
| "G08": { | |
| "title": "Assume the handshake is confirmed, active client migration is permitted, the server address S remains unchanged, and both peers have enough unused nonzero connection IDs. Client addresses C_old and C_new each represent an IP-address/UDP-port pair. The new client address changes its IP, not merely its port. All illustrated challenge/response datagrams are padded to 1200 bytes, with sufficient anti-amplification allowance. Treat this as an explicit scenario assumption, not a universal exception-free rule. Show one logical connection and separate client/server validation states.", | |
| "dimension": "CP", | |
| "scope": [ | |
| "Requirement: The entire animation shows one logical connection.", | |
| "Requirement: Show client and server validation states separately.", | |
| "Requirement: C_new represents changing the IP, not merely changing the UDP port.", | |
| "Requirement: The challenge/response datagrams shown in the animation are labeled as padded to 1200 bytes." | |
| ], | |
| "objective_key": "requirement:prompt.md:5" | |
| }, | |
| "G09": { | |
| "title": "Use stable endpoint/path lanes, labelled arrow direction and payload aliases, readable status badges, and clear transitions between the two scenarios. A changed connection ID does not mean a new logical connection. Avoid suggesting a new TLS identity handshake, a complete NAT-traversal mechanism or universal migration by arbitrary servers. A short note may distinguish involuntary NAT rebinding from this deliberate client-address change.", | |
| "dimension": "CP", | |
| "scope": [ | |
| "Requirement: Changing the connection ID does not indicate a new logical connection.", | |
| "Requirement: Use stable endpoint/path lanes.", | |
| "Requirement: Label arrow directions.", | |
| "Requirement: Label challenge and response arrows with payload aliases A/B.", | |
| "Requirement: Use status badges to indicate validation status.", | |
| "Requirement: Have a clear transition between the two scenarios." | |
| ], | |
| "objective_key": "requirement:prompt.md:15" | |
| }, | |
| "G10": { | |
| "title": "Evidence-bounded claims and truthful scenario identity", | |
| "dimension": "CP", | |
| "scope": [ | |
| "Requirement: The overall presentation is a protocol explainer, not a packet capture or performance benchmark.", | |
| "Requirement: Do not invent throughput guarantees.", | |
| "Requirement: Do not imply a new TLS identity handshake.", | |
| "Requirement: Do not imply a complete NAT-traversal mechanism.", | |
| "Requirement: Do not imply universal migration by arbitrary servers." | |
| ], | |
| "objective_key": "constraint:evidence-boundary" | |
| }, | |
| "G11": { | |
| "title": "0–5: introduce the established connection using C_old, a candidate path via C_new, and available new connection IDs.", | |
| "dimension": "CP", | |
| "scope": [ | |
| "Requirement: 0–5 seconds introduces the established connection using C_old.", | |
| "Requirement: 0–5 seconds introduces the candidate path via C_new.", | |
| "Requirement: 0–5 seconds shows available new connection IDs." | |
| ], | |
| "objective_key": "requirement:prompt.md:8" | |
| }, | |
| "G12": { | |
| "title": "5–13: client probes from C_new with PATH_CHALLENGE(A), using a previously unused destination connection ID. Server echoes A in PATH_RESPONSE on the path where it received the challenge. At 10 seconds show the response travelling, before client receipt: client validation remains pending. By 13 seconds it has arrived and the client marks its validation successful. Explain that an ACK alone would not do this. Keep these packets probing-only; do not silently add ACK or application frames while calling them probing-only.", | |
| "dimension": "CP", | |
| "scope": [ | |
| "Requirement: 5–13 seconds: the client sends PATH_CHALLENGE(A) from C_new.", | |
| "Requirement: The client probe uses a previously unused destination connection ID.", | |
| "Requirement: The server echoes A as PATH_RESPONSE on the same path on which it received the challenge.", | |
| "Requirement: At 10 seconds, show response A in transit and not yet received by the client.", | |
| "Requirement: At 10 seconds, the client validation state is still pending.", | |
| "Requirement: By 13 seconds, response A has arrived at the client.", | |
| "Requirement: By 13 seconds, the client marks its validation as successful.", | |
| "Requirement: Explain that an ACK alone cannot complete path validation.", | |
| "Requirement: Do not silently include ACKs or application frames in probing-only packets." | |
| ], | |
| "objective_key": "requirement:prompt.md:9" | |
| }, | |
| "G13": { | |
| "title": "13–23: server independently sends PATH_CHALLENGE(B) to C_new and receives PATH_RESPONSE(B). At 18 seconds show the response travelling before server receipt: client validation is successful, server validation is still pending. By 23 seconds both have completed their respective checks. Use A and B as aliases for distinct illustrative unpredictable 8-byte values, not literal one-byte protocol fields.", | |
| "dimension": "CP", | |
| "scope": [ | |
| "Requirement: 13–23 seconds: the server independently sends PATH_CHALLENGE(B) to C_new.", | |
| "Requirement: At 18 seconds, show response B in transit and not yet received by the server.", | |
| "Requirement: At 18 seconds, the client validation state is successful.", | |
| "Requirement: At 18 seconds, the server validation state is still pending.", | |
| "Requirement: By 23 seconds, both sides have completed their respective validation.", | |
| "Requirement: A and B are aliases for distinct values.", | |
| "Requirement: A/B are represented as 8-byte values, not literal one-byte protocol fields." | |
| ], | |
| "objective_key": "requirement:prompt.md:10" | |
| }, | |
| "G14": { | |
| "title": "23–29: client begins sending a non-probing application packet from C_new. Make this migration distinct from the earlier probes. In this success scenario C_old now becomes unreachable. Show the server's required probe of the previously active path as well; its lack of response does not invalidate the validated new path. At 26 seconds show application traffic on the new path and the old-path check pending. Note that the new path requires appropriate congestion/RTT state handling; do not invent throughput guarantees.", | |
| "dimension": "CP", | |
| "scope": [ | |
| "Requirement: 23–29 seconds: the client begins sending a non-probing application packet from C_new.", | |
| "Requirement: Migration traffic is clearly distinguished from the earlier probe traffic.", | |
| "Requirement: In the success scenario, C_old becomes unreachable.", | |
| "Requirement: Show the server's required probe of the previously active path.", | |
| "Requirement: The old path probe's lack of response does not invalidate the validated new path.", | |
| "Requirement: At 26 seconds, show application traffic on the new path.", | |
| "Requirement: At 26 seconds, show the old-path check still pending.", | |
| "Requirement: Explain that the new path requires appropriate congestion/RTT state handling." | |
| ], | |
| "objective_key": "requirement:prompt.md:11" | |
| }, | |
| "G15": { | |
| "title": "29–36: explicitly reset to an alternative scenario before any migration. Here C_old stays usable, but a new-path response is lost. Show pending, a later retry with a fresh challenge value, elapsed protocol time, and eventual abandonment of that candidate path. At 35 seconds the candidate is abandoned while the existing connection continues on C_old. Do not treat one lost packet as immediate validation failure or reuse the success scenario's completed validation state. Indicate time compression rather than assigning a made-up fixed timeout.", | |
| "dimension": "CP", | |
| "scope": [ | |
| "Requirement: 29–36 seconds: explicitly reset to an alternative scenario before any migration.", | |
| "Requirement: In the alternative scenario, the new-path response is lost.", | |
| "Requirement: After the new-path response is lost, show pending.", | |
| "Requirement: Later retry with a fresh challenge value.", | |
| "Requirement: Show elapsed protocol time.", | |
| "Requirement: At 35 seconds, the candidate path is abandoned.", | |
| "Requirement: At 35 seconds, the existing connection continues on C_old.", | |
| "Requirement: Do not treat one lost packet as immediate validation failure.", | |
| "Requirement: The failure branch does not reuse the success scenario's completed validation state.", | |
| "Requirement: Represent the wait with time compression.", | |
| "Requirement: Do not assign a made-up fixed timeout." | |
| ], | |
| "objective_key": "requirement:prompt.md:12" | |
| }, | |
| "G16": { | |
| "title": "36–40: summarize three distinctions: probing versus migration; failed candidate path versus failed connection; responder routing versus initiator acceptance. The responder must send the response on the received-challenge path, but a matching response arriving via any path validates the path on which the challenge was sent. Do not teach the initiator to reject it solely because it arrived on a different path.", | |
| "dimension": "CP", | |
| "scope": [ | |
| "Requirement: Summarize the distinction between probing and migration at 36–40 seconds.", | |
| "Requirement: Summarize the distinction between failed candidate path and failed connection at 36–40 seconds.", | |
| "Requirement: Summarize the distinction between responder routing and initiator acceptance at 36–40 seconds.", | |
| "Requirement: State that the responder must send the response on the received-challenge path.", | |
| "Requirement: State that a matching response arriving via any path validates the path on which the challenge was sent.", | |
| "Requirement: Do not teach the initiator to reject solely because the response arrived on a different path." | |
| ], | |
| "objective_key": "requirement:prompt.md:13" | |
| } | |
| }, | |
| "grouping_revision": "cp-fn-objectives-v2-20261114" | |
| } | |