File size: 127,956 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 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 447 448 449 450 451 452 453 454 455 456 457 458 459 460 461 462 463 464 465 466 467 468 469 470 471 472 473 474 475 476 477 478 479 480 481 482 483 484 485 486 487 488 489 490 491 492 493 494 495 496 497 498 499 500 501 502 503 504 505 506 507 508 509 510 511 512 513 514 515 516 517 518 519 520 521 522 523 524 525 526 527 528 529 530 531 532 533 534 535 536 537 538 539 540 541 542 543 544 545 546 547 548 549 550 551 552 553 554 555 556 557 558 559 560 561 562 563 564 565 566 567 568 569 570 571 572 573 574 575 576 577 578 579 580 581 582 583 584 585 586 587 588 589 590 591 592 593 594 595 596 597 598 599 600 601 602 603 604 605 606 607 608 609 610 611 612 613 614 615 616 617 618 619 620 621 622 623 624 625 626 627 628 629 630 631 632 633 634 635 636 637 638 639 640 641 642 643 644 645 646 647 648 649 650 651 652 653 654 655 656 657 658 659 660 661 662 663 664 665 666 667 668 669 670 671 672 673 674 675 676 677 678 679 680 681 682 683 684 685 686 687 688 689 690 691 692 693 694 695 696 697 698 699 700 701 702 703 704 705 706 707 708 709 710 711 712 713 714 715 716 717 718 719 720 721 722 723 724 725 726 727 728 729 730 731 732 733 734 735 736 737 738 739 740 741 742 743 744 745 746 747 748 749 750 751 752 753 754 755 756 757 758 759 | [
{
"id": "IF01",
"dimension": "Task Fulfillment / Compliance",
"criterion": "Requirement: The presentation content's time point is fixed as the 2023-09-28 first launch. Verification method: Check whether the first-launch time point in the cover, titles, and body text is 2023-09-28; if other dates appear, confirm they are not stated as this first-launch time point. Pass criterion: Fully meets this requirement; missing, incorrect, or partially met is No. Evaluation-tool failure cannot be the basis for No. Verification boundary: Verify against the frozen prompt and necessary originals/ground truth; the author's self-description does not replace artifact evidence. Prompt basis: prompt.md original line 7: Fix the scenario to the 2023-09-28 launch..",
"answers": {
"Yes": "Complete all necessary checks for this criterion, with actual evidence supporting satisfaction of the requirement; equivalent implementations within the task's scope are allowed.",
"No": "At least one necessary requirement is not satisfied; identify evidence of actual omissions, errors, or partial satisfaction."
},
"compliance_groups": [
"G01"
],
"benchmark_source": "vas"
},
{
"id": "IF02",
"dimension": "Task Fulfillment / Compliance",
"criterion": "Requirement: The presentation targets developers and makers and is organized as a product launch presentation. Verification method: Check whether the page copy and use cases target developers/makers and whether the content is organized as a product launch presentation. Pass criterion: Fully meets this requirement; missing, incorrect, or partially met is No. Evaluation-tool failure cannot be the basis for No. Verification boundary: Verify against the frozen prompt and necessary originals/ground truth; the author's self-description does not replace artifact evidence. Prompt basis: prompt.md original line 16: Audience/channel: developers and makers, product launch presentation..",
"answers": {
"Yes": "Complete all necessary checks for this criterion, with actual evidence supporting satisfaction of the requirement; equivalent implementations within the task's scope are allowed.",
"No": "At least one necessary requirement is not satisfied; identify evidence of actual omissions, errors, or partial satisfaction."
},
"compliance_groups": [
"G02"
],
"benchmark_source": "vas"
},
{
"id": "IF03",
"dimension": "Task Fulfillment / Compliance",
"criterion": "Requirement: Launch configurations, prices, selling points, and conditions take input/workspace/sources/launch_2023.html as the authoritative source; TXT is only a search aid. Verification method: Check whether the configuration, price, selling point, and condition citations in sources.md and the presentation point to input/workspace/sources/launch_2023.html; TXT must not be used as the final basis. Pass criterion: Fully meets this requirement; missing, incorrect, or partially met is No. Evaluation-tool failure cannot be the basis for No. Verification boundary: Verify against the frozen prompt and necessary originals/ground truth; the author's self-description does not replace artifact evidence. Material basis (relative to inputs/): input/workspace/README.md original line 7: - `sources/launch_2023.html`: official launch text, authoritative for launch configurations, prices, benefits, and conditions. TXT is only a search aid; HTML takes precedence..",
"answers": {
"Yes": "Complete all necessary checks for this criterion, with actual evidence supporting satisfaction of the requirement; equivalent implementations within the task's scope are allowed.",
"No": "At least one necessary requirement is not satisfied; identify evidence of actual omissions, errors, or partial satisfaction."
},
"compliance_groups": [
"G03"
],
"benchmark_source": "vas"
},
{
"id": "IF04",
"dimension": "Task Fulfillment / Compliance",
"criterion": "Requirement: List the memory options in the official launch article at launch time. Verification method: Open input/workspace/sources/launch_2023.html and check whether the memory options listed in the presentation match the launch article. Pass criterion: Fully meets this requirement; missing, incorrect, or partially met is No. Evaluation-tool failure cannot be the basis for No. Verification boundary: Verify against the frozen prompt and necessary originals/ground truth; the author's self-description does not replace artifact evidence. Prompt basis: prompt.md original line 7: Extract the launch-time memory options, USD prices, and tax basis from the official launch article..",
"answers": {
"Yes": "Complete all necessary checks for this criterion, with actual evidence supporting satisfaction of the requirement; equivalent implementations within the task's scope are allowed.",
"No": "At least one necessary requirement is not satisfied; identify evidence of actual omissions, errors, or partial satisfaction."
},
"compliance_groups": [
"G01"
],
"benchmark_source": "vas"
},
{
"id": "IF05",
"dimension": "Task Fulfillment / Compliance",
"criterion": "Requirement: List the USD prices in the official launch article at launch time. Verification method: Open input/workspace/sources/launch_2023.html and check whether the USD prices listed in the presentation match the launch article. Pass criterion: Fully meets this requirement; missing, incorrect, or partially met is No. Evaluation-tool failure cannot be the basis for No. Verification boundary: Verify against the frozen prompt and necessary originals/ground truth; the author's self-description does not replace artifact evidence. Prompt basis: prompt.md original line 7: Extract the launch-time memory options, USD prices, and tax basis from the official launch article..",
"answers": {
"Yes": "Complete all necessary checks for this criterion, with actual evidence supporting satisfaction of the requirement; equivalent implementations within the task's scope are allowed.",
"No": "At least one necessary requirement is not satisfied; identify evidence of actual omissions, errors, or partial satisfaction."
},
"compliance_groups": [
"G01"
],
"benchmark_source": "vas"
},
{
"id": "IF06",
"dimension": "Task Fulfillment / Compliance",
"criterion": "Requirement: Explain the tax basis or tax basis definition of the launch price. Verification method: Check whether the tax basis definition/tax basis is clearly stated near the price and is consistent with the launch article. Pass criterion: Fully meets this requirement; missing, incorrect, or partially met is No. Evaluation-tool failure cannot be the basis for No. Verification boundary: Verify against the frozen prompt and necessary originals/ground truth; the author's self-description does not replace artifact evidence. Prompt basis: prompt.md original line 7: Extract the launch-time memory options, USD prices, and tax basis from the official launch article..",
"answers": {
"Yes": "Complete all necessary checks for this criterion, with actual evidence supporting satisfaction of the requirement; equivalent implementations within the task's scope are allowed.",
"No": "At least one necessary requirement is not satisfied; identify evidence of actual omissions, errors, or partial satisfaction."
},
"compliance_groups": [
"G01"
],
"benchmark_source": "vas"
},
{
"id": "IF07",
"dimension": "Task Fulfillment / Compliance",
"criterion": "Requirement: Product, configuration, and price information are labeled separately and are not mixed into the same field. Verification method: Check whether the product name, configuration (e.g., memory), and price are separately labeled and can be matched on the page. Pass criterion: Fully meets this requirement; missing, incorrect, or partially met is No. Evaluation-tool failure cannot be the basis for No. Verification boundary: Verify against the frozen prompt and necessary originals/ground truth; the author's self-description does not replace artifact evidence. Prompt basis: prompt.md original line 19: Clearly distinguish product, configuration, and price, following the template's visual system..",
"answers": {
"Yes": "Complete all necessary checks for this criterion, with actual evidence supporting satisfaction of the requirement; equivalent implementations within the task's scope are allowed.",
"No": "At least one necessary requirement is not satisfied; identify evidence of actual omissions, errors, or partial satisfaction."
},
"compliance_groups": [
"G04"
],
"benchmark_source": "vas"
},
{
"id": "IF08",
"dimension": "Task Fulfillment / Compliance",
"criterion": "Requirement: The presentation includes at least three selling points and use-case entries. Verification method: Count whether the number of distinct selling point/use-case entries is ≥3. Pass criterion: Fully meets this requirement; missing, incorrect, or partially met is No. Evaluation-tool failure cannot be the basis for No. Verification boundary: Verify against the frozen prompt and necessary originals/ground truth; the author's self-description does not replace artifact evidence. Prompt basis: prompt.md original line 8: Explain at least three launch-supported benefits and use cases.",
"answers": {
"Yes": "Complete all necessary checks for this criterion, with actual evidence supporting satisfaction of the requirement; equivalent implementations within the task's scope are allowed.",
"No": "At least one necessary requirement is not satisfied; identify evidence of actual omissions, errors, or partial satisfaction."
},
"compliance_groups": [
"G05"
],
"benchmark_source": "vas"
},
{
"id": "IF09",
"dimension": "Task Fulfillment / Compliance",
"criterion": "Requirement: Each selling point is connected to a concrete use case. Verification method: Check item by item whether each selling point is paired with a concrete developer/maker use case, rather than merely listing feature names. Pass criterion: Fully meets this requirement; missing, incorrect, or partially met is No. Evaluation-tool failure cannot be the basis for No. Verification boundary: Verify against the frozen prompt and necessary originals/ground truth; the author's self-description does not replace artifact evidence. Prompt basis: prompt.md original line 18: Connect benefits to concrete uses and make accessory requirements and conditions easy to assess..",
"answers": {
"Yes": "Complete all necessary checks for this criterion, with actual evidence supporting satisfaction of the requirement; equivalent implementations within the task's scope are allowed.",
"No": "At least one necessary requirement is not satisfied; identify evidence of actual omissions, errors, or partial satisfaction."
},
"compliance_groups": [
"G06"
],
"benchmark_source": "vas"
},
{
"id": "IF10",
"dimension": "Task Fulfillment / Compliance",
"criterion": "Requirement: The selected selling points and use cases are all supported by launch material evidence. Verification method: Compare input/workspace/sources/launch_2023.html and sources.md to confirm that each selected selling point/use case can be traced to the launch material. Pass criterion: Fully meets this requirement; missing, incorrect, or partially met is No. Evaluation-tool failure cannot be the basis for No. Verification boundary: Verify against the frozen prompt and necessary originals/ground truth; the author's self-description does not replace artifact evidence. Prompt basis: prompt.md original line 8: Explain at least three launch-supported benefits and use cases.",
"answers": {
"Yes": "Complete all necessary checks for this criterion, with actual evidence supporting satisfaction of the requirement; equivalent implementations within the task's scope are allowed.",
"No": "At least one necessary requirement is not satisfied; identify evidence of actual omissions, errors, or partial satisfaction."
},
"compliance_groups": [
"G05"
],
"benchmark_source": "vas"
},
{
"id": "IF11",
"dimension": "Task Fulfillment / Compliance",
"criterion": "Requirement: For selling points/use cases that depend on accessories or operating conditions, explicitly list the necessary accessories or operating conditions. Verification method: Check whether selling points or use cases involving accessories/conditions clearly indicate the necessary accessories or operating conditions and are consistent with the launch article. Pass criterion: Fully meets this requirement; missing, incorrect, or partially met is No. Evaluation-tool failure cannot be the basis for No. Verification boundary: Verify against the frozen prompt and necessary originals/ground truth; the author's self-description does not replace artifact evidence. Prompt basis: prompt.md original line 8: including required accessories or operating conditions..",
"answers": {
"Yes": "Complete all necessary checks for this criterion, with actual evidence supporting satisfaction of the requirement; equivalent implementations within the task's scope are allowed.",
"No": "At least one necessary requirement is not satisfied; identify evidence of actual omissions, errors, or partial satisfaction."
},
"compliance_groups": [
"G05"
],
"benchmark_source": "vas"
},
{
"id": "IF12",
"dimension": "Task Fulfillment / Compliance",
"criterion": "Requirement: Identify input/workspace/sources/product_brief_2026.pdf as later-version material. Verification method: Check whether sources.md or the notes indicate that this brief is 2026 later material. Pass criterion: Fully meets this requirement; missing, incorrect, or partially met is No. Evaluation-tool failure cannot be the basis for No. Verification boundary: Verify against the frozen prompt and necessary originals/ground truth; the author's self-description does not replace artifact evidence. Material basis (relative to inputs/): input/workspace/README.md original line 8: - `sources/product_brief_2026.pdf`: later official brief, useful for identifying the product and images; do not treat later additions as launch facts..",
"answers": {
"Yes": "Complete all necessary checks for this criterion, with actual evidence supporting satisfaction of the requirement; equivalent implementations within the task's scope are allowed.",
"No": "At least one necessary requirement is not satisfied; identify evidence of actual omissions, errors, or partial satisfaction."
},
"compliance_groups": [
"G07"
],
"benchmark_source": "vas"
},
{
"id": "IF13",
"dimension": "Task Fulfillment / Compliance",
"criterion": "Requirement: Do not treat specifications, prices, or configurations newly added in later versions as 2023-09-28 launch facts. Verification method: Compare whether the specifications/prices/configurations in the presentation come only from the launch article and do not use newly added content from the 2026 brief. Pass criterion: Fully meets this requirement; missing, incorrect, or partially met is No. Evaluation-tool failure cannot be the basis for No. Verification boundary: Verify against the frozen prompt and necessary originals/ground truth; the author's self-description does not replace artifact evidence. Prompt basis: prompt.md original line 8: Identify later-version materials and avoid importing later specifications..",
"answers": {
"Yes": "Complete all necessary checks for this criterion, with actual evidence supporting satisfaction of the requirement; equivalent implementations within the task's scope are allowed.",
"No": "At least one necessary requirement is not satisfied; identify evidence of actual omissions, errors, or partial satisfaction."
},
"compliance_groups": [
"G05"
],
"benchmark_source": "vas"
},
{
"id": "IF14",
"dimension": "Task Fulfillment / Compliance",
"criterion": "Requirement: Do not infer launch specifications from product_figures images. Verification method: Check the specification descriptions derived from images in the presentation and sources.md; specifications that cannot be confirmed by the launch article must not appear. Pass criterion: Fully meets this requirement; missing, incorrect, or partially met is No. Evaluation-tool failure cannot be the basis for No. Verification boundary: Verify against the frozen prompt and necessary originals/ground truth; the author's self-description does not replace artifact evidence. Material basis (relative to inputs/): input/workspace/README.md original line 9: - `assets/product_figures/`: assets extracted from the brief; verify image purpose and do not infer launch specifications from pictures..",
"answers": {
"Yes": "Complete all necessary checks for this criterion, with actual evidence supporting satisfaction of the requirement; equivalent implementations within the task's scope are allowed.",
"No": "At least one necessary requirement is not satisfied; identify evidence of actual omissions, errors, or partial satisfaction."
},
"compliance_groups": [
"G08"
],
"benchmark_source": "vas"
},
{
"id": "IF15",
"dimension": "Task Fulfillment / Compliance",
"criterion": "Requirement: When using product_figures assets, verify their image purpose. Verification method: Check whether the asset records in sources.md and the images used on pages state and conform to the image purpose. Pass criterion: Fully meets this requirement; missing, incorrect, or partially met is No. Evaluation-tool failure cannot be the basis for No. Verification boundary: Verify against the frozen prompt and necessary originals/ground truth; the author's self-description does not replace artifact evidence. Material basis (relative to inputs/): input/workspace/README.md original line 9: - `assets/product_figures/`: assets extracted from the brief; verify image purpose and do not infer launch specifications from pictures..",
"answers": {
"Yes": "Complete all necessary checks for this criterion, with actual evidence supporting satisfaction of the requirement; equivalent implementations within the task's scope are allowed.",
"No": "At least one necessary requirement is not satisfied; identify evidence of actual omissions, errors, or partial satisfaction."
},
"compliance_groups": [
"G08"
],
"benchmark_source": "vas"
},
{
"id": "IF16",
"dimension": "Task Fulfillment / Compliance",
"criterion": "Requirement: Replace all template example content. Verification method: Check whether the template example titles, example body text, and example data have all been replaced. Pass criterion: Fully meets this requirement; missing, incorrect, or partially met is No. Evaluation-tool failure cannot be the basis for No. Verification boundary: Verify against the frozen prompt and necessary originals/ground truth; the author's self-description does not replace artifact evidence. Material basis (relative to inputs/): input/workspace/templates/usage-rules.md original line 1: Replace all example content..",
"answers": {
"Yes": "Complete all necessary checks for this criterion, with actual evidence supporting satisfaction of the requirement; equivalent implementations within the task's scope are allowed.",
"No": "At least one necessary requirement is not satisfied; identify evidence of actual omissions, errors, or partial satisfaction."
},
"compliance_groups": [
"G09"
],
"benchmark_source": "vas"
},
{
"id": "IF17",
"dimension": "Task Fulfillment / Compliance",
"criterion": "Requirement: Preserve the template theme colors. Verification method: Compare whether the presentation theme colors match the template theme colors. Pass criterion: Fully meets this requirement; missing, incorrect, or partially met is No. Evaluation-tool failure cannot be the basis for No. Verification boundary: Verify against the frozen prompt and necessary originals/ground truth; the author's self-description does not replace artifact evidence. Material basis (relative to inputs/): input/workspace/templates/usage-rules.md original line 1: Preserve the template's theme colors, title hierarchy, page-number/footer style, and editable text structure..",
"answers": {
"Yes": "Complete all necessary checks for this criterion, with actual evidence supporting satisfaction of the requirement; equivalent implementations within the task's scope are allowed.",
"No": "At least one necessary requirement is not satisfied; identify evidence of actual omissions, errors, or partial satisfaction."
},
"compliance_groups": [
"G09"
],
"benchmark_source": "vas"
},
{
"id": "IF18",
"dimension": "Task Fulfillment / Compliance",
"criterion": "Requirement: Preserve the template title hierarchy. Verification method: Check whether the font sizes, hierarchy relationships, and styles of titles at each level conform to the template rules. Pass criterion: Fully meets this requirement; missing, incorrect, or partially met is No. Evaluation-tool failure cannot be the basis for No. Verification boundary: Verify against the frozen prompt and necessary originals/ground truth; the author's self-description does not replace artifact evidence. Material basis (relative to inputs/): input/workspace/templates/usage-rules.md original line 1: Preserve the template's theme colors, title hierarchy, page-number/footer style, and editable text structure..",
"answers": {
"Yes": "Complete all necessary checks for this criterion, with actual evidence supporting satisfaction of the requirement; equivalent implementations within the task's scope are allowed.",
"No": "At least one necessary requirement is not satisfied; identify evidence of actual omissions, errors, or partial satisfaction."
},
"compliance_groups": [
"G09"
],
"benchmark_source": "vas"
},
{
"id": "IF19",
"dimension": "Task Fulfillment / Compliance",
"criterion": "Requirement: Preserve the template page-number style. Verification method: Check whether the position and style of page numbers on each page are consistent with the template rules. Pass criterion: Fully meets this requirement; missing, incorrect, or partially met is No. Evaluation-tool failure cannot be the basis for No. Verification boundary: Verify against the frozen prompt and necessary originals/ground truth; the author's self-description does not replace artifact evidence. Material basis (relative to inputs/): input/workspace/templates/usage-rules.md original line 1: Preserve the template's theme colors, title hierarchy, page-number/footer style, and editable text structure..",
"answers": {
"Yes": "Complete all necessary checks for this criterion, with actual evidence supporting satisfaction of the requirement; equivalent implementations within the task's scope are allowed.",
"No": "At least one necessary requirement is not satisfied; identify evidence of actual omissions, errors, or partial satisfaction."
},
"compliance_groups": [
"G09"
],
"benchmark_source": "vas"
},
{
"id": "IF20",
"dimension": "Task Fulfillment / Compliance",
"criterion": "Requirement: Preserve the template footer style. Verification method: Check whether the position, content, and style of footers on each page are consistent with the template rules. Pass criterion: Fully meets this requirement; missing, incorrect, or partially met is No. Evaluation-tool failure cannot be the basis for No. Verification boundary: Verify against the frozen prompt and necessary originals/ground truth; the author's self-description does not replace artifact evidence. Material basis (relative to inputs/): input/workspace/templates/usage-rules.md original line 1: Preserve the template's theme colors, title hierarchy, page-number/footer style, and editable text structure..",
"answers": {
"Yes": "Complete all necessary checks for this criterion, with actual evidence supporting satisfaction of the requirement; equivalent implementations within the task's scope are allowed.",
"No": "At least one necessary requirement is not satisfied; identify evidence of actual omissions, errors, or partial satisfaction."
},
"compliance_groups": [
"G09"
],
"benchmark_source": "vas"
},
{
"id": "IF21",
"dimension": "Task Fulfillment / Compliance",
"criterion": "Requirement: Preserve editable text and graphics, and do not replace them with non-editable objects. Verification method: Check whether the text and main graphics in the slides are editable objects rather than being entirely rasterized/imagified. Pass criterion: Fully meets this requirement; missing, incorrect, or partially met is No. Evaluation-tool failure cannot be the basis for No. Verification boundary: Verify against the frozen prompt and necessary originals/ground truth; the author's self-description does not replace artifact evidence. Prompt basis: prompt.md original line 9: preserve editable text and graphics.",
"answers": {
"Yes": "Complete all necessary checks for this criterion, with actual evidence supporting satisfaction of the requirement; equivalent implementations within the task's scope are allowed.",
"No": "At least one necessary requirement is not satisfied; identify evidence of actual omissions, errors, or partial satisfaction."
},
"compliance_groups": [
"G10"
],
"benchmark_source": "vas"
},
{
"id": "IF22",
"dimension": "Task Fulfillment / Compliance",
"criterion": "Requirement: A full-slide image cannot be the sole content of any page. Verification method: Check whether each page has editable text or graphical content in addition to a full-slide background image. Pass criterion: Fully meets this requirement; missing, incorrect, or partially met is No. Evaluation-tool failure cannot be the basis for No. Verification boundary: Verify against the frozen prompt and necessary originals/ground truth; the author's self-description does not replace artifact evidence. Prompt basis: prompt.md original line 9: full-slide images cannot be the sole content..",
"answers": {
"Yes": "Complete all necessary checks for this criterion, with actual evidence supporting satisfaction of the requirement; equivalent implementations within the task's scope are allowed.",
"No": "At least one necessary requirement is not satisfied; identify evidence of actual omissions, errors, or partial satisfaction."
},
"compliance_groups": [
"G11"
],
"benchmark_source": "vas"
},
{
"id": "IF23",
"dimension": "Task Fulfillment / Compliance",
"criterion": "Requirement: Important text, prices, and conditions must not extend beyond the page or be obscured. Verification method: Check page by page whether key text, prices, and conditions extend beyond page boundaries, are obscured, or conflict with graphics. Pass criterion: Fully meets this requirement; missing, incorrect, or partially met is No. Evaluation-tool failure cannot be the basis for No. Verification boundary: Verify against the frozen prompt and necessary originals/ground truth; the author's self-description does not replace artifact evidence. Prompt basis: prompt.md original line 10: Use clear hierarchy without important content overflow; PNGs must match the final PPTX..",
"answers": {
"Yes": "Complete all necessary checks for this criterion, with actual evidence supporting satisfaction of the requirement; equivalent implementations within the task's scope are allowed.",
"No": "At least one necessary requirement is not satisfied; identify evidence of actual omissions, errors, or partial satisfaction."
},
"compliance_groups": [
"G12"
],
"benchmark_source": "vas"
},
{
"id": "IF24",
"dimension": "Task Fulfillment / Compliance",
"criterion": "Requirement: Deliver a six-page PPTX. Verification method: Open the final PPTX and count the pages as 6. Pass criterion: Fully meets this requirement; missing, incorrect, or partially met is No. Evaluation-tool failure cannot be the basis for No. Verification boundary: Verify against the frozen prompt and necessary originals/ground truth; the author's self-description does not replace artifact evidence. Prompt basis: prompt.md original line 3: Create a **six-slide PPTX plus slide PNGs**.",
"answers": {
"Yes": "Complete all necessary checks for this criterion, with actual evidence supporting satisfaction of the requirement; equivalent implementations within the task's scope are allowed.",
"No": "At least one necessary requirement is not satisfied; identify evidence of actual omissions, errors, or partial satisfaction."
},
"compliance_groups": [
"G13"
],
"benchmark_source": "vas"
},
{
"id": "IF25",
"dimension": "Task Fulfillment / Compliance",
"criterion": "Requirement: Deliver six slide PNGs. Verification method: Check that the number of slide PNGs in artifact/ is 6 and that they correspond to the six pages. Pass criterion: Fully meets this requirement; missing, incorrect, or partially met is No. Evaluation-tool failure cannot be the basis for No. Verification boundary: Verify against the frozen prompt and necessary originals/ground truth; the author's self-description does not replace artifact evidence. Prompt basis: prompt.md original line 3: Create a **six-slide PPTX plus slide PNGs**.",
"answers": {
"Yes": "Complete all necessary checks for this criterion, with actual evidence supporting satisfaction of the requirement; equivalent implementations within the task's scope are allowed.",
"No": "At least one necessary requirement is not satisfied; identify evidence of actual omissions, errors, or partial satisfaction."
},
"compliance_groups": [
"G14"
],
"benchmark_source": "vas"
},
{
"id": "IF26",
"dimension": "Task Fulfillment / Compliance",
"criterion": "Requirement: The slide PNGs correspond consistently with the final PPTX. Verification method: Compare page by page whether the PNGs and the final PPTX are consistent in page order, text, and graphical content. Pass criterion: Fully meets this requirement; missing, incorrect, or partially met is No. Evaluation-tool failure cannot be the basis for No. Verification boundary: Verify against the frozen prompt and necessary originals/ground truth; the author's self-description does not replace artifact evidence. Prompt basis: prompt.md original line 10: PNGs must match the final PPTX..",
"answers": {
"Yes": "Complete all necessary checks for this criterion, with actual evidence supporting satisfaction of the requirement; equivalent implementations within the task's scope are allowed.",
"No": "At least one necessary requirement is not satisfied; identify evidence of actual omissions, errors, or partial satisfaction."
},
"compliance_groups": [
"G12"
],
"benchmark_source": "vas"
},
{
"id": "IF27",
"dimension": "Task Fulfillment / Compliance",
"criterion": "Requirement: Provide sources.md in artifact/. Verification method: Check whether artifact/sources.md exists. Pass criterion: Fully satisfies this requirement; missing, incorrect, or partial satisfaction is No. Evaluation-tool failures cannot be grounds for No. Verification boundary: Verify against the frozen prompt and necessary original files/ground truth; the author's self-report does not substitute for artifact evidence. Task basis: prompt.md line 12 of the original text: Include sources.md documenting versions, factual references, and assets.",
"answers": {
"Yes": "Complete all necessary checks for this criterion, with actual evidence supporting satisfaction of the requirement; equivalent implementations within the task's scope are allowed.",
"No": "At least one necessary requirement is not satisfied; identify evidence of actual omissions, errors, or partial satisfaction."
},
"compliance_groups": [
"G15"
],
"benchmark_source": "vas"
},
{
"id": "IF28",
"dimension": "Task Fulfillment / Compliance",
"criterion": "Requirement: sources.md records the versions of the materials used. Verification method: Open sources.md and check whether it lists the source materials used and their versions/dates. Pass criterion: Fully satisfies this requirement; missing, incorrect, or partial satisfaction is No. Evaluation-tool failures cannot be grounds for No. Verification boundary: Verify against the frozen prompt and necessary original files/ground truth; the author's self-report does not substitute for artifact evidence. Task basis: prompt.md line 12 of the original text: Include sources.md documenting versions, factual references, and assets.",
"answers": {
"Yes": "Complete all necessary checks for this criterion, with actual evidence supporting satisfaction of the requirement; equivalent implementations within the task's scope are allowed.",
"No": "At least one necessary requirement is not satisfied; identify evidence of actual omissions, errors, or partial satisfaction."
},
"compliance_groups": [
"G15"
],
"benchmark_source": "vas"
},
{
"id": "IF29",
"dimension": "Task Fulfillment / Compliance",
"criterion": "Requirement: sources.md records factual references. Verification method: Open sources.md and check whether key facts have corresponding cited sources. Pass criterion: Fully satisfies this requirement; missing, incorrect, or partial satisfaction is No. Evaluation-tool failures cannot be grounds for No. Verification boundary: Verify against the frozen prompt and necessary original files/ground truth; the author's self-report does not substitute for artifact evidence. Task basis: prompt.md line 12 of the original text: Include sources.md documenting versions, factual references, and assets.",
"answers": {
"Yes": "Complete all necessary checks for this criterion, with actual evidence supporting satisfaction of the requirement; equivalent implementations within the task's scope are allowed.",
"No": "At least one necessary requirement is not satisfied; identify evidence of actual omissions, errors, or partial satisfaction."
},
"compliance_groups": [
"G15"
],
"benchmark_source": "vas"
},
{
"id": "IF30",
"dimension": "Task Fulfillment / Compliance",
"criterion": "Requirement: sources.md records the assets used. Verification method: Open sources.md and check whether the images/assets used in the presentation list their sources and purposes. Pass criterion: Fully satisfies this requirement; missing, incorrect, or partial satisfaction is No. Evaluation-tool failures cannot be grounds for No. Verification boundary: Verify against the frozen prompt and necessary original files/ground truth; the author's self-report does not substitute for artifact evidence. Task basis: prompt.md line 12 of the original text: Include sources.md documenting versions, factual references, and assets.",
"answers": {
"Yes": "Complete all necessary checks for this criterion, with actual evidence supporting satisfaction of the requirement; equivalent implementations within the task's scope are allowed.",
"No": "At least one necessary requirement is not satisfied; identify evidence of actual omissions, errors, or partial satisfaction."
},
"compliance_groups": [
"G15"
],
"benchmark_source": "vas"
},
{
"id": "IF31",
"dimension": "Task Fulfillment / Compliance",
"criterion": "Requirement: Provide delivery.md in artifact/. Verification method: Check whether artifact/delivery.md exists. Pass criterion: Fully satisfies this requirement; missing, incorrect, or partial satisfaction is No. Evaluation-tool failures cannot be grounds for No. Verification boundary: Verify against the frozen prompt and necessary original files/ground truth; the author's self-report does not substitute for artifact evidence. Task basis: prompt.md line 12 of the original text: plus delivery.md with file locations and opening instructions..",
"answers": {
"Yes": "Complete all necessary checks for this criterion, with actual evidence supporting satisfaction of the requirement; equivalent implementations within the task's scope are allowed.",
"No": "At least one necessary requirement is not satisfied; identify evidence of actual omissions, errors, or partial satisfaction."
},
"compliance_groups": [
"G15"
],
"benchmark_source": "vas"
},
{
"id": "IF32",
"dimension": "Task Fulfillment / Compliance",
"criterion": "Requirement: delivery.md records the locations of the delivered files. Verification method: Open delivery.md and check whether it gives the locations of the delivered files such as the PPTX, PNG, and sources.md. Pass criterion: Fully satisfies this requirement; missing, incorrect, or partial satisfaction is No. Evaluation-tool failures cannot be grounds for No. Verification boundary: Verify against the frozen prompt and necessary original files/ground truth; the author's self-report does not substitute for artifact evidence. Task basis: prompt.md line 12 of the original text: plus delivery.md with file locations and opening instructions..",
"answers": {
"Yes": "Complete all necessary checks for this criterion, with actual evidence supporting satisfaction of the requirement; equivalent implementations within the task's scope are allowed.",
"No": "At least one necessary requirement is not satisfied; identify evidence of actual omissions, errors, or partial satisfaction."
},
"compliance_groups": [
"G15"
],
"benchmark_source": "vas"
},
{
"id": "IF33",
"dimension": "Task Fulfillment / Compliance",
"criterion": "Requirement: delivery.md provides opening instructions. Verification method: Open delivery.md and check whether it explains how to open/view the final delivered files. Pass criterion: Fully satisfies this requirement; missing, incorrect, or partial satisfaction is No. Evaluation-tool failures cannot be grounds for No. Verification boundary: Verify against the frozen prompt and necessary original files/ground truth; the author's self-report does not substitute for artifact evidence. Task basis: prompt.md line 12 of the original text: plus delivery.md with file locations and opening instructions..",
"answers": {
"Yes": "Complete all necessary checks for this criterion, with actual evidence supporting satisfaction of the requirement; equivalent implementations within the task's scope are allowed.",
"No": "At least one necessary requirement is not satisfied; identify evidence of actual omissions, errors, or partial satisfaction."
},
"compliance_groups": [
"G15"
],
"benchmark_source": "vas"
},
{
"id": "IF34",
"dimension": "Task Fulfillment / Compliance",
"criterion": "Requirement: Do not modify the read-only original files. [v7 verifiable boundary: check that the final input matches the frozen snapshot file by file; it is not required to prove that no writes ever occurred during production. Public runtime inputs are guaranteed by read-only mounts.]. Verification method: Check that originals such as input/workspace/README.md, input/workspace/sources/, input/workspace/templates/, and input/workspace/assets/ have not been altered. Pass criterion: Fully satisfies this requirement; missing, incorrect, or partial satisfaction is No. Evaluation-tool failures cannot be grounds for No. Verification boundary: Verify against the frozen prompt and necessary original files/ground truth; the author's self-report does not substitute for artifact evidence. Material basis (relative to inputs/): input/workspace/README.md line 14 of the original text: Originals are read-only..",
"answers": {
"Yes": "Complete all necessary checks for this criterion, with actual evidence supporting satisfaction of the requirement; equivalent implementations within the task's scope are allowed.",
"No": "At least one necessary requirement is not satisfied; identify evidence of actual omissions, errors, or partial satisfaction."
},
"compliance_groups": [
"G16"
],
"benchmark_source": "vas"
},
{
"id": "IF37",
"dimension": "Task Fulfillment / Compliance",
"criterion": "Requirement: Newly authored content uses English. Verification method: Check that the newly added presentation copy is in English; the original language of the original source materials does not count as newly authored content. Pass criterion: Fully satisfies this requirement; missing, incorrect, or partial satisfaction is No. Evaluation-tool failures cannot be grounds for No. Verification boundary: Verify against the frozen prompt and necessary original files/ground truth; the author's self-report does not substitute for artifact evidence. Task basis: prompt.md line 3 of the original text: Write newly authored content in English..",
"answers": {
"Yes": "Complete all necessary checks for this criterion, with actual evidence supporting satisfaction of the requirement; equivalent implementations within the task's scope are allowed.",
"No": "At least one necessary requirement is not satisfied; identify evidence of actual omissions, errors, or partial satisfaction."
},
"compliance_groups": [
"G17"
],
"benchmark_source": "vas"
},
{
"id": "IF38",
"dimension": "Task Fulfillment / Compliance",
"criterion": "Requirement: Do not treat template example copy as product facts. Verification method: Check whether the product facts in the presentation come from the launch article or other recorded sources rather than template example copy. Pass criterion: Fully satisfies this requirement; missing, incorrect, or partial satisfaction is No. Evaluation-tool failures cannot be grounds for No. Verification boundary: Verify against the frozen prompt and necessary original files/ground truth; the author's self-report does not substitute for artifact evidence. Material basis (relative to inputs/): input/workspace/README.md line 10 of the original text: Example copy is not product evidence..",
"answers": {
"Yes": "Complete all necessary checks for this criterion, with actual evidence supporting satisfaction of the requirement; equivalent implementations within the task's scope are allowed.",
"No": "At least one necessary requirement is not satisfied; identify evidence of actual omissions, errors, or partial satisfaction."
},
"compliance_groups": [
"G18"
],
"benchmark_source": "vas"
},
{
"id": "C1",
"dimension": "Content",
"criterion": "Launch terminology and price framing are accurate.\nObject of measurement: Terminology (4GB/8GB, Cortex-A76, Active Cooler, USB power, etc.) and price framing are stated accurately and are appropriate for a developer audience, clearly distinguishing capacity, unit price, and pre-tax conditions.\nObservation scope: 6-page English PPTX and PNG, following the existing template, a 2023-09-28 launch introduction for developers and makers.\nObservation basis: Check whether every price states $60/4GB, $80/8GB, plus local tax. Check that the relationship among capacity, unit price, and tax conditions is clear in the wording, and that pre-tax prices are not written as tax-inclusive prices. Check whether prices, capacities, or wireless specifications from later versions appear as 2023-09-28 launch facts.\nScoring boundary: Whether terminology, concepts, and wording let this task's audience understand accurately; IF verifies factual accuracy, and C1 does not award points by number of terms.\nFull-refinement check (+2): The densest configuration comparison remains concise and explicit about price basis; accuracy and the exclusion of later versions alone do not earn this tier.\nExceptional check (+3): A concise presentation of configuration, price and tax basis resolves their interdependence more directly than a flawless conventional specification table, without removing conditions or inventing a computed total.",
"answers": {
"-3": "Severe failure: This item's core understanding or usage goal cannot be achieved. Specific manifestations: prices or capacity units are confused, later specifications are treated as launch facts, core terminology is seriously distorted, and readers cannot confirm launch configurations and prices. Judged by the above actual impact; harmless minor differences do not trigger this level.",
"-2": "Clearly unacceptable: This item's main areas or key processes are persistently damaged. Specific manifestations: price or tax framing is missing key items, such as not stating additional local tax, prices and capacities are mismatched, or terminology is inconsistent with the launch in multiple places. Judged by the above actual impact; harmless minor differences do not trigger this level.",
"-1": "Below basic requirements: This item has clear local substantive defects. Specific manifestations: price and tax framing is basically presented, but individual wording is vague, the relationship among capacity/unit price/tax is not clear enough, or terminology consistency is insufficient. Judged by the above actual impact; harmless minor differences do not trigger this level.",
"0": "Basically acceptable: Launch prices, capacities, and tax framing are correct; basic terminology is readable and has no substantive ambiguity; this item's necessary requirements are fully satisfied, with no substantive defects and ordinary performance.",
"1": "Accomplished but not yet fully refined: meets tier 0 and demonstrates a substantive, observable quality gain. A potentially confusing configuration, price or tax term is clarified where it appears. A specific remaining opportunity or failure to meet the complete +2 quality conditions keeps the item at this tier; explain the actual gap in reason. Ordinary correctness alone is not excellent execution.",
"2": "Fully refined within scope: meets tier 0 and achieves the following throughout every applicable part of this item, not just one successful local example. Configuration labels, prices and tax qualifications work together to support direct comparison rather than scattered fact lookup. Difficult-case check: The densest configuration comparison remains concise and explicit about price basis; accuracy and the exclusion of later versions alone do not earn this tier. Across the full applicable scope, there is no identifiable substantive weakness or feasible task-relevant improvement with material benefit under this criterion. Establish this through complete observation and an active search for plausible shortcomings; absence of a noticed error does not prove full refinement.",
"3": "Exceptional beyond conventional full refinement: fully meets +2, then demonstrates a non-obvious design with a substantial additional benefit. A concise presentation of configuration, price and tax basis resolves their interdependence more directly than a flawless conventional specification table, without removing conditions or inventing a computed total. In reason identify the choice, real difficulty, benefit beyond an equally correct/complete/polished conventional solution, and observed evidence. These benefit descriptions do not prescribe a unique design. Repeating +2 strengths, adding complexity or expressing amazement is insufficient; without the exceptional evidence, the ceiling is +2."
},
"weight": 9,
"benchmark_source": "vas"
},
{
"id": "C2",
"dimension": "Content",
"criterion": "Selling points and factual source support.\nObject of measurement: At least three selling points and usage scenarios are grounded in the launch article text, and accessories and operating conditions cite real facts rather than speculation.\nObservation scope: 6-page English PPTX and PNG, following the existing template, a 2023-09-28 launch introduction for developers and makers.\nObservation basis: Count whether the number of selling points with launch sources is ≥3, and check whether each selling point is connected to a specific use case. If the chosen selling points involve USB power or high-power peripherals, check whether the condition statements match the launch article text, and do not write 1.6A as achievable on every USB port. Check whether scenario inferences are labeled as usage inferences rather than measured performance, and that accessory conditions appear alongside the selling points.\nScoring boundary: The support relationship between task claims and evidence/data/actual process; do not repeatedly evaluate graphic encoding or whether source documents are easy to find.\nScenario reference · content quality (adds no threshold): launch date and price framing, launch selling points and conditions, usage scenarios and accessory requirements.\nThis task's applicable boundary (all relevant entries apply; adds no scoring items): It is not mandatory to present every optional specification in the given original materials; only at least three sourced selling points are required.\nThis task's applicable boundary (all relevant entries apply; adds no scoring items): New specifications from the 2026 brief must not be treated as 2023-09-28 launch facts.\nFull-refinement check (+2): The most conditional chosen benefit retains its limitation without obscuring its use; optional specifications not selected for the presentation are not required.\nExceptional check (+3): A benefit explanation reveals how a launch-supported capability and its operating condition jointly enable a use, offering insight beyond accurate feature-plus-accessory listings.",
"answers": {
"-3": "Severe failure: This item's core understanding or usage goal cannot be achieved. Specific manifestations: the three selling points are unsourced or clearly fabricated, and conditions contradict facts. Judged by the above actual impact; harmless minor differences do not trigger this level.",
"-2": "Clearly unacceptable: This item's main areas or key processes are persistently damaged. Specific manifestations: only one or two selling points are traceable, or accessory conditions are missing/incorrect. Judged by the above actual impact; harmless minor differences do not trigger this level.",
"-1": "Below basic requirements: This item has clear local substantive defects. Specific manifestations: the number of selling points is sufficient, but individual statements go beyond the original text or conditions are vague. Judged by the above actual impact; harmless minor differences do not trigger this level.",
"0": "Basically acceptable: Three selling points are traceable and conditions are stated; this item's necessary requirements are fully satisfied, with no substantive defects and ordinary performance.",
"1": "Accomplished but not yet fully refined: meets tier 0 and demonstrates a substantive, observable quality gain. A selected launch benefit is paired with a concrete supported use and its relevant condition. A specific remaining opportunity or failure to meet the complete +2 quality conditions keeps the item at this tier; explain the actual gap in reason. Ordinary correctness alone is not excellent execution.",
"2": "Fully refined within scope: meets tier 0 and achieves the following throughout every applicable part of this item, not just one successful local example. Benefits, supporting launch facts and applicable accessories reinforce each other across the chosen use cases. Difficult-case check: The most conditional chosen benefit retains its limitation without obscuring its use; optional specifications not selected for the presentation are not required. Across the full applicable scope, there is no identifiable substantive weakness or feasible task-relevant improvement with material benefit under this criterion. Establish this through complete observation and an active search for plausible shortcomings; absence of a noticed error does not prove full refinement.",
"3": "Exceptional beyond conventional full refinement: fully meets +2, then demonstrates a non-obvious design with a substantial additional benefit. A benefit explanation reveals how a launch-supported capability and its operating condition jointly enable a use, offering insight beyond accurate feature-plus-accessory listings. In reason identify the choice, real difficulty, benefit beyond an equally correct/complete/polished conventional solution, and observed evidence. These benefit descriptions do not prescribe a unique design. Repeating +2 strengths, adding complexity or expressing amazement is insufficient; without the exceptional evidence, the ceiling is +2."
},
"weight": 9,
"benchmark_source": "vas"
},
{
"id": "C3",
"dimension": "Content",
"criterion": "Information selection and version boundaries.\nObject of measurement: Select content according to the launch presentation's purpose, covering the launch date, prices, selling points, and conditions, while isolating later-version materials and irrelevant details.\nObservation scope: 6-page English PPTX and PNG, following the existing template, a 2023-09-28 launch introduction for developers and makers.\nObservation basis: Confirm that the 2023-09-28 date appears in the content. Check whether 2026 materials are used only to verify images without citing their parameters. Check whether purchase entry points or brand statements not required by the prompt are crammed in.\nScoring boundary: Content selection, density, tone, and necessary qualifications around the scenario's purpose; not font size or page visual hierarchy.\nTask scenario: A Raspberry Pi 5 product launch presentation for developers and makers, producing a six-page presentation and corresponding slide PNGs for product marketing and launch explanation.\nScenario reference · audience (adds no threshold): Developers and makers familiar with the embedded and maker ecosystem, concerned with specifications, prices, accessory conditions, and usage scenarios.\nScenario reference · purpose (adds no threshold): A product launch presentation explaining launch configurations, price framing, and usable scenarios.\nScenario reference · content selection (adds no threshold): Launch date and prices are accurate, selling points are sourced, accessories and usage conditions are easy to judge, and product/configuration/price levels are distinct.\nThis task's applicable boundary (all relevant entries apply; adds no scoring items): Purchase entry points, brand statements, or official brand asset certification are not required.\nThis task's applicable boundary (all relevant entries apply; adds no scoring items): Citing the 2026 brief as the basis for launch parameters is not required; it may only be used to verify images.\nContent focus: Launch configurations/USD prices/tax basis, three sourced selling points and accessory conditions, later-version boundaries\nFull-refinement check (+2): The most qualification-heavy chosen use case remains persuasive but not overstated within six slides; a purchase CTA is not required.\nExceptional check (+3): The chosen launch story makes a conditional benefit more useful and persuasive through precise selection rather than overstatement, surpassing a complete and well-edited feature catalogue.",
"answers": {
"-3": "Severe failure: This item's core understanding or usage goal cannot be achieved. Specific manifestations: core launch information is missing or 2026 specifications are the main subject. Judged by the above actual impact; harmless minor differences do not trigger this level.",
"-2": "Clearly unacceptable: This item's main areas or key processes are persistently damaged. Specific manifestations: key prices or dates are missing, or later information seeps in extensively. Judged by the above actual impact; harmless minor differences do not trigger this level.",
"-1": "Below basic requirements: One information selection or tone weakens a necessary qualification, imposing a substantive comprehension burden on this task's audience. Provide actual-impact evidence in the parts of this task relevant to information selection and version boundaries; ordinary performance, harmless minor differences, or pure personal preference do not trigger a negative level.",
"0": "Basically acceptable: Core launch information is complete, with no substantive spillover; this item's necessary requirements are fully satisfied, with no substantive defects and ordinary performance.",
"1": "Accomplished but not yet fully refined: meets tier 0 and demonstrates a substantive, observable quality gain. One clearly bounded use-case statement distinguishes a supported feature from a suggested use. A specific remaining opportunity or failure to meet the complete +2 quality conditions keeps the item at this tier; explain the actual gap in reason. Ordinary correctness alone is not excellent execution.",
"2": "Fully refined within scope: meets tier 0 and achieves the following throughout every applicable part of this item, not just one successful local example. The selected benefits and necessary conditions form a focused launch story without later-version information or a catalogue dump. Difficult-case check: The most qualification-heavy chosen use case remains persuasive but not overstated within six slides; a purchase CTA is not required. Across the full applicable scope, there is no identifiable substantive weakness or feasible task-relevant improvement with material benefit under this criterion. Establish this through complete observation and an active search for plausible shortcomings; absence of a noticed error does not prove full refinement.",
"3": "Exceptional beyond conventional full refinement: fully meets +2, then demonstrates a non-obvious design with a substantial additional benefit. The chosen launch story makes a conditional benefit more useful and persuasive through precise selection rather than overstatement, surpassing a complete and well-edited feature catalogue. In reason identify the choice, real difficulty, benefit beyond an equally correct/complete/polished conventional solution, and observed evidence. These benefit descriptions do not prescribe a unique design. Repeating +2 strengths, adding complexity or expressing amazement is insufficient; without the exceptional evidence, the ceiling is +2."
},
"weight": 7,
"benchmark_source": "vas"
},
{
"id": "O1",
"dimension": "Organization",
"criterion": "Six-page launch narrative path.\nObject of measurement: The six pages form a coherent presentation path from product positioning, launch configuration and prices, and selling points to scenarios and conditions.\nObservation scope: 6-page English PPTX and PNG, following the existing template, a 2023-09-28 launch introduction for developers and makers.\nObservation basis: Read in page order and judge whether the product is introduced before configuration, prices, and selling points. Check whether each page serves a clear narrative function with no duplicate pages. Observe whether the final page closes on usage conditions rather than ending abruptly.\nScoring boundary: The logic of the overall argument/decision/operation/concept path; do not score by a fixed structural template.\nFull-refinement check (+2): The move from product benefits to conditional use cases and the existing ending remains clear without extra slides or a prescribed slide order.\nExceptional check (+3): An economical narrative lets configuration choices and supported uses explain each other, reducing decisions a reader must reconstruct from a conventional polished launch sequence.",
"answers": {
"-3": "Severe failure: This item's core understanding or usage goal cannot be achieved. Specific manifestations: page order is chaotic or key links are missing, and readers cannot form a six-page launch understanding. Judged by the above actual impact; harmless minor differences do not trigger this level.",
"-2": "Clearly unacceptable: This item's main areas or key processes are persistently damaged. Specific manifestations: all six pages are present but the order is reversed or clearly jumps, making the main launch path hard to track. Judged by the above actual impact; harmless minor differences do not trigger this level.",
"-1": "Below basic requirements: This item has clear local substantive defects. Specific manifestations: the narrative path is basically discernible, but some page is disconnected, repetitive, or has an abrupt transition. Judged by the above actual impact; harmless minor differences do not trigger this level.",
"0": "Basically acceptable: The six-page order is understandable and covers necessary links such as product positioning, configuration and prices, selling points, scenarios, and conditions, but with obvious organizational simplification; this item's necessary requirements are fully satisfied, with no substantive defects and ordinary performance.",
"1": "Accomplished but not yet fully refined: meets tier 0 and demonstrates a substantive, observable quality gain. A transition explains why a configuration or benefit matters to the next part of the launch story. A specific remaining opportunity or failure to meet the complete +2 quality conditions keeps the item at this tier; explain the actual gap in reason. Ordinary correctness alone is not excellent execution.",
"2": "Fully refined within scope: meets tier 0 and achieves the following throughout every applicable part of this item, not just one successful local example. Configurations, uses and operating conditions build a coherent six-slide account rather than disconnected specifications. Difficult-case check: The move from product benefits to conditional use cases and the existing ending remains clear without extra slides or a prescribed slide order. Across the full applicable scope, there is no identifiable substantive weakness or feasible task-relevant improvement with material benefit under this criterion. Establish this through complete observation and an active search for plausible shortcomings; absence of a noticed error does not prove full refinement.",
"3": "Exceptional beyond conventional full refinement: fully meets +2, then demonstrates a non-obvious design with a substantial additional benefit. An economical narrative lets configuration choices and supported uses explain each other, reducing decisions a reader must reconstruct from a conventional polished launch sequence. In reason identify the choice, real difficulty, benefit beyond an equally correct/complete/polished conventional solution, and observed evidence. These benefit descriptions do not prescribe a unique design. Repeating +2 strengths, adding complexity or expressing amazement is insufficient; without the exceptional evidence, the ceiling is +2."
},
"weight": 6,
"benchmark_source": "vas"
},
{
"id": "O2",
"dimension": "Organization",
"criterion": "Within-page development of selling points and conditions.\nObject of measurement: Within a single page, the relationship between a selling point and its use value and accessory conditions is developed clearly, with discernible hierarchy.\nObservation scope: 6-page English PPTX and PNG, following the existing template, a 2023-09-28 launch introduction for developers and makers.\nObservation basis: Check whether selling-point pages present both use value and required accessories. Observe whether condition statements are placed in easily overlooked corners. Check whether a single page carries too many parallel selling points and loses focus.\nScoring boundary: The semantic order and relationships of explanations within a single page, stage, node, or comparison unit.\nFull-refinement check (+2): On the densest chosen use-case slide, each condition clearly applies to the right benefit and does not need a later slide to repair its meaning.\nExceptional check (+3): A locally integrated feature-use-condition unit lets the reader understand a conditional benefit at once, beyond merely placing a caveat beside a feature.",
"answers": {
"-3": "Severe failure: This item's core understanding or usage goal cannot be achieved. Specific manifestations: within-page information is piled up or relationships are broken, making selling points and conditions incomprehensible. Judged by the above actual impact; harmless minor differences do not trigger this level.",
"-2": "Clearly unacceptable: This item's main areas or key processes are persistently damaged. Specific manifestations: selling points and conditions are mixed together, making primary and secondary information hard to distinguish. Judged by the above actual impact; harmless minor differences do not trigger this level.",
"-1": "Below basic requirements: This item has clear local substantive defects. Specific manifestations: some page's development is awkward or conditions are weakened. Judged by the above actual impact; harmless minor differences do not trigger this level.",
"0": "Basically acceptable: Within-page information is readable and relationships are discernible; this item's necessary requirements are fully satisfied, with no substantive defects and ordinary performance.",
"1": "Accomplished but not yet fully refined: meets tier 0 and demonstrates a substantive, observable quality gain. A benefit and its condition are grouped so their relationship is immediately apparent. A specific remaining opportunity or failure to meet the complete +2 quality conditions keeps the item at this tier; explain the actual gap in reason. Ordinary correctness alone is not excellent execution.",
"2": "Fully refined within scope: meets tier 0 and achieves the following throughout every applicable part of this item, not just one successful local example. Feature, application and accessory explanations develop in connected local groups. Difficult-case check: On the densest chosen use-case slide, each condition clearly applies to the right benefit and does not need a later slide to repair its meaning. Across the full applicable scope, there is no identifiable substantive weakness or feasible task-relevant improvement with material benefit under this criterion. Establish this through complete observation and an active search for plausible shortcomings; absence of a noticed error does not prove full refinement.",
"3": "Exceptional beyond conventional full refinement: fully meets +2, then demonstrates a non-obvious design with a substantial additional benefit. A locally integrated feature-use-condition unit lets the reader understand a conditional benefit at once, beyond merely placing a caveat beside a feature. In reason identify the choice, real difficulty, benefit beyond an equally correct/complete/polished conventional solution, and observed evidence. These benefit descriptions do not prescribe a unique design. Repeating +2 strengths, adding complexity or expressing amazement is insufficient; without the exceptional evidence, the ceiling is +2."
},
"weight": 5,
"benchmark_source": "vas"
},
{
"id": "O3",
"dimension": "Organization",
"criterion": "Cross-page product and configuration identity inheritance.\nObject of measurement: The product name, configuration, prices, and conditions remain consistent across the six pages, with no drift in naming or numbers.\nObservation scope: 6-page English PPTX and PNG, following the existing template, a 2023-09-28 launch introduction for developers and makers.\nObservation basis: Compare page by page whether the product name, capacity, and price wording are consistent. Check whether condition statements change meaning through different wording on some page. Observe whether configuration, prices, and conditions maintain traceable semantic inheritance across the six pages.\nScoring boundary: Semantic inheritance across pages/states, or the closure of a single-page branch path with identity/action; do not force an added ending.\nFull-refinement check (+2): When similar configurations or accessory-dependent uses recur, their distinct conditions remain traceable without inventing a new ending.\nExceptional check (+3): Product and configuration references carry a useful conceptual distinction across changing use cases, reducing reinterpretation beyond flawless naming continuity.",
"answers": {
"-3": "Severe failure: This item's core understanding or usage goal cannot be achieved. Specific manifestations: product names or price numbers contradict across pages. Judged by the above actual impact; harmless minor differences do not trigger this level.",
"-2": "Clearly unacceptable: This item's main areas or key processes are persistently damaged. Specific manifestations: inconsistent naming or configurations across multiple pages cause confusion. Judged by the above actual impact; harmless minor differences do not trigger this level.",
"-1": "Below basic requirements: This item has clear local substantive defects. Specific manifestations: terminology or numbers on individual pages are not unified with the rest. Judged by the above actual impact; harmless minor differences do not trigger this level.",
"0": "Basically acceptable: Consistent across pages, with no substantive contradictions; this item's necessary requirements are fully satisfied, with no substantive defects and ordinary performance.",
"1": "Accomplished but not yet fully refined: meets tier 0 and demonstrates a substantive, observable quality gain. A repeated configuration or product reference explicitly carries its meaning into the next slide. A specific remaining opportunity or failure to meet the complete +2 quality conditions keeps the item at this tier; explain the actual gap in reason. Ordinary correctness alone is not excellent execution.",
"2": "Fully refined within scope: meets tier 0 and achieves the following throughout every applicable part of this item, not just one successful local example. Product identity, memory options and use-case references remain semantically connected across the deck. Difficult-case check: When similar configurations or accessory-dependent uses recur, their distinct conditions remain traceable without inventing a new ending. Across the full applicable scope, there is no identifiable substantive weakness or feasible task-relevant improvement with material benefit under this criterion. Establish this through complete observation and an active search for plausible shortcomings; absence of a noticed error does not prove full refinement.",
"3": "Exceptional beyond conventional full refinement: fully meets +2, then demonstrates a non-obvious design with a substantial additional benefit. Product and configuration references carry a useful conceptual distinction across changing use cases, reducing reinterpretation beyond flawless naming continuity. In reason identify the choice, real difficulty, benefit beyond an equally correct/complete/polished conventional solution, and observed evidence. These benefit descriptions do not prescribe a unique design. Repeating +2 strengths, adding complexity or expressing amazement is insufficient; without the exceptional evidence, the ceiling is +2."
},
"weight": 4,
"benchmark_source": "vas"
},
{
"id": "V1",
"dimension": "Visuals",
"criterion": "Within-page hierarchy and focus.\nObject of measurement: Each page's title, selling-point body, and condition statements form a clear visual hierarchy, and launch priorities can be located quickly.\nObservation scope: 6-page English PPTX and PNG, following the existing template, a 2023-09-28 launch introduction for developers and makers.\nObservation basis: Check the size and position contrast between each page's title and body. Judge whether prices or core selling points are the visual focus. Check whether condition statements are at a secondary level but not ignored.\nScoring boundary: The salience relationships among title, body, evidence, and supporting information; evaluate attention entry points, core focus, and emphasis strength.\nNegative-score scope: Judge the extent and severity of defects in this visual criterion; functional unusability is not a prerequisite. Retain the concrete defect examples and assess only permitted edits and newly introduced regressions where applicable.\nFull-refinement check (+2): The most crowded configuration or accessory slide retains a clear focus without visually suppressing a required caveat.\nExceptional check (+3): A content-specific hierarchy makes both a benefit and its decisive qualification salient without competing emphasis, beyond a fully refined conventional headline-detail layout.",
"answers": {
"-3": "Severe failure: This item’s visual goal is severely impaired. Specific manifestations: no hierarchy, and readers cannot find the page's focus. Judged by the above actual impact; harmless minor differences do not trigger this level.",
"-2": "Clearly unacceptable: This item's main areas or key processes are persistently damaged. Specific manifestations: titles compete with body text or the focus is wrong. Judged by the above actual impact; harmless minor differences do not trigger this level.",
"-1": "Below basic requirements: This item has clear local substantive defects. Specific manifestations: some page's hierarchy is vague and condition statements are drowned out. Judged by the above actual impact; harmless minor differences do not trigger this level.",
"0": "Basically acceptable: Hierarchy is discernible and the focus can be found; this item's necessary requirements are fully satisfied, with no substantive defects and ordinary performance.",
"1": "Accomplished but not yet fully refined: meets tier 0 and demonstrates a substantive, observable quality gain. One slide distinguishes its principal benefit from supporting specification and qualification. A specific remaining opportunity or failure to meet the complete +2 quality conditions keeps the item at this tier; explain the actual gap in reason. Ordinary correctness alone is not excellent execution.",
"2": "Fully refined within scope: meets tier 0 and achieves the following throughout every applicable part of this item, not just one successful local example. Product, configuration and condition have coordinated levels of emphasis across the template layouts. Difficult-case check: The most crowded configuration or accessory slide retains a clear focus without visually suppressing a required caveat. Across the full applicable scope, there is no identifiable substantive weakness or feasible task-relevant improvement with material benefit under this criterion. Establish this through complete observation and an active search for plausible shortcomings; absence of a noticed error does not prove full refinement.",
"3": "Exceptional beyond conventional full refinement: fully meets +2, then demonstrates a non-obvious design with a substantial additional benefit. A content-specific hierarchy makes both a benefit and its decisive qualification salient without competing emphasis, beyond a fully refined conventional headline-detail layout. In reason identify the choice, real difficulty, benefit beyond an equally correct/complete/polished conventional solution, and observed evidence. These benefit descriptions do not prescribe a unique design. Repeating +2 strengths, adding complexity or expressing amazement is insufficient; without the exceptional evidence, the ceiling is +2."
},
"weight": 5,
"benchmark_source": "vas"
},
{
"id": "V2",
"dimension": "Visuals",
"criterion": "Block proportions and whitespace.\nObject of measurement: The proportions of image and text blocks, alignment, and whitespace suit presentation viewing, with no important content overflow or large empty areas.\nObservation scope: 6-page English PPTX and PNG, following the existing template, a 2023-09-28 launch introduction for developers and makers.\nObservation basis: Check whether text runs off the page or covers images. Observe whether the proportions of image and text blocks are coordinated. Check whether there are obvious empty or crowded pages.\nScoring boundary: Area proportions among information blocks, grid, edges, center of gravity, density, and whitespace; evaluate overall composition and spatial organization.\nNegative-score scope: Judge the extent and severity of defects in this visual criterion; functional unusability is not a prerequisite. Retain the concrete defect examples and assess only permitted edits and newly introduced regressions where applicable.\nFull-refinement check (+2): The longest chosen use-case description fits the template with breathing room and without violating retained layout rules.\nExceptional check (+3): A creative adaptation of the existing template resolves the most difficult image/copy/condition space conflict with unusual clarity and balance, without breaking retained rules.",
"answers": {
"-3": "Severe failure: This item’s visual goal is severely impaired. Specific manifestations: content overflow or layout collapse impairs reading. Judged by the above actual impact; harmless minor differences do not trigger this level.",
"-2": "Clearly unacceptable: This item's main areas or key processes are persistently damaged. Specific manifestations: imbalanced block proportions or whitespace causes cramped content. Judged by the above actual impact; harmless minor differences do not trigger this level.",
"-1": "Below basic requirements: This item has clear local substantive defects. Specific manifestations: individual pages have clearly uncoordinated alignment or whitespace. Judged by the above actual impact; harmless minor differences do not trigger this level.",
"0": "Basically acceptable: Layout is balanced and readable; this item's necessary requirements are fully satisfied, with no substantive defects and ordinary performance.",
"1": "Accomplished but not yet fully refined: meets tier 0 and demonstrates a substantive, observable quality gain. A template block is allocated space according to the actual copy or image it contains. A specific remaining opportunity or failure to meet the complete +2 quality conditions keeps the item at this tier; explain the actual gap in reason. Ordinary correctness alone is not excellent execution.",
"2": "Fully refined within scope: meets tier 0 and achieves the following throughout every applicable part of this item, not just one successful local example. Content density, image proportions and whitespace are balanced across the selected template layouts. Difficult-case check: The longest chosen use-case description fits the template with breathing room and without violating retained layout rules. Across the full applicable scope, there is no identifiable substantive weakness or feasible task-relevant improvement with material benefit under this criterion. Establish this through complete observation and an active search for plausible shortcomings; absence of a noticed error does not prove full refinement.",
"3": "Exceptional beyond conventional full refinement: fully meets +2, then demonstrates a non-obvious design with a substantial additional benefit. A creative adaptation of the existing template resolves the most difficult image/copy/condition space conflict with unusual clarity and balance, without breaking retained rules. In reason identify the choice, real difficulty, benefit beyond an equally correct/complete/polished conventional solution, and observed evidence. These benefit descriptions do not prescribe a unique design. Repeating +2 strengths, adding complexity or expressing amazement is insufficient; without the exceptional evidence, the ceiling is +2."
},
"weight": 8,
"benchmark_source": "vas"
},
{
"id": "V3",
"dimension": "Visuals",
"criterion": "Font sizes, line spacing, and presentation readability.\nObject of measurement: Title, body, and annotation font sizes and line spacing are readable at presentation viewing scale, and English line breaks are reasonable.\nObservation scope: 6-page English PPTX and PNG, following the existing template, a 2023-09-28 launch introduction for developers and makers.\nObservation basis: View the minimum body font size at presentation scale. Check line breaks and orphan words in long English sentences. Confirm that condition statements and price figures are not truncated.\nScoring boundary: The complete visibility of text in the actual delivered image, font size, contrast, line spacing, and line breaks; evaluate text presentation and reading at the target scale.\nNegative-score scope: Judge the extent and severity of defects in this visual criterion; functional unusability is not a prerequisite. Retain the concrete defect examples and assess only permitted edits and newly introduced regressions where applicable.\nFull-refinement check (+2): The smallest necessary qualification and longest label remain comfortably readable on the densest slide, not merely present without clipping.\nExceptional check (+3): Typographic organization reveals configuration or accessory relationships as the reader scans, delivering more than immaculate legibility and consistency.",
"answers": {
"-3": "Severe failure: This item’s visual goal is severely impaired. Specific manifestations: key text is too small or line breaks are chaotic and unreadable. Judged by the above actual impact; harmless minor differences do not trigger this level.",
"-2": "Clearly unacceptable: This item's main areas or key processes are persistently damaged. Specific manifestations: multiple font-size or line-spacing issues make reading difficult. Judged by the above actual impact; harmless minor differences do not trigger this level.",
"-1": "Below basic requirements: This item has clear local substantive defects. Specific manifestations: individual pages have overly small font sizes or improper line breaks. Judged by the above actual impact; harmless minor differences do not trigger this level.",
"0": "Basically acceptable: Text is readable and font sizes are differentiated; this item's necessary requirements are fully satisfied, with no substantive defects and ordinary performance.",
"1": "Accomplished but not yet fully refined: meets tier 0 and demonstrates a substantive, observable quality gain. Line breaks, sizing or spacing reduce effort in reading a configuration or condition. A specific remaining opportunity or failure to meet the complete +2 quality conditions keeps the item at this tier; explain the actual gap in reason. Ordinary correctness alone is not excellent execution.",
"2": "Fully refined within scope: meets tier 0 and achieves the following throughout every applicable part of this item, not just one successful local example. Headings, specifications, prices and footnotes form a coordinated typographic system at presentation scale. Difficult-case check: The smallest necessary qualification and longest label remain comfortably readable on the densest slide, not merely present without clipping. Across the full applicable scope, there is no identifiable substantive weakness or feasible task-relevant improvement with material benefit under this criterion. Establish this through complete observation and an active search for plausible shortcomings; absence of a noticed error does not prove full refinement.",
"3": "Exceptional beyond conventional full refinement: fully meets +2, then demonstrates a non-obvious design with a substantial additional benefit. Typographic organization reveals configuration or accessory relationships as the reader scans, delivering more than immaculate legibility and consistency. In reason identify the choice, real difficulty, benefit beyond an equally correct/complete/polished conventional solution, and observed evidence. These benefit descriptions do not prescribe a unique design. Repeating +2 strengths, adding complexity or expressing amazement is insufficient; without the exceptional evidence, the ceiling is +2."
},
"weight": 7,
"benchmark_source": "vas"
},
{
"id": "V4",
"dimension": "Visuals",
"criterion": "Accurate decoding of graphics and data symbols.\nObject of measurement: Product images, specification diagrams, arrows, or comparison symbols have clear meanings themselves and readable labels, and unclear graphics do not prevent readers from understanding configurations or port conditions.\nObservation scope: 6-page English PPTX and PNG, following the existing template, a 2023-09-28 launch introduction for developers and makers.\nObservation basis: Check whether the symbols and arrows in port or power diagrams are recognizable and whether labels are readable. Check whether image labels correspond visually to the actual product images, with no obvious pointing at the wrong object. Confirm that arrows, comparison symbols, or graphic groupings can be decoded consistently within the page and do not clearly contradict the same page's text to the point of being incomprehensible.\nScoring boundary: The recognizability and semantic correspondence of graphic marks, lines, arrows, symbols, and dynamic states; evaluate accurate decoding and reliable comparison.\nNegative-score scope: Judge the extent and severity of defects in this visual criterion; functional unusability is not a prerequisite. Retain the concrete defect examples and assess only permitted edits and newly introduced regressions where applicable.\nFull-refinement check (+2): The most complex chosen comparison remains decodable without implying unsupported capability or a misleading scale; no extra diagram is required.\nExceptional check (+3): A visual representation makes a supported capability-condition relationship directly understandable, avoiding mental assembly from correct specifications; no additional diagram is mandatory.",
"answers": {
"-3": "Severe failure: This item’s visual goal is severely impaired. Specific manifestations: diagrams convey wrong configuration or port information. Judged by the above actual impact; harmless minor differences do not trigger this level.",
"-2": "Clearly unacceptable: This item's main areas or key processes are persistently damaged. Specific manifestations: graphic meanings are ambiguous or contradict text. Judged by the above actual impact; harmless minor differences do not trigger this level.",
"-1": "Below basic requirements: This item has clear local substantive defects. Specific manifestations: individual symbols or labels are unclear. Judged by the above actual impact; harmless minor differences do not trigger this level.",
"0": "Basically acceptable: Graphics are understandable with no substantive misleading; this item's necessary requirements are fully satisfied, with no substantive defects and ordinary performance.",
"1": "Accomplished but not yet fully refined: meets tier 0 and demonstrates a substantive, observable quality gain. A product diagram or comparison symbol has a direct, helpful correspondence to its label. A specific remaining opportunity or failure to meet the complete +2 quality conditions keeps the item at this tier; explain the actual gap in reason. Ordinary correctness alone is not excellent execution.",
"2": "Fully refined within scope: meets tier 0 and achieves the following throughout every applicable part of this item, not just one successful local example. Visual encodings and annotations reinforce the chosen configurations or benefits consistently. Difficult-case check: The most complex chosen comparison remains decodable without implying unsupported capability or a misleading scale; no extra diagram is required. Across the full applicable scope, there is no identifiable substantive weakness or feasible task-relevant improvement with material benefit under this criterion. Establish this through complete observation and an active search for plausible shortcomings; absence of a noticed error does not prove full refinement.",
"3": "Exceptional beyond conventional full refinement: fully meets +2, then demonstrates a non-obvious design with a substantial additional benefit. A visual representation makes a supported capability-condition relationship directly understandable, avoiding mental assembly from correct specifications; no additional diagram is mandatory. In reason identify the choice, real difficulty, benefit beyond an equally correct/complete/polished conventional solution, and observed evidence. These benefit descriptions do not prescribe a unique design. Repeating +2 strengths, adding complexity or expressing amazement is insufficient; without the exceptional evidence, the ceiling is +2."
},
"weight": 5,
"benchmark_source": "vas"
},
{
"id": "V5",
"dimension": "Visuals",
"criterion": "Integration of the template visual system and graphic language.\nObject of measurement: Non-color graphic abstraction, typographic tone, product images, and component language are integrated along the template visual system and suit the developer launch scenario.\nObservation scope: 6-page English PPTX and PNG, following the existing template, a 2023-09-28 launch introduction for developers and makers.\nObservation basis: Observe whether product images and template graphic elements are coordinated in style and visual language. Judge whether the typographic tone is consistent with the template's existing hierarchy and stable across pages, without imposing a fixed aesthetic. Check whether graphic components and typographic language continue across pages; color coordination serves only as supporting evidence and does not alone support a high score.\nScoring boundary: Audience, purpose, medium character, and the integration of graphic abstraction, typography, imagery, and component surface language; pure color aesthetics is deferred to V9.\nScenario reference · visual language (adds no threshold): Follow the given template visual system, unify title hierarchy and footers, integrate graphic abstraction and typographic tone, and do not pursue a specific reference layout.\nScenario reference · design constraints (adds no threshold): The 2026 handbook and images easily induce later specifications to be mixed in; template example copy is easily taken as fact; prices need to distinguish capacity and pre-tax framing.\nScenario reference · design goals (adds no threshold): Strictly lock launch facts, three or more conditionally supported selling points, template rules preserved with clear hierarchy on every page, and images, text, and explanations self-consistent.\nScoring boundary: V9 independently evaluates the aesthetic coordination and refinement of color; reading impairment caused by text contrast belongs to V3, color-to-object meaning mismatch belongs to V4, and cross-page color-code identity drift belongs to V7. Attribute across items only when a different functional impairment is demonstrated. V5 must not merely repeat V9's color quality, and V9 must not directly award a professional level on the grounds of \"fitting the scenario\".\nThis task's applicable boundary (all relevant entries apply; adds no scoring items): Reproducing a specific reference layout or reference artifact is not required.\nNegative-score scope: Judge the extent and severity of defects in this visual criterion; functional unusability is not a prerequisite. Retain the concrete defect examples and assess only permitted edits and newly introduced regressions where applicable.\nFull-refinement check (+2): Accessory conditions and dense technical content feel integrated rather than pasted onto an otherwise polished template; no redesign of the template is required.\nExceptional check (+3): The new content and existing template produce a distinctive, coherent launch language that expresses the product's developer context, beyond seamless template matching; identify a non-color contribution.",
"answers": {
"-3": "Severe failure: This item’s visual goal is severely impaired. Specific manifestations: visual language is chaotic and breaks from the template system. Judged by the above actual impact; harmless minor differences do not trigger this level.",
"-2": "Clearly unacceptable: This item's main areas or key processes are persistently damaged. Specific manifestations: graphic style or typographic tone is clearly uncoordinated. Judged by the above actual impact; harmless minor differences do not trigger this level.",
"-1": "Below basic requirements: This item has clear local substantive defects. Specific manifestations: individual pages' graphics or tone deviate from the template. Judged by the above actual impact; harmless minor differences do not trigger this level.",
"0": "Basically acceptable: Visual style is unified and suits the launch scenario; this item's necessary requirements are fully satisfied, with no substantive defects and ordinary performance.",
"1": "Accomplished but not yet fully refined: meets tier 0 and demonstrates a substantive, observable quality gain. A non-color choice in typography or graphic abstraction integrates new content with the template. A specific remaining opportunity or failure to meet the complete +2 quality conditions keeps the item at this tier; explain the actual gap in reason. Ordinary correctness alone is not excellent execution.",
"2": "Fully refined within scope: meets tier 0 and achieves the following throughout every applicable part of this item, not just one successful local example. Product imagery, diagrams and text share the template's visual language while serving actual launch content. Difficult-case check: Accessory conditions and dense technical content feel integrated rather than pasted onto an otherwise polished template; no redesign of the template is required. Across the full applicable scope, there is no identifiable substantive weakness or feasible task-relevant improvement with material benefit under this criterion. Establish this through complete observation and an active search for plausible shortcomings; absence of a noticed error does not prove full refinement.",
"3": "Exceptional beyond conventional full refinement: fully meets +2, then demonstrates a non-obvious design with a substantial additional benefit. The new content and existing template produce a distinctive, coherent launch language that expresses the product's developer context, beyond seamless template matching; identify a non-color contribution. In reason identify the choice, real difficulty, benefit beyond an equally correct/complete/polished conventional solution, and observed evidence. These benefit descriptions do not prescribe a unique design. Repeating +2 strengths, adding complexity or expressing amazement is insufficient; without the exceptional evidence, the ceiling is +2."
},
"weight": 7,
"benchmark_source": "vas"
},
{
"id": "V6",
"dimension": "Visuals",
"criterion": "Local geometry and optical alignment.\nObject of measurement: Graphic endpoints, line widths, cropping, and optical alignment are clean on the page, with no obvious rough edges or misalignment.\nObservation scope: 6-page English PPTX and PNG, following the existing template, a 2023-09-28 launch introduction for developers and makers.\nObservation basis: Zoom in to check product image crop edges. Check the alignment of divider lines and arrow endpoints. Observe whether text boxes and graphic edges are optically aligned.\nScoring boundary: Graphic contours, line widths, endpoints, image proportions and cropping, and intra-component geometric and optical alignment; evaluate local construction precision.\nNegative-score scope: Judge the extent and severity of defects in this visual criterion; functional unusability is not a prerequisite. Retain the concrete defect examples and assess only permitted edits and newly introduced regressions where applicable.\nFull-refinement check (+2): Crowded specification labels and small condition blocks retain the same precision as large product visuals.\nExceptional check (+3): Local precision resolves a demanding small-component or annotation ambiguity in the adapted template, rather than merely demonstrating clean alignment everywhere.",
"answers": {
"-3": "Severe failure: This item’s visual goal is severely impaired. Specific manifestations: cropping or alignment errors impair readability. Judged by the above actual impact; harmless minor differences do not trigger this level.",
"-2": "Clearly unacceptable: This item's main areas or key processes are persistently damaged. Specific manifestations: multiple inconsistent line widths or endpoints cause clutter. Judged by the above actual impact; harmless minor differences do not trigger this level.",
"-1": "Below basic requirements: This item has clear local substantive defects. Specific manifestations: individual graphics are misaligned or improperly cropped. Judged by the above actual impact; harmless minor differences do not trigger this level.",
"0": "Basically acceptable: Local graphics are clean; this item's necessary requirements are fully satisfied, with no substantive defects and ordinary performance.",
"1": "Accomplished but not yet fully refined: meets tier 0 and demonstrates a substantive, observable quality gain. A group of image edges, icon labels or text baselines shows careful local alignment. A specific remaining opportunity or failure to meet the complete +2 quality conditions keeps the item at this tier; explain the actual gap in reason. Ordinary correctness alone is not excellent execution.",
"2": "Fully refined within scope: meets tier 0 and achieves the following throughout every applicable part of this item, not just one successful local example. Line weights, spacing and optical alignment are consistently finished across the newly authored components. Difficult-case check: Crowded specification labels and small condition blocks retain the same precision as large product visuals. Across the full applicable scope, there is no identifiable substantive weakness or feasible task-relevant improvement with material benefit under this criterion. Establish this through complete observation and an active search for plausible shortcomings; absence of a noticed error does not prove full refinement.",
"3": "Exceptional beyond conventional full refinement: fully meets +2, then demonstrates a non-obvious design with a substantial additional benefit. Local precision resolves a demanding small-component or annotation ambiguity in the adapted template, rather than merely demonstrating clean alignment everywhere. In reason identify the choice, real difficulty, benefit beyond an equally correct/complete/polished conventional solution, and observed evidence. These benefit descriptions do not prescribe a unique design. Repeating +2 strengths, adding complexity or expressing amazement is insufficient; without the exceptional evidence, the ceiling is +2."
},
"weight": 6,
"benchmark_source": "vas"
},
{
"id": "V7",
"dimension": "Visuals",
"criterion": "Cross-page visible identity and visual consistency.\nObject of measurement: The six pages maintain visible identity consistency in color usage, title style, footers, and graphic language.\nObservation scope: 6-page English PPTX and PNG, following the existing template, a 2023-09-28 launch introduction for developers and makers.\nObservation basis: Compare title styles and footer positions across the six pages. Check whether color usage is consistent rather than merely identical in color values. Observe whether graphic language continues across pages.\nScoring boundary: The stable correspondence of the same object, identity, markers, styles, and content across pages, states, and carriers; evaluate visual inheritance.\nNegative-score scope: Judge the extent and severity of defects in this visual criterion; functional unusability is not a prerequisite. Retain the concrete defect examples and assess only permitted edits and newly introduced regressions where applicable.\nFull-refinement check (+2): The densest adapted layout retains that system in both PPTX and PNG without local style or export drift.\nExceptional check (+3): Recurring visual identity helps readers recognize a product or configuration through different use-case layouts without re-decoding it, beyond identical styling and matching exports.",
"answers": {
"-3": "Severe failure: This item’s visual goal is severely impaired. Specific manifestations: styles change abruptly from page to page, as if different presentations were spliced together. Judged by the above actual impact; harmless minor differences do not trigger this level.",
"-2": "Clearly unacceptable: This item's main areas or key processes are persistently damaged. Specific manifestations: title or footer styles are inconsistent across multiple pages. Judged by the above actual impact; harmless minor differences do not trigger this level.",
"-1": "Below basic requirements: This item has clear local substantive defects. Specific manifestations: individual pages' elements deviate from the overall style. Judged by the above actual impact; harmless minor differences do not trigger this level.",
"0": "Basically acceptable: Style is unified across pages; this item's necessary requirements are fully satisfied, with no substantive defects and ordinary performance.",
"1": "Accomplished but not yet fully refined: meets tier 0 and demonstrates a substantive, observable quality gain. A recurring configuration or product element has a stable visible identity across slides. A specific remaining opportunity or failure to meet the complete +2 quality conditions keeps the item at this tier; explain the actual gap in reason. Ordinary correctness alone is not excellent execution.",
"2": "Fully refined within scope: meets tier 0 and achieves the following throughout every applicable part of this item, not just one successful local example. Template components, recurring symbols and slide previews preserve a coherent visual system. Difficult-case check: The densest adapted layout retains that system in both PPTX and PNG without local style or export drift. Across the full applicable scope, there is no identifiable substantive weakness or feasible task-relevant improvement with material benefit under this criterion. Establish this through complete observation and an active search for plausible shortcomings; absence of a noticed error does not prove full refinement.",
"3": "Exceptional beyond conventional full refinement: fully meets +2, then demonstrates a non-obvious design with a substantial additional benefit. Recurring visual identity helps readers recognize a product or configuration through different use-case layouts without re-decoding it, beyond identical styling and matching exports. In reason identify the choice, real difficulty, benefit beyond an equally correct/complete/polished conventional solution, and observed evidence. These benefit descriptions do not prescribe a unique design. Repeating +2 strengths, adding complexity or expressing amazement is insufficient; without the exceptional evidence, the ceiling is +2."
},
"weight": 3,
"benchmark_source": "vas"
},
{
"id": "V8",
"dimension": "Visuals",
"criterion": "Static reading path and dwell experience.\nObject of measurement: As a static presentation, each page's information dwell rhythm along the actual reading path is reasonable, with clear entry points and closure.\nObservation scope: 6-page English PPTX and PNG, following the existing template, a 2023-09-28 launch introduction for developers and makers.\nObservation basis: Judge each page's first point of attention by the line-of-sight starting point. Check whether pages have clear closure rather than dangling. Observe whether multi-element pages guide sequential reading.\nScoring boundary: Movement of the gaze between information units, and content reveal, dwell, motion, and transitions; evaluate scanning and time rhythm.\nNegative-score scope: Judge the extent and severity of defects in this visual criterion; functional unusability is not a prerequisite. Retain the concrete defect examples and assess only permitted edits and newly introduced regressions where applicable.\nFull-refinement check (+2): The most detailed configuration slide supports both quick orientation and closer inspection without repeatedly searching for the relevant condition.\nExceptional check (+3): A scanning solution supports immediate benefit discovery and close condition checking with substantially less backtracking than a flawlessly tidy conventional deck.",
"answers": {
"-3": "Severe failure: This item’s visual goal is severely impaired. Specific manifestations: pages have no reading entry point, and it is unclear where to start reading the information. Judged by the above actual impact; harmless minor differences do not trigger this level.",
"-2": "Clearly unacceptable: This item's main areas or key processes are persistently damaged. Specific manifestations: reading paths jump or pages lack closure. Judged by the above actual impact; harmless minor differences do not trigger this level.",
"-1": "Below basic requirements: This item has clear local substantive defects. Specific manifestations: individual pages' reading order is vague. Judged by the above actual impact; harmless minor differences do not trigger this level.",
"0": "Basically acceptable: Every page has a discernible reading start and path; this item's necessary requirements are fully satisfied, with no substantive defects and ordinary performance.",
"1": "Accomplished but not yet fully refined: meets tier 0 and demonstrates a substantive, observable quality gain. A slide's benefit-to-condition scanning route reduces needless backtracking. A specific remaining opportunity or failure to meet the complete +2 quality conditions keeps the item at this tier; explain the actual gap in reason. Ordinary correctness alone is not excellent execution.",
"2": "Fully refined within scope: meets tier 0 and achieves the following throughout every applicable part of this item, not just one successful local example. Slide entry points, feature groups and notes form a steady static reading rhythm. Difficult-case check: The most detailed configuration slide supports both quick orientation and closer inspection without repeatedly searching for the relevant condition. Across the full applicable scope, there is no identifiable substantive weakness or feasible task-relevant improvement with material benefit under this criterion. Establish this through complete observation and an active search for plausible shortcomings; absence of a noticed error does not prove full refinement.",
"3": "Exceptional beyond conventional full refinement: fully meets +2, then demonstrates a non-obvious design with a substantial additional benefit. A scanning solution supports immediate benefit discovery and close condition checking with substantially less backtracking than a flawlessly tidy conventional deck. In reason identify the choice, real difficulty, benefit beyond an equally correct/complete/polished conventional solution, and observed evidence. These benefit descriptions do not prescribe a unique design. Repeating +2 strengths, adding complexity or expressing amazement is insufficient; without the exceptional evidence, the ceiling is +2."
},
"weight": 3,
"benchmark_source": "vas"
},
{
"id": "V9",
"dimension": "Visuals",
"criterion": "Color aesthetics and image background integration.\nObject of measurement: Color aesthetics are coordinated in hue, lightness, saturation, and area allocation, and product image backgrounds blend with the layout.\nObservation scope: 6-page English PPTX and PNG, following the existing template, a 2023-09-28 launch introduction for developers and makers.\nObservation basis: Observe whether the area of accent color use is restrained. Check the relationship between product image backgrounds and the page background. Judge whether hue and lightness allocation are coordinated.\nScoring boundary: Hue, lightness, saturation × area, accent colors, and the aesthetic relationship between images/backgrounds; demonstrate quality goals separately from V3/V4/V5/V7.\nObservation elements: Hue compatibility and warm-cool relationships. Lightness hierarchy and color center of gravity. Saturation × area ratio. Number, weight, and restraint of accent colors. Integration of images, graphics, panels, and backgrounds.\nScoring boundary: V9 independently evaluates the aesthetic coordination and refinement of color; reading impairment caused by text contrast belongs to V3, color-to-object meaning mismatch belongs to V4, and cross-page color-code identity drift belongs to V7. Attribute across items only when a different functional impairment is demonstrated. V5 must not merely repeat V9's color quality, and V9 must not directly award a professional level on the grounds of \"fitting the scenario\".\nApply negative examples to this task’s designable areas; reading contrast belongs to V3 and encoding meaning to V4, and neither alone substitutes for evaluating color relationships.\nFull-refinement check (+2): The hardest-to-integrate image or dense specification area remains balanced and restrained; a fashionable palette or unmodified template alone earns no bonus.\nExceptional check (+3): Image tones and template colors are reconciled with unusually refined hue/lightness/area control in the hardest mixed-content slide, yielding a perceptual benefit beyond ordinary harmonious branding.",
"answers": {
"-3": "The primary subjects, background and accents have fundamentally incoherent color relationships, so this item’s color-composition goal fails. Identify the actual relationships and locations; personal palette preference is not evidence.",
"-2": "Across main affected areas, repeated hue/lightness/saturation or accent-area conflicts create persistently harsh, muddy or unbalanced color composition. This can be a substantial visual defect even when content remains readable.",
"-1": "A local, material mismatch of hue, lightness, saturation or accent area disrupts color harmony. Identify the affected relationship; harmless style differences and merely lacking novelty are not defects.",
"0": "Basically acceptable: Colors are coordinated and images can blend in; this item's necessary requirements are fully satisfied, with no substantive defects and ordinary performance.",
"1": "Accomplished but not yet fully refined: meets tier 0 and demonstrates a substantive, observable quality gain. A specific relationship between image tones, background and accent area improves color harmony. A specific remaining opportunity or failure to meet the complete +2 quality conditions keeps the item at this tier; explain the actual gap in reason. Ordinary correctness alone is not excellent execution.",
"2": "Fully refined within scope: meets tier 0 and achieves the following throughout every applicable part of this item, not just one successful local example. Product imagery, template colors and emphasis work together across different content densities. Difficult-case check: The hardest-to-integrate image or dense specification area remains balanced and restrained; a fashionable palette or unmodified template alone earns no bonus. Across the full applicable scope, there is no identifiable substantive weakness or feasible task-relevant improvement with material benefit under this criterion. Establish this through complete observation and an active search for plausible shortcomings; absence of a noticed error does not prove full refinement.",
"3": "Exceptional beyond conventional full refinement: fully meets +2, then demonstrates a non-obvious design with a substantial additional benefit. Image tones and template colors are reconciled with unusually refined hue/lightness/area control in the hardest mixed-content slide, yielding a perceptual benefit beyond ordinary harmonious branding. In reason identify the choice, real difficulty, benefit beyond an equally correct/complete/polished conventional solution, and observed evidence. These benefit descriptions do not prescribe a unique design. Repeating +2 strengths, adding complexity or expressing amazement is insufficient; without the exceptional evidence, the ceiling is +2."
},
"weight": 6,
"benchmark_source": "vas"
},
{
"id": "D1",
"dimension": "Delivery",
"criterion": "Delivered files can be opened and located directly.\nMeasurement object: the PPTX can be opened, the six PNGs correspond to the final PPTX, and sources.md and delivery.md are in artifact/ and can be directly located and used.\nObservation scope: 6-page English PPTX and PNG, following the existing template, a 2023-09-28 release introduction for developers and makers.\nObservation basis: open the PPTX and confirm six pages. Compare the PNG and PPTX content page by page. Check that sources.md and delivery.md exist in artifact/ and can be located.\nScoring boundary: opening, locating, and direct use of the required files; V7 evaluates the consistency of actually visible content and does not substitute file existence for quality.\nScenario reference · medium (no additional threshold): 16:9 presentation PPTX and page-by-page PNG static delivery.\nApplicable boundary for this task (applies to all relevant items, no additional scoring items): input/workspace/sources/, input/workspace/templates/, input/workspace/assets/, and input/workspace/README.md are read-only originals and must not be modified.\nApplicable boundary for this task (applies to all relevant items, no additional scoring items): deliverables go in artifact/.\nFull-refinement check (+2): The final six-slide version and its previews remain immediately identifiable among necessary companion files without trial-and-error opening.\nExceptional check (+3): Within the required files and opening guidance, the handoff removes a genuine final-version or preview-selection ambiguity more elegantly than a conventional complete delivery; extra files do not qualify by themselves.",
"answers": {
"-3": "Severe failure: A core required deliverable is missing or, because of its own defects, cannot be opened/used as a whole, making the task's core use objective impossible to achieve; first rule out evaluation-tool and environment failures.",
"-2": "Clearly unacceptable: Required content is missing on a large scale, or key opening/locating processes are persistently obstructed, requiring substantial remediation of the main use workflow; judge according to actual impact, not by mechanically assigning a tier based solely on a single discrepancy in file count.",
"-1": "Below basic requirements: There is a clear, localized issue involving a missing deliverable, version identification, file correspondence, or opening instructions that affects necessary use under this criterion, while the remaining core content is usable.",
"0": "Basically acceptable: the six-page PPTX and PNG are complete and can be opened; the necessary requirements of this item are fully met, with no substantive defects, and performance is ordinary.",
"1": "Accomplished but not yet fully refined: meets tier 0 and demonstrates a substantive, observable quality gain. Final PPTX and previews have a clear correspondence that reduces file-selection effort. A specific remaining opportunity or failure to meet the complete +2 quality conditions keeps the item at this tier; explain the actual gap in reason. Ordinary correctness alone is not excellent execution.",
"2": "Fully refined within scope: meets tier 0 and achieves the following throughout every applicable part of this item, not just one successful local example. File organization, page ordering and existing opening instructions support direct use of the launch deck. Difficult-case check: The final six-slide version and its previews remain immediately identifiable among necessary companion files without trial-and-error opening. Across the full applicable scope, there is no identifiable substantive weakness or feasible task-relevant improvement with material benefit under this criterion. Establish this through complete observation and an active search for plausible shortcomings; absence of a noticed error does not prove full refinement.",
"3": "Exceptional beyond conventional full refinement: fully meets +2, then demonstrates a non-obvious design with a substantial additional benefit. Within the required files and opening guidance, the handoff removes a genuine final-version or preview-selection ambiguity more elegantly than a conventional complete delivery; extra files do not qualify by themselves. In reason identify the choice, real difficulty, benefit beyond an equally correct/complete/polished conventional solution, and observed evidence. These benefit descriptions do not prescribe a unique design. Repeating +2 strengths, adding complexity or expressing amazement is insufficient; without the exceptional evidence, the ceiling is +2."
},
"weight": 4,
"benchmark_source": "vas"
},
{
"id": "D2",
"dimension": "Delivery",
"criterion": "Editable structure and template rules are retained.\nMeasurement object: text and graphics are editable, not purely full-page images, and the template theme colors, title hierarchy, footer style, and editable text structure are retained.\nObservation scope: 6-page English PPTX and PNG, following the existing template, a 2023-09-28 release introduction for developers and makers.\nObservation basis: spot-check whether text boxes and graphics are editable. Check whether the theme colors and title hierarchy follow the template. Confirm that the footer/page number style is retained.\nScoring boundary: the editable structure, resources, and material organization of the objects required by the prompt; no engineering scripts or additional tests are required.\nApplicable boundary for this task (applies to all relevant items, no additional scoring items): no specific scripts, compilation environment, or animation/video delivery are required.\nApplicable boundary for this task (applies to all relevant items, no additional scoring items): the source file language is not required to be Chinese; the target product is English.\nApplicable boundary for this task (applies to all relevant items, no additional scoring items): the template theme colors, title hierarchy, page number/footer style, and editable text structure must be retained.\nFull-refinement check (+2): The densest adapted layout remains structurally understandable and its required resources are resolvable without an extra refactoring or editing experiment.\nExceptional check (+3): Native object relationships make a complex template adaptation unusually transparent to a maintainer, reducing content-to-template mapping effort beyond fully refined editability and grouping.",
"answers": {
"-3": "Severe failure: the core understanding or usage goal of this item cannot be completed. Specific manifestation: the core content is a full-page image and is not editable. Judge by the above actual impact; harmless minor differences do not trigger this level.",
"-2": "Clearly unacceptable: the main area or key process of this item is persistently impaired. Specific manifestation: a large amount of text is converted to images or the template structure is broken. Judge by the above actual impact; harmless minor differences do not trigger this level.",
"-1": "Below basic requirements: this item has a clear local substantive defect. Specific manifestation: individual pages rely on images or the footer rules are not retained. Judge by the above actual impact; harmless minor differences do not trigger this level.",
"0": "Basically acceptable: the newly added text, graphics, and template-required structure are complete and editable as specified by the prompt, and necessary resources can be parsed; the boundary between native content and permitted raster assets is correct, and it does not depend on the author's private missing paths; the necessary requirements of this item are fully met, with no substantive defects, and performance is ordinary.",
"1": "Accomplished but not yet fully refined: meets tier 0 and demonstrates a substantive, observable quality gain. Meaningful object grouping makes one class of editable launch content easier to locate. A specific remaining opportunity or failure to meet the complete +2 quality conditions keeps the item at this tier; explain the actual gap in reason. Ordinary correctness alone is not excellent execution.",
"2": "Fully refined within scope: meets tier 0 and achieves the following throughout every applicable part of this item, not just one successful local example. New text, graphics and template structures have coordinated editing relationships rather than merely existing as native objects. Difficult-case check: The densest adapted layout remains structurally understandable and its required resources are resolvable without an extra refactoring or editing experiment. Across the full applicable scope, there is no identifiable substantive weakness or feasible task-relevant improvement with material benefit under this criterion. Establish this through complete observation and an active search for plausible shortcomings; absence of a noticed error does not prove full refinement.",
"3": "Exceptional beyond conventional full refinement: fully meets +2, then demonstrates a non-obvious design with a substantial additional benefit. Native object relationships make a complex template adaptation unusually transparent to a maintainer, reducing content-to-template mapping effort beyond fully refined editability and grouping. In reason identify the choice, real difficulty, benefit beyond an equally correct/complete/polished conventional solution, and observed evidence. These benefit descriptions do not prescribe a unique design. Repeating +2 strengths, adding complexity or expressing amazement is insufficient; without the exceptional evidence, the ceiling is +2."
},
"weight": 3,
"benchmark_source": "vas"
},
{
"id": "D3",
"dimension": "Delivery",
"criterion": "Provenance and delivery notes are verifiable.\nMeasurement object: sources.md records versions, factual citations, and asset sources, and delivery.md gives file locations and opening instructions, all verifiable.\nObservation scope: 6-page English PPTX and PNG, following the existing template, a 2023-09-28 release introduction for developers and makers.\nObservation basis: check whether sources.md records the source launch article and template asset sources. Check whether delivery.md gives opening instructions and file locations. Confirm that the version statements in the notes are consistent with the content.\nScoring boundary: the verifiability of the required sources, calculations/changes/captures, or usage instructions; select according to the actual requirements of this task, and do not insist on all document types.\nApplicable boundary for this task (applies to all relevant items, no additional scoring items): no extra engineering documentation is required; only the content listed in sources.md and delivery.md is needed.\nFull-refinement check (+2): The most easily confused launch versus later-version material has an explicit traceable use boundary without relying on author assertions alone.\nExceptional check (+3): Launch facts, later material and asset uses are traceable through an economical evidence organization that substantially reduces version-disambiguation effort beyond complete source notes.",
"answers": {
"-3": "Severe failure: the core understanding or usage goal of this item cannot be completed. Specific manifestation: explanatory files are missing or the consistency of content with the output cannot be verified. Judge by the above actual impact; harmless minor differences do not trigger this level.",
"-2": "Clearly unacceptable: the main area or key process of this item is persistently impaired. Specific manifestation: the notes lack key sources or have incorrect location information. Judge by the above actual impact; harmless minor differences do not trigger this level.",
"-1": "Below basic requirements: this item has a clear local substantive defect. Specific manifestation: the notes exist but are incomplete or the citations are vague. Judge by the above actual impact; harmless minor differences do not trigger this level.",
"0": "Basically acceptable: sources.md and delivery.md are complete and verifiable; the necessary requirements of this item are fully met, with no substantive defects, and performance is ordinary.",
"1": "Accomplished but not yet fully refined: meets tier 0 and demonstrates a substantive, observable quality gain. A chosen feature or image can be traced directly to its dated source. A specific remaining opportunity or failure to meet the complete +2 quality conditions keeps the item at this tier; explain the actual gap in reason. Ordinary correctness alone is not excellent execution.",
"2": "Fully refined within scope: meets tier 0 and achieves the following throughout every applicable part of this item, not just one successful local example. Version notes, factual references and asset credits consistently map to the slides they support. Difficult-case check: The most easily confused launch versus later-version material has an explicit traceable use boundary without relying on author assertions alone. Across the full applicable scope, there is no identifiable substantive weakness or feasible task-relevant improvement with material benefit under this criterion. Establish this through complete observation and an active search for plausible shortcomings; absence of a noticed error does not prove full refinement.",
"3": "Exceptional beyond conventional full refinement: fully meets +2, then demonstrates a non-obvious design with a substantial additional benefit. Launch facts, later material and asset uses are traceable through an economical evidence organization that substantially reduces version-disambiguation effort beyond complete source notes. In reason identify the choice, real difficulty, benefit beyond an equally correct/complete/polished conventional solution, and observed evidence. These benefit descriptions do not prescribe a unique design. Repeating +2 strengths, adding complexity or expressing amazement is insufficient; without the exceptional evidence, the ceiling is +2."
},
"weight": 3,
"benchmark_source": "vas"
}
]
|