diff --git a/.gitattributes b/.gitattributes new file mode 100644 index 0000000000000000000000000000000000000000..c8c77223ab48a1419a9f33cdbd5ff0d35a18e88c --- /dev/null +++ b/.gitattributes @@ -0,0 +1,66 @@ +*.7z filter=lfs diff=lfs merge=lfs -text +*.arrow filter=lfs diff=lfs merge=lfs -text +*.avro filter=lfs diff=lfs merge=lfs -text +*.bin filter=lfs diff=lfs merge=lfs -text +*.bz2 filter=lfs diff=lfs merge=lfs -text +*.ckpt filter=lfs diff=lfs merge=lfs -text +*.ftz filter=lfs diff=lfs merge=lfs -text +*.gz filter=lfs diff=lfs merge=lfs -text +*.h5 filter=lfs diff=lfs merge=lfs -text +*.joblib filter=lfs diff=lfs merge=lfs -text +*.lfs.* filter=lfs diff=lfs merge=lfs -text +*.lz4 filter=lfs diff=lfs merge=lfs -text +*.mds filter=lfs diff=lfs merge=lfs -text +*.mlmodel filter=lfs diff=lfs merge=lfs -text +*.model filter=lfs diff=lfs merge=lfs -text +*.msgpack filter=lfs diff=lfs merge=lfs -text +*.npy filter=lfs diff=lfs merge=lfs -text +*.npz filter=lfs diff=lfs merge=lfs -text +*.onnx filter=lfs diff=lfs merge=lfs -text +*.ot filter=lfs diff=lfs merge=lfs -text +*.parquet filter=lfs diff=lfs merge=lfs -text +*.pb filter=lfs diff=lfs merge=lfs -text +*.pickle filter=lfs diff=lfs merge=lfs -text +*.pkl filter=lfs diff=lfs merge=lfs -text +*.pt filter=lfs diff=lfs merge=lfs -text +*.pth filter=lfs diff=lfs merge=lfs -text +*.rar filter=lfs diff=lfs merge=lfs -text +*.safetensors filter=lfs diff=lfs merge=lfs -text +saved_model/**/* filter=lfs diff=lfs merge=lfs -text +*.tar.* filter=lfs diff=lfs merge=lfs -text +*.tar filter=lfs diff=lfs merge=lfs -text +*.tflite filter=lfs diff=lfs merge=lfs -text +*.tgz filter=lfs diff=lfs merge=lfs -text +*.wasm filter=lfs diff=lfs merge=lfs -text +*.xz filter=lfs diff=lfs merge=lfs -text +*.zip filter=lfs diff=lfs merge=lfs -text +*.zst filter=lfs diff=lfs merge=lfs -text +*tfevents* filter=lfs diff=lfs merge=lfs -text +# Audio files - uncompressed +*.pcm filter=lfs diff=lfs merge=lfs -text +*.sam filter=lfs diff=lfs merge=lfs -text +*.raw filter=lfs diff=lfs merge=lfs -text +# Audio files - compressed +*.aac filter=lfs diff=lfs merge=lfs -text +*.flac filter=lfs diff=lfs merge=lfs -text +*.mp3 filter=lfs diff=lfs merge=lfs -text +*.ogg filter=lfs diff=lfs merge=lfs -text +*.wav filter=lfs diff=lfs merge=lfs -text +# Image files - uncompressed +*.bmp filter=lfs diff=lfs merge=lfs -text +*.gif filter=lfs diff=lfs merge=lfs -text +*.png filter=lfs diff=lfs merge=lfs -text +*.tiff filter=lfs diff=lfs merge=lfs -text +# Image files - compressed +*.jpg filter=lfs diff=lfs merge=lfs -text +*.jpeg filter=lfs diff=lfs merge=lfs -text +*.webp filter=lfs diff=lfs merge=lfs -text +# Video files - compressed +*.mp4 filter=lfs diff=lfs merge=lfs -text +*.webm filter=lfs diff=lfs merge=lfs -text +*.xlsx filter=lfs diff=lfs merge=lfs -text +*.docx filter=lfs diff=lfs merge=lfs -text +*.tif filter=lfs diff=lfs merge=lfs -text +*.geojson filter=lfs diff=lfs merge=lfs -text +*.pdf filter=lfs diff=lfs merge=lfs -text +*.pptx filter=lfs diff=lfs merge=lfs -text diff --git a/README.md b/README.md new file mode 100644 index 0000000000000000000000000000000000000000..dd91934b43d93087a0f8e5718bb33f6a3a277a68 --- /dev/null +++ b/README.md @@ -0,0 +1,63 @@ +--- +license: apache-2.0 +task_categories: + - image-text-to-text + - visual-question-answering + - document-question-answering +language: + - en +pretty_name: Multimodal Knowledge Agent (MKA) Showcase Examples +--- + +# Multimodal Knowledge Agent (MKA) — 10 Showcase Examples + +**Multimodal Knowledge Agent (MKA)** is a benchmark from Google DeepMind for evaluating autonomous AI agents on complex, multi-step, real-world visual knowledge work across professional domains. + +Unlike text-extractable benchmarks where attachments can be solved via plain-text extraction or OCR alone, every MKA task contains a multi-file workspace with load-bearing visual artifacts—such as architectural CAD blueprints, electrical and RF schematics, geospatial rasters, seasonal dependency graphs, biochemical gel and spectrophotometric plates, and multi-axis charts—that require native multimodal perception, cross-document synthesis, tool orchestration (code execution, file inspection), and standalone deliverable generation (`.xlsx`, `.pptx`, `.docx`, `.json`, or structured technical reports). + +--- + +## 10 Showcase Tasks (10 Unique Domains & Verticals) + +| # | Vertical | Domain | Role | Task ID | +| :-: | :--- | :--- | :--- | :--- | +| **1** | **Logistics & Mapping** | Surveying & GIS | GIS Analyst | `task_4308eaef4d504328988c1cb5dfd7db77` | +| **2** | **Construction** | Architecture | Architect | `task_a46a6c3cebd54b82b9ad5e66d1e14e48` | +| **3** | **Engineering** | Electrical & RF Engineering | RF IC Design Engineer | `task_143a5623f26c404baaeb63ccd891e196` | +| **4** | **Engineering** | Mechanical & Control Systems | Mechanical Engineering Instructor | `task_dd94dc222db74864a13fcb7c6c2844a2` | +| **5** | **Science** | Applied Sciences (Biochemistry) | Biochemist | `task_47d262f6d58c4e5293a22623f0d711e5` | +| **6** | **Business** | Workforce Planning & HR Analytics | Workforce Planning Analyst | `task_fea07f327cfd4f4c91af0bf78da197d4` | +| **7** | **Finance** | M&A / Management Consulting | Investment Analyst | `task_c9ab91021dc14eab926dfea0a208108a` | +| **8** | **Education** | History & Cartography | Historian | `task_9e3bdd2bdccd4164bcc792c914f59925` | +| **9** | **Law & Government** | Public Policy | Policy Analyst | `task_5a0212833c224c85b79960604679eb84` | +| **10** | **Software & Data** | Data Science | Data Scientist | `task_e49e96e764424db08531c39fb685ed70` | + +--- + +## Repository Structure + +```text +tasks/ +└── task_/ + ├── metadata.json # Task ID, prompt, domain, role, input file list, task goal, and economic rationale + ├── rubrics.json # Fine-grained grading criteria and criterion weights + └── input/ # All source input files provided to the agent in the workspace +``` + +Each `metadata.json` contains: +- `TaskID`: Unique task identifier (`task_<32-hex>`) +- `Prompt`: Full verbatim instruction prompt given to the agent +- `All Task Files`: Relative path to the task input workspace (`tasks/task_/input/`) +- `Rubric Criteria`: Relative path to the task rubric file (`tasks/task_/rubrics.json`) +- `Input_files`: Comma-separated list of input filenames inside `input/` +- `Vertical`: Top-level industry vertical +- `Domain`: Professional domain +- `Role`: Target professional role +- `Task Goal`: Summary of the deliverable goal +- `Economic Rationale`: Real-world professional time and value context + +--- + +## License + +Licensed under the [Apache License 2.0](https://www.apache.org/licenses/LICENSE-2.0). diff --git a/tasks/task_143a5623f26c404baaeb63ccd891e196/input/block_diagram.png b/tasks/task_143a5623f26c404baaeb63ccd891e196/input/block_diagram.png new file mode 100644 index 0000000000000000000000000000000000000000..7f20b3ae8833ba096c45b4ad04258f0d2eb1d83f --- /dev/null +++ b/tasks/task_143a5623f26c404baaeb63ccd891e196/input/block_diagram.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6a953fa08833fc4bb045fcf6036975c86e069de42275e7991b0285053fb354f3 +size 3809490 diff --git a/tasks/task_143a5623f26c404baaeb63ccd891e196/input/signoff_performance_limits.png b/tasks/task_143a5623f26c404baaeb63ccd891e196/input/signoff_performance_limits.png new file mode 100644 index 0000000000000000000000000000000000000000..ee23090e3de5db6f00ad38a6ad622183659bcf35 --- /dev/null +++ b/tasks/task_143a5623f26c404baaeb63ccd891e196/input/signoff_performance_limits.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7ad552d0bbf62a7c80500186da568189d75a814240e7bf4a57281b7dcb7a1ced +size 194882 diff --git a/tasks/task_143a5623f26c404baaeb63ccd891e196/input/validation_spectrum.jpg b/tasks/task_143a5623f26c404baaeb63ccd891e196/input/validation_spectrum.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0595018eb607d82eb5417e8640969db47b1286f1 --- /dev/null +++ b/tasks/task_143a5623f26c404baaeb63ccd891e196/input/validation_spectrum.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e4622dc3db86faa86a9a4a5d1861dfb9e6306013bc43f4e307b39309d7fe70d9 +size 1291770 diff --git a/tasks/task_143a5623f26c404baaeb63ccd891e196/metadata.json b/tasks/task_143a5623f26c404baaeb63ccd891e196/metadata.json new file mode 100644 index 0000000000000000000000000000000000000000..b639263e977b29d48569235435621e24ddf7d4fc --- /dev/null +++ b/tasks/task_143a5623f26c404baaeb63ccd891e196/metadata.json @@ -0,0 +1,12 @@ +{ + "TaskID": "task_143a5623f26c404baaeb63ccd891e196", + "Vertical": "Engineering", + "Domain": "Electrical & Electronics", + "Role": "RF engineer", + "Task Goal": "Assess tape-out readiness for an RF digital-to-analog converter from its spectral and performance data.", + "Prompt": "Write a tape-out readiness analysis and recommendation for the radio-frequency digital-to-analog converter (RF-DAC) as your response text, not as an attached file. Use the attached architecture block diagram, input and output spectrum plots, and sign-off performance limits chart. In this report, in-band means 0 Hz to 16 GHz, and every reported quantity takes one committed value.\n\nStructure the report as follows:\n\nSection 0: Architecture: Name each external input signal and each external output signal of the converter, and state the function of each.\n\nSection 1: Spectral Analysis: List the frequency and level of each output-spectrum tone needed to calculate the tape-out gating specifications. Classify each marked output-spectrum tone by architectural origin as fundamental, harmonic distortion (state the order), time-interleaving spur, DAC Nyquist image, clock feedthrough, or no architectural origin, and give the percentage of marked output-spectrum tones that have an architectural origin. State the frequency of the worst-case DAC Nyquist image, and state which marked tone is the worst-case time-interleaving spur together with its level relative to the fundamental in dBc and how many dB it lies above the other time-interleaving spur. Give the total harmonic distortion (THD) of the marked harmonic-distortion tones, as their power sum relative to the fundamental in dBc. Finally, state the two most dominant mechanisms attenuating the in-band noise floor of the output spectrum.\n\nSection 2: Calculations: Detail the formulas and arithmetic for each tape-out gating specification, and only those specifications.\n\nSection 3: Results: Provide a PASS / FAIL table with exactly one row per tape-out gating specification, each row containing the specification name, measured value, margin, and PASS / FAIL, followed by the percentage of tape-out gating specifications that passed and the passing gating specifications listed in order of decreasing margin.\n\nSection 4: Conclusion: Give a tape-out recommendation of APPROVED or REJECTED that identifies each violation and the amount by which it exceeds its limit.\n\nFormat all tone frequencies, levels, percentages, and dB and dBc values in Section 1, all calculated results in Section 2, and all Section 3 values to two decimal places. Write the document title and all section titles in uppercase. Separate major sections with exactly two blank lines. Number the sections, use hyphen bullets for all other lists, and indent sub-bullets by exactly two spaces per level. Do not use asterisks anywhere in the response. Render the Section 3 table in monospaced text so that cells on different lines line up vertically.", + "Input_files": "block_diagram.png, signoff_performance_limits.png, validation_spectrum.jpg", + "All Task Files": "tasks/task_143a5623f26c404baaeb63ccd891e196/input/", + "Rubric Criteria": "tasks/task_143a5623f26c404baaeb63ccd891e196/rubrics.json", + "Economic Rationale": "A typical designer spends a large amount of time sifting through large datasets to ensure the performance results meet requirements across several design corners, easily missing a corner case. One specification violation could cause a chip re-spin which can cost several hundreds of thousands of dollars or more. This highlights the economic value added from the implementation of this task." +} diff --git a/tasks/task_143a5623f26c404baaeb63ccd891e196/rubrics.json b/tasks/task_143a5623f26c404baaeb63ccd891e196/rubrics.json new file mode 100644 index 0000000000000000000000000000000000000000..fe0052b137d5739093300d80d5db6be3059703dc --- /dev/null +++ b/tasks/task_143a5623f26c404baaeb63ccd891e196/rubrics.json @@ -0,0 +1,434 @@ +{ + "criterion 1": { + "description": "Structures the response into five numbered sections in this order: Section 0 Architecture, Section 1 Spectral Analysis, Section 2 Calculations, Section 3 Results, Section 4 Conclusion.", + "justification": "The prompt lists Section 0 to Section 4 with these titles and asks to 'Number the sections'.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "All output (modified files and final message in console)", + "dependencies": [] + }, + "criterion 2": { + "description": "Writes the document title and all five section titles entirely in uppercase letters.", + "justification": "The prompt states 'Write the document title and all section titles in uppercase.'", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "All output (modified files and final message in console)", + "dependencies": [] + }, + "criterion 3": { + "description": "Separates every pair of adjacent major sections with exactly two blank lines.", + "justification": "The prompt states 'Separate major sections with exactly two blank lines.'", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "All output (modified files and final message in console)", + "dependencies": [] + }, + "criterion 4": { + "description": "Uses a hyphen as the bullet marker on every non-section list item.", + "justification": "The prompt states 'use hyphen bullets for all other lists'. A list item with no marker or another marker does not meet this.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "All output (modified files and final message in console)", + "dependencies": [] + }, + "criterion 5": { + "description": "Indents each sub-bullet level by exactly two spaces relative to its parent bullet.", + "justification": "The prompt states 'indent sub-bullets by exactly two spaces per level'.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "All output (modified files and final message in console)", + "dependencies": [] + }, + "criterion 6": { + "description": "Contains zero asterisk characters in the response.", + "justification": "The prompt states 'Do not use asterisks anywhere in the response.'", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "All output (modified files and final message in console)", + "dependencies": [] + }, + "criterion 7": { + "description": "Renders the Section 3 table in monospaced text with every column boundary aligned vertically across all rows.", + "justification": "The prompt states 'Render the Section 3 table in monospaced text so that cells on different lines line up vertically.'", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "All output (modified files and final message in console)", + "dependencies": [] + }, + "criterion 8": { + "description": "States every Section 1 tone frequency, level, percentage, and dB or dBc value, every Section 2 calculated result, and every Section 3 value to two decimal places.", + "justification": "The prompt states 'Format all tone frequencies, levels, percentages, and dB and dBc values in Section 1, all calculated results in Section 2, and all Section 3 values to two decimal places.' A Section 1 frequency written as 3.969 GHz does not meet this. Input constants quoted inside formulas (for example a 52 dB limit or a 16 GHz clock) are not calculated results.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "All output (modified files and final message in console)", + "dependencies": [] + }, + "criterion 9": { + "description": "States, in Section 0, exactly three external inputs: Test_Signal, DAC_en, and ext_clk.", + "justification": "block_diagram.png shows three signal lines entering the converter from outside the block boundaries: Test_Signal (Baseband Data Generation Interface), DAC_en (Clock Generation), and ext_clk (External Clock Input). All other nets are internal.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "All output (modified files and final message in console)", + "dependencies": [] + }, + "criterion 10": { + "description": "States, in Section 0, that DAC_en is the external enable signal controlling the RF-DAC clock-generation circuitry and enabling the required interleaved clock phases.", + "justification": "The architecture diagram shows DAC_en entering the Clock Generation block and controlling the clock-generation enable circuitry. The en_p0/en_p90 sequence establishes the internal phase ordering, but describing that exact sequence is not necessary to explain the external input's function.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "All output (modified files and final message in console)", + "dependencies": [] + }, + "criterion 11": { + "description": "States, in Section 0, that Test_Signal provides an analog input stimulus to the Baseband Data Generation Interface, where it is digitized into phase-interleaved digital data streams used by the RF-DAC.", + "justification": "The architecture diagram shows Test_Signal entering the Baseband Data Generation Interface, which digitizes the signal using quadrature ADCs. A response explaining this conversion function meets the criterion without needing to enumerate all four ADC phases or the individual data-bus names.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "All output (modified files and final message in console)", + "dependencies": [] + }, + "criterion 12": { + "description": "States, in Section 0, that ext_clk provides the external clock source for the RF-DAC.", + "justification": "block_diagram.png: ext_clk enters the External Clock Input (16 GHz) block, is converted to clkp/clkn through the 1:1 transformer and buffers, and clocks the Clock Generation, Interleaver, and RF-DAC Core.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "All output (modified files and final message in console)", + "dependencies": [] + }, + "criterion 13": { + "description": "States, in Section 0, that RF_out is the external output that delivers the converted analog RF signal from the Output Match to the external load.", + "justification": "block_diagram.png: the only line leaving the converter is RF_out from the Output Match block, which combines cout_p and cout_n through a 1:1 transformer and shunt capacitor into the 50 Ohm load.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "All output (modified files and final message in console)", + "dependencies": [] + }, + "criterion 14": { + "description": "Lists, in Section 1, the fundamental tone near 12.03 GHz with a level of -15.82 dB as a tone needed for the gating calculations (acceptable frequency 11.83 to 12.23 GHz; acceptable level -17.82 to -13.82, with the unit written as dB or dBVpk).", + "justification": "validation_spectrum.jpg Output Spectrum: the tallest marked peak sits at about 12 GHz and about -16 dB (data value -15.82). Levels are read from the validation_spectrum.jpg Output Spectrum y-axis (20 dB gridlines, about 1.95 px per dB), tolerance +/-2 dB; frequencies from the x-axis (5 GHz gridlines, about 33 px per GHz), tolerance +/-0.20 GHz. It is the reference for SFDR, IRR and CLK_FT. In signoff_performance_limits.png, following each ribbon from its Definition node to the Gating column gives SFDR, IRR and CLK_FT as gating and Pout, SINAD, ENOB, HD2 and HD3 as non-gating.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "All output (modified files and final message in console)", + "dependencies": [] + }, + "criterion 15": { + "description": "Lists, in Section 1, the tone near 10.53 GHz with a level of -74.97 dB as the worst in-band spur used for SFDR (acceptable frequency 10.33 to 10.73 GHz; acceptable level -76.97 to -72.97, with the unit written as dB or dBVpk).", + "justification": "validation_spectrum.jpg Output Spectrum: within 0 to 16 GHz (in-band per the prompt) the tallest marked non-fundamental peak is near 10.5 GHz at about -75 dB (data value -74.97); the other in-band markers near 4 GHz (about -85) and 16 GHz (about -83) are lower. Levels are read from the validation_spectrum.jpg Output Spectrum y-axis (20 dB gridlines, about 1.95 px per dB), tolerance +/-2 dB; frequencies from the x-axis (5 GHz gridlines, about 33 px per GHz), tolerance +/-0.20 GHz. In signoff_performance_limits.png, following each ribbon from its Definition node to the Gating column gives SFDR, IRR and CLK_FT as gating and Pout, SINAD, ENOB, HD2 and HD3 as non-gating.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "All output (modified files and final message in console)", + "dependencies": [] + }, + "criterion 16": { + "description": "Lists, in Section 1, the DAC Nyquist image at 19.97 GHz with a level of -100.80 dB as the tone used for IRR (acceptable frequency 19.77 to 20.17 GHz; acceptable level -105.80 to -95.80, with the unit written as dB or dBVpk).", + "justification": "block_diagram.png (RF-DAC Core) shows the two sub-DACs latched on opposite phases clkp and clkn of the 16 GHz clock, so fs = 32.00 GHz and each sub-DAC runs at 16.00 GHz. The only DAC Nyquist image in the span is fs - f_fund = 32.00 - 12.03 = 19.97 GHz. It carries no marker and sits inside the noise floor, so its level is read from the trace at that frequency (data value -100.80); a +/-5 dB tolerance covers the noise-floor read. In signoff_performance_limits.png, following each ribbon from its Definition node to the Gating column gives SFDR, IRR and CLK_FT as gating and Pout, SINAD, ENOB, HD2 and HD3 as non-gating.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "All output (modified files and final message in console)", + "dependencies": [] + }, + "criterion 17": { + "description": "Lists, in Section 1, the tone near 16.00 GHz with a plotted absolute level of -83.13 dB as the clock tone used for CLK_FT (acceptable frequency 15.80 to 16.20 GHz; acceptable level -85.13 to -81.13 dB, with the unit written as dB or dBVpk, but not dBc).", + "justification": "The output spectrum shows an absolute clock-tone level of -83.13 dB at 16.00 GHz. Its carrier-relative level is -67.31 dBc after subtracting the -15.82 dB fundamental. These quantities are not interchangeable. The dBc result is assessed separately under the clock-feedthrough calculation.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "All output (modified files and final message in console)", + "dependencies": [] + }, + "criterion 18": { + "description": "Classifies, in Section 1, the marked tone near 3.97 GHz as a time-interleaving spur (acceptable frequency 3.77 to 4.17 GHz).", + "justification": "block_diagram.png (RF-DAC Core) shows the two sub-DACs latched on opposite phases clkp and clkn of the 16 GHz clock, so fs = 32.00 GHz and each sub-DAC runs at 16.00 GHz. fs/2 - f_fund = 16.00 - 12.03 = 3.97 GHz. The marker dot sits at about 3.97 GHz, not at the HD5 alias (3.84 GHz) or the HD7 interleave product (4.22 GHz), each about 4 px away. Frequencies are read from the validation_spectrum.jpg x-axis (about 33 px per GHz).", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "All output (modified files and final message in console)", + "dependencies": [] + }, + "criterion 19": { + "description": "Classifies, in Section 1, the marked tone near 16.00 GHz as clock feedthrough (acceptable frequency 15.80 to 16.20 GHz).", + "justification": "The marker sits at the 16 GHz external clock frequency labelled in block_diagram.png. Frequencies are read from the validation_spectrum.jpg x-axis (about 33 px per GHz).", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "All output (modified files and final message in console)", + "dependencies": [] + }, + "criterion 20": { + "description": "Classifies, in Section 1, the marked tone near 20.22 GHz as 7th-order harmonic distortion (HD7) (acceptable frequency 20.02 to 20.42 GHz).", + "justification": "block_diagram.png (RF-DAC Core) shows the two sub-DACs latched on opposite phases clkp and clkn of the 16 GHz clock, so fs = 32.00 GHz and each sub-DAC runs at 16.00 GHz. 7 x 12.03 = 84.21 GHz images to 84.21 - 64.00 = 20.21 GHz; the marker dot sits at about 20.2 GHz, not at the HD3 interleave product (20.09 GHz, about 4 px lower). Frequencies are read from the validation_spectrum.jpg x-axis (about 33 px per GHz).", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "All output (modified files and final message in console)", + "dependencies": [] + }, + "criterion 21": { + "description": "Classifies, in Section 1, the marked tone near 24.06 GHz as 2nd-order harmonic distortion (HD2) (acceptable frequency 23.86 to 24.26 GHz).", + "justification": "2 x 12.03 = 24.06 GHz. Frequencies are read from the validation_spectrum.jpg x-axis (about 33 px per GHz).", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "All output (modified files and final message in console)", + "dependencies": [] + }, + "criterion 22": { + "description": "Classifies, in Section 1, the lower-frequency marker of the pair near 28 GHz (about 27.91 GHz) as 3rd-order harmonic distortion (HD3) (acceptable frequency 27.71 to 28.03 GHz, as the lower of the two markers).", + "justification": "block_diagram.png (RF-DAC Core) shows the two sub-DACs latched on opposite phases clkp and clkn of the 16 GHz clock, so fs = 32.00 GHz and each sub-DAC runs at 16.00 GHz. 3 x 12.03 = 36.09 GHz images to 64.00 - 36.09 = 27.91 GHz. The two markers near 28 GHz are 0.12 GHz apart; their left-to-right order identifies the lower one as HD3. Frequencies are read from the validation_spectrum.jpg x-axis (about 33 px per GHz).", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "All output (modified files and final message in console)", + "dependencies": [] + }, + "criterion 23": { + "description": "Classifies, in Section 1, the higher-frequency marker of the pair near 28 GHz (about 28.03 GHz) as a time-interleaving spur (acceptable frequency 27.91 to 28.23 GHz, as the higher of the two markers).", + "justification": "block_diagram.png (RF-DAC Core) shows the two sub-DACs latched on opposite phases clkp and clkn of the 16 GHz clock, so fs = 32.00 GHz and each sub-DAC runs at 16.00 GHz. fs/2 + f_fund = 16.00 + 12.03 = 28.03 GHz. With matched sub-DACs the fs/2 -/+ f_fund images of the two 16 GS/s sub-DACs cancel; the residual tones there are mismatch (time-interleaving) spurs, and the only DAC Nyquist image in the span is 19.97 GHz. Frequencies are read from the validation_spectrum.jpg x-axis (about 33 px per GHz).", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "All output (modified files and final message in console)", + "dependencies": [] + }, + "criterion 24": { + "description": "Classifies, in Section 1, the marked tone near 32.00 GHz as clock feedthrough (acceptable frequency 31.80 to 32.00 GHz).", + "justification": "2 x 16.00 GHz = 32.00 GHz, the second harmonic of the clock; the marker sits at the right edge of the span. Frequencies are read from the validation_spectrum.jpg x-axis (about 33 px per GHz).", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "All output (modified files and final message in console)", + "dependencies": [] + }, + "criterion 25": { + "description": "Classifies, in Section 1, the marked tone near 10.53 GHz as having no architectural origin (acceptable frequency 10.33 to 10.73 GHz).", + "justification": "block_diagram.png (RF-DAC Core) shows the two sub-DACs latched on opposite phases clkp and clkn of the 16 GHz clock, so fs = 32.00 GHz and each sub-DAC runs at 16.00 GHz. 10.53 GHz matches no |n x f_fund - k x fs| for n = 1 to 25, no fs/2-offset interleave product, no DAC image and no clock product; the nearest candidates (11.28, 11.53, 11.78 GHz) are more than 0.7 GHz away, so the axis read cannot be confused with them. Every other marked tone has an origin.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "All output (modified files and final message in console)", + "dependencies": [] + }, + "criterion 26": { + "description": "States, in Section 1, the percentage of marked output-spectrum tones with an architectural origin as 88.89 percent (acceptable value 88.89 percent).", + "justification": "validation_spectrum.jpg Output Spectrum carries 9 marker dots (about 3.97, 10.53, 12.03, 16.00, 20.22, 24.06, 27.91, 28.03, 32.00 GHz); the 19.97 GHz image has no marker. Only 10.53 GHz lacks an origin: 8 / 9 = 88.89 percent.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 4, + "grading_target": "All output (modified files and final message in console)", + "dependencies": [] + }, + "criterion 27": { + "description": "States, in Section 1, that the worst-case DAC Nyquist image is at 19.97 GHz (acceptable frequency 19.77 to 20.17 GHz).", + "justification": "block_diagram.png (RF-DAC Core) shows the two sub-DACs latched on opposite phases clkp and clkn of the 16 GHz clock, so fs = 32.00 GHz and each sub-DAC runs at 16.00 GHz. DAC Nyquist images fall at k x fs -/+ f_fund; inside 0 to 32 GHz the only one is 32.00 - 12.03 = 19.97 GHz (it carries no marker). The marked tones at about 3.97 and 28.03 GHz sit at fs/2 -/+ f_fund and are time-interleaving spurs, because the sub-DAC images there cancel when the sub-DACs match.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 5, + "grading_target": "All output (modified files and final message in console)", + "dependencies": [] + }, + "criterion 28": { + "description": "States, in Section 1, that the worst-case time-interleaving spur is the marked tone near 28.03 GHz, the higher-frequency marker of the pair near 28 GHz (acceptable frequency 27.91 to 28.23 GHz).", + "justification": "block_diagram.png (RF-DAC Core) shows the two sub-DACs latched on opposite phases clkp and clkn of the 16 GHz clock, so fs = 32.00 GHz and each sub-DAC runs at 16.00 GHz. The two interleaving spurs are at fs/2 -/+ f_fund: about 3.97 GHz (about -85 dB) and about 28.03 GHz (about -59 dB) in validation_spectrum.jpg. The 28.03 GHz peak is visibly about 26 dB taller.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 5, + "grading_target": "All output (modified files and final message in console)", + "dependencies": [] + }, + "criterion 29": { + "description": "States, in Section 1, the level of the worst-case time-interleaving spur relative to the fundamental as -42.79 dBc (acceptable range -46.79 to -38.79 dBc).", + "justification": "Plot reads: 28.03 GHz peak about -59 dB (data -58.61) and fundamental about -16 dB (data -15.82): -58.61 - (-15.82) = -42.79 dBc. Two reads at +/-2 dB each give +/-4 dB.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "All output (modified files and final message in console)", + "dependencies": [] + }, + "criterion 30": { + "description": "States, in Section 1, the RF-DAC Core's series unit-cell capacitors as a primary mechanism attenuating lower-frequency in-band noise through capacitive high-pass coupling, accepting technically equivalent descriptions of the same mechanism.", + "justification": "block_diagram.png shows series Cunit = 3.6 fF capacitors at each RF-DAC Core unit-cell output, forming a high-pass response with the load; validation_spectrum.jpg Output Spectrum shows the floor rolling off deeply toward 0 GHz. A bullet that names this together with the output-match response meets this, provided the series capacitors are identified as a filtering mechanism.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 4, + "grading_target": "All output (modified files and final message in console)", + "dependencies": [] + }, + "criterion 31": { + "description": "States, in Section 1, the frequency-selective band-pass response of the output matching network as a primary mechanism attenuating out-of-band and off-resonance noise, accepting equivalent descriptions involving the matching transformer's inductance and shunt capacitance.", + "justification": "block_diagram.png Output Match = 1:1 transformer plus shunt capacitor, a band-pass network centred near the fundamental (a description in terms of the transformer magnetizing inductance and the shunt capacitance forming an LC band-pass also meets this); validation_spectrum.jpg Output Spectrum shows the floor peaking near 12 GHz and falling away on both sides. A bullet that names this together with the series capacitors meets this, provided the output-match band-pass response is identified as a filtering mechanism. A zero-order-hold sinc response falls monotonically with frequency; the floor rising to a maximum near 12 GHz and falling on both sides identifies the band-pass match as the dominant shaping.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 4, + "grading_target": "All output (modified files and final message in console)", + "dependencies": [] + }, + "criterion 32": { + "description": "Calculates, in Section 2, a single SFDR value of 59.15 dB (acceptable range 55.15 to 63.15, with the unit written as dB or dBc) as fundamental level minus worst in-band spur level.", + "justification": "SFDR = -15.82 - (-74.97) = 59.15 dB from two plot reads (+/-2 dB each). Every value in the range passes the 52 dB minimum.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "All output (modified files and final message in console)", + "dependencies": [] + }, + "criterion 33": { + "description": "Calculates, in Section 2, a single IRR value of 84.98 dBc (acceptable range 77.98 to 91.98, with the unit written as dB or dBc) as fundamental level minus worst DAC Nyquist image level.", + "justification": "IRR = -15.82 - (-100.80) = 84.98 dBc; the fundamental read (+/-2 dB) and the noise-floor read at 19.97 GHz (+/-5 dB) give 77.98 to 91.98 dBc. Every value passes the 40 dBc minimum.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "All output (modified files and final message in console)", + "dependencies": [] + }, + "criterion 34": { + "description": "Calculates, in Section 2, a single CLK_FT value of -67.31 dBc (acceptable range -71.31 to -63.31 dBc) as clock tone level minus fundamental level.", + "justification": "CLK_FT = -83.13 - (-15.82) = -67.31 dBc from two plot reads (+/-2 dB each). The whole range lies above the -72 dBc maximum in signoff_performance_limits.png, so FAIL is fixed for any read.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "All output (modified files and final message in console)", + "dependencies": [] + }, + "criterion 35": { + "description": "Limits the Section 2 calculations to exactly the three tape-out gating specifications: SFDR, IRR, and CLK_FT.", + "justification": "The prompt asks for 'each tape-out gating specification, and only those specifications'. In signoff_performance_limits.png, following each ribbon from its Definition node to the Gating column gives SFDR, IRR and CLK_FT as gating and Pout, SINAD, ENOB, HD2 and HD3 as non-gating. A Section 2 calculation of Pout or SINAD does not meet this.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "All output (modified files and final message in console)", + "dependencies": [] + }, + "criterion 36": { + "description": "Includes, in Section 3, exactly one PASS / FAIL table with exactly three rows (SFDR, IRR, CLK_FT), each containing the specification name, measured value, margin, and PASS / FAIL.", + "justification": "The prompt asks for one row per gating specification with these four fields. In signoff_performance_limits.png, following each ribbon from its Definition node to the Gating column gives SFDR, IRR and CLK_FT as gating and Pout, SINAD, ENOB, HD2 and HD3 as non-gating.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "All output (modified files and final message in console)", + "dependencies": [] + }, + "criterion 37": { + "description": "States, in the Section 3 table, the SFDR margin as +7.15 dB (acceptable range +3.15 to +11.15, with the unit written as dB or dBc).", + "justification": "signoff_performance_limits.png: SFDR Min = 52 dB (ribbon from 'In-band spur-free range' to Min 52). Margin = 59.15 - 52.00 = +7.15 dB; the SFDR range carries through.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "All output (modified files and final message in console)", + "dependencies": [] + }, + "criterion 38": { + "description": "States, in the Section 3 table, the IRR margin as +44.98 dB (acceptable range +37.98 to +51.98, with the unit written as dB or dBc).", + "justification": "signoff_performance_limits.png: IRR Min = 40 dBc (ribbon from 'Worst DAC Nyquist image / Pout' to Min 40). Margin = 84.98 - 40.00 = +44.98 dB; the IRR range carries through.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "All output (modified files and final message in console)", + "dependencies": [] + }, + "criterion 39": { + "description": "States, in the Section 3 table, the CLK_FT margin as -4.69 dB (acceptable range -8.69 to -0.69, with the unit written as dB or dBc).", + "justification": "signoff_performance_limits.png: CLK_FT Max = -72 dBc (ribbon from 'Residual clock-tone power / Pout' to the empty Min node, then Max -72). Margin = -72.00 - (-67.31) = -4.69 dB; the CLK_FT range carries through and stays negative.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "All output (modified files and final message in console)", + "dependencies": [] + }, + "criterion 40": { + "description": "States, in Section 3, the percentage of tape-out gating specifications passed as 66.67 percent (acceptable value 66.67 percent).", + "justification": "Of the three gating specifications (SFDR, IRR, CLK_FT) only CLK_FT fails: 2 / 3 = 66.67 percent.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "All output (modified files and final message in console)", + "dependencies": [] + }, + "criterion 41": { + "description": "States, in Section 4, a tape-out recommendation of REJECTED.", + "justification": "CLK_FT is gating and fails its -72 dBc maximum for every plot read, so tape-out cannot be approved.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "All output (modified files and final message in console)", + "dependencies": [] + }, + "criterion 42": { + "description": "States, in Section 4, that clock feedthrough is the only violation.", + "justification": "Only CLK_FT (-67.31 > -72) fails; SFDR and IRR pass for every plot read. A Section 4 violations list that contains clock feedthrough and no other specification meets this; the word 'only' is not required.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "All output (modified files and final message in console)", + "dependencies": [] + }, + "criterion 43": { + "description": "States, in Section 4, that clock feedthrough exceeds its limit by 4.69 dB (acceptable range 0.69 to 8.69, with the unit written as dB or dBc).", + "justification": "-67.31 - (-72.00) = 4.69 dB; two plot reads at +/-2 dB each give 0.69 to 8.69 dB.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "All output (modified files and final message in console)", + "dependencies": [] + }, + "criterion 44": { + "description": "Provides the full report in the response text.", + "justification": "The prompt states 'as your response text, not as an attached file'.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "All output (modified files and final message in console)", + "dependencies": [] + }, + "criterion 45": { + "description": "Classifies, in Section 1, the marked tone near 12.03 GHz as the fundamental (acceptable frequency 11.83 to 12.23 GHz).", + "justification": "validation_spectrum.jpg Output Spectrum: the tallest marked peak, at about 12 GHz on the x-axis (about 33 px per GHz); the Input Spectrum peak sits at the same frequency.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "All output (modified files and final message in console)", + "dependencies": [] + }, + "criterion 46": { + "description": "States, in Section 1, the total harmonic distortion of the marked harmonic tones as -50.85 dBc (acceptable range -54.85 to -46.85 dBc).", + "justification": "HD2 about 24.06 GHz (-75.31), HD3 about 27.91 GHz (-67.54) and HD7 about 20.22 GHz (-80.11), against the fundamental at -15.82: -59.49, -51.72 and -64.29 dBc. THD = 10 x log10(10^(-5.949) + 10^(-5.172) + 10^(-6.429)) = -50.85 dBc. The harmonic reads and the fundamental read each carry +/-2 dB, so the range is +/-4 dB.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "All output (modified files and final message in console)", + "dependencies": [] + }, + "criterion 47": { + "description": "Lists, in Section 3, the passing gating specifications in order of decreasing margin as IRR, then SFDR.", + "justification": "Margins: IRR +44.98 dB (range +37.98 to +51.98) and SFDR +7.15 dB (range +3.15 to +11.15); the ranges do not overlap, so the order is fixed. CLK_FT fails and is not listed.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "All output (modified files and final message in console)", + "dependencies": [] + }, + "criterion 48": { + "description": "States, in Section 1, that the worst-case time-interleaving spur lies 26.50 dB above the other time-interleaving spur (acceptable range 22.50 to 30.50 dB).", + "justification": "Plot reads: about -59 dB at 28.03 GHz and about -85 dB at 3.97 GHz (data -58.61 and -85.11): -58.61 - (-85.11) = 26.50 dB; two reads at +/-2 dB each.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "All output (modified files and final message in console)", + "dependencies": [] + } +} \ No newline at end of file diff --git a/tasks/task_4308eaef4d504328988c1cb5dfd7db77/input/Boundary.geojson b/tasks/task_4308eaef4d504328988c1cb5dfd7db77/input/Boundary.geojson new file mode 100644 index 0000000000000000000000000000000000000000..f4ea5a86fc394318b6f8d3723cb208bbdee15547 --- /dev/null +++ b/tasks/task_4308eaef4d504328988c1cb5dfd7db77/input/Boundary.geojson @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e5891aa93c8114aacb326db3ee29cdb695c4f08e016b276c96b19d9a395b4eca +size 259954593 diff --git a/tasks/task_4308eaef4d504328988c1cb5dfd7db77/input/Buildings.geojson b/tasks/task_4308eaef4d504328988c1cb5dfd7db77/input/Buildings.geojson new file mode 100644 index 0000000000000000000000000000000000000000..193b0c04652651e424a118e4bf65aab2899d7b6f --- /dev/null +++ b/tasks/task_4308eaef4d504328988c1cb5dfd7db77/input/Buildings.geojson @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f53f013cc9434389bab7d0bde3dbe8c001edce6a33fa223a4f11806e17fc398c +size 129588526 diff --git a/tasks/task_4308eaef4d504328988c1cb5dfd7db77/input/Conservationareas.geojson b/tasks/task_4308eaef4d504328988c1cb5dfd7db77/input/Conservationareas.geojson new file mode 100644 index 0000000000000000000000000000000000000000..e269e009836eba4128763260dd023d6cc7291981 --- /dev/null +++ b/tasks/task_4308eaef4d504328988c1cb5dfd7db77/input/Conservationareas.geojson @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d8a58d58aeb0f79e2785e716ca782b704f612d3edb20570864593b46395ac65d +size 156633555 diff --git a/tasks/task_4308eaef4d504328988c1cb5dfd7db77/input/LIDAR_DSM_1m.tif b/tasks/task_4308eaef4d504328988c1cb5dfd7db77/input/LIDAR_DSM_1m.tif new file mode 100644 index 0000000000000000000000000000000000000000..679f28db9da2082c8a05a29be0cc68638fe5d65c --- /dev/null +++ b/tasks/task_4308eaef4d504328988c1cb5dfd7db77/input/LIDAR_DSM_1m.tif @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a6c4963d6b3c8373aa499d14da83ef8beba921f2b2d3d394d8d352eecaec0534 +size 113398630 diff --git a/tasks/task_4308eaef4d504328988c1cb5dfd7db77/input/Nationalheritage.geojson b/tasks/task_4308eaef4d504328988c1cb5dfd7db77/input/Nationalheritage.geojson new file mode 100644 index 0000000000000000000000000000000000000000..16ab032505c384a0f224aa54d6d351ad3f23bfbd --- /dev/null +++ b/tasks/task_4308eaef4d504328988c1cb5dfd7db77/input/Nationalheritage.geojson @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:58b98ad907942f63c65eab351a30e6ef26b59af2a8c814d60e4c4f7acc3db6f6 +size 260990629 diff --git a/tasks/task_4308eaef4d504328988c1cb5dfd7db77/input/Solar_Radiation_2014_2024.tif b/tasks/task_4308eaef4d504328988c1cb5dfd7db77/input/Solar_Radiation_2014_2024.tif new file mode 100644 index 0000000000000000000000000000000000000000..2bc1ba49c71065118369df4bc0c8f1339aef77a1 --- /dev/null +++ b/tasks/task_4308eaef4d504328988c1cb5dfd7db77/input/Solar_Radiation_2014_2024.tif @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a9a17a528eb087fb907eb3025169e75b4d2a52b9ab72a8c8de986b4d387b2b7b +size 25495254 diff --git a/tasks/task_4308eaef4d504328988c1cb5dfd7db77/input/Study_Area.jpeg b/tasks/task_4308eaef4d504328988c1cb5dfd7db77/input/Study_Area.jpeg new file mode 100644 index 0000000000000000000000000000000000000000..ea7862e8b64277fb7e1ea0e5b6e8c53f10b9b090 --- /dev/null +++ b/tasks/task_4308eaef4d504328988c1cb5dfd7db77/input/Study_Area.jpeg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1ee3b3c472194d7632ee1a925967b5a3884c3c2d3ac3a7c1da0c7c2bec79df40 +size 360757 diff --git a/tasks/task_4308eaef4d504328988c1cb5dfd7db77/input/asset-register-2025.xlsx b/tasks/task_4308eaef4d504328988c1cb5dfd7db77/input/asset-register-2025.xlsx new file mode 100644 index 0000000000000000000000000000000000000000..4f60d2bf573b966c78dd7828cb79258345efdb07 --- /dev/null +++ b/tasks/task_4308eaef4d504328988c1cb5dfd7db77/input/asset-register-2025.xlsx @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6b410fdf098ce1f3d098abf4ba7dd113a17923cf49840a7e0e087e807650b343 +size 372448 diff --git a/tasks/task_4308eaef4d504328988c1cb5dfd7db77/input/rules_solar.txt b/tasks/task_4308eaef4d504328988c1cb5dfd7db77/input/rules_solar.txt new file mode 100644 index 0000000000000000000000000000000000000000..f2349e4f0d4a81208f1b33cc47f8399ca94c672c --- /dev/null +++ b/tasks/task_4308eaef4d504328988c1cb5dfd7db77/input/rules_solar.txt @@ -0,0 +1,114 @@ +1. Supplied data + +Study_Area.jpeg +- Reference image used only to identify the highlighted local-authority study area. + +Boundary.geojson +- Administrative boundary data. +- Select the polygon whose outline matches the highlighted area in Study_Area.jpeg. That polygon is the authoritative study-area boundary. + +Buildings.geojson +- Building-footprint data. +- Use footprints that intersect the study-area boundary and clip them to that boundary. + +asset-register-2025.xlsx +- Council asset register. +- Use records where Holding Type = Land/Buildings. +- Use Property Name, UPRN, Longitude and Latitude. +- Treat Longitude and Latitude as WGS84 (EPSG:4326). + +LIDAR_DSM_1m.tif +- 1 m Digital Surface Model used to derive roof slope and aspect. + +Solar_Radiation_2014_2024.tif +- Average annual solar irradiation in kWh/m²/year. + +Nationalheritage.geojson +- Listed-building constraint data. + +Conservationareas.geojson +- Conservation-area constraint data. + + +2. Common study-area treatment + +- Use British National Grid (EPSG:27700) for all spatial analysis. +- Restrict all reported spatial results to the selected study-area boundary. +- Task 1 identifies the study area and building stock. +- Tasks 2, 3 and 4 are independent analyses. An error or exclusion in one must not alter the input population used by the other two. +- Task 5 is the only task that combines the outputs of Tasks 2, 3 and 4. + + +3. Task 2 – Council-owned building inventory + +- Use only asset records where Holding Type = Land/Buildings. +- Match each asset to the building footprint containing its coordinate. If none contains it, match it to the nearest footprint within 25 m. +- If more than one footprint is equally valid, use the lowest OBJECTID. +- If multiple asset records match the same footprint, retain the record with the lowest UPRN for building-level analysis. +- Assets with no footprint match within 25 m are unmatched. +- Unique matched council-owned buildings are the distinct matched footprints after duplicate removal. +- Combined roof area is the clipped polygon area of those unique matched footprints. +- Do not apply heritage constraints or rooftop-suitability rules in Task 2. + + +4. Task 3 – Heritage constraints + +- Assess all building footprints in the study area, independently of Task 2. +- A building intersecting Nationalheritage.geojson is classified as Listed Building. +- A building intersecting Conservationareas.geojson is classified as Conservation Area only when it is not already classified as Listed Building. +- Listed Building therefore takes precedence where both constraints overlap. +- Report the number of affected buildings and the clipped polygon roof area for each constraint category. +- Do not apply council-ownership matching or rooftop-suitability rules in Task 3. + + +5. Task 4 – Rooftop solar potential + +- Assess all building footprints in the study area, independently of Tasks 2 and 3. +- Assign a 1 m DSM cell to a building when the cell centre falls within or on its clipped footprint. Assign each cell to one building only; if a centre lies on more than one footprint, use the lowest OBJECTID. +- Derive slope and aspect from the DSM using the Horn 3×3 method, planar distances and z-factor 1. +- Cells without a complete valid 3×3 neighbourhood are NoData and are excluded. +- Flat = slope <5°. +- For slope >=5°, use: E 67.5–<112.5°, SE 112.5–<157.5°, S 157.5–<202.5°, SW 202.5–<247.5°, W 247.5–292.5°. +- All other aspects at slope >=5° are North-facing. +- A roof cell is suitable only when slope <=60° and orientation is Flat, E, SE, S, SW or W. +- North-facing cells and cells with slope >60° are unsuitable. +- For each suitable 1 m roof cell, obtain Solar_Radiation by bilinear sampling at the cell centre from Solar_Radiation_2014_2024.tif. Cells with Solar_Radiation NoData are excluded. +- Suitable_Roof_Area_m2 equals the number of suitable cells with valid solar radiation. +- Assessed_Roof_Area_m2 equals the number of valid assigned 1 m cells. +- Suitable_Roof_Percent = Suitable_Roof_Area_m2 / Assessed_Roof_Area_m2 × 100. +- A building qualifies when Suitable_Roof_Area_m2 >=20 m². +- Capacity_kWp = Suitable_Roof_Area_m2 × 0.20. +- Cell_Annual_Generation_kWh = 0.20 × Solar_Radiation × Orientation_Factor × 0.80. +- Orientation factors: Flat 0.95, E 0.85, SE 0.95, S 1.00, SW 0.95, W 0.85. +- Annual_Generation_kWh for a building is the sum of Cell_Annual_Generation_kWh across its suitable cells. +- Task 4 totals use all qualifying study-area buildings; do not remove council or heritage-constrained buildings at this stage. + + +6. Task 5 – Council solar investment priority + +- Start with the unique matched council-owned buildings from Task 2. +- Remove buildings classified as Listed Building or Conservation Area in Task 3. +- Keep only buildings that qualify under Task 4 with Suitable_Roof_Area_m2 >=20 m². +- Use each retained building's Task 4 Suitable_Roof_Area_m2, Potential_Capacity_kWp and Annual_Generation_kWh values. +- Rank by Annual_Generation_kWh descending, then Suitable_Roof_Area_m2 descending, then Property Name A–Z, then UPRN ascending. +- Use unrounded values for ranking. +- Report the top five buildings, or all eligible buildings if fewer than five qualify. +- Rank 1 is the solar-investment priority building. + + +7. Numerical reporting + +- Display areas, percentages, capacity and generation to two decimal places. +- Report counts and ranks as whole numbers. +- Use thousands separators where applicable. + + +8. Presentation + +- Create one interleaved DOCX named Council_Owned_Rooftop_Solar_Potential.docx. +- Present Tasks 1–5 in order and place each task's map immediately after its reported results. +- Do not create separate methodology, map or appendix sections. +- Maps must include a title, legend, north arrow, scale bar and CRS. +- Use Arial throughout. +- Use 20 pt for the report heading, 16 pt for task headings, 12 pt for body text and 11 pt for tables and map text. +- Use green table-header fill with white text. diff --git a/tasks/task_4308eaef4d504328988c1cb5dfd7db77/metadata.json b/tasks/task_4308eaef4d504328988c1cb5dfd7db77/metadata.json new file mode 100644 index 0000000000000000000000000000000000000000..a2d112c9075a303874c7b8cc77f23db55b9b18c4 --- /dev/null +++ b/tasks/task_4308eaef4d504328988c1cb5dfd7db77/metadata.json @@ -0,0 +1,12 @@ +{ + "TaskID": "task_4308eaef4d504328988c1cb5dfd7db77", + "Vertical": "Logistics & Mapping", + "Domain": "Surveying & GIS", + "Role": "GIS analyst", + "Task Goal": "Identify which council owned rooftops are best suited for solar panels.", + "Prompt": "Using the supplied data, prepare an interleaved Word document named Council_Owned_Rooftop_Solar_Potential.docx. Consult rules_solar.txt for input definitions, analysis rules, calculations and presentation.\n\nStart by identifying the study area shown in the supplied reference image, then use the accompanying spatial, raster and tabular data to complete the following five analyses.\n\n1.Identify the study area and report its name, area in hectares, total number of building footprints and their combined footprint area. Include a map showing the study area and building footprints.\n\n2.Independently assess the council asset register against the building footprints. Report the number of Land/Buildings asset records, number of unique matched council-owned buildings and their combined roof area. Include a map showing the asset locations and matched council-owned buildings.\n\n3.Independently assess all building footprints in the study area against the supplied heritage data. Report the number of buildings and roof area affected by listed-building and conservation-area constraints. Include a map showing the affected buildings by constraint category.\n\n4.Independently assess all building footprints in the study area using the LiDAR and solar-radiation data. Report total assessed roof area, suitable roof area, suitable percentage, number of buildings with at least 20 m² suitable roof area, total potential installed capacity and potential annual generation. Also report suitable roof area for Flat, E, SE, S, SW and W orientations. Include a map showing rooftop solar suitability.\n\n5.Combine the results of Tasks 2–4. Retain only matched council-owned buildings that are not excluded by the heritage rules and meet the rooftop-suitability threshold. Report the five buildings with the highest annual generation, including Rank, Property_Name, UPRN, Suitable_Roof_Area_m2, Potential_Capacity_kWp and Annual_Generation_kWh. Identify the Rank 1 building and show the top five buildings on a map labelled by rank.", + "Input_files": "Boundary.geojson, Buildings.geojson, Conservationareas.geojson, LIDAR_DSM_1m.tif, Nationalheritage.geojson, Solar_Radiation_2014_2024.tif, Study_Area.jpeg, asset-register-2025.xlsx, rules_solar.txt", + "All Task Files": "tasks/task_4308eaef4d504328988c1cb5dfd7db77/input/", + "Rubric Criteria": "tasks/task_4308eaef4d504328988c1cb5dfd7db77/rubrics.json", + "Economic Rationale": "The task helps prioritise rooftop solar investment across council-owned buildings using GIS rather than costly building-by-building surveys. By combining building footprints, LiDAR, solar irradiation and planning constraints, it identifies the strongest candidates for further investment, reduces spending on unsuitable roofs and supports lower long-term energy costs. Automating the workflow could reduce repeat analysis from roughly 16–30 analyst hours to around 1–3 hours, saving about 85–95% of analyst effort on future runs" +} diff --git a/tasks/task_4308eaef4d504328988c1cb5dfd7db77/rubrics.json b/tasks/task_4308eaef4d504328988c1cb5dfd7db77/rubrics.json new file mode 100644 index 0000000000000000000000000000000000000000..fe4488493ad7e0fe079459f5807322fddf6fd6b6 --- /dev/null +++ b/tasks/task_4308eaef4d504328988c1cb5dfd7db77/rubrics.json @@ -0,0 +1,560 @@ +{ + "criterion 1": { + "description": "States the final deliverable document's name as Council_Owned_Rooftop_Solar_Potential.docx.", + "justification": "", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Word Documents (.docx, .doc, .odt)", + "dependencies": [] + }, + "criterion 2": { + "description": "States the study area as City of Nottingham (B).", + "justification": "", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Word Documents (.docx, .doc, .odt)", + "dependencies": [] + }, + "criterion 3": { + "description": "Reports study-area area as 7,464.41 ha.(Acceptable range : 7,462 - 7,466)", + "justification": "", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Word Documents (.docx, .doc, .odt)", + "dependencies": [] + }, + "criterion 4": { + "description": "Reports 44,815 study-area building footprints. (Acceptable range : 44,813 - 44,817)", + "justification": "", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Word Documents (.docx, .doc, .odt)", + "dependencies": [] + }, + "criterion 5": { + "description": "Reports combined clipped building-footprint area as 11,927,707.26 m\u00b2.(Acceptable range : 11,927,697.26 - 11,927,717.26)", + "justification": "", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 4, + "grading_target": "Word Documents (.docx, .doc, .odt)", + "dependencies": [] + }, + "criterion 6": { + "description": "Includes a Map of the Study area, showing the building footprints, and the study area boundary.", + "justification": "", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Word Documents (.docx, .doc, .odt)", + "dependencies": [] + }, + "criterion 7": { + "description": "Reports 2,793 Land/Buildings asset records.(Acceptable range: 2,791 - 2,795)", + "justification": "", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 5, + "grading_target": "Word Documents (.docx, .doc, .odt)", + "dependencies": [] + }, + "criterion 8": { + "description": "Reports 1,614 unique matched council-owned buildings.(Acceptable range : 1612 - 1616)", + "justification": "", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 4, + "grading_target": "Word Documents (.docx, .doc, .odt)", + "dependencies": [] + }, + "criterion 9": { + "description": "Reports combined council-owned roof area as 1,381,241.80 m\u00b2.(Acceptable range : 1,381,231.80 - 1,381,251.80)", + "justification": "", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Word Documents (.docx, .doc, .odt)", + "dependencies": [] + }, + "criterion 10": { + "description": "Includes a map showing matched council owned buildings, Council asset points, other buildings, study area boundary.", + "justification": "", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Word Documents (.docx, .doc, .odt)", + "dependencies": [] + }, + "criterion 11": { + "description": "Reports 376 Listed Building constrained buildings.(Acceptable range 374 -378)", + "justification": "", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Word Documents (.docx, .doc, .odt)", + "dependencies": [] + }, + "criterion 12": { + "description": "Reports Listed Building roof area as 577,995.92 m\u00b2.(Acceptable range : 577,985.92 - 578,005.92)", + "justification": "", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Word Documents (.docx, .doc, .odt)", + "dependencies": [] + }, + "criterion 13": { + "description": "Reports 3,723 Conservation Area constrained buildings.(Acceptable range : 3,720 - 3,725)", + "justification": "", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Word Documents (.docx, .doc, .odt)", + "dependencies": [] + }, + "criterion 14": { + "description": "Reports Conservation Area roof area as 1,149,155.97 m\u00b2.(Acceptable range : 1,149,145.97 - 1,149,165.97)", + "justification": "", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Word Documents (.docx, .doc, .odt)", + "dependencies": [] + }, + "criterion 15": { + "description": "Includes a Constraint Map showing Listed buildings, Conservation area, other buildings, study area boundary.", + "justification": "", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Word Documents (.docx, .doc, .odt)", + "dependencies": [] + }, + "criterion 16": { + "description": "Reports assessed roof area as 11,928,440.00 m\u00b2.(Acceptable range : 11,928,430.00 - 11,928,450.00)", + "justification": "", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 5, + "grading_target": "Word Documents (.docx, .doc, .odt)", + "dependencies": [] + }, + "criterion 17": { + "description": "Reports 42,352 qualifying buildings (Acceptable range: 42,310 - 42,394).", + "justification": "", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Word Documents (.docx, .doc, .odt)", + "dependencies": [] + }, + "criterion 18": { + "description": "Reports suitable roof area for qualifying buildings as 6,731,593.00 m\u00b2.(Acceptable range : 6,724,861 - 6,738,325)", + "justification": "", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Word Documents (.docx, .doc, .odt)", + "dependencies": [] + }, + "criterion 19": { + "description": "Reports suitable roof area percentage as 56.43.(Acceptable range : 56.33 - 56.82)", + "justification": "", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Word Documents (.docx, .doc, .odt)", + "dependencies": [] + }, + "criterion 20": { + "description": "Reports potential installed capacity as 1,346,318.60 kWp.(Acceptable range : 1,344,972.60 - 1,347,664.60)", + "justification": "", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Word Documents (.docx, .doc, .odt)", + "dependencies": [] + }, + "criterion 21": { + "description": "Reports potential annual generation as 1,021,809,213.00 kWh/year.(Acceptable range : 1,020,787,404.00 - 1,022,831,022.00 )", + "justification": "", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Word Documents (.docx, .doc, .odt)", + "dependencies": [] + }, + "criterion 22": { + "description": "Reports Flat suitable roof area as 1,391,650.00 m\u00b2.(Acceptable range : 1,390,258 - 1,393,042)", + "justification": "", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Word Documents (.docx, .doc, .odt)", + "dependencies": [] + }, + "criterion 23": { + "description": "Reports E suitable roof area as 1,071,208.00 m\u00b2. (Acceptable range : 1,070,137 - 1,072,279)", + "justification": "", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Word Documents (.docx, .doc, .odt)", + "dependencies": [] + }, + "criterion 24": { + "description": "Reports SE suitable roof area as 1,030,899.00 m\u00b2. (Acceptable range : 1,029,868 - 1,031,930)", + "justification": "", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Word Documents (.docx, .doc, .odt)", + "dependencies": [] + }, + "criterion 25": { + "description": "Reports S suitable roof area as 1,107,757.00 m\u00b2.(Acceptable range : 1,106,649 - 1,108,865)", + "justification": "", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Word Documents (.docx, .doc, .odt)", + "dependencies": [] + }, + "criterion 26": { + "description": "Reports SW suitable roof area as 1,050,411.00 m\u00b2.(Acceptable range : 1,049,361 - 1,051,461)", + "justification": "", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Word Documents (.docx, .doc, .odt)", + "dependencies": [] + }, + "criterion 27": { + "description": "Reports W suitable roof area as 1,079,668.00 m\u00b2.(Acceptable range : 1,078,588 - 1,080,748)", + "justification": "", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Word Documents (.docx, .doc, .odt)", + "dependencies": [] + }, + "criterion 28": { + "description": "Includes a rooftop solar suitability map showing potential annual generation breaks.", + "justification": "", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Word Documents (.docx, .doc, .odt)", + "dependencies": [] + }, + "criterion 29": { + "description": "Reports Property Name - UPRN ( Queens Court- 200001385371) as Rank 1", + "justification": "", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Word Documents (.docx, .doc, .odt)", + "dependencies": [] + }, + "criterion 30": { + "description": "Reports Rank 1(Queens Court) suitable roof area as 16,501.00 m\u00b2.(Acceptable range : 16,499 - 16,503)", + "justification": "", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Word Documents (.docx, .doc, .odt)", + "dependencies": [] + }, + "criterion 31": { + "description": "Reports Rank 1(Queens Court) capacity as 3,300.20 kWp(Acceptable range : 3,290 - 3,310)", + "justification": "", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Word Documents (.docx, .doc, .odt)", + "dependencies": [] + }, + "criterion 32": { + "description": "Reports Rank 1(Queens Court) annual generation as 2,539,446.49 kWh/year (Acceptable range : 2,539,444- 2,539,448)", + "justification": "", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Word Documents (.docx, .doc, .odt)", + "dependencies": [] + }, + "criterion 33": { + "description": "Reports Property Name - UPRN ( Land at Crossgate Drive/Longwall Avenue and Substation- 200001378447) as Rank 2", + "justification": "", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Word Documents (.docx, .doc, .odt)", + "dependencies": [] + }, + "criterion 34": { + "description": "Reports Rank 2 ( Land at Crossgate Drive/Longwall Avenue and Substation) suitable roof area as 12,402.00 m\u00b2.(Acceptable range : 12,400 - 12,404)", + "justification": "", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Word Documents (.docx, .doc, .odt)", + "dependencies": [] + }, + "criterion 35": { + "description": "Reports Rank 2 ( Land at Crossgate Drive/Longwall Avenue and Substation) capacity as 2,480.40 kWp(Acceptable range : 2,478 - 2,482)", + "justification": "", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Word Documents (.docx, .doc, .odt)", + "dependencies": [] + }, + "criterion 36": { + "description": "Reports Rank 2 ( Land at Crossgate Drive/Longwall Avenue and Substation) annual generation as 1,929,338.30 kWh/year (Acceptable range : 1,929,336.30- 1,929,340.30)", + "justification": "", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Word Documents (.docx, .doc, .odt)", + "dependencies": [] + }, + "criterion 37": { + "description": "Reports Property Name - UPRN ( National Ice Centre and Car Park South Of 14 to 28 Hockley - 200001386180) as Rank 3", + "justification": "", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Word Documents (.docx, .doc, .odt)", + "dependencies": [] + }, + "criterion 38": { + "description": "Reports Rank 3 (National Ice Centre and Car Park South Of 14 to 28 Hockley) suitable roof area as 11,256.00 m\u00b2.(Acceptable range : 11,254.00 - 11,258.00)", + "justification": "", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Word Documents (.docx, .doc, .odt)", + "dependencies": [] + }, + "criterion 39": { + "description": "Reports Rank 3 (National Ice Centre and Car Park South Of 14 to 28 Hockley) capacity as 2,251.20 kWp.(Acceptable range : 2,249.20 - 2,253.20)", + "justification": "", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Word Documents (.docx, .doc, .odt)", + "dependencies": [] + }, + "criterion 40": { + "description": "Reports Rank 3 (National Ice Centre and Car Park South Of 14 to 28 Hockley) annual generation as 1,707,560.80 kWh/year(Acceptable range : 1,707,558.80- 1,707,562.80)", + "justification": "", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Word Documents (.docx, .doc, .odt)", + "dependencies": [] + }, + "criterion 41": { + "description": "Reports Property Name - UPRN ( Land at Hyperama - 100032287788) as Rank 4", + "justification": "", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Word Documents (.docx, .doc, .odt)", + "dependencies": [] + }, + "criterion 42": { + "description": "Reports Rank 4 ( Land at Hyperama) suitable roof area as 10,107.00 m\u00b2.(Acceptable range : 10,105.00 - 10,109.00)", + "justification": "", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Word Documents (.docx, .doc, .odt)", + "dependencies": [] + }, + "criterion 43": { + "description": "Reports Rank 4 ( Land at Hyperama) capacity as 2,021.40 kWp.(Acceptable range :2,019.40 - 2,023.40)", + "justification": "", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Word Documents (.docx, .doc, .odt)", + "dependencies": [] + }, + "criterion 44": { + "description": "Reports Rank 4 ( Land at Hyperama) annual generation as 1,482,389.78 kWh/year.(Acceptable range : 1,482,387.78 - 1,482,391.78)", + "justification": "", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Word Documents (.docx, .doc, .odt)", + "dependencies": [] + }, + "criterion 45": { + "description": "Reports Property Name - UPRN ( Land at Thane Road/Bull Close Road - 010093154164) as Rank 5", + "justification": "", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Word Documents (.docx, .doc, .odt)", + "dependencies": [] + }, + "criterion 46": { + "description": "Reports Rank 5 ( Land at Thane Road/Bull Close Road) suitable roof area as 8,733.00 m\u00b2.(Acceptable range : 8,731.00 - 8,735.00)", + "justification": "", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Word Documents (.docx, .doc, .odt)", + "dependencies": [] + }, + "criterion 47": { + "description": "Reports Rank 5 ( Land at Thane Road/Bull Close Road) capacity as 1,746.60 kWp .(Acceptable range : 1,744 - 1,748)", + "justification": "", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Word Documents (.docx, .doc, .odt)", + "dependencies": [] + }, + "criterion 48": { + "description": "Reports Rank 5 ( Land at Thane Road/Bull Close Road) annual generation as 1,361,178.52 kWh/year .(Acceptable range : 1,361,176.52 - 1,361,180.52 )", + "justification": "", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Word Documents (.docx, .doc, .odt)", + "dependencies": [] + }, + "criterion 49": { + "description": "Includes a map showing the top five eligible council buildings labelled by rank.(1-5)", + "justification": "", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Word Documents (.docx, .doc, .odt)", + "dependencies": [] + }, + "criterion 50": { + "description": "Uses Arial throughout", + "justification": "", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Word Documents (.docx, .doc, .odt)", + "dependencies": [] + }, + "criterion 51": { + "description": "Uses 20pt for Report heading", + "justification": "", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Word Documents (.docx, .doc, .odt)", + "dependencies": [] + }, + "criterion 52": { + "description": "Uses 16 pt for subheadings", + "justification": "", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Word Documents (.docx, .doc, .odt)", + "dependencies": [] + }, + "criterion 53": { + "description": "Uses 12 pt for body text", + "justification": "", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Word Documents (.docx, .doc, .odt)", + "dependencies": [] + }, + "criterion 54": { + "description": "Uses 11 pt for table and map text", + "justification": "", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Word Documents (.docx, .doc, .odt)", + "dependencies": [] + }, + "criterion 55": { + "description": "Displays Areas and percentages to two decimal place", + "justification": "", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Word Documents (.docx, .doc, .odt)", + "dependencies": [] + }, + "criterion 56": { + "description": "Reports counts and ranks as whole numbers", + "justification": "", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Word Documents (.docx, .doc, .odt)", + "dependencies": [] + }, + "criterion 57": { + "description": "Presents prompts Tasks 1\u20135 in order and place each task's map immediately after its reported results.", + "justification": "", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Word Documents (.docx, .doc, .odt)", + "dependencies": [] + }, + "criterion 58": { + "description": "Displays Capacity and annual generation to two decimal place", + "justification": "", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Word Documents (.docx, .doc, .odt)", + "dependencies": [] + }, + "criterion 59": { + "description": "Uses a green table header fill and white text", + "justification": "", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 4, + "grading_target": "Word Documents (.docx, .doc, .odt)", + "dependencies": [] + }, + "criterion 60": { + "description": "Uses thousands separators where applicable", + "justification": "", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Word Documents (.docx, .doc, .odt)", + "dependencies": [] + }, + "criterion 61": { + "description": "Includes a title and legend in each Map (map showing the top five eligible council buildings labelled by rank.(1-5),Map of the Study area, showing the building footprints, and the study area boundary, map showing matched council owned buildings, Council asset points, other buildings, study area boundary,Constraint Map showing Listed buildings, Conservation area, other buildings, study area boundary,rooftop solar suitability map showing potential annual generation breaks. )", + "justification": "", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Word Documents (.docx, .doc, .odt)", + "dependencies": [] + }, + "criterion 62": { + "description": "Includes a North arrow, scale bar and CRS in each Map (map showing the top five eligible council buildings labelled by rank.(1-5),Map of the Study area, showing the building footprints, and the study area boundary, map showing matched council owned buildings, Council asset points, other buildings, study area boundary,Constraint Map showing Listed buildings, Conservation area, other buildings, study area boundary,rooftop solar suitability map showing potential annual generation breaks. )", + "justification": "", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Word Documents (.docx, .doc, .odt)", + "dependencies": [] + } +} \ No newline at end of file diff --git a/tasks/task_47d262f6d58c4e5293a22623f0d711e5/input/Branding_Layout.pptx b/tasks/task_47d262f6d58c4e5293a22623f0d711e5/input/Branding_Layout.pptx new file mode 100644 index 0000000000000000000000000000000000000000..8315403a4ee1e0ba78da38087d2cc0a0a716f84d --- /dev/null +++ b/tasks/task_47d262f6d58c4e5293a22623f0d711e5/input/Branding_Layout.pptx @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d98edfc50c9a771396d77da055669e1eb6e967b40f46c3e898ac76798a345352 +size 52418 diff --git a/tasks/task_47d262f6d58c4e5293a22623f0d711e5/input/PPT_File.pptx b/tasks/task_47d262f6d58c4e5293a22623f0d711e5/input/PPT_File.pptx new file mode 100644 index 0000000000000000000000000000000000000000..0e3faf37d2deea7802d24af64c73fa06d0b1b742 --- /dev/null +++ b/tasks/task_47d262f6d58c4e5293a22623f0d711e5/input/PPT_File.pptx @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:eb91e49912c9a09b327772daa11fc413e3c229b68a5be39fc863ecdc5665d324 +size 5471241 diff --git a/tasks/task_47d262f6d58c4e5293a22623f0d711e5/input/Paper_1.pdf b/tasks/task_47d262f6d58c4e5293a22623f0d711e5/input/Paper_1.pdf new file mode 100644 index 0000000000000000000000000000000000000000..7f4721e639d0350a27a5ec2f1d93ee26c2ed88fb --- /dev/null +++ b/tasks/task_47d262f6d58c4e5293a22623f0d711e5/input/Paper_1.pdf @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:02951d4e3e34d1be139aecdafeb04dffb93f2bc1a8cfc53bf3569a7a0b23f3f9 +size 10577189 diff --git a/tasks/task_47d262f6d58c4e5293a22623f0d711e5/input/Paper_2.pdf b/tasks/task_47d262f6d58c4e5293a22623f0d711e5/input/Paper_2.pdf new file mode 100644 index 0000000000000000000000000000000000000000..4182733125b3c7c0efe5d3a0b1c317a9398d8644 --- /dev/null +++ b/tasks/task_47d262f6d58c4e5293a22623f0d711e5/input/Paper_2.pdf @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:759aba7941bf267788886637e2b8ca5c12a1b1cabfeb53f6199dd270b2201fa0 +size 277305 diff --git a/tasks/task_47d262f6d58c4e5293a22623f0d711e5/input/Paper_3.pdf b/tasks/task_47d262f6d58c4e5293a22623f0d711e5/input/Paper_3.pdf new file mode 100644 index 0000000000000000000000000000000000000000..b3459607d480eeb409f9e80072dc5f775f3bdf8f --- /dev/null +++ b/tasks/task_47d262f6d58c4e5293a22623f0d711e5/input/Paper_3.pdf @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c4e1d1b5804e98776e584a598a3450e450007d0561dade187057690a107e497e +size 4786755 diff --git a/tasks/task_47d262f6d58c4e5293a22623f0d711e5/input/Zinc_binding_values.xlsx b/tasks/task_47d262f6d58c4e5293a22623f0d711e5/input/Zinc_binding_values.xlsx new file mode 100644 index 0000000000000000000000000000000000000000..044f17027a591fa1f44709019aacb603b13a1636 --- /dev/null +++ b/tasks/task_47d262f6d58c4e5293a22623f0d711e5/input/Zinc_binding_values.xlsx @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e43b3f05ed7bbd94a4b35e5d8965d526da3daf46acaa900d7ddda9c09f921b40 +size 9715 diff --git a/tasks/task_47d262f6d58c4e5293a22623f0d711e5/metadata.json b/tasks/task_47d262f6d58c4e5293a22623f0d711e5/metadata.json new file mode 100644 index 0000000000000000000000000000000000000000..8a1f3d1006d597765754559195c4ff6c7eb798f3 --- /dev/null +++ b/tasks/task_47d262f6d58c4e5293a22623f0d711e5/metadata.json @@ -0,0 +1,12 @@ +{ + "TaskID": "task_47d262f6d58c4e5293a22623f0d711e5", + "Vertical": "Science", + "Domain": "Applied Sciences", + "Role": "Biochemist", + "Task Goal": "Analyze zinc-binding assay data for a mutant protein series and present the results in a PowerPoint deck.", + "Prompt": "Construct a PPTX file (titled Zinc_Binding_Assay.pptx) using the branding layout that includes -\nSlide 1: An introduction slide for the zinc-binding assay (ZBA). Heading: \"Zinc binding assay\". Provide assay workflow and APA citation for Paper 2. Draw chemical structures to show reversible absorbance shift from PAR (4-(2-pyridylazo)resorcinol) (416nm) to (PAR)2·ZN(II).\nSlide 2: Create a solid line graph plotting Zn/protein monomer versus PMB (p-hydroxymercuribenzoate) Equivalents (relative to hexameric protein) for a hexameric protein (concentration of the hexameric protein: 5 µM) for WT (wild-type), R0S, R1S, R1,2S mutants using the absorbance values provided in the zinc binding file. The absorbance values for the standard zinc graph are also provided (linear regression). Round off all values to 4 decimal places. Calculate Zn/protein monomer for all the proteins (baseline correction with respect to 0 µM PMB should be done after calculating zinc concentration and before calculating zinc concentration/ protein monomer). Heading: \"Zinc Binding Is Altered in Mutants\". The mutants indicate that the amino acid R is mutated to S.\nSlide 3: Label the individual components of the 2D classifications of protein structure with provided arrow. Also, list the orientation of the components in panels 1,2,4,5,8. Provide orientation examples, where n = #:side view of ClpPn, ClpPn views, single-capped ClpXP particle, double-capped ClpXP particle, ClpXn.\nSlide 4: Make a table of the first line of comparative studies of filamentation defects in mutants (R1S to R8S), with respect to the empty plasmid and WT (scale bars:2 µm) (for the first line of comparison we don't need exact bacterial length). The rule is to compare the population average defects in filament length with respect to WT and empty plasmid where WT has a normal filamentation morphology, estimate to the nearest whole number. Short cells (<5µm), long filamentous cells (5-10µm), and very long filamentous cells (>10µm). Heading: Comparative studies of filamentation defects. Since the defects in filamentation are significantly different and it is the first line of comparison, there is no need of exact numerical values the average estimation is enough. Italicise mutant names.\nSlide 5: Find out which of the purified protein gels (1 to 7) represents the respective mutants mentioned in the table (out of 10 options) with its expected molecular weight as a first line analysis (answer for the \"After SEC\" bands). Use the whole KDa rule. If two proteins on the list are only 2kDa apart (45kDa and 47kDa), label the higher molecular band as 47KDa). Heading: Protein identification based on the molecular weight.\nSlide 6: If the molecular weight of ClpX monomer is 45KDa and ClpP monomer is 23KDa, create a table representing protein names and their respective molecular weight for 2-D classified complexes 1-10 (calculate final weight of everything visible in the picture). Heading: Protein complexes with their respective molecular weights.", + "Input_files": "Branding_Layout.pptx, PPT_File.pptx, Paper_1.pdf, Paper_2.pdf, Paper_3.pdf, Zinc_binding_values.xlsx", + "All Task Files": "tasks/task_47d262f6d58c4e5293a22623f0d711e5/input/", + "Rubric Criteria": "tasks/task_47d262f6d58c4e5293a22623f0d711e5/rubrics.json", + "Economic Rationale": "During protein purification, metalloproteins frequently lose their cofactors due to chelating agents, dilution, or column matrices, resulting in a high yield of inactive protein. By quantifying the exact stoichiometric requirement, researchers can identify the root cause of activity loss early. This allows for the rational redesign of the purification protocol (e.g., adding specific zinc salts to lysis and running buffers). Economic benefit for that is it maximizes the yield of fully functional protein per gram of starting biomass, reducing the need to scale up cultures unnecessarily and saving labor, time, and consumables.\nIn biochemical economics, the zinc-binding assay is a force multiplier. The minimal cost and time required to perform the assay are vastly outweighed by the savings generated through optimized purification yields, prevented reagent waste, precise sample reconstitution, and robust quality control. It transforms protein production from a trial-and-error process into a predictable, efficient, and cost-effective operation." +} diff --git a/tasks/task_47d262f6d58c4e5293a22623f0d711e5/rubrics.json b/tasks/task_47d262f6d58c4e5293a22623f0d711e5/rubrics.json new file mode 100644 index 0000000000000000000000000000000000000000..38f397044469f50c5716ac92c09b72e6eb33e033 --- /dev/null +++ b/tasks/task_47d262f6d58c4e5293a22623f0d711e5/rubrics.json @@ -0,0 +1,1154 @@ +{ + "criterion 1": { + "description": "Delivers the file named \"Zinc_Binding_Assay.pptx\".", + "justification": "The prompt names the deliverable exactly: \"Zinc_Binding_Assay.pptx''. The check reads the delivered file name; any other name, extension or capitalization fails.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 2": { + "description": "Contains exactly seven slides corresponding to Slide 0 through Slide 6.", + "justification": "The branding layout includes slide 0 to 6 and the prompt enumerates Slide1 through Slide 6 and assigns distinct content to each, so the deck contains seven slides and no more.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 3": { + "description": "States the Slide 1 heading exactly as \"Zinc binding assay\".", + "justification": "The prompt specifies the slide 1 heading verbatim: 'Heading: \"Zinc binding assay\"'.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 4": { + "description": "States the Slide 2 heading exactly as \"Zinc Binding Is Altered in Mutants\".", + "justification": "The prompt specifies the slide 2 heading verbatim: 'Heading: \"Zinc Binding Is Altered in Mutants\"'.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 5": { + "description": "States the Slide 4 heading exactly as \"Comparative studies of filamentation defects\".", + "justification": "The prompt specifies the slide 4 heading verbatim: 'Heading: \"Comparative studies of filamentation defects\"'.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 6": { + "description": "States the Slide 5 heading exactly as \"Protein identification based on the molecular weight\".", + "justification": "The prompt specifies the slide 5 heading verbatim: 'Heading: \"Protein identification based on the molecular weight\"'.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 7": { + "description": "States the Slide 6 heading exactly as \"Protein complexes with their respective molecular weights\".", + "justification": "The prompt specifies the slide 6 heading verbatim: 'Heading: \"Protein complexes with their respective molecular weights\"'.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 8": { + "description": "Uses every slide heading in Calibri at 28 pt.", + "justification": "The branding layout file includes Calibri, size 28, for every slide heading.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 9": { + "description": "Labels panel 8 protein name as (ClpX\u2086+ClpP\u2081\u2084+ClpX\u2086)/Double-capped ClpXP (2ClpX6 + ClpP14) on Slide 6.", + "justification": "The prompt asks for a table listing protein names and their molecular weights for 2-D classified complexes 1-10, citing PPT_File.pptx Slide 1 and Paper_1.pdf page 3 (Figure 1\u2014figure supplement 1)", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 4, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 10": { + "description": "Uses all non-heading slide text in Calibri.", + "justification": "The branding layout file includes Calibri for all slide text. ", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 11": { + "description": "Places a page number in the bottom-right corner of every slide.", + "justification": "The branding layout file includes page numbers at the right-bottom corner.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 12": { + "description": "Labels panel 9 protein name as (ClpX\u2086+ClpP\u2081\u2084+ClpX\u2086)/Double-capped ClpXP (2ClpX6 + ClpP14) on Slide 6.", + "justification": "The prompt asks for a table listing protein names and their molecular weights for 2-D classified complexes 1-10, citing PPT_File.pptx Slide 1 and Paper_1.pdf page 3 (Figure 1\u2014figure supplement 1)", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 4, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 13": { + "description": "Presents the zinc-binding assay flowchart as left-aligned on slide 1.", + "justification": "The branding layout file requires that the flowchart be left-aligned on slide 1.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 14": { + "description": "Presents the zinc-binding assay on slide 1 as a four-step flowchart, with boxes in this order: protein purification, removal of free metal from the protein sample, PAR addition, and absorbance measurement, each in its own box and connected in sequence by arrows or connector lines (or use a semantically equivalent statement).", + "justification": "Paper 2 (page 2) (the zinc-binding assay method paper) prescribes the protocol for measuring Zinc in protein; the branding layout file includes a flowchart with 4 steps. The prompt states, \"Provide assay workflow and APA citation for Paper 2.\" Paper 2 page 2 supplies the four boxes. The Proteins section supplies protein purification. The Stoichiometry of Zinc Cations in ClpX section supplies the rest: increasing amounts of PMPS free the zinc, so box two is removal of free metal and PMPS addition. PAR is already in the cuvette at 0.1 mM before the first PMPS aliquot and remains at 0.1 mM, so box three is PAR presence rather than a later addition, and it is placed after the PMPS step. Absorbance is then read at 500 nm. The denaturation and renaturation section is a separate procedure and is not this assay step.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 4, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 15": { + "description": "Includes a flowchart step stating that the proteins are purified at 95% or greater purity, or use a semantically equivalent statement.", + "justification": "Paper 2 (page 2) states that the proteins are purified to 95% or greater purity. The branding layout file includes a flowchart to summarize the assay workflow in 4 steps, and refers to Paper 2.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 16": { + "description": "Includes a flowchart step stating that the removal of Zn+2 cations from the protein is achieved using denaturation and renaturation or using increasing amounts of PMPS, by forming covalent bonds with the sulfhydryls of the cysteine amino acids in the protein (or use a semantically equivalent statement).", + "justification": "Paper 2 zinc-binding measurement states that Zn+2 cations from the protein are removed by increasing amounts of PMPS, which forms covalent bonds with the sulfhydryls of the cysteine amino acids in the protein; this is the second stage of the assay that the branding layout file includes to be diagrammed. Cite Paper_2.pdf page 2 (\"Stoichiometry of Zinc Cations in ClpX\")", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 17": { + "description": "Includes a flowchart step stating that 0.1 mM PAR 4-(2-pyridylazo)resorcinol is added to the cuvette to detect free zinc in the solution (or use a semantically equivalent statement).", + "justification": "Paper 2 (page 2) states that 0.1 mM PAR 4-(2-pyridylazo)resorcinol is present in the cuvette to detect free zinc in the solution; this is the third stage of the assay that the branding layout file includes to be diagrammed.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 18": { + "description": "Includes an APA-style in-text citation of paper 2 on slide 1 in the form (Banecki et al., 2001) or similar equivalents (Banecki et al. (2001) or a full APA reference citation).", + "justification": "The branding layout file includes: 'citation', APA parenthetical form for three or more authors is (Banecki et al., 2001). Cite Paper_2.pdf, page 1, for the author surname Banecki and publication year 2001. ", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 19": { + "description": "Displays the chemical structure of free PAR as 4-(2-pyridylazo)resorcinol with two distinct aromatic rings: a resorcinol ring (a benzene ring substituted with two hydroxyl groups at the 1 and 3 positions) and a pyridine ring (a six-membered aromatic ring containing one nitrogen atom).", + "justification": "The prompt requires the chemical structure of PAR and the wavelength change from paper 2. The resorcinol and pyridine ring structures follow from the IUPAC name 4-(2-pyridylazo)resorcinol. ", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 5, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 20": { + "description": "Displays the chemical structure of free PAR state with absorption at 416 nm.", + "justification": "The prompt mentions the absorbance of PAR at 416 nm.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 21": { + "description": "Includes a drawn chemical structure of the (PAR)2\u00b7Zn(II) complex in which a single Zn(II) ion is coordinated by two PAR (4-(2-pyridylazo)resorcinol) molecules, with all aromatic rings drawn closed. The central Zn(II) ion is connected to two PAR ligands.", + "justification": "The prompt requires the structural shift from PAR to (PAR)2\u00b7Zn(II) to be shown. The stoichiometry in the name (PAR)2\u00b7Zn(II) is two PAR ligands per zinc ion, each ligand chelating through its pyridine nitrogen, azo nitrogen and ortho phenolate oxygen; the aromatic rings remain intact upon complexation. The shift from PAR to (PAR)2\u00b7Zn(II) is mentioned in paper 2.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 5, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 22": { + "description": "States the absorbance wavelength at which the (PAR)2\u00b7Zn(II) complex is quantified is 500 nm.", + "justification": "Paper 2 (page 2) quantifies released zinc from the absorbance of the (PAR)2\u00b7Zn(II) chromophore at 500 nm; the absorbance channel is part of explaining the assay in the slide 1 flowchart.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 23": { + "description": "Presents a Zn(II)-dependent transition (double-headed arrow) from free PAR to the (PAR)\u2082\u00b7Zn(II) complex between the two chemical structures.", + "justification": "The prompt explicitly asks to show the reversible shift from PAR to (PAR)\u2082\u00b7Zn(II) using their chemical structures.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 24": { + "description": "Presents on slide 2 a line graph drawn with solid lines.", + "justification": "The prompt requires a solid line graph containing protein series on the same Slide 2 graph.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 25": { + "description": "Labels panel 10 protein name as (ClpX\u2086+ClpP\u2081\u2084+ClpX\u2086)/Double-capped ClpXP (2ClpX6 + ClpP14).", + "justification": "The prompt asks for a table listing protein names and their molecular weights for 2-D classified complexes 1-10, citing PPT_File.pptx Slide 1 and Paper_1.pdf page 3 (Figure 1\u2014figure supplement 1)", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 4, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 26": { + "description": "Labels the x-axis title \"PMB (p-hydroxymercuribenzoate) Equivalents (relative to hexameric protein)\".", + "justification": "The prompt specifies Zn/protein monomer versus PMB (p-hydroxymercuribenzoate) Equivalents (relative to hexameric protein); the Zinc_binding_values.xlsx PMB concentrations 0\u201345 \u00b5M correspond to 0\u20139 equivalents relative to 5 \u00b5M hexamer.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 27": { + "description": "Labels the x-axis with 0 to 9, plotted points per curve (acceptable value is 0 to 9 equivalents).", + "justification": "The prompt specifies Zn/protein monomer versus PMB (p-hydroxymercuribenzoate) Equivalents (relative to hexameric protein); the Zinc_binding_values.xlsx PMB concentrations 0\u201345 \u00b5M correspond to 0\u20139 equivalents relative to 5 \u00b5M hexamer.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 28": { + "description": "Labels the y-axis title exactly \"Zn/protein monomer\".", + "justification": "The prompt explicitly specifies Zn/protein monomer as the plotted response variable.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 29": { + "description": "Presents the group legend entries as WT, R0S, R1S, and R1,2S", + "justification": "The prompt requires all four protein series to be identifiable on the final graph. The prompt also states, \"for WT (wild-type), R0S, R1S, R1,2S mutants \"", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 30": { + "description": "Draws a black rectangular border around the complete Slide 2 graph.", + "justification": "The branding layout file includes a black border around the final graph.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 31": { + "description": "Italicizes the strain names WT, R0S, R1S, and R1,2S in the Slide 2 graph labels or legend.", + "justification": "The Branding layout file requires the strain names to be italicized.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 32": { + "description": "Presents ten 2D class average panels of ClpXP, ClpX\u2086, or ClpP\u2081\u2084, as shown on \"Zinc_Binding_Assay.pptx \" Slide 3, with none omitted.", + "justification": "The prompt requires the components of the 2D classifications of protein structure shown in the \"PPT_File.pptx\" Slide 1' to be labelled. PPT File slide 1 presents ten numbered 2D classification panels (1 to 10), so the complete set of ten is carried onto slide 3 as the substrate for that labelling and no panel may be dropped.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 33": { + "description": "Uses red arrows on \"Zinc_Binding_Assay.pptx\" Slide 3 to indicate ClpX\u2086 and ClpP\u2081\u2084.", + "justification": "The branding layout file includes the red arrows. The prompt states ' Label the individual components of the 2D classifications of protein structure with provided arrow.'", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 34": { + "description": "Labels Zinc_Binding_Assay.pptx, Slide 3, panel 1 as Top view/axial view of a single ClpP\u2081\u2084 particle.", + "justification": "Paper 1 and Paper 3 provide the ClpP\u2081\u2084 structural context. The prompt asks to list the orientation of the components in Panel 1. Cite PPT_File.pptx Slide 1 and Paper_1.pdf page 3 (Figure 1\u2014figure supplement 1). ", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 4, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 35": { + "description": "Labels Zinc_Binding_Assay.pptx, Slide 3, panel 2 as a Top view/axial view of two ClpP\u2081\u2084 particles.", + "justification": "Paper 1 and Paper 3 provide the top view of ClpP\u2081\u2084 structural context. The prompt asks to list the orientation of the components in panel 2. Cite PPT_File.pptx Slide 1 and Paper_1.pdf page 3 (Figure 1\u2014figure supplement 1). ", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 4, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 36": { + "description": "Labels the assembled ClpP\u2081\u2084\u2013ClpX\u2086 units visible in Zinc_Binding_Assay.pptx, Slide 3, panel 3, as two units of ClpXP or 2 x ClpXP or two single-capped ClpXP particles.", + "justification": "The associated ClpXP architecture is described in Paper 1, and Paper 3 individually. Cite PPT_File.pptx Slide 1 and Paper_1.pdf page 3 (Figure 1\u2014figure supplement 1). Panel 3 is two single-capped ClpXP units. One unit is ClpX\u2086 plus ClpP\u2081\u2084, 270 + 322 = 592 kDa, and two units are 1,184 kDa, the same size graded for this panel. A double-capped particle is a 2:1 complex and is not an accepted label.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 4, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 37": { + "description": "Labels Zinc_Binding_Assay.pptx, Slide 3, panel 4 as a double-capped ClpXP particle.", + "justification": "Paper 1 and Paper 3 provide the ClpXP structural context. Prompt asks to list orientation of the components in panel 4. Cite PPT_File.pptx Slide 1 and Paper_1.pdf page 3 (Figure 1\u2014figure supplement 1). ", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 4, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 38": { + "description": "Labels Zinc_Binding_Assay.pptx, Slide 3, panel 4 with two \"ClpX\u2086\" and one \"ClpP\u2081\u2084\".", + "justification": "Paper 1 and Paper 3 provide the two ClpX\u2086 caps flanking ClpP\u2081\u2084. Cite PPT_File.pptx Slide 1 and Paper_1.pdf page 3 (Figure 1\u2014figure supplement 1). ", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 4, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 39": { + "description": "Labels Zinc_Binding_Assay.pptx, Slide 3, panel 5 as Top view/axial view of ClpP\u2081\u2084.", + "justification": "Paper 1 and Paper 3 provide the ClpP\u2081\u2084 structural context. The prompt asks to list the orientation of the components in panel 5. Cite PPT_File.pptx Slide 1 and Paper_1.pdf page 3 (Figure 1\u2014figure supplement 1). ", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 4, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 40": { + "description": "Labels panel 6 with a size of 592KDa on Slide 6.", + "justification": "The prompt states that ClpP has a molecular weight of 23 KDa and ClpX of 45KDa. The 14 units of ClpP\u2081\u2084 have a molecular weight of 322KDa and 6 units of ClpX\u2086 have a molecular weight of 270 kDa, for a total of 592KDa. Cite PPT_File.pptx Slide 1 for the subunit stoichiometry of each panel.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 4, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 41": { + "description": "Labels panel 5 with a size of 322KDa on Slide 6.", + "justification": "The prompt mentions the molecular weight of ClpP as 23 kDa. The 14 units of ClpP\u2081\u2084 have a molecular weight of 322KDa. Cite PPT_File.pptx Slide 1 for the subunit stoichiometry of each panel.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 4, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 42": { + "description": "Labels the assembled ClpX\u2086-ClpP\u2081\u2084 units visible in Zinc_Binding_Assay.pptx, Slide 3, panel 6, as ClpXP or a single-capped ClpXP particle.", + "justification": "Panel 6 shows a single-capped ClpXP complex (one ClpX6 cap bound to one ClpP14 barrel) described in Paper 1 and Paper 3. Cite PPT_File.pptx Slide 1 and Paper_1.pdf page 3 (Figure 1\u2014figure supplement 1). ", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 4, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 43": { + "description": "Labels Zinc_Binding_Assay.pptx, Slide 3, panel 7 as two \"ClpX\u2086\" and one \"ClpP\u2081\u2084\".", + "justification": "Paper 1 and Paper 3 provide the two ClpX\u2086 caps flanking ClpP\u2081\u2084. Cite PPT_File.pptx Slide 1 and Paper_1.pdf page 3 (Figure 1\u2014figure supplement 1). ", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 4, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 44": { + "description": "Labels Zinc_Binding_Assay.pptx, Slide 3, panel 8 with two \"ClpX\u2086\" and one \"ClpP\u2081\u2084\".", + "justification": "Paper 1 and Paper 3 provide the two ClpX\u2086 caps flanking ClpP\u2081\u2084. Cite PPT_File.pptx Slide 1 and Paper_1.pdf page 3 (Figure 1\u2014figure supplement 1). ", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 4, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 45": { + "description": "Labels Zinc_Binding_Assay.pptx, Slide 3, panel 8 as a double-capped ClpXP particle.", + "justification": "Paper 1 and Paper 3 provide the ClpXP structural context. The prompt asks to list the orientation of the components in panel 8. Cite PPT_File.pptx Slide 1 and Paper_1.pdf page 3 (Figure 1\u2014figure supplement 1). ", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 4, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 46": { + "description": "Labels panel 9 with a size of 862KDa.", + "justification": "The prompt states that ClpP has a molecular weight of 23 KDa and ClpX of 45KDa. The 14 units of ClpP\u2081\u2084 have a molecular weight of 322 KDa and 6 units of ClpX\u2086 have a molecular weight of 270 kDa. Two units of ClpX\u2086 and one unit of ClpP\u2081\u2084 have an 862KDa weight (2 \u00d7 270 + 322 = 862 KDa). Cite PPT_File.pptx Slide 1, for the subunit stoichiometry of each panel.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 4, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 47": { + "description": "Labels Zinc_Binding_Assay.pptx, Slide 3, panel 9 as two \"ClpX\u2086\" and one \"ClpP\u2081\u2084\".", + "justification": "Paper 1 and Paper 3 provide the two ClpX\u2086 caps flanking ClpP\u2081\u2084. Cite PPT_File.pptx Slide 1 and Paper_1.pdf page 3 (Figure 1\u2014figure supplement 1). ", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 4, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 48": { + "description": "Labels panel 10 with a size of 862KDa.", + "justification": "The prompt states that ClpP has a molecular weight of 23 KDa and ClpX of 45 KDa. The 14 units of ClpP\u2081\u2084 have a molecular weight of 322 KDa and 6 units of ClpX\u2086 have a molecular weight of 270 kDa. Two units of ClpX\u2086 and one unit of ClpP\u2081\u2084 have an 862KDa weight (2 \u00d7 270 + 322 = 862 KDa). Cite PPT_File.pptx Slide 1 for the subunit stoichiometry of each panel.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 4, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 49": { + "description": "Labels Zinc_Binding_Assay.pptx, Slide 3, panel 10 as two \"ClpX\u2086\" and one \"ClpP\u2081\u2084\".", + "justification": "Paper 1 and Paper 3 provide the two ClpX\u2086 caps flanking ClpP\u2081\u2084. Cite PPT_File.pptx Slide 1 and Paper_1.pdf page 3 (Figure 1\u2014figure supplement 1). ", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 4, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 50": { + "description": "Presents table with column headers, 'Strains' and 'Filament Length' on Slide 4.", + "justification": "The prompt asks for a comparative table of filamentation defects relative to empty plasmid and WT, so the table must make this information explicit.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 51": { + "description": "Places a page number at 10 point.", + "justification": "The branding layout file includes page numbers in size 10.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 52": { + "description": "Classifies empty plasmid as >10 \u00b5m (very long filamentous cells) on Slide 4.", + "justification": "The prompt defines >10 \u00b5m as very long filamentous cells. PPT_File.pptx, slide 2, shows the elongated filamentation defect of the empty plasmid. \"The rule is to compare the population average defects in filament length with respect to WT and empty plasmid where WT has a normal filamentation morphology, estimate to the nearest whole number. Short cells (<5\u00b5m), long filamentous cells (5-10\u00b5m), and very long filamentous cells (>10\u00b5m).\"", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 53": { + "description": "Classifies WT as <5 \u00b5m (short cells) on Slide 4.", + "justification": "The prompt defines WT as <5 \u00b5m as short cells; the supporting PPT_File.pptx slide 2 visually matches this class. \"The rule is to compare the population average defects in filament length with respect to WT and empty plasmid where WT has a normal filamentation morphology, estimate to the nearest whole number. Short cells (<5\u00b5m), long filamentous cells (5-10\u00b5m), and very long filamentous cells (>10\u00b5m).\"", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 54": { + "description": "Classifies R1S as 5\u201310 \u00b5m (long filamentous cells) on Slide 4.", + "justification": "The first-line supporting PPT \"PPT_File.pptx\" slide 2 comparison places R1S in the intermediate long-filament class defined by the prompt as 5\u201310 \u00b5m. \"The rule is to compare the population average defects in filament length with respect to WT and empty plasmid where WT has a normal filamentation morphology, estimate to the nearest whole number. Short cells (<5\u00b5m), long filamentous cells (5-10\u00b5m), and very long filamentous cells (>10\u00b5m).\"", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 55": { + "description": "Classifies R2S as 5\u201310 \u00b5m (long filamentous cells) on Slide 4.", + "justification": "The first-line supporting PPT \"PPT_File.pptx\" slide 2 comparison places R2S in the intermediate long-filament class defined by the prompt as 5\u201310 \u00b5m. \"The rule is to compare the population average defects in filament length with respect to WT and empty plasmid where WT has a normal filamentation morphology, estimate to the nearest whole number. Short cells (<5\u00b5m), long filamentous cells (5-10\u00b5m), and very long filamentous cells (>10\u00b5m).\"", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 56": { + "description": "Classifies R3S as 5\u201310 \u00b5m (long filamentous cells) on Slide 4.", + "justification": "The first-line supporting PPT \"PPT_File.pptx\" slide 2 comparison places R3S in the intermediate long-filament class defined by the prompt as 5\u201310 \u00b5m. \"The rule is to compare the population average defects in filament length with respect to WT and empty plasmid where WT has a normal filamentation morphology, estimate to the nearest whole number. Short cells (<5\u00b5m), long filamentous cells (5-10\u00b5m), and very long filamentous cells (>10\u00b5m).\"", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 57": { + "description": "Classifies R4S as 5\u201310 \u00b5m (long filamentous cells) on Slide 4.", + "justification": "The first-line supporting PPT \"PPT_File.pptx\" slide 2 comparison places R4S in the intermediate long-filament class defined by the prompt as 5\u201310 \u00b5m. \"The rule is to compare the population average defects in filament length with respect to WT and empty plasmid where WT has a normal filamentation morphology, estimate to the nearest whole number. Short cells (<5\u00b5m), long filamentous cells (5-10\u00b5m), and very long filamentous cells (>10\u00b5m).\"", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 58": { + "description": "Classifies R5S as >10 \u00b5m (very long filamentous cells) on Slide 4.", + "justification": "The first-line supporting PPT \"PPT_File.pptx\" slide 2 comparison places R5S in the very-long filamentation class defined by the prompt as >10 \u00b5m. \"The rule is to compare the population average defects in filament length with respect to WT and empty plasmid where WT has a normal filamentation morphology, estimate to the nearest whole number. Short cells (<5\u00b5m), long filamentous cells (5-10\u00b5m), and very long filamentous cells (>10\u00b5m).\"", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 59": { + "description": "Classifies R6S as >10 \u00b5m (very long filamentous cells) on Slide 4.", + "justification": "The first-line supporting PPT \"PPT_File.pptx\" slide 2 comparison places R6S in the very-long filamentation class defined by the prompt as >10 \u00b5m. \"The rule is to compare the population average defects in filament length with respect to WT and empty plasmid where WT has a normal filamentation morphology, estimate to the nearest whole number. Short cells (<5\u00b5m), long filamentous cells (5-10\u00b5m), and very long filamentous cells (>10\u00b5m).\"", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 60": { + "description": "Classifies R7S as >10 \u00b5m (very long filamentous cells) on Slide 4.", + "justification": "The first-line supporting PPT \"PPT_File.pptx\" slide 2 comparison places R7S in the very-long filamentation class defined by the prompt as >10 \u00b5m. \"The rule is to compare the population average defects in filament length with respect to WT and empty plasmid where WT has a normal filamentation morphology, estimate to the nearest whole number. Short cells (<5\u00b5m), long filamentous cells (5-10\u00b5m), and very long filamentous cells (>10\u00b5m).\"", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 61": { + "description": "Classifies R8S as <5 \u00b5m (short cells) on Slide 4.", + "justification": "The first-line supporting PPT \"PPT_File.pptx\" slide 2 comparison places R8S in the short-cell class, matching WT-like normal filamentation under the prompt's categories. \"The rule is to compare the population average defects in filament length with respect to WT and empty plasmid where WT has a normal filamentation morphology, estimate to the nearest whole number. Short cells (<5\u00b5m), long filamentous cells (5-10\u00b5m), and very long filamentous cells (>10\u00b5m).\"", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 62": { + "description": "Italicizes the mutant names R1S through R8S in the Slide 4 table.", + "justification": "The prompt instructs to italicise the mutant names. ", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 63": { + "description": "Applies fill color #0070C0 to the Slide 4 table header row.", + "justification": "The branding layout file includes the table heading color #0070C0.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 64": { + "description": "Draws a black rectangular border around the Slide 4 table.", + "justification": "The branding layout file includes a black border around the table.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 65": { + "description": "Applies fill color #FFFFFF and #F0F2F5 in alternating cells to the Slide 4 table subsection/body cells.", + "justification": "The branding layout file includes subsection color #FFFFFF and #F0F2F5.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 66": { + "description": "Places the name of the protein below the gel image with its molecular weight in KDa on Slide 5.", + "justification": "The branding layout file includes the name of the protein below the gel image with the size (in KDa).", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 67": { + "description": "States gel 1 (the first purified-protein gel panel) as R1S with a size of 45 KDa.", + "justification": "The molecular-weight table in the PPT file, slide 3, lists R1S at 45 KDa, R2S 62, R3S 52, R4S 58, R5S 19, R6S 37, R7S 13, R8S 30, R0S 25, and R9S 47 KDa. In gel 1, the final-protein lane band migrates between the 37 and 50 kDa marker bands of the 250 to 2 kDa ladder, which matches only the 45 kDa entry, R1S.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 68": { + "description": "States gel 2 (the second purified-protein gel panel) as R7S with a size of 13 KDa.", + "justification": "In gel 2 the final-protein lane band runs near the bottom of the 250 to 2 kDa marker ladder, between the 10 and 15 kDa marker bands; the only entry in the PPT File slide 3 table in that range is R7S at 13 kDa.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 69": { + "description": "States gel 3 (the third purified-protein gel panel) as R5S with a size of 19 KDa.", + "justification": "In gel 3 the final-protein lane band migrates between the 15 and 20 kDa marker bands of the 250 to 2 kDa ladder; the matching table entry in PPT File slide 3 is R5S at 19 kDa.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 70": { + "description": "States gel 4 (the fourth purified-protein gel panel) as R0S with a size of 25 KDa.", + "justification": "In gel 4, the final-protein lane band aligns with the 25 kDa marker band of the 250 to 2 kDa ladder; the only entry of that mass in the PPT file, slide 3 table, is R0S at 25 kDa.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 71": { + "description": "States gel 5 (the fifth purified-protein gel panel) as R9S with a size of 47 KDa.", + "justification": "In gel 5 the final-protein lane band migrates just below the 50 kDa marker band of the 250 to 2 kDa ladder, which matches the 47 kDa entry, R9S, rather than the 52 kDa entry that would run just above 50 kDa.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 72": { + "description": "States gel 6 (the sixth purified-protein gel panel) as R3S with a size of 52 KDa.", + "justification": "In gel 6, the final-protein lane band migrates at or just above the 50 kDa marker band of the 250 to 2 kDa ladder, matching the 52 kDa entry in the PPT_File.pptx slide 3 table, R3S.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 73": { + "description": "States gel 7 (the seventh purified-protein gel panel) as R6S with a size of 37 KDa.", + "justification": "In gel 7 the final band aligns with the 37 kDa marker band of the 250 to 2 kDa ladder, matching the R6S entry at 37 kDa in the PPT File slide 3 table.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 74": { + "description": "Presents a table with column headers: panel number, protein name, and Total Size (KDa), their respective molecular weights as Total Size (KDa), on Slide 6.", + "justification": "The branding layout file includes a table showing proteins and their respective molecular weight for 2-D classified complexes 1-10", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 75": { + "description": "Applies fill color #E7E7E7 and #FFFFFF in alternating cells to the Slide 6 table subsection/body cells.", + "justification": "The branding layout file includes subsection color #E7E7E7 and #FFFFFF.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 76": { + "description": "Labels panel 1 with a size of 322KDa.", + "justification": "The prompt mentions the molecular weight of ClpP as 23 kDa. The 14 units of ClpP\u2081\u2084 have the molecular weight of 322KDa. Cite PPT_File.pptx Slide 1 for the subunit stoichiometry of each panel.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 4, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 77": { + "description": "Plots all four curves starting from 0.0000 Zn per protein monomer at 0 PMB equivalents (acceptable value is 0.0000).", + "justification": "The prompt states, 'baseline correction with respect to 0 \u00b5M PMB should be done after calculating zinc concentration and before calculating zinc concentration/ protein monomer'. Subtracting each variant's own 0 \u00b5M PMB zinc concentration from itself forces every curve through the 0,0 point.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 78": { + "description": "Uses all non-heading slide text at 20 pt, excluding the separately specified page numbers.", + "justification": "The branding layout file includes all non-heading slide text at 20 pt; page numbers have a separate 10 pt requirement. ", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 79": { + "description": "Uses #000000 for all text color except the graph x and y axis coordinates on slide 2.", + "justification": "The branding layout file includes a styling requirement that requires #000000 as the color for all text.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 80": { + "description": "Labels panel 7 with a size of 862KDa.", + "justification": "The prompt states that ClpP has a molecular weight of 23 KDa and ClpX of 45 KDa. The 14 units of ClpP\u2081\u2084 have a molecular weight of 322 KDa and 6 units of ClpX\u2086 have a molecular weight of 270 kDa. Two units of ClpX\u2086 and one unit of ClpP\u2081\u2084 have an 862KDa weight (2 \u00d7 270 + 322 = 862 KDa). Cite PPT_File.pptx Slide 1 for the subunit stoichiometry of each panel.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 4, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 81": { + "description": "Labels panel 8 with a size of 862KDa.", + "justification": "The prompt states that ClpP has a molecular weight of 23 KDa and ClpX of 45 KDa. The 14 units of ClpP\u2081\u2084 have a molecular weight of 322 KDa and 6 units of ClpX\u2086 have a molecular weight of 270 kDa. Two units of ClpX\u2086 and one unit of ClpP\u2081\u2084 have an 862KDa weight (2 \u00d7 270 + 322 = 862 KDa). Cite PPT_File.pptx Slide 1 for the subunit stoichiometry of each panel.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 4, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 82": { + "description": "Labels panel 2 with a size of 644KDa.", + "justification": "The prompt states that ClpP has a molecular weight of 23 KDa. The 14 units of ClpP\u2081\u2084 have a molecular weight of 322KDa, and 2 units have a molecular weight of 644KDa. Cite PPT_File.pptx Slide 1 for the subunit stoichiometry of each panel.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 4, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 83": { + "description": "Labels panel 3 with a size of 1184KDa.", + "justification": "The prompt states that ClpP has a molecular weight of 23 KDa and ClpX has 45 KDa. The 14 units of ClpP\u2081\u2084 have a molecular weight of 322 KDa and 6 units of ClpX\u2086 have a molecular weight of 270 kDa, for a total of 592 KDa. Two units of the complex have a molecular weight of 1184 kDa. Cite PPT_File.pptx Slide 1 for the subunit stoichiometry of each panel.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 4, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 84": { + "description": "Labels panel 4 with a size of 862KDa.", + "justification": "The prompt states that ClpP has a molecular weight of 23 KDa and ClpX of 45 KDa. The 14 units of ClpP\u2081\u2084 have a molecular weight of 322 KDa and 6 units of ClpX\u2086 have a molecular weight of 270 kDa. Two units of ClpX\u2086 and one unit of ClpP\u2081\u2084 have an 862KDa weight (2 \u00d7 270 + 322 = 862 KDa). Cite PPT_File.pptx Slide 1 for the subunit stoichiometry of each panel.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 4, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 85": { + "description": "Labels panel 1 protein name as ClpP\u2081\u2084 on Slide 6.", + "justification": "The prompt asks for a table listing protein names and their molecular weights for 2-D classified complexes 1-10, citing PPT_File.pptx Slide 1 and Paper_1.pdf page 3 (Figure 1\u2014figure supplement 1)", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 4, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 86": { + "description": "Labels panel 2 protein name as 2 x ClpP\u2081\u2084 on Slide 6.", + "justification": "The prompt asks for a table listing protein names and their molecular weights for 2-D classified complexes 1-10, citing PPT_File.pptx Slide 1 and Paper_1.pdf page 3 (Figure 1\u2014figure supplement 1)", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 4, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 87": { + "description": "Labels panel 3 protein name as (ClpXP(ClpX\u2086+ClpP\u2081\u2084)x2)/ 2 x ClpXP on Slide 6.", + "justification": "The prompt asks for a table listing protein names and their molecular weights for 2-D classified complexes 1-10, citing PPT_File.pptx Slide 1 and Paper_1.pdf page 3 (Figure 1\u2014figure supplement 1)", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 4, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 88": { + "description": "Labels panel 4 protein name as (ClpX\u2086+ClpP\u2081\u2084+ClpX\u2086)/Double-capped ClpXP (2ClpX6 + ClpP14) on Slide 6.", + "justification": "The prompt asks for a table listing protein names and their molecular weights for 2-D classified complexes 1-10, citing PPT_File.pptx Slide 1 and Paper_1.pdf page 3 (Figure 1\u2014figure supplement 1)", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 4, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 89": { + "description": "Labels panel 6 protein name as (ClpXP(ClpX\u2086+ClpP\u2081\u2084)) on Slide 6.", + "justification": "The prompt asks for a table listing protein names and their molecular weights for 2-D classified complexes 1-10, citing PPT_File.pptx Slide 1 and Paper_1.pdf page 3 (Figure 1\u2014figure supplement 1)", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 4, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 90": { + "description": "Labels panel 5 protein name as ClpP\u2081\u2084 on Slide 6.", + "justification": "The prompt asks for a table listing protein names and their molecular weights for 2-D classified complexes 1-10, citing PPT_File.pptx Slide 1 and Paper_1.pdf page 3 (Figure 1\u2014figure supplement 1)", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 4, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 91": { + "description": "Labels panel 7 protein name as (ClpX\u2086+ClpP\u2081\u2084+ClpX\u2086)/Double-capped ClpXP (2ClpX6 + ClpP14) on Slide 6.", + "justification": "The prompt asks for a table listing protein names and their molecular weights for 2-D classified complexes 1-10, citing PPT_File.pptx Slide 1 and Paper_1.pdf page 3 (Figure 1\u2014figure supplement 1)", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 4, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 92": { + "description": "Applies fill color #0070C0 to the Slide 6 table header row.", + "justification": "The branding layout file includes the table heading color #0070C0.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 93": { + "description": "Plots 0.3846 Zn per protein monomer at 1 PMB equivalents (acceptable value is 0.3846) for the WT line.", + "justification": "Plotting the Zinc_binding_values.xlsx to generate the linear regression curve yields y = 0.0013x + 0.0017. Rearrange the equation to solve for zinc conc. (uM), x = [(y - 0.0017) / 0.0013]. Use the provided absorbance value to solve for the respective zinc concentrations, x. Normalize each zinc concentration to the respective 0 uM Zn conc, and then calculate the Zinc/protein monomer by dividing by 30. \nx = [(y - 0.0017) / 0.0013]; Zn/protein monomer = (x - x_0uM) /30. \nx = [(0.132 - 0.0017) / 0.0013] = 100.2308; Zn/protein monomer = (100.2308 - 88.6923) /30 = 0.3846", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 94": { + "description": "Plots 0.6154 Zn per protein monomer at 2 PMB equivalents (acceptable value is 0.6154) for the WT line.", + "justification": "Plotting the Zinc_binding_values.xlsx to generate the linear regression curve yields y = 0.0013x + 0.0017. Rearrange the equation to solve for zinc conc. (uM), x = [(y - 0.0017) / 0.0013]. Use the provided absorbance value to solve for the respective zinc concentrations, x. Normalize each zinc concentration to the respective 0 uM Zn conc, and then calculate the Zinc/protein monomer by dividing by 30. \nx = [(y - 0.0017) / 0.0013]; Zn/protein monomer = (x - x_0uM) /30. \nx = [(0.141 - 0.0017) / 0.0013] = 107.1538; Zn/protein monomer = (107.1538 - 88.6923) /30 = 0.6154", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 95": { + "description": "Plots 0.7179 Zn per protein monomer at 3 PMB equivalents (acceptable value is 0.7179) for the WT line.", + "justification": "Plotting the Zinc_binding_values.xlsx to generate the linear regression curve yields y = 0.0013x + 0.0017. Rearrange the equation to solve for zinc conc. (uM), x = [(y - 0.0017) / 0.0013]. Use the provided absorbance value to solve for the respective zinc concentrations, x. Normalize each zinc concentration to the respective 0 uM Zn conc, and then calculate the Zinc/protein monomer by dividing by 30. \nx = [(y - 0.0017) / 0.0013]; Zn/protein monomer = (x - x_0uM) /30. \nx = [(0.145 - 0.0017) / 0.0013] = 110.2308; Zn/protein monomer = (110.2308 - 88.6923) /30 = 0.7179", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 96": { + "description": "Plots 1.0000 Zn per protein monomer at 4 PMB equivalents (acceptable value is 1.0000) for the WT line.", + "justification": "Plotting the Zinc_binding_values.xlsx to generate the linear regression curve yields y = 0.0013x + 0.0017. Rearrange the equation to solve for zinc conc. (uM), x = [(y - 0.0017) / 0.0013]. Use the provided absorbance value to solve for the respective zinc concentrations, x. Normalize each zinc concentration to the respective 0 uM Zn conc, and then calculate the Zinc/protein monomer by dividing by 30. \nx = [(y - 0.0017) / 0.0013]; Zn/protein monomer = (x - x_0uM) /30. \nx = [(0.156 - 0.0017) / 0.0013] = 118.6923; Zn/protein monomer = (118.6923 - 88.6923) /30 = 1.0000", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 97": { + "description": "Plots 1.0256 Zn per protein monomer at 5 PMB equivalents (acceptable value is 1.0256) for the WT line.", + "justification": "Plotting the Zinc_binding_values.xlsx to generate the linear regression curve yields y = 0.0013x + 0.0017. Rearrange the equation to solve for zinc conc. (uM), x = [(y - 0.0017) / 0.0013]. Use the provided absorbance value to solve for the respective zinc concentrations, x. Normalize each zinc concentration to the respective 0 uM Zn conc, and then calculate the Zinc/protein monomer by dividing by 30. \nx = [(y - 0.0017) / 0.0013]; Zn/protein monomer = (x - x_0uM) /30. \nx = [(0.157 - 0.0017) / 0.0013] = 119.4615; Zn/protein monomer = (119.4615 - 88.6923) /30 = 1.0256", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 98": { + "description": "Plots 1.0513 Zn per protein monomer at 6 PMB equivalents (acceptable value is 1.0513) for the WT line.", + "justification": "Plotting the Zinc_binding_values.xlsx to generate the linear regression curve yields y = 0.0013x + 0.0017. Rearrange the equation to solve for zinc conc. (uM), x = [(y - 0.0017) / 0.0013]. Use the provided absorbance value to solve for the respective zinc concentrations, x. Normalize each zinc concentration to the respective 0 uM Zn conc, and then calculate the Zinc/protein monomer by dividing by 30. \nx = [(y - 0.0017) / 0.0013]; Zn/protein monomer = (x - x_0uM) /30. \nx = [(0.158 - 0.0017) / 0.0013] = 120.2308; Zn/protein monomer = (120.2308 - 88.6923) /30 = 1.0513", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 99": { + "description": "Plots 1.0513 Zn per protein monomer at 7 PMB equivalents (acceptable value is 1.0513) for the WT line.", + "justification": "Plotting the Zinc_binding_values.xlsx to generate the linear regression curve yields y = 0.0013x + 0.0017. Rearrange the equation to solve for zinc conc. (uM), x = [(y - 0.0017) / 0.0013]. Use the provided absorbance value to solve for the respective zinc concentrations, x. Normalize each zinc concentration to the respective 0 uM Zn conc, and then calculate the Zinc/protein monomer by dividing by 30. \nx = [(y - 0.0017) / 0.0013]; Zn/protein monomer = (x - x_0uM) /30. \nx = [(0.158 - 0.0017) / 0.0013] = 120.2308; Zn/protein monomer = (120.2308 - 88.6923) / 30 = 1.0513", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 100": { + "description": "Plots 1.0256 Zn per protein monomer at 8 PMB equivalents (acceptable value is 1.0256) for the WT line.", + "justification": "Plotting the Zinc_binding_values.xlsx to generate the linear regression curve yields y = 0.0013x + 0.0017. Rearrange the equation to solve for zinc conc. (uM), x = [(y - 0.0017) / 0.0013]. Use the provided absorbance value to solve for the respective zinc concentrations, x. Normalize each zinc concentration to the respective 0 uM Zn conc, and then calculate the Zinc/protein monomer by dividing by 30. \nx = [(y - 0.0017) / 0.0013]; Zn/protein monomer = (x - x_0uM) /30. \nx = [(0.157 - 0.0017) / 0.0013] = 119.4615; Zn/protein monomer = (119.4615 - 88.6923) /30 = 1.0256", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 101": { + "description": "Plots 1.0513 Zn per protein monomer at 9 PMB equivalents (acceptable value is 1.0513) for the WT line.", + "justification": "Plotting the Zinc_binding_values.xlsx to generate the linear regression curve yields y = 0.0013x + 0.0017. Rearrange the equation to solve for zinc conc. (uM), x = [(y - 0.0017) / 0.0013]. Use the provided absorbance value to solve for the respective zinc concentrations, x. Normalize each zinc concentration to the respective 0 uM Zn conc, and then calculate the Zinc/protein monomer by dividing by 30. \nx = [(y - 0.0017) / 0.0013]; Zn/protein monomer = (x - x_0uM) /30. \nx = [(0.158 - 0.0017) / 0.0013] = 120.2308; Zn/protein monomer = (120.2308 - 88.6923) / 30 = 1.0513", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 102": { + "description": "Plots 0.0256 Zn per protein monomer at 1 PMB equivalents (acceptable value is 0.0256) for the R1S mutant line.", + "justification": "Plotting the Zinc_binding_values.xlsx to generate the linear regression curve yields y = 0.0013x + 0.0017. Rearrange the equation to solve for zinc conc. (uM), x = [(y - 0.0017) / 0.0013]. Use the provided absorbance value to solve for the respective zinc concentrations, x. Normalize each zinc concentration to the respective 0 uM Zn conc, and then calculate the Zinc/protein monomer by dividing by 30. \nx = [(y - 0.0017) / 0.0013]; Zn/protein monomer = (x - x_0uM) /30. \nx = [(0.082 - 0.0017) / 0.0013] = 61.7692; Zn/protein monomer = (61.7692 - 61.0000) /30 = 0.0256", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 103": { + "description": "Plots 0.0513 Zn per protein monomer at 2 PMB equivalents (acceptable value is 0.0513) for the R1S mutant line.", + "justification": "Plotting the Zinc_binding_values.xlsx to generate the linear regression curve yields y = 0.0013x + 0.0017. Rearrange the equation to solve for zinc conc. (uM), x = [(y - 0.0017) / 0.0013]. Use the provided absorbance value to solve for the respective zinc concentrations, x. Normalize each zinc concentration to the respective 0 uM Zn conc, and then calculate the Zinc/protein monomer by dividing by 30. \nx = [(y - 0.0017) / 0.0013]; Zn/protein monomer = (x - x_0uM) /30. \nx = [(0.083 - 0.0017) / 0.0013] = 62.5385; Zn/protein monomer = (62.5385 - 61.0000) /30 = 0.0513", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 104": { + "description": "Plots 0.1282 Zn per protein monomer at 3 PMB equivalents (acceptable value is 0.1282) for the R1S mutant line.", + "justification": "Plotting the Zinc_binding_values.xlsx to generate the linear regression curve yields y = 0.0013x + 0.0017. Rearrange the equation to solve for zinc conc. (uM), x = [(y - 0.0017) / 0.0013]. Use the provided absorbance value to solve for the respective zinc concentrations, x. Normalize each zinc concentration to the respective 0 uM Zn conc, and then calculate the Zinc/protein monomer by dividing by 30. \nx = [(y - 0.0017) / 0.0013]; Zn/protein monomer = (x - x_0uM) /30. \nx = [(0.086 - 0.0017) / 0.0013] = 64.8462; Zn/protein monomer = (64.8462 - 61.0000) /30 = 0.1282", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 105": { + "description": "Plots 0.1795 Zn per protein monomer at 4 PMB equivalents (acceptable value is 0.1795) for the R1S mutant line.", + "justification": "Plotting the Zinc_binding_values.xlsx to generate the linear regression curve yields y = 0.0013x + 0.0017. Rearrange the equation to solve for zinc conc. (uM), x = [(y - 0.0017) / 0.0013]. Use the provided absorbance value to solve for the respective zinc concentrations, x. Normalize each zinc concentration to the respective 0 uM Zn conc, and then calculate the Zinc/protein monomer by dividing by 30. \nx = [(y - 0.0017) / 0.0013]; Zn/protein monomer = (x - x_0uM) /30. \nx = [(0.088 - 0.0017) / 0.0013] = 66.3846; Zn/protein monomer = (66.3846 - 61.0000) /30 = 0.1795", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 106": { + "description": "Plots 0.1795 Zn per protein monomer at 5 PMB equivalents (acceptable value is 0.1795) for the R1S mutant line.", + "justification": "Plotting the Zinc_binding_values.xlsx to generate the linear regression curve yields y = 0.0013x + 0.0017. Rearrange the equation to solve for zinc conc. (uM), x = [(y - 0.0017) / 0.0013]. Use the provided absorbance value to solve for the respective zinc concentrations, x. Normalize each zinc concentration to the respective 0 uM Zn conc, and then calculate the Zinc/protein monomer by dividing by 30. \nx = [(y - 0.0017) / 0.0013]; Zn/protein monomer = (x - x_0uM) /30. \nx = [(0.088 - 0.0017) / 0.0013] = 66.3846; Zn/protein monomer = (66.3846 - 61.0000) /30 = 0.1795", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 107": { + "description": "Plots 0.1795 Zn per protein monomer at 6 PMB equivalents (acceptable value is 0.1795) for the R1S mutant line.", + "justification": "Plotting the Zinc_binding_values.xlsx to generate the linear regression curve yields y = 0.0013x + 0.0017. Rearrange the equation to solve for zinc conc. (uM), x = [(y - 0.0017) / 0.0013]. Use the provided absorbance value to solve for the respective zinc concentrations, x. Normalize each zinc concentration to the respective 0 uM Zn conc, and then calculate the Zinc/protein monomer by dividing by 30. \nx = [(y - 0.0017) / 0.0013]; Zn/protein monomer = (x - x_0uM) /30. \nx = [(0.088 - 0.0017) / 0.0013] = 66.3846; Zn/protein monomer = (66.3846 - 61.0000) /30 = 0.1795", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 108": { + "description": "Plots 0.1538 Zn per protein monomer at 7 PMB equivalents (acceptable value is 0.1538) for the R1S mutant line.", + "justification": "Plotting the Zinc_binding_values.xlsx to generate the linear regression curve yields y = 0.0013x + 0.0017. Rearrange the equation to solve for zinc conc. (uM), x = [(y - 0.0017) / 0.0013]. Use the provided absorbance value to solve for the respective zinc concentrations, x. Normalize each zinc concentration to the respective 0 uM Zn conc, and then calculate the Zinc/protein monomer by dividing by 30. \nx = [(y - 0.0017) / 0.0013]; Zn/protein monomer = (x - x_0uM) /30. \nx = [(0.087 - 0.0017) / 0.0013] = 65.6154; Zn/protein monomer = (65.6154 - 61.0000) /30 = 0.1538", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 109": { + "description": "Plots 0.1538 Zn per protein monomer at 8 PMB equivalents (acceptable value is 0.1538) for the R1S mutant line.", + "justification": "Plotting the Zinc_binding_values.xlsx to generate the linear regression curve yields y = 0.0013x + 0.0017. Rearrange the equation to solve for zinc conc. (uM), x = [(y - 0.0017) / 0.0013]. Use the provided absorbance value to solve for the respective zinc concentrations, x. Normalize each zinc concentration to the respective 0 uM Zn conc, and then calculate the Zinc/protein monomer by dividing by 30. \nx = [(y - 0.0017) / 0.0013]; Zn/protein monomer = (x - x_0uM) /30. \nx = [(0.087 - 0.0017) / 0.0013] = 65.6154; Zn/protein monomer = (65.6154 - 61.0000) /30 = 0.1538", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 110": { + "description": "Plots 0.1538 Zn per protein monomer at 9 PMB equivalents (acceptable value is 0.1538) for the R1S mutant line.", + "justification": "Plotting the Zinc_binding_values.xlsx to generate the linear regression curve yields y = 0.0013x + 0.0017. Rearrange the equation to solve for zinc conc. (uM), x = [(y - 0.0017) / 0.0013]. Use the provided absorbance value to solve for the respective zinc concentrations, x. Normalize each zinc concentration to the respective 0 uM Zn conc, and then calculate the Zinc/protein monomer by dividing by 30. \nx = [(y - 0.0017) / 0.0013]; Zn/protein monomer = (x - x_0uM) /30. \nx = [(0.087 - 0.0017) / 0.0013] = 65.6154; Zn/protein monomer = (65.6154 - 61.0000) /30 = 0.1538", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 111": { + "description": "Plots 0.0000 Zn per protein monomer at 1 PMB equivalents (acceptable value is 0.0000) for the R1,2S mutant line.", + "justification": "Plotting the Zinc_binding_values.xlsx to generate the linear regression curve yields y = 0.0013x + 0.0017. Rearrange the equation to solve for zinc conc. (uM), x = [(y - 0.0017) / 0.0013]. Use the provided absorbance value to solve for the respective zinc concentrations, x. Normalize each zinc concentration to the respective 0 uM Zn conc, and then calculate the Zinc/protein monomer by dividing by 30. \nx = [(y - 0.0017) / 0.0013]; Zn/protein monomer = (x - x_0uM) /30. \nx = [(0.088 - 0.0017) / 0.0013] = 66.3846; Zn/protein monomer = (66.3846 - 66.3846) /30 = 0.0000", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 112": { + "description": "Plots 0.1795 Zn per protein monomer at 2 PMB equivalents (acceptable value is 0.1795) for the R1,2S mutant line.", + "justification": "Plotting the Zinc_binding_values.xlsx to generate the linear regression curve yields y = 0.0013x + 0.0017. Rearrange the equation to solve for zinc conc. (uM), x = [(y - 0.0017) / 0.0013]. Use the provided absorbance value to solve for the respective zinc concentrations, x. Normalize each zinc concentration to the respective 0 uM Zn conc, and then calculate the Zinc/protein monomer by dividing by 30. \nx = [(y - 0.0017) / 0.0013]; Zn/protein monomer = (x - x_0uM) /30. \nx = [(0.095 - 0.0017) / 0.0013] = 71.7692; x_0uM = [(0.088 - 0.0017) / 0.0013] = 66.3846; Zn/protein monomer = (71.7692 - 66.3846) / 30 = 0.1795", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 113": { + "description": "Plots 0.2051 Zn per protein monomer at 3 PMB equivalents (acceptable value is 0.2051) for the R1,2S mutant line.", + "justification": "Plotting the Zinc_binding_values.xlsx to generate the linear regression curve yields y = 0.0013x + 0.0017. Rearrange the equation to solve for zinc conc. (uM), x = [(y - 0.0017) / 0.0013]. Use the provided absorbance value to solve for the respective zinc concentrations, x. Normalize each zinc concentration to the respective 0 uM Zn conc, and then calculate the Zinc/protein monomer by dividing by 30. \nx = [(y - 0.0017) / 0.0013]; Zn/protein monomer = (x - x_0uM) /30. \nx = [(0.096 - 0.0017) / 0.0013] = 72.5385; Zn/protein monomer = (72.5385 - 66.3846) /30 = 0.2051", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 114": { + "description": "Plots 0.2051 Zn per protein monomer at 4 PMB equivalents (acceptable value is 0.2051) for the R1,2S mutant line.", + "justification": "Plotting the Zinc_binding_values.xlsx to generate the linear regression curve yields y = 0.0013x + 0.0017. Rearrange the equation to solve for zinc conc. (uM), x = [(y - 0.0017) / 0.0013]. Use the provided absorbance value to solve for the respective zinc concentrations, x. Normalize each zinc concentration to the respective 0 uM Zn conc, and then calculate the Zinc/protein monomer by dividing by 30. \nx = [(y - 0.0017) / 0.0013]; Zn/protein monomer = (x - x_0uM) /30. \nx = [(0.096 - 0.0017) / 0.0013] = 72.5385; Zn/protein monomer = (72.5385 - 66.3846) /30 = 0.2051", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 115": { + "description": "Plots 0.2051 Zn per protein monomer at 5 PMB equivalents (acceptable value is 0.2051) for the R1,2S mutant line.", + "justification": "Plotting the Zinc_binding_values.xlsx to generate the linear regression curve yields y = 0.0013x + 0.0017. Rearrange the equation to solve for zinc conc. (uM), x = [(y - 0.0017) / 0.0013]. Use the provided absorbance value to solve for the respective zinc concentrations, x. Normalize each zinc concentration to the respective 0 uM Zn conc, and then calculate the Zinc/protein monomer by dividing by 30. \nx = [(y - 0.0017) / 0.0013]; Zn/protein monomer = (x - x_0uM) /30. \nx = [(0.096 - 0.0017) / 0.0013] = 72.5385; Zn/protein monomer = (72.5385 - 66.3846) /30 = 0.2051", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 116": { + "description": "Plots 0.1795 Zn per protein monomer at 6 PMB equivalents (acceptable value is 0.1795) for the R1,2S mutant line.", + "justification": "Plotting the Zinc_binding_values.xlsx to generate the linear regression curve yields y = 0.0013x + 0.0017. Rearrange the equation to solve for zinc conc. (uM), x = [(y - 0.0017) / 0.0013]. Use the provided absorbance value to solve for the respective zinc concentrations, x. Normalize each zinc concentration to the respective 0 uM Zn conc, and then calculate the Zinc/protein monomer by dividing by 30. \nx = [(y - 0.0017) / 0.0013]; Zn/protein monomer = (x - x_0uM) /30. \nx = [(0.095 - 0.0017) / 0.0013] = 71.7692; x_0uM = [(0.088 - 0.0017) / 0.0013] = 66.3846; Zn/protein monomer = (71.7692 - 66.3846) / 30 = 0.1795", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 117": { + "description": "Plots 0.1538 Zn per protein monomer at 7 PMB equivalents (acceptable value is 0.1538) for the R1,2S mutant line.", + "justification": "Plotting the Zinc_binding_values.xlsx to generate the linear regression curve yields y = 0.0013x + 0.0017. Rearrange the equation to solve for zinc conc. (uM), x = [(y - 0.0017) / 0.0013]. Use the provided absorbance value to solve for the respective zinc concentrations, x. Normalize each zinc concentration to the respective 0 uM Zn conc, and then calculate the Zinc/protein monomer by dividing by 30. \nx = [(y - 0.0017) / 0.0013]; Zn/protein monomer = (x - x_0uM) /30. \nx = [(0.094 - 0.0017) / 0.0013] = 71.0000; Zn/protein monomer = (71.0000 - 66.3846) /30 = 0.1538", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 118": { + "description": "Plots 0.1538 Zn per protein monomer at 8 PMB equivalents (acceptable value is 0.1538) for the R1,2S mutant line.", + "justification": "Plotting the Zinc_binding_values.xlsx to generate the linear regression curve yields y = 0.0013x + 0.0017. Rearrange the equation to solve for zinc conc. (uM), x = [(y - 0.0017) / 0.0013]. Use the provided absorbance value to solve for the respective zinc concentrations, x. Normalize each zinc concentration to the respective 0 uM Zn conc, and then calculate the Zinc/protein monomer by dividing by 30. \nx = [(y - 0.0017) / 0.0013]; Zn/protein monomer = (x - x_0uM) /30. \nx = [(0.094 - 0.0017) / 0.0013] = 71.0000; Zn/protein monomer = (71.0000 - 66.3846) /30 = 0.1538", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 119": { + "description": "Plots 0.1538 Zn per protein monomer at 9 PMB equivalents (acceptable value is 0.1538) for the R1,2S mutant line.", + "justification": "Plotting the Zinc_binding_values.xlsx to generate the linear regression curve yields y = 0.0013x + 0.0017. Rearrange the equation to solve for zinc conc. (uM), x = [(y - 0.0017) / 0.0013]. Use the provided absorbance value to solve for the respective zinc concentrations, x. Normalize each zinc concentration to the respective 0 uM Zn conc, and then calculate the Zinc/protein monomer by dividing by 30. \nx = [(y - 0.0017) / 0.0013]; Zn/protein monomer = (x - x_0uM) /30. \nx = [(0.094 - 0.0017) / 0.0013] = 71.0000; Zn/protein monomer = (71.0000 - 66.3846) /30 = 0.1538", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 120": { + "description": "Plots 0.0000 Zn per protein monomer at 1 PMB equivalents (acceptable value is 0.0000) for the R0S mutant line.", + "justification": "Plotting the Zinc_binding_values.xlsx to generate the linear regression curve yields y = 0.0013x + 0.0017. Rearrange the equation to solve for zinc conc. (uM), x = [(y - 0.0017) / 0.0013]. Use the provided absorbance value to solve for the respective zinc concentrations, x. Normalize each zinc concentration to the respective 0 uM Zn conc, and then calculate the Zinc/protein monomer by dividing by 30. \nx = [(y - 0.0017) / 0.0013]; Zn/protein monomer = (x - x_0uM) /30. \nx = [(0.082 - 0.0017) / 0.0013] = 61.7692; Zn/protein monomer = (61.7692 - 61.7692) /30 = 0.0000", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 121": { + "description": "Plots 0.0256 Zn per protein monomer at 2 PMB equivalents (acceptable value is 0.0256) for the R0S mutant line.", + "justification": "Plotting the Zinc_binding_values.xlsx to generate the linear regression curve yields y = 0.0013x + 0.0017. Rearrange the equation to solve for zinc conc. (uM), x = [(y - 0.0017) / 0.0013]. Use the provided absorbance value to solve for the respective zinc concentrations, x. Normalize each zinc concentration to the respective 0 uM Zn conc, and then calculate the Zinc/protein monomer by dividing by 30. \nx = [(y - 0.0017) / 0.0013]; Zn/protein monomer = (x - x_0uM) /30. \nx = [(0.083 - 0.0017) / 0.0013] = 62.5385; Zn/protein monomer = (62.5385 - 61.7692) /30 = 0.0256", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 122": { + "description": "Plots 0.0000 Zn per protein monomer at 3 PMB equivalents (acceptable value is 0.0000) for the R0S mutant line.", + "justification": "Plotting the Zinc_binding_values.xlsx to generate the linear regression curve yields y = 0.0013x + 0.0017. Rearrange the equation to solve for zinc conc. (uM), x = [(y - 0.0017) / 0.0013]. Use the provided absorbance value to solve for the respective zinc concentrations, x. Normalize each zinc concentration to the respective 0 uM Zn conc, and then calculate the Zinc/protein monomer by dividing by 30. \nx = [(y - 0.0017) / 0.0013]; Zn/protein monomer = (x - x_0uM) /30. \nx = [(0.082 - 0.0017) / 0.0013] = 61.7692; Zn/protein monomer = (61.7692 - 61.7692) /30 = 0.0000", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 123": { + "description": "Plots 0.0513 Zn per protein monomer at 4 PMB equivalents (acceptable value is 0.0513) for the R0S mutant line.", + "justification": "Plotting the Zinc_binding_values.xlsx to generate the linear regression curve yields y = 0.0013x + 0.0017. Rearrange the equation to solve for zinc conc. (uM), x = [(y - 0.0017) / 0.0013]. Use the provided absorbance value to solve for the respective zinc concentrations, x. Normalize each zinc concentration to the respective 0 uM Zn conc, and then calculate the Zinc/protein monomer by dividing by 30. \nx = [(y - 0.0017) / 0.0013]; Zn/protein monomer = (x - x_0uM) /30. \nx = [(0.084 - 0.0017) / 0.0013] = 63.3077; Zn/protein monomer = (63.3077 - 61.7692) /30 = 0.0513", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 124": { + "description": "Plots 0.0000 Zn per protein monomer at 5 PMB equivalents (acceptable value is 0.0000) for the R0S mutant line.", + "justification": "Plotting the Zinc_binding_values.xlsx to generate the linear regression curve yields y = 0.0013x + 0.0017. Rearrange the equation to solve for zinc conc. (uM), x = [(y - 0.0017) / 0.0013]. Use the provided absorbance value to solve for the respective zinc concentrations, x. Normalize each zinc concentration to the respective 0 uM Zn conc, and then calculate the Zinc/protein monomer by dividing by 30. \nx = [(y - 0.0017) / 0.0013]; Zn/protein monomer = (x - x_0uM) /30. \nx = [(0.082 - 0.0017) / 0.0013] = 61.7692; Zn/protein monomer = (61.7692 - 61.7692) /30 = 0.0000", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 125": { + "description": "Plots 0.0256 Zn per protein monomer at 6 PMB equivalents (acceptable value is 0.0256) for the R0S mutant line.", + "justification": "Plotting the Zinc_binding_values.xlsx to generate the linear regression curve yields y = 0.0013x + 0.0017. Rearrange the equation to solve for zinc conc. (uM), x = [(y - 0.0017) / 0.0013]. Use the provided absorbance value to solve for the respective zinc concentrations, x. Normalize each zinc concentration to the respective 0 uM Zn conc, and then calculate the Zinc/protein monomer by dividing by 30. \nx = [(y - 0.0017) / 0.0013]; Zn/protein monomer = (x - x_0uM) /30. \nx = [(0.083 - 0.0017) / 0.0013] = 62.5385; Zn/protein monomer = (62.5385 - 61.7692) /30 = 0.0256", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 126": { + "description": "Plots 0.0256 Zn per protein monomer at 7 PMB equivalents (acceptable value is 0.0256) for the R0S mutant line.", + "justification": "Plotting the Zinc_binding_values.xlsx to generate the linear regression curve yields y = 0.0013x + 0.0017. Rearrange the equation to solve for zinc conc. (uM), x = [(y - 0.0017) / 0.0013]. Use the provided absorbance value to solve for the respective zinc concentrations, x. Normalize each zinc concentration to the respective 0 uM Zn conc, and then calculate the Zinc/protein monomer by dividing by 30. \nx = [(y - 0.0017) / 0.0013]; Zn/protein monomer = (x - x_0uM) /30. \nx = [(0.083 - 0.0017) / 0.0013] = 62.5385; Zn/protein monomer = (62.5385 - 61.7692) /30 = 0.0256", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 127": { + "description": "Plots 0.0513 Zn per protein monomer at 8 PMB equivalents (acceptable value is 0.0513) for the R0S mutant line.", + "justification": "Plotting the Zinc_binding_values.xlsx to generate the linear regression curve yields y = 0.0013x + 0.0017. Rearrange the equation to solve for zinc conc. (uM), x = [(y - 0.0017) / 0.0013]. Use the provided absorbance value to solve for the respective zinc concentrations, x. Normalize each zinc concentration to the respective 0 uM Zn conc, and then calculate the Zinc/protein monomer by dividing by 30. \nx = [(y - 0.0017) / 0.0013]; Zn/protein monomer = (x - x_0uM) /30. \nx = [(0.084 - 0.0017) / 0.0013] = 63.3077; Zn/protein monomer = (63.3077 - 61.7692) /30 = 0.0513", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 128": { + "description": "Plots 0.0256 Zn per protein monomer at 9 PMB equivalents (acceptable value is 0.0256) for the R0S mutant line.", + "justification": "Plotting the Zinc_binding_values.xlsx to generate the linear regression curve yields y = 0.0013x + 0.0017. Rearrange the equation to solve for zinc conc. (uM), x = [(y - 0.0017) / 0.0013]. Use the provided absorbance value to solve for the respective zinc concentrations, x. Normalize each zinc concentration to the respective 0 uM Zn conc, and then calculate the Zinc/protein monomer by dividing by 30. \nx = [(y - 0.0017) / 0.0013]; Zn/protein monomer = (x - x_0uM) /30. \nx = [(0.083 - 0.0017) / 0.0013] = 62.5385; Zn/protein monomer = (62.5385 - 61.7692) /30 = 0.0256", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + } +} \ No newline at end of file diff --git a/tasks/task_5a0212833c224c85b79960604679eb84/input/Evidence_Reporting_Standard.docx b/tasks/task_5a0212833c224c85b79960604679eb84/input/Evidence_Reporting_Standard.docx new file mode 100644 index 0000000000000000000000000000000000000000..660c4b654e62217489449c2547fedd0866cf85bd --- /dev/null +++ b/tasks/task_5a0212833c224c85b79960604679eb84/input/Evidence_Reporting_Standard.docx @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e565226d6fc9edc06402a16a7d65e2df8aeaaf7336029d40692fc2e37b4aefd6 +size 10299 diff --git a/tasks/task_5a0212833c224c85b79960604679eb84/input/Housing_and_Work_Databook.xlsx b/tasks/task_5a0212833c224c85b79960604679eb84/input/Housing_and_Work_Databook.xlsx new file mode 100644 index 0000000000000000000000000000000000000000..8b99e5bd99bade52cd6947b9de91e94cd9a2db16 --- /dev/null +++ b/tasks/task_5a0212833c224c85b79960604679eb84/input/Housing_and_Work_Databook.xlsx @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b0e07fcb619269bcff6245ec3b2051729341abf3daa98c91314d28dc232165f1 +size 2239152 diff --git a/tasks/task_5a0212833c224c85b79960604679eb84/input/Retirement_Income_Chartbook.pptx b/tasks/task_5a0212833c224c85b79960604679eb84/input/Retirement_Income_Chartbook.pptx new file mode 100644 index 0000000000000000000000000000000000000000..1c1acd412e72240e2368828d010e026b35280710 --- /dev/null +++ b/tasks/task_5a0212833c224c85b79960604679eb84/input/Retirement_Income_Chartbook.pptx @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:29f3b0d21b14945bc3898c291aa470bd0ab4850fcaef947c1006ec5db5bb2dfe +size 1369322 diff --git a/tasks/task_5a0212833c224c85b79960604679eb84/input/formatting_aesthetics_template.pptx b/tasks/task_5a0212833c224c85b79960604679eb84/input/formatting_aesthetics_template.pptx new file mode 100644 index 0000000000000000000000000000000000000000..b3021122e5859487a6e554b300cf95f8fc125943 --- /dev/null +++ b/tasks/task_5a0212833c224c85b79960604679eb84/input/formatting_aesthetics_template.pptx @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:13c2753b3fd84686f1bc014a4dd332b796cae7f604f7217ee30920776caeae49 +size 22273 diff --git a/tasks/task_5a0212833c224c85b79960604679eb84/metadata.json b/tasks/task_5a0212833c224c85b79960604679eb84/metadata.json new file mode 100644 index 0000000000000000000000000000000000000000..bb8e48ad319d76aea8baeb7ae55f93aa936d5b8c --- /dev/null +++ b/tasks/task_5a0212833c224c85b79960604679eb84/metadata.json @@ -0,0 +1,12 @@ +{ + "TaskID": "task_5a0212833c224c85b79960604679eb84", + "Vertical": "Law & Government", + "Domain": "Government Backoffice", + "Role": "Policy analyst", + "Task Goal": "Present the financial, housing and employment position of older adults after retirement for an internal policy team.", + "Prompt": "Create a six-slide PowerPoint deck for an internal public health policy team on the financial, housing and employment position of older Canadians after retirement. Follow the attached template and evidence reporting standard, use the attached plates, build every chart as an editable PowerPoint chart with data labels and save the deck as post_retirement_financial_housing_employment_status_of_older_adults.pptx.\nSlide 1 is the title page. Slide 2 charts 2020 pension receipt by racialized status, disability and education and names the dimension with the widest receipt gap, its size and how far it exceeds the narrowest gap. Slide 3 charts core housing need in four panels with one identical value axis, for people aged 65 and older by gender and for immigrants, visible minorities and Indigenous people against their reference populations at all ages; it gives the change in each gap between successive years, states whether each gap narrowed in each successive year and names which of the three population groups shows the gap that closed least and gives the change in that gap from 2006 to 2021. Slide 4 charts working after retirement by gender for 2016 and 2023 as columns with the gender gap as a line on a secondary axis and gives the change in the gap, charts the 2023 class of worker of the previously retired, gives the widest gap between the three family debt tiers and names the provinces that differ from Ontario. It also tabulates the predicted probabilities for all ten characteristics across the three regression models under one merged model header, shades cells only when their plate markers are filled and their predicted probabilities are at least 10.0%, marks untested cells n/a, explains both shading conditions in a table note, and names the characteristics meeting both conditions in every model that tests them. Slide 5 charts the main reasons for retiring by gender and names the reasons for which the women's share is higher than the men's, charts the average retirement age by reason for 2023 and 2025; it ranks the reasons by 2023 age and gives the share-weighted average age for 2025. Slide 6 lists the sources in APA style with hanging indents and italic titles, naming the slides that use each.\nGive each chart a numbered note line with a superscript marker that cites its source. Cite every claim, spell out acronyms at first use, avoid causal wording and report changes as signed values.", + "Input_files": "Evidence_Reporting_Standard.docx, Housing_and_Work_Databook.xlsx, Retirement_Income_Chartbook.pptx, formatting_aesthetics_template.pptx", + "All Task Files": "tasks/task_5a0212833c224c85b79960604679eb84/input/", + "Rubric Criteria": "tasks/task_5a0212833c224c85b79960604679eb84/rubrics.json", + "Economic Rationale": "This task converts three separate Statistics Canada sources into a concise, presentation-ready briefing for internal policy use. Preparing the charts, reconciling population scopes and definitions, checking source limitations, and formatting the deck would reasonably require about 4 to 6 hours of senior analyst time; at an estimated fully loaded labor cost of $75 to $100 per hour. The deliverable also reduces review and rework risk by presenting the indicators with consistent source attribution and clearly separated older-adult and broader-population comparisons, supporting faster policy discussions and briefing preparation." +} diff --git a/tasks/task_5a0212833c224c85b79960604679eb84/rubrics.json b/tasks/task_5a0212833c224c85b79960604679eb84/rubrics.json new file mode 100644 index 0000000000000000000000000000000000000000..28b073ba7538108e409dedaba4e4e694056b8079 --- /dev/null +++ b/tasks/task_5a0212833c224c85b79960604679eb84/rubrics.json @@ -0,0 +1,1208 @@ +{ + "criterion 1": { + "description": "Produces a PowerPoint file named \"post_retirement_financial_housing_employment_status_of_older_adults.pptx\".", + "justification": "Per the prompt: \"save the deck as post_retirement_financial_housing_employment_status_of_older_adults.pptx\".", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 2": { + "description": "Produces a deck that contains six slides.", + "justification": "Per the prompt opening: \"Create a six-slide PowerPoint deck for an internal public health policy team on the financial, housing and employment position of older Canadians after retirement.\" The prompt then specifies Slide 1 to Slide 6, so the deck holds six slides.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 3": { + "description": "Names the deck subject on slide 1 as the financial, housing and employment position of older Canadians after retirement.", + "justification": "Per the prompt: \"Create a six-slide PowerPoint deck for an internal public health policy team on the financial, housing and employment position of older Canadians after retirement.\" Slide 1 is the title page, so the subject appears there.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 4": { + "description": "Names the intended audience on slide 1 as an internal public health policy team.", + "justification": "Per the prompt: \"for an internal public health policy team\". formatting_aesthetics_template.pptx, slide 1, places an audience line on its title page.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 5": { + "description": "Presents 2020 pension receipt on slide 2 as a native editable PowerPoint chart with one plotted receipt value for each of six groups: racialized group, non-racialized group, have had a disability, no disability, high school or less, and postsecondary graduate.", + "justification": "The prompt requires a chart of 2020 pension receipt by racialized status, disability and education, but specifies no chart type. Source: Retirement_Income_Chartbook.pptx, slide 3, Plate 2, panel A. A native chart that displays the six required values satisfies this structural criterion; the numerical values are checked separately.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 6": { + "description": "Plots the 2020 receipt of the racialized group and of the non-racialized group in the native slide 2 chart as 32.8 and 53.8 percent (acceptable ranges 32.3 to 33.3 and 53.3 to 54.3).", + "justification": "Per the prompt: \"Slide 2 charts 2020 pension receipt by racialized status, disability and education and names the dimension with the widest receipt gap, its size and how far it exceeds the narrowest gap.\" Retirement_Income_Chartbook.pptx, slide 3 (Plate 2), panel A: the received shares end at 32.8 and 53.8 on an axis with gridlines every 1 point, so each read carries 0.5. The prompt asks for receipt by racialized status, so both racialized-status bars are charted; the racialized estimate is hatched and marked M and stays out of comparisons (Evidence_Reporting_Standard.docx, footnote 5), which does not remove it from the chart. Only the values of the native, editable PowerPoint chart count; a value written only in a sentence or a table, or shown in a picture of a chart, does not.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 7": { + "description": "Plots the 2020 receipt of the group that has had a disability and of the group with no disability in the native slide 2 chart as 44.2 and 54.7 percent (acceptable ranges 43.7 to 44.7 and 54.2 to 55.2).", + "justification": "Per the prompt: \"Slide 2 charts 2020 pension receipt by racialized status, disability and education and names the dimension with the widest receipt gap, its size and how far it exceeds the narrowest gap.\" Retirement_Income_Chartbook.pptx, slide 3 (Plate 2), panel A: the received shares end at 44.2 and 54.7 on an axis with gridlines every 1 point, so each read carries 0.5. Only the values of the native, editable PowerPoint chart count; a value written only in a sentence or a table, or shown in a picture of a chart, does not.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 8": { + "description": "Plots the 2020 receipt of the high school or less group and of the postsecondary graduate group in the native slide 2 chart as 41.2 and 58.0 percent (acceptable ranges 40.7 to 41.7 and 57.5 to 58.5).", + "justification": "Per the prompt: \"Slide 2 charts 2020 pension receipt by racialized status, disability and education and names the dimension with the widest receipt gap, its size and how far it exceeds the narrowest gap.\" Retirement_Income_Chartbook.pptx, slide 3 (Plate 2), panel A: the received shares end at 41.2 and 58.0 on an axis with gridlines every 1 point, so each read carries 0.5. Only the values of the native, editable PowerPoint chart count; a value written only in a sentence or a table, or shown in a picture of a chart, does not.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 9": { + "description": "States on slide 2 that the racialized-group receipt estimate, marked M, is left out of the comparison of dimensions.", + "justification": "The plate marks the racialized estimate with a hatched segment carrying the letter M in panel A of Retirement_Income_Chartbook.pptx, slide 3 (Plate 2); the hatched bar sits in the racialized group row. Evidence_Reporting_Standard.docx, footnote 5, sets the rule: M estimates are shown, are not used in comparisons, and the M estimate is named as unused. The prompt asks the deck to follow the evidence reporting standard. Source: Retirement_Income_Chartbook.pptx, slide 3 (Plate 2), panel A. A plotted value or data label alone does not satisfy this check; the deck has to write the name, description or rank in a sentence, list line or table cell.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 4, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 10": { + "description": "Names education as the dimension with the widest 2020 pension receipt gap, together with its two groups, postsecondary graduate and high school or less.", + "justification": "Per the prompt: \"Slide 2 charts 2020 pension receipt by racialized status, disability and education and names the dimension with the widest receipt gap, its size and how far it exceeds the narrowest gap.\" Gaps: education 58.0 - 41.2 = 16.8; disability 54.7 - 44.2 = 10.5; racialized 53.8 - 32.8 = 21.0. The racialized estimate carries the letter M in the plate. Evidence_Reporting_Standard.docx, footnote 5, states that M estimates are shown but not used in gaps, comparisons or rankings, and that a dimension containing an M estimate is left out of any comparison of dimensions. The comparison therefore runs between education and disability, and education is widest. Source: Retirement_Income_Chartbook.pptx, slide 3 (Plate 2), panel A. A plotted value or data label alone does not satisfy this check; the deck has to write the name, description or rank in a sentence, list line or table cell.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 5, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 11": { + "description": "States the widest 2020 receipt gap as 16.8 percentage points (acceptable range 15.8 to 17.8).", + "justification": "Per the prompt: \"Slide 2 charts 2020 pension receipt by racialized status, disability and education and names the dimension with the widest receipt gap, its size and how far it exceeds the narrowest gap.\" Gap = 58.0 - 41.2 = 16.8. Tolerance 1.0 from two reads at 0.5. The racialized gap of 21.0 is outside the range. Source: Retirement_Income_Chartbook.pptx, slide 3 (Plate 2), panel A. A value shown as a chart data label, a table cell or a sentence counts as stated.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 12": { + "description": "States that the widest receipt gap exceeds the narrowest receipt gap by 6.3 percentage points (acceptable range 4.3 to 8.3).", + "justification": "Per the prompt: \"Slide 2 charts 2020 pension receipt by racialized status, disability and education and names the dimension with the widest receipt gap, its size and how far it exceeds the narrowest gap.\" Widest 16.8 (education) minus narrowest 10.5 (disability) = 6.3. Tolerance 2.0 from four reads at 0.5: each gap is the difference of two chart reads, and the spread is the difference of the two gaps. With the racialized estimate included the spread would be 21.0 - 10.5 = 10.5, outside the range; Evidence_Reporting_Standard.docx, footnote 5, leaves it out. Source: Retirement_Income_Chartbook.pptx, slide 3 (Plate 2), panel A. A value shown as a chart data label, a table cell or a sentence counts as stated.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 13": { + "description": "Presents core housing need on slide 3 as four native charts: people aged 65 and older by gender, immigrants against non-immigrants, visible minorities against not a visible minority, and Indigenous identity against non-Indigenous identity.", + "justification": "Per the prompt: \"Slide 3 charts core housing need in four panels with one identical value axis, for people aged 65 and older by gender and for immigrants, visible minorities and Indigenous people against their reference populations at all ages; it gives the change in each gap between successive years, states whether each gap narrowed in each successive year and names which of the three population groups shows the gap that closed least and gives the change in that gap from 2006 to 2021.\" Source plates: Housing_and_Work_Databook.xlsx, sheets Housing_65_Plus and Housing_Groups (first three panels). The fourth panel of the sheet (immigrant subgroups) is not one of the requested comparisons.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 14": { + "description": "Gives the four slide 3 charts the same value-axis range and gridline interval, so that the four plot areas show the same scale.", + "justification": "Per the prompt: \"Slide 3 charts core housing need in four panels with one identical value axis, for people aged 65 and older by gender and for immigrants, visible minorities and Indigenous people against their reference populations at all ages; it gives the change in each gap between successive years, states whether each gap narrowed in each successive year and names which of the three population groups shows the gap that closed least and gives the change in that gap from 2006 to 2021.\" The phrase \"one identical value axis\" is the requirement. The check reads the rendered axes: identical range and gridline spacing in all four charts.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 15": { + "description": "Plots the Women+ series of the native slide 3 gender chart as three census-year points, 14.0 for 2006, 12.9 for 2016 and 10.5 for 2021 (acceptable ranges 13.85 to 14.15, 12.75 to 13.05 and 10.35 to 10.65).", + "justification": "Per the prompt: \"Slide 3 charts core housing need in four panels with one identical value axis, for people aged 65 and older by gender and for immigrants, visible minorities and Indigenous people against their reference populations at all ages; it gives the change in each gap between successive years, states whether each gap narrowed in each successive year and names which of the three population groups shows the gap that closed least and gives the change in that gap from 2006 to 2021.\" Housing_and_Work_Databook.xlsx, sheet Housing_65_Plus (Plate 1), shows 14.0, 13.1, 12.9 and 10.5 for 2006, 2011, 2016 and 2021 on an axis with gridlines every 0.5 points, so each read carries 0.15; the 2011 marker is hollow and the legend names it the National Household Survey (voluntary). Evidence_Reporting_Standard.docx, footnote 9: the 2011 values are shown in the plate and left out of deck charts, which use the census years 2006, 2016 and 2021 only. A series with a fourth point for 2011 fails. Only the values of the native, editable PowerPoint chart count; a value written only in a sentence or a table, or shown in a picture of a chart, does not.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 16": { + "description": "Plots the Men+ series of the native slide 3 gender chart as three census-year points, 7.4 for 2006, 8.2 for 2016 and 7.1 for 2021 (acceptable ranges 7.25 to 7.55, 8.05 to 8.35 and 6.95 to 7.25).", + "justification": "Per the prompt: \"Slide 3 charts core housing need in four panels with one identical value axis, for people aged 65 and older by gender and for immigrants, visible minorities and Indigenous people against their reference populations at all ages; it gives the change in each gap between successive years, states whether each gap narrowed in each successive year and names which of the three population groups shows the gap that closed least and gives the change in that gap from 2006 to 2021.\" Housing_and_Work_Databook.xlsx, sheet Housing_65_Plus (Plate 1), shows 7.4, 7.3, 8.2 and 7.1 for 2006, 2011, 2016 and 2021 on an axis with gridlines every 0.5 points, so each read carries 0.15; the 2011 marker is hollow and the legend names it the National Household Survey (voluntary). Evidence_Reporting_Standard.docx, footnote 9: the 2011 values are shown in the plate and left out of deck charts, which use the census years 2006, 2016 and 2021 only. A series with a fourth point for 2011 fails. Only the values of the native, editable PowerPoint chart count; a value written only in a sentence or a table, or shown in a picture of a chart, does not.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 17": { + "description": "Plots the immigrant series of the native slide 3 immigrant chart as three census-year points, 17.1 for 2006, 15.7 for 2016 and 10.7 for 2021 (acceptable ranges 16.95 to 17.25, 15.55 to 15.85 and 10.55 to 10.85).", + "justification": "Per the prompt: \"Slide 3 charts core housing need in four panels with one identical value axis, for people aged 65 and older by gender and for immigrants, visible minorities and Indigenous people against their reference populations at all ages; it gives the change in each gap between successive years, states whether each gap narrowed in each successive year and names which of the three population groups shows the gap that closed least and gives the change in that gap from 2006 to 2021.\" Housing_and_Work_Databook.xlsx, sheet Housing_Groups (Plate 2), shows 17.1, 15.4, 15.7 and 10.7 for 2006, 2011, 2016 and 2021 on an axis with gridlines every 0.5 points, so each read carries 0.15; the 2011 marker is hollow and the legend names it the National Household Survey (voluntary). Evidence_Reporting_Standard.docx, footnote 9: the 2011 values are shown in the plate and left out of deck charts, which use the census years 2006, 2016 and 2021 only. A series with a fourth point for 2011 fails. Only the values of the native, editable PowerPoint chart count; a value written only in a sentence or a table, or shown in a picture of a chart, does not.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 18": { + "description": "Plots the non-immigrant series of the native slide 3 immigrant chart as three census-year points, 9.2 for 2006, 9.1 for 2016 and 6.4 for 2021 (acceptable ranges 9.05 to 9.35, 8.95 to 9.25 and 6.25 to 6.55).", + "justification": "Per the prompt: \"Slide 3 charts core housing need in four panels with one identical value axis, for people aged 65 and older by gender and for immigrants, visible minorities and Indigenous people against their reference populations at all ages; it gives the change in each gap between successive years, states whether each gap narrowed in each successive year and names which of the three population groups shows the gap that closed least and gives the change in that gap from 2006 to 2021.\" Housing_and_Work_Databook.xlsx, sheet Housing_Groups (Plate 2), shows 9.2, 9.3, 9.1 and 6.4 for 2006, 2011, 2016 and 2021 on an axis with gridlines every 0.5 points, so each read carries 0.15; the 2011 marker is hollow and the legend names it the National Household Survey (voluntary). Evidence_Reporting_Standard.docx, footnote 9: the 2011 values are shown in the plate and left out of deck charts, which use the census years 2006, 2016 and 2021 only. A series with a fourth point for 2011 fails. Only the values of the native, editable PowerPoint chart count; a value written only in a sentence or a table, or shown in a picture of a chart, does not.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 19": { + "description": "Plots the visible minority series of the native slide 3 visible minority chart as three census-year points, 21.4 for 2006, 17.8 for 2016 and 11.3 for 2021 (acceptable ranges 21.25 to 21.55, 17.65 to 17.95 and 11.15 to 11.45).", + "justification": "Per the prompt: \"Slide 3 charts core housing need in four panels with one identical value axis, for people aged 65 and older by gender and for immigrants, visible minorities and Indigenous people against their reference populations at all ages; it gives the change in each gap between successive years, states whether each gap narrowed in each successive year and names which of the three population groups shows the gap that closed least and gives the change in that gap from 2006 to 2021.\" Housing_and_Work_Databook.xlsx, sheet Housing_Groups (Plate 2), shows 21.4, 18.3, 17.8 and 11.3 for 2006, 2011, 2016 and 2021 on an axis with gridlines every 0.5 points, so each read carries 0.15; the 2011 marker is hollow and the legend names it the National Household Survey (voluntary). Evidence_Reporting_Standard.docx, footnote 9: the 2011 values are shown in the plate and left out of deck charts, which use the census years 2006, 2016 and 2021 only. A series with a fourth point for 2011 fails. Only the values of the native, editable PowerPoint chart count; a value written only in a sentence or a table, or shown in a picture of a chart, does not.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 20": { + "description": "Plots the not a visible minority series of the native slide 3 visible minority chart as three census-year points, 8.8 for 2006, 8.6 for 2016 and 6.3 for 2021 (acceptable ranges 8.65 to 8.95, 8.45 to 8.75 and 6.15 to 6.45).", + "justification": "Per the prompt: \"Slide 3 charts core housing need in four panels with one identical value axis, for people aged 65 and older by gender and for immigrants, visible minorities and Indigenous people against their reference populations at all ages; it gives the change in each gap between successive years, states whether each gap narrowed in each successive year and names which of the three population groups shows the gap that closed least and gives the change in that gap from 2006 to 2021.\" Housing_and_Work_Databook.xlsx, sheet Housing_Groups (Plate 2), shows 8.8, 8.8, 8.6 and 6.3 for 2006, 2011, 2016 and 2021 on an axis with gridlines every 0.5 points, so each read carries 0.15; the 2011 marker is hollow and the legend names it the National Household Survey (voluntary). Evidence_Reporting_Standard.docx, footnote 9: the 2011 values are shown in the plate and left out of deck charts, which use the census years 2006, 2016 and 2021 only. A series with a fourth point for 2011 fails. Only the values of the native, editable PowerPoint chart count; a value written only in a sentence or a table, or shown in a picture of a chart, does not.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 21": { + "description": "Plots the Indigenous identity series of the native slide 3 Indigenous chart as three census-year points, 22.7 for 2006, 19.8 for 2016 and 13.2 for 2021 (acceptable ranges 22.55 to 22.85, 19.65 to 19.95 and 13.05 to 13.35).", + "justification": "Per the prompt: \"Slide 3 charts core housing need in four panels with one identical value axis, for people aged 65 and older by gender and for immigrants, visible minorities and Indigenous people against their reference populations at all ages; it gives the change in each gap between successive years, states whether each gap narrowed in each successive year and names which of the three population groups shows the gap that closed least and gives the change in that gap from 2006 to 2021.\" Housing_and_Work_Databook.xlsx, sheet Housing_Groups (Plate 2), shows 22.7, 21.0, 19.8 and 13.2 for 2006, 2011, 2016 and 2021 on an axis with gridlines every 0.5 points, so each read carries 0.15; the 2011 marker is hollow and the legend names it the National Household Survey (voluntary). Evidence_Reporting_Standard.docx, footnote 9: the 2011 values are shown in the plate and left out of deck charts, which use the census years 2006, 2016 and 2021 only. A series with a fourth point for 2011 fails. Only the values of the native, editable PowerPoint chart count; a value written only in a sentence or a table, or shown in a picture of a chart, does not.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 22": { + "description": "Plots the non-Indigenous identity series of the native slide 3 Indigenous chart as three census-year points, 10.5 for 2006, 10.3 for 2016 and 7.4 for 2021 (acceptable ranges 10.35 to 10.65, 10.15 to 10.45 and 7.25 to 7.55).", + "justification": "Per the prompt: \"Slide 3 charts core housing need in four panels with one identical value axis, for people aged 65 and older by gender and for immigrants, visible minorities and Indigenous people against their reference populations at all ages; it gives the change in each gap between successive years, states whether each gap narrowed in each successive year and names which of the three population groups shows the gap that closed least and gives the change in that gap from 2006 to 2021.\" Housing_and_Work_Databook.xlsx, sheet Housing_Groups (Plate 2), shows 10.5, 10.3, 10.3 and 7.4 for 2006, 2011, 2016 and 2021 on an axis with gridlines every 0.5 points, so each read carries 0.15; the 2011 marker is hollow and the legend names it the National Household Survey (voluntary). Evidence_Reporting_Standard.docx, footnote 9: the 2011 values are shown in the plate and left out of deck charts, which use the census years 2006, 2016 and 2021 only. A series with a fourth point for 2011 fails. Only the values of the native, editable PowerPoint chart count; a value written only in a sentence or a table, or shown in a picture of a chart, does not.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 23": { + "description": "States that the trend judgments on slide 3 compare the census years 2006, 2016 and 2021 and that the 2011 National Household Survey (NHS) values are left out.", + "justification": "The plates mark 2011 with a hollow marker and the legend \"2011: National Household Survey (voluntary)\". Evidence_Reporting_Standard.docx, footnote 9, states that 2011 values are shown in the plate and left out of deck charts, of trend judgments and of changes between years, which use 2006, 2016 and 2021 only, and that the deck states that the 2011 values were left out. The prompt asks the deck to follow the standard and to state whether each gap narrowed in each successive year. Source: Housing_and_Work_Databook.xlsx, sheets Housing_65_Plus (Plate 1, Women+ and Men+ aged 65 and older) and Housing_Groups (Plate 2, population groups at all ages). A plotted value or data label alone does not satisfy this check; the deck has to write the name, description or rank in a sentence, list line or table cell.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 4, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 24": { + "description": "Describes the gap between Women+ and Men+ aged 65 and older, the visible minority gap and the Indigenous identity gap on slide 3 as narrowing in each successive census year.", + "justification": "Sources: Housing_and_Work_Databook.xlsx, Housing_65_Plus, Plate 1, Women+ and Men+ aged 65 and older; and Housing_Groups, Plate 2, visible-minority and Indigenous-identity groups at all ages with their reference populations. Census-year gaps for 2006, 2016 and 2021 are 6.6, 4.7, 3.4 for gender; 12.6, 9.2, 5.0 for visible minorities; and 12.2, 9.5, 5.8 for Indigenous identity. Each underlying reading allows \u00b10.15 percentage points, each gap \u00b10.30, and each change between two gaps \u00b10.60. The smallest central decline is 1.3 points, so every interval remains a decline throughout the accepted bounds. Evidence_Reporting_Standard.docx, section 4 and footnote 9, defines narrowing on the census years and excludes 2011 NHS values. The deliverable states the trend conclusion; equivalent wording is accepted.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 25": { + "description": "Describes the immigrant gap on slide 3 as narrowing in each successive census year, from 2006 to 2016 and from 2016 to 2021.", + "justification": "Source: Housing_and_Work_Databook.xlsx, Housing_Groups, Plate 2, immigrant and non-immigrant series at all ages. Census-year gaps are 17.1 - 9.2 = 7.9 in 2006, 15.7 - 9.1 = 6.6 in 2016, and 10.7 - 6.4 = 4.3 in 2021. Changes are -1.3 and -2.3 percentage points. Each source reading allows \u00b10.15, each gap \u00b10.30, and each four-read change \u00b10.60. Even the smallest decline remains at least 0.70 points, so narrowing is stable. Evidence_Reporting_Standard.docx, section 4 and footnote 9, uses census years only; the hollow 2011 NHS markers are excluded. The deliverable states the trend conclusion; equivalent wording is accepted.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 26": { + "description": "States the change in the immigrant gap from 2006 to 2021 as -3.6 percentage points (acceptable range -4.2 to -3.0).", + "justification": "Source: Housing_and_Work_Databook.xlsx, worksheet Housing_Groups (Plate 2). Readings for 2006, 2016 and 2021 are immigrants 17.1, 15.7, 10.7 and non-immigrants 9.2, 9.1, 6.4; the resulting group-minus-reference gaps are 7.9, 6.6 and 4.3 percentage points. Each source reading allows \u00b10.15 percentage points. A difference between two gaps uses four readings, so its bounded tolerance is \u00b10.60 percentage points. The 2006\u20132021 change is 4.3 - 7.9 = -3.6, with accepted bounds -4.2 to -3.0. Evidence_Reporting_Standard.docx, sections 2\u20134 and footnotes 3, 4 and 9, requires signed changes, the named reference groups, annualisation over more than four years and census years only. A value in a chart data label, table cell or sentence counts as stated. Grade the reported outcome, rather than requiring a displayed calculation.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 27": { + "description": "Names immigrants as the group whose gap in core housing need closed least between 2006 and 2021, among immigrants, visible minorities and Indigenous people.", + "justification": "Source: Housing_and_Work_Databook.xlsx, Housing_Groups, Plate 2, immigrant, visible-minority and Indigenous-identity series against their whole-population reference groups. Their 2006\u20132021 gap changes are -3.6, -7.6 and -6.4 percentage points. Four readings at \u00b10.15 give \u00b10.60 for each change: -4.2 to -3.0, -8.2 to -7.0 and -7.0 to -5.8, respectively. Immigrants therefore have the smallest closure throughout the accepted bounds. The comparison covers these three population groups at all ages, as the prompt requests; it excludes the separate age-65-plus gender panel. A value in a chart data label, table cell or sentence counts as stated. Grade the reported outcome, rather than requiring a displayed calculation.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 5, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 28": { + "description": "States the change in the gap between Women+ and Men+ aged 65 and older from 2006 to 2021 as -3.2 percentage points (acceptable range -3.8 to -2.6).", + "justification": "Source: Housing_and_Work_Databook.xlsx, worksheet Housing_65_Plus (Plate 1). Readings for 2006, 2016 and 2021 are Women+ 14.0, 12.9, 10.5 and Men+ 7.4, 8.2, 7.1; the resulting group-minus-reference gaps are 6.6, 4.7 and 3.4 percentage points. Each source reading allows \u00b10.15 percentage points. A difference between two gaps uses four readings, so its bounded tolerance is \u00b10.60 percentage points. The 2006\u20132021 change is 3.4 - 6.6 = -3.2, with accepted bounds -3.8 to -2.6. Evidence_Reporting_Standard.docx, sections 2\u20134 and footnotes 3, 4 and 9, requires signed changes, the named reference groups, annualisation over more than four years and census years only. A value in a chart data label, table cell or sentence counts as stated. Grade the reported outcome, rather than requiring a displayed calculation.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 29": { + "description": "States the change in the visible minority gap from 2006 to 2021 as -7.6 percentage points (acceptable range -8.2 to -7.0).", + "justification": "Source: Housing_and_Work_Databook.xlsx, worksheet Housing_Groups (Plate 2). Readings for 2006, 2016 and 2021 are visible minorities 21.4, 17.8, 11.3 and not a visible minority 8.8, 8.6, 6.3; the resulting group-minus-reference gaps are 12.6, 9.2 and 5.0 percentage points. Each source reading allows \u00b10.15 percentage points. A difference between two gaps uses four readings, so its bounded tolerance is \u00b10.60 percentage points. The 2006\u20132021 change is 5.0 - 12.6 = -7.6, with accepted bounds -8.2 to -7.0. ", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 30": { + "description": "States the change in the Indigenous identity gap from 2006 to 2021 as -6.4 percentage points (acceptable range -7.0 to -5.8).", + "justification": "Source: Housing_and_Work_Databook.xlsx, worksheet Housing_Groups (Plate 2). Readings for 2006, 2016 and 2021 are Indigenous identity 22.7, 19.8, 13.2 and non-Indigenous identity 10.5, 10.3, 7.4; the resulting group-minus-reference gaps are 12.2, 9.5 and 5.8 percentage points. Each source reading allows \u00b10.15 percentage points. A difference between two gaps uses four readings, so its bounded tolerance is \u00b10.60 percentage points. The 2006-2021 change is 5.8 - 12.2 = -6.4, with accepted bounds -7.0 to -5.8. Evidence_Reporting_Standard.docx, sections 2-4 and footnotes 3, 4 and 9, requires signed changes, the named reference groups, annualisation over more than four years and census years only. A value in a chart data label, table cell or sentence counts as stated. Grade the reported outcome, rather than requiring a displayed calculation.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 31": { + "description": "States the change in the gap between Women+ and Men+ aged 65 and older as \u22121.9 percentage points from 2006 to 2016 and \u22121.3 percentage points from 2016 to 2021 (acceptable ranges \u22122.5 to \u22121.3 and \u22121.9 to \u22120.7, respectively).", + "justification": "Source: Housing_and_Work_Databook.xlsx, Housing_65_Plus, Plate 1, Women+ and Men+ series. The Women+ minus Men+ gaps are 6.6, 4.7 and 3.4 percentage points in 2006, 2016 and 2021. The successive changes are 4.7 \u2212 6.6 = \u22121.9 and 3.4 \u2212 4.7 = \u22121.3. Each change uses four source readings, each accepted within \u00b10.15 percentage points, giving a bounded tolerance of \u00b10.60. The resulting ranges are \u22122.5 to \u22121.3 and \u22121.9 to \u22120.7. Evidence_Reporting_Standard.docx, footnote 9, excludes 2011 NHS values. Grade the reported signed results.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 32": { + "description": "States the change in the immigrant gap as -1.3 percentage points from 2006 to 2016 and -2.3 percentage points from 2016 to 2021 (acceptable ranges -1.9 to -0.7 and -2.9 to -1.7).", + "justification": "Source: Housing_and_Work_Databook.xlsx, worksheet Housing_Groups (Plate 2). Readings for 2006, 2016 and 2021 are immigrants 17.1, 15.7, 10.7 and non-immigrants 9.2, 9.1, 6.4; the resulting group-minus-reference gaps are 7.9, 6.6 and 4.3 percentage points. Each source reading allows \u00b10.15 percentage points. A difference between two gaps uses four readings, so its bounded tolerance is \u00b10.60 percentage points. The 2006-2016 change is -1.3 and the 2016-2021 change is -2.3; each allows \u00b10.60. Evidence_Reporting_Standard.docx, sections 2-4 and footnotes 3, 4 and 9, requires signed changes, the named reference groups, annualisation over more than four years and census years only. A value in a chart data label, table cell or sentence counts as stated. Grade the reported outcome, rather than requiring a displayed calculation.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 33": { + "description": "States the change in the visible minority gap as -3.4 percentage points from 2006 to 2016 and -4.2 percentage points from 2016 to 2021 (acceptable ranges -4.0 to -2.8 and -4.8 to -3.6).", + "justification": "Source: Housing_and_Work_Databook.xlsx, worksheet Housing_Groups (Plate 2). Readings for 2006, 2016 and 2021 are visible minorities 21.4, 17.8, 11.3 and not a visible minority 8.8, 8.6, 6.3; the resulting group-minus-reference gaps are 12.6, 9.2 and 5.0 percentage points. Each source reading allows \u00b10.15 percentage points. A difference between two gaps uses four readings, so its bounded tolerance is \u00b10.60 percentage points. The 2006-2016 change is -3.4 and the 2016-2021 change is -4.2; each allows \u00b10.60. Evidence_Reporting_Standard.docx, sections 2-4 and footnotes 3, 4 and 9, requires signed changes, the named reference groups, annualisation over more than four years and census years only. A value in a chart data label, table cell or sentence counts as stated. Grade the reported outcome, rather than requiring a displayed calculation.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 34": { + "description": "States the change in the Indigenous identity gap as -2.7 percentage points from 2006 to 2016 and -3.7 percentage points from 2016 to 2021 (acceptable ranges -3.3 to -2.1 and -4.3 to -3.1).", + "justification": "Source: Housing_and_Work_Databook.xlsx, worksheet Housing_Groups (Plate 2). Readings for 2006, 2016 and 2021 are Indigenous identity 22.7, 19.8, 13.2 and non-Indigenous identity 10.5, 10.3, 7.4; the resulting group-minus-reference gaps are 12.2, 9.5 and 5.8 percentage points. Each source reading allows \u00b10.15 percentage points. A difference between two gaps uses four readings, so its bounded tolerance is \u00b10.60 percentage points. The 2006-2016 change is -2.7 and the 2016-2021 change is -3.7; each allows \u00b10.60. Evidence_Reporting_Standard.docx, sections 2-4 and footnotes 3, 4 and 9, requires signed changes, the named reference groups, annualisation over more than four years and census years only. A value in a chart data label, table cell or sentence counts as stated. Grade the reported outcome, rather than requiring a displayed calculation.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 35": { + "description": "States the change in the immigrant gap from 2006 to 2021 as -0.24 percentage points per year (acceptable range -0.28 to -0.20).", + "justification": "Source: Housing_and_Work_Databook.xlsx, worksheet Housing_Groups (Plate 2). Readings for 2006, 2016 and 2021 are immigrants 17.1, 15.7, 10.7 and non-immigrants 9.2, 9.1, 6.4; the resulting group-minus-reference gaps are 7.9, 6.6 and 4.3 percentage points. Each source reading allows \u00b10.15 percentage points. A difference between two gaps uses four readings, so its bounded tolerance is \u00b10.60 percentage points. The 2006-2021 change is 4.3 - 7.9 = -3.6, with accepted bounds -4.2 to -3.0. Dividing the unrounded change bounds by 15 years and rounding once to two decimals gives -0.28 to -0.20 percentage points per year. Evidence_Reporting_Standard.docx, sections 2-4 and footnotes 3, 4 and 9, requires signed changes, the named reference groups, annualisation over more than four years and census years only. A value in a chart data label, table cell or sentence counts as stated. Grade the reported outcome, rather than requiring a displayed calculation.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 36": { + "description": "States the per-year change in the gap between Women+ and Men+ aged 65 and older as -0.19 percentage points per year from 2006 to 2016 and -0.26 percentage points per year from 2016 to 2021 (acceptable ranges -0.25 to -0.13 and -0.38 to -0.14).", + "justification": "Source: Housing_and_Work_Databook.xlsx, worksheet Housing_65_Plus (Plate 1). Readings for 2006, 2016 and 2021 are Women+ 14.0, 12.9, 10.5 and Men+ 7.4, 8.2, 7.1; the resulting group-minus-reference gaps are 6.6, 4.7 and 3.4 percentage points. Each source reading allows \u00b10.15 percentage points. A difference between two gaps uses four readings, so its bounded tolerance is \u00b10.60 percentage points. The 2006-2016 change is -1.9 and the 2016-2021 change is -1.3; each allows \u00b10.60. Divide the first change bounds by 10 years and the second by 5 years, then round once to two decimals. The annual ranges are -0.25 to -0.13 and -0.38 to -0.14. Evidence_Reporting_Standard.docx, sections 2-4 and footnotes 3, 4 and 9, requires signed changes, the named reference groups, annualisation over more than four years and census years only. A value in a chart data label, table cell or sentence counts as stated. Grade the reported outcome, rather than requiring a displayed calculation.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 37": { + "description": "States the per-year change in the immigrant gap as -0.13 percentage points per year from 2006 to 2016 and -0.46 percentage points per year from 2016 to 2021 (acceptable ranges -0.19 to -0.07 and -0.58 to -0.34).", + "justification": "Source: Housing_and_Work_Databook.xlsx, worksheet Housing_Groups (Plate 2). Readings for 2006, 2016 and 2021 are immigrants 17.1, 15.7, 10.7 and non-immigrants 9.2, 9.1, 6.4; the resulting group-minus-reference gaps are 7.9, 6.6 and 4.3 percentage points. Each source reading allows \u00b10.15 percentage points. A difference between two gaps uses four readings, so its bounded tolerance is \u00b10.60 percentage points. The 2006-2016 change is -1.3 and the 2016-2021 change is -2.3; each allows \u00b10.60. Divide the first change bounds by 10 years and the second by 5 years, then round once to two decimals. The annual ranges are -0.19 to -0.07 and -0.58 to -0.34. Evidence_Reporting_Standard.docx, sections 2-4 and footnotes 3, 4 and 9, requires signed changes, the named reference groups, annualisation over more than four years and census years only. A value in a chart data label, table cell or sentence counts as stated. Grade the reported outcome, rather than requiring a displayed calculation.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 38": { + "description": "States the per-year change in the visible minority gap as -0.34 percentage points per year from 2006 to 2016 and -0.84 percentage points per year from 2016 to 2021 (acceptable ranges -0.40 to -0.28 and -0.96 to -0.72).", + "justification": "Source: Housing_and_Work_Databook.xlsx, worksheet Housing_Groups (Plate 2). Readings for 2006, 2016 and 2021 are visible minorities 21.4, 17.8, 11.3 and not a visible minority 8.8, 8.6, 6.3; the resulting group-minus-reference gaps are 12.6, 9.2 and 5.0 percentage points. Each source reading allows \u00b10.15 percentage points. A difference between two gaps uses four readings, so its bounded tolerance is \u00b10.60 percentage points. The 2006-2016 change is -3.4 and the 2016-2021 change is -4.2; each allows \u00b10.60. Divide the first change bounds by 10 years and the second by 5 years, then round once to two decimals. The annual ranges are -0.40 to -0.28 and -0.96 to -0.72. Evidence_Reporting_Standard.docx, sections 2-4 and footnotes 3, 4 and 9, requires signed changes, the named reference groups, annualisation over more than four years and census years only. A value in a chart data label, table cell or sentence counts as stated. Grade the reported outcome, rather than requiring a displayed calculation.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 39": { + "description": "States the per-year change in the Indigenous identity gap as -0.27 percentage points per year from 2006 to 2016 and -0.74 percentage points per year from 2016 to 2021 (acceptable ranges -0.33 to -0.21 and -0.86 to -0.62).", + "justification": "Source: Housing_and_Work_Databook.xlsx, worksheet Housing_Groups (Plate 2). Readings for 2006, 2016 and 2021 are Indigenous identity 22.7, 19.8, 13.2 and non-Indigenous identity 10.5, 10.3, 7.4; the resulting group-minus-reference gaps are 12.2, 9.5 and 5.8 percentage points. Each source reading allows \u00b10.15 percentage points. A difference between two gaps uses four readings, so its bounded tolerance is \u00b10.60 percentage points. The 2006-2016 change is -2.7 and the 2016-2021 change is -3.7; each allows \u00b10.60. Divide the first change bounds by 10 years and the second by 5 years, then round once to two decimals. The annual ranges are -0.33 to -0.21 and -0.86 to -0.62. Evidence_Reporting_Standard.docx, sections 2-4 and footnotes 3, 4 and 9, requires signed changes, the named reference groups, annualisation over more than four years and census years only. A value in a chart data label, table cell or sentence counts as stated. Grade the reported outcome, rather than requiring a displayed calculation.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 40": { + "description": "States the change in the gap between Women+ and Men+ aged 65 and older from 2006 to 2021 as -0.21 percentage points per year (acceptable range -0.25 to -0.17).", + "justification": "Source: Housing_and_Work_Databook.xlsx, worksheet Housing_65_Plus (Plate 1). Readings for 2006, 2016 and 2021 are Women+ 14.0, 12.9, 10.5 and Men+ 7.4, 8.2, 7.1; the resulting group-minus-reference gaps are 6.6, 4.7 and 3.4 percentage points. Each source reading allows \u00b10.15 percentage points. A difference between two gaps uses four readings, so its bounded tolerance is \u00b10.60 percentage points. The 2006-2021 change is 3.4 - 6.6 = -3.2, with accepted bounds -3.8 to -2.6. Dividing the unrounded change bounds by 15 years and rounding once to two decimals gives -0.25 to -0.17 percentage points per year. Evidence_Reporting_Standard.docx, sections 2-4 and footnotes 3, 4 and 9, requires signed changes, the named reference groups, annualisation over more than four years and census years only. A value in a chart data label, table cell or sentence counts as stated. Grade the reported outcome, rather than requiring a displayed calculation.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 41": { + "description": "States the change in the visible minority gap from 2006 to 2021 as -0.51 percentage points per year (acceptable range -0.55 to -0.47).", + "justification": "Source: Housing_and_Work_Databook.xlsx, worksheet Housing_Groups (Plate 2). Readings for 2006, 2016 and 2021 are visible minorities 21.4, 17.8, 11.3 and not a visible minority 8.8, 8.6, 6.3; the resulting group-minus-reference gaps are 12.6, 9.2 and 5.0 percentage points. Each source reading allows \u00b10.15 percentage points. A difference between two gaps uses four readings, so its bounded tolerance is \u00b10.60 percentage points. The 2006-2021 change is 5.0 - 12.6 = -7.6, with accepted bounds -8.2 to -7.0. Dividing the unrounded change bounds by 15 years and rounding once to two decimals gives -0.55 to -0.47 percentage points per year. Evidence_Reporting_Standard.docx, sections 2-4 and footnotes 3, 4 and 9, requires signed changes, the named reference groups, annualisation over more than four years and census years only. A value in a chart data label, table cell or sentence counts as stated. Grade the reported outcome, rather than requiring a displayed calculation.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 42": { + "description": "States the change in the Indigenous identity gap from 2006 to 2021 as -0.43 percentage points per year (acceptable range -0.47 to -0.39).", + "justification": "Source: Housing_and_Work_Databook.xlsx, worksheet Housing_Groups (Plate 2). Readings for 2006, 2016 and 2021 are Indigenous identity 22.7, 19.8, 13.2 and non-Indigenous identity 10.5, 10.3, 7.4; the resulting group-minus-reference gaps are 12.2, 9.5 and 5.8 percentage points. Each source reading allows \u00b10.15 percentage points. A difference between two gaps uses four readings, so its bounded tolerance is \u00b10.60 percentage points. The 2006-2021 change is 5.8 - 12.2 = -6.4, with accepted bounds -7.0 to -5.8. Dividing the unrounded change bounds by 15 years and rounding once to two decimals gives -0.47 to -0.39 percentage points per year. Evidence_Reporting_Standard.docx, sections 2-4 and footnotes 3, 4 and 9, requires signed changes, the named reference groups, annualisation over more than four years and census years only. A value in a chart data label, table cell or sentence counts as stated. Grade the reported outcome, rather than requiring a displayed calculation.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 43": { + "description": "Presents working after retirement on slide 4 as one native combination chart: columns for Men+ and Women+ at 2016 and 2023, and a line series for the gender gap plotted on a secondary value axis.", + "justification": "Per the prompt: \"Slide 4 charts working after retirement by gender for 2016 and 2023 as columns with the gender gap as a line on a secondary axis and gives the change in the gap, charts the 2023 class of worker of the previously retired, gives the widest gap between the three family debt tiers and names the provinces that differ from Ontario.\" Source plate: Housing_and_Work_Databook.xlsx, sheet Work_After_Retirement.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 44": { + "description": "Plots the 2016 values of the native slide 4 combination chart as 8.1 percent for Men+, 5.3 percent for Women+ and -2.8 percentage points for the gender gap (acceptable ranges 7.95 to 8.25, 5.15 to 5.45 and -3.10 to -2.50).", + "justification": "Source: Housing_and_Work_Databook.xlsx, Work_After_Retirement worksheet, 2016 Men+ and Women+ markers. The central readings are 8.1 and 5.3 percent; each allows \u00b10.15 percentage points on the 0.5-point grid. Evidence_Reporting_Standard.docx, footnote 3, defines the gender gap as Women+ minus Men+: 5.3 - 8.1 = -2.8. Subtracting two bounded readings gives \u00b10.30 for the gap, hence -3.10 to -2.50. Grade the values in the native editable PowerPoint chart.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 45": { + "description": "Plots the 2023 values of the native slide 4 combination chart as 12.3 percent for Men+, 8.6 percent for Women+ and -3.7 percentage points for the gender gap (acceptable ranges 12.15 to 12.45, 8.45 to 8.75 and -4.00 to -3.40).", + "justification": "Source: Housing_and_Work_Databook.xlsx, Work_After_Retirement worksheet, 2023 Men+ and Women+ markers. The central readings are 12.3 and 8.6 percent; each allows \u00b10.15 percentage points on the 0.5-point grid. Evidence_Reporting_Standard.docx, footnote 3, defines the gender gap as Women+ minus Men+: 8.6 - 12.3 = -3.7. Subtracting two bounded readings gives \u00b10.30 for the gap, hence -4.00 to -3.40. Grade the values in the native editable PowerPoint chart.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 46": { + "description": "Presents the 2023 class of worker of the previously retired on slide 4 as a native editable PowerPoint chart, using employee and combined self-employed/family-business-without-pay categories for a chart of previously retired All only, or employee, self-employed and family business without pay separately in a multi-group comparison that includes previously retired All or both previously retired Men+ and Women+.", + "justification": "Source: Housing_and_Work_Databook.xlsx, Class_of_Worker worksheet, Plate 5, 2023 stacked bars labelled Previously retired \u2014 All, Men+ and Women+. Expected values cited here concern previously retired populations; additional comparator populations may also be shown. The prompt specifies the subject and editable chart, but not a bar-chart type or an All-only presentation. Evidence_Reporting_Standard.docx, footnote 12, combines a below-10.0% category into the next larger category for a single-group distribution and retains the original categories whenever two or more groups are compared. Accepted comparisons include previously retired Men+ versus Women+, with or without All, and previously retired All versus a never-retired comparator. Every comparison shows employee, self-employed and family business without pay separately. Numerical grading concerns the previously retired values requested by the prompt. Both chart structures are accepted.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 47": { + "description": "Plots each employee share shown in the native slide 4 class-of-worker chart within these ranges: All 62.7 percent (61.7 to 63.7), Men+ 60.6 percent (59.6 to 61.6), and Women+ 65.3 percent (64.3 to 66.3).", + "justification": "Source: Housing_and_Work_Databook.xlsx, Class_of_Worker worksheet, Plate 5, 2023 stacked bars labelled Previously retired \u2014 All, Men+ and Women+. Expected values cited here concern previously retired populations; additional comparator populations may also be shown. Employee shares for previously retired All, Men+ and Women+ are 62.7, 60.6 and 65.3 percent, respectively. Each source reading allows \u00b11.0 percentage point. Check every displayed previously retired population against its range. A valid single-group chart uses previously retired All. A valid comparison includes previously retired All or both previously retired Men+ and Women+ and may also include comparator populations. Values of optional comparator populations are outside this prompt-specific numerical check. Grade the values in the native editable PowerPoint chart.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 48": { + "description": "States the change in the gender gap in working after retirement from 2016 to 2023 as -0.9 percentage points (acceptable range -1.5 to -0.3).", + "justification": "Source: Housing_and_Work_Databook.xlsx, Work_After_Retirement worksheet. The central Women+ minus Men+ gaps are 5.3 - 8.1 = -2.8 in 2016 and 8.6 - 12.3 = -3.7 in 2023. Their change is -3.7 - (-2.8) = -0.9 percentage points. Each underlying reading allows \u00b10.15; the four-read change therefore allows \u00b10.60, giving -1.5 to -0.3. Evidence_Reporting_Standard.docx, footnote 3, fixes the reference direction, and section 2 requires a signed change. The tolerance is based on accepted readings, rather than on excluding a neighbouring-year result. A value in a chart data label, table cell or sentence counts as stated. Grade the reported outcome, rather than requiring a displayed calculation.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 49": { + "description": "Includes a chart note identifying the combination of family business without pay with self-employed when the slide 4 class-of-worker chart shows previously retired All as a single-group distribution; a multi-group comparison showing employee, self-employed and family business without pay separately also satisfies this criterion.", + "justification": "Source: Housing_and_Work_Databook.xlsx, Class_of_Worker worksheet, Plate 5, 2023 stacked bars labelled Previously retired \u2014 All, Men+ and Women+. Expected values cited here concern previously retired populations; additional comparator populations may also be shown. Evidence_Reporting_Standard.docx, footnote 12, requires a merge note for a single-group distribution and preserves original categories in a multi-group comparison. For previously retired All, family business without pay is 4.6 \u00b11.0 percent and remains below 10.0%; self-employed is 32.8 \u00b11.0 and remains the next larger category. Combining them gives 37.4 \u00b12.0 percent. Thus the single-group merge is stable throughout the accepted source-reading bounds. In the comparison alternative there is no merge to explain; the retained three-category comparison satisfies this conditional requirement. Grade the chart and its note, rather than the steps used to create them.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 4, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 50": { + "description": "States the widest gap in working after retirement between the family debt tiers as 9.4 percentage points, between the greater than $40,000 tier and the $0 tier (acceptable range 8.4 to 10.4).", + "justification": "Per the prompt: \"Slide 4 charts working after retirement by gender for 2016 and 2023 as columns with the gender gap as a line on a secondary axis and gives the change in the gap, charts the 2023 class of worker of the previously retired, gives the widest gap between the three family debt tiers and names the provinces that differ from Ontario.\" Read from Housing_and_Work_Databook.xlsx, sheet Debt, panel A: $0 6.9, $1 to $40,000 11.5, greater than $40,000 16.3. Widest gap 16.3 - 6.9 = 9.4. Tolerance 1.0 from two reads at 0.5 (fine grid at 0.5). A value shown as a chart data label, a table cell or a sentence counts as stated.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 51": { + "description": "States the change in the gender gap in working after retirement from 2016 to 2023 as -0.13 percentage points per year (acceptable range -0.21 to -0.04).", + "justification": "Source: Housing_and_Work_Databook.xlsx, Work_After_Retirement worksheet, 2016 and 2023 gender series. Central gap change: (8.6 - 12.3) - (5.3 - 8.1) = -0.9 percentage points. Four readings at \u00b10.15 give an accepted change interval of -1.5 to -0.3. Divide those bounds by seven years and round once to two decimals: -0.21 to -0.04 percentage points per year, with a central result of -0.13. Evidence_Reporting_Standard.docx, footnotes 3 and 4, defines the gap direction and annual reporting. A value in a chart data label, table cell or sentence counts as stated. Grade the reported outcome, rather than requiring a displayed calculation.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 52": { + "description": "Names Prince Edward Island and Manitoba as the only provinces that differ from Ontario.", + "justification": "Per the prompt: \"Slide 4 charts working after retirement by gender for 2016 and 2023 as columns with the gender gap as a line on a secondary axis and gives the change in the gap, charts the 2023 class of worker of the previously retired, gives the widest gap between the three family debt tiers and names the provinces that differ from Ontario.\" Read from the Model 3 plate in Housing_and_Work_Databook.xlsx, sheet Provinces. Filled markers: Prince Edward Island 17.0, Manitoba 15.2, Saskatchewan 12.1, Quebec 11.8, British Columbia 11.6; Ontario 8.8. Evidence_Reporting_Standard.docx, footnote 6, reports a province as differing when its marker is filled and the difference in predicted probability is at least 4.5 percentage points. Differences: Prince Edward Island +8.2, Manitoba +6.4, Saskatchewan +3.3, Quebec +3.0, British Columbia +2.8. Each read carries 0.2; the nearest difference to the line, Saskatchewan, is 1.2 below it. Quebec, Saskatchewan and British Columbia have filled markers but fall below the line and are not reported as differing. A plotted value or data label alone does not satisfy this check; the deck has to write the name, description or rank in a sentence, list line or table cell.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 5, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 53": { + "description": "States the differences in Model 3 predicted probability from Ontario as +8.2 percentage points for Prince Edward Island and +6.4 percentage points for Manitoba (acceptable ranges +7.8 to +8.6 and +6.0 to +6.8).", + "justification": "Per the prompt: \"Slide 4 charts working after retirement by gender for 2016 and 2023 as columns with the gender gap as a line on a secondary axis and gives the change in the gap, charts the 2023 class of worker of the previously retired, gives the widest gap between the three family debt tiers and names the provinces that differ from Ontario.\" Read from the Model 3 plate in Housing_and_Work_Databook.xlsx, sheet Provinces: Prince Edward Island 17.0, Manitoba 15.2, Ontario 8.8, so 17.0 - 8.8 = +8.2 and 15.2 - 8.8 = +6.4. The plate has gridlines every 0.5 points, about 0.7 inches per point, so each read carries 0.2 and each difference 0.4. Evidence_Reporting_Standard.docx, section 2: a difference between two groups is reported by its size; section 3: comparisons between provinces use the model that adjusts for all characteristics. A value shown as a chart data label, a table cell or a sentence counts as stated.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 54": { + "description": "Presents the regression results on slide 4 as a table with ten characteristic rows and three model columns under one header cell that spans all three model columns.", + "justification": "Per the prompt: \"It also tabulates the predicted probabilities for all ten characteristics across the three regression models under one merged model header, shades cells only when their plate markers are filled and their predicted probabilities are at least 10.0%, marks untested cells n/a, explains both shading conditions in a table note, and names the characteristics meeting both conditions in every model that tests them.\" The merged model header is visible in the rendered table as a single cell above the three columns.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 55": { + "description": "Marks with n/a the Model 1 cells of education, age group, employer pension plan, widowed, gender, racialized population and immigrant status and the Model 2 cells of the last five of these in the slide 4 table.", + "justification": "Per the prompt: \"It also tabulates the predicted probabilities for all ten characteristics across the three regression models under one merged model header, shades cells only when their plate markers are filled and their predicted probabilities are at least 10.0%, marks untested cells n/a, explains both shading conditions in a table note, and names the characteristics meeting both conditions in every model that tests them.\" Untested cells read not in model in the plate: rows 4 to 10 in Model 1 (education, age group, employer pension plan, widowed, gender, racialized population, immigrant status) and rows 6 to 10 in Model 2. Only the literal n/a mark in the table cells counts; a sentence about untested cells does not. Source: Housing_and_Work_Databook.xlsx, sheet Regression_Summary.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 56": { + "description": "Shades the family debt greater than $40,000 cells of Models 1, 2 and 3 in the slide 4 table.", + "justification": "Source: Housing_and_Work_Databook.xlsx, Regression_Summary worksheet, three-model plate. The family-debt-greater-than-$40,000 markers are filled in Models 1, 2 and 3 at 15.5, 14.1 and 14.2 percent. Each reading allows \u00b10.20, consistent with the numerical table criteria; even the lowest accepted reading, 13.9, remains above 10.0. Evidence_Reporting_Standard.docx, footnote 7, requires both a filled marker and a predicted probability of at least 10.0 percent for shading. All three table cells are therefore shaded. Grade the displayed cell fills.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 57": { + "description": "Shades the family assets greater than $2,264,100 cell of Model 1 in the slide 4 table.", + "justification": "Source: Housing_and_Work_Databook.xlsx, Regression_Summary worksheet, three-model plate. The family-assets-greater-than-$2,264,100 marker is filled in Model 1 at 15.6 \u00b10.20 percent. Its accepted range, 15.4-15.8, remains above 10.0. The Model 2 and 3 markers are hollow. Evidence_Reporting_Standard.docx, footnote 7, requires both a filled marker and a predicted probability of at least 10.0 percent for shading. The Model 1 table cell is shaded. Grade the displayed cell fill.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 58": { + "description": "Presents the Model 3 widowed cell of the slide 4 regression table with an unshaded fill.", + "justification": "Source: Housing_and_Work_Databook.xlsx, Regression_Summary worksheet, three-model plate. The widowed marker is filled in Model 3 at 6.9 \u00b10.20 percent (6.7-7.1), wholly below 10.0. Evidence_Reporting_Standard.docx, footnote 7, requires both a filled marker and a predicted probability of at least 10.0 percent for shading. The cell remains unshaded although the filled marker indicates statistical significance. Grade the displayed table-cell fill.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 59": { + "description": "Leaves the family assets cells of Models 2 and 3 in the slide 4 table unshaded.", + "justification": "Per the prompt: \"It also tabulates the predicted probabilities for all ten characteristics across the three regression models under one merged model header, shades cells only when their plate markers are filled and their predicted probabilities are at least 10.0%, marks untested cells n/a, explains both shading conditions in a table note, and names the characteristics meeting both conditions in every model that tests them.\" Housing_and_Work_Databook.xlsx, sheet Regression_Summary: the assets markers are hollow in Models 2 and 3 at 12.4 and 12.6, above 10.0 percent but not statistically significant, so the cells stay unshaded. Only the fill of the table cells counts.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 60": { + "description": "Leaves the age group 60 to 64 years cells of Models 2 and 3 in the slide 4 table unshaded.", + "justification": "Per the prompt: \"It also tabulates the predicted probabilities for all ten characteristics across the three regression models under one merged model header, shades cells only when their plate markers are filled and their predicted probabilities are at least 10.0%, marks untested cells n/a, explains both shading conditions in a table note, and names the characteristics meeting both conditions in every model that tests them.\" Housing_and_Work_Databook.xlsx, sheet Regression_Summary: the age markers are hollow in Models 2 and 3 at 16.9 and 16.4, above 10.0 percent but not statistically significant, so the cells stay unshaded. Only the fill of the table cells counts.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 61": { + "description": "Presents the Model 3 employer pension plan cell of the slide 4 regression table with an unshaded fill.", + "justification": "Source: Housing_and_Work_Databook.xlsx, Regression_Summary worksheet, three-model plate. The employer pension plan marker in Model 3 is hollow at 11.1 \u00b10.20 percent (10.9-11.3). Evidence_Reporting_Standard.docx, footnote 7, requires both a filled marker and a predicted probability of at least 10.0 percent for shading. A hollow marker leaves this cell unshaded regardless of the probability within that range. Grade the displayed table-cell fill.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 62": { + "description": "Leaves the other family income greater than $121,000 cells of Models 1, 2 and 3 in the slide 4 table unshaded.", + "justification": "Per the prompt: \"It also tabulates the predicted probabilities for all ten characteristics across the three regression models under one merged model header, shades cells only when their plate markers are filled and their predicted probabilities are at least 10.0%, marks untested cells n/a, explains both shading conditions in a table note, and names the characteristics meeting both conditions in every model that tests them.\" Housing_and_Work_Databook.xlsx, sheet Regression_Summary: the other family income markers are hollow in all three models, at 9.6, 9.9 and 9.9, so the cells stay unshaded whatever the reading of the value. Only the fill of the table cells counts.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 63": { + "description": "Presents the Models 2 and 3 education: high school diploma cells of the slide 4 regression table with unshaded fills.", + "justification": "Source: Housing_and_Work_Databook.xlsx, Regression_Summary worksheet, three-model plate. The education: high school diploma markers are hollow in Models 2 and 3 at 8.7 \u00b10.20 and 8.9 \u00b10.20 percent (8.5-8.9 and 8.7-9.1). Evidence_Reporting_Standard.docx, footnote 7, requires both a filled marker and a predicted probability of at least 10.0 percent for shading. The cells remain unshaded; the hollow markers alone determine this state. Grade the displayed table-cell fills.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 64": { + "description": "Leaves the n/a cells of the slide 4 table unshaded.", + "justification": "Per the prompt: \"It also tabulates the predicted probabilities for all ten characteristics across the three regression models under one merged model header, shades cells only when their plate markers are filled and their predicted probabilities are at least 10.0%, marks untested cells n/a, explains both shading conditions in a table note, and names the characteristics meeting both conditions in every model that tests them.\" A cell is shaded only when its plate marker is filled and its predicted probability is at least 10.0 percent; an n/a cell has no marker in the plate (Housing_and_Work_Databook.xlsx, sheet Regression_Summary, rows that read not in model), so it stays unshaded. Only the fill of the table cells counts.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 65": { + "description": "Gives the family debt greater than $40,000 row of the slide 4 table the predicted probabilities 15.5, 14.1 and 14.2 percent for Models 1, 2 and 3 (acceptable ranges 15.3 to 15.7, 13.9 to 14.3 and 14.0 to 14.4).", + "justification": "Per the prompt: \"It also tabulates the predicted probabilities for all ten characteristics across the three regression models under one merged model header, shades cells only when their plate markers are filled and their predicted probabilities are at least 10.0%, marks untested cells n/a, explains both shading conditions in a table note, and names the characteristics meeting both conditions in every model that tests them.\" Housing_and_Work_Databook.xlsx, sheet Regression_Summary: the markers of this row sit at 15.5, 14.1 and 14.2 for Models 1, 2 and 3 on an axis with gridlines every 0.5 points, so each read carries 0.2. Only the values in the table cells count.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 66": { + "description": "Gives the family assets greater than $2,264,100 row of the slide 4 table the predicted probabilities 15.6, 12.4 and 12.6 percent for Models 1, 2 and 3 (acceptable ranges 15.4 to 15.8, 12.2 to 12.6 and 12.4 to 12.8).", + "justification": "Per the prompt: \"It also tabulates the predicted probabilities for all ten characteristics across the three regression models under one merged model header, shades cells only when their plate markers are filled and their predicted probabilities are at least 10.0%, marks untested cells n/a, explains both shading conditions in a table note, and names the characteristics meeting both conditions in every model that tests them.\" Housing_and_Work_Databook.xlsx, sheet Regression_Summary: the markers of this row sit at 15.6, 12.4 and 12.6 for Models 1, 2 and 3 on an axis with gridlines every 0.5 points, so each read carries 0.2. Only the values in the table cells count.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 67": { + "description": "Gives the other family income greater than $121,000 row of the slide 4 table the predicted probabilities 9.6, 9.9 and 9.9 percent for Models 1, 2 and 3 (acceptable ranges 9.4 to 9.8, 9.7 to 10.1 and 9.7 to 10.1).", + "justification": "Per the prompt: \"It also tabulates the predicted probabilities for all ten characteristics across the three regression models under one merged model header, shades cells only when their plate markers are filled and their predicted probabilities are at least 10.0%, marks untested cells n/a, explains both shading conditions in a table note, and names the characteristics meeting both conditions in every model that tests them.\" Housing_and_Work_Databook.xlsx, sheet Regression_Summary: the markers of this row sit at 9.6, 9.9 and 9.9 for Models 1, 2 and 3 on an axis with gridlines every 0.5 points, so each read carries 0.2. Only the values in the table cells count.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 68": { + "description": "Gives the education: high school diploma row of the slide 4 table the predicted probabilities 8.7 and 8.9 percent for Models 2 and 3 (acceptable ranges 8.5 to 8.9 and 8.7 to 9.1).", + "justification": "Per the prompt: \"It also tabulates the predicted probabilities for all ten characteristics across the three regression models under one merged model header, shades cells only when their plate markers are filled and their predicted probabilities are at least 10.0%, marks untested cells n/a, explains both shading conditions in a table note, and names the characteristics meeting both conditions in every model that tests them.\" Housing_and_Work_Databook.xlsx, sheet Regression_Summary: the markers of this row sit at 8.7 and 8.9 for Models 2 and 3 on an axis with gridlines every 0.5 points, so each read carries 0.2. Only the values in the table cells count.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 69": { + "description": "Gives the age group 60 to 64 years row of the slide 4 table the predicted probabilities 16.9 and 16.4 percent for Models 2 and 3 (acceptable ranges 16.7 to 17.1 and 16.2 to 16.6).", + "justification": "Per the prompt: \"It also tabulates the predicted probabilities for all ten characteristics across the three regression models under one merged model header, shades cells only when their plate markers are filled and their predicted probabilities are at least 10.0%, marks untested cells n/a, explains both shading conditions in a table note, and names the characteristics meeting both conditions in every model that tests them.\" Housing_and_Work_Databook.xlsx, sheet Regression_Summary: the markers of this row sit at 16.9 and 16.4 for Models 2 and 3 on an axis with gridlines every 0.5 points, so each read carries 0.2. Only the values in the table cells count.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 70": { + "description": "Presents the Model 3 employer pension plan cell of the slide 4 regression table with a predicted probability of 11.1 percent (acceptable range 10.9 to 11.3).", + "justification": "Source: Housing_and_Work_Databook.xlsx, Regression_Summary worksheet, three-model plate. The employer pension plan marker in Model 3 is at 11.1 percent; allow \u00b10.20 percentage points on the 0.5-point grid. Models 1 and 2 do not test this characteristic. Grade the value displayed in the table cell.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 71": { + "description": "Presents the Model 3 racialized population cell of the slide 4 regression table with a predicted probability of 8.4 percent (acceptable range 8.2 to 8.6).", + "justification": "Source: Housing_and_Work_Databook.xlsx, Regression_Summary worksheet, three-model plate. The racialized population marker in Model 3 is at 8.4 percent; allow \u00b10.20 percentage points on the 0.5-point grid. Models 1 and 2 do not test this characteristic. Grade the value displayed in the table cell.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 72": { + "description": "States in the slide 4 table note that a shaded cell has a filled marker and a predicted probability of at least 10.0 percent, and that filled-marker results below 10.0 percent remain statistically significant but are left unshaded.", + "justification": "Per the prompt: \"It also tabulates the predicted probabilities for all ten characteristics across the three regression models under one merged model header, shades cells only when their plate markers are filled and their predicted probabilities are at least 10.0%, marks untested cells n/a, explains both shading conditions in a table note, and names the characteristics meeting both conditions in every model that tests them.\" Evidence_Reporting_Standard.docx, footnote 7: the 10.0 percent cutoff is an additional reporting threshold and does not determine statistical significance; the table note explains the distinction.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 73": { + "description": "Names family debt greater than $40,000 as the only characteristic that meets both conditions, a filled marker and a predicted probability of at least 10.0 percent, in every model that tests it.", + "justification": "Per the prompt: \"It also tabulates the predicted probabilities for all ten characteristics across the three regression models under one merged model header, shades cells only when their plate markers are filled and their predicted probabilities are at least 10.0%, marks untested cells n/a, explains both shading conditions in a table note, and names the characteristics meeting both conditions in every model that tests them.\" Family debt is filled and at least 10.0 percent in all three models. Family assets meets both conditions in Model 1 only. Widowed (6.9) and Women+ (8.6) are tested in Model 3 only, are filled and therefore statistically significant, but fall below 10.0 percent. Source: Housing_and_Work_Databook.xlsx, sheet Regression_Summary. A plotted value or data label alone does not satisfy this check; the deck has to write the name, description or rank in a sentence, list line or table cell.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 5, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 74": { + "description": "Presents the main reasons for retiring on slide 5 as a native chart with six reasons and one series each for Men+ and Women+.", + "justification": "Per the prompt: \"Slide 5 charts the main reasons for retiring by gender and names the reasons for which the women's share is higher than the men's, charts the average retirement age by reason for 2023 and 2025; it ranks the reasons by 2023 age and gives the share-weighted average age for 2025.\" Source plate: Retirement_Income_Chartbook.pptx, slide 4 (Plate 3).", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 75": { + "description": "Plots the Men+ shares of agreement with spouse or partner, financial considerations and health or disability issues of self or spouse in the native slide 5 reasons chart as 2.4, 37.2 and 22.0 percent (acceptable ranges 2.1 to 2.7, 36.9 to 37.5 and 21.7 to 22.3).", + "justification": "Per the prompt: \"Slide 5 charts the main reasons for retiring by gender and names the reasons for which the women's share is higher than the men's, charts the average retirement age by reason for 2023 and 2025; it ranks the reasons by 2023 age and gives the share-weighted average age for 2025.\" Retirement_Income_Chartbook.pptx, slide 4 (Plate 3): the Men+ bars end at 2.4, 37.2 and 22.0 on an axis with gridlines every 0.5 points, so each read carries 0.3. Only the values of the native, editable PowerPoint chart count; a value written only in a sentence or a table, or shown in a picture of a chart, does not.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 76": { + "description": "Plots the Men+ shares of layoff or other employer-related reason, other factor and personal reasons in the native slide 5 reasons chart as 12.4, 13.9 and 12.0 percent (acceptable ranges 12.1 to 12.7, 13.6 to 14.2 and 11.7 to 12.3).", + "justification": "Per the prompt: \"Slide 5 charts the main reasons for retiring by gender and names the reasons for which the women's share is higher than the men's, charts the average retirement age by reason for 2023 and 2025; it ranks the reasons by 2023 age and gives the share-weighted average age for 2025.\" Retirement_Income_Chartbook.pptx, slide 4 (Plate 3): the Men+ bars end at 12.4, 13.9 and 12.0 on an axis with gridlines every 0.5 points, so each read carries 0.3. Only the values of the native, editable PowerPoint chart count; a value written only in a sentence or a table, or shown in a picture of a chart, does not.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 77": { + "description": "Plots the Women+ shares of agreement with spouse or partner, financial considerations and health or disability issues of self or spouse in the native slide 5 reasons chart as 5.3, 32.1 and 22.3 percent (acceptable ranges 5.0 to 5.6, 31.8 to 32.4 and 22.0 to 22.6).", + "justification": "Per the prompt: \"Slide 5 charts the main reasons for retiring by gender and names the reasons for which the women's share is higher than the men's, charts the average retirement age by reason for 2023 and 2025; it ranks the reasons by 2023 age and gives the share-weighted average age for 2025.\" Retirement_Income_Chartbook.pptx, slide 4 (Plate 3): the Women+ bars end at 5.3, 32.1 and 22.3 on an axis with gridlines every 0.5 points, so each read carries 0.3. Only the values of the native, editable PowerPoint chart count; a value written only in a sentence or a table, or shown in a picture of a chart, does not.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 78": { + "description": "Plots the Women+ shares of layoff or other employer-related reason, other factor and personal reasons in the native slide 5 reasons chart as 9.2, 18.3 and 12.8 percent (acceptable ranges 8.9 to 9.5, 18.0 to 18.6 and 12.5 to 13.1).", + "justification": "Per the prompt: \"Slide 5 charts the main reasons for retiring by gender and names the reasons for which the women's share is higher than the men's, charts the average retirement age by reason for 2023 and 2025; it ranks the reasons by 2023 age and gives the share-weighted average age for 2025.\" Retirement_Income_Chartbook.pptx, slide 4 (Plate 3): the Women+ bars end at 9.2, 18.3 and 12.8 on an axis with gridlines every 0.5 points, so each read carries 0.3. Only the values of the native, editable PowerPoint chart count; a value written only in a sentence or a table, or shown in a picture of a chart, does not.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 79": { + "description": "Names agreement with spouse or partner and other factor as the only reasons for which the Women+ share is higher than the Men+ share.", + "justification": "Per the prompt: \"Slide 5 charts the main reasons for retiring by gender and names the reasons for which the women's share is higher than the men's, charts the average retirement age by reason for 2023 and 2025; it ranks the reasons by 2023 age and gives the share-weighted average age for 2025.\" Women+ minus Men+: other factor +4.4, agreement with spouse or partner +2.9, health or disability +0.3, personal reasons +0.8, layoff -3.2, financial considerations -5.1. Evidence_Reporting_Standard.docx, footnote 3, describes a difference of less than 2.0 percentage points as similar and names neither group as higher, which removes health or disability and personal reasons. Each difference carries 0.6 (two reads at 0.3); the nearest difference to the line, agreement with spouse or partner, is 0.9 above it. The plate sets two groups side by side, so footnote 12 does not merge any category, and footnote 10 keeps the residual category other factor in comparisons between groups. Source: Retirement_Income_Chartbook.pptx, slide 4 (Plate 3). A plotted value or data label alone does not satisfy this check; the deck has to write the name, description or rank in a sentence, list line or table cell.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 5, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 80": { + "description": "Presents the average retirement age by reason on slide 5 as a native chart with series for 2023 and 2025 across the six reasons.", + "justification": "Per the prompt: \"Slide 5 charts the main reasons for retiring by gender and names the reasons for which the women's share is higher than the men's, charts the average retirement age by reason for 2023 and 2025; it ranks the reasons by 2023 age and gives the share-weighted average age for 2025.\" Source plate: Retirement_Income_Chartbook.pptx, slide 5 (Plate 4).", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 81": { + "description": "Plots the 2023 average retirement ages of agreement with spouse or partner, financial considerations and health or disability issues of self or spouse in the native slide 5 age chart as 55.4, 60.9 and 57.6 years (acceptable ranges 55.3 to 55.5, 60.8 to 61.0 and 57.5 to 57.7).", + "justification": "Per the prompt: \"Slide 5 charts the main reasons for retiring by gender and names the reasons for which the women's share is higher than the men's, charts the average retirement age by reason for 2023 and 2025; it ranks the reasons by 2023 age and gives the share-weighted average age for 2025.\" Retirement_Income_Chartbook.pptx, slide 5 (Plate 4): the June 2023 markers, hollow as the legend assigns them, sit at 55.4, 60.9 and 57.6 on an axis with gridlines every 0.1 year; each age sits on a gridline, and the range allows one gridline either way. Only the values of the native, editable PowerPoint chart count; a value written only in a sentence or a table, or shown in a picture of a chart, does not.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 82": { + "description": "Plots the 2023 average retirement ages of layoff or other employer-related reason, other factor and personal reasons in the native slide 5 age chart as 61.3, 58.6 and 60.7 years (acceptable ranges 61.2 to 61.4, 58.5 to 58.7 and 60.6 to 60.8).", + "justification": "Per the prompt: \"Slide 5 charts the main reasons for retiring by gender and names the reasons for which the women's share is higher than the men's, charts the average retirement age by reason for 2023 and 2025; it ranks the reasons by 2023 age and gives the share-weighted average age for 2025.\" Retirement_Income_Chartbook.pptx, slide 5 (Plate 4): the June 2023 markers, hollow as the legend assigns them, sit at 61.3, 58.6 and 60.7 on an axis with gridlines every 0.1 year; each age sits on a gridline, and the range allows one gridline either way. Only the values of the native, editable PowerPoint chart count; a value written only in a sentence or a table, or shown in a picture of a chart, does not.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 83": { + "description": "Plots the 2025 average retirement ages of agreement with spouse or partner, financial considerations and health or disability issues of self or spouse in the native slide 5 age chart as 55.7, 61.1 and 58.2 years (acceptable ranges 55.6 to 55.8, 61.0 to 61.2 and 58.1 to 58.3).", + "justification": "Per the prompt: \"Slide 5 charts the main reasons for retiring by gender and names the reasons for which the women's share is higher than the men's, charts the average retirement age by reason for 2023 and 2025; it ranks the reasons by 2023 age and gives the share-weighted average age for 2025.\" Retirement_Income_Chartbook.pptx, slide 5 (Plate 4): the June 2025 markers, filled as the legend assigns them, sit at 55.7, 61.1 and 58.2 on an axis with gridlines every 0.1 year; each age sits on a gridline, and the range allows one gridline either way. Only the values of the native, editable PowerPoint chart count; a value written only in a sentence or a table, or shown in a picture of a chart, does not.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 84": { + "description": "Plots the 2025 average retirement ages of layoff or other employer-related reason, other factor and personal reasons in the native slide 5 age chart as 60.8, 59.5 and 60.8 years (acceptable ranges 60.7 to 60.9, 59.4 to 59.6 and 60.7 to 60.9).", + "justification": "Per the prompt: \"Slide 5 charts the main reasons for retiring by gender and names the reasons for which the women's share is higher than the men's, charts the average retirement age by reason for 2023 and 2025; it ranks the reasons by 2023 age and gives the share-weighted average age for 2025.\" Retirement_Income_Chartbook.pptx, slide 5 (Plate 4): the June 2025 markers, filled as the legend assigns them, sit at 60.8, 59.5 and 60.8 on an axis with gridlines every 0.1 year; each age sits on a gridline, and the range allows one gridline either way. Only the values of the native, editable PowerPoint chart count; a value written only in a sentence or a table, or shown in a picture of a chart, does not.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 85": { + "description": "Ranks layoff or other employer-related reason, financial considerations, personal reasons, health or disability issues of self or spouse and agreement with spouse or partner in this descending order of 2023 average retirement age, with a rank number before each category.", + "justification": "Per the prompt: \"Slide 5 charts the main reasons for retiring by gender and names the reasons for which the women's share is higher than the men's, charts the average retirement age by reason for 2023 and 2025; it ranks the reasons by 2023 age and gives the share-weighted average age for 2025.\" 2023 ages: layoff 61.3, financial considerations 60.9, personal reasons 60.7, health 57.6, spouse 55.4; other factor 58.6. The plate has gridlines every 0.1 year and each age sits on one; financial considerations (60.9) and personal reasons (60.7) lie two gridlines apart, which fixes their order. Evidence_Reporting_Standard.docx, section 5, ranks highest first and states a ranking in descending order with the rank number before each category. This check reads the order of these five reasons and the rank numbers; whether other factor is kept out of the ranking is graded on its own (Evidence_Reporting_Standard.docx, footnote 10). A plotted value or data label alone does not satisfy this check; the deck has to write the name, description or rank in a sentence, list line or table cell.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 86": { + "description": "Names the other factor category on slide 5 as a residual category that is shown and kept apart from the ranking.", + "justification": "Evidence_Reporting_Standard.docx, footnote 10: residual categories such as Other factor are shown in the plate but not ranked, and the residual category is named as unranked. The prompt asks the deck to follow the standard and to rank the reasons by 2023 age. Source: Retirement_Income_Chartbook.pptx, slide 5 (Plate 4). A plotted value or data label alone does not satisfy this check; the deck has to write the name, description or rank in a sentence, list line or table cell.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 4, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 87": { + "description": "States the share-weighted average retirement age for 2025, with Men+ and Women+ weighted equally, as 59.9 years (acceptable range 59.8 to 60.0).", + "justification": "Per the prompt: \"Slide 5 charts the main reasons for retiring by gender and names the reasons for which the women's share is higher than the men's, charts the average retirement age by reason for 2023 and 2025; it ranks the reasons by 2023 age and gives the share-weighted average age for 2025.\" Weights are the June 2025 shares of each reason (Retirement_Income_Chartbook.pptx, slide 4) applied to the 2025 ages (Retirement_Income_Chartbook.pptx, slide 5) and divided by the sum of the shares of the group. Men+ gives 60.04 and Women+ gives 59.81; with equal weight on both gender groups, as Evidence_Reporting_Standard.docx, section 5, states, the average is 59.92. The share reads carry 0.3 and the age reads 0.1; carried through the weights they move the average by up to about 0.1, so the range is 59.8 to 60.0. The criterion also requires Men+ and Women+ weighted equally: an average stated for one group only, such as the Women+ value 59.8 or the Men+ value 60.0, does not meet it, and a simple mean of the six ages (59.35) lies outside. A value shown as a chart data label, a table cell or a sentence counts as stated.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 88": { + "description": "Lists on slide 6 the Statistics Canada (2022) infographic Income in retirement: Expectations versus reality with Catalogue no. 11-627-M, and names slide 2 as the slide that uses it.", + "justification": "Per the prompt: \"Slide 6 lists the sources in APA style with hanging indents and italic titles, naming the slides that use each.\" Source line printed on Retirement_Income_Chartbook.pptx, slide 3 (Plate 2), the plate behind slide 2.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 89": { + "description": "Lists on slide 6 the Statistics Canada (2025) table Population in core housing need by selected sociocultural characteristics, economic family structure and gender with Table 39-10-0048-01, and names slide 3 as the slide that uses it.", + "justification": "Per the prompt: \"Slide 6 lists the sources in APA style with hanging indents and italic titles, naming the slides that use each.\" Source line printed on Housing_and_Work_Databook.xlsx, sheets Housing_65_Plus and Housing_Groups.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 90": { + "description": "Lists on slide 6 Uppal, S., Etmanski, B., Hardy, V., & LaRochelle-C\u00f4t\u00e9, S. (2026), Retirement and post-retirement employment among older Canadians, Insights on Canadian Society, Catalogue no. 75-006-X, and names slides 4 and 5 as the slides that use it.", + "justification": "Per the prompt: \"Slide 6 lists the sources in APA style with hanging indents and italic titles, naming the slides that use each.\" Source line printed on the plates of Retirement_Income_Chartbook.pptx, slides 4 and 5 (Plates 3 and 4), and of Housing_and_Work_Databook.xlsx, sheets Work_After_Retirement, Debt, Class_of_Worker, Regression_Summary and Provinces.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 91": { + "description": "Formats every source entry on slide 6 with a hanging indent: the first line starts at the left margin and the following lines are indented.", + "justification": "Per the prompt: \"Slide 6 lists the sources in APA style with hanging indents and italic titles, naming the slides that use each.\" The hanging indent is visible in the rendered list.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 92": { + "description": "Sets in italics the infographic title Income in retirement: Expectations versus reality, the table title Population in core housing need by selected sociocultural characteristics, economic family structure and gender, and the journal name Insights on Canadian Society in the source entries on slide 6.", + "justification": "Per the prompt: \"Slide 6 lists the sources in APA style with hanging indents and italic titles, naming the slides that use each.\" The italic titles are visible in the rendered list.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 93": { + "description": "Places under each chart on slide 2 a note line that begins with the superscript number shown after that chart's title and cites Statistics Canada (2022).", + "justification": "Per the prompt: \"Give each chart a numbered note line with a superscript marker that cites its source.\" Evidence_Reporting_Standard.docx, section 6: each chart carries a numbered note line below it that begins with a superscript number matching the number after the chart title. The source citation follows the author and year printed on the plates.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 94": { + "description": "Places under each chart on slide 3 a note line that begins with the superscript number shown after that chart's title and cites Statistics Canada (2025).", + "justification": "Per the prompt: \"Give each chart a numbered note line with a superscript marker that cites its source.\" Evidence_Reporting_Standard.docx, section 6: each chart carries a numbered note line below it that begins with a superscript number matching the number after the chart title. The source citation follows the author and year printed on the plates.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 95": { + "description": "Places under each chart on slide 4 a note line that begins with the superscript number shown after that chart's title and cites Uppal et al. (2026).", + "justification": "Per the prompt: \"Give each chart a numbered note line with a superscript marker that cites its source.\" Evidence_Reporting_Standard.docx, section 6: each chart carries a numbered note line below it that begins with a superscript number matching the number after the chart title. The source citation follows the author and year printed on the plates.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 96": { + "description": "Places under each chart on slide 5 a note line that begins with the superscript number shown after that chart's title and cites Uppal et al. (2026).", + "justification": "Per the prompt: \"Give each chart a numbered note line with a superscript marker that cites its source.\" Evidence_Reporting_Standard.docx, section 6: each chart carries a numbered note line below it that begins with a superscript number matching the number after the chart title. The source citation follows the author and year printed on the plates.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 97": { + "description": "Cites Statistics Canada (2022), the source of the slide 2 findings, in every sentence and every list line on slide 2 that states a finding, in APA author-date form, parenthetical or narrative.", + "justification": "Per the prompt: \"Cite every claim\". Evidence_Reporting_Standard.docx, section 1: the source is cited where the claim is made; footnote 1: APA format, seventh edition. The slide 2 findings come from Retirement_Income_Chartbook.pptx, slide 3 (Plate 2), whose source line names Statistics Canada (2022). A parenthetical citation such as (Statistics Canada, 2022) and a narrative citation such as Statistics Canada (2022) both count; a citation to another source does not. Sentences in text boxes and key finding boxes and lines of a list are covered; chart titles, axis text and note lines are not.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 98": { + "description": "Cites Statistics Canada (2025), the source of the slide 3 findings, in every sentence and every list line on slide 3 that states a finding, in APA author-date form, parenthetical or narrative.", + "justification": "Per the prompt: \"Cite every claim\". Evidence_Reporting_Standard.docx, section 1: the source is cited where the claim is made; footnote 1: APA format, seventh edition. The slide 3 findings come from Housing_and_Work_Databook.xlsx, sheets Housing_65_Plus and Housing_Groups, whose source line names Statistics Canada (2025). A parenthetical citation such as (Statistics Canada, 2025) and a narrative citation such as Statistics Canada (2025) both count; a citation to another source does not. Sentences in text boxes and key finding boxes and lines of a list are covered; chart titles, axis text and note lines are not.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 99": { + "description": "Cites Uppal et al. (2026), the source of the slide 4 findings, in every sentence and every list line on slide 4 that states a finding, in APA author-date form, parenthetical or narrative.", + "justification": "Per the prompt: \"Cite every claim\". Evidence_Reporting_Standard.docx, section 1: the source is cited where the claim is made; footnote 1: APA format, seventh edition. The slide 4 findings come from Housing_and_Work_Databook.xlsx, sheets Work_After_Retirement, Debt, Class_of_Worker, Regression_Summary and Provinces, whose source line names Uppal et al. (2026). A parenthetical citation such as (Uppal et al., 2026) and a narrative citation such as Uppal et al. (2026) both count; a citation to another source does not. Sentences in text boxes and key finding boxes and lines of a list are covered; chart titles, axis text and note lines are not.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 100": { + "description": "Cites Uppal et al. (2026), the source of the slide 5 findings, in every sentence and every list line on slide 5 that states a finding, in APA author-date form, parenthetical or narrative.", + "justification": "Per the prompt: \"Cite every claim\". Evidence_Reporting_Standard.docx, section 1: the source is cited where the claim is made; footnote 1: APA format, seventh edition. The slide 5 findings come from Retirement_Income_Chartbook.pptx, slides 4 and 5 (Plates 3 and 4), whose source line names Uppal et al. (2026). A parenthetical citation such as (Uppal et al., 2026) and a narrative citation such as Uppal et al. (2026) both count; a citation to another source does not. Sentences in text boxes and key finding boxes and lines of a list are covered; chart titles, axis text and note lines are not.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 101": { + "description": "Cites Uppal et al. (2026) in the note or the title of the slide 4 regression table.", + "justification": "Per the prompt: \"Cite every claim\". Evidence_Reporting_Standard.docx, section 1: every figure, table and statement in a briefing rests on a published source, and the source is cited where the claim is made. The predicted probabilities come from Housing_and_Work_Databook.xlsx, sheet Regression_Summary, whose source line names Uppal et al. (2026). A parenthetical or narrative citation in the table note or the table title counts.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 102": { + "description": "Spells out every acronym used in the deck at its first use, with the acronym following in brackets.", + "justification": "Per the prompt: \"spell out acronyms at first use\". Evidence_Reporting_Standard.docx, section 1: acronyms are spelled out at first use and the acronym follows in brackets. A shortened unit such as pp counts as an acronym; the cell mark n/a that the prompt prescribes and the quality letter M of the plates do not.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 103": { + "description": "Describes every relationship between variables with associative or descriptive wording, such as is associated with or is higher for, in place of the causal terms because, leads to, driven by, results in and due to.", + "justification": "Per the prompt: \"avoid causal wording\". Evidence_Reporting_Standard.docx, section 7, lists words that attribute cause (because, leads to, driven by, results in, due to).", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 104": { + "description": "Reports percentages and percentage-point values to one decimal place, and per-year changes to two decimal places.", + "justification": "Evidence_Reporting_Standard.docx, section 2: values are reported to one decimal place for percentages. Evidence_Reporting_Standard.docx, footnote 4: a change stated per year is given to two decimal places.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 105": { + "description": "Sets the title of every slide in white text on a dark purple band.", + "justification": "Per the prompt: \"Follow the attached template\" (formatting_aesthetics_template.pptx). formatting_aesthetics_template.pptx, slide 1, sets the title in white on a purple band (hex 5B2C6F), and slide 2, the content slide, does the same in a band of 0.55 inches at the top edge.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 4, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 106": { + "description": "Places a grey horizontal line near the bottom edge of every slide, running from the left margin to the right margin.", + "justification": "Per the prompt: \"Follow the attached template\" (formatting_aesthetics_template.pptx). formatting_aesthetics_template.pptx, slides 1 and 2: a grey footer line (hex 999999) runs from 0.5 inches to 12.83 inches at 7.0 inches, the full width between the margins.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 107": { + "description": "Shows the page number of every slide in white text on a dark purple box.", + "justification": "Per the prompt: \"Follow the attached template\" (formatting_aesthetics_template.pptx). formatting_aesthetics_template.pptx, slides 1 and 2: the page number sits in white on a purple box (hex 5B2C6F) at the right end of the footer line.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 4, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 108": { + "description": "Places the page number box of every slide in the bottom right corner, at the right end of the footer line.", + "justification": "Per the prompt: \"Follow the attached template\" (formatting_aesthetics_template.pptx). formatting_aesthetics_template.pptx, slides 1 and 2: the page number box sits at 12.4 inches from the left and 7.1 inches from the top, under the right end of the footer line.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 109": { + "description": "Sets all slide text, chart text and table text in Arial.", + "justification": "Per the prompt: \"Follow the attached template\" (formatting_aesthetics_template.pptx). formatting_aesthetics_template.pptx uses Arial throughout.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 110": { + "description": "Draws the chart series fills and the table body cell fills of slides 2 to 5 from the template palette, dark purple, light blue, grey, white and light grey, with dark purple and light blue among the chart series colours.", + "justification": "Per the prompt: \"Follow the attached template\" (formatting_aesthetics_template.pptx). formatting_aesthetics_template.pptx, slide 2: the chart uses light blue (hex AED6F1) and dark purple (hex 5B2C6F); the table uses purple, white and light grey (hex E6E6E6); the footer line is grey (hex 999999), and a neutral grey series counts as grey. Light blue is also a palette colour for table fills, for example shaded cells.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 4, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 111": { + "description": "Carries on each of slides 2 to 5 a key finding box with light grey fill and a dark purple outline, as the template does.", + "justification": "Per the prompt: \"Follow the attached template\" (formatting_aesthetics_template.pptx). formatting_aesthetics_template.pptx, slide 2: the key finding box has a light grey fill (hex E6E6E6) and a purple outline (hex 5B2C6F).", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 4, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 112": { + "description": "Sets the header cells of the slide 4 table in white text on dark purple fill.", + "justification": "Per the prompt: \"Follow the attached template\" (formatting_aesthetics_template.pptx). formatting_aesthetics_template.pptx, slide 2: the table header is white text on purple fill (hex 5B2C6F).", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 4, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 113": { + "description": "Gives the value axis of every chart on slides 2 to 5 an axis title that names the unit: percent, percentage points or years.", + "justification": "Per the prompt: \"Follow the attached template and evidence reporting standard\". Evidence_Reporting_Standard.docx, section 6: a value axis carries a title that names the unit.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 114": { + "description": "Provides a legend or direct labels on every chart with two or more series, naming each series.", + "justification": "Evidence_Reporting_Standard.docx, section 6: a chart with more than one series carries a legend or direct labels.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 115": { + "description": "Shows data labels on every chart of slides 2 to 5.", + "justification": "Per the prompt: \"build every chart as an editable PowerPoint chart with data labels\". Evidence_Reporting_Standard.docx, section 6, repeats the requirement.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 116": { + "description": "Numbers the chart titles on each of slides 2 to 5 in the order of the charts, starting at 1.", + "justification": "Evidence_Reporting_Standard.docx, section 6: the number after each chart title is matched by the note line below the chart; footnote 13: chart title numbers run in the order of the charts on the slide.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 117": { + "description": "Starts the value axis of every chart on slides 2 to 5 in which bar or column length carries the value at zero.", + "justification": "Evidence_Reporting_Standard.docx, section 6: bar and column charts start at zero. Bar and column length encodes the value. Line and marker charts, such as the age chart on a 54 to 62 axis of the plate, are outside this check.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 118": { + "description": "Keeps every data label of the charts on slide 2 separated from the other labels, from the axis text and from the chart edge.", + "justification": "Per the prompt: \"build every chart as an editable PowerPoint chart with data labels\". Evidence_Reporting_Standard.docx, section 6: text in charts stays inside its shape and is set at a readable size. A data label that overlaps another label, the axis text or the chart edge cannot be read, which is the common presentation standard for labelled charts.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 119": { + "description": "Keeps every data label of the charts on slide 3 separated from the other labels, from the axis text and from the chart edge.", + "justification": "Per the prompt: \"build every chart as an editable PowerPoint chart with data labels\". Evidence_Reporting_Standard.docx, section 6: text in charts stays inside its shape and is set at a readable size. A data label that overlaps another label, the axis text or the chart edge cannot be read, which is the common presentation standard for labelled charts.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 120": { + "description": "Keeps every data label of the charts on slide 4 separated from the other labels, from the axis text and from the chart edge.", + "justification": "Per the prompt: \"build every chart as an editable PowerPoint chart with data labels\". Evidence_Reporting_Standard.docx, section 6: text in charts stays inside its shape and is set at a readable size. A data label that overlaps another label, the axis text or the chart edge cannot be read, which is the common presentation standard for labelled charts.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 121": { + "description": "Keeps every data label of the charts on slide 5 separated from the other labels, from the axis text and from the chart edge.", + "justification": "Per the prompt: \"build every chart as an editable PowerPoint chart with data labels\". Evidence_Reporting_Standard.docx, section 6: text in charts stays inside its shape and is set at a readable size. A data label that overlaps another label, the axis text or the chart edge cannot be read, which is the common presentation standard for labelled charts.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 122": { + "description": "Keeps all text of every slide inside its shape and inside the slide boundary.", + "justification": "Evidence_Reporting_Standard.docx, section 6: text stays inside its shape. Judged from the rendered slide: a line that crosses the border of its shape or of the slide fails the criterion, even when the rest of the slide fits.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 123": { + "description": "Places the charts, the table and the text boxes of slide 4 in separate regions of the slide.", + "justification": "Per the prompt, slide 4 carries a combination chart, a class of worker chart and a table of model results (\"Slide 4 charts working after retirement by gender for 2016 and 2023 as columns with the gender gap as a line on a secondary axis and gives the change in the gap, charts the 2023 class of worker of the previously retired, gives the widest gap between the three family debt tiers and names the provinces that differ from Ontario.\" \"It also tabulates the predicted probabilities for all ten characteristics across the three regression models under one merged model header, shades cells only when their plate markers are filled and their predicted probabilities are at least 10.0%, marks untested cells n/a, explains both shading conditions in a table note, and names the characteristics meeting both conditions in every model that tests them.\"). Evidence_Reporting_Standard.docx, section 6: text stays inside its shape. Elements that overlap hide each other, so the common presentation standard keeps each element in its own region.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 124": { + "description": "Sets all text in the charts, tables and notes of slides 2 to 5, including data labels, axis text, legends and table text, at 9 point or larger.", + "justification": "Evidence_Reporting_Standard.docx, section 6: text in charts, tables and notes is set at 9 point or larger. Other text, such as a subtitle on the title page, is outside this check. Font sizes are set in the slide shapes and in the chart definitions; both are read from the file.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 125": { + "description": "Gives the titles of slides 2 to 6 the same position on the slide.", + "justification": "Per the prompt: \"Follow the attached template\" (formatting_aesthetics_template.pptx). formatting_aesthetics_template.pptx, slide 2, the content slide, places the title in the purple band at the top edge, at the same place on every content slide.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 126": { + "description": "Sets the title of every slide at 24 point bold, as the template does.", + "justification": "Per the prompt: \"Follow the attached template\" (formatting_aesthetics_template.pptx). formatting_aesthetics_template.pptx, slide 1, sets the title in the purple band at 24 point bold, and slide 2, the content slide, sets its title at 24 point bold as well. A smaller or larger title size on any slide fails.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 127": { + "description": "Sets the title of every chart on slides 2 to 5 at 16 point bold, as the template does.", + "justification": "Per the prompt: \"Follow the attached template\" (formatting_aesthetics_template.pptx). formatting_aesthetics_template.pptx, slide 2: the chart title above the chart is set at 16 point bold, with the superscript note number after it. Chart titles are read from the slide shapes or, where the title is part of the chart, from the chart definition.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 128": { + "description": "Sets every numbered chart note line on slides 2 to 5 in 10 point italic, as the template does.", + "justification": "Per the prompt: \"Follow the attached template\" (formatting_aesthetics_template.pptx). formatting_aesthetics_template.pptx, slide 2: the note line below the chart, which begins with the superscript note number, is set in 10 point italic grey text. Font sizes are read from the slide shapes; a note line at another size fails.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 129": { + "description": "Opens the text of every key finding box with the label Key finding, in the singular or the plural, as the template does.", + "justification": "Per the prompt: \"Follow the attached template\" (formatting_aesthetics_template.pptx). formatting_aesthetics_template.pptx, slide 2: the text of the key finding box begins with the label \"Key finding:\" and then states the finding. A box that opens with another heading or directly with the finding fails.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 130": { + "description": "Shows Women+ and Men+ in two distinct colours that stay the same in every chart of slides 3 to 5 that separates the two gender groups.", + "justification": "Evidence_Reporting_Standard.docx, section 6: Women+ and Men+ keep the same colours in every chart of a deck.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 131": { + "description": "Carries on each of slides 3, 4 and 5 the note that non-binary persons are distributed into the two gender categories.", + "justification": "Evidence_Reporting_Standard.docx, section 7: the note on non-binary persons is carried into the deck on every slide that shows gender. The plates print the note: Housing_and_Work_Databook.xlsx, sheets Housing_65_Plus, Work_After_Retirement, Class_of_Worker and Regression_Summary, and Retirement_Income_Chartbook.pptx, slide 4 (Plate 3).", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 132": { + "description": "Presents the Model 3 Women+ cell of the slide 4 regression table with a predicted probability of 8.6 percent (acceptable range 8.4 to 8.8 percent, inclusive).", + "justification": "The prompt requires predicted probabilities for all ten characteristics across the three regression models. Source: Housing_and_Work_Databook.xlsx, Regression_Summary worksheet, Plate 6, Model 3 panel, \u201cGender: Women+\u201d row, reference category Men+. The marker is at approximately 8.6 percent. Allow \u00b10.20 percentage points for the visual reading, giving an inclusive acceptable range of 8.4\u20138.8 percent. Models 1 and 2 do not test this characteristic. This criterion grades the numerical value displayed in the slide 4 table cell.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 133": { + "description": "Presents the Model 3 immigrant-status cell of the slide 4 regression table with a predicted probability of 10.8 percent (acceptable range 10.6 to 11.0 percent, inclusive).", + "justification": "The prompt requires predicted probabilities for all ten characteristics across the three regression models. Source: Housing_and_Work_Databook.xlsx, Regression_Summary worksheet, Plate 6, Model 3 panel, \u201cImmigrant status: immigrant\u201d row, reference category Canadian by birth. The marker is at approximately 10.8 percent. Allow \u00b10.20 percentage points for the visual reading, giving an inclusive acceptable range of 10.6-11.0 percent. Models 1 and 2 do not test this characteristic. This criterion grades the numerical value displayed in the slide 4 table cell.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 134": { + "description": "Presents the Model 3 widowed cell of the slide 4 regression table with a predicted probability of 6.9 percent (acceptable range 6.7 to 7.1 percent, inclusive).", + "justification": "The prompt requires predicted probabilities for all ten characteristics across the three regression models. Source: Housing_and_Work_Databook.xlsx, Regression_Summary worksheet, Plate 6, Model 3 panel, \u201cMarital status: widowed\u201d row, reference category Married. The marker is at approximately 6.9 percent. Allow \u00b10.20 percentage points for the visual reading, giving an inclusive acceptable range of 6.7-7.1 percent. Models 1 and 2 do not test this characteristic. This criterion grades the numerical value displayed in the slide 4 table cell; C58 separately grades its shading.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + } +} \ No newline at end of file diff --git a/tasks/task_9e3bdd2bdccd4164bcc792c914f59925/input/Figure_41_Map_of_Andalusi_period_settlement_in_Guadalajara.png b/tasks/task_9e3bdd2bdccd4164bcc792c914f59925/input/Figure_41_Map_of_Andalusi_period_settlement_in_Guadalajara.png new file mode 100644 index 0000000000000000000000000000000000000000..37502b15c660744345482fd13f7897ded1f3a7b7 --- /dev/null +++ b/tasks/task_9e3bdd2bdccd4164bcc792c914f59925/input/Figure_41_Map_of_Andalusi_period_settlement_in_Guadalajara.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:03b44b4e1bd4d2a533a32f82675369c9b1c59622e2ad53dfaf7464a8fb0cb879 +size 2042599 diff --git a/tasks/task_9e3bdd2bdccd4164bcc792c914f59925/input/Figure_42_Map_of_Guadalajara_after_the_Christian_conquests.png b/tasks/task_9e3bdd2bdccd4164bcc792c914f59925/input/Figure_42_Map_of_Guadalajara_after_the_Christian_conquests.png new file mode 100644 index 0000000000000000000000000000000000000000..b993cf7a14e5a1dc31aa8e5c984744e93ce9ebf7 --- /dev/null +++ b/tasks/task_9e3bdd2bdccd4164bcc792c914f59925/input/Figure_42_Map_of_Guadalajara_after_the_Christian_conquests.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:558348c8d0d3c25bd30e1261a35b7faf53141ac816ee7fe18636745a949e3554 +size 1911708 diff --git a/tasks/task_9e3bdd2bdccd4164bcc792c914f59925/input/Figure_43_Map_of_Andalusi_settlement_in_the_Malaga_region.png b/tasks/task_9e3bdd2bdccd4164bcc792c914f59925/input/Figure_43_Map_of_Andalusi_settlement_in_the_Malaga_region.png new file mode 100644 index 0000000000000000000000000000000000000000..190d51f7449584bd9e57d4d6bef3f75f28ebf865 --- /dev/null +++ b/tasks/task_9e3bdd2bdccd4164bcc792c914f59925/input/Figure_43_Map_of_Andalusi_settlement_in_the_Malaga_region.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cd7916acc6a1ace9de804c8aa906af6dfdc95bcdaac4f4fe74be466c06c71bb6 +size 1023058 diff --git a/tasks/task_9e3bdd2bdccd4164bcc792c914f59925/input/Figure_44_Map_of_settlement_in_Malaga_after_the_Castilian_conquest.png b/tasks/task_9e3bdd2bdccd4164bcc792c914f59925/input/Figure_44_Map_of_settlement_in_Malaga_after_the_Castilian_conquest.png new file mode 100644 index 0000000000000000000000000000000000000000..b646a61fc46d03aab4786d12ee75572391eb10f5 --- /dev/null +++ b/tasks/task_9e3bdd2bdccd4164bcc792c914f59925/input/Figure_44_Map_of_settlement_in_Malaga_after_the_Castilian_conquest.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:70b635fa5e30405581b1a047e19d06b6f519ad1b742de50bb2186b9a21274a1c +size 1900971 diff --git a/tasks/task_9e3bdd2bdccd4164bcc792c914f59925/input/Plate_41_Map_showing_Andalusi_settlement_in_the_northwestern_NasridCastilian_frontier.png b/tasks/task_9e3bdd2bdccd4164bcc792c914f59925/input/Plate_41_Map_showing_Andalusi_settlement_in_the_northwestern_NasridCastilian_frontier.png new file mode 100644 index 0000000000000000000000000000000000000000..577305661e515a79adabad5dacf699e6abbb4694 --- /dev/null +++ b/tasks/task_9e3bdd2bdccd4164bcc792c914f59925/input/Plate_41_Map_showing_Andalusi_settlement_in_the_northwestern_NasridCastilian_frontier.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f4bf5448a9640a4ccfba44d9cb60762f9a1986d746168ad6347c10aa01f72eab +size 2186946 diff --git a/tasks/task_9e3bdd2bdccd4164bcc792c914f59925/input/Plate_42_Map_showing_settlement_in_the_territory_of_Granada_after_the_Castilian_conquest.png b/tasks/task_9e3bdd2bdccd4164bcc792c914f59925/input/Plate_42_Map_showing_settlement_in_the_territory_of_Granada_after_the_Castilian_conquest.png new file mode 100644 index 0000000000000000000000000000000000000000..f866f299b5a37ee351c036cc015b47431c0ca8c1 --- /dev/null +++ b/tasks/task_9e3bdd2bdccd4164bcc792c914f59925/input/Plate_42_Map_showing_settlement_in_the_territory_of_Granada_after_the_Castilian_conquest.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:02736333c5c9f82be3460bf08acf14de9a075e152ba7c76865f2552621b02b3b +size 1899232 diff --git a/tasks/task_9e3bdd2bdccd4164bcc792c914f59925/input/Presentation_formatting_guidelines.pdf b/tasks/task_9e3bdd2bdccd4164bcc792c914f59925/input/Presentation_formatting_guidelines.pdf new file mode 100644 index 0000000000000000000000000000000000000000..6f7001a35b1b8c3890c7d8f3ac06bc6c31a004f8 --- /dev/null +++ b/tasks/task_9e3bdd2bdccd4164bcc792c914f59925/input/Presentation_formatting_guidelines.pdf @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:52fba173da946c5c96bcabcb64cd097f6b183e18182c81390cad37e0904a496d +size 607683 diff --git a/tasks/task_9e3bdd2bdccd4164bcc792c914f59925/input/Presentation_prep.pdf b/tasks/task_9e3bdd2bdccd4164bcc792c914f59925/input/Presentation_prep.pdf new file mode 100644 index 0000000000000000000000000000000000000000..4038ba82797281a90177cb8f406ad00e0808649f --- /dev/null +++ b/tasks/task_9e3bdd2bdccd4164bcc792c914f59925/input/Presentation_prep.pdf @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7a3ab9d656fb820d9ff95b10b6c3115f1102e880c6dcc6ed0b0c63f3d6e51245 +size 1011475 diff --git a/tasks/task_9e3bdd2bdccd4164bcc792c914f59925/metadata.json b/tasks/task_9e3bdd2bdccd4164bcc792c914f59925/metadata.json new file mode 100644 index 0000000000000000000000000000000000000000..b735fb12de0e5ad53a5f6b640450ff168df8873c --- /dev/null +++ b/tasks/task_9e3bdd2bdccd4164bcc792c914f59925/metadata.json @@ -0,0 +1,12 @@ +{ + "TaskID": "task_9e3bdd2bdccd4164bcc792c914f59925", + "Vertical": "Education", + "Domain": "Education", + "Role": "Historian", + "Task Goal": "Document how castle settlements in Guadalajara changed after the Christian conquest of Iberia.", + "Prompt": "Create a three-slide PPTX presentation to document post-Christian settlement changes in Iberia.\n\nTitle Slide 1: Settlement changes after Christian conquest in Guadalajara\n\nDetermine the values for W, X, Y, Z, and B, then add the following sentences to the slide:\n“Of the W castles that existed during the Andalusi period, X became villas, Y became feudal castles, and Z are assumed to be destroyed (no longer on the map). There are B new castle sites following the conquest.” \nA site “became” something if its symbol is in the same position on the two maps. For X, count only castles that became a villa.\nCastles considered destroyed are those that are marked on the Andalusi-period map, but no castle or villa is found in the same location on the post-conquest map.\nA castle is new if it is marked on the post-conquest map, but no castle is found on the Andalusi-period map.\n\nCastles are markers that are labeled as such on the map from the Andalusi period and feudal castles on the post-conquest map. Villas are labeled as such on the post-conquest map. Disregard the marker for \"case study\".\n\nAdd a second sentence to the slide: determine the values for RA and RC, calculate R. Determine if increase or decrease needs to be used:\n“Rural settlement sites (alqueria and aldea) increased/decreased by R%, from RA to RC.”\nIf the number is unchanged, add the following sentence: \"The number of rural settlement sites (alqueria and aldea) is unchanged after the conquest.\"\nRural settlements are labeled as alqueria on the Andalusi-period map and aldea on the post-conquest map.\n\nAdd a third sentence to the slide: determine the value for PA and PC and calculate P%. Determine if increase or decrease needs to be used:\n“The number of towers increased/decreased by P%, from PA to PC.”\nIf the number is unchanged, use: \"The number of towers is unchanged after the conquest.\"\n\nOn the Andalusi-period map, both watchtowers and towers of alqueria are considered towers. On the post-conquest map, feudal towers are considered towers.\n\nCalculate R and P relative to the Andalusi-period counts and round to the nearest whole percent.\n\nInclude the coat-of-arms of Guadalajara.\n\n\nTitle Slide 2: Settlement changes after Christian conquest in Málaga \n\nDetermine the values for N, V, VA, G, GA, K, and KA, and add the following sentences to the slides. Leave all values as raw counts:\n\n“The ratio of castles during the Andalusi period to the post-conquest period is V : VA”\n“The ratio of alqueria during the Andalusi period to village sites after the conquest is G : GA. There are N sites that became a village after the conquest, from an alqueria”\n“The ratio of towers during the Andalusi period to the post-conquest period is K : KA.”\n\nOn the Andalusi-period map, include both watchtowers and the towers of alqueria in the tower count, and include only castle markers in the castle counts. If a category does not have a corresponding marker in the figure legend, assume that there are none.\n\nInclude the coat-of-arms of Málaga. \n\n\nTitle Slide 3: Settlement changes after Christian conquest in Granada\n\nDetermine the values for T, S, M, H, J, and L, and calculate the value for MM. Leave T, S, H, J, and L as raw counts. Add the following sentences to the slides:\n\n“The ratio of Christian to Islamic castles during the Andalusi period was T : S.”\n“Of the Nasrid alquerias and towers of alquerias in the Andalusi period, M (MM%) became villages after the conquest.”\n“The ratio of farmhouses, Moorish farmhouses, and villages after the conquest was H : J : L.”\n\nCalculate MM relative to the Andalusi-period counts and round to the nearest whole percent.\n\nCount Nasrid alquerias and towers of alquerias as one group, and as potential precursors to villages in the post-conquest period. A site “became” something if its marker is in the same position on the two maps. Islamic castle icons inside Border villa red circles on the Andalusi-period map should be counted.\n\nInclude the coat-of-arms of Granada.\n\nSearch coat-of-arms images on English-language Wikipedia as of October 14, 2026, 12 pm PDT. Search the region name followed by “Spain” and use the infobox image. \n\nFor all three slides, count only markers that are fully within the boundaries marked on the Andalusi-period maps. Markers touching the boundary lines from the inside count as being inside. Markers that straddle the line or touch it from the outside are not to be counted. For the post-conquest maps, align the maps so that you identify symbols in the same exact area, using the same rules. Count markers that are visible under a semi-transparent scale bar. Count every marker, even if they overlap. If two Andalusi settlements became one after the conquest, count both. Settlement icons located inside \"Case study\" circles count toward their respective settlement categories.\n\nI uploaded my prep file on all this.\nName the presentation “Post_Christian_settlement_changes_in_Iberia.pptx”.\nOmit quotation marks for all sentences you add to the slides.\nBuild the presentation from a blank file, exactly matching the specifications in the presentation guidelines.", + "Input_files": "Figure_41_Map_of_Andalusi_period_settlement_in_Guadalajara.png, Figure_42_Map_of_Guadalajara_after_the_Christian_conquests.png, Figure_43_Map_of_Andalusi_settlement_in_the_Malaga_region.png, Figure_44_Map_of_settlement_in_Malaga_after_the_Castilian_conquest.png, Plate_41_Map_showing_Andalusi_settlement_in_the_northwestern_NasridCastilian_frontier.png, Plate_42_Map_showing_settlement_in_the_territory_of_Granada_after_the_Castilian_conquest.png, Presentation_formatting_guidelines.pdf, Presentation_prep.pdf", + "All Task Files": "tasks/task_9e3bdd2bdccd4164bcc792c914f59925/input/", + "Rubric Criteria": "tasks/task_9e3bdd2bdccd4164bcc792c914f59925/rubrics.json", + "Economic Rationale": "This task requires reasoning across multiple figures in a way that benefits from dedicated geographic experience and historical rigor suitable for scholars of Iberian, medieval, Islamic, and Christian history. The output is intentionally designed to be presentation-ready and educationally useful. This type of work could be commissioned by a curriculum publisher, museum, or educational media team preparing historical geography materials from scholarly sources. The full process requires analyzing figures, compiling and reconciling facts across maps, applying precise spatial coding, verifying sources, and producing a polished reusable presentation, saving staff time that would otherwise be spent manually completing each of those steps." +} diff --git a/tasks/task_9e3bdd2bdccd4164bcc792c914f59925/rubrics.json b/tasks/task_9e3bdd2bdccd4164bcc792c914f59925/rubrics.json new file mode 100644 index 0000000000000000000000000000000000000000..afb5a010f6c97d4dd1b632eb8f22b08a2e1c1684 --- /dev/null +++ b/tasks/task_9e3bdd2bdccd4164bcc792c914f59925/rubrics.json @@ -0,0 +1,470 @@ +{ + "criterion 1": { + "description": "Outputs a three-slide .pptx file.", + "justification": "The prompt reads \"Create a three-slide PPTX presentation.....\".", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 2": { + "description": "Names the .pptx file \u201cPost_Christian_settlement_changes_in_Iberia.pptx\u201d.", + "justification": "The prompt reads: \"Name the presentation \u201cPost_Christian_settlement_changes_in_Iberia.pptx\u201d.\n", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 3": { + "description": "Formats the gradient fill of the background on all slides at 90 degrees, bottom to top, in #EA6922 in position 0%, #F0925E in position 15%, #F6BFA0 in position 32%, and #FBE5D9 in position 60%.\n", + "justification": "The prompt says: \"Build the presentation from a blank file, exactly matching the specifications in the presentation guidelines\". According to the presentation guidelines, a precision gradient fill background is to be engineered at a 90\u00b0 angle from bottom to top, anchored by a full-bleed top accent band measuring exactly 2 inches in height. The gradient stops are as follows: #EA6922 in position 0%, #F0925E in position 15%, #F6BFA0 in position 32%, and #FBE5D9 in position 60%.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 4": { + "description": "Centers the title on each slide vertically and horizontally within the 2-inch top accent band.", + "justification": "Page 3 of the formatting guidelines says titles are \"centered vertically and horizontally within the top accent band\".", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 5": { + "description": "Formats the colour of all titles in #D1D1D1.", + "justification": "The prompt says: \"Build the presentation from a blank file, exactly matching the specifications in the presentation guidelines\". According to the presentation guidelines, all titles need to be formatted in #D1D1D1.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 6": { + "description": "Formats all titles in bold Chamberi Super Display.", + "justification": "The prompt says: \"Build the presentation from a blank file, exactly matching the specifications in the presentation guidelines\". According to the presentation guidelines, all titles need to be formatted in bold Chamberi Super Display.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 7": { + "description": "Formats all titles in 44-point font.", + "justification": "The prompt says: \"Build the presentation from a blank file, exactly matching the specifications in the presentation guidelines\". According to the presentation guidelines, all titles are to be in 44-point font.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 8": { + "description": "Formats the colour of all non-title text in #002060.", + "justification": "The prompt says: \"Build the presentation from a blank file, exactly matching the specifications in the presentation guidelines\". According to the presentation guidelines, format all non-title text in #002060 at 4% transparency.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 9": { + "description": "Formats the colour of all non-title text with 4% transparency.", + "justification": "The prompt says: \"Build the presentation from a blank file, exactly matching the specifications in the presentation guidelines\". According to the presentation guidelines, format all non-title text in #002060 at 4% transparency.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 10": { + "description": "Formats all non-title text in Bierstadt.", + "justification": "The prompt says: \"Build the presentation from a blank file, exactly matching the specifications in the presentation guidelines\". According to the presentation guidelines, format all non-title text in Bierstadt font.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 11": { + "description": "Formats all non-title text in 24-point font.", + "justification": "The prompt says: \"Build the presentation from a blank file, exactly matching the specifications in the presentation guidelines\". According to the presentation guidelines, format all non-title text in 24-point font.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 12": { + "description": "Includes a full-bleed top accent band exactly 2 inches tall on all slides.", + "justification": "The prompt says: \"Build the presentation from a blank file, exactly matching the specifications in the presentation guidelines\". Page 2 of Presentation_formatting_guidelines.pdf reads: \"Precision gradient fill background engineered at a 90\u00b0 angle from bottom to top, anchored by a full-bleed top accent band measuring exactly 2 inches in height.\"", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 13": { + "description": "Includes text on the left side of every slide.", + "justification": "According to the style guide: \"...place all primary descriptive text content on the left side of the slide and complementary visual assets on the right side.\"", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 14": { + "description": "Includes the coat-of-arms photos on the right side of each slide. \n", + "justification": "According to the style guide: \"...place all primary descriptive text content on the left side of the slide and complementary visual assets on the right side.\" The visual assets are the photos of the coats of arms for each region. ", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 15": { + "description": "Includes the title \u201cSettlement changes after Christian conquest in Guadalajara\u201d on slide one.", + "justification": "The prompt says: \"Title Slide 1: Settlement changes after Christian conquest in Guadalajara\".\n", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 16": { + "description": "Includes on Slide 1 the photo of a coat of arms that includes 11 stars in the sky, one knight on horseback carrying a red banner, and four soldiers carrying spears.", + "justification": "Searching \u201cGuadalajara, Spain\u201d in English-language Wikipedia as of October 14, 2026, 12 pm PDT, leads to the Guadalajara, Spain article and its Coat of Arms image: https://en.wikipedia.org/wiki/Guadalajara,_Spain#/media/File:Coat_of_Arms_of_Guadalajara_(Spain).svg. The Coat of Arms includes 11 stars in the sky, one knight on horseback carrying a red banner, and four soldiers carrying spears.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 17": { + "description": "Includes the title \u201cSettlement changes after Christian conquest in M\u00e1laga\u201d on slide 2.", + "justification": "The prompt says: \"Title Slide 2: Settlement changes after Christian conquest in M\u00e1laga\".", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 18": { + "description": "Includes on Slide 2 the photo of a coat of arms that includes the text \u201cLA PRIMERA EN EL PELIGRO DE LA LIBERTAD\u201d along the top of a shield portraying two people praying in the top left corner.", + "justification": "Searching \u201cM\u00e1laga\u201d in English-language Wikipedia as of October 14, 2026, 12 pm PDT, leads to the M\u00e1laga article and its Coat of Arms image: https://en.wikipedia.org/wiki/M%C3%A1laga#/media/File:Coat_of_Arms_of_M%C3%A1laga.svg. The Coat of Arms includes the text \u201cLA PRIMERA EN EL PELIGRO DE LA LIBERTAD\u201d along the top of a shield portraying two people praying in the top left corner.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 19": { + "description": "Includes the title \u201cSettlement changes after Christian conquest in Granada\u201d on slide 3.", + "justification": "The prompt says:\"Title Slide 3: Settlement changes after Christian conquest in Granada\"\n", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 20": { + "description": "Includes on Slide 3 the photo of the coat of arms of Granada that includes a crown on top, a ribbon weaving around the body with the text \"GRANADA CIUDAD DE CELEB\u00c9RRIMA Y HEROICA\" on the left side and \"MUY NOBLE, MUY LEAL NOMBRADA, GRANDE\" on the right side, and an image of a royal couple, a tower, and a capsule of a poppy.", + "justification": "Searching \u201cGranada\u201d in English-language Wikipedia as of October 14, 2026, 12 pm PDT, leads to the Granada article and its Coat of Arms image: https://en.wikipedia.org/wiki/Granada#/media/File:Escudo_de_Granada_(Granada).svg. The Coat of Arms includes a crown on top, a ribbon weaving around the body with the text \"GRANADA CIUDAD DE CELEB\u00c9RRIMA Y HEROICA\" on the left side and \"MUY NOBLE, MUY LEAL NOMBRADA, GRANDE\" on the right side, and an image of a royal couple, a tower, and a capsule of a poppy.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 21": { + "description": "States in the sentence on Slide 1 that 27 castles existed during the Andalusi period (acceptable value is 27).", + "justification": "Figure_41_Map_of_Andalusi_period_settlement_in_Guadalajara.png is a greyscale map that shows the location of castles, watchtowers, towers of alqueria, alqueria (rural settlements) and rivers in the region of Guadalajara during the Andalusi period. If a grid consisting of 8 columns of equal width, labeled A-H, and 5 rows of equal height labeled 1-5 from top to bottom is placed on the map, the distribution of the castles in the cells is as follows, listing only cells that have a marker for a castle: A1:1; B1:3; F1:1; A2:1; B2:3; C2:2; D2:1; F2:3; A3:1; B3:2; C3:1; F3:1; H3:1; E4:1; G4:1; H4:1; C5:2; F5:1, for a total of 27 castles. \n", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 4, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 22": { + "description": "States in the sentence on Slide 1 that of the castles that existed during the Andalusi period, 4 became villas (acceptable value is 4).", + "justification": "Figure_41_Map_of_Andalusi_period_settlement_in_Guadalajara.png shows 27 castle markers fully inside the red boundary, counting the castle inside the Atienza case-study circle, which the prompt says counts toward its category. \nFigure_42_Map_of_Guadalajara_after_the_Christian_conquests.png shows 7 villas (castle icon inside a grey circle): Atienza, Riba de Santiuste, Sig\u00fcenza, Aragosa, Jadraque, Castej\u00f3n de Henares (east of Jadraque, south of the R\u00edo Henares), and Molina de Arag\u00f3n. The two maps are aligned using Atienza and Molina de Arag\u00f3n, which are labelled on both, and the river lines. The prompt says a site became something only if its symbol is in the same position on both maps. Four villas sit on an Andalusi castle: Atienza, Riba de Santiuste, Aragosa and Jadraque. The other three do not. Sig\u00fcenza sits on a watchtower (the nearest castle is offset to the northeast), Castej\u00f3n de Henares sits on an alquer\u00eda, and Molina de Arag\u00f3n sits on a tower of alquer\u00eda inside its case-study circle (the castle southeast of it became a feudal castle). Therefore 4 Andalusi castles became villas.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 4, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 23": { + "description": "States in the sentence on Slide 1 that of the castles that existed during the Andalusi period, 14 became feudal castles (acceptable value is 14).", + "justification": "Figure_41_Map_of_Andalusi_period_settlement_in_Guadalajara.png shows 27 castle markers fully inside the red boundary, counting the castle inside the Atienza case-study circle. Under the prompt's definitions every one of those 27 sites falls into exactly one of three groups on Figure_42_Map_of_Guadalajara_after_the_Christian_conquests.png, aligned on Atienza, Molina de Arag\u00f3n and the rivers: a villa in the same position, a feudal castle in the same position, or neither (destroyed). Four carry a villa (Atienza, Riba de Santiuste, Aragosa and Jadraque; see the villa criterion). Nine carry neither a castle nor a villa (the nine sites located in the destroyed-castles criterion: east of the Atienza label; south of Riba de Santiuste; southwest of that one, southeast of Atienza; in the watchtower cluster east of Riba de Santiuste; northeast of the Sig\u00fcenza villa site; east of that one; the eastern castle of the pair west of Sig\u00fcenza; northeast of the R\u00edo Ablanquejo label; and southwest of the R\u00edo Bullones label). The remaining 27 - 4 - 9 = 14 Andalusi castle sites carry a feudal castle marker in the same position after the conquest. Check: 4 + 14 + 9 = 27.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 4, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 24": { + "description": "States in the sentence on Slide 1 that of the castles that existed during the Andalusi period, 9 are assumed to be destroyed (acceptable value is 9).", + "justification": "Figure_41_Map_of_Andalusi_period_settlement_in_Guadalajara.png shows 27 castle markers fully inside the red boundary, counting the castle inside the Atienza case-study circle. The prompt defines a destroyed castle as one marked on the Andalusi-period map where no castle or villa is found in the same location on the post-conquest map. Aligning Figure_42_Map_of_Guadalajara_after_the_Christian_conquests.png on Atienza, Molina de Arag\u00f3n and the rivers, 4 of the 27 castles have a villa on them (Atienza, Riba de Santiuste, Aragosa, Jadraque) and 14 have a feudal castle on them. The remaining 9 have no castle or villa in the same position: the castle immediately east of the Atienza label; the castle directly south of Riba de Santiuste; the castle southwest of that one, southeast of Atienza; the castle in the watchtower cluster east of Riba de Santiuste; the castle just northeast of the Sig\u00fcenza villa site; the castle east of that one; the eastern castle of the pair that sits west of Sig\u00fcenza; the castle just northeast of the R\u00edo Ablanquejo label; and the castle southwest of the R\u00edo Bullones label. Some of these sites carry an aldea or sit next to a feudal tower after the conquest, but neither is a castle or a villa, so they still count as destroyed. Check: 4 villas + 14 feudal castles + 9 destroyed = 27.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 4, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 25": { + "description": "States in the sentence on Slide 1 that there are 11 new castle sites following the conquest (acceptable value is 11).", + "justification": "The prompt defines a new castle as a feudal castle marked on Figure_42_Map_of_Guadalajara_after_the_Christian_conquests.png with no castle in the same position on Figure_41_Map_of_Andalusi_period_settlement_in_Guadalajara.png, counted inside the Figure 4.1 red boundary after aligning the maps on Atienza, Molina de Arag\u00f3n and the rivers. Figure 4.2 shows 25 feudal castle markers inside that aligned boundary. Of those, 14 sit on Andalusi castle sites (the feudal-castles criterion: 27 Andalusi castles less 4 that carry a villa and 9 that carry neither). The other 25 - 14 = 11 feudal castles stand where Figure 4.1 shows no castle (several sit on former alquer\u00eda, tower or empty positions), so there are 11 new castle sites.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 4, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 26": { + "description": "Includes on Slide 1 the sentences: \"Of the __ castles that existed during the Andalusi period, __ became villas, __ became feudal castles, and __ are assumed to be destroyed (no longer on the map). There are __ new castle sites following the conquest.\", word for word, with a number in each blank. Any numbers pass this criterion; each value is graded by its own criterion.", + "justification": "The prompt says: \"......add the following sentences to the slide:\n\u201cOf the W castles that existed during the Andalusi period, X became villas, Y became feudal castles, and Z are assumed to be destroyed (no longer on the map). There are B new castle sites following the conquest.\u201d ", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 27": { + "description": "States in the sentence on Slide 1 that there were 44 rural settlement sites (alqueria) (acceptable value is 44).", + "justification": "Figure_41_Map_of_Andalusi_period_settlement_in_Guadalajara.png is a greyscale map that shows the location of castles, watchtowers, towers of alqueria, alqueria (rural settlements) and rivers in the region of Guadalajara during the Andalusi period. If a grid consisting of 8 columns of equal width, labeled A-H, and 5 rows of equal height labeled 1-5 from top to bottom is placed on the map, the distribution of the alqueria in the cells is as follows, listing only cells that have a marker for an alqueria (cell:number of alqueria): B1:1; C1:4; B2:8; C2:6; D2:7; A3:1; B3;3; C3:1; D3:2; E4:3; F4:1; G4:1; G5:3; H5:3, For a total of 44 alqueria.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 4, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 28": { + "description": "States in the sentence on Slide 1 that the number of rural settlement sites increased to 97 aldea (acceptable value is 97).", + "justification": "Figure_42_Map_of_Guadalajara_after_the_Christian_conquests.png is a greyscale map that shows an overlapping area of the Guadalajara region after the conquest with markers for villas, feudal castles, feudal towers and aldea (rural settlements). If a grid consisting of 8 columns of equal width, labeled A-H, and 5 rows of equal height labeled 1-5 from top to bottom is placed on the map, the distribution of aldea in the cells is as follows, listing only cells that have a marker for aldea (cell:number of aldea): A1:5; B1:8; C1:4; A2:1; B2:14; C2:10; D2:5; E2:1; G2:2; B3:1; C3:4; D3:4; E3:3; F3:4; G3:4; E4:2; F4:2; G4:8; H4:6; F5:3; G5:3; H5:3, for a total of 97 aldea.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 4, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 29": { + "description": "States in the sentence on Slide 1 that rural settlement sites (alqueria and aldea) increased by 120% (only the exact percentage is acceptable).", + "justification": "The prompt asks the user to count the number of alqueria during the Andalusi period, the number of aldea after the conquest, and calculate the percent increase or decrease. \n\nThe number of alqueria is counted on Figure_41_Map_of_Andalusi_period_settlement_in_Guadalajara.png. Figure_41_Map_of_Andalusi_period_settlement_in_Guadalajara.png is a greyscale map that shows the location of castles, watchtowers, towers of alqueria, alqueria (rural settlements) and rivers in the region of Guadalajara during the Andalusi period. If a grid consisting of 8 columns of equal width, labeled A-H, and 5 rows of equal height labeled 1-5 from top to bottom is placed on the map, the distribution of the alqueria in the cells is as follows, listing only cells that have a marker for an alqueria (cell:number of alqueria): B1:1; C1:4; B2:8; C2:6; D2:7; A3:1; B3;3; C3:1; D3:2; E4:3; F4:1; G4:1; G5:3; H5:3, For a total of 44 alqueria. \n\nThe number of aldea is determined from Figure_42_Map_of_Guadalajara_after_the_Christian_conquests.png. Figure_42_Map_of_Guadalajara_after_the_Christian_conquests.png is a greyscale map that shows an overlapping area of the Guadalajara region after the conquest with markers for villas, feudal castles, feudal towers and aldea (rural settlements). If a grid consisting of 8 columns of equal width, labeled A-H, and 5 rows of equal height labeled 1-5 from top to bottom is placed on the map, the distribution of aldea in the cells is as follows, listing only cells that have a marker for aldea (cell:number of aldea): A1:5; B1:8; C1:4; A2:1; B2:14; C2:10; D2:5; E2:1; G2:2; B3:1; C3:4; D3:4; E3:3; F3:4; G3:4; E4:2; F4:2; G4:8; H4:6; F5:3; G5:3; H5:3, for a total of 97 aldea. \n\nThe number of rural sites, therefore, increased from 44 to 97. To calculate the percent increase relative to the Andalusi period, the difference between the two numbers is calculated (44-97=-53), divided by the Andalusi count (53:44=1.2045), multiplied by 100, and rounded to the nearest whole percent. Therefore, there was a 120% (only the exact percentage is acceptable) increase in rural settlements after the conquest.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 5, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 30": { + "description": "Includes on Slide 1 the sentence: \"Rural settlement sites (alqueria and aldea) increased by __%, from __ to __.\", word for word, with a number in each blank. Any numbers pass this criterion; each value is graded by its own criterion.", + "justification": "The prompt instructs the user to add the following sentence to the slide: \"Rural settlement sites (alqueria and aldea) increased/decreased by R%, from RA to RC.\", and determine if increase or decrease needs to be used in the sentence. \n", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 31": { + "description": "States on Slide 1 that the number of towers is unchanged after the conquest.", + "justification": "The prompt instructs the user to add the following sentence to the slide if the number of towers is unchanged from the Andalusi period to the post-conquest period: \"The number of towers is unchanged after the conquest.\" \n\nThe number of towers during the Andalusi period is counted on Figure_41_Map_of_Andalusi_period_settlement_in_Guadalajara.png. This is a greyscale map that shows the location of castles, watchtowers, towers of alqueria, alqueria (rural settlements) and rivers in the region of Guadalajara during the Andalusi period. Both towers of alqueria and watchtowers are counted under \"towers\". If a grid consisting of 8 columns of equal width, labeled A-H, and 5 rows of equal height labeled 1-5 from top to bottom is placed on the map, the distribution of towers of alqueria and watchtowers in the cells is as follows, listing only cells that have a marker for a tower (cell:number of towers): A1:2; B1:3; C1:4; D1:2; E1:1; B2:1; C2:8; D2:2; A3:2; D3:1; E3:1; F3:1; F4:1; G4:1; H4:1, for a total of 31 towers.\n\nThe number of towers after the conquest is determined from Figure_42_Map_of_Guadalajara_after_the_Christian_conquests.png. This is a greyscale map that shows an overlapping area of the Guadalajara region after the conquest with markers for villas, feudal castles, feudal towers and aldea (rural settlements). If a grid consisting of 8 columns of equal width, labeled A-H, and 5 rows of equal height labeled 1-5 from top to bottom is placed on the map, the distribution of feudal towers in the cells is as follows, listing only cells that have a marker for feudal towers (cell:number of feudal towers): A1:1; B1:1; C1:3; B2:1; C2:6; D2:4; F2:1; H2:1; A3:1; D3:2; E3:2; F3:2; E4:1; G4:2; H4:1; F5:1; H5:1, for a total of 31 towers.\n\nThere is an equal number of towers on both maps.\n\n", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 4, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 32": { + "description": "States in a sentence on Slide 2 that the number of castles during the Andalusi period is 12 (acceptable value is 12).", + "justification": "The number of castles is determined from Figure_43_Map_of_Andalusi_settlement_in_the_Malaga_region.png. This is a greyscale map that shows the location of castles, watchtowers, towers of alqueria, alqueria (rural settlements) and rivers in the region of Malaga during the Andalusi period. If a grid consisting of 9 columns of equal width, labeled A-I, and 6 rows of equal height labeled 1-6 from top to bottom is placed on the map, the distribution of the castles in the cells is as follows, listing only cells that have a marker for them (cell:number of castles): B1:1; G1:1; F2:1; H2:1; B3:1; C3:1; C4:1; E4:1; G4:1; B5:1; C5:1; F6:1, for a total of 12 castles.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 4, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 33": { + "description": "States in a sentence on Slide 2 that the number of castles after the conquest is 0 (acceptable value is 0).", + "justification": "The number of castles is to be determined from Figure_44_Map_of_settlement_in_Malaga_after_the_Castilian_conquest.png This is a greyscale map that shows the location of cities, villas, villages and rivers in the region of Malaga after the conquest. The map does not show castles in the region, therefore the number is 0.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 4, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 34": { + "description": "Includes on Slide 2 the sentence: \"The ratio of castles during the Andalusi period to the post-conquest period is __ : __\", word for word, with a number in each blank. Any numbers pass this criterion; each value is graded by its own criterion.", + "justification": "The prompt instructs the user to include the following sentence on the slide: \u201cThe ratio of castles during the Andalusi period to the post-conquest period is V : VA\u201d, where V is the number of castles during the Andalusi period, and VA is the number after the conquest.\n\n", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 35": { + "description": "States in a sentence on Slide 2 that the number of alqueria during the Andalusi period was 35 (acceptable value is 35).", + "justification": "The number of alqueria is determined from Figure_43_Map_of_Andalusi_settlement_in_the_Malaga_region.png. This is a greyscale map that shows the location of cities, castles, watchtowers, towers of alqueria, alqueria (rural settlements) and rivers in the region of Malaga during the Andalusi period. If a grid consisting of 9 columns of equal width, labeled A-I, and 6 rows of equal height labeled 1-6 from top to bottom is placed on the map, the distribution of the alqueria in the cells is as follows, listing only cells that have a marker for an alqueria (cell:number of alqueria): B1:3; C1:1; A2:2; B2:2; E2:1; A3:2; B3:1; C3:6; D3:1; A4:1; D5:1; E5:1; F5:1; G5:1; B6:3; C6:4; D6:2; F6:1; I6:1, for a total of 35 alqueria.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 4, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 36": { + "description": "States in a sentence on Slide 2 that the number of village sites after the conquest was 19 (acceptable value is 19).", + "justification": "The number of village sites is determined from Figure_44_Map_of_settlement_in_Malaga_after_the_Castilian_conquest.png This is a greyscale map that shows the location of cities, villas, villages and rivers in the region of Malaga after the conquest. If a grid consisting of 9 columns of equal width, labeled A-I, and 6 rows of equal height labeled 1-6 from top to bottom is placed on the map, the distribution of village sites is as follows, listing only cells that have a marker for a village (cell:number of villages): B1:2; A2:1; B2:1; E2:1; A3:1; C3:2; D3:1; A4:1; G4:1; D5:1; E5:1; F5:1; G5:1; B6:2; C6:1; I6:1, for a total of 19 villages. \n", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 4, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 37": { + "description": "States in a sentence on Slide 2 that of the alqueria during the Andalusi period, 18 became villages after the conquest (acceptable value is 18).", + "justification": "The number of alqueria is determined from Figure_43_Map_of_Andalusi_settlement_in_the_Malaga_region.png. This is a greyscale map that shows the location of cities, castles, watchtowers, towers of alqueria, alqueria (rural settlements) and rivers in the region of Malaga during the Andalusi period. If a grid consisting of 9 columns of equal width, labeled A-I, and 6 rows of equal height labeled 1-6 from top to bottom is placed on the map, the distribution of the alqueria in the cells is as follows, listing only cells that have a marker for an alqueria (cell:number of alqueria): B1:3; C1:1; A2:2; B2:2; E2:1; A3:2; B3:1; C3:6; D3:1; A4:1; D5:1; E5:1; F5:1; G5:1; B6:3; C6:4; D6:2; F6:1; I6:1, for a total of 35 alqueria.\n\nThe number of village sites is determined from Figure_44_Map_of_settlement_in_Malaga_after_the_Castilian_conquest.png This is a greyscale map that shows the location of cities, villas, villages and rivers in the region of Malaga after the conquest. If a grid consisting of 9 columns of equal width, labeled A-I, and 6 rows of equal height labeled 1-6 from top to bottom is placed on the map, the distribution of village sites is as follows, listing only cells that have a marker for a village (cell:number of villages): B1:2; A2:1; B2:1; E2:1; A3:1; C3:2; D3:1; A4:1; G4:1; D5:1; E5:1; F5:1; G5:1; B6:2; C6:1; I6:1, for a total of 19 villages. Only the village in cell G4 was not an alqueria in the Andalusi period; therefore, 18 alqueria became villages after the conquest.\n", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 4, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 38": { + "description": "Includes on Slide 2 the sentences: \"The ratio of alqueria during the Andalusi period to village sites after the conquest is __ : __. There are __ sites that became a village after the conquest, from an alqueria\", word for word, with a number in each blank. Any numbers pass this criterion; each value is graded by its own criterion.", + "justification": "The prompt instructs the user to add the following sentence to the slide: \u201cThe ratio of alqueria during the Andalusi period to village sites after the conquest is G : GA. There are N sites that became a village after the conquest, from an alqueria\u201d\n\n", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 39": { + "description": "States in a sentence on Slide 2 that there were 10 towers during the Andalusi period (acceptable value is 10).", + "justification": "The number of towers is determined from Figure_43_Map_of_Andalusi_settlement_in_the_Malaga_region.png. This is a greyscale map that shows the location of castles, watchtowers, towers of alqueria, alqueria (rural settlements) and rivers in the region of Malaga during the Andalusi period. If a grid consisting of 9 columns of equal width, labeled A-I, and 6 rows of equal height labeled 1-6 from top to bottom is placed on the map, the distribution of towers (Watchtowers and towers of alqueria combined) in the cells is as follows, listing only cells that have a marker for a tower (cell:number of towers): F1:1; G1:1; H1:1; I1:1; A2:1; B2:1; F2:1; B3:1; G3:1; F6:1, for a total of 10 towers.\n", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 4, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 40": { + "description": "States in a sentence on Slide 2 that there were 0 towers after the conquest (acceptable value is 0).", + "justification": "The number of towers is to be determined from Figure_44_Map_of_settlement_in_Malaga_after_the_Castilian_conquest.png This is a greyscale map that shows the location of cities, villas, villages and rivers in the region of Malaga after the conquest. The map does not show towers in the region, therefore the number is 0.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 4, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 41": { + "description": "Includes on Slide 2 the sentence: \"The ratio of towers during the Andalusi period to the post-conquest period is __ : __.\", word for word, with a number in each blank. Any numbers pass this criterion; each value is graded by its own criterion.", + "justification": "The prompt instructs the user to include the following sentence in the slide: \u201cThe ratio of towers during the Andalusi period to the post-conquest period is K : KA.\u201d, where K is the number of towers during the Andalusi period, and KA is the number of towers after the conquest.\n\n", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 42": { + "description": "States in a sentence on Slide 3 that there were 2 Christian castles during the Andalusi period (acceptable value is 2).", + "justification": "The number of Christian castles is determined from Plate_41_Map_showing_Andalusi_settlement_in_the_northwestern_NasridCastilian_frontier.png. It is a colored map of the region of Granada during the Andalusi period, showing locations for Christian and Islamic castles, watchtowers and towers of alqueria, Nasrid alqueria and border villas. If a grid consisting of 9 columns of equal width, labeled A-I, and 6 rows of equal height labeled 1-6 from top to bottom is placed on the map, the location of Christian castles is as follows, listing only cells that have a marker for Christian castles (cell:number of castles): A1:1 and D1:1, for a total of 2 Christian castles.\n", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 4, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 43": { + "description": "States in a sentence on Slide 3 that there were 8 Islamic castles during the Andalusi period (acceptable value is 8).", + "justification": "The number of Islamic castles is determined from Plate_41_Map_showing_Andalusi_settlement_in_the_northwestern_NasridCastilian_frontier.png. It is a colored map of the region of Granada during the Andalusi period, showing locations for Christian and Islamic castles, watchtowers and towers of alqueria, Nasrid alqueria and border villas. If a grid consisting of 9 columns of equal width, labeled A-I, and 6 rows of equal height labeled 1-6 from top to bottom is placed on the map, the location of Islamic castles is as follows, listing only cells that have a marker for Islamic castles (cell:number of castles): F2:2; I2:1; A3:1; C3:1; E3:1; A4:1; A5:1, for a total of 8 Islamic castles.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 4, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 44": { + "description": "Includes on Slide 3 the sentence: \"The ratio of Christian to Islamic castles during the Andalusi period was __ : __.\", word for word, with a number in each blank. Any numbers pass this criterion; each value is graded by its own criterion.\n", + "justification": "The prompt instructs the user to include the following sentence on the slide: \"The ratio of Christian to Islamic castles during the Andalusi period was T : S.\" \n", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 45": { + "description": "States on Slide 3 that of the Nasrid alquerias and towers of alquerias in the Andalusi period, 58 became villages after the conquest (acceptable value is 58).", + "justification": "The number of Nasrid alquerias and towers of alquerias in the Andalusi period is determined from Plate_41_Map_showing_Andalusi_settlement_in_the_northwestern_NasridCastilian_frontier.png. It is a colored map of the region of Granada during the Andalusi period, showing locations for Christian and Islamic castles, watchtowers and towers of alqueria, Nasrid alqueria and border villas. If a grid consisting of 9 columns of equal width, labeled A-I, and 6 rows of equal height labeled 1-6 from top to bottom is placed on the map, the location of Nasrid alquerias and towers of alquerias is as follows, listing only cells that have a marker for them (cell:number of markers): G1:2; C2:1; F2:4; H2:1; A3:1; C3:1; D3:1; E3:1; F3:3; G3:5; H3:3; B4:2; D4:3; E4:6; F4:11; G4:8; H4:12; I4:1; A5:2; B5;1; C5;2; E5:6; F5:4; G5:13; H5:9; I5:6; E6:4; F6:1; G6:6; H6:9; I6:2, for a total of 131 Nasrid alquerias and towers of alquerias combined.\n\nThe number of villages after the conquest is counted from Plate_42_Map_showing_settlement_in_the_territory_of_Granada_after_the_Castilian_conquest.png. It is a colored map of the region of Granada after the conquest showing locations for Cities, castles, villages, villas, farmhouses and Moorish farmhouses. If a grid consisting of 9 columns of equal width, labeled A-I, and 6 rows of equal height labeled 1-6 from top to bottom is placed on the map, the location of villages is as follows, listing only cells that have a marker for them (cell:number of markers): F2:1; F3:1; G3:1; H3:1; C4:1; D4:3; E4:3; F4:3; G4:3; H4:10; I4:1; A5:1; B5:1; C5:1; E5:2; F5:3; G5:5; H5:4; I5:4; E6:1; F6:1; G6:4; H6:4; I6:2, for a total of 61 villages. \n\nTo identify the village sites that were Nasrid alquerias or towers of alquerias in the Andalusi period the two maps need to be overlaid using the rivers as guides. Of the 131 Nasrid alquerias and towers of alquerias in the Andalusi period 58 became villages. ", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 4, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 46": { + "description": "States on Slide 3 that of the Nasrid alquerias and towers of alquerias in the Andalusi period, 44% (only the exact percentage is acceptable) became villages after the conquest.\n", + "justification": "The number of Nasrid alquerias and towers of alquerias in the Andalusi period is determined from Plate_41_Map_showing_Andalusi_settlement_in_the_northwestern_NasridCastilian_frontier.png. It is a colored map of the region of Granada during the Andalusi period, showing locations for Christian and Islamic castles, watchtowers and towers of alqueria, Nasrid alqueria and border villas. If a grid consisting of 9 columns of equal width, labeled A-I, and 6 rows of equal height labeled 1-6 from top to bottom is placed on the map, the location of Nasrid alquerias and towers of alquerias is as follows, listing only cells that have a marker for them (cell:number of markers): G1:2; C2:1; F2:4; H2:1; A3:1; C3:1; D3:1; E3:1; F3:3; G3:5; H3:3; B4:2; D4:3; E4:6; F4:11; G4:8; H4:12; I4:1; A5:2; B5;1; C5:2; E5:6; F5:4; G5:13; H5:9; I5:6; E6:4; F6:1; G6:6; H6:9; I6:2, for a total of 131 Nasrid alquerias and towers of alquerias combined.\n\nThe number of villages after the conquest is counted from Plate_42_Map_showing_settlement_in_the_territory_of_Granada_after_the_Castilian_conquest.png. It is a colored map of the region of Granada after the conquest showing locations for Cities, castles, villages, villas, farmhouses and Moorish farmhouses. If a grid consisting of 9 columns of equal width, labeled A-I, and 6 rows of equal height labeled 1-6 from top to bottom is placed on the map, the location of villages is as follows, listing only cells that have a marker for them (cell:number of markers): F2:1; F3:1; G3:1; H3:1; C4:1; D4:3; E4:3; F4:3; G4:3; H4:10; I4:1; A5:1; B5:1; C5:1; E5:2; F5:3; G5:5; H5:4; I5:4; E6:1; F6:1; G6:4; H6:4; I6:2, for a total of 61 villages. \n\nTo identify the village sites that were Nasrid alquerias or towers of alquerias in the Andalusi period the two maps need to be overlaid using the rivers as guides. Of the 61 villages, 58 were sites for Nasrid alquerias or towers of alquerias in the Andalusi period. The three that were not are in cells C4, H4, H5.\n\nTo calculate the percent of Nasrid alqueria and towers of alqueria that became villages after the conquest, the number of villages that developed on these sites (58) is divided by the number of Nasrid alqueria and towers of alqueria (131) and is multiplied by 100, which equals 44.27. Therefore, MM = 44% (only the exact percentage is acceptable) of the Nasrid alquerias and towers of alquerias became villages after the conquest.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 5, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 47": { + "description": "Includes on Slide 3 the sentence: \"Of the Nasrid alquerias and towers of alquerias in the Andalusi period, __ (__%) became villages after the conquest.\", word for word, with a number in each blank. Any numbers pass this criterion; each value is graded by its own criterion.", + "justification": "The prompt instructs the user to include the sentence: \u201cOf the Nasrid alquerias and towers of alquerias in the Andalusi period, M (MM%) became villages after the conquest.\u201d\n", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 48": { + "description": "States in a sentence on Slide 3 that the number of farmhouses after the conquest was 86 (acceptable value is 86).", + "justification": "The number of farmhouses after the conquest is counted from Plate_42_Map_showing_settlement_in_the_territory_of_Granada_after_the_Castilian_conquest.png. It is a colored map of the region of Granada after the conquest showing locations for Cities, castles, villages, villas, farmhouses and Moorish farmhouses. If a grid consisting of 9 columns of equal width, labeled A-I, and 6 rows of equal height labeled 1-6 from top to bottom is placed on the map, the location of farmhouses is as follows, listing only cells that have a marker for them (cell:number of markers): E1:2; F1:6; G1:10; H1:4; B2:5; C2:4; D2:4; E2:5; F2:5; G2:2; H2:3; I2:1; A3:3; B3:6; C3:1; D3:8; E3:1; F3:5; G3:2; A4:1; B4:5; C4:2; D4:1, for a total of 86 farmhouses.\n", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 4, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 49": { + "description": "States in a sentence on Slide 3 that the number of Moorish farmhouses after the conquest was 13 (acceptable value is 13).", + "justification": "The number of Moorish farmhouses after the conquest is counted from Plate_42_Map_showing_settlement_in_the_territory_of_Granada_after_the_Castilian_conquest.png. It is a colored map of the region of Granada after the conquest showing locations for Cities, castles, villages, villas, farmhouses and Moorish farmhouses. If a grid consisting of 9 columns of equal width, labeled A-I, and 6 rows of equal height labeled 1-6 from top to bottom is placed on the map, the locations of Moorish farmhouses are as follows, listing only cells that have a marker for them (cell:number of markers): G1:1; H1:4; E2:4; G2:1; D3:1; B4:1; C4:1, for a total of 13 Moorish farmhouses.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 4, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 50": { + "description": "States in a sentence on Slide 3 that the number of villages after the conquest was 61 (acceptable value is 61).", + "justification": "The number of villages after the conquest is counted from Plate_42_Map_showing_settlement_in_the_territory_of_Granada_after_the_Castilian_conquest.png. It is a colored map of the region of Granada after the conquest showing locations for Cities, castles, villages, villas, farmhouses and Moorish farmhouses. If a grid consisting of 9 columns of equal width, labeled A-I, and 6 rows of equal height labeled 1-6 from top to bottom is placed on the map, the location of villages is as follows, listing only cells that have a marker for them (cell:number of markers): F2:1; F3:1; G3:1; H3:1; C4:1; D4:3; E4:3; F4:3; G4:3; H4:10; I4:1; A5:1; B5:1; C5:1; E5:2; F5:3; G5:5; H5:4; I5:4; E6:1; F6:1; G6:4; H6:4; I6:2, for a total of 61 villages. ", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 4, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 51": { + "description": "Includes on Slide 3 the sentence: \"The ratio of farmhouses, Moorish farmhouses, and villages after the conquest was __ : __ : __.\", word for word, with a number in each blank. Any numbers pass this criterion; each value is graded by its own criterion.", + "justification": "The prompt instructs the user to include the following sentence on the slide: \u201cThe ratio of farmhouses, Moorish farmhouses, and villages after the conquest was H : J : L.\", where H is the number of farmhouses, J is the number of Moorish farmhouses, and L is the number of villages.\n", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 52": { + "description": "Quotation marks are omitted from sentences on every slide.", + "justification": "The prompt says: \"Omit quotation marks for all sentences you add to the slides.\"\n", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + } +} \ No newline at end of file diff --git a/tasks/task_a46a6c3cebd54b82b9ad5e66d1e14e48/input/Drawing_Coordination_Review_Standard.pptx b/tasks/task_a46a6c3cebd54b82b9ad5e66d1e14e48/input/Drawing_Coordination_Review_Standard.pptx new file mode 100644 index 0000000000000000000000000000000000000000..2e821e15bfd8adef47a83f983f796959627407e1 --- /dev/null +++ b/tasks/task_a46a6c3cebd54b82b9ad5e66d1e14e48/input/Drawing_Coordination_Review_Standard.pptx @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6e24fbe3782aa3a73ad1bc05b179bf20d46e0d1663be4cee6e0dca01bfb0f188 +size 53355 diff --git a/tasks/task_a46a6c3cebd54b82b9ad5e66d1e14e48/input/Elevation_01.pdf b/tasks/task_a46a6c3cebd54b82b9ad5e66d1e14e48/input/Elevation_01.pdf new file mode 100644 index 0000000000000000000000000000000000000000..1a30e9f98a8e9b02f2343d58d5a5509ef0884b39 --- /dev/null +++ b/tasks/task_a46a6c3cebd54b82b9ad5e66d1e14e48/input/Elevation_01.pdf @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a40d678b74a3123567834ab78b918e4cf9d391e5b3c7032e0cb754cb5c554a8a +size 236280 diff --git a/tasks/task_a46a6c3cebd54b82b9ad5e66d1e14e48/input/Elevation_02.pdf b/tasks/task_a46a6c3cebd54b82b9ad5e66d1e14e48/input/Elevation_02.pdf new file mode 100644 index 0000000000000000000000000000000000000000..9a4e5c92a6285b9938d00a742e968e514a79bfd8 --- /dev/null +++ b/tasks/task_a46a6c3cebd54b82b9ad5e66d1e14e48/input/Elevation_02.pdf @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:953875961306754fd1318dc8f0fd2f746440d1ff20b50907ae5ac868956a7122 +size 282628 diff --git a/tasks/task_a46a6c3cebd54b82b9ad5e66d1e14e48/input/Elevation_03.pdf b/tasks/task_a46a6c3cebd54b82b9ad5e66d1e14e48/input/Elevation_03.pdf new file mode 100644 index 0000000000000000000000000000000000000000..f04a628bc2af247b2a3105df74abd18140a01c37 --- /dev/null +++ b/tasks/task_a46a6c3cebd54b82b9ad5e66d1e14e48/input/Elevation_03.pdf @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d82b36e1a378a6c28428286bebead7dd7c837a878a59656d8cfbc00a192692cf +size 186637 diff --git a/tasks/task_a46a6c3cebd54b82b9ad5e66d1e14e48/input/Elevation_04.pdf b/tasks/task_a46a6c3cebd54b82b9ad5e66d1e14e48/input/Elevation_04.pdf new file mode 100644 index 0000000000000000000000000000000000000000..1a566a1cb98d65f5e282f0a4e0cce50e662ea26f --- /dev/null +++ b/tasks/task_a46a6c3cebd54b82b9ad5e66d1e14e48/input/Elevation_04.pdf @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:270038eb75952a590ff89fe0d68be21b9b3dff3c85d636bf6ae8329f8351ca15 +size 206356 diff --git a/tasks/task_a46a6c3cebd54b82b9ad5e66d1e14e48/input/First_Floor_Plan.pdf b/tasks/task_a46a6c3cebd54b82b9ad5e66d1e14e48/input/First_Floor_Plan.pdf new file mode 100644 index 0000000000000000000000000000000000000000..b29c423f6eb23c346fac43fb1f1a6ada7ca4e2b6 --- /dev/null +++ b/tasks/task_a46a6c3cebd54b82b9ad5e66d1e14e48/input/First_Floor_Plan.pdf @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b9852864fe91847ac68d3c4c80fdcb140c7d8aaed82ebc41b19b231a147c10cc +size 366773 diff --git a/tasks/task_a46a6c3cebd54b82b9ad5e66d1e14e48/input/Ground_Floor_Plan.pdf b/tasks/task_a46a6c3cebd54b82b9ad5e66d1e14e48/input/Ground_Floor_Plan.pdf new file mode 100644 index 0000000000000000000000000000000000000000..bf00f2f484f06671bb507a0ecfc7600c6cf0cc93 --- /dev/null +++ b/tasks/task_a46a6c3cebd54b82b9ad5e66d1e14e48/input/Ground_Floor_Plan.pdf @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:57e7f91c5f9c77e17ad889843fe17e47799dbdc9ba783728a9f7370c184bc580 +size 363012 diff --git a/tasks/task_a46a6c3cebd54b82b9ad5e66d1e14e48/input/Roof_Floor_Plan.pdf b/tasks/task_a46a6c3cebd54b82b9ad5e66d1e14e48/input/Roof_Floor_Plan.pdf new file mode 100644 index 0000000000000000000000000000000000000000..c0b24366db531f8abd3fa47244dcc934dc6d9ef1 --- /dev/null +++ b/tasks/task_a46a6c3cebd54b82b9ad5e66d1e14e48/input/Roof_Floor_Plan.pdf @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:afc270038bf1cc2ebae19a9bf931d3ab74f0b2da86c4f9a515580bc5307c9e69 +size 262011 diff --git a/tasks/task_a46a6c3cebd54b82b9ad5e66d1e14e48/input/Second_Floor_Plan.pdf b/tasks/task_a46a6c3cebd54b82b9ad5e66d1e14e48/input/Second_Floor_Plan.pdf new file mode 100644 index 0000000000000000000000000000000000000000..77effa74e48390e99c091f45633260eb42bf3e11 --- /dev/null +++ b/tasks/task_a46a6c3cebd54b82b9ad5e66d1e14e48/input/Second_Floor_Plan.pdf @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7711b924eb77379cd1f12525a5c5815ba75aa42afa1e7cf811ed0edcde660999 +size 388618 diff --git a/tasks/task_a46a6c3cebd54b82b9ad5e66d1e14e48/input/Section_A_A.pdf b/tasks/task_a46a6c3cebd54b82b9ad5e66d1e14e48/input/Section_A_A.pdf new file mode 100644 index 0000000000000000000000000000000000000000..5ee8013b5c0b8ffd96f2487d8ae1eb263e42d0cd --- /dev/null +++ b/tasks/task_a46a6c3cebd54b82b9ad5e66d1e14e48/input/Section_A_A.pdf @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bf8d828a5c0a8d80f0f71849c059290ba2a52aceb23477687e8a0d94a03f3c46 +size 549943 diff --git a/tasks/task_a46a6c3cebd54b82b9ad5e66d1e14e48/input/Section_B_B.pdf b/tasks/task_a46a6c3cebd54b82b9ad5e66d1e14e48/input/Section_B_B.pdf new file mode 100644 index 0000000000000000000000000000000000000000..bd48064c94edf1c4e3af06529e3094a3e49b12be --- /dev/null +++ b/tasks/task_a46a6c3cebd54b82b9ad5e66d1e14e48/input/Section_B_B.pdf @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:095b061967054fbc8de9c37e91c584b652689a688663ee85d976e16f4d105d32 +size 400885 diff --git a/tasks/task_a46a6c3cebd54b82b9ad5e66d1e14e48/input/Third_Floor_Plan.pdf b/tasks/task_a46a6c3cebd54b82b9ad5e66d1e14e48/input/Third_Floor_Plan.pdf new file mode 100644 index 0000000000000000000000000000000000000000..f762985ef2fc2413259c9863708231c47c7948f8 --- /dev/null +++ b/tasks/task_a46a6c3cebd54b82b9ad5e66d1e14e48/input/Third_Floor_Plan.pdf @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:19847be1b78508210081f92174c6e5f4d53c5aa8efb75807f59d44c1ac9b379b +size 358859 diff --git a/tasks/task_a46a6c3cebd54b82b9ad5e66d1e14e48/metadata.json b/tasks/task_a46a6c3cebd54b82b9ad5e66d1e14e48/metadata.json new file mode 100644 index 0000000000000000000000000000000000000000..a5ea29d650f1df923d3cec6580a0454cf8ed9550 --- /dev/null +++ b/tasks/task_a46a6c3cebd54b82b9ad5e66d1e14e48/metadata.json @@ -0,0 +1,12 @@ +{ + "TaskID": "task_a46a6c3cebd54b82b9ad5e66d1e14e48", + "Vertical": "Construction", + "Domain": "Architecture", + "Role": "Architect", + "Task Goal": "Audit floor plans against building sections and elevations to flag coordination exceptions.", + "Prompt": "Create ‘Architectural_Section_Elevation_Opening_Coordination_Audit.pptx’, an exception-only coordination audit of the five floor plans against Sections A-A and B-B and the four elevations. Base the analysis only on the supplied drawings, and prepare the report in accordance with the attached drawing coordination review standard.\n\nOn every floor, audit the content cut by each section against the plan, the content visible beyond each cut plane, and every exterior door and window opening, including its representation on the elevations, its floor band and its written width. Begin with a building summary showing each floor’s overall status and separate Mismatch and Cannot Determine counts, then present only Mismatch and Cannot Determine findings, organized by floor and supported by crops from the relevant drawings. Limit the report to 10 slides.", + "Input_files": "Drawing_Coordination_Review_Standard.pptx, Elevation_01.pdf, Elevation_02.pdf, Elevation_03.pdf, Elevation_04.pdf, First_Floor_Plan.pdf, Ground_Floor_Plan.pdf, Roof_Floor_Plan.pdf, Second_Floor_Plan.pdf, Section_A_A.pdf, Section_B_B.pdf, Third_Floor_Plan.pdf", + "All Task Files": "tasks/task_a46a6c3cebd54b82b9ad5e66d1e14e48/input/", + "Rubric Criteria": "tasks/task_a46a6c3cebd54b82b9ad5e66d1e14e48/rubrics.json", + "Economic Rationale": "This audit helps identify plan-to-section, elevation, and opening-schedule coordination errors before construction, reducing RFIs, costly rework, material waste, and project delays." +} diff --git a/tasks/task_a46a6c3cebd54b82b9ad5e66d1e14e48/rubrics.json b/tasks/task_a46a6c3cebd54b82b9ad5e66d1e14e48/rubrics.json new file mode 100644 index 0000000000000000000000000000000000000000..e56b705f0efbc458131a45e55cfe3f627e6e800a --- /dev/null +++ b/tasks/task_a46a6c3cebd54b82b9ad5e66d1e14e48/rubrics.json @@ -0,0 +1,758 @@ +{ + "criterion 1": { + "description": "Includes a distinct Ground Floor finding for Ground western D3 at the Entrance Hall / Living Room side intersected by Section B-B, identified as G-01 or by an equivalent unambiguous location-specific identifier.", + "justification": "On Ground_Floor_Plan.pdf, the Section B-B cut line passes through the western D3 door opening on the Entrance Hall / Living Room side, while Section_B_B.pdf draws a continuous cut Interior Wall at that position in the Ground floor band. This is finding G-01; an equivalent identifier is accepted where the physical occurrence is unmistakable. A finding referring only to the eastern D3 on the Dining side does not satisfy this separate western D3 requirement.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 5, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 2": { + "description": "Classifies the finding at Ground western D3 at the Entrance Hall / Living Room side intersected by Section B-B as Mismatch.", + "justification": "On Ground_Floor_Plan.pdf, the Section B-B cut line passes through the western D3 door opening on the Entrance Hall / Living Room side, while Section_B_B.pdf draws a continuous cut Interior Wall at that position in the Ground floor band. The expected classification is Mismatch: the drawings show a definite contradiction, which Drawing_Coordination_Review_Standard.pptx page 2 classifies as Mismatch.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 4, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 3": { + "description": "Explains the Ground Floor western D3 issue at the Entrance Hall / Living Room side where Section B-B crosses the Ground Floor Plan: the plan shows a door opening intersected by the cut line, but the Ground band of Section B-B shows a continuous cut interior wall at the corresponding position.", + "justification": "On Ground_Floor_Plan.pdf, the Section B-B cut line passes through the western D3 door opening on the Entrance Hall / Living Room side, while Section_B_B.pdf draws a continuous cut Interior Wall at that position in the Ground floor band. Graded on naming the compared drawings, the location and the nature of the contradiction or uncertainty, not on any proposed correction.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 4": { + "description": "Includes original drawing crops for the Ground Floor western D3 at the Entrance Hall / Living Room side intersected by Section B-B: the Ground Floor Plan showing this D3 and the B-B cut, and Section B-B showing the corresponding continuous wall in the Ground band.", + "justification": "Drawing_Coordination_Review_Standard.pptx page 4 requires crops from the relevant drawings showing both sides of the disputed relationship with enough grid or level context to verify it. For G-01 the relevant drawings are Ground_Floor_Plan.pdf and Section_B_B.pdf. Judged from the content visible in the crop image, not from its caption.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 5": { + "description": "Includes a distinct Ground Floor finding for Ground eastern D3 at the Entrance Hall / Dining side intersected by Section B-B, identified as G-02 or by an equivalent unambiguous location-specific identifier.", + "justification": "On Ground_Floor_Plan.pdf, the Section B-B cut line passes through the eastern D3 door opening on the Entrance Hall / Dining side, while Section_B_B.pdf draws a continuous cut Interior Wall at that position in the Ground floor band. This is finding G-02; an equivalent identifier is accepted where the physical occurrence is unmistakable.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 5, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 6": { + "description": "Classifies the finding at Ground eastern D3 at the Entrance Hall / Dining side intersected by Section B-B as Mismatch.", + "justification": "On Ground_Floor_Plan.pdf, the Section B-B cut line passes through the eastern D3 door opening on the Entrance Hall / Dining side, while Section_B_B.pdf draws a continuous cut Interior Wall at that position in the Ground floor band. The expected classification is Mismatch: the drawings show a definite contradiction, which Drawing_Coordination_Review_Standard.pptx page 2 classifies as Mismatch.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 4, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 7": { + "description": "Explains the Ground Floor eastern D3 issue at the Entrance Hall / Dining side where Section B-B crosses the Ground Floor Plan: the plan shows a door opening intersected by the cut line, but the Ground band of Section B-B shows a continuous cut interior wall at this separate position.", + "justification": "On Ground_Floor_Plan.pdf, the Section B-B cut line passes through the eastern D3 door opening on the Entrance Hall / Dining side, while Section_B_B.pdf draws a continuous cut Interior Wall at that position in the Ground floor band. Graded on naming the compared drawings, the location and the nature of the contradiction or uncertainty, not on any proposed correction.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 8": { + "description": "Includes original drawing crops for the Ground Floor eastern D3 at the Entrance Hall / Dining side intersected by Section B-B: the Ground Floor Plan showing this D3 and the B-B cut, and Section B-B showing the corresponding continuous wall in the Ground band.", + "justification": "Drawing_Coordination_Review_Standard.pptx page 4 requires crops from the relevant drawings showing both sides of the disputed relationship with enough grid or level context to verify it. For G-02 the relevant drawings are Ground_Floor_Plan.pdf and Section_B_B.pdf. Judged from the content visible in the crop image, not from its caption.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 9": { + "description": "Includes a distinct Ground Floor finding for Ground W4 on Grid 4 facade (Bay B\u2013C), Elevation 02, identified as G-03 or by an equivalent unambiguous location-specific identifier.", + "justification": "Ground_Floor_Plan.pdf shows exterior window W4 on the Grid 4 facade in bay B\u2013C, while Elevation_02.pdf shows no opening in bay B\u2013C within the Ground floor band (\u00b10.00 to +4.00); the four stair windows drawn on Elevation 02 all sit above +4.00. This is finding G-03; an equivalent identifier is accepted where the physical occurrence is unmistakable.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 5, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 10": { + "description": "Classifies the finding at Ground W4 on Grid 4 facade (Bay B\u2013C), Elevation 02 as Mismatch.", + "justification": "Ground_Floor_Plan.pdf shows exterior window W4 on the Grid 4 facade in bay B\u2013C, while Elevation_02.pdf shows no opening in bay B\u2013C within the Ground floor band (\u00b10.00 to +4.00); the four stair windows drawn on Elevation 02 all sit above +4.00. The expected classification is Mismatch: the drawings show a definite contradiction, which Drawing_Coordination_Review_Standard.pptx page 2 classifies as Mismatch.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 4, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 11": { + "description": "Explains the Ground Floor exterior W4 issue at Grid 4 facade, Bay B\u2013C, in the Ground Floor Plan versus Elevation 02: the plan shows W4, but Elevation 02 has no corresponding opening in the Ground floor band (\u00b10.00, equivalently +0.00, to +4.00).", + "justification": "Ground_Floor_Plan.pdf shows exterior window W4 on the Grid 4 facade in bay B\u2013C, while Elevation_02.pdf shows no opening in bay B\u2013C within the Ground floor band (\u00b10.00 to +4.00); the four stair windows drawn on Elevation 02 all sit above +4.00. Graded on naming the compared drawings, the location and the nature of the contradiction or uncertainty, not on any proposed correction.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 12": { + "description": "Includes original drawing crops for the Ground Floor exterior W4 at Grid 4 facade, Bay B\u2013C: the Ground Floor Plan showing W4 and Grid 4, and Elevation 02 showing the Ground floor band and the absence of the corresponding opening.", + "justification": "Drawing_Coordination_Review_Standard.pptx page 4 requires crops from the relevant drawings showing both sides of the disputed relationship with enough grid or level context to verify it. For G-03 the relevant drawings are Ground_Floor_Plan.pdf and Elevation_02.pdf. Judged from the content visible in the crop image, not from its caption.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 13": { + "description": "Includes a distinct Ground Floor finding for Ground W4 projected visibility beyond Section B-B near stair/landing, identified as G-04 or by an equivalent unambiguous location-specific identifier.", + "justification": "On Ground_Floor_Plan.pdf, W4 sits on the Grid 4 wall within the stairwell beyond the B-B cut plane in the viewing direction, so part of it would appear in the Ground band of Section_B_B.pdf, but the section shows no opening on that wall. This is separate from its confirmed absence on Elevation 02. This is finding G-04; an equivalent identifier is accepted where the physical occurrence is unmistakable.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 5, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 14": { + "description": "Classifies the finding at Ground W4 projected visibility beyond Section B-B near stair/landing as Mismatch.", + "justification": "On Ground_Floor_Plan.pdf, W4 sits on the Grid 4 wall within the stairwell beyond the B-B cut plane in the viewing direction, so part of it would appear in the Ground band of Section_B_B.pdf, but the section shows no opening on that wall. This is separate from its confirmed absence on Elevation 02. The expected classification is Mismatch: the plan places an opening where the section shows none, a definite contradiction between corresponding drawing information, which Drawing_Coordination_Review_Standard.pptx page 2 classifies as Mismatch (Cannot Determine is not used in place of an established error).", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 4, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 15": { + "description": "Explains the Ground Floor W4 issue beyond Section B-B near the stair/landing: the Ground Floor Plan places W4 on the Grid 4 wall within the stairwell beyond the B-B cut, but the Ground band of Section B-B shows no opening on that wall.", + "justification": "On Ground_Floor_Plan.pdf, W4 sits on the Grid 4 wall within the stairwell beyond the B-B cut plane in the viewing direction, so part of it would appear in the Ground band of Section_B_B.pdf, but the section shows no opening on that wall. This is separate from its confirmed absence on Elevation 02. Graded on naming the compared drawings, the location and the nature of the contradiction, not on any proposed correction.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 16": { + "description": "Includes original drawing crops for the Ground Floor W4 visibility beyond Section B-B near the stair/landing: the Ground Floor Plan showing W4 and B-B viewing direction, and Section B-B showing the Ground stair/landing and section windows.", + "justification": "Drawing_Coordination_Review_Standard.pptx page 4 requires crops from the relevant drawings showing both sides of the disputed relationship with enough grid or level context to verify it. For G-04 the relevant drawings are Ground_Floor_Plan.pdf and Section_B_B.pdf. Judged from the content visible in the crop image, not from its caption.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 17": { + "description": "Includes a distinct First Floor finding for First-floor Grid A facade W2 by Gaming Room, Grids 3\u20134, identified as F-01 or by an equivalent unambiguous location-specific identifier.", + "justification": "On First_Floor_Plan.pdf, the W2 window on the Grid A facade at the Gaming Room (grids 3\u20134) carries a written width of 1.99 m in the dimension chain, while the other W2 windows on the same plan carry 2.00 m. This is finding F-01; an equivalent identifier is accepted where the physical occurrence is unmistakable.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 5, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 18": { + "description": "Classifies the finding at First-floor Grid A facade W2 by Gaming Room, Grids 3\u20134 as Mismatch.", + "justification": "On First_Floor_Plan.pdf, the W2 window on the Grid A facade at the Gaming Room (grids 3\u20134) carries a written width of 1.99 m in the dimension chain, while the other W2 windows on the same plan carry 2.00 m. The expected classification is Mismatch: the drawings show a definite contradiction, which Drawing_Coordination_Review_Standard.pptx page 2 classifies as Mismatch.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 4, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 19": { + "description": "Explains the First Floor W2 written-width discrepancy on Grid A facade at Gaming Room, between Grids 3\u20134, in the First Floor Plan: that W2 opening is annotated 1.99 m while other windows tagged W2 on the same plan are annotated 2.00 m.", + "justification": "On First_Floor_Plan.pdf, the W2 window on the Grid A facade at the Gaming Room (grids 3\u20134) carries a written width of 1.99 m in the dimension chain, while the other W2 windows on the same plan carry 2.00 m. Graded on naming the compared drawings, the location and the nature of the contradiction or uncertainty, not on any proposed correction.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 20": { + "description": "Includes original drawing crops for the First Floor Grid A facade W2 at Gaming Room, Grids 3\u20134: the First Floor Plan showing its 1.99 m width and another W2 on the same plan with a 2.00 m width.", + "justification": "Drawing_Coordination_Review_Standard.pptx page 4 requires crops from the relevant drawings showing both sides of the disputed relationship with enough grid or level context to verify it. For F-01 the relevant drawings are First_Floor_Plan.pdf. Judged from the content visible in the crop image, not from its caption.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 21": { + "description": "Includes a distinct First Floor finding for First-floor recessed D6, Grid 4 facade Bay A\u2013B, Elevation 02, identified as F-02 or by an equivalent unambiguous location-specific identifier.", + "justification": "First_Floor_Plan.pdf tags the recessed balcony opening on the Grid 4 facade (bay A\u2013B) as door D6. On Elevation_02.pdf, the corresponding opening in the First floor band (+4.00 to +7.45) has no bottom frame and is cut off by the balcony recess line, so its full extent and its category as door or window cannot be established. This is finding F-02; an equivalent identifier is accepted where the physical occurrence is unmistakable.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 5, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 22": { + "description": "Classifies the finding at First-floor recessed D6, Grid 4 facade Bay A\u2013B, Elevation 02 as Cannot Determine.", + "justification": "First_Floor_Plan.pdf tags the recessed balcony opening on the Grid 4 facade (bay A\u2013B) as door D6. On Elevation_02.pdf, the corresponding opening in the First floor band (+4.00 to +7.45) has no bottom frame and is cut off by the balcony recess line, so its full extent and its category as door or window cannot be established. The expected classification is Cannot Determine: the relationship cannot be resolved uniquely from the drawings, which Drawing_Coordination_Review_Standard.pptx page 2 classifies as Cannot Determine.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 4, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 23": { + "description": "Explains the First Floor recessed D6 issue at Grid 4 facade, Bay A\u2013B: the First Floor Plan identifies D6 as a door, but on Elevation 02 the element\u2019s lower edge in the First floor band (+4.00 to +7.45) coincides with the balcony recess edge, leaving unresolved whether it is drawn as a door or a window.", + "justification": "First_Floor_Plan.pdf tags the recessed balcony opening on the Grid 4 facade (bay A\u2013B) as door D6. On Elevation_02.pdf, the corresponding opening in the First floor band (+4.00 to +7.45) has no bottom frame and is cut off by the balcony recess line, so its full extent and its category as door or window cannot be established. Graded on naming the compared drawings, the location and the nature of the contradiction or uncertainty, not on any proposed correction. The plan category of D6 is not reclassified, and no separate First Floor B-B visible-content finding is expected.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 24": { + "description": "Includes original drawing crops for the First Floor recessed D6 at Grid 4 facade, Bay A\u2013B, near Gaming Room: the First Floor Plan identifying D6, and Elevation 02 showing the First floor band (+4.00 to +7.45).", + "justification": "Drawing_Coordination_Review_Standard.pptx page 4 requires crops from the relevant drawings showing both sides of the disputed relationship with enough grid or level context to verify it. For F-02 the relevant drawings are First_Floor_Plan.pdf and Elevation_02.pdf. Judged from the content visible in the crop image, not from its caption.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 25": { + "description": "Includes a distinct Second Floor finding for Second-floor Grid A facade W2 by Master Bedroom, Grids 3\u20134, identified as S-01 or by an equivalent unambiguous location-specific identifier.", + "justification": "On Second_Floor_Plan.pdf, the W2 window on the Grid A facade at the Master Bedroom (grids 3\u20134) carries a written width of 1.99 m in the dimension chain, while the other W2 windows on the same plan carry 2.00 m. This is finding S-01; an equivalent identifier is accepted where the physical occurrence is unmistakable.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 5, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 26": { + "description": "Classifies the finding at Second-floor Grid A facade W2 by Master Bedroom, Grids 3\u20134 as Mismatch.", + "justification": "On Second_Floor_Plan.pdf, the W2 window on the Grid A facade at the Master Bedroom (grids 3\u20134) carries a written width of 1.99 m in the dimension chain, while the other W2 windows on the same plan carry 2.00 m. The expected classification is Mismatch: the drawings show a definite contradiction, which Drawing_Coordination_Review_Standard.pptx page 2 classifies as Mismatch.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 4, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 27": { + "description": "Explains the Second Floor W2 written-width discrepancy on Grid A facade at Master Bedroom, between Grids 3\u20134, in the Second Floor Plan: that W2 opening is annotated 1.99 m whereas other W2 windows on the same plan are annotated 2.00 m.", + "justification": "On Second_Floor_Plan.pdf, the W2 window on the Grid A facade at the Master Bedroom (grids 3\u20134) carries a written width of 1.99 m in the dimension chain, while the other W2 windows on the same plan carry 2.00 m. Graded on naming the compared drawings, the location and the nature of the contradiction or uncertainty, not on any proposed correction.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 28": { + "description": "Includes original drawing crops for the Second Floor Grid A facade W2 at Master Bedroom, Grids 3\u20134: the Second Floor Plan showing its 1.99 m width and another W2 with a 2.00 m width.", + "justification": "Drawing_Coordination_Review_Standard.pptx page 4 requires crops from the relevant drawings showing both sides of the disputed relationship with enough grid or level context to verify it. For S-01 the relevant drawings are Second_Floor_Plan.pdf. Judged from the content visible in the crop image, not from its caption.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 29": { + "description": "Includes a distinct Second Floor finding for Second-floor recessed D6, Grid 4 facade Bay A\u2013B, Elevation 02, identified as S-02 or by an equivalent unambiguous location-specific identifier.", + "justification": "Second_Floor_Plan.pdf tags the recessed balcony opening on the Grid 4 facade (bay A\u2013B) as door D6. On Elevation_02.pdf, the corresponding opening in the Second floor band (+7.45 to +10.90) has no bottom frame and is cut off by the balcony recess line, so its full extent and its category as door or window cannot be established. This is finding S-02; an equivalent identifier is accepted where the physical occurrence is unmistakable.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 5, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 30": { + "description": "Classifies the finding at Second-floor recessed D6, Grid 4 facade Bay A\u2013B, Elevation 02 as Cannot Determine.", + "justification": "Second_Floor_Plan.pdf tags the recessed balcony opening on the Grid 4 facade (bay A\u2013B) as door D6. On Elevation_02.pdf, the corresponding opening in the Second floor band (+7.45 to +10.90) has no bottom frame and is cut off by the balcony recess line, so its full extent and its category as door or window cannot be established. The expected classification is Cannot Determine: the relationship cannot be resolved uniquely from the drawings, which Drawing_Coordination_Review_Standard.pptx page 2 classifies as Cannot Determine.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 4, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 31": { + "description": "Explains the Second Floor recessed D6 issue at Grid 4 facade, Bay A\u2013B: the Second Floor Plan identifies D6 as a door, but on Elevation 02 the element\u2019s lower edge in the Second floor band (+7.45 to +10.90) coincides with the balcony recess edge, leaving unresolved whether it is drawn as a door or a window.", + "justification": "Second_Floor_Plan.pdf tags the recessed balcony opening on the Grid 4 facade (bay A\u2013B) as door D6. On Elevation_02.pdf, the corresponding opening in the Second floor band (+7.45 to +10.90) has no bottom frame and is cut off by the balcony recess line, so its full extent and its category as door or window cannot be established. Graded on naming the compared drawings, the location and the nature of the contradiction or uncertainty, not on any proposed correction.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 32": { + "description": "Includes original drawing crops for the Second Floor recessed D6 at Grid 4 facade, Bay A\u2013B: the Second Floor Plan identifying that D6, and Elevation 02 showing the Second floor band (+7.45 to +10.90).", + "justification": "Drawing_Coordination_Review_Standard.pptx page 4 requires crops from the relevant drawings showing both sides of the disputed relationship with enough grid or level context to verify it. For S-02 the relevant drawings are Second_Floor_Plan.pdf and Elevation_02.pdf. Judged from the content visible in the crop image, not from its caption.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 33": { + "description": "Includes a distinct Second Floor finding for Second-floor D6 visibility beyond B-B at Dressing Room wall end, identified as S-03 or by an equivalent unambiguous location-specific identifier.", + "justification": "On Second_Floor_Plan.pdf, the Dressing Room south wall ends close to D6's right jamb, leaving only a narrow, undimensioned portion of D6 beyond the wall end in the B-B viewing direction. Because that portion can only be established by scaling, whether D6 is visible beyond the B-B cut plane in Section_B_B.pdf cannot be resolved. This is separate from the Elevation 02 reading of D6. This is finding S-03; an equivalent identifier is accepted where the physical occurrence is unmistakable.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 5, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 34": { + "description": "Classifies the finding at Second-floor D6 visibility beyond B-B at Dressing Room wall end as Cannot Determine.", + "justification": "On Second_Floor_Plan.pdf, the Dressing Room south wall ends close to D6's right jamb, leaving only a narrow, undimensioned portion of D6 beyond the wall end in the B-B viewing direction. Because that portion can only be established by scaling, whether D6 is visible beyond the B-B cut plane in Section_B_B.pdf cannot be resolved. This is separate from the Elevation 02 reading of D6. The expected classification is Cannot Determine: the relationship cannot be resolved uniquely from the drawings, which Drawing_Coordination_Review_Standard.pptx page 2 classifies as Cannot Determine.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 4, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 35": { + "description": "Explains the Second Floor D6 visibility uncertainty beyond Section B-B near the Dressing Room wall end: no written dimension fixes D6\u2019s jamb position relative to the wall end, leaving unresolved whether D6 is visible in Section B-B.", + "justification": "On Second_Floor_Plan.pdf, the Dressing Room south wall ends close to D6's right jamb, leaving only a narrow, undimensioned portion of D6 beyond the wall end in the B-B viewing direction. Because that portion can only be established by scaling, whether D6 is visible beyond the B-B cut plane in Section_B_B.pdf cannot be resolved. This is separate from the Elevation 02 reading of D6. Graded on naming the compared drawings, the location and the nature of the contradiction or uncertainty, not on any proposed correction.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 36": { + "description": "Includes original drawing crops for the Second Floor D6 near the Dressing Room wall end and beyond Section B-B: the Second Floor Plan showing D6 and the B-B view direction, and Section B-B showing the Second floor visible-content region.", + "justification": "Drawing_Coordination_Review_Standard.pptx page 4 requires crops from the relevant drawings showing both sides of the disputed relationship with enough grid or level context to verify it. For S-03 the relevant drawings are Second_Floor_Plan.pdf and Section_B_B.pdf. Judged from the content visible in the crop image, not from its caption.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 37": { + "description": "Includes a distinct Third Floor finding for Third-floor Grid A facade W2 by Bedroom 2, Grids 3\u20134, identified as T-01 or by an equivalent unambiguous location-specific identifier.", + "justification": "On Third_Floor_Plan.pdf, the W2 window on the Grid A facade at Bedroom 2 (grids 3\u20134) carries a written width of 1.99 m in the dimension chain, while the other W2 windows on the same plan carry 2.00 m. This is finding T-01; an equivalent identifier is accepted where the physical occurrence is unmistakable.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 5, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 38": { + "description": "Classifies the finding at Third-floor Grid A facade W2 by Bedroom 2, Grids 3\u20134 as Mismatch.", + "justification": "On Third_Floor_Plan.pdf, the W2 window on the Grid A facade at Bedroom 2 (grids 3\u20134) carries a written width of 1.99 m in the dimension chain, while the other W2 windows on the same plan carry 2.00 m. The expected classification is Mismatch: the drawings show a definite contradiction, which Drawing_Coordination_Review_Standard.pptx page 2 classifies as Mismatch.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 4, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 39": { + "description": "Explains the Third Floor W2 written-width discrepancy on Grid A facade at Bedroom 2, between Grids 3\u20134, in the Third Floor Plan: that W2 opening is annotated 1.99 m, whereas other windows tagged W2 on the same plan are annotated 2.00 m.", + "justification": "On Third_Floor_Plan.pdf, the W2 window on the Grid A facade at Bedroom 2 (grids 3\u20134) carries a written width of 1.99 m in the dimension chain, while the other W2 windows on the same plan carry 2.00 m. Graded on naming the compared drawings, the location and the nature of the contradiction or uncertainty, not on any proposed correction.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 40": { + "description": "Includes original drawing crops for the Third Floor Grid A facade W2 at Bedroom 2, Grids 3\u20134: the Third Floor Plan showing its 1.99 m width and another W2 with a 2.00 m width.", + "justification": "Drawing_Coordination_Review_Standard.pptx page 4 requires crops from the relevant drawings showing both sides of the disputed relationship with enough grid or level context to verify it. For T-01 the relevant drawings are Third_Floor_Plan.pdf. Judged from the content visible in the crop image, not from its caption.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 41": { + "description": "States the Ground Floor overall status as Mismatch, with separate finding counts of exactly 4 Mismatch (acceptable value 4) and 0 Cannot Determine (acceptable value 0) in the building summary.", + "justification": "Ground Floor findings: Mismatch G-01, G-02, G-03, G-04 (4); Cannot Determine none (0). Drawing_Coordination_Review_Standard.pptx page 3 counts each distinct occurrence or independently unresolved relationship once, and under its floor-status table at least one Mismatch makes the status Mismatch.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 42": { + "description": "Limits the Ground Floor detailed findings, regardless of equivalent unambiguous Finding ID labels, to one occurrence each of these four relationships: western D3 at Entrance Hall / Living Room side cut by Section B-B; eastern D3 at Entrance Hall / Dining side cut by Section B-B; exterior W4 missing from Ground band of Elevation 02 at Grid 4 facade, Bay B\u2013C; and Ground W4 visibility beyond Section B-B near the stair/landing.", + "justification": "Ground_Floor_Plan.pdf and Section_B_B.pdf show two distinct D3 cut-path discrepancies at the western and eastern Entrance Hall sides and the Ground W4 visibility relationship near the stair/landing. Ground_Floor_Plan.pdf and Elevation_02.pdf show Ground Grid 4 Bay B\u2013C W4 missing from the elevation band. Drawing_Coordination_Review_Standard.pptx pages 3\u20134 require distinct occurrences to be counted once and exception findings to be source-grounded. Grading accepts any unambiguous equivalent Finding ID.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 43": { + "description": "States the First Floor overall status as Mismatch, with separate finding counts of exactly 1 Mismatch (acceptable value 1) and 1 Cannot Determine (acceptable value 1) in the building summary.", + "justification": "First Floor findings: Mismatch F-01 (1); Cannot Determine F-02 (1). Drawing_Coordination_Review_Standard.pptx page 3 counts each distinct occurrence or independently unresolved relationship once, and under its floor-status table at least one Mismatch makes the status Mismatch.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 44": { + "description": "Limits the First Floor detailed findings, regardless of equivalent unambiguous Finding ID labels, to one occurrence each of these two relationships: the Grid A W2 written-width discrepancy at the Gaming Room, Grids 3\u20134 (1.99 m versus 2.00 m for other W2 windows on that plan); and the unresolved elevation representation of recessed D6 at Grid 4 facade, Bay A\u2013B, in Elevation 02.", + "justification": "First_Floor_Plan.pdf identifies the Grid A Gaming Room W2 and the recessed D6 on Grid 4 Bay A\u2013B; Elevation_02.pdf does not establish a unique elevation counterpart for D6. Drawing_Coordination_Review_Standard.pptx pages 3\u20134 restrict detail to distinct, source-supported exceptions. This criterion scores only whether the First Floor findings that ARE reported are within these two permitted relationship types and are not duplicated. A first-floor D6 note solely about missing written width is an additional, different relationship and fails this limit.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 45": { + "description": "States the Second Floor overall status as Mismatch, with separate finding counts of exactly 1 Mismatch (acceptable value 1) and 2 Cannot Determine (acceptable value 2) in the building summary.", + "justification": "Second Floor findings: Mismatch S-01 (1); Cannot Determine S-02, S-03 (2). Drawing_Coordination_Review_Standard.pptx page 3 counts each distinct occurrence or independently unresolved relationship once, and under its floor-status table at least one Mismatch makes the status Mismatch.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 46": { + "description": "Limits the Second Floor detailed findings, regardless of equivalent unambiguous Finding ID labels, to one occurrence each of these three relationships: Grid A W2 width at Master Bedroom, Grids 3\u20134 (1.99 m versus 2.00 m on other W2 windows); recessed D6 elevation representation at Grid 4 facade, Bay A\u2013B, in Elevation 02; and D6 visibility beyond Section B-B at the Dressing Room wall end.", + "justification": "Second_Floor_Plan.pdf shows the Master Bedroom Grid A W2 width discrepancy, recessed D6 at Grid 4 Bay A\u2013B, and the Dressing Room wall end affecting D6 visibility beyond Section B-B. Elevation_02.pdf addresses the recessed D6 elevation uncertainty and Section_B_B.pdf shows the relevant section-view geometry. Drawing_Coordination_Review_Standard.pptx pages 3\u20134 require independent relationships to be counted separately and repeated occurrences not to be duplicated. Grading accepts any unambiguous equivalent Finding ID.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 47": { + "description": "States the Third Floor overall status as Mismatch, with separate finding counts of exactly 1 Mismatch (acceptable value 1) and 0 Cannot Determine (acceptable value 0) in the building summary.", + "justification": "Third Floor findings: Mismatch T-01 (1); Cannot Determine none (0). Drawing_Coordination_Review_Standard.pptx page 3 counts each distinct occurrence or independently unresolved relationship once, and under its floor-status table at least one Mismatch makes the status Mismatch.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 48": { + "description": "Limits the Third Floor detailed findings, regardless of equivalent unambiguous Finding ID labels, to one occurrence of the Grid A facade W2 written-width discrepancy at Bedroom 2, Grids 3\u20134 (1.99 m versus 2.00 m for other W2 windows on the Third Floor Plan).", + "justification": "Third_Floor_Plan.pdf shows Grid A W2 by Bedroom 2 at 1.99 m versus 2.00 m at other W2 occurrences on that plan. Drawing_Coordination_Review_Standard.pptx pages 3\u20134 require the exception-only finding to be assigned to its actual floor and counted once; unambiguous equivalent Finding IDs are accepted.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 49": { + "description": "States the Roof overall status as Full Matched, with separate finding counts of exactly 0 Mismatch (acceptable value 0) and 0 Cannot Determine (acceptable value 0) in the building summary.", + "justification": "Roof findings: Mismatch none (0); Cannot Determine none (0). Drawing_Coordination_Review_Standard.pptx page 3 counts each distinct occurrence or independently unresolved relationship once; floor counts are the findings assigned to that floor.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 50": { + "description": "Shows the Roof only in the building summary, with zero detailed findings.", + "justification": "No findings are assigned to the Roof Floor, so the Roof appears only in the building summary as allowed by Drawing_Coordination_Review_Standard.pptx page 4.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 51": { + "description": "Reports a building Mismatch total of exactly 7 in the Mismatch total cell of the Slide 1 building summary, consistent with the five floor-row Mismatch counts (acceptable value 7).", + "justification": "Drawing_Coordination_Review_Standard.pptx page 4 requires both building totals in the Slide 1 building summary; page 3 defines building totals as the sum of the five floor counts. Mismatch floor counts: Ground 4 (G-01, G-02, G-03, G-04), First 1 (F-01), Second 1 (S-01), Third 1 (T-01), Roof 0. The Slide 1 summary Mismatch total cell must therefore show 7 (4 + 1 + 1 + 1 + 0); a correct number stated only elsewhere cannot substitute for an incorrect or blank total cell.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 52": { + "description": "Reports a building Cannot Determine total of exactly 3 in the Cannot Determine total cell of the Slide 1 building summary, consistent with the five floor-row Cannot Determine counts (acceptable value 3).", + "justification": "Drawing_Coordination_Review_Standard.pptx page 4 requires both building totals in the Slide 1 building summary; page 3 defines building totals as the sum of the five floor counts. Cannot Determine floor counts: Ground 0, First 1 (F-02), Second 2 (S-02, S-03), Third 0, Roof 0. The Slide 1 summary Cannot Determine total cell must therefore show 3 (0 + 1 + 2 + 0 + 0); a correct number stated only elsewhere cannot substitute for an incorrect or blank total cell.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 53": { + "description": "Places only the building summary on slide 1, before any detailed findings.", + "justification": "Drawing_Coordination_Review_Standard.pptx page 4 places the building summary on Slide 1, before the findings, with no separate cover.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 54": { + "description": "Displays all five floor summary rows in the order Ground, First, Second, Third, Roof.", + "justification": "Drawing_Coordination_Review_Standard.pptx page 4 orders the summary rows from the lowest floor up to the roof (Ground, First, Second, Third, Roof); the Roof row appears even with no findings.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 55": { + "description": "Groups each detailed finding under the heading for its source-plan floor.", + "justification": "Drawing_Coordination_Review_Standard.pptx page 4 requires detailed exception findings to be organized by their relevant floor. Score only whether any presented finding is grouped under its identified source-plan floor heading. The accuracy and completeness of findings, duplicate occurrences, and the Roof zero-finding rule are graded separately.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 56": { + "description": "Presents the detailed findings in a table that gives each finding\u2019s ID, location, classification and reason, with its source drawings stated in the table or in labels tied to its crops; any equivalent column headings are accepted.", + "justification": "Drawing_Coordination_Review_Standard.pptx page 4 lists Finding ID, affected floor(s), identifiable location, source drawings, classification and precise reason for each finding. Affected drawings may be stated in the row or in source labels tied to the adjacent crops.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 57": { + "description": "States every dimension cited in the findings as a written dimension printed on the drawings, with no scaled or estimated measurements.", + "justification": "Drawing_Coordination_Review_Standard.pptx page 1 prohibits scaling drawings and inferring undocumented tolerances or missing values. This check independently evaluates the method used to justify findings; it does not regrade which findings are included or how they are classified.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 58": { + "description": "Names the output file Architectural_Section_Elevation_Opening_Coordination_Audit.pptx.", + "justification": "The prompt specifies this exact output file name.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 59": { + "description": "Keeps the report within 10 slides.", + "justification": "The prompt and Drawing_Coordination_Review_Standard.pptx pages 4\u20135 set a maximum of 10 slides, including the summary.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 60": { + "description": "Uses a 16:9 widescreen slide size.", + "justification": "Drawing_Coordination_Review_Standard.pptx page 5 specifies a 16:9 widescreen slide format.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 61": { + "description": "Uses Aptos for all report-authored text, excluding original source drawing crops.", + "justification": "Drawing_Coordination_Review_Standard.pptx page 5 specifies Aptos for all report text; text inside original drawing crops is excluded.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 62": { + "description": "Formats every analytical slide title at 24 pt.", + "justification": "Drawing_Coordination_Review_Standard.pptx page 5 specifies 24 pt slide titles.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 63": { + "description": "Formats every analytical slide title in bold.", + "justification": "Drawing_Coordination_Review_Standard.pptx page 5 specifies bold slide titles.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 64": { + "description": "Colors every analytical slide title dark teal #214E52.", + "justification": "Drawing_Coordination_Review_Standard.pptx page 5 specifies dark teal #214E52 slide titles.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 4, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 65": { + "description": "Keeps authored body and table text at 11 pt or larger.", + "justification": "Drawing_Coordination_Review_Standard.pptx page 5 specifies body and table text of at least 11 pt; text inside drawing crops is excluded.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 66": { + "description": "Uses uniform off-white #F7F6F2 slide backgrounds.", + "justification": "Drawing_Coordination_Review_Standard.pptx page 5 specifies a solid warm off-white #F7F6F2 background.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 4, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 67": { + "description": "Fills every table header row with teal #2F6F73.", + "justification": "Drawing_Coordination_Review_Standard.pptx page 5 specifies a teal #2F6F73 table header fill.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 4, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 68": { + "description": "Formats every table header text in white.", + "justification": "Drawing_Coordination_Review_Standard.pptx page 5 specifies white table header text.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 4, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 69": { + "description": "Fills regular table body cells in white.", + "justification": "Drawing_Coordination_Review_Standard.pptx page 5 specifies white regular table cells.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 4, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 70": { + "description": "Formats regular table body text in dark #1F1F1F.", + "justification": "Drawing_Coordination_Review_Standard.pptx page 5 specifies dark #1F1F1F regular table text.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 4, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 71": { + "description": "Fills the Roof Full Matched status cell in the building summary with #E8F5E9.", + "justification": "Drawing_Coordination_Review_Standard.pptx page 5 assigns #E8F5E9 to Full Matched status cells. The Roof row is the only Full Matched floor in this review, so its status cell in the Slide 1 building summary must carry that fill; a Roof status cell left unfilled or filled with another colour fails.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 4, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 72": { + "description": "Fills every Mismatch status cell with #FDECEA.", + "justification": "Drawing_Coordination_Review_Standard.pptx page 5 assigns #FDECEA to Mismatch status cells.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 4, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 73": { + "description": "Fills every Cannot Determine status cell with #FFF4D6.", + "justification": "Drawing_Coordination_Review_Standard.pptx page 5 assigns #FFF4D6 to Cannot Determine status cells.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 4, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 74": { + "description": "Displays each source drawing crop without stretching or distortion, preserving the aspect ratio of the source region actually visible after cropping.", + "justification": "Drawing_Coordination_Review_Standard.pptx pages 4\u20135 require original drawing crops to retain their visual proportions. For embedded PowerPoint images, evaluate the aspect ratio of the displayed picture shape against the source-image REGION REMAINING AFTER any crop_left, crop_right, crop_top and crop_bottom settings, not against the full original bitmap when cropped. Nominal rounding in stored dimensions is not distortion. Grade the visible result, not an uncropped-image assumption.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 75": { + "description": "Shows every drawing crop in its original colors.", + "justification": "Drawing_Coordination_Review_Standard.pptx page 5 states that source drawing crops are not recolored.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 76": { + "description": "Keeps all finding text, summary counts and evidence crops fully visible and separate from one another.", + "justification": "Drawing_Coordination_Review_Standard.pptx pages 4\u20135 require findings and evidence to remain readable at 11 pt minimum; text boxes, tables and crops are checked for clipping or overlap in the rendered slides.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 77": { + "description": "Limits report commentary to documented drawing findings and their explanations, without presenting recommendations or proposed design corrections.", + "justification": "Drawing_Coordination_Review_Standard.pptx pages 1 and 4 specify a findings-only exception report and prohibit recommendations and design corrections. Evaluate whether the delivered PPTX includes an actionable recommendation or proposed correction anywhere, independent of whether its finding identifiers or classifications are correct.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 78": { + "description": "Uses the specified drawing-coordination classifications without adding severity ratings, priority scores, or severity-ranking columns to findings.", + "justification": "Drawing_Coordination_Review_Standard.pptx page 4 explicitly prohibits severity ratings. This criterion grades the presence of any severity/priority assessment, not the correctness of Mismatch or Cannot Determine classifications (graded separately).", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 79": { + "description": "Bases coordination conclusions on the supplied drawings and the attached review standard, without citing external building codes or outside design-preference standards as grounds for a finding.", + "justification": "Drawing_Coordination_Review_Standard.pptx page 1 states findings must be based only on the supplied drawings and prohibits external codes and design preferences. Grade the use of external authorities to support a conclusion separately from dimension-scaling restrictions.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 80": { + "description": "Limits the detailed findings table rows to Mismatch and Cannot Determine classifications, with no Match rows.", + "justification": "Drawing_Coordination_Review_Standard.pptx page 4 describes the report as an exception register rather than a catalogue of correctly coordinated items and prohibits Match rows. Grade any Match row in the detailed findings table independently of the correctness of the Mismatch and Cannot Determine rows.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 81": { + "description": "Restricts the three prescribed status fill colors (#E8F5E9, #FDECEA, #FFF4D6) to status-classification cells, rather than using those fills in headers, count cells, finding reasons, or other non-status cells.", + "justification": "Drawing_Coordination_Review_Standard.pptx page 5 explicitly says status colors apply only to status cells. This evaluates WHERE the three status colors are applied, independently of the criteria that evaluate the correct fill on applicable status cells.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 82": { + "description": "Limits slides 2 onward to detailed exception findings and their drawing-evidence crops.", + "justification": "Drawing_Coordination_Review_Standard.pptx page 4 states Remaining slides | Findings only, and specifies no cover. This grades off-purpose slide content even if Slide 1 correctly contains the summary and the total slide count is within 10.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 83": { + "description": "Describes coordination discrepancies in neutral drawing-based terms without assigning responsibility or fault to the designer, contractor, or other project participants.", + "justification": "Drawing_Coordination_Review_Standard.pptx page 1 explicitly forbids assigning fault. The outcome check is whether the delivered report attributes blame; it does not reconsider the technical evidence or Mismatch/Cannot Determine classifications.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 84": { + "description": "Formats every table header text in bold.", + "justification": "Drawing_Coordination_Review_Standard.pptx page 5 specifies bold table header text.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + } +} \ No newline at end of file diff --git a/tasks/task_c9ab91021dc14eab926dfea0a208108a/input/01_Scope_and_Reporting_Memorandum.pdf b/tasks/task_c9ab91021dc14eab926dfea0a208108a/input/01_Scope_and_Reporting_Memorandum.pdf new file mode 100644 index 0000000000000000000000000000000000000000..9e44582799ccc3de57887835b340ec56a0415ddb --- /dev/null +++ b/tasks/task_c9ab91021dc14eab926dfea0a208108a/input/01_Scope_and_Reporting_Memorandum.pdf @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3b4d39d9ed2e365f93416f5d200da509a81f7ebee15e2f9f5c13a338cb02d02f +size 95488 diff --git a/tasks/task_c9ab91021dc14eab926dfea0a208108a/input/02_Arden_QoE_Databook.xlsx b/tasks/task_c9ab91021dc14eab926dfea0a208108a/input/02_Arden_QoE_Databook.xlsx new file mode 100644 index 0000000000000000000000000000000000000000..12eb110b1c24b41817b50bc2f3abb0b1b190af63 --- /dev/null +++ b/tasks/task_c9ab91021dc14eab926dfea0a208108a/input/02_Arden_QoE_Databook.xlsx @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:36b45b21883a6253e2840e348106cef808c321057dfbcad25371f54d5f96d96c +size 48350 diff --git a/tasks/task_c9ab91021dc14eab926dfea0a208108a/input/03_Commercial_Diligence_Market_Assessment.pdf b/tasks/task_c9ab91021dc14eab926dfea0a208108a/input/03_Commercial_Diligence_Market_Assessment.pdf new file mode 100644 index 0000000000000000000000000000000000000000..4e08173c6fe06d44ccd477062dfa1a21ee8067d8 --- /dev/null +++ b/tasks/task_c9ab91021dc14eab926dfea0a208108a/input/03_Commercial_Diligence_Market_Assessment.pdf @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:822bd8d0d8b9fec4929a46cbd9b3552968c19460f4813efe6d25193064cae9ee +size 620680 diff --git a/tasks/task_c9ab91021dc14eab926dfea0a208108a/input/04_Cloud_Migration_and_Interface_Map.pdf b/tasks/task_c9ab91021dc14eab926dfea0a208108a/input/04_Cloud_Migration_and_Interface_Map.pdf new file mode 100644 index 0000000000000000000000000000000000000000..5c4068c74fa20dd14c17589ae61c59163aa59823 --- /dev/null +++ b/tasks/task_c9ab91021dc14eab926dfea0a208108a/input/04_Cloud_Migration_and_Interface_Map.pdf @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9bc6b486a1bce66d6e21fe98b7ed60afa0cbd466a686e04094a3632baeb143d8 +size 2983095 diff --git a/tasks/task_c9ab91021dc14eab926dfea0a208108a/input/05_Separation_and_TSA_Schedule.xlsx b/tasks/task_c9ab91021dc14eab926dfea0a208108a/input/05_Separation_and_TSA_Schedule.xlsx new file mode 100644 index 0000000000000000000000000000000000000000..42f756ec939d0698cae02bae02ebbde2279f1e04 --- /dev/null +++ b/tasks/task_c9ab91021dc14eab926dfea0a208108a/input/05_Separation_and_TSA_Schedule.xlsx @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:59070eb83b9eb30f47127f0ec330069fdfd00866a39089b8668984871720729b +size 68916 diff --git a/tasks/task_c9ab91021dc14eab926dfea0a208108a/input/06_Integration_Synergy_Schedule.xlsx b/tasks/task_c9ab91021dc14eab926dfea0a208108a/input/06_Integration_Synergy_Schedule.xlsx new file mode 100644 index 0000000000000000000000000000000000000000..083bdf9a6de9b163cbdd09e2f80982c21cfeae59 --- /dev/null +++ b/tasks/task_c9ab91021dc14eab926dfea0a208108a/input/06_Integration_Synergy_Schedule.xlsx @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ca7eb81f0a00be6bc5d5c7c98fb44b1248d73e0a1846311bb30d6b881fc17d2b +size 14972 diff --git a/tasks/task_c9ab91021dc14eab926dfea0a208108a/input/07_Management_Investment_Case.pdf b/tasks/task_c9ab91021dc14eab926dfea0a208108a/input/07_Management_Investment_Case.pdf new file mode 100644 index 0000000000000000000000000000000000000000..a5e0b86cdca68e96d7335b1c1d5399907ec7b10b --- /dev/null +++ b/tasks/task_c9ab91021dc14eab926dfea0a208108a/input/07_Management_Investment_Case.pdf @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:390f964bf2a8bb4d53f95d077c4e40592f73f42826e852926a9c3ecc87d61968 +size 73594 diff --git a/tasks/task_c9ab91021dc14eab926dfea0a208108a/input/08_Executed_Transfer_Instruments.pdf b/tasks/task_c9ab91021dc14eab926dfea0a208108a/input/08_Executed_Transfer_Instruments.pdf new file mode 100644 index 0000000000000000000000000000000000000000..710a04263fd7539ba8f5acf5f6d9324c84dd04d4 --- /dev/null +++ b/tasks/task_c9ab91021dc14eab926dfea0a208108a/input/08_Executed_Transfer_Instruments.pdf @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f5697da7635c609d0751b1dbfec8497588ce8cae479003d4a001088bacf659de +size 1726409 diff --git a/tasks/task_c9ab91021dc14eab926dfea0a208108a/input/09_Hosting_Topology_and_Capacity_Pools.pdf b/tasks/task_c9ab91021dc14eab926dfea0a208108a/input/09_Hosting_Topology_and_Capacity_Pools.pdf new file mode 100644 index 0000000000000000000000000000000000000000..a86961c7824cf3b0f3a7f0c96aed839aba1e166d --- /dev/null +++ b/tasks/task_c9ab91021dc14eab926dfea0a208108a/input/09_Hosting_Topology_and_Capacity_Pools.pdf @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5d1332242526784a0bb34b20e847f4e7002e83f6af4c7d2523956cf54e2c28b2 +size 1592152 diff --git a/tasks/task_c9ab91021dc14eab926dfea0a208108a/input/10_Group_Recharge_Allocation_Map.pdf b/tasks/task_c9ab91021dc14eab926dfea0a208108a/input/10_Group_Recharge_Allocation_Map.pdf new file mode 100644 index 0000000000000000000000000000000000000000..77876624cb73da2a272a20dfc1a3fe378627c5f3 --- /dev/null +++ b/tasks/task_c9ab91021dc14eab926dfea0a208108a/input/10_Group_Recharge_Allocation_Map.pdf @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:965e639887c944818a8a8103e95b8aeb2a989762ac74d9fa6feb0cfc0a4dd1aa +size 1193766 diff --git a/tasks/task_c9ab91021dc14eab926dfea0a208108a/metadata.json b/tasks/task_c9ab91021dc14eab926dfea0a208108a/metadata.json new file mode 100644 index 0000000000000000000000000000000000000000..84d82df24b84739d3ef0e2de6b8fb72ae2b75909 --- /dev/null +++ b/tasks/task_c9ab91021dc14eab926dfea0a208108a/metadata.json @@ -0,0 +1,12 @@ +{ + "TaskID": "task_c9ab91021dc14eab926dfea0a208108a", + "Vertical": "Finance", + "Domain": "Management Consulting", + "Role": "Investment analyst", + "Task Goal": "Prepare an investment committee pre-read with a recommendation on a proposed acquisition.", + "Prompt": "Prepare the Project Relay pre-read for Halcyon's Investment Committee (IC) on the proposed acquisition of Arden People Technologies Ltd and Arden Software Ireland Ltd from Calderwood Group plc at an enterprise value of 465.0 million (USD). Conduct the analysis as at the 31 March 2026 information cut-off and give the IC a recommendation it can act on, with the terms that attach to it.\n\nThe ten attachments are the complete confirmatory diligence record. The approval criteria and basis of preparation in the scope and reporting memorandum govern every test, figure, recommendation label and conflict between sources. Where resolving a conflict changes a test result, state how it was resolved. For each standing test, give the threshold, the position measured and the outcome.\n\nReturn the Project Relay IC memorandum directly in your final response, not as a separate file of no more than 1,500 words, including the source ledger. Use these headings in uppercase, in this order, with one blank line after each heading and between sections:\n\nPROJECT RELAY - INVESTMENT COMMITTEE MEMORANDUM\nDECISION\nEXECUTIVE RATIONALE\nGROWTH QUALITY\nNORMALIZED STANDALONE ECONOMICS\nTECHNOLOGY AND SEPARATION\nPEOPLE PERIMETER\nBENEFITS RECONCILIATION\nIC CONDITIONS TO APPROVAL\nIC UNDERWRITING CONSTRAINT\nSOURCE LEDGER\n\nPresent the conditions as a numbered list, giving the required action, accountable owner and deadline for each. Write every other section except the source ledger as narrative paragraphs of no more than four sentences, with no Markdown tables, bullets or typographic emphasis. In the source ledger, give one entry per line naming the conclusion, the filename and the precise location (sheet, section, table, exhibit or register entry) for every conclusion that decides an approval test, the recommendation, a condition or the underwriting constraint. State money in USD millions to one decimal place, and percentages, percentage-point differences, margins and multiples to one decimal place.", + "Input_files": "01_Scope_and_Reporting_Memorandum.pdf, 02_Arden_QoE_Databook.xlsx, 03_Commercial_Diligence_Market_Assessment.pdf, 04_Cloud_Migration_and_Interface_Map.pdf, 05_Separation_and_TSA_Schedule.xlsx, 06_Integration_Synergy_Schedule.xlsx, 07_Management_Investment_Case.pdf, 08_Executed_Transfer_Instruments.pdf, 09_Hosting_Topology_and_Capacity_Pools.pdf, 10_Group_Recharge_Allocation_Map.pdf", + "All Task Files": "tasks/task_c9ab91021dc14eab926dfea0a208108a/input/", + "Rubric Criteria": "tasks/task_c9ab91021dc14eab926dfea0a208108a/rubrics.json", + "Economic Rationale": "A carve-out IC paper like this usually takes a senior diligence team two to three days. Most of that time is spent reconciling the data room: checking exhibits against the workbooks, working out which revision or handwritten correction applies, and deciding which numbers hold up. Getting a reliable first draft would save 12 to 16 hours of senior time each time the evidence changes. It also matters for accuracy. This deal sits close to the line on several tests, so one misread chart, recharge band or hosting pool can turn a USD 465 million recommendation the wrong way." +} diff --git a/tasks/task_c9ab91021dc14eab926dfea0a208108a/rubrics.json b/tasks/task_c9ab91021dc14eab926dfea0a208108a/rubrics.json new file mode 100644 index 0000000000000000000000000000000000000000..87a29da8c72f03bc32d917222aba6f49027beae5 --- /dev/null +++ b/tasks/task_c9ab91021dc14eab926dfea0a208108a/rubrics.json @@ -0,0 +1,884 @@ +{ + "criterion 1": { + "description": "States the recommendation as Do not proceed.", + "justification": "Paragraph 4.10 of Appendix A in 01_Scope_and_Reporting_Memorandum.pdf says that where two or more standing tests are failed the Committee records Do not proceed, and section 4 of 01_Scope_and_Reporting_Memorandum.pdf requires the paper to recommend it. Exactly two tests fail: the technology and separation readiness test (4.5) at a weighted 79.6% and the benefits test (4.6) at USD 3.0 million. Growth is met subject to conditions and the margin, entry multiple and retention tests are met. A memo that misses either failure finds one failed test and reaches Proceed subject to conditions with a departure, which is the wrong label; a false failure elsewhere (the Figure 4.1 reading, the correction note on the Standalone costs sheet in 02_Arden_QoE_Databook.xlsx, or the backfill plan on SEP-04) leaves the label in place and is scored on its own rows.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 5, + "grading_target": "Final Answer Only (No Files)", + "dependencies": [] + }, + "criterion 2": { + "description": "States, in the DECISION section, that two standing tests fail, the technology and separation readiness test (4.5) and the benefits test (4.6).", + "justification": "This conclusion needs several complex visuals read together. The technology test fails on limb (a) only with the Pay and HR Core lines in Exhibit 04A Rev 2 in 04_Cloud_Migration_and_Interface_Map.pdf assigned correctly, the callout value of 80.0 applied to Arden Time in place of the plotted 85.0 (which gives 80.3%), and the connector from step 4 in Exhibit 04D keeping the final issued points (the step 5 move gives 81.6%). The benefits test fails only with the four UK pools and the four Irish pools in Exhibit 04C in 09_Hosting_Topology_and_Capacity_Pools.pdf placed correctly against the C-041 regions in the schedule to paragraph 4.6 on page 5 of 01_Scope_and_Reporting_Memorandum.pdf, and with MI-01 not validated on management's own schedule (validating it gives USD 5.2 million). The other tests hold: the entry multiple passes at 10.8x only with SA-4 at the corrected 1.85 from the correction note on the Standalone costs sheet in 02_Arden_QoE_Databook.xlsx and the recharge credits traced in 10_Group_Recharge_Allocation_Map.pdf (corporate functions flows 3 and 9, engine flow 12, insurance flow 28 against SA-2), where the printed 2.75 gives 11.11x; growth is met subject to conditions on the 9.5% reading in Figure 4.1 of 03_Commercial_Diligence_Market_Assessment.pdf; and retention is met under limb (b) on SEP-04 in 05_Separation_and_TSA_Schedule.xlsx, although the execution page in 08_Executed_Transfer_Instruments.pdf, read with the register extract picture on the Signing Authorities sheet, shows that the deed does not bind the employer.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 5, + "grading_target": "Final Answer Only (No Files)", + "dependencies": [] + }, + "criterion 3": { + "description": "States that no departure is available under paragraph 4.10 because two standing tests are failed.", + "justification": "Paragraph 4.10 of Appendix A in 01_Scope_and_Reporting_Memorandum.pdf: a departure may be recorded in respect of not more than one failed standing test; where two or more standing tests are failed the Committee records Do not proceed, and the paper states the remediation on which the Committee would reconsider.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 5, + "grading_target": "Final Answer Only (No Files)", + "dependencies": [] + }, + "criterion 4": { + "description": "States FY25 organic ARR growth as 7.5%, to one decimal place (acceptable range 7.45% to 7.55%).", + "justification": "ARR movement sheet in 02_Arden_QoE_Databook.xlsx: closing 114.14 less acquired PeoplePort 8.36 gives organic closing 105.78; 105.78 / 98.40 - 1 = 7.5% exactly. Paragraph 4.3 of Appendix A and B.6 of Appendix B in 01_Scope_and_Reporting_Memorandum.pdf exclude acquired ARR even though it is now reported within Arden HR Core. The prompt and B.8 of Appendix B in 01_Scope_and_Reporting_Memorandum.pdf require this figure as a percentage to one decimal place; that presentation requirement is part of this criterion, and the range brackets the unrounded value.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 5, + "grading_target": "Final Answer Only (No Files)", + "dependencies": [] + }, + "criterion 5": { + "description": "States the relevant market as the Padgett Rowe UK and Ireland payroll and HCM segment for smaller and mid-sized employers. For reference, Padgett Rowe defines that segment as employers of 20 to 999 employees, and employers of 1,000 or more form the enterprise segment. Naming the correct Padgett Rowe segment is enough and the memo need not state employee bounds. Any employee bounds it does state must be consistent with that source definition; equivalent descriptions of the same bounds are accepted.", + "justification": "B.6 of Appendix B in 01_Scope_and_Reporting_Memorandum.pdf treats a segment as corresponding where at least 75% of closing ARR falls inside its boundary on each dimension, and takes the narrowest such segment. From Tables 4.5, 4.6a, 4.6b and 4.7 in 03_Commercial_Diligence_Market_Assessment.pdf: Padgett Rowe holds 98.3% on geography, 80.1% on size and all four modules; Brightwell fails on size (16.8%); Marchmont fails on product (Arden Time 13.9%); Fenchurch corresponds but is wider on every dimension. Paragraph 4.3 of Appendix A in 01_Scope_and_Reporting_Memorandum.pdf tests the narrowest published market segment, and B.10 of Appendix B takes a third-party reading from the publisher's published edition. The Fenchurch UK HR technology sub-panel in Table 4.3 is a cut of the European panel, whose markets Table 4.5 records as not reported separately in the subscriber edition, and Table 4.3 carries it as an adjacent reading not carried into the comparison, so it is not a candidate segment. Taking it as the relevant market (10.0% for FY25 in Figure 4.1) would give a 2.5 percentage point gap and a false failure. The reference figures in the criterion come from Table 4.5 (Padgett Rowe: employers of 20 to 999 employees) and the employer-size boundaries note in 03_Commercial_Diligence_Market_Assessment.pdf (Brightwell's enterprise universe begins at 1,000 employees); the memo is not required to state either boundary. Omitting the numerical bounds is allowed; an explicitly contradictory lower or upper employee boundary is not a correct description of the named segment. Even taken as a candidate, the sub-panel is narrower than Padgett Rowe on geography only and wider on employer size and software category, so Padgett Rowe stays the narrowest.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Final Answer Only (No Files)", + "dependencies": [] + }, + "criterion 6": { + "description": "States the relevant market's FY25 growth reading as 9.5%, to one decimal place (acceptable range 9.45% to 9.55%).", + "justification": "Figure 4.1 in 03_Commercial_Diligence_Market_Assessment.pdf plots readings without value labels on 0.5 percentage point gridlines. All eleven series share one line style and are named only at FY16. The Padgett Rowe (1) line starts at 10.0% in FY16 and runs 9.5, 9.0, 8.0, 8.5, 8.0, 9.0, 10.0 and 10.5 to FY24, then falls to 9.5% at FY25; Marchmont (3) UK sits at 10.0% at FY24, one gridline below it, and rises to 11.0%, crossing it, while the Fenchurch UK sub-panel line runs from 11.0% to 10.0% beside the P mark. Following the straighter path at FY24 lands on Marchmont's 11.0%. Note 3 says the Padgett Rowe line ends at the FY2025 edition as amended by Addendum 1; the lettered marks beside the column are P, the provisional pulse (10.0%), A2, the draft Addendum 2 (9.0%), and D, the superseded December edition (8.5%), none relied on under B.10 of Appendix B in 01_Scope_and_Reporting_Memorandum.pdf. The reading sits below Padgett Rowe's FY24 10.5%, which rules out Marchmont's 11.0%. Every reading sits on a gridline, so the tolerance allows rounding only. The value appears only in the image. The prompt and B.8 of Appendix B in 01_Scope_and_Reporting_Memorandum.pdf require this figure as a percentage to one decimal place; that presentation requirement is part of this criterion, and the range brackets the unrounded value.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 5, + "grading_target": "Final Answer Only (No Files)", + "dependencies": [] + }, + "criterion 7": { + "description": "States that the Padgett Rowe subscriber pulse (the 10.0% reading) is not relied on because the publisher issued it as provisional. Ranking the 10.0% pulse below the published Addendum 1 reading as provisional under B.10 satisfies this; the pulse need not be identified by its 23 March 2026 date.", + "justification": "In Figure 4.1 in 03_Commercial_Diligence_Market_Assessment.pdf the mark lettered P beside the FY25 column sits on the 10.0% gridline; note 3 says P is the 23 March 2026 subscriber pulse, issued by the publisher as a provisional estimate. B.10 of Appendix B in 01_Scope_and_Reporting_Memorandum.pdf excludes an estimate its publisher marks preliminary or provisional. Using it would give a 2.5 percentage point gap and fail the test, so the prompt requires the resolution to be stated. Equivalent wording is accepted: ranking the 10.0% pulse below the Addendum 1 reading as provisional under B.10 states that it is not relied on; the 23 March 2026 date is identification only.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Final Answer Only (No Files)", + "dependencies": [] + }, + "criterion 8": { + "description": "States that organic growth is 2.0 percentage points below the relevant market, to one decimal place (acceptable value is 2.0 percentage points), within the band of not more than 2.0 percentage points.", + "justification": "9.5% read from Figure 4.1 in 03_Commercial_Diligence_Market_Assessment.pdf less 7.5% organic growth is exactly 2.0 percentage points on unrounded figures (B.8 of Appendix B in 01_Scope_and_Reporting_Memorandum.pdf); paragraph 4.3 includes a shortfall of exactly 2.0 in the conditional band. Floating-point arithmetic in code can return 2.0000000000000046 and a false failure. The prompt and B.8 of Appendix B in 01_Scope_and_Reporting_Memorandum.pdf require this figure in percentage points to one decimal place; that presentation requirement is part of this criterion, and the range brackets the unrounded value.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 5, + "grading_target": "Final Answer Only (No Files)", + "dependencies": [] + }, + "criterion 9": { + "description": "States the growth test as met subject to conditions.", + "justification": "Paragraph 4.3 of Appendix A in 01_Scope_and_Reporting_Memorandum.pdf: a shortfall of not more than 2.0 percentage points is met subject to conditions. The shortfall against the 9.5% reading in Figure 4.1 of 03_Commercial_Diligence_Market_Assessment.pdf is exactly 2.0. The provisional 10.0% pulse, or Marchmont's 11.0% picked up at the FY24 crossing, would fail the test; the draft 9.0% and superseded 8.5% readings would also give met subject to conditions.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 5, + "grading_target": "Final Answer Only (No Files)", + "dependencies": [] + }, + "criterion 10": { + "description": "States management's reported FY25 ARR growth as 16.0%, to one decimal place.", + "justification": "Section 5 of 07_Management_Investment_Case.pdf reports 16.0%. Section 4 of 01_Scope_and_Reporting_Memorandum.pdf requires management's position and the evidence to be presented with the difference where they differ. The prompt and B.8 of Appendix B in 01_Scope_and_Reporting_Memorandum.pdf require this figure as a percentage to one decimal place; that presentation requirement is part of this criterion, and the range brackets the unrounded value.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Final Answer Only (No Files)", + "dependencies": [] + }, + "criterion 11": { + "description": "States management's adjusted FY25 EBITDA as USD 65.4 million, in USD millions to one decimal place (acceptable range USD 65.35 million to USD 65.45 million).", + "justification": "Adjustments sheet in 02_Arden_QoE_Databook.xlsx: GBP 52.35 million x 1.25 FY25 average rate (B.3 of Appendix B in 01_Scope_and_Reporting_Memorandum.pdf) = USD 65.44 million. The prompt and B.8 of Appendix B in 01_Scope_and_Reporting_Memorandum.pdf require this figure in USD millions to one decimal place; that presentation requirement is part of this criterion, and the range brackets the unrounded value.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Final Answer Only (No Files)", + "dependencies": [] + }, + "criterion 12": { + "description": "States that the reorganisation add-back of USD 2.8 million, in USD millions to one decimal place (acceptable range USD 2.7 million to USD 2.8 million), is reversed.", + "justification": "Cost detail sheet in 02_Arden_QoE_Databook.xlsx: account 7420 carries 1.95, 2.40 and 2.20 in FY23 to FY25, and note 3 of the Basis of Preparation sheet in 06_Integration_Synergy_Schedule.xlsx describes the efficiency programme as in its third year, so B.5 of Appendix B in 01_Scope_and_Reporting_Memorandum.pdf treats it as recurring. GBP 2.20 million x 1.25 = USD 2.75 million. The prompt and B.8 of Appendix B in 01_Scope_and_Reporting_Memorandum.pdf require this figure in USD millions to one decimal place; that presentation requirement is part of this criterion, and the range brackets the unrounded value.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Final Answer Only (No Files)", + "dependencies": [] + }, + "criterion 13": { + "description": "States that the gross standalone cost schedule total is not the incremental standalone adjustment, because recharges already carried in the P&L are credited against it. Any schedule total the memo quotes (the USD 25.2 million printed, the USD 24.0 million recomputed, or the USD 23.7 million on the correction note) is acceptable; the criterion grades the rejection, not the total.", + "justification": "", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Final Answer Only (No Files)", + "dependencies": [] + }, + "criterion 14": { + "description": "States the corporate functions recharge already carried in account 7200 as USD 2.8 million, in USD millions to one decimal place (acceptable range USD 2.7 million to USD 2.8 million).", + "justification": "Group recharge allocation map in 10_Group_Recharge_Allocation_Map.pdf: flow numbers sit where each band enters its recharged entity, so each Arden band has to be traced back through the crossings to its pool. The corporate functions pool reaches Arden through flow 3 (GBP 1.90 million, Arden People Technologies Ltd) and flow 9 (GBP 0.30 million, Arden Software Ireland Ltd), FY25 column; GBP 2.20 million x 1.25 = USD 2.75 million. The UK flow alone gives USD 2.4 million and the FY24 column USD 2.4 million; either misstates the credit, although with the insurance credit the multiple still passes (10.92x and 10.93x). The 10.93x FY24 sensitivity uses all FY24 flows (corporate functions GBP 1.95 million, engine licence GBP 0.85 million and insurance GBP 0.30 million), not only the FY24 corporate functions column. The prompt and B.8 of Appendix B in 01_Scope_and_Reporting_Memorandum.pdf require this figure in USD millions to one decimal place; that presentation requirement is part of this criterion, and the range brackets the unrounded value.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Final Answer Only (No Files)", + "dependencies": [] + }, + "criterion 15": { + "description": "States the calculation engine licence recharge already carried in account 7200 as USD 1.1 million, in USD millions to one decimal place (acceptable range USD 1.05 million to USD 1.15 million).", + "justification": "Group recharge allocation map in 10_Group_Recharge_Allocation_Map.pdf: traced back from the Arden People Technologies Ltd bar, band 12 leaves the statutory calculation engine pool; that pool reaches Arden only through flow 12, GBP 0.90 million in FY25; x 1.25 = USD 1.13 million. Flow 2 (GBP 1.40 million) from the same pool goes to Calderwood Payments Ltd. The prompt and B.8 of Appendix B in 01_Scope_and_Reporting_Memorandum.pdf require this figure in USD millions to one decimal place; that presentation requirement is part of this criterion, and the range brackets the unrounded value.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Final Answer Only (No Files)", + "dependencies": [] + }, + "criterion 16": { + "description": "Credits the existing insurance premium recharge (flow 28) against SA-2 because SA-2 includes the standalone insurance programme.", + "justification": "The Standalone costs sheet in 02_Arden_QoE_Databook.xlsx describes SA-2 (GBP 7.95 million) as the full standalone establishment 'including ... the standalone insurance programme'. The map in 10_Group_Recharge_Allocation_Map.pdf shows flow 28 (GBP 0.35 million FY25) from the group insurance programme to Arden Software Ireland Ltd, posted to account 7350 under note 2. B.2 of Appendix B in 01_Scope_and_Reporting_Memorandum.pdf sets the adjustment as the increase over any existing charge for the same function, so 0.35 is credited against SA-2 together with flows 3 and 9: SA-2 increment 7.95 - 2.20 - 0.35 = GBP 5.40 million. Not crediting it understates EBITDA by USD 0.44 million. Column E names only 7200, but B.2 says the schedule does not perform the comparison, and the carve-out result bears the 0.35 in 7350, so leaving it uncredited carries insurance twice.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Final Answer Only (No Files)", + "dependencies": [] + }, + "criterion 17": { + "description": "States the incremental standalone cost as USD 19.7 million, in USD millions to one decimal place (acceptable range USD 19.65 million to USD 19.75 million). The figure that counts is the one the memo adopts as its measured position; a figure given only as a conditional alternative to a different adopted figure does not satisfy this, and sensitivities shown alongside an adopted figure within the range do not prevent it. Where the memo instead carries SA-2 at the correction note's GBP 7.71 million, or does not credit the insurance recharge (flow 28, GBP 0.35 million) against SA-2, or both, the figure consistent with that stated treatment is accepted in place of USD 19.7 million: USD 19.4 million (SA-2 at 7.71), USD 20.2 million (no insurance credit) or USD 19.9 million (both), each within plus or minus USD 0.05 million.", + "justification": "Apply Appendix B.2 to the current standalone schedule: SA-1 6.05 + SA-2 (7.95 - 2.20 corporate functions - 0.35 insurance) + SA-3 (3.38 - 0.90 engine licence) + SA-4 1.85, the figure on the correction note directly below the schedule and not the printed 2.75, = GBP 15.78 million. Translate at the FY25 average rate 1.25: USD 19.725 million, displayed USD 19.7 million. SA-4 at the printed 2.75 gives GBP 16.68 million and USD 20.9 million. SA-2 stays at the printed 7.95, because the cut on the correction note is the benefit of the acquirer's group volume band, which B.2 does not net against a standalone cost; SA-2 at the 7.71 on the correction note gives GBP 15.54 million and USD 19.4 million. The print/postage charge has no corresponding standalone replacement; SA-1 is already an uplift over hosting charges. The prompt and B.8 of Appendix B in 01_Scope_and_Reporting_Memorandum.pdf require this figure in USD millions to one decimal place; that presentation requirement is part of this criterion, and the range brackets the unrounded value. The prompt asks for the position measured on each test and a recommendation the Committee can act on, so the figure that counts is the one the memo carries into its margin, multiple and underwriting constraint. Alternative treatments accepted by the criterion: SA-2 at the correction note's GBP 7.71 million (incremental cost GBP 15.54 million), no credit of the GBP 0.35 million flow 28 insurance recharge against SA-2 (GBP 16.13 million), or both (GBP 15.89 million); at 1.25 these give USD 19.4 / 20.2 / 19.9 million incremental cost, USD 43.3 / 42.5 / 42.8 million EBITDA, 28.7% / 28.2% / 28.4% margin, 10.7x / 10.9x / 10.9x, USD 475.9 / 467.8 / 471.1 million maximum enterprise value and USD 10.9 / 2.8 / 6.1 million headroom. Every test outcome is unchanged under each treatment. The memo's figure must match the treatment it states; mixing treatments fails.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Final Answer Only (No Files)", + "dependencies": [] + }, + "criterion 18": { + "description": "States normalized standalone EBITDA as USD 43.0 million, in USD millions to one decimal place (acceptable range USD 42.95 million to USD 43.05 million). The figure that counts is the one the memo adopts as its measured position; a figure given only as a conditional alternative to a different adopted figure does not satisfy this, and sensitivities shown alongside an adopted figure within the range do not prevent it. Where the memo instead carries SA-2 at the correction note's GBP 7.71 million, or does not credit the insurance recharge (flow 28, GBP 0.35 million) against SA-2, or both, the figure consistent with that stated treatment is accepted in place of USD 43.0 million: USD 43.3 million (SA-2 at 7.71), USD 42.5 million (no insurance credit) or USD 42.8 million (both), each within plus or minus USD 0.05 million.", + "justification": "GBP 52.35 million management adjusted EBITDA less GBP 2.20 million recurring reorganisation add-back = GBP 50.15 million. Less GBP 15.78 million incremental standalone costs gives GBP 34.37 million. At 1.25 this is USD 42.9625 million, displayed USD 43.0 million. SA-4 at the printed 2.75 gives GBP 33.47 million and USD 41.8 million. SA-2 at the 7.71 on the correction note gives GBP 34.61 million and USD 43.3 million. The prompt and B.8 of Appendix B in 01_Scope_and_Reporting_Memorandum.pdf require this figure in USD millions to one decimal place; that presentation requirement is part of this criterion, and the range brackets the unrounded value. Section 4 of 01_Scope_and_Reporting_Memorandum.pdf and the prompt ask for the position measured on each standing test, and section 4 asks for one underwriting constraint with its headroom, so the adopted figure is the one graded. This adds no requirement on any other figure. Alternative treatments accepted by the criterion: SA-2 at the correction note's GBP 7.71 million (incremental cost GBP 15.54 million), no credit of the GBP 0.35 million flow 28 insurance recharge against SA-2 (GBP 16.13 million), or both (GBP 15.89 million); at 1.25 these give USD 19.4 / 20.2 / 19.9 million incremental cost, USD 43.3 / 42.5 / 42.8 million EBITDA, 28.7% / 28.2% / 28.4% margin, 10.7x / 10.9x / 10.9x, USD 475.9 / 467.8 / 471.1 million maximum enterprise value and USD 10.9 / 2.8 / 6.1 million headroom. Every test outcome is unchanged under each treatment. The memo's figure must match the treatment it states; mixing treatments fails.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 5, + "grading_target": "Final Answer Only (No Files)", + "dependencies": [] + }, + "criterion 19": { + "description": "States the normalized standalone margin as 28.5%, to one decimal place (acceptable range 28.45% to 28.55%). The figure that counts is the one the memo adopts as its measured position; a figure given only as a conditional alternative to a different adopted figure does not satisfy this, and sensitivities shown alongside an adopted figure within the range do not prevent it. Where the memo instead carries SA-2 at the correction note's GBP 7.71 million, or does not credit the insurance recharge (flow 28, GBP 0.35 million) against SA-2, or both, the figure consistent with that stated treatment is accepted in place of 28.5%: 28.7% (SA-2 at 7.71), 28.2% (no insurance credit) or 28.4% (both), each within plus or minus 0.05 percentage points.", + "justification": "Under Appendix B.4 compute in sterling: 34.37 / 120.45 * 100 = 28.5346616853%, displayed 28.5%. SA-4 at the printed 2.75 gives 27.8%, which still meets the floor. SA-2 at the 7.71 on the correction note gives 28.7%. Do not round inputs. The prompt and B.8 of Appendix B in 01_Scope_and_Reporting_Memorandum.pdf require this figure as a percentage to one decimal place; that presentation requirement is part of this criterion, and the range brackets the unrounded value. Section 4 of 01_Scope_and_Reporting_Memorandum.pdf and the prompt ask for the position measured on each standing test, and section 4 asks for one underwriting constraint with its headroom, so the adopted figure is the one graded. This adds no requirement on any other figure. Alternative treatments accepted by the criterion: SA-2 at the correction note's GBP 7.71 million (incremental cost GBP 15.54 million), no credit of the GBP 0.35 million flow 28 insurance recharge against SA-2 (GBP 16.13 million), or both (GBP 15.89 million); at 1.25 these give USD 19.4 / 20.2 / 19.9 million incremental cost, USD 43.3 / 42.5 / 42.8 million EBITDA, 28.7% / 28.2% / 28.4% margin, 10.7x / 10.9x / 10.9x, USD 475.9 / 467.8 / 471.1 million maximum enterprise value and USD 10.9 / 2.8 / 6.1 million headroom. Every test outcome is unchanged under each treatment. The memo's figure must match the treatment it states; mixing treatments fails.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 5, + "grading_target": "Final Answer Only (No Files)", + "dependencies": [] + }, + "criterion 20": { + "description": "States the entry multiple as 10.8x, to one decimal place (acceptable range 10.75x to 10.85x). The figure that counts is the one the memo adopts as its measured position; a figure given only as a conditional alternative to a different adopted figure does not satisfy this, and sensitivities shown alongside an adopted figure within the range do not prevent it. Where the memo instead carries SA-2 at the correction note's GBP 7.71 million, or does not credit the insurance recharge (flow 28, GBP 0.35 million) against SA-2, or both, the figure consistent with that stated treatment is accepted in place of 10.8x: 10.7x (SA-2 at 7.71) or 10.9x (no insurance credit, or both), each within plus or minus 0.05x.", + "justification": "USD 465.0 million / USD 42.9625 million = 10.8233924935x, displayed 10.8x. Test the unrounded result against 11.0x. Omitting GBP 0.30 million Irish corporate credit would give USD 42.5875 million EBITDA and 10.9186968007x, still passing. SA-4 at the printed 2.75, which the correction note replaces, gives USD 41.8375 million and 11.11x, which fails the test. SA-2 at the 7.71 on the correction note gives USD 43.2625 million and 10.7x (10.7483x), still passing. The prompt and B.8 of Appendix B in 01_Scope_and_Reporting_Memorandum.pdf require this figure as a multiple to one decimal place; that presentation requirement is part of this criterion, and the range brackets the unrounded value. Section 4 of 01_Scope_and_Reporting_Memorandum.pdf and the prompt ask for the position measured on each standing test, and section 4 asks for one underwriting constraint with its headroom, so the adopted figure is the one graded. This adds no requirement on any other figure. Alternative treatments accepted by the criterion: SA-2 at the correction note's GBP 7.71 million (incremental cost GBP 15.54 million), no credit of the GBP 0.35 million flow 28 insurance recharge against SA-2 (GBP 16.13 million), or both (GBP 15.89 million); at 1.25 these give USD 19.4 / 20.2 / 19.9 million incremental cost, USD 43.3 / 42.5 / 42.8 million EBITDA, 28.7% / 28.2% / 28.4% margin, 10.7x / 10.9x / 10.9x, USD 475.9 / 467.8 / 471.1 million maximum enterprise value and USD 10.9 / 2.8 / 6.1 million headroom. Every test outcome is unchanged under each treatment. The memo's figure must match the treatment it states; mixing treatments fails.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 5, + "grading_target": "Final Answer Only (No Files)", + "dependencies": [] + }, + "criterion 21": { + "description": "States the margin test as met against the 25.0% floor.", + "justification": "Paragraph 4.4(a) of Appendix A in 01_Scope_and_Reporting_Memorandum.pdf: 28.5% is not less than 25.0%.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 5, + "grading_target": "Final Answer Only (No Files)", + "dependencies": [] + }, + "criterion 22": { + "description": "States the entry multiple test as met against the 11.0x ceiling.", + "justification": "Paragraph 4.4(b) of Appendix A in 01_Scope_and_Reporting_Memorandum.pdf, as amended to 11.0x by Amendment 3: 10.8x is not more than 11.0x. Taking SA-4 at the printed 2.75 (11.11x), deducting the schedule total (12.0x with SA-4 at 1.85, 11.9x on the total the correction note prints, 12.4x printed) or rejecting the platform discovery add-back (11.05x) would breach it.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 5, + "grading_target": "Final Answer Only (No Files)", + "dependencies": [] + }, + "criterion 23": { + "description": "States the underwriting constraint as a maximum enterprise value of USD 472.6 million, in USD millions to one decimal place (acceptable range USD 472.55 million to USD 472.65 million). The figure that counts is the one the memo adopts as its measured position; a figure given only as a conditional alternative to a different adopted figure does not satisfy this, and sensitivities shown alongside an adopted figure within the range do not prevent it. Where the memo instead carries SA-2 at the correction note's GBP 7.71 million, or does not credit the insurance recharge (flow 28, GBP 0.35 million) against SA-2, or both, the figure consistent with that stated treatment is accepted in place of USD 472.6 million: USD 475.9 million (SA-2 at 7.71), USD 467.8 million (no insurance credit) or USD 471.1 million (both), each within plus or minus USD 0.05 million.", + "justification": "Section 4 and Appendix A paragraph 4.4(b) set the ceiling: 11.0 * USD 42.9625 million unrounded EBITDA = USD 472.5875 million, displayed USD 472.6 million. SA-4 at the printed 2.75 gives USD 460.2 million. SA-2 at the 7.71 on the correction note gives USD 475.9 million. The prompt and B.8 of Appendix B in 01_Scope_and_Reporting_Memorandum.pdf require this figure in USD millions to one decimal place; that presentation requirement is part of this criterion, and the range brackets the unrounded value. Section 4 of 01_Scope_and_Reporting_Memorandum.pdf and the prompt ask for the position measured on each standing test, and section 4 asks for one underwriting constraint with its headroom, so the adopted figure is the one graded. This adds no requirement on any other figure. Alternative treatments accepted by the criterion: SA-2 at the correction note's GBP 7.71 million (incremental cost GBP 15.54 million), no credit of the GBP 0.35 million flow 28 insurance recharge against SA-2 (GBP 16.13 million), or both (GBP 15.89 million); at 1.25 these give USD 19.4 / 20.2 / 19.9 million incremental cost, USD 43.3 / 42.5 / 42.8 million EBITDA, 28.7% / 28.2% / 28.4% margin, 10.7x / 10.9x / 10.9x, USD 475.9 / 467.8 / 471.1 million maximum enterprise value and USD 10.9 / 2.8 / 6.1 million headroom. Every test outcome is unchanged under each treatment. The memo's figure must match the treatment it states; mixing treatments fails.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 5, + "grading_target": "Final Answer Only (No Files)", + "dependencies": [] + }, + "criterion 24": { + "description": "States the headroom between the underwriting constraint and the agreed enterprise value as USD 7.6 million, in USD millions to one decimal place (acceptable range USD 7.55 million to USD 7.65 million). The figure that counts is the one the memo adopts as its measured position; a figure given only as a conditional alternative to a different adopted figure does not satisfy this, and sensitivities shown alongside an adopted figure within the range do not prevent it. Where the memo instead carries SA-2 at the correction note's GBP 7.71 million, or does not credit the insurance recharge (flow 28, GBP 0.35 million) against SA-2, or both, the figure consistent with that stated treatment is accepted in place of USD 7.6 million: USD 10.9 million (SA-2 at 7.71), USD 2.8 million (no insurance credit) or USD 6.1 million (both), each within plus or minus USD 0.05 million.", + "justification": "USD 472.5875 million unrounded maximum enterprise value less USD 465.0 million = USD 7.5875 million headroom, displayed USD 7.6 million. SA-4 at the printed 2.75 gives a shortfall of USD 4.8 million. SA-2 at the 7.71 on the correction note gives headroom of USD 10.9 million. The prompt and B.8 of Appendix B in 01_Scope_and_Reporting_Memorandum.pdf require this figure in USD millions to one decimal place; that presentation requirement is part of this criterion, and the range brackets the unrounded value. Section 4 of 01_Scope_and_Reporting_Memorandum.pdf and the prompt ask for the position measured on each standing test, and section 4 asks for one underwriting constraint with its headroom, so the adopted figure is the one graded. This adds no requirement on any other figure. Alternative treatments accepted by the criterion: SA-2 at the correction note's GBP 7.71 million (incremental cost GBP 15.54 million), no credit of the GBP 0.35 million flow 28 insurance recharge against SA-2 (GBP 16.13 million), or both (GBP 15.89 million); at 1.25 these give USD 19.4 / 20.2 / 19.9 million incremental cost, USD 43.3 / 42.5 / 42.8 million EBITDA, 28.7% / 28.2% / 28.4% margin, 10.7x / 10.9x / 10.9x, USD 475.9 / 467.8 / 471.1 million maximum enterprise value and USD 10.9 / 2.8 / 6.1 million headroom. Every test outcome is unchanged under each treatment. The memo's figure must match the treatment it states; mixing treatments fails.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 5, + "grading_target": "Final Answer Only (No Files)", + "dependencies": [] + }, + "criterion 25": { + "description": "States the Arden Pay hosted share at 31 March 2026 as 92.5%, to one decimal place (acceptable range 92.0% to 93.0%). The figure that counts is the one the memo adopts as its measured position; a figure given only as a conditional alternative to a different adopted figure does not satisfy this, and sensitivities shown alongside an adopted figure within the range do not prevent it.", + "justification": "Section 4 of 01_Scope_and_Reporting_Memorandum.pdf requires each product's share at the measurement date. Exhibit 04A Rev 2 (issued) in 04_Cloud_Migration_and_Interface_Map.pdf: each product panel stacks production workload by hosting location to 100% (Kelmarsh legacy at the bottom, then the Arden cloud platform, PeoplePort and third-party hosting, and Beechfield colocation), with the tenant share as a dashed overlay and the plan as diamonds. The cloud share is the depth of the second layer at the Q1-26 column, so it takes two boundary reads on the 2.5-point steps. At Q1-26 the Kelmarsh legacy layer runs from 0 to 5.0 and the cloud layer from 5.0 to 97.5, so the cloud depth is 92.5; the dashed tenant overlay ends at 95.0 and the plan diamond at 97.5, neither of which counts. Note 4 of Exhibit 04A and note 1 of Exhibit 04D on page 4 of 04_Cloud_Migration_and_Interface_Map.pdf say points are plotted before the last steps of the recording pathway, so the share recorded is the value at the foot of the pathway. At Q1-26 the largest gap between the source systems is 0.5 points, so step 4 answers NO and its connector runs straight into the NO box beside step 5, Keep the final issued point, which bypasses the step 5 question; the recorded share stays 92.5. Reading step 5 as the next numbered step and moving Pay up one gridline gives 95.0, which is not the recorded share. The value appears only in the image. The prompt and B.8 of Appendix B in 01_Scope_and_Reporting_Memorandum.pdf require this figure as a percentage to one decimal place; that presentation requirement is part of this criterion, and the range brackets the unrounded value. Section 4 of 01_Scope_and_Reporting_Memorandum.pdf and the prompt ask for the position measured on each standing test, so the adopted figure is the one graded. This adds no requirement on any other figure.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Final Answer Only (No Files)", + "dependencies": [] + }, + "criterion 26": { + "description": "States the Arden HR Core hosted share at 31 March 2026 as 82.5%, to one decimal place (acceptable range 82.0% to 83.0%). The figure that counts is the one the memo adopts as its measured position; a figure given only as a conditional alternative to a different adopted figure does not satisfy this, and sensitivities shown alongside an adopted figure within the range do not prevent it.", + "justification": "Section 4 of 01_Scope_and_Reporting_Memorandum.pdf requires each product's share at the measurement date. Exhibit 04A Rev 2 (issued) in 04_Cloud_Migration_and_Interface_Map.pdf: each product panel stacks production workload by hosting location to 100% (Kelmarsh legacy at the bottom, then the Arden cloud platform, PeoplePort and third-party hosting, and Beechfield colocation), with the tenant share as a dashed overlay and the plan as diamonds. The cloud share is the depth of the second layer at the Q1-26 column, so it takes two boundary reads on the 2.5-point steps. At Q1-26 the legacy layer runs from 0 to 2.5 and the cloud layer from 2.5 to 85.0, a depth of 82.5; reading the cloud layer's top edge (85.0) or the tenant overlay (90.0) instead gives a different figure. Note 4 of Exhibit 04A and note 1 of Exhibit 04D on page 4 of 04_Cloud_Migration_and_Interface_Map.pdf say points are plotted before the last steps of the recording pathway, so the share recorded is the value at the foot of the pathway. At Q1-26 the largest gap between the source systems is 0.5 points, so step 4 answers NO and its connector runs straight into the NO box beside step 5, Keep the final issued point, which bypasses the step 5 question; the recorded share stays 82.5. Reading step 5 as the next numbered step and moving HR Core up one gridline gives 85.0, which is not the recorded share. The value appears only in the image. The prompt and B.8 of Appendix B in 01_Scope_and_Reporting_Memorandum.pdf require this figure as a percentage to one decimal place; that presentation requirement is part of this criterion, and the range brackets the unrounded value. Section 4 of 01_Scope_and_Reporting_Memorandum.pdf and the prompt ask for the position measured on each standing test, so the adopted figure is the one graded. This adds no requirement on any other figure.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Final Answer Only (No Files)", + "dependencies": [] + }, + "criterion 27": { + "description": "States the Arden Time hosted share at 31 March 2026 as 80.0%, to one decimal place (acceptable range 79.5% to 80.5%). The figure that counts is the one the memo adopts as its measured position; a figure given only as a conditional alternative to a different adopted figure does not satisfy this, and sensitivities shown alongside an adopted figure within the range do not prevent it.", + "justification": "Section 4 of 01_Scope_and_Reporting_Memorandum.pdf requires each product's share at the measurement date. Exhibit 04A Rev 2 (issued) in 04_Cloud_Migration_and_Interface_Map.pdf: each product panel stacks production workload by hosting location to 100% (Kelmarsh legacy at the bottom, then the Arden cloud platform, PeoplePort and third-party hosting, and Beechfield colocation), with the tenant share as a dashed overlay and the plan as diamonds. The cloud share is the depth of the second layer at the Q1-26 column, so it takes two boundary reads on the 2.5-point steps. At Q1-26 the plotted cloud layer runs from 7.5 to 92.5, a depth of 85.0, but a correction callout sitting in the HR Core panel, dated 2 April 2026, carries a leader that drops through the Comply panel and ends in an arrowhead at the Time panel's Q1-26 column, restating the cloud share to 80.0% and the legacy estate to 12.5%; note 3 says the callout governs. The date does not keep the callout out of the test: it restates the observation at 31 March 2026, so it is not a matter arising after the cut-off under section 4 of 01_Scope_and_Reporting_Memorandum.pdf. Reading the plotted 85.0%, or applying the callout to HR Core or Comply, fails this row; the plotted 85.0% gives a weighted 80.30%, which would meet paragraph 4.5(a). Note 4 of Exhibit 04A and note 1 of Exhibit 04D on page 4 of 04_Cloud_Migration_and_Interface_Map.pdf say points are plotted before the last steps of the recording pathway, so the share recorded is the value at the foot of the pathway. At Q1-26 the largest gap between the source systems is 0.5 points, so step 4 answers NO and its connector runs straight into the NO box beside step 5, Keep the final issued point, which bypasses the step 5 question; the recorded share stays 80.0, the callout value that note 3 makes the final issued point. Reading step 5 as the next numbered step and moving Time up one gridline gives 82.5, which is not the recorded share. The value appears only in the image. The prompt and B.8 of Appendix B in 01_Scope_and_Reporting_Memorandum.pdf require this figure as a percentage to one decimal place; that presentation requirement is part of this criterion, and the range brackets the unrounded value. Section 4 of 01_Scope_and_Reporting_Memorandum.pdf and the prompt ask for the position measured on each standing test, so the adopted figure is the one graded. This adds no requirement on any other figure.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Final Answer Only (No Files)", + "dependencies": [] + }, + "criterion 28": { + "description": "States the Arden Comply hosted share at 31 March 2026 as 52.5%, to one decimal place (acceptable range 52.0% to 53.0%).", + "justification": "Section 4 of 01_Scope_and_Reporting_Memorandum.pdf requires each product's share at the measurement date. Exhibit 04A Rev 2 (issued) in 04_Cloud_Migration_and_Interface_Map.pdf: each product panel stacks production workload by hosting location to 100% (Kelmarsh legacy at the bottom, then the Arden cloud platform, PeoplePort and third-party hosting, and Beechfield colocation), with the tenant share as a dashed overlay and the plan as diamonds. The cloud share is the depth of the second layer at the Q1-26 column, so it takes two boundary reads on the 2.5-point steps. At Q1-26 the legacy layer, which rose again after the Q4-25 return to Slough, runs from 0 to 30.0 and the cloud layer from 30.0 to 82.5, a depth of 52.5; the tenant overlay ends at 47.5. The recording pathway in Exhibit 04D on page 4 leaves Comply at 52.5 at this quarter end. The value appears only in the image. The prompt and B.8 of Appendix B in 01_Scope_and_Reporting_Memorandum.pdf require this figure as a percentage to one decimal place; that presentation requirement is part of this criterion, and the range brackets the unrounded value.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Final Answer Only (No Files)", + "dependencies": [] + }, + "criterion 29": { + "description": "States or applies that the post-issue correction callout in Exhibit 04A Rev 2 governs over the plotted Arden Time value at 31 March 2026. Applying Note 3's Time Q1-26 restatement from 85.0% to 80.0% satisfies this; the literal words 'governs' and 'plotted' are not required.", + "justification": "Exhibit 04A Rev 2 in 04_Cloud_Migration_and_Interface_Map.pdf: the callout box sits in the HR Core panel, but its leader runs down through the Comply panel and ends in an arrowhead at the Q1-26 column of the Arden Time panel, where the plotted cloud layer is 85.0% deep and the callout restates it to 80.0%. Note 3 of the exhibit makes the callout value govern. The callout is dated 2 April 2026, after the 31 March 2026 cut-off, but it is not a matter arising after the cut-off that section 4 of 01_Scope_and_Reporting_Memorandum.pdf keeps out of the tests: it restates the observation at 31 March 2026 on a telemetry re-run, in an exhibit stated as of that date. Note 2 of Exhibit 04D states the gaps after any telemetry re-run, and B.10 of Appendix B in 01_Scope_and_Reporting_Memorandum.pdf makes the latest issued revision govern, which is Rev 2, dated 7 April 2026, carrying the callout. The prompt requires the resolution of a conflict that changes a test result: on the plotted value the weighted share is 80.3% and the test would be met.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Final Answer Only (No Files)", + "dependencies": [] + }, + "criterion 30": { + "description": "States the ARR-weighted hosted share at 31 March 2026 as 79.6%, to one decimal place (acceptable range 79.55% to 79.65%). The figure that counts is the one the memo adopts as its measured position; a figure given only as a conditional alternative to a different adopted figure does not satisfy this, and sensitivities shown alongside an adopted figure within the range do not prevent it.", + "justification": "Weights from the ARR by product sheet in 02_Arden_QoE_Databook.xlsx (43.27, 30.89, 15.87, 24.11 of 114.14) applied to 92.5, 82.5, 80.0 and 52.5 read from Exhibit 04A Rev 2 in 04_Cloud_Migration_and_Interface_Map.pdf: 90.86275 / 114.14 = 79.61%. One gridline high on Pay, HR Core or Comply (80.55, 80.28, 80.13), or the plotted Time value of 85.0 (80.30), takes it to 80.0% or above, a false pass. Exhibit 04D on page 4 leaves all four final issued points in place at Q1-26: the largest gap is 0.5 points, so step 4 answers NO and its connector runs straight into Keep the final issued point. Moving Pay, HR Core and Time up one gridline gives 95.0, 85.0 and 82.5 and a weighted 81.58%, which would meet limb (a) but is not the recorded share. Test the unrounded result: 79.61% is less than 80.0% under B.8 of Appendix B in 01_Scope_and_Reporting_Memorandum.pdf. The prompt and B.8 of Appendix B in 01_Scope_and_Reporting_Memorandum.pdf require this figure as a percentage to one decimal place; that presentation requirement is part of this criterion, and the range brackets the unrounded value. Section 4 of 01_Scope_and_Reporting_Memorandum.pdf and the prompt ask for the position measured on each standing test, so the adopted figure is the one graded. This adds no requirement on any other figure.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 5, + "grading_target": "Final Answer Only (No Files)", + "dependencies": [] + }, + "criterion 31": { + "description": "States the technology and separation readiness test as failed against the 80.0% hosted-share floor.", + "justification": "Paragraph 4.5 of Appendix A in 01_Scope_and_Reporting_Memorandum.pdf requires each limb to be demonstrated, and limb (a) is met only where the weighted share is not less than 80.0%. The share is 79.6% (79.61) from Exhibit 04A Rev 2, as recorded through the pathway in Exhibit 04D. Limb (b) is met by SEP-06 and limb (c) by the executed Fenwold statement of work, but neither cures limb (a), so the test is failed. The prompt asks for the threshold, the measured position and the outcome of each standing test, so this row requires the failed outcome to be given with the 80.0% floor; stating that limb (a) fails because the weighted share is below 80.0% satisfies this, in any section. Naming the failed test without its threshold, as a decision summary may, does not.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 5, + "grading_target": "Final Answer Only (No Files)", + "dependencies": [] + }, + "criterion 32": { + "description": "States the ARR-weighted hosted share at Q2-25 as 62.0%, to one decimal place (acceptable range 61.95% to 62.05%). The figure that counts is the one the memo adopts as its measured position; a figure given only as a conditional alternative to a different adopted figure does not satisfy this, and sensitivities shown alongside an adopted figure within the range do not prevent it.", + "justification": "Section 4 of 01_Scope_and_Reporting_Memorandum.pdf requires the weighted share at each of the five quarter ends, with the databook product ARR weights applied unchanged. Cloud-layer depths read from Exhibit 04A Rev 2 in 04_Cloud_Migration_and_Interface_Map.pdf at Q2-25 (two boundary reads per product) weighted by 43.27, 30.89, 15.87 and 24.11 of 114.14: 62.0%. Exhibit 04D on page 4 gives a largest gap of 0.5 points at Q2-25, so step 4 answers NO and its connector runs straight into Keep the final issued point; moving HR Core and Time up one gridline gives 63.02%, which is not the recorded share. The prompt and B.8 of Appendix B in 01_Scope_and_Reporting_Memorandum.pdf require this figure as a percentage to one decimal place; that presentation requirement is part of this criterion, and the range brackets the unrounded value. Section 4 of 01_Scope_and_Reporting_Memorandum.pdf and the prompt ask for the position measured on each standing test, so the adopted figure is the one graded. This adds no requirement on any other figure.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Final Answer Only (No Files)", + "dependencies": [] + }, + "criterion 33": { + "description": "States the ARR-weighted hosted share at Q3-25 as 63.8%, to one decimal place (acceptable range 63.75% to 63.85%).", + "justification": "Section 4 of 01_Scope_and_Reporting_Memorandum.pdf requires the weighted share at each of the five quarter ends, with the databook product ARR weights applied unchanged. Cloud-layer depths read from Exhibit 04A Rev 2 in 04_Cloud_Migration_and_Interface_Map.pdf at Q3-25 (two boundary reads per product) weighted by 43.27, 30.89, 15.87 and 24.11 of 114.14: 63.8%. Exhibit 04D on page 4 gives a largest gap of 1.5 points at Q3-25, so step 4 answers YES and step 5 follows, but no wave was open, so step 5 answers NO and each product keeps its final issued point. The prompt and B.8 of Appendix B in 01_Scope_and_Reporting_Memorandum.pdf require this figure as a percentage to one decimal place; that presentation requirement is part of this criterion, and the range brackets the unrounded value.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Final Answer Only (No Files)", + "dependencies": [] + }, + "criterion 34": { + "description": "States the ARR-weighted hosted share at Q4-25 as 71.0%, to one decimal place (acceptable range 70.95% to 71.05%). The figure that counts is the one the memo adopts as its measured position; a figure given only as a conditional alternative to a different adopted figure does not satisfy this, and sensitivities shown alongside an adopted figure within the range do not prevent it.", + "justification": "Section 4 of 01_Scope_and_Reporting_Memorandum.pdf requires the weighted share at each of the five quarter ends, with the databook product ARR weights applied unchanged. Cloud-layer depths read from Exhibit 04A Rev 2 in 04_Cloud_Migration_and_Interface_Map.pdf at Q4-25 (two boundary reads per product) weighted by 43.27, 30.89, 15.87 and 24.11 of 114.14: 71.0%. Exhibit 04D on page 4 gives a largest gap of 0.5 points at Q4-25, so step 4 answers NO and its connector runs straight into Keep the final issued point; moving Time up one gridline gives 71.32%, which is not the recorded share. The prompt and B.8 of Appendix B in 01_Scope_and_Reporting_Memorandum.pdf require this figure as a percentage to one decimal place; that presentation requirement is part of this criterion, and the range brackets the unrounded value. Section 4 of 01_Scope_and_Reporting_Memorandum.pdf and the prompt ask for the position measured on each standing test, so the adopted figure is the one graded. This adds no requirement on any other figure.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Final Answer Only (No Files)", + "dependencies": [] + }, + "criterion 35": { + "description": "States that Exhibit 04A Rev 3 is not relied on because it is marked preliminary.", + "justification": "Page 1 of 04_Cloud_Migration_and_Interface_Map.pdf carries Rev 3, dated 14 April 2026, with status PRELIMINARY in its revision block, Comply at 65.0% and Time at 80.0% (a weighted 82.2%); the issued Rev 2 is page 2. B.10 of Appendix B in 01_Scope_and_Reporting_Memorandum.pdf relies only on the latest issued revision. The issued revision governs. Relying on Rev 3 takes the weighted share above 80.0% and would meet paragraph 4.5(a).", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Final Answer Only (No Files)", + "dependencies": [] + }, + "criterion 36": { + "description": "States the Arden Pay hosted share at Q1-25 as 52.5%, to one decimal place (acceptable range 52.0% to 53.0%).", + "justification": "Section 4 of 01_Scope_and_Reporting_Memorandum.pdf requires each product's share twelve months before the measurement date. Exhibit 04A Rev 2 in 04_Cloud_Migration_and_Interface_Map.pdf: depth of the Arden cloud platform layer at the dashed Q1-25 comparator line, read from its two boundaries on the 2.5-point steps. The recording pathway in Exhibit 04D on page 4 leaves this point in place at Q1-25 (largest gap 0.5 points, no open wave). The value appears only in the image. The prompt and B.8 of Appendix B in 01_Scope_and_Reporting_Memorandum.pdf require this figure as a percentage to one decimal place; that presentation requirement is part of this criterion, and the range brackets the unrounded value.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Final Answer Only (No Files)", + "dependencies": [] + }, + "criterion 37": { + "description": "States the Arden HR Core hosted share at Q1-25 as 57.5%, to one decimal place (acceptable range 57.0% to 58.0%).", + "justification": "Section 4 of 01_Scope_and_Reporting_Memorandum.pdf requires each product's share twelve months before the measurement date. Exhibit 04A Rev 2 in 04_Cloud_Migration_and_Interface_Map.pdf: depth of the Arden cloud platform layer at the dashed Q1-25 comparator line, read from its two boundaries on the 2.5-point steps. The recording pathway in Exhibit 04D on page 4 leaves this point in place at Q1-25 (largest gap 0.5 points, no open wave). The value appears only in the image. The prompt and B.8 of Appendix B in 01_Scope_and_Reporting_Memorandum.pdf require this figure as a percentage to one decimal place; that presentation requirement is part of this criterion, and the range brackets the unrounded value.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Final Answer Only (No Files)", + "dependencies": [] + }, + "criterion 38": { + "description": "States the Arden Time hosted share at Q1-25 as 45.0%, to one decimal place (acceptable range 44.5% to 45.5%).", + "justification": "Section 4 of 01_Scope_and_Reporting_Memorandum.pdf requires each product's share twelve months before the measurement date. Exhibit 04A Rev 2 in 04_Cloud_Migration_and_Interface_Map.pdf: depth of the Arden cloud platform layer at the dashed Q1-25 comparator line, read from its two boundaries on the 2.5-point steps. The recording pathway in Exhibit 04D on page 4 leaves this point in place at Q1-25 (largest gap 0.5 points, no open wave). The value appears only in the image. The prompt and B.8 of Appendix B in 01_Scope_and_Reporting_Memorandum.pdf require this figure as a percentage to one decimal place; that presentation requirement is part of this criterion, and the range brackets the unrounded value.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Final Answer Only (No Files)", + "dependencies": [] + }, + "criterion 39": { + "description": "States the Arden Comply hosted share at Q1-25 as 55.0%, to one decimal place (acceptable range 54.5% to 55.5%).", + "justification": "Section 4 of 01_Scope_and_Reporting_Memorandum.pdf requires each product's share twelve months before the measurement date. Exhibit 04A Rev 2 in 04_Cloud_Migration_and_Interface_Map.pdf: depth of the Arden cloud platform layer at the dashed Q1-25 comparator line, read from its two boundaries on the 2.5-point steps. The recording pathway in Exhibit 04D on page 4 leaves this point in place at Q1-25 (largest gap 0.5 points, no open wave). The value appears only in the image. The prompt and B.8 of Appendix B in 01_Scope_and_Reporting_Memorandum.pdf require this figure as a percentage to one decimal place; that presentation requirement is part of this criterion, and the range brackets the unrounded value.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Final Answer Only (No Files)", + "dependencies": [] + }, + "criterion 40": { + "description": "States the ARR-weighted hosted share at Q1-25 as 53.3%, to one decimal place (acceptable range 53.25% to 53.35%).", + "justification": "Section 4 of 01_Scope_and_Reporting_Memorandum.pdf requires the weighted share twelve months earlier. Q1-25 reads from Exhibit 04A Rev 2 in 04_Cloud_Migration_and_Interface_Map.pdf: Pay 52.5, HR Core 57.5, Time 45.0, Comply 55.0; weighted by product ARR = 60.881 / 114.14 = 0.5334, or 53.34%. The recording pathway in Exhibit 04D on page 4 leaves all four points in place at Q1-25 (largest gap 0.5 points, no open wave). The prompt and B.8 of Appendix B in 01_Scope_and_Reporting_Memorandum.pdf require this figure as a percentage to one decimal place; that presentation requirement is part of this criterion, and the range brackets the unrounded value.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Final Answer Only (No Files)", + "dependencies": [] + }, + "criterion 41": { + "description": "States that the ARR-weighted hosted share rose by 26.3 percentage points over the year to 31 March 2026, to one decimal place (acceptable range 26.25 to 26.35 percentage points). The figure that counts is the one the memo adopts as its measured position; a figure given only as a conditional alternative to a different adopted figure does not satisfy this, and sensitivities shown alongside an adopted figure within the range do not prevent it.", + "justification": "79.61% at Q1-26 less 53.34% at Q1-25, both weighted from the Exhibit 04A Rev 2 reads in 04_Cloud_Migration_and_Interface_Map.pdf as recorded through the pathway in Exhibit 04D, is 26.27 percentage points. Moving products up one gridline at Q1-26 would give 28.24 points, and the plotted Time value 26.96 points, neither of which is the recorded change. Section 4 of 01_Scope_and_Reporting_Memorandum.pdf requires the change between the two dates. The prompt and B.8 of Appendix B in 01_Scope_and_Reporting_Memorandum.pdf require this figure in percentage points to one decimal place; that presentation requirement is part of this criterion, and the range brackets the unrounded value. Section 4 of 01_Scope_and_Reporting_Memorandum.pdf and the prompt ask for the position measured on each standing test, so the adopted figure is the one graded. This adds no requirement on any other figure.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Final Answer Only (No Files)", + "dependencies": [] + }, + "criterion 42": { + "description": "Identifies Arden Comply as the product whose hosted share regressed against twelve months earlier.", + "justification": "Paragraph 4.5(b) of Appendix A in 01_Scope_and_Reporting_Memorandum.pdf requires any regression against twelve months earlier to be identified. Exhibit 04A Rev 2 in 04_Cloud_Migration_and_Interface_Map.pdf shows Comply at 55.0% at Q1-25 and 52.5% at Q1-26; every other product rose.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Final Answer Only (No Files)", + "dependencies": [] + }, + "criterion 43": { + "description": "States that limb (b) of paragraph 4.5 is met by the SEP-06 Arden Comply re-migration plan.", + "justification": "Separation Risks sheet SEP-06 and Integration Envelope sheet IE-03 (GBP 0.48 million) in 05_Separation_and_TSA_Schedule.xlsx meet paragraph 4.5(b) of Appendix A in 01_Scope_and_Reporting_Memorandum.pdf: named owner (Halcyon CTO office), completion date (30 September 2027) and funding within the envelope.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Final Answer Only (No Files)", + "dependencies": [] + }, + "criterion 44": { + "description": "States that limb (c) of paragraph 4.5 is met because the Fenwold statement of work replacing the Norbury SCE-7 engine has been executed.", + "justification": "Separation Risks sheet SEP-02 in 05_Separation_and_TSA_Schedule.xlsx records execution on 26 March 2026, and Integration Envelope IE-01 funds it. Paragraph 4.5(c) of Appendix A in 01_Scope_and_Reporting_Memorandum.pdf needs the remedy funded and contracted; the Novara arrangement in section 7.2 of 07_Management_Investment_Case.pdf is unexecuted and does not count.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Final Answer Only (No Files)", + "dependencies": [] + }, + "criterion 45": { + "description": "States that Arden Time no longer calls the SCE-7 engine at the cut-off because its Exhibit 04B entry is struck through and initialled, so the Fenwold statement of work covers every remaining SCE-7 dependency. Describing the Exhibit 04B Time entry as removed or corrected by the CTO office's manuscript note satisfies 'struck through and initialled'.", + "justification": "Exhibit 04B on page 3 of 04_Cloud_Migration_and_Interface_Map.pdf prints Live for Arden Time against the SCE-7 Tax Engine, but the entry is struck through by hand with the manuscript note none from 20/3/26 and the CTO office initials; note 3 says the initialled correction governs. SEP-02 in 05_Separation_and_TSA_Schedule.xlsx scopes the Fenwold replacement to Arden Pay and Arden Comply only, so reading the printed entry leaves Time with an unremedied non-assignable dependency and fails limb (c), a misreading, although paragraph 4.5 is failed on limb (a) in any event. Equivalent wording is accepted: describing the Exhibit 04B Time entry as removed or corrected by the CTO office's manuscript note satisfies 'struck through and initialled'.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Final Answer Only (No Files)", + "dependencies": [] + }, + "criterion 46": { + "description": "States that management's 86.0% migration figure is a tenant count that paragraph 4.5(a) does not accept.", + "justification": "Section 7.1 of 07_Management_Investment_Case.pdf reports 3,713 of 4,317 tenants (86%). Paragraph 4.5(a) of Appendix A in 01_Scope_and_Reporting_Memorandum.pdf excludes counts of tenants. Taking the 86.0% as the position would meet the 80.0% level in limb (a), which is wrong.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Final Answer Only (No Files)", + "dependencies": [] + }, + "criterion 47": { + "description": "States that the Chief Technology Officer approved a backfill plan with named cover and dated milestones for the lead architect role.", + "justification": "Separation Risks sheet SEP-04 in 05_Separation_and_TSA_Schedule.xlsx: a contract lead architect (Wardlow reference WTR-2217) was selected as named cover on 26 March 2026, and the backfill plan, with cover engaged by 30 September 2026 (M3) and documented handover complete by 31 December 2026 (M6), was approved by the Chief Technology Officer on 30 March 2026. That is limb (b) of paragraph 4.9 of Appendix A in 01_Scope_and_Reporting_Memorandum.pdf: a backfill plan with named cover and dated milestones approved by the Chief Technology Officer or the relevant functional executive. The internal cover proposed by Arden on 26 March 2026 was not accepted and is not the plan relied on. Missing the approval leaves the role unretained and fails paragraph 4.9, a false failure.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Final Answer Only (No Files)", + "dependencies": [] + }, + "criterion 48": { + "description": "Identifies all eight critical roles as retained, with the lead architect, platform separation (CGP-08033) retained under limb (b) of paragraph 4.9.", + "justification": "Paragraph 4.9 of Appendix A in 01_Scope_and_Reporting_Memorandum.pdf requires each critical role's status. Of the eight roles marked critical in the Policy 4.9 column of the Employee Schedule sheet in 05_Separation_and_TSA_Schedule.xlsx, seven have a binding position and an agreed, funded retention arrangement. CGP-08033 does not meet limb (a), because the execution authority read from 08_Executed_Transfer_Instruments.pdf does not bind the employer, but it meets limb (b) through the backfill plan approved on 30 March 2026 (SEP-04), so it is retained.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 5, + "grading_target": "Final Answer Only (No Files)", + "dependencies": [] + }, + "criterion 49": { + "description": "States, in the PEOPLE PERIMETER section, that the retention test is met. The threshold (no critical role unretained; equivalently all or 100% of critical roles retained, or zero unretained) may be stated in that section or elsewhere in the memorandum.", + "justification": "Paragraph 4.9 of Appendix A in 01_Scope_and_Reporting_Memorandum.pdf: a critical role is retained under limb (a) or limb (b), and the test is failed only where a critical role satisfies neither. All eight critical roles are retained, CGP-08033 under limb (b).", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 5, + "grading_target": "Final Answer Only (No Files)", + "dependencies": [] + }, + "criterion 50": { + "description": "States management's claimed run-rate benefits as USD 16.6 million, in USD millions to one decimal place (acceptable range USD 16.55 million to USD 16.65 million).", + "justification": "Run-Rate Initiatives sheet in 06_Integration_Synergy_Schedule.xlsx: GBP 13.83 million x 1.20 planning rate = USD 16.60 million. The prompt and B.8 of Appendix B in 01_Scope_and_Reporting_Memorandum.pdf require this figure in USD millions to one decimal place; that presentation requirement is part of this criterion, and the range brackets the unrounded value.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Final Answer Only (No Files)", + "dependencies": [] + }, + "criterion 51": { + "description": "States that pool ARD-P1 runs in production in the United Kingdom. Naming the Kelmarsh site or Slough as where ARD-P1 runs, or listing ARD-P1 among the UK pools counted in MI-02, satisfies this without the word 'production'. Placing ARD-P1's production in the Republic of Ireland, or omitting ARD-P1, does not.", + "justification": "Exhibit 04C in 09_Hosting_Topology_and_Capacity_Pools.pdf: ARD-P1's solid line (production placement, per the key) runs to the Kelmarsh Data Centres box in the United Kingdom panel; its dotted line to UK South is a backup copy target and its dash-dot line to UK West is a planned placement, not in production at the cut-off. MI-02 in 06_Integration_Synergy_Schedule.xlsx re-hosts each pool in the jurisdiction of its production site, and C-041, as set out in the schedule to paragraph 4.6 on page 5 of 01_Scope_and_Reporting_Memorandum.pdf, commits only UK regions, so the validated amount turns on the production jurisdiction. Equivalent wording is accepted: naming the Kelmarsh site or Slough as the production placement, or placing ARD-P1 among the UK pools counted in MI-02, satisfies the criterion. Placing ARD-P1 in the Republic of Ireland, or omitting it, does not. The placement appears only in the image.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Final Answer Only (No Files)", + "dependencies": [] + }, + "criterion 52": { + "description": "States that pool ARD-P2 runs in production in the Republic of Ireland. Naming Beechfield Exchange or Dublin as where ARD-P2 runs, or listing ARD-P2 among the Irish pools excluded from MI-02, satisfies this without the word 'production'. Placing ARD-P2's production in the United Kingdom, or omitting ARD-P2, does not.", + "justification": "Exhibit 04C in 09_Hosting_Topology_and_Capacity_Pools.pdf: ARD-P2's solid line runs to the Beechfield Exchange box in the Republic of Ireland panel; its dashed line to UK West is a disaster-recovery replica target, not where the pool runs. MI-02 in 06_Integration_Synergy_Schedule.xlsx re-hosts each pool in the jurisdiction of its production site, and C-041, as set out in the schedule to paragraph 4.6 on page 5 of 01_Scope_and_Reporting_Memorandum.pdf, commits only UK regions, so the validated amount turns on the production jurisdiction. Equivalent wording is accepted: naming Beechfield Exchange or Dublin as the production placement, or placing ARD-P2 among the Irish pools excluded from MI-02, satisfies the criterion. Placing ARD-P2 in the United Kingdom, or omitting it, does not. The placement appears only in the image.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Final Answer Only (No Files)", + "dependencies": [] + }, + "criterion 53": { + "description": "States that pool ARD-D1 runs in production in the United Kingdom. Naming the UK South region as where ARD-D1 runs, or listing ARD-D1 among the UK pools counted in MI-02, satisfies this without the word 'production'. Placing ARD-D1's production in the Republic of Ireland, or omitting ARD-D1, does not.", + "justification": "Exhibit 04C in 09_Hosting_Topology_and_Capacity_Pools.pdf: ARD-D1's solid line runs to the UK South cloud box. Its dashed line to the Dublin cloud box is a disaster-recovery replica target and its dash-dot line to Beechfield Exchange is a planned placement after a later migration wave, which the key says is not in production at the cut-off. Taking either Irish line as current makes D1 Irish and understates validated benefits. MI-02 in 06_Integration_Synergy_Schedule.xlsx re-hosts each pool in the jurisdiction of its production site, and C-041, as set out in the schedule to paragraph 4.6 on page 5 of 01_Scope_and_Reporting_Memorandum.pdf, commits only UK regions, so the validated amount turns on the production jurisdiction. Equivalent wording is accepted: naming the UK South region as the production placement, or placing ARD-D1 among the UK pools counted in MI-02, satisfies the criterion. Placing ARD-D1 in the Republic of Ireland, or omitting it, does not. The placement appears only in the image.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Final Answer Only (No Files)", + "dependencies": [] + }, + "criterion 54": { + "description": "States that pool ARD-C2 runs in production in the Republic of Ireland. Naming the Dublin cloud region (or Dublin) as where ARD-C2 runs, or listing ARD-C2 among the Irish pools excluded from MI-02, satisfies this without the word 'production'. Placing ARD-C2's production in the United Kingdom, or omitting ARD-C2, does not.", + "justification": "Exhibit 04C in 09_Hosting_Topology_and_Capacity_Pools.pdf: ARD-C2's solid line runs to the Dublin cloud box; its dotted line to UK West is a backup copy target and its dash-dot line to UK South is a planned placement, not in production. MI-02 in 06_Integration_Synergy_Schedule.xlsx re-hosts each pool in the jurisdiction of its production site, and C-041, as set out in the schedule to paragraph 4.6 on page 5 of 01_Scope_and_Reporting_Memorandum.pdf, commits only UK regions, so the validated amount turns on the production jurisdiction. Equivalent wording is accepted: naming the Dublin cloud region as the production placement, or placing ARD-C2 among the Irish pools excluded from MI-02, satisfies the criterion. Placing ARD-C2 in the United Kingdom, or omitting it, does not. The placement appears only in the image.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Final Answer Only (No Files)", + "dependencies": [] + }, + "criterion 55": { + "description": "States that pool ARD-B2 runs in production in the United Kingdom. Naming the UK South region as where ARD-B2 runs, or listing ARD-B2 among the UK pools counted in MI-02, satisfies this without the word 'production'. Placing ARD-B2's production in the Republic of Ireland, or omitting ARD-B2, does not.", + "justification": "Exhibit 04C in 09_Hosting_Topology_and_Capacity_Pools.pdf: ARD-B2's solid line runs to the UK South cloud box and its dotted line to UK West is a backup copy target. A third line, to Beechfield Exchange, is drawn grey and crossed through, which the key defines as a placement superseded since Rev 0 that no longer applies. Taking it as current makes B2 Irish and understates validated benefits. MI-02 in 06_Integration_Synergy_Schedule.xlsx re-hosts each pool in the jurisdiction of its production site, and C-041, as set out in the schedule to paragraph 4.6 on page 5 of 01_Scope_and_Reporting_Memorandum.pdf, commits only UK regions, so the validated amount turns on the production jurisdiction. Equivalent wording is accepted: naming the UK South region as the production placement, or placing ARD-B2 among the UK pools counted in MI-02, satisfies the criterion. Placing ARD-B2 in the Republic of Ireland, or omitting it, does not. The placement appears only in the image.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Final Answer Only (No Files)", + "dependencies": [] + }, + "criterion 56": { + "description": "States that pool ARD-P3 runs in production in the United Kingdom. Naming the UK West region as where ARD-P3 runs, or listing ARD-P3 among the UK pools counted in MI-02, satisfies this without the word 'production'. Placing ARD-P3's production in the Republic of Ireland, or omitting ARD-P3, does not.", + "justification": "Exhibit 04C in 09_Hosting_Topology_and_Capacity_Pools.pdf: ARD-P3's solid line runs to the UK West cloud box and its dotted line to Kelmarsh is a backup copy target. A third line, to the Dublin cloud box, is drawn grey and crossed through as superseded, so it no longer applies; taking it as current makes P3 Irish and understates validated benefits. MI-02 in 06_Integration_Synergy_Schedule.xlsx re-hosts each pool in the jurisdiction of its production site, and C-041, as set out in the schedule to paragraph 4.6 on page 5 of 01_Scope_and_Reporting_Memorandum.pdf, commits only UK regions, so the validated amount turns on the production jurisdiction. Equivalent wording is accepted: naming the UK West region as the production placement, or placing ARD-P3 among the UK pools counted in MI-02, satisfies the criterion. Placing ARD-P3 in the Republic of Ireland, or omitting it, does not. The placement appears only in the image.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Final Answer Only (No Files)", + "dependencies": [] + }, + "criterion 57": { + "description": "States that pool ARD-C3 runs in production in the Republic of Ireland. Naming the Dublin cloud region (or Dublin) as where ARD-C3 runs, or listing ARD-C3 among the Irish pools excluded from MI-02, satisfies this without the word 'production'. Placing ARD-C3's production in the United Kingdom, or omitting ARD-C3, does not.", + "justification": "Exhibit 04C in 09_Hosting_Topology_and_Capacity_Pools.pdf: ARD-C3's solid line runs to the Dublin cloud box; its dashed line to UK South is a disaster-recovery replica target, and its grey, crossed-through line to UK West is a superseded placement. MI-02 in 06_Integration_Synergy_Schedule.xlsx re-hosts each pool in the jurisdiction of its production site, and C-041, as set out in the schedule to paragraph 4.6 on page 5 of 01_Scope_and_Reporting_Memorandum.pdf, commits only UK regions, so the validated amount turns on the production jurisdiction. Equivalent wording is accepted: naming the Dublin cloud region as the production placement, or placing ARD-C3 among the Irish pools excluded from MI-02, satisfies the criterion. Placing ARD-C3 in the United Kingdom, or omitting it, does not. The placement appears only in the image.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Final Answer Only (No Files)", + "dependencies": [] + }, + "criterion 58": { + "description": "States that pool ARD-D2 runs in production in the Republic of Ireland. Naming Beechfield Exchange or Dublin as where ARD-D2 runs, or listing ARD-D2 among the Irish pools excluded from MI-02, satisfies this without the word 'production'. Placing ARD-D2's production in the United Kingdom, or omitting ARD-D2, does not.", + "justification": "Exhibit 04C in 09_Hosting_Topology_and_Capacity_Pools.pdf: ARD-D2's solid line runs to the Beechfield Exchange box; its dashed line to UK South is a disaster-recovery replica target. MI-02 in 06_Integration_Synergy_Schedule.xlsx re-hosts each pool in the jurisdiction of its production site, and C-041, as set out in the schedule to paragraph 4.6 on page 5 of 01_Scope_and_Reporting_Memorandum.pdf, commits only UK regions, so the validated amount turns on the production jurisdiction. Equivalent wording is accepted: naming Beechfield Exchange or Dublin as the production placement, or placing ARD-D2 among the Irish pools excluded from MI-02, satisfies the criterion. Placing ARD-D2 in the United Kingdom, or omitting it, does not. The placement appears only in the image.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Final Answer Only (No Files)", + "dependencies": [] + }, + "criterion 59": { + "description": "States that the hosting consolidation (MI-02) portions for the pools that run in production in the Republic of Ireland are excluded because Ireland is outside Schedule 1 of Halcyon's committed-use cloud infrastructure agreement (C-041) and no regional addendum has been signed. The memo need not name the pools for this row.", + "justification": "MI-02 in 06_Integration_Synergy_Schedule.xlsx re-hosts each pool in the jurisdiction where it runs in production; ARD-P2, ARD-C2, ARD-C3 and ARD-D2 run in Ireland per Exhibit 04C in 09_Hosting_Topology_and_Capacity_Pools.pdf. The C-041 row of the schedule to paragraph 4.6 on page 5 of 01_Scope_and_Reporting_Memorandum.pdf commits only the Schedule 1 regions UK South and UK West, and its clause 5.6 condition requires a signed regional addendum. The C-041 note on the Contracts and Consents sheet in 05_Separation_and_TSA_Schedule.xlsx says the agreement has not been amended or supplemented since signature, so no addendum exists. Keeping the four Irish pools gives USD 5.2 million (5.196) and would meet paragraph 4.6. This row grades the exclusion rule for the Irish production pools as a group. The memo need not list the pools here, because each pool's production jurisdiction and the excluded amount are graded on their own rows. Stating that C-041 commits only the UK regions, so Irish pools cannot be placed under it without a signed regional addendum, satisfies the reason.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Final Answer Only (No Files)", + "dependencies": [] + }, + "criterion 60": { + "description": "States the validated benefit from hosting consolidation onto the acquirer's cloud infrastructure agreement (MI-02) as USD 2.5 million, in USD millions to one decimal place (acceptable range USD 2.45 million to USD 2.55 million).", + "justification": "UK pools ARD-P1 (GBP 0.80 million), ARD-D1 (0.40), ARD-B2 (0.50) and ARD-P3 (0.40) = GBP 2.10 million x 1.20 = USD 2.52 million, validated because all four run in production in the UK (Exhibit 04C in 09_Hosting_Topology_and_Capacity_Pools.pdf), inside the C-041 regions in the schedule to paragraph 4.6 on page 5 of 01_Scope_and_Reporting_Memorandum.pdf. Counting all eight pools gives USD 4.7 million and total benefits of USD 5.2 million, which would meet paragraph 4.6. The pool amounts are stated in management's schedule, but the evidence condition in paragraph 4.6 of Appendix A is met on what sits outside Arden: C-041, provided by Halcyon procurement on 14 March 2026 so that hosting migration savings can be priced (Contracts and Consents sheet in 05_Separation_and_TSA_Schedule.xlsx), and Exhibit 04C, the diligence exhibit that fixes where each pool runs. Note 4 on the Basis of Preparation sheet calls MI-02 a management estimate, but its inputs can be checked outside Arden: the acquirer's rate card of 4 November 2025, C-041 and Exhibit 04C. The prompt and B.8 of Appendix B in 01_Scope_and_Reporting_Memorandum.pdf require this figure in USD millions to one decimal place; that presentation requirement is part of this criterion, and the range brackets the unrounded value.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Final Answer Only (No Files)", + "dependencies": [] + }, + "criterion 61": { + "description": "States the excluded Irish portion of the hosting consolidation benefit (MI-02) as USD 2.2 million, in USD millions to one decimal place (acceptable range USD 2.15 million to USD 2.25 million). This quantity is the MI-02 benefit of the four pools that run in production in the Republic of Ireland: ARD-P2, ARD-C2, ARD-C3 and ARD-D2. The memo need not list the pools, and naming some of them as examples is fine, but a figure it expressly attributes to a different set of pools (leaving out some of the four, or including pools outside them) is not this quantity.", + "justification": "ARD-P2 0.70 + ARD-C2 0.45 + ARD-C3 0.40 + ARD-D2 0.30 = GBP 1.85 million x 1.20 planning rate = USD 2.22 million, excluded because all four pools run in Ireland per Exhibit 04C in 09_Hosting_Topology_and_Capacity_Pools.pdf, outside the C-041 regions in the schedule to paragraph 4.6 on page 5 of 01_Scope_and_Reporting_Memorandum.pdf. The prompt and B.8 of Appendix B in 01_Scope_and_Reporting_Memorandum.pdf require this figure in USD millions to one decimal place; that presentation requirement is part of this criterion, and the range brackets the unrounded value. The accepted source reading of Exhibit 04C and MI-02 places exactly these four MI-02 pools in the Republic of Ireland; no other pool forms part of the excluded Irish portion. Excluding nothing gives total benefits of USD 5.2 million, which would meet paragraph 4.6.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Final Answer Only (No Files)", + "dependencies": [] + }, + "criterion 62": { + "description": "States that the data-centre exit (MI-03) is excluded because it covers the same Kelmarsh and Beechfield sites as the hosting consolidation (MI-02), which has the earlier run-rate month. Identifying the shared sites by contract reference (C-016 Kelmarsh, C-038 Beechfield) and giving the two run-rate months (MI-02 month 18, MI-03 month 20) with the B.7 rule satisfies this.", + "justification": "MI-03 in 06_Integration_Synergy_Schedule.xlsx names the Kelmarsh hall and the Beechfield facility; Exhibit 04C in 09_Hosting_Topology_and_Capacity_Pools.pdf shows these are the production sites of pools ARD-P1 (Kelmarsh) and ARD-P2 and ARD-D2 (Beechfield) claimed by MI-02. B.7 of Appendix B in 01_Scope_and_Reporting_Memorandum.pdf credits shared scope to the earlier run-rate month (MI-02, month 18) and excludes the later claim (MI-03, month 20). Equivalent wording is accepted: identifying the shared sites by contract reference (C-016 Kelmarsh, C-038 Beechfield) with the B.7 earlier-month rule (MI-02 month 18, MI-03 month 20) satisfies the criterion. Both MI-03 sites and contracts are shared in whole under B.7, and IE-08 carries the facility exit, so no residual survives. Exhibit 04C also shows ARD-A1, ARD-K1 and ARD-M1 at Kelmarsh and ARD-D3 and ARD-D4 at Beechfield, but MI-03 is claimed by site and contract and no source splits it by pool. MI-02's pool figures are net of the committed-use charge and MI-03 is a gross facility charge, so 2.15 less 1.80 is not a measured residual and a memo that keeps it does not meet this row. Keeping MI-03 whole gives USD 5.6 million and would meet paragraph 4.6. Even as an amount, 0.35 fails paragraph 4.6 on its own: note 4 makes it a management estimate, the two contracts' annual value is GBP 0.58 million (C-016, C-038), and Exhibit 04C shows no planned placement for ARD-K1 at Kelmarsh or for any of the four Beechfield pools, so exit of either site is not shown within the horizon.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Final Answer Only (No Files)", + "dependencies": [] + }, + "criterion 63": { + "description": "States that the support organisation consolidation (MI-06) is excluded because its one-off cost is not funded within the integration envelope.", + "justification": "Integration Envelope sheet in 05_Separation_and_TSA_Schedule.xlsx: the MI-06 request of GBP 0.95 million was not approved and is not allocated. Paragraph 4.6 of Appendix A in 01_Scope_and_Reporting_Memorandum.pdf requires the cost of achievement to be funded within the envelope. Column H says the cost is to be met from the acquirer's integration budget, but that is a request and not an allocation. Keeping MI-06 gives USD 5.0 million (5.016) and would meet paragraph 4.6.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Final Answer Only (No Files)", + "dependencies": [] + }, + "criterion 64": { + "description": "States that the retirement of the Norbury SCE-7 tax determination engine (MI-05) is excluded because the saving cannot be earned in full before month 25.", + "justification": "Clause 9.4 of C-023 on the Contracts and Consents sheet in 05_Separation_and_TSA_Schedule.xlsx: notice can be served only once Arden stops calling the engine (the Fenwold cutover at month 12, SEP-02), and the fee runs for the twelve-month notice period, so the first full month of saving is month 25, outside the 24-month horizon.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Final Answer Only (No Files)", + "dependencies": [] + }, + "criterion 65": { + "description": "States that the development and security tooling rationalisation (MI-08) is validated because it is earned in full from month 24, inside the inclusive horizon. Identifying the initiative by its reference MI-08 and stating that its run-rate month 24 falls within the inclusive 24-month horizon satisfies this.", + "justification": "MI-08 in 06_Integration_Synergy_Schedule.xlsx is earned in full from month 24; B.7 of Appendix B in 01_Scope_and_Reporting_Memorandum.pdf makes the horizon inclusive of month 24; IE-09 funds its one-off cost. The facts are stated in management's schedule, but the evidence condition in paragraph 4.6 of Appendix A is met on what sits outside Arden: EA-07 in the schedule to paragraph 4.6 on page 5 of 01_Scope_and_Reporting_Memorandum.pdf, and the confirmation of the acquirer's procurement team on 12 March 2026 that its enterprise agreements cover all eleven products, which is the product coverage EA-07 requires. That confirmation is reported only in cell H13 of the Run-Rate Initiatives sheet, which is management's schedule. The line still holds, because the confirmation is the acquirer's own act and EA-07 makes it the required step. A memo that excludes MI-08 on this ground reaches USD 2.5 million and paragraph 4.6 stays failed, but it does not meet this row.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Final Answer Only (No Files)", + "dependencies": [] + }, + "criterion 66": { + "description": "States that the indirect procurement re-tender (MI-01, USD 2.2 million) is not validated.", + "justification": "The claim is GBP 1.82 million x 1.20 = USD 2.18 million. The Run-Rate Initiatives sheet in 06_Integration_Synergy_Schedule.xlsx says the figure is priced at the prices agreed in the selected bids and grades MI-01 Firm, and note 4 on the Basis of Preparation sheet says a supplier price is contractually agreed, but these are management's own statements in management's own schedule. The Run-Rate Initiatives sheet says management confidence is not an evidence grading, and the Definitions and Contacts sheet says the tender file is not in the data room and is available on request. Unlike MI-02, which rests on C-041 and Exhibit 04C, and MI-08, which rests on EA-07 and the acquirer's own procurement confirmation (reported only in column H, but the acquirer's act and the step EA-07 requires), MI-01 has nothing outside Arden behind it, and its primary file is expressly not in the data room. Paragraph 4.6 of Appendix A in 01_Scope_and_Reporting_Memorandum.pdf requires evidence beyond management assertion, paragraph 4.2 applies the tests to the figures in the buy-side diligence report and not to a figure that stands only on the target's presentation, and B.9 of Appendix B bars substituting an assumption for a document not given. IE-07 funds the one-time cost, which meets a different condition of paragraph 4.6. Validating MI-01 gives USD 5.2 million and would meet paragraph 4.6, a false pass. Two further points lead the same way: column H relies on the acquirer's framework terms, which are not on the schedule to paragraph 4.6 on page 5 of 01_Scope_and_Reporting_Memorandum.pdf, and that schedule validates a benefit relying on a group commitment only within the scope and conditions it shows; and note 1 on the Basis of Preparation sheet leaves MI-01 unchanged since the list of 30 January 2026, which predates the bids of 19 February 2026. A memo that excludes MI-01 on either point meets this row. Item 4 in the section 9 table of 07_Management_Investment_Case.pdf (Procurement re-tender, GBP 0.8 million to GBP 1.1 million) is a re-tender of third-party software and data licences. The Definitions and Contacts sheet in 06_Integration_Synergy_Schedule.xlsx excludes software licences from indirect categories, so that item is a different scope and gives MI-01 no support. This row tests the statement that MI-01 is not validated; the amount identifies the claim.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Final Answer Only (No Files)", + "dependencies": [] + }, + "criterion 67": { + "description": "States validated run-rate benefits as USD 3.0 million, in USD millions to one decimal place (acceptable range USD 2.95 million to USD 3.05 million). This quantity represents the validated portions of MI-02 and MI-08. The memo need not repeat the breakdown, but a figure it expressly attributes to a different set of initiatives is not this quantity.", + "justification": "Validated GBP 2.10 (MI-02, ARD-P1, ARD-D1, ARD-B2 and ARD-P3, per Exhibit 04C in 09_Hosting_Topology_and_Capacity_Pools.pdf and the C-041 regions in the schedule to paragraph 4.6 on page 5 of 01_Scope_and_Reporting_Memorandum.pdf) + 0.38 (MI-08) = GBP 2.48 million x 1.20 planning rate = USD 2.976 million, displayed USD 3.0 million. MI-01 is not validated, because management's own schedule is its only support. Validating it gives USD 5.16 million, keeping the four Irish pools USD 5.196 million, keeping MI-03 whole USD 5.556 million, keeping MI-06 USD 5.016 million and counting the revenue initiative MI-09 USD 5.376 million, each a false pass. USD 3.4 million reached by keeping GBP 0.35 million of MI-03 is a different set and does not pass. The prompt and B.8 of Appendix B in 01_Scope_and_Reporting_Memorandum.pdf require this figure in USD millions to one decimal place; that presentation requirement is part of this criterion, and the range brackets the unrounded value. The total is the validated benefit quantity, not any set of benefits that happens to sum to the same rounded number. No additional initiative listing or calculation method is required. An expressly stated different benefit set does not establish this total; separately graded component figures and test conclusions are assessed on their own criteria.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 5, + "grading_target": "Final Answer Only (No Files)", + "dependencies": [] + }, + "criterion 68": { + "description": "States the benefits test as failed against the USD 5.0 million floor.", + "justification": "Paragraph 4.6 of Appendix A in 01_Scope_and_Reporting_Memorandum.pdf: USD 2.976 million is less than USD 5.0 million, a shortfall of USD 2.024 million. Validating MI-01, keeping the four Irish pools, keeping MI-03, keeping MI-06 or counting the revenue initiative MI-09 would each meet the floor, a false pass.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 5, + "grading_target": "Final Answer Only (No Files)", + "dependencies": [] + }, + "criterion 69": { + "description": "Includes a required action for each condition listed.", + "justification": "The prompt requires each condition to state the required action.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Final Answer Only (No Files)", + "dependencies": [] + }, + "criterion 70": { + "description": "Includes an accountable owner for each condition listed.", + "justification": "The prompt requires each condition to state the accountable owner.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Final Answer Only (No Files)", + "dependencies": [] + }, + "criterion 71": { + "description": "Includes a deadline for each condition listed.", + "justification": "The prompt requires each condition to state the deadline.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Final Answer Only (No Files)", + "dependencies": [] + }, + "criterion 72": { + "description": "Includes a corrective FY26 growth plan owned by the Arden chief executive officer and due before signing on 15 May 2026. A deadline stated as before or prior to signing satisfies the date.", + "justification": "Paragraph 4.3 of Appendix A in 01_Scope_and_Reporting_Memorandum.pdf requires this plan when growth is met subject to conditions, so it stays in the conditions section on a Do not proceed; signing is 15 May 2026 (section 1 of 01_Scope_and_Reporting_Memorandum.pdf). Equivalent wording is accepted: a deadline stated as before signing satisfies the date element, because section 1 fixes signing at 15 May 2026.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 5, + "grading_target": "Final Answer Only (No Files)", + "dependencies": [] + }, + "criterion 73": { + "description": "Includes, as remediation on which the Committee would reconsider, raising the ARR-weighted hosted share to at least 80.0% at a later quarter end on the paragraph 4.5(a) basis.", + "justification": "Section 4 and paragraph 4.10 of Appendix A in 01_Scope_and_Reporting_Memorandum.pdf: where the decision is Do not proceed, the conditions section states the remediation on which the Committee would reconsider, each item with its owner and date. Paragraph 4.5(a) is met only where the weighted share is not less than 80.0% at the most recent quarter end preceding Committee approval, measured on a consistent denominator weighted by revenue or customer value. The share is 79.6% at 31 March 2026, so the cure is a later quarter end at 80.0% or above on that basis. A tenant count or a restated reading of the same quarter does not cure it. Assess the item in its full memo context; the decision label is scored separately. The next quarter end after 31 March 2026 is 30 June 2026, which is after signing on 15 May 2026 and is the completion date; a condition to show 80.0% before signing can therefore only restate the 31 March 2026 quarter, including through waves switched off after the cut-off, and does not satisfy this row unless it ties the cure to a quarter end after 31 March 2026.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 5, + "grading_target": "Final Answer Only (No Files)", + "dependencies": [] + }, + "criterion 74": { + "description": "Includes, as remediation on which the Committee would reconsider, obtaining evidence beyond management assertion for MI-01, such as the tender file, or validating at least USD 2.0 million more benefits.", + "justification": "Section 4 and paragraph 4.10 of Appendix A in 01_Scope_and_Reporting_Memorandum.pdf: where the decision is Do not proceed, the conditions section states the remediation on which the Committee would reconsider, each item with its owner and date. The benefits test is short by USD 2.024 million. Paragraph 4.6 needs evidence beyond management assertion, and the Definitions and Contacts sheet in 06_Integration_Synergy_Schedule.xlsx says the tender file is available on request. MI-01 at USD 2.2 million, once evidenced, would cure the shortfall, and so would any other USD 2.0 million of benefits that meet paragraph 4.6. Either route satisfies this row. Assess the item in its full memo context; the decision label is scored separately.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 5, + "grading_target": "Final Answer Only (No Files)", + "dependencies": [] + }, + "criterion 75": { + "description": "Cites paragraph 4.10 of Appendix A in 01_Scope_and_Reporting_Memorandum.pdf in the source ledger for the recommendation.", + "justification": "The prompt requires a filename and precise location for the conclusion that decides the recommendation.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Final Answer Only (No Files)", + "dependencies": [] + }, + "criterion 76": { + "description": "Cites 02_Arden_QoE_Databook.xlsx in the source ledger for normalized standalone EBITDA, identifying a real worksheet relevant to that conclusion. A descriptive alias is acceptable if it unambiguously identifies an actual worksheet. A separate component-only citation does not replace the required normalized-EBITDA citation, and a nonexistent or unrelated worksheet does not count. The actual worksheets are Cover, P&L, Adjustments, Cost detail, Standalone costs, ARR movement, ARR by product, Monthly accounts, Headcount and Source notes.", + "justification": "The prompt asks for the filename and precise location supporting each decision-critical conclusion. This criterion checks the source location attached to normalized standalone EBITDA, not whether every financial calculation is correct. Clear aliases for real sheets are acceptable. A specific invalid citation for the normalized figure is not cured merely by citing a real sheet for another component elsewhere in the ledger. Numeric correctness is graded separately.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Final Answer Only (No Files)", + "dependencies": [] + }, + "criterion 77": { + "description": "Cites Figure 4.1 of 03_Commercial_Diligence_Market_Assessment.pdf in the source ledger for the market reading.", + "justification": "The market reading that decides the growth test appears only in Figure 4.1.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Final Answer Only (No Files)", + "dependencies": [] + }, + "criterion 78": { + "description": "Cites Exhibit 04A Rev 2 of 04_Cloud_Migration_and_Interface_Map.pdf in the source ledger for the hosted shares.", + "justification": "The hosted shares that decide the technology test appear only in Exhibit 04A; the issued revision is Rev 2.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Final Answer Only (No Files)", + "dependencies": [] + }, + "criterion 79": { + "description": "Cites Exhibit 04C in 09_Hosting_Topology_and_Capacity_Pools.pdf in the source ledger for the pool-to-site mapping.", + "justification": "The mapping that decides the MI-02 split and the MI-03 overlap appears only in Exhibit 04C.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Final Answer Only (No Files)", + "dependencies": [] + }, + "criterion 80": { + "description": "Cites 10_Group_Recharge_Allocation_Map.pdf in the source ledger for the recharges credited against the standalone schedule.", + "justification": "The split of account 7200 by cost pool and entity appears only in the recharge map.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Final Answer Only (No Files)", + "dependencies": [] + }, + "criterion 81": { + "description": "Cites Separation Risks SEP-04 of 05_Separation_and_TSA_Schedule.xlsx in the source ledger for the backfill plan on the lead architect role.", + "justification": "The approved backfill plan that decides the retention test under limb (b) of paragraph 4.9 appears only in SEP-04. The deed of transfer does not decide that test, so no ledger entry for its execution page is required.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Final Answer Only (No Files)", + "dependencies": [] + }, + "criterion 82": { + "description": "Returns the memorandum directly in the final response rather than as a separate file.", + "justification": "The prompt asks for the memorandum directly in the final response, not as a separate file.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Final Answer Only (No Files)", + "dependencies": [] + }, + "criterion 83": { + "description": "Includes the eleven headings in uppercase in this order: PROJECT RELAY - INVESTMENT COMMITTEE MEMORANDUM; DECISION; EXECUTIVE RATIONALE; GROWTH QUALITY; NORMALIZED STANDALONE ECONOMICS; TECHNOLOGY AND SEPARATION; PEOPLE PERIMETER; BENEFITS RECONCILIATION; IC CONDITIONS TO APPROVAL; IC UNDERWRITING CONSTRAINT; SOURCE LEDGER.", + "justification": "The prompt lists these headings, in uppercase and in this order.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Final Answer Only (No Files)", + "dependencies": [] + }, + "criterion 84": { + "description": "Leaves one blank line after each heading and between sections.", + "justification": "The prompt requires one blank line after each heading and between sections.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Final Answer Only (No Files)", + "dependencies": [] + }, + "criterion 85": { + "description": "Keeps the whole memo, including the source ledger, at 1,500 words or fewer.", + "justification": "The prompt sets a 1,500-word limit that includes the source ledger. Count the whole memorandum, including its title, headings, numbered conditions and source ledger. Include words and numerical items such as amounts, percentages, dates and reference codes rather than dropping those sections or items from the count.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Final Answer Only (No Files)", + "dependencies": [] + }, + "criterion 86": { + "description": "Keeps every narrative paragraph to four sentences or fewer.", + "justification": "The prompt limits narrative paragraphs to four sentences.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Final Answer Only (No Files)", + "dependencies": [] + }, + "criterion 87": { + "description": "Uses no Markdown tables.", + "justification": "The prompt rules out Markdown tables.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Final Answer Only (No Files)", + "dependencies": [] + }, + "criterion 88": { + "description": "Uses no bullet points.", + "justification": "The prompt rules out bullets.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Final Answer Only (No Files)", + "dependencies": [] + }, + "criterion 89": { + "description": "Uses no bold, italic or other typographic emphasis.", + "justification": "The prompt rules out typographic emphasis.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Final Answer Only (No Files)", + "dependencies": [] + }, + "criterion 90": { + "description": "Presents the conditions as a numbered list.", + "justification": "The prompt requires a numbered list for the conditions.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Final Answer Only (No Files)", + "dependencies": [] + }, + "criterion 91": { + "description": "Presents the source ledger with one entry per line.", + "justification": "The prompt requires one ledger entry per line.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Final Answer Only (No Files)", + "dependencies": [] + }, + "criterion 92": { + "description": "Identifies individuals in the memorandum by role, with the employee reference where the sources give one, and reproduces no personal names.", + "justification": "B.11 of Appendix B in 01_Scope_and_Reporting_Memorandum.pdf requires individuals to be identified in the paper by role and employee reference, with names held on the deal file and not reproduced; the prompt makes that basis of preparation govern the memorandum. Employee references exist only for the CGP- records on the Employee Schedule and Transfer Instruments sheets in 05_Separation_and_TSA_Schedule.xlsx, such as the lead architect, platform separation (CGP-08033). Individuals with no reference in the sources, including the attorney on the execution page in 08_Executed_Transfer_Instruments.pdf, the holders on the Signing Authorities sheet, Halcyon executives and adviser staff, are identified by role alone, and a reference invented for them fails. Any personal name of an individual anywhere in the memo, including the source ledger and the condition owners, fails. Names of organisations, adviser firms, projects, products, documents, powers of attorney and contracts are not personal names and are allowed. The criterion checks the identification convention only: it does not require any particular individual to be mentioned or retest which reference belongs to which role, and a condition owner stated as a role, such as the Halcyon CTO, meets it.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Final Answer Only (No Files)", + "dependencies": [] + }, + "criterion 93": { + "description": "States the channel commissions standalone cost (SA-4) as USD 2.3 million, in USD millions to one decimal place (acceptable range USD 2.25 million to USD 2.35 million), because the correction note on the Standalone costs sheet replaces the 2.75 printed for SA-4 with GBP 1.85 million. Stating the corrected GBP 1.85 million and that the note governs on SA-4 satisfies this.", + "justification": "The Standalone costs sheet in 02_Arden_QoE_Databook.xlsx prints SA-4 at 2.75. The correction note, a picture directly below the schedule total on that sheet, issued by Calderwood Group finance on 26 March 2026 in response to data room request Q-0436, signed by the Group Financial Controller and agreed to the FY25 partner commission statements by Bramhall Quinn LLP on 27 March 2026, replaces it with 1.85 because the 2.75 was struck on FY26 budget partner volumes and commission rates. That agreement covers the SA-4 line only; the SA-2 line on the same note has no such agreement and is not adopted. B.2 of Appendix B in 01_Scope_and_Reporting_Memorandum.pdf states the standalone basis at FY25 price and volume levels, and Arden bears no charge for channel commissions today, so the whole GBP 1.85 million is the adjustment. GBP 1.85 million x 1.25 = USD 2.3125 million, displayed USD 2.3 million. The printed 2.75 gives USD 3.4 million, an entry multiple of 11.11x and a false failure of paragraph 4.4(b), and the prompt requires the resolution of a conflict that changes a test result to be stated. The prompt states money in USD millions, so giving the printed and corrected amounts as USD 3.4 million and USD 2.3 million also meets this. The value appears only in the image. The prompt and B.8 of Appendix B in 01_Scope_and_Reporting_Memorandum.pdf require this figure in USD millions to one decimal place; that presentation requirement is part of this criterion, and the range brackets the unrounded value.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Final Answer Only (No Files)", + "dependencies": [] + }, + "criterion 94": { + "description": "States that MI-01 is supported by management's own schedule and that its tender file has not been provided. Referring to the tender file not being in the data room or to the absence of evidence beyond management assertion satisfies this; the management confidence grade does not.", + "justification": "", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Final Answer Only (No Files)", + "dependencies": [] + }, + "criterion 95": { + "description": "States that the step 5 gridline move in Exhibit 04D does not apply at Q1-26, because the 0.5-point gap answers step 4 NO and the pathway runs from sign-off straight to Keep the final issued point. Stating that the final issued Exhibit 04A points stand at Q1-26 with no step 5 uplift satisfies this.", + "justification": "", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Final Answer Only (No Files)", + "dependencies": [] + }, + "criterion 96": { + "description": "Cites Exhibit 04D of 04_Cloud_Migration_and_Interface_Map.pdf in the source ledger for the recording of the hosted shares.", + "justification": "The recording pathway decides whether the step 5 move applies at Q1-26, and that move would meet paragraph 4.5(a), so this is the location for a conclusion that decides the technology test. The pathway appears only in Exhibit 04D.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Final Answer Only (No Files)", + "dependencies": [] + }, + "criterion 97": { + "description": "Cites the Definitions and Contacts sheet (section 3.B) of 06_Integration_Synergy_Schedule.xlsx in the source ledger as the location of the entry recording that the procurement tender file is not in the data room. A ledger line for the benefits or MI-01 conclusion that cites this sheet satisfies this; the line need not repeat the words tender file.", + "justification": "Whether MI-01 is validated decides the benefits test, and the entry recording that the tender file is not in the data room appears only on this sheet, in section 3.B. Note 4 on the Basis of Preparation sheet states a different point, that the file is available to the buyer team on request, so this row does not test the status of the file in general. A ledger may cite note 4 as well, and that costs nothing here; a ledger that cites note 4 alone has not located this entry.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Final Answer Only (No Files)", + "dependencies": [] + }, + "criterion 98": { + "description": "States that SA-2 stays at USD 9.9 million (GBP 7.95 million) and is not reduced to the USD 9.6 million (GBP 7.71 million) on the correction note, because that cut is the benefit of the acquirer's group volume band in the reseller's requote, which paragraph B.2 does not allow to be netted against a standalone cost. Saying that the SA-2 cut on the note is an acquisition benefit and carrying SA-2 at USD 9.9 million (GBP 7.95 million) satisfies this.", + "justification": "The correction note on the Standalone costs sheet in 02_Arden_QoE_Databook.xlsx replaces SA-2 with 7.71, at unchanged FY25 seat volumes, per the reseller's quotation of 20 March 2026. The contracts register in 05_Separation_and_TSA_Schedule.xlsx, C-028, names the reseller and records that requote. Section 2.C of the Basis of Preparation sheet in 06_Integration_Synergy_Schedule.xlsx lists the benefit of the acquirer's group volume band in that requote among the items outside the benefits schedule. B.2 of Appendix B in 01_Scope_and_Reporting_Memorandum.pdf says standalone costs are not netted against, offset by, or presented alongside acquisition benefits. The standalone schedule follows that line elsewhere: SA-1 is priced on the provider's standalone schedule, and the acquirer's rate card appears only in the benefit MI-02. The Bramhall Quinn agreement on the note is to the FY25 partner commission statements, which concern SA-4 only, and the quotation is not among the attachments, so B.9 gives no ground to substitute it. SA-2 therefore stays at GBP 7.95 million. Taking 7.71 moves EBITDA, margin, multiple, maximum enterprise value and headroom to USD 43.3 million, 28.7%, 10.7x, USD 475.9 million and USD 10.9 million, and no test outcome changes. The prompt states money in USD millions, so a memo that gives its SA-2 amounts (USD 9.9 million, and USD 9.6 million if it quotes the note) in USD alone also meets this.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Final Answer Only (No Files)", + "dependencies": [] + } +} \ No newline at end of file diff --git a/tasks/task_dd94dc222db74864a13fcb7c6c2844a2/input/Presentation_Specification.docx b/tasks/task_dd94dc222db74864a13fcb7c6c2844a2/input/Presentation_Specification.docx new file mode 100644 index 0000000000000000000000000000000000000000..3dde5bfe55537844363dc5833c686b6b1eff3369 --- /dev/null +++ b/tasks/task_dd94dc222db74864a13fcb7c6c2844a2/input/Presentation_Specification.docx @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:952e38815fcfce868b4cb649e44ef8d4121b1203034c98f82f6b74071d710b60 +size 48363 diff --git a/tasks/task_dd94dc222db74864a13fcb7c6c2844a2/input/Presentation_Specification.pdf b/tasks/task_dd94dc222db74864a13fcb7c6c2844a2/input/Presentation_Specification.pdf new file mode 100644 index 0000000000000000000000000000000000000000..6004bd5468f5abd7174f17666087fd59f4680540 --- /dev/null +++ b/tasks/task_dd94dc222db74864a13fcb7c6c2844a2/input/Presentation_Specification.pdf @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:24db3ef7b652ff135485e1e12a44cc2d00333f61687bf81d4f9181611ed99d04 +size 510687 diff --git a/tasks/task_dd94dc222db74864a13fcb7c6c2844a2/input/SimLAB_Presentation_Style_Guide.pdf b/tasks/task_dd94dc222db74864a13fcb7c6c2844a2/input/SimLAB_Presentation_Style_Guide.pdf new file mode 100644 index 0000000000000000000000000000000000000000..e8c373624bd61a99628f9b771b323fdd0085bbaa --- /dev/null +++ b/tasks/task_dd94dc222db74864a13fcb7c6c2844a2/input/SimLAB_Presentation_Style_Guide.pdf @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:93875d8b4f9bb2037bcccb852f58caa4883af851d3bcda7b29b3cb50f9d439c4 +size 509556 diff --git a/tasks/task_dd94dc222db74864a13fcb7c6c2844a2/input/SimLAB_Simulation_Activity.pdf b/tasks/task_dd94dc222db74864a13fcb7c6c2844a2/input/SimLAB_Simulation_Activity.pdf new file mode 100644 index 0000000000000000000000000000000000000000..263298953fbe4e27675d5aaec37686ae6cc6c875 --- /dev/null +++ b/tasks/task_dd94dc222db74864a13fcb7c6c2844a2/input/SimLAB_Simulation_Activity.pdf @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:72d3b090b4c2e22c81fddf5f5320a859bcddc6a76e851cf97e2465e4ec68dd4c +size 609894 diff --git a/tasks/task_dd94dc222db74864a13fcb7c6c2844a2/input/SimLAB_Simulation_Flowchart.pdf b/tasks/task_dd94dc222db74864a13fcb7c6c2844a2/input/SimLAB_Simulation_Flowchart.pdf new file mode 100644 index 0000000000000000000000000000000000000000..70468493b6c07fafeccd747101bc7ab5dbd79d5c --- /dev/null +++ b/tasks/task_dd94dc222db74864a13fcb7c6c2844a2/input/SimLAB_Simulation_Flowchart.pdf @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8d64257702f76ac491209ba62c74dddbfd80e63e928dd70e5aa801414dbec92e +size 384926 diff --git a/tasks/task_dd94dc222db74864a13fcb7c6c2844a2/input/SimLAB_System_Diagram_and_Parameters.pdf b/tasks/task_dd94dc222db74864a13fcb7c6c2844a2/input/SimLAB_System_Diagram_and_Parameters.pdf new file mode 100644 index 0000000000000000000000000000000000000000..ed6b78b45768c10cc6db0d35644ed42ee9c41816 --- /dev/null +++ b/tasks/task_dd94dc222db74864a13fcb7c6c2844a2/input/SimLAB_System_Diagram_and_Parameters.pdf @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b97cd4248c58bde8987e7a51daf8e14647a232012439b612819efab2a6cd8d75 +size 400308 diff --git a/tasks/task_dd94dc222db74864a13fcb7c6c2844a2/input/paper_multipleshooting_method_new.pdf b/tasks/task_dd94dc222db74864a13fcb7c6c2844a2/input/paper_multipleshooting_method_new.pdf new file mode 100644 index 0000000000000000000000000000000000000000..889a8c4375f587f7b1d671ffe71472dac48f3f59 --- /dev/null +++ b/tasks/task_dd94dc222db74864a13fcb7c6c2844a2/input/paper_multipleshooting_method_new.pdf @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d198f4df099b792c9e6ab620b8a00794345b4f36ee797b5913b36b93b92505fb +size 167135 diff --git a/tasks/task_dd94dc222db74864a13fcb7c6c2844a2/input/template_task2.pptx b/tasks/task_dd94dc222db74864a13fcb7c6c2844a2/input/template_task2.pptx new file mode 100644 index 0000000000000000000000000000000000000000..a6228114e611ef9edfcf1f13f728a98e5b4505a4 --- /dev/null +++ b/tasks/task_dd94dc222db74864a13fcb7c6c2844a2/input/template_task2.pptx @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:79ccfd9ef1c73debb66ebbbb4cc134c73c266361d14e0dd7e5e887f96aae3a7c +size 134302 diff --git a/tasks/task_dd94dc222db74864a13fcb7c6c2844a2/metadata.json b/tasks/task_dd94dc222db74864a13fcb7c6c2844a2/metadata.json new file mode 100644 index 0000000000000000000000000000000000000000..1ade225e7e313da27ebc0058311df7226db26bf5 --- /dev/null +++ b/tasks/task_dd94dc222db74864a13fcb7c6c2844a2/metadata.json @@ -0,0 +1,12 @@ +{ + "TaskID": "task_dd94dc222db74864a13fcb7c6c2844a2", + "Vertical": "Engineering", + "Domain": "Education", + "Role": "Mechanical engineering instructor", + "Task Goal": "Create a lab activity presentation on simulating a mass-spring-damper system's periodic response using the multiple shooting method.", + "Prompt": "Create a PowerPoint presentation titled \"Sim_Nonlinear_LabActivity.pptx\" with instructions for simulating the periodic response of a mass and spring damper system with a backlash nonlinearity, as given in the attached system diagram. \n\nThe periodic orbit is computed using the multiple shooting method, as detailed in the attached paper and the attached associated flow chart.\n\nUse the instructions in the latest Presentation Specification to create the deliverable. Title each slide as given in the specification.\n\nFollow the formatting rules in the attached style guide and task template for titles, footers and slide layout.", + "Input_files": "Presentation_Specification.docx, Presentation_Specification.pdf, SimLAB_Presentation_Style_Guide.pdf, SimLAB_Simulation_Activity.pdf, SimLAB_Simulation_Flowchart.pdf, SimLAB_System_Diagram_and_Parameters.pdf, paper_multipleshooting_method_new.pdf, template_task2.pptx", + "All Task Files": "tasks/task_dd94dc222db74864a13fcb7c6c2844a2/input/", + "Rubric Criteria": "tasks/task_dd94dc222db74864a13fcb7c6c2844a2/rubrics.json", + "Economic Rationale": "This is a template task for design of simulation based lab activity which is typically required in many engineering courses. Each semester, instructors would have to generate these instructions for a new model and parameters. This typically requires up to two days of work. This task allows the instructors to upload a new image and parameters each semester and generate the new slide deck/lab instructions, which saves this time each semester. The economic value of this task is generated from saving multiple hours of work each semester to refine and redesign lab activities with specified learning outcomes." +} diff --git a/tasks/task_dd94dc222db74864a13fcb7c6c2844a2/rubrics.json b/tasks/task_dd94dc222db74864a13fcb7c6c2844a2/rubrics.json new file mode 100644 index 0000000000000000000000000000000000000000..b4af1ca0cc035d1ef1b8a4a5c0a65ca648371592 --- /dev/null +++ b/tasks/task_dd94dc222db74864a13fcb7c6c2844a2/rubrics.json @@ -0,0 +1,488 @@ +{ + "criterion 1": { + "description": "Includes a PowerPoint presentation file named \"Sim_Nonlinear_LabActivity.pptx\".", + "justification": "The prompt explicitly requests a PowerPoint presentation named \u2018Sim_Nonlinear_LabActivity.pptx\u2019. This criterion checks the requested deliverable format and filename.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 2": { + "description": "States the title of the first slide as \"Simulation Lab: Nonlinear System Simulation Using Multiple Shooting Method\".", + "justification": "The prompt requires each slide to use the title given in the specification. Presentation_Specification.pdf, page 1, Version 1.13, Slide 1, supplies the exact title \u2018Simulation Lab: Nonlinear System Simulation Using Multiple Shooting Method\u2019.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 3": { + "description": "States the title of the second slide as \"System Model\".", + "justification": "Presentation_Specification.pdf, page 1, Version 1.13, names Slide 2 \u2018System Model\u2019. The prompt\u2019s instruction to title each slide as given in the specification makes this the required second-slide title.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 4": { + "description": "States the title of the third slide as \"Backlash Nonlinearity\".", + "justification": "Presentation_Specification.pdf, page 1, Version 1.13, names Slide 3 \u2018Backlash Nonlinearity\u2019. This supplies the third-slide title required by the prompt\u2019s instruction to follow the specification\u2019s slide titles.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 5": { + "description": "States the title of the fourth slide as \"Simulation Method\".", + "justification": "Presentation_Specification.pdf, page 1, Version 1.13, names Slide 4 \u2018Simulation Method\u2019. The prompt expressly requires the slide titles to match those given in that specification.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 6": { + "description": "States the title of the fifth slide as \"Sample Result\".", + "justification": "Presentation_Specification.pdf, page 1, Version 1.13, names Slide 5 \u2018Sample Result\u2019. This is the fifth-slide title required by the prompt\u2019s instruction to use the specification\u2019s slide titles.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 7": { + "description": "States the title of the sixth slide as \"Bonus Activity\".", + "justification": "Presentation_Specification.pdf, page 1, Version 1.13, names Slide 6 \u2018Bonus Activity\u2019. This establishes the final-slide title under the prompt\u2019s instruction to follow the specified slide titles.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 8": { + "description": "Presents every equation in the deliverable as a visible native PowerPoint equation object, editable through PowerPoint\u2019s equation editor.", + "justification": "SimLAB_Presentation_Style_Guide.pdf, page 1, \u2018Equations\u2019, requires every equation to be inserted as a native PowerPoint equation object using the equation editor. ", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 9": { + "description": "Includes an image of the mechanical system schematic of the mass, spring and damper system with backlash showing a single mass with two springs on the \"System Model\" slide.", + "justification": "Presentation_Specification.pdf, page 1, Slide 2 (\u2018System Model\u2019), requires an image of the mechanical system schematic. SimLAB_System_Diagram_and_Parameters.pdf, page 1, Fig. 1 (\u2018A single degree of freedom system with backlash\u2019), supplies that image, showing one mass m between left and right contact spring\u2013damper elements, together with the permanent damper and backlash clearances. This criterion checks inclusion of the supplied mechanical system on the specified slide.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 10": { + "description": "Includes the caption text \"MCK System with Backlash\" for the mechanical system schematic on the \"System Model\" slide.", + "justification": "Presentation_Specification.pdf, page 1, Slide 2, specifies the caption wording \u2018MCK System with Backlash\u2019. ", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 11": { + "description": "States the equation of motion for the system on the \"System Model\" slide as \\(m\\ddot{x} + C(x)\\dot{x} + K(x) = F\\). Algebraically equivalent equation-of-motion notations are acceptable, such as \\(m\\ddot{x} + C(x, \\dot{x}) + K(x, \\dot{x}) = F(t)\\), and \\(m\\ddot{x} + c\\dot{x} + C(x, \\dot{x}) + K(x, \\dot{x}) = F(t)\\).", + "justification": "Presentation_Specification.pdf, page 1, Slide 2, requires the equation of motion for the supplied system. The prompt describes a forced mass\u2013spring\u2013damper system with backlash, and SimLAB_System_Diagram_and_Parameters.pdf, page 1, Fig. 1, supplies its mechanical model. Applying Newton\u2019s second law gives m x\u0308 + Fd + Fs = F(t). With total damping force Fd = C(x)x\u0307 and restoring force Fs = K(x), this becomes m x\u0308 + C(x)x\u0307 + K(x) = F. K(x) denotes a force in this notation; consistently defined algebraically equivalent formulations express the same force balance.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 4, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 12": { + "description": "States that the restoring force is zero in the clearance subspace on the \u201cBacklash Nonlinearity\u201d slide. Equivalent force symbols and argument lists, such as $K(x)$, $K(x,\\dot{x})$ or $F_s$, are acceptable. Equivalent subspace descriptions include $x \\in V$, $(x,\\dot{x}) \\in V$, and alternative region labels or conditions that denote the same clearance subspace as $V$.", + "justification": "Presentation_Specification.pdf, page 1, Slide 3 (\u2018Backlash Nonlinearity\u2019), requires restoring-force equations for every subspace using a linear spring model. In SimLAB_System_Diagram_and_Parameters.pdf, page 1, Figs. 1 and 2, V is the free or clearance subspace in which neither contact spring acts. Its restoring-force branch is therefore K(x) = 0. The subspace is identified from the supplied phase-space diagram, whose boundaries include slanted segments.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 4, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 13": { + "description": "States the restoring forces as $k_1(x+b)$ in the left contact subspace $V_1$ and $k_2(x-b)$ in the right contact subspace $V_2$ on the \u201cBacklash Nonlinearity\u201d slide. Algebraically equivalent force laws, alternative force symbols and argument lists, and equivalent subspace descriptions are acceptable. These descriptions include phase space membership $(x,\\dot{x}) \\in V_1$ and $(x,\\dot{x}) \\in V_2$, and alternative region labels or conditions that denote the same left and right contact subspaces as $V_1$ and $V_2$, respectively.", + "justification": "Presentation_Specification.pdf, page 1, Slide 3, requires a linear restoring-force expression for each subspace. SimLAB_System_Diagram_and_Parameters.pdf, page 1, Fig. 1, shows contact springs at clearance offsets \u2212b and +b; Fig. 2 identifies the active left and right contact subspaces V1 and V2. The signed spring deformations give restoring terms k1(x + b) in V1 and k2(x \u2212 b) in V2. These expressions describe the spring forces within the respective active contact subspaces.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 4, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 14": { + "description": "States either the total damping force $c\\dot{x}$ or a contact-damping contribution of zero in the clearance subspace $V$ on the \u201cBacklash Nonlinearity\u201d slide. The zero-contact-damping form, such as $C(x)=0$ or $C(x,\\dot{x})=0$, is acceptable when the permanent base damping $c\\dot{x}$ is included separately in the equation of motion on the \u201cSystem Model\u201d slide or on the \u201cBacklash Nonlinearity\u201d slide. The resulting force balance includes the base damping contribution exactly once. Equivalent force or damping-coefficient notation and equivalent subspace descriptions, including $x \\in V$, $(x,\\dot{x}) \\in V$, or alternative labels identifying the same clearance subspace, are acceptable.", + "justification": "Presentation_Specification.pdf, Version 1.13, page 1, Slide 3, requires damping-force expressions for each subspace. SimLAB_System_Diagram_and_Parameters.pdf, page 1, Fig. 1, shows that the permanent damper $c$ acts in the clearance subspace while the contact dampers are disengaged. The total damping force in $V$ is therefore $c\\dot{x}$. In a decomposed formulation, the permanent base damping $c\\dot{x}$ appears separately in the equation of motion, and the piecewise contact-damping contribution is zero in $V$, expressed as $C(x)=0$ or $C(x,\\dot{x})=0$. When the base term is shown on the \u201cSystem Model\u201d slide or the \u201cBacklash Nonlinearity\u201d slide, these representations describe the same total damping force, with the permanent base contribution included exactly once.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 4, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 15": { + "description": "States the damping contributions in the contact subspaces on the \u201cBacklash Nonlinearity\u201d slide using either total damping forces $(c+c_1)\\dot{x}$ in the left contact subspace $V_1$ and $(c+c_2)\\dot{x}$ in the right contact subspace $V_2$, or contact damping forces $c_1\\dot{x}$ in $V_1$ and $c_2\\dot{x}$ in $V_2$, with the permanent base damping $c\\dot{x}$ included separately in the equation of motion on the \u201cSystem Model\u201d slide or on the \u201cBacklash Nonlinearity\u201d slide. The resulting force balance includes the base damping contribution exactly once. Equivalent force symbols, damping-coefficient notation, algebraically equivalent expressions, and alternative subspace labels or conditions identifying the same physical contact regions are acceptable.", + "justification": "Presentation_Specification.pdf, Version 1.13, page 1, Slide 3, requires damping-force expressions for each subspace. SimLAB_System_Diagram_and_Parameters.pdf, page 1, Fig. 1, shows that the permanent damper $c$ continues to act when either contact damper is engaged. The total damping forces are therefore $c\\dot{x}+c_1\\dot{x}=(c+c_1)\\dot{x}$ in $V_1$ and $c\\dot{x}+c_2\\dot{x}=(c+c_2)\\dot{x}$ in $V_2$. A formulation that includes $c\\dot{x}$ separately in the equation of motion may define its piecewise contact damping as $c_1\\dot{x}$ and $c_2\\dot{x}$. Both formulations receive credit when their definitions produce the same total damping contribution, consistently with the equation of motion.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 4, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 16": { + "description": "Includes the backlash-subspace figure on the \u201cBacklash Nonlinearity\u201d slide, built using native PowerPoint drawing elements. The figure includes the position axis $x$, velocity axis $\\dot{x}$, subspace labels $V_1$, $V$ and $V_2$, clearance thresholds $-b$ and $b$ on the position axis, and two switching boundaries with vertical and slanted segments.", + "justification": "Presentation_Specification.pdf, Version 1.13, page 1, Slide 3, requires the supplied subspace figure. SimLAB_System_Diagram_and_Parameters.pdf, page 1, Fig. 2, provides its axes, region labels, clearance thresholds and boundary geometry. SimLAB_Presentation_Style_Guide.pdf, page 1, requires the subspace chart to be a native PowerPoint object.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 17": { + "description": "States the continuity condition as \\(y(x_j;\\, x_{j-1}, s_{j-1}) = s_j,\\ j = 1,\\dots,m-1\\) on the \"Simulation Method\" slide.", + "justification": "Presentation_Specification.pdf, page 1, Slide 4, requires the continuity condition exactly as listed in the attached paper. In paper_multipleshooting_method_new.pdf, Section 6.2 (\u2018Multiple Shooting Methods \u2014 The Set-up\u2019), printed page 3, equation (6.31) states y(xj; xj\u22121, sj\u22121) = sj for j = 1, \u2026, m\u22121. This matches the trajectory integrated from one shooting node to the state at the next interior node.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 18": { + "description": "States the boundary condition as \\(A s_0 + B\\, y(b;\\, x_{m-1}, s_{j-1}) = \\alpha\\) on the \"Simulation Method\" slide. It is acceptable to use \\(s_{m-1}\\) as an equivalent to \\(s_{j-1}\\) since the latter is a typo in the supplied paper.", + "justification": "Presentation_Specification.pdf, page 1, Slide 4, requires the boundary condition exactly as listed in the paper. In paper_multipleshooting_method_new.pdf, Section 6.2, printed page 4, equation (6.32) prints As0 + B y(b; xm\u22121, sj\u22121) = \u03b1. The criterion reproduces that printed form, including its sj\u22121 index. Here b is the paper\u2019s right endpoint of the BVP interval; it is distinct from the mechanical clearance parameter with the same symbol.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 19": { + "description": "States the transformed two-point boundary value problem differential equation as \\(\\dfrac{dY}{d\\tau} = F(\\tau, Y),\\ 0 \\le \\tau \\le 1\\).", + "justification": "Presentation_Specification.pdf, page 1, Slide 4, requires the transformed two-point BVP equations as given in the paper. In paper_multipleshooting_method_new.pdf, Section 6.2, printed page 4, equations (6.33)-(6.38) rescale the shooting intervals. The subsequent definition of the stacked variable Y leads to equation (6.39): dY/d\u03c4 = F(\u03c4, Y), 0 \u2264 \u03c4 \u2264 1. This criterion assesses that transformed differential equation and its normalized interval.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 20": { + "description": "States the transformed two-point boundary value problem boundary equation as \\(P\\,Y(0) + Q\\,Y(1) = \\beta\\).", + "justification": "Presentation_Specification.pdf, page 1, Slide 4, requires the transformed two-point BVP equations from the paper. In paper_multipleshooting_method_new.pdf, Section 6.2, printed page 4, equation (6.40) states PY(0) + QY(1) = \u03b2. The matrices P and Q printed below it collect the original boundary relation and shooting continuity relations into this transformed two-point boundary condition.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 21": { + "description": "Includes the supplied simulation-procedure flowchart on the \u201cSimulation Method\u201d slide, built using connected native PowerPoint blocks and directional arrows. It shows the time vector; initial state, subspace and forcing phase; system-matrix selection; state calculation; subspace checking; and the decision whether the subspace has changed. The \u201cno\u201d branch leads to stopping. The \u201cyes\u201d branch leads to finding the switching time, calculating the new initial condition and updating the forcing phase, followed by a return to system-matrix selection. Equivalent wording that preserves these stages and connections is acceptable.", + "justification": "Presentation_Specification.pdf, Version 1.13, page 1, Slide 4, requires the attached simulation flowchart. SimLAB_Simulation_Flowchart.pdf, page 1, Fig. 1, supplies the initialization sequence, state calculations, subspace-change decision, stopping branch and switching-update loop. SimLAB_Presentation_Style_Guide.pdf, page 1, \u201cFlowchart and subspace chart\u201d, requires the flowchart to be a native PowerPoint object. ", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 22": { + "description": "States the undamped natural frequency of the linearized system in each contact subspace, $V_1$ and $V_2$, as $2.00$ rad/s on the \u201cSample Result\u201d slide, reported to two decimal places (acceptable range is $1.99$ to $2.01$ rad/s). Separate values or one shared value explicitly identified as applying to both contact subspaces are acceptable. The unit rad/s appears with the value or in an applicable table label or header.", + "justification": "Presentation_Specification.pdf (Version 1.13), page 1, Slide 5, requires the contact-subspace undamped natural frequencies in rad/s to two decimal places. The topology in Fig. 1 of SimLAB_System_Diagram_and_Parameters.pdf (page 1) shows that the contacted side's spring acts on the mass; Table 1 gives m = 1 kg and k1 = k2 = 4 N/m. Thus omega_n,i = sqrt(ki/m) = sqrt(4/1) = 2.00 rad/s in both contact subspaces. The clearance offset changes equilibrium position rather than the engaged spring's stiffness. The 1.99 to 2.01 rad/s acceptance band is a rubric tolerance.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 23": { + "description": "Lists two separately identified absolute frequency-difference results on the \u201cSample Result\u201d slide for forcing frequency $0.4$ rad/s: one for contact subspace $V_1$ and one for contact subspace $V_2$. Each result is $1.60$ rad/s, reported to two decimal places (acceptable range is $1.59$ to $1.61$ rad/s). The unit rad/s appears with each value or in an applicable table label or header.", + "justification": "Presentation_Specification.pdf (Version 1.13), page 1, Slide 5, requires absolute differences between each of the forcing frequencies 0.4 and 1.4 rad/s and each contact-subspace natural frequency, reported with units to two decimal places. From the active-spring topology and Table 1 of SimLAB_System_Diagram_and_Parameters.pdf (page 1), both contact natural frequencies are 2.00 rad/s. For the lower forcing frequency, |0.40 - 2.00| = 1.60 rad/s in each contact subspace.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 24": { + "description": "Lists two separately identified absolute frequency-difference results on the \u201cSample Result\u201d slide for forcing frequency $1.4$ rad/s: one for contact subspace $V_1$ and one for contact subspace $V_2$. Each result is $0.60$ rad/s, reported to two decimal places (acceptable range is $0.59$ to $0.61$ rad/s). The unit rad/s appears with each value or in an applicable table label or header.", + "justification": "Presentation_Specification.pdf (Version 1.13), page 1, Slide 5, requires all four absolute frequency differences, covering both specified forcing frequencies and both contact subspaces, with units and two-decimal reporting. The two contact natural frequencies derived from Fig. 1 and Table 1 of SimLAB_System_Diagram_and_Parameters.pdf (page 1) are each 2.00 rad/s. For the higher forcing frequency, |1.40 - 2.00| = 0.60 rad/s in each contact subspace.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 25": { + "description": "States the peak amplitude of mass position for the sample result at forcing frequency $0.4$ rad/s as $1.79$ m on the \u201cSample Result\u201d slide, reported as a single final numerical value rounded to two decimal places (acceptable range is $1.77$ to $1.81$ m).", + "justification": "Presentation_Specification.pdf (Version 1.13), page 1, Slide 5, requires peak mass-position amplitude in meters as a single final value rounded to two decimal places. SimLAB_Simulation_Activity.pdf (page 1), Fig. 1, shows a 1 N force with period 5 pi s, giving omega = 0.4 rad/s; its Fig. 2 and Initial state entry identify the orange t = 0 state as x0 = 1.0 m and x_dot0 = 1.45 m/s. The mechanical model and parameters come from SimLAB_System_Diagram_and_Parameters.pdf (page 1). The rubric's reference periodic-orbit calculation for this sample case gives approximately 1.79 m, reported as 1.79 m, with acceptance from 1.77 to 1.81 m. This peak is calculated, rather than printed in the input files.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 5, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 26": { + "description": "States the peak velocity for the sample result at forcing frequency 0.4 rad/s as 1.44 m/s, reported as a single final numerical value rounded to two decimal places (acceptable range is 1.42 to 1.46 m/s).", + "justification": "Presentation_Specification.pdf (Version 1.13), page 1, Slide 5, requires peak velocity in meters per second as a single final value rounded to two decimal places. The sample forcing and initialization are read from SimLAB_Simulation_Activity.pdf (page 1): Fig. 1 gives amplitude 1 N and period 5 pi s, hence omega = 0.4 rad/s, and the orange t = 0 marker in Fig. 2 gives x0 = 1.0 m and x_dot0 = 1.45 m/s. With the mechanical model in SimLAB_System_Diagram_and_Parameters.pdf (page 1) and the activity's multiple-shooting configuration, the rubric's reference periodic solution has peak velocity approximately 1.44 m/s. The reported target is 1.44 m/s and the rubric tolerance is 1.42 to 1.46 m/s; this is a computed result.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 5, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 27": { + "description": "Includes the phase portrait on the \"Sample Result\" slide as a native editable chart object with its own underlying data series.", + "justification": "Presentation_Specification.pdf (Version 1.13), page 1, Slide 5, explicitly requires the sample phase portrait to be embedded as a native chart. A native editable PowerPoint chart containing its own position/velocity data series implements that requirement and makes the plotted data available for editing inside the presentation.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 28": { + "description": "Includes the phase portrait on the \"Bonus Activity\" slide, as a native editable chart object with its own underlying data series.", + "justification": "Presentation_Specification.pdf (Version 1.13), page 1, Slide 6, explicitly requires the bonus phase portrait to be embedded as a native chart. The chart therefore needs an editable PowerPoint chart object with its own underlying position/velocity data series.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 29": { + "description": "Includes the horizontal axis title \"x [m]\" on both the \"Sample Result\" and the \"Bonus Activity\" phase-portrait charts.", + "justification": "Presentation_Specification.pdf (Version 1.13), page 1, Slides 5 and 6, explicitly requires the horizontal phase-portrait axis to be labelled x [m]. The label identifies mass position as the horizontal coordinate and states its unit in meters. This criterion checks that same required axis title on both the Sample Result and Bonus Activity charts.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 30": { + "description": "Includes the vertical axis title \"x_dot [m/s]\" on both the \"Sample Result\" and the \"Bonus Activity\" phase-portrait charts.", + "justification": "Presentation_Specification.pdf (Version 1.13), page 1, Slides 5 and 6, explicitly requires the vertical phase-portrait axis to be labelled x_dot [m/s]. This denotes velocity in meters per second.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 31": { + "description": "Includes two switching lines using dashed lines on the \"Sample Result\" phase-portrait chart.", + "justification": "Presentation_Specification.pdf (Version 1.13), page 1, Slide 5, requires dashed switching lines on the sample phase portrait. Fig. 2 of SimLAB_System_Diagram_and_Parameters.pdf (page 1) supplies the two boundaries separating V1, V and V2.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 32": { + "description": "Includes two switching lines using dashed lines on the \"Bonus Activity\" phase-portrait chart.", + "justification": "Presentation_Specification.pdf (Version 1.13), page 1, Slide 6, requires dashed switching lines on the bonus phase portrait. Fig. 2 of SimLAB_System_Diagram_and_Parameters.pdf (page 1) shows the two boundaries between V1, V and V2.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 33": { + "description": "Presents a closed periodic orbit trajectory with absolute peak amplitude of 1.79 m (acceptable range 1.77 to 1.81 m) on the \"Sample Result\" phase-portrait chart.", + "justification": "The prompt requires a periodic orbit computed by multiple shooting, and Presentation_Specification.pdf (Version 1.13), page 1, Slide 5, requires its sample phase portrait. SimLAB_Simulation_Activity.pdf (page 1) supplies the graph-read sample forcing and initial state and specifies evaluation over one full response period, with maximum sampling interval T/200. A periodic state returns to the same position and velocity and therefore forms a closed phase-plane curve. Using the mechanical model and parameters in SimLAB_System_Diagram_and_Parameters.pdf (page 1), the rubric's reference sample orbit at omega = 0.4 rad/s has absolute peak position approximately 1.79 m. This criterion checks the plotted trajectory and its 1.77 to 1.81 m peak tolerance, rather than only the rounded scalar listed on the slide.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 34": { + "description": "Shows a peak absolute velocity of $1.44$ m/s (acceptable range is $1.42$ to $1.46$ m/s) in the periodic-orbit data series on the \u201cSample Result\u201d phase-portrait chart for forcing frequency $\\omega = 0.4$ rad/s.", + "justification": "Presentation_Specification.pdf, Version 1.13, page 1, Slide 5, requires a sample phase portrait for the system and simulation configuration supplied in the inputs. SimLAB_Simulation_Activity.pdf, page 1, provides the forcing signal corresponding to $\\omega = 0.4$ rad/s and the initial state $x_0 = 1.0$ m and $\\dot{x}_0 = 1.45$ m/s. Using the nominal mechanical model and parameters in SimLAB_System_Diagram_and_Parameters.pdf gives a reference periodic orbit with peak absolute velocity approximately $1.44$ m/s. This criterion checks the maximum value of $|\\dot{x}|$ in the plotted orbit data series. The scalar velocity reported elsewhere on the slide is assessed separately. ", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 35": { + "description": "Presents a closed periodic orbit trajectory for forcing frequency 1.4 rad/s with absolute peak position amplitude of 2.45 m (acceptable range 2.4 to 2.6 m) on the 'Bonus Activity' phase-portrait chart.", + "justification": "Presentation_Specification.pdf, Version 1.13, page 1, Slide 6, requires a bonus phase portrait for forcing frequency $\\omega = 1.4$ rad/s, starting from $x_0 = 1.0$ m and $\\dot{x}_0 = 2.75$ m/s. The nominal mechanical model and parameters are supplied in SimLAB_System_Diagram_and_Parameters.pdf, and the periodic-orbit evaluation configuration is supplied in SimLAB_Simulation_Activity.pdf. The reference calculation gives a closed periodic orbit with peak absolute position approximately $2.45$ m (acceptable range is $2.4$ to $2.6$ m). This criterion checks the closed trajectory and the maximum value of $|x|$ in the chart\u2019s plotted orbit data series over one complete forcing period. The scalar peak-position value reported elsewhere on the slide and the chart\u2019s peak velocity are assessed separately.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 36": { + "description": "Shows a peak absolute velocity of $3.24$ m/s (acceptable range is $3.1$ to $3.3$ m/s) in the periodic-orbit data series on the \u201cBonus Activity\u201d phase-portrait chart for the nominal system at forcing frequency $\\omega = 1.4$ rad/s.", + "justification": "Presentation_Specification.pdf, Version 1.13, page 1, Slide 6, requires a bonus phase portrait for $\\omega = 1.4$ rad/s, starting from $x_0 = 1.0$ m and $\\dot{x}_0 = 2.75$ m/s. Using the nominal mechanical model and parameters in SimLAB_System_Diagram_and_Parameters.pdf and the evaluation configuration in SimLAB_Simulation_Activity.pdf gives a reference periodic orbit with peak absolute velocity approximately $3.24$ m/s. This criterion checks the maximum value of $|\\dot{x}|$ in the plotted orbit series. The scalar velocity reported elsewhere on the slide is assessed separately.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 37": { + "description": "Presents a bonus activity statement on the \"Bonus Activity\" slide instructing students to redo the simulation and generate a phase portrait for the excitation frequency \\(\\omega = 1.4\\) rad/s.", + "justification": "Presentation_Specification.pdf, Version 1.13, page 1, Slide 6 \u201cBonus Activity\u201d, asks students to redo the simulation and generate a phase portrait for omega = 1.4 rad/s. The slide must communicate both actions and identify 1.4 rad/s as the angular forcing frequency for this bonus case.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 38": { + "description": "States the bonus activity starting conditions as \\(x_0 = 1.0\\) m and \\(\\dot{x}_0 = 2.75\\) m/s on the \"Bonus Activity\" slide.", + "justification": "Presentation_Specification.pdf, Version 1.13, page 1, Slide 6 \u201cBonus Activity\u201d, specifies the starting state as x0 = 1.0 m and x_dot0 = 2.75 m/s. These are the bonus simulation\u2019s initial position and initial velocity and must be stated together with their units.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 39": { + "description": "States the peak amplitude of mass position for the bonus activity at forcing frequency 1.4 rad/s as 2.5 m, rounded to one decimal place (acceptable range is 2.4 to 2.6 m).", + "justification": "Presentation_Specification.pdf, Version 1.13, page 1, Slide 6 \u201cBonus Activity\u201d, requires the resulting peak position amplitude in metres rounded to one decimal place. Computing the periodic orbit at omega = 1.4 rad/s from the specified bonus initial state, using the mechanical model and nominal parameters in SimLAB_System_Diagram_and_Parameters.pdf, page 1, and the evaluation configuration in SimLAB_Simulation_Activity.pdf, page 1, gives a peak absolute position of approximately 2.45017 m. This simulation-derived reference rounds to 2.5 m; the criterion\u2019s accepted reporting range is 2.4\u20132.6 m.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 5, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 40": { + "description": "States the peak velocity for the bonus activity at forcing frequency 1.4 rad/s as 3.2 m/s, rounded to one decimal place (acceptable range is 3.1 to 3.3 m/s).", + "justification": "Presentation_Specification.pdf, Version 1.13, page 1, Slide 6 \u201cBonus Activity\u201d, requires the resulting peak velocity in metres per second rounded to one decimal place. Computing the periodic orbit at omega = 1.4 rad/s from the specified bonus initial state, using SimLAB_System_Diagram_and_Parameters.pdf, page 1, and the evaluation configuration in SimLAB_Simulation_Activity.pdf, page 1, gives a peak absolute velocity of approximately 3.24 m/s. This simulation-derived reference rounds to 3.2 m/s; the criterion\u2019s accepted reporting range is 3.1\u20133.3 m/s.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 5, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 41": { + "description": "Marks at least one peak-position location and at least one peak-velocity location on the \u201cBonus Activity\u201d phase-portrait chart. For each quantity independently, the positive maximum, negative minimum, or both are acceptable. Each selected location uses a single triangle as its sole point-marker symbol.", + "justification": "Presentation_Specification.pdf, Version 1.13, page 1, Slide 6, requires triangle markers at the peak-amplitude and peak-velocity locations without specifying their signs or a marker count. A positive maximum or negative minimum of position satisfies the peak-position requirement, and either corresponding velocity extremum satisfies the peak-velocity requirement. The signs may be selected independently. Marking additional corresponding extrema with triangles is acceptable. This criterion assesses the marker locations and shapes; the orbit\u2019s numerical peak values are assessed separately.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 42": { + "description": "Inserts a footer with text \"Simulation of Nonlinear Systems with Backlash\" line on all slides.", + "justification": "SimLAB_Presentation_Style_Guide.pdf, page 1, \u201cSlide layout and text\u201d, Footer row, requires every slide to include the exact text \u201cSimulation of Nonlinear Systems with Backlash\u201d. The complete footer phrase must therefore appear on all six slides, including the title slide.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 43": { + "description": "Includes a slide number on each of the six slides.", + "justification": "SimLAB_Presentation_Style_Guide.pdf, page 1, \u201cSlide layout and text\u201d, Footer row, requires a page number on each slide. Applied to the six-slide presentation specified in Presentation_Specification.pdf, Version 1.13, page 1, this requires a visible slide number on every slide.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 44": { + "description": "Formats every slide title in the Arial font of size 22.", + "justification": "SimLAB_Presentation_Style_Guide.pdf, page 1, \u2018Slide layout and text\u2019, Titles row, explicitly specifies 22-point Arial for slide titles. This criterion checks that every slide title uses both the required typeface and the required point size.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 45": { + "description": "Presents the phase-portrait charts on the right half of the slides.", + "justification": "SimLAB_Presentation_Style_Guide.pdf, page 1, \u201cSlide layout and text\u201d, Images row, requires images on the right half of the slide. Applying that placement rule to the native phase-portrait figures required by Presentation_Specification.pdf, Version 1.13, page 1, Slides 5 and 6, places both phase-portrait charts on the right half of their respective slides.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 46": { + "description": "Presents the equations and tables on the left half of the slides.", + "justification": "SimLAB_Presentation_Style_Guide.pdf, page 1, \u201cSlide layout and text\u201d, Equations and tables row, explicitly places both equations and tables on the left half of slides. This applies to the governing and force equations, the multiple-shooting equations and any tables in the presentation, including the Sample Result numerical-results table required by Presentation_Specification.pdf, Version 1.13, page 1, Slide 5.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 47": { + "description": "Presents the model schematic on the right half of the slide.", + "justification": "SimLAB_Presentation_Style_Guide.pdf, page 1, \u201cSlide layout and text\u201d, Images row, requires images on the right half of the slide. The mechanical schematic required by Presentation_Specification.pdf, Version 1.13, page 1, Slide 2 \u201cSystem Model\u201d, is an image and must therefore occupy the right half of that slide.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 48": { + "description": "Uses a black background on the title slide, as specified by the attached presentation template (template_task2.pptx).", + "justification": "The black title-slide background comes from template_task2.pptx, which the prompt requires the presentation to follow.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 49": { + "description": "Uses a black background for the header on content slides, as specified by the attached presentation template (template_task2.pptx).", + "justification": "The black header background on content slides comes from template_task2.pptx, which the prompt requires the presentation to follow.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 50": { + "description": "Sets the horizontal axis range of the \u201cSample Result\u201d phase-portrait chart below $-1$ m and above $1$ m, displaying interior portions of both contact regions.", + "justification": "Presentation_Specification.pdf, Version 1.13, page 1, Slide 5 \u201cSample Result\u201d, requires axis ranges that make both contact regions visible. SimLAB_System_Diagram_and_Parameters.pdf, page 1, Table 1, gives the clearance parameter b = 1 m, and Figure 2 places the clearance thresholds at x = \u2212b and x = b. The Sample Result chart must therefore include x = \u22121 m and x = 1 m in its displayed range. Figure 2 also shows the slanted, velocity-dependent branches of the full switching boundaries.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 51": { + "description": "Sets the horizontal axis range of the \u201cBonus Activity\u201d phase-portrait chart below $-1$ m and above $1$ m, displaying interior portions of both contact regions.", + "justification": "Presentation_Specification.pdf, Version 1.13, page 1, Slide 6 \u201cBonus Activity\u201d, requires axis ranges that make both contact regions visible. SimLAB_System_Diagram_and_Parameters.pdf, page 1, Table 1 and Figure 2, give b = 1 m and locate the clearance thresholds at x = \u2212b and x = b. The Bonus Activity chart must therefore include x = \u22121 m and x = 1 m in its displayed range. The full phase-plane boundaries also include the slanted branches shown in Figure 2.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 52": { + "description": "Formats all non-title slides in #0F9ED5 background color below the header.", + "justification": "SimLAB_Presentation_Style_Guide.pdf, page 1, \u201cTemplate\u201d, requires use of the attached presentation template. The content layout used by Slide 2 in template_task2.pptx fills the body below the black header with theme color accent4, which the template theme defines as RGB #0F9ED5. Every non-title slide must retain that lower-body background color.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 53": { + "description": "Presents the numerical results for the Sample Result on Slide 5 in a two-column table with headers \"Quantity\" and \"Value\".", + "justification": "Presentation_Specification.pdf, Version 1.13, page 1, Slide 5 \u201cSample Result\u201d, explicitly requires the numerical results in one two-column table headed \u201cQuantity\u201d and \u201cValue\u201d. The Sample Result slide must therefore present its numerical results in that table structure, with quantity labels in the first column and their corresponding reported values in the second, using the two required header texts.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + }, + "criterion 54": { + "description": "Captions each figure in the deliverable in the form Fig. N ", + "justification": "SimLAB_Presentation_Style_Guide.pdf, page 1, Slide layout and text, Figure captions row, requires captions in the form Fig. N ", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Presentations (.pptx, .ppt, .odp)", + "dependencies": [] + } +} \ No newline at end of file diff --git a/tasks/task_e49e96e764424db08531c39fb685ed70/input/dependencies.png b/tasks/task_e49e96e764424db08531c39fb685ed70/input/dependencies.png new file mode 100644 index 0000000000000000000000000000000000000000..c7e127aeee1de8a5531471b38ec549e45475a16d --- /dev/null +++ b/tasks/task_e49e96e764424db08531c39fb685ed70/input/dependencies.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c6dea6648591459b5ed4f6db16cc59545bb82a7cf40233cdd4d629696a9c80ec +size 296143 diff --git a/tasks/task_e49e96e764424db08531c39fb685ed70/input/driver_method.docx b/tasks/task_e49e96e764424db08531c39fb685ed70/input/driver_method.docx new file mode 100644 index 0000000000000000000000000000000000000000..1c96b81d89476fd16baeec8f7cb800154c00d6b3 --- /dev/null +++ b/tasks/task_e49e96e764424db08531c39fb685ed70/input/driver_method.docx @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f177524d19c401305588dac445d7475b0706b2fbaedb3450de5dbc820871819d +size 21351 diff --git a/tasks/task_e49e96e764424db08531c39fb685ed70/input/driver_schema.docx b/tasks/task_e49e96e764424db08531c39fb685ed70/input/driver_schema.docx new file mode 100644 index 0000000000000000000000000000000000000000..5ee7af725c3008e1a0c784c67ba623382561f41e --- /dev/null +++ b/tasks/task_e49e96e764424db08531c39fb685ed70/input/driver_schema.docx @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2280e1f29f5ce72df6b8086cfc1745392d4d1ceec497a232c0151c2a291ff525 +size 21979 diff --git a/tasks/task_e49e96e764424db08531c39fb685ed70/input/main_rules.xlsx b/tasks/task_e49e96e764424db08531c39fb685ed70/input/main_rules.xlsx new file mode 100644 index 0000000000000000000000000000000000000000..84d17f712a10cfb25b212149b7408406d4a31ff9 --- /dev/null +++ b/tasks/task_e49e96e764424db08531c39fb685ed70/input/main_rules.xlsx @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ee9cbb449251156b16dfba5a7539a9ff7840c57b7ef39e3fd9ca4bb3aa1fc60b +size 18817 diff --git a/tasks/task_e49e96e764424db08531c39fb685ed70/input/other_rules.xlsx b/tasks/task_e49e96e764424db08531c39fb685ed70/input/other_rules.xlsx new file mode 100644 index 0000000000000000000000000000000000000000..db41651d4a2dfd460cf5f31c52c722a5a29e748a --- /dev/null +++ b/tasks/task_e49e96e764424db08531c39fb685ed70/input/other_rules.xlsx @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:716281a25aaec7532218ace08ad6c74bfe2284362be9e5f5d4c5e5580cc7d599 +size 18515 diff --git a/tasks/task_e49e96e764424db08531c39fb685ed70/input/revenue_2025.csv b/tasks/task_e49e96e764424db08531c39fb685ed70/input/revenue_2025.csv new file mode 100644 index 0000000000000000000000000000000000000000..4402d9cdafd365aeed2b73bdddc643a8cd1fc2d4 --- /dev/null +++ b/tasks/task_e49e96e764424db08531c39fb685ed70/input/revenue_2025.csv @@ -0,0 +1,34 @@ +department,jan,feb,mar,apr,may,jun,jul,aug,sep,oct,nov,dec +Admin & General,56634,78274,95577,73681,91815,64563,91144,96174,61925,94456,67534,54166 +Bar,81139,73362,55843,82990,58697,76472,87165,53495,84267,55052,59833,61810 +Breakfast,53840,60577,60970,62990,96670,56582,74874,89550,54261,61000,68959,96866 +Business Lounge,94075,60422,64033,78057,53438,51290,98529,89150,97205,86856,67889,82369 +EWW (Utilities),72734,53552,52327,68352,69164,71118,53052,96767,53975,75622,52710,57570 +F&B Other Income,93492,50346,64503,84807,88524,80104,92789,80508,82613,79616,96209,71673 +F&B division,92881,79774,65331,76150,56176,57945,98025,84609,76503,82967,56310,50830 +F&B overheads,67105,83653,72631,78406,88465,60588,72303,80801,66579,62375,80706,59142 +Front Office,90175,77801,87074,62636,87006,66511,98330,57108,72841,83576,89940,62995 +HouseKeeping,96552,74588,58654,59810,57254,92302,69027,81677,68420,59007,79616,80352 +IT & Telecom,88519,50424,99321,84857,91030,95457,88987,90959,73244,96756,63505,71349 +Kitchen,56545,68055,56495,68193,52704,82781,80921,97805,65230,82926,95813,70197 +Meeting & Event F&B,55067,70866,59087,64367,76793,76707,58730,80829,98150,83420,65486,68508 +Meeting & Event Other,53281,76288,61683,85159,53409,97260,53808,53896,84627,76661,98125,89054 +Minibar,86568,91187,92891,87751,98123,57968,91333,94235,66389,74446,99651,55663 +Nightclub,64223,69729,96412,90207,83282,61862,91875,69250,94995,51907,55883,87243 +Other - Other Income,98336,91761,76262,82949,64890,67855,96558,55105,58178,66250,73168,73662 +Other - overheads,73491,70227,57412,56606,64776,77577,80460,99498,66031,61190,91725,67435 +Other Operating Departments division,80618,81762,90041,78058,84662,54993,93690,75714,69012,75619,82686,91937 +Other services,89053,73734,65915,89986,54514,61042,58491,91663,57056,68458,85470,86765 +Overhead Expenses division,75436,56665,96084,97363,88029,86283,67175,70983,96333,96938,93140,97427 +Property,64869,70104,90849,89721,53232,68717,93954,80341,55573,98386,53851,76426 +Public Area Cleaning,61573,99166,80894,50147,96962,69443,98426,74308,59998,90086,61140,79868 +Repair & Maintainance,89339,82004,78436,97771,51735,60625,62835,86886,69945,54125,81407,77208 +Restaurant,86434,79889,72492,55648,54721,67110,67857,52503,67905,70040,59877,91683 +Retail,68920,78153,92627,66201,55031,67091,51342,59008,64332,89418,66007,61091 +Room Service,80120,67377,53036,54628,73046,62596,57442,86053,53495,69117,98041,65339 +Rooms Other Income,77915,94499,91205,98753,96479,51448,90816,56279,72825,56988,68208,55058 +Rooms division,63161,55819,68831,55698,78039,83335,84777,50576,65043,74271,85761,84436 +Rooms overheads,63177,72459,55057,96607,77642,95974,95775,92732,58792,54349,62454,57098 +Sales & Marketing,97279,79310,85994,89416,81209,99688,57617,56967,54478,77266,54319,53857 +Spa,61965,94424,60579,87480,75292,62456,82278,66142,65676,66991,63127,95011 +Stewarding,80732,94196,93244,62199,69768,80648,74173,75067,67179,61684,63961,92489 diff --git a/tasks/task_e49e96e764424db08531c39fb685ed70/metadata.json b/tasks/task_e49e96e764424db08531c39fb685ed70/metadata.json new file mode 100644 index 0000000000000000000000000000000000000000..8b5febd6d6146e5b2a45af353b6125425baa9480 --- /dev/null +++ b/tasks/task_e49e96e764424db08531c39fb685ed70/metadata.json @@ -0,0 +1,12 @@ +{ + "TaskID": "task_e49e96e764424db08531c39fb685ed70", + "Vertical": "Software & Data", + "Domain": "Data Science", + "Role": "Data scientist", + "Task Goal": "Identify which measures best predict hotel department labour costs for the month ahead.", + "Prompt": "Generate the candidate drivers as sources to forecast labor cost of hotel departments in June, 2026. Return exactly one file, candidate_drivers.json, a single JSON document built to the schema in driver_schema.docx.\n\nUse driver_method.docx to get general rules for candidate drivers generation; main_rules.xlsx to get how many days to be used to generate candidate drivers for primary cost drivers; other_rules.xlsx to get how many days to be used to generate candidate drivers for dependent departments; dependencies.png to get dependency among departments throughout the year or in each particular season; revenue_2025.csv to get the monthly revenue for each department in 2025.\n\nFor revenue-season totals and every season-specific average used in the adjusted-revenue calculation, include every row in revenue_2025.csv, including Property and Division rollup rows. \n\nFormat the output for review readability: indent the JSON with two spaces per nesting level. Place the opening brace for each top-level department object on the line immediately below its department key. Leave exactly one blank line between the departments array and the first department object. Leave exactly one blank line between consecutive top-level department objects. Order the departments alphabetically in ascending order. Write booleans as native JSON literals (true, false), never quoted and never omitted. Keep every string plain American Standard Code for Information Interchange (ASCII) text.", + "Input_files": "dependencies.png, driver_method.docx, driver_schema.docx, main_rules.xlsx, other_rules.xlsx, revenue_2025.csv", + "All Task Files": "tasks/task_e49e96e764424db08531c39fb685ed70/input/", + "Rubric Criteria": "tasks/task_e49e96e764424db08531c39fb685ed70/rubrics.json", + "Economic Rationale": "Labor cost forecasting is critical in hotel management because it enables proactive and effective staff scheduling across hotel departments. While there are multiple approaches to forecasting labor costs, one efficient and practical method is to identify candidate cost drivers from various sources and compute their correlations with the target department to determine the most predictive driver. Discovering these candidate drivers manually, however, is both time-consuming and error-prone because it requires checking settings and revenue values across several departments. It often takes several hours for a hotel manager to do this task correctly." +} diff --git a/tasks/task_e49e96e764424db08531c39fb685ed70/rubrics.json b/tasks/task_e49e96e764424db08531c39fb685ed70/rubrics.json new file mode 100644 index 0000000000000000000000000000000000000000..d6641c49040b8311023ed327b3127384c9a99f7f --- /dev/null +++ b/tasks/task_e49e96e764424db08531c39fb685ed70/rubrics.json @@ -0,0 +1,767 @@ +{ + "criterion 1": { + "description": "Produces exactly one output file named candidate_drivers.json.", + "justification": "", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "JSON/YAML (.json, .yaml, .yml)", + "dependencies": [] + }, + "criterion 2": { + "description": "Contains one valid, parseable JSON document.", + "justification": "", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "JSON/YAML (.json, .yaml, .yml)", + "dependencies": [] + }, + "criterion 3": { + "description": "Indents the JSON document with two spaces per nesting level.", + "justification": "The Review formatting section of driver_schema.docx requires two spaces per indentation level. This criterion grades the visual layout of the JSON text, not the statistical computation.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "JSON/YAML (.json, .yaml, .yml)", + "dependencies": [] + }, + "criterion 4": { + "description": "States month as Jun-2026.", + "justification": "The solver prompt identifies June 2026; driver_schema.docx gives the MMM-YYYY month format and the literal case-sensitive output value Jun-2026.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "JSON/YAML (.json, .yaml, .yml)", + "dependencies": [] + }, + "criterion 5": { + "description": "Orders the departments array alphabetically in ascending order.", + "justification": "The driver_schema.docx review requirements specify alphabetical ascending order for the department names; the prompt defers to the documented schema.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "JSON/YAML (.json, .yaml, .yml)", + "dependencies": [] + }, + "criterion 6": { + "description": "States 'Bar'.dep_sources as [\"Meeting & Event F&B\"] (acceptable value [\"Meeting & Event F&B\"]).", + "justification": "", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 4, + "grading_target": "JSON/YAML (.json, .yaml, .yml)", + "dependencies": [] + }, + "criterion 7": { + "description": "States 'Bar'.params.pri_force.day_before as \"1-6\" (acceptable value \"1-6\").", + "justification": "The Update rule in driver_method.docx applies when an arrow exists in dependencies.png but is excluded by the rules above. Those rules include both season matching and the revenue comparison. June is non-peak. Restaurant is excluded by the revenue comparison (Group A, +3 days). Room Service and Meeting & Event Other are peak-only incoming sources and are excluded by season matching (Group B, +2 days, and Group C, +1 day). Meeting & Event F&B remains the retained source. The three exclusions add 6 days and make same_day false. Both default timing windows are empty/true/empty: main_rules.xlsx, SMART!E12:G12, and other_rules.xlsx, SMART!D12:F12. The result for both parameters is 1-6/false/1-6. Restricting the update to revenue-test exclusions would omit Condition 1 from the phrase rules above.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "JSON/YAML (.json, .yaml, .yml)", + "dependencies": [] + }, + "criterion 8": { + "description": "States 'Bar'.params.pri_force.same_day as false (acceptable value false).", + "justification": "", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "JSON/YAML (.json, .yaml, .yml)", + "dependencies": [] + }, + "criterion 9": { + "description": "States 'Bar'.params.pri_force.day_after as \"1-6\" (acceptable value \"1-6\").", + "justification": "The Update rule in driver_method.docx applies when an arrow exists in dependencies.png but is excluded by the rules above. Those rules include both season matching and the revenue comparison. June is non-peak. Restaurant is excluded by the revenue comparison (Group A, +3 days). Room Service and Meeting & Event Other are peak-only incoming sources and are excluded by season matching (Group B, +2 days, and Group C, +1 day). Meeting & Event F&B remains the retained source. The three exclusions add 6 days and make same_day false. Both default timing windows are empty/true/empty: main_rules.xlsx, SMART!E12:G12, and other_rules.xlsx, SMART!D12:F12. The result for both parameters is 1-6/false/1-6. Restricting the update to revenue-test exclusions would omit Condition 1 from the phrase rules above.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "JSON/YAML (.json, .yaml, .yml)", + "dependencies": [] + }, + "criterion 10": { + "description": "States 'Bar'.params.department.day_before as \"1-6\" (acceptable value \"1-6\").", + "justification": "The Update rule in driver_method.docx applies when an arrow exists in dependencies.png but is excluded by the rules above. Those rules include both season matching and the revenue comparison. June is non-peak. Restaurant is excluded by the revenue comparison (Group A, +3 days). Room Service and Meeting & Event Other are peak-only incoming sources and are excluded by season matching (Group B, +2 days, and Group C, +1 day). Meeting & Event F&B remains the retained source. The three exclusions add 6 days and make same_day false. Both default timing windows are empty/true/empty: main_rules.xlsx, SMART!E12:G12, and other_rules.xlsx, SMART!D12:F12. The result for both parameters is 1-6/false/1-6. Restricting the update to revenue-test exclusions would omit Condition 1 from the phrase rules above.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "JSON/YAML (.json, .yaml, .yml)", + "dependencies": [] + }, + "criterion 11": { + "description": "States 'Bar'.params.department.same_day as false (acceptable value false).", + "justification": "", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "JSON/YAML (.json, .yaml, .yml)", + "dependencies": [] + }, + "criterion 12": { + "description": "States 'Bar'.params.department.day_after as \"1-6\" (acceptable value \"1-6\").", + "justification": "The Update rule in driver_method.docx applies when an arrow exists in dependencies.png but is excluded by the rules above. Those rules include both season matching and the revenue comparison. June is non-peak. Restaurant is excluded by the revenue comparison (Group A, +3 days). Room Service and Meeting & Event Other are peak-only incoming sources and are excluded by season matching (Group B, +2 days, and Group C, +1 day). Meeting & Event F&B remains the retained source. The three exclusions add 6 days and make same_day false. Both default timing windows are empty/true/empty: main_rules.xlsx, SMART!E12:G12, and other_rules.xlsx, SMART!D12:F12. The result for both parameters is 1-6/false/1-6. Restricting the update to revenue-test exclusions would omit Condition 1 from the phrase rules above.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "JSON/YAML (.json, .yaml, .yml)", + "dependencies": [] + }, + "criterion 13": { + "description": "States 'Breakfast'.dep_sources as [\"Nightclub\"] (acceptable value [\"Nightclub\"]).", + "justification": "", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 4, + "grading_target": "JSON/YAML (.json, .yaml, .yml)", + "dependencies": [] + }, + "criterion 14": { + "description": "States 'Breakfast'.params.pri_force.day_before as \"1-3\" (acceptable value \"1-3\").", + "justification": "", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "JSON/YAML (.json, .yaml, .yml)", + "dependencies": [] + }, + "criterion 15": { + "description": "States 'Breakfast'.params.pri_force.same_day as false (acceptable value false).", + "justification": "", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "JSON/YAML (.json, .yaml, .yml)", + "dependencies": [] + }, + "criterion 16": { + "description": "States 'Breakfast'.params.pri_force.day_after as \"1-3\" (acceptable value \"1-3\").", + "justification": "", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "JSON/YAML (.json, .yaml, .yml)", + "dependencies": [] + }, + "criterion 17": { + "description": "States 'Breakfast'.params.department.day_before as \"1-1\" (acceptable value \"1-1\").", + "justification": "", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "JSON/YAML (.json, .yaml, .yml)", + "dependencies": [] + }, + "criterion 18": { + "description": "States 'Breakfast'.params.department.same_day as false (acceptable value false).", + "justification": "", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "JSON/YAML (.json, .yaml, .yml)", + "dependencies": [] + }, + "criterion 19": { + "description": "States 'Breakfast'.params.department.day_after as \"1-1\" (acceptable value \"1-1\").", + "justification": "", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "JSON/YAML (.json, .yaml, .yml)", + "dependencies": [] + }, + "criterion 20": { + "description": "States 'F&B overheads'.dep_sources as [\"Stewarding\"] (acceptable value [\"Stewarding\"]).", + "justification": "The prompt includes all 33 revenue rows when identifying seasons. June is non-peak. In dependencies.png, incoming arrows to F&B overheads are Restaurant and Meeting & Event F&B in all seasons, plus Meeting & Event Other and Stewarding in non-peak seasons. The March-May average adjusted revenues are 77,145.882576 for F&B overheads, 67,705.715909 for Restaurant, 70,603.382576 for Meeting & Event F&B, 70,604.049242 for Meeting & Event Other, and 74,764.049242 for Stewarding. All four sources fail the strict greater-than test. The fallback in driver_method.docx retains Stewarding, the highest-valued source. The other three sources are excluded: Restaurant adds 3 days, Meeting & Event F&B adds 2 days, and Meeting & Event Other adds 1 day. Three exclusions set same_day to false. main_rules.xlsx, SMART!E24:G24, gives pri_force defaults 1-2/true/1-2. other_rules.xlsx, SMART!D24:F24, gives department defaults empty/true/1. Adding 6 days gives pri_force 1-8/false/1-8 and department 1-6/false/1-7. Comparisons use unrounded revenues.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 4, + "grading_target": "JSON/YAML (.json, .yaml, .yml)", + "dependencies": [] + }, + "criterion 21": { + "description": "States 'F&B overheads'.params.pri_force.day_before as \"1-8\" (acceptable value \"1-8\").", + "justification": "The prompt includes all 33 revenue rows when identifying seasons. June is non-peak. In dependencies.png, incoming arrows to F&B overheads are Restaurant and Meeting & Event F&B in all seasons, plus Meeting & Event Other and Stewarding in non-peak seasons. The March-May average adjusted revenues are 77,145.882576 for F&B overheads, 67,705.715909 for Restaurant, 70,603.382576 for Meeting & Event F&B, 70,604.049242 for Meeting & Event Other, and 74,764.049242 for Stewarding. All four sources fail the strict greater-than test. The fallback in driver_method.docx retains Stewarding, the highest-valued source. The other three sources are excluded: Restaurant adds 3 days, Meeting & Event F&B adds 2 days, and Meeting & Event Other adds 1 day. Three exclusions set same_day to false. main_rules.xlsx, SMART!E24:G24, gives pri_force defaults 1-2/true/1-2. other_rules.xlsx, SMART!D24:F24, gives department defaults empty/true/1. Adding 6 days gives pri_force 1-8/false/1-8 and department 1-6/false/1-7. Comparisons use unrounded revenues.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "JSON/YAML (.json, .yaml, .yml)", + "dependencies": [] + }, + "criterion 22": { + "description": "States 'F&B overheads'.params.pri_force.same_day as false (acceptable value false).", + "justification": "The prompt includes all 33 revenue rows when identifying seasons. June is non-peak. In dependencies.png, incoming arrows to F&B overheads are Restaurant and Meeting & Event F&B in all seasons, plus Meeting & Event Other and Stewarding in non-peak seasons. The March-May average adjusted revenues are 77,145.882576 for F&B overheads, 67,705.715909 for Restaurant, 70,603.382576 for Meeting & Event F&B, 70,604.049242 for Meeting & Event Other, and 74,764.049242 for Stewarding. All four sources fail the strict greater-than test. The fallback in driver_method.docx retains Stewarding, the highest-valued source. The other three sources are excluded: Restaurant adds 3 days, Meeting & Event F&B adds 2 days, and Meeting & Event Other adds 1 day. Three exclusions set same_day to false. main_rules.xlsx, SMART!E24:G24, gives pri_force defaults 1-2/true/1-2. other_rules.xlsx, SMART!D24:F24, gives department defaults empty/true/1. Adding 6 days gives pri_force 1-8/false/1-8 and department 1-6/false/1-7. Comparisons use unrounded revenues.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "JSON/YAML (.json, .yaml, .yml)", + "dependencies": [] + }, + "criterion 23": { + "description": "States 'F&B overheads'.params.pri_force.day_after as \"1-8\" (acceptable value \"1-8\").", + "justification": "The prompt includes all 33 revenue rows when identifying seasons. June is non-peak. In dependencies.png, incoming arrows to F&B overheads are Restaurant and Meeting & Event F&B in all seasons, plus Meeting & Event Other and Stewarding in non-peak seasons. The March-May average adjusted revenues are 77,145.882576 for F&B overheads, 67,705.715909 for Restaurant, 70,603.382576 for Meeting & Event F&B, 70,604.049242 for Meeting & Event Other, and 74,764.049242 for Stewarding. All four sources fail the strict greater-than test. The fallback in driver_method.docx retains Stewarding, the highest-valued source. The other three sources are excluded: Restaurant adds 3 days, Meeting & Event F&B adds 2 days, and Meeting & Event Other adds 1 day. Three exclusions set same_day to false. main_rules.xlsx, SMART!E24:G24, gives pri_force defaults 1-2/true/1-2. other_rules.xlsx, SMART!D24:F24, gives department defaults empty/true/1. Adding 6 days gives pri_force 1-8/false/1-8 and department 1-6/false/1-7. Comparisons use unrounded revenues.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "JSON/YAML (.json, .yaml, .yml)", + "dependencies": [] + }, + "criterion 24": { + "description": "States 'F&B overheads'.params.department.day_before as \"1-6\" (acceptable value \"1-6\").", + "justification": "The prompt includes all 33 revenue rows when identifying seasons. June is non-peak. In dependencies.png, incoming arrows to F&B overheads are Restaurant and Meeting & Event F&B in all seasons, plus Meeting & Event Other and Stewarding in non-peak seasons. The March-May average adjusted revenues are 77,145.882576 for F&B overheads, 67,705.715909 for Restaurant, 70,603.382576 for Meeting & Event F&B, 70,604.049242 for Meeting & Event Other, and 74,764.049242 for Stewarding. All four sources fail the strict greater-than test. The fallback in driver_method.docx retains Stewarding, the highest-valued source. The other three sources are excluded: Restaurant adds 3 days, Meeting & Event F&B adds 2 days, and Meeting & Event Other adds 1 day. Three exclusions set same_day to false. main_rules.xlsx, SMART!E24:G24, gives pri_force defaults 1-2/true/1-2. other_rules.xlsx, SMART!D24:F24, gives department defaults empty/true/1. Adding 6 days gives pri_force 1-8/false/1-8 and department 1-6/false/1-7. Comparisons use unrounded revenues.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "JSON/YAML (.json, .yaml, .yml)", + "dependencies": [] + }, + "criterion 25": { + "description": "States 'F&B overheads'.params.department.same_day as false (acceptable value false).", + "justification": "The prompt includes all 33 revenue rows when identifying seasons. June is non-peak. In dependencies.png, incoming arrows to F&B overheads are Restaurant and Meeting & Event F&B in all seasons, plus Meeting & Event Other and Stewarding in non-peak seasons. The March-May average adjusted revenues are 77,145.882576 for F&B overheads, 67,705.715909 for Restaurant, 70,603.382576 for Meeting & Event F&B, 70,604.049242 for Meeting & Event Other, and 74,764.049242 for Stewarding. All four sources fail the strict greater-than test. The fallback in driver_method.docx retains Stewarding, the highest-valued source. The other three sources are excluded: Restaurant adds 3 days, Meeting & Event F&B adds 2 days, and Meeting & Event Other adds 1 day. Three exclusions set same_day to false. main_rules.xlsx, SMART!E24:G24, gives pri_force defaults 1-2/true/1-2. other_rules.xlsx, SMART!D24:F24, gives department defaults empty/true/1. Adding 6 days gives pri_force 1-8/false/1-8 and department 1-6/false/1-7. Comparisons use unrounded revenues.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "JSON/YAML (.json, .yaml, .yml)", + "dependencies": [] + }, + "criterion 26": { + "description": "States 'F&B overheads'.params.department.day_after as \"1-7\" (acceptable value \"1-7\").", + "justification": "The prompt includes all 33 revenue rows when identifying seasons. June is non-peak. In dependencies.png, incoming arrows to F&B overheads are Restaurant and Meeting & Event F&B in all seasons, plus Meeting & Event Other and Stewarding in non-peak seasons. The March-May average adjusted revenues are 77,145.882576 for F&B overheads, 67,705.715909 for Restaurant, 70,603.382576 for Meeting & Event F&B, 70,604.049242 for Meeting & Event Other, and 74,764.049242 for Stewarding. All four sources fail the strict greater-than test. The fallback in driver_method.docx retains Stewarding, the highest-valued source. The other three sources are excluded: Restaurant adds 3 days, Meeting & Event F&B adds 2 days, and Meeting & Event Other adds 1 day. Three exclusions set same_day to false. main_rules.xlsx, SMART!E24:G24, gives pri_force defaults 1-2/true/1-2. other_rules.xlsx, SMART!D24:F24, gives department defaults empty/true/1. Adding 6 days gives pri_force 1-8/false/1-8 and department 1-6/false/1-7. Comparisons use unrounded revenues.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "JSON/YAML (.json, .yaml, .yml)", + "dependencies": [] + }, + "criterion 27": { + "description": "States 'Kitchen'.dep_sources as [\"Total food revenue\"] (acceptable value [\"Total food revenue\"]).", + "justification": "", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 4, + "grading_target": "JSON/YAML (.json, .yaml, .yml)", + "dependencies": [] + }, + "criterion 28": { + "description": "States 'Kitchen'.params.pri_force.day_before as \"1-1\" (acceptable value \"1-1\").", + "justification": "The Update rule in driver_method.docx covers arrows excluded by either dependency condition, including season matching. June is non-peak, so the peak-only incoming F&B overheads arrow to Kitchen is excluded. F&B overheads belongs to Group C, so this adds 1 day to each side and one exclusion sets same_day to false. Total food revenue is retained under the exception that ignores the revenue comparison. Both default timing windows are empty/true/1-2: main_rules.xlsx, SMART!E10:G10, and other_rules.xlsx, SMART!D10:F10. The updated values are 1-1/false/1-3 for both parameters.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "JSON/YAML (.json, .yaml, .yml)", + "dependencies": [] + }, + "criterion 29": { + "description": "States 'Kitchen'.params.pri_force.same_day as false (acceptable value false).", + "justification": "The Update rule in driver_method.docx covers arrows excluded by either dependency condition, including season matching. June is non-peak, so the peak-only incoming F&B overheads arrow to Kitchen is excluded. F&B overheads belongs to Group C, so this adds 1 day to each side and one exclusion sets same_day to false. Total food revenue is retained under the exception that ignores the revenue comparison. Both default timing windows are empty/true/1-2: main_rules.xlsx, SMART!E10:G10, and other_rules.xlsx, SMART!D10:F10. The updated values are 1-1/false/1-3 for both parameters.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "JSON/YAML (.json, .yaml, .yml)", + "dependencies": [] + }, + "criterion 30": { + "description": "States 'Kitchen'.params.pri_force.day_after as \"1-3\" (acceptable value \"1-3\").", + "justification": "The Update rule in driver_method.docx covers arrows excluded by either dependency condition, including season matching. June is non-peak, so the peak-only incoming F&B overheads arrow to Kitchen is excluded. F&B overheads belongs to Group C, so this adds 1 day to each side and one exclusion sets same_day to false. Total food revenue is retained under the exception that ignores the revenue comparison. Both default timing windows are empty/true/1-2: main_rules.xlsx, SMART!E10:G10, and other_rules.xlsx, SMART!D10:F10. The updated values are 1-1/false/1-3 for both parameters.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "JSON/YAML (.json, .yaml, .yml)", + "dependencies": [] + }, + "criterion 31": { + "description": "States 'Kitchen'.params.department.day_before as \"1-1\" (acceptable value \"1-1\").", + "justification": "The Update rule in driver_method.docx covers arrows excluded by either dependency condition, including season matching. June is non-peak, so the peak-only incoming F&B overheads arrow to Kitchen is excluded. F&B overheads belongs to Group C, so this adds 1 day to each side and one exclusion sets same_day to false. Total food revenue is retained under the exception that ignores the revenue comparison. Both default timing windows are empty/true/1-2: main_rules.xlsx, SMART!E10:G10, and other_rules.xlsx, SMART!D10:F10. The updated values are 1-1/false/1-3 for both parameters.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "JSON/YAML (.json, .yaml, .yml)", + "dependencies": [] + }, + "criterion 32": { + "description": "States 'Kitchen'.params.department.same_day as false (acceptable value false).", + "justification": "The Update rule in driver_method.docx covers arrows excluded by either dependency condition, including season matching. June is non-peak, so the peak-only incoming F&B overheads arrow to Kitchen is excluded. F&B overheads belongs to Group C, so this adds 1 day to each side and one exclusion sets same_day to false. Total food revenue is retained under the exception that ignores the revenue comparison. Both default timing windows are empty/true/1-2: main_rules.xlsx, SMART!E10:G10, and other_rules.xlsx, SMART!D10:F10. The updated values are 1-1/false/1-3 for both parameters.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "JSON/YAML (.json, .yaml, .yml)", + "dependencies": [] + }, + "criterion 33": { + "description": "States 'Kitchen'.params.department.day_after as \"1-3\" (acceptable value \"1-3\").", + "justification": "The Update rule in driver_method.docx covers arrows excluded by either dependency condition, including season matching. June is non-peak, so the peak-only incoming F&B overheads arrow to Kitchen is excluded. F&B overheads belongs to Group C, so this adds 1 day to each side and one exclusion sets same_day to false. Total food revenue is retained under the exception that ignores the revenue comparison. Both default timing windows are empty/true/1-2: main_rules.xlsx, SMART!E10:G10, and other_rules.xlsx, SMART!D10:F10. The updated values are 1-1/false/1-3 for both parameters.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "JSON/YAML (.json, .yaml, .yml)", + "dependencies": [] + }, + "criterion 34": { + "description": "States 'Meeting & Event F&B'.dep_sources as [\"Meeting & Event Other\"] (acceptable value [\"Meeting & Event Other\"]).", + "justification": "June is non-peak. In dependencies.png, the dashed arrow leaving Kitchen continues right/down into Meeting & Event F&B. The dashed arrow leaving F&B overheads crosses that path and continues right/up into Nightclub. The crossing has no junction. Meeting & Event F&B therefore has incoming sources Kitchen, Restaurant, and Meeting & Event Other. March-May average adjusted revenue is 70,603.382576 for the target, 66,794.215909 for Kitchen, 67,705.715909 for Restaurant, and 70,604.049242 for Meeting & Event Other. Only Meeting & Event Other passes the strict greater-than test. Its unrounded advantage is 2/3. Kitchen and Restaurant are both Group A sources, so the update rule adds 3+3=6 days. Two exclusions keep same_day true. main_rules.xlsx, SMART!E14:G14, gives pri_force defaults empty/true/empty. other_rules.xlsx, SMART!D14:F14, gives department defaults 1/true/empty. Updated values are pri_force 1-6/true/1-6 and department 1-7/true/1-6.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 4, + "grading_target": "JSON/YAML (.json, .yaml, .yml)", + "dependencies": [] + }, + "criterion 35": { + "description": "States 'Meeting & Event F&B'.params.pri_force.day_before as \"1-6\" (acceptable value \"1-6\").", + "justification": "June is non-peak. In dependencies.png, the dashed arrow leaving Kitchen continues right/down into Meeting & Event F&B. The dashed arrow leaving F&B overheads crosses that path and continues right/up into Nightclub. The crossing has no junction. Meeting & Event F&B therefore has incoming sources Kitchen, Restaurant, and Meeting & Event Other. March-May average adjusted revenue is 70,603.382576 for the target, 66,794.215909 for Kitchen, 67,705.715909 for Restaurant, and 70,604.049242 for Meeting & Event Other. Only Meeting & Event Other passes the strict greater-than test. Its unrounded advantage is 2/3. Kitchen and Restaurant are both Group A sources, so the update rule adds 3+3=6 days. Two exclusions keep same_day true. main_rules.xlsx, SMART!E14:G14, gives pri_force defaults empty/true/empty. other_rules.xlsx, SMART!D14:F14, gives department defaults 1/true/empty. Updated values are pri_force 1-6/true/1-6 and department 1-7/true/1-6.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "JSON/YAML (.json, .yaml, .yml)", + "dependencies": [] + }, + "criterion 36": { + "description": "States 'Meeting & Event F&B'.params.pri_force.same_day as true (acceptable value true).", + "justification": "June is non-peak. In dependencies.png, the dashed arrow leaving Kitchen continues right/down into Meeting & Event F&B. The dashed arrow leaving F&B overheads crosses that path and continues right/up into Nightclub. The crossing has no junction. Meeting & Event F&B therefore has incoming sources Kitchen, Restaurant, and Meeting & Event Other. March-May average adjusted revenue is 70,603.382576 for the target, 66,794.215909 for Kitchen, 67,705.715909 for Restaurant, and 70,604.049242 for Meeting & Event Other. Only Meeting & Event Other passes the strict greater-than test. Its unrounded advantage is 2/3. Kitchen and Restaurant are both Group A sources, so the update rule adds 3+3=6 days. Two exclusions keep same_day true. main_rules.xlsx, SMART!E14:G14, gives pri_force defaults empty/true/empty. other_rules.xlsx, SMART!D14:F14, gives department defaults 1/true/empty. Updated values are pri_force 1-6/true/1-6 and department 1-7/true/1-6.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "JSON/YAML (.json, .yaml, .yml)", + "dependencies": [] + }, + "criterion 37": { + "description": "States 'Meeting & Event F&B'.params.pri_force.day_after as \"1-6\" (acceptable value \"1-6\").", + "justification": "June is non-peak. In dependencies.png, the dashed arrow leaving Kitchen continues right/down into Meeting & Event F&B. The dashed arrow leaving F&B overheads crosses that path and continues right/up into Nightclub. The crossing has no junction. Meeting & Event F&B therefore has incoming sources Kitchen, Restaurant, and Meeting & Event Other. March-May average adjusted revenue is 70,603.382576 for the target, 66,794.215909 for Kitchen, 67,705.715909 for Restaurant, and 70,604.049242 for Meeting & Event Other. Only Meeting & Event Other passes the strict greater-than test. Its unrounded advantage is 2/3. Kitchen and Restaurant are both Group A sources, so the update rule adds 3+3=6 days. Two exclusions keep same_day true. main_rules.xlsx, SMART!E14:G14, gives pri_force defaults empty/true/empty. other_rules.xlsx, SMART!D14:F14, gives department defaults 1/true/empty. Updated values are pri_force 1-6/true/1-6 and department 1-7/true/1-6.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "JSON/YAML (.json, .yaml, .yml)", + "dependencies": [] + }, + "criterion 38": { + "description": "States 'Meeting & Event F&B'.params.department.day_before as \"1-7\" (acceptable value \"1-7\").", + "justification": "June is non-peak. In dependencies.png, the dashed arrow leaving Kitchen continues right/down into Meeting & Event F&B. The dashed arrow leaving F&B overheads crosses that path and continues right/up into Nightclub. The crossing has no junction. Meeting & Event F&B therefore has incoming sources Kitchen, Restaurant, and Meeting & Event Other. March-May average adjusted revenue is 70,603.382576 for the target, 66,794.215909 for Kitchen, 67,705.715909 for Restaurant, and 70,604.049242 for Meeting & Event Other. Only Meeting & Event Other passes the strict greater-than test. Its unrounded advantage is 2/3. Kitchen and Restaurant are both Group A sources, so the update rule adds 3+3=6 days. Two exclusions keep same_day true. main_rules.xlsx, SMART!E14:G14, gives pri_force defaults empty/true/empty. other_rules.xlsx, SMART!D14:F14, gives department defaults 1/true/empty. Updated values are pri_force 1-6/true/1-6 and department 1-7/true/1-6.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "JSON/YAML (.json, .yaml, .yml)", + "dependencies": [] + }, + "criterion 39": { + "description": "States 'Meeting & Event F&B'.params.department.same_day as true (acceptable value true).", + "justification": "June is non-peak. In dependencies.png, the dashed arrow leaving Kitchen continues right/down into Meeting & Event F&B. The dashed arrow leaving F&B overheads crosses that path and continues right/up into Nightclub. The crossing has no junction. Meeting & Event F&B therefore has incoming sources Kitchen, Restaurant, and Meeting & Event Other. March-May average adjusted revenue is 70,603.382576 for the target, 66,794.215909 for Kitchen, 67,705.715909 for Restaurant, and 70,604.049242 for Meeting & Event Other. Only Meeting & Event Other passes the strict greater-than test. Its unrounded advantage is 2/3. Kitchen and Restaurant are both Group A sources, so the update rule adds 3+3=6 days. Two exclusions keep same_day true. main_rules.xlsx, SMART!E14:G14, gives pri_force defaults empty/true/empty. other_rules.xlsx, SMART!D14:F14, gives department defaults 1/true/empty. Updated values are pri_force 1-6/true/1-6 and department 1-7/true/1-6.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "JSON/YAML (.json, .yaml, .yml)", + "dependencies": [] + }, + "criterion 40": { + "description": "States 'Meeting & Event F&B'.params.department.day_after as \"1-6\" (acceptable value \"1-6\").", + "justification": "June is non-peak. In dependencies.png, the dashed arrow leaving Kitchen continues right/down into Meeting & Event F&B. The dashed arrow leaving F&B overheads crosses that path and continues right/up into Nightclub. The crossing has no junction. Meeting & Event F&B therefore has incoming sources Kitchen, Restaurant, and Meeting & Event Other. March-May average adjusted revenue is 70,603.382576 for the target, 66,794.215909 for Kitchen, 67,705.715909 for Restaurant, and 70,604.049242 for Meeting & Event Other. Only Meeting & Event Other passes the strict greater-than test. Its unrounded advantage is 2/3. Kitchen and Restaurant are both Group A sources, so the update rule adds 3+3=6 days. Two exclusions keep same_day true. main_rules.xlsx, SMART!E14:G14, gives pri_force defaults empty/true/empty. other_rules.xlsx, SMART!D14:F14, gives department defaults 1/true/empty. Updated values are pri_force 1-6/true/1-6 and department 1-7/true/1-6.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "JSON/YAML (.json, .yaml, .yml)", + "dependencies": [] + }, + "criterion 41": { + "description": "States 'Meeting & Event Other'.dep_sources as [\"Nightclub\"] (acceptable value [\"Nightclub\"]).", + "justification": "", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 4, + "grading_target": "JSON/YAML (.json, .yaml, .yml)", + "dependencies": [] + }, + "criterion 42": { + "description": "States 'Meeting & Event Other'.params.pri_force.day_before as \"1-4\" (acceptable value \"1-4\").", + "justification": "", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "JSON/YAML (.json, .yaml, .yml)", + "dependencies": [] + }, + "criterion 43": { + "description": "States 'Meeting & Event Other'.params.pri_force.same_day as true (acceptable value true).", + "justification": "", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "JSON/YAML (.json, .yaml, .yml)", + "dependencies": [] + }, + "criterion 44": { + "description": "States 'Meeting & Event Other'.params.pri_force.day_after as \"1-4\" (acceptable value \"1-4\").", + "justification": "", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "JSON/YAML (.json, .yaml, .yml)", + "dependencies": [] + }, + "criterion 45": { + "description": "States 'Meeting & Event Other'.params.department.day_before as \"1-4\" (acceptable value \"1-4\").", + "justification": "", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "JSON/YAML (.json, .yaml, .yml)", + "dependencies": [] + }, + "criterion 46": { + "description": "States 'Meeting & Event Other'.params.department.same_day as true (acceptable value true).", + "justification": "", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "JSON/YAML (.json, .yaml, .yml)", + "dependencies": [] + }, + "criterion 47": { + "description": "States 'Meeting & Event Other'.params.department.day_after as \"1-4\" (acceptable value \"1-4\").", + "justification": "", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "JSON/YAML (.json, .yaml, .yml)", + "dependencies": [] + }, + "criterion 48": { + "description": "States 'Nightclub'.dep_sources as [\"F&B overheads\"] (acceptable value [\"F&B overheads\"]).", + "justification": "June is non-peak. In dependencies.png, the only incoming arrows to Nightclub are two dashed (non-peak) arrows into its bottom edge, one from Stewarding and one from F&B overheads; the F&B overheads arrow leaves the top of that box, rises past Kitchen and Restaurant and crosses the Kitchen to Meeting & Event F&B dashed arrow without a junction. March-May average adjusted revenue is 82,212.382576 for Nightclub, 74,764.049242 for Stewarding and 77,145.882576 for F&B overheads, so both sources fail the strict greater-than test and the fallback in driver_method.docx retains F&B overheads, the higher of the two. Stewarding is excluded: Group B adds 2 days to each side and one exclusion sets same_day to false. main_rules.xlsx, SMART!E31:G31, gives pri_force defaults empty/true/empty. other_rules.xlsx, SMART!D31:F31, gives department defaults 1/true/empty. The results are pri_force 1-2/false/1-2 and department 1-3/false/1-2. Comparisons use unrounded revenues.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 4, + "grading_target": "JSON/YAML (.json, .yaml, .yml)", + "dependencies": [] + }, + "criterion 49": { + "description": "States 'Nightclub'.params.pri_force.day_before as \"1-2\" (acceptable value \"1-2\").", + "justification": "June is non-peak. In dependencies.png, the only incoming arrows to Nightclub are two dashed (non-peak) arrows into its bottom edge, one from Stewarding and one from F&B overheads; the F&B overheads arrow leaves the top of that box, rises past Kitchen and Restaurant and crosses the Kitchen to Meeting & Event F&B dashed arrow without a junction. March-May average adjusted revenue is 82,212.382576 for Nightclub, 74,764.049242 for Stewarding and 77,145.882576 for F&B overheads, so both sources fail the strict greater-than test and the fallback in driver_method.docx retains F&B overheads, the higher of the two. Stewarding is excluded: Group B adds 2 days to each side and one exclusion sets same_day to false. main_rules.xlsx, SMART!E31:G31, gives pri_force defaults empty/true/empty. other_rules.xlsx, SMART!D31:F31, gives department defaults 1/true/empty. The results are pri_force 1-2/false/1-2 and department 1-3/false/1-2. Comparisons use unrounded revenues.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "JSON/YAML (.json, .yaml, .yml)", + "dependencies": [] + }, + "criterion 50": { + "description": "States 'Nightclub'.params.pri_force.same_day as false (acceptable value false).", + "justification": "June is non-peak. In dependencies.png, the only incoming arrows to Nightclub are two dashed (non-peak) arrows into its bottom edge, one from Stewarding and one from F&B overheads; the F&B overheads arrow leaves the top of that box, rises past Kitchen and Restaurant and crosses the Kitchen to Meeting & Event F&B dashed arrow without a junction. March-May average adjusted revenue is 82,212.382576 for Nightclub, 74,764.049242 for Stewarding and 77,145.882576 for F&B overheads, so both sources fail the strict greater-than test and the fallback in driver_method.docx retains F&B overheads, the higher of the two. Stewarding is excluded: Group B adds 2 days to each side and one exclusion sets same_day to false. main_rules.xlsx, SMART!E31:G31, gives pri_force defaults empty/true/empty. other_rules.xlsx, SMART!D31:F31, gives department defaults 1/true/empty. The results are pri_force 1-2/false/1-2 and department 1-3/false/1-2. Comparisons use unrounded revenues.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "JSON/YAML (.json, .yaml, .yml)", + "dependencies": [] + }, + "criterion 51": { + "description": "States 'Nightclub'.params.pri_force.day_after as \"1-2\" (acceptable value \"1-2\").", + "justification": "June is non-peak. In dependencies.png, the only incoming arrows to Nightclub are two dashed (non-peak) arrows into its bottom edge, one from Stewarding and one from F&B overheads; the F&B overheads arrow leaves the top of that box, rises past Kitchen and Restaurant and crosses the Kitchen to Meeting & Event F&B dashed arrow without a junction. March-May average adjusted revenue is 82,212.382576 for Nightclub, 74,764.049242 for Stewarding and 77,145.882576 for F&B overheads, so both sources fail the strict greater-than test and the fallback in driver_method.docx retains F&B overheads, the higher of the two. Stewarding is excluded: Group B adds 2 days to each side and one exclusion sets same_day to false. main_rules.xlsx, SMART!E31:G31, gives pri_force defaults empty/true/empty. other_rules.xlsx, SMART!D31:F31, gives department defaults 1/true/empty. The results are pri_force 1-2/false/1-2 and department 1-3/false/1-2. Comparisons use unrounded revenues.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "JSON/YAML (.json, .yaml, .yml)", + "dependencies": [] + }, + "criterion 52": { + "description": "States 'Nightclub'.params.department.day_before as \"1-3\" (acceptable value \"1-3\").", + "justification": "June is non-peak. In dependencies.png, the only incoming arrows to Nightclub are two dashed (non-peak) arrows into its bottom edge, one from Stewarding and one from F&B overheads; the F&B overheads arrow leaves the top of that box, rises past Kitchen and Restaurant and crosses the Kitchen to Meeting & Event F&B dashed arrow without a junction. March-May average adjusted revenue is 82,212.382576 for Nightclub, 74,764.049242 for Stewarding and 77,145.882576 for F&B overheads, so both sources fail the strict greater-than test and the fallback in driver_method.docx retains F&B overheads, the higher of the two. Stewarding is excluded: Group B adds 2 days to each side and one exclusion sets same_day to false. main_rules.xlsx, SMART!E31:G31, gives pri_force defaults empty/true/empty. other_rules.xlsx, SMART!D31:F31, gives department defaults 1/true/empty. The results are pri_force 1-2/false/1-2 and department 1-3/false/1-2. Comparisons use unrounded revenues.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "JSON/YAML (.json, .yaml, .yml)", + "dependencies": [] + }, + "criterion 53": { + "description": "States 'Nightclub'.params.department.same_day as false (acceptable value false).", + "justification": "June is non-peak. In dependencies.png, the only incoming arrows to Nightclub are two dashed (non-peak) arrows into its bottom edge, one from Stewarding and one from F&B overheads; the F&B overheads arrow leaves the top of that box, rises past Kitchen and Restaurant and crosses the Kitchen to Meeting & Event F&B dashed arrow without a junction. March-May average adjusted revenue is 82,212.382576 for Nightclub, 74,764.049242 for Stewarding and 77,145.882576 for F&B overheads, so both sources fail the strict greater-than test and the fallback in driver_method.docx retains F&B overheads, the higher of the two. Stewarding is excluded: Group B adds 2 days to each side and one exclusion sets same_day to false. main_rules.xlsx, SMART!E31:G31, gives pri_force defaults empty/true/empty. other_rules.xlsx, SMART!D31:F31, gives department defaults 1/true/empty. The results are pri_force 1-2/false/1-2 and department 1-3/false/1-2. Comparisons use unrounded revenues.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "JSON/YAML (.json, .yaml, .yml)", + "dependencies": [] + }, + "criterion 54": { + "description": "States 'Nightclub'.params.department.day_after as \"1-2\" (acceptable value \"1-2\").", + "justification": "June is non-peak. In dependencies.png, the only incoming arrows to Nightclub are two dashed (non-peak) arrows into its bottom edge, one from Stewarding and one from F&B overheads; the F&B overheads arrow leaves the top of that box, rises past Kitchen and Restaurant and crosses the Kitchen to Meeting & Event F&B dashed arrow without a junction. March-May average adjusted revenue is 82,212.382576 for Nightclub, 74,764.049242 for Stewarding and 77,145.882576 for F&B overheads, so both sources fail the strict greater-than test and the fallback in driver_method.docx retains F&B overheads, the higher of the two. Stewarding is excluded: Group B adds 2 days to each side and one exclusion sets same_day to false. main_rules.xlsx, SMART!E31:G31, gives pri_force defaults empty/true/empty. other_rules.xlsx, SMART!D31:F31, gives department defaults 1/true/empty. The results are pri_force 1-2/false/1-2 and department 1-3/false/1-2. Comparisons use unrounded revenues.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "JSON/YAML (.json, .yaml, .yml)", + "dependencies": [] + }, + "criterion 55": { + "description": "States 'Restaurant'.dep_sources as the set [\"Bar\", \"Total food revenue\"] in any order.", + "justification": "", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 4, + "grading_target": "JSON/YAML (.json, .yaml, .yml)", + "dependencies": [] + }, + "criterion 56": { + "description": "States 'Restaurant'.params.pri_force.day_before as \"1-2\" (acceptable value \"1-2\").", + "justification": "", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "JSON/YAML (.json, .yaml, .yml)", + "dependencies": [] + }, + "criterion 57": { + "description": "States 'Restaurant'.params.pri_force.same_day as false (acceptable value false).", + "justification": "", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "JSON/YAML (.json, .yaml, .yml)", + "dependencies": [] + }, + "criterion 58": { + "description": "States 'Restaurant'.params.pri_force.day_after as \"1-2\" (acceptable value \"1-2\").", + "justification": "", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "JSON/YAML (.json, .yaml, .yml)", + "dependencies": [] + }, + "criterion 59": { + "description": "States 'Restaurant'.params.department.day_before as \"1-2\" (acceptable value \"1-2\").", + "justification": "", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "JSON/YAML (.json, .yaml, .yml)", + "dependencies": [] + }, + "criterion 60": { + "description": "States 'Restaurant'.params.department.same_day as false (acceptable value false).", + "justification": "", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "JSON/YAML (.json, .yaml, .yml)", + "dependencies": [] + }, + "criterion 61": { + "description": "States 'Restaurant'.params.department.day_after as \"1-2\" (acceptable value \"1-2\").", + "justification": "", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "JSON/YAML (.json, .yaml, .yml)", + "dependencies": [] + }, + "criterion 62": { + "description": "States 'Room Service'.dep_sources as the set [\"Breakfast\", \"Nightclub\", \"Restaurant\"] in any order.", + "justification": "June is non-peak. In dependencies.png, incoming arrows to Room Service are Breakfast, Nightclub and Restaurant in all seasons, plus a dotted (peak-only) arrow from Total food revenue that is excluded by season matching. Total food revenue is not a department and belongs to no group, so that exclusion adds no days and does not count toward the same_day parity. March-May average adjusted revenue is 67,347.215909 for Room Service, 74,000.549242 for Breakfast, 82,212.382576 for Nightclub and 67,705.715909 for Restaurant; all three department sources pass the strict greater-than test and are retained. main_rules.xlsx, SMART!E32:G32, and other_rules.xlsx, SMART!D32:F32, both give defaults empty/true/empty, so both parameters stay empty/true/empty. Comparisons use unrounded revenues.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 4, + "grading_target": "JSON/YAML (.json, .yaml, .yml)", + "dependencies": [] + }, + "criterion 63": { + "description": "States 'Room Service'.params.pri_force.day_before as \"\" (acceptable value \"\").", + "justification": "June is non-peak. In dependencies.png, incoming arrows to Room Service are Breakfast, Nightclub and Restaurant in all seasons, plus a dotted (peak-only) arrow from Total food revenue that is excluded by season matching. Total food revenue is not a department and belongs to no group, so that exclusion adds no days and does not count toward the same_day parity. March-May average adjusted revenue is 67,347.215909 for Room Service, 74,000.549242 for Breakfast, 82,212.382576 for Nightclub and 67,705.715909 for Restaurant; all three department sources pass the strict greater-than test and are retained. main_rules.xlsx, SMART!E32:G32, and other_rules.xlsx, SMART!D32:F32, both give defaults empty/true/empty, so both parameters stay empty/true/empty. Comparisons use unrounded revenues.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "JSON/YAML (.json, .yaml, .yml)", + "dependencies": [] + }, + "criterion 64": { + "description": "States 'Room Service'.params.pri_force.same_day as true (acceptable value true).", + "justification": "June is non-peak. In dependencies.png, incoming arrows to Room Service are Breakfast, Nightclub and Restaurant in all seasons, plus a dotted (peak-only) arrow from Total food revenue that is excluded by season matching. Total food revenue is not a department and belongs to no group, so that exclusion adds no days and does not count toward the same_day parity. March-May average adjusted revenue is 67,347.215909 for Room Service, 74,000.549242 for Breakfast, 82,212.382576 for Nightclub and 67,705.715909 for Restaurant; all three department sources pass the strict greater-than test and are retained. main_rules.xlsx, SMART!E32:G32, and other_rules.xlsx, SMART!D32:F32, both give defaults empty/true/empty, so both parameters stay empty/true/empty. Comparisons use unrounded revenues.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "JSON/YAML (.json, .yaml, .yml)", + "dependencies": [] + }, + "criterion 65": { + "description": "States 'Room Service'.params.pri_force.day_after as \"\" (acceptable value \"\").", + "justification": "June is non-peak. In dependencies.png, incoming arrows to Room Service are Breakfast, Nightclub and Restaurant in all seasons, plus a dotted (peak-only) arrow from Total food revenue that is excluded by season matching. Total food revenue is not a department and belongs to no group, so that exclusion adds no days and does not count toward the same_day parity. March-May average adjusted revenue is 67,347.215909 for Room Service, 74,000.549242 for Breakfast, 82,212.382576 for Nightclub and 67,705.715909 for Restaurant; all three department sources pass the strict greater-than test and are retained. main_rules.xlsx, SMART!E32:G32, and other_rules.xlsx, SMART!D32:F32, both give defaults empty/true/empty, so both parameters stay empty/true/empty. Comparisons use unrounded revenues.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "JSON/YAML (.json, .yaml, .yml)", + "dependencies": [] + }, + "criterion 66": { + "description": "States 'Room Service'.params.department.day_before as \"\" (acceptable value \"\").", + "justification": "June is non-peak. In dependencies.png, incoming arrows to Room Service are Breakfast, Nightclub and Restaurant in all seasons, plus a dotted (peak-only) arrow from Total food revenue that is excluded by season matching. Total food revenue is not a department and belongs to no group, so that exclusion adds no days and does not count toward the same_day parity. March-May average adjusted revenue is 67,347.215909 for Room Service, 74,000.549242 for Breakfast, 82,212.382576 for Nightclub and 67,705.715909 for Restaurant; all three department sources pass the strict greater-than test and are retained. main_rules.xlsx, SMART!E32:G32, and other_rules.xlsx, SMART!D32:F32, both give defaults empty/true/empty, so both parameters stay empty/true/empty. Comparisons use unrounded revenues.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "JSON/YAML (.json, .yaml, .yml)", + "dependencies": [] + }, + "criterion 67": { + "description": "States 'Room Service'.params.department.same_day as true (acceptable value true).", + "justification": "June is non-peak. In dependencies.png, incoming arrows to Room Service are Breakfast, Nightclub and Restaurant in all seasons, plus a dotted (peak-only) arrow from Total food revenue that is excluded by season matching. Total food revenue is not a department and belongs to no group, so that exclusion adds no days and does not count toward the same_day parity. March-May average adjusted revenue is 67,347.215909 for Room Service, 74,000.549242 for Breakfast, 82,212.382576 for Nightclub and 67,705.715909 for Restaurant; all three department sources pass the strict greater-than test and are retained. main_rules.xlsx, SMART!E32:G32, and other_rules.xlsx, SMART!D32:F32, both give defaults empty/true/empty, so both parameters stay empty/true/empty. Comparisons use unrounded revenues.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "JSON/YAML (.json, .yaml, .yml)", + "dependencies": [] + }, + "criterion 68": { + "description": "States 'Room Service'.params.department.day_after as \"\" (acceptable value \"\").", + "justification": "June is non-peak. In dependencies.png, incoming arrows to Room Service are Breakfast, Nightclub and Restaurant in all seasons, plus a dotted (peak-only) arrow from Total food revenue that is excluded by season matching. Total food revenue is not a department and belongs to no group, so that exclusion adds no days and does not count toward the same_day parity. March-May average adjusted revenue is 67,347.215909 for Room Service, 74,000.549242 for Breakfast, 82,212.382576 for Nightclub and 67,705.715909 for Restaurant; all three department sources pass the strict greater-than test and are retained. main_rules.xlsx, SMART!E32:G32, and other_rules.xlsx, SMART!D32:F32, both give defaults empty/true/empty, so both parameters stay empty/true/empty. Comparisons use unrounded revenues.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "JSON/YAML (.json, .yaml, .yml)", + "dependencies": [] + }, + "criterion 69": { + "description": "States 'Stewarding'.dep_sources as [\"Total food revenue\"] (acceptable value [\"Total food revenue\"]).", + "justification": "", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 4, + "grading_target": "JSON/YAML (.json, .yaml, .yml)", + "dependencies": [] + }, + "criterion 70": { + "description": "States 'Stewarding'.params.pri_force.day_before as \"1-11\" (acceptable value \"1-11\").", + "justification": "", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "JSON/YAML (.json, .yaml, .yml)", + "dependencies": [] + }, + "criterion 71": { + "description": "States 'Stewarding'.params.pri_force.same_day as true (acceptable value true).", + "justification": "", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "JSON/YAML (.json, .yaml, .yml)", + "dependencies": [] + }, + "criterion 72": { + "description": "States 'Stewarding'.params.pri_force.day_after as \"1-11\" (acceptable value \"1-11\").", + "justification": "", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "JSON/YAML (.json, .yaml, .yml)", + "dependencies": [] + }, + "criterion 73": { + "description": "States 'Stewarding'.params.department.day_before as \"1-12\" (acceptable value \"1-12\").", + "justification": "", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "JSON/YAML (.json, .yaml, .yml)", + "dependencies": [] + }, + "criterion 74": { + "description": "States 'Stewarding'.params.department.same_day as true (acceptable value true).", + "justification": "", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "JSON/YAML (.json, .yaml, .yml)", + "dependencies": [] + }, + "criterion 75": { + "description": "States 'Stewarding'.params.department.day_after as \"1-11\" (acceptable value \"1-11\").", + "justification": "", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "JSON/YAML (.json, .yaml, .yml)", + "dependencies": [] + }, + "criterion 76": { + "description": "Uses plain ASCII for every JSON string.", + "justification": "", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "JSON/YAML (.json, .yaml, .yml)", + "dependencies": [] + }, + "criterion 77": { + "description": "Includes month and departments as top-level keys.", + "justification": "driver_schema.docx, JSON structure, requires both keys but specifies no relative order for them. Department objects must still follow the alphabetical department order, and the prompt's explicit blank-line placement remains covered by existing criteria.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "JSON/YAML (.json, .yaml, .yml)", + "dependencies": [] + }, + "criterion 78": { + "description": "Lists exactly 10 entries in departments.", + "justification": "", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 5, + "grading_target": "JSON/YAML (.json, .yaml, .yml)", + "dependencies": [] + }, + "criterion 79": { + "description": "Uses the same ascending departments order for the ten top-level department keys.", + "justification": "", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "JSON/YAML (.json, .yaml, .yml)", + "dependencies": [] + }, + "criterion 80": { + "description": "Includes exactly dep_sources and params in every department object, in either order.", + "justification": "driver_schema.docx, department objects, requires these two keys without prescribing their order. The separate order requirement for pri_force and department inside params remains unchanged.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "JSON/YAML (.json, .yaml, .yml)", + "dependencies": [] + }, + "criterion 81": { + "description": "Includes exactly pri_force and department, in that order, in every params object.", + "justification": "", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "JSON/YAML (.json, .yaml, .yml)", + "dependencies": [] + }, + "criterion 82": { + "description": "Includes exactly day_before, same_day, and day_after in every parameter object, in any order.", + "justification": "driver_schema.docx, params, requires these three keys without saying in this order. The phrase in this order applies only to pri_force and department, which criterion 81 still checks.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "JSON/YAML (.json, .yaml, .yml)", + "dependencies": [] + }, + "criterion 83": { + "description": "Leaves exactly one blank line between the departments array and the first department object.", + "justification": "", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "JSON/YAML (.json, .yaml, .yml)", + "dependencies": [] + }, + "criterion 84": { + "description": "Leaves exactly one blank line between consecutive top-level department objects.", + "justification": "", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "JSON/YAML (.json, .yaml, .yml)", + "dependencies": [] + }, + "criterion 85": { + "description": "Places each top-level department object's opening brace on the line immediately below its department key.", + "justification": "", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "JSON/YAML (.json, .yaml, .yml)", + "dependencies": [] + } +} \ No newline at end of file diff --git a/tasks/task_fea07f327cfd4f4c91af0bf78da197d4/input/ZenAnalytics_Branding.xlsx b/tasks/task_fea07f327cfd4f4c91af0bf78da197d4/input/ZenAnalytics_Branding.xlsx new file mode 100644 index 0000000000000000000000000000000000000000..f18d41e1b70fcf5bfd0b217f193b8cab48ae230a --- /dev/null +++ b/tasks/task_fea07f327cfd4f4c91af0bf78da197d4/input/ZenAnalytics_Branding.xlsx @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9183dd423e3b868568dac2f0e59f518ee62468d55048681c93e249e755f0df61 +size 10527 diff --git a/tasks/task_fea07f327cfd4f4c91af0bf78da197d4/input/headcount_1jul2025.csv b/tasks/task_fea07f327cfd4f4c91af0bf78da197d4/input/headcount_1jul2025.csv new file mode 100644 index 0000000000000000000000000000000000000000..1dcc63515959b65d051c9dc6cddf2cc1b70a73bb --- /dev/null +++ b/tasks/task_fea07f327cfd4f4c91af0bf78da197d4/input/headcount_1jul2025.csv @@ -0,0 +1,16 @@ +code,department,employees_1jul2025 +CMP,Compliance,140 +CUS,Customer Care,210 +CXD,Customer Experience Design,95 +DEN,Data Engineering,160 +FAC,Facilities,130 +FIN,Finance Operations,155 +GRW,Growth Analytics,185 +LEG,Legal Operations,120 +PAY,Partner Accounts,128 +PRC,Procurement,165 +PSV,People Services,175 +RET,Retail Operations,340 +SLS,Sales Operations,150 +SUP,Supply Chain,220 +TRS,Treasury & Capital Markets,75 diff --git a/tasks/task_fea07f327cfd4f4c91af0bf78da197d4/input/involuntary_leaves_FY26.png b/tasks/task_fea07f327cfd4f4c91af0bf78da197d4/input/involuntary_leaves_FY26.png new file mode 100644 index 0000000000000000000000000000000000000000..5cb73a27a3f0ded397ec32b773ea3b66b7d17bb2 --- /dev/null +++ b/tasks/task_fea07f327cfd4f4c91af0bf78da197d4/input/involuntary_leaves_FY26.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b901c0d2cd77c4122a61a6df36dcd4c7d46a8f12f7936a32fbf0e512863a5e97 +size 1609703 diff --git a/tasks/task_fea07f327cfd4f4c91af0bf78da197d4/input/voluntary_leaves_FY26.png b/tasks/task_fea07f327cfd4f4c91af0bf78da197d4/input/voluntary_leaves_FY26.png new file mode 100644 index 0000000000000000000000000000000000000000..74a163c74bba53cd1da5840b8e37618d0a696e83 --- /dev/null +++ b/tasks/task_fea07f327cfd4f4c91af0bf78da197d4/input/voluntary_leaves_FY26.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:df46a8cc028f8c8e6e5284b59a357cab114d6fa5d8e31ac926066871911469eb +size 2397982 diff --git a/tasks/task_fea07f327cfd4f4c91af0bf78da197d4/input/workforce_staffing_rules.pdf b/tasks/task_fea07f327cfd4f4c91af0bf78da197d4/input/workforce_staffing_rules.pdf new file mode 100644 index 0000000000000000000000000000000000000000..317c3051d9d6eaa07f3a56b8b6d8f563b4871d69 --- /dev/null +++ b/tasks/task_fea07f327cfd4f4c91af0bf78da197d4/input/workforce_staffing_rules.pdf @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:045e826d78b59486ffb598c82916139d910966145fe50726f2b85f3f4a8552df +size 339153 diff --git a/tasks/task_fea07f327cfd4f4c91af0bf78da197d4/input/zenlogo.jpg b/tasks/task_fea07f327cfd4f4c91af0bf78da197d4/input/zenlogo.jpg new file mode 100644 index 0000000000000000000000000000000000000000..99fdf5b55621b5dea8014f052b77b37b7b9fbf83 --- /dev/null +++ b/tasks/task_fea07f327cfd4f4c91af0bf78da197d4/input/zenlogo.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0990086804b5f460475297315429ff5f2e94209aa706af4f2b7d01a3b30fe451 +size 1709720 diff --git a/tasks/task_fea07f327cfd4f4c91af0bf78da197d4/metadata.json b/tasks/task_fea07f327cfd4f4c91af0bf78da197d4/metadata.json new file mode 100644 index 0000000000000000000000000000000000000000..11c0af908101413222acd0ede35d3cc07a524cee --- /dev/null +++ b/tasks/task_fea07f327cfd4f4c91af0bf78da197d4/metadata.json @@ -0,0 +1,12 @@ +{ + "TaskID": "task_fea07f327cfd4f4c91af0bf78da197d4", + "Vertical": "Business", + "Domain": "Data Science", + "Role": "HR analyst", + "Task Goal": "Conduct a department staffing review for a generative AI transition and report it in a workbook.", + "Prompt": "Conduct the Fiscal Year 2026 (FY26) department staffing review for the generative artificial intelligence (GenAI) transition cycle and produce a single Excel workbook named department_staffing_review.xlsx as the only output. Follow the styling and formatting conventions in the ZenAnalytics branding template.", + "Input_files": "ZenAnalytics_Branding.xlsx, headcount_1jul2025.csv, involuntary_leaves_FY26.png, voluntary_leaves_FY26.png, workforce_staffing_rules.pdf, zenlogo.jpg", + "All Task Files": "tasks/task_fea07f327cfd4f4c91af0bf78da197d4/input/", + "Rubric Criteria": "tasks/task_fea07f327cfd4f4c91af0bf78da197d4/rubrics.json", + "Economic Rationale": "This task reduces the manual effort needed to trace quarterly department transfers and identify departments for staffing review." +} diff --git a/tasks/task_fea07f327cfd4f4c91af0bf78da197d4/rubrics.json b/tasks/task_fea07f327cfd4f4c91af0bf78da197d4/rubrics.json new file mode 100644 index 0000000000000000000000000000000000000000..b003b24301324aa8adc4b358b135a7337700c162 --- /dev/null +++ b/tasks/task_fea07f327cfd4f4c91af0bf78da197d4/rubrics.json @@ -0,0 +1,812 @@ +{ + "criterion 1": { + "description": "Outputs an Excel (.xlsx) file.", + "justification": "Source: Prompt and workforce_staffing_rules.pdf Section 6 (File): produce a single Excel workbook. Passes when the deliverable is an .xlsx file that opens as a valid workbook.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Spreadsheets (.xlsx, .xls, .xlsm, .ods)", + "dependencies": [] + }, + "criterion 2": { + "description": "Names the output department_staffing_review.xlsx.", + "justification": "Source: Prompt and workforce_staffing_rules.pdf Section 6 (File): the workbook is named department_staffing_review.xlsx. Exact filename match; any other name or extension fails.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Spreadsheets (.xlsx, .xls, .xlsm, .ods)", + "dependencies": [] + }, + "criterion 3": { + "description": "Includes exactly two sheets named department_reads and summary, in that order.", + "justification": "Source: workforce_staffing_rules.pdf Section 6 (Sheets): exactly two sheets, in this order: department_reads, summary. Sheet names must match exactly; a missing, extra, renamed or reordered sheet fails.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Spreadsheets (.xlsx, .xls, .xlsm, .ods)", + "dependencies": [] + }, + "criterion 4": { + "description": "Displays the supplied ZenAnalytics logo on the department_reads worksheet, preserving its original appearance and proportions.", + "justification": "Source: workforce_staffing_rules.pdf Section 6 (Format): only the first sheet, department_reads, carries the company logo, zenlogo.jpg, placed right next to the table in row 1, where template sheet 1 reserves it (its Image Placeholder box); the summary sheet has no logo.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Spreadsheets (.xlsx, .xls, .xlsm, .ods)", + "dependencies": [] + }, + "criterion 5": { + "description": "Positions the logo within the designated image-placeholder area of the department_reads worksheet, without overlapping any table content.", + "justification": "Source: workforce_staffing_rules.pdf Section 6 (Format): only the first sheet, department_reads, carries the company logo, zenlogo.jpg, placed right next to the table in row 1, where template sheet 1 reserves it (its Image Placeholder box); the summary sheet has no logo.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Spreadsheets (.xlsx, .xls, .xlsm, .ods)", + "dependencies": [] + }, + "criterion 6": { + "description": "Keeps the summary worksheet free of the ZenAnalytics logo.\n\n", + "justification": "Source: workforce_staffing_rules.pdf Section 6 (Format): only the first sheet, department_reads, carries the company logo, zenlogo.jpg, placed right next to the table in row 1, where template sheet 1 reserves it (its Image Placeholder box); the summary sheet has no logo.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Spreadsheets (.xlsx, .xls, .xlsm, .ods)", + "dependencies": [] + }, + "criterion 7": { + "description": "Places a sheet title in cell A1 of the department_reads sheet, merged across A1:E1.", + "justification": "Source: workforce_staffing_rules.pdf Section 6 (Format) assigns template sheet 1 to department_reads. ZenAnalytics_Branding.xlsx, Sheet_Title-1, places its title at A1 and merges A1:E1. This criterion checks title placement and merge geometry. C9 checks the title and header fill color.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Spreadsheets (.xlsx, .xls, .xlsm, .ods)", + "dependencies": [] + }, + "criterion 8": { + "description": "Places a sheet title in cell A1 of the summary sheet, merged across A1:B1 or A1:E1.", + "justification": "Source: workforce_staffing_rules.pdf Section 6 (Format) assigns template sheet 2 to summary. ZenAnalytics_Branding.xlsx, Sheet_Title-2, merges its title across A1:E1. The required summary table has two populated columns, but the protocol does not require narrowing the title. Retaining A1:E1 or adapting the title to A1:B1 both pass. C80 checks the two populated table columns. C77 checks the title and header fill color.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Spreadsheets (.xlsx, .xls, .xlsm, .ods)", + "dependencies": [] + }, + "criterion 9": { + "description": "Fills the title cell A1 and header cells A2:E2 of the department_reads sheet with #465D92.", + "justification": "Source: workforce_staffing_rules.pdf Section 6 (Format) requires the styling of ZenAnalytics_Branding.xlsx, Sheet_Title-1. Its title at A1, merged A1:E1, and header cells A2:E2 use solid fill #465D92. This criterion checks the effective native fill for both title and headers. It does not require a particular storage method for a valid native table style.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 4, + "grading_target": "Spreadsheets (.xlsx, .xls, .xlsm, .ods)", + "dependencies": [] + }, + "criterion 10": { + "description": "Uses font Montserrat for the title and header rows of both worksheets.", + "justification": "Source: workforce_staffing_rules.pdf Section 6 (Format) assigns the corresponding branding-template sheet to each output sheet. ZenAnalytics_Branding.xlsx, Sheet_Title-1 and Sheet_Title-2, use Montserrat for title cell A1 and every header cell in row 2. Applies to A1 and A2:E2 on department_reads, and A1 and A2:B2 on summary. This named brand typeface is a Branding requirement.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 4, + "grading_target": "Spreadsheets (.xlsx, .xls, .xlsm, .ods)", + "dependencies": [] + }, + "criterion 11": { + "description": "Uses font Roboto for all table body cells of both worksheets.", + "justification": "Source: workforce_staffing_rules.pdf Section 6 (Format) assigns the corresponding branding-template sheet to each output sheet. ZenAnalytics_Branding.xlsx, Sheet_Title-1 and Sheet_Title-2, use Roboto for table body cells. Applies to department_reads!A3:E17 and summary!A3:B5. This named brand typeface is a Branding requirement.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 4, + "grading_target": "Spreadsheets (.xlsx, .xls, .xlsm, .ods)", + "dependencies": [] + }, + "criterion 12": { + "description": "Displays exactly five populated table columns with the headers \"DEPARTMENT_CODE\", \"LEAST_FEEDER_1\", \"LEAST_FEEDER_2\", \"MOST_FEEDER_1\" and \"MOST_FEEDER_2\" in the header row of the \"department_reads\" sheet, in that order, and no additional populated table column (headers acceptable: case-insensitive).", + "justification": "Source: workforce_staffing_rules.pdf Section 6 (department_reads) fixes the columns as department_code, least_feeder_1, least_feeder_2, most_feeder_1, most_feeder_2; ZenAnalytics_Branding.xlsx, sheet 1, row 2 (the table header row beneath the row-1 title) writes headers in capitals. Expected, in order: DEPARTMENT_CODE, LEAST_FEEDER_1, LEAST_FEEDER_2, MOST_FEEDER_1, MOST_FEEDER_2.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Spreadsheets (.xlsx, .xls, .xlsm, .ods)", + "dependencies": [] + }, + "criterion 13": { + "description": "Includes in the department_reads sheet the sorted list of departments CMP, CUS, CXD, DEN, FAC, FIN, GRW, LEG, PAY, PRC, PSV, RET, SLS, SUP, TRS, exactly once each, and no other department rows.", + "justification": "Source: workforce_staffing_rules.pdf Section 6 (department_reads): exactly fifteen rows, one per rostered department, sorted ascending by department_code; Section 1 roster. A missing, extra, duplicated or out-of-order row fails.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Spreadsheets (.xlsx, .xls, .xlsm, .ods)", + "dependencies": [] + }, + "criterion 14": { + "description": "Alternates the body-row backgrounds of the department_reads sheet between #F9F8FF and #FFFFFF, starting with #F9F8FF on the first body row (row 3).", + "justification": "Source: workforce_staffing_rules.pdf Section 6 (Format): each output sheet takes the layout and styling of the template sheet in the same position (department_reads follows template sheet 1, Sheet_Title-1; summary follows template sheet 2, Sheet_Title-2). Template Sheet_Title-1 formats its table A2:E52 with table style Sheet_Title-1-style, row stripes on: firstRowStripe #F9F8FF, secondRowStripe #FFFFFF. Rows 3, 5, 7 ... are #F9F8FF and rows 4, 6, 8 ... are #FFFFFF across all 15 body rows. Banding applied by explicit cell fills or by an Excel table that uses a table style with these stripe colours both pass; a white band may be stored as #FFFFFF or as no fill. Exact hex match on the light band.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Spreadsheets (.xlsx, .xls, .xlsm, .ods)", + "dependencies": [] + }, + "criterion 15": { + "description": "Applies thin borders colored #757780 on all four sides of every table cell (header and body) in the department_reads sheet.", + "justification": "Source: workforce_staffing_rules.pdf Section 6 (Format): each output sheet takes the layout and styling of the template sheet in the same position (department_reads follows template sheet 1, Sheet_Title-1; summary follows template sheet 2, Sheet_Title-2). Template Sheet_Title-1: title, header and body cells all carry thin borders, colour #757780, on all four sides. Applies to A2:E17 of department_reads.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Spreadsheets (.xlsx, .xls, .xlsm, .ods)", + "dependencies": [] + }, + "criterion 16": { + "description": "Applies thin borders colored #6E7979 on all four sides of every table cell (header and body) in the summary sheet.", + "justification": "Source: workforce_staffing_rules.pdf Section 6 (Format): each output sheet takes the layout and styling of the template sheet in the same position (department_reads follows template sheet 1, Sheet_Title-1; summary follows template sheet 2, Sheet_Title-2). Template Sheet_Title-2: title, header and body cells all carry thin borders, colour #6E7979, on all four sides. Applies to A2:B5 of summary.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Spreadsheets (.xlsx, .xls, .xlsm, .ods)", + "dependencies": [] + }, + "criterion 17": { + "description": "States least_feeder_1 for CMP in the department_reads sheet as \"DEN: 1\" (acceptable value is \"DEN: 1\"; spacing around the colon may vary).", + "justification": "Source: voluntary_leaves_FY26.png and involuntary_leaves_FY26.png (leave bands into CMP at all three transitions, each traced back to the department and people count at its start), headcount_1jul2025.csv. Rule: workforce_staffing_rules.pdf Section 3 S2 and Section 4. least_feeder_1: feeders of CMP, leaves over the year (voluntary + involuntary), fewest first: DEN 1 (employees 1 Jul 2025: 160); SLS 1 (employees 1 Jul 2025: 150); FAC 1 (employees 1 Jul 2025: 130); LEG 1 (employees 1 Jul 2025: 120). Tie-break needed (more employees on 1 July 2025 first, headcount_1jul2025.csv): DEN, SLS, FAC, LEG. DEN -> CMP leave bands: Q4 2025 -> Q1 2026: 1 voluntary, 0 involuntary.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Spreadsheets (.xlsx, .xls, .xlsm, .ods)", + "dependencies": [] + }, + "criterion 18": { + "description": "States least_feeder_1 for CUS in the department_reads sheet as \"PAY: 1\" (acceptable value is \"PAY: 1\"; spacing around the colon may vary).", + "justification": "Source: voluntary_leaves_FY26.png and involuntary_leaves_FY26.png (leave bands into CUS at all three transitions, each traced back to the department and people count at its start), headcount_1jul2025.csv. Rule: workforce_staffing_rules.pdf Section 3 S2 and Section 4. least_feeder_1: feeders of CUS, leaves over the year (voluntary + involuntary), fewest first: PAY 1 (employees 1 Jul 2025: 128); CMP 2 (employees 1 Jul 2025: 140); FAC 2 (employees 1 Jul 2025: 130); LEG 2 (employees 1 Jul 2025: 120); TRS 2 (employees 1 Jul 2025: 75). PAY -> CUS leave bands: Q3 2025 -> Q4 2025: 1 voluntary, 0 involuntary.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Spreadsheets (.xlsx, .xls, .xlsm, .ods)", + "dependencies": [] + }, + "criterion 19": { + "description": "States least_feeder_1 for CXD in the department_reads sheet as \"RET: 1\" (acceptable value is \"RET: 1\"; spacing around the colon may vary).", + "justification": "Source: voluntary_leaves_FY26.png and involuntary_leaves_FY26.png (leave bands into CXD at all three transitions, each traced back to the department and people count at its start), headcount_1jul2025.csv. Rule: workforce_staffing_rules.pdf Section 3 S2 and Section 4. least_feeder_1: feeders of CXD, leaves over the year (voluntary + involuntary), fewest first: RET 1 (employees 1 Jul 2025: 340); SUP 1 (employees 1 Jul 2025: 220); CUS 1 (employees 1 Jul 2025: 210); GRW 1 (employees 1 Jul 2025: 185); PSV 1 (employees 1 Jul 2025: 175); DEN 1 (employees 1 Jul 2025: 160); SLS 1 (employees 1 Jul 2025: 150); CMP 1 (employees 1 Jul 2025: 140); PAY 1 (employees 1 Jul 2025: 128); LEG 1 (employees 1 Jul 2025: 120). Tie-break needed (more employees on 1 July 2025 first, headcount_1jul2025.csv): RET, SUP, CUS, GRW, PSV, DEN, SLS, CMP, PAY, LEG. RET -> CXD leave bands: Q1 2026 -> Q2 2026: 1 voluntary, 0 involuntary.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Spreadsheets (.xlsx, .xls, .xlsm, .ods)", + "dependencies": [] + }, + "criterion 20": { + "description": "States least_feeder_1 for DEN in the department_reads sheet as \"PAY: 1\" (acceptable value is \"PAY: 1\"; spacing around the colon may vary).", + "justification": "Source: voluntary_leaves_FY26.png and involuntary_leaves_FY26.png (leave bands into DEN at all three transitions, each traced back to the department and people count at its start), headcount_1jul2025.csv. Rule: workforce_staffing_rules.pdf Section 3 S2 and Section 4. least_feeder_1: feeders of DEN, leaves over the year (voluntary + involuntary), fewest first: PAY 1 (employees 1 Jul 2025: 128); CMP 2 (employees 1 Jul 2025: 140). PAY -> DEN leave bands: Q1 2026 -> Q2 2026: 0 voluntary, 1 involuntary.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Spreadsheets (.xlsx, .xls, .xlsm, .ods)", + "dependencies": [] + }, + "criterion 21": { + "description": "States least_feeder_1 for FAC in the department_reads sheet as \"CUS: 1\" (acceptable value is \"CUS: 1\"; spacing around the colon may vary).", + "justification": "Source: voluntary_leaves_FY26.png and involuntary_leaves_FY26.png (leave bands into FAC at all three transitions, each traced back to the department and people count at its start), headcount_1jul2025.csv. Rule: workforce_staffing_rules.pdf Section 3 S2 and Section 4. least_feeder_1: feeders of FAC, leaves over the year (voluntary + involuntary), fewest first: CUS 1 (employees 1 Jul 2025: 210); PSV 1 (employees 1 Jul 2025: 175); DEN 1 (employees 1 Jul 2025: 160); SLS 1 (employees 1 Jul 2025: 150); PAY 1 (employees 1 Jul 2025: 128); CXD 1 (employees 1 Jul 2025: 95). Tie-break needed (more employees on 1 July 2025 first, headcount_1jul2025.csv): CUS, PSV, DEN, SLS, PAY, CXD. CUS -> FAC leave bands: Q1 2026 -> Q2 2026: 1 voluntary, 0 involuntary.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Spreadsheets (.xlsx, .xls, .xlsm, .ods)", + "dependencies": [] + }, + "criterion 22": { + "description": "States least_feeder_1 for FIN in the department_reads sheet as \"LEG: 1\" (acceptable value is \"LEG: 1\"; spacing around the colon may vary).", + "justification": "Source: voluntary_leaves_FY26.png and involuntary_leaves_FY26.png (leave bands into FIN at all three transitions, each traced back to the department and people count at its start), headcount_1jul2025.csv. Rule: workforce_staffing_rules.pdf Section 3 S2 and Section 4. least_feeder_1: feeders of FIN, leaves over the year (voluntary + involuntary), fewest first: LEG 1 (employees 1 Jul 2025: 120); SUP 2 (employees 1 Jul 2025: 220). LEG -> FIN leave bands: Q3 2025 -> Q4 2025: 0 voluntary, 1 involuntary.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Spreadsheets (.xlsx, .xls, .xlsm, .ods)", + "dependencies": [] + }, + "criterion 23": { + "description": "States least_feeder_1 for GRW in the department_reads sheet as \"RET: 1\" (acceptable value is \"RET: 1\"; spacing around the colon may vary).", + "justification": "Source: voluntary_leaves_FY26.png and involuntary_leaves_FY26.png (leave bands into GRW at all three transitions, each traced back to the department and people count at its start), headcount_1jul2025.csv. Rule: workforce_staffing_rules.pdf Section 3 S2 and Section 4. least_feeder_1: feeders of GRW, leaves over the year (voluntary + involuntary), fewest first: RET 1 (employees 1 Jul 2025: 340); FAC 1 (employees 1 Jul 2025: 130); LEG 1 (employees 1 Jul 2025: 120). Tie-break needed (more employees on 1 July 2025 first, headcount_1jul2025.csv): RET, FAC, LEG. RET -> GRW leave bands: Q1 2026 -> Q2 2026: 1 voluntary, 0 involuntary.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Spreadsheets (.xlsx, .xls, .xlsm, .ods)", + "dependencies": [] + }, + "criterion 24": { + "description": "States least_feeder_1 for LEG in the department_reads sheet as \"SUP: 1\" (acceptable value is \"SUP: 1\"; spacing around the colon may vary).", + "justification": "Source: voluntary_leaves_FY26.png and involuntary_leaves_FY26.png (leave bands into LEG at all three transitions, each traced back to the department and people count at its start), headcount_1jul2025.csv. Rule: workforce_staffing_rules.pdf Section 3 S2 and Section 4. least_feeder_1: feeders of LEG, leaves over the year (voluntary + involuntary), fewest first: SUP 1 (employees 1 Jul 2025: 220); CUS 1 (employees 1 Jul 2025: 210); PSV 1 (employees 1 Jul 2025: 175); SLS 1 (employees 1 Jul 2025: 150); CMP 1 (employees 1 Jul 2025: 140); FAC 1 (employees 1 Jul 2025: 130); CXD 1 (employees 1 Jul 2025: 95); TRS 1 (employees 1 Jul 2025: 75). Tie-break needed (more employees on 1 July 2025 first, headcount_1jul2025.csv): SUP, CUS, PSV, SLS, CMP, FAC, CXD, TRS. SUP -> LEG leave bands: Q1 2026 -> Q2 2026: 1 voluntary, 0 involuntary.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Spreadsheets (.xlsx, .xls, .xlsm, .ods)", + "dependencies": [] + }, + "criterion 25": { + "description": "States least_feeder_1 for PAY in the department_reads sheet as \"RET: 1\" (acceptable value is \"RET: 1\"; spacing around the colon may vary).", + "justification": "Source: voluntary_leaves_FY26.png and involuntary_leaves_FY26.png (leave bands into PAY at all three transitions, each traced back to the department and people count at its start), headcount_1jul2025.csv. Rule: workforce_staffing_rules.pdf Section 3 S2 and Section 4. least_feeder_1: feeders of PAY, leaves over the year (voluntary + involuntary), fewest first: RET 1 (employees 1 Jul 2025: 340); PSV 1 (employees 1 Jul 2025: 175); DEN 1 (employees 1 Jul 2025: 160); CMP 1 (employees 1 Jul 2025: 140). Tie-break needed (more employees on 1 July 2025 first, headcount_1jul2025.csv): RET, PSV, DEN, CMP. RET -> PAY leave bands: Q1 2026 -> Q2 2026: 0 voluntary, 1 involuntary.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Spreadsheets (.xlsx, .xls, .xlsm, .ods)", + "dependencies": [] + }, + "criterion 26": { + "description": "States least_feeder_1 for PRC in the department_reads sheet as \"PSV: 1\" (acceptable value is \"PSV: 1\"; spacing around the colon may vary).", + "justification": "Source: voluntary_leaves_FY26.png and involuntary_leaves_FY26.png (leave bands into PRC at all three transitions, each traced back to the department and people count at its start), headcount_1jul2025.csv. Rule: workforce_staffing_rules.pdf Section 3 S2 and Section 4. least_feeder_1: feeders of PRC, leaves over the year (voluntary + involuntary), fewest first: PSV 1 (employees 1 Jul 2025: 175); PAY 1 (employees 1 Jul 2025: 128); LEG 1 (employees 1 Jul 2025: 120); CXD 1 (employees 1 Jul 2025: 95). Tie-break needed (more employees on 1 July 2025 first, headcount_1jul2025.csv): PSV, PAY, LEG, CXD. PSV -> PRC leave bands: Q4 2025 -> Q1 2026: 1 voluntary, 0 involuntary.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Spreadsheets (.xlsx, .xls, .xlsm, .ods)", + "dependencies": [] + }, + "criterion 27": { + "description": "States least_feeder_1 for PSV in the department_reads sheet as \"TRS: 1\" (acceptable value is \"TRS: 1\"; spacing around the colon may vary).", + "justification": "Source: voluntary_leaves_FY26.png and involuntary_leaves_FY26.png (leave bands into PSV at all three transitions, each traced back to the department and people count at its start), headcount_1jul2025.csv. Rule: workforce_staffing_rules.pdf Section 3 S2 and Section 4. least_feeder_1: feeders of PSV, leaves over the year (voluntary + involuntary), fewest first: TRS 1 (employees 1 Jul 2025: 75); PRC 2 (employees 1 Jul 2025: 165); DEN 2 (employees 1 Jul 2025: 160); CXD 2 (employees 1 Jul 2025: 95). TRS -> PSV leave bands: Q1 2026 -> Q2 2026: 1 voluntary, 0 involuntary.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Spreadsheets (.xlsx, .xls, .xlsm, .ods)", + "dependencies": [] + }, + "criterion 28": { + "description": "States least_feeder_1 for RET in the department_reads sheet as \"LEG: 1\" (acceptable value is \"LEG: 1\"; spacing around the colon may vary).", + "justification": "Source: voluntary_leaves_FY26.png and involuntary_leaves_FY26.png (leave bands into RET at all three transitions, each traced back to the department and people count at its start), headcount_1jul2025.csv. Rule: workforce_staffing_rules.pdf Section 3 S2 and Section 4. least_feeder_1: feeders of RET, leaves over the year (voluntary + involuntary), fewest first: LEG 1 (employees 1 Jul 2025: 120); TRS 1 (employees 1 Jul 2025: 75). Tie-break needed (more employees on 1 July 2025 first, headcount_1jul2025.csv): LEG, TRS. LEG -> RET leave bands: Q3 2025 -> Q4 2025: 1 voluntary, 0 involuntary.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Spreadsheets (.xlsx, .xls, .xlsm, .ods)", + "dependencies": [] + }, + "criterion 29": { + "description": "States least_feeder_1 for SLS in the department_reads sheet as \"CMP: 1\" (acceptable value is \"CMP: 1\"; spacing around the colon may vary).", + "justification": "Source: voluntary_leaves_FY26.png and involuntary_leaves_FY26.png (leave bands into SLS at all three transitions, each traced back to the department and people count at its start), headcount_1jul2025.csv. Rule: workforce_staffing_rules.pdf Section 3 S2 and Section 4. least_feeder_1: feeders of SLS, leaves over the year (voluntary + involuntary), fewest first: CMP 1 (employees 1 Jul 2025: 140); PAY 1 (employees 1 Jul 2025: 128). Tie-break needed (more employees on 1 July 2025 first, headcount_1jul2025.csv): CMP, PAY. CMP -> SLS leave bands: Q3 2025 -> Q4 2025: 0 voluntary, 1 involuntary.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Spreadsheets (.xlsx, .xls, .xlsm, .ods)", + "dependencies": [] + }, + "criterion 30": { + "description": "States least_feeder_1 for SUP in the department_reads sheet as \"SLS: 1\" (acceptable value is \"SLS: 1\"; spacing around the colon may vary).", + "justification": "Source: voluntary_leaves_FY26.png and involuntary_leaves_FY26.png (leave bands into SUP at all three transitions, each traced back to the department and people count at its start), headcount_1jul2025.csv. Rule: workforce_staffing_rules.pdf Section 3 S2 and Section 4. least_feeder_1: feeders of SUP, leaves over the year (voluntary + involuntary), fewest first: SLS 1 (employees 1 Jul 2025: 150); CMP 1 (employees 1 Jul 2025: 140); PAY 1 (employees 1 Jul 2025: 128); LEG 1 (employees 1 Jul 2025: 120). Tie-break needed (more employees on 1 July 2025 first, headcount_1jul2025.csv): SLS, CMP, PAY, LEG. SLS -> SUP leave bands: Q4 2025 -> Q1 2026: 1 voluntary, 0 involuntary.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Spreadsheets (.xlsx, .xls, .xlsm, .ods)", + "dependencies": [] + }, + "criterion 31": { + "description": "States least_feeder_1 for TRS in the department_reads sheet as \"FIN: 1\" (acceptable value is \"FIN: 1\"; spacing around the colon may vary).", + "justification": "Source: voluntary_leaves_FY26.png and involuntary_leaves_FY26.png (leave bands into TRS at all three transitions, each traced back to the department and people count at its start), headcount_1jul2025.csv. Rule: workforce_staffing_rules.pdf Section 3 S2 and Section 4. least_feeder_1: feeders of TRS, leaves over the year (voluntary + involuntary), fewest first: FIN 1 (employees 1 Jul 2025: 155); LEG 2 (employees 1 Jul 2025: 120). FIN -> TRS leave bands: Q1 2026 -> Q2 2026: 0 voluntary, 1 involuntary.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Spreadsheets (.xlsx, .xls, .xlsm, .ods)", + "dependencies": [] + }, + "criterion 32": { + "description": "States least_feeder_2 for CMP in the department_reads sheet as \"SLS: 1\" (acceptable value is \"SLS: 1\"; spacing around the colon may vary).", + "justification": "Source: voluntary_leaves_FY26.png and involuntary_leaves_FY26.png (leave bands into CMP at all three transitions, each traced back to the department and people count at its start), headcount_1jul2025.csv. Rule: workforce_staffing_rules.pdf Section 3 S2 and Section 4. least_feeder_2: feeders of CMP, leaves over the year (voluntary + involuntary), fewest first: DEN 1 (employees 1 Jul 2025: 160); SLS 1 (employees 1 Jul 2025: 150); FAC 1 (employees 1 Jul 2025: 130); LEG 1 (employees 1 Jul 2025: 120). Tie-break needed (more employees on 1 July 2025 first, headcount_1jul2025.csv): DEN, SLS, FAC, LEG. SLS -> CMP leave bands: Q3 2025 -> Q4 2025: 1 voluntary, 0 involuntary.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Spreadsheets (.xlsx, .xls, .xlsm, .ods)", + "dependencies": [] + }, + "criterion 33": { + "description": "States least_feeder_2 for CUS in the department_reads sheet as \"CMP: 2\" (acceptable value is \"CMP: 2\"; spacing around the colon may vary).", + "justification": "Source: voluntary_leaves_FY26.png and involuntary_leaves_FY26.png (leave bands into CUS at all three transitions, each traced back to the department and people count at its start), headcount_1jul2025.csv. Rule: workforce_staffing_rules.pdf Section 3 S2 and Section 4. least_feeder_2: feeders of CUS, leaves over the year (voluntary + involuntary), fewest first: PAY 1 (employees 1 Jul 2025: 128); CMP 2 (employees 1 Jul 2025: 140); FAC 2 (employees 1 Jul 2025: 130); LEG 2 (employees 1 Jul 2025: 120); TRS 2 (employees 1 Jul 2025: 75). Tie-break needed (more employees on 1 July 2025 first, headcount_1jul2025.csv): CMP, FAC, LEG, TRS. CMP -> CUS leave bands: Q3 2025 -> Q4 2025: 0 voluntary, 1 involuntary; Q1 2026 -> Q2 2026: 1 voluntary, 0 involuntary.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Spreadsheets (.xlsx, .xls, .xlsm, .ods)", + "dependencies": [] + }, + "criterion 34": { + "description": "States least_feeder_2 for CXD in the department_reads sheet as \"SUP: 1\" (acceptable value is \"SUP: 1\"; spacing around the colon may vary).", + "justification": "Source: voluntary_leaves_FY26.png and involuntary_leaves_FY26.png (leave bands into CXD at all three transitions, each traced back to the department and people count at its start), headcount_1jul2025.csv. Rule: workforce_staffing_rules.pdf Section 3 S2 and Section 4. least_feeder_2: feeders of CXD, leaves over the year (voluntary + involuntary), fewest first: RET 1 (employees 1 Jul 2025: 340); SUP 1 (employees 1 Jul 2025: 220); CUS 1 (employees 1 Jul 2025: 210); GRW 1 (employees 1 Jul 2025: 185); PSV 1 (employees 1 Jul 2025: 175); DEN 1 (employees 1 Jul 2025: 160); SLS 1 (employees 1 Jul 2025: 150); CMP 1 (employees 1 Jul 2025: 140); PAY 1 (employees 1 Jul 2025: 128); LEG 1 (employees 1 Jul 2025: 120). Tie-break needed (more employees on 1 July 2025 first, headcount_1jul2025.csv): RET, SUP, CUS, GRW, PSV, DEN, SLS, CMP, PAY, LEG. SUP -> CXD leave bands: Q4 2025 -> Q1 2026: 0 voluntary, 1 involuntary.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Spreadsheets (.xlsx, .xls, .xlsm, .ods)", + "dependencies": [] + }, + "criterion 35": { + "description": "States least_feeder_2 for DEN in the department_reads sheet as \"CMP: 2\" (acceptable value is \"CMP: 2\"; spacing around the colon may vary).", + "justification": "Source: voluntary_leaves_FY26.png and involuntary_leaves_FY26.png (leave bands into DEN at all three transitions, each traced back to the department and people count at its start), headcount_1jul2025.csv. Rule: workforce_staffing_rules.pdf Section 3 S2 and Section 4. least_feeder_2: feeders of DEN, leaves over the year (voluntary + involuntary), fewest first: PAY 1 (employees 1 Jul 2025: 128); CMP 2 (employees 1 Jul 2025: 140). CMP -> DEN leave bands: Q3 2025 -> Q4 2025: 1 voluntary, 0 involuntary; Q4 2025 -> Q1 2026: 0 voluntary, 1 involuntary.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Spreadsheets (.xlsx, .xls, .xlsm, .ods)", + "dependencies": [] + }, + "criterion 36": { + "description": "States least_feeder_2 for FAC in the department_reads sheet as \"PSV: 1\" (acceptable value is \"PSV: 1\"; spacing around the colon may vary).", + "justification": "Source: voluntary_leaves_FY26.png and involuntary_leaves_FY26.png (leave bands into FAC at all three transitions, each traced back to the department and people count at its start), headcount_1jul2025.csv. Rule: workforce_staffing_rules.pdf Section 3 S2 and Section 4. least_feeder_2: feeders of FAC, leaves over the year (voluntary + involuntary), fewest first: CUS 1 (employees 1 Jul 2025: 210); PSV 1 (employees 1 Jul 2025: 175); DEN 1 (employees 1 Jul 2025: 160); SLS 1 (employees 1 Jul 2025: 150); PAY 1 (employees 1 Jul 2025: 128); CXD 1 (employees 1 Jul 2025: 95). Tie-break needed (more employees on 1 July 2025 first, headcount_1jul2025.csv): CUS, PSV, DEN, SLS, PAY, CXD. PSV -> FAC leave bands: Q1 2026 -> Q2 2026: 1 voluntary, 0 involuntary.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Spreadsheets (.xlsx, .xls, .xlsm, .ods)", + "dependencies": [] + }, + "criterion 37": { + "description": "States least_feeder_2 for FIN in the department_reads sheet as \"SUP: 2\" (acceptable value is \"SUP: 2\"; spacing around the colon may vary).", + "justification": "Source: voluntary_leaves_FY26.png and involuntary_leaves_FY26.png (leave bands into FIN at all three transitions, each traced back to the department and people count at its start), headcount_1jul2025.csv. Rule: workforce_staffing_rules.pdf Section 3 S2 and Section 4. least_feeder_2: feeders of FIN, leaves over the year (voluntary + involuntary), fewest first: LEG 1 (employees 1 Jul 2025: 120); SUP 2 (employees 1 Jul 2025: 220). SUP -> FIN leave bands: Q3 2025 -> Q4 2025: 1 voluntary, 0 involuntary; Q1 2026 -> Q2 2026: 1 voluntary, 0 involuntary.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Spreadsheets (.xlsx, .xls, .xlsm, .ods)", + "dependencies": [] + }, + "criterion 38": { + "description": "States least_feeder_2 for GRW in the department_reads sheet as \"FAC: 1\" (acceptable value is \"FAC: 1\"; spacing around the colon may vary).", + "justification": "Source: voluntary_leaves_FY26.png and involuntary_leaves_FY26.png (leave bands into GRW at all three transitions, each traced back to the department and people count at its start), headcount_1jul2025.csv. Rule: workforce_staffing_rules.pdf Section 3 S2 and Section 4. least_feeder_2: feeders of GRW, leaves over the year (voluntary + involuntary), fewest first: RET 1 (employees 1 Jul 2025: 340); FAC 1 (employees 1 Jul 2025: 130); LEG 1 (employees 1 Jul 2025: 120). Tie-break needed (more employees on 1 July 2025 first, headcount_1jul2025.csv): RET, FAC, LEG. FAC -> GRW leave bands: Q4 2025 -> Q1 2026: 1 voluntary, 0 involuntary.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Spreadsheets (.xlsx, .xls, .xlsm, .ods)", + "dependencies": [] + }, + "criterion 39": { + "description": "States least_feeder_2 for LEG in the department_reads sheet as \"CUS: 1\" (acceptable value is \"CUS: 1\"; spacing around the colon may vary).", + "justification": "Source: voluntary_leaves_FY26.png and involuntary_leaves_FY26.png (leave bands into LEG at all three transitions, each traced back to the department and people count at its start), headcount_1jul2025.csv. Rule: workforce_staffing_rules.pdf Section 3 S2 and Section 4. least_feeder_2: feeders of LEG, leaves over the year (voluntary + involuntary), fewest first: SUP 1 (employees 1 Jul 2025: 220); CUS 1 (employees 1 Jul 2025: 210); PSV 1 (employees 1 Jul 2025: 175); SLS 1 (employees 1 Jul 2025: 150); CMP 1 (employees 1 Jul 2025: 140); FAC 1 (employees 1 Jul 2025: 130); CXD 1 (employees 1 Jul 2025: 95); TRS 1 (employees 1 Jul 2025: 75). Tie-break needed (more employees on 1 July 2025 first, headcount_1jul2025.csv): SUP, CUS, PSV, SLS, CMP, FAC, CXD, TRS. CUS -> LEG leave bands: Q3 2025 -> Q4 2025: 0 voluntary, 1 involuntary.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Spreadsheets (.xlsx, .xls, .xlsm, .ods)", + "dependencies": [] + }, + "criterion 40": { + "description": "States least_feeder_2 for PAY in the department_reads sheet as \"PSV: 1\" (acceptable value is \"PSV: 1\"; spacing around the colon may vary).", + "justification": "Source: voluntary_leaves_FY26.png and involuntary_leaves_FY26.png (leave bands into PAY at all three transitions, each traced back to the department and people count at its start), headcount_1jul2025.csv. Rule: workforce_staffing_rules.pdf Section 3 S2 and Section 4. least_feeder_2: feeders of PAY, leaves over the year (voluntary + involuntary), fewest first: RET 1 (employees 1 Jul 2025: 340); PSV 1 (employees 1 Jul 2025: 175); DEN 1 (employees 1 Jul 2025: 160); CMP 1 (employees 1 Jul 2025: 140). Tie-break needed (more employees on 1 July 2025 first, headcount_1jul2025.csv): RET, PSV, DEN, CMP. PSV -> PAY leave bands: Q3 2025 -> Q4 2025: 1 voluntary, 0 involuntary.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Spreadsheets (.xlsx, .xls, .xlsm, .ods)", + "dependencies": [] + }, + "criterion 41": { + "description": "States least_feeder_2 for PRC in the department_reads sheet as \"PAY: 1\" (acceptable value is \"PAY: 1\"; spacing around the colon may vary).", + "justification": "Source: voluntary_leaves_FY26.png and involuntary_leaves_FY26.png (leave bands into PRC at all three transitions, each traced back to the department and people count at its start), headcount_1jul2025.csv. Rule: workforce_staffing_rules.pdf Section 3 S2 and Section 4. least_feeder_2: feeders of PRC, leaves over the year (voluntary + involuntary), fewest first: PSV 1 (employees 1 Jul 2025: 175); PAY 1 (employees 1 Jul 2025: 128); LEG 1 (employees 1 Jul 2025: 120); CXD 1 (employees 1 Jul 2025: 95). Tie-break needed (more employees on 1 July 2025 first, headcount_1jul2025.csv): PSV, PAY, LEG, CXD. PAY -> PRC leave bands: Q4 2025 -> Q1 2026: 0 voluntary, 1 involuntary.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Spreadsheets (.xlsx, .xls, .xlsm, .ods)", + "dependencies": [] + }, + "criterion 42": { + "description": "States least_feeder_2 for PSV in the department_reads sheet as \"PRC: 2\" (acceptable value is \"PRC: 2\"; spacing around the colon may vary).", + "justification": "Source: voluntary_leaves_FY26.png and involuntary_leaves_FY26.png (leave bands into PSV at all three transitions, each traced back to the department and people count at its start), headcount_1jul2025.csv. Rule: workforce_staffing_rules.pdf Section 3 S2 and Section 4. least_feeder_2: feeders of PSV, leaves over the year (voluntary + involuntary), fewest first: TRS 1 (employees 1 Jul 2025: 75); PRC 2 (employees 1 Jul 2025: 165); DEN 2 (employees 1 Jul 2025: 160); CXD 2 (employees 1 Jul 2025: 95). Tie-break needed (more employees on 1 July 2025 first, headcount_1jul2025.csv): PRC, DEN, CXD. PRC -> PSV leave bands: Q3 2025 -> Q4 2025: 1 voluntary, 0 involuntary; Q4 2025 -> Q1 2026: 0 voluntary, 1 involuntary.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Spreadsheets (.xlsx, .xls, .xlsm, .ods)", + "dependencies": [] + }, + "criterion 43": { + "description": "States least_feeder_2 for RET in the department_reads sheet as \"TRS: 1\" (acceptable value is \"TRS: 1\"; spacing around the colon may vary).", + "justification": "Source: voluntary_leaves_FY26.png and involuntary_leaves_FY26.png (leave bands into RET at all three transitions, each traced back to the department and people count at its start), headcount_1jul2025.csv. Rule: workforce_staffing_rules.pdf Section 3 S2 and Section 4. least_feeder_2: feeders of RET, leaves over the year (voluntary + involuntary), fewest first: LEG 1 (employees 1 Jul 2025: 120); TRS 1 (employees 1 Jul 2025: 75). Tie-break needed (more employees on 1 July 2025 first, headcount_1jul2025.csv): LEG, TRS. TRS -> RET leave bands: Q4 2025 -> Q1 2026: 0 voluntary, 1 involuntary.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Spreadsheets (.xlsx, .xls, .xlsm, .ods)", + "dependencies": [] + }, + "criterion 44": { + "description": "States least_feeder_2 for SLS in the department_reads sheet as \"PAY: 1\" (acceptable value is \"PAY: 1\"; spacing around the colon may vary).", + "justification": "Source: voluntary_leaves_FY26.png and involuntary_leaves_FY26.png (leave bands into SLS at all three transitions, each traced back to the department and people count at its start), headcount_1jul2025.csv. Rule: workforce_staffing_rules.pdf Section 3 S2 and Section 4. least_feeder_2: feeders of SLS, leaves over the year (voluntary + involuntary), fewest first: CMP 1 (employees 1 Jul 2025: 140); PAY 1 (employees 1 Jul 2025: 128). Tie-break needed (more employees on 1 July 2025 first, headcount_1jul2025.csv): CMP, PAY. PAY -> SLS leave bands: Q3 2025 -> Q4 2025: 1 voluntary, 0 involuntary.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Spreadsheets (.xlsx, .xls, .xlsm, .ods)", + "dependencies": [] + }, + "criterion 45": { + "description": "States least_feeder_2 for SUP in the department_reads sheet as \"CMP: 1\" (acceptable value is \"CMP: 1\"; spacing around the colon may vary).", + "justification": "Source: voluntary_leaves_FY26.png and involuntary_leaves_FY26.png (leave bands into SUP at all three transitions, each traced back to the department and people count at its start), headcount_1jul2025.csv. Rule: workforce_staffing_rules.pdf Section 3 S2 and Section 4. least_feeder_2: feeders of SUP, leaves over the year (voluntary + involuntary), fewest first: SLS 1 (employees 1 Jul 2025: 150); CMP 1 (employees 1 Jul 2025: 140); PAY 1 (employees 1 Jul 2025: 128); LEG 1 (employees 1 Jul 2025: 120). Tie-break needed (more employees on 1 July 2025 first, headcount_1jul2025.csv): SLS, CMP, PAY, LEG. CMP -> SUP leave bands: Q1 2026 -> Q2 2026: 0 voluntary, 1 involuntary.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Spreadsheets (.xlsx, .xls, .xlsm, .ods)", + "dependencies": [] + }, + "criterion 46": { + "description": "States least_feeder_2 for TRS in the department_reads sheet as \"LEG: 2\" (acceptable value is \"LEG: 2\"; spacing around the colon may vary).", + "justification": "Source: voluntary_leaves_FY26.png and involuntary_leaves_FY26.png (leave bands into TRS at all three transitions, each traced back to the department and people count at its start), headcount_1jul2025.csv. Rule: workforce_staffing_rules.pdf Section 3 S2 and Section 4. least_feeder_2: feeders of TRS, leaves over the year (voluntary + involuntary), fewest first: FIN 1 (employees 1 Jul 2025: 155); LEG 2 (employees 1 Jul 2025: 120). LEG -> TRS leave bands: Q4 2025 -> Q1 2026: 1 voluntary, 1 involuntary.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Spreadsheets (.xlsx, .xls, .xlsm, .ods)", + "dependencies": [] + }, + "criterion 47": { + "description": "States most_feeder_1 for CMP in the department_reads sheet as \"RET: 4\" (acceptable value is \"RET: 4\"; spacing around the colon may vary).", + "justification": "Source: voluntary_leaves_FY26.png and involuntary_leaves_FY26.png (leave bands into CMP at all three transitions, each traced back to the department and people count at its start), headcount_1jul2025.csv. Rule: workforce_staffing_rules.pdf Section 3 S2 and Section 4. most_feeder_1: feeders of CMP, leaves over the year (voluntary + involuntary), most first: RET 4 (employees 1 Jul 2025: 340); GRW 4 (employees 1 Jul 2025: 185). Tie-break needed (more employees on 1 July 2025 first, headcount_1jul2025.csv): RET, GRW. RET -> CMP leave bands: Q3 2025 -> Q4 2025: 2 voluntary, 0 involuntary; Q4 2025 -> Q1 2026: 0 voluntary, 1 involuntary; Q1 2026 -> Q2 2026: 0 voluntary, 1 involuntary.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Spreadsheets (.xlsx, .xls, .xlsm, .ods)", + "dependencies": [] + }, + "criterion 48": { + "description": "States most_feeder_1 for CUS in the department_reads sheet as \"GRW: 6\" (acceptable value is \"GRW: 6\"; spacing around the colon may vary).", + "justification": "Source: voluntary_leaves_FY26.png and involuntary_leaves_FY26.png (leave bands into CUS at all three transitions, each traced back to the department and people count at its start), headcount_1jul2025.csv. Rule: workforce_staffing_rules.pdf Section 3 S2 and Section 4. most_feeder_1: feeders of CUS, leaves over the year (voluntary + involuntary), most first: GRW 6 (employees 1 Jul 2025: 185); RET 5 (employees 1 Jul 2025: 340); PRC 5 (employees 1 Jul 2025: 165). GRW -> CUS leave bands: Q3 2025 -> Q4 2025: 3 voluntary, 0 involuntary; Q4 2025 -> Q1 2026: 0 voluntary, 1 involuntary; Q1 2026 -> Q2 2026: 2 voluntary, 0 involuntary.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Spreadsheets (.xlsx, .xls, .xlsm, .ods)", + "dependencies": [] + }, + "criterion 49": { + "description": "States most_feeder_1 for CXD in the department_reads sheet as \"PRC: 3\" (acceptable value is \"PRC: 3\"; spacing around the colon may vary).", + "justification": "Source: voluntary_leaves_FY26.png and involuntary_leaves_FY26.png (leave bands into CXD at all three transitions, each traced back to the department and people count at its start), headcount_1jul2025.csv. Rule: workforce_staffing_rules.pdf Section 3 S2 and Section 4. most_feeder_1: feeders of CXD, leaves over the year (voluntary + involuntary), most first: PRC 3 (employees 1 Jul 2025: 165); FIN 2 (employees 1 Jul 2025: 155). PRC -> CXD leave bands: Q4 2025 -> Q1 2026: 1 voluntary, 1 involuntary; Q1 2026 -> Q2 2026: 0 voluntary, 1 involuntary.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Spreadsheets (.xlsx, .xls, .xlsm, .ods)", + "dependencies": [] + }, + "criterion 50": { + "description": "States most_feeder_1 for DEN in the department_reads sheet as \"SUP: 4\" (acceptable value is \"SUP: 4\"; spacing around the colon may vary).", + "justification": "Source: voluntary_leaves_FY26.png and involuntary_leaves_FY26.png (leave bands into DEN at all three transitions, each traced back to the department and people count at its start), headcount_1jul2025.csv. Rule: workforce_staffing_rules.pdf Section 3 S2 and Section 4. most_feeder_1: feeders of DEN, leaves over the year (voluntary + involuntary), most first: SUP 4 (employees 1 Jul 2025: 220); GRW 4 (employees 1 Jul 2025: 185). Tie-break needed (more employees on 1 July 2025 first, headcount_1jul2025.csv): SUP, GRW. SUP -> DEN leave bands: Q3 2025 -> Q4 2025: 0 voluntary, 1 involuntary; Q1 2026 -> Q2 2026: 2 voluntary, 1 involuntary.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Spreadsheets (.xlsx, .xls, .xlsm, .ods)", + "dependencies": [] + }, + "criterion 51": { + "description": "States most_feeder_1 for FAC in the department_reads sheet as \"RET: 4\" (acceptable value is \"RET: 4\"; spacing around the colon may vary).", + "justification": "Source: voluntary_leaves_FY26.png and involuntary_leaves_FY26.png (leave bands into FAC at all three transitions, each traced back to the department and people count at its start), headcount_1jul2025.csv. Rule: workforce_staffing_rules.pdf Section 3 S2 and Section 4. most_feeder_1: feeders of FAC, leaves over the year (voluntary + involuntary), most first: RET 4 (employees 1 Jul 2025: 340); SUP 3 (employees 1 Jul 2025: 220). RET -> FAC leave bands: Q3 2025 -> Q4 2025: 2 voluntary, 1 involuntary; Q1 2026 -> Q2 2026: 1 voluntary, 0 involuntary.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Spreadsheets (.xlsx, .xls, .xlsm, .ods)", + "dependencies": [] + }, + "criterion 52": { + "description": "States most_feeder_1 for FIN in the department_reads sheet as \"DEN: 5\" (acceptable value is \"DEN: 5\"; spacing around the colon may vary).", + "justification": "Source: voluntary_leaves_FY26.png and involuntary_leaves_FY26.png (leave bands into FIN at all three transitions, each traced back to the department and people count at its start), headcount_1jul2025.csv. Rule: workforce_staffing_rules.pdf Section 3 S2 and Section 4. most_feeder_1: feeders of FIN, leaves over the year (voluntary + involuntary), most first: DEN 5 (employees 1 Jul 2025: 160); RET 4 (employees 1 Jul 2025: 340). DEN -> FIN leave bands: Q3 2025 -> Q4 2025: 0 voluntary, 1 involuntary; Q4 2025 -> Q1 2026: 1 voluntary, 0 involuntary; Q1 2026 -> Q2 2026: 1 voluntary, 2 involuntary.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Spreadsheets (.xlsx, .xls, .xlsm, .ods)", + "dependencies": [] + }, + "criterion 53": { + "description": "States most_feeder_1 for GRW in the department_reads sheet as \"SUP: 5\" (acceptable value is \"SUP: 5\"; spacing around the colon may vary).", + "justification": "Source: voluntary_leaves_FY26.png and involuntary_leaves_FY26.png (leave bands into GRW at all three transitions, each traced back to the department and people count at its start), headcount_1jul2025.csv. Rule: workforce_staffing_rules.pdf Section 3 S2 and Section 4. most_feeder_1: feeders of GRW, leaves over the year (voluntary + involuntary), most first: SUP 5 (employees 1 Jul 2025: 220); CMP 5 (employees 1 Jul 2025: 140); PAY 5 (employees 1 Jul 2025: 128). Tie-break needed (more employees on 1 July 2025 first, headcount_1jul2025.csv): SUP, CMP, PAY. SUP -> GRW leave bands: Q3 2025 -> Q4 2025: 0 voluntary, 1 involuntary; Q4 2025 -> Q1 2026: 2 voluntary, 1 involuntary; Q1 2026 -> Q2 2026: 1 voluntary, 0 involuntary.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Spreadsheets (.xlsx, .xls, .xlsm, .ods)", + "dependencies": [] + }, + "criterion 54": { + "description": "States most_feeder_1 for LEG in the department_reads sheet as \"RET: 2\" (acceptable value is \"RET: 2\"; spacing around the colon may vary).", + "justification": "Source: voluntary_leaves_FY26.png and involuntary_leaves_FY26.png (leave bands into LEG at all three transitions, each traced back to the department and people count at its start), headcount_1jul2025.csv. Rule: workforce_staffing_rules.pdf Section 3 S2 and Section 4. most_feeder_1: feeders of LEG, leaves over the year (voluntary + involuntary), most first: RET 2 (employees 1 Jul 2025: 340); SUP 1 (employees 1 Jul 2025: 220); CUS 1 (employees 1 Jul 2025: 210); PSV 1 (employees 1 Jul 2025: 175); SLS 1 (employees 1 Jul 2025: 150); CMP 1 (employees 1 Jul 2025: 140); FAC 1 (employees 1 Jul 2025: 130); CXD 1 (employees 1 Jul 2025: 95); TRS 1 (employees 1 Jul 2025: 75). RET -> LEG leave bands: Q4 2025 -> Q1 2026: 0 voluntary, 1 involuntary; Q1 2026 -> Q2 2026: 1 voluntary, 0 involuntary.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Spreadsheets (.xlsx, .xls, .xlsm, .ods)", + "dependencies": [] + }, + "criterion 55": { + "description": "States most_feeder_1 for PAY in the department_reads sheet as \"PRC: 4\" (acceptable value is \"PRC: 4\"; spacing around the colon may vary).", + "justification": "Source: voluntary_leaves_FY26.png and involuntary_leaves_FY26.png (leave bands into PAY at all three transitions, each traced back to the department and people count at its start), headcount_1jul2025.csv. Rule: workforce_staffing_rules.pdf Section 3 S2 and Section 4. most_feeder_1: feeders of PAY, leaves over the year (voluntary + involuntary), most first: PRC 4 (employees 1 Jul 2025: 165); CUS 3 (employees 1 Jul 2025: 210). PRC -> PAY leave bands: Q4 2025 -> Q1 2026: 1 voluntary, 0 involuntary; Q1 2026 -> Q2 2026: 1 voluntary, 2 involuntary.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Spreadsheets (.xlsx, .xls, .xlsm, .ods)", + "dependencies": [] + }, + "criterion 56": { + "description": "States most_feeder_1 for PRC in the department_reads sheet as \"FAC: 5\" (acceptable value is \"FAC: 5\"; spacing around the colon may vary).", + "justification": "Source: voluntary_leaves_FY26.png and involuntary_leaves_FY26.png (leave bands into PRC at all three transitions, each traced back to the department and people count at its start), headcount_1jul2025.csv. Rule: workforce_staffing_rules.pdf Section 3 S2 and Section 4. most_feeder_1: feeders of PRC, leaves over the year (voluntary + involuntary), most first: FAC 5 (employees 1 Jul 2025: 130); RET 4 (employees 1 Jul 2025: 340); SUP 4 (employees 1 Jul 2025: 220). FAC -> PRC leave bands: Q3 2025 -> Q4 2025: 1 voluntary, 0 involuntary; Q4 2025 -> Q1 2026: 0 voluntary, 1 involuntary; Q1 2026 -> Q2 2026: 2 voluntary, 1 involuntary.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Spreadsheets (.xlsx, .xls, .xlsm, .ods)", + "dependencies": [] + }, + "criterion 57": { + "description": "States most_feeder_1 for PSV in the department_reads sheet as \"RET: 6\" (acceptable value is \"RET: 6\"; spacing around the colon may vary).", + "justification": "Source: voluntary_leaves_FY26.png and involuntary_leaves_FY26.png (leave bands into PSV at all three transitions, each traced back to the department and people count at its start), headcount_1jul2025.csv. Rule: workforce_staffing_rules.pdf Section 3 S2 and Section 4. most_feeder_1: feeders of PSV, leaves over the year (voluntary + involuntary), most first: RET 6 (employees 1 Jul 2025: 340); SUP 6 (employees 1 Jul 2025: 220). Tie-break needed (more employees on 1 July 2025 first, headcount_1jul2025.csv): RET, SUP. RET -> PSV leave bands: Q3 2025 -> Q4 2025: 1 voluntary, 0 involuntary; Q1 2026 -> Q2 2026: 2 voluntary, 3 involuntary.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Spreadsheets (.xlsx, .xls, .xlsm, .ods)", + "dependencies": [] + }, + "criterion 58": { + "description": "States most_feeder_1 for RET in the department_reads sheet as \"CUS: 7\" (acceptable value is \"CUS: 7\"; spacing around the colon may vary).", + "justification": "Source: voluntary_leaves_FY26.png and involuntary_leaves_FY26.png (leave bands into RET at all three transitions, each traced back to the department and people count at its start), headcount_1jul2025.csv. Rule: workforce_staffing_rules.pdf Section 3 S2 and Section 4. most_feeder_1: feeders of RET, leaves over the year (voluntary + involuntary), most first: CUS 7 (employees 1 Jul 2025: 210); SLS 6 (employees 1 Jul 2025: 150). CUS -> RET leave bands: Q4 2025 -> Q1 2026: 2 voluntary, 1 involuntary; Q1 2026 -> Q2 2026: 2 voluntary, 2 involuntary.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Spreadsheets (.xlsx, .xls, .xlsm, .ods)", + "dependencies": [] + }, + "criterion 59": { + "description": "States most_feeder_1 for SLS in the department_reads sheet as \"RET: 7\" (acceptable value is \"RET: 7\"; spacing around the colon may vary).", + "justification": "Source: voluntary_leaves_FY26.png and involuntary_leaves_FY26.png (leave bands into SLS at all three transitions, each traced back to the department and people count at its start), headcount_1jul2025.csv. Rule: workforce_staffing_rules.pdf Section 3 S2 and Section 4. most_feeder_1: feeders of SLS, leaves over the year (voluntary + involuntary), most first: RET 7 (employees 1 Jul 2025: 340); GRW 4 (employees 1 Jul 2025: 185). RET -> SLS leave bands: Q3 2025 -> Q4 2025: 3 voluntary, 0 involuntary; Q4 2025 -> Q1 2026: 1 voluntary, 1 involuntary; Q1 2026 -> Q2 2026: 2 voluntary, 0 involuntary.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Spreadsheets (.xlsx, .xls, .xlsm, .ods)", + "dependencies": [] + }, + "criterion 60": { + "description": "States most_feeder_1 for SUP in the department_reads sheet as \"PRC: 7\" (acceptable value is \"PRC: 7\"; spacing around the colon may vary).", + "justification": "Source: voluntary_leaves_FY26.png and involuntary_leaves_FY26.png (leave bands into SUP at all three transitions, each traced back to the department and people count at its start), headcount_1jul2025.csv. Rule: workforce_staffing_rules.pdf Section 3 S2 and Section 4. most_feeder_1: feeders of SUP, leaves over the year (voluntary + involuntary), most first: PRC 7 (employees 1 Jul 2025: 165); RET 4 (employees 1 Jul 2025: 340); CUS 4 (employees 1 Jul 2025: 210). PRC -> SUP leave bands: Q3 2025 -> Q4 2025: 1 voluntary, 0 involuntary; Q4 2025 -> Q1 2026: 2 voluntary, 0 involuntary; Q1 2026 -> Q2 2026: 3 voluntary, 1 involuntary.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Spreadsheets (.xlsx, .xls, .xlsm, .ods)", + "dependencies": [] + }, + "criterion 61": { + "description": "States most_feeder_1 for TRS in the department_reads sheet as \"LEG: 2\" (acceptable value is \"LEG: 2\"; spacing around the colon may vary).", + "justification": "Source: voluntary_leaves_FY26.png and involuntary_leaves_FY26.png (leave bands into TRS at all three transitions, each traced back to the department and people count at its start), headcount_1jul2025.csv. Rule: workforce_staffing_rules.pdf Section 3 S2 and Section 4. most_feeder_1: feeders of TRS, leaves over the year (voluntary + involuntary), most first: LEG 2 (employees 1 Jul 2025: 120); FIN 1 (employees 1 Jul 2025: 155). LEG -> TRS leave bands: Q4 2025 -> Q1 2026: 1 voluntary, 1 involuntary.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Spreadsheets (.xlsx, .xls, .xlsm, .ods)", + "dependencies": [] + }, + "criterion 62": { + "description": "States most_feeder_2 for CMP in the department_reads sheet as \"GRW: 4\" (acceptable value is \"GRW: 4\"; spacing around the colon may vary).", + "justification": "Source: voluntary_leaves_FY26.png and involuntary_leaves_FY26.png (leave bands into CMP at all three transitions, each traced back to the department and people count at its start), headcount_1jul2025.csv. Rule: workforce_staffing_rules.pdf Section 3 S2 and Section 4. most_feeder_2: feeders of CMP, leaves over the year (voluntary + involuntary), most first: RET 4 (employees 1 Jul 2025: 340); GRW 4 (employees 1 Jul 2025: 185). Tie-break needed (more employees on 1 July 2025 first, headcount_1jul2025.csv): RET, GRW. GRW -> CMP leave bands: Q4 2025 -> Q1 2026: 0 voluntary, 1 involuntary; Q1 2026 -> Q2 2026: 1 voluntary, 2 involuntary.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Spreadsheets (.xlsx, .xls, .xlsm, .ods)", + "dependencies": [] + }, + "criterion 63": { + "description": "States most_feeder_2 for CUS in the department_reads sheet as \"RET: 5\" (acceptable value is \"RET: 5\"; spacing around the colon may vary).", + "justification": "Source: voluntary_leaves_FY26.png and involuntary_leaves_FY26.png (leave bands into CUS at all three transitions, each traced back to the department and people count at its start), headcount_1jul2025.csv. Rule: workforce_staffing_rules.pdf Section 3 S2 and Section 4. most_feeder_2: feeders of CUS, leaves over the year (voluntary + involuntary), most first: GRW 6 (employees 1 Jul 2025: 185); RET 5 (employees 1 Jul 2025: 340); PRC 5 (employees 1 Jul 2025: 165). Tie-break needed (more employees on 1 July 2025 first, headcount_1jul2025.csv): RET, PRC. RET -> CUS leave bands: Q3 2025 -> Q4 2025: 2 voluntary, 0 involuntary; Q4 2025 -> Q1 2026: 0 voluntary, 1 involuntary; Q1 2026 -> Q2 2026: 1 voluntary, 1 involuntary.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Spreadsheets (.xlsx, .xls, .xlsm, .ods)", + "dependencies": [] + }, + "criterion 64": { + "description": "States most_feeder_2 for CXD in the department_reads sheet as \"FIN: 2\" (acceptable value is \"FIN: 2\"; spacing around the colon may vary).", + "justification": "Source: voluntary_leaves_FY26.png and involuntary_leaves_FY26.png (leave bands into CXD at all three transitions, each traced back to the department and people count at its start), headcount_1jul2025.csv. Rule: workforce_staffing_rules.pdf Section 3 S2 and Section 4. most_feeder_2: feeders of CXD, leaves over the year (voluntary + involuntary), most first: PRC 3 (employees 1 Jul 2025: 165); FIN 2 (employees 1 Jul 2025: 155). FIN -> CXD leave bands: Q1 2026 -> Q2 2026: 2 voluntary, 0 involuntary.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Spreadsheets (.xlsx, .xls, .xlsm, .ods)", + "dependencies": [] + }, + "criterion 65": { + "description": "States most_feeder_2 for DEN in the department_reads sheet as \"GRW: 4\" (acceptable value is \"GRW: 4\"; spacing around the colon may vary).", + "justification": "Source: voluntary_leaves_FY26.png and involuntary_leaves_FY26.png (leave bands into DEN at all three transitions, each traced back to the department and people count at its start), headcount_1jul2025.csv. Rule: workforce_staffing_rules.pdf Section 3 S2 and Section 4. most_feeder_2: feeders of DEN, leaves over the year (voluntary + involuntary), most first: SUP 4 (employees 1 Jul 2025: 220); GRW 4 (employees 1 Jul 2025: 185). Tie-break needed (more employees on 1 July 2025 first, headcount_1jul2025.csv): SUP, GRW. GRW -> DEN leave bands: Q3 2025 -> Q4 2025: 1 voluntary, 1 involuntary; Q4 2025 -> Q1 2026: 0 voluntary, 1 involuntary; Q1 2026 -> Q2 2026: 0 voluntary, 1 involuntary.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Spreadsheets (.xlsx, .xls, .xlsm, .ods)", + "dependencies": [] + }, + "criterion 66": { + "description": "States most_feeder_2 for FAC in the department_reads sheet as \"SUP: 3\" (acceptable value is \"SUP: 3\"; spacing around the colon may vary).", + "justification": "Source: voluntary_leaves_FY26.png and involuntary_leaves_FY26.png (leave bands into FAC at all three transitions, each traced back to the department and people count at its start), headcount_1jul2025.csv. Rule: workforce_staffing_rules.pdf Section 3 S2 and Section 4. most_feeder_2: feeders of FAC, leaves over the year (voluntary + involuntary), most first: RET 4 (employees 1 Jul 2025: 340); SUP 3 (employees 1 Jul 2025: 220). SUP -> FAC leave bands: Q4 2025 -> Q1 2026: 3 voluntary, 0 involuntary.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Spreadsheets (.xlsx, .xls, .xlsm, .ods)", + "dependencies": [] + }, + "criterion 67": { + "description": "States most_feeder_2 for FIN in the department_reads sheet as \"RET: 4\" (acceptable value is \"RET: 4\"; spacing around the colon may vary).", + "justification": "Source: voluntary_leaves_FY26.png and involuntary_leaves_FY26.png (leave bands into FIN at all three transitions, each traced back to the department and people count at its start), headcount_1jul2025.csv. Rule: workforce_staffing_rules.pdf Section 3 S2 and Section 4. most_feeder_2: feeders of FIN, leaves over the year (voluntary + involuntary), most first: DEN 5 (employees 1 Jul 2025: 160); RET 4 (employees 1 Jul 2025: 340). RET -> FIN leave bands: Q4 2025 -> Q1 2026: 1 voluntary, 2 involuntary; Q1 2026 -> Q2 2026: 0 voluntary, 1 involuntary.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Spreadsheets (.xlsx, .xls, .xlsm, .ods)", + "dependencies": [] + }, + "criterion 68": { + "description": "States most_feeder_2 for GRW in the department_reads sheet as \"CMP: 5\" (acceptable value is \"CMP: 5\"; spacing around the colon may vary).", + "justification": "Source: voluntary_leaves_FY26.png and involuntary_leaves_FY26.png (leave bands into GRW at all three transitions, each traced back to the department and people count at its start), headcount_1jul2025.csv. Rule: workforce_staffing_rules.pdf Section 3 S2 and Section 4. most_feeder_2: feeders of GRW, leaves over the year (voluntary + involuntary), most first: SUP 5 (employees 1 Jul 2025: 220); CMP 5 (employees 1 Jul 2025: 140); PAY 5 (employees 1 Jul 2025: 128). Tie-break needed (more employees on 1 July 2025 first, headcount_1jul2025.csv): SUP, CMP, PAY. CMP -> GRW leave bands: Q3 2025 -> Q4 2025: 1 voluntary, 0 involuntary; Q4 2025 -> Q1 2026: 0 voluntary, 1 involuntary; Q1 2026 -> Q2 2026: 2 voluntary, 1 involuntary.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Spreadsheets (.xlsx, .xls, .xlsm, .ods)", + "dependencies": [] + }, + "criterion 69": { + "description": "States most_feeder_2 for LEG in the department_reads sheet as \"SUP: 1\" (acceptable value is \"SUP: 1\"; spacing around the colon may vary).", + "justification": "Source: voluntary_leaves_FY26.png and involuntary_leaves_FY26.png (leave bands into LEG at all three transitions, each traced back to the department and people count at its start), headcount_1jul2025.csv. Rule: workforce_staffing_rules.pdf Section 3 S2 and Section 4. most_feeder_2: feeders of LEG, leaves over the year (voluntary + involuntary), most first: RET 2 (employees 1 Jul 2025: 340); SUP 1 (employees 1 Jul 2025: 220); CUS 1 (employees 1 Jul 2025: 210); PSV 1 (employees 1 Jul 2025: 175); SLS 1 (employees 1 Jul 2025: 150); CMP 1 (employees 1 Jul 2025: 140); FAC 1 (employees 1 Jul 2025: 130); CXD 1 (employees 1 Jul 2025: 95); TRS 1 (employees 1 Jul 2025: 75). Tie-break needed (more employees on 1 July 2025 first, headcount_1jul2025.csv): SUP, CUS, PSV, SLS, CMP, FAC, CXD, TRS. SUP -> LEG leave bands: Q1 2026 -> Q2 2026: 1 voluntary, 0 involuntary.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Spreadsheets (.xlsx, .xls, .xlsm, .ods)", + "dependencies": [] + }, + "criterion 70": { + "description": "States most_feeder_2 for PAY in the department_reads sheet as \"CUS: 3\" (acceptable value is \"CUS: 3\"; spacing around the colon may vary).", + "justification": "Source: voluntary_leaves_FY26.png and involuntary_leaves_FY26.png (leave bands into PAY at all three transitions, each traced back to the department and people count at its start), headcount_1jul2025.csv. Rule: workforce_staffing_rules.pdf Section 3 S2 and Section 4. most_feeder_2: feeders of PAY, leaves over the year (voluntary + involuntary), most first: PRC 4 (employees 1 Jul 2025: 165); CUS 3 (employees 1 Jul 2025: 210). CUS -> PAY leave bands: Q1 2026 -> Q2 2026: 3 voluntary, 0 involuntary.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Spreadsheets (.xlsx, .xls, .xlsm, .ods)", + "dependencies": [] + }, + "criterion 71": { + "description": "States most_feeder_2 for PRC in the department_reads sheet as \"RET: 4\" (acceptable value is \"RET: 4\"; spacing around the colon may vary).", + "justification": "Source: voluntary_leaves_FY26.png and involuntary_leaves_FY26.png (leave bands into PRC at all three transitions, each traced back to the department and people count at its start), headcount_1jul2025.csv. Rule: workforce_staffing_rules.pdf Section 3 S2 and Section 4. most_feeder_2: feeders of PRC, leaves over the year (voluntary + involuntary), most first: FAC 5 (employees 1 Jul 2025: 130); RET 4 (employees 1 Jul 2025: 340); SUP 4 (employees 1 Jul 2025: 220). Tie-break needed (more employees on 1 July 2025 first, headcount_1jul2025.csv): RET, SUP. RET -> PRC leave bands: Q3 2025 -> Q4 2025: 2 voluntary, 0 involuntary; Q4 2025 -> Q1 2026: 2 voluntary, 0 involuntary.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Spreadsheets (.xlsx, .xls, .xlsm, .ods)", + "dependencies": [] + }, + "criterion 72": { + "description": "States most_feeder_2 for PSV in the department_reads sheet as \"SUP: 6\" (acceptable value is \"SUP: 6\"; spacing around the colon may vary).", + "justification": "Source: voluntary_leaves_FY26.png and involuntary_leaves_FY26.png (leave bands into PSV at all three transitions, each traced back to the department and people count at its start), headcount_1jul2025.csv. Rule: workforce_staffing_rules.pdf Section 3 S2 and Section 4. most_feeder_2: feeders of PSV, leaves over the year (voluntary + involuntary), most first: RET 6 (employees 1 Jul 2025: 340); SUP 6 (employees 1 Jul 2025: 220). Tie-break needed (more employees on 1 July 2025 first, headcount_1jul2025.csv): RET, SUP. SUP -> PSV leave bands: Q3 2025 -> Q4 2025: 1 voluntary, 1 involuntary; Q4 2025 -> Q1 2026: 2 voluntary, 0 involuntary; Q1 2026 -> Q2 2026: 1 voluntary, 1 involuntary.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Spreadsheets (.xlsx, .xls, .xlsm, .ods)", + "dependencies": [] + }, + "criterion 73": { + "description": "States most_feeder_2 for RET in the department_reads sheet as \"SLS: 6\" (acceptable value is \"SLS: 6\"; spacing around the colon may vary).", + "justification": "Source: voluntary_leaves_FY26.png and involuntary_leaves_FY26.png (leave bands into RET at all three transitions, each traced back to the department and people count at its start), headcount_1jul2025.csv. Rule: workforce_staffing_rules.pdf Section 3 S2 and Section 4. most_feeder_2: feeders of RET, leaves over the year (voluntary + involuntary), most first: CUS 7 (employees 1 Jul 2025: 210); SLS 6 (employees 1 Jul 2025: 150). SLS -> RET leave bands: Q3 2025 -> Q4 2025: 2 voluntary, 0 involuntary; Q4 2025 -> Q1 2026: 1 voluntary, 1 involuntary; Q1 2026 -> Q2 2026: 1 voluntary, 1 involuntary.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Spreadsheets (.xlsx, .xls, .xlsm, .ods)", + "dependencies": [] + }, + "criterion 74": { + "description": "States most_feeder_2 for SLS in the department_reads sheet as \"GRW: 4\" (acceptable value is \"GRW: 4\"; spacing around the colon may vary).", + "justification": "Source: voluntary_leaves_FY26.png and involuntary_leaves_FY26.png (leave bands into SLS at all three transitions, each traced back to the department and people count at its start), headcount_1jul2025.csv. Rule: workforce_staffing_rules.pdf Section 3 S2 and Section 4. most_feeder_2: feeders of SLS, leaves over the year (voluntary + involuntary), most first: RET 7 (employees 1 Jul 2025: 340); GRW 4 (employees 1 Jul 2025: 185). GRW -> SLS leave bands: Q3 2025 -> Q4 2025: 1 voluntary, 0 involuntary; Q4 2025 -> Q1 2026: 1 voluntary, 1 involuntary; Q1 2026 -> Q2 2026: 1 voluntary, 0 involuntary.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Spreadsheets (.xlsx, .xls, .xlsm, .ods)", + "dependencies": [] + }, + "criterion 75": { + "description": "States most_feeder_2 for SUP in the department_reads sheet as \"RET: 4\" (acceptable value is \"RET: 4\"; spacing around the colon may vary).", + "justification": "Source: voluntary_leaves_FY26.png and involuntary_leaves_FY26.png (leave bands into SUP at all three transitions, each traced back to the department and people count at its start), headcount_1jul2025.csv. Rule: workforce_staffing_rules.pdf Section 3 S2 and Section 4. most_feeder_2: feeders of SUP, leaves over the year (voluntary + involuntary), most first: PRC 7 (employees 1 Jul 2025: 165); RET 4 (employees 1 Jul 2025: 340); CUS 4 (employees 1 Jul 2025: 210). Tie-break needed (more employees on 1 July 2025 first, headcount_1jul2025.csv): RET, CUS. RET -> SUP leave bands: Q3 2025 -> Q4 2025: 2 voluntary, 0 involuntary; Q1 2026 -> Q2 2026: 1 voluntary, 1 involuntary.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Spreadsheets (.xlsx, .xls, .xlsm, .ods)", + "dependencies": [] + }, + "criterion 76": { + "description": "States most_feeder_2 for TRS in the department_reads sheet as \"FIN: 1\" (acceptable value is \"FIN: 1\"; spacing around the colon may vary).", + "justification": "Source: voluntary_leaves_FY26.png and involuntary_leaves_FY26.png (leave bands into TRS at all three transitions, each traced back to the department and people count at its start), headcount_1jul2025.csv. Rule: workforce_staffing_rules.pdf Section 3 S2 and Section 4. most_feeder_2: feeders of TRS, leaves over the year (voluntary + involuntary), most first: LEG 2 (employees 1 Jul 2025: 120); FIN 1 (employees 1 Jul 2025: 155). FIN -> TRS leave bands: Q1 2026 -> Q2 2026: 0 voluntary, 1 involuntary.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 3, + "grading_target": "Spreadsheets (.xlsx, .xls, .xlsm, .ods)", + "dependencies": [] + }, + "criterion 77": { + "description": "Fills the title cell A1 and header cells A2:B2 of the summary sheet with #006971.", + "justification": "Source: workforce_staffing_rules.pdf Section 6 (Format) requires the styling of ZenAnalytics_Branding.xlsx, Sheet_Title-2. Its title at A1 and header row 2 use solid fill #006971. The output summary has two populated header cells, A2:B2. The title may use either merge span accepted by C8. This criterion checks the effective native fill of the title through A1 and both header cells, including valid native table-style formatting.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 4, + "grading_target": "Spreadsheets (.xlsx, .xls, .xlsm, .ods)", + "dependencies": [] + }, + "criterion 78": { + "description": "Uses font size 11 pt for the title and header rows of both worksheets.", + "justification": "Source: workforce_staffing_rules.pdf Section 6 (Format): each output sheet takes the layout and styling of the template sheet in the same position (department_reads follows template sheet 1, Sheet_Title-1; summary follows template sheet 2, Sheet_Title-2). Templates Sheet_Title-1 and Sheet_Title-2: title cell A1 and header row 2 are 11 pt.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Spreadsheets (.xlsx, .xls, .xlsm, .ods)", + "dependencies": [] + }, + "criterion 79": { + "description": "Formats the title and header text of both worksheets in bold.", + "justification": "Source: workforce_staffing_rules.pdf Section 6 (Format): each output sheet takes the layout and styling of the template sheet in the same position (department_reads follows template sheet 1, Sheet_Title-1; summary follows template sheet 2, Sheet_Title-2). Templates Sheet_Title-1 and Sheet_Title-2: title cell A1 and every header cell in row 2 are bold.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Spreadsheets (.xlsx, .xls, .xlsm, .ods)", + "dependencies": [] + }, + "criterion 80": { + "description": "Displays exactly two populated table columns with the headers \"METRIC\" and \"VALUE\" in the header row of the \"summary\" sheet, in that order, and no additional populated table column (headers acceptable: case-insensitive).", + "justification": "Source: workforce_staffing_rules.pdf Section 6 (summary) fixes the columns as metric, value; ZenAnalytics_Branding.xlsx, sheet 2, row 2 (the table header row beneath the row-1 title) writes headers in capitals. Expected, in order: METRIC, VALUE. Missing, duplicated, reordered or additional table headers/fields fail. An extra working column such as a separate leave count, a fourth feeder or a headcount fails, and so does residual template text in an extra table column, such as HEADER 3 in C2. The sheet title and blank formatted margin cells do not count as table columns (the summary sheet carries no logo).", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Spreadsheets (.xlsx, .xls, .xlsm, .ods)", + "dependencies": [] + }, + "criterion 81": { + "description": "Includes exactly these metric values in this order in the \"METRIC\" column: involuntary_least_departments, reciprocal_least_departments, short_feeder_departments.", + "justification": "Source: workforce_staffing_rules.pdf Section 6 (summary): one row per Section 5 list, in the Section 5 order, with metric holding the Section 5 list name. Exact strings in this exact order; a missing, extra or reordered metric fails.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 2, + "grading_target": "Spreadsheets (.xlsx, .xls, .xlsm, .ods)", + "dependencies": [] + }, + "criterion 82": { + "description": "Alternates the body-row backgrounds of the summary sheet between #F5F9FA and #FFFFFF, starting with #F5F9FA on the first body row (row 3).", + "justification": "Source: workforce_staffing_rules.pdf Section 6 (Format): each output sheet takes the layout and styling of the template sheet in the same position (department_reads follows template sheet 1, Sheet_Title-1; summary follows template sheet 2, Sheet_Title-2). Template Sheet_Title-2 formats its table A2:E80 with table style Sheet_Title-2-style, row stripes on: firstRowStripe #F5F9FA, secondRowStripe #FFFFFF. Rows 3 and 5 are #F5F9FA and row 4 is #FFFFFF across all 3 body rows. Banding applied by explicit cell fills or by an Excel table that uses a table style with these stripe colours both pass; a white band may be stored as #FFFFFF or as no fill. Exact hex match on the light band.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Spreadsheets (.xlsx, .xls, .xlsm, .ods)", + "dependencies": [] + }, + "criterion 83": { + "description": "Formats the table body text in regular weight (not bold, not italic), colored #1A1B1F in the department_reads sheet and #161D1E in the summary sheet.", + "justification": "Source: workforce_staffing_rules.pdf Section 6 (Format): each output sheet takes the layout and styling of the template sheet in the same position (department_reads follows template sheet 1, Sheet_Title-1; summary follows template sheet 2, Sheet_Title-2). Template body cells (row 3 down) are neither bold nor italic; font colour #1A1B1F in Sheet_Title-1 and #161D1E in Sheet_Title-2. Applies to every body cell of both output sheets.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Spreadsheets (.xlsx, .xls, .xlsm, .ods)", + "dependencies": [] + }, + "criterion 84": { + "description": "Uses font size 10 pt for all table body cells of both worksheets.", + "justification": "Source: workforce_staffing_rules.pdf Section 6 (Format): each output sheet takes the layout and styling of the template sheet in the same position (department_reads follows template sheet 1, Sheet_Title-1; summary follows template sheet 2, Sheet_Title-2). Templates Sheet_Title-1 and Sheet_Title-2: every body cell from row 3 down is 10 pt.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Spreadsheets (.xlsx, .xls, .xlsm, .ods)", + "dependencies": [] + }, + "criterion 85": { + "description": "States the summary sheet value for involuntary_least_departments as exactly \"DEN, FIN, PAY, SLS, TRS\" (acceptable value is that exact list).", + "justification": "Rule: workforce_staffing_rules.pdf Section 5: departments whose least_feeder_1 leaves all appear in the involuntary chart: CMP DEN: 1 (1 voluntary); CUS PAY: 1 (1 voluntary); CXD RET: 1 (1 voluntary); DEN PAY: 1 (0 voluntary); FAC CUS: 1 (1 voluntary); FIN LEG: 1 (0 voluntary); GRW RET: 1 (1 voluntary); LEG SUP: 1 (1 voluntary); PAY RET: 1 (0 voluntary); PRC PSV: 1 (1 voluntary); PSV TRS: 1 (1 voluntary); RET LEG: 1 (1 voluntary); SLS CMP: 1 (0 voluntary); SUP SLS: 1 (1 voluntary); TRS FIN: 1 (0 voluntary). Codes ascending, joined by a comma and one space. Expected: DEN, FIN, PAY, SLS, TRS.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 4, + "grading_target": "Spreadsheets (.xlsx, .xls, .xlsm, .ods)", + "dependencies": [] + }, + "criterion 86": { + "description": "States the summary sheet value for reciprocal_least_departments as exactly \"CMP, PRC, SLS\" (acceptable value is that exact list).", + "justification": "Rule: workforce_staffing_rules.pdf Section 5: departments D whose least_feeder_1 F has D among F's own two least feeders: CMP -> DEN (PAY, CMP); CUS -> PAY (RET, PSV); CXD -> RET (LEG, TRS); DEN -> PAY (RET, PSV); FAC -> CUS (PAY, CMP); FIN -> LEG (SUP, CUS); GRW -> RET (LEG, TRS); LEG -> SUP (SLS, CMP); PAY -> RET (LEG, TRS); PRC -> PSV (TRS, PRC); PSV -> TRS (FIN, LEG); RET -> LEG (SUP, CUS); SLS -> CMP (DEN, SLS); SUP -> SLS (CMP, PAY); TRS -> FIN (LEG, SUP). Codes ascending, joined by a comma and one space. Expected: CMP, PRC, SLS.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 4, + "grading_target": "Spreadsheets (.xlsx, .xls, .xlsm, .ods)", + "dependencies": [] + }, + "criterion 87": { + "description": "States the summary sheet value for short_feeder_departments as exactly \"TRS\" (acceptable value is that exact list).", + "justification": "Rule: workforce_staffing_rules.pdf Section 5: departments with fewer than three feeders in all (Section 4 feeders, both charts, all three transitions): CMP 11; CUS 12; CXD 12; DEN 7; FAC 11; FIN 9; GRW 11; LEG 9; PAY 8; PRC 12; PSV 12; RET 13; SLS 10; SUP 11; TRS 2. Codes ascending, joined by a comma and one space. Expected: TRS.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 4, + "grading_target": "Spreadsheets (.xlsx, .xls, .xlsm, .ods)", + "dependencies": [] + }, + "criterion 88": { + "description": "Leaves no template placeholder content in the output: no cell in either sheet reads SHEET TITLE, COLUMN HEADER, COLUMN HEADER 2 to COLUMN HEADER 5, HEADER, HEADER 2 to HEADER 5, ROW LABEL, Row Header, Week 1 to Week 4 or data, and no 'Image Placeholder' box remains on either sheet.", + "justification": "Source: workforce_staffing_rules.pdf Section 6 (Format): replace all template placeholder text and the placeholder box itself; none of it may remain in the output. The listed strings are every placeholder value in ZenAnalytics_Branding.xlsx sheets 1 and 2; the 'Image Placeholder' box is the template's logo slot, which the logo replaces. A cell fails when its whole trimmed value matches a listed string, case-insensitive; the words inside real content (e.g. a department named Data Engineering) do not count. Copying template rows, headers or titles without replacing them fails, and so does leaving the placeholder box alongside or instead of the logo.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Spreadsheets (.xlsx, .xls, .xlsm, .ods)", + "dependencies": [] + }, + "criterion 89": { + "description": "Formats the title and header text of both worksheets in white (#FFFFFF).", + "justification": "Source: workforce_staffing_rules.pdf Section 6 (Format): each output sheet takes the layout and styling of the template sheet in the same position (department_reads follows template sheet 1, Sheet_Title-1; summary follows template sheet 2, Sheet_Title-2). Templates Sheet_Title-1 and Sheet_Title-2: title cell A1 and every header cell in row 2 are with font colour #FFFFFF.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Spreadsheets (.xlsx, .xls, .xlsm, .ods)", + "dependencies": [] + }, + "criterion 90": { + "description": "Formats the title and header text of both worksheets horizontally centered.", + "justification": "Source: workforce_staffing_rules.pdf Section 6 (Format): each output sheet takes the layout and styling of the template sheet in the same position (department_reads follows template sheet 1, Sheet_Title-1; summary follows template sheet 2, Sheet_Title-2). Templates Sheet_Title-1 and Sheet_Title-2: title cell A1 and every header cell in row 2 are horizontal alignment center.", + "weight": "Primary objective(s)", + "criterion_tags": [], + "criterion_weight": 1, + "grading_target": "Spreadsheets (.xlsx, .xls, .xlsm, .ods)", + "dependencies": [] + } +} \ No newline at end of file